can't even get past adp devices under Arch Linux

[Dusty Phillips]

Hey all,

Just trying the instructions at HTC support. I'm using an unmodified
1.0 ADP, no holiday update. I'm pretty sure my issue is Linux
related... I have no reason to blame the ADP update (yet). :-) I'm
using Arch Linux current with kernel 2.6.28 on a 32 bit older thinkpad
X60 Core Duo.

The basic problem is that I can't get the device to show up in adb
devices:
===
dusty:adp1.1 $ adb devices
List of devices attached

dusty:adp1.1 $
===

This is very probably because the device is not showing up in lsusb:
===
dusty:adp1.1 $ lsusb
Bus 002 Device 003: ID 05f3:0007 PI Engineering, Inc. Kinesis
Advantage PRO MPC/USB Keyboard
Bus 002 Device 004: ID 03f0:0b1d Hewlett-Packard
Bus 002 Device 002: ID 05f3:0081 PI Engineering, Inc. Kinesis
Integrated Hub
Bus 002 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0001
Bus 001 Device 001: ID 1d6b:0002
Bus 005 Device 002: ID 0483:2016 SGS Thomson Microelectronics
Fingerprint Reader
Bus 005 Device 001: ID 1d6b:0001
dusty:adp1.1 $
===

I'm relatively confident that none of those unlabelled devices is the
phone, as the exact same list shows up whether or not the phone is
plugged in.

Now, here's the interesting thing. The phone seems to be perfectly
recognized by dmesg:

===
dusty:adp1.1 $ dmesg | tail
usb 1-5: USB disconnect, address 12
usb 1-5: new high speed USB device using ehci_hcd and address 13
usb 1-5: configuration #1 chosen from 1 choice
scsi13 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 13
usb-storage: waiting for device to settle before scanning
scsi 13:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0
ANSI: 2
sd 13:0:0:0: [sdb] Attached SCSI removable disk
sd 13:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
dusty:adp1.1 $
===

At this point the device /dev/sdb is created. If I then touch the
mount button, /dev/sdb1 is also created, and I can mount this to
browse the sd card.

In other words, the usb storage driver seems to be working fine, but
adb has no interest in the phone.

My only guess is that I am missing some kernel module. So here's
lsmod, with apologies for the verbosity:

===
dusty:adp1.1 $ lsmod
Module Size Used by
usbserial 31976 0
nls_cp437 7424 0
vfat 12800 0
fat 50592 1 vfat
usb_storage 95552 0
wlan_tkip 12928 3
ipv6 260340 12
i915 58372 2
drm 83880 3 i915
pcmcia 35532 0
ohci1394 31280 0
yenta_socket 25996 1
rsrc_nonstatic 13056 1 yenta_socket
pcmcia_core 34452 3 pcmcia,yenta_socket,rsrc_nonstatic
video 18704 0
output 4608 1 video
ieee1394 79940 1 ohci1394
sdhci_pci 9088 0
snd_pcsp 11048 0
serio_raw 7172 0
i2c_i801 10896 0
sg 26804 0
i2c_core 22804 1 i2c_i801
psmouse 55828 0
iTCO_wdt 12836 0
iTCO_vendor_support 4996 1 iTCO_wdt
intel_agp 27836 1
agpgart 31572 3 drm,intel_agp
e1000e 114480 0
thermal 17180 0
fan 6276 0
button 7824 0
battery 12036 0
ac 6020 0
ppp_generic 25116 0
slhc 7552 1 ppp_generic
vboxdrv 115368 0
cpufreq_powersave 3456 0
cpufreq_ondemand 8972 0
cpufreq_conservative 7944 2
uinput 9216 0
sdhci 17028 1 sdhci_pci
mmc_core 46876 1 sdhci
shpchp 34068 0
pci_hotplug 28064 1 shpchp
acpi_cpufreq 9868 0
freq_table 5632 2 cpufreq_ondemand,acpi_cpufreq
processor 41388 4 thermal,acpi_cpufreq
evdev 11296 16
thinkpad_acpi 59704 0
rfkill 11596 1 thinkpad_acpi
led_class 5508 1 thinkpad_acpi
nvram 8972 1 thinkpad_acpi
usblp 13952 0
wlan_scan_sta 15104 1
ath_rate_sample 15872 1
ath_pci 246072 0
wlan 222448 5
wlan_tkip,wlan_scan_sta,ath_rate_sample,ath_pci
ath_hal 250976 3 ath_rate_sample,ath_pci
snd_hda_intel 412980 2
snd_hwdep 9092 1 snd_hda_intel
snd_seq_oss 31872 0
snd_seq_midi_event 8192 1 snd_seq_oss
snd_seq 49968 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8204 2 snd_seq_oss,snd_seq
snd_pcm_oss 40192 0
snd_pcm 70020 4 snd_pcsp,snd_hda_intel,snd_pcm_oss
snd_timer 21384 3 snd_seq,snd_pcm
snd_page_alloc 10120 2 snd_hda_intel,snd_pcm
snd_mixer_oss 16512 1 snd_pcm_oss
snd 50852 12
snd_pcsp,snd_hda_intel,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 8160 1 snd
e1000 121540 0
rtc_cmos 12332 0
rtc_core 17564 1 rtc_cmos
rtc_lib 4480 1 rtc_core
usbhid 36640 0
hid 40704 1 usbhid
ext3 127112 1
jbd 46996 1 ext3
mbcache 8708 1 ext3
sd_mod 26904 3
uhci_hcd 24592 0
ehci_hcd 36876 0
usbcore 136848 7
usbserial,usb_storage,usblp,usbhid,uhci_hcd,ehci_hcd
ata_piix 23300 0
ahci 30988 2
ata_generic 6788 0
libata 157856 3 ata_piix,ahci,ata_generic
scsi_mod 102164 4 usb_storage,sg,sd_mod,libata
dusty:adp1.1 $
===

Does anyone have any ideas as to why the device won't show up in
lsusb?

Thanks,
Dusty Phillips

[Jean-Baptiste Queru]

Just making sure...

-adb devices should show the device while it's actively running android.

-fastboot devices should show the device while it's in the bootloader.

-someone kindly mentioned on another thread that your 50-android.rules
files might have to be modified for fastboot:

SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02",SYMLINK
+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c01",SYMLINK
+="android_fastboot"

I hope that helps,
JBQ

--
Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[Dusty Phillips]

On Mar 11, 8:07 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> -someone kindly mentioned on another thread that your 50-android.rules
> files might have to be modified for fastboot:
>
> SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02",SYMLINK
> +="android_adb"
> SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c01",SYMLINK
> +="android_fastboot"

Thanks, JBQ, that's exactly what was required. I've now successfully
updated the ADP. I apologize for missing the earlier thread.

Dusty

[Dusty Phillips]

On Mar 11, 8:07 pm, Jean-Baptiste Queru <j...@android.com> wrote:

> -someone kindly mentioned on another thread that your 50-android.rules
> files might have to be modified for fastboot:
>
> SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02",SYMLINK
> +="android_adb"
> SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c01",SYMLINK
> +="android_fastboot"

[Jean-Baptiste Queru]

Glad to know that fixed it for you. I'll pass the information around
so that the documentation can be udpated.

JBQ