I’ve run into problems with my laptop after kernel update to 3.7.10-1.16-desktop.
The problems that I’ve noticed:
Wireless not working.
External monitor not detected.
Laptop display resolution cannot be changed, and is set lower than the optimum resolution.
None of these problems happened with kernel 3.7.10-1.11-desktop.
The same problems occur with kernel 3.7.10-1.16-default.
I haven’t found any solution on the web, so I guess it’s not happening to other users. Any ideas of how to fix it? (Other than booting kernel 1.11, which I’m doing now of course).
I think I didn’t need to install the drivers, everything worked after installing 12.3, but I’m not sure (I’ve installed it a couple of times, and played with the Ati drivers before deciding to keep the ATI card off). To check the drivers, I’ve used lspci. Here are the results:
On 1.11:
# lspci
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Whistler XT [AMD Radeon HD 6700M Series] (rev ff)
0d:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
On 1.16:
# lspci
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Whistler XT [AMD Radeon HD 6700M Series]
0d:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
I checked the details using ‘# lspci -vv -s xxxxxx’. In all three cases, the line ‘Kernel driver in use:’ is only present on kernel 1.11, but not on 1.16.
The kernel drivers are i915, radeon and wl.
Details for the Intel graphics card:
On 1.11:
# lspci -vv -s 00:02.0
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 3388
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 50
Region 0: Memory at c0000000 (64-bit, non-prefetchable) [size=4]
Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256]
Region 4: I/O ports at 6000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: feeff00c Data: 4182
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: i915
On 1.16:
# lspci -vv -s 00:02.0
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 3388
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 16
Region 0: Memory at c0000000 (64-bit, non-prefetchable) [size=4]
Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256]
Region 4: I/O ports at 6000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: 00000000 Data: 0000
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
For the ATI graphics card (I keep it off, using vgaswitcheroo, which is not available on 1.16).
On 1.11:
# lspci -vv -s 01:00.0
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Whistler XT [AMD Radeon HD 6700M Series] (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: radeon
On 1.16:
# lspci -vv -s 01:00.0
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Whistler XT [AMD Radeon HD 6700M Series] (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 3388
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 16
Region 0: Memory at a0000000 (64-bit, prefetchable) [size=256]
Region 2: Memory at c6500000 (64-bit, non-prefetchable) [size=128]
Region 4: I/O ports at 5000 [size=256]
Expansion ROM at c6520000 [disabled] [size=128]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00
[cut since post was too long for forum!]
Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 00000000feeff00c Data: 4182
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Capabilities: [150 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap+ ChkEn-
Could you please post the output of the following in the non-working case, i.e. when booting to 3.7.10-1.16?
cat /proc/cmdline
Maybe you have the “nomodeset” option specified, which would prevent the loading of the gfxdrivers.
Maybe you have the kernel-desktop-base-3.7.10-1.16 installed? That one misses many of the drivers.
Please show the output of:
rpm -qa | grep kernel
Regarding Wireless:
The wl driver is not included in openSUSE. But there are packages on Packman.
Try to reinstall those (broadcom-wl and broadcom-wl-kmp-desktop).
Yeah, that’s because of that kernel multiversion thingy. That implies also multiple versions of the kernel modules can (and will) be installed at the same time. But AFAIK older kernel modules don’t get removed automatically (like the kernel itself), so I would call this a bug.
Anyway, that’s not related to your problem.
But it’s strange that your kernel modules don’t get loaded, while they do with 3.7.10-1.11.
I do still have that line “Kernel driver in use: radeon” with 1.16…
Could you maybe post the output of “dmesg” to SUSE Paste or similar when booting to 1.16?
Maybe there is something in there that tells us why the modules are not loaded.
Or you could try to run “depmod -a” (as root). Maybe there is something wrong with the kernel modules dependency cache…
Hi, thank you for the explanation for the multiple package versions. I guess some of those were created when I installed kernel-default, then kernel-base-default, before I managed to remove both :P.
Not that I can make sense of any of those files, but I noticed this in dmesg:
line 768: 2.215906] radeon 0000:01:00.0: Fatal error during modeset ini
line 776: 2.218301] radeon: probe of 0000:01:00.0 failed with error -12
line 1266: 24.065541] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart module.
3.125111] systemd-udevd[375]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
Not sure if that causes problems, but at least it’s not normal. (and interestingly it talks about hal, which isn’t part of openSUSE anymore)
Couly you show the output of:
The dmesg does not show anything new (all lines are old):
# dmesg | tail
23.921527] r8169 0000:07:00.0 eth0: link down
23.921532] r8169 0000:07:00.0 eth0: link down
23.921571] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
24.065541] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart module.
24.065545] DRM: Fill_in_dev failed.
25.584467] r8169 0000:07:00.0 eth0: link up
25.584488] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
25.611005] NET: Registered protocol family 17
28.282296] EXT4-fs (sda6): re-mounted. Opts: acl,user_xattr,commit=0
28.287367] EXT4-fs (sda7): re-mounted. Opts: acl,user_xattr,commit=0
For wl, it does generate a message:
# sudo /sbin/modprobe wl
FATAL: Error inserting wl (/lib/modules/3.7.10-1.16-desktop/updates/wl.ko): Invalid module format
# dmesg | tail
... same old lines...]
3354.169570] lib80211: exports duplicate symbol lib80211_crypt_delayed_deinit (owned by kernel)
Which sounds a bit nasty… :(.
Eloy
edited:
Also, in case it’s useful I checked this:
# zypper se hal
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
--+----------------------------+------------------------------------------------------+-----------
i | hal | Daemon for Collecting Hardware Information | package
That means they are already loaded.
Could you please post your Xorg log?
The easiest way would be to boot to 1.16, then reboot to 1.11 and post the file /var/log/Xorg.0.log.old, that one should then contain the info for the failed boot.
Another user of a hybrid system had a video problem lately right after the kernel update. (for him X did start, but he wasn’t able to view videos satisfactorily)
For him, disabling plymouth (the bootsplash) fixed it. Maybe you can try that as well? (Press the ‘e’ key on the boot menu, then search for the line starting with “linux” and append “plymouth.enable=0”. Then press F10 to boot)
For wl, it does generate a message:
sudo /sbin/modprobe wl
FATAL: Error inserting wl (/lib/modules/3.7.10-1.16-desktop/updates/wl.ko): Invalid module format
dmesg | tail
… same old lines…]
3354.169570] lib80211: exports duplicate symbol lib80211_crypt_delayed_deinit (owned by kernel)
Which sounds a bit nasty… :(.
Right. And that’s the reason why it doesn’t load.
You did reinstall it before, didn’t you?
Try to uninstall it, redownload it and install it again, maybe?
S | Name | Summary | Type
–±---------------------------±-----------------------------------------------------±----------
i | hal | Daemon for Collecting Hardware Information | package
You should uninstall it.
It’s not used anymore since a few releases ago.
But it isn’t even included anymore in 12.3, so your package seems to be a left-over from 12.1…
Another user of a hybrid system had a video problem lately right after the kernel update. (for him X did start, but he wasn’t able to view videos satisfactorily)
For him, disabling plymouth (the bootsplash) fixed it. Maybe you can try that as well? (Press the ‘e’ key on the boot menu, then search for the line starting with “linux” and append “plymouth.enable=0”. Then press F10 to boot)
This didn’t help, same problems.
Right. And that’s the reason why it doesn’t load.
You did reinstall it before, didn’t you?
Try to uninstall it, redownload it and install it again, maybe?
Still now working. I checked that uninstalling the broadcom removed the file wl.ko, and it was created after installation. After reboot, the wifi is still not working.
You should uninstall it.
It’s not used anymore since a few releases ago.
But it isn’t even included anymore in 12.3, so your package seems to be a left-over from 12.1…
[/quote]
I removed it, though the problems are still there. I’m not sure why I had it, I didn’t do an update from 12.1 but rather a installation of 12.3 on an empty system.
Wolfi232, I really appreciate all the effort you’re putting into this!
It seems that the problems have been solved. I decided to check all the driver versions installed, and I noticed that I had this package: compat-drivers-kmp-desktop from repository home:MargueriteSu.
Since I only added that repo to install KingsoftOffice, it made no sense to me to have drivers from it. So I crossed fingers and tried removing the package compat-drivers-kmp-desktop. After a reboot, all seems well, both wifi and displays.
I really don’t recall installing that package!
Wolfi323, thank you very much for your help, and I apologize for not noticing those drivers were installed…
compat-drivers contains kernel modules for Ethernet/Wireless/Bluetooth
backported from latest kernel.
It supports all supported kernel releases, currently 2.6.24 - 3.6,
and depreciates older compat-wireless project unless you’re on a
unsupported kernel.
So no wonder that you had problems, that package contains and overrides radeon, i915, …
Strange that it did work with the 3.7.10-1.10 kernel though.:\
And I have no idea why wl was also affected, but well, doesn’t really matter anymore, does it?
When I add a non-standard repo to install something, I disable that repo as soon as I have completed the install I wanted. That reduces the risk of accidentally picking up unwanted libraries, drivers, etc.
Well, since some users kept pinging me for this link and thought I should be responsible for this, or even had a wild guess that I should “fix” this, I think it might be good to explain some stuff here.
The package description leads misunderstanding, it was my fault.
This package is the backported kernel modules frome latest “next” kernel. it supports all supported kernels on kernel.org, starting from 3.7, and some unsupported kernel eg 2.6.32 to 3.6.
So it should be fine for 3.7.16.
But, as it backports Bluetooth/Wireless/Ethernet drivers and experimental Video drivers, you may run into problems with the Video part. It’s not a packaging bug (my fault), it is upstream kernel bug of the version it was backported. eg: if you get black screen from here, same thing will happen with 3.10 RC1 vanilla kernel. So use kernel.org mailing list for such bug report.
A temporary workaround may be: delete modules you didn’t need from /lib/modules/your kernel version/update directory.
Why it was in my repository?
Because I am the original packager for that package in driver:wireless.
Why it was automatically installed to my system?
because it declaims to “enhance” the specific kernel it was built against. That’s exactly what this package do. So no fault here.
It’s the user’s carelessness on reviewing automatic change that leads to the problem. So indeed it’s beyond my capacity to fix any user’s mind except mine.
