Re: Project Evil: TI ACX111 non-success

I guess I tried everything possible...
acx driver failed cause it's simply not supported "acx111".
ndis driver failed also with 3 different firmware types...

--------------
cardbus1: Expecting link target, got 0xcb
cardbus1: Resource not specified in CIS: id=10, size=2000
cardbus1: Resource not specified in CIS: id=14, size=20000
ndis0: <D-Link AirPlus G+ DWL-G650+ Wireless Cardbus Adapter> mem 0x88000000-0x8
801ffff,0x88020000-0x88021fff irq 11 at device 0.0 on cardbus1
ndis0: [GIANT-LOCKED]
ndis0: NDIS API version: 5.1
ndis0: init handler failed
device_attach: ndis0 attach returned 6
cardbus1: release_all_resource: Resource still owned by child, oops. (type=3, ri
d=20, addr=88000000)
cbb1: CardBus card activation failed
-------------

best regards,
-Dennis

On Thu, Aug 12, 2004 at 10:00:58AM -0700, Evan Dower wrote:
> With ndis do you get the same "init handler failed" error message? Have you 
> emailed Bill Paul with all the appropriate info? What have you tried? What 
> were the results?
> 
> --
> Evan Dower
> Undergraduate, Computer Science
> University of Washington
> Public key: http://students.washington.edu/evantd/pgp-pub-key.txt
> Key fingerprint = D321 FA24 4BDA F82D 53A9  5B27 7D15 5A4F 033F 887D
> 
> 
> 
> 
> 
> >From: Dennis Berger <db_at_nipsi.de>
> >To: Evan Dower <evantd_at_hotmail.com>
> >CC: freebsd-current_at_freebsd.org
> >Subject: Re: Project Evil: TI ACX111 non-success
> >Date: Thu, 12 Aug 2004 09:56:15 +0200
> >
> >I have the dlink g650+ which also has the acx111 chipset...
> >NDIS failed acx driver failed also.
> >regards,
> >-Dennis
> >
> >On Wed, Aug 11, 2004 at 04:40:58PM -0700, Evan Dower wrote:
> >> I've been trying to get the ndisulator to work for my NetGear WG311v2 so 
> >I
> >> can take the ethernet cables and switches offthe floor in my hall. The
> >> following is the "conversation" I've had with Bill Paul. It is perhaps 
> >best
> >> to read from the bottom up to get the chronology right. Also, as it 
> >turns
> >> out the net/acx100 port makes no claim to support the acx111, and I was
> >> eventually able to build and load it, though of course it didn't work
> >> because it doesn't support the acx111. Any help would be greatly
> >> appreciated.
> >>
> >> --
> >>
> >> I managed to get rid of the "can't re-use a leaf" messaged by deleting
> >> the duplicate entry in ndis_driver_data.h. For some reason, whenever I
> >> try to load if_ndis.ko (ndis.ko is already loaded), I get messages about
> >> amdpm. Perhaps ndis returning 6 and failing to load is a result of the
> >> same return value from trying to attach amdpm.
> >>
> >> amdpm0: <AMD 756/766/768/8111 Power Management Controller> port
> >> 0xe4e0-0xe4ff at device 7.3 on pci0
> >> amdpm0: could not map i/o space
> >> device_attach: amdpm0 attach returned 6
> >> ndis0: <NETGEAR WG311v2 802.11g Wireless PCI Adapter> mem
> >> 0xf0800000-0xf081ffff,0xf1000000-0xf1001fff irq 17 at device 6.0 on pci2
> >> ndis0: [GIANT-LOCKED]
> >> no match for srand
> >> ndis0: NDIS API version: 5.1
> >> ndis0: init handler failed
> >> device_attach: ndis0 attach returned 6
> >>
> >> Thanks again,
> >> Evan Dower
> >>
> >> El mar, 20-07-2004 a las 10:58, Evan Dower escribi?:
> >> >I have figured out that the "can't re-use a leaf" message is coming 
> >from
> >> >trying to register a sysctl, which comes from the .inf file. This seems
> >> >to indicate some limitations on the complexity of .inf files that can 
> >be
> >> >properly parsed and turned into a list of sysctls. Since I'm not 
> >exactly
> >> >sure what those limitations are, I'm sending you a link to the .inf 
> >file
> >> >(and the .sys file for good measure)? Other than that, it looks like
> >> >srand might just need to be plugged into one of the function tables
> >> >(probably the hal table, I guess). Also, if you can tell me what
> >> >limitations exist for the .inf file, I will gladly modify it to work 
> >and
> >> >make it available to other WG311v2 owners.
> >> >Thanks again,
> >> >Evan Dower
> >> >Note: Much of the .inf file (anything not for XP) is commented out in 
> >an
> >> >attempt to make things work. This was my doing. It didn't ship that 
> >way.
> >> >Since I don't really understand the Windows registry, I didn't get too
> >> >adventurous.
> >> >
> >> >Files at: http://students.washington.edu/evantd/pub/evil/
> >> >
> >> >El lun, 12-07-2004 a las 16:05, Evan Dower escribi?:
> >> >> I have a Netgear WG311v2. The v2 turns out to be very important as 
> >the
> >> >> original (v1 you might call it now) was based on an Atheros AR5212 
> >and
> >> >> was thus supported by the ath driver. v2 is based on the the TI 
> >AXC111
> >> >> (aka TNETW1130), which should be supported by the net/acx100 port, 
> >but
> >> >> if_acx.ko fails to load due to a missing __panic symbol. Following 
> >the
> >> >> instructions you posted in an email, I made ndis_driver_data.h and
> >> >> built and loaded the if_ndis.ko module (after loading ndis.ko or
> >> >> compiling it into the kernel). I used the Windows XP .SYS and .INF
> >> >> files, though the Windows 2000 versions gave the same result, the
> >> >> Windows 98 files produced a module that panicked on load, and I 
> >didn't
> >> >> try the Windows ME files. The following is the output from `make
> >> >> load`.
> >> >> > /sbin/kldload -v /usr/current/src/sys/modules/if_ndis/if_ndis.ko
> >> >> ndis0: <NETGEAR WG311v2 802.11g Wireless PCI Adapter> mem
> >> >> 0xec800000-0xec81ffff,
> >> >> 0xed000000-0xed001fff irq 17 at device 6.0 on pci2
> >> >> ndis0: [GIANT-LOCKED]
> >> >> can't re-use a leaf (dot11DesiredBSSType)!
> >> >> no match for srand
> >> >> ndis0: NDIS API version: 5.1
> >> >> ndis0: init handler failed
> >> >> device_attach: ndis0 attach returned 6
> >> >> Loaded /usr/current/src/sys/modules/if_ndis/if_ndis.ko, id=11
> >> >> > Loading the module does not create /dev/ndis0 or /dev/if_ndis0 (or
> >> >> anything of the sort). I am running today's -CURRENT.
> >> >> > It seems that it requires srand, and I assume the 'can't re-use a 
> >leaf
> >> >> (dot11DesiredBSSType)!' is also a show-stopper. I ordered my card 
> >from
> >> >> newegg.com for about $50.
> >> >> > If there is anything else you might be interested in (a verbose 
> >boot
> >> >> log, copies of the .SYS and .INF files, testing for patches, etc.),
> >> >> just let me know. I'd be happy to help (especially since the result 
> >is
> >> >> a working wireless connection).
> >> >> > Thanks very much,
> >>
> >> --
> >> Evan Dower
> >> Undergraduate, Computer Science
> >> University of Washington
> >> Public key: http://students.washington.edu/evantd/pgp-pub-key.txt
> >> Key fingerprint = D321 FA24 4BDA F82D 53A9  5B27 7D15 5A4F 033F 887D
> >>
> >> _________________________________________________________________
> >> Don?t just search. Find. Check out the new MSN Search!
> >> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
> >>
> >> _______________________________________________
> >> freebsd-current_at_freebsd.org mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> To unsubscribe, send any mail to 
> >"freebsd-current-unsubscribe_at_freebsd.org"
> 
> _________________________________________________________________
> On the road to retirement? Check out MSN Life Events for advice on how to 
> get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
>