Re: debian xfce network tethering an SGS2 [long, with syslog extract]
On 27/11/2013 10:58, Roland Mueller wrote:
for tethering you shouln't need a package at all: on phone side you should
be able setup USB debugging mode (permanently) and enable tethering after
the phone has been connected to the Linux machine.
Having D7/XFCE and a Samsung Galaxy S2 (SGS2) I thought I'd try this,
but without success, so far.
Expected behaviour:
- Plug in SGS2 to laptop USB port, set USB tethering
- See a new interface listed in wicd
- Be able to choose to connect, disconnect, set IP settings, DNS, etc
Actual behaviour:
- Plug in SGS2 to laptop USB port, set USB tethering:
Done
- See a new interface listed in wicd:
SGS2 or usb connection not listed
- Be able to choose to connect, disconnect, set IP settings, DNS, etc:
Unable
Not much of an expert on network drivers etc in Linux, so would
welcome some guidance on exactly where to look for the problem, but
here are the relevant syslog entries. The first block is when
plugging in the SGS2, before the USB tethering was selected. The
second block is the Debian response once the SGS2 was in tethering
mode. [The syslog extracts have had date, time, and machine name
removed to make the lines shorter, and easier to post and read.]
Log of initial SGS2 to USB connection
kernel: [ 98.648208] usb 7-5: new high-speed USB device number 4 using ehci_hcd
kernel: [ 98.782415] usb 7-5: New USB device found, idVendor=04e8, idProduct=6860
kernel: [ 98.782425] usb 7-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [ 98.782432] usb 7-5: Product: SAMSUNG_Android
kernel: [ 98.782438] usb 7-5: Manufacturer: SAMSUNG
kernel: [ 98.782443] usb 7-5: SerialNumber: [nnnnnn]
kernel: [ 98.845013] cdc_acm 7-5:1.0: This device cannot do calls on its own. It is not a modem.
kernel: [ 98.845247] cdc_acm 7-5:1.0: ttyACM0: USB ACM device
kernel: [ 98.845798] usbcore: registered new interface driver cdc_acm
kernel: [ 98.845805] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
kernel: [ 101.054841] usb 7-5: USB disconnect, device number 4
kernel: [ 101.324179] usb 7-5: new high-speed USB device number 5 using ehci_hcd
kernel: [ 101.458294] usb 7-5: New USB device found, idVendor=04e8, idProduct=6860
kernel: [ 101.458304] usb 7-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [ 101.458312] usb 7-5: Product: SAMSUNG_Android
kernel: [ 101.458317] usb 7-5: Manufacturer: SAMSUNG
kernel: [ 101.458323] usb 7-5: SerialNumber: [nnnnnn]
kernel: [ 101.459986] cdc_acm 7-5:1.1: This device cannot do calls on its own. It is not a modem.
kernel: [ 101.460218] cdc_acm 7-5:1.1: ttyACM0: USB ACM device
kernel: [ 102.368337] usb 7-5: USB disconnect, device number 5
20 seconds later, after finding my way through the Android menus, USB
tethering was switched on the phone; here's the syslog following that:
kernel: [ 121.728222] usb 7-5: new high-speed USB device number 6 using ehci_hcd
kernel: [ 121.862377] usb 7-5: New USB device found, idVendor=04e8, idProduct=6863
kernel: [ 121.862392] usb 7-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: [ 121.862400] usb 7-5: Product: SAMSUNG_Android
kernel: [ 121.862405] usb 7-5: Manufacturer: SAMSUNG
kernel: [ 121.862410] usb 7-5: SerialNumber: [nnnnnn]
udevd[3360]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci0000:00/0000:00:1d.7/usb7/7-5 7 6': No such file or directory
kernel: [ 121.940297] usbcore: registered new interface driver cdc_ether
kernel: [ 121.944679] rndis_host 7-5:1.0: usb0: register 'rndis_host' at usb-0000:00:1d.7-5, RNDIS device, [xx:xx:MAC_of_SGS2:xx]
kernel: [ 121.944806] usbcore: registered new interface driver rndis_host
kernel: [ 121.957209] usbcore: registered new interface driver rndis_wlan
Notes:
(a) The udevd line is very long, so I've added a blank line above and
below it for readability on the list in cases where the reader will
wrap the text
(b) wicd does not list this usb interface, listing only its existing
wired ethernet adaptor, and the different wifi networks that its
built-in wifi device can receive.
Does the syslog extract show it working, or not? Perhaps there is
another log that would be useful - I checked dmesg but that contained
nothing since startup. /etc/network/interfaces only contained eth0
(the wired socket on the laptop). Should wicd be able to list the
SGS2/usb device or connection?
Not knowing much about the networking setup in the machine, I really
Would be very grateful for any suggestions; it would be worth getting
it to work.
regards, Ron
Reply to: