LinuxQuestions.org
Help answer threads with 0 replies.
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 11-06-2003, 08:45 PM   #376
witchdoctor
LQ Newbie
 
Registered: Nov 2003
Posts: 1

Rep: Reputation: 0

My Turn. :-)

I got done reading this monster thread last night. Tried the new drivers today and same problems.

setup:
2.4.20-gentoo-r6
wireless_tools (downloaded tues from Jean's)
Said it compiled as v16 instead of 19 cause the Kernel support was old.
Card: DLINK-DWL-520D PCI not PCMCIA (520 Rev D uses rtl8180L)
rtl8180 Driver V14 (downloaded today compiled for non-AP mode)

I am trying to run infrastructure mode WEP off.

I see a few main things in my output that I cannot understand or account for:
(hope I didn't just miss them in one of the messages in this thread)

1) Right after driver initialization I get a bunch of messages:
BB Reg Write Fails! offset[...]
Any clues what this means? See support docs below...

2) I also get a bunch of the following:
TX NORMAL Descriptor unavailable!
Is this one just a way of the driver saying it's searching and can't find anything?

3) Can someone verify that the driver looks to be loaded correctly and I just need to get the commands right? Or does question 2) (or anything) suggest a deeper problem.

See supporting docs below...

Thanks,
Doc




SUPPORTING DOCS


/proc/rtl8180/status
==============
---------------------------------------
Driver status
---------------------------------------

rtl8180_pci_driver version 1.4 loaded.
The Network is configured as Infrastructure mode.
MacAddr = 00:11:22:33:44:55 #<-I changed output for security
ioaddr = 0xb000
irq = 10


---------------------------------------
Wireless Link status
---------------------------------------

Link Fail!

Channel number = 0
beacon period = 100
BSSID = 0x00 0x11 0x22 0x33 0x44 0x55 #<-Hmm this ones real what up with that?
SSID = aptest2
Capability = 0x00
AID = 0x00
Operational rates = <1><2><5.5><11>Mbps
Current TX operational rates = <1>Mbps

/var/log/messages (cleaned)
====================
kernel: ******** RTL8180 Wireless Lan Driver 2003-10-17 loaded********
kernel: RTL8180: 00:0b.0: region #0 IS a PIO resource!
kernel: RTL8180: request_region(0x0000b000,0x00000100) !
kernel: RTL8180: Turn on RTL_DDEBUG_OUTINFO
kernel: RTL8180: ------ Enable wlan driver ------
kernel: RTL8180 WLAN driver version 1.4
kernel: RTL8180: wireless LAN controller RTL8180 + philips RF.
kernel: RTL8180: PHILIPS_Config()
kernel: RTL8180: PHILIPS_Config() - Analog mode
kernel: RTL8180: BB Reg Write Fails! offset = 0x00, data = 0x98, ReadData = 0x91
kernel: RTL8180: BB Reg Write Fails! offset = 0x03, data = 0x38, ReadData = 0x91
kernel: RTL8180: BB Reg Write Fails! offset = 0x04, data = 0xe0, ReadData = 0x91
kernel: RTL8180: BB Reg Write Fails! offset = 0x05, data = 0x90, ReadData = 0x91
kernel: RTL8180: BB Reg Write Fails! offset = 0x06, data = 0x1a, ReadData = 0x91
kernel: RTL8180: BB Reg Write Fails! offset = 0x07, data = 0x64, ReadData = 0x91
kernel: RTL8180: BB Reg Write Fails! offset = 0x11, data = 0x80, ReadData = 0x91
kernel: RTL8180: BB Reg Write Fails! offset = 0x12, data = 0xc7, ReadData = 0x91
kernel: RTL8180: BB Reg Write Fails! offset = 0x13, data = 0x9b, ReadData = 0x91
kernel: RTL8180: BB Reg Write Fails! offset = 0x19, data = 0x00, ReadData = 0x91
kernel: RTL8180: BB Reg Write Fails! offset = 0x1a, data = 0xa0, ReadData = 0x91
kernel: RTL8180: Set dot11PrivacyInvoked = 0.
kernel: RTL8180: encryptmode = RTL_ENC_NONE
kernel: RTL8180: wepkeymode = WEP_MODE_OFF
kernel: RTL8180: TX NORMAL Descriptor unavailable!
last message repeated 534 times
last message repeated 1065 times
last message repeated 1066 times
last message repeated 1065 times
last message repeated 747 times
kernel: RTL8180: ------ Disable wlan driver ------
kernel: RTL8180: release_region(0x0000b000,0x00000100) !
kernel: RTL8180: wlan driver removed
kernel: ******** RTL8180 Wireless Lan Driver 2003-10-17 removed ********
 
Old 11-07-2003, 12:00 PM   #377
coolj478
LQ Newbie
 
Registered: Oct 2003
Distribution: Slackware 10
Posts: 11

Rep: Reputation: 0
help...

my kernel version is 2.4.22-10 on mandrake 9.2


i load the driver and when i lsmod it says "initializing"......i've heard of other people getting things to work on kernel version 2.4.20

how did you guys get around the problem of the driver being stuck at initialization
 
Old 11-10-2003, 02:46 PM   #378
wacek79
LQ Newbie
 
Registered: Oct 2003
Posts: 7

Rep: Reputation: 0
i tried kernel version 2.4.22 with no success, but kernel 2.4.21 work fine for me, the original redhat kernel didn't work, because it didn't assign an irq for the card, so, if you don't get an irq, it possibly won't work. try the kernel from www.kernel.org, i used the alan cox kernel, and the original one, both worked for me in version 2.4.21. before i tried the kernel, i had the same problem as WICHDOCTOR, but it solved itself, as i compiled the module with the new kernel! hope i could help somebody :-)
 
Old 11-10-2003, 03:28 PM   #379
nirvanaguy19
LQ Newbie
 
Registered: Nov 2003
Posts: 5

Rep: Reputation: 0
i cant seem to get dhcp working but otherwise it works cool
 
Old 11-10-2003, 06:20 PM   #380
ky0
LQ Newbie
 
Registered: Nov 2003
Posts: 1

Rep: Reputation: 0
I have read through this tread a number of times.

I downloaded the latest (and only) driver version from realtek's website, v1.4. I am running redhat 9 stock with a 2.4.20-8 kernel. I modified the makefile to put to the kernel share directory. When I run the make command I get this error:

storage size of 'rtl8180_pci_driver' isn't known
make: *** [r8180_pci_init.o] Error 1

and then it stops. I am running gcc 3.2.2 and make v 3.8. I do not know how to fix this.

Anyone out there running the same kernel version as I am want to email me thie compiled object file? That would be too cool. I think whats I get that I should be all set.

email: ky0@zerodev.net

Last edited by ky0; 11-10-2003 at 06:22 PM.
 
Old 11-12-2003, 04:53 AM   #381
dan2003
LQ Newbie
 
Registered: Nov 2003
Location: UK
Distribution: gentoo
Posts: 6

Rep: Reputation: 0
I have the MA521 with the rtl8180.

I gave up trying to build the module with 2.6 and installed 2.4.22 to see if i could get this thing to work.

I can load the module and eneable it and the results in /proc/rtl8180/status say link sucessful and has my ssid and ap mac address correctly.

The link light on the card blinks eratically rather than stayin go which is odd.

I cannot connect to anything via the card. i set up the card with

ifconfig wlan0 192.168.22.103 up

then set up routing

route del default

route add default gw 192.168.22.1 dev wlan0

then try to ping somthing. I cannot get any response from either my router or the AP itself (on 192.168.22.254)

Something appears to be wrong between the network interface and the driver. ifconfig reports ever increasing rx bytes but 0 tx bytes.

I had also seen some errors along the lines of tx error (can't remeber exactly) but recently have not seen the error.

I wonder if this is somethign to do with the kernel version and perhaps the renamed priv function / struct that ws mentioned earlier?

I have used the linuxant thing with the XP driver and proved that the setup works (although terribly unstable).

Any ideas what to try next?
 
Old 11-12-2003, 05:09 AM   #382
Cimmerian
Member
 
Registered: Sep 2003
Location: Trondheim, Norway
Distribution: Slackware10 + Dropline Gnome
Posts: 47

Rep: Reputation: 15
2.4.22 and newer seems not to be working, try an older kernel or use the driverloader. They are impressive at fixing bugs and increasing stability giving out releases quite frequently. At one point my laptop would freeze after running a patched 2.6.0-test9 for a while, then a couple of days later, new version and now it is running flawlessly.
 
Old 11-12-2003, 06:09 AM   #383
dan2003
LQ Newbie
 
Registered: Nov 2003
Location: UK
Distribution: gentoo
Posts: 6

Rep: Reputation: 0
Cheers for the advice.
I will have a go with an older kernel and if have success look to see what may have changed to cause the problem.
I read earlier in this thread that it needed to be earlier than 2.4.18 IIRC to not suffer from the change in naming of the priv function. Has anybody got it working in a later kernel? Maybe if people could post the latest kernel they have it working in we could try to locate where the difference is and alter the r8180_if.c file accordingly. Maybe even hack the symbol names in the priv_part if necasary but i think all relavant stuff is exposed.

RE: linuxant. Yes there have been many releases in the past week, but they have announced that the driver will not be supported byt he manufacturers and that we have to pay for it. As i have already payed for the card i refuse to do this and will instead if necasary buy an alternative card for which native kernel support exists.
 
Old 11-12-2003, 09:02 AM   #384
wacek79
LQ Newbie
 
Registered: Oct 2003
Posts: 7

Rep: Reputation: 0
the latest kernel working for me is 2.4.21 with acpi patch
 
Old 11-12-2003, 01:30 PM   #385
bostonben
Member
 
Registered: Jun 2003
Location: Boston
Distribution: Red Hat 7.1
Posts: 31

Rep: Reputation: 15
Quote:
Originally posted by ky0
I have read through this tread a number of times.

I downloaded the latest (and only) driver version from realtek's website, v1.4. I am running redhat 9 stock with a 2.4.20-8 kernel. I modified the makefile to put to the kernel share directory. When I run the make command I get this error:

storage size of 'rtl8180_pci_driver' isn't known
make: *** [r8180_pci_init.o] Error 1

and then it stops. I am running gcc 3.2.2 and make v 3.8. I do not know how to fix this.
This is the sort of error you get when compiling against the
stock "/usr/include" files in Red Hat. To compile this driver, you
need the kernel *sources*, usually found in "/usr/src/linux-<version>".
gcc will search "/usr/include" by default, so make sure the
"gcc" commands issued by "make" have "-I/usr/src/linux-<version>" (and
that it's spelled correctly, the directory is accessible, etc).

If you don't have such a directory, you're probably lacking the
kernel sources package:
$ rpm -q kernel-source
I don't know if they're part of a stock RH9 install, but you can easily
get the RPM from their web site.
 
Old 11-12-2003, 02:15 PM   #386
bostonben
Member
 
Registered: Jun 2003
Location: Boston
Distribution: Red Hat 7.1
Posts: 31

Rep: Reputation: 15
Quote:
Originally posted by dan2003

I read earlier in this thread that it needed to be earlier than 2.4.18 IIRC to not suffer from the change in naming of the priv function. Has anybody got it working in a later kernel? Maybe if people could post the latest kernel they have it working in we could try to locate where the difference is and alter the r8180_if.c file accordingly. Maybe even hack the symbol names in the priv_part if necasary but i think all relavant stuff is exposed.
WARNING: long, boring, not-particularly relevant, technical explanation follows.

It's not a symbol name issue, it's a position issue.

In the official 2.4.23-pre1 kernel, the relevant data structure looks
something like this (excerpted from include/linux/netdevice.h):

struct net_device
{
...

/* List of functions to handle Wireless Extensions (instead of ioctl).
* See <net/iw_handler.h> for details. Jean II */

struct iw_handler_def * wireless_handlers;

struct ethtool_ops *ethtool_ops;

...
void *priv; /* pointer to private data */
...
}

The Realtek driver relies on "priv" to carry around stuff specific to its operation.
It even sets it up in source we can read (r8180_if.c, around line 85).
But the C compiler doesn't care about the name of "priv", only about it's
position in the "net_device" structure:

- In the 2.4.23-pre1 kernel, as above, "priv" is 108 bytes from the start (if I'm counting correctly).

- In the 2.4.20 kernel version, "ethtool_ops" isn't there, so "priv" is 104 bytes from the start.

- In the 2.4.18 kernel version, "wireless_handlers" isn't there either, so "priv" is 100 bytes from the start.

So whichever kernel the "priv_part.o" file was compiled with, that's the position that
the field has to be in for the driver to work correctly. If your kernel puts it in a different
position, "priv_part.o" won't find it, and so the driver won't work.

And that's just one minor change to one structure! Even if you managed to fix
this somehow, you'd probably only run into the next incompatible change. This
is the problem with binary drivers under Linux (or with Linux's development
philosophies, depending on your point of view).

User-space programs (eg, email clients, web browsers, text editors, etc) don't face these issues as much because the user/kernel
interfaces are much less fluid than the internal kernel interfaces (and most user-space programs use things like glibc as an intermediary to the kernel anyway).
 
Old 11-12-2003, 02:17 PM   #387
dan2003
LQ Newbie
 
Registered: Nov 2003
Location: UK
Distribution: gentoo
Posts: 6

Rep: Reputation: 0
Well i built myself the gentoo-r8 kernel (2.4.20) and built the rtl8180 again and now i can actually get a few seconds of access over the link but it literally is a few seconds.. The link dies and often my AP has crashed (can't access via the built in webpage) . i assume some have had moreluck than this.
 
Old 11-12-2003, 02:19 PM   #388
dan2003
LQ Newbie
 
Registered: Nov 2003
Location: UK
Distribution: gentoo
Posts: 6

Rep: Reputation: 0
I'm gonna have a go with the redhat kernel

edit : first gonna try with prempt switched off in gentoo kernel

Last edited by dan2003; 11-12-2003 at 02:27 PM.
 
Old 11-12-2003, 02:32 PM   #389
dan2003
LQ Newbie
 
Registered: Nov 2003
Location: UK
Distribution: gentoo
Posts: 6

Rep: Reputation: 0
thanks for the details bostonben, Do you know what the offset should be? i.e. the offset for the kernel against which it was built (probably redhat)

I think we perhaps need to obtain the datasheet and start a driver of our own from scratch. I read several coments from freeBSD forums written by people saying they have received a datasheet from realtek and even some example source code.

Worth a shot i think.

Last edited by dan2003; 11-12-2003 at 02:37 PM.
 
Old 11-12-2003, 02:36 PM   #390
bostonben
Member
 
Registered: Jun 2003
Location: Boston
Distribution: Red Hat 7.1
Posts: 31

Rep: Reputation: 15
And I should also point out (just in case I've not been long-winded enough today)
that I'm not saying you need the *exact* same kernel as the driver. I myself
run RH 7.1 with an updated kernel from RH labelled "2.4.20-13.7", and I've been
able to use both the old Suse driver ("2.4.20-4GB") and the more recent RH9
drivers ("2.4.20-8").

I'm just trying to explain one particular kind of driver failure (ie, the failures I
get when I try to use any other driver versions) so people have some idea
what their options are when they see that failure.
 
  


Reply


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
Linksys WPC11 version 4 aover25 Linux - Wireless Networking 5 02-12-2006 11:01 PM
WPC11 version 3 chiatello Linux - Networking 0 10-28-2003 09:32 PM
Linksys WPC11 version 4 kronixx Linux - Networking 1 06-07-2003 10:25 PM
WPC11 Version 4 StarCat Linux - Networking 1 05-03-2003 12:13 PM
Linksys WPC11 Version 3 haqtiq Linux - Networking 3 01-15-2003 11:33 PM


All times are GMT -5. The time now is 05:31 AM.

Main Menu
Advertisement
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