Click to See Complete Forum and Search --> : Suse 10.2(kde) detects my wireless but wont connect to the internet
Leon945
02-27-2007, 12:49 PM
Hi All..
I have a problem connecting to the internet..
I installed openSUSE 10.2, and it automatically detected my wireless card as a Ralink 2500..
My wireless' card model is this:
MSI PC54G2
When i try to connect to the internet (via network manager) it gets to 28% and it says "configuring device" or something like that.
And it stays there... it wont do anything else.. eventually it will ask for the wireless network name and passcode again.. but it never connects
can anyone help me with this?
thanks in advance.
enshum
02-27-2007, 02:56 PM
You may have to go to the control center and configure the card.
ed
Leon945
02-27-2007, 03:00 PM
Well... that was the first thing i did..
but there really isnt much to configure since suse detected it automatically...
all i did was add the ESSID and WEP code.. but that's it...
is there anything else i should configure?
enshum
02-27-2007, 09:51 PM
My connection is hardwired and suse (I no longer use suse) did detect it and it worked. I know from experince that suse detects some hardware that will not work until the user configs them printers is one that comes to mind. I'am using ubuntu 6.10 and Sabayon Linux (Gentoo based)now. I will be dropping ubuntu soon as Sabayon seems to be a better fit for me.
ed
deathadder
02-28-2007, 06:40 AM
Hi,
Just a few questions for you.
What the chipset for the wireless? Is any firmware required? If so have you got it?
If you run 'iwconfig' from the command line, what device is shown? eth0, eth1 etc
Are you using DHCP? If so what happens when you run 'dhcpcd xxxx' from the command line as root. Where xxxx is the device shown by iwconfig.
enshum
02-28-2007, 12:00 PM
My router is a hawking, ethernet SIS900. ethernet device sis 900 using dhcp eth 0. Suse always detected it correctly. In the control center it is listed under network devices. Mandriva, Ubuntu, Sabayon, and Puppy have all found and installed it correctly and the connection works first boot. Hope this helps
ed
nikodell
03-01-2007, 01:19 PM
Ok I often would get this for no appearent reason.
first try: dhcpcd eth0
it will then tell you that it has an address most likely
and to remove the address to continue
rm the file it tells you than: dhcpcd eth0
if you get an address now and internet works good
now gointo yast and remove your eth card configs completly
and reconfigure the card you are useing first if you have multy cards and it should work till it breaks again.
Happend to me all the time in suse but olny if I had more than one eth card in the computer.
Good Luck
justlinux.com
Copyright 2007 Jupitermedia Corporation All Rights Reserved.