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, 9 months
no printout, but no other hint of error. F18.
by William Mattison
Hi,
When I try to print anything out, I get no printout. Even a test page does not come out. But no indication of trouble shows up on the monitor, and no indication of trouble on the printer's display. I did download and install the driver. cups gives no hint of trouble that I recognize. If I restart the system and boot up with Windows 7 home, I do get printouts.
The printer is a Xerox WorkCentre 6015ni, I'm using Fedora-18, 64-bit, and the printer is connected to the system via usb bus. This is a stand-alone home desktop.
I'm neither trained nor experienced in sys. admin. I've exhausted the help I can get from the printer's manual (media and web site). Any help you can give will be appreciated.
Bill.
10 years, 10 months
how to make user account partially bi-lingual?
by William Mattison
(Fedora-18; all desktops)
A user needs all
* menu entries, buttons, prompts, messages, application icon labels, etc.
within
* desktops (Gnome, KDE, Xfce, etc.), all LibreOffice applications, vi, etc.
to be English.
But he needs to be able to both
* enter and view
text in both
* English and simplified Chinese
within
* vi, all LibreOffice applications, internet e-mail (Yahoo mail, gmail, etc.), etc.
where most files/messages will contain a mix of English and simplified Chinese.
How does root and/or the user set up his account so he always has these abilities? In effect, we want the account to be bi-lingual, with English as the primary language, and simplified Chinese being a secondary language.
Thank-you in advance for your help.
Bill.
10 years, 11 months
mount --move doesn't work
by Pasha R
Hi,
I'm trying to understand how mount --move can be used. Whenever I use it, I
get an error "mount: wrong fs type, bad option, bad superblock..."
for example (something I found that supposed to work):
mkdir foo bar
mount --bind foo foo
mount --move foo bar
mount: wrong fs type, bad option, bad superblock on foo,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
What is wrong with it?
P.S. I'm using F17, with kernel 3.8.3
10 years, 11 months
fedora 18 gnome-shell core dumps before live system starts
by Bram Mertens
Hi,
I wanted to give fedora 18 a try so I created a new virtual machine in
virtualbox (host is Windows 7 enterprise 64bit).
I'm using the 32bit live CD but no matter what options I try after the
fedora 18 progress bar I get a black screen followed by the blue
background for a short while and then a window displaying "oh no
something has gone wrong please contact your system administrator".
I've checked the media (troubleshoot check media and start fedora 18)
and it reported no errors.
I tried adding xdriver=vesa and troubleshooting > start with basic
vide driver but I get the same result.
I opened one of the virtual terminals and I'm able to log on as root
so some system is running, but I'm unable to tell if this is the live
system or some anaconda or other installer shell.
/var/log/messages contains reports that gnome-shell core dumped and an
abrt trace has been created.
The only report I found that resembles what I see is
https://bugzilla.redhat.com/show_bug.cgi?id=919669. In the abrt
report I also see "Process /usr/bin/gnome-shell was killed by signal 4
(SIGILL)" in the reason file.
Is there any other boot option I can try? Is there a way to recover
from the gnome-shell crash? Perhaps force fallback mode?
Thanks in advance.
Bram Mertens
10 years, 11 months
Extraordinary delay in accessing web-site
by Timothy Murphy
I have a Linksys WVC54GCA camera in a remote site,
which I access at http://xyz.com:8080 on one of my Fedora-18 laptops.
For some reason there is now a delay of an hour or so
in getting the image on my laptop.
This occurs on both my Fedora-18/KDE laptops,
whether connected by WiFi or ethernet,
and whether using Firefox, Chrome or Konqueror.
But it does not occur - I get an immediate view -
running Windows XP on the same laptops,
or on my server running CentOS-6.4.
With Firefox I get the message "Connecting to ..."
and then (endlessly) "Transferring data from ...".
Any enlightenment gratefully received.
10 years, 11 months
F17 recalcitrant X server
by Beartooth
My wife's machine downstairs (built for us by a friend who speaks
hardware; I do not) has been hitting the Diagonal Screen of Death (DSoD);
it brings up the login screen with both our names, and lets you choose
one. You type in userid and password, and whammo : DSoD.
In that condition it does however let me login over ssh and
become root. I did so, ran yum update (no trouble with that), and did a
reboot. No joy.
I tried startx.
[root@Msgv2 ~]# startx
xauth: file /root/.serverauth.1267 does not exist
[....]
Fatal server error:
xf86OpenConsole: VT_ACTIVATE failed: No such device or address
It referred me to wiki.x.org, where I found only discussions well
over my head. But the directions there recommended trying to configure,
and I tried :
[root@Msgv2 log]# X -configure
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
It said :
Please also check the log file at "/var/log/Xorg.1.log" for additional
information.
I did that :
[root@Msgv2 tmp]# rm .X0-lock
rm: remove regular file `.X0-lock'? y
[root@Msgv2 tmp]# cd
[root@Msgv2 ~]# X -configure
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
At this point, it looks to me like a catch-22 -- wie man's auch
macht, is' es verkehrt.
Can anybody spare me a clue?
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.
10 years, 11 months
Upgrade to 3.8.8-100: now boot loops !
by sean darcy
Upgraded F17 kernel to 3.8.8-100. Now it goes boots though udevd, i.e.
"Welcome" seems to find the devices, though it's hard to tell since
everything goes so fast.
/var/log/messages has no messages from these boot loops.
3.7.9-104 works.
3.8.4-102, but now dies with an fb message that nouveaufb conflicts with
vesa vga, so it's removing the generic driver. But it just hangs there.
Any help appreciated.
sean
10 years, 11 months
