On Wednesday 27 April 2005 13:04, you wrote:
> Valur Olafsson wrote:
> >Hello all,
> >Before going into the problem at hand let me say that my desktop computer
> > was working as it should running SUSE 9.2, which was installed on the
> > machine before I upgraded to SUSE 9.3.
> >Now to the problem. As the title indicates I have been experiencing
> > lockups after upgrading my AMD64 desktop machine to 64-bit SUSE 9.3.
> > This all started when I wanted to configure my USB Linksys wireless card
> > (WUSB11 v2.8) on my desktop. I needed to configure it to access the
> > internet. So, like I did when I installed SUSE 9.2 in the past, I
> > installed the wireless-tools and atmel-firmware rpms, and plugged the
> > WUSB11 into a USB port on my desktop. Using 'dmesg' I saw that the atmel
> > firmware got uploaded to the WUSB11. So the system recognized the WUSB11
> > as it had done when I was running 9.2. Then I went into the network
> > module in Yast2 and setup the wireless connection. After that I needed to
> > unplug and plug the WUSB11 to get it to start to connect to my router,
> > but as it was about the get an IP from my router the computer froze.
> >At first I did not know what the problem was, so I tried to install
> > different versions of the atmel-firmware rpm, both the one that came with
> > 9.2 (and had worked previously) and the most recent one from the homepage
> > of the atmel-firmware project. Still the computer froze when the WUSB11
> > was about to get an IP from my router. Next I thought that maybe the
> > dhcp client on SUSE 9.3 was to blame so I hardwired a particular IP to
> > WUSB11 when setting up the connection in the network module in Yast2 to
> > bypass it. This did the trick, I was finally able to get online, without
> > the machine locking up. This is currently the only way I know how to get
> > the computer online using the WUSB11.
> >This however was to be a short victory, since about a half an hour after
> >getting online for the first time, while surfing the net, the computer
> > locked up again. This time, I was not doing anything specific, just
> > browsing the web through the wireless connection. I thought that maybe
> > this was a one off thing, but this has happened multiple times after that
> > incident.
> >As I said in the first paragraph, everything was working well when running
> >SUSE 9.2 on the same hardware and using the same WUSB11 device to access
> > the internet. Also, the machine is a dual boot machine, and everything
> > is working fine in windows.
> >So what would be my next steps in debugging this problem. Currently, I
> > have no idea what is causing the lockups, or why even the dhcp should be
> > causing lockups when I'm not bypassing that by hardwiring the IP. Any
> > suggestions to logs or something of that sort that I should be looking at
> > are welcome, 'cause I sure as hell don't know what should be my next
> > steps.
> >Valur Olafsson
> I had even worse problems with a Belkin F5D6050 usb adapter. The
> adapter was recognised as "wlan0" device. However, whenever I tried to
> connect to the wirless network my entire system would freeze, forcing me
> to hard boot the PC. My solution was to delete the wireless drivers
> provided by SuSE located in the /lib/modules directory and to compile
> the drivers from source.
> My suggestion would be that you try this approach, if you can find the
> source code for the the drivers.
Are you talking about the source that comes when you install the km_wlan rpm
that comes with suse 9.3. If so, then that is just what I did, that is, I
deleted the wireless drivers in /lib/modules and compiled the drivers from
source that came from the km_wlan rpm. Did you maybe find some other source
for the drivers that worked for you? I ask, because I believe that our USB
adapters have the same atmel chipset. My adapter uses the at76c503
(at76c505_rfmd2958 to be more specific) kernel module. Anyway, after the
recompile, I still need to hardwire the IP number for the adapter when I am
setting it up in the network module in Yast2. But, so far, I've had no
lockups and thus no hard reboots needed to fix that.
Thanks for all the help,