[SuSE Linux] Initrd image fails...
11 Dec
1998
11 Dec
'98
10:15
Hi, I've rebuilt my kernel, recompiled it and now my document is telling me to create an 'initrd image' in order to load my SCSI modules at boot time. When I try to run ' # /sbin/mkinitrd /boot/initrd-2.0.35.img 2.0.35' I get the following error. # mount: the kernel does not recognize /dev/loop0 as a block device (maybe 'insmod driver' ?) Can't get a loopback device. This suggests that the loopback block device is unavailable or that a line for the scsi adapter is missing from my /etc/conf.modules file (which is not!). What should I do ? Can I install the new compiled kernel and use the old image file ? -- Luca Colombi System Administrator The Hub Communications Co. Ltd. The Farmhouse Syon Park Middlesex TW8 8JF Tel: +44(0)181 560 9222 Fax: +44(0)181 560 9333 E-mail: luca@thehub.co.uk URL: <A HREF="http://www.thehub.co.uk"><A HREF="http://www.thehub.co.uk</A">http://www.thehub.co.uk</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
11 Dec
11 Dec
14:12
New subject: [SuSE Linux] Re: Initrd image fails...
Hi, On Fri, Dec 11, Luca Colombi wrote:
I've rebuilt my kernel, recompiled it and now my document is telling me to create an 'initrd image' in order to load my SCSI modules at boot time.
Seems you are reading some Red Hat document ;-)
When I try to run ' # /sbin/mkinitrd /boot/initrd-2.0.35.img 2.0.35' I get the following error.
There's no need to use an initrd when compiling your own kernel. Just compile the SCSI driver in and you are fine.
# mount: the kernel does not recognize /dev/loop0 as a block device (maybe 'insmod driver' ?) Can't get a loopback device.
This suggests that the loopback block device is unavailable or that a line for the scsi adapter is missing from my /etc/conf.modules file (which is not!).
What should I do ? Can I install the new compiled kernel and use the old image file ?
-- Luca Colombi -o) Hubert Mantel Goodbye, dots... /\\ _\_v
There is no mkinitrd on a SuSE system. The Red Hat mkinitrd uses a loopback filesystem in order to create the initial ramdisk. So you need a loopback device. But if you are compiling the kernel on your own, why not simply compile the SCSI driver in? No need to fiddle around with initrd. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
18:06
New subject: [SuSE Linux] Re: Initrd image fails...
Hi Hubert, I think I am almost there but... :-( I've created a monolitic kernel, compress it with make bzImage and now I get the following problem: Starting kswapd v 1.4.2.2 sx: Special IO8+ driver v1.7, (c) R.E.Wolff 1997 sx: derived from work etc. sx: DTR/RTS pin is RTS when CRTSCTS is on. sx0: specialix I08+ Board at 0x100 not fount. sx1: specialix I08+ Board at 0x180 not fount. sx2: specialix I08+ Board at 0x250 not fount. sx3: specialix I08+ Board at 0x260 not fount. sx: No specialix I08+ boards detected. loop: registered device at major 7 etc. ... FDC 0 is a National Semiconductor PC87306 (scsi 0) <Adaptec AHA-294X SCSI host adapter> found at PCI 11/0 (scsi 0) Narrow Channel, SCSI ID=7, 16/255 SCBs (scsi 0) BIOS enabled, IO Port 0x1100, IRQ=9 (scsi 0) IO Memory at 0x400001000, MMAP Memory at 0x3807000 (scsi 0) Resetting channel (scsi 0) Downloading sequencer code...406 instructions downloaded scsi 1: SCSI busy, waiting up to 5 seconds scsi 1: bus busy, attempting abort I guess I have to remove the IO8+ from the kernel, right ? but what' s scsi 1 ... it's my CD or I 've compiled too many SCSI devices on my kernel ? After receiving the 'attempting abort ' my machine won't do anything anymore. Any suggestion ? Hubert Mantel wrote: > Hi, > > On Fri, Dec 11, Luca Colombi wrote: > > > I've rebuilt my kernel, recompiled it and now my document is telling me > > to create an 'initrd image' in order to load my SCSI modules at boot > > time. > > Seems you are reading some Red Hat document ;-) > > > When I try to run ' # /sbin/mkinitrd /boot/initrd-2.0.35.img 2.0.35' > > I get the following error. > > There's no need to use an initrd when compiling your own kernel. Just > compile the SCSI driver in and you are fine. > > > # mount: the kernel does not recognize /dev/loop0 as a block device > > (maybe 'insmod driver' ?) > > Can't get a loopback device. > > There is no mkinitrd on a SuSE system. The Red Hat mkinitrd uses a > loopback filesystem in order to create the initial ramdisk. So you need a > loopback device. > But if you are compiling the kernel on your own, why not simply compile > the SCSI driver in? No need to fiddle around with initrd. > > > This suggests that the loopback block device is unavailable or that a > > line for the scsi adapter is missing from my /etc/conf.modules file > > (which is not!). > > > > What should I do ? > > Can I install the new compiled kernel and use the old image file ? > > > > > > > > -- > > Luca Colombi > -o) > Hubert Mantel Goodbye, dots... /\\ > _\_v > - > To get out of this list, please send email to majordomo@suse.com with > this text in its body: unsubscribe suse-linux-e > Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the > archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>> -- Luca Colombi System Administrator The Hub Communications Co. Ltd. The Farmhouse Syon Park Middlesex TW8 8JF Tel: +44(0)181 560 9222 Fax: +44(0)181 560 9333 E-mail: luca@thehub.co.uk URL: <A HREF="http://www.thehub.co.uk"><A HREF="http://www.thehub.co.uk</A">http://www.thehub.co.uk</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
13 Dec
13 Dec
11:40
New subject: [SuSE Linux] Re: Re: Initrd image fails...
Hi,
On Fri, Dec 11, Luca Colombi wrote:
> I think I am almost there but... :-(
>
> I've created a monolitic kernel, compress it with make bzImage and now I get
> the following problem:
>
>
> Starting kswapd v 1.4.2.2
> sx: Special IO8+ driver v1.7, (c) R.E.Wolff 1997
> sx: derived from work etc.
> sx: DTR/RTS pin is RTS when CRTSCTS is on.
> sx0: specialix I08+ Board at 0x100 not fount.
> sx1: specialix I08+ Board at 0x180 not fount.
> sx2: specialix I08+ Board at 0x250 not fount.
> sx3: specialix I08+ Board at 0x260 not fount.
> sx: No specialix I08+ boards detected.
> loop: registered device at major 7
> etc.
> ...
> FDC 0 is a National Semiconductor PC87306
> (scsi 0) <Adaptec AHA-294X SCSI host adapter> found at PCI 11/0
> (scsi 0) Narrow Channel, SCSI ID=7, 16/255 SCBs
> (scsi 0) BIOS enabled, IO Port 0x1100, IRQ=9
> (scsi 0) IO Memory at 0x400001000, MMAP Memory at 0x3807000
> (scsi 0) Resetting channel
> (scsi 0) Downloading sequencer code...406 instructions downloaded
> scsi 1: SCSI busy, waiting up to 5 seconds
> scsi 1: bus busy, attempting abort
>
> I guess I have to remove the IO8+ from the kernel, right ?
>
> but what' s scsi 1 ... it's my CD or I 've compiled too many SCSI devices on
> my kernel ?
Seems you compiled more than one SCSI lowlevel driver in. Or you have
multiple 2940's. Or...
It's almost impossible to help. you don't provide any information on your
hardware and on the config options of your kernel.
> After receiving the 'attempting abort ' my machine won't do anything
> anymore.
>
> Any suggestion ?
>
> Hubert Mantel wrote:
>
> > Hi,
> >
> > On Fri, Dec 11, Luca Colombi wrote:
> >
> > > I've rebuilt my kernel, recompiled it and now my document is telling me
> > > to create an 'initrd image' in order to load my SCSI modules at boot
> > > time.
> >
> > Seems you are reading some Red Hat document ;-)
> >
> > > When I try to run ' # /sbin/mkinitrd /boot/initrd-2.0.35.img 2.0.35'
> > > I get the following error.
> >
> > There's no need to use an initrd when compiling your own kernel. Just
> > compile the SCSI driver in and you are fine.
> >
> > > # mount: the kernel does not recognize /dev/loop0 as a block device
> > > (maybe 'insmod driver' ?)
> > > Can't get a loopback device.
> >
> > There is no mkinitrd on a SuSE system. The Red Hat mkinitrd uses a
> > loopback filesystem in order to create the initial ramdisk. So you need a
> > loopback device.
> > But if you are compiling the kernel on your own, why not simply compile
> > the SCSI driver in? No need to fiddle around with initrd.
> >
> > > This suggests that the loopback block device is unavailable or that a
> > > line for the scsi adapter is missing from my /etc/conf.modules file
> > > (which is not!).
> > >
> > > What should I do ?
> > > Can I install the new compiled kernel and use the old image file ?
> > >
> > >
> > >
> > > --
> > > Luca Colombi
> > -o)
> > Hubert Mantel Goodbye, dots... /\\
> > _\_v
> > -
> > To get out of this list, please send email to majordomo@suse.com with
> > this text in its body: unsubscribe suse-linux-e
> > Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the
> > archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
>
>
>
> --
> Luca Colombi
> System Administrator
> The Hub Communications Co. Ltd.
> The Farmhouse
> Syon Park
> Middlesex
> TW8 8JF
>
> Tel: +44(0)181 560 9222 Fax: +44(0)181 560 9333
> E-mail: luca@thehub.co.uk URL: <A HREF="http://www.thehub.co.uk"><A HREF="http://www.thehub.co.uk</A">http://www.thehub.co.uk</A</A>>
>
>
>
> -
> To get out of this list, please send email to majordomo@suse.com with
> this text in its body: unsubscribe suse-linux-e
> Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the
> archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
--
-o)
Hubert Mantel Goodbye, dots... /\\
_\_v
-
To get out of this list, please send email to majordomo@suse.com with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the
archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
14 Dec
14 Dec
09:15
New subject: [SuSE Linux] Re: Re: Initrd image fails...
Hi Hubert, I did compile too many SCSI interfaces, I went back to my .config file and made the necessary changes, re-compiled my kernel (as you suggested without modules ) and everything went fine. Thanks for your help! Cheers, Hubert Mantel wrote: > Hi, > > On Fri, Dec 11, Luca Colombi wrote: > > > I think I am almost there but... :-( > > > > I've created a monolitic kernel, compress it with make bzImage and now I get > > the following problem: > > > > > > Starting kswapd v 1.4.2.2 > > sx: Special IO8+ driver v1.7, (c) R.E.Wolff 1997 > > sx: derived from work etc. > > sx: DTR/RTS pin is RTS when CRTSCTS is on. > > sx0: specialix I08+ Board at 0x100 not fount. > > sx1: specialix I08+ Board at 0x180 not fount. > > sx2: specialix I08+ Board at 0x250 not fount. > > sx3: specialix I08+ Board at 0x260 not fount. > > sx: No specialix I08+ boards detected. > > loop: registered device at major 7 > > etc. > > ... > > FDC 0 is a National Semiconductor PC87306 > > (scsi 0) <Adaptec AHA-294X SCSI host adapter> found at PCI 11/0 > > (scsi 0) Narrow Channel, SCSI ID=7, 16/255 SCBs > > (scsi 0) BIOS enabled, IO Port 0x1100, IRQ=9 > > (scsi 0) IO Memory at 0x400001000, MMAP Memory at 0x3807000 > > (scsi 0) Resetting channel > > (scsi 0) Downloading sequencer code...406 instructions downloaded > > scsi 1: SCSI busy, waiting up to 5 seconds > > scsi 1: bus busy, attempting abort > > > > I guess I have to remove the IO8+ from the kernel, right ? > > > > but what' s scsi 1 ... it's my CD or I 've compiled too many SCSI devices on > > my kernel ? > > Seems you compiled more than one SCSI lowlevel driver in. Or you have > multiple 2940's. Or... > > It's almost impossible to help. you don't provide any information on your > hardware and on the config options of your kernel. > > > After receiving the 'attempting abort ' my machine won't do anything > > anymore. > > > > Any suggestion ? > > > > Hubert Mantel wrote: > > > > > Hi, > > > > > > On Fri, Dec 11, Luca Colombi wrote: > > > > > > > I've rebuilt my kernel, recompiled it and now my document is telling me > > > > to create an 'initrd image' in order to load my SCSI modules at boot > > > > time. > > > > > > Seems you are reading some Red Hat document ;-) > > > > > > > When I try to run ' # /sbin/mkinitrd /boot/initrd-2.0.35.img 2.0.35' > > > > I get the following error. > > > > > > There's no need to use an initrd when compiling your own kernel. Just > > > compile the SCSI driver in and you are fine. > > > > > > > # mount: the kernel does not recognize /dev/loop0 as a block device > > > > (maybe 'insmod driver' ?) > > > > Can't get a loopback device. > > > > > > There is no mkinitrd on a SuSE system. The Red Hat mkinitrd uses a > > > loopback filesystem in order to create the initial ramdisk. So you need a > > > loopback device. > > > But if you are compiling the kernel on your own, why not simply compile > > > the SCSI driver in? No need to fiddle around with initrd. > > > > > > > This suggests that the loopback block device is unavailable or that a > > > > line for the scsi adapter is missing from my /etc/conf.modules file > > > > (which is not!). > > > > > > > > What should I do ? > > > > Can I install the new compiled kernel and use the old image file ? > > > > > > > > > > > > > > > > -- > > > > Luca Colombi > > > -o) > > > Hubert Mantel Goodbye, dots... /\\ > > > _\_v > > > - > > > To get out of this list, please send email to majordomo@suse.com with > > > this text in its body: unsubscribe suse-linux-e > > > Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the > > > archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>> > > > > > > > > -- > > Luca Colombi > > System Administrator > > The Hub Communications Co. Ltd. > > The Farmhouse > > Syon Park > > Middlesex > > TW8 8JF > > > > Tel: +44(0)181 560 9222 Fax: +44(0)181 560 9333 > > E-mail: luca@thehub.co.uk URL: <A HREF="http://www.thehub.co.uk"><A HREF="http://www.thehub.co.uk</A">http://www.thehub.co.uk</A</A>> > > > > > > > > - > > To get out of this list, please send email to majordomo@suse.com with > > this text in its body: unsubscribe suse-linux-e > > Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the > > archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>> > > -- > -o) > Hubert Mantel Goodbye, dots... /\\ > _\_v > - > To get out of this list, please send email to majordomo@suse.com with > this text in its body: unsubscribe suse-linux-e > Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the > archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>> -- Luca Colombi System Administrator The Hub Communications Co. Ltd. The Farmhouse Syon Park Middlesex TW8 8JF Tel: +44(0)181 560 9222 Fax: +44(0)181 560 9333 E-mail: luca@thehub.co.uk URL: <A HREF="http://www.thehub.co.uk"><A HREF="http://www.thehub.co.uk</A">http://www.thehub.co.uk</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
9504
Age (days ago)
9507
Last active (days ago)
4 comments
2 participants
participants (2)
-
luca＠thehub.co.uk -
mantel＠suse.de