LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices

Reply
 
Search this Thread
Old 01-27-2007, 03:50 PM   #1
jrp
LQ Newbie
 
Registered: Jan 2007
Location: Ottawa, Canada
Distribution: Ubuntu, FC6
Posts: 13

Rep: Reputation: 0
Question Freeze on starting ndiswrapper


I have followed a variety of leads to try and activate wireless on my T60p (Ubuntu). The most promising was to use ndiswrapper with the Windows driver for Atheros (the Windows XP installation which came with the machine lists ar5416.sys as the driver.

So I go through the procedure: install ndiswrapper, then unpack the driver, then issue
ndiswrapper -i net5416.inf

All that works fine.

sudo modprobe ndiswrapper

FREEZE. Need to disconnect PS & battery to get out of it...

So I check /var/log/messages and find out that things stopped at "disable_irq..."

I set a tail -f on /var/log/messages and retry. Sure enough things stop at the same place. (see copy below)
ndiswrapper -l gives the expected listing.
ndiswrapper -m behaves OK.

I try again with tail, this time the process goes one step further, and freezes again.
Note that the last step shows an error.

No info available on that error.

Anyone can shed light on this?

I'd be grateful!

BELOW the transcript of /var/log/messages:
==========================================================
sudo modprobe ndiswrapper

Jan 27 13:15:29 jrp kernel: [17179705.676000] ndiswrapper version 1.34 loaded (preempt=no,smp=yes)
Jan 27 13:15:29 jrp kernel: [17179705.752000] ndiswrapper: driver net5416 (,05/26/2006,6.0.0.180) loaded
Jan 27 13:15:29 jrp kernel: [17179705.756000] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 82
Jan 27 13:15:29 jrp kernel: [17179705.908000] ndiswrapper: using IRQ 82
Jan 27 13:15:30 jrp kernel: [17179706.408000] wlan0: ethernet device 00:16:cf:af:c7:e7 using serialized NDIS driver: net5416, version: 0x60000, NDIS version: 0x501, vendor: '', 168C:0024.5.conf
Jan 27 13:15:30 jrp kernel: [17179706.408000] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c01491cf> softlockup_tick+0x9f/0xf0 <c012bee1> update_process_times+0x31/0x80
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c0114d13> smp_apic_timer_interrupt+0x53/0x60 <c010413c> apic_timer_interrupt+0x1c/0x30
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f8d8149b> wrap_miniport_timer+0x2b/0x80 [ndiswrapper] <c01172c8> hpet_readl+0x8/0x10
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f8d880b0> timer_proc+0x50/0x70 [ndiswrapper] <c012be69> run_timer_softirq+0x159/0x1a0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f8d88060> timer_proc+0x0/0x70 [ndiswrapper] <c0127842> __do_softirq+0x72/0xe0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c01278e5> do_softirq+0x35/0x40 <c0127c0b> local_bh_enable+0x4b/0x80
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f8d86900> ExAllocatePoolWithTag+0x30/0x160 [ndiswrapper] <f8d86948> ExAllocatePoolWithTag+0x78/0x160 [ndiswrapper]
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f8d8311f> NdisAllocateMemoryWithTag+0x1f/0x40 [ndiswrapper] <f8d8311f> NdisAllocateMemoryWithTag+0x1f/0x40 [ndiswrapper]
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c016b8b0> file_free_rcu+0x0/0x10 <c011b8e7> activate_task+0x67/0xb0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c011ba7e> try_to_wake_up+0x6e/0x3d0 <c02487d4> dma_pool_alloc+0x194/0x1f0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c02487d4> dma_pool_alloc+0x194/0x1f0 <c011b8e7> activate_task+0x67/0xb0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c011aca4> __activate_task+0x14/0x30 <c011ba7e> try_to_wake_up+0x6e/0x3d0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c01e4d29> __delay+0x9/0x10 <f8d7cc99> KeStallExecutionProcessor+0x9/0x10 [ndiswrapper]
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c02d8aa4> schedule+0xf4/0xcc0 <c011b8e7> activate_task+0x67/0xb0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c011aca4> __activate_task+0x14/0x30 <c011ba7e> try_to_wake_up+0x6e/0x3d0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c011b8e7> activate_task+0x67/0xb0 <c011aca4> __activate_task+0x14/0x30
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c011ba7e> try_to_wake_up+0x6e/0x3d0 <c011b8e7> activate_task+0x67/0xb0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c011ba7e> try_to_wake_up+0x6e/0x3d0 <c02d8dce> schedule+0x41e/0xcc0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f8d90ddb> miniport_query_info_needed+0x1ab/0x290 [ndiswrapper] <f8d90ddb> miniport_query_info_needed+0x1ab/0x290 [ndiswrapper]
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c01e489c> vsnprintf+0x55c/0x640 <f8d908c1> miniport_set_info+0xe1/0x290 [ndiswrapper]
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f8d7d259> set_essid+0x59/0xd0 [ndiswrapper] <f8d91d11> NdisDispatchPnp+0x951/0x970 [ndiswrapper]
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f8d8ab26> IofCallDriver+0x36/0x70 [ndiswrapper] <f8d8d38b> IoSendIrpTopDev+0xbb/0x120 [ndiswrapper]
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f8d8d6d3> pnp_start_device+0x53/0xb0 [ndiswrapper] <f8d8d903> wrap_pnp_start_device+0x1d3/0x2b0 [ndiswrapper]
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f8d8da25> wrap_pnp_start_pci_device+0x45/0x50 [ndiswrapper] <c02862a8> netlink_broadcast+0x208/0x320
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c01edc33> pci_match_device+0x13/0xe0 <c01e0f5f> kobject_get+0xf/0x20
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c01edd76> pci_device_probe+0x56/0x80 <c0245f44> driver_probe_device+0x44/0xc0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c02460c2> __driver_attach+0x82/0x90 <c02458bb> bus_for_each_dev+0x3b/0x60
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c0245e86> driver_attach+0x16/0x20 <c0246040> __driver_attach+0x0/0x90
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c024552c> bus_add_driver+0x8c/0x140 <c02462f1> driver_register+0x41/0xa0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c01edf17> __pci_register_driver+0x47/0x70 <f8d80788> loader_init+0x138/0x260 [ndiswrapper]
Jan 27 13:15:40 jrp kernel: [17179716.160000] <f895c0c7> wrapper_init+0xc7/0xd2 [ndiswrapper] <c013cda8> sys_init_module+0x148/0x19c0
Jan 27 13:15:40 jrp kernel: [17179716.160000] <c0149540> disable_irq+0x0/0x30 <c0102fbb> sysenter_past_esp+0x54/0x79
<FREEZE>



Jan 27 13:29:19 jrp gconfd (root-5246): starting (version 2.16.0), pid 5246 user 'root'


NEXT TIME AROUND, IT GOES ONE STEP FURTHER

Jan 27 14:27:37 jrp kernel: [17180190.044000] <c0149540> disable_irq+0x0/0x30 <c0102fbb> sysenter_past_esp+0x54/0x79
Jan 27 14:29:11 jrp kernel: [17180283.924000] ndiswrapper (iw_get_network_type:306): getting network type failed: C0000001

Jan 27 14:44:03 jrp gnome-power-manager: (jrp) Screen dim because idle mode started
Jan 27 14:44:22 jrp gnome-power-manager: (jrp) Screen resume because idle mode ended

Jan 27 14:44:42 jrp gconfd (jrp-4764): Exiting
Jan 27 14:45:04 jrp exiting on signal 15
Jan 27 14:46:02 jrp syslogd 1.4.1#18ubuntu6: restart.



==========================================================
 
Old 01-28-2007, 10:19 AM   #2
2Gnu
Senior Member
 
Registered: Jan 2002
Location: Southern California
Distribution: Slackware 14.0
Posts: 1,874

Rep: Reputation: 49
You might try several versions of ndiswrapper while you're waiting for the MadWiFi drivers to catch up with the latest chipset.

http://madwifi.org/ticket/1001
 
Old 01-28-2007, 03:44 PM   #3
jrp
LQ Newbie
 
Registered: Jan 2007
Location: Ottawa, Canada
Distribution: Ubuntu, FC6
Posts: 13

Original Poster
Rep: Reputation: 0
Angry

Quote:
Originally Posted by 2Gnu
You might try several versions of ndiswrapper while you're waiting for the MadWiFi drivers to catch up with the latest chipset.

http://madwifi.org/ticket/1001
Thanks for the pointer.
I had already looked up madwifi, but had not noticed the warning about DWA-645 version 1.02.
As it happens, Ihad used that one.
Now I have moved over to version 1.01, and the ndiswrapper installs fine.
HOWEVER (there is always one more bug...) whilw I can see wlan0 under iwconfig, I can't see it under my netwrok connections Icon. When I invoke system>Administration>Networking, I do see it, I can activate it (apparently), but a ping on anything fails. I an still not connected.

Help!
 
Old 01-28-2007, 10:02 PM   #4
2Gnu
Senior Member
 
Registered: Jan 2002
Location: Southern California
Distribution: Slackware 14.0
Posts: 1,874

Rep: Reputation: 49
Try running things manually.

iwconfig wlan0 essid <your_ssid> mode managed
dhclient wlan0

If that works, edit the /etc network config script and forget the GUI.

If not, post any errors.
 
Old 01-29-2007, 08:27 AM   #5
jrp
LQ Newbie
 
Registered: Jan 2007
Location: Ottawa, Canada
Distribution: Ubuntu, FC6
Posts: 13

Original Poster
Rep: Reputation: 0
Thanks, 2Gnu.
In fact, as shown in the listing below, wlan0 was configured already.
But there is an IPv6 address and no IPv4 address, for some reason.
When I do dhclient, no response.
For confirmation, I did a dhclient on eth0, and the response was immediate.

What am I missing?
======================================
jrp@jrp:~$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1160 (1.1 KiB) TX bytes:1160 (1.1 KiB)

wlan0 Link encap:Ethernet HWaddr 00:16:CF:AF:C7:E7
inet6 addr: fe80::216:cfff:feaf:c7e7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:25 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:74 Memory:edf00000-edf10000

jrp@jrp:~$ dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

can't create /var/lib/dhcp3/dhclient.leases: Permission denied
Can't create /var/run/dhclient.pid: Permission denied
drop_privileges: could not set group id: Operation not permitted
jrp@jrp:~$ sudo dhclient wlan0
Password:
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:16:cf:af:c7:e7
Sending on LPF/wlan0/00:16:cf:af:c7:e7
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
jrp@jrp:~$ dhclient eth0
There is already a pid file /var/run/dhclient.pid with pid 30966
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

can't create /var/lib/dhcp3/dhclient.leases: Permission denied
Can't create /var/run/dhclient.pid: Permission denied
drop_privileges: could not set group id: Operation not permitted
jrp@jrp:~$ sudo dhclient eth0
There is already a pid file /var/run/dhclient.pid with pid 30966
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:16:41:e2:0d:45
Sending on LPF/eth0/00:16:41:e2:0d:45
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.1.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.109 -- renewal in 37843 seconds.
jrp@jrp:~$
========================================
 
Old 01-29-2007, 09:06 AM   #6
2Gnu
Senior Member
 
Registered: Jan 2002
Location: Southern California
Distribution: Slackware 14.0
Posts: 1,874

Rep: Reputation: 49
Does iwconfig show that the interface is associated?
 
Old 01-30-2007, 10:06 AM   #7
jrp
LQ Newbie
 
Registered: Jan 2007
Location: Ottawa, Canada
Distribution: Ubuntu, FC6
Posts: 13

Original Poster
Rep: Reputation: 0
Actually no, Access point: Not associated.
I have done the whole iwconfig setup (ESSID, WEP).
But it still does not associate.
 
Old 01-30-2007, 11:57 AM   #8
2Gnu
Senior Member
 
Registered: Jan 2002
Location: Southern California
Distribution: Slackware 14.0
Posts: 1,874

Rep: Reputation: 49
I would still try an older version of ndiswrapper, just in case.
Maybe try removing and reinstalling 1.34, putting both the .inf and .sys files in the directory where you run ndiswrapper -i.

Run ndiswrapper -l to see if all is reported as running.

Also, make sure that the interface is up before doing anything:
ifconfig wlan0 up
Then, iwconfig essid, etc.

Until iwconfig shows the card as associated, there's no use trying to run dhclient. You won't get an IP.

Make sure that no other wireless driver is loading which might conflict.

Otherwise, I'm out of brilliant suggestions.
 
Old 01-31-2007, 05:27 PM   #9
EcoR1
Member
 
Registered: Aug 2006
Posts: 34

Rep: Reputation: 15
Just a question, are you using kernel 2.6.19.* ? I know I had a hell of alot of problems with atheros and that kernel.. bottom line was you need to install 1.34rc2 but anyways just a note
 
Old 01-31-2007, 05:40 PM   #10
jrp
LQ Newbie
 
Registered: Jan 2007
Location: Ottawa, Canada
Distribution: Ubuntu, FC6
Posts: 13

Original Poster
Rep: Reputation: 0
EcoR1, thanks for asking. I am actually using 2.6.17-10
So I am not faced with your problem...
But I still need the insight of anyone who really understands wireless:

What is it that would keep my radio from associating with my access point? Its about 5 feet away, and other machines see it perfectly well from the other side of the apt.
 
Old 01-31-2007, 09:48 PM   #11
2Gnu
Senior Member
 
Registered: Jan 2002
Location: Southern California
Distribution: Slackware 14.0
Posts: 1,874

Rep: Reputation: 49
It's likely not associating because ndiswrapper is not properly installed or it's not compatible with the Windows drivers.

Did you try any of the steps I suggested in my last post? Did you run ndiswrapper -l?

Then again, I don't really understand wireless.
 
Old 02-01-2007, 12:51 PM   #12
jrp
LQ Newbie
 
Registered: Jan 2007
Location: Ottawa, Canada
Distribution: Ubuntu, FC6
Posts: 13

Original Poster
Rep: Reputation: 0
2Gnu:

Thank you for persevering in this thankless thread...

Yes, I did try all your suggestions, no joy.
I want to restart from scratch, but I am not too sure how to remove all trace of previous activity.
Any suggestions?
Maybe there is some leftover from a previous attempt which gums up the works :-)

Also, I keep getting "Interface does not support scanning" whenever I try iwlist.
Any idea why?

Thanks again
 
Old 02-01-2007, 01:16 PM   #13
2Gnu
Senior Member
 
Registered: Jan 2002
Location: Southern California
Distribution: Slackware 14.0
Posts: 1,874

Rep: Reputation: 49
iwlist isn't working because the driver isn't working.

To undo the ndiswrapper installation, cd to the directory where you unzipped the package - /home/your_home/ndiswrapper-1.34 for example - and as root, run make uninstall.

Then, make, make install.
Post any errors.

Copy both the .sys and .inf files for your card (and any .bin which may contain firmware) to some directory. cd to that directory and run, as root, ndiswrapper -i driver_name.inf
Post any errors.

Run, as root, modprobe ndiswrapper
Post any errors

Run, as root, ndiswraper -l
Post the output.

This is all in the INSTALL file that comes with the source package, if you want to use that as a reference.

Then, make sure the interface is there with iwconfig.
Bring up the interface (may be redundant, but sometimes helps) with ifconfig wlan0 up
iwconfig mode managed essid your_ssid, etc.
Check for association, then dhclient wlan0

Post any errors.
 
Old 02-02-2007, 06:26 AM   #14
jrp
LQ Newbie
 
Registered: Jan 2007
Location: Ottawa, Canada
Distribution: Ubuntu, FC6
Posts: 13

Original Poster
Rep: Reputation: 0
Thanks, 2Gnu

I did what you suggested.
No joy.
In fact, the wlan0 interface does not even appear, now. (and the wireless indicator on my machine no longer lights up).

Here is the transcript of my terminal session:
..........................................
jrp@jrp:~/ndiswrapper-1.34$ sudo make uninstall
Password:
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /sbin/loadndisdriver
removing /usr/sbin/ndiswrapper
removing /usr/sbin/ndiswrapper-buginfo
removing /lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper
/bin/rm: cannot remove `/lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper': Is a directory
removing /lib/modules/2.6.17-10-generic/misc/ndiswrapper.ko
jrp@jrp:~/ndiswrapper-1.34$ sudo make uninstall
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper
/bin/rm: cannot remove `/lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper': Is a directory
make: *** [uninstall] Error 1
jrp@jrp:~/ndiswrapper-1.34$ cd ../ndis*2
jrp@jrp:~/ndiswrapper-1.34rc2$ sudo make uninstall
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper
/bin/rm: cannot remove `/lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper': Is a directory
make: *** [uninstall] Error 1
jrp@jrp:~/ndiswrapper-1.34rc2$ sudo make uninstall
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper
/bin/rm: cannot remove `/lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper': Is a directory
make: *** [uninstall] Error 1
jrp@jrp:~/ndiswrapper-1.34rc2$ ls /lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper
jrp@jrp:~/ndiswrapper-1.34rc2$ ls -al /lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper
total 12
drwxr-xr-x 2 root root 4096 2007-01-27 12:58 .
drwxr-xr-x 21 root root 8192 2007-01-26 21:12 ..
jrp@jrp:~/ndiswrapper-1.34rc2$ sudo make clean
make -C driver clean
make[1]: Entering directory `/home/jrp/ndiswrapper-1.34rc2/driver'
rm -rf ndiswrapper.ko ndiswrapper.o crt.o hal.o iw_ndis.o loader.o ndis.o ntoskernel.o ntoskernel_io.o pe_linker.o pnp.o proc.o rtl.o wrapmem.o wrapndis.o wrapper.o usb.o divdi3.o usb.o win2lin_stubs.o \
divdi3.o workqueue.o .*.ko.cmd .*.o.cmd \
ndiswrapper.mod.[oc] *~ .tmp_versions Modules.symvers Module.symvers
make[1]: Leaving directory `/home/jrp/ndiswrapper-1.34rc2/driver'
make -C utils clean
make[1]: Entering directory `/home/jrp/ndiswrapper-1.34rc2/utils'
rm -f *~ *.o loadndisdriver
make[1]: Leaving directory `/home/jrp/ndiswrapper-1.34rc2/utils'
rm -f *~
rm -fr ndiswrapper-1.34rc2 ndiswrapper-1.34rc2.tar.gz patch-stamp
jrp@jrp:~/ndiswrapper-1.34rc2$ sudo make
make -C driver
make[1]: Entering directory `/home/jrp/ndiswrapper-1.34rc2/driver'
make -C /lib/modules/2.6.17-10-generic/build SUBDIRS=/home/jrp/ndiswrapper-1.34rc2/driver
make[2]: Entering directory `/usr/src/linux-headers-2.6.17-10-generic'
LD /home/jrp/ndiswrapper-1.34rc2/driver/built-in.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/crt.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/hal.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/iw_ndis.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/loader.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/ndis.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/ntoskernel.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/ntoskernel_io.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/pe_linker.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/pnp.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/proc.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/rtl.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/wrapmem.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/wrapndis.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/wrapper.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/usb.o
CC [M] /home/jrp/ndiswrapper-1.34rc2/driver/divdi3.o
LD [M] /home/jrp/ndiswrapper-1.34rc2/driver/ndiswrapper.o
Building modules, stage 2.
MODPOST
CC /home/jrp/ndiswrapper-1.34rc2/driver/ndiswrapper.mod.o
LD [M] /home/jrp/ndiswrapper-1.34rc2/driver/ndiswrapper.ko
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-10-generic'
make[1]: Leaving directory `/home/jrp/ndiswrapper-1.34rc2/driver'
make -C utils
make[1]: Entering directory `/home/jrp/ndiswrapper-1.34rc2/utils'
gcc -g -Wall -I../driver -o loadndisdriver loadndisdriver.c
make[1]: Leaving directory `/home/jrp/ndiswrapper-1.34rc2/utils'
jrp@jrp:~/ndiswrapper-1.34rc2$ ls -al /lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper
total 12
drwxr-xr-x 2 root root 4096 2007-01-27 12:58 .
drwxr-xr-x 21 root root 8192 2007-01-26 21:12 ..
jrp@jrp:~/ndiswrapper-1.34rc2$ sudo make install
make -C driver install
make[1]: Entering directory `/home/jrp/ndiswrapper-1.34rc2/driver'
make -C /lib/modules/2.6.17-10-generic/build SUBDIRS=/home/jrp/ndiswrapper-1.34rc2/driver
make[2]: Entering directory `/usr/src/linux-headers-2.6.17-10-generic'
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-10-generic'
echo /lib/modules/2.6.17-10-generic/misc
/lib/modules/2.6.17-10-generic/misc
mkdir -p /lib/modules/2.6.17-10-generic/misc
install -m 0644 ndiswrapper.ko /lib/modules/2.6.17-10-generic/misc
/sbin/depmod -a 2.6.17-10-generic -b /
make[1]: Leaving directory `/home/jrp/ndiswrapper-1.34rc2/driver'
make -C utils install
make[1]: Entering directory `/home/jrp/ndiswrapper-1.34rc2/utils'
install -D -m 755 loadndisdriver /sbin/loadndisdriver
install -D -m 755 ndiswrapper /usr/sbin/ndiswrapper
install -D -m 755 ndiswrapper-buginfo /usr/sbin/ndiswrapper-buginfo

NOTE: Windows driver configuration file format has changed since 1.5. You must re-install Windows drivers if they were installed before.
make[1]: Leaving directory `/home/jrp/ndiswrapper-1.34rc2/utils'
mkdir -p -m 0755 /usr/share/man/man8
install -m 644 ndiswrapper.8 /usr/share/man/man8
install -m 644 loadndisdriver.8 /usr/share/man/man8
jrp@jrp:~/ndiswrapper-1.34rc2$ ls -al /lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper
total 12
drwxr-xr-x 2 root root 4096 2007-01-27 12:58 .
drwxr-xr-x 21 root root 8192 2007-01-26 21:12 ..
jrp@jrp:~/ndiswrapper-1.34rc2$ modprobe -l ndiswrapper
/lib/modules/2.6.17-10-generic/misc/ndiswrapper.ko
jrp@jrp:~/ndiswrapper-1.34rc2$ ls /lib/modules/2.6.17-10-generic/misc/ndiswrapper.ko
/lib/modules/2.6.17-10-generic/misc/ndiswrapper.ko
jrp@jrp:~/ndiswrapper-1.34rc2$ ls /lib/modules/2.6.17-10-generic/misc
ndiswrapper.ko
jrp@jrp:~/ndiswrapper-1.34rc2$

====================================================
jrp@jrp:~$ cd Driver
jrp@jrp:~/Driver$ ls
ar5416.sys net5416.cat net5416.inf
jrp@jrp:~/Driver$ ndiswrapper -i net5416.inf
driver net5416 is already installed
jrp@jrp:~/Driver$ ndiswrapper -l
net5416 : driver installed
device (168C:0024) present
jrp@jrp:~/Driver$ sudo modprobe ndiswrapper
Password:
jrp@jrp:~/Driver$ iwconfig
lo no wireless extensions.

irda0 no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

jrp@jrp:~/Driver$ lsmod | grep ndiswrapper
ndiswrapper 200724 0
usbcore 134912 7 ndiswrapper,usbhid,wacom,hci_usb,uhci_hcd,ehci_hcd
jrp@jrp:~/Driver$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:41:E2:0D:45
inet addr:192.168.1.109 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::216:41ff:fee2:d45/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4525 errors:0 dropped:0 overruns:0 frame:0
TX packets:2863 errors:0 dropped:0 overruns:0 carrier:0
collisions:6 txqueuelen:100
RX bytes:2205325 (2.1 MiB) TX bytes:767787 (749.7 KiB)
Base address:0x3000 Memory:ee000000-ee020000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3142 errors:0 dropped:0 overruns:0 frame:0
TX packets:3142 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1065543 (1.0 MiB) TX bytes:1065543 (1.0 MiB)

jrp@jrp:~/Driver$
...........................................

I hope there is some glaring mistake which you can see in this transcript...

JP
 
Old 02-02-2007, 09:22 AM   #15
2Gnu
Senior Member
 
Registered: Jan 2002
Location: Southern California
Distribution: Slackware 14.0
Posts: 1,874

Rep: Reputation: 49
No glaring errors. This is the only part I don't like:
Code:
jrp@jrp:~/Driver$ ndiswrapper -i net5416.inf
driver net5416 is already installed
It might be a useless move, but I would nuke the /etc/ndiswrapper directory and repeat the ndiswrapper -i step to confirm successful installation messages.

You're using 1.34RC2. Have you always been using that version? Have you tried an older one?

The only other suggestion I have is to contact the ndiswrapper devs. Maybe they can provide some guidance.
 
  


Reply

Tags
freeze, ndiswrapper


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
random system freeze with ndiswrapper amam Linux - Wireless Networking 3 03-31-2005 03:51 PM
ndiswrapper kernel freeze! buffamolo Linux - Hardware 0 02-23-2005 08:53 PM
system freeze - ndiswrapper in FC3 topcatzz Linux - Wireless Networking 13 12-21-2004 04:19 AM
ndiswrapper make os freeze a_spak Linux - Laptop and Netbook 5 08-18-2004 10:34 AM
Modprobe Ndiswrapper => Freeze Jaster Linux - Software 5 08-17-2004 10:05 AM


All times are GMT -5. The time now is 12:32 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration