Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 79326 - sparc64-universal-2004.3 fails with "clock_probe: Could not find timer chip"
Summary: sparc64-universal-2004.3 fails with "clock_probe: Could not find timer chip"
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Everything (show other bugs)
Hardware: Sparc Linux
: High major
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-24 05:52 UTC by Joseph D. Wieber, Jr.
Modified: 2005-05-16 10:39 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph D. Wieber, Jr. 2005-01-24 05:52:45 UTC 
I have a sunblade1500 with OBP version 4.16.4 that I'm trying to install gentoo on. I started off with OBP version 4.9.5 and the cd booted fine. I got the install to complete successfully, but could not get silo to boot. I scoured the net and tried all (valid) suggestions with no success. The final suggestion I tried was updating OBP. I upgraded to the version above and now the sparc64-universal-2004.3 cd fails with "clock_probe: Could not find timer chip". When we put the hdd with solaris on it, it boots fine. Here is a link http://forums.gentoo.org/viewtopic.php?t=282777&highlight=silo to my posting on the gentoo forum. It has a more detailed explanation of the whole issue. 

Reproducible: Always
Steps to Reproduce:
1.ok boot cdrom
2.
3.

Actual Results:  
clock_probe: Could not find timer chip

Expected Results:  
Live cd should have loaded so I could chroot into my gentoo env and try to fix 
silo.

http://forums.gentoo.org/viewtopic.php?t=282777&highlight=silo
Comment 1 Jason Wever (RETIRED) gentoo-dev 2005-03-06 20:08:24 UTC 
Please try http://dev.gentoo.org/~gustavoz/sparc/experimental/gentoo-sparc64-20050306.iso and see if this fixes the issue for you.
Comment 2 Chris Gianelloni (RETIRED) gentoo-dev 2005-05-16 10:39:49 UTC 
Please REOPEN if this is still an issue with 2005.0's release.