Re: lenny Installer with PXE on HP DL360G5 / bnx2
On Wed, Sep 10, 2008 at 01:51:22PM +0200, Christian Hofstaedtler wrote: > I've tried this with the lenny installer daily build from today; on > amd64. Installation works, but: > > - the firmware files on the installed system (in /lib/firmware) are owned > by the initial user, not by root. That's because the permissions of the files in the initrd are kept when firmware are copied. You probably have copied the firmware file as a non-root user before recreating the initrd. > - the firmware-bnx2 package is not installed, those files are not > claimed by any package. I wonder how they will get updated, if > needed? You will need to install the package manually (but this can be automated by a simple preseeding file). > BTW, the manual [1] doesn't seem to contain this info yet, may be > this should be added at some point? Probably, yes. :) Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Re: lenny Installer with PXE on HP DL360G5 / bnx2
On 2008-09-09 23:11:13, Jérémy Bobbio wrote: > On Tue, Sep 09, 2008 at 03:29:42PM +0200, Christian Hofstaedtler wrote: > > How is one supposed to install from the network/PXE on such common > > hardware? > > You will need to add the firmware to the initrd.gz available on your > TFTP server. You can find it in the bnx2-firmware package in the > non-free section of the archive. Then use gzip and cpio to extract and > compress the image again: > > * Extract in current directory: >$ zcat /path/to/installer/initrd.gz | cpio -iv > > * Create a new image from the current directory: >$ find . -print0 | cpio -0 -H newc -ov | \ >gzip -c > /path/to/installer/initrd.gz > I've tried this with the lenny installer daily build from today; on amd64. Installation works, but: - the firmware files on the installed system (in /lib/firmware) are owned by the initial user, not by root. - the firmware-bnx2 package is not installed, those files are not claimed by any package. I wonder how they will get updated, if needed? Are these known issues or shall I write a bug report? (Didn't find any bugs against debian-installer, but then that may be the wrong package?) BTW, the manual [1] doesn't seem to contain this info yet, may be this should be added at some point? Chris [1] http://d-i.alioth.debian.org/manual/en.amd64/ -- Christian Hofstädtler InQnet GmbH, Praterstrasse 31, Vienna, Austria -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lenny Installer with PXE on HP DL360G5 / bnx2
On Tue, Sep 09, 2008 at 11:42:11PM +0200, Christian Hofstaedtler wrote: > I fully understand. Why was this then OK for etch, but not for > lenny? (Not wanting to start a discussion about this, just want to > know why things have changed.) See #383403 [1] which was not addressed properly for etch (tagged etch-ignore) along with other non-free firmwares present in the kernel. Lenny now finally have proper ways to deal with such issues! :) [1] http://bugs.debian.org/383403 Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Re: lenny Installer with PXE on HP DL360G5 / bnx2
* Jérémy Bobbio <[EMAIL PROTECTED]> [080909 23:11]: > On Tue, Sep 09, 2008 at 03:29:42PM +0200, Christian Hofstaedtler wrote: > > We've got quite a few machines from HP, of type ProLiant DL360 G5. We > > used to install etch using the etch installer netboot media + > > pxelinux. This worked quite fine. > > > > Now I'm testing lenny (beta2 installer), and I found that the network > > cards in these servers (bnx2) seem to require a firmware, which is not > > in the installer image, but is available seperately. As the firmware is > > not in the image, and I'm booting from a PXE server, installing just > > doesn't work (without plugging in an USB key, but that makes booting > > from PXE quite useless). > > Please use the daily builds instead of beta2 to do your tests. A lot of > issues present in the beta 2 have been addressed since. Will try again with those. > > Is this the intended behaviour? > > Yes: Debian is 100% free software and the firmware needed for bnx2 is > not. The other option would have been to completely remove the bnx2 > module from kernel shipped by Debian. I fully understand. Why was this then OK for etch, but not for lenny? (Not wanting to start a discussion about this, just want to know why things have changed.) > > How is one supposed to install from the network/PXE on such common > > hardware? > > You will need to add the firmware to the initrd.gz available on your > TFTP server. You can find it in the bnx2-firmware package in the > non-free section of the archive. Then use gzip and cpio to extract and > compress the image again: > > * Extract in current directory: >$ zcat /path/to/installer/initrd.gz | cpio -iv > > * Create a new image from the current directory: >$ find . -print0 | cpio -0 -H newc -ov | \ >gzip -c > /path/to/installer/initrd.gz Thanks for the instructions. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lenny Installer with PXE on HP DL360G5 / bnx2
On Tue, Sep 09, 2008 at 03:29:42PM +0200, Christian Hofstaedtler wrote: > We've got quite a few machines from HP, of type ProLiant DL360 G5. We > used to install etch using the etch installer netboot media + > pxelinux. This worked quite fine. > > Now I'm testing lenny (beta2 installer), and I found that the network > cards in these servers (bnx2) seem to require a firmware, which is not > in the installer image, but is available seperately. As the firmware is > not in the image, and I'm booting from a PXE server, installing just > doesn't work (without plugging in an USB key, but that makes booting > from PXE quite useless). Please use the daily builds instead of beta2 to do your tests. A lot of issues present in the beta 2 have been addressed since. > Is this the intended behaviour? Yes: Debian is 100% free software and the firmware needed for bnx2 is not. The other option would have been to completely remove the bnx2 module from kernel shipped by Debian. > How is one supposed to install from the network/PXE on such common > hardware? You will need to add the firmware to the initrd.gz available on your TFTP server. You can find it in the bnx2-firmware package in the non-free section of the archive. Then use gzip and cpio to extract and compress the image again: * Extract in current directory: $ zcat /path/to/installer/initrd.gz | cpio -iv * Create a new image from the current directory: $ find . -print0 | cpio -0 -H newc -ov | \ gzip -c > /path/to/installer/initrd.gz Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
lenny Installer with PXE on HP DL360G5 / bnx2
Hello! We've got quite a few machines from HP, of type ProLiant DL360 G5. We used to install etch using the etch installer netboot media + pxelinux. This worked quite fine. Now I'm testing lenny (beta2 installer), and I found that the network cards in these servers (bnx2) seem to require a firmware, which is not in the installer image, but is available seperately. As the firmware is not in the image, and I'm booting from a PXE server, installing just doesn't work (without plugging in an USB key, but that makes booting from PXE quite useless). Is this the intended behaviour? How is one supposed to install from the network/PXE on such common hardware? Thanks, Christian -- Christian Hofstaedtler InQnet GmbH, Praterstrasse 31, Vienna, Austria -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]