Re: CFT: ndis(4) testers needed!

> If you haven't ever successfully run ndis before on this hardware, then testing
> the patch is quite useless :( Since we don't have a working reference point.

> Sorry for waisting your time.

> Totus tuus, Glebius.

I remember trying ndis from a USB-stick installation of FreeBSD 9.2-STABLE, but it failed.

I could try again, since I already have the setup, with
set hint.rsu.0.disabled="1"  from loader prompt.

UPDATE: I tried, rsu did not show on "ifconfig", but it seems not viable.  Last 15 lines of var/log/messages are:

Aug 14 06:34:34 amelia2 root: /etc/rc: INFO: RSA1 host key exists.
Aug 14 06:34:34 amelia2 root: /etc/rc: INFO: RSA host key exists.
Aug 14 06:34:34 amelia2 root: /etc/rc: INFO: DSA host key exists.
Aug 14 06:34:34 amelia2 root: /etc/rc: INFO: ECDSA host key exists.
Aug 14 06:34:34 amelia2 root: /etc/rc: INFO: ED25519 host key exists.
Aug 14 06:34:38 amelia2 login: ROOT LOGIN (root) ON ttyv0
Aug 14 06:36:19 amelia2 kernel: ndis0: <vendor 0x0bda product 0x8172, class 0/0, rev 2.00/2.00, addr 5> on usbus1
Aug 14 06:36:19 amelia2 kernel: ndis0: NDIS API version: 5.1
Aug 14 06:36:19 amelia2 kernel: ndis0: ioctl 0xfffff800 isn't supported
Aug 14 06:36:19 amelia2 last message repeated 20 times
Aug 14 06:36:19 amelia2 kernel: ndis0: init handler failed
Aug 14 06:36:19 amelia2 kernel: device_attach: ndis0 attach returned 6
Aug 14 06:36:19 amelia2 root: Unknown USB device: vendor 0x0cf3 product 0x3000 bus uhub4
Aug 14 06:36:19 amelia2 root: Unknown USB device: vendor 0x0cf3 product 0x9271 bus uhub4
Aug 14 06:37:26 amelia2 login: ROOT LOGIN (root) ON ttyv1

I feel like I was justified in this last try, having gone so far already.

I browsed

en.wikipedia.org/wiki/NDISwrapper

and saw various reasons why ndis would likely fail.  Maybe it's really not workable for Hiro H50191.

Now should I svn revert the src tree and update normally, without patches?

When possible, for the sake of others if not myself, it would be good to have more documentation of how to set up with ndis, and what to do when the Windows drivers don't include .inf and .sys files.

Regarding two Unknown USB device messages, I believe 0x9271 is on-motherboard quasi-USB wireless adapter, and 0x3000 might be on-motherboard Bluetooth (ubt).

Tom