Hi,
I would like to do a network install using PIXES boot, however the ethernet device was not supported by centos installation (RTL8110SC). How do i add this module into the initrd? I know i can use: mkinitrd --with=r8169 `uname -r`, but i did not know what is the standard modules included in the installation initrd of Centos.
Thanks!
--beast
In article 20070810071942.GA3164@localhost.localdomain, beast beast@ldap.or.id wrote:
Hi,
I would like to do a network install using PIXES boot, however the ethernet device was not supported by centos installation (RTL8110SC). How do i add this module into the initrd? I know i can use: mkinitrd --with=r8169 `uname -r`, but i did not know what is the standard modules included in the installation initrd of Centos.
The initrd file is just a gzipped ext2 filesystem image, so you need to uncompress it into a temporary file and then mount that file using loopback:
zcat /boot/initrd-`uname -r`.img >/tmp/fs mkdir /mnt/initrd mount -r -t ext2 -o loop /tmp/fs /mnt/initrd
Then you can look under /mnt/initrd to see the contents of the initial ramdisk.
Cheers Tony
On 10/08/07 10:26 +0000, Tony Mountifield wrote:
In article 20070810071942.GA3164@localhost.localdomain, beast beast@ldap.or.id wrote:
Hi,
I would like to do a network install using PIXES boot, however the ethernet device was not supported by centos installation (RTL8110SC). How do i add this module into the initrd? I know i can use: mkinitrd --with=r8169 `uname -r`, but i did not know what is the standard modules included in the installation initrd of Centos.
The initrd file is just a gzipped ext2 filesystem image, so you need to uncompress it into a temporary file and then mount that file using loopback:
zcat /boot/initrd-`uname -r`.img >/tmp/fs mkdir /mnt/initrd mount -r -t ext2 -o loop /tmp/fs /mnt/initrd
Then you can look under /mnt/initrd to see the contents of the initial ramdisk.
Its not an image anymore : fs: ASCII cpio archive (SVR4 with no CRC)
However it can be extarct using cpio: gunzip < /boot/initrd-version.img |cpio -i --make-directories
Thanks for the hint.
--beast
In article 20070813042010.GA3338@localhost.localdomain, beast beast@ldap.or.id wrote:
On 10/08/07 10:26 +0000, Tony Mountifield wrote:
In article 20070810071942.GA3164@localhost.localdomain, beast beast@ldap.or.id wrote:
Hi,
I would like to do a network install using PIXES boot, however the ethernet device was not supported by centos installation (RTL8110SC). How do i add this module into the initrd? I know i can use: mkinitrd --with=r8169 `uname -r`, but i did not know what is the standard modules included in the installation initrd of Centos.
The initrd file is just a gzipped ext2 filesystem image, so you need to uncompress it into a temporary file and then mount that file using loopback:
zcat /boot/initrd-`uname -r`.img >/tmp/fs mkdir /mnt/initrd mount -r -t ext2 -o loop /tmp/fs /mnt/initrd
Then you can look under /mnt/initrd to see the contents of the initial ramdisk.
Its not an image anymore : fs: ASCII cpio archive (SVR4 with no CRC)
Ah, I didn't realise it had changed. I must admin the box I tried it on was my old FC1 system with a 2.4 kernel. Should have checked on a more recent system!
Thanks for the correction, and glad the hint helped anyway.
Cheers Tony
On 13/08/07 11:20 +0700, beast wrote:
The initrd file is just a gzipped ext2 filesystem image, so you need to uncompress it into a temporary file and then mount that file using loopback:
zcat /boot/initrd-`uname -r`.img >/tmp/fs mkdir /mnt/initrd mount -r -t ext2 -o loop /tmp/fs /mnt/initrd
Then you can look under /mnt/initrd to see the contents of the initial ramdisk.
Its not an image anymore : fs: ASCII cpio archive (SVR4 with no CRC)
However it can be extarct using cpio: gunzip < /boot/initrd-version.img |cpio -i --make-directories
Aparently its not as simply copy .ko file into modules.cgz. I have copied the ethernet driver, however it did not get loaded when loadning from pxeboot. Any other steps required?
--beast
one of the files /linuxrc should list what modules get loaded on start.
On Wed, 2007-08-15 at 20:23 +0700, beast wrote:
On 14/08/07 07:26 +0200, maze@cela.pl wrote:
one of the files /linuxrc should list what modules get loaded on start.
Thanks for the hint. Where linuxrc located? i already searched initrd image and can not found it.
Looks like the script "init" in the top level does the job. I would expect mkinitrd to generate it automatically if you add a module, but one should be able to modify it if doing the job manually.
Phil
On 15/08/07 17:38 -0400, Phil Schaffner wrote:
On Wed, 2007-08-15 at 20:23 +0700, beast wrote:
On 14/08/07 07:26 +0200, maze@cela.pl wrote:
one of the files /linuxrc should list what modules get loaded on start.
Thanks for the hint. Where linuxrc located? i already searched initrd image and can not found it.
Looks like the script "init" in the top level does the job. I would expect mkinitrd to generate it automatically if you add a module, but one should be able to modify it if doing the job manually.
/init is executable file, statically linked. Any other hints please? i've been googling around and no clue so far :( Looks like nobody willing to customize the boot image, and prefer to wait the new release and hoping it will be supported...
--beast
On Thu, 2007-08-16 at 12:02 +0700, beast wrote:
On 15/08/07 17:38 -0400, Phil Schaffner wrote:
On Wed, 2007-08-15 at 20:23 +0700, beast wrote:
On 14/08/07 07:26 +0200, maze@cela.pl wrote:
one of the files /linuxrc should list what modules get loaded on start.
Thanks for the hint. Where linuxrc located? i already searched initrd image and can not found it.
Looks like the script "init" in the top level does the job. I would expect mkinitrd to generate it automatically if you add a module, but one should be able to modify it if doing the job manually.
/init is executable file, statically linked.
Sorry - was looking at an initrd from an installed kernel - that "init" is a shell script. Looks like the installer initrd.img is a different beast :-) than those for the installed kernels or created by mkinitrd.
For the CentOS 5 installer initrd.img:
[root@wx1 TMP]# gunzip < /raid/RH/CentOS/5/os/i386/isolinux/initrd.img |cpio -i --make-directories 12907 blocks [root@wx1 TMP]# ll total 36 lrwxrwxrwx 1 root root 4 Aug 16 09:23 bin -> sbin drwxr-xr-x 2 root root 4096 Aug 16 09:23 dev drwxr-xr-x 3 root root 4096 Aug 16 09:23 etc lrwxrwxrwx 1 root root 10 Aug 16 09:23 init -> /sbin/init drwxr-xr-x 2 root root 4096 Aug 16 09:23 modules drwxr-xr-x 2 root root 4096 Aug 16 09:23 proc drwxr-xr-x 2 root root 4096 Aug 16 09:23 sbin drwxr-xr-x 2 root root 4096 Aug 16 09:23 selinux drwxr-xr-x 2 root root 4096 Aug 16 09:23 sys drwxr-xr-x 2 root root 4096 Aug 16 09:23 tmp drwxr-xr-x 6 root root 4096 Aug 16 09:23 var [root@wx1 TMP]# find . -type f -exec file {} ; ./.buildstamp: ASCII text ./.profile: ASCII text ./etc/loader.tr: gzip compressed data, from Unix, last modified: Tue Apr 10 15:26:52 2007, max compression ./etc/arch: ASCII text ./etc/terminfo/l/linux: Compiled terminfo entry ./etc/terminfo/v/vt100: Compiled terminfo entry ./etc/terminfo/v/vt100-nav: Compiled terminfo entry ./etc/lang-table: ASCII text ./etc/passwd: ASCII text ./etc/keymaps.gz: gzip compressed data, from Unix, last modified: Mon Feb 27 16:54:51 2006, max compression ./etc/screenfont.gz: gzip compressed data, was "screenfont-i386", from Unix, last modified: Fri Dec 13 09:51:44 2002, max compression ./sbin/loader: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, statically linked, for GNU/Linux 2.6.9, stripped ./sbin/init: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, statically linked, for GNU/Linux 2.6.9, stripped ./modules/module-info: ASCII text ./modules/modules.cgz: gzip compressed data, from Unix, last modified: Tue Apr 10 15:51:11 2007, max compression ./modules/modules.dep: ASCII text ./modules/modules.alias: ASCII text ./modules/pci.ids: ASCII text
Any other hints please? i've been googling around and no clue so far :(
Looks like nobody willing to customize the boot image, and prefer to wait the new release and hoping it will be supported...
For CentOS5 the r8169.ko module is in modules.cgz and the following entries are found in the text files:
[root@wx1 modules]# grep r8169 module-info modules.alias modules.dep module-info:r8169 modules.alias:alias pci:v00001737d00001032sv*sd00000024bc*sc*i* r8169 modules.alias:alias pci:v000016ECd00000116sv*sd*bc*sc*i* r8169 modules.alias:alias pci:v00001186d00004300sv*sd*bc*sc*i* r8169 modules.alias:alias pci:v000010ECd00008129sv*sd*bc*sc*i* r8169 modules.alias:alias pci:v000010ECd00008169sv*sd*bc*sc*i* r8169
Backing up to square 1 - What CentOS version are you trying to install?
Phil
On 16/08/07 10:12 -0400, Phil Schaffner wrote:
For CentOS5 the r8169.ko module is in modules.cgz and the following entries are found in the text files:
[root@wx1 modules]# grep r8169 module-info modules.alias modules.dep module-info:r8169 modules.alias:alias pci:v00001737d00001032sv*sd00000024bc*sc*i* r8169 modules.alias:alias pci:v000016ECd00000116sv*sd*bc*sc*i* r8169 modules.alias:alias pci:v00001186d00004300sv*sd*bc*sc*i* r8169 modules.alias:alias pci:v000010ECd00008129sv*sd*bc*sc*i* r8169 modules.alias:alias pci:v000010ECd00008169sv*sd*bc*sc*i* r8169
Yes, but this 'default' driver is not working on my PC, it seems the chipset is different, though it recognised as 8169/8110SC.
I have to download from realtek site and compile myself then it working wellby using modprobe. However i was trying to make C5 install from network, so its like chicken and egg problem :-(
Backing up to square 1 - What CentOS version are you trying to install?
Centos 5.0
--beast
beast wrote:
On 15/08/07 17:38 -0400, Phil Schaffner wrote:
On Wed, 2007-08-15 at 20:23 +0700, beast wrote:
On 14/08/07 07:26 +0200, maze@cela.pl wrote:
one of the files /linuxrc should list what modules get loaded on start.
Thanks for the hint. Where linuxrc located? i already searched initrd image and can not found it.
Looks like the script "init" in the top level does the job. I would expect mkinitrd to generate it automatically if you add a module, but one should be able to modify it if doing the job manually.
/init is executable file, statically linked. Any other hints please? i've been googling around and no clue so far :( Looks like nobody willing to customize the boot image, and prefer to wait the new release and hoping it will be supported...
This site has lots of good info about creating driver disks and might help you:
On 18/08/07 01:26 -0500, Johnny Hughes wrote:
beast wrote:
On 15/08/07 17:38 -0400, Phil Schaffner wrote:
On Wed, 2007-08-15 at 20:23 +0700, beast wrote:
On 14/08/07 07:26 +0200, maze@cela.pl wrote:
one of the files /linuxrc should list what modules get loaded on start.
Thanks for the hint. Where linuxrc located? i already searched initrd image and can not found it.
Looks like the script "init" in the top level does the job. I would expect mkinitrd to generate it automatically if you add a module, but one should be able to modify it if doing the job manually.
/init is executable file, statically linked. Any other hints please? i've been googling around and no clue so far :( Looks like nobody willing to customize the boot image, and prefer to wait the new release and hoping it will be supported...
This site has lots of good info about creating driver disks and might help you:
Thanks for the link, I'll check it. anyway i have been able to avoid RTL8169 chipset, so it may useful for another cases :)
--beast
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
beast spake the following on 8/13/2007 2:39 AM:
On 13/08/07 11:20 +0700, beast wrote:
The initrd file is just a gzipped ext2 filesystem image, so you need to uncompress it into a temporary file and then mount that file using loopback:
zcat /boot/initrd-`uname -r`.img >/tmp/fs mkdir /mnt/initrd mount -r -t ext2 -o loop /tmp/fs /mnt/initrd
Then you can look under /mnt/initrd to see the contents of the initial ramdisk.
Its not an image anymore : fs: ASCII cpio archive (SVR4 with no CRC)
However it can be extarct using cpio: gunzip < /boot/initrd-version.img |cpio -i --make-directories
Aparently its not as simply copy .ko file into modules.cgz. I have copied the ethernet driver, however it did not get loaded when loadning from pxeboot. Any other steps required?
--beast
I think you have to also modify modules.dep and maybe modules.info. Look at them and you will see what needs to be done to them. AFAIR modules.dep is the most important. I think the boot images are more like the addon driver disks are.
-
beast -
Johnny Hughes -
maze＠cela.pl -
Phil Schaffner -
Scott Silva -
tony＠softins.clara.co.uk