Andrew Morton wrote:
Sid Boyce <[EMAIL PROTECTED]> wrote:
Andrew Morton wrote:
Sid Boyce <[EMAIL PROTECTED]> wrote:
PhoneSkype USB Phone SK-04.
It gets detected, is registered in /sys/bus/usb as a Keypad. Everything
else USB works including the phone handset. Nothing is detected by
showkey when keys are pressed.
# less /sys/bus/usb/devices/usb3/3-2/3-2:1.3/interface
Keypad
/dev/usb/hiddev? and /dev/input/keyboard say they are not valid devices
and they are the ones created by the SuSE 9.3 install, not by udev.
From dmesg
----------
usbcore: registered new driver hiddev
drivers/usb/input/hid-core.c: timeout initializing reports
=============================
input: USB HID v1.10 Keyboard [BeyondTel USB Phone] on usb-0000:00:02.1-2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
input: USB HID v1.00 Joystick [CH PRODUCTS CH FLIGHT SIM YOKE USB ] on
usb-0000:00:02.1-1.1
input: USB HID v1.00 Joystick [CH PRODUCTS CH PRO PEDALS USB ] on
usb-0000:00:02.1-1.4
I am puzzled by the fact that the keypad is recognised, but I cannot do
anything with it.
# lsusb
Bus 003 Device 009: ID 04b8:0103 Seiko Epson Corp. Perfection 610
Bus 003 Device 008: ID 067b:3507 Prolific Technology, Inc.
Bus 003 Device 007: ID 068e:00f2 CH Products, Inc. Flight Sim Pedals
Bus 003 Device 006: ID 05e3:0760 Genesys Logic, Inc. Card Reader
Bus 003 Device 005: ID 03f0:0604 Hewlett-Packard DeskJet 840c
Bus 003 Device 004: ID 068e:00ff CH Products, Inc. Flight Sim Yoke
Bus 003 Device 003: ID 04b4:0303 Cypress Semiconductor Corp. <====
Bus 003 Device 002: ID 0451:2077 Texas Instruments, Inc. TUSB2077 Hub
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Was this hardware known to work on ealier kernels? If so, which?
Is this working OK now?
If not, I think a fresh report is needed - please cc
linux-usb-devel@lists.sourceforge.net, thanks.
Sadly no, the problem is still the same with up to 2.6.13-rc3-git9. I've
had a look around the skypejournal site and found some stuff suggesting
user space tools may be needed, the example program at
http://share.skype.com/developer_zone/documentation/skype_api_for_linux/
skype-dbus-testclient-20050422.tar.bz2 does not build.
barrabas:/ftp/jul05/skype.dbus # make
g++ -c -pipe -Wall -W -g -DDBUS_API_SUBJECT_TO_CHANGE -ggdb -DQT_SHARED
-DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I/usr/lib/qt3/mkspecs/default -I.
-I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
-I/usr/lib/qt3/include -I.ui/ -I.moc/ -o .obj/main.o main.cpp
Assembler messages:
FATAL: can't create .obj/main.o: No such file or directory
make: *** [.obj/main.o] Error 2
Although all the signs are that it is detected, YaST hardware info does
not report it and it doesn't bind to a device.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
Retired IBM Mainframes and Sun Servers Tech Support Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks
barrabas:/ # cat /proc/asound/oss/sndstat
Sound Driver:3.8.1a-980706 (ALSA v1.0.9rc2 emulation code)
Kernel: Linux barrabas 2.6.12-rc6-git81 #1 Fri Jun 17 20:27:31 BST 2005 i686
Config options: 0
Installed drivers:
Type 10: ALSA emulation
Card config:
NVidia nForce2 with ALC650F at 0xed080000, irq 201
BeyondTel USB Phone at usb-0000:00:02.1-2, full speed
Audio devices:
0: NVidia nForce2 (DUPLEX)
1: USB Audio (DUPLEX)
Synth devices: NOT ENABLED IN CONFIG
Midi devices: NOT ENABLED IN CONFIG
Timers:
7: system timer
Mixers:
0: Realtek ALC650F
1: USB Mixer
# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: CH [NVidia nForce2], device 0: Intel ICH [NVidia nForce2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CH [NVidia nForce2], device 2: Intel ICH - IEC958 [NVidia nForce2 -
IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Phone [USB Phone], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
# arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: CH [NVidia nForce2], device 0: Intel ICH [NVidia nForce2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CH [NVidia nForce2], device 1: Intel ICH - MIC ADC [NVidia nForce2 -
MIC ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Phone [USB Phone], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
>From "cat /proc/bus/usb/devices".
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=04b4 ProdID=0303 Rev= 1.00
S: Manufacturer=BeyondTel
S: Product=USB Phone
S: SerialNumber=0004
C:* #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio
I: If#= 1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
I: If#= 1 Alt= 1 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
E: Ad=08(O) Atr=09(Isoc) MxPS= 16 Ivl=1ms
I: If#= 2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
I: If#= 2 Alt= 1 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
E: Ad=88(I) Atr=01(Isoc) MxPS= 16 Ivl=1ms
I: If#= 3 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
E: Ad=01(O) Atr=03(Int.) MxPS= 64 Ivl=1ms
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
barrabas:/home/lancelot # less /sys/bus/usb/devices/usb3/3-2/3-2:1.3/interface
Keypad
# udevinfo -a -p /sys/bus/usb/devices/usb3/3-2/3-2:1.3
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at class device '/sys/bus/usb/devices/usb3/3-2/3-2:1.3':
SUBSYSTEM="unknown"
SYSFS{bAlternateSetting}=" 0"
SYSFS{bInterfaceClass}="03"
SYSFS{bInterfaceNumber}="03"
SYSFS{bInterfaceProtocol}="00"
SYSFS{bInterfaceSubClass}="00"
SYSFS{bNumEndpoints}="02"
SYSFS{interface}="Keypad"
SYSFS{modalias}="usb:v04B4p0303d0100dc00dsc00dp00ic03isc00ip00"
# udevinfo -a -p /sys/bus/usb/devices/usb3/3-2
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at class device '/sys/bus/usb/devices/usb3/3-2':
SUBSYSTEM="unknown"
SYSFS{bConfigurationValue}="1"
SYSFS{bDeviceClass}="00"
SYSFS{bDeviceProtocol}="00"
SYSFS{bDeviceSubClass}="00"
SYSFS{bMaxPower}="100mA"
SYSFS{bNumConfigurations}="1"
SYSFS{bNumInterfaces}=" 4"
SYSFS{bcdDevice}="0100"
SYSFS{bmAttributes}="80"
SYSFS{configuration}="USB Phone"
SYSFS{devnum}="3"
SYSFS{idProduct}="0303"
SYSFS{idVendor}="04b4"
SYSFS{manufacturer}="BeyondTel"
SYSFS{maxchild}="0"
SYSFS{product}="USB Phone"
SYSFS{serial}="0004"
SYSFS{speed}="12"
SYSFS{version}=" 1.00"
barrabas:/ftp/jul05 # cat /proc/bus/input/devices
I: Bus=0003 Vendor=04b4 Product=0303 Version=0100
N: Name="BeyondTel USB Phone"
P: Phys=usb-0000:00:02.1-2/input3
H: Handlers=kbd event0
B: EV=100003
B: KEY=e080ffdf 1cfffff ffffffff fffffffe
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 34
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 34, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 28
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 28, Value: 1
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Disconnected device: usb-0000:00:02.1-2/input3
evbug.c: Disconnected device: usb-0000:00:02.1-1.1/input0
evbug.c: Disconnected device: usb-0000:00:02.1-1.4/input0
evbug.c: Disconnected device: isa0061/input0
evbug.c: Disconnected device: isa0060/serio0/input0
evbug.c: Disconnected device: isa0060/serio1/input0
