Find the answer to your Linux question:
Results 1 to 3 of 3
Hey. A while back I had problems trying to get my Netgear MA101 adapter to work on Mandrake 10.1 Community. I've run into a couple problems once more, but this ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Newbie
    Join Date
    Nov 2004
    Location
    New York
    Posts
    150

    at76c503 driver not compiling


    Hey. A while back I had problems trying to get my Netgear MA101 adapter to work on Mandrake 10.1 Community. I've run into a couple problems once more, but this time I think I have a much better handle on the situation.


    Due to my excessive stupidity, I managed to fubar my mandrake system pretty badly (yes yes, I know, the distro name has changed, but I haven't upgraded yet). Before I wipe the partitions and start fresh, I've created a sort of test partition to try reinstalling the OS on to, just to make sure I know what I'm in for and remember how to set up everything. This was sort of a cruddy patch job, a quick testing of the water before I nuke most of my drive.

    Er, but that's not the problem at hand. I've downloaded the at76c503 berlios driver, which I used in the past, as well as the proper firmware. However, when I type "make" in the driver directory, I get the following:

    Code:
    [root@localhost at76c503a]# make
    mkdir -p .tmp_versions
    cp /lib/modules/2.6.8.1-10mdk/build/.tmp_versions/*.mod /root/drivers/at76c503a/.tmp_versions
    cp: cannot stat `/lib/modules/2.6.8.1-10mdk/build/.tmp_versions/*.mod': No such file or directory
    make: [modules] Error 1 (ignored)
    make -C /lib/modules/2.6.8.1-10mdk/build SUBDIRS=/root/drivers/at76c503a MODVERDIR=/root/drivers/at76c503a/.tmp_versions \
    EXTRA_CFLAGS=" -DCOMPILE_FIRMWARE_INTO_DRIVER" modules
    make[1]: Entering directory `/usr/src/linux-2.6.8.1-10mdk'
      Building modules, stage 2.
      MODPOST
    make[1]: Leaving directory `/usr/src/linux-2.6.8.1-10mdk'
    This is after I installed the kernel header package. Sure enough, the directory .tmp_versions does not exist in the header directory, and I don't really know what it's looking for, or if that's even the unrecoverable error that causes make to stop after 10 lines.

    Looking at the last thread I started here, I decided to restart and see if anything clicked into place. Wlan0 appeared in iwconfig and ifconfig -a, but something's not quite right. The firmware loader atmel_fwl doesn't recognize wlan0 as an atmel device, and ifup wlan0 fails.

    A chunk of my /var/log/syslog:
    Code:
    ay 14 12:21:51 localhost kernel: /root/drivers/at76c503a/at76_usbdfu.c: USB Device Firmware Upgrade (DFU) handler v0.12beta22-static loading
    May 14 12:21:51 localhost kernel: /root/drivers/at76c503a/at76c503.c: Generic Atmel at76c503/at76c505 routines v0.12beta22-static
    May 14 12:21:51 localhost kernel: /root/drivers/at76c503a/at76c503-fw_skel.c: Atmel at76c503 (RFMD) Wireless LAN Driver v0.12beta22-static loading
    May 14 12:21:51 localhost kernel: /root/drivers/at76c503a/at76c503-fw_skel.c: using compiled-in firmware
    May 14 12:21:51 localhost kernel: usbcore: registered new driver at76c503-rfmd
    May 14 12:21:53 localhost kernel: usb 3-2: reset full speed USB device using address 2
    May 14 12:21:53 localhost kernel: usb 3-2: device firmware changed
    May 14 12:21:53 localhost kernel: usb 3-2: USB disconnect, address 2
    May 14 12:21:53 localhost kernel: /root/drivers/at76c503a/at76c503-fw_skel.c: wlan%%d disconnecting
    May 14 12:21:53 localhost kernel: /root/drivers/at76c503a/at76c503-fw_skel.c: at76c503-rfmd disconnected
    May 14 12:21:53 localhost kernel: usb 3-2: new full speed USB device using address 3
    May 14 12:21:53 localhost kernel: /root/drivers/at76c503a/at76c503-fw_skel.c: using compiled-in firmware
    May 14 12:21:54 localhost kernel: /root/drivers/at76c503a/at76c503.c: $Id: at76c503.c,v 1.72 2004/10/19 20:45:25 jal2 Exp $ compiled Dec 27 2004 01:13:07
    May 14 12:21:54 localhost kernel: /root/drivers/at76c503a/at76c503.c: firmware version 1.101.2 #84 (fcs_len 4)
    May 14 12:21:54 localhost kernel: /root/drivers/at76c503a/at76c503.c: device's MAC 00:09:5b:3b:e0:3c, regulatory domain FCC (U.S) (id 16)
    May 14 12:21:54 localhost kernel: /root/drivers/at76c503a/at76c503.c: registered wlan0
    So I'm guessing that the driver's the problem and not the firmware? I'm never quite sure what to make of logs, but I've heard that "registered wlan0" is a good sign.


    [edit] I guess I should state the error from when I tried ifup wlan0:
    Code:
    /sbin/ifup: configuration for wlan0 not found.
    Usage&#58; ifup <device name>
    \"Nifty News Fifty: When news breaks, we give you the pieces.\" - Sluggy Freelance

  2. #2
    Linux Newbie
    Join Date
    Nov 2004
    Location
    New York
    Posts
    150
    Ok, here's an update of what I'm dealing with. I recompiled the driver and replaced the firmware on both my cruddy new mandrake installation and my screwed-up old one, and then compared the output of both. They look exactly the same, so I don't think either the firmware or the driver is the problem. However, I get an extra syslog message on the installation that it doesn't work with:

    Code:
    net.agent&#91;4475&#93;&#58; how do I bring up interfaces on this distro?
    net.agent&#91;4475&#93;&#58; add event not handled  &#91;i&#93;&#40;this one may be irrelevant&#41;&#91;/i&#93;
    Further inspection revealed that /etc/hotplug/net.agent displays that message when its call to ifup does not succeed. The real question then, is what causes this:
    Code:
    /sbin/ifup&#58; configuration for wlan0 not found.
    Usage&#58; ifup <device name>
    Here's where my limited knowledge of bash script syntax prevents me from exploring the problem deeper. I have no idea what this configuration thing is, or why I have not run into this issue when I set up my wireless adapter for the first time. Can anyone shed some light on the situation?
    \"Nifty News Fifty: When news breaks, we give you the pieces.\" - Sluggy Freelance

  3. #3
    Linux Newbie
    Join Date
    Nov 2004
    Location
    New York
    Posts
    150
    Holy <Insert phrase of profanity or religious swear that will not breach forum standards>!!

    I copied over from my old installation /etc/sysconfig/network-scripts/ifcfg-wlan0 over to my new installation and it worked like a charm! I can't believe that was all it took. Well, now I'm happy; I can proceed with my repartitioning plans, confident that I can reproduce a working mandrake system.

    Does anyone happen to know why that file wasn't created automatically, or what utility is responsible for managing it? If not, thanks for bearing with me this long anyway.


    [edit] Interesting.. After making this change, I was unable to connect to the internet through eth0, my temporary hard link, yet I could use it to ping the local network. wlan0 allowed me to do both. Probably a fluke.
    \"Nifty News Fifty: When news breaks, we give you the pieces.\" - Sluggy Freelance

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •