Going from Windows to Linux

[lokiju]

Originally posted by: kamper

Originally posted by: lokiju
I just feel like such a noob.

Don't. Running binary drivers from another operating system is not a pretty thing. The best thing in the long run is to buy chips from companies that release enough documentation for proper drivers to be written.

No clue why I'm getting that line 135 error, I even logged in as root and still get the same thing.

Not sure what else I can try.

 

[lokiju]

Originally posted by: Alienwho

Originally posted by: lokiju

Originally posted by: kamper
Did you do it from the same directory that you extracted the driver in (as in if you 'ls' do you see the inf file in the list)?

Yep.

I even found by googling this which didn't work, still get that line 135 error.



1. Use Synaptic to get ndiswrapper-tools
2. Get the windows drivers, and copy the .sys and .inf to somewhere (say /home/<yourusername>/Linksys/)
3. Open terminal, and enter the following commands:
3a. cd Linksys
3b. sudo ndiswrapper -i <name>.inf (mine was lsb something, but I just renamed it to linksys.inf as it makes it easier). The screen should show something about Forcing parameter RadioState|0 to RadioState|1... mine had 4 lines.
3c. cd /etc/ndiswrapper/
3d. Edit all the .conf files, look for the line RadioState|1 and change it to RadioState|0 (to do this, I had to type sudo gedit and open the files from the GUI... gedit didn't quite like opening files with \: from the command line, not sure why) I'm not sure if just changing one or two files will work, but I just changed all 4.
3e. sudo modprobe ndiswrapper
3f. (optional) sudo echo ndiswrapper >> /etc/modules
3g. sudo iwlist wlan0 scan (look for your access point in the list)
3h. sudo iwconfig wlan0 channel <X> essid <ESSID> mode Managed (the X and ESSID should come from the iwlist)
3i. sudo ifup wlan0


If I can't get my wireless nic working there isn't much reason to stay with SUSE

Hopefully theres a solution, I just feel like such a noob.

This is the reason why I went back to Ubuntu after trying Suse 10.1. The wireless just plain freaking works, you don't have to do anything. Oddly enough, it will probably work just fine for you if you try SUSE 10.

Try Ubuntu Dapper. You can download it, it's just one cd, like 600 megs.

Already got it burnt and ready to go, just wanna give this thing a try a little more and if I can't make it happen then I'll go this route.

Would rather get SUSE 10.1 working if possible though.

 

[SleepWalkerX]

Originally posted by: Alienwho

Originally posted by: lokiju

Originally posted by: kamper
Did you do it from the same directory that you extracted the driver in (as in if you 'ls' do you see the inf file in the list)?

Yep.

I even found by googling this which didn't work, still get that line 135 error.



1. Use Synaptic to get ndiswrapper-tools
2. Get the windows drivers, and copy the .sys and .inf to somewhere (say /home/<yourusername>/Linksys/)
3. Open terminal, and enter the following commands:
3a. cd Linksys
3b. sudo ndiswrapper -i <name>.inf (mine was lsb something, but I just renamed it to linksys.inf as it makes it easier). The screen should show something about Forcing parameter RadioState|0 to RadioState|1... mine had 4 lines.
3c. cd /etc/ndiswrapper/
3d. Edit all the .conf files, look for the line RadioState|1 and change it to RadioState|0 (to do this, I had to type sudo gedit and open the files from the GUI... gedit didn't quite like opening files with \: from the command line, not sure why) I'm not sure if just changing one or two files will work, but I just changed all 4.
3e. sudo modprobe ndiswrapper
3f. (optional) sudo echo ndiswrapper >> /etc/modules
3g. sudo iwlist wlan0 scan (look for your access point in the list)
3h. sudo iwconfig wlan0 channel <X> essid <ESSID> mode Managed (the X and ESSID should come from the iwlist)
3i. sudo ifup wlan0


If I can't get my wireless nic working there isn't much reason to stay with SUSE

Hopefully theres a solution, I just feel like such a noob.

This is the reason why I went back to Ubuntu after trying Suse 10.1. The wireless just plain freaking works, you don't have to do anything. Oddly enough, it will probably work just fine for you if you try SUSE 10.

Try Ubuntu Dapper. You can download it, it's just one cd, like 600 megs.

If he tries Dapper the wireless isn't going to "just freaking work". Its a broadcom chipset and Dapper does not have the 2.6.17 or higher kernel so there won't be the bcm43x driver so he would have to do the same thing he is doing now. Get ndiswrapper to work.

edit: Or try to experiment with the bcm43x driver in Ubuntu's repository.

 

[SleepWalkerX]

Originally posted by: lokiju

Originally posted by: kamper

Originally posted by: lokiju
I just feel like such a noob.

Don't. Running binary drivers from another operating system is not a pretty thing. The best thing in the long run is to buy chips from companies that release enough documentation for proper drivers to be written.

No clue why I'm getting that line 135 error, I even logged in as root and still get the same thing.

Not sure what else I can try.

Do you still have your cd with the original drivers? Try using those.

 

[lokiju]

Originally posted by: SleepWalkerX
[Get ndiswrapper to work.

I wish I knew how

I've been looking like crazy but can't seem to find a solution.

 

[lokiju]

Originally posted by: SleepWalkerX

Originally posted by: lokiju

Originally posted by: kamper

Originally posted by: lokiju
I just feel like such a noob.

Don't. Running binary drivers from another operating system is not a pretty thing. The best thing in the long run is to buy chips from companies that release enough documentation for proper drivers to be written.

No clue why I'm getting that line 135 error, I even logged in as root and still get the same thing.

Not sure what else I can try.

Do you still have your cd with the original drivers? Try using those.

I'll look, I might.

EDIT:
Damn, nope.

EDIT 2:

I looked on Linksys' site and it looks like theres only ever been one release of the driver for this NIC.

Last Driver Version: 1.22.1.2004
__________________________________________________________


Driver Version 1.22.1.2004
- Initial release

 

[SleepWalkerX]

Try using the command lspci and then do lspci -n and give the pciid for the card (it might look something like 10b9:1695).

 

[lokiju]

Originally posted by: SleepWalkerX
Try using the command lspci and then do lspci -n and give the pciid for the card (it might look something like 10b9:1695).

lspci - n produced

00:00.0 Class 0600: 8086:3575 (rev 04)
00:01.0 Class 0604: 8086:3576 (rev 04)
00:1e.0 Class 0604: 8086:2448 (rev 42)
00:1f.0 Class 0601: 8086:248c (rev 02)
00:1f.1 Class 0101: 8086:248a (rev 02)
00:1f.5 Class 0401: 8086:2485 (rev 02)
01:00.0 Class 0300: 1002:4c59
02:02.0 Class 0c03: 1033:0035 (rev 41)
02:02.1 Class 0c03: 1033:0035 (rev 41)
02:02.2 Class 0c03: 1033:00e0 (rev 02)
02:03.0 Class 0607: 104c:ac50 (rev 02)
02:04.0 Class 0200: 8086:1229 (rev 09)
02:04.1 Class 0700: 11c1:045c
03:00.0 Class 0200: 17fe:2220

 

[Cerb]

Originally posted by: azev
I am in exactly the same boat as you are... I have extensive windows background, but very very little linux. I have a friend who is a unix master, and re recomended me to install gentoo stage 1 to learn linux. It has been 3 days since I tried, and I have not been successfull yet. If I can get it to work by this weekend, he is going to give me a walkthrough of how to get it done the right way, and whats every command means.
Good luck......

:Q Gentoo...to start?! That's mean. Debian, CentOS, PLOS, Ubuntu, other Debian derivatives...but Gentoo?

WPC54G

Check the version, then check the ndiswrapper list (it may or may not be a broadcom!). As of the newest PCLOS, the included driver didn't work well for the one I've got (V1), and got in the way of using ndiswrapper.

I think Ubuntu currently includes the ndiswrapper driver; the last MEPIS even included it. Try the Live CD version of Ubuntu, or try MEPIS, to see. In the future, get Ralink (the worst problem I've had w/ Ralink is making it use wlan0 instead of rausb0).

 

[SleepWalkerX]

Yeah I see it right here: 03:00.0 Class 0200: 17fe:2220

You're using the right driver according to the ndiswrapper list. Hmm.. Try using these drivers that are under that card: ftp://ftp.linksys.com/pub/network/WPC54G%20v4%20driver%20rev%201.22.1.2004.zip

 

[lokiju]

Originally posted by: Cerb

Originally posted by: azev
I am in exactly the same boat as you are... I have extensive windows background, but very very little linux. I have a friend who is a unix master, and re recomended me to install gentoo stage 1 to learn linux. It has been 3 days since I tried, and I have not been successfull yet. If I can get it to work by this weekend, he is going to give me a walkthrough of how to get it done the right way, and whats every command means.
Good luck......

:Q Gentoo...to start?! That's mean. Debian, CentOS, PLOS, Ubuntu, other Debian derivatives...but Gentoo?

WPC54G

Check the version, then check the ndiswrapper list (it may or may not be a broadcom!). As of the newest PCLOS, the included driver didn't work well for the one I've got (V1), and got in the way of using ndiswrapper.

I think Ubuntu currently includes the ndiswrapper driver; the last MEPIS even included it. Try the Live CD version of Ubuntu, or try MEPIS, to see. In the future, get Ralink (the worst problem I've had w/ Ralink is making it use wlan0 instead of rausb0).

It's version 4 which isn't a Broadcom.

Text

Card: Linksys #[WPC54G v4], 54mbps -- [link here|List#WPC54G v4]

* Chipset: AirConn? IPROCOMM IPN 2220 (rev 01)
* pciid: 17fe:2220
* Driver: Linksys ftp://ftp.linksys.com/pub/network/WPC54G%20v4%20driver%20rev%201.22.1.2004.zip
* Used ndiswrapper -i WLINPDS.INF on Debian Sarge for the Linksys driver. Worked perfectly.
* Driver:IPN2220 ftp://ftp.rediris.es/sites/arklinux.org...ver-ipn2220-2.10.03.2004-1ark.i586.rpm
* Other: Debian/Sarge 2.6.11, Ndiswrapper 1.1 with module asistant.Works with WEP 64bits and 128bits and WAP-PSK,other encription not tested

 

[lokiju]

Originally posted by: SleepWalkerX
Yeah I see it right here: 03:00.0 Class 0200: 17fe:2220

You're using the right driver according to the ndiswrapper list. Hmm.. Try using these drivers that are under that card: <a target=_blank class=ftalternatingbarlinklarge href="ftp://ftp.linksys.com/pub/network/WPC54G%20v4%20driver%20rev%201.22.1.2004.zip">ftp://ftp.linksys.com/pub/network/WP......4%20driver%20rev%201.22.1.2004.zip</a>

Same "couldn't copy xyz line 135" error message.

:scratches head;

 

[SleepWalkerX]

Hmm, even I could install the driver. Try compiling the latest ndiswrapper release. The newest stable version is 1.23. http://sourceforge.net/project/showfiles.php?group_id=93482

To compile the module make sure kernel-source is installed (same version as the kernel you're running as far as default or smp goes), make, and gcc. Extract the contents, open up the command line and navigate to the folder, and type "make && make install" as root. Then try to install it again.

 

[lokiju]

Originally posted by: SleepWalkerX
Hmm, even I could install the driver. Try compiling the latest ndiswrapper release. The newest stable version is 1.23. http://sourceforge.net/project/showfiles.php?group_id=93482

To compile the module make sure kernel-source is installed (same version as the kernel you're running as far as default or smp goes), make, and gcc. Extract the contents, open up the command line and navigate to the folder, and type "make && make install" as root. Then try to install it again.

Is that "make && make install" verbatim?

Or do you mean for me to enter something else where the "&&" is?



I'm in process of trying though.

 

[SleepWalkerX]

Verbatim, it'll run make then make install once make is done.

 

[lokiju]

Originally posted by: SleepWalkerX
Verbatim, it'll run make then make install once make is done.

That's so confusing sounding

But in process of reinstalling ndiswrapper still.

 

[xtknight]

IMO an easier way of putting it would be: It runs make, and once make finishes, it runs the make install command. It's just one command after another finishes (synchronous fashion), that's all.

I don't usually like doing make && make install. I would rather type make and then make sure myself that that are no errors before I proceed to a make install. Make compiles and links the code and make install is the installation script.

 

[lokiju]

Originally posted by: xtknight
IMO an easier way of putting it would be: It runs make, and once make finishes, it runs the make install command. It's just one command after another finishes (synchronous fashion), that's all.

I don't usually like doing make && make install. I would rather type make and then make sure myself that that are no errors before I proceed to a make install. Make compiles and links the code and make install is the installation script.

Wait a min, am I supposed to download the updated ndiswrapper files to the root dir then run that make && make install command?

Either way thank you SleepWalkerX and everyone else that's helped today.


Looks like I'll have to call it a day and pick it back up tomorrow.

 

[SleepWalkerX]

Originally posted by: lokiju

Originally posted by: xtknight
IMO an easier way of putting it would be: It runs make, and once make finishes, it runs the make install command. It's just one command after another finishes (synchronous fashion), that's all.

I don't usually like doing make && make install. I would rather type make and then make sure myself that that are no errors before I proceed to a make install. Make compiles and links the code and make install is the installation script.

Wait a min, am I supposed to download the updated ndiswrapper files to the root dir then run that make && make install command?

Either way thank you SleepWalkerX and everyone else that's helped today.


Looks like I'll have to call it a day and pick it back up tomorrow.

Nah just run the commands from where they are and they will be put in the right places.

 

[Nothinman]

I don't usually like doing make && make install. I would rather type make and then make sure myself that that are no errors before I proceed to a make install. Make compiles and links the code and make install is the installation script.

That's what the && is for, 'make install' only runs if 'make' returns 0 for it's exit code.

 

[xtknight]

So && checks but ; doesn't?

 

[Nothinman]

So && checks but ; doesn't?

Correct. And || is used for the opposite, if the first command fails the second one executes.

 

[Cerb]

&& = and (a and b). If not a, then b doesn't matter, because they can't both be true if the first one is false.
|| = or (but I'm not sure if it's exclusive or inclusive)

So, with 'make && make install':
If make succeeds, make install runs. If make install also succeeds, the statement is true. However, you don't need them both to succeed to make it work like you need. If make fails, though, it won't bother with a make install, which could just pollute your filesystem with junk (compile in tmpfs FTW?).

If not actually coding something, I think such scripting features are better left unused, because they can be confusing sometimes, and slight mistakes can drive you nuts.

 

[lokiju]

Originally posted by: Cerb
&& = and (a and b). If not a, then b doesn't matter, because they can't both be true if the first one is false.
|| = or (but I'm not sure if it's exclusive or inclusive)

So, with 'make && make install':
If make succeeds, make install runs. If make install also succeeds, the statement is true. However, you don't need them both to succeed to make it work like you need. If make fails, though, it won't bother with a make install, which could just pollute your filesystem with junk (compile in tmpfs FTW?).

If not actually coding something, I think such scripting features are better left unused, because they can be confusing sometimes, and slight mistakes can drive you nuts.

I read from here that

Choose at leat C/C++ Compiler and Tools. You might also need KDE, Gnome and Tcl/Tk Development and in some cases Kernel Development. The only drawback of installing this is loss of diskspace

So I have to install one of these first before I can compile something? Is that right?

I'm installing them now and will try again, maybe that's why it wasn't working?

 

[lokiju]

Originally posted by: SleepWalkerX
Hmm, even I could install the driver. Try compiling the latest ndiswrapper release. The newest stable version is 1.23. http://sourceforge.net/project/showfiles.php?group_id=93482

To compile the module make sure kernel-source is installed (same version as the kernel you're running as far as default or smp goes), make, and gcc. Extract the contents, open up the command line and navigate to the folder, and type "make && make install" as root. Then try to install it again.

Woot!

Got it to install the update after installing a complier that I didn't realize wasn't installed by default.

Going to try getting ndiswrapper 1.23 working now.

:crosses fingers;