Re: ALSA busted in 2.5.69

Re: ALSA busted in 2.5.69

[walt]

Torrey Hoffman wrote:
> On Fri, 2003-05-09 at 01:09, Giuliano Pochini wrote:
> 
>>On 08-May-2003 Torrey Hoffman wrote:
>>
>>>ALSA isn't working for me in 2.5.69.  It appears to be because
>>>/proc/asound/dev is missing the control devices.
> 
> ...
> 
>>If you are not using devfs, you need to create the devices. There is a
>>script in the ALSA-driver package to do that. Otherwise I can't help
>>you because I never tried devfs and linux 2.5.x.
> 
> 
> No.  /dev/snd is a symbolic link to /proc/asound/dev,
> and that symbolic link was created by the script you mention.
> (I am not using devfs.)
> 
> So the missing "/dev/snd/controlC0" should actually be created
> by the ALSA modules in the proc filesystem as
> "/proc/asound/dev/controlC0".  But only the timer device is there.

Warning:  I'm no expert on any of this -- but -- I'm listening to sound
right now using 2.5.69 (with devfs) and this is what I see:

There are NO symlinks from /dev to /proc.  None.

/dev/snd and /dev/sound are real directories -- neither is a symlink.

#ls -l /dev/snd
total 0
crw-------    1 wa1ter   audio    116,   0 Dec 31  1969 controlC0
crw-------    1 wa1ter   audio    116,  32 Dec 31  1969 controlC1
crw-------    1 wa1ter   audio    116,  64 Dec 31  1969 controlC2
crw-------    1 wa1ter   audio    116,  96 Dec 31  1969 controlC3
crw-------    1 wa1ter   audio    116, 128 Dec 31  1969 controlC4
crw-------    1 wa1ter   audio    116, 160 Dec 31  1969 controlC5
crw-------    1 wa1ter   audio    116, 192 Dec 31  1969 controlC6
crw-------    1 wa1ter   audio    116, 224 Dec 31  1969 controlC7
crw-------    1 wa1ter   audio    116,  24 Dec 31  1969 pcmC0D0c
crw-------    1 wa1ter   audio    116,  16 Dec 31  1969 pcmC0D0p
crw-------    1 wa1ter   audio    116,  25 Dec 31  1969 pcmC0D1c
crw-------    1 wa1ter   audio    116,  17 Dec 31  1969 pcmC0D1p
crw-------    1 wa1ter   audio    116,   1 Dec 31  1969 seq
crw-------    1 wa1ter   audio    116,  33 Dec 31  1969 timer

#ls -l /dev/sound
total 0
crw-------    1 wa1ter   audio     14,  12 Dec 31  1969 adsp
crw-------    1 wa1ter   audio     14,   4 Dec 31  1969 audio
crw-------    1 wa1ter   audio     14,   3 Dec 31  1969 dsp
crw-------    1 wa1ter   audio     14,   0 Dec 31  1969 mixer
crw-------    1 wa1ter   audio     14,   1 Dec 31  1969 sequencer
crw-------    1 wa1ter   audio     14,   8 Dec 31  1969 sequencer2

#ls -l /dev/dsp
lr-xr-xr-x    1 root     root            9 May  9 10:33 /dev/dsp -> sound/dsp
#ls -l /dev/adsp
lr-xr-xr-x    1 root     root           10 May  9 10:33 /dev/adsp -> sound/adsp


Seems to me that any symlinks to /proc don't really belong in /dev.
Any opinions to the contrary?  (Remember:  my sound is working just fine.)

Re: ALSA busted in 2.5.69

[Andy Pfiffer]

On Fri, 2003-05-09 at 11:14, walt wrote:
> Torrey Hoffman wrote:
> > On Fri, 2003-05-09 at 01:09, Giuliano Pochini wrote:
> > 
> >>On 08-May-2003 Torrey Hoffman wrote:
> >>
> >>>ALSA isn't working for me in 2.5.69.  It appears to be because
> >>>/proc/asound/dev is missing the control devices.
> > ...
> >>If you are not using devfs, you need to create the devices. There is a
> >>script in the ALSA-driver package to do that. Otherwise I can't help
> >>you because I never tried devfs and linux 2.5.x.
> > 
> > No.  /dev/snd is a symbolic link to /proc/asound/dev,
> > and that symbolic link was created by the script you mention.
> > (I am not using devfs.)

I'm not using devfs, and I've had no luck getting ALSA to work on my
i810-audio system.  OSS works fine.

Is there a step-by-step writeup available for morons like me that
haven't gotten ALSA working?

Thanks,
Andy

Re: ALSA busted in 2.5.69

[David van Hoose]

Andy Pfiffer wrote:
> On Fri, 2003-05-09 at 11:14, walt wrote:
> 
>>Torrey Hoffman wrote:
>>
>>>On Fri, 2003-05-09 at 01:09, Giuliano Pochini wrote:
>>>
>>>
>>>>On 08-May-2003 Torrey Hoffman wrote:
>>>>
>>>>
>>>>>ALSA isn't working for me in 2.5.69.  It appears to be because
>>>>>/proc/asound/dev is missing the control devices.
>>>
>>>...
>>>
>>>>If you are not using devfs, you need to create the devices. There is a
>>>>script in the ALSA-driver package to do that. Otherwise I can't help
>>>>you because I never tried devfs and linux 2.5.x.
>>>
>>>No.  /dev/snd is a symbolic link to /proc/asound/dev,
>>>and that symbolic link was created by the script you mention.
>>>(I am not using devfs.)
> 
> 
> I'm not using devfs, and I've had no luck getting ALSA to work on my
> i810-audio system.  OSS works fine.
> 
> Is there a step-by-step writeup available for morons like me that
> haven't gotten ALSA working?

I have ALSA working under 2.4.21-rc1 using Erik's kernel patch, but I 
cannot get it to work under 2.5.69. I don't know what's wrong. I get 
Audio from my CD-ROM since it is connected to my sound card, but I get 
no sound from the Arts sound server in KDE. I get no errors and no warnings.
I don't understand how it can't work. I'm thinking that the OSS 
emulation is broken. The ALSA version I have for 2.4 is 0.9.2. 0.9.3a is 
in 2.5.69, right? Have any bugs been reported to the ALSA people?

Regards,
David

Re: ALSA busted in 2.5.69

[Norbert Wolff]

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

On 09 May 2003 12:12:10 -0700
Andy Pfiffer <andyp@osdl.org> wrote:

> I'm not using devfs, and I've had no luck getting ALSA to work on my
> i810-audio system.  OSS works fine.
> 
> Is there a step-by-step writeup available for morons like me that
> haven't gotten ALSA working?

Hi Andy !

The Problem seems to be that ALSA has moved their devices some weeks ago.
In the alsa-driver-0.9.3a-Package (ftp://ftp.alsa-project.org) is a script
called snddevices (attached) which creates the needed devices and links.

Execute it as root and all should be fine ...

Maybe this Script should be distributed with the Kernel too ?

Regards,

	Norbert


-- 
 Norbert Wolff
 OpenPGP-Key:
   http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF13BD6F6


[-- Attachment #2: snddevices --]
[-- Type: application/octet-stream, Size: 3611 bytes --]

#!/bin/bash

MAJOR=116
OSSMAJOR=14
MAX_CARDS=4
PERM=666
STATIC=0
OWNER=root.root

if [ "`grep -w -E "^audio" /etc/group`x" != x ]; then
  PERM=660
  OWNER=root.audio
fi

function create_odevice () {
  rm -f $1
  echo -n "Creating $1..."
  mknod -m $PERM $1 c $OSSMAJOR $2
  chown $OWNER $1
  echo " done"
}

function create_odevices () {
  tmp=0
  tmp1=0
  rm -f $1 $1?
  echo -n "Creating $1?..."
  while [ $tmp1 -lt $MAX_CARDS ]; do
    minor=$[ $2 + $tmp ]
    mknod -m $PERM $1$tmp1 c $OSSMAJOR $minor
    chown $OWNER $1$tmp1
    tmp=$[ $tmp + 16 ]
    tmp1=$[ $tmp1 + 1 ]
  done
  echo " done"
}

function create_device1 () {
  rm -f $1
  minor=$2
  echo -n "Creating $1..."
  mknod -m $PERM $1 c $MAJOR $minor
  chown $OWNER $1
  echo " done"
}

function create_devices () {
  tmp=0
  rm -f $1 $1?
  echo -n "Creating $1?..."
  while [ $tmp -lt $MAX_CARDS ]; do
    minor=$[ $tmp * 32 ]
    minor=$[ $2 + $minor ]
    mknod -m $PERM "${1}C${tmp}" c $MAJOR $minor
    chown $OWNER "${1}C${tmp}"
    tmp=$[ $tmp + 1 ]
  done
  echo " done"
}

function create_devices2 () {
  tmp=0
  rm -f $1 $1?
  echo -n "Creating $1??..."
  while [ $tmp -lt $MAX_CARDS ]; do
    tmp1=0
    while [ $tmp1 -lt $3 ]; do
      minor=$[ $tmp * 32 ]
      minor=$[ $2 + $minor + $tmp1 ]
      mknod -m $PERM "${1}C${tmp}D${tmp1}" c $MAJOR $minor
      chown $OWNER "${1}C${tmp}D${tmp1}"
      tmp1=$[ $tmp1 + 1 ]
    done
    tmp=$[ $tmp + 1 ]
  done
  echo " done"
}

function create_devices3 () {
  tmp=0
  rm -f $1 $1?
  echo -n "Creating $1??$4..."
  while [ $tmp -lt $MAX_CARDS ]; do
    tmp1=0
    while [ $tmp1 -lt $3 ]; do
      minor=$[ $tmp * 32 ]
      minor=$[ $2 + $minor + $tmp1 ]
      mknod -m $PERM "${1}C${tmp}D${tmp1}${4}" c $MAJOR $minor
      chown $OWNER "${1}C${tmp}D${tmp1}${4}"
      tmp1=$[ $tmp1 + 1 ]
    done
    tmp=$[ $tmp + 1 ]
  done
  echo " done"
}

if test "$1" = "-?" || test "$1" = "-h" || test "$1" = "--help"; then
  echo "Usage: snddevices [max]"
  exit
fi

if test "$1" = "max"; then
  DSP_MINOR=19
fi

# OSS (Lite) compatible devices...

if test $OSSMAJOR -eq 14; then
  create_odevices /dev/mixer		0
  create_odevice /dev/sequencer		1
  create_odevices /dev/midi		2
  create_odevices /dev/dsp		3
  create_odevices /dev/audio		4
  create_odevice /dev/sndstat		6
  create_odevice /dev/music		8
  create_odevices /dev/dmmidi		9
  create_odevices /dev/dmfm		10
  create_odevices /dev/amixer		11	# alternate mixer
  create_odevices /dev/adsp		12	# alternate dsp
  create_odevices /dev/amidi		13	# alternate midi
  create_odevices /dev/admmidi		14	# alternate direct midi
  # create symlinks
  ln -svf /dev/mixer0 /dev/mixer
  ln -svf /dev/midi0 /dev/midi
  ln -svf /dev/dsp0 /dev/dsp
  ln -svf /dev/audio0 /dev/audio
  ln -svf /dev/music /dev/sequencer2
  ln -svf /dev/adsp0 /dev/adsp
  ln -svf /dev/amidi0 /dev/amidi
fi

# New devices (obsolete now)...

mv -f /dev/sndstat /dev/1sndstat
rm -f /dev/snd*
mv -f /dev/1sndstat /dev/sndstat
if [ -d /dev/snd ]; then
  rm -f /dev/snd/*
  rmdir /dev/snd
fi
if [ $STATIC -gt 0 ]; then
  mkdir -p /dev/snd
  create_devices  /dev/snd/control	0
  create_device1  /dev/snd/seq		1
  create_device1  /dev/snd/timer	33
  create_devices2 /dev/snd/hw		4	4
  create_devices2 /dev/snd/midi		8	8
  create_devices3 /dev/snd/pcm		16	8	p
  create_devices3 /dev/snd/pcm		24	8	c
fi

# New dynamic sound device filesystem

if [ $STATIC -le 0 ]; then
  echo "ALSA dynamic sound device filesystem"
  ln -sfv /proc/asound/dev /dev/snd
fi

# Loader devices

echo "ALSA loader devices"
rm -f /dev/aload*
create_devices  /dev/aload		0
create_device1  /dev/aloadSEQ		1

Re: ALSA busted in 2.5.69

[David Ford]

Shrug :)

I use devfs, all is magic.  All is [nearly always] correct.

David

Norbert Wolff wrote:

>On 09 May 2003 12:12:10 -0700
>Andy Pfiffer <andyp@osdl.org> wrote:
>
>  
>
>>I'm not using devfs, and I've had no luck getting ALSA to work on my
>>i810-audio system.  OSS works fine.
>>
>>Is there a step-by-step writeup available for morons like me that
>>haven't gotten ALSA working?
>>    
>>
>
>Hi Andy !
>
>The Problem seems to be that ALSA has moved their devices some weeks ago.
>In the alsa-driver-0.9.3a-Package (ftp://ftp.alsa-project.org) is a script
>called snddevices (attached) which creates the needed devices and links.
>
>Execute it as root and all should be fine ...
>
>Maybe this Script should be distributed with the Kernel too ?
>
>Regards,
>
>	Norbert
>
>
>  
>

[RFC] devfs [was Re: ALSA busted in 2.5.69]

[David van Hoose]

David Ford wrote:
> Shrug :)
> 
> I use devfs, all is magic.  All is [nearly always] correct.

Are there any compatibility issues in 2.4 while using devfs under 2.5? 
I'm looking into it, but I'd like to hear that there are no problems 
before I jump into using it.
I would love to hear comments from anyone using devfs. Good or bad.

Thanks,
David

Re: ALSA busted in 2.5.69

[David van Hoose]

Norbert Wolff wrote:
> On 09 May 2003 12:12:10 -0700
> Andy Pfiffer <andyp@osdl.org> wrote:
> 
> 
>>I'm not using devfs, and I've had no luck getting ALSA to work on my
>>i810-audio system.  OSS works fine.
>>
>>Is there a step-by-step writeup available for morons like me that
>>haven't gotten ALSA working?
> 
> 
> Hi Andy !
> 
> The Problem seems to be that ALSA has moved their devices some weeks ago.
> In the alsa-driver-0.9.3a-Package (ftp://ftp.alsa-project.org) is a script
> called snddevices (attached) which creates the needed devices and links.
> 
> Execute it as root and all should be fine ...
> 
> Maybe this Script should be distributed with the Kernel too ?

Will I have any problems if I run this script even though I'm using ALSA 
0.9.2 with 2.4.21-rc2 and whatever version is in 2.5.69-bk4?

Thanks,
David

Re: [RFC] devfs [was Re: ALSA busted in 2.5.69]

[David Ford]

I've used devfs for years.  A few people here and there gripe about it, 
my only gripe about it are drivers that don't [haven't yet] been updated 
to use it.  In 2.5 those are rare.  As to 2.4 vs 2.5, there aren't too 
many user visible changes and I think most of the new things for devfs 
(user visible) in 2.5 are also in 2.4.

My vote: devfs is _great_

David

David van Hoose wrote:

> David Ford wrote:
>
>> Shrug :)
>>
>> I use devfs, all is magic.  All is [nearly always] correct.
>
>
> Are there any compatibility issues in 2.4 while using devfs under 2.5? 
> I'm looking into it, but I'd like to hear that there are no problems 
> before I jump into using it.
> I would love to hear comments from anyone using devfs. Good or bad.
>
> Thanks,
> David