Overclock.net banner

1 - 17 of 17 Posts

·
Premium Member
Joined
·
1,730 Posts
Discussion Starter · #1 ·
Could not make my old laptop take Mandrake, so I dual booted my P3 with Mandrake 10.0. One of the best things I have done.

Anyway, as part of the install, I wanted to set up my wireless card, but Mandrake does not have the proper driver. I have the driver now, have read the installation instructions and I have to say that I am a tad confused. So, is there a way to automate the detection of hardware/selection of driver in Linux?
 

·
Premium Member
Joined
·
1,730 Posts
Discussion Starter · #2 ·
This are the parameters I need o change to make my WiFi card run:

Kernel version (it is 2.6.3-7)
IO Flags: no idea
Endian: no idea
OP_Mode: no idea
DRV_Flags: no idea

I was reading about this particular chipset (Realtek 8180), and people is having luck using ndiswrapper. I an having trouble making it go too.

This is a Mandrake 10.0 installation
 

·
Premium Member
Joined
·
1,730 Posts
Discussion Starter · #4 ·
Quote:

Originally Posted by Xaimus
What exactly were the installation instructions?
RTL8180 Linux Driver version 1.4

- Support Client mode for either infrastructure or adhoc mode
- Support AP mode

RTL8180 Linux Driver version 1.5

- Turn on Dynamic Carrier Sense Function.

================================================== =============================================
< Component >
The driver is composed of several parts:
(1)source code
driver module initialization and interface between rtl8180 driver and system call.
r8180_pci_init.c driver module initialization and register/unregister network device
r8180_pci_init.h include file
r8180_if.c interface between rtl8180 driver and system call
r8180_if.h include file
r8180_type.h type definition for rtl8180 driver
r8180_export.h exported function name from rtl8180 driver

(2)object code
rtl8180 driver
priv_part.o rtl8180 driver object code

(3)Default driver
rtl8180_24x.o default driver module compiled in kernel 2.4.18.

(4)Makefile
PLEASE SPECIFY INCLUDEPATH CORRECTLY ACCORDING TO YOUR LINUX ENVIRONMENT.
FOR EXAMPLE, " INCLUDEPATH=-I /usr/src/linux-2.4.18-3/include/ " in RedHat7.3.
FOR EXAMPLE, " INCLUDEPATH=-I /usr/src/linux-2.4.18-14/include/ " in RedHat8.0.

(5)wlanup/wlandown
simple script file to activate/shut_down wireless lan.

< Installation >
Please try to load linux_24x.o first by "insmod -f rtl8180_24x.o".
If it doesn't work, you are suggested to compile loadable driver module following the steps as:

(0)Make sure the C-compile version. Run "gcc -v".
If gcc version is 2.xx, use release driver RTL8180_24x_RH73.zip.
If gcc version is 3.xx, use release driver RTL8180_24x_RH90.zip.

(1)Modify macros in Makefile.
KERNELRELEASE - represent kernel release version
IO_FLAGS - pci I/O space mapping
ENDIAN_FLAGS - big/little endian
OP_MODE_FLAGS - Operation on either AP or Client mode
DRV_FLAGS - Driver debugging messge ...etc.

(2)Check pci module initialization and system call interfaces in the provided source code,
r8180_pci_init.c ....etc.

(3)Run 'make' to generate new driver module.

(4)Run 'make install' to install new driver module.

(5)Refer to < Set wireless lan MIBs > and modify script files,
wlanup/wlandown, to set Wireless LAN specific parameters.
Run wlanup/wlandown to activate/shut_down wireless lan.
Usage:
./wlanup {ap|infra|adhoc}
./wlandown
Note:
- "./wlanup ap" works if OP_MODE_FLAGS is assigned RTL_ACT_AS_AP in Makefile.
- "./wlanup {infra|adhoc}" works if OP_MODE_FLAGS is assigned RTL_ACT_AS_AP
in Makefile.

< Set wireless lan MIBs >
This driver uses Wireless Extension as an interface allowing you to set
Wireless LAN specific parameters.
Current driver supports "iwpriv", manipulate driver private ioctls, to set MIBs.

iwpriv wlan0 wlan_para [parameters]=[val]
where

parameter explaination [parameters] [val] constraints
----------------------- ------------- ------------------
Set beacon interval bcnint {20~1000} msec
Set channel number channel {1~14}
Set basic rates basicrates {bit0 = 1Mbps, bit1 = 2Mbps, bit2 = 5.5Mbps, bit3 = 11 Mbps}
Set operational rates oprates {bit0 = 1Mbps, bit1 = 2Mbps, bit2 = 5.5Mbps, bit3 = 11 Mbps}
Set authentication type authtype {opensystem, sharedkey, both<only AP mode>}
Set desired ssid to scan ssid2scan {0~z, less than 32 characters}
Set RTS threshold rtsthres {256~2304}
Set fragment threshold fragthres {256~2304}
Set preamble mode preamble {short,long,auto}
Set network type networktype {infra,adhoc,auto}
Set WEP mode wepmode {off,wep40,wep104}
Set WEP default key ID wepdkeyid {0~3}
Set 1st WEP40 key value wepkey40_1 {0~f, total 10 characters}
Set 2st WEP40 key value wepkey40_2 {0~f, total 10 characters}
Set 3st WEP40 key value wepkey40_3 {0~f, total 10 characters}
Set 4st WEP40 key value wepkey40_4 {0~f, total 10 characters}
Set 1st WEP104 key value wepkey104_1 {0~f, total 26 characters}
Set 2st WEP104 key value wepkey104_2 {0~f, total 26 characters}
Set 3st WEP104 key value wepkey104_3 {0~f, total 26 characters}
Set 4st WEP104 key value wepkey104_4 {0~f, total 26 characters}
Set AP ssid ssid {0~z, less than 32 characters}
Set Mac address macaddr {0~f, total 6 characters}
Set DTIM period dtimperiod {1~255}
Set hidden AP hiddenAP {true,false}
Set mac filter policy addmac {0~f, total 6 characters}
Delete mac filter policy delmac {0~f, total 6 characters}
Set deny mac filter policy denymacaddr {0~f, total 6 characters}
Delete deny mac filter deldenymacaddr {0~f, total 6 characters}
Set sta expired time expired_time {1~100000} *10 msec
Set rate adaptive autorate {true,false}
Print help message help

For example:

iwpriv wlan0 wlan_para bcnint=100
iwpriv wlan0 wlan_para channel=1
iwpriv wlan0 wlan_para basicrates=0xf
iwpriv wlan0 wlan_para oprates=0xf
iwpriv wlan0 wlan_para authtype=opensystem
iwpriv wlan0 wlan_para ssid2scan=testssid
iwpriv wlan0 wlan_para fragthres=512
iwpriv wlan0 wlan_para preamble=long
iwpriv wlan0 wlan_para wepmode=off
iwpriv wlan0 wlan_para wepdkeyid=0
iwpriv wlan0 wlan_para wepkey40_1=012
 

·
Premium Member
Joined
·
1,730 Posts
Discussion Starter · #6 ·
Quote:


Originally Posted by Xaimus

Hm. Searching around on the INTARWEB doesn't bring much hope--it looks like the driver will only work on a 2.4.x kernel. You'll have to use a windows driver and the NDISWrapper.

Here's an installation guide for the NDISWrapper:
http://ndiswrapper.sourceforge.net/p...p/Installation

I downloaded ndiswrapper form sourceforge and the instructions does not match the software. If the file is .run, there is nothing to compile. Double click on it, and opens the browser to connect to the freaking net. Crap, I am trying to get my nic card going to I can freaking connect!!!!


Does it sounds like I am a little frustrated?
 

·
Premium Member
Joined
·
573 Posts
Quote:

Originally Posted by slow'puter
I downloaded ndiswrapper form sourceforge and the instructions does not match the software. If the file is .run, there is nothing to compile. Double click on it, and opens the browser to connect to the freaking net.
Uhm. You need to execute that from the command line. As MrSmiley said:

[email protected]~# chmod +x blahblah.run
[email protected]~# ./blahblah.run
 

·
Premium Member
Joined
·
1,730 Posts
Discussion Starter · #9 ·
I'm running KDE, so I am doing this the easy way.
chmod ,eh? I'll open the console and do it that way. Tomorrow. I want to sleep now.
 

·
Premium Member
Joined
·
1,730 Posts
Discussion Starter · #10 ·
Quote:

Originally Posted by slow'puter
I downloaded ndiswrapper form sourceforge and the instructions does not match the software. If the file is .run, there is nothing to compile. Double click on it, and opens the browser to connect to the freaking net. Crap, I am trying to get my nic card going to I can freaking connect!!!!


Does it sounds like I am a little frustrated?

My mistake. Trying to use the Linux driver, I downloaded Linuxant. That is the one with the .run. NDISwrapper is a tar file, already expanded to the hda1.

Now it is asking me for the kernel source.. Crap, I am a frigging noob... where do I find it?
 

·
Premium Member
Joined
·
1,730 Posts
Discussion Starter · #13 ·
I installed the kernel source, ndiswrapper works, the driver module is loaded (as verified by dmesg), but when I use iwconfig, it says that there is no such device.

What is going on? This is the same driver I use when in Windows. I am about to say about Mandrake the same thing I said about Ubuntu...
 

·
Premium Member
Joined
·
1,730 Posts
Discussion Starter · #15 ·
You will note that I installed the driver (rtl8180.inf and .sys) using Linuxant, not ndiswrapper.

Here is the PCI device log from dmesg:
 

·
Premium Member
Joined
·
573 Posts
Hm. Can ifconfig see and manipulate the device?

Also, does the same weirdness occur if the NDISwrapper is used instead of Linuxant?
 

·
Premium Member
Joined
·
1,730 Posts
Discussion Starter · #17 ·
Quote:


Originally Posted by Xaimus

Hm. Can ifconfig see and manipulate the device?

Also, does the same weirdness occur if the NDISwrapper is used instead of Linuxant?


Yes it does. I can enter all parameters, but they don't stick.

NDISwrapper is another matter. when I tried to modprob, it just would not work, yet the driver was installed. I have been thinking, since I fudged around a lot with ndiswrapper before I went to Linuxant, that I might reinstall Mandrake and try again.
 
1 - 17 of 17 Posts
Top