On 23/02/12 20:21, Larry Stotler wrote:
On Thu, Feb 23, 2012 at 2:29 PM, Richard
Booting NET ISO (build 0003) still (*) fails with
"Insert CD number 1" but
backing up to the configuration and specifying network install parameters
(to local the server) loads the images and starts YaST. Yay!
(*) This also occurred with OSL 11.0, previously run on this box. Same
Yeah, evidently since there's no media it fails. There's probably a
way to set it up from the boot, but I don't remember how, and like you
said the work around does get you started.
SHA1 sum error: ftp://.../oss/boot/ppc/config Continue (Y/N). I said Y... Is
this just me (maybe a corrupted image, but rsync is good at not doing that and was
used for both transfers) or is it a bug?
More than likely it is the test of the package that is failing. I had
an issue with that with the older 10.x systems with a lot of MD5
errors on the packages from the CDs. It could be that there is a
problem with the RAM, which is what I think was wrong with mine.
However, I could usually skip enough to get a bootable system and fix
it then. Try doing a minimal install just to get a working system and
then add in what you need/want. That will also help narrow down where
we have broken packages.
I think the RAM & other hardware is OK - OS-X boots as expected.
I just realised that I can check the file SHA1 sum on the server - I'll
do that in the morning. Not sure how many people are on this list, I
assume no-one else sees the error but is that because no-one is testing?
Or is the sum wrong on the repo?
YaST then reports no hard disc, and getting a console with
Alt-F2 and running "fdisk -l" confirms this. I assume the necessary module
is not being loaded, but how do I find which one? I may be able to run OSL
11.0 again to see what it loads, if I can find the Hard Disc - or at least a
gzipped image to create one. Sounds like a bug unless caused by (1) - I
wonder if it's worth creating one in bugzilla?
Are you sure there's a disk in it? You should use pdisk to partition,
not fdisk. fdisk should still see the drive but it will be empty.
My bad. But there is an HD - it boots OS-X just fine. So "fdisk -l"
should at least report it, as should pdisk. Will try the latter tomorrow.
Looks to me like a missing module - I need that OSL 11.0 HD
IIRC some machines still show the drives as IDE with
I'll check this, but "pdisk -l" alone (no device specifier) should list
all devices (subject to driver modules), no?
Hardware is a
G3 "New world" iMac from 1999 (the iconic translucent blue
model) ("G5" in my earlier message was a typo). 512M RAM, 333 MHz PPC CPU. I
also have somewhere a MacBook from the same era, will try that too when I
It would be a PowerBook from that era. MacBooks are Intel based.
Just make sure it's not an Old World Mac. Those won't boot from CD
like the newer Colored Macs.
Again, my bad. I think it's a Powerbook ("Lombard" G3, with a dodgy
I don't have a fast enough internet connection to
do an install so I
haven't had time to test it yet.
rsync is your friend! repo is around 10G at the moment.
I DID grab the Fedora 16 PPC install DVD and hop to try it out next
week when I have time.
Is that easy to find on their site? I'd appreciate a link if not.
Linux user # 439271
To unsubscribe, e-mail: opensuse-ppc+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-ppc+owner(a)opensuse.org