users September 2013

users@lists.fedoraproject.org

185 participants
244 discussions

Problems with 3COM 3C900Combo
by Christian Moller 05 Jun '15

05 Jun '15

Hi all Fedora users, I have just joined this list. I am running the latest Fedora but I can't get my 3C900Combo networking card to work. I can see that the card is installed but no IP-address is asigned to it and I can't set it. So I think that there is a bug in that driver. Any other user out there who have a solution for this? Best regards and thanks, Christian

2 1

RAGE XL Framebuffer
by Yanick Quirion 05 Jun '15

05 Jun '15

Hi all I know that is not a specific question about Fedora, but I can't find answer on the kernel mailing list. Is somebody having server with integrated ATI RAGE XL video card? Is it possible to patch the kernel to support this video card? If I add VGA=791 in my grub.conf, I will have a resolution of 1024x768 which is good, but the display is very slow (especially when the screen is scrolling). If I use I this: "video=aty128fb:1024x768@70" it will not work. I'm using kernel 2.4.22 but I will try 2.6.0-test11 today. If somebody has a patch, a link or anything else that can help me, it will be appreciated. Thanks for your help. Regards, ----------- Yanick Quirion Administrateur Réseau/Network Manager NEOKIMIA INC. Institut de Pharmacologie de Sherbrooke 3e étage (Édifice Z5) 3001 12e avenue Nord Sherbrooke, Québec CANADA J1H 5N4 Tél.: +1 819 820-6040 Direct: +1 819 820-6855 Fax.: +1 819 820-6841 email: Yanick.Quirion(a)neokimia.com

2 1

Soundblaster
by Antonio Montagnani 05 Jun '15

05 Jun '15

I have two similar PC (old Pentium but workin fine) In Pc no.1 I upgraded from RH8 to Fedora and it went fine: Soundblaster is working fine In Pc no.2 I made a fresh installation but in redhat-sound-config Fedora doesn't see any card, that was working on Redhat 9 after soundconfig... Where is the trick?? I assume that my Sounblaster is an old 16...but fine on a router/firewall. Tnx Antonio

4 6

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

Suspension problem last 2 days
by Timothy Murphy 18 Oct '13

18 Oct '13

I've been having a problem on my Thinkpad T61 for the last 2 days. In fact since "yum update" installed kernel-PAE-3.11.1-200.fc19.i686, though that is probably a coincidence. The problem is that when the laptop lid is closed and then opened later the machine is in a confused state. For example it is impossible to shutdown the machine except by pressing the power button for 10 seconds. I just wondered if anyone else has had similar symptoms recently? These are some of the entries in /var/log/messages following "Lid opened": -------------------------------------- Sep 21 21:22:37 rose systemd-logind[358]: Lid opened. Sep 21 21:22:37 rose systemd[1]: Caught <SEGV>, dumped core as pid 1590. Sep 21 21:22:37 rose systemd[1]: Freezing execution. Sep 21 21:22:37 rose kernel: [ 1026.161712] video LNXVIDEO:01: Restoring backlight state Sep 21 21:22:37 rose systemd-sleep[1511]: System resumed. Sep 21 21:22:37 rose systemd-cgroups-agent[1596]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused ... Sep 21 21:23:10 rose kdm[371]: X server for display :0 terminated unexpectedly Sep 21 21:23:12 rose dbus-daemon[362]: dbus[362]: [system] Failed to activate service 'net.reactivated.Fprint': timed out Sep 21 21:23:12 rose dbus-daemon[362]: dbus[362]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Sep 21 21:23:12 rose dbus[362]: [system] Failed to activate service 'net.reactivated.Fprint': timed out Sep 21 21:23:12 rose dbus[362]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Sep 21 21:23:24 rose kdm: :0[1650]: Fatal X server IO error: Interrupted system call Sep 21 21:23:46 rose systemd-cgroups-agent[1691]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused Sep 21 21:39:55 rose chronyd[335]: Selected source 149.157.192.251 ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ -------------------------------------- -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

4 9

Fedora 19, KDE 4.11.1, no login screen
by Andrea 17 Oct '13

17 Oct '13

Hi, I've just updated F19 and after reboot I do not get the usual kdm login screen. The graphic screen with the F stays there forever. I can login in text mode and run 'startx' and I get to the normal KDE session. Looking at the logs I only noticed [FAILED] Wait for Plymouh Boot Screen to quit and in /var/log/messages there is something about Sep 21 15:24:35 localhost kdm[335]: plymouth --ping -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth is running ... Sep 21 15:24:35 localhost kdm[335]: plymouth deactivate -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth --has-active-vt -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth should quit when server starts Sep 21 15:24:36 localhost kdm[335]: plymouth is active on VT 1, reusing for :0 Sep 21 15:24:36 localhost kdm[335]: X server startup timeout, terminating Sep 21 15:24:36 localhost kdm[335]: X server for display :0 cannot be started, session disabled any idea?

6 10

What happened to my printer!?!
by Alan Evans 10 Oct '13

10 Oct '13

Hello all, Sometime in the last couple of weeks, I lost my ability to print to the office printer. If I check (KDE) System Settings, the printer's status reads, "Paused - 'Unable to connect to CIFS host after (tried 3 times)'". Everybody else can still use this printer, and there have been no major network reconfiguration events recently. I can't figure out how to bring this back online. I tried to simply re-add the long-existing printer again, but the "Add a New Printer" dialog won't let me browse the network for any printers at all. The [Browse] button under "Windows Printer via SAMBA" is greyed out, so I would have to type the URI by hand. But the URI is correct in the configuration of the current, non-working, printer, as far as I know. Is there any way to figure out why the current printer is offline, beyond "Unable to connect"? Not being able to print is really messing with my workflow. -Alan

5 7

F19:personal file sharing doesn't work
by Antonio M 05 Oct '13

05 Oct '13

when I want to share files in a easy way, I was used to Personal Files Sharing. Now I enabled it on my F19 systems (both in Gnome and Mate) but something seems wrong: When I open Resources/Network I see shares of computers A and B but: working on A clicking on B I get : Impossible to mount position Error HTTP: Cannot connect to destination (PCdesktop.local) Clicking on A (per quanto abbia senso) I get: Impossible to mount the position Error HTTP: Internal Server Error Same if I work on B any hint?? googling around didn't give me any clue Tnx -- Antonio M Skype: amontag52 Linux Fedora F19(Schroedinger's cat) on Acer 5720 http://lugsaronno.altervista.org http://www.campingmonterosa.com

3 3

Jump to page: