Bug 555608 - no networkcards available after boot (cards disabled)
Summary: no networkcards available after boot (cards disabled)
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.2
: P5 - None : Major with 13 votes (vote)
Target Milestone: ---
Assignee: Brandon Philips
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-15 08:52 UTC by m s
Modified: 2010-03-29 19:35 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Collection of network data for wired network (7.37 KB, text/plain)
2009-11-16 19:28 UTC, m s
Details
Collection of network data for wireless network (ifconfig lspci hwinfo...) (18.65 KB, text/plain)
2009-11-16 19:30 UTC, m s
Details
dmesg output (56.57 KB, text/plain)
2009-11-16 19:30 UTC, m s
Details

Note You need to log in before you can comment on or make changes to this bug.
Description m s 2009-11-15 08:52:41 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4

1. install openSuse 11.2 (full install, no upgrade)
2. boot system

Then no network devices will be shown with ifconfig -a.

English description can be found under:
http://forums.opensuse.org/network-internet/425463-no-network-cards-available-suse-11-2-11-1-fine.html

German description can be found under:
http://www.linuxforen.de/forums/showthread.php?t=264727

Workaround:
Add the follwing kernel options: acpi=off apm=on

Reproducible: Always

Steps to Reproduce:
1. install openSuse 11.2 (full install, no upgrade)
2. boot system
3. run dmesg ifconfig etc... to check
Comment 1 m s 2009-11-16 19:24:35 UTC
Used Hardware: Acer Extensa 7630EZ
Comment 2 m s 2009-11-16 19:28:46 UTC
Created attachment 327754 [details]
Collection of network data for wired network

Created with the script from:
http://www.linux-tips-and-tricks.de/index.php/Netzwerktoolsrepository/View-category.html?ascdesc=DESC&orderby=dmdatecounter
Comment 3 m s 2009-11-16 19:30:17 UTC
Created attachment 327755 [details]
Collection of network data for wireless network (ifconfig lspci hwinfo...)

Created with the script from:
http://www.linux-tips-and-tricks.de/index.php/Netzwerktoolsrepository/View-category.html?ascdesc=DESC&orderby=dmdatecounter
Comment 4 m s 2009-11-16 19:30:41 UTC
Created attachment 327756 [details]
dmesg output
Comment 5 Stephan Binner 2009-11-17 04:53:57 UTC
Please read http://en.opensuse.org/Bugs/Definitions#Bug_Priorities
Comment 6 Greg Kroah-Hartman 2009-11-21 14:48:45 UTC
only the developer should adjust the priority.
Comment 7 Jiri Slaby 2009-11-24 22:58:02 UTC
It looks like a borked BIOS. Could you try to update your BIOS?
Comment 8 Jiri Slaby 2009-11-24 23:48:09 UTC
Just for the record, ath9k fails because ath_attach fails. All other fail paths in ->probe prints out a reason (except pci_enable_device, but we see setting latency in dmesg).

It may be worth trying pci=noacpi instead of whole acpi=off, if it fixes anything (as it shouldn't here). And I will build a kernel with more verbose ath9k on errors (I just wonder why there are only debug printks in there) to see what's happening.
Comment 9 Jiri Slaby 2009-11-25 08:52:43 UTC
Could you try the kernel from:
http://labs.suse.cz/jslaby/bug-555608/
to see what happens with ath9k?
Comment 10 m s 2009-11-25 17:48:20 UTC
(In reply to comment #8)
> It may be worth trying pci=noacpi instead of whole acpi=off, if it fixes
> anything (as it shouldn't here).
pci=noacpi doesn't help.
Comment 11 m s 2009-11-25 17:50:17 UTC
(In reply to comment #7)
> It looks like a borked BIOS. Could you try to update your BIOS?
I dont't think that is the problem, because with openSuse 11.0 everything was working. Except that the LED that indicates WLAN activity wasn't blinking (but who cares?). A change in the OS shouldn't require a BIOS update?!
Comment 12 m s 2009-11-25 18:12:45 UTC
(In reply to comment #9)
> Could you try the kernel from:
> http://labs.suse.cz/jslaby/bug-555608/
> to see what happens with ath9k?

I installed the smaller rpm kernel-desktop-base-2.6.31.6-0.1.x86_64.rpm. But I couldn't install kernel-desktop-2.6.31.6-0.1.x86_64.rpm because of broken dependencies. See http://fischlii.gmxhome.de/11.2/snapshot1.png

After I tried to boot the system with the new installed kernel (without the bigger rpm) I ran to the following problem. The kernel doesn't know ext4. See http://fischlii.gmxhome.de/11.2/DSC01806.JPG

Sorry its a poor camera. But the basic error message is: 
mount: unknown filesystem type 'ext4'
could not mount root filesystem ...
Comment 13 Jeff Mahoney 2009-11-25 18:42:02 UTC
Instead of installing it as an upgrade, just install it (rpm -i). The dependency problem isn't coming from installing the new kernel - it's coming from trying to remove the old one, where a KMP depends on it.

You'll need to install the full kernel-desktop. kernel-desktop-base is only for use with virtualized systems where the majority of drivers just aren't necessary.
Comment 14 m s 2009-11-25 19:24:39 UTC
After installing the new kernel packages everything works fine with the openSuse default kernel options (vga=something)/boot settings. So the new kernel looks like a fix to me. Do you need more information? Or is it a fix by a "lucky coincidence"?
Comment 15 Brandon Philips 2009-12-04 01:20:08 UTC
(In reply to comment #14)
> After installing the new kernel packages everything works fine with the
> openSuse default kernel options (vga=something)/boot settings. So the new
> kernel looks like a fix to me. Do you need more information? Or is it a fix by
> a "lucky coincidence"?

Which Kernel fixed it? Was it Jiri's Kernel from Comment #9?
Comment 16 m s 2009-12-04 05:41:34 UTC
(In reply to comment #15)
> Which Kernel fixed it? Was it Jiri's Kernel from Comment #9?

Yes. The kernel was from http://labs.suse.cz/jslaby/bug-555608/ and fixed both network devices, which had problems before.
Comment 17 Patrick Smart 2009-12-08 23:07:48 UTC
(In reply to comment #9)
> Could you try the kernel from:
> http://labs.suse.cz/jslaby/bug-555608/
> to see what happens with ath9k?

Unfortunately, I can't try this kernel due to Bug #543076. Can you create a non-desktop kernel?

Patrick
Comment 18 Patrick Smart 2009-12-08 23:17:05 UTC
I don't see any question to the reporter without a response, I suppose he just forgot to clear the needinfo flag.
Comment 19 Jiri Slaby 2009-12-09 15:45:44 UTC
(In reply to comment #17)
> Unfortunately, I can't try this kernel due to Bug #543076. Can you create a
> non-desktop kernel?

Please try a kernel from
ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.2/
instead.
Comment 20 m s 2009-12-15 06:21:56 UTC
(In reply to comment #19)
> (In reply to comment #17)
> > Unfortunately, I can't try this kernel due to Bug #543076. Can you create a
> > non-desktop kernel?
> 
> Please try a kernel from
> ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.2/
> instead.

Well, I hope this is not up to me - because  I don't like changing kernels too often. And Patrick Smart doesn't seem to respond.
Comment 21 Patrick Smart 2009-12-15 22:51:54 UTC
I am the info provider and will do so eventually. Right now I am running kernel-desktop-2.6.31.7-0.0.0.8.a22d080.x86_64. I will come back to this in a few days when I can attest this kernel works fine for me. This network issue was not systematic AFAIK.

Due to Bug #543076, you should indeed be careful with updates as I had made my system unbootable this way.
Comment 22 Patrick Smart 2009-12-17 21:56:33 UTC
Unfortunately, I had the case again of having a freshly booted system with no network. I did an "rcnetwork restart" and had it all normal. I suspect it has nothing to do with it but nfs ans nfsserver also fail to start.
Comment 23 Brandon Philips 2010-03-03 18:52:39 UTC
(In reply to comment #22)
> Unfortunately, I had the case again of having a freshly booted system with no
> network. I did an "rcnetwork restart" and had it all normal. I suspect it has
> nothing to do with it but nfs ans nfsserver also fail to start.

What Kernel are you running. Did you test ftp://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.2/ as suggested in Comment #19?

> (In reply to comment #19)
> Well, I hope this is not up to me - because  I don't like changing kernels too
> often. And Patrick Smart doesn't seem to respond.

We can't really help if you can't test Kernels.(In reply to comment #20)

Thanks.
Comment 24 Patrick Smart 2010-03-29 12:12:22 UTC
I haven't seen this issue in a long while. I have indeed upgraded the kernel since my last update. I presume this should be marked as fixed. Up to the reporter...
Comment 25 m s 2010-03-29 19:35:46 UTC
So I'll close that - as it is fixed -for me- long time ago by a new kernel.