'Twas brillig, and sibu xolo at 22/09/10 02:04 did gyre and gimble:
iii---I I recompiled kdemultimedia also. On restart I obtained sound on
the second login but none subsequenty and cdrom sound is practicly mute
~
a tenth as loud as a hungry mosquito.
FWIW, unless you are wroking
On Monday 20 September 2010 08:37:02 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 20/09/10 00:41 did gyre and gimble:
On Tuesday 14 September 2010 13:58:08 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 14/09/10 13:33 did gyre and gimble:
On Monday 13 September 2010 11:59:14
'Twas brillig, and sibu xolo at 21/09/10 11:12 did gyre and gimble:
I managed to fix the problem. It was a udev problem. After I updated to
udev-162, the /dev/cdrom and /dev/dvd symlinks to my ide cdrom disappeared.
I used a simple udev rule to re-create these and now cdrom sound plays
On Tuesday 21 September 2010 12:28:04 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 21/09/10 11:12 did gyre and gimble:
I managed to fix the problem. It was a udev problem. After I updated to
udev-162, the /dev/cdrom and /dev/dvd symlinks to my ide cdrom
disappeared. I used a
'Twas brillig, and sibu xolo at 20/09/10 00:41 did gyre and gimble:
On Tuesday 14 September 2010 13:58:08 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 14/09/10 13:33 did gyre and gimble:
On Monday 13 September 2010 11:59:14 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 13/09/10
On Tuesday 14 September 2010 13:58:08 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 14/09/10 13:33 did gyre and gimble:
On Monday 13 September 2010 11:59:14 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 13/09/10 11:10 did gyre and gimble:
First of all thanks (or shall I say
On Monday 13 September 2010 11:59:14 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 13/09/10 11:10 did gyre and gimble:
First of all thanks (or shall I say 'kallu kalay') for the help.
I'm not sure why udev-detect would cause problems. I would suggest to
double check your udev setup
'Twas brillig, and sibu xolo at 14/09/10 13:33 did gyre and gimble:
On Monday 13 September 2010 11:59:14 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 13/09/10 11:10 did gyre and gimble:
First of all thanks (or shall I say 'kallu kalay') for the help.
I'm not sure why udev-detect
On 09/12/10 19:04, sibu xolo wrote:
pcm.pulse {
type pulse
}
ctl.pulse {
type pulse
}
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
Try the following, it should allow alsamixer to control the default device
pcm.pulse {
type pulse
}
ctl.pulse {
type
'Twas brillig, and sibu xolo at 13/09/10 02:04 did gyre and gimble:
a) I am using system5 init and alsamixer refuses to start on the CLI at run-
level 3 reporting
pulseaaudio' connection refused (or somesuch) but...
I guess PA cannot start on the CLI for some reason. alsamixer or aplay
On Monday 13 September 2010 09:28:22 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 13/09/10 02:04 did gyre and gimble:
a) I am using system5 init and alsamixer refuses to start on the CLI at
run- level 3 reporting
pulseaaudio' connection refused (or somesuch) but...
I guess PA
'Twas brillig, and sibu xolo at 13/09/10 11:10 did gyre and gimble:
On Monday 13 September 2010 09:28:22 Colin Guthrie wrote:
'Twas brillig, and sibu xolo at 13/09/10 02:04 did gyre and gimble:
a) I am using system5 init and alsamixer refuses to start on the CLI at
run- level 3 reporting
Greetings,
I am new to this list. I have a computer with these:
-cpu-amd64-2 cores, dsp: HDA NVidia/Realtek ALC662 rev1
-o/s cblfs-linux 64-bit kernel-2.6.35.4, xorg-7.5 kde-4.4.5, udev-147
-audio-progs: alsa-1.0.23. pulse-0.9.21 (default configurations in
/etc/pulse)
13 matches
Mail list logo