Re: Help with ATMEL Wireless on SuSe 9.1 (Was: Help/Question SCM2662 (USB - atmel) wireless card on SuSe 9.1)

From: Diego Diaz (diegochely_at_noway.netzero)
Date: 07/19/04


Date: Sun, 18 Jul 2004 21:58:32 -0500

David,
    Many thanks for your reply. As of why the driver loads from my
directory, that was just my mistake. I couldn't get the file via CVS, so I
used the "snapshop" and got sloppy (was the 4th re-install) in 2 days.
Anyway, I sort of figured out that the driver was there. Along the 3
previous installs, I tried a few things. If I choose to upgrade the Kernel
from YOU the PC crashes completely and needed to re-install and I learned
the hard way.

I tried updating the firmware from YOU only and it detected the card, but
gave me the same problems. I then updates the driver from the Berlios site
and did not work. Now, the card seems to be detected properly, iwconf...
ives me a decent "signal", Mac address, access point address, etc. Seems to
me like the problem is the card associating with the network. Mandrake uses
the same driver (as per the /etc/modules.conf) and there it works. From SuSe
I always get the:

Jul 16 16:26:25 susewireless1 kernel: wlan0: no IPv6 routers present

for some reason I am still to figure out.

Will it make a difference if I install the firmware from thekelleys website
instead of the YOU version?

Thank you so much for your help. Any pointers will be greatly appreciated.

Diego J. Diaz
(if you want to send private message, please follow this link:
http://www.uiuc.edu/ricker/PH?domainUrl=http%3A%2F%2Fwww.uiuc.edu%2Fcgi-bin%2Fphcgi%2Fns.uiuc.edu&Query=diegod -
so I do not have to put my address here).

"David Haggett" <news-spam@haggett.demon.co.uk> wrote in message
news:pan.2004.07.18.14.20.37.490607@haggett.demon.co.uk...
> On Fri, 16 Jul 2004 16:52:30 -0500, Diego J. Diaz wrote:
> >
> Sorry, Diego, I think I must have missed your earlier posting, and could
> have saved you some effort.
>
> Suse 9.1 provides the Berlios driver, so you probably didn't need to go
> to the effort of downloading the latest (CVS) version from the berlios
> site. I'm a little confused as to why it seems to be loading the driver
> from your home directory, but I guess that's something to do with the way
> you installed it.
>
> Have you downloaded and installed the firmware files from
> http://thekelleys.org.uk/atmel/ ? The SuSE implementation needs external
> firmware to load the driver, and because of licencing concerns they don't
> provide it directly. It's available as an update through YOU or you can
> get an RPM direct from the site if you prefer (I did).
>
> Hope this helps.
> --
> David Haggett
> Linux user since 01/01/2003
> Email: david<at>haggett<dot>demon<dot>co<dot>uk
>



Relevant Pages

  • RE: AVStream INF files + Chkinf + Fastinst = Brain-ache!!
    ... Driver and each bus driver has a different mechanism for enumerating the ... TestCap installs itself on the ROOT Bus and therefore ... I ran Chkinf on the inf file and it gave ...
    (microsoft.public.development.device.drivers)
  • Re: pscript5 customization
    ... I downloaded your rleased code from cvs (which installs ok) but throws ... exceptions in a few places once i tried playing with it. ... To get some direction, checkout my driver, well it won't ...
    (microsoft.public.development.device.drivers)
  • Re: Clone a W2K server???
    ... If you want to do multiple installs with the same settings, but onto different hardware, you ... > Server I had a SCSI error. ... > driver on Bootup it gave me a "SCSI Port Start Entry ...
    (microsoft.public.win2000.setup_deployment)
  • Re: New version of iwi(4) - Call for testers [regression!]
    ... didn't experience this with the driver currently present in the tree; ... > properly; and it's really ready to boot a firmware ... iwiconfig is no longer needed to load firmware. ... The aim is to merge the changes in "my" driver to CVS modulo ...
    (freebsd-net)
  • RE: Windows update replaces incorrect audio driver...
    ... my audio hardware as "Via AC 97" and installed the correct driver. ... installs an incorrect driver. ...
    (microsoft.public.windowsupdate)