DevHeads.net

I am running fedora 12 (2.6.31.12-174.2.3.fc12.x86_64 #1 SMP) and I am
only showing pulseaudio as an output device for sound.

I have been trying to get a Sound Blaster X-Fi Xtreme Audio card working
with no luck but even when I go back to the on board chipset for audio I
only show pulseaudio as an output device. The on board chipset does
provide sound but I do not see the on board chipset as one of the
choices like I am used to seeing.

I am not even sure how to ask the question but shouldn't I see more than
just the pulseaudio choice for output devices?

Back to the subject, is pulseaudio alive?
$ ps -AH | grep pulse

------->ps -AH | grep pulse
------->1691 ?

2010/1/8 John Nissley:

Sorry, was this with or without kernel based modesetting enabled?

Thanks

John Nissley writes:

I did a clean installation of Fedora 12 from the CD today and the
first boot was fine. I could log into the computer and get the
graphical interface. I then did a yum upgrade and 500 MB later the
upgrade was finished. I then rebooted the computer and now the boot
gets stuck at the f that looks like infinity which is just before
the login screen would display. I can boot into single user mode and
also get into text mode but the graphical mode will not give me the
login screen.

I did a clean installation of Fedora 12 from the CD today and the first
boot was fine. I could log into the computer and get the graphical
interface. I then did a yum upgrade and 500 MB later the upgrade was
finished. I then rebooted the computer and now the boot gets stuck at
the f that looks like infinity which is just before the login screen
would display. I can boot into single user mode and also get into text
mode but the graphical mode will not give me the login screen.

Your X-FI seems to be loaded just fine.
Stupid question... Have you un-muted your sound card? (By default sound
is muted.)

If you did, please install alsa-utils and check if alsa-mixer sees and
can control the sound card.

If it doesn't please install pavucontrol and check that pulseaudio is
configured correctly.

- Gilboa
Not a stupid question because I spent a few hours one day troubleshooting sound and the card was muted.

This in not the case here. The card is not muted.

According to the alsa matrix its supposed to be included in alsa
1.0.21,.
...

I am running Fedora 12 and am up to date on the updates.

Thanks for the IOTOP command. It does not show me much in this case. I
do not know what is causing the disk drive light to stay on now. The
disk drive light works fine until about 5 minutes after boot up. then
the hard drive light goes crazy and stays on solid. I can not really
tell if the the hard drive is really in use but according to IOTOP it is
not being used.

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4657 (20091203) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

I have a Fedora 11 server running 2.6.30.9-96.fc11.x86_64. I recently
noticed that my hard drive light is on constantly and was wondering how
I can determine what is accessing the hard disk so much. After boot the
hard disk is acting normally for a few minutes to a few hours and then
the hard drive light is lit up constantly.

I have tried ps -ef to see if there was anything running that I do not
know about and there is not.

I had an up to date fedora 11 install that was working fine. I followed
the instructions on the wiki for doing a yum upgrade and everything
seemed to go very well until I rebooted and things hung as the graphical
interface (I use KDE) was to boot. I am able to boot into single user
mode and run level 3 and things appear to be fine. I just can not get
the graphical display.

Show us more of the output and the full command you entered!

The glibc-common.x86_64 that is installed on your machine is from
updates-testing. The one that Yum tries to pull in is from updates.
Did you forget to enable updates-testing when trying to install qt-devel?

I went down that same route also. I had the fedora-updates.repo enabled so I
decieded to enable the fedora-updates-testing.repo.

On Fri, 04 Sep 2009 13:13:29 -0500

I have this problem during updates when there is a component on the
system that needs an older version of something yum wants to update.

I am trying to compile an application on a Fedora 11 computer I have but
keep getting a missing dependency error when trying to install qt-devel.
Here is the error:
--> Processing Dependency: glibc-common = 2.10.1-4 for package:
glibc-2.10.1-4.i686
---> Package nss-softokn-freebl.i586 0:3.12.3.99.3-2.11.4.fc11 set to be
updated
--> Finished Dependency Resolution
glibc-2.10.1-4.i686 from updates has depsolving problems
--> Missing Dependency: glibc-common = 2.10.1-4 is needed by package
glibc-2.10.1-4.i686 (updates)
Error: Missing Dependency: glibc-common = 2.10.1-4 is needed by package