This is the old SliTaz forum - Please use the main forum.slitaz.org

KORG nanoKEY - Howto make it work - Kernel Module
  • KSFKSF August 2010
    Hello, my name is John, and first of all I wish to thank for your comments and help.
    The title says it all, I need to make work my KORG nanoKEY inside Slitaz 3.0 stable, I have trouble with Java midi classes and the MuSE program, they simply don't detect the keyboard, although it was detected as it shows the lsusb command in its output (the system sees it, the programs don't).
    I added my normal user to the root group, to have administrative privileges, to prevent permission problems.

    I hope you can help me, thanks in advance.

    John

    //.

    CONTEXT INFORMATION

    HW: AMD Athlon 64, 2 GB RAM, USB KORG nanoKEY
    SW: Slitaz 3 stable, MuSE, Java Midi classes

    lsmod output:

    Module Size Used by Tainted: G
    snd_pcm_oss 29240 0
    snd_mixer_oss 11844 1 snd_pcm_oss
    usbip 12208 0
    usbip_common_mod 9608 1 usbip
    amd64_agp 8952 1
    agpgart 25980 1 amd64_agp
    k8temp 3820 0
    hwmon 2028 1 k8temp
    snd_via82xx_modem 9736 0
    snd_via82xx 20416 1
    gameport 9348 1 snd_via82xx
    snd_ac97_codec 88736 2 snd_via82xx_modem,snd_via82xx
    ac97_bus 1308 1 snd_ac97_codec
    snd_pcm 51780 4 snd_pcm_oss,snd_via82xx_modem,snd_via82xx,snd_ac97_codec
    snd_timer 16344 1 snd_pcm
    snd_page_alloc 7256 3 snd_via82xx_modem,snd_via82xx,snd_pcm
    snd_mpu401_uart 5612 1 snd_via82xx
    snd_rawmidi 16920 1 snd_mpu401_uart
    snd_seq_device 5544 1 snd_rawmidi
    snd 43584 12 snd_pcm_oss,snd_mixer_oss,snd_via82xx_modem,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
    soundcore 5180 1 snd

    lsusb output:

    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 003: ID 0944:010d KORG, Inc.
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  • Trixar_zaTrixar_za August 2010
    lsusb just reports that the device is there and that it's connected. The system might just not know what to do with it.

    Could you unplug the device and plug it back in? Paste what the dmesg command outputs. Maybe it's not being assigned properly.
  • KSFKSF August 2010
    Hello Trixar_za,
    Thanks for the response.

    I paste part of the dmesg output (the lines which refer to the USB ports), I cut them because of the number (>300).
    If you don't see anything, I'll post everything.

    John.

    .//

    DMESG OUTPUT (last 118 lines)

    ...
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci_hcd 0000:00:10.4: PCI INT C -> GSI 21 (level, low) -> IRQ 21
    ehci_hcd 0000:00:10.4: EHCI Host Controller
    ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:10.4: irq 21, io mem 0xfad00000
    ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 8 ports detected
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    uhci_hcd: USB Universal Host Controller Interface driver
    uhci_hcd 0000:00:10.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
    uhci_hcd 0000:00:10.0: UHCI Host Controller
    uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
    uhci_hcd 0000:00:10.0: irq 21, io base 0x0000b800
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 2 ports detected
    uhci_hcd 0000:00:10.1: PCI INT A -> GSI 21 (level, low) -> IRQ 21
    uhci_hcd 0000:00:10.1: UHCI Host Controller
    uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
    uhci_hcd 0000:00:10.1: irq 21, io base 0x0000c000
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    uhci_hcd 0000:00:10.2: PCI INT B -> GSI 21 (level, low) -> IRQ 21
    uhci_hcd 0000:00:10.2: UHCI Host Controller
    uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
    uhci_hcd 0000:00:10.2: irq 21, io base 0x0000c400
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    uhci_hcd 0000:00:10.3: PCI INT B -> GSI 21 (level, low) -> IRQ 21
    uhci_hcd 0000:00:10.3: UHCI Host Controller
    uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 5
    uhci_hcd 0000:00:10.3: irq 21, io base 0x0000c800
    usb usb5: configuration #1 chosen from 1 choice
    hub 5-0:1.0: USB hub found
    hub 5-0:1.0: 2 ports detected
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    input: PC Speaker as /devices/platform/pcspkr/input/input0
    cpuidle: using governor ladder
    cpuidle: using governor menu
    usbcore: registered new interface driver hiddev
    usbcore: registered new interface driver usbhid
    usbhid: v2.6:USB HID core driver
    TCP cubic registered
    NET: Registered protocol family 17
    NET: Registered protocol family 15
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    Using IPI No-Shortcut mode
    input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
    ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata1.00: ATA-7: SAMSUNG HD080HJ, WT100-41, max UDMA7
    ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata1.00: configured for UDMA/133
    scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD080HJ WT10 PQ: 0 ANSI: 5
    sd 0:0:0:0: [sda] 156301488 512-byte hardware sectors: (80.0 GB/74.5 GiB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda:<5>sd 0:0:0:0: Attached scsi generic sg0 type 0
    sda1 sda2
    sd 0:0:0:0: [sda] Attached SCSI disk
    usb 4-1: new full speed USB device using uhci_hcd and address 2
    input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input2
    ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
    EXT3-fs: INFO: recovery required on readonly filesystem.
    EXT3-fs: write access will be enabled during recovery.
    usb 4-1: configuration #1 chosen from 1 choice
    usb 4-1: USB disconnect, address 2
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: recovery complete.
    EXT3-fs: mounted filesystem with writeback data mode.
    VFS: Mounted root (ext3 filesystem) readonly on device 8:2.
    Freeing unused kernel memory: 328k freed
    usb 4-1: new full speed USB device using uhci_hcd and address 3
    usb 4-1: configuration #1 chosen from 1 choice
    EXT3 FS on sda2, internal journal
    udev: starting version 150
    VIA 82xx Audio 0000:00:11.5: PCI INT C -> GSI 22 (level, low) -> IRQ 22
    VIA 82xx Audio 0000:00:11.5: setting latency timer to 64
    codec_read: codec 0 is not valid [0xfe0000]
    codec_read: codec 0 is not valid [0xfe0000]
    codec_read: codec 0 is not valid [0xfe0000]
    codec_read: codec 0 is not valid [0xfe0000]
    VIA 82xx Modem 0000:00:11.6: enabling device (0000 -> 0001)
    VIA 82xx Modem 0000:00:11.6: PCI INT C -> GSI 22 (level, low) -> IRQ 22
    VIA 82xx Modem 0000:00:11.6: setting latency timer to 64
    VIA 82xx Modem 0000:00:11.6: PCI INT C disabled
    VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
    Linux agpgart interface v0.103
    agpgart-amd64 0000:00:00.0: AGP bridge [1106/0204]
    agpgart-amd64 0000:00:00.0: AGP aperture is 64M @ 0xf0000000
    Adding 3905528k swap on /dev/sda1. Priority:-1 extents:1 across:3905528k
    eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
    usbip_common_mod: module is from the staging directory, the quality is unknown, you have been warned.
    usbip_common_mod: usbip common driver1.0<4>usbip: module is from the staging directory, the quality is unknown, you have been warned.
    usbip 4-1:1.0: this device 4-1 is not in match_busid table. skip!
    usbcore: registered new interface driver usbip
    usbip:Stub Driver for USB/IP:1.0
    ISO 9660 Extensions: Microsoft Joliet Level 3
    ISO 9660 Extensions: RRIP_1991A
    usb 4-1: USB disconnect, address 3
    usb 3-2: new full speed USB device using uhci_hcd and address 2
    usb 3-2: configuration #1 chosen from 1 choice
    usbip 3-2:1.0: this device 3-2 is not in match_busid table. skip!
    Generic RTC Driver v1.07
    usb 3-2: USB disconnect, address 2
    usb 4-1: new full speed USB device using uhci_hcd and address 4
    usb 4-1: configuration #1 chosen from 1 choice
    usbip 4-1:1.0: this device 4-1 is not in match_busid table. skip!

  • Trixar_zaTrixar_za August 2010
    Two things I find interesting is:
    usbip_common_mod: module is from the staging directory, the quality is unknown, you have been warned.
    usbip_common_mod: usbip common driver1.0<4>usbip: module is from the staging directory, the quality is unknown, you have been warned.

    And:
    usb 4-1: new full speed USB device using uhci_hcd and address 4
    usb 4-1: configuration #1 chosen from 1 choice
    usbip 4-1:1.0: this device 4-1 is not in match_busid table. skip!

    For the last one, try typing:
    echo 'add 4-1' > /sys/bus/usb/drivers/usbip/match_busid
    and
    echo '4-1' > /sys/bus/usb/drivers/usbip/match_busid
    in your terminal (changing the 4-1 to whatever dmesg says the device number is now is now) and see if that does anything (I'm asking you to do both, because I'm actually unsure how it expects you to add the number). From what I've read it might be a bug in that module.

    Alternatively, you may need to connect your device to the proper channel using the aconnect command. Links about it is found here:
    http://www.headphonedeals.com/joomla/tmresearch/38-catresearch/99-korg-nanokey-review
    http://alsa.opensrc.org/index.php/Aconnect

    There is also a GUI interface for it called aconnectgui, but it seems to be mostly Debian and Ubuntu based. It could probably be converted over to SliTaz if somebody takes the time to do it.
  • KSFKSF August 2010
    Hi Trixar_za
    I tried your first alternative, and didn't have deal.

    I am going to compile aconnectgui, to check out if this problem can be solved, and have a try installing Zynaddsub-FX, and see how it goes.

    Thank you for your kind help, any advance I have with these duties it will be posted here in this thread.

    See you.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership

SliTaz Social