2.5.7 make modules_install error (oss)
I really wish the OSS drivers would be fixed. They worked perfectly with my Crystal SoundFusion card, but the ALSA drivers are very unreliable with it. Sometimes they work, sometimes they don't. (One day a couple of weeks ago I rebooted about ten times, and the sound worked consistently *on alternate boots* (that is, it didn't work after the first boot, worked on the second boot, didn't work on the third, worked on the fourth, etc.). The next day it worked on every boot. Since then it works sometimes, and sometimes doesn't, with no discernible pattern. Even when it's working, it works sporadically -- some sound effects in Gnome work, others don't, then a few minutes later they all work again; RealPlayer works OK until I open a new window, then the sound cuts out and won't start again until I restart RealPlayer; and so forth. The OSS drivers don't give me any of these problems.
[email protected] on 03/19/2002 08:10:03 AM
To: Corporal Pisang <[email protected]>,
[email protected]
cc: (bcc: Wayne Brown/Corporate/Altec)
Subject: Re: 2.5.7 make modules_install error (oss)
Quoted 12 lines
Hi,
make -C
arch/i386/libmodules_install
make[1]: Entering directory/usr/src/linux/arch/i386/lib' make[1]: Nothing to be done formodules_install'.
make[1]: Leaving directory `/usr/src/linux/arch/i386/lib'
cd/lib/modules/2.5.7; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia if [ -r System.map ]; then/sbin/depmod-ae -F System.map 2.5.7; fi
depmod: *** Unresolved symbols in/lib/modules/2.5.7/kernel/sound/oss/sound.o
depmod:virt_to_bus_not_defined_use_pci_map
The OSS driver that you selected has not been converted to use the new pci API I'm not sure if it will ever be updated though, since alsa is now part of 2.5 try to use the alsa drivers instead. If you read this virt_to_bus_not_defined_use_pci_map carefully yo will see that it says virt_to_bus not defined use pci_map nice way to get people to fix the old drivers
;)
---------------------------------------------
This message was sent using M-Web Airmail.
JUST LIKE THAT
http://airmail.mweb.co.za/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 3 lines
I really wish the OSS drivers would be fixed. They worked perfectly with my Crystal SoundFusion card, but the ALSA drivers are very unreliable with it. Sometimes they work, sometimes they don't. (One day a couple of weeks ago I
In the longer term its more productive to fix the ALSA drivers and import any fixups they need. 2.5 is about the longer term maintainability of audio
Agreed, the oss drivers should _at least_ be maintained as an alternative, e.g. for those of us who want reliable sound with *low latency*
<explanation>
I haven't checked lately, but not too long ago the alsa drivers were found to be one of the worst sources of latency in the kernel. </explanation>
Joe
Quoted 71 lines · [email protected] wrote:
I really wish the OSS drivers would be fixed. They worked perfectly with my Crystal SoundFusion card, but the ALSA drivers are very unreliable with it. Sometimes they work, sometimes they don't. (One day a couple of weeks ago I rebooted about ten times, and the sound worked consistently *on alternate boots* (that is, it didn't work after the first boot, worked on the second boot, didn't work on the third, worked on the fourth, etc.). The next day it worked on every boot. Since then it works sometimes, and sometimes doesn't, with no discernible pattern. Even when it's working, it works sporadically -- some sound effects in Gnome work, others don't, then a few minutes later they all work again; RealPlayer works OK until I open a new window, then the sound cuts out and won't start again until I restart RealPlayer; and so forth. The OSS drivers don't give me any of these problems.
[email protected] on 03/19/2002 08:10:03 AM
To: Corporal Pisang <[email protected]>,
[email protected]
cc: (bcc: Wayne Brown/Corporate/Altec)Subject: Re: 2.5.7 make
modules_installerror (oss)Quoted 13 lines
Hi,
make -C
arch/i386/libmodules_install
make[1]: Entering directory/usr/src/linux/arch/i386/lib' make[1]: Nothing to be done formodules_install'.
make[1]: Leaving directory `/usr/src/linux/arch/i386/lib'
cd/lib/modules/2.5.7; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia if [ -r System.map ]; then/sbin/depmod-ae -F System.map 2.5.7; fi
depmod: *** Unresolved symbols in/lib/modules/2.5.7/kernel/sound/oss/sound.o
depmod:virt_to_bus_not_defined_use_pci_mapThe OSS driver that you selected has not been converted to use the new pci API I'm not sure if it will ever be updated though, since alsa is now part of 2.5 try to use the alsa drivers instead. If you read this
virt_to_bus_not_defined_use_pci_mapcarefully yo will see that it saysvirt_to_busnot defined usepci_mapnice way to get people to fix the old drivers
;)---------------------------------------------
This message was sent using M-Web Airmail.
JUST LIKE THAT
http://airmail.mweb.co.za/-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 4 lines
Agreed, the oss drivers should
_atleast_be maintained as an alternative, e.g. for those of us who want reliable sound with *low latency*
Not really. Well not unless you wish to volunteer.
Quoted 3 lines
I haven't checked lately, but not too long ago the alsa drivers were found to be one of the worst sources of latency in the kernel.
So fix it. On an SMP box the mess the oss drivers make is very visible because its all running under lock_kernel
Quoted 3 lines · Alan Cox
Not really. Well not unless you wish to volunteer.
Well, if I feel the pain, the motivation is there...
If the alsa drivers do not seem a viable choice, then I'll certainly volunteer to maintain the oss stuff that I find neccessary (mostly a collection of sb cards) -
Of course, there is always the possibility that alsa will turn out right in the end...
:-)
Joe
Quoted 10 lines · J Sloan
Agreed, the oss drivers should
_atleast_be maintained as an alternative, e.g. for those of us who want reliable sound with *low latency*<explanation>
I haven't checked lately, but not too long ago the alsa drivers were found to be one of the worst sources of latency in the kernel. </explanation>
You should really take care about your words. You've not written any technical reason to say these sentences. We are not aware about any problems against low-latency. Sure, OSS API emulation is only emulation, so there is additional layer which can be a bit slower than simplified native OSS drivers, but using ALSA API, we get really serious latencies even for multichannel hardware.
I propose to join to our efford and fix (or at least - point to) problems (if any) in ALSA drivers. Thanks.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linux http://www.suse.com
Quoted 14 lines · Jaroslav Kysela
Quoted 11 lines · J Sloan
Agreed, the oss drivers should
_atleast_be maintained as an alternative, e.g. for those of us who want reliable sound with *low latency*<explanation>
I haven't checked lately, but not too long ago the alsa drivers were found to be one of the worst sources of latency in the kernel. </explanation>
Quoted 3 lines
You should really take care about your words. You've not written any technical reason to say these sentences.
Fair enough - I don't see any technical reasons why alsa *couldn't* perform as well, latency wise, as oss.
Quoted 3 lines
We are not aware about any
problems against low-latency.
Some folks on this list had been doing latency profiling on their kernels during the past year (sorry, I don't remember the exact dates) and surprisingly the alsa driver was showing up as one of the top sources of latency - IIRC one possible explanation was "in-kernel mixing".
Quoted 5 lines
Sure, OSS API emulation is only emulation,
so there is additional layer which can be a bit slower than simplified native OSS drivers, but using ALSA API, we get really serious latencies even for multichannel hardware.
Thanks for the feedback, I'll have to do some testing of my own and see what the situation is at this point - I'd be very happy to learn that my concerns are outdated and already resolved.
Joe