users July 2013

users@lists.fedoraproject.org

270 participants
421 discussions

Re: Getting more juice from a preamp?
by Antonio Olivares 05 Jun '15

05 Jun '15

--- On Sat, 7/11/09, gilpel(a)altern.org <gilpel(a)altern.org> wrote: > From: gilpel(a)altern.org <gilpel(a)altern.org> > Subject: Getting more juice from a preamp? > To: fedora-list(a)redhat.com > Date: Saturday, July 11, 2009, 10:34 PM > I listen to sound on my system with > headphones, so I only use the preamp. > > This aft, I was watching this feature on the cause of > Beethoven's death: > > http://www.radio-canada.ca/emissions/decouverte/2008-2009/Reportage.asp?idD… > > but the sound is a bit weak. You don't miss anything, but > you feel you > have to be very attentive. Maybe they wanted to make you > feel like you're > getting deaf yourself :) > > I checked alsamixer, but volume control is maxed out. Is > there any other > control somewhere else? Anything in alsactl or pulseaudio, > for instance? > > Thnaks! > > -- Try the following: $ alsamixer -c0 then $ pavucontrol after adjusting those to your preference save your settings with $ su -c '/sbin/alsactl store' put in your password and settings should be saved for next reboot, ***unless*** an update(s) breaks your configuration and let us hope that those things don't happen :) Regards, Antonio

2 1

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

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

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

16 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

Jump to page: