SliTaz Forum

LeitiHUN

Member

Registered: 2013-12-24

Posts: 2

How can i install OFFLINE my wireless NIC?

Hi all,

My problem is that i haven't got any Internet access, but i need to install my wireless cards to Slitaz 2.0. Please help me, i'm new in linux, and in Slitaz too!

Sorry for my bad English, i understand what you say, but i can't speak.

The cards:

Gigabyte GN-WP01GS

TP-LINK TL-653AG

Thanks

Guest

Guest

Re: How can i install OFFLINE my wireless NIC?

You would be better off using a more up to date version, at least SliTaz 4.0. You might need the later drivers in it for your wifi card.

Then use menu-network-wicd (if memory serves me right, I'm not on SliTaz at the moment) to set up your wifi

To check if the neccessary drivers are being loaded at boot up, run

sudo ifconfig -a

in a terminal & you should see your wifi card mac address & some other info.

LeitiHUN

Member

Registered: 2013-12-24

Posts: 2

Re: How can i install OFFLINE my wireless NIC?

Thx!

I hate Slitaz 4.0's tazpanel, and completly the GUI.

I installed the drivers rt61pci and ath5. The system can't see the ath5 (this is the TP-LINK card), ath5 module is in use, but not works. RT61pci (this is the Gigabyte card) is in use, RT61 firmware in use. The system see this as wlan0. But not see the networks.

How can i config the RT61? And what can i do with the ath5?

Thx

kultex

Administrator

Registered: 2011-03-28

Posts: 1,175

Re: How can i install OFFLINE my wireless NIC?

Look, if you like rolling more

http://forum.slitaz.org/topic/testing-iso-with-kernel-3250

2.0 is to old

[attachment=27350,1278]

Guest

Guest

Re: How can i install OFFLINE my wireless NIC?

On 4.0 it is - menu > system tools > configure networking

If it is different on 2.0, you will need to find it.

Trixar_za

Administrator

Registered: 2011-03-29

Posts: 1,506

Re: How can i install OFFLINE my wireless NIC?

I pretty sure 2.0 lacks most of the graphical tools that only got introduced in 3.0. I'm also pretty sure the wifi packages only got included in the repository since 4.0. So using 2.0 because you hate 4.0's interface - which you can change - is the biggest cause of your problem.