Closed GoogleCodeExporter closed 9 years ago
the driver is not ready
Original comment by jalav...@gmail.com
on 30 Aug 2008 at 12:03
Hi Jalavoui,
Firstly, I want to acknowledge you and the other project owners (jalavoui,
kazuhisa,
fliphdk, asaf.algawi, jalilcejin, braschlosan, ursulaslover, airflypan,
kemenaran,
cosmo1t, smcross, NCouffin, glorybox.away, mlazy73, jpwhittaker, madcat) for
stepping up to build this site and all the work you guys have done. It's
awesome.
do you think you can provide an overview of where the iwi4965 drivers are at?
are
there some milestones in building driver? can this be done without the help of
Intel? can we expect more active coding / developing on this driver?
Are there big differences for the mini pci express wireless card compared to
the
other stable drivers that were released? Also I'm curious how long you have
been
coding drivers?
Thanks for your time.
redash
Original comment by jdpope2006@gmail.com
on 17 Sep 2008 at 12:09
Hi,
I have Toshiba with 4965agn and iwi4965 network selector gives kernel ID 2
error.
Also I cannot find the wireless/ethernet in network preferences (it stays the
same -
only shows firewire).
We would be really happy if you fixed this problem. BTW, thank you for working
on
these drivers!
Original comment by saqib...@gmail.com
on 25 Oct 2008 at 11:54
Hi whats going on with this driver has anyone started or resumed working on the
driver yet?
Regards
Rick
Original comment by sandyshe...@gmail.com
on 22 Feb 2009 at 12:10
Hi, any news on 4965 driver update?
Original comment by Pavel.Pe...@gmail.com
on 23 Mar 2009 at 9:39
hi does anybody know if the 4965 driver project stills alive?
Original comment by elme...@gmail.com
on 13 Apr 2009 at 5:56
any news on 4965 driver update?
Original comment by nots...@gmail.com
on 3 May 2009 at 4:02
I also want to ask if there is something new out?
the networkselector doesn´t show me any network!
Original comment by Robin.Mo...@googlemail.com
on 9 May 2009 at 5:56
Original comment by jalav...@gmail.com
on 12 Jun 2009 at 1:03
Original issue reported on code.google.com by
yene...@gmail.com
on 6 Aug 2008 at 11:25Attachments: