users August 2013

users@lists.fedoraproject.org

205 participants
215 discussions

WiFi permanently disappeared after booting test kernel
by Mike Fleetwood 26 Aug '14

26 Aug '14

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.

4 3

losing WiFi Access - prompted for password
by SternData 09 Jun '14

09 Jun '14

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

3 3

138a:0018 Validity Sensors will not work
by Jerome Yanga 01 Dec '13

01 Dec '13

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

6 14

Weird network problem
by Phil Dobbin 02 Oct '13

02 Oct '13

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

9 28

HDA jack retasking
by Raman Gupta 01 Oct '13

01 Oct '13

I have Intel HDA Audio on my motherboard (Asus P9X79 PRO). This chipset has the capability to retask jacks for another purpose, for example changing a line out jack to a headphone jack. Has anyone successfully retasked an audio jack (specifically, on my motherboard, the blue Line Out jack) to a headphone? I found a post on pulseaudio-discuss re. this hda-jack-retask program which seems to imply it can be done, but it didn't seem to work (I didn't try every available combination however): http://lists.freedesktop.org/archives/pulseaudio-discuss/2011-December/0123… Regards, Raman

3 4

odd issue booting F19 with LUKS partition
by Fred Smith 15 Sep '13

15 Sep '13

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) ------------------------------

3 3

Native Nvidia Optimus and Fedora 19
by Powell, Michael 09 Sep '13

09 Sep '13

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.h…> 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-b…> on the nvidia forums.

7 16

Fedora/Redhat and perfect forward secrecy
by Reindl Harald 06 Sep '13

06 Sep '13

https://bugzilla.redhat.com/show_bug.cgi?id=319901 looks like Redhat based systems are the only remaining which does not support EECDHE which is a shame these days in context of PRISM and more and more Ciphers are going to be unuseable (BEAST/CRIME weakness) ______________________________________________________________ https://bugzilla.redhat.com/show_bug.cgi?id=960193 > ECC will be supported on RHEL-6.5 and will also be > part of the planned FIPS-140 revalidation so what is here state of play for Fedora? ______________________________________________________________ https://www.google.at/search?q=postfix+EECDHE https://www.google.at/search?q=%22EECDHE-RSA%22 http://en.wikipedia.org/wiki/Elliptic_curve_Diffie%E2%80%93Hellman http://en.wikipedia.org/wiki/Perfect_forward_secrecy

4 4

Copy-pasting without transferring format
by Oliver Ruebenacker 04 Sep '13

04 Sep '13

Hello, I would like to be able to copy-paste text without transferring the format. I'm using F19 with KDE. Currently, when I copy-paste (between Firefox, LibreOffice, etc), formatting like font, font size and font attributes get also copied and pasted. But I am looking for a way to copy-paste such that the format of the original text is discarded and instead the format of the target document is used, as if I had typed the text on the keyboard. (My wife uses the following trick on Windows: copy-paste text into URL-field of the browser, then copy-paste from URL-field to destination). Thanks! Best, Oliver -- Oliver Ruebenacker IT Project Lead at PanGenX (http://www.pangenx.com) Be always grateful, but never satisfied.

10 14

SSH problem with kernel 3.10.9-200
by SternData 04 Sep '13

04 Sep '13

Is it just me or is anyone else seeing this? Description of problem: Using SSH to access files on remote system (but local to my LAN). Using arrow key to scroll through files or up/down in bash_history or left or right in current command. Works fine with 3.10.7-200. When using kernel 3.10.9-200, cursor stops moving and characters are either not being transmitted or are not echoing back. Have to wait for 3-5 seconds to be able to continue typing. Version-Release number of selected component (if applicable): 3.10.9-200 How reproducible: SSH to another system. vi into a file. Press down-arrow and hold it. Response will stop after 10-15 lines. Fedora 19 64 bit fully up-to-date as of 2013-08-31 https://bugzilla.redhat.com/show_bug.cgi?id=1003181 -- -- Steve

3 4

Jump to page: