Lost audio on headphones (F9)
by Andre Costa
Hi,
my desktop computer has one of those front headphones connectors, and it
always worked (always = since Fedora8), playing the same audio that goes to
the front speakers. I tried it today and it doesn't work anymore, my guess
is that some of the recent updates might have changed something on audio
config (I know hardware is ok because system is dual-boot, and headphones
work on XP). Front speakers are working as expected.
I tried playing around with PulseAudio settings, but didn't get anywhere
I know this is a lame call for help, but I don't even know what kind of info
I should provide. Here's something that might help:
# cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xa3220000 irq 22
System is running Fedora 9 with latest updates.
Any help will be appreciated. Let me know what kind of additional info I
should provide.
Regards,
Andre
15 years, 4 months
Virtualizing XP with dual boot FC10/XP
by Hal Meyer
I have FC10 and Windows dual booted on my PC and would like to
virtualize XP with KVM.
I want to be able to both boot to XP and also virtualize it in FC10
(obviously not at the same time).
When I try to install a new virtual machine the process wants to install
XP from the CD. Is there a way to just point to the XP partition on the
disk?
Vmware workstation claims to be able to do this but there seem to be
other issues with vmware and FC10.
Thanks,
Hal
15 years, 4 months
VMware Server 2.0, selinux, and F10
by Christopher A Williams
I had promised to do this and post my results a week ago and got
thoroughly tied up over the holidays - sorry about that. It was a good
Christmas for us though! :)
So - I did get around to loading up a server with the latest version of
F10 (32-bit in this case) to run the 32-bit version of VMware Server 2.0
(build 122956) to try and answer the burning question: Does selinux need
to be disabled for VMware Server to run properly on F10?
I know the inpatient out there can't wait to read the whole post, so
here's the answer:
Yes.
According to our testing (a friend of mine who also frequents this list
was here too), the current version of VMware Server DOES NOT RUN on F10
(32-bit) unless selinux is DISABLED. Permissive mode doesn't cut it - it
still causes VMware Server to not run.
Here are the details:
Server: "Whitebox" Supermicro 1U chassis, dual 2.4GHz Pentium Xeon
processors, 4GB RAM, Dual Gig-E NICs, dual 250GB IDE drives
OS: F10 32-bit, with all patches as of 12-28-08
Kernel: 2.6.27.9-159.fc10 (PAE version - required to see the full 4GB)
We loaded a fresh copy F10 with all of the required development tools
and supporting stuff VMware Server needs to compile, and left selinux in
its default (enforcing) mode and targeted policy. The system was
intentionally updated with all of the latest available patches. After
rebooting (kernel update that included a switch to the PAE kernel), we
then installed VMware Server from the RPM via Package Kit. The initial
RPM install went as expected with no errors or issues beyond the warning
that the RPM is not signed (Request to VMware: Please, PLEASE make sure
that you always sign your RPMs!).
Next up was to configure the system. We fired up a terminal window,
switched user to root, and then launched vmware-config.pl as normal. The
script properly found everything it needed, set up the virtual networks,
and compiled all of the modules against the PAE kernel with no errors at
all. All of the services reported in as having started successfully when
the script exited, which was when the trouble started.
We immediately picked up an selinux error saying that one of the modules
required the ability to use text relocation. No big deal here, which is
why I don't remember off hand which module committed the offense. I'll
go back and pull it up next chance - I'm on a different system right
now. The selinux troubleshooter gave us the required command to address
this issue, so we fixed the problem and off we went.
...Or so we thought.
It seems that something else in selinux is interfering with a new VMware
Server 2.0 service called VirtualMachines. I'm not sure what the problem
is, how it happens, or why. What happens is that you can launch Firefox
to talk to VMware server (http://localhost:8222 in this case) and get
the VMware Server login page. However, from there you are unable to
login. The system times out with a message basically saying that
communication with the back-end server processes has been lost. Further
checking (service vmware status) shows that several VMware Server
services are actually NOT running.
Upon trying to restart the vmware services (service vmware restart), we
see that the VirtualMachines service has failed. There are no errors I
can see, and nothing in dmesg out of the ordinary.
Next, we placed selinux into permissive mode to see if anything might
pop up or change, and then rebooted the system. We saw exactly the same
behavior from VMware Server as before when selinux was in enforcing
mode.
Finally, we disabled selinux altogether and rebooted once more. This
time, VMware Server came up and ran flawlessly. In fact, it was
impressively fast given the age of the hardware.
Just for grins, we then completely erased VMware Server, rebooted, and
double-checked to make sure everything about it was completely gone from
the system. We then re-installed it using the exact same procedure as
before. VMware Server installed and ran flawlessly. In fact, just to be
sure again, we rebooted the server one more time. Again VMware Server
came up and ran without issues.
Thus, in our testing of this, it is clear there are multiple issues with
VMware Server and selinux. One of the issues is that a specific module
requires text relocation, which is easily solved. The other issue is
going to be a little more difficult to troubleshoot, but clearly there
is something that conflicts between selinux and one of the new VMware
Server services, and the only way to get around it at this point is to
disable selinux.
I'll have the system handy for the next day or so to do some additional
testing, but then I have to put it back into production. Let me know
what specifics I should look for next to find the source of the problem.
Cheers,
Chris
--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.
--Socrates
15 years, 4 months
Default route not set on boot up
by awrobinson-ml＠nc.rr.com
After installing F10, when I power up my laptop, the default route does
not get set. I have a "GATEWAY=192.168.1.1" statement in both the
ifcfg-wlan0 file and the /etc/sysconfig/network file. 'netstat -nr'
shows no gateway until I run 'route add default gw 192.168.1.1'. This is
the first time that I put my network setup under the control of Network
Manager. I don't know if that has anything to do with this. I know I
could code the default route in rc.local or something like that, but I
would rather have it work correctly. Any ideas?
Thanks!
Andrew Robinson
15 years, 5 months
Need advice on music management software
by Konstantin Svist
Hi all,
I have a music collection that's being merged from several
computers/devices onto a single one (which doubles as a media
center/HTPC). Problem is, I'd like to merge the duplicate files (and
there are plenty) but still need to be able to sync between this central
system and the other computers (all running Fedora, btw).
User 1 has a laptop with Amarok and syncs her music to an iPod (listens
on both laptop and iPod)
User 2 also uses Amarok, but no external devices
User 3 uses a car mp3 player only (wirelessly synced to her laptop using
special software...)
Everyone wants all the music on the HTPC, though everyone will keep a
copy of their own subsection of the collection on their own devices.
Nobody expects to sync to the HTPC from anything other than laptops,
though iPod integration would be a bonus.
Would be nice to listen to music from HTPC, and upon hearing a song I
like to quickly mark it to send it to my laptop at the next sync :)
Crazy setup, I know
Any suggestions?
15 years, 5 months
F10 Strange Audio Errors
by Sean Bruno
I'm seeing strange audio issues(skipping and buffering) when playing
audio from Amarok(1.4), Audacity and from the video game Quake Wars.
I have an on-board sound card:
00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97
Audio Controller (rev a2)
And a USB Turntable:
Bus 002 Device 005: ID 08bb:2900 Texas Instruments Japan PCM2900 Audio
Codec
Periodically, while Amarok(1.4) is playing back I see:
Dec 25 16:48:45 localhost pulseaudio[15582]: module-alsa-sink.c: ALSA
woke us up to write new data to the device, but there was actually
nothing to write! Most likely t
his is an ALSA driver bug. Please report this issue to the PulseAudio
developers.
When Audacity is recording from the USB turntable I see:
ALSA sound/usb/usbaudio.c:351: frame 0 active: -70
And when Quake Wars is running, I see the following in the console
output:
snd_pcm_readi failed: Input/output error
snd_pcm_readi failed: Input/output error
snd_pcm_readi failed: Input/output error
Any ideas as to what is going on here?
Sean
15 years, 5 months
F10 and Pulseaudio
by Niels Weber
Hi all,
what is the state of Pulseaudio in F10?
On my previous installation (F8) I disabled PA after a short test as
there where to many problems with it. On my fresh install of F10 I
have it currently enabled, thinking that it should be more mature by
now.
At first it had the wrong soundcard as a default device, this was
easily changed and is no real bug (although perhaps the installer
should ask which soundcard should be used if there is more than one).
Rhythmbox and mplayer now have sound (but only stereo instead of 5.1
it seems), so that's fine.
All games have no sound though, even those installed from the Fedora
repository (for example "Battle for Wesnoth").
I can understand if third-party software still has problems with PA,
but shouldn't at least the games that are shipped with the
distribution work with the default sound setup?
How to fix this? Uninstall PA again?
Niels
15 years, 5 months
Jackd Problems -- alsa_pcm: xrun of at least 1227061150613.504 msecs
by Jonathan Ryshpan
In the past I've never had any problems running jackd. Now I'm getting
a very large number of messages reading:
**** alsa_pcm: xrun of at least 1227061150613.504 msecs
I'm running F9 on an x86_64 system with all updates installed.
Pulseaudio is not running. Jackd is started via qjackctl. No past
problems with audio beyond the usual conflicts between pulseaudio and
firefox.
Questions:
(1) What exactly does this message mean? An "xrun" is a buffer under-
or over-run -- but what does the time interval represent?
(2) Whatever the time interval means, it looks rather large.
1227061150613.504 msec is many days (or maybe years if msec means
millisec and not microsec) This looks like a misconfiguration of some
kind or a missing component. Any idea what it might be?
Here is the start of the qjackctl log of the session.
18:53:38.317 Patchbay deactivated.
18:53:38.364 Statistics reset.
18:53:38.566 ALSA connection graph change.
18:53:38.752 ALSA connection change.
18:53:41.050 Startup script...
18:53:41.050 artsshell -q terminate
18:53:42.247 Startup script terminated with exit status=256.
18:53:42.261 JACK is starting...
18:53:42.262 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p1024 -n2
18:53:42.267 JACK was started with PID=3423.
jackd 0.109.2
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|
32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2
periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback
**** alsa_pcm: xrun of at least 1227061150613.504 msecs
**** alsa_pcm: xrun of at least 1227061150613.504 msecs
**** alsa_pcm: xrun of at least 1227061150613.504 msecs
**** alsa_pcm: xrun of at least 1227061150613.504 msecs
...
15 years, 5 months
