WiFi permanently disappeared after booting test kernel
by Mike Fleetwood
Hi,
On my netbook I booted a test kernel 3.8.0-rc4+ I compiled. Now after
booting back into my regular Fedora kernel 3.6.11-5.fc17.i686.PAE my
wifi network device remains permanently disappeared. No wifi networks
displayed in Network Manager gui. Also the Network Manager syslog
messages make it look like the device has completely disappeared.
Suggestions for restoring wifi welcome.
Thanks
Mike
Fragment of Network Manager syslog messages when working before
--8<--
Jan 18 23:01:53 edge NetworkManager[479]: <info> monitoring kernel
firmware directory '/lib/firmware'.
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill2: found WiFi
radio killswitch (at
/sys/devices/pci0000:00/0000:00:1c.3/0000:01:00.0/ieee80211/phy0/rfkill2)
(driver ath9k)
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill0: found WiFi
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill0)
(platform driver eeepc)
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill4: found WWAN
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill4)
(platform driver eeepc)
Jan 18 23:01:53 edge NetworkManager[479]: <info> WiFi enabled by radio
killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> WWAN enabled by radio
killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> WiMAX enabled by
radio killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> Networking is enabled
by state file
...
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): using
nl80211 for WiFi device control
Jan 18 23:01:53 edge NetworkManager[479]: <warn> (wlan0): driver
supports Access Point (AP) mode
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): new 802.11
WiFi device (driver: 'ath9k' ifindex: 3)
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): exported as
/org/freedesktop/NetworkManager/Devices/1
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): now managed
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): device state
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): bringing up device.
...
Jan 18 23:01:59 edge NetworkManager[479]: <info> Activation (wlan0)
successful, device activated.
Jan 18 23:01:59 edge NetworkManager[479]: <info> Activation (wlan0)
Stage 5 of 5 (IPv4 Commit) complete.
Fragment of Network Manager syslog messages when broken after
--8<--
Jan 28 18:43:26 edge NetworkManager[466]: <info> monitoring kernel
firmware directory '/lib/firmware'.
Jan 28 18:43:26 edge NetworkManager[466]: <info> rfkill0: found WiFi
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill0)
(platform driver eeepc)
Jan 28 18:43:26 edge NetworkManager[466]: <info> rfkill2: found WWAN
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill2)
(platform driver eeepc)
Jan 28 18:43:26 edge NetworkManager[466]: <info> WiFi disabled by
radio killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> WWAN enabled by radio
killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> WiMAX enabled by
radio killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> Networking is enabled
by state file
No (wlan0) related NetworkManager syslog messages afterwards at all.
9 years, 8 months
losing WiFi Access - prompted for password
by SternData
F18...
Over the last few days, I'm getting prompted to re-enter my password for
my WiFi network. It's not the router because no other device on the
network seems to be having problems.
Potential changes on my system include
May 07 21:39:32 Updated: 1:wpa_supplicant-1.1-1.fc18.x86_64
May 25 15:33:44 Installed: kernel-3.9.3-201.fc18.x86_64
May 27 08:06:42 Updated:
1:NetworkManager-glib-0.9.8.1-3.git20130514.fc18.x86_64
May 27 08:06:47 Updated: 1:NetworkManager-0.9.8.1-3.git20130514.fc18.x86_64
May 27 08:06:53 Updated:
network-manager-applet-0.9.8.1-4.git20130514.fc18.x86_64
Given that this has really started the day before yesterday, I suspect
it has something to do with the NetworkManager update. Is anyone else
having this problem?
(Please -- do not tell me to "dump the evil NetworkManager". I'm trying
to solve a problem here, not make some stand against the tide. Thanks.)
--
-- Steve
9 years, 10 months
138a:0018 Validity Sensors will not work
by Jerome Yanga
Please help me get my fingerprint sensor to work.
# cat /etc/redhat-release
Fedora release 18 (Spherical Cow)
# uname -a
Linux laptop1 3.9.6-200.fc18.x86_64 #1 SMP Thu Jun 13 18:56:55 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
# yum list installed | grep fprint
fprint_demo.x86_64 0.4-10.fc18.1 @fedora
fprintd.x86_64 0.4.1-4.fc18
@koji-override-1/$releasever
fprintd-pam.x86_64 0.4.1-4.fc18
@koji-override-1/$releasever
libfprint.x86_64 0.5.0-2.fc18 installed
libfprint-devel.x86_64 0.5.0-2.fc18 installed
Thank you in advance.
j
10 years, 4 months
mouse track-pad
by Richard Vickery
Hi Gang:
The mouse doesn't work work on new Acer; any ideas on how I can find it?
Apparently Fedora knows that the pad exists, but it is rendered useless
right now.
Thanks,
Richard
10 years, 5 months
KDE without gnome-shell?
by Oliver Ruebenacker
Hello,
Can you run KDE on Fedora 19 without gnome-shell?
Thanks!
Best,
Oliver
--
Oliver Ruebenacker
IT Project Lead at PanGenX (http://www.pangenx.com)
Be always grateful, but never satisfied.
10 years, 5 months
twm: icons size
by Hiisi
Dear list!
I'm using twm on Fedora 19. Everything is perfect except that I don't like
the size of icons on desktop. I.e. when application is minimized a tab
appeared on the screen. And for most applications it look awful:
http://img19.imageshack.us/img19/7089/77bf.png
icons are too big :-(
How do I change the size of icons?
TIA
--
Hiisi.
Registered Linux User #487982. Be counted at: https://linuxcounter.net/
--
Spandex is a privilege, not a right.
10 years, 5 months
hibernate/suspend immediately resumes
by Greg Woods
Judging from the results of Google searches about this, this is a
problem that has been around for a while, but I have not found a
solution that works for my case. Most of the hits were on postings in
the Ubuntu forums, and regarding pretty old versions of Ubuntu at that
(which means they don't account for systemd, grub2, etc. if any of that
comes into play). So I thought I would ask here on the Fedora list.
This is for a brand-new machine with an ASUS Z-87 motherboard, Intel i5
Haswell processor (4 core, 64-bit) and fully updated F19 (64-bit).
The problem is that when doing a suspend or hibernate, the process
completes, but almost immediately the system resumes again. In the case
of hibernation, I have tried forcibly powering it off when the resume
starts. In that case, when I power it on again, the hibernated image
loads, but then the system hangs and never completes the resume.
Just for completeness, the system also has a Windows 7 64-bit installed
OS, and that one is able to suspend and hibernate just fine, which would
seem to rule out hardware issues.
The solutions I found for Linux were of two types: disabling ACPI
wakeups (using "acpitool -W") and "unbinding" USB drivers (not sure what
that even means). I've tried both approaches with no success.
More details: I spent an entire evening last night fiddling with this
with no success, so I really REALLY don't want anyone coming back and
saying I haven't done my homework, or do some Google searches you idiot,
etc. (unless you can point me to the exact Google search I need to do).
I have done these things to the best of my ability already.
# acpitool -w
Device S-state Status Sysfs node
---------------------------------------
1. UAR1 S4 *disabled pnp:00:0a
2. RP01 S4 *disabled pci:0000:00:1c.0
3. PXSX S4 *disabled
4. RP03 S4 *disabled pci:0000:00:1c.2
5. PXSX S4 *enabled pci:0000:03:00.0
6. RP04 S4 *disabled pci:0000:00:1c.3
7. PXSX S4 *disabled pci:0000:04:00.0
8. RP08 S4 *disabled pci:0000:00:1c.7
9. PXSX S4 *disabled pci:0000:08:00.0
10. RP07 S4 *disabled pci:0000:00:1c.6
11. PXSX S4 *disabled pci:0000:06:00.0
12. GLAN S4 *disabled
13. EHC1 S4 *enabled pci:0000:00:1d.0
14. EHC2 S4 *enabled pci:0000:00:1a.0
15. XHC S4 *enabled pci:0000:00:14.0
16. HDEF S4 *disabled pci:0000:00:1b.0
17. PEG0 S4 *disabled pci:0000:00:01.0
18. PEGP S4 *disabled pci:0000:01:00.0
19. PEG1 S4 *disabled
20. PEG2 S4 *disabled
So I tried disabling 5, 13, 14, and 15 ("acpitool -w 5" and so forth). 5
can't be disabled (at least, it still shows as "enabled" after running
"acpitool -W 5), so I assume that's the power button. The others show up
as "disabled" after doing this, but hibernate/suspend still resumes
immediately even after doing this.
"Unbinding" drivers is done with a shell script that looks like this:
==============================================================================
function unbind_usb {
for driver in ehci-pci firewire_ohci ohci-pci uhci_hcd xhci_hcd;
do
cd "/sys/bus/pci/drivers/${driver}";
ids=$(ls | grep :);
echo $ids > /var/tmp/DISABLED_$driver;
for id in $ids; do
echo "Unbinding $id";
echo -n "$id" > unbind;
disabled="$disabled $id";
done;
done;
}
function bind_usb {
for driver in ehci-pci firewire_ohci ohci-pci uhci_hcd xhci_hcd;
do
cd "/sys/bus/pci/drivers/${driver}";
for id in $(cat /var/tmp/DISABLED_$driver); do
echo "Binding $id";
echo -n "$id" > bind;
done;
rm /var/tmp/DISABLED_$driver;
done;
}
A script that calls unbind_usb on hibernate/suspend and calls bind_usb
on thaw/resume is placed in /usr/lib64/pm-utils/sleep.d/S50usbbind .
This does not work either.
The most aggravating thing is that I have another machine built from the
same hardware, and suspend/hibernate works fine on that one, without any
of this being necessary. So it may well come down to determining exactly
which drivers need to be unbound. The machine that doesn't work does
have a couple of additional cards in it (that provide extra USB ports
and some Firewire ports) which suggests the driver for one of those
cards is causing the problem. The original script wanted to unbind
everything that had *hci* in the name, but I found that if "ahci" was
unbound, then I could no longer access anything on the disk, and I had
to push the reset button to recover; maybe that is the hard disk driver.
So I can't just try unbinding everything.
Anything that can point me in the right direction here is greatly
appreciated.
--Greg
10 years, 5 months
"Oh no! Something has gone wrong."
by Oliver Ruebenacker
Hello,
After a failed attempt to install the manufacturer's nvidia driver, my
system (Fedora 19, with both Gnome and KDE, on a Lenovo ThinkPad T430) does
not reach the graphical login screen any more, but instead ends up in a
white screen with a frowning computer cartoon and the message
"Oh no! Something has gone wrong. A problem occurred and the system can't
recover. Please contact a system administrator."
I can still do Ctrl-Alt-F2 to log into text mode. When I try startx, I
get an empty screen with white or black background and a mouse cursor,
extending over my two screens (laptop and external). When I try startkde it
says:
$DISPLAY is not set or cannot connect to X server.
The only error in /var/etc/X11.0.log is:
Failed to load module "nv" (module does not exist, 0)
In /var/log/messages, there are a bunch of lines like (I'm typing by
hand):
gnome-session[2658]: (gnome-shell:2949): Cogl-WARNING **:
./driver/gl/cogl-framebuffer-gl.c:561: GL error (1282): Invalid operation
Could not find a solution on Google.
I already reinstalled a bunch of packages, including cogl, gdm,
gnome-shell, @kde-desktop, xorg-x11-drv-nouveau, kernel, but no change.
Any advice? Thanks!
Best,
Oliver
--
Oliver Ruebenacker
IT Project Lead at PanGenX (http://www.pangenx.com)
Be always grateful, but never satisfied.
10 years, 6 months
OT: Upgrading to Newer Laptop
by Tim Evans
Looking to move up from my ThinkPad T61p (Fedora 19) to something more
current. Looks like the T530 might be an option, as might be the Dell
Latitude E6350. Both are priced in the same ballpark. Comments
welcome, as well as other suggestions. Thanks.
--
Tim Evans | 5 Chestnut Court
Linux/UNIX Consulting | Owings Mills, MD 21117
http://www.tkevans.com/ | 443-394-3864
tkevans(a)tkevans.com
10 years, 6 months