- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Linux initrd
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2010 10:13 PM
04-11-2010 10:13 PM
Linux initrd
We have been using SLES 10 Linux Customised OS so far. Recently our system could not detect one of the fibre cards.
Now we have downloaded the required drivers that should make the card recognised by the system.
What we need to do so that when we install the OS from scratch the system automatically loads the drivers in the sense post installation the card is ready to be used?
I have heard about initird. Does it help here or kernel compilation ??
Please suggest.
Thanks,
admin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2010 10:54 PM
04-11-2010 10:54 PM
Re: Linux initrd
though I'm really not into SLES at all (we use RHEL),
I guess that in this respect an answer wouldn't be that distro specific.
To my knowledge, in your initial ram disk you only require those drivers that are essential to boot the kernel and mount your rootfs.
So I would guess that if you don't intend to boot your kernel from one of your SAN disks or need to mount one such device in the initial boot stage that you then don't need to modify your initrd image file.
If you are curious to see what drivers/modules are contained in your initrd then you could unzip the image and dump the contained cpio archive to some temporary filesystem (at least the following should work under RHEL, and their relatively dated kernels)
e.g.
# mkdir /tmp/initrd && cd /tmp/initrd
# gzip -dc /boot/initrd-$(uname -r).img | cpio -id
then you could look for the modules contained under /tmp/initrd/lib or have a look at the init script /tmp/initrd/init to find out which modules get loaded
e.g.
# egrep insmod\|modprobe /tmp/initrd/init
If you really think that you need to create a new or customize your initrd you could theoretically just modify the extracted cpio archive by adding some required module and editing init and finally cpio-ing it out (i.e. -o...), gziping it and copying it back into /boot.
However, the recommended way would be to use some tool (script) like mkinitrd (under RHEL, which also has a manpage).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2010 10:58 PM
04-11-2010 10:58 PM
Re: Linux initrd
We dont need to recognise this Fibre card in the initial phase of booting.
So initird option is not mandatory.
But then the question is , if not through initrd then whats the other option?
Please clarify that.
Thanks,
admin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2010 11:30 PM
04-11-2010 11:30 PM
Re: Linux initrd
If I remember corrently you can also use yast, going to system -> sysconf editor -> System -> kernel -> MODULES_LOADED_ON_BOOT -> add your module (driver) name there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2010 11:33 PM
04-11-2010 11:33 PM
Re: Linux initrd
So that it is avialable after every installations.
Thanx,
admin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2010 12:15 AM
04-12-2010 12:15 AM
Re: Linux initrd
If your post-install customization sets the correct value to the MODULES_LOADED_ON_BOOT variable in this file, the script will automatically load the module(s) at system boot time.
If the module requires any options, your post-install customization should also drop a file with the appropriate "options
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2010 11:25 PM
09-01-2010 11:25 PM