Re: urndis and umodem device collision for ue device
On 12/22/14 10:29, Randall Fox wrote: On Mon, Dec 22, 2014 at 1:23 AM, Hans Petter Selasky wrote: I am not familiar with RNDIS.. This thread is about umodem and urndis. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
On Mon, Dec 22, 2014 at 1:23 AM, Hans Petter Selasky wrote: > On 12/22/14 10:14, Randall Fox wrote: > >> On Mon, Dec 22, 2014 at 12:42 AM, Hans Petter Selasky >> wrote: >> >> On 12/21/14 22:28, Randall Fox wrote: >>> >>> On Sun, Dec 21, 2014 at 1:02 PM, Hans Petter Selasky wrote: On 12/21/14 21:40, Randall Fox wrote: > > Did you update /etc/devd/usb.conf, install new kernel and reboot your > >> >> >>> system? >>> >> >> I actually had the FreeNAS team apply this fix to the nightly build >> and >> I >> created a whole new install based on their Nightly Build. The DEVs >> put >> the >> fix in, and it must have been correct because it worked for someone >> else. >> >> Here is the link to the ticket for this: >> https://bugs.freenas.org/issues/7153 >> It appears they are familiar with you! >> >> I will try putting the usb.conf in the location you specify, to see if >> that >> works. I would be surprised if the dev's missed this. >> >> >> >> On Sun, Dec 21, 2014 at 12:24 PM, Hans Petter Selasky < >> h...@selasky.org> >> wrote: >> >>On 12/21/14 21:21, Randall Fox wrote: >> >> >>>Hi, >>> >>> The following patches should fix your problem: > > https://svnweb.freebsd.org/changeset/base/275790 > https://svnweb.freebsd.org/changeset/base/275791 > > --HPS > > > > Can you get the dmesg when plugging your device? >>> > --HPS > > > uhid0: 1.10/2.0a, > addr 3> on usbus1 ugen1.3: at usbus1 (disconnected) uhid0: at uhub3, port 1, addr 3 (disconnected) ugen1.3: at usbus1 uhid0: >>> addr 3> on usbus1 ugen1.3: at usbus1 (disconnected) uhid0: at uhub3, port 1, addr 3 (disconnected) I tried putting the usb.conf in /etc/devd and rebooting, but no change.. Hi, >>> >>> This looks correct. Did you select the correct device profile? >>> >>> Also, did you set the correct USB configuration number? >>> >>> usbconfig -d X.Y dump_device_desc dump_curr_config_desc >>> usbconfig -d X.Y set_config 1 >>> >>> --HPS >>> >>> >> I ran the set_config 1, but that didn't have any effect, nor did >> set_config >> 0. the dump device & config is below. >> >> I did not select any profile, I just plug the unit in and I get the >> disconnect messages. >> >> ugen1.3: at usbus1, cfg=0 >> md=HOST spd=LOW (1.5Mbps) pwr=ON (0mA) >> >>bLength = 0x0012 >>bDescriptorType = 0x0001 >>bcdUSB = 0x0110 >>bDeviceClass = 0x >>bDeviceSubClass = 0x >>bDeviceProtocol = 0x >>bMaxPacketSize0 = 0x0008 >>idVendor = 0x09ae >>idProduct = 0x3015 >>bcdDevice = 0x020a >>iManufacturer = 0x0002 >>iProduct = 0x0003 >>iSerialNumber = 0x0004 <2351BY0SM820600181> >>bNumConfigurations = 0x0001 >> >> >> Configuration index 0 >> >> bLength = 0x0009 >> bDescriptorType = 0x0002 >> wTotalLength = 0x0022 >> bNumInterfaces = 0x0001 >> bConfigurationValue = 0x0001 >> iConfiguration = 0x >> bmAttributes = 0x00e0 >> bMaxPower = 0x >> >> Interface 0 >>bLength = 0x0009 >>bDescriptorType = 0x0004 >>bInterfaceNumber = 0x >>bAlternateSetting = 0x >>bNumEndpoints = 0x0001 >>bInterfaceClass = 0x0003 >>bInterfaceSubClass = 0x >>bInterfaceProtocol = 0x >>iInterface = 0x >> >>Additional Descriptor >> >>bLength = 0x09 >>bDescriptorType = 0x21 >>bDescriptorSubType = 0x10 >> RAW dump: >> 0x00 | 0x09, 0x21, 0x10, 0x01, 0x00, 0x01, 0x22, 0xe4, >> 0x08 | 0x04 >> >>Endpoint 0 >> >>bLength = 0x0007 >>bDescriptorType = 0x0005 >>bEndpointAddress = 0x0081 >>bmAttributes = 0x0003 >>wMaxPacketSize = 0x0008 >>bInterval = 0x0028 >>bRefresh = 0x >>bSynchAddress = 0x >> >> > Hi, > > There is no RNDIS device here! There is only a UHID device. > > --HPS > I am not familiar with RNDIS.. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
On 12/22/14 10:14, Randall Fox wrote: On Mon, Dec 22, 2014 at 12:42 AM, Hans Petter Selasky wrote: On 12/21/14 22:28, Randall Fox wrote: On Sun, Dec 21, 2014 at 1:02 PM, Hans Petter Selasky wrote: On 12/21/14 21:40, Randall Fox wrote: Did you update /etc/devd/usb.conf, install new kernel and reboot your system? I actually had the FreeNAS team apply this fix to the nightly build and I created a whole new install based on their Nightly Build. The DEVs put the fix in, and it must have been correct because it worked for someone else. Here is the link to the ticket for this: https://bugs.freenas.org/issues/7153 It appears they are familiar with you! I will try putting the usb.conf in the location you specify, to see if that works. I would be surprised if the dev's missed this. On Sun, Dec 21, 2014 at 12:24 PM, Hans Petter Selasky wrote: On 12/21/14 21:21, Randall Fox wrote: Hi, The following patches should fix your problem: https://svnweb.freebsd.org/changeset/base/275790 https://svnweb.freebsd.org/changeset/base/275791 --HPS Can you get the dmesg when plugging your device? --HPS uhid0: addr 3> on usbus1 ugen1.3: at usbus1 (disconnected) uhid0: at uhub3, port 1, addr 3 (disconnected) ugen1.3: at usbus1 uhid0: on usbus1 ugen1.3: at usbus1 (disconnected) uhid0: at uhub3, port 1, addr 3 (disconnected) I tried putting the usb.conf in /etc/devd and rebooting, but no change.. Hi, This looks correct. Did you select the correct device profile? Also, did you set the correct USB configuration number? usbconfig -d X.Y dump_device_desc dump_curr_config_desc usbconfig -d X.Y set_config 1 --HPS I ran the set_config 1, but that didn't have any effect, nor did set_config 0. the dump device & config is below. I did not select any profile, I just plug the unit in and I get the disconnect messages. ugen1.3: at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (0mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x09ae idProduct = 0x3015 bcdDevice = 0x020a iManufacturer = 0x0002 iProduct = 0x0003 iSerialNumber = 0x0004 <2351BY0SM820600181> bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0022 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x00e0 bMaxPower = 0x Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x bInterfaceProtocol = 0x iInterface = 0x Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x10 RAW dump: 0x00 | 0x09, 0x21, 0x10, 0x01, 0x00, 0x01, 0x22, 0xe4, 0x08 | 0x04 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x0028 bRefresh = 0x bSynchAddress = 0x Hi, There is no RNDIS device here! There is only a UHID device. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
On Mon, Dec 22, 2014 at 12:42 AM, Hans Petter Selasky wrote: > On 12/21/14 22:28, Randall Fox wrote: > >> On Sun, Dec 21, 2014 at 1:02 PM, Hans Petter Selasky >> wrote: >> >> On 12/21/14 21:40, Randall Fox wrote: >>> >>> Did you update /etc/devd/usb.conf, install new kernel and reboot your > > system? I actually had the FreeNAS team apply this fix to the nightly build and I created a whole new install based on their Nightly Build. The DEVs put the fix in, and it must have been correct because it worked for someone else. Here is the link to the ticket for this: https://bugs.freenas.org/issues/7153 It appears they are familiar with you! I will try putting the usb.conf in the location you specify, to see if that works. I would be surprised if the dev's missed this. On Sun, Dec 21, 2014 at 12:24 PM, Hans Petter Selasky wrote: On 12/21/14 21:21, Randall Fox wrote: > > Hi, > >> >> >>> The following patches should fix your problem: >>> >>> https://svnweb.freebsd.org/changeset/base/275790 >>> https://svnweb.freebsd.org/changeset/base/275791 >>> >>> --HPS >>> >>> >>> >> >> Can you get the dmesg when plugging your device? >>> >>> --HPS >>> >>> >>> uhid0: > addr 3> on usbus1 >> ugen1.3: at usbus1 (disconnected) >> uhid0: at uhub3, port 1, addr 3 (disconnected) >> ugen1.3: at usbus1 >> uhid0: > addr 3> on usbus1 >> ugen1.3: at usbus1 (disconnected) >> uhid0: at uhub3, port 1, addr 3 (disconnected) >> >> I tried putting the usb.conf in /etc/devd and rebooting, but no change.. >> >> > Hi, > > This looks correct. Did you select the correct device profile? > > Also, did you set the correct USB configuration number? > > usbconfig -d X.Y dump_device_desc dump_curr_config_desc > usbconfig -d X.Y set_config 1 > > --HPS > I ran the set_config 1, but that didn't have any effect, nor did set_config 0. the dump device & config is below. I did not select any profile, I just plug the unit in and I get the disconnect messages. ugen1.3: at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (0mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x09ae idProduct = 0x3015 bcdDevice = 0x020a iManufacturer = 0x0002 iProduct = 0x0003 iSerialNumber = 0x0004 <2351BY0SM820600181> bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0022 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x00e0 bMaxPower = 0x Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x bInterfaceProtocol = 0x iInterface = 0x Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x10 RAW dump: 0x00 | 0x09, 0x21, 0x10, 0x01, 0x00, 0x01, 0x22, 0xe4, 0x08 | 0x04 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x0028 bRefresh = 0x bSynchAddress = 0x ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
On 12/21/14 22:28, Randall Fox wrote: On Sun, Dec 21, 2014 at 1:02 PM, Hans Petter Selasky wrote: On 12/21/14 21:40, Randall Fox wrote: Did you update /etc/devd/usb.conf, install new kernel and reboot your system? I actually had the FreeNAS team apply this fix to the nightly build and I created a whole new install based on their Nightly Build. The DEVs put the fix in, and it must have been correct because it worked for someone else. Here is the link to the ticket for this: https://bugs.freenas.org/issues/7153 It appears they are familiar with you! I will try putting the usb.conf in the location you specify, to see if that works. I would be surprised if the dev's missed this. On Sun, Dec 21, 2014 at 12:24 PM, Hans Petter Selasky wrote: On 12/21/14 21:21, Randall Fox wrote: Hi, The following patches should fix your problem: https://svnweb.freebsd.org/changeset/base/275790 https://svnweb.freebsd.org/changeset/base/275791 --HPS Can you get the dmesg when plugging your device? --HPS uhid0: on usbus1 ugen1.3: at usbus1 (disconnected) uhid0: at uhub3, port 1, addr 3 (disconnected) ugen1.3: at usbus1 uhid0: on usbus1 ugen1.3: at usbus1 (disconnected) uhid0: at uhub3, port 1, addr 3 (disconnected) I tried putting the usb.conf in /etc/devd and rebooting, but no change.. Hi, This looks correct. Did you select the correct device profile? Also, did you set the correct USB configuration number? usbconfig -d X.Y dump_device_desc dump_curr_config_desc usbconfig -d X.Y set_config 1 --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
On Sun, Dec 21, 2014 at 1:02 PM, Hans Petter Selasky wrote: > On 12/21/14 21:40, Randall Fox wrote: > >> Did you update /etc/devd/usb.conf, install new kernel and reboot your >>> >> system? >> >> I actually had the FreeNAS team apply this fix to the nightly build and I >> created a whole new install based on their Nightly Build. The DEVs put >> the >> fix in, and it must have been correct because it worked for someone else. >> >> Here is the link to the ticket for this: >> https://bugs.freenas.org/issues/7153 >> It appears they are familiar with you! >> >> I will try putting the usb.conf in the location you specify, to see if >> that >> works. I would be surprised if the dev's missed this. >> >> >> >> On Sun, Dec 21, 2014 at 12:24 PM, Hans Petter Selasky >> wrote: >> >> On 12/21/14 21:21, Randall Fox wrote: >>> >>> Hi, > > The following patches should fix your problem: > > https://svnweb.freebsd.org/changeset/base/275790 > https://svnweb.freebsd.org/changeset/base/275791 > > --HPS > > > Can you get the dmesg when plugging your device? > > --HPS > > uhid0: on usbus1 ugen1.3: at usbus1 (disconnected) uhid0: at uhub3, port 1, addr 3 (disconnected) ugen1.3: at usbus1 uhid0: on usbus1 ugen1.3: at usbus1 (disconnected) uhid0: at uhub3, port 1, addr 3 (disconnected) I tried putting the usb.conf in /etc/devd and rebooting, but no change.. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
On 12/21/14 21:40, Randall Fox wrote: Did you update /etc/devd/usb.conf, install new kernel and reboot your system? I actually had the FreeNAS team apply this fix to the nightly build and I created a whole new install based on their Nightly Build. The DEVs put the fix in, and it must have been correct because it worked for someone else. Here is the link to the ticket for this: https://bugs.freenas.org/issues/7153 It appears they are familiar with you! I will try putting the usb.conf in the location you specify, to see if that works. I would be surprised if the dev's missed this. On Sun, Dec 21, 2014 at 12:24 PM, Hans Petter Selasky wrote: On 12/21/14 21:21, Randall Fox wrote: Hi, The following patches should fix your problem: https://svnweb.freebsd.org/changeset/base/275790 https://svnweb.freebsd.org/changeset/base/275791 --HPS Can you get the dmesg when plugging your device? --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
> Did you update /etc/devd/usb.conf, install new kernel and reboot your system? I actually had the FreeNAS team apply this fix to the nightly build and I created a whole new install based on their Nightly Build. The DEVs put the fix in, and it must have been correct because it worked for someone else. Here is the link to the ticket for this: https://bugs.freenas.org/issues/7153 It appears they are familiar with you! I will try putting the usb.conf in the location you specify, to see if that works. I would be surprised if the dev's missed this. On Sun, Dec 21, 2014 at 12:24 PM, Hans Petter Selasky wrote: > On 12/21/14 21:21, Randall Fox wrote: > >> Hi, >>> >>> The following patches should fix your problem: >>> >>> https://svnweb.freebsd.org/changeset/base/275790 >>> https://svnweb.freebsd.org/changeset/base/275791 >>> >>> --HPS >>> >> >> >> I finally was able to apply this, and it did not work for me. I am still >> getting the disconnect messages. It seems to have worked for someone else >> with a different (but similar) Tripp Lite unit. He had the same issue as >> I >> did, but this seemed to have fixed it. >> >> Were you able to get the ID values from my data? Or did you pull them >> from >> another source? If it was another source, how can I get a trace so I can >> get you the needed ID values? >> >> Thanks >> > > Hi, > > Did you update /etc/devd/usb.conf, install new kernel and reboot your > system? > > --HPS > > ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
On 12/21/14 21:21, Randall Fox wrote: Hi, The following patches should fix your problem: https://svnweb.freebsd.org/changeset/base/275790 https://svnweb.freebsd.org/changeset/base/275791 --HPS I finally was able to apply this, and it did not work for me. I am still getting the disconnect messages. It seems to have worked for someone else with a different (but similar) Tripp Lite unit. He had the same issue as I did, but this seemed to have fixed it. Were you able to get the ID values from my data? Or did you pull them from another source? If it was another source, how can I get a trace so I can get you the needed ID values? Thanks Hi, Did you update /etc/devd/usb.conf, install new kernel and reboot your system? --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
> Hi, > > The following patches should fix your problem: > > https://svnweb.freebsd.org/changeset/base/275790 > https://svnweb.freebsd.org/changeset/base/275791 > > --HPS I finally was able to apply this, and it did not work for me. I am still getting the disconnect messages. It seems to have worked for someone else with a different (but similar) Tripp Lite unit. He had the same issue as I did, but this seemed to have fixed it. Were you able to get the ID values from my data? Or did you pull them from another source? If it was another source, how can I get a trace so I can get you the needed ID values? Thanks On Mon, Dec 15, 2014 at 8:02 PM, Anish Mistry wrote: > On Monday, December 15, 2014 10:37:14 AM Hans Petter Selasky wrote: > > Hi, > > > > The following patches should fix your problem: > > > > https://svnweb.freebsd.org/changeset/base/275790 > > https://svnweb.freebsd.org/changeset/base/275791 > > > > --HPS > > Just tested and confirmed this works. > > Thanks, > > -- > Anish Mistry > ___ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org" > ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
On Monday, December 15, 2014 10:37:14 AM Hans Petter Selasky wrote: > Hi, > > The following patches should fix your problem: > > https://svnweb.freebsd.org/changeset/base/275790 > https://svnweb.freebsd.org/changeset/base/275791 > > --HPS Just tested and confirmed this works. Thanks, -- Anish Mistry ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
Hi, On 12/15/14 18:12, Randall Fox wrote: The following patches should fix your problem: https://svnweb.freebsd.org/changeset/base/275790 https://svnweb.freebsd.org/changeset/base/275791 Would it be correct to assume I need to recompile the kernel to get this working? You need to build a new kernel and update /etc/devd/usb.conf . Can you describe the issue and the solution? I will need to explain it to others. The problem is that the different USB vendors are using some undefined ID's without talking to each other getting standard values in there instead. Also, what version of FreeBSD would these eventually be included in, if any at all? 11/10 and 9. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
> The following patches should fix your problem: > > https://svnweb.freebsd.org/changeset/base/275790 > https://svnweb.freebsd.org/changeset/base/275791 Would it be correct to assume I need to recompile the kernel to get this working? Can you describe the issue and the solution? I will need to explain it to others. Also, what version of FreeBSD would these eventually be included in, if any at all? Thanks again.. On Mon, Dec 15, 2014 at 1:37 AM, Hans Petter Selasky wrote: > > Hi, > > The following patches should fix your problem: > > https://svnweb.freebsd.org/changeset/base/275790 > https://svnweb.freebsd.org/changeset/base/275791 > > --HPS > ___ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org" > ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
Hi, The following patches should fix your problem: https://svnweb.freebsd.org/changeset/base/275790 https://svnweb.freebsd.org/changeset/base/275791 --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
Patches attached. This only work if umodem is not already loaded, otherwise
it will grab the device.
On Saturday, December 13, 2014 11:22:25 AM you wrote:
> On 12/13/14 06:43, Anish Mistry wrote:
> > I have a HP Pre3 (webos) which when switched into USB tethering mode
> > with
> >
> > freetether exposes a RNDIS Ethernet Device. This should simply appear as
> > ue0 and off to the races. Unfortunately it attached via umodem due to
> > the usb.conf/devd usb_autoconf scripts and a device class overlap with
> > if_urndis. After commenting out those manual attach lines for umodem and
> > kldload if_urndis the device still didn't attach. After going into
> > if_rndis.c and enabling the "umodem" conflict section on line
> > ifrndis.c:173 (I'm running 10.1) and recompling the kernel module the
> > device appears and
> > functions, I'm using it to post this.
> >
> > How to I make this permenant (create a quirk?) so I don't have to hack
> >
> > usb.conf and if_rndis.c each time I upgrade?
> >
> > Thanks,
>
> Could you send the complete patch you are using?
>
> --HPS
--
Anish Mistry--- sys/dev/usb/net/if_urndis.c.orig 2014-12-13 10:20:50.0 -0500
+++ sys/dev/usb/net/if_urndis.c 2014-12-13 10:21:19.0 -0500
@@ -170,7 +170,7 @@
};
static const STRUCT_USB_HOST_ID urndis_host_devs[] = {
-#if 0
+#if 1
/* XXX this entry has a conflict an entry the umodem driver XXX */
{USB_IFACE_CLASS(UICLASS_CDC), USB_IFACE_SUBCLASS(UISUBCLASS_ABSTRACT_CONTROL_MODEL),
USB_IFACE_PROTOCOL(0xff)},
--- usb.conf.orig 2014-12-13 10:29:19.0 -0500
+++ usb.conf 2014-12-13 10:33:54.0 -0500
@@ -14,6 +14,14 @@
};
nomatch 32 {
+match "bus" "uhub[0-9]+";
+match "mode" "host";
+match "vendor" "0x0830";
+match "product" "0x8056";
+action "kldload -n if_urndis";
+};
+
+nomatch 32 {
match "bus" "uhub[0-9]+";
match "mode" "host";
match "vendor" "0x0123";
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: urndis and umodem device collision for ue device
On 12/13/14 06:43, Anish Mistry wrote: I have a HP Pre3 (webos) which when switched into USB tethering mode with freetether exposes a RNDIS Ethernet Device. This should simply appear as ue0 and off to the races. Unfortunately it attached via umodem due to the usb.conf/devd usb_autoconf scripts and a device class overlap with if_urndis. After commenting out those manual attach lines for umodem and kldload if_urndis the device still didn't attach. After going into if_rndis.c and enabling the "umodem" conflict section on line ifrndis.c:173 (I'm running 10.1) and recompling the kernel module the device appears and functions, I'm using it to post this. How to I make this permenant (create a quirk?) so I don't have to hack usb.conf and if_rndis.c each time I upgrade? Thanks, Could you send the complete patch you are using? --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
urndis and umodem device collision for ue device
I have a HP Pre3 (webos) which when switched into USB tethering mode with freetether exposes a RNDIS Ethernet Device. This should simply appear as ue0 and off to the races. Unfortunately it attached via umodem due to the usb.conf/devd usb_autoconf scripts and a device class overlap with if_urndis. After commenting out those manual attach lines for umodem and kldload if_urndis the device still didn't attach. After going into if_rndis.c and enabling the "umodem" conflict section on line ifrndis.c:173 (I'm running 10.1) and recompling the kernel module the device appears and functions, I'm using it to post this. How to I make this permenant (create a quirk?) so I don't have to hack usb.conf and if_rndis.c each time I upgrade? Thanks, ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0830 idProduct = 0x8056 bcdDevice = 0x0326 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <0123456789ABCDEF> bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0079 bNumInterfaces = 0x0004 bConfigurationValue = 0x0005 iConfiguration = 0x0004 bmAttributes = 0x00c0 bMaxPower = 0x00fa Additional Descriptor bLength = 0x08 bDescriptorType = 0x0b bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x08, 0x0b, 0x00, 0x02, 0x02, 0x06, 0x00, 0x07 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0002 bInterfaceSubClass = 0x0002 bInterfaceProtocol = 0x00ff iInterface = 0x0005 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x05, 0x24, 0x00, 0x10, 0x01 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x01 RAW dump: 0x00 | 0x05, 0x24, 0x01, 0x00, 0x01 Additional Descriptor bLength = 0x04 bDescriptorType = 0x24 bDescriptorSubType = 0x02 RAW dump: 0x00 | 0x04, 0x24, 0x02, 0x00 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x06 RAW dump: 0x00 | 0x05, 0x24, 0x06, 0x00, 0x01 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x0009 bRefresh = 0x bSynchAddress = 0x Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x000a bInterfaceSubClass = 0x bInterfaceProtocol = 0x iInterface = 0x0006 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Interface 2 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0002 bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0008 bInterfaceSubClass = 0x0006 bInterfaceProtocol = 0x0050 iInterface = 0x Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0001 bRefresh = 0x bSynchAddress = 0x Interface 3 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0003 bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x0047 bInterfaceProtocol = 0x0011 iInterface = 0x0008 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0084 bmAttributes = 0x000
