Has anyone been able to get /usr/ports/opt/alsa-driver to compile on CRUX 2.3.? The port uses alsa-driver-1.0.14rc3. Crux 2.3 default kernel (2.6.20.3) "contains" alsa-driver-1.0.14rc3 (cat /proc/asound/version). The alsa-driver-1.0.14rc3 source code says it is not supported in kernels > 2.6.20. Therefore, I don't expect our port to compile. So, after googling, patching, hacking and praying, I've come to the conclusion that, unless you revert back to a kernel older than 2.6.20, our alsa-driver port is useless. Perhaps this ports is simply left over from Crux 2.2, where the older kernel allowed it to compile? Chris (Yes I've tried 1.0.14rc4 and the daily alsa snapshots, and every kernel
= 2.6.20.)
On Tue, 2007-05-08 at 12:15 -0500, Chris Pemberton wrote:
Has anyone been able to get /usr/ports/opt/alsa-driver to compile on CRUX 2.3.? [...]
I use the alsa-driver port (1.0.14rc3) with kernel 2.6.20.3 on crux 2.3, works like a charm. No compilation problems so far, just a footprint conflict between alsa-driver and glibc, oddly enough. Perhaps it'd be more beneficial to pastebin/post the actual problem? Matt (jaeger@freenode/#crux)
Matt Housh wrote:
On Tue, 2007-05-08 at 12:15 -0500, Chris Pemberton wrote:
Has anyone been able to get /usr/ports/opt/alsa-driver to compile on CRUX 2.3.?
[...]
I use the alsa-driver port (1.0.14rc3) with kernel 2.6.20.3 on crux 2.3, works like a charm. No compilation problems so far, just a footprint conflict between alsa-driver and glibc, oddly enough.
Perhaps it'd be more beneficial to pastebin/post the actual problem?
Matt (jaeger@freenode/#crux)
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
Interesting...? After reading that it works for you, I tried on my old desktop machine, and it worked. It doesn't work on my laptop, however. Here is the error: ... make[1]: Entering directory `/usr/src/linux-2.6.20.3' /usr/src/linux-2.6.20.3/Makefile:491: /usr/src/linux-2.6.20.3/arch//Makefile: No such file or directory make[2]: *** No rule to make target `/usr/src/linux-2.6.20.3/arch//Makefile'. Stop. make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.20.3' make: *** [compile] Error 2 =======> ERROR: Building '/usr/ports/opt/alsa-driver/alsa-driver#1.0.14rc3-1.pkg.tar.gz' failed. bash-3.2# I've been all through the kernel sources and alsa sources trying to fix this problem; a problem I assumed everyone was having with alsa-1.0.14rc3. But now that I know it works for some kernel configs and not others, I can stop playing with kernel sources and alsa sources and focus on what kernel configs work and which dont. I don't knnow why my laptop kernel config wouldn't work: I have alsa drivers compiled as modules and the kernel compiles without issue. It is just the external alsa that is not working for me on this machine. Thanks, Chris
On Tue, 2007-05-08 at 13:59 -0500, Chris Pemberton wrote: [...]
Here is the error:
... make[1]: Entering directory `/usr/src/linux-2.6.20.3' /usr/src/linux-2.6.20.3/Makefile:491: /usr/src/linux-2.6.20.3/arch//Makefile: No such file or directory [...]
That bit looks pretty suspicious; /usr/src/linux-2.6.20.3/arch/<arch>/Makefile would be more useful, such as /usr/src/linux-2.6.20.3/arch/i386/Makefile. Not sure why the arch wouldn't be set properly, though. Matt (jaeger@freenode/#crux)
Matt Housh wrote:
On Tue, 2007-05-08 at 13:59 -0500, Chris Pemberton wrote: [...]
Here is the error:
... make[1]: Entering directory `/usr/src/linux-2.6.20.3' /usr/src/linux-2.6.20.3/Makefile:491: /usr/src/linux-2.6.20.3/arch//Makefile: No such file or directory
[...]
That bit looks pretty suspicious; /usr/src/linux-2.6.20.3/arch/<arch>/Makefile would be more useful, such as /usr/src/linux-2.6.20.3/arch/i386/Makefile. Not sure why the arch wouldn't be set properly, though.
Matt (jaeger@freenode/#crux)
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
I agree. For the past several days I've been thinking 1.0.14rc3 was incompatible with 2.6.20.3; because it always failed to compile clean. Now that others are telling me I works for them, I will look into my kernel config and leave the alsa code alone. Thanks everyone, this has been helpful. I am no longer barking up the wrong tree. Chris
Matt Housh wrote:
On Tue, 2007-05-08 at 13:59 -0500, Chris Pemberton wrote: [...]
Here is the error:
... make[1]: Entering directory `/usr/src/linux-2.6.20.3' /usr/src/linux-2.6.20.3/Makefile:491: /usr/src/linux-2.6.20.3/arch//Makefile: No such file or directory
[...]
That bit looks pretty suspicious; /usr/src/linux-2.6.20.3/arch/<arch>/Makefile would be more useful, such as /usr/src/linux-2.6.20.3/arch/i386/Makefile. Not sure why the arch wouldn't be set properly, though.
Matt (jaeger@freenode/#crux)
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
Well, I "solved" the problem. I compiled /usr/ports/opt/alsa-driver on the desktop machine (PIII i686). Transferred the modules from the desktop to the laptop (core2). When laptop tried to load the modules, it complained horribly about not having core2 built into them. And that got me thinking.... I rebuilt the laptop kernel and changed it to PIII i686 instead of Core2. Rebooted laptop. This time laptop /usr/ports/opt/alsa-driver compiled clean! So, I'm off to the kernel and alsa mailing lists to report the bug. Who would have thought selecting core2 in the kernel would screw up the external alsa drivers? Chris
participants (2)
-
Chris Pemberton
-
Matt Housh