DISCUSSION: ndiswrapper on Debian Sarge without having to compile anything
LinuxAnswers DiscussionThis forum is to discuss articles posted to LinuxAnswers.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I've been f#&$*(&# with this awful awful awful version of debian sarge called Demudi. And I have been trying for almost TWO MONTHS to get my wireless card working. Actually, it was a struggle to get my ethernet connection working.
In defense of Demudi, it is beta, and I am an idiot.
But congratulations, you fixed my computer.
The only problem now is, I have to switch kernels for different uses?!? Is this good or normal. Demudi relies on a special kernel (2.6.8-12-multimedia-686) to connect all of its audio applications. Yeah, it's for audiophiles and it's weird. The trick was to start the computer with the sane kernel. So, I have one kernel for the internet, and one for my music... is this where recompiling comes in?
I think it would help your tutorial to either insert a "/" before "lib" in:
insmod lib/modules/`uname -r`/misc/ndiswrapper.ko
so it reads:
insmod /lib/modules/`uname -r`/misc/ndiswrapper.ko
in case they are not in the right directory. When I first installed linux (Mepis) I had no clue how to navigate in the konsole, and wouldn't have known that all i had to do was change directories.
but great tutorial. it's amazing how much easier this method was than the gui method in Mepis..at least for me.
after:
root@box:~# apt-get install wireless-tools
I get this:
You are running a kernel (version 2.6.8-2-686) and attempting to remove
the same version. This is a potentially disastrous action. Not only
will /boot/vmlinuz-2.6.8-2-686 be removed, making it impossible to boot
it, (you will have to take action to change your boot loader to boot
a new kernel), it will also remove all modules under the directory
/lib/modules/2.6.8-2-686. Just having a copy of the kernel image is not
enough, you will have to replace the modules too.
I repeat, this is very dangerous. If at all in doubt, answer
no. If you know exactly what you are doing, and are prepared to
hose your system, then answer Yes.
Remove the running kernel image (not recommended) [No]?
Here I write No and:
dpkg: error processing kernel-image-2.6.8-2-686 (--remove):
subprocess pre-removal script returned error exit status 1
dpkg: initrd-tools: dependency problems, but removing anyway as you request:
kernel-image-2.6.8-2-686 depends on initrd-tools (>= 0.1.63).
Removing initrd-tools ...
Errors were encountered while processing:
kernel-image-2.6.8-2-686
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@box:~#
If I choice Yes ,after restart I allready there is no Linux2.6.8
Any idea?
I wrote : apt get -f install and
wireless-tools is already the newest version
but new problem:
root@box:~# apt-get install ndiswrapper-modules-2.6.8-2-686
Reading Package Lists... Done
Building Dependency Tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
ndiswrapper-modules-2.6.8-2-686: Depends: ndiswrapper-utils (>= 1.1-1) but it is not going to be installed
Depends: ndiswrapper-utils (<= 1.1-999) but it is not going to be installed
E: Broken packages
After this I have no idea - help,pls
To bring up a network interface automatically at reboot we can edit /etc/network/interfaces, here's my copy
Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# My wireless card
auto wlan0
iface wlan0 inet dhcp
wireless-essid WRC_Network
I did compile ndiswrapper manually on slackware and debian before, but somehow I can't get it compiled on kernel 2.6.12. Anyone successfully did that?
I'm a total Noob, but I'm trying to get my wireless Internet card working (WMP54G). This is my problem. I down -loaded and installed Sarge 2.4.27-2-356 from CD images on my PIII Dell. Following your instructions I was able to upgrade my kernel to 2.6.8-2-386. (FYI, this process didn't download from the Internet, rather, I was prompted to use one of my CDs). Upon reboot, I selected 2.6.8. I was able to install the wireless tools. I tried to install ndiswrapper but was given an error message that is didn't recognize the package. I suspect part of the problem is that Sarge doesn't try to download the filed from the net. Instead, it defaults to the CDs. Do I have to update my sources.list file? If so, with what and how. I've played with this file in the desktop environment but wasn't able to save any changes. Do I have to edit this via command prompt? If so, what command. Did I mention I'm a total Noob.
Also, for some reason, I can't surf in 2.6.8 via my NIC. I can, however, still surf in 2.4.27. Weird. Are there settings I need to update?
Thank you for teh reply. Here are the contents of from /etc/apt/sources.list
#deb file:///cdrom/ sarge main
deb cdrom:[Debian GNU/Linux 3.1 r0a _Sarge_ - Official i386 Binary-1 (20050607)]/ unstable contrib main
deb cdrom:[Debian GNU/Linux 3.1 r0a _Sarge_ - Official i386 Binary-5 (20050607)]/ unstable contrib main
deb cdrom:[Debian GNU/Linux 3.1 r0a _Sarge_ - Official i386 Binary-4 (20050607)]/ unstable contrib main
deb cdrom:[Debian GNU/Linux 3.1 r0a _Sarge_ - Official i386 Binary-3 (20050607)]/ unstable contrib main
deb cdrom:[Debian GNU/Linux 3.1 r0a _Sarge_ - Official i386 Binary-2 (20050607)]/ unstable contrib main
Thanks for that. But I also had another issue. Under 2.6, I can't surf via my wired NIC. So I can't download the necessary files. Oddly, I can still surf under 2.4. I posted the following in the Newbie forum, perhaps you can shed some light on what I think is a driver problem.
I looked at the boot record for both versions. This is a portion from 2.6.
Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Found IRQ 11 for device 0000:02:0b.0
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
tulip0: Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) block.
tulip0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.tulip0: Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) block.
eth1: Digital DS21143 Tulip rev 48 at 0xd880, 00:00:F8:04:F3:1D, IRQ 11.
gameport: pci0000:02:0c.1 speed 1125 kHz
Real Time Clock Driver v1.12
input: PC Speaker
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
inserting floppy driver for 2.6.8-2-386
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
NET: Registered protocol family 10
Disabled Privacy Extensions on device c02cc960(lo)
IPv6 over IPv4 tunneling driver
This is from 2.4
Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
PCI: Found IRQ 11 for device 02:0b.0
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block .
tulip0: Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) b lock.
tulip0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
tulip0: Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) bl ock.
eth0: Digital DS21143 Tulip rev 48 at 0xd880, 00:00:F8:04:F3:1D, IRQ 11.
uhci.c: USB Universal Host Controller Interface driver v1.1
ich2rom: firmware access control, I can't enable writes
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x1001
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x1001
i810_rng hardware driver 0.9.8 loaded
hw_random: misc device register failed
usb.c: registered new driver usblp
printer.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04A9 pid 0x107F
printer.c: v0.13: USB Printer Device Class driver
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
I notice from the 2.6 version that the Tulip driver is differnet. Is there a way I can force 2.6 to use the Tulip driver version 0.9.15-pre12?
I don't know about your NIC problem. That kind of thing is beyond my knowlege.
You should still be able to download and install while under 2.4, just boot into 2.6 after you've downloaded and installed everything and contine the guide from there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.