Fedora Hardware :: Wlan Breaks After Kernel Update
Aug 8, 2011
I run an Aspire One 522 with a Broadcom BCM4313-Wlan-Card and Fedora 15. To run the card, I had to install der broadcom-wl-Driver, as described here: [URL]... It worked okay. (Althought not perfect. It crushed everytime the whole system, when it tried to connect to a WLAN-Net, unless I first started the Windows on the computer, then shut it down and restarted Fedora. But maybe thats some strange Dual-Boot-thing.) Anyway. After I updated the Kernel to 2.6.40 it seems to be broken. I deleted the driver, reinstalled it, tried the B43-driver. But no mater what: It seems like the NetworkManager doesn't find the card at all. lsmod shows that a modul "wl" is running. And - as mentioned - I installed the Kernel and the two other packages fresh form the repositories.
I'm running Virtualbox from the Sun website (need the USB support) and it breaks after each kernel update.The problem is that I installed a lot of Ubuntu systems for transitioning windows users with Windows in virtualbox to ease the migration but I have to rerun vboxdrv setup after each kernel patch.
I have a Dell Vostro 3500, which has a Broadcom wifi card. It requires non free drivers. So far it has been working well. However, after updating the kernel (via yum update), my wifi card (it used to be eth1) is totally gone: $ ifconfig eth1 eth1: error fetching interface information: Device not found The wireless indicator does not light up either. The kernel version is
I just updated my kernel to the latest version (2.6.35-24). Now my suspend function on my Thinkpad SL510 no longer works. The system simply hangs with a solid cursor in the corner of a black screen. USB devices remain powered on, HDD keeps spinning, and all indicator lights remain lit. When this happens, the only thing I can do is hold the power button down for a hard power off.My first thought would be to troubleshoot this with dmesg, but I don't know how to record dmesg after a power off. The message buffer is reset when I reboot.
I have Lenovo T410 with NVIDIA NVS 3100m running nouveau driver/F13. When I updated to the latest kernel, the display goes blank when booting and remains blank. I can ssh to the machine, so - it appears to be an X/display issue. All else seems to be working normally, and I didn't spot anything of interest in the logs - but perhaps I don't know what to look for.
Also, it appears to be an issue in the kernel package rather than in the nouveau driver package. I can still boot the former kernel successfully - even with the new driver files.
The previous kernel version was the version of the kernel that is provided with the initial F13 install.
On my HP i7 based laptop the latest kernel 2.6.33-147 and possibly Nouveau/X.org seems to have broken suspend. ie If the laptop is suspended then when woke, the screen is dead and networking does not work and I cannot change to a different console.If I boot the previous kernel this behaviour does not occur.
I'm not sure what changed but when I recently upgraded via yum to Kernel 2.6.34 none of my uPnP or DLNA apps show up on my tvs (Sony TV and PS3). Booting an older version, i.e. 2.6.33 solves the problem with no other changes. I use MediaTomb, MythTV uPNP server and Serviio. All work fine except with the newest kernel.
I updated my fedora 12 GNOME installation. Now Compiz fusion is not working. It says Accelerated 3D support not found. Though Nvidia drivers are already installed. Now I can't even ALT+TAB between open applications.
I tried "metacity -- replace" but then windows wore a weird look with only a minimize button. No sign of maximise & close buttons.
I updated last night and after a reboot I can get the GDM login but as my desktop loads it suddenly stops and complains of an error and won't load. If I load legacy Gnome desktop with Compiz it loads but ALL the lettering and words on the interface are messed up. By this I mean the letters are upside down and the words are spelt backwards. The mouse menus also work in reverse as in the menus themselves are also upside down and the highlighting moves from bottom to top as I move down the menu. Amusing but not what I want from my computer. There is nothing in /var/log/messages or /var/log/Xorg.0.log that would indicate anything is wrong.
I sooo don't want to have to rebuild, again, because of instabilities in F15 updates.
The updated Kernel 184.108.40.206.175.fc12 (i686) broke nVidia 96xx drivers (nVidia MX-4000 card).Resulted in a quickly flashing cursor in the upper left corner, with no X startup.I removed the driver and let it rebuild using akmod. Still have the same problem.When I revert back to the previous kernel 220.127.116.11-170.fc12.i686, all is well.At this point, wonder what the chances are of this being fixed? Seems the last set of updates before EOL of a release always breaks something critical.
kernel-18.104.22.168-90.fc12 seems to break 802.11n with my intel 4965 chip on my thinkpad t61p. Anyone else seeing the same thing? iwconfig shows extremely low bit rate. dmesg doesn't show anything at all unusual.
I installed Chromium via a repo generously maintained by Tom "Spot" Callaway. Since it's his repo I thought I'd contact him, but I don't really know how - so I'm brining my issue to the forum to see if anyone has a possible solution.I've been using Tom's Chromium fine for the past couple months. After a "yum update", Flash no longer works in Chromium. It works in Firefox. If I try to play any Flash videos it's just a blank box.
After I had upgraded the system to Fedora 14, the icons for pretty much everything except for programs and plain text files in gnome theme (and every other theme that shares them) became inaccessible - they are replaced by a standard icon that appears when no other is found. Other themes, that share no icon with gnome (tango, gnome-colors, etc.), work correctly. I'm using Xfce desktop.
I've deleted icon-theme.cache, but it did nothing.
My PC has a broadcom wlan adapter. When I clean installed Fedora 15 about two weeks back, the wifi wasn't working on its own. I searched the internet and found out that installing broadcom-wl and akmod-wl would solve the problem. I tried it, and the wifi started working after that.
Wifi not working means there is no wireless option in the network settings and the wifi indicator light is off.. when wifi started working both of these got fixed
Now i did a yum update yesterday, after which my wifi has stopped working again. No use of reinstalling broadcom-wl, akmod-wl, or even kmod-wl...
Enabling kernel modesetting on my computer breaks graphics, but Xorg.log and syslog don't tell me much, because they don't log any error.
The symptoms are the following: boot goes on normally, then the KDM login screen is corrupted. On the login screen there is a big square instead of the cursor, and that square does move as I move the mouse. If I press Ctrl+Alt+F1 I'll get a black screen instead of the terminal, and from there I cannot go back to virtual terminal 7 for login. The only thing I can do is to issue sys-requests for read-only remount and reboot.
Where could I start looking for the problem? What does it seem to be related to, Xorg, kernel, radeon driver?
I just got a set of updates from Xorg11 (Index of /repositories/X11:/XOrg/openSUSE_11.1/i586) repository and now, my X doesn't come up. During update, zypper complained about xorg-x11-libxcb and it didn't get updated. On further investigation I noticed that libxcb-xlib.so.0.0.0 is missing in the new package (version 7.4-4.2. The one currently installed in 7.4-1.24).
I updated my server (Ubuntu 10.04 LTS) today and had about 23 updates in Webmin. After the update suddenly apache doesn't render php pages anymore, instead letting you download the source code for the scripts. I checked the logs and found this:
Code: Syntax error on line 1 of /etc/apache2/mods-enabled/php5.load: Cannot load /usr/lib/apache2/modules/libphp5.so into server: /usr/lib/apache2/modules/libphp5.so: cannot open shared object file: No such file or directory I tried reinstalling php5 but I can't get it to work. I also hope that this was a glitch and that updates that break stuff like this don't get through QA.
a fresh install of 10.04 all worked well installed apps as i wanted all went well... system update download completed no restart required... restarted anyway only get grub prompt... repeated this operation twice.... how do i fix getting fed up with ubuntu promising easy of use ...
I upgraded testing today on my intel laptop. During the upgrade I got the message that the new kernel would require additional firmware, see attached. Is the solution for this to install the driver from Realtek? [URL] If so, the instructions said to check if the driver was already installed, but what does the output below mean?
I have an ATI radeon HD 3400 series video card, and the open-source drivers make my computer run really hot. I tried installing FGLRX by using "Check For New Hardware Drivers", but it did not work, so I installed the ATI catalyst 10.5 package from AMD's website, and am using Xserver-xorg-core-1.7.6-2ubuntu7+backclear1 from k0ekk0ek's PPA so there is no lag when minimizing windows and such.
Everything was perfect until the 2.6.32-23 kernel update came along. I let it update, and rebooted, but the ATI driver no longer starts, even when I uninstall and reinstall it.
I am just using the 2.6.32-22 kernel for now, as the 2.6.32-23 kernel still runs hot without the ATI driver enabled. I would like to start using the new kernel at some point...
I've just installed Lucid Lynx on both my machines in the interest of sitting and waiting for the Unity/Gnome 3 storm to blow over. On the HP (see below), everything works great, and I've followed instructions online on how to upgrade to LibreOffice, upgrade the kernel to 2.6.38 using the kernel PPA, etc.
However, on the IBM, I'm using Nvidia proprietary graphics drivers. These work well on the stock kernel that 10.04 installed (2.6.32-32), but installing 2.6.38 seems to break the driver. If I install the driver first, and then the kernel on top, X stops working and I have to revert to the default, generic driver to get back in. Once there, I cannot install the driver again. The Additional Drivers dialog goes through the motions, but then drops a "systemerror: installarchives() failed" error message.
So, is there a different version of the driver I should be trying to install? I should clarify at this point I tried all three options the Additional Drivers dialog provided me, all gave the same result (version 96, version 173, and version current).
Or should I leave the kernel at 2.6.32? Is there any downside to leaving it?
yesterday I updated my squeeze amd64 on my Phenom X4 and now it is not booting anymore. Have you experienced the same problem?
After that I noticed the shutdown was not working anymore, it just restarted instead of powering down. This morning it wouldn't boot squeeze anymore, when grub starts and prints "Welcome to grub" (or something like that) the list of operating systems is not shown.
I noticed the updated also included grub and I saw it correctly detected my operating systems.
I am planning to boot knoppix soon and try to reinstall grub from chroot, but currently I am at work.
I did an update during a time when power was cycling due do a nasty snow storm, but I'm pretty sure the update was completed successfully before I lost power. What did happen though is that my BIOS setup was reset.
Now if my HP Laserjet 1020 is plugged into USB during boot all other USB devices freeze for a while. So I played with my BIOS setting for USB:
- Enabled V1.1 and V2.0 - Disabled System USB Shadowing
So now my bootup doesn't hang. But now when I actually go into Karmic I still can't print.
dmesg shows the following:
[ 205.940008] usb 1-10: new high speed USB device using ehci_hcd and address 9 [ 219.510026] hub 1-0:1.0: unable to enumerate USB device on port 10 [ 223.430008] usb 1-10: new high speed USB device using ehci_hcd and address 10 [ 223.600766] usb 1-10: configuration #1 chosen from 1 choice
I am not fully sure if this belongs more to the networking section or the software. O hope it is related to here enough.
My problem is as the topic says.
My port 80 seems to be already taken. lighttpd fails to start reporting that it cannot bind to port cause its already taken. The error message itself:
Code: "Starting web server: lighttpd2010-02-21 07:01:02: (network.c.345) can't bind to port: :: 80 Address already in use failed!"
I am not able to crack this by myself. Ihve tried investigating this by
Code: lsof -i :80 netstat -ape | grep -v unix
First doesn't show anything second anything abt port 80.
Now hints I can think of. Maybe you have more experience and ideas what I can do and where should I look for the culprit.
I am using debian (unstable) and lighttpd. I even tried rebooting; it says that the port is taken already at the boot sequence (well it starts pretty much at end anyway but the system should be clean).
It seems that it started failing after a major distro update, so maybe there are some conflicts based on ipv6/v4 or something, though I have no idea what it could be. Well my hit for that is the part of error msg "bind to port: :: 80 ". This "::" looks like ipv6 naming convention. Maybe its lighttpd internal.
My mythbuntu 10.10 system including its lirc managed remote control has been working fine.I've recently done some updates (see below) and now the remote doesn't work correctly (only some of its keys seem to work). I suspect that lirc is no longer managing the remote and now instead the remote is now being treated like a keyboard.How do I get lirc managing my remote control correctly again,Before the updates the kernel was:
Code: $ uname -a Linux pvr 2.6.35-28-generic-pae #50-Ubuntu SMP Fri Mar 18 20:43:15 UTC 2011 i686 GNU/Linux
I have just updated my Squeeze system. The update included a newer version of network-manager (and it can not be more than a few hours old). After the update all network functionality on my machine (via knetwork-manager) is broken. The GUI applet has no effect.
Hence can anyone help me: a) Downgrade network-manager by one version; b) Find out what is causing knetworkmanager to break; c) See if the problem is with knetworkmanager or network-manager.