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
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
Runlevel 3 after fedup
by ellis@spinics.net
After upgrade from 17 to 18 with fedup and installing all the updates I was
unable to login as any user other than root. When I tried I was greeted with
the message: "System is booting up".
After beating my head against the wall I finally tried booting to runlevel
5 instead of 3. That fixed the issue. But booting to runlevel 3 and switching
to 5 doesn't work.
Possibly a problem with systemd?
--
http://yosemitenews.info/
11 years
Unrelieved black popups and message boxes
by Temlakos
Everyone:
I asked this before under a different heading, and no one answered.
I get a large volume of e-mail, and very often I interact with a site
that brings up a lot of message boxes, "suggestion boxes" (for
auto-filling from a few keystroke clues), and bringing up apps after
they were minimized to the system tray or the task bar. Now why is it
that, after maybe two hours of operation, those popups come up and are
totally black? The only way to solve the problem, that I have found, is
to shut down. And even then, I can't even see what I'm doing, but have
to guess where the icons are for executing a controlled shutdown. (I can
always bring up a command-line login screen, log in as root, and then
shut down. But that doesn't seem to solve the problem for the next session.)
And when I log back on, everything's fine--until it starts happening
again, after several more window draws.
What could be causing this? Where do I even look for error logs and the
like?
I never had this problem in any other version of Fedora. I'm having it
now, and it's driving me nuts.
For the record, I used the "upgrading from F17 to F18 using yum" method.
I even used the elaborate script that walks you through rpmnew and
rpmsave reconciliation. And I've kept up with every system update since
then. Actually, the problem began about three kernel updates back.
Temlakos
11 years
Samba 4
by Gabriel VLASIU
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi!
Maybe someone can help me with samba 4 (F18).
In previous version (samba 3/F17) I had this definition for a share:
[xxx]
path = /xxx
browseable = yes
writable = yes
; writable = no
printable = no
public = yes
guest only = yes
guest ok = yes
create mask = 0664
directory mask = 0775
force group = xxx
The important thing here is "create mask". I do not want all files created
by users to be executable in linux.
The same definition work in samba 4 with the exception of running windoze
.exe files from the share. In windoze, there is no read & exec permissions
associated with the file. Only read for everyone and read/write for unix
user/group. I can manually set the exec flag (from linux or windoze) but
this has to be made every time someone copy an executable file.
Any chance to revert to the behavior from samba 3?
Thank you.
Sincerely,
Gabriel
- --
// Gabriel VLASIU
//
// OpenGPG-KeyID : 44952F15
// OpenGPG-Fingerprint: 4AC5 7C26 2FE9 02DA 4906 24B2 D32B 7ED7 4495 2F15
// OpenGPG-URL : http://www.vlasiu.net/public.key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
iQIcBAEBCgAGBQJRCntGAAoJENMrftdElS8VccwP/1Bn7zfctWYW86LES/0kE0J/
nig6I927ekX2d+UwUBffUmFgL/G9Pfh4drX7Lrh/HakT/MBerUxZa79URF3v7mLS
OmX00areoAHBc1wBo39xHLujNKwwifr4fdgLLFt3hsA0iL6R71l6eDz9tzk7SUPA
zpdo6bx9mqX95TdmDHR/q+2Z5ab39hP5AkIRWZwa8jQiSHKn5RN4MyWsTtpFnCkR
fM88zmDq72NGXJD9oApd9LLvZbw08rILI7na6IXIcFg+HTowM0IhozPUdqfPtYf9
FgmQP7vg1J38U8Lw7P4n+5/eei/+h0YdMHs1N864aYumNz+Ts+2KU1RLyzr9ZIUg
YkcQ6V60WA5Esy2c7p87/TgL+5bRa4pqMhghLXcoBAxRbaqFOY7i2fbb8/+JfU1y
lJq5z08M0RXDV0dSwKix1iuGd5cfSfoFroC8J9SXttMZcPwoDVIz5L/arWFFGByo
f9m5XD5fPMxOY8vIkGbO62oYhH66gIIelvQXT8g7TiTWgIeTXdOigYEeZQye43Fk
Sst9nS/JUpZcXSq8qIErh/WD4nvAOzUg3p0IgwHpmqxIndDNrVD1aol3mooKuv94
gzZWQEU1Z0Tfm5NnS5qrsiU3RnwgkI8qya5xHVFIhzMTUP7ickWNA1myRdBWXDt0
gc7W1TxMJY3xZ2u1Bngx
=uDBh
-----END PGP SIGNATURE-----
11 years, 1 month
Read AIFF metadata
by Ranbir
Hi Everyone,
I bought some AIFF tracks from Beatport the other day. I prefer them
over WAV because the AIFF have embedded album art, song name, etc.
I loaded them up in Audacious (F17+GNOME) which played them happily.
But, it's not reading any of the metadata. All of the fields are
displayed as empty. I tried VLC and mplayer, too. Still nothing.
I downloaded the same tracks on to a Windows 7 PC and listened to them
with VLC. VLC read the metadata without any problems. Hmmm....
I then installed Kid3 to see if it could read the metadata. Sure
enough, it was all there. So, the tracks are clearly not broken.
I tried converting the AIFFs to FLAC with ffmpeg and flac, but the
metadata was still missing.
I'd appreciate a recommendation for an audio player that can read AIFF
metadata in GNOME or better yet, how I can convert these AIFFs to FLAC
and keep the metadata intact.
Regards,
Ranbir
--
Kanwar Ranbir Sandhu
Linux 3.7.3-101.fc17.x86_64 x86_64 GNU/Linux
09:55:17 up 6 days, 20:36, 9 users, load average: 0.04, 0.06, 0.05
11 years, 1 month
Fedora hangs driving me nuts, in Windows it works without problems!
by Valent Turkovic
My work Fedora 17 64bit box gangs without reason, and I can't track
down issue causing it! When I reboot into Windows 7 32bit it works for
days without any hangs.
This is a company PC so IT installed Windows 7, but I don't use it,
that is why I installed Fedora and use it as my primary desktop.
I'm not some guru sysadmin, but I'm not a newbie, as I have been using
Linux over 10 years as my primary desktop and have few private servers
that I maintain, I have troubleshooted and fixed numerous issues with
mine and friends machines.
My desktop works perfectly for hours, sometime for days, but after
some time (usually 1-2 days) it just freezes. It doesn't matter how
many free memory I have, which apps I'm runnig or which desktop I'm
using. I tried leaving just desktop running with no apps, still
freezes, changed desktops, kde - hangs, gnome 3 - hangs, mate - gangs,
tried leaving multiple apps doing something, still hangs. I ran memory
test utils, memory is working ok. These gangs are driving me nuts!
Is anybody having unexplained hangs with Fedora 16 and 17 64bit? Could
it be some 64bit issue because Windows is 32bit and it works?
How can I troubleshoot what is causing hangs of my machine?
Thanks.
--
follow me - www.twitter.com/valentt & http://kernelreloaded.blog385.com
linux, anime, spirituality, wireless, scuba, linuxmce smart home, zwave
ICQ: 2125241, Skype: valent.turkovic, MSN: valent.turkovic(a)hotmail.com
11 years, 1 month
Adwaita GTK3 on F18 no longer honors bgcolor
by Gordon Messmer
Under Fedora 17, I was able to select an alternate background color for
GTK2 and GTK3. Under F18, only the GTK2 applications honor the setting.
Before I file a a bug, does anyone know if this behavior was an
expected change?
$ dconf dump /org/gnome/desktop/interface/
[/]
gtk-color-scheme='selected_bg_color:#493f53;'
$ cat .gconf/desktop/gnome/interface/%gconf.xml
<?xml version="1.0"?>
<gconf>
<entry name="gtk_color_scheme" mtime="1358361695" type="string">
<stringvalue>selected_bg_color:#493f53;</stringvalue>
</entry>
</gconf>
11 years, 2 months