Re: quik and initrd and kernel-image-2.6.7-powerpc

2004-08-04 Thread Simon Vallet
On Wed, 04 Aug 2004 13:17:39 +0200 Christian Leimer <[EMAIL PROTECTED]> wrote: > > So It could be a quik problem? Is there a way of yaboot for oldworld? > Or is it my wrong config or the kernel-image? Still trying to find the > problem. I think it is : I posted to the list about this at that ti

Re: quik and initrd and kernel-image-2.6.7-powerpc

2004-08-04 Thread Jens Schmalzing
Hi, Rick Thomas writes: > the 2.6.7 kernel works just fine on my beige G3 minitower, unless > you're trying to use the onboard SCSI. Currently, the "mesh" SCSI > controller driver module is not available for the 2.6.7 kernel on > the powerpc CD-ROMs. That driver is installed as part of kernel-i

Re: quik and initrd and kernel-image-2.6.7-powerpc

2004-08-04 Thread Christian Leimer
Simon Vallet wrote: > Hi, > > On Tue, 03 Aug 2004 20:54:58 +0200 > Christian Leimer <[EMAIL PROTECTED]> wrote: > >> Anyone out there with an oldworld had luck with the >> kernel-image-2.6.7-powerpc froms sarge? > custom 2.6.7 works fine here on a beige G3 booted with quik... I don't > use any in

Re: quik and initrd and kernel-image-2.6.7-powerpc

2004-08-04 Thread Christian Leimer
Rick_Thomas wrote: > On Tue, 2004-08-03 at 14:54, Christian Leimer wrote: > >> Anyone out there with an oldworld had luck with the >> kernel-image-2.6.7-powerpc froms sarge? > > > I don't use quik, so this may not be relevant to your situation, but I > find that with BootX, the 2.6.7 kernel wor

Re: quik and initrd and kernel-image-2.6.7-powerpc

2004-08-04 Thread Simon Vallet
Hi, On Tue, 03 Aug 2004 20:54:58 +0200 Christian Leimer <[EMAIL PROTECTED]> wrote: > Anyone out there with an oldworld had luck with the > kernel-image-2.6.7-powerpc froms sarge? custom 2.6.7 works fine here on a beige G3 booted with quik... I don't use any initrd, though... I can remember havin

Re: quik and initrd and kernel-image-2.6.7-powerpc

2004-08-03 Thread Rick_Thomas
On Tue, 2004-08-03 at 14:54, Christian Leimer wrote: > Anyone out there with an oldworld had luck with the > kernel-image-2.6.7-powerpc froms sarge? I don't use quik, so this may not be relevant to your situation, but I find that with BootX, the 2.6.7 kernel works just fine on my beige G3 minito

Re: quik and initrd and kernel-image-2.6.7-powerpc

2004-08-03 Thread Christian Leimer
Derrik Pates wrote: > Christian Leimer wrote: >> Now I have this in my quik.conf: >> >> image = /boot/vmlinux >> ramdisk=/boot/initrd.img >> root=/dev/sda5 >> label = test >> >> but still does not work. >> >> My disk is connected to an uw adaptec card. >> How do I tell t

Re: quik and initrd and kernel-image-2.6.7-powerpc

2004-08-03 Thread Derrik Pates
Christian Leimer wrote: Now I have this in my quik.conf: image = /boot/vmlinux ramdisk=/boot/initrd.img root=/dev/sda5 label = test but still does not work. My disk is connected to an uw adaptec card. How do I tell the kernel to use the aic7xxx module? Do you have a s

Re: quik and initrd and kernel-image-2.6.7-powerpc

2004-08-02 Thread Christian Leimer
Derrik Pates wrote: > Christian Leimer wrote: >> What do I have to add to the quik.conf file? I can not find something in >> my bootloader manual. Is initrd supported by quik? > > The man page says the parameter in quik.conf is 'ramdisk='. Also, > specify the full path to the initrd - if it's in

Re: quik and initrd and kernel-image-2.6.7-powerpc

2004-07-31 Thread Derrik Pates
Christian Leimer wrote: What do I have to add to the quik.conf file? I can not find something in my bootloader manual. Is initrd supported by quik? The man page says the parameter in quik.conf is 'ramdisk='. Also, specify the full path to the initrd - if it's in /boot (and you don't have a se

quik and initrd and kernel-image-2.6.7-powerpc

2004-07-31 Thread Christian Leimer
Hi! Is it possible to boot on oldworld with quik and an initrd kernel-image like the actual 2.6.7-3? Anyone had sucsess? What do I have to add to the quik.conf file? I can not find something in my bootloader manual. Is initrd supported by quik? This does not work: image = /boot/vmlinux