users January 2013

users@lists.fedoraproject.org

270 participants
335 discussions

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, 9 months

4
3
0 / 0

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

8
15
0 / 0

f18+gnome3: howto recording desktop with audio

by Dario Lesca

How to record via ctrl+alt+shift+r, video and audio together ? I have fount this trick: http://askubuntu.com/questions/112473/audio-not-working-for-gnome-screenc... But the command for set the "org.gnome.shell.recorder pipeline" key: > gsettings set org.gnome.shell.recorder pipeline "queue ! \ > videorate ! vp8enc quality=10 speed=2 ! mux. pulsesrc ! \ > audio/x-raw-int ! queue ! audioconvert ! vorbisenc ! \ > mux. webmmux name=mux" ... do not work, and break the recording, likely this setting is for gstreamer-0.10, bud f18 use gstreamer1-1.x, true?. This is home page of shell recorder, but there is nothing for enable audio recording. http://developer.gnome.org/shell/stable/shell-shell-recorder.html Someone have suggest? Many thanks -- Dario Lesca - sip:dario@solinos.it (Inviato dal mio Linux Fedora18+Gnome3)

11 years

6
10
0 / 0

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

2
3
0 / 0

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, 2 months

15
41
0 / 0

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

1
1
0 / 0

Grub2/Grub2 Themes Usage Issues

by Stephen Morris

Hi, I have activated the usage of the Starfield theme for grub2 in Fedora 17 and I am having issues with it. 1). Scrolling through the list of entries in the menu at boot time is horribly slow. Every time I scroll with the arrow keys the screen flashes black and it takes several seconds for the next/previous entry to be highlighted. 2). I have just upgraded from from an Nvidia Geforce 9800 GT to an Nvidia Geforce GTX 650 (this is a PCI-E 3 card plugged into a PCI-E 2 slot) and now I can see the graphics for the theme being drawn on the screen as I watch, whereas with the 9800 the screen draw was instantaneous. The issue highlighted in point 1) occurs independently of the graphics card in terms of the same thing happens with both graphics cards. 3). When I do an upgrade that upgrades the kernel the upgrade process tries to update the grub2 config and mbr but is unable to because /sbin/grubby fails with an access denied error even though I am effectively running in root mode via sudo (implemented via the wheel group). I have also tried this after switching to root mode via su but that fails with the same error. 4). Because of the error highlighted in point 3, when upgrading the kernel, I have to manual run a grub2-mkconfig and grub2-install to update grub and this process rebuilds the Starfield's Theme.txt file back to the defaults from the manual customization I have done from white/grey bold text. The black/black bold text does not work for me on the Starfield background. My system is an Asus Sabertooth 990FX R2.0 motherboard, AMD FX 4 GHz 8 core cpu, Geforce GTX 650 2 GB graphics card, 16 GB memory, 256 GB SSD (this has Win 8 and the boot partitions for Fedora 17 and Ubuntu 12.10 installed on it) and 2 2 TB Seagate hard disks, so from my perspective computing power is not an issue. What is the best way to rectify these issues? regards, Steve

11 years, 2 months

2
3
0 / 0

fedora 16, ext4 corruption

by Ian Malone

Hi, Is anyone else seeing problems with F16 ext4? I recently moved my install onto a new harddisc (which is reporting SMART is fine after running a full test) and did that by making a new ext4 fs (previously ext3) then rsyncing across. I'm now seeing occasional system 'freezes' (not hard freezes, but programs can fail to start or freeze. Yesterday the desktop completely stopped, but I was able to switch to a virtual console). dmesg reports errors to do with failing to write the journal and remounting read-only. On reboot an fsck is required, which finds some fixable problems. Obviously I'm wondering if it's the OS or the new disc. Was planning an F18 install soon which might help with one problem but not the other. Don't know if it's the 'ext4 data corruption bug' or if that's been fixed. http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ -- imalone http://ibmalone.blogspot.co.uk

11 years, 2 months

4
6
0 / 0

Enabling Wireless network without NetworkManager

by Mickey

Fedora 17 / KDE How do I enable Wireless network, NetworkManager is disabled. Wired Network is functioning normal. I'm sure that all I have to do is enable the Wireless Network. Module rt2800pci is loading and I can read MAC# of wireless card ifcfg-wlan below # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. BOOTPROTO=dhcp TYPE=Wireless HWADDR=00:15:af:e5:0b:49 GATEWAY=192.168.1.1 ONBOOT=yes USERCTL=yes PEERDNS=no IPV6INIT=no ESSID=dd-wrt MODE=Managed RATE=auto NM_CONTROLLED=no DNS2=8.8.0.0 DNS1=8.8.8.8 CHANNEL=

11 years, 3 months

7
15
0 / 0

Steam on Fedora

by Konstantin Svist

In case you missed it (I did), Steam linux beta client is now available for everyone, and there's a way to get it running on Fedora: # cd /etc/yum.repos.d # wget http://spot.fedorapeople.org/steam/steam.repo # yum install steam Million thanks to Spot!

11 years, 3 months

9
24
0 / 0

← Newer
1
2
3
4
5
6
...
34
Older →

Jump to page: