[macdude425]

I just put Debian Sarge on my dad's Latitude D600, and so far it works great except for one thing: Ndiswrapper. Whenever I try to 'modprobe ndiswrapper' the kernel crashes, and the system locks up. So far, I haven't been able to find out why.

Kernel is 2.6.8-2-686. Any ideas are welcome.

TIA.

[macdude425]

OK, that no longer seems to be a problem, but now it doesn't show a WLAN0 interface. Any ideas?

[jakec]

Macdude:

Try this Link

http://lists.debian.org/debian-lapto.../msg00253.html

it might help,

Jake

[macdude425]

No luck; I'm still being thrown into a kernel panic everytime I try.

[jeelliso]

I'm not sure if you've done this already, but once you load ndiswrapper & install the driver you wish to use, you have to run

ndiswrapper -m

to write the alias. Without it, the wlan0 interface is not configured.

What is throwing you into a lockup?

[macdude425]

modprobe ndiswrapper throws it into a panic.

I have done ndiswrapper -m and depmod -a, all of which run flawlessly, but when I go to modprobe, it locks up.

[jakec]

Macdude,

Sorry for posting twice, seperate thought of mine

Sounds like your intrid file is playing up. Intrid is a RAM disk that is initialized or loaded by the boot loader before the kernel is started.

you can find a complete discription intrid here: http://www.security-protocols.com/un.../initrd.4.html

Anyway you might need to check the etc./lilo.conf or the /boot/grub/menu.lst to find out if your Kernel is using intrid. If you see a file that looks like initrd.img-<version> or something similar, you need to use the mkinitrd command OR configure your kernel so that initrd is not necessary, then compile again.

here is a HOWto on mkinitrid, it tells you how to allocate and de-allocate the initrid ramdsisk. Pay particular attention to the bold heading The mkinitrd command it is a fair way down the page you will just have to look for it

http://snow.nl/dist/xhtmlc/ch01s02.html

Hope this Helps,

Jake

[macdude425]

I think I will just recompile. I've been meaning to do it anyways...

[macdude425]

:bump:

So I totally recompiled with a new kernel (2.6.15.6) and recompiled Ndiswrapper, which I HOPED would fix the problem, but sure enough, It's still doing it.

Any ideas?

[Sevoma]

The kernel panic is most likley from an incompatable driver. Some drivers will cause a kernel panic. See this: http://ndiswrapper.sourceforge.net/m...index.php/List
for compatible wireless cards and drivers that you can use for them