Recently clean installed 9.3 on my IBM r40e laptop (not upgrade).

Amongst other problems such as ACPI hanging the machine (which is not SuSE specific), Im having a very annoying problem with wireless support.

one thing to note is that I never had a problem in SuSE 9.2. Also, this is a orinoco wireless PCMCIA Card, using a lucent chipset AFAIK.

the problem is, when I try to connect to my wireless access point using either the Yast network module, Kinternet, netapplet or anything else (i read up about a command line tool, but have forgotten what that was) It just doesn't connect.

I did manage to get it to connect once using Kinternet, but it was more good luck than managment, and after a reboot it had gone again.

I also tried disabling onboard ethernet, and i remember changing a setting about it being user controlled to on and off with still no luck.

this is really quite frustrating because it worked fine under 9.2.

I would value any input anybody can have.

Can you be more specific on your issues? "it doesn't work" doesn't really help us help you.

Show config files and your own troubleshooting steps for starters...

yours truly,
randomx

Sorry for being unspecific. My problem is I can't provide config files as I don't know where they are. I'm pretty new to linux, so I've only ever used the GUI's available for things like this.

The problem is that When I specify an SSID and encryption key for the wireless AP I have at home, the PC doesn't make a connection to the wireless network (I'm looking at the net applet graph the says 0) and the internet doesn't work. IU've tried to set the above using Yast Network module, Netapplet, Kinternet adn the control panel in KDE.

If you could point me in the right direction on what config file you want a copy of, I'm happy to get it for you.

many thanks for replying

I have had similar problems with Suse 9.3 freezing up my laptop when I try to change wireless settings.

Also I have been able to connect and pull and IP address from my wireless router but I am unable to access the web. When I uninstall the ACPI it does not improve the situation.

I don't think this is specific to Suse. I have had the same problem with Mandrake and Fedora, and don't get me started on Ubuntu

Just installed 9.3 on a spare hard drive for a 770x thinkpad. Not real good at Suse yet as cut teeth on Slackware.

I think the problem you might be experiencing is that pcmcia cards work great with the 2.4 kernel but are a shot in the dark with the 2.6 kernel. [Suse experts was 9.2 a 2.4 kernel version?]

With Slackware and a 2.4 kernel, I can insert/remove/insert card and everthing is fine. With Slackware and 2.6 kernel the card has to be in at boot and don't even think about removing it. Don't have Suse drive in at the moment so can't/haven't tried removing and reinserting the DLink 650 card, but fully expect it to fail.

I did get Suse to work by manually configuring the 'other' shown by yast2. After it was configured at reboot says it found new hardware -- the DLink card. Told yast not to tell me again as this was probably the udev not recognizing the wlan device is the same as the Dlink eth0 device it is asking to configure.

This doesn't help fixing the problem and am to new to Suse of offer a solution.

Back on the Suse drive and please pass the crow. Yank the DLink card and ifconfig drops to just lo; replace and network is brought back up including automount directories from a server having NIS users under /home/users/'username'. Rather impressed for a while thought there was a problem but guess I just wasn't patient enough as return from tty2 to KDE/x on F7 is at first garbled but it does clear and return to normal.

While you are a newbie, you might want to try viewing /etc/sysconfig/network/ifcfg.template as it is well commented an might lead you in the right direction.

good luck

You know that there's a typo in the wpa-psk script as shipped with SuSE 9.3 ? So if you're using wpa-psk that could very well be the problem. I use a Linksys WRT54GS WiFi router and although I could scan it and despite I specified the right key in YaST, it could never make the connection with the router. No wonder, the label 'DRIVER' is mispelled in:

/etc/sysconfig/network/scripts/ifstatus-wireless-wpa

That's around line 180. Correct that, re-run YaST and there you (could) go.

The bad thing with this situation is that if you entirely rely on WiFI to get the updates you'll never get them using a secure WiFi connection. Unless the typo is fixed, the WiFi security has to be dropped to enable connection.

So, I hope this was the problem in your case because although it was not easy to find (I spent about a whole day on and off on that) it's easy to fix.

Cheers.

Either that or do as root:

/etc/rc.d/network restart

I agree that the kernel may be the cause for wireless problems. I was trying to use a wireless usb adapter at one point and that made things even worse.

I had problems getting the drivers for the Orinoco Gold compiled. Here's how to fix it:
http://www.digital-seven.net/index.p...d=33&Itemid=45