RE: Belkin F5D7000 and Red Hat 9 [eid-20040531-c48]

Thanks. That got things working...almost. Driverloader seems to have
loaded fine. I completed the configuration with the web interface. My
wireless pci card is recognized. Dldrconfig lists valid info and my
license status is "OK". My wireless AP is listed under iwlist scan.
(Sorry if this information is not exact. I still don't have an internet
connection from Linux so I'm doing this from memory.) *However*, I still
can't access anything on my network. The wireless device is not listed
under network devices (using neat). I've tried to add a new wireless
connection but my adaptor isn't listed and there's no way to specify
wlan0 (just eth0, eth1, etc.) (I don't know that that's important.) (I
have an Ethernet card in another pci slot. It shows as eth0. Don't know
if this is important.)

So, what do I do now? Should this wireless device be listed as a network
device? I assume so. How do I configure it? 

Thanks,

Dave

-----Original Message-----
From: Linuxant support (Jonathan) [mailto:support <at> linuxant.com] 
Sent: Monday, May 31, 2004 2:06 PM
To: dave <at> electricseaturtle.com
Subject: Re: [driverloader] Belkin F5D7000 and Red Hat 9
[eid-20040531-c48]

Hi,

you obtain many unresolved symbols while inserting the DriverLoader

Unable to associate, using Intel 2200BG

Hello,

driverloader seems to find the device just fine, and defines it as
eth1.

However, when trying to set the access point, I get an error, and I
hope someone can help.

wpa_supplicant says it's trying to associate with my AP, and prints
the correct BSSID, SSID, and frequency.  Then it outputs:

 ioctl[SIOCSIWAP]: Input/output error

And this shows up in syslog:

  driverloader: ndisSetInformation: 802_11_BSSID st=FAILURE W=0 N=0

I also get a similar error when attempting iwconfig eth1 ap <mac
address>:

   SET failed on device eth1 ; Input/output error.

(If I turn off the encryption security at the AP, I still get the
same error).

I'm using:
   generic kernel 2.4.25 with wireless extensions enabled.
   WAP: Dell TrueMobile 2300.
   chipset: Intel 2200BG
   driverloader 1.71

Re: Unable to associate, using Intel 2200BG

Hi,

please try to use DriverLoader without any kind of encryption (WEP, WPA) and 
try again. You could also try with different versions of the Windows XP 
driver to see if there is a difference.

If you require more assistance, please send at support <at> linuxant.com the output 
of 'dumpdiag'. Type the following in a root shell:

---
dldrconfig --dumpdiag
---

Just send us the generated file located in /tmp ('driverloaderdiag.txt').
It'll help us solve the problem.

Thanks,

Jonathan
Technical specialist / Linuxant
www.linuxant.com
support <at> linuxant.com

On Wednesday 02 June 2004 06:26, Byron Darrah wrote:
> Hello,
>
> driverloader seems to find the device just fine, and defines it as
> eth1.
>
> However, when trying to set the access point, I get an error, and I

an idea to resolve the DHCP problem

hello everybody
i've resolved the DHCP problem on my laptop (like lots of people using
driverloader, static IPs are working well but DHCP client couldn't receive an IP)

so, i've modified the ifup-wireless script on my mdk 9.2 (i think many distros
have this script). now, when U plug the card, 50 to 60 later U have an IP
delivered by the DHCP server.

I 've just added 6 lines at the end of the script

first i force a static ip on the card (like 192.168.0.Z)
second i ping an ip for 40 times in the range of the card (like 192.168.0.230)
(the IP don't have to exist, it must be just in the same subnet)
after i put a ifconfig thedevice down

i put a ifconfig $DEVICE $IPADDR $NETMASK (parameters from the ifcfg-ethX file
in case of an static IP config)

and finally a ifconfig $DEVICE up
(the dhclient command will be execute automatically after)

with this script both static and dhcp IPs are working.

an example of ifcfg-ethx config file (i had a parameter SECUMODE for encryption
mode, this parameter is used by the ifup-wireless script)

DEVICE=eth1
ONBOOT=yes
MII_NOT_SUPPORTED=yes

Re: Unable to associate, using Intel 2200BG

On Wednesday 02 June 2004 08:30, Linuxant support (Jonathan) wrote:

> please try to use DriverLoader without any kind of encryption (WEP, WPA)
> and try again. You could also try with different versions of the Windows XP
> driver to see if there is a difference.

Okay, I tried it again.  Same result.  "Input/output error" when I try to 
associate with an AP.  All encryption disabled as requested.

> If you require more assistance, please send at support <at> linuxant.com the
> output of 'dumpdiag'. Type the following in a root shell:
>
> ---
> dldrconfig --dumpdiag
> ---

File attached.  Hope you can help.

Thanks.

+ dldrstop

+ modprobe -v driverloader
/sbin/insmod /lib/modules/2.4.25/misc/driverloader.o
Using /lib/modules/2.4.25/misc/driverloader.o
Symbol version prefix ''
Warning: loading /lib/modules/2.4.25/misc/driverloader.o will taint the kernel: non-GPL license - see LICENSE file; Copyright (c)2003-2004 Linuxant inc.

Re: Belkin F5D7000 and Red Hat 9 [eid-20040531-c48]

Woo-Hoo!! I'm connected! This is my first email sent from Linux! Your
final suggestion to change the line in ifcfg-wlan0 did the trick. It
seems pretty cool that I'm able to use a state of the art periferal
(Belkin F5D7000 wireless 802.11g) with Linux. Thanks to driverloader!
Jonathan you've been great help. Thanks! I'm going to give this a few
days to check for stability and then you'll most certainly receive my
$19.95.

For reference here's the contents of
/etc/sysconfig/network-scripts/ifcfg-wlan0:

# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
USERCTL=no
PEERDNS=yes
GATEWAY=
TYPE=Wireless
DEVICE=wlan0
HWADDR=
BOOTPROTO=dhcp
NETMASK=
ONBOOT=yes
DHCP_HOSTNAME=
IPADDR=
NAME=
DOMAIN=
ESSID=belkin54g
CHANNEL=11
MODE=Auto
KEY=1111111111

Re: Unable to associate, using Intel 2200BG

Hi,

we can see the following warning message in the output of the 'iwconfig' 
command :

---
Warning: Driver for device eth1 has been compiled with version 16
of Wireless Extension, while this program is using version 15.
Some things may be broken...
---

Please try to upgrade your 'wireless-tools' package and try again. If it 
doesn't fix the problem, we can also see these messages in your 'dmesg' :

---
driverloader: stack=8192/1448/0
dldr_thread: 1623 stack overflow
---

It seems that you are using a custom kernel and the 'task_struct' on your 
kernel is rather large (1448 bytes). Since the 'task_struct' takes a large 
amount of sthe stack and that the Intel Centrino Windows driver is known to 
take a lot of stack space, the problem might be a stack overflow problem and 
the second error message seems to point in this direction.

If you have compiled your kernel with additional patches, please try to 
recompile your kernel without these patches. If you recompile your kernel, 
please also recompile the DriverLoader module with the 'dldrconfig --kernel' 
command in a root shell.

/etc/init.d/driverloader

Hello everyone!

I hope a developer from Linuxant is reading this mailing list. When 
"dldrconfig" is run it overwrites the file /etc/init.d/driverloader even 
if such a file exists! This behavior is inadequate. I lose my self 
written init script for Gentoo Linux every time I run "dldrconfig" 

I am using DriverLoader 1.71. By the way, I am currently writing a 
DriverLoader ebuild for Gentoo Linux. I will let you know when it's done.

Re: /etc/init.d/driverloader

Hi,

for the '/etc/init.d/driverloader' issue, we could implement a check in the 
script that prevents that the file gets overwritten if the user did 
modifications to the file. I have added it to my 'TODO' list.

In the meantime, you could instead modify the file 'scripts/rcdldr.in' in the 
DriverLoader package and put your custom init script there and then reinstall 
DriverLoader.

You could also edit the shell script '/usr/sbin/dldrconfig' and remove the 
line which modify the '/etc/init.d/driverloader' file.

Thanks your for your work on a ebuild. This will make DriverLoader easier to 
install for Gentoo users. When your work is done, you can post the ebuild on 
this mailing list so the whole DriverLoader community will be able to enjoy 
your work.

Regards,

Jonathan
Technical specialist / Linuxant
www.linuxant.com
support <at> linuxant.com

On Friday 04 June 2004 10:09, Sven Jacobs wrote:
> Hello everyone!
>
> I hope a developer from Linuxant is reading this mailing list. When
> "dldrconfig" is run it overwrites the file /etc/init.d/driverloader even

Re: /etc/init.d/driverloader

An ebuild for driverloader would be greatly
appreciated! Could you please also add an optional
support for WPA (wpa_supplicant) as a USE flag?

Thanks!

Ben

--- Sven Jacobs <sven.jacobs <at> web.de> wrote:
> Hello everyone!
> 
> I hope a developer from Linuxant is reading this
> mailing list. When 
> "dldrconfig" is run it overwrites the file
> /etc/init.d/driverloader even 
> if such a file exists! This behavior is inadequate.
> I lose my self 
> written init script for Gentoo Linux every time I
> run "dldrconfig" 
> 
> I am using DriverLoader 1.71. By the way, I am
> currently writing a 
> DriverLoader ebuild for Gentoo Linux. I will let you
> know when it's done.
> _______________________________________________
> driverloader mailing list
> driverloader <at> lists.linuxant.com
>
https://www.linuxant.com/mailman/listinfo/driverloader