Re: dracut warning: could not boot
On Fri, Sep 26, 2014 at 03:36:17PM +0200, Thomas Lange wrote: > > On Tue, 29 Jul 2014 16:20:22 -0500, Peter Keller > > said: > > > /etc/dracut.conf.d/whatever.conf file. Then, how do I run dracut > > such that it reproduces the initrd.img.blah in the /boot chroot > > which > chroot /srv/fai/nfsroot dpkg-reconfigure dracut Awesome! Thanks! -pete
Re: dracut warning: could not boot
> On Tue, 29 Jul 2014 16:20:22 -0500, Peter Keller > said: > /etc/dracut.conf.d/whatever.conf file. Then, how do I run dracut > such that it reproduces the initrd.img.blah in the /boot chroot > which chroot /srv/fai/nfsroot dpkg-reconfigure dracut -- regards Thomas
Re: dracut warning: could not boot
On Tue, Jul 29, 2014 at 10:04:03PM +0200, Thomas Lange wrote: > > On Tue, 29 Jul 2014 13:24:42 -0500, Peter Keller > > said: > > Basically, I need to add some more modules into the initrd in order > > for a USB dongle to be (I hope) properly set up after the PXE boot, > > but I'm not sure how to do that in the new dracut world order. > man dracut.conf, then look at > add_drivers+= Ok, so I get that I'll have to add the drivers I want into the nfsroot's /etc/dracut.conf.d/whatever.conf file. Then, how do I run dracut such that it reproduces the initrd.img.blah in the /boot chroot which contains the new modules? The default output is to /boot/initramfs-blah, so I must be missing something about what to tell dracut. Then, I assume I copy the new initrd out of the nfsroot and stick it into the tftp directory. Right? Thank you! -pete
Re: dracut warning: could not boot
> On Tue, 29 Jul 2014 13:24:42 -0500, Peter Keller > said: > Basically, I need to add some more modules into the initrd in order > for a USB dongle to be (I hope) properly set up after the PXE boot, > but I'm not sure how to do that in the new dracut world order. man dracut.conf, then look at add_drivers+= -- regards Thomas
Re: dracut warning: could not boot
On Sat, Jul 26, 2014 at 08:26:20PM +0200, Carsten Aulbert wrote: > On 07/25/2014 06:33 PM, Peter Keller wrote: > > It *seems* that after the kernel boots and discovers the usb devices, it > > somehow suddenly forgets that it is using the usb device as a network > > interface card. > > I also think so, that sems to be the norm if your booted kernel does not > support this card out of the box (e.g. missing non-free firmware) So, I found this message from the fai lists: http://comments.gmane.org/gmane.linux.debian.fai/8253 except it uses the old(?) initramfs method of FAI from a while ago. Now, FAI uses dracut, so what is the translation of the above into dracut? Basically, I need to add some more modules into the initrd in order for a USB dongle to be (I hope) properly set up after the PXE boot, but I'm not sure how to do that in the new dracut world order. Thank you! -pete
Re: dracut warning: could not boot
Hi Pete On 07/25/2014 06:33 PM, Peter Keller wrote: > > .. Relatively normal stuff. > ... [snip] > ... Refined TSC clocksource calibration: 1596.373 MHz. > ... Switching to clocksource tsc > > ... dracut Warning: Could not boot. > dracut Warning: Could not boot. > > Dropping to debug shell > /bin/sh: 0: can't access tty; job control turned off > dracut:/# > you could add dracut debug messages by adding command line arguments (to the kernel pxeconfig line) http://fedoraproject.org/wiki/How_to_debug_Dracut_problems#Additional_dracut_boot_parameters > It *seems* that after the kernel boots and discovers the usb devices, it > somehow suddenly forgets that it is using the usb device as a network > interface card. > I also think so, that sems to be the norm if your booted kernel does not support this card out of the box (e.g. missing non-free firmware) > Also, Thank You for all the great help I've gotten on this list. I > know sometimes I get answers then vanish for a week without saying > thanks. Sorry about that. HTH Carsten -- Dr. Carsten Aulbert - Max Planck Institute for Gravitational Physics Callinstrasse 38, 30167 Hannover, Germany phone/fax: +49 511 762-17185 / -17193 https://wiki.atlas.aei.uni-hannover.de/foswiki/bin/view/ATLAS/WebHome
dracut warning: could not boot
Hello, I just run into an odd problem on an asus laptop that I'd like to install with FAI. This laptop is normally a wireless laptop, but with a asix usb dongle to a hard line network, the bios can be convinced to perform PXE booting. The PXE boot works fine(miraculously), and the FAI installation kernel is found and loaded over the network. Then, after a relatively normal kernel boot, I get: .. Relatively normal stuff. ... [snip] ... Refined TSC clocksource calibration: 1596.373 MHz. ... Switching to clocksource tsc ... dracut Warning: Could not boot. dracut Warning: Could not boot. Dropping to debug shell /bin/sh: 0: can't access tty; job control turned off dracut:/# I currently have disabled nfs4 on the fai server by exporting an empty nfs4 directory with fsid=0, the rest of the nfs exports should be nfsv3. It *seems* that after the kernel boots and discovers the usb devices, it somehow suddenly forgets that it is using the usb device as a network interface card. An 'ip link' at the prompt show only the loopback address. I believe this might be why dracut suddenlly got confused. It is as if the kernel suddenly forgot about eth0. Any ideas how to make FAI installation to a laptop with a USB dongle work? Also, Thank You for all the great help I've gotten on this list. I know sometimes I get answers then vanish for a week without saying thanks. Sorry about that. -pete
