Re: Compiling new kernel, lilo problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Burger wrote: If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. Forgive me for being dense, but why would one want to compile as a module a driver which is needed for the system to even boot? Modules are great for peripherals and supporting functions, and I can see the benefit of low-level drivers as modules too if you're building a kernel that must be portable. For a dedicated custom build, though, why would one not build the crucial components into the kernel and spare oneself the trouble? - -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp - -- http://setiathome.ssl.berkeley.edu/pale_blue_dot.html -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQA/AwUBPEp5i79BpdPKTBGtEQJBIACffb+E72TCQ0Ctz0y/G9qwHNT8FHgAn1hw TULK1VDeHV8L9HlrCHKaMZ3N =oZAX -END PGP SIGNATURE- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
I'm currently using X-CD-Roast...but I'll look at some others at some point, too. On 19 Jan 2002, Brandon Robert Dorman wrote: I compiled most everything I'll need into the kernel. cdburner, visor, usb printer/scanner stuff, etc. but for next time, thanks for the info Bret, Mike and Werner. -Brandon p.s. this doesn't have to be a list question, but what do you guys recommend for a cd-burning software? Now that I have scsi support in there I'll actually be able to do it under linux... (that was the reason i recompiled.) On Sat, 2002-01-19 at 22:34, Mike Burger wrote: That'll kinda depend. If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. For example, if you were booting from a SCSI drive, and had compiled the driver for the SCSI card as a module, you'd need to create the initrd-whatever.img file (using mkinitrd), and include it in your lilo.conf, in order to properly boot from that SCSI card/drive combo. On 19 Jan 2002, Brandon Robert Dorman wrote: Before I got this e-mail i just removed the initrd line and rebooted. now i get: [Brandon@localhost Brandon]$ uname -a Linux localhost.localdomain 2.4.17 #1 Sat Jan 19 19:28:25 PST 2002 i686 unknown :-) So it works. Is there any danger in doing that? seems to work fine for me right now though.. -Brandon On Sat, 2002-01-19 at 21:00, Werner Puschitz wrote: On 19 Jan 2002, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. mkinitrd /boot/initrd-2.4.17.img 2.4.17 Make sure it says /boot/initrd-2.4.17.img and not /boot/initrd-2.4.17 in /etc/lilo.conf Werner ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
Simply put, I don't know. G On Sun, 20 Jan 2002, David Talkington wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Burger wrote: If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. Forgive me for being dense, but why would one want to compile as a module a driver which is needed for the system to even boot? Modules are great for peripherals and supporting functions, and I can see the benefit of low-level drivers as modules too if you're building a kernel that must be portable. For a dedicated custom build, though, why would one not build the crucial components into the kernel and spare oneself the trouble? - -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp - -- http://setiathome.ssl.berkeley.edu/pale_blue_dot.html -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQA/AwUBPEp5i79BpdPKTBGtEQJBIACffb+E72TCQ0Ctz0y/G9qwHNT8FHgAn1hw TULK1VDeHV8L9HlrCHKaMZ3N =oZAX -END PGP SIGNATURE- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
On Sun, 20 Jan 2002, Mike Burger wrote: Simply put, I don't know. G On Sun, 20 Jan 2002, David Talkington wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Burger wrote: If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. Forgive me for being dense, but why would one want to compile as a module a driver which is needed for the system to even boot? Modules are great for peripherals and supporting functions, and I can see the benefit of low-level drivers as modules too if you're building a kernel that must be portable. For a dedicated custom build, though, why would one not build the crucial components into the kernel and spare oneself the trouble? if you look closely, you'll notice that red hat 7.2 gives you the option of building ext3 filesystems at install time, but the supplied kernel does not contain ext3 functionality -- the ext3 module is in fact in the initrd.img file shipped by red hat. rday ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 rpjday wrote: Forgive me for being dense, but why would one want to compile as a module a driver which is needed for the system to even boot? Modules are great for peripherals and supporting functions, and I can see the benefit of low-level drivers as modules too if you're building a kernel that must be portable. For a dedicated custom build, though, why would one not build the crucial components into the kernel and spare oneself the trouble? if you look closely, you'll notice that red hat 7.2 gives you the option of building ext3 filesystems at install time, but the supplied kernel does not contain ext3 functionality -- the ext3 module is in fact in the initrd.img file shipped by red hat. Sure ... like I said, for a portable kernel, it makes sense. - -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp - -- http://setiathome.ssl.berkeley.edu/pale_blue_dot.html -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQA/AwUBPEqYE79BpdPKTBGtEQLFIQCgvyJXNXNcLAtjuSdeWTpo6XkTIDMAoNhi 1mhEaW/5TWtMQNTt52lVy3D2 =KlMI -END PGP SIGNATURE- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Compiling new kernel, lilo problem
Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. -Brandon [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
On 19 Jan 2002, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. mkinitrd /boot/initrd-2.4.17.img 2.4.17 Make sure it says /boot/initrd-2.4.17.img and not /boot/initrd-2.4.17 in /etc/lilo.conf Werner ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
Check out man mkinitrd. seems like I have always just given it the kernel version and the imgfile name needed. I guess the real question is do you really need an initrd? Unless you need something like scsi drivers that you compiled as modules that need to be availible before the file systems are availible you should not need one. If unsure, comment out the line in lilo that refers to it, run lilo again and reboot. Bret On Sat, at 22:50, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. -Brandon [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
Before I got this e-mail i just removed the initrd line and rebooted. now i get: [Brandon@localhost Brandon]$ uname -a Linux localhost.localdomain 2.4.17 #1 Sat Jan 19 19:28:25 PST 2002 i686 unknown :-) So it works. Is there any danger in doing that? seems to work fine for me right now though.. -Brandon On Sat, 2002-01-19 at 21:00, Werner Puschitz wrote: On 19 Jan 2002, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. mkinitrd /boot/initrd-2.4.17.img 2.4.17 Make sure it says /boot/initrd-2.4.17.img and not /boot/initrd-2.4.17 in /etc/lilo.conf Werner ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
That'll kinda depend. If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. For example, if you were booting from a SCSI drive, and had compiled the driver for the SCSI card as a module, you'd need to create the initrd-whatever.img file (using mkinitrd), and include it in your lilo.conf, in order to properly boot from that SCSI card/drive combo. On 19 Jan 2002, Brandon Robert Dorman wrote: Before I got this e-mail i just removed the initrd line and rebooted. now i get: [Brandon@localhost Brandon]$ uname -a Linux localhost.localdomain 2.4.17 #1 Sat Jan 19 19:28:25 PST 2002 i686 unknown :-) So it works. Is there any danger in doing that? seems to work fine for me right now though.. -Brandon On Sat, 2002-01-19 at 21:00, Werner Puschitz wrote: On 19 Jan 2002, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. mkinitrd /boot/initrd-2.4.17.img 2.4.17 Make sure it says /boot/initrd-2.4.17.img and not /boot/initrd-2.4.17 in /etc/lilo.conf Werner ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling new kernel, lilo problem
I compiled most everything I'll need into the kernel. cdburner, visor, usb printer/scanner stuff, etc. but for next time, thanks for the info Bret, Mike and Werner. -Brandon p.s. this doesn't have to be a list question, but what do you guys recommend for a cd-burning software? Now that I have scsi support in there I'll actually be able to do it under linux... (that was the reason i recompiled.) On Sat, 2002-01-19 at 22:34, Mike Burger wrote: That'll kinda depend. If you compiled the kernel with the device drivers as modules, and not directly into the kernel, and any of those drivers/modules are needed for the initial startup, it could cause problems. If you compiled all those drivers directly into the kernel, instead of as modules, then you don't need the initrd-whatever.img. For example, if you were booting from a SCSI drive, and had compiled the driver for the SCSI card as a module, you'd need to create the initrd-whatever.img file (using mkinitrd), and include it in your lilo.conf, in order to properly boot from that SCSI card/drive combo. On 19 Jan 2002, Brandon Robert Dorman wrote: Before I got this e-mail i just removed the initrd line and rebooted. now i get: [Brandon@localhost Brandon]$ uname -a Linux localhost.localdomain 2.4.17 #1 Sat Jan 19 19:28:25 PST 2002 i686 unknown :-) So it works. Is there any danger in doing that? seems to work fine for me right now though.. -Brandon On Sat, 2002-01-19 at 21:00, Werner Puschitz wrote: On 19 Jan 2002, Brandon Robert Dorman wrote: Hey guys, Was recompiling my kernel today to 2.4.17 from 2.4-7-10. Upon changing my lilo.conf, ran /sbin/lilo and got this: Added linux fatal: open /boot/initrd-2.4.17: no such file or directory. Sure enough, a ls of /boot shows: ls /boot boot.b kernel.hmodule-info-2.4.7-10 vmlinuz chain.b kernel.h-2.4.7 os2_d.b vmlinuz-2.4.17 grub message System.map vmlinuz-2.4.7-10 initrd-2.4.7-10.img module-info System.map-2.4.7-10 No initrd. Where can i copy it from? This is my first time compiling a kernel after about 2.5 years working off and on with linux, i followed the howtos but am stumped here. Thanks. mkinitrd /boot/initrd-2.4.17.img 2.4.17 Make sure it says /boot/initrd-2.4.17.img and not /boot/initrd-2.4.17 in /etc/lilo.conf Werner ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
