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, 7 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, 9 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
Suspension problem last 2 days
by Timothy Murphy
I've been having a problem on my Thinkpad T61 for the last 2 days.
In fact since "yum update" installed kernel-PAE-3.11.1-200.fc19.i686,
though that is probably a coincidence.
The problem is that when the laptop lid is closed and then opened later
the machine is in a confused state.
For example it is impossible to shutdown the machine
except by pressing the power button for 10 seconds.
I just wondered if anyone else has had similar symptoms recently?
These are some of the entries in /var/log/messages following "Lid opened":
--------------------------------------
Sep 21 21:22:37 rose systemd-logind[358]: Lid opened.
Sep 21 21:22:37 rose systemd[1]: Caught <SEGV>, dumped core as pid 1590.
Sep 21 21:22:37 rose systemd[1]: Freezing execution.
Sep 21 21:22:37 rose kernel: [ 1026.161712] video LNXVIDEO:01: Restoring
backlight state
Sep 21 21:22:37 rose systemd-sleep[1511]: System resumed.
Sep 21 21:22:37 rose systemd-cgroups-agent[1596]: Failed to get D-Bus
connection: Failed to connect to socket /org/freedesktop/systemd1/private:
Connection refused
...
Sep 21 21:23:10 rose kdm[371]: X server for display :0 terminated
unexpectedly
Sep 21 21:23:12 rose dbus-daemon[362]: dbus[362]: [system] Failed to
activate service 'net.reactivated.Fprint': timed out
Sep 21 21:23:12 rose dbus-daemon[362]: dbus[362]: [system] Failed to
activate service 'org.freedesktop.systemd1': timed out
Sep 21 21:23:12 rose dbus[362]: [system] Failed to activate service
'net.reactivated.Fprint': timed out
Sep 21 21:23:12 rose dbus[362]: [system] Failed to activate service
'org.freedesktop.systemd1': timed out
Sep 21 21:23:24 rose kdm: :0[1650]: Fatal X server IO error: Interrupted
system call
Sep 21 21:23:46 rose systemd-cgroups-agent[1691]: Failed to get D-Bus
connection: Failed to connect to socket /org/freedesktop/systemd1/private:
Connection refused
Sep 21 21:39:55 rose chronyd[335]: Selected source 149.157.192.251
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
--------------------------------------
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland
10 years, 5 months
Fedora 19, KDE 4.11.1, no login screen
by Andrea
Hi,
I've just updated F19 and after reboot I do not get the usual kdm login screen.
The graphic screen with the F stays there forever.
I can login in text mode and run 'startx' and I get to the normal KDE session.
Looking at the logs I only noticed
[FAILED] Wait for Plymouh Boot Screen to quit
and in /var/log/messages
there is something about
Sep 21 15:24:35 localhost kdm[335]: plymouth --ping -> 0
Sep 21 15:24:35 localhost kdm[335]: plymouth is running ...
Sep 21 15:24:35 localhost kdm[335]: plymouth deactivate -> 0
Sep 21 15:24:35 localhost kdm[335]: plymouth --has-active-vt -> 0
Sep 21 15:24:35 localhost kdm[335]: plymouth should quit when server starts
Sep 21 15:24:36 localhost kdm[335]: plymouth is active on VT 1, reusing for :0
Sep 21 15:24:36 localhost kdm[335]: X server startup timeout, terminating
Sep 21 15:24:36 localhost kdm[335]: X server for display :0 cannot be started, session disabled
any idea?
10 years, 5 months
What happened to my printer!?!
by Alan Evans
Hello all,
Sometime in the last couple of weeks, I lost my ability to print to the
office printer. If I check (KDE) System Settings, the printer's status
reads, "Paused - 'Unable to connect to CIFS host after (tried 3 times)'".
Everybody else can still use this printer, and there have been no major
network reconfiguration events recently. I can't figure out how to bring
this back online.
I tried to simply re-add the long-existing printer again, but the "Add a
New Printer" dialog won't let me browse the network for any printers at
all. The [Browse] button under "Windows Printer via SAMBA" is greyed out,
so I would have to type the URI by hand. But the URI is correct in the
configuration of the current, non-working, printer, as far as I know.
Is there any way to figure out why the current printer is offline, beyond
"Unable to connect"? Not being able to print is really messing with my
workflow.
-Alan
10 years, 5 months
F19:personal file sharing doesn't work
by Antonio M
when I want to share files in a easy way, I was used to Personal Files
Sharing.
Now I enabled it on my F19 systems (both in Gnome and Mate) but
something seems wrong:
When I open Resources/Network I see shares of computers A and B but:
working on A clicking on B I get :
Impossible to mount position
Error HTTP: Cannot connect to destination (PCdesktop.local)
Clicking on A (per quanto abbia senso) I get:
Impossible to mount the position
Error HTTP: Internal Server Error
Same if I work on B
any hint?? googling around didn't give me any clue
Tnx
--
Antonio M
Skype: amontag52
Linux Fedora F19(Schroedinger's cat) on Acer 5720
http://lugsaronno.altervista.org
http://www.campingmonterosa.com
10 years, 5 months
Accessing usb in text
by Richard Vickery
Hi gang,
I'm stuck in a text environment. I want to save stuff in /home to a USB
drive but I forget how it is mapped / how the GUI accesses it; I know that
it is under /run, and after this I am lost.
Thanks for any help,
Richard
10 years, 6 months
Weird network problem
by Phil Dobbin
Hi, all.
I've got several machines on a LAN behind a NAT with DHCP assigning
always the same addresses from a dynamic IP.
A couple of days ago the IP changed & since then, one of the machines
running Fedora 17 always fails first time to connect to the network:
launch Thunderbird, no start screen, first attempt to check mail, it
tells me that there's no network connection, second attempt it connects.
The scheduled DejaDup backup always fails with no network but will run
manually no problem. Firefox can't find Google but the Nagios
web interface is fine as is all the cli stuff (ping, ssh, etc).
Most annoyingly, yum update goes through every mirror before partially
downloading part of the updates & if the updates are large, it takes
about three attempts to get them all installed.
I'd like to clear this up naturally especially as in the next couple of
weeks I'll be upgrading this box to Fedora 18 & the last thing I need is
a dodgy network connection.
All the machines below are on the same LAN & they all work fine after
the IP address change, it's only the Fedora box that's causing problems.
Any help appreciated. I'm stuck.
Cheers,
Phil...
--
currently (ab)using
CentOS 5.9 & 6.4, Debian Squeeze & Wheezy, Fedora Beefy, Spherical &
That Damn Cat, Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise,
Quantal & Raring
GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc
10 years, 6 months
usb stick specify as /dev/sdz
by Frank Murphy
Is it possible to have a usb stick
used a specific /dev/sdz
based on device label
So no matter which usb slot,
it's pugged into, gets the same sdz
my udev rule. so far:
BUS=="usb",
KERNEL=="sd*",
ATTRS{label}=="foo_or_bar",
[...]
--
Regards,
Frank
www.frankly3d.com
10 years, 6 months