solo-1 chip
Hi,
Anyone have any luck configuring kernel 2.2.2 to work with the
solo-1 chip (on the motherboard)? I can get it to work with the sb driver, but only in 8-bit mode. WSS driver seems to be able to access it, but I can't think of a way to figure out the IRQ/DMA for it.
Any ideas?
Thanks
Dan
Quoted 4 lines · Dan Boger
Anyone have any luck configuring kernel 2.2.2 to work with the
solo-1 chip (on the motherboard)? I can get it to work with the sb driver, but only in 8-bit mode. WSS driver seems to be able to access it, but I can't think of a way to figure out the IRQ/DMA for it.
To get native ESS Solo support ATM, you'd either have to use the 2.2.*-ac patches (ftp.linux.org.uk:/pub/linux/alan/2.2), or ALSA
(http://alsa.jcu.cz/)
Bill
Quoted 3 lines · Bill Nottingham
To get native ESS Solo support ATM, you'd either have to use the 2.2.*-ac patches (ftp.linux.org.uk:/pub/linux/alan/2.2), or ALSA
(http://alsa.jcu.cz/)
AFAIK, the -ac - patches contain initialisation code for the ESS Maestro2, not the Solo.
And the ALSA driver only supports playback at the moment.
Tom
On Thu, 11 Mar 1999 01:10:13 -0500 Bill Nottingham <[email protected]> wrote
concerning 'Re: solo-1 chip':
Quoted 4 lines
To get native ESS Solo support ATM, you'd either have to use the 2.2.*-ac patches (ftp.linux.org.uk:/pub/linux/alan/2.2), or ALSA
(http://alsa.jcu.cz/)
Great! So I download the alsa driver install it. But when I try to modprobe it says that the device is already in use. I look at proc/modules, it did load a bunch of stuff, but still no sound. Do I need to edit my /etc/conf.modules for options? The solo1 isn't mentioned in any of the documents - how do I know the name of the options?
Thanks,
Dan
Quoted 9 lines · Dan Boger
On Thu, 11 Mar 1999 01:10:13 -0500 Bill Nottingham <[email protected]> wrote
concerning 'Re: solo-1 chip':Quoted 4 lines
To get native ESS Solo support ATM, you'd either have to use the 2.2.*-ac patches (ftp.linux.org.uk:/pub/linux/alan/2.2), or ALSA
(http://alsa.jcu.cz/)Great! So I download the alsa driver install it. But when I try to modprobe it says that the device is already in use. I look at
i have seen this error when trying to load the sb module and it seemed to happen simply because i did not specify enough or the right options.
Quoted 4 lines
proc/modules, it did load a bunch of stuff, but still no sound. Do I need to edit my
/etc/conf.modulesfor options? The solo1 isn't mentioned in any of the documents - how do I know the name of the options?
i believe the names of the options are uniform, at least the generic ones. try io=0x... irq=... dma1=... and such.
you can supply these on the command line, until you get it working, then put the right values into your conf.modules
ie 'modprobe ess-solo irq=x io=0xwhatever ...'
-cc