still, no help on this matter? it seems that no one knows how to fix it, as it is a very very very very common issue with sound in ubuntu. or, people know how to fix it, but are too damn lazy to...
Type: Posts; User: mikebailey; Keyword(s):
still, no help on this matter? it seems that no one knows how to fix it, as it is a very very very very common issue with sound in ubuntu. or, people know how to fix it, but are too damn lazy to...
I posted this problem first back in 2008 about my old x-fi xtreme gamer pci card. i figured, hey, they should have this problem fixed, its been 4 years, but, alas, was i ever wrong.
i have a...
i am also having this problem. i have a creative labs xtremem music pci-e version. i can get the sound to work with aplay | arecord with the right variables in there, but it is horrifically lagged...
bump??
anyone with some info on this yet? its the onboard alc889a chipset.
i think i may have found a solution to your "ERROR: pdc: wrong # of devices in RAID set" issue.
short story, if the only drive in your computer is the raid array, windows creates a 100 mb partiton...
i think i may have found a solution to your "ERROR: pdc: wrong # of devices in RAID set" issue.
short story, if the only drive in your computer is the raid array, windows creates a 100 mb partiton...
Alright, just installed maverick, got the sound to work great on the 7.1 with pulseaudio. works great in movies, and everything else just wonderfully. the only thing i am stumped by is how to get the...
i find i'm having a similar problem. i have also noticed that i never actually connect to my AP at the full 54Mbps that i should be. most i have seen is 11Mbps, but over in windows same machine, same...
the wubi install is a great option really. solves the problem of ubuntu making windows running off with its ntldr and boot.ini between its legs and killing windows on the dual boot. but i had a...
I also find i have this same problem, i ran the "sudo update-apt-xapian-indexcommand", and everything worked great, but after i reloaded my repos lists the problem showed itself to be present again....