no, no luck.

its turning out to be a real waste of time. i mean it should not be taking this long to configure something this simple, especially when it works straight out of the box on the so called demon of all OS's windows.

so i am done. i am pretty disappointed as well with Suse , i mean for all the hype , especially on their website. this truly is a joke.

i have had other issues with it too, configuring my video card which is a pretty generic ATI mobility 7500, nothing fancy.

so if you have any luck when you give it a shot let me know.

thanks.

Okay , i installed fedora core 1, upgraded to the latest kernel, downloaded the driverloader version for fedora core 1 from linuxant. installed it, and BAM it WORKS!!!!!

it was easy and quick, almost as easy as XP!!

so it is an issue with Suse as far as i am concerned.

just thought i would let you guys know if you wanted to give it another shot.

thanks.

So basically you blew away SUSE for Fedora. And how is it working?

Read this tread. It is how I got my MN-720 802.11g card working in Suse 9.0.

http://www.linuxquestions.org/questi...hreadid=126753

Hi Jbraum

yes i blew suse for fedora. within minutes of the install (of driver loader) everything worked fine. i checked out Sabin's post. and it is true that suse makes the wifi connection wlan0, but in fedora it is eth1. so it looks like sabin changed that and then got it working under suse. so if your not interested in going my route maybe you should give that a try and maybe you may be lucky in getting it to work. if not , at least you know fedora is an option that works.

good luck.

Bam it the word... Downloaded Fedora did all the necessary configs (very little at that), loaded the linuxant driver and I'm on. Your right it is every bit as easy as XP. You'd think Suse would be just as easy to get your wireless but I guess not. It's worth using Fedora (which after playing with for a day has been flawless) to be able to use my wireless. None of the distros I've used were worth the troubles. Fedora runs well and setup of my wireless was easy. Worth it to me. Thanks for your feedback and support. I'll see you on the board.

jbraum

hey, glad to hear it worked out for you. your right, i mean if i can't use the internet i dont care how nice or easy SuSE claims to be, its not for me.


fedora has been good so far, i have not had any issues with it .

good luck.

One question. I updated the kernal to 135 from 115 and have both kernals on my login screen. When I select the 135 kernal I login and cannot get the wireless. I imagine I need to update the driver for my wireless adapter. Check linuxant and they have a download for 129. Is that the one you used? What is your kernal version?

Thanks again

the kernel that i upgraded to is this:

2.4.22-1.2129.nptl, my system is a i686.

i am not sure which kernel you upgraded to , because i have not seen that one, what type of pc do you have?

Tosiba Satellite A15. I downloaded the kernal via the red hat update in fedora. I'll check on fedoras site for an update. I'm pretty new with Linux so I'm just figuring things out. I know Linuxant didn't have a updated driver for the kernal I updated to. I seem to be running to 'tkernal versions. I get the option of which kernal to use when I login. Don't know if that is normal or not. I would think that the kernal would update and overwrite any previous version.

jbraum

OK, looks like you have updated to the latest possible kernel for fedora. one for which right now, linuxant does not have an RPM pre made for. you could try installing the one i mentioned above if you want to use a newer kernel than the default that ships with fedora. looks like the one you got was just posted a few days ago.

so you could either use the default one (that you already have setup and works), or install the one above and then install the driver loader version for that kernel, and you should be fine.

here is where you can download the kernel i mentioned above along with the other versions also.

http://rpmfind.net/linux/fedora/core/updates/1/i386/

before you download a version though you might want to run this command 1st to see if you have an i586 or i686.

open a terminal, su to root, and type

rpm -q --queryformat "%{ARCH}\n" kernel

this should tell you if it is i586 or i686.

then just download the appropriate version of 2.4.22-1.2129.nptl.

Thanks. I'll give it a try and let you know.

FWIW, I have a brand new IBM T41 with the Intel Centrino wifi card. Using SuSE 9 and the linuxant driver it is working fine for me! Only problem was with DHCP, I also could only browse the local LAN (this is at home with a Dlink 802.11g router) but would not be routed to the Internet, even if I manually assigned the gateway and DNS.

I gave myself a static IP, Gateway, DNS and everything works great. I'm going to try to resolve the DHCP issue over the next week or so and see if I can determine why it won't route with DHCP enabled (even though it can ping the gateway !?!)

Regardless, I'm quite happy.

In general on SuSE 9:
1-Make sure you do not have an eth1 for your wireless card.
2-If you have eth1, delete it from YaST (and if you were playing with dldrconfig before do a dldrconfig --remove.
3-Install the proper SuSE linuxant RPM package if you have not already.
4-Run dldroadercfg. Make sure it configures as wlan0 NOT eth1, perform step 2 if it does.!!!
5-Browse to http://127.0.0.2:18020 and upload your win driver files and licensing info. You should see the device as wlan0! (this really matters :) ).
6- Run YaST2 and configure wlan0 wireless details with ESSID and key if appropriate. If you are experiencing the DHCP non-routing issue then give yourself an available static IP. Gateway, DNS.
7-Enjoy!

Hi

after successfully being able to make my wireless connection work with fedora core 1, driverloader and my wpc54g card, i gave suse 9 one more shot, this time with a suggestion from linuxant tech support.


this is what they told me:
" Hi,

this is a comon problem when using DHCP with SuSE 9. Verify your interface's
configuration (/etc/sysconfig/network/ifcfg-...) to make sure you have the
following parameters.

DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'


after adding those parameters in, and specyfying the ESSID of my network (entering "any" does not work) i was able to surf the internet and browse my local network. BUT, every time i reboot/restart i have to go into YAST, network settings and act like i am editing something in my WLAN0 config, and let it rewrite the config settings again, and then it works.

so if i turn off the laptop, restart, login and try to surf, nothing. if i open up yast, network settings , click on edit wlan0, and just clcik finish, it then acti vates the network.

this has been verified multiple times by me. so its not perfect, obviously something needs to be finetuned and edited but at least it works now.

Again things were a lot simpler under fedora, but i just wanted to see why it would not work under suse9.

Woah. Thanks for that tip. I don't have to go into YaST after a reboot, it just works now!

I rebooted, still works!

Powered off, boot up, still works!

So DHCP is really working now. Only time I need to go into YaST is if I change wirelss networks and have to edit the ESSID. I no longer have to add the default gateway at the command line.

Not sure why you have to revisit yast every boot, but your post was a complete fix for me.

Thanks.