Sound in g4

2005-06-07 Thread Mike S
this is probably a totally newbie question, but I have just switched to 
debian from ubuntu, and am working on a self compiled 2.6.11 upstream 
kernel.  I compiled all the sound stuff as modules, but I do not know 
what file to edit to load them, or even how to start.  KDE reports no 
/dev/dsp on startup, and when I run lsmod it shows no snd or anything 
like that, so could someone point me in the right direction to start 
setting up sound on this thing?


--Mike S
if specs are needed this is a G4 Dual 450 (Gigabit Ethernet model) and I 
am not sure what the sound card is.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Fwd: Sound in g4

2005-06-07 Thread Albert Farrés
2005/6/7, Mike S <[EMAIL PROTECTED]>:
> this is probably a totally newbie question, but I have just switched to
> debian from ubuntu, and am working on a self compiled 2.6.11 upstream
> kernel.  I compiled all the sound stuff as modules, but I do not know
> what file to edit to load them, or even how to start.  KDE reports no
> /dev/dsp on startup, and when I run lsmod it shows no snd or anything
> like that, so could someone point me in the right direction to start
> setting up sound on this thing?
Install alsa-base and alsa-utils packages and run "alsaconf".
>
> --Mike S
> if specs are needed this is a G4 Dual 450 (Gigabit Ethernet model) and I
> am not sure what the sound card is.
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
Albert



Re: Sound in g4

2005-06-07 Thread Martin Habets
With ALSA/Debian I have the issue that I have to add snd to
/etc/modules manually. /etc/init.d/alsa won't do anything
otherwise, as /proc/asound does not exist.

Not sure if the init script is from debian or alsa. This happens
on all hardware platforms. In your case, a
 modprobe snd-powermac
should load the sound driver for you. Run alsamixer to unmute it.

Martin

On Tue, Jun 07, 2005 at 02:30:51AM +, Mike S wrote:
> this is probably a totally newbie question, but I have just switched to 
> debian from ubuntu, and am working on a self compiled 2.6.11 upstream 
> kernel.  I compiled all the sound stuff as modules, but I do not know 
> what file to edit to load them, or even how to start.  KDE reports no 
> /dev/dsp on startup, and when I run lsmod it shows no snd or anything 
> like that, so could someone point me in the right direction to start 
> setting up sound on this thing?
> 
> --Mike S
> if specs are needed this is a G4 Dual 450 (Gigabit Ethernet model) and I 
> am not sure what the sound card is.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Sound in g4

2005-06-07 Thread Mike S

Martin Habets wrote:


With ALSA/Debian I have the issue that I have to add snd to
/etc/modules manually. /etc/init.d/alsa won't do anything
otherwise, as /proc/asound does not exist.

Not sure if the init script is from debian or alsa. This happens
on all hardware platforms. In your case, a
modprobe snd-powermac
should load the sound driver for you. Run alsamixer to unmute it.

Martin

On Tue, Jun 07, 2005 at 02:30:51AM +, Mike S wrote:
 

this is probably a totally newbie question, but I have just switched to 
debian from ubuntu, and am working on a self compiled 2.6.11 upstream 
kernel.  I compiled all the sound stuff as modules, but I do not know 
what file to edit to load them, or even how to start.  KDE reports no 
/dev/dsp on startup, and when I run lsmod it shows no snd or anything 
like that, so could someone point me in the right direction to start 
setting up sound on this thing?


--Mike S
if specs are needed this is a G4 Dual 450 (Gigabit Ethernet model) and I 
am not sure what the sound card is.
   




 

I thank you martin, that cracked it, atleast for now, haven't restarted 
the computer yet, but I did modprobe snd-powermac, and that loaded all 
the snd modules, and then I changes the group id of /dev/dsp so that my 
user's group had permission to it, and long story short three logout's 
later kde finally uttered sound on startup and did not give me the 
/dev/dsp not found or /dev/dsp (permission Denied) errors.  looks like 
there's a lot of subtle little differences in debian and ubuntu, as it 
looks like I am going to have to change o lot of group id's just so I 
can access them without being root.


Thanks again,
--Mike S


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Sound in g4

2005-06-07 Thread David Pye
On Tuesday 07 June 2005 15:01, Mike S wrote:

>
> I thank you martin, that cracked it, atleast for now, haven't restarted
> the computer yet, but I did modprobe snd-powermac, and that loaded all
> the snd modules, and then I changes the group id of /dev/dsp so that my
> user's group had permission to it, and long story short three logout's
> later kde finally uttered sound on startup and did not give me the
> /dev/dsp not found or /dev/dsp (permission Denied) errors.  looks like
> there's a lot of subtle little differences in debian and ubuntu, as it
> looks like I am going to have to change o lot of group id's just so I
> can access them without being root.

No!

There's a point to these group-ids.

The correct way to allow yourself to write to /dev/dsp is to add yourself to 
the audio group, as a secondary group, *not* chmod the device.

This applies to any other devices which are owned by 'special' groups.

David

> Thanks again,
> --Mike S

-- 
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS d- s-: a-- C++ UL P L+++ E--- W++ N+ o+ K- w---
O M V- PS+ PE+ Y+ PGP t 5- X+ R- tv+ b+ DI++ D+
G+ e++ h r% y++ s-: e++
--END GEEK CODE BLOCK--


pgpGo2rz20mJ9.pgp
Description: PGP signature


Re: Sound in g4

2005-06-07 Thread Mike S

David Pye wrote:


On Tuesday 07 June 2005 15:01, Mike S wrote:

 


I thank you martin, that cracked it, atleast for now, haven't restarted
the computer yet, but I did modprobe snd-powermac, and that loaded all
the snd modules, and then I changes the group id of /dev/dsp so that my
user's group had permission to it, and long story short three logout's
later kde finally uttered sound on startup and did not give me the
/dev/dsp not found or /dev/dsp (permission Denied) errors.  looks like
there's a lot of subtle little differences in debian and ubuntu, as it
looks like I am going to have to change o lot of group id's just so I
can access them without being root.
   



No!

There's a point to these group-ids.

The correct way to allow yourself to write to /dev/dsp is to add yourself to 
the audio group, as a secondary group, *not* chmod the device.


This applies to any other devices which are owned by 'special' groups.

David

 


Thanks again,
--Mike S
   



 

ok, I need to learn to quit whinning to the lsit, I apologize for that, 
I used chown :audio on the device, which is what I think you said it was 
right, and then I did a usermod -G on myself for the audio group, which 
should have added me to the audio group, correct? Kuser reports that 
indeed I am a part of the admin and audio group, so I am guessing I did 
that right, please let me know if I did not.


--Mike S


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Sound in g4

2005-06-07 Thread Mike S

David Pye wrote:


On Tuesday 07 June 2005 15:01, Mike S wrote:

 


I thank you martin, that cracked it, atleast for now, haven't restarted
the computer yet, but I did modprobe snd-powermac, and that loaded all
the snd modules, and then I changes the group id of /dev/dsp so that my
user's group had permission to it, and long story short three logout's
later kde finally uttered sound on startup and did not give me the
/dev/dsp not found or /dev/dsp (permission Denied) errors.  looks like
there's a lot of subtle little differences in debian and ubuntu, as it
looks like I am going to have to change o lot of group id's just so I
can access them without being root.
   



No!

There's a point to these group-ids.

The correct way to allow yourself to write to /dev/dsp is to add yourself to 
the audio group, as a secondary group, *not* chmod the device.


This applies to any other devices which are owned by 'special' groups.

David

 


Thanks again,
--Mike S
   



 

Again I thank this list and the people in it for their help.  After some 
tinkering around I finally got it to work, everytime after a reboot.  I 
am not sure it is the best way, and no little to nothing about the rc 
scripts, but what I had to do was echo both snd and snd-powermac into 
the /etc/modules file to get it to work right, and play around with the 
usermod command to give myself access to various things.


I still haven't managed to get kscd to work right, but that is probably 
another group I will have to add my user to in order to be able to 
access the cdrom.  And it also has (probably) something to do with the 
same reason that things don't automount, but again, Thanks


--Mike S


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Sound in g4

2005-06-07 Thread Paul Brossier
On Tue, Jun 07, 2005 at 04:02:26PM +, Mike S wrote:
> ok, I need to learn to quit whinning to the lsit, I apologize for that, 
> I used chown :audio on the device, which is what I think you said it was 
> right, and then I did a usermod -G on myself for the audio group, which 
> should have added me to the audio group, correct? Kuser reports that 
> indeed I am a part of the admin and audio group, so I am guessing I did 
> that right, please let me know if I did not.

all you need to do is to 'adduser  ', and log in again.
you can use 'groups' to list the groups you are part of, and a similar
'deluser  ' to remove a user from a group.

on a desktop sarge install, it gives the following
$ groups
piem dialout cdrom floppy audio video plugdev

except if you installed gnome or other packages (alsa?) after creating
your user. then you will want to add yourself to the above groups. the
'plugdev' group is to have group-volume-manager automount your devices.

the group 'src' is also useful to compile kernels in /usr/src as a user.
and the 'adm' one sometimes, to read the syslogs.

bye, piem


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Sound in g4

2005-06-07 Thread Paul Brossier
On Tue, Jun 07, 2005 at 06:08:10PM +, Mike S wrote:
> Again I thank this list and the people in it for their help.  After some 
> tinkering around I finally got it to work, everytime after a reboot.  I 
> am not sure it is the best way, and no little to nothing about the rc 
> scripts, but what I had to do was echo both snd and snd-powermac into 
> the /etc/modules file to get it to work right, and play around with the 
> usermod command to give myself access to various things.

adduser is a lot simpler to use i found.

$ adduser mike audio

> I still haven't managed to get kscd to work right, but that is probably 
> another group I will have to add my user to in order to be able to 
> access the cdrom.  And it also has (probably) something to do with the 
> same reason that things don't automount, but again, Thanks

you need to be part of the plugdev group to have automount working:

$ sudo apt-get install gnome-volume-manager
$ sudo adduser $USER plugdev

bye, piem


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]