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
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
odd issue booting F19 with LUKS partition
by Fred Smith
hi gang!
I've put F19 on my Acer Aspire One (dual-core Atom) where it mostly runs
just fine.
but I've noticed one oddity (by no means a show-stopper) during boot:
when it prompts for the LUKS password (for the encrypted /home partition)
the box for password entry flashes on the screen, then the screen goes
blank for 30 seconds (or so) then the box appears again.
I noticed a day or two ago that if there's a bright lamp shining on the
screen when it is in that blank state that the box is in fact still drawn
there, but it appears that the screen backlight has been shut off--I can
still see the image of it faintly in the bright light.
Everything else regarding screen behavior is fine, but this one is
pretty consistently occurring every system boot.
This did not occur immediately after installation, but I first noticed
it only a week (or so) ago (sorry, I wasn't taking notes...) so one
wonders if some update has caused it.
Any ideas on this one?
Thanks!
Fred
--
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
But God demonstrates his own love for us in this:
While we were still sinners,
Christ died for us.
------------------------------- Romans 5:8 (niv) ------------------------------
10 years, 6 months
Native Nvidia Optimus and Fedora 19
by Powell, Michael
Has anyone tried to get native Optimus running on a Fedora 19 box? When I attempt it, I get a blank black screen. I posted on the Nvidia forums, but no one has replied yet and I'm getting anxious ;-)
The general consensus is that the kernel must be 3.9 or higher, and I am running 3.9.9-302. The Nvidia readme<http://us.download.nvidia.com/XFree86/Linux-x86-ARM/319.32/README/randr14...> indicates CONFIG_DRM has to be enabled and the following driver interfaces present:
drm_gem_prime_export
drm_gem_prime_import
gem_prime_pin
gem_prime_get_sg_table
gem_prime_import_sg_table
gem_prime_vmap
gem_prime_vunmap
I have verified that CONFIG_DRM is enabled within the kernel as a module and it's loaded, but when I attempted to verify the list of module symbols, I only found two (the ones in bold).
The way I determined this information was through:
`cat /boot/config-3.9.9-302.fc19.x86_64 | grep CONFIG_DRM`
`cat /lib/modules/3.9.9-302.fc19.x86_64/modules.symbols | grep gem_prime`
Am I missing something or does it appear that F19 kernel is missing vital parts for native Nvidia Optimus support?
For those more interested, here is the post<https://devtalk.nvidia.com/default/topic/551709/linux/319-23-the-infamous...> on the nvidia forums.
10 years, 6 months
Mate desktop, login produces up to ten caja instances
by Fred Smith
On F19 with Mate desktop, sometimes after login 8 or 9 or even 10 copies
of Caja (Mate File Manger) are started up.
Most of the time not, but perhaps once every day or two this will happen.
the rest of the time it's completely normal.
I found these /var/log/messages entries at around the right time, but I'm
not certain whether they are from login or the boot a small bit earlier:
Jul 19 19:23:56 aspirebox dbus-daemon[556]: dbus[556]: [system] Rejected send me
ssage, 2 matched rules; type="method_call", sender=":1.52" (uid=1000 pid=1410 co
mm="caja -n ") interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.12" (uid=0 pid=638 comm="/us
r/sbin/console-kit-daemon --no-daemon ")
Jul 19 19:23:56 aspirebox dbus[556]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.52" (uid=1000 pid=1410 comm="caja -n ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.12" (uid=0 pid=638 comm="/usr/sbin/console-kit-daemon --no-daemon ")
Anybody got any clues?
thanks!
Fred
--
-------------------------------------------------------------------------------
Under no circumstances will I ever purchase anything offered to me as
the result of an unsolicited e-mail message. Nor will I forward chain
letters, petitions, mass mailings, or virus warnings to large numbers
of others. This is my contribution to the survival of the online
community.
--Roger Ebert, December, 1996
----------------------------- The Boulder Pledge -----------------------------
10 years, 7 months
SELinux error on every policy package update
by Suvayu Ali
Hi,
I have been having this weird problem; everytime I there is a
selinux-policy update, I get the following error:
libsepol.print_missing_requirements: hotplug's global requirements
were not met: bool init_systemd (No such file or directory).
libsemanage.semanage_link_sandbox: Link packages failed (No such file
or directory).
semodule: Failed!
FWIW, this machine was updated from F17 to F19 with yum. I tried
searching for the error above, but could not make sense of what I found.
Any ideas?
--
Suvayu
Open source is the future. It sets us free.
10 years, 7 months
Re: The state of blu-ray burning in linux is terrible
by Thomas Schmitt
Hi,
sorry for breaking the thread. I was not subscribed up to now
and did not yet find an archive that exposes message ids.
--------------------------------------------------------------
It is not that bad with Blu-ray. At least with the backends.
(I am the developer of libburn and use BD-R and BD-RE media daily.)
But wodim (or "cdrecord") out of cdrkit should really be used
only for CD.
The slowliness of BD media comes from their Defect Management
which checkreads the written blocks while they are still present
in the drive's buffer. In case of poor read quality the blocks
get written again or redirected to the Spare Area where the data
get stored in replacement blocks.
This checkreading reduces write speed to at most half of the
nominal speed of drive and BD medium.
BD-R do Defect Management by default if they are formatted.
BD-RE can only be used formatted and do Defect Management by default.
--------------------------------------------------------------
Original cdrecord out of cdrtools was already discussed in the this
thread. To my knowledge it is fast with BD-R, because it does not
format them. It is not fast with BD-RE, because it uses SCSI command
WRITE(10) which does not allow to override the slow Defect Management.
--------------------------------------------------------------
growisofs out of dvd+rw-tools has a little bug with BD-R.
https://bugzilla.redhat.com/show_bug.cgi?id=858029
https://bugzilla.redhat.com/show_bug.cgi?id=868527
It is supposed to be fixed in
dvd+rw-tools-7.1-13.fc19
The tiny patch is shown in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016
Workaround is to explicitely format the BD-R before use by
dvd+rw-format /dev/sr0
or to use option
-use-the-force-luke=spare:none
when giving an unformatted BD-R to growisofs.
growisofs formats BD-R by default and then uses slow Defect
Management. This can be prevented by option
-use-the-force-luke=spare:none
growisofs has no means to prevent Defect Management on BD-RE media.
--------------------------------------------------------------
My own programs, libburn based cdrskin and xorriso, do not format
BD-R by default. So they are as fast as with cdrecord.
Other than with cdrecord it is possible to format BD-R on request
cdrskin -v dev=/dev/sr0 blank=format_if_needed
xorriso -outdev /dev/sr0 -format as_needed
which makes them capable of slow Defect Management.
Other than growisofs and cdrecord, cdrskin and xorriso offer the
opportunity to disable Defect Management on formatted BD-R and
on BD-RE
cdrskin stream_recording=on ...cdrecord-like-burn-options...
xorriso -stream_recording on ...xorriso-burn-commands...
This is especially helpful with 2x BD-RE, which elsewise need
an awfully long time to write their capacity of 22.5 GiB.
Have a nice day :)
Thomas
10 years, 7 months
Do I need avahi?
by Timothy Murphy
I recently noticed that I have been getting warnings
avahi-daemon[5884]: dbus-protocol.c:
Too many objects for client ':1.15', client request failed.
on my server.
I must admit I didn't know I was running avahi on the server.
I looked at a couple of avahi howtos,
and it seemed that for almost any usage other packages are required,
in particular nss-mdns .
If this is in fact required by avahi, it seems surprising
that it is not automatically installed at the same time.
(None of the examples of avahi usage actually worked on my system.)
But my real query is whether avahi (or zeroconf)
could actually offer me anything useful.
I'm running dhcpd on the server,
and I'm not looking for information about printers
or other users on my home network.
Also, is there any way of discovering who "client 1.15" is?
And is anything likely to go wrong if I simply "service avahi-daemon stop"?
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
School of Mathematics, Trinity College, Dublin 2, Ireland
10 years, 7 months