Tiny Core Linux

Tiny Core Extensions => TCE News => TCE 1.x => Topic started by: Juanito on March 14, 2009, 01:52:29 AM

Title: ndiswrapper_full
Post by: Juanito on March 14, 2009, 01:52:29 AM
ndiswrapper_full tcem/tczm extensions posted.

If, like I found, the ndiswrapper extension will not parse your windows driver file, then you need ndiswrapper_full and the perl5 extension to get ndiswrapper working.

Note that once you've used ndiswrapper_full to create the necessary driver files in /etc/ndiswrapper/drivername, you can make an extension of these files and use the ndiswrapper extension, which does not need perl, from that point onwards.

An example howto:
Code: [Select]
$ ls /mnt/sda1/drivers/ndiswrapper
bcm43xx.cat  bcmwl5.inf   bcmwl5.sys
$ sudo ndiswrapper -i /mnt/sda1/drivers/ndiswrapper/bcmwl5.inf
installing bcmwl5 ...
$ sudo ndiswrapper -l                                         
bcmwl5 : driver installed
        device (14E4:4315) present
$ sudo ndiswrapper -m
adding "alias wlan0 ndiswrapper" to /etc/modprobe.conf ...
$ sudo modprobe ndiswrapper
$ dmesg | tail -10
ndiswrapper version 1.54 loaded (smp=yes, preempt=no)
ndiswrapper: driver bcmwl5 (Broadcom,09/20/2007, loaded
ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:0c:00.0 to 64
ndiswrapper: using IRQ 17
wlan0: ethernet device 00:24:2b:60:07:5a using NDIS driver: bcmwl5, version: 0x4aa190c, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4315.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
usbcore: registered new interface driver ndiswrapper

$ sudo iwconfig wlan0 essid "ssid"
$ sudo iwconfig wlan0 key restricted 12:34:56:78:9A:BC:DE:F0:12:34:56:78:9A
$ sudo udhcpc -b -i wlan0
udhcpc (v1.12.3) started
Sending discover...
Sending discover...
Sending select for
Lease of obtained, lease time 600
deleting routers
route: SIOCDELRT: No such process
adding dns
adding dns

[to make your personal ndiswrapper driver extension]
$ cd /
$ sudo tar -cvzf bcmwl5.tce etc/ndiswrapper

After reboot, all that remains is to load the ndiswrapper and (in this example) bcmwl5 extensions and then "sudo modprobe ndiswrapper".

Code: [Select]
Title:          ndiswrapper_full.tcem
Description:    ndiswrapper
Version:        1.54
Author:         see list of sites below
Original-site:  see list of sites below
Copying-policy: see list of sites below
Size: 97KB
Extension_by:   juanito
Comments:       ndiswrapper for tinycore
                Requires perl5.tcel and wireless_tools.tcel
                example howto:
                $ sudo ndiswrapper -i /mnt/sda1/drivers/ndiswrapper/bcmwl5.inf
                $ sudo ndiswrapper -l
                $ sudo ndiswrapper -m
                $ sudo modprobe ndiswrapper
                Note: you can now make an extension out of everything in
                .. /etc/ndiswrapper and use it with the ndiswrapper extension
                ..to avoid having to use the perl5 extension
                This extension contains:
                ndiswrapper-1.54 - GPL - http://freefr.dl.sourceforge.net/sourceforge/ndiswrapper/ndiswrapper-1.54.tar.gz
Change-log:     First version
Current:        2009/03/13
Title: Re: ndiswrapper_full
Post by: coreplayer2 on April 17, 2012, 01:34:52 PM
Well I couldn't find "ndiswrapper_full" in the repository,  it appears that the components of the full version are included in or with ndiswrapper.tcz  in tc 4.4..?  But I could be wrong
Title: Re: ndiswrapper_full
Post by: Juanito on April 17, 2012, 07:29:22 PM
That should be correct
Title: Re: ndiswrapper_full
Post by: coreplayer2 on May 08, 2012, 09:37:52 PM
Honestly at first I thought the ndiswrapper was a little too bloated, but I got to tell you, the module is growing on me, especially with the success I've had with it lately.

Now I'm thinking, how can we make this automated..?  H'mmm..   :-\
Title: Re: ndiswrapper_full
Post by: Juanito on May 08, 2012, 10:20:01 PM
Since perl is only used when you load ndiswrapper - you can make an extension out of the files copied to /etc - you can reduce the bloat.

For me the issue is more that, in my experience, you need to try several (many) windows drivers before you find one that works and the more recent drivers require a version of ndis that is not yet supported by ndiswrapper.

..and it's worth remembering that the reason you need to use ndiswrapper in the first place is because the manufacturers do not make a driver available to linux - i.e. if you have a choice then better to chose alternate hardware.