Support for wireless

Post by **clem** » Sun Dec 03, 2006 7:30 am

I don't think we will automate the wireless configuration in Bianca, but if it helps we could have ndiswrapper-utils installed by default. Maybe we could even include some INF files and a copy of the ndiswrapper wiki on the disc...

.. would that help ?

Post by **clem** » Mon Dec 04, 2006 9:03 am

Well... you mean ndisgtk automates the whole process so you don't have to fetch the right INF file yourself ? Also, how does ndisgtk fetch the INF file... via an Internet connection ? lol

We have to assume the user won't be connected at this stage.

Clem

jonpackard · Post by **jonpackard** » Mon Dec 04, 2006 11:51 am

I think the best bet is to have a GUI setup utility that allows the user to select the driver files from a CD or other media. Most users will have a driver disc or will have them on their windows partition.

Post by **clem** » Tue Dec 05, 2006 9:02 am

Ok I'll look into that and probably add those three packages to Bianca.

Post by **clem** » Wed Dec 06, 2006 2:52 pm

Oh we'll find a way. The more we look at it the more we see things to remove and others to add

jonpackard · Post by **jonpackard** » Thu Dec 07, 2006 9:42 am

manishk wrote:I just read that Fiesty supports these Broadcom cards by default.

I read it in on a blog, who has been testing Fiesty.

May be you can just look into it, because I dint know what to make of it.

I just ran the Fiesty Fawn Alpha 1 Live CD on my fiancee's laptop that uses a broadcom wireless card. It still gives the same errors Edgy gives about broadcom drivers during boot. Looks like ndiswrapper is still the way to go.

Post by **clem** » Thu Dec 07, 2006 10:52 am

A Quick update on that: ndiswrapper 1.1 and ndisgtk will be there in Bea's stable release.

Clem

jonpackard · Post by **jonpackard** » Thu Dec 07, 2006 11:16 am

Thanks Clem! Now I'll be able to run the Live CD on my fiancee's laptop.

Post by **clem** » Sat Dec 09, 2006 3:14 pm

Ok, I'm including ndiswrapper-utils-1.8 in Bea. I don't like to do that, especially after a code freeze, and I hope I'm not introducing a bug by doing that. I suppose in the worst case, people will be able to remove that package and default their ndiswrapper back to a 1.1 version by doing so.

Clem