Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!
On Saturday 10 January 2009, Dale wrote: Neil Bothwick wrote: On Fri, 9 Jan 2009 22:37:44 +, Mick wrote: Filed a bug and it was suggested to me that I try building the alsa drivers as modules. I tried it on for size and guess what, it worked! AFAIR the Gentoo ALSA docs have always recommended building as modules. And yet I have never used modules for anything except Nvidia. That has worked for me over 5 years now. What a puzzle. Same here. With three different machines I had alsa built in the kernel, less that six months or so after alsa first became part of the kernel (can't remember if I was running stable back then). -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!
On Saturday 10 January 2009 12:26:09 Mick wrote: On Saturday 10 January 2009, Dale wrote: Neil Bothwick wrote: On Fri, 9 Jan 2009 22:37:44 +, Mick wrote: Filed a bug and it was suggested to me that I try building the alsa drivers as modules. I tried it on for size and guess what, it worked! AFAIR the Gentoo ALSA docs have always recommended building as modules. And yet I have never used modules for anything except Nvidia. That has worked for me over 5 years now. What a puzzle. Same here. With three different machines I had alsa built in the kernel, less that six months or so after alsa first became part of the kernel (can't remember if I was running stable back then). My money says that if you track this down to the exact lines of code that cause the problem, you'll find something along the lines of incorrect loading order. As in, module A must load before module B, but you compiled B into the kernel. Plus no dev picked it up and nobody coded a check for it. I believe the correct technical term for this is a software bug :-) It's usually worth the effort to report a bug, the least that can happen is someone else's life is easier in the future -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!
On Saturday 10 January 2009, Alan McKinnon wrote: On Saturday 10 January 2009 12:26:09 Mick wrote: On Saturday 10 January 2009, Dale wrote: Neil Bothwick wrote: On Fri, 9 Jan 2009 22:37:44 +, Mick wrote: Filed a bug and it was suggested to me that I try building the alsa drivers as modules. I tried it on for size and guess what, it worked! AFAIR the Gentoo ALSA docs have always recommended building as modules. And yet I have never used modules for anything except Nvidia. That has worked for me over 5 years now. What a puzzle. Same here. With three different machines I had alsa built in the kernel, less that six months or so after alsa first became part of the kernel (can't remember if I was running stable back then). My money says that if you track this down to the exact lines of code that cause the problem, you'll find something along the lines of incorrect loading order. As in, module A must load before module B, but you compiled B into the kernel. Plus no dev picked it up and nobody coded a check for it. I noticed this when I built a kernel with sound as modules: CC [M] sound/core/pcm.o CC [M] sound/core/pcm_native.o sound/core/pcm_native.c: In function 'snd_pcm_fasync': sound/core/pcm_native.c:3255: warning: label 'out' defined but not used CC [M] sound/core/pcm_lib.o CC [M] sound/core/pcm_timer.o also noticed: LD [M] sound/pci/ac97/snd-ac97-codec.o LD sound/synth/built-in.o LD sound/usb/built-in.o LD vmlinux.o MODPOST vmlinux.o WARNING: modpost: Found 1 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' I believe the correct technical term for this is a software bug :-) It's usually worth the effort to report a bug, the least that can happen is someone else's life is easier in the future I have filed bug 253110 for my problem (sound) but not for the OP. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!
On Tuesday 06 January 2009, Dale wrote: Denis wrote: Looks like there are other bugs filed elsewhere on the net about E1000 not loading with the 2.6.27 kernel. Here's a curious note from https://bugs.launchpad.net/launchpad-foundations/+bug/275611 = If I remove the line of the card in /etc/udev/rules.d/70-persistent-net.rules and boot with kernel 2.6.27-4, nothing happens, it's like the card does not exist. If I modprobe e1000, and try to bring up manually eth0: eth0: error fetching interface information: Device not found If I boot back in kernel 2.6.27-3, everything works fine, /etc/udev/rules.d/70-persistent-net.rules is correctly configured, and so on. = Sounds like something's up. I will try to configure my 2.6.27 using menuconfig, but why do I get the sense that I'll just waste time doing that and end up at square one? Because if it is in the kernel, it is in the kernel. It doesn't matter if it is put there by oldconfig or menuconfig or some other config. It's either there built in, as a module or it is not there. Really simple. Well, I would have thought the same up until a week or so ago, but my conspiracy theory is that the 2.6.27-r7 gentoo kernel (don't know about the vanilla version) broke things. In my case I couldn't get my sound card to work - alsa would error out not recognising my card. I have been using oldconfig for years now, but also tried menuconfig just in case - of course it made no difference. Filed a bug and it was suggested to me that I try building the alsa drivers as modules. I tried it on for size and guess what, it worked! I have not idea why as modules it worked, while built in the kernel it did not. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!
On Fri, 9 Jan 2009 22:37:44 +, Mick wrote: Filed a bug and it was suggested to me that I try building the alsa drivers as modules. I tried it on for size and guess what, it worked! AFAIR the Gentoo ALSA docs have always recommended building as modules. -- Neil Bothwick Puns are bad, but poetry is verse... signature.asc Description: PGP signature
[gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!
Denis denis.che at gmail.com writes: I was just updating from kernel linux-2.6.24-gentoo-r7 to linux-2.6.27-gentoo-r7 using the oldconfig method, and I cannot get the new kernel to load my network. I have Intel network hardware that runs on the E1000 driver, which I generally compile right into the kernel - never had any problem. For some reason, the linux-2.6.27-gentoo-r7 kernel leaves me netless. We seem to be getting this a lot lately. I upgraded a sony laptop (intel cpu, eth etc) and had no problems with 2.6.27-gentoo-r7, right out of the box. However, I do not use 'make oldconfing'. What I do is use 'make menuconfig' and most of the meaningful options are carried forward (automatically) into the new kernel configurations. I also save both the old and new configs for comparison and trouble shooting. for Example on an amd 64 after the kernel is built: cd /usr/src make menuconfig (make choices in gui-menu) make make modules_install cp System.map /boot/System.map-2.6.27-gentoo-r7 cp arch/x86_64/boot/bzImage /boot/kernel-2.6.27-gentoo-r7 cp .config /boot/config-2.6.27-gentoo-r7 edit grub.conf The .config file saving is really worth keeping around for a few revs in case you experience problems. I know lost of folks use 'oldconfig' but I think it is problematic. (Surely, I'll get a few flames here). Particularly when your options do need to change as the kernel is routinely reorganized (sometimes) when new version numbers change I.E. (2.6.26 -- 2.6.27) for example. Using the .config files top parse line by line (when needed) is a very excellent methodology, methinks, to troubleshoot. YMMV, James
Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!
Looks like there are other bugs filed elsewhere on the net about E1000 not loading with the 2.6.27 kernel. Here's a curious note from https://bugs.launchpad.net/launchpad-foundations/+bug/275611 = If I remove the line of the card in /etc/udev/rules.d/70-persistent-net.rules and boot with kernel 2.6.27-4, nothing happens, it's like the card does not exist. If I modprobe e1000, and try to bring up manually eth0: eth0: error fetching interface information: Device not found If I boot back in kernel 2.6.27-3, everything works fine, /etc/udev/rules.d/70-persistent-net.rules is correctly configured, and so on. = Sounds like something's up. I will try to configure my 2.6.27 using menuconfig, but why do I get the sense that I'll just waste time doing that and end up at square one?
Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!
Denis wrote: Looks like there are other bugs filed elsewhere on the net about E1000 not loading with the 2.6.27 kernel. Here's a curious note from https://bugs.launchpad.net/launchpad-foundations/+bug/275611 = If I remove the line of the card in /etc/udev/rules.d/70-persistent-net.rules and boot with kernel 2.6.27-4, nothing happens, it's like the card does not exist. If I modprobe e1000, and try to bring up manually eth0: eth0: error fetching interface information: Device not found If I boot back in kernel 2.6.27-3, everything works fine, /etc/udev/rules.d/70-persistent-net.rules is correctly configured, and so on. = Sounds like something's up. I will try to configure my 2.6.27 using menuconfig, but why do I get the sense that I'll just waste time doing that and end up at square one? Because if it is in the kernel, it is in the kernel. It doesn't matter if it is put there by oldconfig or menuconfig or some other config. It's either there built in, as a module or it is not there. Really simple. Dale :-) :-)
