Kernel Compile Problems
A make menuconfig fails in checklist.c with the following: debian-rtg:/usr/src/linux-2.6.3# make menuconfig HOSTCC scripts/fixdep SHIPPED scripts/kconfig/zconf.tab.h HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/mconf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/lex.zconf.c HOSTCC -fPIC scripts/kconfig/zconf.tab.o HOSTLLD -shared scripts/kconfig/libkconfig.so HOSTLD scripts/kconfig/mconf HOSTCC scripts/lxdialog/checklist.o In file included from scripts/lxdialog/checklist.c:24: scripts/lxdialog/dialog.h:29:20: curses.h: No such file or directory In file included from scripts/lxdialog/checklist.c:24: scripts/lxdialog/dialog.h:127: error: parse error before use_colors scripts/lxdialog/dialog.h:127: warning: type defaults to `int' in declaration of `use_colors' scripts/lxdialog/dialog.h:127: warning: data definition has no type or storage class scripts/lxdialog/dialog.h:128: error: parse error before use_shadow scripts/lxdialog/dialog.h:128: warning: type defaults to `int' in declaration of `use_shadow' scripts/lxdialog/dialog.h:128: warning: data definition has no type or storage class SNIP The errors continue for another two pages, but the above text is sufficient to show that something in wrong. This immediately following the download from www.kernel.org of linux-2.6.3.bz2. After bunzip2'ing the file, tar xf'ing the result, cd'ing to the directory, and issuing a make menuconfig the above is the result. For what is purported to be a release kernel, my problems indicate errors on the part of the kernel maintainers or myself. I hope it is myself. -- Comments are appreciated, Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel Compile Problems
On Sun, Feb 22, 2004 at 11:11:24AM -0500, Robert Tilley wrote: scripts/lxdialog/dialog.h:29:20: curses.h: No such file or directory Install libncurses-dev. IIRC its one of the suggests for kernel-source-* Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile problems with gcc 3.3
On Mon, 09 Jun 2003 23:16:55 -0400, Peter S Galbraith wrote: Dan Jones [EMAIL PROTECTED] wrote: On Mon, 09 Jun 2003 18:26:46 GMT, Matthias Leopold wrote: hi i tried to recompile my 2.4.20 kernel with make-kpkg (as i have successfully done before) incorporating the xfs and ck patches. this time the process stopped with the following error message: net/network.o(.text+0xe117): In function `rtnetlink_rcv': : undefined reference to `rtnetlink_rcv_skb Two ways. One is to use gcc-3.2.3. You can install the gcc-3.2.3 without uninstalling the gcc-3.3 package. Just change the symbolic link in /usr/bin to point to the older compiler after install. I'm now compiling with gcc-3.2 (by editing the top-level Makefile value for CC) but I'm getting erors all over the place. Then I config out the problematic file only to have it fail later. :-( Did you restart the compile process from the beginning? Start with make config (or xconfig or menuconfig), then make dep, make clean and make bzImage (assuming you're using bzImages.) If you change compilers and simply go right to make bzImage, you'll get all kinds of problems like you described. Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile problems with gcc 3.3
On Mon, 09 Jun 2003 23:44:58 -0400, J.F.Gratton wrote: Actually, both errors are *not* the same Dan's is due to something missing in the kernel sources; I've read the thread in the kernel developpers' mailing list, I can't recall exactly what is missing, but I know that a patch is available, either for 2.4.20 or the soon-to-come 2.4.21. An acceptable workaround for now is to downgrade your compiler (3.2.x seems to be OK with it; I recompiled my kernel using 2.95 and it worked fine). Everything I've read indicates that it's a case of gcc-3.3 deciding that you REALLY didn't want that function inlined. The patch simply does the same thing I posted here - changes it to a static inline which causes gcc to go ahead and inline it. If you've seen another explination and have a pointer handy, I'd be interested in seeing the discussion. Thanks, Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel compile problems with gcc 3.3
hi i tried to recompile my 2.4.20 kernel with make-kpkg (as i have successfully done before) incorporating the xfs and ck patches. this time the process stopped with the following error message: net/network.o(.text+0xe117): In function `rtnetlink_rcv': : undefined reference to `rtnetlink_rcv_skb in google i found one reference to this problem (but no solution) which linked the problem to the newly introduced gcc-3.3. how do i avoid this? relevant parts of my system are from testing. thanks for advice matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile problems with gcc 3.3
On Mon, Jun 09, 2003 at 06:26:46PM +, Matthias Leopold wrote: i tried to recompile my 2.4.20 kernel with make-kpkg (as i have successfully done before) incorporating the xfs and ck patches. this time the process stopped with the following error message: net/network.o(.text+0xe117): In function `rtnetlink_rcv': : undefined reference to `rtnetlink_rcv_skb in google i found one reference to this problem (but no solution) which linked the problem to the newly introduced gcc-3.3. how do i avoid this? Search the D-U archives. There have been a number of discussions recently about kernel compiling. MAKEFLAGS=CC=gcc-2.95 make-kpkg ... The above will have the effect of using gcc-2.95. -- Jamin W. Collins This is the typical unix way of doing things: you string together lots of very specific tools to accomplish larger tasks. -- Vineet Kumar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile problems with gcc 3.3
On Mon, Jun 09, 2003 at 06:26:46PM +, Matthias Leopold wrote: hi hi, i tried to recompile my 2.4.20 kernel with make-kpkg (as i have successfully done before) incorporating the xfs and ck patches. this time the process stopped with the following error message: net/network.o(.text+0xe117): In function `rtnetlink_rcv': : undefined reference to `rtnetlink_rcv_skb in google i found one reference to this problem (but no solution) which linked the problem to the newly introduced gcc-3.3. how do i avoid this? use an older gcc. i got the same problems in the same object files as you. using 2.95 did solve the problem. - regards, turrican -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile problems with gcc 3.3
On Mon, 09 Jun 2003 18:26:46 GMT, Matthias Leopold wrote: hi i tried to recompile my 2.4.20 kernel with make-kpkg (as i have successfully done before) incorporating the xfs and ck patches. this time the process stopped with the following error message: net/network.o(.text+0xe117): In function `rtnetlink_rcv': : undefined reference to `rtnetlink_rcv_skb in google i found one reference to this problem (but no solution) which linked the problem to the newly introduced gcc-3.3. how do i avoid this? Two ways. One is to use gcc-3.2.3. You can install the gcc-3.2.3 without uninstalling the gcc-3.3 package. Just change the symbolic link in /usr/bin to point to the older compiler after install. Alternately, you can edit /usr/src/linux/net/core/rtnetlink.c and change the function declaration from extern __inline__ int rtlink_rcv_skb(struct sk_buf *skb); to static inline int rtlink_rcv_skb(struct sk_buf *skb); (The leading and trailing underscores around inline are no longer needed.) Changing the declaration from extern inline to static inline causes gcc-3.3 to actually inline the function and fix the problem. regards, Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile problems with gcc 3.3
Dan Jones [EMAIL PROTECTED] wrote: On Mon, 09 Jun 2003 18:26:46 GMT, Matthias Leopold wrote: hi i tried to recompile my 2.4.20 kernel with make-kpkg (as i have successfully done before) incorporating the xfs and ck patches. this time the process stopped with the following error message: net/network.o(.text+0xe117): In function `rtnetlink_rcv': : undefined reference to `rtnetlink_rcv_skb in google i found one reference to this problem (but no solution) which linked the problem to the newly introduced gcc-3.3. how do i avoid this? I had the exact same error. Two ways. One is to use gcc-3.2.3. You can install the gcc-3.2.3 without uninstalling the gcc-3.3 package. Just change the symbolic link in /usr/bin to point to the older compiler after install. Alternately, you can edit /usr/src/linux/net/core/rtnetlink.c and change the function declaration from extern __inline__ int rtlink_rcv_skb(struct sk_buf *skb); to static inline int rtlink_rcv_skb(struct sk_buf *skb); (The leading and trailing underscores around inline are no longer needed.) Changing the declaration from extern inline to static inline causes gcc-3.3 to actually inline the function and fix the problem. I'm now compiling with gcc-3.2 (by editing the top-level Makefile value for CC) but I'm getting erors all over the place. Then I config out the problematic file only to have it fail later. :-( Latest is: gcc-3.2 -D__KERNEL__ -I/usr/src/kernel-source-2.4.20/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -DMODULE -DMODVERSIONS -include /usr/src/kernel-source-2.4.20/include/linux/modversions.h -nostdinc -iwithprefix include -DKBUILD_BASENAME=cciss -c -o cciss.o cciss.c cciss.c: In function `cciss_ioctl': cciss.c:422: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. make[3]: *** [cciss.o] Error 1 make[3]: Leaving directory `/usr/src/kernel-source-2.4.20/drivers/block' make[2]: *** [_modsubdir_block] Error 2 make[2]: Leaving directory `/usr/src/kernel-source-2.4.20/drivers' make[1]: *** [_mod_drivers] Error 2 make[1]: Leaving directory `/usr/src/kernel-source-2.4.20' make: *** [stamp-build] Error 2 Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile problems with gcc 3.3
Actually, both errors are *not* the same Dan's is due to something missing in the kernel sources; I've read the thread in the kernel developpers' mailing list, I can't recall exactly what is missing, but I know that a patch is available, either for 2.4.20 or the soon-to-come 2.4.21. An acceptable workaround for now is to downgrade your compiler (3.2.x seems to be OK with it; I recompiled my kernel using 2.95 and it worked fine). As for Peter's, this kind of segfaulting has been around since gcc-3.x AFAIK. I've came across quite a few times, everytime it involved compilation of large projects (the kernel, QT3, etc). All you have to do is simply to re-start make (make, make bzImage, make modules, whatever) and all works fine. For both of you, I'm not saying that the solutions I offer is *THE* solutions, but at least these worked for me. Someone might come with a better one, you decide :) Jeff On Mon, 2003-06-09 at 23:16, Peter S Galbraith wrote: Dan Jones [EMAIL PROTECTED] wrote: On Mon, 09 Jun 2003 18:26:46 GMT, Matthias Leopold wrote: hi i tried to recompile my 2.4.20 kernel with make-kpkg (as i have successfully done before) incorporating the xfs and ck patches. this time the process stopped with the following error message: net/network.o(.text+0xe117): In function `rtnetlink_rcv': : undefined reference to `rtnetlink_rcv_skb in google i found one reference to this problem (but no solution) which linked the problem to the newly introduced gcc-3.3. how do i avoid this? I had the exact same error. Two ways. One is to use gcc-3.2.3. You can install the gcc-3.2.3 without uninstalling the gcc-3.3 package. Just change the symbolic link in /usr/bin to point to the older compiler after install. Alternately, you can edit /usr/src/linux/net/core/rtnetlink.c and change the function declaration from extern __inline__ int rtlink_rcv_skb(struct sk_buf *skb); to static inline int rtlink_rcv_skb(struct sk_buf *skb); (The leading and trailing underscores around inline are no longer needed.) Changing the declaration from extern inline to static inline causes gcc-3.3 to actually inline the function and fix the problem. I'm now compiling with gcc-3.2 (by editing the top-level Makefile value for CC) but I'm getting erors all over the place. Then I config out the problematic file only to have it fail later. :-( Latest is: gcc-3.2 -D__KERNEL__ -I/usr/src/kernel-source-2.4.20/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -DMODULE -DMODVERSIONS -include /usr/src/kernel-source-2.4.20/include/linux/modversions.h -nostdinc -iwithprefix include -DKBUILD_BASENAME=cciss -c -o cciss.o cciss.c cciss.c: In function `cciss_ioctl': cciss.c:422: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. make[3]: *** [cciss.o] Error 1 make[3]: Leaving directory `/usr/src/kernel-source-2.4.20/drivers/block' make[2]: *** [_modsubdir_block] Error 2 make[2]: Leaving directory `/usr/src/kernel-source-2.4.20/drivers' make[1]: *** [_mod_drivers] Error 2 make[1]: Leaving directory `/usr/src/kernel-source-2.4.20' make: *** [stamp-build] Error 2 Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile problems
On Tue, Dec 25, 2001 at 10:53:06PM -0500, Sean Johnson wrote: The current binutils in sid is fine for compiling 2.4.17 (latest 2.4.x stable kernel). It's not binutils that have the problem... it's the kernel. Use a 2.4.17 or later kernel if you want to avoid the error showing up most of the time. The fixes contiue as well... I saw in the kernel mailing list that another one of them was identified and fixed. It'll probably take a while. See lkml for the gory details. -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] pgpmkqCgyd0Fo.pgp Description: PGP signature
kernel compile problems
Greetings -- I've been setting up a new Athlon system (thanks Santa!), and I've been having some kernel compile issues (linker bombing out, mainly). I was chalking it up to some Athlon quirk (power supply, cooling, etc.), but just on the off chance I tried to re-compile a kernel on my old Celeron-based system -- and I got the same *sort* of error (not the exact same error, but the same sort of linker error). So, is there some sort of problem with kernel compiles here recently? I notice we got new gcc packages yesterday... Running: sid, up to date as of 12/25. john. -- genehack.org * weblog == ( bioinfo / linux / opinion / stuff ) * daily * Avoid multiple exits from loops. - The Elements of Programming Style (Kernighan Plaugher)
Re: kernel compile problems
John S. J. Anderson wrote: Greetings -- I've been setting up a new Athlon system (thanks Santa!), and I've been having some kernel compile issues (linker bombing out, mainly). I was chalking it up to some Athlon quirk (power supply, cooling, etc.), but just on the off chance I tried to re-compile a kernel on my old Celeron-based system -- and I got the same *sort* of error (not the exact same error, but the same sort of linker error). So, is there some sort of problem with kernel compiles here recently? I notice we got new gcc packages yesterday... Running: sid, up to date as of 12/25. john. Are you using debian unstable, and using binutils? If so, your best bet would be to downgrade binutils to the latest stable. I had the same problem. David.
Re: kernel compile problems
On Tue, 25 Dec 2001 19:43:46 +0100 David Gardi [EMAIL PROTECTED] wrote: --snip-- So, is there some sort of problem with kernel compiles here recently? I notice we got new gcc packages yesterday... Running: sid, up to date as of 12/25. john. Are you using debian unstable, and using binutils? If so, your best bet would be to downgrade binutils to the latest stable. I had the same problem. David. The current binutils in sid is fine for compiling 2.4.17 (latest 2.4.x stable kernel). Sean -- GPG Public Key available: http://www.gutenpress.org/gpg/sean.asc pgpW6NFcMYPSm.pgp Description: PGP signature
Re: kernel compile problems
Sean Johnson wrote: The current binutils in sid is fine for compiling 2.4.17 (latest 2.4.x stable kernel). No, it isn't. This has come up a few times already just in the few days since 2.4.17 came out. Depending on your kernel configuration, you may still run into the same problems that people were having before. It may well be that this crops up with 2.4.17 less than it did with previous 2.4.x kernels, but it is still there. There's no need, however, to go as far back as Potato's binutils. The unstable/testing binutils from late November (2.11.92.0.10-4) seems to work; I haven't heard of any problems from anyone using that version. It can be found via a search at tuxfinder.org; and I have it as well, in my Sid not-quite-latest archive (use a web browser, not dpkg, to access) at http://crdic.ath.cx/debian . Craig
Re: kernel compile problems
David Gardi wrote: Are you using debian unstable, and using binutils? If so, your best bet would be to downgrade binutils to the latest stable. I had the same problem. *shudder* No need to go back that far! Sid's binutils from late November (2.11.92.0.10-4) seems to work fine. You can get it by searching at tuxfinder.org, or from my Web-browseable (not dpkg-searchable) archive at http://crdic.ath.cx/debian . Craig
Re: kernel compile problems
On Tue, 25 Dec 2001 19:43:46 +0100 David Gardi [EMAIL PROTECTED] wrote: --snip-- So, is there some sort of problem with kernel compiles here recently? I notice we got new gcc packages yesterday... Running: sid, up to date as of 12/25. john. Are you using debian unstable, and using binutils? If so, your best bet would be to downgrade binutils to the latest stable. I had the same problem. David. The current binutils in sid is fine for compiling 2.4.17 (latest 2.4.x stable kernel). Sean -- GPG Public Key available: http://www.gutenpress.org/gpg/sean.asc pgpbGoTxNPheY.pgp Description: PGP signature
kernel compile problems
Just finished installing Potato on my iBook, and now I'm trying to buildd BenH's 2.4 kernel (which has AirPort support and a working Powerbook ethernet driver, among other things). Did make config, went through the whole she-bang, that all worked fine. Did make dep and about halfway through got the following error message (the line that begins find... is shortened considerably): scripts/mkdep -- `find /root/benh-ker` .hdepend /bin/sh: scripts/mkdep: Argument list too long make: *** [dep-files] Error 126 It's pretty clear to me that the last line being executed by scripts/mkdep is too long, and that's what the machine is tripping over. What's not clear to me is how I can fix it. Any thoughts/ideas? - Ian -- [EMAIL PROTECTED] 773 667 2550 Eventually all things merge into one, and a river runs through it. The river was cut by the world's great flood and runs over rocks from the basement of time. On some of the rocks are timeless raindrops. Under the rocks are the words, and some of the words are theirs. I am haunted by waters.
Re: kernel compile problems
Pulling this out of a hat but see if you can break the arguments of it into two lines and then make the second one append into .hdepend --mike On 10 Aug 2001 15:27:16 -0500, Ian Marlier wrote: Just finished installing Potato on my iBook, and now I'm trying to buildd BenH's 2.4 kernel (which has AirPort support and a working Powerbook ethernet driver, among other things). Did make config, went through the whole she-bang, that all worked fine. Did make dep and about halfway through got the following error message (the line that begins find... is shortened considerably): scripts/mkdep -- `find /root/benh-ker` .hdepend /bin/sh: scripts/mkdep: Argument list too long make: *** [dep-files] Error 126 It's pretty clear to me that the last line being executed by scripts/mkdep is too long, and that's what the machine is tripping over. What's not clear to me is how I can fix it. Any thoughts/ideas? - Ian -- [EMAIL PROTECTED] 773 667 2550 Eventually all things merge into one, and a river runs through it. The river was cut by the world's great flood and runs over rocks from the basement of time. On some of the rocks are timeless raindrops. Under the rocks are the words, and some of the words are theirs. I am haunted by waters. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile problems
On Fri, Aug 10, 2001 at 03:31:35PM -0500, Michael Heldebrant wrote: Pulling this out of a hat but see if you can break the arguments of it into two lines and then make the second one append into .hdepend Mike, Please please please learn how to quote your emails properly. You're driving me (and probably others) nuts. Your replies should always follow the quoted message, and should not come before. Otherwise, it's much harder to follow the thread and the context of your reply. Check out these links for more info (especially the last one): http://www.math.fu-berlin.de/~guckes/mail/edit.html http://www.iwillfollow.com/email.htm http://home.online.no/~vidaandr/news/FAQquoting.html Thanks. On 10 Aug 2001 15:27:16 -0500, Ian Marlier wrote: snip -- Brian Nelson [EMAIL PROTECTED]
Re: kernel compile problems
On 10 Aug 2001 16:43:36 -0400, Brian Nelson wrote: On Fri, Aug 10, 2001 at 03:31:35PM -0500, Michael Heldebrant wrote: Pulling this out of a hat but see if you can break the arguments of it into two lines and then make the second one append into .hdepend Mike, Please please please learn how to quote your emails properly. You're driving me (and probably others) nuts. Your replies should always follow the quoted message, and should not come before. Otherwise, it's much harder to follow the thread and the context of your reply. Check out these links for more info (especially the last one): http://www.math.fu-berlin.de/~guckes/mail/edit.html http://www.iwillfollow.com/email.htm http://home.online.no/~vidaandr/news/FAQquoting.html Thanks. On 10 Aug 2001 15:27:16 -0500, Ian Marlier wrote: snip -- Brian Nelson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I'm sorry, didn't know that was the proper way to follow up a post. I'll start from the bottom in the future. --mike
Re: kernel compile problems
At 3:31 PM -0500 8/10/01, Michael Heldebrant wrote: Pulling this out of a hat but see if you can break the arguments of it into two lines and then make the second one append into .hdepend --mike On 10 Aug 2001 15:27:16 -0500, Ian Marlier wrote: Just finished installing Potato on my iBook, and now I'm trying to buildd BenH's 2.4 kernel (which has AirPort support and a working Powerbook ethernet driver, among other things). Did make config, went through the whole she-bang, that all worked fine. Did make dep and about halfway through got the following error message (the line that begins find... is shortened considerably): scripts/mkdep -- `find /root/benh-ker` .hdepend /bin/sh: scripts/mkdep: Argument list too long make: *** [dep-files] Error 126 It's pretty clear to me that the last line being executed by scripts/mkdep is too long, and that's what the machine is tripping over. What's not clear to me is how I can fix it. Any thoughts/ideas? - Ian Hrm...this is what I was planning to do, but mkdep isn't a shell script -- it's a C file that (I guess) gets compiled on the fly to pull in the config variables. So there isn't a line somewhere that I can just cut in half... The other problem is that almost the entire line that's causing the problem is one find command (it searches for a file in 4 or 5 directories, then does stuff to the result). Ian -- [EMAIL PROTECTED] 773 667 2550 Eventually all things merge into one, and a river runs through it. The river was cut by the world's great flood and runs over rocks from the basement of time. On some of the rocks are timeless raindrops. Under the rocks are the words, and some of the words are theirs. I am haunted by waters.
Re: kernel compile problems
On Fri, Aug 10, 2001 at 04:00:45PM -0500, Ian Marlier wrote: Hrm...this is what I was planning to do, but mkdep isn't a shell script -- it's a C file that (I guess) gets compiled on the fly to pull in the config variables. So there isn't a line somewhere that I can just cut in half... The other problem is that almost the entire line that's causing the problem is one find command (it searches for a file in 4 or 5 directories, then does stuff to the result). Then split up the find commands to only look in one or two directories...
Re: kernel compile problems
Subject: Re: kernel compile problems Date: Fri, Aug 10, 2001 at 03:46:43PM -0500 In reply to:Michael Heldebrant Quoting Michael Heldebrant([EMAIL PROTECTED]): On 10 Aug 2001 16:43:36 -0400, Brian Nelson wrote: On Fri, Aug 10, 2001 at 03:31:35PM -0500, Michael Heldebrant wrote: Pulling this out of a hat but see if you can break the arguments of it into two lines and then make the second one append into .hdepend Mike, Please please please learn how to quote your emails properly. You're driving me (and probably others) nuts. Your replies should always follow the quoted message, and should not come before. Otherwise, it's much harder to follow the thread and the context of your reply. Check out these links for more info (especially the last one): http://www.math.fu-berlin.de/~guckes/mail/edit.html http://www.iwillfollow.com/email.htm http://home.online.no/~vidaandr/news/FAQquoting.html Quote useless text follows Thanks. On 10 Aug 2001 15:27:16 -0500, Ian Marlier wrote: snip -- Brian Nelson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Unqoute useless text I'm sorry, didn't know that was the proper way to follow up a post. I'll start from the bottom in the future. --mike Mike, could you also delete the useless text as well, please. A lot of the guys in Europe pay for internet access on a per/byte basis, IIRC. They would appreciate it and it would make the reading easier for all of us. -- The information went data way - ___
kernel compile problems
I'm running progeny rc1 and, since it didn't configure my sound card during install, I recompiled my kernel (2.2.18) and included support for my soundcard (Yamaha OPL3-SA2) through OSS. After several tries, I finally seem to have gotten all the io settings right (dma, ioports and interrupts in /proc look like they're all in order, as does /proc/sound and dmesg shows everything being recognized/loaded fine) but I still can't get sound working and it also breaks my network card (3com Etherlink XL Combo 3C900). My first though was that there was some kind of conflict but I can't find any. Here're the settings for both cards: Sound (from /usr/src/linux/.config): CONFIG_SOUND_OPL3SA2=y CONFIG_OPL3SA2_CHIPSET=-1 CONFIG_OPL3SA2_BASE=530 CONFIG_OPL3SA2_IRQ=5 CONFIG_OPL3SA2_DMA=0 CONFIG_OPL3SA2_DMA2=1 CONFIG_OPL3SA2_CTRL_BASE=370 CONFIG_OPL3SA2_MPU_BASE=330 CONFIG_OPL3SA2_MPU_IRQ=5 I'd include the settings from /proc but that would require me to install the new kernel again and break networking :) They looked right, anyway. Ethernet: ioports: fcc0-fcff : eth0 interrupts: 9: 28040 XT-PIC eth0 With regard to sound, I've tried running both aumix and gmix, both of which complain about not being able to access /dev/dsp (how can I make sure I included /dev/dsp support in the kernel... I couldn't find an option for it in menuconfig). As for the network card, ifconfig finds it and running 'dhclient eth0' returns no errors but still doesn't seem to work. I also tried including it as a module with no success... I'm trying to connect through a cable modem, btw. Any ideas on how I can debug this?
Re: [FIXED] kernel compile problems
Sound wasn't working because /dev/dsp and /dev/mixer weren't user read/writeable... duh :-\ For networking I had to run pump and not dhclient. What's more, I had to run pump without any switch first and then run pump -R (don't know if the pump -R was even necessary). Anyway, it's fixed... DvB wrote: I'm running progeny rc1 and, since it didn't configure my sound card during install, I recompiled my kernel (2.2.18) and included support for my soundcard (Yamaha OPL3-SA2) through OSS. After several tries, I finally seem to have gotten all the io settings right (dma, ioports and interrupts in /proc look like they're all in order, as does /proc/sound and dmesg shows everything being recognized/loaded fine) but I still can't get sound working and it also breaks my network card (3com Etherlink XL Combo 3C900). My first though was that there was some kind of conflict but I can't find any. Here're the settings for both cards: Sound (from /usr/src/linux/.config): CONFIG_SOUND_OPL3SA2=y CONFIG_OPL3SA2_CHIPSET=-1 CONFIG_OPL3SA2_BASE=530 CONFIG_OPL3SA2_IRQ=5 CONFIG_OPL3SA2_DMA=0 CONFIG_OPL3SA2_DMA2=1 CONFIG_OPL3SA2_CTRL_BASE=370 CONFIG_OPL3SA2_MPU_BASE=330 CONFIG_OPL3SA2_MPU_IRQ=5 I'd include the settings from /proc but that would require me to install the new kernel again and break networking :) They looked right, anyway. Ethernet: ioports: fcc0-fcff : eth0 interrupts: 9: 28040 XT-PIC eth0 With regard to sound, I've tried running both aumix and gmix, both of which complain about not being able to access /dev/dsp (how can I make sure I included /dev/dsp support in the kernel... I couldn't find an option for it in menuconfig). As for the network card, ifconfig finds it and running 'dhclient eth0' returns no errors but still doesn't seem to work. I also tried including it as a module with no success... I'm trying to connect through a cable modem, btw. Any ideas on how I can debug this?
Re: Kernel COmpile Problems
Ronald == Ronald Castillo [EMAIL PROTECTED] writes: Ronald Thanks for your help.. I'll do that. I also think Ronald kernel-source should recommend that. Otherwise, how would Ronald newbies like me do without help from this mailing list? Firstly, this is not required for the forthcoming 2.4 series kernels. Secondly, kernel-package is an arch all package, and bin86 does not even exist on any other architecture than the i356, so dependencies are definitely out. The description of the kernel-source package, the README files, the README files for the kernel-package package, the Debian FAQ's, all explain that if you need to compile a kernel on an i386 machine, you need to download the bin86 package. It also appears on the Bug list at frequent intervals.I still think people should read those prior to compiling a kernel. Not having bin86 is only the smallest of gotchas in a kernel compile. I strongly recommend that people compiling kernels should read these docs ;-) I repeat: People should not try to compile a kernel who do not read docs. Consider this a security feature. Thus, this lack of a explicit dependency is by design. The requirement is documented enough that people have ample opportunity to discover this on their own. manoj -- He who writes with no misspelled words has prevented a first suspicion on the limits of his scholarship or, in the social world, of his general education and culture. Julia Norton McCorkle Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Kernel COmpile Problems
Hi... I had a small problem when I was compiling my kernel. when I typed the make bzImage command, at the end I got an error message saying make: as86: Command not found or something like that. Do I have to install any package? I'm using the rain distribution of Storm, based on Slink. Thanks for your help... Ronald
Re: Kernel COmpile Problems
On Mon, Sep 11, 2000 at 11:31:15AM -, Ronald Castillo wrote: Hi... I had a small problem when I was compiling my kernel. when I typed the make bzImage command, at the end I got an error message saying make: as86: Command not found or something like that. Do I have to install any package? I'm using the rain distribution of Storm, based on Slink. Thanks for your help... $ dpkg -S as86 bin86: /usr/share/doc/bin86/examples/as86_encap bin86: /usr/bin/as86 bin86: /usr/share/man/man1/as86.1.gz :) Install bin86 package. Mirek
RE: Kernel COmpile Problems
I'll do it. Thanks for your help!! -Original Message- From: Mirek Kwasniak [mailto:[EMAIL PROTECTED] Sent: Monday, September 11, 2000 3:40 PM To: Ronald Castillo Cc: Debian-User Mailing List Subject: Re: Kernel COmpile Problems On Mon, Sep 11, 2000 at 11:31:15AM -, Ronald Castillo wrote: Hi... I had a small problem when I was compiling my kernel. when I typed the make bzImage command, at the end I got an error message saying make: as86: Command not found or something like that. Do I have to install any package? I'm using the rain distribution of Storm, based on Slink. Thanks for your help... $ dpkg -S as86 bin86: /usr/share/doc/bin86/examples/as86_encap bin86: /usr/bin/as86 bin86: /usr/share/man/man1/as86.1.gz :) Install bin86 package. Mirek -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
RE: Kernel COmpile Problems
Thanks for your help.. I'll do that. I also think kernel-source should recommend that. Otherwise, how would newbies like me do without help from this mailing list? -Original Message- From: Michal F. Hanula [mailto:[EMAIL PROTECTED] Sent: Monday, September 11, 2000 3:42 PM To: Ronald Castillo Subject: Re: Kernel COmpile Problems On Mon, Sep 11, 2000 at 11:31:15AM -, Ronald Castillo wrote: Hi... I had a small problem when I was compiling my kernel. when I typed the make bzImage command, at the end I got an error message saying make: as86: Command not found or something like that. Do I have to install any package? I'm using the rain distribution of Storm, based on Slink. Thanks for your help... Ronald Install ``bin86'' (somwhere in the devel section, I believe.). A question to the maintainer (if he is listening): shouldn't the kernel-source package suggest|recommend bin86? MisoFrankie -- Energy equals milk chocolate square.
Re: Kernel COmpile Problems
%% Ronald Castillo [EMAIL PROTECTED] writes: rc Thanks for your help.. I'll do that. I also think kernel-source rc should recommend that. Otherwise, how would newbies like me do rc without help from this mailing list? Well... I don't mean to be snippy but they _could_ read the docs :) /usr/share/doc/kernel-source-xxx/debian.README.gz -- --- Paul D. Smith [EMAIL PROTECTED] Network Management Development Please remain calm...I may be mad, but I am a professional. --Mad Scientist --- These are my opinions---Nortel Networks takes no responsibility for them.
Kernel Compile problems
Posting from my brother, I also gave him directions that I used, so I'm not sure why this isn't working:) I am attempting to upgrade P100 system from 2.0.36 to 2.2.14. These are all the steps that I have followed: 1 - gzip -cd linux-2.2.14.tar.gz | tar xfv - 2 - cd linux 3 - make mrproper (I have attempted the same process without the make mrproper) 4 - make menuconfig 5 - Complete configuration of Linux Kernel (483KB in size) 6 - make dep 7 - make clean 8 - make zlilo 9 - make modules 10 - make modules_install Reboot. The system will reboot and get part way through the boot up seuqence before all of a sudden displaying this error message repeatedly over and over at a fast speed : kmod: failed to exec /sbin/modprobe -s -k binfmt-464c, errno = 8 request_module[binfmt-464c]: fork failed, errono 11 At the suggestion of a friend, I've updated my modprobe (using modutils_2_1_121-18.deb) with no success. I've attempted doing this via 'make zimage' and 'make zdisk' with no success. Am I missing something somewhere? The steps I've followed have been straight out of Running Linux and my notes when I did it on another PC successfully. = God, Root. What is the difference? Pitr, User Friendly __ Do You Yahoo!? Yahoo! Photos -- now, 100 FREE prints! http://photos.yahoo.com
Sound Card Config/Kernel Compile Problems
I'm having some problems with my yamaha pci sound card that I just installed. After reading the kernel documentation, I compiled in every thing it said to for the olp3-sa stuff. However, on the reboot of my system, it looks like some of the sound card parameters are wrong, and I'm not sure what they should be. Here is what the kernel said: OSS: OPL3-SA chip not found Found OPL3-SAx (YMF719) MSS: I/O port conflict Sound initialization complete Alright, the kernel found my card and called thinks it's a YMF719, although it really is a YMF724E-V. Anyway, how can I tell what the MSS i/o port should be? Here is some other information I've found while snooping around the proc dir. /proc/sound: OSS/Free:3.8s2++-971130 Load type: Driver compiled into kernel Kernel: Linux debian 2.3.1 #2 Sun May 23 23:48:52 EST 1999 i586 Config options: 0 Installed drivers: Type 10: MS Sound System Type 27: Compaq Deskpro XL Type 42: OPL3SA2 Type 43: OPL3SA2 MIDI Type 1: OPL-2/OPL-3 FM Type 5: Roland MPU-401 Type 26: MPU-401 (UART) Type 38: Yamaha OPL3-SA Type 40: OPL3-SA MIDI Type 36: SoftOSS Virtual Wave Table Card config: (Yamaha OPL3-SA at 0x530 irq 11 drq 0,3) (OPL3-SA MIDI at 0x330 irq 9 drq 0) SoftOSS Virtual Wave Table (OPL3SA2 MIDI at 0x330 irq 9 drq 0) OPL3SA2 at 0x530 irq 9 drq 0,1 (Compaq Deskpro XL at 0x530 irq 11 drq 3) (Roland MPU-401 at 0x330 irq 9 drq 0) (OPL-2/OPL-3 FM at 0x388 drq 0) Audio devices: Synth devices: 0: SoftOSS Midi devices: Timers: 0: System clock 1: SoftOSS Mixers: /proc/pci: PCI devices found: Bus 0, device 0, function 0: Host bridge: VIA Technologies VT 82C585 Apollo VP1/VPX (rev 35). Medium devsel. Fast back-to-back capable. Master Capable. Latency=32. Bus 0, device 7, function 0: ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 39). Medium devsel. Master Capable. No bursts. Bus 0, device 7, function 1: IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6). Medium devsel. Fast back-to-back capable. Master Capable. Latency=32. I/O at 0x6000 [0x6001]. Bus 0, device 8, function 0: Multimedia audio controller: Unknown vendor Unknown device (rev 5). Vendor id=1073. Device id=4. Medium devsel. IRQ 11. Master Capable. Latency=32. Min Gnt=5.Max Lat=25. Non-prefetchable 32 bit memory at 0xe200 [0xe200]. Bus 0, device 10, function 0: Ethernet controller: 3Com 3C595 100bTX (rev 0). Medium devsel. IRQ 10. Master Capable. Latency=248. Min Gnt=3.Max Lat=8. I/O at 0x6200 [0x6201]. Bus 0, device 11, function 0: VGA compatible controller: NVidia Unknown device (rev 4). Vendor id=10de. Device id=20. Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. Latency=32. Min Gnt=5.Max Lat=1. Non-prefetchable 32 bit memory at 0xe000 [0xe000]. Prefetchable 32 bit memory at 0xe100 [0xe108]. Thanks for any help you can provide. Chris
