HoRNDIS not creating network adapter

[ronaldace]

Hello!

First of all, thanks for HoRNDIS! I used it a few times with my HTC Desire and it worked nicely.

Recently I upgraded to a Samsung Galaxy S3 Mini. Today I tried using HoRNDIS (release 2) with it, but it seemed not to detect my phone. I saw on the website that there was a new version available, so I deleted the android network interface, deleted the HoRNDIS kext, installed HoRNDIS release 4 and restarted.

Whis this release, using dmesg I can see that HoRNDIS detects the phone when I connect it to the USB port and activate USB tethering, but no network adapter is created in network preferences so I'm not able to use the ISB tethering. Do you know of a way I can create this network adapter? I'm using Snow Leopard, 10.6.8, with 64-bit kernel.

Thanks!

[jwise]

Oh dear -- that's no good.

Can you provide a dmesg log of HoRNDIS detecting it? Additionally, can you provide an 'ifconfig -a' before and after connecting the device?

[ronaldace]

Here it goes:

Before connecting device:

Ronald-MBP:~ Ronald$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 58:b0:35:f3:98:cd
media: autoselect (none)
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr d8:30:62:ff:fe:f7:00:62
media: autoselect
status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether f8:1e:df:e9:c6:74
inet 172.29.21.80 netmask 0xfffffc00 broadcast 172.29.23.255
media: autoselect
status: active
ham0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1404
ether 7a:79:19:1b:1b:22
inet 25.27.27.34 netmask 0xff000000 broadcast 25.255.255.255
open (pid 55)

After connecting device, USB tethering not enabled yet:

Ronald-MBP:~ Ronald$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 58:b0:35:f3:98:cd
media: autoselect (none)
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr d8:30:62:ff:fe:f7:00:62
media: autoselect
status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether f8:1e:df:e9:c6:74
inet 172.29.21.80 netmask 0xfffffc00 broadcast 172.29.23.255
media: autoselect
status: active
ham0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1404
ether 7a:79:19:1b:1b:22
inet 25.27.27.34 netmask 0xff000000 broadcast 25.255.255.255
open (pid 55)

DMESG (latest lines):
Dbg Lev 2, Type 1, OS MJ 10 MN 8
[DGMTP_Drv.cpp][getLogLevel()][00164][BUGS] Enabled
[DGMTP_Drv.cpp][getLogLevel()][00165][ERRO] Enabled
MTP Driver Started (Addr 0xffffff80164be000)

After connecting device, USB tethering enabled:

Ronald-MBP:~ Ronald$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 58:b0:35:f3:98:cd
media: autoselect (none)
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr d8:30:62:ff:fe:f7:00:62
media: autoselect
status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether f8:1e:df:e9:c6:74
inet 172.29.21.80 netmask 0xfffffc00 broadcast 172.29.23.255
media: autoselect
status: active
ham0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1404
ether 7a:79:19:1b:1b:22
inet 25.27.27.34 netmask 0xff000000 broadcast 25.255.255.255
open (pid 55)

DMESG (latest lines, including lines shown before):
Dbg Lev 2, Type 1, OS MJ 10 MN 8
[DGMTP_Drv.cpp][getLogLevel()][00164][BUGS] Enabled
[DGMTP_Drv.cpp][getLogLevel()][00165][ERRO] Enabled
MTP Driver Started (Addr 0xffffff80164be000)
[DGMTP_Drv.cpp][fnEvtReadComplete()][01490][ERRO] INT RD F e00002ed
[DGMTP_Drv.cpp][fnEvtReadComplete()][01515]:[ERRO]INT RD F e000404f
HoRNDIS: init: HoRNDIS tethering driver for Snow Leopard+, by Joshua Wise

[ronaldace]

Hello again,

I've kept trying things. I still have my HTC Desire around, so I tried to see if HoRNDIS release 4 kept working nicely with this device.

I plugged in the Desire, enabled USB tethering and nothing happenned. So, just in case, I disconnected the Desire from the Macbook, disabled KiesAgent and KiesWifiAgent from my startup items and restarted. Then, I connected the Desire again, enabled USB tethering again and I got a message saying that a new network device was detected. Yay!

The dmesg output I get in this situation is as follows:

---

USBMSC Identifier (non-unique): SH0Axxxxxxxxx 0xbb4 0xc87 0x226
HoRNDIS: init: HoRNDIS tethering driver for Snow Leopard+, by Joshua Wise
0 0 dgmdmcontrol: start - Failed to find the CDC driver
HoRNDIS: rndisInit: their MTU 1486
HoRNDIS: init: starting up with MTU 1486
HoRNDISUSBInterface: Ethernet address 1a:3a:1b:56:c4:a3
0 0 AppleUSBCDCACMData: start - allocateResources failed

---

So, after that, I disconnected the Desire, connected the S3 Mini and enabled USB tethering there. The network device created before shows up as disconnected, and a Samsung Modem device is available. dmesg output in this situation is as follows:

---

[DGMTP_Drv.cpp][getLogLevel()][00164][BUGS] Enabled
[DGMTP_Drv.cpp][getLogLevel()][00165][ERRO] Enabled
MTP Driver Started (Addr 0xffffff801a9a0800)
[DGMTP_Drv.cpp][fnEvtReadComplete()][01490][ERRO] INT RD F e00002ed
[DGMTP_Drv.cpp][fnEvtReadComplete()][01515]:[ERRO]INT RD F e000404f
HoRNDIS: init: HoRNDIS tethering driver for Snow Leopard+, by Joshua Wise

---

Hope this helps. Let me know if I can provide any more information.

[jwise]

Oops. Sorry for the latency... I missed this one a long while ago.

Unfortunately, I'm not really sure what's going on here. It is difficult to do too much debugging without a device; if I come up with any ideas as to what could be going on, I'll let you know, though.

Thanks for the report.