Re: [Line6linux-user] HD300 on Mint, need help

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Am Montag, 17. Dezember 2012, 13:22:28 schrieb Greg Schwimer:
> ----- Original Message -----
> 
> > From: "Stefan Hajnoczi" <ste...@gm...>
> > To: "Greg Schwimer" <sc...@bi...>
> > Cc: lin...@li...
> > Sent: Monday, December 17, 2012 9:31:18 AM
> > Subject: Re: [Line6linux-user] HD300 on Mint, need help
> > 
> > On Mon, Dec 17, 2012 at 5:03 PM, Greg Schwimer <sc...@bi...>
> > 
> > wrote:
> > > ----- Original Message -----
> > > 
> > >> From: "Stefan Hajnoczi" <ste...@gm...>
> > >> To: "Greg Schwimer" <sc...@bi...>
> > >> Cc: lin...@li...
> > >> Sent: Sunday, December 16, 2012 11:45:49 PM
> > >> Subject: Re: [Line6linux-user] HD300 on Mint, need help
> > >> 
> > >> On Mon, Dec 17, 2012 at 5:20 AM, Greg Schwimer
> > >> <sc...@bi...>
> > >> 
> > >> wrote:
> > >> > I have an HD300 that simply will not work with linux.
> > >> > 
> > >> > System: Linux Mint 13 "Maya", Kernel 3.2.0-23. I have the output
> > >> > of
> > >> > sysinfo.sh below for more info.
> > >> > 
> > >> > I plug the HD300 in. The system detects a new USB device, and an
> > >> > lsmod shows
> > >> > the driver loads:
> > >> > 
> > >> > line6usb               82196  0
> > >> > snd_pcm                80845  4
> > >> > line6usb,snd_ca0106,snd_ac97_codec,snd_usb_audio
> > >> > snd_rawmidi            25424  4
> > >> > line6usb,snd_ca0106,snd_usbmidi_lib,snd_seq_midi
> > >> > snd                    62064  15
> > >> > line6usb,snd_ca0106,snd_ac97_codec,snd_usb_audio,snd_hwdep,snd_usbmid
> > >> > i_lib,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
> > >> > 
> > >> > 
> > >> > However, I cannot see the audio interfaces at all, anywhere,
> > >> > including in
> > >> > /proc/asound.
> > >> > 
> > >> > I see the following in /var/log/syslog when I plug the HD300 in:
> > >> > 
> > >> > Dec 16 21:10:08 minion kernel: [98107.288113] usb 5-1: new
> > >> > full-speed USB
> > >> > device number 8 using uhci_hcd
> > >> > Dec 16 21:10:08 minion mtp-probe: checking bus 5, device 8:
> > >> > "/sys/devices/pci0000:00/0000:00:1d.3/usb5/5-1"
> > >> > Dec 16 21:10:08 minion mtp-probe: bus: 5, device: 8 was not an
> > >> > MTP
> > >> > device
> > >> > 
> > >> > 
> > >> > Any clues?
> > >> > 
> > >> > ##################################################################
> > >> > ##################################################################
> > >> > 
> > >> > ---------------------------------------------------------------------
> > >> > ----------- output of "uname -a":
> > >> > Linux minion 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:41:14
> > >> > UTC 2012
> > >> > i686 i686 i386 GNU/Linux
> > >> > 
> > >> > ---------------------------------------------------------------------
> > >> > ----------- output of "cat /sys/module/line6usb/version":
> > >> > 0.9.1beta (revision
> > >> > https://line6linux.svn.sourceforge.net/svnroot/line6linux/driver/trun
> > >> > k@972)
> > >> 
> > >> Did you need to modify the driver to make it compile for your
> > >> kernel?
> > >> 
> > >> Stefan
> > > 
> > > No - it compiled and installed cleanly from what I can tell.
> > 
> > I have no explanation - the output you posted suggests that the
> > driver
> > is not matching the device you plugged in.  Therefore you don't get
> > the "Line6 POD HD300 found" message that you normally see at the very
> > beginning when the device is detected.
> > 
> > I suggest you do the following to further debug what is going on:
> > 
> > Please check that you have the following line in /lib/modules/$(uname
> > -r)/modules.alias:
> > alias usb:v0E41p5057d*dc*dsc*dp*ic*isc*ip*in* line6usb
> > 
> > This is normally automatically added when you install the kernel
> > module.  It's how the system knows to load the line6usb driver when
> > you plug in the POD HD300.
> > 
> > Once you're sure the modules.alias line is there, restart your
> > computer and don't manually modprobe the driver.  When you plug in
> > the
> > POD the driver should be automatically loaded - you can check with
> > lsmod | grep line6usb.
> > 
> > Now check dmesg and see if there is a "Line6 POD HD300 found" message
> > or anything else about line6 or the USB device.
> > 
> > If the module is being loaded but you're getting no dmesg logs about
> > it, double-check that your dmesg log level allows dev_info() messages
> > through (please search for how to do this, I can't remember).  Then
> > the next step would be to add a printk() to
> > drivers/staging/line6/driver.c:line6_probe() so we know the kernel is
> > asking the line6 driver to try the new device.
> > 
> > Stefan
> 
> Yes, that was what I was thinking. However, the module is installing when I
> plug the device in. Yet, there are no logfiles indicating it that I can
> find.
> 
> Anyway, here is what the modules.alias file includes:
> 
>      --snip--snip--
>      ...
>      alias usb:v0E41p5057d*dc*dsc*dp*ic*isc*ip* line6usb
>      ...
>      --snip--snip--
> 
> It was there, with the exception of the "in*".  They're all missing that.
> So, I adjusted that one line, rebooted, and got the same result. The module
> is installed automatically per lsmod, but no audio devices are installed.
> 
> I'm working on figuring out how to adjust dmesg per your recommendation.
> Regarding adding printk() to line6_probe(), I admit that I'm not in danger
> of becoming a C developer any time soon, so I'm not quite sure what that
> looks like.
Look up the line starting with "static int line6_probe" in driver.c and more 
or less randomly add the line

	printk("%s:%d", __FILE__, __LINE__);

to the code. If you pick a location where it is not allowed, the compiler will 
tell you. Most interesting is close to "if(...)" statements to see which 
decisions are made by the driver.

Alternatively, this can be done fully automatically as described here:

https://line6linux.svn.sourceforge.net/svnroot/line6linux/driver/trunk/checkpoint/README.txt

However, I didn't test this for a while, it may or may not work with your 
kernel version.

	Kind regards,
		Markus