(B> Perhaps you can explain initrd kernel images to me one day :-)
(BIf I had a clue, I most certainly would. Thanks for your help ;-)
(B--
(B: : : : : DataFly.Net : : : : :
(BComplete Web Services
(Bhttp://www.datafly.net
> Thank you thank you thank you!!!
>
> My mac is back in action and kde is purring...
>
> :-)
>
> Thanks again guys!
>
> Sean
Pleased to hear you're back up and running.
Perhaps you can explain initrd kernel images to me one day :-)
sebyte
Thank you thank you thank you!!!
My mac is back in action and kde is purring...
:-)
Thanks again guys!
Sean
On Sunday 11 July 2004 12:06 am, Rafael Ávila de Espíndola wrote:
> Em Saturday 10 July 2004 11:55, Sean Schertell escreveu:
> > I tried this:
> > linux root=/dev/hda11
> >
> > But stil
On Sat, Jul 10, 2004 at 11:09:38PM +0900, Sean Schertell wrote:
> You were right Sebyte, I needed to use your ISO, not the one I had. So I
> was able to mount my fs, but then in an effort to change my initrd.img.old
> symlink, I accidentally hosed my real initrd.img-2.4.25-powerpc! Doh!
Ah,
Well that chroot and then apt-get trick is pretty neat. But no network =
no new kernel. I guess I'll see if I can get the network up, then fire up
the shell, then mount my partition, then chroot into it, then apt-get my
kernel, then fix yaboot --- ugh.. hope I can figure out how to bring up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em Saturday 10 July 2004 11:55, Sean Schertell escreveu:
> I tried this:
> linux root=/dev/hda11
>
> But still no joy...
Boot with the cdrom, mount /dev/hda11 and chroot into it. Now you may
"apt-get install" a kernel.
Good luck.
Rafael
-BEGIN
I tried this:
linux root=/dev/hda11
But still no joy...
On Saturday 10 July 2004 11:47 pm, Rafael Ávila de Espíndola wrote:
> Em Saturday 10 July 2004 11:09, Sean Schertell escreveu:
> > Oh man.. This just keeps getting dumber :-(
> >
> > You were right Sebyte, I needed to use your ISO, not th
-BEGIN PGP SIGNED MESSAGE-
(BHash: SHA1
(B
(BEm Saturday 10 July 2004 11:09, Sean Schertell escreveu:
(B> Oh man.. This just keeps getting dumber :-(
(B>
(B> You were right Sebyte, I needed to use your ISO, not the one I had. So I
(B> was able to mount my fs, but then in an effort t
Oh man.. This just keeps getting dumber :-(
(B
(BYou were right Sebyte, I needed to use your ISO, not the one I had. So I
(Bwas able to mount my fs, but then in an effort to change my initrd.img.old
(Bsymlink, I accidentally hosed my real initrd.img-2.4.25-powerpc! Doh!
(BAnd of course t
> Thanks so much for your help Sebyte (and Colin). Unfortunately, neither
> method seems to work for me. Colin's method looks like it's gonna work
> but then panics for some reason. Sebyte's method looks good up until I
> try to mount my filesystem --- there's nothing useful in /dev
On Saturday 10 July 2004 08:47 pm, you wrote:
(B> On Saturday, July 10, 2004, at 10:07 am, Sean Schertell wrote:
(B> > Please help! I've gotta get some work done quickly but I seem to have
(B> > killed my yaboot and can't boot. It's on a PowerBook, so no floppy.
(B> > I got
(B> > hit with t
On Saturday, July 10, 2004, at 10:07 am, Sean Schertell wrote:
Please help! I've gotta get some work done quickly but I seem to have
killed my yaboot and can't boot. It's on a PowerBook, so no floppy. I got
hit with the bug in module-init-tools 3.1-pre2-1 which causes this
craziness:
modp
On Sat, Jul 10, 2004 at 06:07:37PM +0900, Sean Schertell wrote:
> Please help! I've gotta get some work done quickly but I seem to have
> killed my yaboot and can't boot. It's on a PowerBook, so no floppy. I got
> hit with the bug in module-init-tools 3.1-pre2-1 which causes this
> craziness:
Please help! I've gotta get some work done quickly but I seem to have
killed my yaboot and can't boot. It's on a PowerBook, so no floppy. I got
hit with the bug in module-init-tools 3.1-pre2-1 which causes this
craziness:
modprobe: FATAL: Could not open '/lib/modules/something...
modprobe: F
14 matches
Mail list logo
