Wireless network dies
by SternData
Since installing the latest kernel, 3.2.2-1.fc16.i686.PAE, my wireless
connection dies after several hours. The access point is functioning
normally -- all other devices continue to work.
Once this happens, NetworkManager shows that wireless is enabled, but
shows no available networks. Stopping and restarting the service doesn't
help. It's necessary to reboot to restore the network connection.
Here's /var/log/messages at the time it went away.
Jan 30 18:15:04 sds-desk kernel: [107165.004357] ath5k_hw_get_isr: ISR:
0x00000400 IMR: 0x00000000
Jan 30 18:17:04 sds-desk kernel: [107285.004581] ath5k_hw_get_isr: ISR:
0x00000400 IMR: 0x00000000
Jan 30 18:20:01 sds-desk systemd-logind[1047]: New session 229 of user root.
Jan 30 18:20:01 sds-desk systemd-logind[1047]: Removed session 229.
Jan 30 18:23:04 sds-desk kernel: [107645.004350] ath5k_hw_get_isr: ISR:
0x00000400 IMR: 0x00000000
Jan 30 18:27:01 sds-desk systemd-logind[1047]: New session 230 of user root.
Jan 30 18:27:02 sds-desk systemd-logind[1047]: Removed session 230.
Jan 30 18:30:01 sds-desk systemd-logind[1047]: New session 231 of user root.
Jan 30 18:30:01 sds-desk systemd-logind[1047]: Removed session 231.
Jan 30 18:30:01 sds-desk systemd-logind[1047]: User root logged out.
Jan 30 18:30:08 sds-desk kernel: [108068.152401] ath5k phy0: gain
calibration timeout (2422MHz)
Jan 30 18:30:08 sds-desk kernel: [108068.486736] ath5k phy0: calibration
of channel 3 failed
Jan 30 18:30:10 sds-desk kernel: [108070.521094] cfg80211: Calling CRDA
to update world regulatory domain
Jan 30 18:30:10 sds-desk kernel: [108070.806151] cfg80211: World
regulatory domain updated:
Jan 30 18:30:10 sds-desk kernel: [108070.806157] cfg80211: (start_freq
- end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 30 18:30:10 sds-desk kernel: [108070.806162] cfg80211: (2402000
KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 30 18:30:10 sds-desk kernel: [108070.806168] cfg80211: (2457000
KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 30 18:30:10 sds-desk kernel: [108070.806172] cfg80211: (2474000
KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 30 18:30:10 sds-desk kernel: [108070.806177] cfg80211: (5170000
KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 30 18:30:10 sds-desk kernel: [108070.806182] cfg80211: (5735000
KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 30 18:30:10 sds-desk NetworkManager[1021]: <info> (wlan0):
supplicant interface state: completed -> disconnected
Jan 30 18:30:10 sds-desk NetworkManager[1021]: <info> (wlan0):
supplicant interface state: disconnected -> scanning
and it repeats like this until I reboot.
https://bugzilla.redhat.com/show_bug.cgi?id=785951
--
-- Steve
12 years, 2 months
Re:Auto Bug reporting tool in KDE-4.7
by adi11bgsg＠gmail.com
Hello KDE Team,
I am using Fedora 16(x86_64) version,with the Default Desktop being
"KDE PLasma Workspace 4.7".
Everything is functional and running smoothly,except such messages:-
*google-chrome-stable Process /opt/google/chrome/chrome was killed by
signal 11(SIGSEGV) 2012-01-29 22:25
*The installed* google-chrome *is of version * 16.0.912.77
*This type of message also occurs while I run* "vlc" mediaplayer *which is
of version *1.1.13* The Luggage
The message box pops up in "Automatic Bug Reporting Tool" as Header of the
message box.
Please,Help me regarding this.
From
-Kaushik Guha
12 years, 2 months
Pulse Audio Continues to be a Menace
by Fedora User
The following happens quite frequently:
A few days ago, I plugged into HDMI. When I was done I manually
returned the "audio hardware setup" to the analog output (once upon a
time it did this automagically). A couple of boots since then - all is
fine.
Today, I have no sound. The ONLY choices I have in the hardware
settings are HDMI or "dummy." If I reboot it might offer the proper
options.
I can also force the issue by removing the scan in /etc/default.pa but
then there is no default device which creates other problems. Back in
the day, I routinely removed Pulse but these days that seems impossible
due to dependencies.
12 years, 2 months
kernel-3.2.2-1.fc16 breaks wifi
by Christian Menzel
Hi,
the kernel-3.2.2-1.fc16 update broke the wifi on my Lenovo X220 (Intel(R)
Centrino(R) Advanced-N 6205 AGN, REV=0xB0).
The system detects and connects to a wireless lan, but after some minutes
the system cannot connect to other hosts anymore.
The wifi icon still shows and the system still has an ip-address but all
pings answer 'destination unreachable'.
After stopping/starting wifi the Internet connection will stay for a short
time before failing again.
For me kernel 3.2.2 is unusable and I went back to 3.2.1.
Is anyone else experiencing this problem?
Chris
12 years, 2 months
Troubleshooting upnp and dlna
by Khairil Yusof
Hi,
Just installed F16 and there is an issue I don't know how to
troubleshoot and couldn't find answers easily on Google.
My media applications can't seem to see upnp devices on my local
network. There are two providers, my phone (dlna provider), home
server (dlna provider). TV which is a dlna media player, can detect,
list and play from both these devices. Banshee on an Ubuntu PC on same
network can also see the DAAP share. So there is at least a working
configurations on the same network. The TV can't see media shared by
rygel either.
Is there something blocking upnp discovery and sharing on FC? Could it
be some sort of network misconfiguration that FC is picky about?
Any help on how to troubleshoot upnp discovery in Fedora would be much
appreciated.
Regards
12 years, 2 months
Virtual machine => Physical machine - fix screen resolution?
by Philip Rhoades
People,
I sent this note to the Fedora virtual list so I thought I might try
here . .
I installed a Fedora 16 x86_64 virtual machine on a Fedora 14 x86_64
server but used a physical disk (/dev/sdb = /dev/vda) so I could get the
new server going almost completely in virtual mode and then when it was
ready to go, reboot the machine on the new drive. This process went
extremely well (thanks to all the Fedora developers!) but there were a
few glitches left to sort out - one of which was the screen resolution
for both the console and in X. It seems the default virtual screen is
1024x768 but I need 1280x1024(or 768). I tried adding a vga parameter
to the linux line in the grub.cfg file but that only temporarily changed
the resolution during bootup. xorg.conf doesn't get used much anymore -
do I need to create it for this case? Is there some way to tell Fedora
to rediscover the maximum screen resolution somehow?
Thanks,
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil(a)pricom.com.au
12 years, 2 months
SMART: sectors waiting to be remapped, negative numbers and dual boot
by Ian Malone
Hi,
I had a slightly worrying moment yesterday when the disc manager in
F16 came up after booting and logging in and warned me that one of my
drives wasn't healthy. It was installed in August so is outside the
traditional early-failure window, which isn't to say it couldn't be on
the verge of failing. Things that are odd though (via the disc
management SMART view):
1. It reports 'electrical failure' as the SMART test status.
2. The parameter that is failing is "197 C5 Current Pending Sector
Count", which shows a large negative number.
3. On refreshing the SMART data both problems clear, current pending
sector count goes to 0 + n/a and drive status is healthy.
4. Running a short self-test the drive still shows as healthy.
5. On a long self test this morning I got 'electrical failure' again
at the end, however refreshing changed this to 'healthy'.
Both times I've seen this (yesterday and today) are after re-booting
from Windows XP, so I'm wondering if there's something about XP SMART
management (or lack off?) that's leaving this parameter unset, or
possibly SMART is reading a small positive value incorrectly before
pending sectors have been cleared.
Does anyone else have any idea what might be going on? Drive is
obviously still in warranty, just want to know how concerned I need to
be.
--
imalone
12 years, 2 months
Virtual machine => Physical machine - fix screen resolution?
by Philip Rhoades
Mark,
> Date: Sun, 29 Jan 2012 00:34:52 -0500
> From: Mark LaPierre <marklapier(a)aol.com>
> To: Mail List Fedora Users <users(a)lists.fedoraproject.org>
> Subject: Re: [CentOS] Virtual machine => Physical machine -
> fix screen
> resolution?
> Message-ID: <4F24DA7C.7060701(a)aol.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> On 01/28/2012 09:01 PM, Philip Rhoades wrote:
>> People,
>>
>> I sent this note to the Fedora virtual list so I thought I might try
>> here . .
>>
>> I installed a Fedora 16 x86_64 virtual machine on a Fedora 14 x86_64
>> server but used a physical disk (/dev/sdb = /dev/vda) so I could get
>> the
>> new server going almost completely in virtual mode and then when it
>> was
>> ready to go, reboot the machine on the new drive. This process went
>> extremely well (thanks to all the Fedora developers!) but there were
>> a
>> few glitches left to sort out - one of which was the screen
>> resolution
>> for both the console and in X. It seems the default virtual screen
>> is
>> 1024x768 but I need 1280x1024(or 768). I tried adding a vga
>> parameter to
>> the linux line in the grub.cfg file but that only temporarily
>> changed
>> the resolution during bootup. xorg.conf doesn't get used much
>> anymore -
>> do I need to create it for this case? Is there some way to tell
>> Fedora
>> to rediscover the maximum screen resolution somehow?
>>
>> Thanks,
>>
>> Phil.
>
> Hey Phil,
>
> I'm assuming that you are using a graphical desktop. Can you adjust
> the
> resolution with System/Preferences/Display?
No - the maximum resolution there is 1024x768 - which I presume is the
default res of the virtual screen. The monitor is capable of 1280x1024
(it was previously running Fedora 14).
Thanks,
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil(a)pricom.com.au
12 years, 2 months
Possible bug with F16 + fingerprint reader and gnome login
by Digimer
Hi all,
I've seen a bug for a while and was going to file a bug, but was
hoping to confirm that others see it as well.
When I log into Gnome by swiping my finger, it logs in and then
immediately kicks out the the screen saver, requiring a second login.
However, if I login by instead typing a password, it is fine.
Fully up to date (as of Jan. 29, 2012) Fedora 16 x86_64.
Was upgraded from Fedora 16
Lenovo Thinkpad 400s
Reader is reported as "UPEK Eikon 2"
--
Digimer
E-Mail: digimer(a)alteeve.com
Papers and Projects: https://alteeve.com
12 years, 2 months
