Suse 9, Linksys wireless G and Linuxant wraper
 

Maybe someone can help me with this one. Loaded the driver and pointed to 127.0.0:18020 and config the setting as asked. Got my license key and everything went fine. The only thing is I can't get the wireless adapter to see my router. It's not active (the notebook adapter). Here's some info that might help.

Device
eth1 (but not wireless settings)

Driver
lsbcmnds

MAC
Is correct

License
OK

Driver
same as above

Vendor
Linksys -correct

2/12/2003 3.10.39.7

Tells me all devices are configured.

jbraum

Anyone!

Hi

did you ever get this to work .

i am about to try a linksys WPC54G w/ the linuxant software on Suse 9.

i plugged in the card yesterday and it was picked up but obviously did not work due to lack of drivers. i did not have time to try the linuxant software but hope to today.

if you were able to get it to work and you have any pointers please let me know.

thanks.

Not yet! If you get it to work let me know. I'll keep trying just haven't had a lot of time.

jbraum

ok, i will download the trial version tonight (hopefully) and then give it a shot and see if it works.

i am also considering purchasing Suse winerack , its going for $39.99, for both the plugin and office, which is not a bad deal. i figure if i can get IE to work w/ it then i can install regualr plugins like quicktime, windows media player etc. have you tried this ?

i know theres mplayer, and xine and stuff, but theres always some issue that i have run into with them .

but i will keep you posted if it works out.

thanks.

Assume winerack is an application or cpu emulator. You might want to try wine. Let me know through this post if you get your wireless working. I will try again tomorrow or maybe tonight.

Jbraum

sure, i'll keep you posted.

Okay!

well , the install whent well, very easy infact, but, i still do not have internet access although i am able to browse my local network.

so this means that its a DNS server issue or some network configuration setting that i need to play w/ in the settings tab.

only thing is unlike in XP, where you just click the wireless tab and it automatically scans all available networks so you just pick one and try to connect to it, in Suse it is a bit more involved.

i have everything set to DHCP but it doesn't seem to be doing the trick.

it cant be the router because i see the linux host name under wireless clients w/ the right IP. so it is giving out the info, but for some reason Suse is not taking it. so i did not have a chance to hard code the network configs yet, but will give it a shot tonight if i have time.

but as far as the Linuxant package goes, i ran an online update through Yast, downloaded all updates, i beleive there was a Kernel update as well. then installed the following from the CD's , perl, python as i beleive these are needed to use the web configuration utility from linuxant. once i did that i donwloaded the latest RPM for Suse from the linuxant website.
just click it, yasttakes over and it installs within seconds. if you get an error check the detailes, most likely it will be because of a mismatch between the rpm package version and the kernel version you have installed.

once its installed, just use the webtool, and login as root, then upload the windows drivers (which also can be downloaded from linuxant if you dont have it) and then enter your license key and thats it.

after doing all this, which took all of 5minutes or less, go to network devices and configure the device.

let me know if this works for you.

I had no problem with the linuxant. The interface appear and I was able to load the driver from my cd supplied by Linksys. Where I having trouble is when I inserted my card Linux sees it as eth 1. Eth 0 being my nic. I then have no wireless configurations. The linuxant interface also sees eth1. Any thoughts.

jbraum

oh , well it seems that it could be a driver issue. because if the right driver is not loader it will not appear as a wireless device. mine shows up at
"WLAN0".

so when i go into network devices in YAST, i see 2 devices
eth0
wlan0

i select wlan0 and click on the edit button and that opens up a new menu with several other options, like dhcp settings, and other wireless settings. so if you do not get that then it does not recognize it as a wireless device.

where did you get the drivers from. i downloaded the drivers from the linuxant website. and then you select one .inf and one .sys file i believe.

but if your install whent fine then i would suspect the driver .

sorry i just re read your post again , so you got the drivers off the cd. i see. let me see which files i used and then compare that against the ones you selected.

because once the drivers were installed , and i whent into the network devices tab, a wireless device was already added there and recognized.

which did not happen before due to the unavailability of drivers.

I'll check my drivers and post. Let me know what your drivers are.

Thanks

Hopefully I'll get it to run soon

Here's the Linuxant Configs.

eth 1

Isbcmrds driver

Let me know what you have.

jbraum

i will when i get home, in the meantime check this out also , this is the exact problem that i am having.

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

Any luck with getting your wireless to work. Haven't had enough time but this weekend I'll try. Also if anyone has been successful at using wireless with suse 9.0 and would like to write a tutorial, I'll gladly post the tutorial on my site. It seems as though there are a lot of users with this problem.

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.

great! glad it helped.

if you could post the contents of your (/etc/sysconfig/network/ifcfg-wlan0) file i could compare it against mine and see where the problem is, thats causing me to have to rerun YAst each time.


oh wait a minute, you have the centrino wifi set up , so its all built in. i have a pcmcia linksys card, so i think the way the services load up, where it brings up the network 1st and then probes for pcmcia later, is the reason i have to rerun YAST again once it boots up.

I'll have to try re numbering the services as suggested in an earlier post and see if that helps. You would think these sorts of issues would be simple enough for a compnay like SuSE to figure out!! i guess not.

Although i have to commend linuxant support for their suggestion and rather quick response.

I bet you're right about the bootup sequence of services.
Just in case here's the content of icfg-wlan0:

BOOTPROTO='dhcp'
BROADCAST='10.0.1.255'
IPADDR='10.0.1.239'
MTU=''
NETMASK='255.255.255.0'
NETWORK='10.0.1.0'
REMOTE_IPADDR=''
STARTMODE='onboot'
UNIQUE=''
WIRELESS_ESSID='yourESSIDhere'
WIRELESS_KEY='yourkeyhere'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
DHCLIENT_MODIFY_RESOLV_CONF='yes'
DHCLIENT_SET_DEFAULT_ROUTE='yes'
~

BTW, the IPADDR is what I previously had the adapter set to. DHCP is enabled now in YaST, and in fact I get a different, dynamic address than the one listed. It just must enter it the file in case DHCP is disabled.

cool thanks.

I have SuSE 9 running flawlessly, have used both a Lynksis card and a Netgear card with equal success with very little work. My wireless adapter, was recognised and configured by Yast. However I could not for the life of me get it to get outside my router, even with the proper settings in Yast.

In the console as root, I did a simple route add default gw 192.168.0.1 wlan0 then opened a browser and whala I was on the net.

Now that it worked, I simply added that line to my /etc/initd.d/rc file so it would be active at boot with the card plugged in. Alls good for me now. I don't know why the yast settings wouldn't do this for me, all I know is this worked for me.

It may or may not help you guys with your problems but it certainly wouldn't hurt to try. Of course you will want to substitute your gateway address in place of my 192.168.0.1.

:Pengy: Your trick solved my problem but I couldn't put it inmy rc file.
I tried it but without succes. It doesn't work. Can you help me?

I've successfully got my broadcom wireless g working the the ndiswrapper over at www.sourceforge.net.

Wes