cat /proc/asound/version: "No such device": HELP!!

cat /proc/asound/version: "No such device": HELP!!

[Andreas Mohr]

Hi all,

I'm almost at my wits end ("ARGH!").
Everything used to work pretty well... until I messed with my system once
again (upgrading some packages and doing other things, or so I think).

After having installed the 0.9rc7 Debian package (or around that time
at least) and having rebuilt ALSA, I didn't manage to start ALSA properly
any more:
root@note:/root# /etc/init.d/alsa start
cat: /proc/asound/version: No such device
Starting ALSA sound driver (version ):/etc/init.d/alsa: line 93: [: =: unary operator expected
 no sound cards defined.
root@note:/root#

root@note:/root# ls -l /proc/asound/
total 0
-r--r--r--    1 root     root            0 Feb 14 12:09 cards
dr-xr-xr-x    2 root     root            0 Feb 14 12:09 dev/
-r--r--r--    1 root     root            0 Feb 14 12:09 devices
-r--r--r--    1 root     root            0 Feb 14 12:09 meminfo
dr-xr-xr-x    2 root     root            0 Feb 14 12:09 oss/
dr-xr-xr-x    2 root     root            0 Feb 14 12:09 seq/
-r--r--r--    1 root     root            0 Feb 14 12:09 version
root@note:/root# cat /proc/asound/version
cat: /proc/asound/version: No such device
root@note:/root#
Modules loaded at that time:
snd                    42532   0
soundcore               3492   0  [snd]

I downgraded to the 0.9rc6 packages: nothing.
I checked out a completely fresh ALSA CVS tree and rebuilt (by using
cvscompile also): nothing.
I checked out an older ALSA tree: nothing.
I waited some weeks: nothing.

I'm almost as desperate as to debug and to rip apart
the whole goddamn thing now (/usr/src/system/CVS/alsa/alsa-kernel/core/info.c).

A reboot didn't help either, of course.

System:
Debian testing/unstable
2.4.20 custom kernel
ALSA latest CVS
root@note:/root# dpkg -l|grep alsa
ii  alsa-base      0.9.0rc7-2     ALSA driver common files
ii  alsa-headers   0.9.0rc7-2     ALSA driver header files
ii  alsa-utils     0.9.0rc7-1     Advanced Linux Sound Architecture (utils)
root@note:/root# dpkg -l|grep gcc
ii  gcc            3.2.2-0        The GNU C compiler.
ii  gcc-2.95       2.95.4-15      The GNU C compiler.
ii  gcc-3.0        3.0.4-0pre0201 The GNU C compiler.
ii  gcc-3.0-base   3.0.4-14       The GNU Compiler Collection (base package)
ii  gcc-3.2        3.2.2-0pre8    The GNU C compiler
ii  gcc-3.2-base   3.2.2-0pre8    The GNU Compiler Collection (base package)
ii  gcc272         2.7.2.3-18     The GNU C compiler.
ii  libgcc1        3.2.3-0pre1    GCC support library

Notebook Dell Inspiron 5000e (ugh!) with Maestro 2E (es1968) soundcard

Does anyone have *any* idea?

Maybe some "slightly too newish" gcc problem or so??
The next thing I'll try is to rebuild with my gcc 3.0.4 version...

Needless to say, I need this ALSA tree to work properly again
(if only to maybe hack on an Aztech PCI338 A3D Aureal AU8820 driver ;-))

Andreas Mohr


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

Re: cat /proc/asound/version: "No such device": HELP!!

[Andrea Venturi (personale)]

Andreas Mohr wrote:
> Hi all,
> 
> I'm almost at my wits end ("ARGH!").
> Everything used to work pretty well... until I messed with my system once
> again (upgrading some packages and doing other things, or so I think).
> 
> After having installed the 0.9rc7 Debian package (or around that time
> at least) and having rebuilt ALSA, I didn't manage to start ALSA properly
> any more:

hi,
i incurred in the same problem since two days, when i decided to upgrade 
my alsa driver from 0.9rc6 to 0.9rc7

some info:

i use a toshiba s3000-214 with an intel8x0 audio device

with 0.9rc6 alsa was running fine

i run debian unstable.


these are the relevant (!) package:

andrea@nb-venturi:~$ dpkg -l | grep alsa-
ii  alsa-base      0.9.0rc7-2     ALSA driver common files
ii  alsa-headers   0.9.0rc7-2     ALSA driver header files
rc  alsa-modules-2 0.9+0beta10+5+ Advanced Linux Sound Architecture 
(drivers)
ii  alsa-source    0.9.0rc7-2     ALSA driver source
ii  alsa-utils     0.9.0rc7-1     Advanced Linux Sound Architecture (utils)

andrea@nb-venturi:~$ dpkg -l | grep gcc
ii  gcc            3.2.2-0        The GNU C compiler.
ii  gcc-2.95       2.95.4-15      The GNU C compiler.
ii  gcc-3.0        3.0.4-13       The GNU C compiler.
ii  gcc-3.0-base   3.0.4-14       The GNU Compiler Collection (base package)
ii  gcc-3.2        3.2.3-0pre1    The GNU C compiler
ii  gcc-3.2-base   3.2.3-0pre1    The GNU Compiler Collection (base package)
ii  libgcc1        3.2.3-0pre1    GCC support library
rc  libstlport4.5g 4.5.3-4        gcc3-version STLport C++ class library
ii  libstlport4.5g 4.5.3-5cjh2    STLport C++ class library compiled 
with gcc3

under /usr/src there was:

andrea@nb-venturi:~$ ls -l /usr/src/
totale 31756
-rw-r--r--    1 root     root      2157649 2003-02-07 12:16 
alsa-driver.tar.gz

that is the debian way to put source tarball to upgrade some driver..

i compiled the usual stuff /usr/src/modules/alsa-driver

ad i installed all the modules with "make install"

than, at next reboot, the /etc/init.d/alsa script failed to run because 
there was a small glitch at line 93: a missing double-quote around 
$alsa_version

the i had to add /etc/modutils/alsa with all the aliases for the modules 
and i was up & running, or, at least, i was thinking.. :-(

the snd-intel8x0 goes up, from dmesg:

PCI: Found IRQ 10 for device 00:1f.5
PCI: Sharing IRQ 10 with 00:1f.3
PCI: Sharing IRQ 10 with 00:1f.6
PCI: Sharing IRQ 10 with 02:01.0
PCI: Sharing IRQ 10 with 02:04.1
PCI: Setting latency timer of device 00:1f.5 to 64
intel8x0: clocking to 48000

but, if i try a "cat /proc/asound/version"

i get an oopps
=====================================
  <1>Unable to handle kernel NULL pointer dereference at virtual address 
00000000
  printing eip:
c0115073
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c0115073>]    Tainted: PF
EFLAGS: 00010097
eax: d2960584   ebx: d2960584   ecx: 00000000   edx: 00000003
esi: d2960588   edi: 00000001   ebp: c3391f30   esp: c3391f18
ds: 0018   es: 0018   ss: 0018
Process esd (pid: 4150, stackpage=c3391000)
Stack: cfe75960 c888b540 d296054c d2960588 00000286 00000003 c888b540 
d9b56451
        c142f360 00000286 cc0385a0 d2960400 cc0385a0 d2960400 d9b5835d 
d2960400
        c888b540 00000000 cc0385c0 c888b540 ca4e1060 c142f360 ca3ac3a0 
c0133444
Call Trace:    [<d9b56451>] [<d9b5835d>] [<c0133444>] [<c0132495>] 
[<c01324e3>]
   [<c0108547>]

Code: 8b 01 85 45 fc 74 4c 31 c0 9c 5e fa c7 01 00 00 00 00 83 79
======================================

and if i try "alsamixer", i get a segmentation fault!!

=== last rows from a "strace alsamixer" ===============
access("/etc/asound.conf", R_OK)        = -1 ENOENT (No such file or 
directory)
access("/home/andrea/.asoundrc", R_OK)  = -1 ENOENT (No such file or 
directory)
open("/dev/snd/controlC0", O_RDONLY)    = 3
close(3 <unfinished ...>
+++ killed by SIGSEGV +++
andrea@nb-venturi:~$
=======================================================

and the very same oops in dmesg

that's all. having not much more skill and time, i'll live without audio 
for some time hoping in better times! ;-)


bye

andrea venturi



> root@note:/root# /etc/init.d/alsa start
> cat: /proc/asound/version: No such device
> Starting ALSA sound driver (version ):/etc/init.d/alsa: line 93: [: =: unary operator expected
>  no sound cards defined.
> root@note:/root#
> 
> root@note:/root# ls -l /proc/asound/
> total 0
> -r--r--r--    1 root     root            0 Feb 14 12:09 cards
> dr-xr-xr-x    2 root     root            0 Feb 14 12:09 dev/
> -r--r--r--    1 root     root            0 Feb 14 12:09 devices
> -r--r--r--    1 root     root            0 Feb 14 12:09 meminfo
> dr-xr-xr-x    2 root     root            0 Feb 14 12:09 oss/
> dr-xr-xr-x    2 root     root            0 Feb 14 12:09 seq/
> -r--r--r--    1 root     root            0 Feb 14 12:09 version
> root@note:/root# cat /proc/asound/version
> cat: /proc/asound/version: No such device
> root@note:/root#
> Modules loaded at that time:
> snd                    42532   0
> soundcore               3492   0  [snd]
> 
> I downgraded to the 0.9rc6 packages: nothing.
> I checked out a completely fresh ALSA CVS tree and rebuilt (by using
> cvscompile also): nothing.
> I checked out an older ALSA tree: nothing.
> I waited some weeks: nothing.
> 
> I'm almost as desperate as to debug and to rip apart
> the whole goddamn thing now (/usr/src/system/CVS/alsa/alsa-kernel/core/info.c).
> 
> A reboot didn't help either, of course.
> 
> System:
> Debian testing/unstable
> 2.4.20 custom kernel
> ALSA latest CVS
> root@note:/root# dpkg -l|grep alsa
> ii  alsa-base      0.9.0rc7-2     ALSA driver common files
> ii  alsa-headers   0.9.0rc7-2     ALSA driver header files
> ii  alsa-utils     0.9.0rc7-1     Advanced Linux Sound Architecture (utils)
> root@note:/root# dpkg -l|grep gcc
> ii  gcc            3.2.2-0        The GNU C compiler.
> ii  gcc-2.95       2.95.4-15      The GNU C compiler.
> ii  gcc-3.0        3.0.4-0pre0201 The GNU C compiler.
> ii  gcc-3.0-base   3.0.4-14       The GNU Compiler Collection (base package)
> ii  gcc-3.2        3.2.2-0pre8    The GNU C compiler
> ii  gcc-3.2-base   3.2.2-0pre8    The GNU Compiler Collection (base package)
> ii  gcc272         2.7.2.3-18     The GNU C compiler.
> ii  libgcc1        3.2.3-0pre1    GCC support library
> 
> Notebook Dell Inspiron 5000e (ugh!) with Maestro 2E (es1968) soundcard
> 
> Does anyone have *any* idea?
> 
> Maybe some "slightly too newish" gcc problem or so??
> The next thing I'll try is to rebuild with my gcc 3.0.4 version...
> 
> Needless to say, I need this ALSA tree to work properly again
> (if only to maybe hack on an Aztech PCI338 A3D Aureal AU8820 driver ;-))
> 
> Andreas Mohr
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
> are you planning your Web Server Security? Click here to get a FREE
> Thawte SSL guide and find the answers to all your  SSL security issues.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

gcc 3.x build issue? (was: cat /proc/asound/version: "No such device": HELP!!)

[Andreas Mohr]

On Mon, Feb 17, 2003 at 07:43:33PM +0100, Andrea Venturi (personale) wrote:
> Andreas Mohr wrote:
> >Hi all,
> >
> >I'm almost at my wits end ("ARGH!").
> >Everything used to work pretty well... until I messed with my system once
> >again (upgrading some packages and doing other things, or so I think).
> >
> >After having installed the 0.9rc7 Debian package (or around that time
> >at least) and having rebuilt ALSA, I didn't manage to start ALSA properly
> >any more:
> 
> hi,
> i incurred in the same problem since two days, when i decided to upgrade 
> my alsa driver from 0.9rc6 to 0.9rc7
Ah, finally! It's quite reassuring to know that I'm not alone in suffering
this severe problem :-)

> some info:
> 
> i use a toshiba s3000-214 with an intel8x0 audio device
> 
> with 0.9rc6 alsa was running fine
> 
> i run debian unstable.
> 
> 
> these are the relevant (!) package:
> 
> andrea@nb-venturi:~$ dpkg -l | grep alsa-
> ii  alsa-base      0.9.0rc7-2     ALSA driver common files
> ii  alsa-headers   0.9.0rc7-2     ALSA driver header files
> rc  alsa-modules-2 0.9+0beta10+5+ Advanced Linux Sound Architecture 
> (drivers)
> ii  alsa-source    0.9.0rc7-2     ALSA driver source
> ii  alsa-utils     0.9.0rc7-1     Advanced Linux Sound Architecture (utils)
> 
> andrea@nb-venturi:~$ dpkg -l | grep gcc
> ii  gcc            3.2.2-0        The GNU C compiler.
> ii  gcc-2.95       2.95.4-15      The GNU C compiler.
> ii  gcc-3.0        3.0.4-13       The GNU C compiler.
> ii  gcc-3.0-base   3.0.4-14       The GNU Compiler Collection (base package)
> ii  gcc-3.2        3.2.3-0pre1    The GNU C compiler
> ii  gcc-3.2-base   3.2.3-0pre1    The GNU Compiler Collection (base package)
> ii  libgcc1        3.2.3-0pre1    GCC support library
> rc  libstlport4.5g 4.5.3-4        gcc3-version STLport C++ class library
> ii  libstlport4.5g 4.5.3-5cjh2    STLport C++ class library compiled 
> with gcc3
> 
> under /usr/src there was:
> 
> andrea@nb-venturi:~$ ls -l /usr/src/
> totale 31756
> -rw-r--r--    1 root     root      2157649 2003-02-07 12:16 
> alsa-driver.tar.gz
> 
> that is the debian way to put source tarball to upgrade some driver..
> 
> i compiled the usual stuff /usr/src/modules/alsa-driver
> 
> ad i installed all the modules with "make install"
> 
> than, at next reboot, the /etc/init.d/alsa script failed to run because 
> there was a small glitch at line 93: a missing double-quote around 
> $alsa_version
> 
> the i had to add /etc/modutils/alsa with all the aliases for the modules 
> and i was up & running, or, at least, i was thinking.. :-(
> 
> the snd-intel8x0 goes up, from dmesg:
> 
> PCI: Found IRQ 10 for device 00:1f.5
> PCI: Sharing IRQ 10 with 00:1f.3
> PCI: Sharing IRQ 10 with 00:1f.6
> PCI: Sharing IRQ 10 with 02:01.0
> PCI: Sharing IRQ 10 with 02:04.1
> PCI: Setting latency timer of device 00:1f.5 to 64
> intel8x0: clocking to 48000
> 
> but, if i try a "cat /proc/asound/version"
> 
> i get an oopps
> =====================================
>  <1>Unable to handle kernel NULL pointer dereference at virtual address 
> 00000000
>  printing eip:
> c0115073
> *pde = 00000000
> Oops: 0000
> CPU:    0
> EIP:    0010:[<c0115073>]    Tainted: PF
> EFLAGS: 00010097
> eax: d2960584   ebx: d2960584   ecx: 00000000   edx: 00000003
> esi: d2960588   edi: 00000001   ebp: c3391f30   esp: c3391f18
> ds: 0018   es: 0018   ss: 0018
> Process esd (pid: 4150, stackpage=c3391000)
> Stack: cfe75960 c888b540 d296054c d2960588 00000286 00000003 c888b540 
> d9b56451
>        c142f360 00000286 cc0385a0 d2960400 cc0385a0 d2960400 d9b5835d 
> d2960400
>        c888b540 00000000 cc0385c0 c888b540 ca4e1060 c142f360 ca3ac3a0 
> c0133444
> Call Trace:    [<d9b56451>] [<d9b5835d>] [<c0133444>] [<c0132495>] 
> [<c01324e3>]
>   [<c0108547>]
> 
> Code: 8b 01 85 45 fc 74 4c 31 c0 9c 5e fa c7 01 00 00 00 00 83 79
> ======================================
Hmm, interesting. I assume your problem is very "similar"
(mine just printed: "No such device").
I just did what I had announced (recompile ALSA using older gcc versions
installed on the system).
root@note:/usr/src/system/CVS/alsa/alsa-driver# dpkg -l|grep gcc
ii  altgcc         2.7.2.3-2      Alternate gcc package for the libc5 environm
ii  gcc            3.2.2-0        The GNU C compiler.
ii  gcc-2.95       2.95.4-15      The GNU C compiler.
ii  gcc-3.0        3.0.4-0pre0201 The GNU C compiler.
ii  gcc-3.0-base   3.0.4-14       The GNU Compiler Collection (base package)
ii  gcc-3.2        3.2.2-0pre8    The GNU C compiler
ii  gcc-3.2-base   3.2.2-0pre8    The GNU Compiler Collection (base package)
ii  gcc272         2.7.2.3-18     The GNU C compiler.
ii  libgcc1        3.2.3-0pre1    GCC support library

Using gcc-3.0 in Makefile.conf: failed.
Using gcc-2.95 in Makefile.conf: SUCCESS!!

Sounds as if there might be a pretty severe gcc 3.x ALSA build problem...
As I've got quite some time now, I'll try to nail it down somewhat.
Any further helpful comments strongly appreciated...

Needless to say I'll concentrate on the info.c /proc support area...
Maybe the various /proc parsing handlers inside that file get corrupted
by some gcc optimization somehow...
I'll add some traces to that file to find out more.

Andreas Mohr


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: gcc 3.x build issue?

[Dmitry Astapov]

Evening, Andreas. 

Andreas Mohr <andi@rhlx01.fht-esslingen.de> 20:11 17/2/2003 wrote:

>> >After having installed the 0.9rc7 Debian package (or around that time
>> >at least) and having rebuilt ALSA, I didn't manage to start ALSA properly
>> >any more:
>> i incurred in the same problem since two days, when i decided to upgrade 
>> my alsa driver from 0.9rc6 to 0.9rc7
 AM> Ah, finally! It's quite reassuring to know that I'm not alone in suffering
 AM> this severe problem :-)
I'd like to second that - "oops" with alsa-drivers built with gcc-3.0 and
gcc-3.2, no problems with 2.95.


-- 
Dmitry Astapov //ADEpt                               E-mail: adept@umc.com.ua
GPG KeyID/fprint: F5D7639D/CA36 E6C4 815D 434D 0498  2B08 7867 4860 F5D7 639D


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: gcc 3.x build issue? (was: cat /proc/asound/version: "No such device": HELP!!)

[Takashi Iwai]

Hi,

are you sure both all kernel sources and alsa drivers are compiled
with the same compiler?
you cannot mix gcc-2.x and gcc-3.x binaries for kernel.  the
combination likely causes oops.


Takashi

At Mon, 17 Feb 2003 20:11:13 +0100,
Andreas Mohr wrote:
> 
> > some info:
> > 
> > i use a toshiba s3000-214 with an intel8x0 audio device
> > 
> > with 0.9rc6 alsa was running fine
> > 
> > i run debian unstable.
> > 
> > 
> > these are the relevant (!) package:
> > 
> > andrea@nb-venturi:~$ dpkg -l | grep alsa-
> > ii  alsa-base      0.9.0rc7-2     ALSA driver common files
> > ii  alsa-headers   0.9.0rc7-2     ALSA driver header files
> > rc  alsa-modules-2 0.9+0beta10+5+ Advanced Linux Sound Architecture 
> > (drivers)
> > ii  alsa-source    0.9.0rc7-2     ALSA driver source
> > ii  alsa-utils     0.9.0rc7-1     Advanced Linux Sound Architecture (utils)
> > 
> > andrea@nb-venturi:~$ dpkg -l | grep gcc
> > ii  gcc            3.2.2-0        The GNU C compiler.
> > ii  gcc-2.95       2.95.4-15      The GNU C compiler.
> > ii  gcc-3.0        3.0.4-13       The GNU C compiler.
> > ii  gcc-3.0-base   3.0.4-14       The GNU Compiler Collection (base package)
> > ii  gcc-3.2        3.2.3-0pre1    The GNU C compiler
> > ii  gcc-3.2-base   3.2.3-0pre1    The GNU Compiler Collection (base package)
> > ii  libgcc1        3.2.3-0pre1    GCC support library
> > rc  libstlport4.5g 4.5.3-4        gcc3-version STLport C++ class library
> > ii  libstlport4.5g 4.5.3-5cjh2    STLport C++ class library compiled 
> > with gcc3
> > 
> > under /usr/src there was:
> > 
> > andrea@nb-venturi:~$ ls -l /usr/src/
> > totale 31756
> > -rw-r--r--    1 root     root      2157649 2003-02-07 12:16 
> > alsa-driver.tar.gz
> > 
> > that is the debian way to put source tarball to upgrade some driver..
> > 
> > i compiled the usual stuff /usr/src/modules/alsa-driver
> > 
> > ad i installed all the modules with "make install"
> > 
> > than, at next reboot, the /etc/init.d/alsa script failed to run because 
> > there was a small glitch at line 93: a missing double-quote around 
> > $alsa_version
> > 
> > the i had to add /etc/modutils/alsa with all the aliases for the modules 
> > and i was up & running, or, at least, i was thinking.. :-(
> > 
> > the snd-intel8x0 goes up, from dmesg:
> > 
> > PCI: Found IRQ 10 for device 00:1f.5
> > PCI: Sharing IRQ 10 with 00:1f.3
> > PCI: Sharing IRQ 10 with 00:1f.6
> > PCI: Sharing IRQ 10 with 02:01.0
> > PCI: Sharing IRQ 10 with 02:04.1
> > PCI: Setting latency timer of device 00:1f.5 to 64
> > intel8x0: clocking to 48000
> > 
> > but, if i try a "cat /proc/asound/version"
> > 
> > i get an oopps
> > =====================================
> >  <1>Unable to handle kernel NULL pointer dereference at virtual address 
> > 00000000
> >  printing eip:
> > c0115073
> > *pde = 00000000
> > Oops: 0000
> > CPU:    0
> > EIP:    0010:[<c0115073>]    Tainted: PF
> > EFLAGS: 00010097
> > eax: d2960584   ebx: d2960584   ecx: 00000000   edx: 00000003
> > esi: d2960588   edi: 00000001   ebp: c3391f30   esp: c3391f18
> > ds: 0018   es: 0018   ss: 0018
> > Process esd (pid: 4150, stackpage=c3391000)
> > Stack: cfe75960 c888b540 d296054c d2960588 00000286 00000003 c888b540 
> > d9b56451
> >        c142f360 00000286 cc0385a0 d2960400 cc0385a0 d2960400 d9b5835d 
> > d2960400
> >        c888b540 00000000 cc0385c0 c888b540 ca4e1060 c142f360 ca3ac3a0 
> > c0133444
> > Call Trace:    [<d9b56451>] [<d9b5835d>] [<c0133444>] [<c0132495>] 
> > [<c01324e3>]
> >   [<c0108547>]
> > 
> > Code: 8b 01 85 45 fc 74 4c 31 c0 9c 5e fa c7 01 00 00 00 00 83 79
> > ======================================
> Hmm, interesting. I assume your problem is very "similar"
> (mine just printed: "No such device").
> I just did what I had announced (recompile ALSA using older gcc versions
> installed on the system).
> root@note:/usr/src/system/CVS/alsa/alsa-driver# dpkg -l|grep gcc
> ii  altgcc         2.7.2.3-2      Alternate gcc package for the libc5 environm
> ii  gcc            3.2.2-0        The GNU C compiler.
> ii  gcc-2.95       2.95.4-15      The GNU C compiler.
> ii  gcc-3.0        3.0.4-0pre0201 The GNU C compiler.
> ii  gcc-3.0-base   3.0.4-14       The GNU Compiler Collection (base package)
> ii  gcc-3.2        3.2.2-0pre8    The GNU C compiler
> ii  gcc-3.2-base   3.2.2-0pre8    The GNU Compiler Collection (base package)
> ii  gcc272         2.7.2.3-18     The GNU C compiler.
> ii  libgcc1        3.2.3-0pre1    GCC support library
> 
> Using gcc-3.0 in Makefile.conf: failed.
> Using gcc-2.95 in Makefile.conf: SUCCESS!!
> 
> Sounds as if there might be a pretty severe gcc 3.x ALSA build problem...
> As I've got quite some time now, I'll try to nail it down somewhat.
> Any further helpful comments strongly appreciated...
> 
> Needless to say I'll concentrate on the info.c /proc support area...
> Maybe the various /proc parsing handlers inside that file get corrupted
> by some gcc optimization somehow...
> I'll add some traces to that file to find out more.
> 
> Andreas Mohr
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: gcc 3.x build issue? (was: cat /proc/asound/version: "No such device": HELP!!)

[Duncan Sands]

> are you sure both all kernel sources and alsa drivers are compiled
> with the same compiler?
> you cannot mix gcc-2.x and gcc-3.x binaries for kernel.  the
> combination likely causes oops.

I had this problem some time ago.  The same compiler was used for
both kernel and ALSA.  I assumed it was a timing problem with card
setup (cs46xx).  I haven't had a problem with recent kernels/ALSA.

Duncan.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: gcc 3.x build issue? (was: cat /proc/asound/version: "No such device": HELP!!)

[Duncan Sands]

> are you sure both all kernel sources and alsa drivers are compiled
> with the same compiler?
> you cannot mix gcc-2.x and gcc-3.x binaries for kernel.  the
> combination likely causes oops.

I just tried compiling the kernel with 2.95 and alsa with 3.2.
This combination results in the kind of no-such-device strangeness
that was reported.

Duncan.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: gcc 3.x build issue? (was: cat /proc/asound/version: "No such device": HELP!!)

[Andreas Mohr]

On Tue, Feb 18, 2003 at 04:56:23PM +0100, Jordi Mallach wrote:
> On Tue, Feb 18, 2003 at 09:52:53AM +0100, Takashi Iwai wrote:
> > are you sure both all kernel sources and alsa drivers are compiled
> > with the same compiler?
> > you cannot mix gcc-2.x and gcc-3.x binaries for kernel.  the
> > combination likely causes oops.
> 
> Yes, this is what causes their problem. We've had oodles of reports
> regarding this, as people were still using kernel images generated
> before the gcc switch.
> 
> People, just recompile your kernel using gcc 3.2.
Indeed, that's what fixed it.
I'm sorry to hear that it's been coming up tons of times already.
But I had searched for cat /proc/* (or in fact asound/version):
"No such device" and hadn't found anything, so I'd decided to ask.
Anyway, a final Thank You for the very informative discussion!

-- 
Andreas Mohr                        Stauferstr. 6, D-71272 Renningen, Germany
Tel. +49 7159 800604                http://mohr.de.tt


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf