Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 73895 - Tadpole Sparcle 650 and Viper fail to boot live CD
Summary: Tadpole Sparcle 650 and Viper fail to boot live CD
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Everything (show other bugs)
Hardware: Sparc Linux
: High major (vote)
Assignee: Gentoo LiveCD Package Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-09 04:28 UTC by Edward Gent
Modified: 2005-08-03 07:10 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Edward Gent 2004-12-09 04:28:45 UTC
Tried with 2004-2 and 2004-3 ISO
Tried with uni processor and SMP images

Failed to boot as follows:

Tadpole Sparcle 650SX (UltraSPARC-IIe 650MHz) PMU version 1.42
OpenBoot 4.03 Tadpole 1.05, 2048 MB Memory

boot cdrom
enters SILO -> Welcome banner
boot: help -> works
boot: gentoo-2.4
Loading initial ramdisk....

Remapping the kernel... done.
Booting Linux...
clock_probe: Cannot find timer chip
Program terminated


Viper

SILO loads correctly
boot: gentoo-2.4

PCI: Bogus PROM assignment. BUS[00] DEVFN[18]
PCI: phys[82001810:00000000:0010200] size[00000000:00002000]
PCI: res[0000000000200000->000000000020ffff:(204)

Please note: both these boxes are available to me for experimentation.

ted


Reproducible: Always
Steps to Reproduce:
1. boot cdrom
2. at SILO boot prompt boot gentoo-2.4
3.

Actual Results:  
As in details

Expected Results:  
Boot to LiveCD Linux
Comment 1 Ciaran McCreesh 2004-12-10 06:42:52 UTC
Yeah, we kinda know about this... Unfortunately Tadpole won't lend us a box so we can't really get the kernel fixed up to play nice with them...
Comment 2 Gustavo Zacarias (RETIRED) gentoo-dev 2005-08-03 07:10:44 UTC
Since we lack hardware and/or information to fix this we can't do anything about it.
Closing as UPSTREAM since it's very likely the kernel maintainers would be able
to fix this - if they had the hardware or needed information (blame tadpole).