Re: Getting Ensoniq 5880 soundcard to work again after 2.4 to 2.6 kernel upgrade.
OK, I think I've got this sorted now. I added snd_pcm_oss to /etc/modules and commented out a bunch of old stuff, then rebooted. Then X wouldn't start. I'm not sure, but I think that might be because I was trying to run udev on kernel-image-2.6.8-2-k7. (This was the first reboot since installing udev and hal to get pmount to work as I expected it to.) So I installed linux-image-2.6.15-1-k7 and booted with that. Now X and the soundcard work. In the end I didn't need to mess with /etc/modprobe.d/*. Thanks very much for your help! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting Ensoniq 5880 soundcard to work again after 2.4 to 2.6 kernel upgrade.
On 2006-02-26, Colin <[EMAIL PROTECTED]> wrote: > Adam Funk wrote: >> Hang on. A few weeks ago when I was asking about preparations for >> switching from 2.4 to 2.6, you said to move customizations from >> /etc/modutils/ to /etc/modprobe.d/ -- does that mean that 2.6 doesn't >> use /etc/modutils/*? > > That is correct. I overlooked that. > >> Do both 2.4 and 2.6 use /etc/modules? > > Yes. Thanks for the confirmations. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting Ensoniq 5880 soundcard to work again after 2.4 to 2.6 kernel upgrade.
Adam Funk wrote: > Hang on. A few weeks ago when I was asking about preparations for > switching from 2.4 to 2.6, you said to move customizations from > /etc/modutils/ to /etc/modprobe.d/ -- does that mean that 2.6 doesn't > use /etc/modutils/*? That is correct. I overlooked that. > Do both 2.4 and 2.6 use /etc/modules? Yes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting Ensoniq 5880 soundcard to work again after 2.4 to 2.6 kernel upgrade.
Some more potential diagnostic information. While I was messing with modprobe, the following appeared in syslog: Feb 25 17:23:52 garcia kernel: usbaudio: dma timed out?? Feb 25 17:43:29 garcia kernel: unable to register OSS mixer device 0:0 Feb 25 17:43:29 garcia kernel: unable to register OSS PCM device 0:0 Feb 25 17:44:59 garcia kernel: es1371: version v0.32 time 14:23:03 Aug 16 2005 Feb 25 17:45:04 garcia kernel: es1371: unloading Feb 25 17:45:06 garcia kernel: es1371: version v0.32 time 14:23:03 Aug 16 2005 Feb 25 17:45:07 garcia kernel: es1371: unloading Feb 25 17:45:21 garcia kernel: unable to register OSS mixer device 0:0 Feb 25 17:45:21 garcia kernel: unable to register OSS PCM device 0:0 Feb 25 17:45:21 garcia devfsd[424]: error stat(2)ing: "sound/mixer1"^INo such file or directory Feb 25 17:45:21 garcia devfsd[424]: error stat(2)ing: "sound/dsp1"^INo such file or directory So I assume that something wants /dev/sound/mixer1 and /dev/sound/dsp, whereas I actually have the following. $ ls -l /dev/sound/* crw-rw 1 root audio 14, 12 1970-01-01 01:00 /dev/sound/adsp crw-rw 1 root audio 14, 9 1970-01-01 01:00 /dev/sound/dmmidi crw-rw 1 root audio 14, 3 1970-01-01 01:00 /dev/sound/dsp crw-rw 1 root audio 14, 2 1970-01-01 01:00 /dev/sound/midi crw-rw 1 root audio 14, 0 1970-01-01 01:00 /dev/sound/mixer Any suggestions on identifying and resolving this conflict? Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting Ensoniq 5880 soundcard to work again after 2.4 to 2.6 kernel upgrade.
On 2006-02-24, Colin <[EMAIL PROTECTED]> wrote: >> I haven't tampered with anything in /etc/modutils/ yet -- should I >> edit modutils/sndconfig and replace es1371 with snd_ens1371. > > Yes, do this Hang on. A few weeks ago when I was asking about preparations for switching from 2.4 to 2.6, you said to move customizations from /etc/modutils/ to /etc/modprobe.d/ -- does that mean that 2.6 doesn't use /etc/modutils/*? There's nothing about the soundcard in the new directory: /etc # grep -r snd modprobe.d/ /etc # grep -r 1371 modprobe.d/ > Also, I'd add "snd_ens1371" and "snd_pcm_oss" to your /etc/modules (not > /etc/modules.conf) file Do both 2.4 and 2.6 use /etc/modules? Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting Ensoniq 5880 soundcard to work again after 2.4 to 2.6 kernel upgrade.
Adam Funk wrote: > /etc $ grep -r 1371 modutils/ > modutils/sndconfig:alias sound-slot-0 es1371 > > I haven't tampered with anything in /etc/modutils/ yet -- should I > edit modutils/sndconfig and replace es1371 with snd_ens1371. Yes, do this > I've just tried > # rmmod es1371 > but it didn't help. (lsmod showed that snd_ens1371 was still there > but not es1371.) Does that mean anything to you? This means that rmmod worked (but you should really use "modprobe -r" instead) Also, I'd add "snd_ens1371" and "snd_pcm_oss" to your /etc/modules (not /etc/modules.conf) file -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting Ensoniq 5880 soundcard to work again after 2.4 to 2.6 kernel upgrade.
On 2006-02-23, Colin <[EMAIL PROTECTED]> wrote: > Adam Funk wrote: >> lsmod includes the following: >> >> es1371 36864 0 >> snd_ens137125252 0 > > You're loading both the OSS and ALSA versions of the sound module. You > have to choose just one. I recommend the ALSA version (snd_ens1371). > Make sure the other module (es1371) isn't in the /etc/modules file and > that the alsa-base and alsa-utils packages are installed with apt-get > (or aptitude or synaptic or...) My /etc/modules file says it's generated automatically from /etc/modutils, so I used my investigative hammer: /etc $ grep 1371 modules.conf alias sound-slot-0 es1371 /etc $ grep -r 1371 modutils/ modutils/sndconfig:alias sound-slot-0 es1371 /etc $ cat modutils/sndconfig alias sound-slot-0 es1371 post-install sound-slot-0 /bin/aumix -f /etc/.aumixrc -L >/dev/null 2>&1 || : pre-remove sound-slot-0 /bin/aumix -f /etc/.aumixrc -S >/dev/null 2>&1 || : I haven't tampered with anything in /etc/modutils/ yet -- should I edit modutils/sndconfig and replace es1371 with snd_ens1371. I've just tried # rmmod es1371 but it didn't help. (lsmod showed that snd_ens1371 was still there but not es1371.) Does that mean anything to you? Thanks, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting Ensoniq 5880 soundcard to work again after 2.4 to 2.6 kernel upgrade.
Adam Funk wrote: > lsmod includes the following: > > es1371 36864 0 > snd_ens137125252 0 You're loading both the OSS and ALSA versions of the sound module. You have to choose just one. I recommend the ALSA version (snd_ens1371). Make sure the other module (es1371) isn't in the /etc/modules file and that the alsa-base and alsa-utils packages are installed with apt-get (or aptitude or synaptic or...) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting Ensoniq 5880 soundcard to work again after 2.4 to 2.6 kernel upgrade.
Adam Funk escribe: > I'm now running a 2.6.8 kernel and my sound card, which worked find > with 2.4.*, no longer works. (The XFCE4 volume control won't adjust > above 0, and when I run XMMS it runs through the sound files at very > high speed and produces no sound.) > > `lscpi` describes the card thus: > > :00:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02) > Subsystem: Ensoniq Creative Sound Blaster AudioPCI128 > Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR+ FastB2B- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- > SERR- Latency: 32 (3000ns min, 32000ns max) > Interrupt: pin A routed to IRQ 209 > Region 0: I/O ports at d000 [size=64] > Capabilities: [dc] Power Management version 1 > Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > > The devices appear normal (I think): /dev/dmmidi /dev/dsp /dev/midi > and /dev/mixer are symlinks to /dev/sound/dmmidi /dev/sound/dsp > /dev/sound/midi and /dev/sound/mixer, which exist: > > $ ls -l /dev/sound/ > total 0 > crw-rw 1 root audio 14, 9 1970-01-01 01:00 dmmidi > crw-rw 1 root audio 14, 3 1970-01-01 01:00 dsp > crw-rw 1 root audio 14, 2 1970-01-01 01:00 midi > crw-rw 1 root audio 14, 0 1970-01-01 01:00 mixer > > > lsmod includes the following: > > ac97_codec 18700 1 es1371 > audio 48064 0 > es1371 36864 0 > snd57380 7 > snd_ens1371,snd_ac97_codec,snd_usb_audio,snd_rawmidi,snd_seq_device,snd_pcm,snd_timer > snd_ac97_codec 69508 1 snd_ens1371 > snd_ens137125252 0 > snd_page_alloc 11720 1 snd_pcm > snd_pcm97480 2 snd_ens1371,snd_usb_audio > snd_rawmidi25316 2 snd_ens1371,snd_usb_audio > snd_seq_device 8264 1 snd_rawmidi > snd_timer 25668 1 snd_pcm > snd_usb_audio 72544 0 > soundcore 10336 3 es1371,snd,audio > usbcore 118308 10 > usbhid,ehci_hcd,uhci_hcd,snd_usb_audio,audio,pwc,ohci_hcd,usb_storage > > I would appreciate any suggestions on how to fix this. Does /proc/asound/cards list your card? Try unmutting outputs using alsamixer, also try playing a test wave file using aplay. Cordially, Ismael -- mí, myself et moi http://lamediahostia.blogspot.com/ http://www.flickr.com/photos/ivalladt/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
