Dec 25 22:41:24 * thekix (n=kix@21.Red-80-24-61.staticIP.rima-tde.net) has joined #synce Dec 25 22:41:26 hi Dec 25 22:41:38 hi Dec 25 22:42:16 how are you :)? Dec 25 22:42:18 are you john? Dec 25 22:42:21 I am rodolfo Dec 25 22:42:27 oh, hi rodolfo :-) Dec 25 22:42:34 thanks for your time Dec 25 22:42:39 np :-) Dec 25 22:43:00 is olea "on-line?" Dec 25 22:43:15 he joined shortly before you :-D Dec 25 22:43:25 though he isn't responding to my prods :-( Dec 25 22:43:30 very busy guy :-D Dec 25 22:43:42 ok Dec 25 22:43:49 so your problem Dec 25 22:43:55 first, I am using an hp ipaq 950rx Dec 25 22:44:00 1950 Dec 25 22:44:03 sorry Dec 25 22:44:31 okie dokie Dec 25 22:44:59 more? Dec 25 22:45:27 i'm just reading the code around your problem area Dec 25 22:46:03 i wouldn't worry about the lsusb just yet, if it got this far i don't think that command can help. Dec 25 22:47:15 Dec 25 23:47:04 localhost kernel: usb 3-2: new full speed USB device using uhci_hcd and address 10 Dec 25 22:47:15 Dec 25 23:47:04 localhost kernel: usb 3-2: configuration #1 chosen from 1 choice Dec 25 22:47:15 Dec 25 23:47:04 localhost kernel: rndis_host 3-2:1.0: RNDIS_MSG_QUERY(0x01010101) failed, -110 Dec 25 22:47:15 Dec 25 23:47:04 localhost kernel: rndis_host: probe of 3-2:1.0 failed with error -110 Dec 25 22:47:19 when I connect Dec 25 22:47:23 and the lsusb -vvv Dec 25 22:47:29 i don't need Dec 25 22:48:05 ok Dec 25 22:48:16 is long :-) Dec 25 22:48:28 yes :-) Dec 25 22:48:57 Class specific interface descriptor for class 239 is unsupported Dec 25 22:48:57 Class specific interface descriptor for class 239 is unsupported Dec 25 22:48:57 Class specific interface descriptor for class 239 is unsupported Dec 25 22:49:00 this is important? Dec 25 22:49:08 :O Dec 25 22:49:29 i think it's normal Dec 25 22:49:38 ok Dec 25 22:49:53 the important thing is that to get as far as it did, it has to have gotten past the point where the descriptors matter Dec 25 22:50:07 thekix: do you have any programming experiencec :-o Dec 25 22:50:17 something :-) Dec 25 22:50:29 in C? Dec 25 22:50:51 yes Dec 25 22:51:00 ahh good :-) Dec 25 22:51:16 can you go in the usb-rndis-lite folder for me Dec 25 22:51:28 open rndis_host.c Dec 25 22:51:44 find the rndis_command function Dec 25 22:51:46 if (unlikely(retval < 0)) { Dec 25 22:51:46 dev_err(&intf->dev, "RNDIS_MSG_QUERY(0x%08x) failed, %d\n", Dec 25 22:51:46 oid, retval); Dec 25 22:51:46 return retval; Dec 25 22:51:46 } Dec 25 22:51:50 here is my problem Dec 25 22:51:59 yes Dec 25 22:52:00 kind of :-) Dec 25 22:52:15 we need to add extra debugs on the bit where retval comes from Dec 25 22:52:20 which is in rndis_command Dec 25 22:52:37 ok Dec 25 22:52:40 what do you see on line 317? Dec 25 22:52:59 if (unlikely(retval < 0 || xid == 0)) Dec 25 22:53:44 good good, just what i was hoping Dec 25 22:54:36 can you make it like this Dec 25 22:54:41 if (unlikely(retval < 0 || xid == 0)) { Dec 25 22:54:41 dev_dbg(&info->control->dev, Dec 25 22:54:41 "retval=%d, xid=%d\n", Dec 25 22:54:41 retval, xid); Dec 25 22:54:41 return retval; Dec 25 22:54:41 } Dec 25 22:55:00 (get rid of the two lines that are there Dec 25 22:55:02 ) Dec 25 22:55:20 also, at the top of the file - can you uncomment #DEBUG and #VERBOSE Dec 25 22:56:14 if your device is attached, remove it Dec 25 22:56:30 then do the make, sudo ./clean.sh, sudo make install Dec 25 22:56:38 plug your device and show me the new dmesg Dec 25 22:56:59 / if (unlikely(retval < 0 || xid == 0)) Dec 25 22:56:59 / return retval; Dec 25 22:56:59 if (unlikely(retval < 0 || xid == 0)) { Dec 25 22:56:59 dev_dbg(&info->control->dev, "retval=%d, xid=%d\n", retval, xid); Dec 25 22:56:59 return retval; Dec 25 22:57:00 } Dec 25 22:57:08 I will compile it and try Dec 25 22:58:04 make Dec 25 22:58:13 sudo ./clean.sh Dec 25 22:58:32 sudo make install Dec 25 23:01:13 thekix: has it compiled? Dec 25 23:01:19 yes Dec 25 23:01:27 I forget to set the DEBUG Dec 25 23:01:40 lollies :-) Dec 25 23:01:45 Dec 26 00:01:10 localhost kernel: usb 3-2: new full speed USB device using uhci_hcd and address 12 Dec 25 23:01:45 Dec 26 00:01:11 localhost kernel: usb 3-2: configuration #1 chosen from 1 choice Dec 25 23:01:45 Dec 26 00:01:11 localhost kernel: usbcore: registered new driver cdc_ether Dec 25 23:01:58 Dec 26 00:01:11 localhost kernel: rndis_host 3-2:1.0: hard mtu 1558 (1642 from dev), rx buflen 16384, align 8 Dec 25 23:01:58 Dec 26 00:01:12 localhost kernel: rndis_host 3-2:1.0: rndis response error, code 1 Dec 25 23:01:58 Dec 26 00:01:12 localhost last message repeated 9 times Dec 25 23:02:14 Dec 26 00:01:12 localhost kernel: rndis_host 3-2:1.0: rndis response timeout Dec 25 23:02:14 Dec 26 00:01:12 localhost kernel: rndis_host 3-2:1.0: RNDIS_MSG_QUERY(0x01010101) failed, -110 Dec 25 23:02:14 Dec 26 00:01:12 localhost kernel: rndis_host: probe of 3-2:1.0 failed with error -110 Dec 25 23:02:14 Dec 26 00:01:12 localhost kernel: usbcore: registered new driver rndis_host Dec 25 23:02:41 unexpected :o Dec 25 23:03:29 dev_dbg(&info->control->dev, Dec 25 23:03:29 "rndis response error, code %d\n", retval); Dec 25 23:03:40 irc ate part of that Dec 25 23:03:43 the comment reads Dec 25 23:03:52 "device probably issued a protocol stall; ignore" Dec 25 23:05:05 it tries to do this 10 times and fails each time Dec 25 23:05:29 then returns -110, which is -ETIMEDOUT Dec 25 23:09:29 it seems to be a common pattern that if a USB error is betwen 1 and 8 its bad :-\ Dec 25 23:09:41 unsure as to why Dec 25 23:11:35 then? Dec 25 23:12:40 ok... that particular function returns a positive value *only* if it (kinda) worked Dec 25 23:12:55 if its positive, then it is a length of the data returned Dec 25 23:13:02 your device is returning 1 byte Dec 25 23:13:20 i think rndis_host is disappointed with such a size and then cries :-) Dec 25 23:13:51 if my device returns 1 byte, then is 1 byte :-) Dec 25 23:14:11 ahh correction Dec 25 23:14:19 oh wait Dec 25 23:14:21 no Dec 25 23:14:28 i hate kernel stuff :( Dec 25 23:14:42 this is 10x beyond me, at least! :-) Dec 25 23:15:01 oleavr: i'll email you all this in case you get disconnected :-/ any ideas? Dec 25 23:15:40 thekix: theres nothing more us mortals can do :-) Dec 25 23:15:51 yes Dec 25 23:16:03 oleavr!!!!! save us! Dec 25 23:16:05 :-) Dec 25 23:16:08 unless you wanted to idle, i can e-mail you if/when i can pin oleavr to the ground and find out what he knows? Dec 25 23:16:20 as it happens, i'm going to bed :-) Dec 25 23:16:31 jc2k, where are you from? Dec 25 23:16:41 england :) Dec 25 23:17:01 ok, we have the same timezone +- Dec 25 23:17:08 spain Dec 25 23:17:13 I need go to the bed too Dec 25 23:18:34 jc2k, the problem is in the bind not? Dec 25 23:18:53 the bind? Dec 25 23:19:29 yes Dec 25 23:19:40 /* REVISIT: peripheral "alignment" request is ignored ... */ Dec 25 23:19:40 dev_dbg(&intf->dev, Dec 25 23:19:40 "hard mtu %u (%u from dev), rx buflen %Zu, align %d\n", Dec 25 23:19:40 dev->hard_mtu, tmp, dev->rx_urb_size, Dec 25 23:19:41 1 << le32_to_cpu(u.init_c->packet_alignment)); Dec 25 23:19:42 here Dec 25 23:19:54 static int rndis_bind(struct usbnet *dev, struct usb_interface *intf) Dec 25 23:19:57 in this function Dec 25 23:20:32 thekix: nope - the hard mtu error scared me the first time i did a fix - i thought i had broke it :P but its a normal error Dec 25 23:20:43 well, its not really an error Dec 25 23:20:55 its more of a.. this is what params i'm using Dec 25 23:21:08 ok Dec 25 23:21:23 the real issue stems from the "rndis response error" in "rndis_command" Dec 25 23:21:31 this is inside a for loop so occurs 10 times Dec 25 23:21:44 after the tenth loop the code gives up and fails with a timeout error Dec 25 23:22:03 the place that called rndis_command then issues the RNDIS_MSG_QUERY error Dec 25 23:22:09 if (unlikely(retval < 0 || xid == 0)) { Dec 25 23:22:09 dev_err(&info->control->dev, "retval=%d, xid=%d\n", retval, xid); Dec 25 23:22:09 return retval; Dec 25 23:22:13 I will try with this Dec 25 23:22:27 thekix: the error is lower down :-) Dec 25 23:23:12 ok Dec 25 23:23:13 :-) Dec 25 23:23:19 it does this: Dec 25 23:23:19 for (count = 0; count < 10; count++) { Dec 25 23:23:19 memset(buf, 0, CONTROL_BUFFER_SIZE); Dec 25 23:23:19 retval = usb_control_msg(dev->udev, Dec 25 23:23:19 usb_rcvctrlpipe(dev->udev, 0), Dec 25 23:23:19 USB_CDC_GET_ENCAPSULATED_RESPONSE, Dec 25 23:23:19 USB_DIR_IN | USB_TYPE_CLASS | USB_RECIP_INTERFACE, Dec 25 23:23:19 0, master_ifnum, Dec 25 23:23:19 buf, CONTROL_BUFFER_SIZE, Dec 25 23:23:19 RNDIS_CONTROL_TIMEOUT_MS); Dec 25 23:23:19 if (likely(retval >= 8)) { Dec 25 23:23:30 but retval < 8 so it goes in to the else: Dec 25 23:23:45 } else { Dec 25 23:23:45 /* device probably issued a protocol stall; ignore */ Dec 25 23:23:45 dev_dbg(&info->control->dev, Dec 25 23:23:45 "rndis response error, code %d\n", retval); Dec 25 23:23:45 } Dec 25 23:23:45 msleep(2); Dec 25 23:23:49 and loops a bit Dec 25 23:23:52 anyway Dec 25 23:23:54 night night! Dec 25 23:24:42 ok Dec 26 12:11:09 rmrfchik: are you Paul? Dec 26 12:11:14 yes Dec 26 12:11:40 =) Dec 26 12:11:41 hi Dec 26 12:11:51 hi :) Dec 26 12:12:16 when i got your last email i was still pretty much asleep so give me 5 to see what the error was and grep the code Dec 26 12:12:24 oleavr: did you get my e-mail :)? Dec 26 12:12:42 i <3 coffee Dec 26 12:13:04 thekix-web: remember me with vodka? well with coffee things are much worse :D Dec 26 12:13:15 i can save your time: rndis_host.c, line 511 Dec 26 12:13:21 error -110 Dec 26 12:14:10 Jc2k: cool :) Dec 26 12:14:23 Jc2k: yeah sorry I've been too sucked in to be able to context-switch Dec 26 12:14:39 oleavr: hehe i know that feeling Dec 26 12:14:46 its a bitch at work sometimes Dec 26 12:14:54 when i've got conduit in my head Dec 26 12:14:59 and they expect me to do VB Dec 26 12:15:02 AAAHAHAHAHHHHHHHHHHHHh Dec 26 12:15:48 rmrfchik: well... it seems it's related to the problem thekix is having Dec 26 12:16:12 thekix-web: what r u using? what pda/phone? Dec 26 12:16:20 oleavr: we have two users with rndis_commands that timeout - but in different places!! Dec 26 12:16:33 rmrfchik: he is using a pda i believe Dec 26 12:16:34 Jc2k: if it does matter: my pda is running Samsung CPU Dec 26 12:17:26 rmrfchik: not sure tbh Dec 26 12:17:41 Jc2k: hmm.. any timeouts from the basic USB subsystem like when retrieving device descriptors? Dec 26 12:18:10 oleavr: i think one of em had that when they used the original usb-rndis Dec 26 12:18:14 according to sources, problem is in usb subsystem, not in rndis Dec 26 12:18:16 but with rndis-lite... Dec 26 12:18:27 its in RNDS init Dec 26 12:18:32 and where it does a MSG_QUERY Dec 26 12:19:02 yes. it seems, we need the protocol dissected Dec 26 12:19:31 oleavr: when rmrfchik had the older driver on the usb sub system spat this out: Dec 26 12:19:31 usb 5-1: device descriptor read/64, error -110 Dec 26 12:19:51 Jc2k: hm, it seems i was wrong. Dec 26 12:20:05 my steps Dec 26 12:20:10 1. built module Dec 26 12:20:15 2. make install Dec 26 12:20:24 3. rmmod rndis and stuff Dec 26 12:20:28 lollies Dec 26 12:20:30 4. modprobe rndis_host Dec 26 12:20:39 it should be 1 3 2, with no 4 Dec 26 12:20:40 nothing happens... then Dec 26 12:20:51 5. rmmod rndis and stuff Dec 26 12:21:04 6. insmod ./*ko modules by hand Dec 26 12:21:08 7. see and error Dec 26 12:21:12 rmrfchik: Dec 26 12:21:16 in usb-rndis-lite Dec 26 12:21:19 make Dec 26 12:21:22 sudo ./clean.sh Dec 26 12:21:26 sudo make install Dec 26 12:21:30 and it should just work.. Dec 26 12:21:37 yes, twogood said me Dec 26 12:21:49 what error do you get if you do that step? Dec 26 12:21:55 so, after clean.sh, I really got the -110 error now Dec 26 12:22:05 ok Dec 26 12:22:12 is it the one that mentions RNDIS Init Dec 26 12:22:23 or the one that mentions MSG_QUERY Dec 26 12:23:29 don't know... Dec 26 12:23:35 stop.. do know Dec 26 12:23:37 look Dec 26 12:23:53 usb 5-2: configuration #1 chosen from 1 choice Dec 26 12:23:53 rndis_host 5-2:1.0: RNDIS init failed, -110 Dec 26 12:23:53 rndis_host: probe of 5-2:1.0 failed with error -110 Dec 26 12:23:57 good :) Dec 26 12:23:57 so, this is init failed Dec 26 12:24:02 well, not good Dec 26 12:24:13 so Dec 26 12:24:22 oleavr: when you aren't "in the zone" :-) Dec 26 12:24:55 getting timeouts from rndis_command, one in RNDIS init, one in the MSG_QUERY bit Dec 26 12:25:22 we have seen a descriptor moan from the usb subsystem, but that was when the rndis_host wasn't installed properly Dec 26 12:26:18 is it proper "./clean.sh; make install" Dec 26 12:27:28 sudo ./clean.sh Dec 26 12:27:31 sudo make install Dec 26 12:27:39 sure, under root Dec 26 12:27:50 oh ok, i'm used to ubuntu's lack of root hehe Dec 26 12:27:58 at least, files *ko are the same as in build dir ;) Dec 26 12:28:06 ./clean.sh Dec 26 12:28:08 make install Dec 26 12:28:11 plug and pray Dec 26 12:28:14 :-) Dec 26 12:28:23 and get the RNDIS init failed, -110 Dec 26 12:28:45 do you have some process for digging such cases? Dec 26 12:29:01 may be you need additional info about pda? Dec 26 12:29:14 or protocol need to be digged.. Dec 26 12:29:17 rmrfchik: i'm new to this really :-) Dec 26 12:29:24 ah, ok Dec 26 12:29:32 my "process" is repetition of what i have seen the masters do hehe Dec 26 12:29:41 :) Dec 26 12:29:50 i have a feeling oleavr knows something, thats why he specifically asked about device descriptors Dec 26 12:30:41 rmrfchik: your problem is closely related to issue witnessed by thekix Dec 26 12:30:55 last night between us we isolated it to the rndis_command sub Dec 26 12:31:17 it takes the else case (comment mentions that the device is "stalling" the protocol Dec 26 12:31:24 when there is a stall it tries again Dec 26 12:31:31 in total it will try 10 times Dec 26 12:31:40 then it gives the timeout error (-110) Dec 26 12:32:39 if you want to confirm this, then define the debug and verbose options at top of rndis_host.c and make / clean / install again Dec 26 12:32:44 it should give you more output Dec 26 12:33:24 if you don't know any C then i just need you to turn this: Dec 26 12:33:24 / #define DEBUG // error path messages, extra info Dec 26 12:33:24 / #define VERBOSE // more; success messages Dec 26 12:33:28 in to this Dec 26 12:33:36 #define DEBUG // error path messages, extra info Dec 26 12:33:36 #define VERBOSE // more; success messages Dec 26 12:33:53 (IRC turned //// into // :() Dec 26 12:33:57 grr! Dec 26 12:34:03 (IRC turned // into / :() Dec 26 12:34:21 * oleavr has quit (Read error: 110 (Connection timed out)) Dec 26 12:35:15 rndis_host 5-2:1.0: RNDIS_MSG_QUERY(0x01010101) failed, -110 Dec 26 12:35:33 correct? Dec 26 12:36:44 :O Dec 26 12:36:52 did you get any more errors? Dec 26 12:37:03 usb 5-2: new full speed USB device using uhci_hcd and address 31 Dec 26 12:37:03 usb 5-2: configuration #1 chosen from 1 choice Dec 26 12:37:03 usbcore: registered new driver cdc_ether Dec 26 12:37:03 rndis_host 5-2:1.0: RNDIS_MSG_QUERY(0x01010101) failed, -110 Dec 26 12:37:03 rndis_host: probe of 5-2:1.0 failed with error -110 Dec 26 12:37:06 full log Dec 26 12:38:05 hmm... wait a sec. Dec 26 12:38:16 weird, now you have the same error as thekix - and the init error is gone!?! Dec 26 12:38:40 * Jc2k cries into his laptop Dec 26 12:38:52 usb 5-2: new full speed USB device using uhci_hcd and address 32 Dec 26 12:38:52 usb 5-2: configuration #1 chosen from 1 choice Dec 26 12:38:52 usbcore: registered new driver cdc_ether Dec 26 12:38:52 rndis_host 5-2:1.0: hard mtu 1558 (8192 from dev), rx buflen 16384, align 8 Dec 26 12:38:52 rndis_host 5-2:1.0: rndis response error, code 1 Dec 26 12:38:52 rndis_host 5-2:1.0: rndis response error, code 1 Dec 26 12:38:54 rndis_host 5-2:1.0: rndis response error, code 1 Dec 26 12:38:58 rndis_host 5-2:1.0: rndis response error, code 1 Dec 26 12:39:00 rndis_host 5-2:1.0: rndis response error, code 1 Dec 26 12:39:02 rndis_host 5-2:1.0: rndis response error, code 1 Dec 26 12:39:05 rndis_host 5-2:1.0: rndis response error, code 1 Dec 26 12:39:06 rndis_host 5-2:1.0: rndis response error, code 1 Dec 26 12:39:08 rndis_host 5-2:1.0: rndis response error, code 1 Dec 26 12:39:10 rndis_host 5-2:1.0: rndis response error, code 1 Dec 26 12:39:14 rndis_host 5-2:1.0: rndis response timeout Dec 26 12:39:17 rndis_host 5-2:1.0: RNDIS_MSG_QUERY(0x01010101) failed, -110 Dec 26 12:39:20 rndis_host: probe of 5-2:1.0 failed with error -110 Dec 26 12:39:22 usbcore: registered new driver rndis_host Dec 26 12:39:24 stop crying... here is the FULL log ;) Dec 26 12:39:58 you can broke you laptop by drops. how you will help me in this case? so, stop crying ;) Dec 26 12:40:10 rmrfchik: hehe :) Dec 26 12:40:21 yep, it's exactly the same error as thekix, but why!!? Dec 26 12:40:28 where is the error from line 511 Dec 26 12:41:42 hmm.. dunno Dec 26 12:43:17 my thoughts exactly :D Dec 26 12:43:21 I have the same problem with my ipaq Dec 26 12:43:39 why? why? Dec 26 12:43:39 :-) Dec 26 12:43:43 lol Dec 26 12:43:45 i jsut said Dec 26 12:43:55 rmrfchik did have a different but similar error Dec 26 12:44:01 now it has morphed in to yours :( Dec 26 12:44:07 * Jc2k cries again Dec 26 12:45:05 ok, I've added dev_err(&intf->dev," RNDIS init ok\n"); to line 519 and got Dec 26 12:45:10 usbcore: registered new driver cdc_ether Dec 26 12:45:11 rndis_host 5-2:1.0: RNDIS init ok Dec 26 12:45:23 so, Init actually took place Dec 26 12:45:32 well.. perplexing! :-) Dec 26 12:46:24 my instinct (which isn't a great tool to be falling back on :-)) makes me think that the only way we could be "fixing" anything by turning on debug is if its a pretty naff timing issue Dec 26 12:46:28 two cases Dec 26 12:46:54 one, its pretty damned random and if you rebooted and tried again you could get either error Dec 26 12:47:28 two, the extra debugs somehow changed the time those few extra cycles enough to let it get further xD Dec 26 12:49:01 hmm. sleep(1)? ;) Dec 26 12:53:16 hehe Dec 26 13:11:58 more ideas¿? Dec 26 13:24:21 * thekix-web has quit ("CGI:IRC (Session timeout)") Dec 26 13:29:39 am i correct --- main idea is to increase timeout? Dec 26 13:32:47 50 retries and msleep(20) won't help Dec 26 13:34:11 rmrfchik: i think its a lost cause until we can pick oleavr's brain :( Dec 26 13:51:39 time to go home Dec 26 13:51:48 bye, I am trying things Dec 26 13:51:54 :-) Dec 26 13:51:59 * thekix-web2 has quit ("CGI:IRC 0.5.4 (2004/01/29)") Dec 26 14:00:58 * oleavr (n=oleavr@177.81-167-82.customer.lyse.net) has joined #SynCE Dec 26 14:01:30 oleavr: wake up. wake up. wake up and dance Dec 26 14:04:02 lol :-) Dec 26 14:04:20 oleavr: hows it going :) Dec 26 14:06:40 rmrfchik: lol Dec 26 14:06:48 Jc2k: I'm in a "boring" family thingy Dec 26 14:06:58 so I'm hacking on a python DTPT implementation Dec 26 14:07:09 let's hack rndis! Dec 26 14:07:16 oleavr: nice :P Dec 26 14:07:36 rmrfchik: you can't make him choose rndis over a family thing! :D Dec 26 14:07:46 *cough* Dec 26 14:07:58 but I can make him chose over python thing! Dec 26 14:09:03 i hope, at least Dec 26 14:09:23 nah, i doubt it =p Dec 26 14:09:51 time to cry for me Dec 26 14:16:35 * Jc2k begins to leak all over his keyboard Dec 26 14:18:46 * alsuren has quit (Remote closed the connection) Dec 26 14:26:26 where r u from? Dec 26 14:33:09 rmrfchik: i am from sunny england Dec 26 14:35:58 russia here Dec 26 14:36:21 so when i say i'm cold i won't get much sympathy :)? Dec 26 14:39:36 why? no problem. (or I just don't get the joke :) Dec 26 14:50:33 my bad joke =) Dec 26 14:50:36 got to go Dec 26 14:50:37 ttys Dec 26 14:50:38 SysTray Integration Plugin unloaded Dec 26 14:50:38 Tcl interface unloaded Dec 26 14:50:38 Python interface unloaded **** ENDING LOGGING AT Tue Dec 26 14:50:38 2006 **** BEGIN LOGGING AT Fri Feb 2 20:39:11 2007 Feb 02 20:39:11 * Now talking on #synce Feb 02 20:39:11 * Topic for #synce is: http://www.engadget.com/2007/01/09/the-apple-iphone/ Feb 02 20:39:11 * Topic for #synce set by lilalinux at Tue Jan 9 19:11:58 2007 Feb 02 20:42:08 * dgollub (i=dani@nat/suse/x-22730095ead715cc) has joined #synce Feb 02 20:42:17 hi Feb 02 21:07:51 hi Feb 02 21:08:10 * wibbit (n=dfurlong@host-84-9-13-237.bulldogdsl.com) has joined #synce Feb 02 21:26:57 can anybody help me with my problem? Feb 02 21:47:02 Civil: it depends what your problem is :-) Feb 02 21:47:33 problem with connecting hp rx1950 using synce... Feb 02 21:47:56 It creates device around 1 time of 50-60... Feb 02 21:48:21 dmesg says: rndis response error, code 1 Feb 02 21:48:25 rndis response error, code 1 Feb 02 21:48:38 rndis response timeout Feb 02 21:48:43 RNDIS_MSG_QUERY(0x01010101) failed, -110 Feb 02 21:49:12 but mpx200 (wm 5.0) connects fine Feb 02 21:49:44 i have seen this problem before, apparently using the usb-rdnis-ng driver is a work around for now Feb 02 21:50:08 hm... at wiki there is only text about usb-rndis-lite ) Feb 02 21:50:12 wich I'm using now... Feb 02 21:50:40 http://www.synce.org/index.php/Connecting_your_Windows_Mobile_2005_device_via_USB ;-) Feb 02 21:50:53 we purposefully removed the link to it as its really a last resort Feb 02 21:51:25 thanks ) Feb 02 21:51:38 you only need to do down to compile and install Feb 02 21:52:03 everything after "using the driver without hal" won't apply to you Feb 02 21:56:53 hm... ./autogen.sh && ./configure --enable-hal && mkae && make install and after that it must work? Feb 02 21:57:45 it may work :) hehe Feb 02 21:58:01 make sure you phone is unplugged before you start Feb 02 21:58:20 it's pda ) phone works, but pda doesn't ) Feb 02 21:59:08 its because i have a phone, so i forget there are even pdas out there xD Feb 02 21:59:16 ))) Feb 02 22:02:41 civil-gentoo civil # usb-rndis-driver Feb 02 22:02:41 scanning for a USB RNDIS device Feb 02 22:02:41 doing rndis_init Feb 02 22:02:41 short read, read 1 out of 16 Feb 02 22:03:19 is that all it says? Feb 02 22:03:23 yes Feb 02 22:03:32