Compiling a kernel module results in insmod version mismatch...
Hi While I can compile and create a kernel loadable module as shown below, I get a kernel version mismatch in the final result as indicated by the insmod command. Can someone look at the steps below and tell me where I can reconcile this difference. Thank You... # # Phase 1: Preparing the kernel source files # from my installation CD... # root# rpm -iv kernel-source-2.4.18-14.i386.rpm root# rpm -iv glibc-kernheaders-2.4-7.20.i386.rpm root# cd /usr/src/linux-2.4 root# make menuconfig (Comparing the Qlogic instructions on what to do here to what came up, it turns out that I did not have to modify anything here). root# make dep # # # Phase 2: Preparing the Qlogic source structure # (i.e. this is the kernel module Im creating to # drive a Qlogic qla2200 HBA). ## root# mkdir -p /qla2x00 root# cd /qla2x00 (I then copied the source tarball (qla2x00-v6.04.00-dist.tgz) to this directory) root# tar -xvzf qla2x00-v6.04.00-dist.tgz root# cd qlogic (the above tar command created this new directory to cd into). root# ./drvrsetup (i.e. /qla2200/qlogic/drvrsetup -- all this did was untar more source files into the current directory, /qla2x00/qlogic) root# pwd /qla2x00/qlogic root# make all SMP=1 OSVER=linux-2.4 cc -D__KERNEL__ -DMODULE -Wall -O -g -DUDEBUG -DLINUX -Dlinux -DINTAPI -DEXPORT_SYMTAB -DMODVERSIONS -include /usr/src/linux-2.4/include/linux/modversions.h -I/usr/src/linux-2.4/include -I/usr/src/linux-2.4/include/../drivers/scsi -falign-functions=2 -falign-jumps=2 -falign-loops=2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -pipe -DCONFIG_X86_LOCAL_APIC -fno-strict-aliasing -fno-common -mpreferred-stack-boundary=2 -march=i686 -D__SMP__ -DCONFIG_SMP -c qla2200.c -o qla2200.o cc -D__KERNEL__ -DMODULE -Wall -O -g -DUDEBUG -DLINUX -Dlinux -DINTAPI -DEXPORT_SYMTAB -DMODVERSIONS -include /usr/src/linux-2.4/include/linux/modversions.h -I/usr/src/linux-2.4/include -I/usr/src/linux-2.4/include/../drivers/scsi -falign-functions=2 -falign-jumps=2 -falign-loops=2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -pipe -DCONFIG_X86_LOCAL_APIC -fno-strict-aliasing -fno-common -mpreferred-stack-boundary=2 -march=i686 -D__SMP__ -DCONFIG_SMP -c qla2300.c -o qla2300.o roo# ls -la *.o -rw-r--r--1 root root 622316 Jul 29 17:08 qla2200.o -rw-r--r--1 root root 640068 Jul 29 17:08 qla2300.o == Finally here is the problem (I could use the -f option to insmod, but am not sure what consequence it will have later): == root# insmod /qla2x00/qlogic/qla2200.o /qla2x00/qlogic/qla2200.o: kernel-module version mismatch /qla2x00/qlogic/qla2200.o was compiled for kernel version 2.4.18-14custom while this kernel is version 2.4.18-14smp. How can I get these versions to match up??? In the end, I guess I need the qla2200.o version to be version 2.4.18-14smp. Thanks In Advance, Milton -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: problems compiling a kernel: from a newbie
Two days ago I had the same problem with RH 7.3. I'm not shure weather I can help you, but my problem were the missing kernel-headers. Notice the following deps: gcc needs glibc-devel, which needs kernel-headers 2.2 But: a packet kernel-headers doesn't exist. Therefore install glibc-kernheaders-2.4-xx.rpm Then make dep clean bzImage modules modules_install should work. If not, I don't know... Good luck! On Wed, 2003-02-12 at 04:55, Darren R. Gitelman wrote: Dear list: I'm sure I'm doing something wrong, but don't know what it is or how to solve it. I've gotten to the make dep part of making a kernel kernel and several dependencies seem unfulfilled. In particular it cannot find stddef.h (which seems to be sitting in /usr/include/linux) and a file called stdarg.h which seems to be buried away in /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include) and it complains that it cannot find the file limits.h which is included in limits.h This all started when I upgraded to redhat 8.0 (or tried to). The installer said we recommend you change to an ext3 filesystem, but it seemed to forget to include ext3 support in the kernel with the install. So.. none of the filesystems want to mount. I have booted using Tomsrtbt, mounted the filesystems appropriately, chroot, and I'm trying to build kernel 2.4.20 to get around this problem. thanks, Darren - Darren R. Gitelman, M.D. Cognitive Neurology and Alzheimer¹s Disease Center E-mail: [EMAIL PROTECTED] WWW: http://www.brain.northwestern.edu Voice: (312) 908-9023 Fax: (312) 908-8789 Northwestern Univ., 320 E. Superior St., Searle 11-470, Chicago, IL 60611 - -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
problems compiling a kernel: from a newbie
Dear list: I'm sure I'm doing something wrong, but don't know what it is or how to solve it. I've gotten to the make dep part of making a kernel kernel and several dependencies seem unfulfilled. In particular it cannot find stddef.h (which seems to be sitting in /usr/include/linux) and a file called stdarg.h which seems to be buried away in /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include) and it complains that it cannot find the file limits.h which is included in limits.h This all started when I upgraded to redhat 8.0 (or tried to). The installer said we recommend you change to an ext3 filesystem, but it seemed to forget to include ext3 support in the kernel with the install. So.. none of the filesystems want to mount. I have booted using Tomsrtbt, mounted the filesystems appropriately, chroot, and I'm trying to build kernel 2.4.20 to get around this problem. thanks, Darren - Darren R. Gitelman, M.D. Cognitive Neurology and Alzheimer¹s Disease Center E-mail: [EMAIL PROTECTED] WWW: http://www.brain.northwestern.edu Voice: (312) 908-9023 Fax: (312) 908-8789 Northwestern Univ., 320 E. Superior St., Searle 11-470, Chicago, IL 60611 - -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
I've written a Mini-HOWTO on compiling the kernel: http://www.eclectic-cheval.net/linux/kr-mhowto.txt I've posted it here for two reasons: 1) In case it will help, and 2) To get suggestions from those who know more than I do. It's licensed under the FDL, so hack away. Daniel. -- Bash forehead on any key to continue... t-shirts still available for $15 Free shipping within the continental U.S. Call (316) 204-1700 to order or email me for details Success doesn't compile itself and arrive as a binary pre-packaged for your OS on a free CD that's been mailed to you by God. Unless you do the work, you don't get it. 6,000+ ebooks free at http://www.gutenberg.net -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
compiling the kernel
Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. I did a custom install, and only installed networking and DNS BIND. I have a feeling I have to install some developer tools. I tried to install the MAKEDEV.RPM, but it says it's already installed, along with the other make RPM. I am a newbie, so any help is appreciated. Craig Cameron Network Specialist, IT Services Edmonton Public Library 7 Sir Winston Churchill Square Edmonton, AB T5J 2V4 Ph: 780-496-8491 Fax: 780-496-1885 mailto:[EMAIL PROTECTED] -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
On Tue, 7 Jan 2003 12:01:34 -0700 Craig Cameron [EMAIL PROTECTED] wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. I did a custom install, and only installed networking and DNS BIND. I have a feeling I have to install some developer tools. I tried to install the MAKEDEV.RPM, but it says it's already installed, along with the other make RPM. I am a newbie, so any help is appreciated. Normally it's 'make xconfig or make menuconfig for kernels. Sice you installed minimal, I'd think 'make menuconfig' would suffice. If you have the Redhat kernel-source rpm installed, and if you don't want to start from scratch, there's one already started in /usr/src/linux-version/configs for whatever architecture you're using. It can help a lot for getting started. Basically, you copy the appropriate one to the top level of the source tree, rename it as .config, 'make oldconfig' then run menuconfig. Such as (this is a Rawhide kernel that you likely won't have): cd /usr/src/linux-2.4.20-0.pp.20 cp configs/kernel-2.4.20-athlon.config ./.config make oldconfig make menuconfig Then you set whatever options you want, get rid of things, etc. Beats having to do it all from scratch (usually). Things are different if you are using the tarball however. -- Me? A skeptic? Can you prove it? -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: compiling the kernel
I have nothing under /src/linux No files or directory's. I really think I need to add an RPM. Thanks. -Original Message- From: ABrady [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:25 PM To: [EMAIL PROTECTED] Subject: Re: compiling the kernel On Tue, 7 Jan 2003 12:01:34 -0700 Craig Cameron [EMAIL PROTECTED] wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. I did a custom install, and only installed networking and DNS BIND. I have a feeling I have to install some developer tools. I tried to install the MAKEDEV.RPM, but it says it's already installed, along with the other make RPM. I am a newbie, so any help is appreciated. Normally it's 'make xconfig or make menuconfig for kernels. Sice you installed minimal, I'd think 'make menuconfig' would suffice. If you have the Redhat kernel-source rpm installed, and if you don't want to start from scratch, there's one already started in /usr/src/linux-version/configs for whatever architecture you're using. It can help a lot for getting started. Basically, you copy the appropriate one to the top level of the source tree, rename it as .config, 'make oldconfig' then run menuconfig. Such as (this is a Rawhide kernel that you likely won't have): cd /usr/src/linux-2.4.20-0.pp.20 cp configs/kernel-2.4.20-athlon.config ./.config make oldconfig make menuconfig Then you set whatever options you want, get rid of things, etc. Beats having to do it all from scratch (usually). Things are different if you are using the tarball however. -- Me? A skeptic? Can you prove it? -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 7 Jan 2003 12:01:34 -0700, Craig Cameron wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. Where the heck did you run that command? ;) You must install the kernel-source i386.rpm and then go into /usr/src/linux-2.4 for kernel configuration and compilation. It's there where the command would work. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Gy/T0iMVcrivHFQRAh9FAJ9WhK2mg97QIJGDm5HbdGqNMjDkSQCcDw1X OJEQ01lsFVXi6n+WRysW4Y0= =0XVO -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: compiling the kernel
Thanks. After installing about 6 other dependency modules, I finally got the kernel source installed. Now I can run make. Thanks again. -Original Message- From: Michael Schwendt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:52 PM To: [EMAIL PROTECTED] Subject: Re: compiling the kernel -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 7 Jan 2003 12:01:34 -0700, Craig Cameron wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. Where the heck did you run that command? ;) You must install the kernel-source i386.rpm and then go into /usr/src/linux-2.4 for kernel configuration and compilation. It's there where the command would work. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Gy/T0iMVcrivHFQRAh9FAJ9WhK2mg97QIJGDm5HbdGqNMjDkSQCcDw1X OJEQ01lsFVXi6n+WRysW4Y0= =0XVO -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: compiling the kernel
I did try make menuconfig, but had the same result. What is the RPM for Kernal hacking? -Original Message- From: Daniel Callahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:19 PM To: [EMAIL PROTECTED] Subject: Re: compiling the kernel On Tuesday 07 January 2003 13:01, Craig Cameron wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. I did a custom install, and only installed networking and DNS BIND. I have a feeling I have to install some developer tools. I tried to install the MAKEDEV.RPM, but it says it's already installed, along with the other make RPM. Make sure you're root (no offense -- I mention this because this is still on my Top 10 Dumb Error List), and try: make menuconfig (in a terminal) make xconfig (only in Xwindows) You will need the developer tools, but RH will add those if you install the Kernel Hacking option in setup. Hope that helps! -- Daniel Callahan CIO, Castle Computer Consultants, Inc. (316) 304-7212 Success doesn't compile itself and arrive as a binary pre-packaged for your OS on a free CD that's been mailed to you by God. Unless you do the work, you don't get it. 6,000+ ebooks free at http://www.gutenberg.net -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
On Tuesday 07 January 2003 13:01, Craig Cameron wrote: Can somebody give me a hand with compiling my kernel. I run make config, and I get an error which essentially says no rule for config. I did a custom install, and only installed networking and DNS BIND. I have a feeling I have to install some developer tools. I tried to install the MAKEDEV.RPM, but it says it's already installed, along with the other make RPM. Make sure you're root (no offense -- I mention this because this is still on my Top 10 Dumb Error List), and try: make menuconfig (in a terminal) make xconfig (only in Xwindows) You will need the developer tools, but RH will add those if you install the Kernel Hacking option in setup. Hope that helps! -- Daniel Callahan CIO, Castle Computer Consultants, Inc. (316) 304-7212 Success doesn't compile itself and arrive as a binary pre-packaged for your OS on a free CD that's been mailed to you by God. Unless you do the work, you don't get it. 6,000+ ebooks free at http://www.gutenberg.net -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: Problem Compiling Linux Kernel 2.4.20
--- Florin Andrei [EMAIL PROTECTED] wrote: Corrupted kernel tarball then? Download/unpack/compile again? Did you also verify the source using the PGP key? How about making the required links to the linux-2.4.20 dir? ln -s /usr/src/linux-2.4.20 linux ln -s /usr/src/linux-2.4.20 linux-2.4 = Kevin C. McConnell --RHCE-- Red Hat Certified Engineer __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
RE: Problem Compiling Linux Kernel 2.4.20
On Mon, 2002-12-16 at 14:45, Joseph D. Wagner wrote: [root@localhost linux-2.4.20]# make xconfig cat header.tk ./kconfig.tk ./tkparse ../arch/i386/config.in kconfig.tk -: 6: unknown command make[1]: *** [kconfig.tk] Error 1 Did you installed the Tcl and Tk stuff? -- Florin Andrei When it comes to discussing Linux, some people become temporarily insane. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
RE: Problem Compiling Linux Kernel 2.4.20
It (make xconfig) works fine on the 2.4.18-3 kernel that comes pre-installed with Redhat 7.3. It just doesn't work with the kernel I downloaded from http://www.kernel.org (version 2.4.20). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Florin Andrei Sent: Tuesday, December 17, 2002 11:35 AM To: [EMAIL PROTECTED] Subject: RE: Problem Compiling Linux Kernel 2.4.20 On Mon, 2002-12-16 at 14:45, Joseph D. Wagner wrote: [root@localhost linux-2.4.20]# make xconfig cat header.tk ./kconfig.tk ./tkparse ../arch/i386/config.in kconfig.tk -: 6: unknown command make[1]: *** [kconfig.tk] Error 1 Did you installed the Tcl and Tk stuff? -- Florin Andrei When it comes to discussing Linux, some people become temporarily insane. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re: Problem Compiling Linux Kernel 2.4.20
Hi, Joseph (1) I can do make xconfig 2.4.20 on RedHat Linux 8.0(LANG=C CC=gcc296). (2) I did some experiment. slime% cd /usr/src/v2.4/linux-2.4.20 slime% ./scripts/tkparse ^M... CNTL-V + CNTL-M + RET -: 1: unknown command slime% Are there extra \r charactors in your config.in file ? -- Yasuo Yamasaki ./tkparse ../arch/i386/config.in kconfig.tk -: 6: unknown command ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re: Problem Compiling Linux Kernel 2.4.20
On Mon, 16 Dec 2002, Joseph D. Wagner wrote: I've downloaded kernel version 2.4.20 from http://www.kernel.org and copied it to the /usr/src/linux-2.4.20 directory, but when I do make xconfig (or any other make for that matter, it exits with error code 2. I figure there is some Redhat-specific tweaking I must do to compile a There's not. generic kernel from http://www.kernel.org on a Redhat system, but I have no idea what that specific tweaking is. Could someone help me, please? We can't read minds. Show us what happened. BTW, I'm using Redhat Linux 7.3. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
RE: Problem Compiling Linux Kernel 2.4.20
Did you do a make mrproper first? Yep. Here's the output from make xconfig [root@localhost linux-2.4.20]# make xconfig rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts kconfig.tk make[1]: Entering directory `/usr/src/linux-2.4.20/scripts' cat header.tk ./kconfig.tk ./tkparse ../arch/i386/config.in kconfig.tk -: 6: unknown command make[1]: *** [kconfig.tk] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.20/scripts' make: *** [xconfig] Error 2 ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
RE: Problem Compiling Linux Kernel 2.4.20
On Mon, 2002-12-16 at 18:24, Joseph D. Wagner wrote: Do you suggest I re-extract the files from the tar archive and start over? By the error message you sent, it looks to me that you do not have software installed that is needed to run xconfig. Try make menuconfig or make config If menuconfig does not work (due to missing software, too), I suggest installing the required packages so you can use xconfig or menuconfig to configure you kernel. Sorry but I don't have a suggestion right now for what RPM to install for xconfig to work. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re: Compiling 2.4.18 kernel - missing module-info file?
Well, I took the path of least resistance and compiled a static kernel. Seems to work ok :) However, I'm still wondering why I'm having trouble building a modular kernel. mkinitrd cannot find the ncr583cxx module, but it doe exist in the appropriate folder. Any thoughts? At 09:05 PM 12/10/2002 +0100, you wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 10 Dec 2002 11:06:51 -0800, Jeff Davis wrote: No. The module-info file is only for your Linux distributor's installation and hardware configuration utilities which maintain kernel driver entries in /etc/modules.conf. The file is not created when building a kernel from source. Huh. So, if I want or need to create a ramdisk image for the new kernel, how do I get mkinitrd to quite whining about not being able to find my ncr53c8xx module. The file (ncr53c8xx.o) is in the /lib/modules/scsi directory. Or should *I* quite whining and build a static kernel? It should be in /lib/modules/$KERNEL_VERSION/kernel/drivers/scsi and whether or not it is found might depend on how you call mkinitrd. The module-info file is not used by mkinitrd. /etc/modules.conf is. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) iD8DBQE99kkd0iMVcrivHFQRAqmAAJ4p3M+PmojHcU9jSZ9TuCwM/pd5RACbB64a NwUhMZqd2GhgihTDaayWE3w= =kUJO -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 09 Dec 2002 08:50:32 -0800, Jeff Davis wrote: The kernel compiles without errors, but for some reason there is no module-info-2.4.18 file created, or at least I have been unable to find it. grep-ing the source tree shows no module-info strings anywhere in the code, Makefiles, or Docs. Likewise find / -iname module-info* only shows those files used by my current kernel, nothing for the 2.4.18 version. Usenet and web search have produced queries from other people with the same problem, but no solutions, which leads me to believe that the solution was so simple that they were embarrassed to post a follow-up. Unfortunately, not simple enough for me to figure out ;) So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? No. The module-info file is only for your Linux distributor's installation and hardware configuration utilities which maintain kernel driver entries in /etc/modules.conf. The file is not created when building a kernel from source. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) iD8DBQE99an/0iMVcrivHFQRApZnAJ95G49m8P3aZyVgTFErL/qUve2r0wCdHfyH Y63axYK4TVgsRa/AqpGQhyE= =517z -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
At 09:46 AM 12/10/2002 +0100, you wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 09 Dec 2002 08:50:32 -0800, Jeff Davis wrote: *snip* So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? No. The module-info file is only for your Linux distributor's installation and hardware configuration utilities which maintain kernel driver entries in /etc/modules.conf. The file is not created when building a kernel from source. Huh. So, if I want or need to create a ramdisk image for the new kernel, how do I get mkinitrd to quite whining about not being able to find my ncr53c8xx module. The file (ncr53c8xx.o) is in the /lib/modules/scsi directory. Or should *I* quite whining and build a static kernel? Thanks -Jeff Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Davis wrote: | Huh. So, if I want or need to create a ramdisk image for the new | kernel, how do I get mkinitrd to quite whining about not being able to | find my ncr53c8xx module. The file (ncr53c8xx.o) is in the | /lib/modules/scsi directory. Or should *I* quite whining and build a | static kernel? The real question is do you need a modular kernel? Do you plan on ever switching the hardware out on this machine or will the configuration remain static for the duration of this kernel's use? If it's going to remain static, there's nothing wrong w/ a static kernel - - or at a minimum, making the SCSI module staticly compiled (leaving the rest modular). Building a modular kernel that works right is a challenge, especially on non-standard hardware. - -Rick - -- Rick Johnson, RHCE - [EMAIL PROTECTED] (from home) Linux/WAN Administrator - Medata, Inc. PGP Key: https://mail.medata.com/pgp/rjohnson.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE99j0HIgQdhlSHZgMRAid6AKD+OaBNtALIH4V16jypDyYTM1YjFQCffUGt cRLzq8R4Vk47X6S3BUiafl4= =1stT -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 10 Dec 2002 11:06:51 -0800, Jeff Davis wrote: No. The module-info file is only for your Linux distributor's installation and hardware configuration utilities which maintain kernel driver entries in /etc/modules.conf. The file is not created when building a kernel from source. Huh. So, if I want or need to create a ramdisk image for the new kernel, how do I get mkinitrd to quite whining about not being able to find my ncr53c8xx module. The file (ncr53c8xx.o) is in the /lib/modules/scsi directory. Or should *I* quite whining and build a static kernel? It should be in /lib/modules/$KERNEL_VERSION/kernel/drivers/scsi and whether or not it is found might depend on how you call mkinitrd. The module-info file is not used by mkinitrd. /etc/modules.conf is. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) iD8DBQE99kkd0iMVcrivHFQRAqmAAJ4p3M+PmojHcU9jSZ9TuCwM/pd5RACbB64a NwUhMZqd2GhgihTDaayWE3w= =kUJO -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Compiling 2.4.18 kernel - missing module-info file?
Ok, this is making me nuts. I've compiled from source before, but it's been awhile (2.2 kernel, I think). I'm hoping I've just missed something basic, but I haven't been able to find it yet. I unpack the source (2.4.18), then execute the following: make xconfig (modular kernel) make dep make clean make bzImage make modules make modules_install My box (proliant 1600, currently running 2.2.19) has the smartarray SCSI controller, and so needs (as I understand it) the initrd file to be able to boot. Installing from binary RPM is not really an option given all the likely failed dependencies... The kernel compiles without errors, but for some reason there is no module-info-2.4.18 file created, or at least I have been unable to find it. grep-ing the source tree shows no module-info strings anywhere in the code, Makefiles, or Docs. Likewise find / -iname module-info* only shows those files used by my current kernel, nothing for the 2.4.18 version. Usenet and web search have produced queries from other people with the same problem, but no solutions, which leads me to believe that the solution was so simple that they were embarrassed to post a follow-up. Unfortunately, not simple enough for me to figure out ;) So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? Thanks, -Jeff Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
Why are you doing a make clean after the make dep? Generally you do the following to build your kernel. (As defined in README) make mrproper make xconfig make dep make bzImage make modules make modules_install Doing the above will not give you a module-info file. I never found an isntance where I needed one. Also, are there any special reasons why are you needing an initrd? -David Jeff Davis wrote: Ok, this is making me nuts. I've compiled from source before, but it's been awhile (2.2 kernel, I think). I'm hoping I've just missed something basic, but I haven't been able to find it yet. I unpack the source (2.4.18), then execute the following: make xconfig (modular kernel) make dep make clean make bzImage make modules make modules_install My box (proliant 1600, currently running 2.2.19) has the smartarray SCSI controller, and so needs (as I understand it) the initrd file to be able to boot. Installing from binary RPM is not really an option given all the likely failed dependencies... The kernel compiles without errors, but for some reason there is no module-info-2.4.18 file created, or at least I have been unable to find it. grep-ing the source tree shows no module-info strings anywhere in the code, Makefiles, or Docs. Likewise find / -iname module-info* only shows those files used by my current kernel, nothing for the 2.4.18 version. Usenet and web search have produced queries from other people with the same problem, but no solutions, which leads me to believe that the solution was so simple that they were embarrassed to post a follow-up. Unfortunately, not simple enough for me to figure out ;) So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? Thanks, -Jeff Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
At 05:01 PM 12/9/2002 -0600, you wrote: Why are you doing a make clean after the make dep? It's been a while since I've customized a kernel... According to the howto they recommended doing a make clean after make dep. Perhaps this was an old howto? Generally you do the following to build your kernel. (As defined in README) make mrproper make xconfig make dep make bzImage make modules make modules_install Doing the above will not give you a module-info file. I never found an isntance where I needed one. Also, are there any special reasons why are you needing an initrd? SCSI driver needs one to boot, as I understand it. I could be misinformed... -David Jeff Davis wrote: Ok, this is making me nuts. I've compiled from source before, but it's been awhile (2.2 kernel, I think). I'm hoping I've just missed something basic, but I haven't been able to find it yet. I unpack the source (2.4.18), then execute the following: make xconfig (modular kernel) make dep make clean make bzImage make modules make modules_install My box (proliant 1600, currently running 2.2.19) has the smartarray SCSI controller, and so needs (as I understand it) the initrd file to be able to boot. Installing from binary RPM is not really an option given all the likely failed dependencies... The kernel compiles without errors, but for some reason there is no module-info-2.4.18 file created, or at least I have been unable to find it. grep-ing the source tree shows no module-info strings anywhere in the code, Makefiles, or Docs. Likewise find / -iname module-info* only shows those files used by my current kernel, nothing for the 2.4.18 version. Usenet and web search have produced queries from other people with the same problem, but no solutions, which leads me to believe that the solution was so simple that they were embarrassed to post a follow-up. Unfortunately, not simple enough for me to figure out ;) So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? Thanks, -Jeff Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling 2.4.18 kernel - missing module-info file?
Jeff Davis wrote: At 05:01 PM 12/9/2002 -0600, you wrote: Why are you doing a make clean after the make dep? It's been a while since I've customized a kernel... According to the howto they recommended doing a make clean after make dep. Perhaps this was an old howto? Perhaps. The README in the src root dir is where the instructions that I use are. Generally you do the following to build your kernel. (As defined in README) make mrproper make xconfig make dep make bzImage make modules make modules_install Doing the above will not give you a module-info file. I never found an isntance where I needed one. Also, are there any special reasons why are you needing an initrd? SCSI driver needs one to boot, as I understand it. I could be misinformed... Hmm. What SCSI driver? I included a lot of SCSI stuff in my kernel even though I don't use 80% of it, and I never need one. Perhaps you could experiment with it once you get everything running and let us know. I'd be very interested to hear more on this. -David -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Compiling 2.4.18 kernel - missing module-info file?
Ok, this is making me nuts. I've compiled from source before, but it's been awhile (2.2 kernel, I think). I'm hoping I've just missed something basic, but I haven't been able to find it yet. I unpack the source (2.4.18), then execute the following: make xconfig (modular kernel) make dep make clean make bzImage make modules make modules_install My box (proliant 1600, currently running 2.2.19) has the smartarray SCSI controller, and so needs (as I understand it) the initrd file to be able to boot. Installing from binary RPM is not really an option given all the likely failed dependencies... The kernel compiles without errors, but for some reason there is no module-info-2.4.18 file created, or at least I have been unable to find it. grep-ing the source tree shows no module-info strings anywhere in the code, Makefiles, or Docs. Likewise find / -iname module-info* only shows those files used by my current kernel, nothing for the 2.4.18 version. Usenet and web search have produced queries from other people with the same problem, but no solutions, which leads me to believe that the solution was so simple that they were embarrassed to post a follow-up. Unfortunately, not simple enough for me to figure out ;) So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? Thanks, -Jeff Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Compiling 2.4.18 kernel - missing module-info file?
Ok, this is making me nuts. I've compiled from source before, but it's been awhile (2.2 kernel, I think). I'm hoping I've just missed something basic, but I haven't been able to find it yet. I unpack the source (2.4.18), then execute the following: make xconfig (modular kernel) make dep make clean make bzImage make modules make modules_install My box (proliant 1600, currently running 2.2.19) has the smartarray SCSI controller, and so needs (as I understand it) the initrd file to be able to boot. Installing from binary RPM is not really an option given all the likely failed dependencies... The kernel compiles without errors, but for some reason there is no module-info-2.4.18 file created, or at least I have been unable to find it. grep-ing the source tree shows no module-info strings anywhere in the code, Makefiles, or Docs. Likewise find / -iname module-info* only shows those files used by my current kernel, nothing for the 2.4.18 version. Usenet and web search have produced queries from other people with the same problem, but no solutions, which leads me to believe that the solution was so simple that they were embarrassed to post a follow-up. Unfortunately, not simple enough for me to figure out ;) So, am I missing something obvious? Do I need to install an additional package to make this work? modutils perhaps? Thanks, -Jeff Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Cant connect to HTTPS after re-compiling the kernel
Hello, Do you know how come i cant connect to HTTPS sites after re-compiling my kernel to 2.4.19 and i un-installed ipchains... rpm -q ipchains Casue im going to use iptables?But i have not put in any rules. It was working before i re-compiled the kernel? Any ideas what could cause this? Im usuing Mozilla 1.1 Browser i also tryed it with netscape and still cant connect to websites HTTPS... RedHat 7.3 2.4.19 Kernel Kernel 2.4.18 is the kernel that it works with? Any ideeas __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2 -- redhat-list mailing list unsubscribe mailto:redhat-list-request;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Cant connect to HTTPS after re-compiling the kernel
Hey, Do you know how come i cant connect to HTTPS sites after re-compiling my kernel to 2.4.19 and i un-installed ipchains...casue im going to use iptables? It was working before i re-compiled the kernel? Any ideas what could cause this? Im usuing Mozilla 1.1 Browser i also tryed it with netscape and still cant connect to websites... RedHat 7.3 2.4.19 Kernel __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2 -- redhat-list mailing list unsubscribe mailto:redhat-list-request;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: [Fwd: RE: [rhn-users] Problems compiling custom kernel]
On 11 Oct 2002 12:30:23 -0700, William L. Thomson Jr. wrote: I am not sure if this topic is covered under this list or not. The thread seems dead on the rhn-users list. Possible the wrong list as well. psyche-list would be the right list: [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/psyche-list -- msg06427/pgp0.pgp Description: PGP signature
[Fwd: RE: [rhn-users] Problems compiling custom kernel]
I am not sure if this topic is covered under this list or not. The thread seems dead on the rhn-users list. Possible the wrong list as well. In short I am unable to compile modules for a custom kernel using the 2.4.18-14 source that comes with RH 8.0. I can compile other kernels, and kernel modules, just not the ones for a custom 2.4.18-14 kernel. I am pretty sure there is a problem some where. Although I do not know if that problem lies in the kernel-sources for 2.4.18-14 or in my machine? It's a fresh install and I have tried to uninstall and reinstall the kernel-sources.rpm. I am looking for a reason or simple a solution. Is there a problem with the sources, or is it me? Has anyone out there been able to compile a custom kernel, and kernel modules using the 2.4.18-14 source from RH? -Forwarded Message- From: William L. Thomson Jr. [EMAIL PROTECTED] To: rhn-users [EMAIL PROTECTED] Subject: RE: [rhn-users] Problems compiling custom kernel Date: 10 Oct 2002 15:13:03 -0700 I have downloaded a vanilla kernel from kernel.org. Both 2.4.18 and 2.4.19. I was able to compile both, and make modules for both. I tried once again to compile modules for the 2.4.18-14 kernel that ships with RedHat 8.0 and I still am unable to compile modules. Can someone from RedHat confirm this? Is there a problem with the sources or what? Why can't I compile modules for the 2.4.18-14 kernel when I attempt to compile a custom one? Do I have to just run a custom kernel from kernel.org and forget about the 2.4.18-14 from RedHat until the sources are fixed, or a new kernel release is available from RedHat? On Mon, 2002-10-07 at 19:54, William L. Thomson Jr. wrote: On Mon, 2002-10-07 at 18:52, Victor Szeto wrote: Yes, I have the same problem when I tried to recompile the RH 8.0 kernel. I can make bzImage, but I can't make modules. Good at least I am not alone. Now we need some others to confirm as well, and maybe someone from RedHat or with the necessary experience can tell us what to do in order to get the kernel modules to compile. I wonder if its due to using the new compiler or what, I have not tried to compile a default kernel from kernel.org. If I have time I will. That at least will let us know if its and env or a code problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of William L. Thomson Jr. Sent: Tuesday, October 08, 2002 6:59 AM To: rhn-users Subject: [rhn-users] Problems compiling custom kernel Recently I upgraded my laptop from 7.3 to 8.0. I have had allot of growing pains, some that are just pains. One of which is I can't seem to compile a custom kernel. I can make dep and make bzImage But I can't make modules No matter what modules I have selected it fails. It will not compile modules for me? I am having some other problems with shared libraries built using ld, so I am not sure if something is messed up on my machine or what. I have rarely had problems compiling custom kernels, and have done it a decent amount of times. I have several other machines I would like to upgrade to RH 8.0, but can't until I can compile custom kernels. Has anyone else had similar problems, any suggestions. I can post the results of an attempted make modules and the many errors that are spit out. Anyway I am looking for some initial feedback, and will provide further info upon request, as I do not want to just toss in a bunch of lines of error codes that gets generated on a variety of modules. It does attempt to make the modules, but fails and stops on the first modules. I have tried not using certain modules and using others, but either way the first one it tries to compile it will fail on. No matter what module it is, for some reason. Any comments, thoughts or input is greatly appreciated. -- Sincerely, William L. Thomson Jr. Support Group Obsidian-Studios Inc. 439 Amber Way Petaluma, Ca. 94952 Phone 707.766.9509 Fax707.766.8989 http://www.obsidian-studios.com ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re-Compiling the kernel.
Hello all. I'm in the process of re-compiling the kernel, but I get to a point where there's an error. These are the steps up to the error: # cd /usr/src/linux-2.4.18-3 # make config (CONFIG_PCMCIA = no to achieve a kernel without PCMCIA support) # make dep # make clean # make bzImage # make modules # make modules_install ( this is where the error appears) ln: when making multiple links, last argument must be a directory make: *** [_modinst_] Error 1 # I read the man pages and it suggests that the directory it should make_install is /lib/modules/2.4.*/ My new kernel will be called 2.4.18-3no-pcmcia-cs so I tried: # make modules_install /lib/modules/2.4.18-3no-pcmcia-cs/ but the same error occurs. Please can you advise me where I'm going wrong. Thanks, Trevor. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re-Compiling the kernel.
Hello all. I'm in the process of re-compiling the kernel, but I get to a point where there's an error. These are the steps up to the error: # cd /usr/src/linux-2.4.18-3 # make config (CONFIG_PCMCIA = no to achieve a kernel without PCMCIA support) # make dep # make clean # make bzImage # make modules # make modules_install ( this is where the error appears) ln: when making multiple links, last argument must be a directory make: *** [_modinst_] Error 1 # I read the man pages and it suggests that the directory it should make_install is /lib/modules/2.4.*/ My new kernel will be called 2.4.18-3no-pcmcia-cs so I tried: # make modules_install /lib/modules/2.4.18-3no-pcmcia-cs/ but the same error occurs. Please can you advise me where I'm going wrong. Thanks, Trevor. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
compiling the kernel to recognize ntfs
Hello friends, I want to recompile my kernel to recognize ntfs (in the kernel or as a module), but, anyone can tell me his experience doing this? My kernel is 2.4.18-3 and my red hat is 7.3 = Saludos desde México RAML _ Do You Yahoo!? Información de Estados Unidos y América Latina, en Yahoo! Noticias. Visítanos en http://noticias.espanol.yahoo.com -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel to recognize ntfs
So..., I recompile the kernel with NTFS suport, and copy to /boot, I modify grub.conf in /boot/grub to select the kernel to boot, but when select the kernel with NTFS suport the system freezing when the red hat 7.3 is begin to load..., then I have to rebooting the machine and select the kernel unmodifing to enter, but without NTFS suport, what is wrong with this procedure? --- Ricardo Mostalac [EMAIL PROTECTED] escribió: Hello friends, I want to recompile my kernel to recognize ntfs (in the kernel or as a module), but, anyone can tell me his experience doing this? My kernel is 2.4.18-3 and my red hat is 7.3 = Saludos desde México RAML _ Do You Yahoo!? Información de Estados Unidos y América Latina, en Yahoo! Noticias. Visítanos en http://noticias.espanol.yahoo.com -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list = Saludos desde México RAML _ Do You Yahoo!? Información de Estados Unidos y América Latina, en Yahoo! Noticias. Visítanos en http://noticias.espanol.yahoo.com -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
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
Re: compiling the kernel
Stuart Why don't try http://www.linuxdoc.org. In here, you can find a detail how-to document for compliling the linux kernel. Regards, Andrew So Hing-pong Hidong Kim wrote: http://www.freeos.com/articles/2589/2/1-3/ among many others found from a google search on "compiling the linux kernel". Good luck, Stuart Clark wrote: Well! anyone would think that instructions for compiling the kernel would be on the kernel.org site . But alas no. Can anyone tell me where to get this info from. Regards Stu ___ 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 ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
-BEGIN PGP SIGNED MESSAGE- Well! anyone would think that instructions for compiling the kernel would be on the kernel.org site . But alas no. Can anyone tell me where to get this info from. Actually, the kernel docs (which you get when you install the kernel-doc package) have everything you'll need. Have you looked there? - -d - -- David Talkington Prairienet [EMAIL PROTECTED] 217-244-1962 PGP key: http://www.prairienet.org/~dtalk/dt000823.asc -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQEVAwUBOsDPTL1ZYOtSwT+tAQE6HggAuLyqPUFJF+WPyet+WvWQXam8G+q8uVmR mZGk8tocpNs+pQT1olSUEPZBWU5rvF9ywAsIV+CLkwOi8TPOxIlNFU9fjDumJA+9 C/IjVI2CZMex+POos0sgPOet0FlhYb2hhT21geAd1t6WIl2OTrRCdX/vFMBRSoDe nBElxe/Fi7Qrqlz+sTDgCybn4f2ykdBWUHS2unqw4z7A6D5I+06YEtxumUR+VTL9 gfcJM5Zw9NdikeZfPyMJZxEDwgE10bNo9PlOq6vVsrZ8YXgk/1Y0T9hO1CGdoIaH eBZqx5qM94VBZQUwDPuAvxRzI4z/8JWZZivPjH2yfZFsnJim5HEiEQ== =PZre -END PGP SIGNATURE- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
compiling the kernel
Well! anyone would think that instructions for compiling the kernel would be on the kernel.org site . But alas no. Can anyone tell me where to get this info from. Regards Stu ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: compiling the kernel
http://www.freeos.com/articles/2589/2/1-3/ among many others found from a google search on "compiling the linux kernel". Good luck, Stuart Clark wrote: Well! anyone would think that instructions for compiling the kernel would be on the kernel.org site . But alas no. Can anyone tell me where to get this info from. Regards Stu ___ 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
Compiling New Kernel
Hi Everyone, How are you? I have been using stock RH kernel rpms for a long time. But now, wishing to usr reiserfs, I need to build a tailored kernel but get an error: 'unresolved ref: memcpy' Do you know how to fix it? My platform is Intel Celeron 667/128MB/RH7.0/Kernel 2.2.18. The machine works flawlessly in all other areas. Alternatively, do you know if there is any stock kernel rpms with reiserfs support? Your help is much appreciated. -- Regards, Clement ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Compiling the Kernel
Ok.. I downloaded the patches... This is going to sound dumb but how do I install them :DOk... I feel like a newbie again ::grinz:: BTW, I also tried compiling the latest egcs source (1.1.2 I think). I'm getting a signal 11 error after I think 70% + complete with the build (make bootstrap). No issues with the config. Looks good. I read the FAQ on signal 11 errors. Is there perhaps a list of software that I should have upgraded prior to compiling egcs? I realize that it could be hardware related (the FAQ suggested this). I'm going over everything to rule that out. Thx for the help! Frank www.xmission.com/~dmacleod Bernhard Rosenkraenzer wrote: On Fri, 11 Feb 2000, Frank Carreiro wrote: sbni.c:1375: Invalid `asm' statement: sbni.c:1375: fixed or forbidden register 1 (sx) was spilled for class DREG. You're trying to compile this kernel with gcc 2.95.x. Either get the gcc 2.95.x kernel patch (http://people.redhat.com/bero/gcc295/) or use egcs 1.1.x/gcc 2.7.x/gcc 2.8.x to compile this kernel. LLaP bero -- The first time Microsoft makes something that doesn't suck is when they start making vacuum cleaners. -- This is Linux Country. On a quiet night, you can hear Windows NT reboot. -- To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
Compiling the Kernel
Hiya there all... I know we just had some conversation about this but I wanted to add my experience and perhaps find a solution. I've compiled Kernels for a couple of years and haven't really had problems until now. I'm "stuck" with a RedHat 5.2 installation (can't upgrade to 6.1 for various reasons). I've upgraded my Kernel from 2.0.36 (the default) to 2.2.10 (no sweat). Everything is happy until now. I've compiled Kernels from version 2.2.12 to 2.2.14 successfully BUT when I try to run "make modules" I get the following errors: sbni.c:1375: Invalid `asm' statement: sbni.c:1375: fixed or forbidden register 1 (sx) was spilled for class DREG. sbni.c:1377: warning: control reaches end of non-void function make[2]: *** [sbni.o] Error 1 make[2]: Leaving directory `/user/src/linux-2-2.12/drivers/net' make[1]: *** [_modsubdir_net] Error 2 make[1]: Leaving directory `/usr/src/linux-2.2.12/drivers' make: *** [_mod_drivers] Error 2 The above compile was 2.2.12 obviously. Figured I'd try it again. My "guess" is that I need to upgrade my glibc or libc. Can't think of any other reason that this wouldn't work. Comments? I really appreciate any tidbits you guys can give. Frank www.xmission.com/~dmacleod -- This is Linux Country. On a quiet night, you can hear Windows NT reboot. -- To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
Re: Compiling the Kernel
On Fri, 11 Feb 2000, Frank Carreiro wrote: sbni.c:1375: Invalid `asm' statement: sbni.c:1375: fixed or forbidden register 1 (sx) was spilled for class DREG. You're trying to compile this kernel with gcc 2.95.x. Either get the gcc 2.95.x kernel patch (http://people.redhat.com/bero/gcc295/) or use egcs 1.1.x/gcc 2.7.x/gcc 2.8.x to compile this kernel. LLaP bero -- The first time Microsoft makes something that doesn't suck is when they start making vacuum cleaners. -- To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
