[gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Denis]

Hello and Happy New Year!

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.  I try to start the
"net.eth0", and it says 'please verify your hardware driver' or
something to that extent.  Has anyone else encountered this problem?

I just compiled linux-2.6.25-gentoo-r9, and everything runs fine - no
network problems at all!

Is this a known problem, or have I run into a freak case of bad luck?

Cheers,
Denis

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Nicolas Sebrecht]

On Mon, Jan 05, 2009 at 08:56:28PM -0500, Denis wrote:

> Hello and Happy New Year!

Happy new year to every members here.

> 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.  

The use of 'oldconfig' when upgrading from a previous .z kernel (as in
2.6.z) is a bad idea. There are too much changes between such upgrades.
Please retry a compilation from scratch.

>                                     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.  I try to start the
> "net.eth0", and it says 'please verify your hardware driver' or
> something to that extent.  Has anyone else encountered this problem?

If compiled as a module, check if it is loaded. Then, check if the
driver is working using the 'ifconfig -a' command (upgrade
sys-apps/net-tools if avaible).
If the module can't load or if it isn't working when loaded, post your
'dmesg' and 'emerge --info' outputs.

> I just compiled linux-2.6.25-gentoo-r9, and everything runs fine - no
> network problems at all!

Ok. What about the 2.6.28 series ?

-- 
Nicolas Sebrecht

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Francisco Ares]

[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]

On Tue, Jan 6, 2009 at 12:25 AM, Nicolas Sebrecht <nicolas.s-dev@laposte.net
> wrote:

>
> On Mon, Jan 05, 2009 at 08:56:28PM -0500, Denis wrote:
>
> > Hello and Happy New Year!
>
> Happy new year to every members here.
>
> > 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.
>
> The use of 'oldconfig' when upgrading from a previous .z kernel (as in
> 2.6.z) is a bad idea. There are too much changes between such upgrades.
> Please retry a compilation from scratch.
>
> >                                     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.  I try to start the
> > "net.eth0", and it says 'please verify your hardware driver' or
> > something to that extent.  Has anyone else encountered this problem?
>
> If compiled as a module, check if it is loaded. Then, check if the
> driver is working using the 'ifconfig -a' command (upgrade
> sys-apps/net-tools if avaible).
> If the module can't load or if it isn't working when loaded, post your
> 'dmesg' and 'emerge --info' outputs.
>
> > I just compiled linux-2.6.25-gentoo-r9, and everything runs fine - no
> > network problems at all!
>
> Ok. What about the 2.6.28 series ?
>
> --
> Nicolas Sebrecht
>
>
>
I always do a genkernel --menuconfig  (or --xconfig) --splash --install all
and then wander here and there in the menu tree.

lspci -k and lsmod are good companions.

Have an excellent new year!
Francisco

-- 
"If you have an apple and I have an apple and we exchange apples then you
and I will still each have one apple. But if you have an idea and I have one
idea and we exchange these ideas, then each of us will have two ideas." -
George Bernard Shaw

[-- Attachment #2: Type: text/html, Size: 2662 bytes --]

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Nicolas Sebrecht]

On Tue, Jan 06, 2009 at 12:59:13AM -0200, Francisco Ares wrote:

<snip>

Avoid the HTML format in your mail, please.
Also, learn to quote.

-- 
Nicolas Sebrecht

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 152 bytes --]

Am Dienstag, 6. Januar 2009 02:56:28 schrieb Denis:
> I have Intel network hardware that
> runs on the E1000 driver

Did you try e1000e?

Bye...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

On Tue, 6 Jan 2009 03:25:44 +0100, Nicolas Sebrecht wrote:

> The use of 'oldconfig' when upgrading from a previous .z kernel (as in
> 2.6.z) is a bad idea. There are too much changes between such upgrades.
> Please retry a compilation from scratch

That's just FUD. oldconfig is intended to be used on minor version
upgrades and is generally highly reliable. It can
cause problems when configuration options move, but manual configuration
each time suffers from the same thing and wastes a lot of time each
time you upgrade. As long as you read the help text when working
through oldconfig, you shouldn't have problems.

To the OP, I'd try building the driver as a module, then you can look for
messages when modprobing it with various options.


-- 
Neil Bothwick

Reality is an obstacle to hallucination.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Nicolas Sebrecht]

On Tue, Jan 06, 2009 at 07:54:30AM +0000, Neil Bothwick wrote:

> That's just FUD. 

You should tell it to the documentation team.

-- 
Nicolas Sebrecht

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Francisco Ares]

On Tue, Jan 6, 2009 at 1:44 AM, Nicolas Sebrecht
<nicolas.s-dev@laposte.net> wrote:
>
> On Tue, Jan 06, 2009 at 12:59:13AM -0200, Francisco Ares wrote:
>
> <snip>
>
> Avoid the HTML format in your mail, please.
> Also, learn to quote.

sorry about that

>
> --
> Nicolas Sebrecht
>
>

Francisco

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 382 bytes --]

On Tue, 6 Jan 2009 09:34:31 +0100, Nicolas Sebrecht wrote:

> > That's just FUD.   
> 
> You should tell it to the documentation team.

The last time I looked at the docs for this, which was a while ago,
they recommended against using it for major version updates, which makes
perfect sense.


-- 
Neil Bothwick

Artificial Intelligence usually beats real stupidity.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Peter Humphrey]

On Tuesday 06 January 2009 11:42:58 Neil Bothwick wrote:
> On Tue, 6 Jan 2009 09:34:31 +0100, Nicolas Sebrecht wrote:
> > > That's just FUD.
> >
> > You should tell it to the documentation team.
>
> The last time I looked at the docs for this, which was a while ago,
> they recommended against using it for major version updates, which makes
> perfect sense.

I've seen a dev complain that most of the problems he's had to deal with 
have been due to oldconfig, so I don't use it at all. I copy the config in 
from the previous tree, then I run menuconfig and search for lines ending 
in [NEW] or [DEPRECATED]. This is far quicker and less error-prone than 
going through the entire set of options.

-- 
Rgds
Peter

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 498 bytes --]

On Tue, 6 Jan 2009 12:13:05 +0000, Peter Humphrey wrote:

> I've seen a dev complain that most of the problems he's had to deal
> with have been due to oldconfig, so I don't use it at all. I copy the
> config in from the previous tree, then I run menuconfig and search for
> lines ending in [NEW] or [DEPRECATED].

How is this different from using make oldconfig, apart from the UI?


-- 
Neil Bothwick

Approx. 1 in 36000 people will break a leg within 3 weeks of reading this
post

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Peter Humphrey]

On Tuesday 06 January 2009 12:45:15 Neil Bothwick wrote:
> On Tue, 6 Jan 2009 12:13:05 +0000, Peter Humphrey wrote:
> > I've seen a dev complain that most of the problems he's had to deal
> > with have been due to oldconfig, so I don't use it at all. I copy the
> > config in from the previous tree, then I run menuconfig and search for
> > lines ending in [NEW] or [DEPRECATED].
>
> How is this different from using make oldconfig, apart from the UI?

I don't know; I just pick up my clues where I can. Perhaps there's a 
difference in handling of unchanged or default values.

On the other hand, maybe the dev was complaining about the way people use 
the two methods rather than the way they operate, in which case I can be a 
bit less paranoid. As I don't have the time to investigate how Make works, 
I propose to continue to take the path of least resistance.

-- 
Rgds
Peter

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]

On Tue, 6 Jan 2009 15:06:28 +0000, Peter Humphrey wrote:

> > > I've seen a dev complain that most of the problems he's had to deal
> > > with have been due to oldconfig, so I don't use it at all. I copy
> > > the config in from the previous tree, then I run menuconfig and
> > > search for lines ending in [NEW] or [DEPRECATED].  
> >
> > How is this different from using make oldconfig, apart from the UI?  
> 
> I don't know; I just pick up my clues where I can. Perhaps there's a 
> difference in handling of unchanged or default values.

Unchanged values are just that. When a config option is new, make
oldconfig prompts for a choice,with a default option (the same default
that menuconfig uses). The only real difference is that with menuconfig
you have to go through the options, looking for those marked NEW (and
risking missing an important one) while oldconfig presents them to you in
sequence,asking for your choice on each one.

I have boxes running 2.6.28 on which I have used oldconfig on every
change since switching them from2.4 to 2.6.


-- 
Neil Bothwick

You know it's going to be a bad day when you forget your new password.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!

[James]

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!

[Denis]

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] kernel linux-2.6.27-gentoo-r7 won't load network!

[Dale]

Neil Bothwick wrote:
> On Tue, 6 Jan 2009 15:06:28 +0000, Peter Humphrey wrote:
>
>   
>>>> I've seen a dev complain that most of the problems he's had to deal
>>>> with have been due to oldconfig, so I don't use it at all. I copy
>>>> the config in from the previous tree, then I run menuconfig and
>>>> search for lines ending in [NEW] or [DEPRECATED].  
>>>>         
>>> How is this different from using make oldconfig, apart from the UI?  
>>>       
>> I don't know; I just pick up my clues where I can. Perhaps there's a 
>> difference in handling of unchanged or default values.
>>     
>
> Unchanged values are just that. When a config option is new, make
> oldconfig prompts for a choice,with a default option (the same default
> that menuconfig uses). The only real difference is that with menuconfig
> you have to go through the options, looking for those marked NEW (and
> risking missing an important one) while oldconfig presents them to you in
> sequence,asking for your choice on each one.
>
> I have boxes running 2.6.28 on which I have used oldconfig on every
> change since switching them from2.4 to 2.6.
>
>
>   

I been using oldconfig a long time too and never had trouble with it. 
It basically will make the same kernel but with bug/security fixes.  I
even copied the config over then forgot to run oldconfig and it compiled
and booted just fine. 

I think FUD was the right term for this one.  Major versions, make it by
hand; incremental upgrades works fine with oldconfig.

Dale

:-)  :-) 

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Denis]

I'm doubtful that using oldconfig would make a driver not work because
I have done it this way for a while, going between various 2.6.x
versions, like 2.6.21 to 2.6.24...  And there was never an issue.
Maybe the E1000 driver somehow got messed up in this particular
version of the kernel.

Now, that e1000e driver someone mentioned - how is it different from
the e1000 driver, and does the kernel float two versions, or it
depends on which kernel it is?

Thanks,
Denis

Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!

[Dale]

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

:-)  :-) 

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Norberto Bensa]

On Tuesday January 6 2009 20:37:31 Denis wrote:
> I'm doubtful that using oldconfig would make a driver not work because

Unless the "driver" (module) changed name ;)  (ata->pata/sata anyone?)

Anyway, I've always used oldconfig except when moving from 2.4 to 2.6

Regards,
Norberto

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Alan McKinnon]

On Wednesday 07 January 2009 00:37:31 Denis wrote:
> I'm doubtful that using oldconfig would make a driver not work because
> I have done it this way for a while, going between various 2.6.x
> versions, like 2.6.21 to 2.6.24...  And there was never an issue.
> Maybe the E1000 driver somehow got messed up in this particular
> version of the kernel.
>
> Now, that e1000e driver someone mentioned - how is it different from
> the e1000 driver, and does the kernel float two versions, or it
> depends on which kernel it is?

e1000e breaks the hardware
e1000 does not break the hardware
Or maybe it's the other way round

Anyway, two different drivers for the same hardware, the broken one was 
removed from the sources till it gets fixed. You can always build both 
drivers in a case like this but obviously you can only use one of them at a 
time



-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Andreas Niederl]

Alan McKinnon wrote:
> On Wednesday 07 January 2009 00:37:31 Denis wrote:
>> I'm doubtful that using oldconfig would make a driver not work because
>> I have done it this way for a while, going between various 2.6.x
>> versions, like 2.6.21 to 2.6.24...  And there was never an issue.
>> Maybe the E1000 driver somehow got messed up in this particular
>> version of the kernel.
>>
>> Now, that e1000e driver someone mentioned - how is it different from
>> the e1000 driver, and does the kernel float two versions, or it
>> depends on which kernel it is?
> 
> e1000e breaks the hardware
> e1000 does not break the hardware
> Or maybe it's the other way round
> 
> Anyway, two different drivers for the same hardware, the broken one was 
> removed from the sources till it gets fixed. You can always build both 
> drivers in a case like this but obviously you can only use one of them at a 
> time

Actually, there was a bug with Ftrace overwriting the flash ROM of a NIC
(which shouldn't have been mapped RW anyway) with e1000e in certain
cases. IIRC this was only present in the 2.6.27 release candidates and
got "fixed" by mapping it read-only for the final release.
2.6.28 then had the fix for the Ftrace bug.


Regards,
Andi

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Dirk Heinrichs]

[-- Attachment #1: Type: text/plain, Size: 301 bytes --]

Am Mittwoch, 7. Januar 2009 07:26:44 schrieb Alan McKinnon:
> e1000e breaks the hardware
> e1000 does not break the hardware
> Or maybe it's the other way round

Nope. None does. That bug was only present in one or two .27 release 
candidates and has been fixed since weeks.

Bye...

	Dirk

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] kernel linux-2.6.27-gentoo-r7 won't load network!

[Eric Martin]

Neil Bothwick wrote:
> On Tue, 6 Jan 2009 15:06:28 +0000, Peter Humphrey wrote:
>
>   
>>>> I've seen a dev complain that most of the problems he's had to deal
>>>> with have been due to oldconfig, so I don't use it at all. I copy
>>>> the config in from the previous tree, then I run menuconfig and
>>>> search for lines ending in [NEW] or [DEPRECATED].  
>>>>         
>>> How is this different from using make oldconfig, apart from the UI?  
>>>       
>> I don't know; I just pick up my clues where I can. Perhaps there's a 
>> difference in handling of unchanged or default values.
>>     
>
> Unchanged values are just that. When a config option is new, make
> oldconfig prompts for a choice,with a default option (the same default
> that menuconfig uses). The only real difference is that with menuconfig
> you have to go through the options, looking for those marked NEW (and
> risking missing an important one) while oldconfig presents them to you in
> sequence,asking for your choice on each one.
>
> I have boxes running 2.6.28 on which I have used oldconfig on every
> change since switching them from2.4 to 2.6
Amen to that.  I've been doing that since 2.4 also and I'm not having 
any problems.  Any other way is just creating unnecessary work.

Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 338 bytes --]

On Fri, 9 Jan 2009 22:37:44 +0000, 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...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!

[Dale]

Neil Bothwick wrote:
> On Fri, 9 Jan 2009 22:37:44 +0000, 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.

Dale

:-)  :-)

Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!

[Mick]

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

On Saturday 10 January 2009, Dale wrote:
> Neil Bothwick wrote:
> > On Fri, 9 Jan 2009 22:37:44 +0000, 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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-user] Re: kernel linux-2.6.27-gentoo-r7 won't load network!

[Alan McKinnon]

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 +0000, 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!

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2094 bytes --]

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 +0000, 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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]