[opensuse] [solved] Add driver to initrd for pxe-boot



I was on the wrong track... putting broadcom into the kernel (not into initrd)
finally did the trick!
In detail:
when the pxe client stopped in linuxrc because of the network error, I fetched /proc/config.gz.
This file contains the configuration for the pxe kernel.
After that, I installed OpenSUSE12.1 from DVD on the computer, and compiled a kernel with
make bzImage and the configuration from the client.
With this kernel image and the old initrd, the client was now able to do the autoinstallation!

Thanks,
Markus
________________________________________
Von: Weich, Markus
Gesendet: Freitag, 17. August 2012 13:32
An: Philipp Thomas
Betreff: AW: [opensuse] Add driver to initrd for pxe-boot

I tried mkinitrd before. It doesn't work with pxe because the
installation routines are in pxe initrd. The tutorials I found on the
internet all unpacked, modified and repacked initrd.
But the format of openSUSE 12.1 pxe initrd seems special:
etc/depmod.d and modprobe.d aren't covered in the
tutorials I found. Nevertheless I messed around with them, too.
No success.

I also tried bootparam keeppxe, didn't work neither.

What i'll try next:
-compile the kernel with the /proc/config.gz from the
pxe environment
- or put all the needed modules into /modules/..., not just only
broadcom and do the depmod thing again...

Any other suggestions are welcome!
Thanks, Markus

________________________________________
Von: Philipp Thomas [Philipp.Thomas2@xxxxxxx]
Gesendet: Freitag, 17. August 2012 13:15
An: opensuse@xxxxxxxxxxxx
Betreff: Re: [opensuse] Add driver to initrd for pxe-boot

[Please use a fixed line length of less than 80 characters as that's
much easier to read, specially when you use text mode MUAs]

On Fri, 17 Aug 2012 00:17:14 +0000, <markus.weich@xxxxxxxxxxxxxxxx>
wrote:

I asked Uwe Gansert, the author of autoyast, and he told me
that broadcom.ko needs to be in the initrd. But how do i get
broadcom.ko into initrd?

For a normal system you would add the needed modules to INITRD_MODULES
in /etc/sysconfig/kernel and call mkinitrd to create the new initrd.
See 'man 8 mkinitrd' for the options mkinitrd supports.

Philipp
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx



Relevant Pages

  • Re: boot a system from PXE
    ... Try Linux Terminal Server Project ... Diskless client overview: ... capability - put the kernel in the /tftpboot location used by pxe client ...
    (linux.redhat.install)
  • diskless boot: anyone else having trouble with network in initrd nashafter PXE?
    ... When booting diskless, after PXE gets an IP address from DHCP and boots the kernel, the initrd is loaded and nash runs the init script. ...
    (Fedora)
  • Network card that does not support pxe
    ... Is it possible to remote boot a client downloading the kernel and ... initrd with a network card that does not support remote boot? ... the kernel and initrd from a TFPT server? ...
    (comp.os.linux.networking)
  • Re: Installing Ubuntu Server on HP ProLiant DL140 w/o CD
    ... You can PXEboot the installer and do net installs. ... The kernel and ... initrd for doing PXE should be in the install dir on the ISO image. ...
    (Ubuntu)
  • Re: booting from ISO image on HD?
    ... >> through customized initrd files for each one. ... > between the loopback device and the underlying file (the iso image). ... I have to insmod the loop kernel module(e.g. ... how can you boot it from an initrd??? ...
    (comp.os.linux.misc)