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, 11 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, 5 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, 7 months
X freezes in FC 18
by Jens Neu
Dear list,
I'm experiencing random freezes of two desktops, both up-to-date FC 18,
totally different hardware (Core2Duo E5300, Core i7), different Graphis
Cards but both Nvidia using nouveau with a dual monitor setup.
Desktop completely freezes, Num Lock on keyboard is dead. Gut feeling
tells me it is induced by scrolling.
When happening, I can ssh into the machine, everything looks perfectly
normal. No 100% CPU on nothing, no zombies, no whatever. Nothing in
dmesg, Xorg.0.log, messages.
Restart of graphical.target does not do anything, when killing
/usr/bin/X (with -9 though) I get kdm back.
Any thoughts where to debug further?
regards
Jens
10 years, 10 months
Procedure for changing ethernet controllers
by Alex
Hi,
I have an fc17 system in which I've had to change the ethernet
controller from an e1000e card to what I believe is an rtl81391`2. I
recall changing the 70-persistent-net udev config file, but that
appears to no longer exist on my fc17 system.
What is the proper procedure for detecting, initializing, and
reconfiguring the system to use my new card?
I believe I'll also had to use dracut to recreate the initrd. I will
also need to detect for sure which driver the new ethernet controller
uses.
Thanks,
Alex
10 years, 10 months
What happened to floppy drive support?
by n2xssvv.g02gfr12930
I've been using a floppy boot disk as reserve if my HD boot fails, But
it appears floppy support as now been removed. Why? Then how can I
create an emergency media that is flexible enough to be updated as required?
JB
10 years, 10 months
RE: retrofitting LUKS encryption on installed system
by J.Witvliet＠mindef.nl
-----Original Message-----
From: users-bounces(a)lists.fedoraproject.org [mailto:users-bounces@lists.fedoraproject.org] On Behalf Of Fred Smith
Sent: Friday, June 28, 2013 3:42 PM
To: users(a)lists.fedoraproject.org
Subject: retrofitting LUKS encryption on installed system
I've got a F19 installation that I'd like to turn into a fully encrypted
system with LUKS.
There are many howtos on the web for encrypting a partition, but they
all show doing it to /home.
-----Original Message-----
No, just re-install.
One partition with /boot and another with an encrypted volume-group, holding /, swap and the rest.
But before embarking on that trip, do you really need full disk encryption?
I mean, the content of /usr is on any fedora-cd ;-) And when up-and-running, everything is unlocked.
The only valid reason I can think about, is that other people have physically access to your machine and could get root-access by booting from cd/dvd, and might alter your system.
It surely works, but at a performance price. And the certainty that you have to enter the LUKS-key each time you boot.
______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
10 years, 10 months
File open/save dialog sort order
by Michael Eager
I reinstalled Fedora 18 with KDE and I notice a change in
the order in which directories and files are displayed.
In some applications, the sort is now case sensitive, so
that all the initial capitals are listed before the initial
lower case names. Previously, the names were sorted without
case sensitivity.
I see this behavior in Firefox, Thunderbird, Acroread and
others. There are other application where the file dialog
sorts files using a case insensitive sort, like Dolphin, k3b,
or kget.
I edited kdeglobals to add "Sort case insensitively=true" to
the [KFileDialog Settings] section. This should be the
default. It did not make any difference.
Any suggestions on how to set the file name sort order?
--
Michael Eager eager(a)eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
10 years, 10 months
