Marc is correct. I had the same problem. With the
2.4 kernel you must find
the correct modules and load them. I never did get
ALSA to work properly
under the 2.4 kernel. So, I am not the right person
to help further. I
solved my problems by moving to the 2.6 kernel,
which, as Marc
alsaconf returns:modinfo: snd: no module by that name foundmodinfo: snd: no module by that name foundmodinfo: snd: no module by that name foundUnloading ALSA sound driver modules: (none loaded).Building card database... modinfo: snd-opl3sa2: no module by that name foundmodinfo: snd-cs4236:
'cat /proc/asound/cards' returns No such file or
directory
--- marc [EMAIL PROTECTED] wrote:
That's because you don't have a soundcard assigned
to ALSA - which is
what Gstreamer was telling you earlier, but it's
best to check.
Open the Control Centre/Sound Multimedia/Sound
--- Roger Creasy [EMAIL PROTECTED] wrote:
Have you run alsaconf?
Roger
alsaconf returns:
modinfo: snd: no module by that name found
modinfo: snd: no module by that name found
modinfo: snd: no module by that name found
Unloading ALSA sound driver modules: (none loaded).
Building card
After doing this, I did as you described. The message
returned in amarok is:
[GStreamer Error] ALSA device default does not exist
--- marc [EMAIL PROTECTED] wrote:
The default gstreamer package in amarok is OSS.
Remove it - why not? -
and install the ALSA version (gstreamer0.8-alsa).
After doing this, I did as you described. The
message
returned in amarok is:
[GStreamer Error] ALSA device default does not
exist
That's pretty clear. What does
# cat /proc/asound/cards
have to say?
Sorry for the top post.
'cat /proc/asound/cards' returns No such file or
When I use XMMS's ALSA driver, I get a message that
says:
Couldn't open audio. Please check that: your
soundcard is configured properly, you have the correct
output plugin selected, and no other program is
blocking the soundcard.
...when attempting to playback.
Amarok has several engines to
I have recently been having an error with several
audio players, including amarok and xmms. Amarok
produces the following error message:
[GStreamer error] Could not open device '/dev/dsp' for
writing. ** gstosselementc(752):
gst_osselement_open_audio /root/bin system error:
Resource
I started using Debian in the past 2 months after using another Linux distro for a long time. The other distro relies on RPM for its package management, with the consequence of the user having to go through "dependency hell" on a regular basis. I have been amazed at the size of the Synaptic
Thank you sir, I will give that a try.Alvin Oga [EMAIL PROTECTED] wrote:
On Sun, 2 Oct 2005, Jeremy Merritt wrote: Windoze is installed on /dev/hda1k /dev/hda1 * 1 2433 19543041 7 HPFS/NTFSk .. that agrees with your prior statement /dev/hda2 2434 4865 19535040 f W95 Ext'd (LBA)that is windoze too
[EMAIL PROTECTED] wrote:
On Sun, 2 Oct 2005, Jeremy Merritt wrote:
Windoze is installed on /dev/hda1
k
/dev/hda1 * 1243319543041
7
HPFS/NTFS
k .. that agrees with your prior statement
/dev/hda22434486519535040
f
I was having trouble getting the grub loader to work
on my machine after having to re-install Windoze XP.
Finally I got the grub menu to come up but Debian will
not load properly.
/dev/hdb2 is the location of /root/grub
The commands for loading Debian are listed as follows:
root (hd1,1)
/root/grub should be /boot/grub, of course.
Tx
__
Yahoo! for Good
Donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
partition. I apparently overlooked this. (?)
TX for your input. Still trying to figure it out...
--- Alvin Oga [EMAIL PROTECTED] wrote:
hi ya jeremy
On Sun, 2 Oct 2005, Jeremy Merritt wrote:
more grub fun :-)
/dev/hdb2 is the location of /root/grub
i assume you have a type
PROTECTED] wrote:
Jeremy Merritt wrote:
I was having trouble getting the grub loader to
work
on my machine after having to re-install Windoze
XP.
Finally I got the grub menu to come up but Debian
will
not load properly.
/dev/hdb2 is the location of /root/grub
The commands
I have been having a problem getting my GRUB
bootloader to return on boot. No matter what I do, it
keeps going to XP. I consulted with other people on
this list and got some good input. But have run into a
dead end again. Can someone analyze these steps and
tell me what I'm doing wrong, or what I
If having multiple partitions is the problem or part
of the problem, how do I make /dev/hda2 bootable and
make the others not bootable? Is that the only thing
that needs to be done in addition to the other steps?
--- Art Edwards [EMAIL PROTECTED]
wrote:
Jeremy Merritt wrote:
I have been
Wow, what a great explanation. I have read through it,
but am going to do another to make sure it's all taken
in. Thanks.
--- Mike McCarty [EMAIL PROTECTED] wrote:
Jeremy Merritt wrote:
I have been having a problem getting my GRUB
bootloader to return on boot. No matter what I do
I need help figuring out what is going on with my
Debian / GRUB bootloader. Because of some Windoze
issues, I had to re-install XP on my machine. It
discarded the grub loader and now you can only boot to
XP from hda1. I consulted with another Debian user who
said to simply run 'grub-install
[EMAIL PROTECTED] wrote:
On Sun September 25 2005 04:32 pm, Jeremy Merritt
wrote:
I need help figuring out what is going on with my
Debian / GRUB bootloader. Because of some Windoze
issues, I had to re-install XP on my machine. It
discarded the grub loader and now you can only
boot
20 matches
Mail list logo
