[PlanetCCRMA] sndcard now lost when booting ccrma kernel in FC2

Thu Mar 9 15:12:01 2006

On Thu, 2006-03-09 at 21:58 +0100, Nigel Henry wrote:
> On Thursday 09 March 2006 03:11, Fernando Lopez-Lezcano wrote:
> > On Wed, 2006-03-08 at 17:41 -0800, Mark Knecht wrote:
> > > On 3/8/06, Mark Knecht <markknecht@gmail.com> wrote:
> > > > On 3/8/06, nigel henry <cave.dnb@tiscali.fr> wrote:
> > > > > Mar  8 01:59:43 localhost alsactl: /usr/sbin/alsactl:
> > > > > set_control:930: Mar  8 01:59:43 localhost alsactl: warning: name
> > > > > mismatch (Music Playback Volume/Synth Playback Volume) for control #6
> > > > > Mar  8 01:59:43 localhost alsactl: /usr/sbin/alsactl:
> > > > > set_control:932: warning: index mismatch (0/0) for control #6
> > > > > Mar  8 01:59:43 localhost alsactl: /usr/sbin/alsactl:
> > > > > set_control:934: failed to obtain info for control #6 (Operation not
> > > > > permitted)
> > > >
> > > > It looks to me like possibly the /etc/asound.state file is set for an
> > > > older version of the alsamixer stuff and Alsa is getting confused.
> > > > Have you possibly tried removing that file and restarting Alsa? If you
> > > > don't get the messages again then run alsamixer and see if you can
> > > > bring levels up.
> > > >
> > > > Just guesses on my part.
> > >
> > > This part of dmesg is pretty ominious also:
> > >
> > > uhci_hcd 0000:00:07.3: UHCI Host Controller
> > > uhci_hcd 0000:00:07.3: irq 11, io base 0xc800
> > > uhci_hcd 0000:00:07.3: new USB bus registered, assigned bus number 2
> > > usb 1-1: new full speed USB device using uhci_hcd and address 2
> > > hub 2-0:1.0: USB hub found
> > > hub 2-0:1.0: 2 ports detected
> > > snd_usb_audio: Unknown parameter `'
> > > snd_usb_audio: Unknown parameter `'
> >
> > Try looking at the /etc/modprobe.conf file, make sure that none of the
> > lines have extra spaces at the end (specially the "options" lines). Save
> > the file, do a "/sbin/depmod -a", try reloading the sound driver...
>
> Hi Fernando. Thanks for the help. I looked at the options lines, and there 
> appeared to be 2 extra spaces. Rebooted and the sounds worked but no USB. 
> Went back to /etc/modprobe.conf, and removed all the lines I'd entered at the 
> initial install, apart from, alias snd-card-0 snd-emu10k1, and alias 
> sound-slot-0 snd-emu10k1, which had been originally set by alsaconf. 
> Rebooted, and got both soundcard and USB back, but loaded in the wrong order, 
> as to be expected. Re-entered the lines I'd removed.
> alias snd-card-1 snd-usb-audio
> alias sound-slot-1 snd-card-1
> options snd-emu10k1 index=0
> options snd-usb-audio index=1
> Rebooted, and it all works ok like nothing had happened.
> 
> All a bit weird, as everything was working ok before I removed the 
> 2.6.10-0.6.rdt kernel, and installed 2.6.11-0.3.rdt, and it's 
> kernel-module-alsa package. Where did the extra spaces come from, that messed 
> everything up? 

I really really don't know. I suspect that it must be kudzu or one of
the hardware configuration daemons (or whatever) that
rewrites /etc/modprobe.conf at boot time.

> And why did the older kernel, 2.6.10-2.1.ll Still work, and 
> have no problems with the sounds or the USB, even though these extra spaces 
> were there?

Hmmm, different versions of alsa I guess. Maybe the newer ones are more
picky about arguments to the module load process. But no hard data to
back this up. 

> I keep repeating to myself. "If it works, don't mess with it" . Thanks again 
> for the help. Nigel.

Sigh, sorry for the trouble. 
-- Fernando

> > > midi: probe of 1-1:1.0 failed with error -5
> > > usb-midi: Found MIDISTREAMING on dev 0a4d:0066, iface 1
> > > usb-midi: Found MIDIStreaming device corresponding to Release 1.00 of
> > > spec. usb-midi: Found IN Jack 0x01 EMBEDDED
> > > usb-midi: Found IN Jack 0x02 EXTERNAL
> > > usb-midi: Found OUT Jack 0x03 EMBEDDED, 1 pins
> > > usb-midi: Found OUT Jack 0x04 EXTERNAL, 1 pins
> > > modprobe/1049: BUG in usb_maxpacket at include/linux/usb.h:1118
> > >  [<f88e3113>] alloc_midi_in_endpoint+0x173/0x1e0 [usb_midi] (8)
> > >  [<f88e3cf7>] alloc_usb_midi_device+0xb7/0x7a0 [usb_midi] (48)
> > >  [<c01da352>] vsnprintf+0x262/0x4f0 (40)
> > >  [<c011f2af>] call_console_drivers+0x9f/0x130 (16)
> > >  [<f88e45fc>] detect_midi_subclass+0xbc/0xe0 [usb_midi] (172)
> > >  [<f88e47e9>] usb_midi_probe+0x89/0x120 [usb_midi] (36)
> > >  [<c028d82f>] usb_probe_interface+0x5f/0x80 (28)
> > >  [<c024f8b9>] driver_probe_device+0x29/0x80 (16)
> > >  [<c024fa07>] driver_attach+0x57/0x90 (12)
> > >  [<c024ff10>] bus_add_driver+0xa0/0xd0 (32)
> > >  [<c028d908>] usb_register+0x48/0xb0 (32)
> > >  [<c0138cca>] sys_init_module+0x19a/0x260 (28)
> > >  [<c0103029>] sysenter_past_esp+0x52/0x75 (24)
> > > ---------------------------
> > >
> > > | preempt count: 00000001 ]
> > > | 1-level deep critical section nesting:
> > >
> > > ----------------------------------------
> > > .. [<c0134cbd>] .... print_traces+0xd/0x40
> > > .....[<00000000>] ..   ( <= 0x0)
> > >
> > > usb-midi: fetchString(2)
> > > usb-midi: fetchString = 25
> > > usbmidi: found [ MK-225C USB MIDI keyboard ] (0x0a4d:0x0066), attached:
> > > usbmidi: /dev/midi00: in (ep:81 cid: 0 bufsiz: 0) out (ep:02 cid: 0
> > > bufsiz:64) usbcore: registered new driver midi