Instaliranje drajvera za wi fi

Ćao svima! Ja sam Nikola friški Mint korisnik, danas sam vam se priključio. Imam nov lap top Toshiba Satellite c855-1LW. Instalirao sam najnoviji Mint 14. Skoro sve je ok. Najviše problema mi pravi to što ne mogu da koristim wireless.
Koliko sam skontao mreže koje hvata bi trebalo da se nalaze u donjem desnom uglu kod netvork setingsa, ali tamo nema ničega Wired (on/off) i Network menager-a.
Celo veče sam čačkao po internetu i našao sam na ovom forumu čoveka sa istim problemom.

U terminalu dobijam sledeće:

sudo /usr/lib/linuxmint/mintWifi/mintWifi.py
[sudo] password for chaslav:
-------------------------
* I. scanning WIFI PCI devices...
-- [b]Realtek Semiconductor Co., Ltd. Device 8723[/b]
==> PCI ID = 10ec:8723
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
eth0	 no wireless extensions.
lo	 no wireless extensions.
-------------------------
* IV. querying ifconfig...
eth0	 Link encap:Ethernet HWaddr 70:54:d2:18:45:6c
inet addr:192.168.1.142 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::7254:d2ff:fe18:456c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:81342 errors:0 dropped:0 overruns:0 frame:0
TX packets:51856 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:102070460 (102.0 MB) TX bytes:4614807 (4.6 MB)
lo	 Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1350 errors:0 dropped:0 overruns:0 frame:0
TX packets:1350 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:192647 (192.6 KB) TX bytes:192647 (192.6 KB)
-------------------------
* V. querying DHCP...
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service smbd reload
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the reload(8) utility, e.g. reload smbd
RTNETLINK answers: File exists
-------------------------
* VI. querying nslookup google.com...
Server: 192.168.1.20
Address: 192.168.1.20#53
Non-authoritative answer:
Name: google.com
Address: 79.101.110.99
Name: google.com
Address: 79.101.110.103
Name: google.com
Address: 79.101.110.104
Name: google.com
Address: 79.101.110.108
Name: google.com
Address: 79.101.110.109
Name: google.com
Address: 79.101.110.113
Name: google.com
Address: 79.101.110.114
Name: google.com
Address: 79.101.110.118
Name: google.com
Address: 79.101.110.119
Name: google.com
Address: 79.101.110.123
Name: google.com
Address: 79.101.110.84
Name: google.com
Address: 79.101.110.88
Name: google.com
Address: 79.101.110.89
Name: google.com
Address: 79.101.110.93
Name: google.com
Address: 79.101.110.94
Name: google.com
Address: 79.101.110.98

Tako da kontam da je to ista mrežna kartica i da samo treba instalirati ove drajvere. Jedini je problem što ne znam kako da ih instaliram. Može li neko u detalje da mi objasni kako da ih instaliram? Evo recimo da mi se oba tar.gz. fajla nalaze u /home šta treba da kucam u terminalu?

Unapred zahvalan :playboy:

skonato sam da treba da ih otpakujem i onda nađem redme.txt fajl u kojem piše uputstvo za instalaciju.

dakle imam dva fajla
8723AE_8723AU_Linux_support_0419.tar.gz
i
rtl_92ce_92se_92de_8723ae_linux_mac80211_0007.0809.2012.tar.gz

kod prvog u readme fajlu piše:

In this document, we introduce how to support rtk 8723AE/AU BT driver in Linux system.
Support kernel version 2.6.32~3.0.1
===========================================================================================================
1. Install
(1) Build and install USB driver,change to the 8723AE_8723AE_Linux_support direcotory
$sudo rmmod rtk_btusb
$sudo make install -s
(2) Insert RTK8723AE/AU dongle
Now RTK8723AE/AU can be recognized by the system and bluetooth function can be used.
===========================================================================================================
2. Uninstall
(1) unplug RTK8723AE/AU dongle
(2) Uninstall
$sudo rmmod rtk_btusb
$sudo make uninstall -s
===========================================================================================================
3.Install blueZ
The default BlueZ in Ubuntu maybe out of date£¬
New versions can be downloaded from http://www.bluez.org/
If you do not want to install blueZ,skip this step
Here we take Ubuntu 11.10 (linux 3.0.0-12-generic) for example.
Make sure system is connected to the internet.
(1) Setting up a Linux build environment
Install dbus
$sudo apt-get install libdbus-1-dev

Install glib
$sudo apt-get install libglib2.0-dev
(2)Decompress and install BlueZ follow Readme file in blueZ-4.96 directory

$sudo tar -zxvf bluez-4.96.tar.gz
$sudo cd bluez-4.96
$sudo ./configure --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc --localstatedir=/var --libexecdir=/lib
$sudo make && make install

kod drugog:

Release Date: 2012-05-09, ver 0006
Realtek Linux mac80211 based driver:
--This driver supports follwing RealTek PCIE Wireless LAN NICs:
RTL8188CE/RTL8192CE
RTL8191SE/RTL8192SE
RTL8192DE
RTL8723AE
--This driver supports follwing Linux OS:
Fedora Core
Debian
Mandriva
Open SUSE
Gentoo
MeeGo
android 2.2 (froyo-x86), etc.
--This driver supports follwing kernel versions:
1) kernel version >=2.6.35
you can build & install drvier use II.

2) kernel version [2.6.24, 2.6.34]
you can build & install drvier use III.

========================================================================================
I. Component
========================================================================================
The driver is composed of several parts:
1. Firmare to make nic work
1.1 firmare/rtlwifi
2. Module source code
2.1 ./*
2.2 rtl8192ce
2.2 rtl8192se
2.2 rtl8192de
2.2 rtl8723ae

3. Script to build the modules
3.1 Makefile
4. compat-wireless
4.1 compat-wireless*.tar.bz2
4.2 compat
========================================================================================
II. Compile & Installation & uninstall
========================================================================================
You can enter top-level directory of driver and execute follwing command to
Compile, Installation, or uninstall the driver:
1. Change to Super User
sudo su
2. Compile driver from the source code
make
3. Install the driver to the kernel
make install
reboot
4. uninstall driver
make uninstall
========================================================================================
III. Compile & Installation & uninstall [2.6.24, 2.6.34]
========================================================================================
We don't support kernel 2.6.24-2.6.34 directly, Because there are
lots of issues in mac80211 from kernel 2.6.24-2.6.34,
So we suggest you to use the latest kernel >= 2.6.35.
but if you want to use our driver in an old kernel,
you can use compat-wireless. this methord can support all kernel
versions higher than 2.6.24, and you can use all functions
of our driver like you use it in the latest kernel version.
You can get more informations of compat-wireless from:
http://wireless.kernel.org/en/users/Download/stable
you should use the following commands to Compile, Installation, or uninstall the driver:
1. Change to Super User
sudo su
2. install compat-wireless driver
./compat/script/compat-install.sh

3. reboot
reboot
4. uninstall driver
./compat/script/compat-uninstall.sh
5. you can get more information form follwing webset for how to use compat-wireless:
http://wireless.kernel.org/en/users/Download/stable

NOTICE:
1. Maybe you can not use other vendors wireless after you install compat wireless,
in this situation, you can uninstall compat-wireless use step 4 to recover it.
2. This install methord can support all versions of kernel, not just 2.6.24-2.6.34,
you can also use it in the kernel higher than 2.6.35.
========================================================================================
IV. Start Up Wireless
========================================================================================
You can use two methord to start up wireless:
1. Install driver like II. and reboot OS, Wireless will be brought
up by GUI, such as NetworkManager
2. If Wireless is not brought up by GUI, you can use:
ifconfig wlan0 up
Note: some times when you have two wireless NICs on your computer,
interface "wlan0" may be changed to "wlan1" or "wlan2", etc.
So before "ifconfig wlan0 up", you can use "iwconfig" to check
which interface our NIC is.
Note: Don't try to down driver by "ifconfig wlan0 down" when
NetworkManager id opened, because NetworkManager will up
driver automatically.
========================================================================================
V. Wireless UI & NetworkManager
========================================================================================
1. All latest distributions have UI & NetworkManager to like with AP.
And it's more easy to link with AP than commandline,
So we suggest you use UI to link with AP.
2. Don't try to like with AP use commandline with UI or NetworkManager opened.
3. If you still used commandline to link with AP, Please check if
NetworkManager & wpa_supplicant is killed by follwing command:
ps -x | grep NetworkManager
ps -x | grep wpa_supplicant
4. Follwing commandlines(V-VII) are all used under Linux without UI.
========================================================================================
VI. Set wireless lan MIBs
========================================================================================
This driver uses Wireless Extension as an interface allowing you to set
Wireless LAN specific parameters.
1. Current driver supports "iwlist" to show the device status of nic
iwlist wlan0 [parameters]
you can use follwing parameters:
parameter explaination	 [parameters]
-----------------------	 -------------
Show available chan and freq freq / channel
Show and Scan BSS and IBSS scan[ning]		
Show supported bit-rate		 rate / bit[rate]	
For example:
iwlist wlan0 channel
iwlist wlan0 scan
iwlist wlan0 rate
2. Driver also supports "iwconfig", manipulate driver private ioctls,
to set MIBs.
iwconfig wlan0 [parameters] [val]
you can use follwing parameters:
parameter explaination	 [parameters]	 [val] constraints
-----------------------	 -------------	 ------------------
Connect to AP by address ap			 [mac_addr]
Set the essid, join (I)BSS essid			 [essid]
Set operation mode		 mode			 {Managed|Ad-hoc}
Set keys and security mode key/enc[ryption] {N|open|restricted|off}
For example:
iwconfig wlan0 ap XX:XX:XX:XX:XX:XX
iwconfig wlan0 essid "ap_name"
iwconfig wlan0 mode Ad-hoc
iwconfig wlan0 essid "name" mode Ad-hoc
iwconfig wlan0 key 0123456789 [2] open
iwconfig wlan0 key off
iwconfig wlan0 key restricted [3] 0123456789
iwconfig wlan0 key s:12345
Note: There are two types of key, "hex" code or "ascii" code. "hex" code
only contains hexadecimal characters, "ascii" code is consist of
"ascii" characters. Assume the "hex" code key is "0123456789", you
are suggested to use command like this "iwconfig wlan0 key 0123456789".
Assume the "ascii" code key is "12345", you should enter command
like this "iwconfig wlan0 key s:12345".
Note: Better to set these MIBS without GUI such as NetworkManager and be
sure that our nic has been brought up before these settings. WEP key
index 2-4 is not supportted by NetworkManager.
========================================================================================
VII. Getting IP address (For OS without UI)
========================================================================================
Before transmit/receive data, you should obtain an IP address use one of
the follwing method:
1. static IP address:
ifconfig wlan0 IP_ADDRESS
2. dynamic IP address using DHCP:

dhclient wlan0

========================================================================================
VIII. WPAPSK/WPA2PSK (For OS without UI)
========================================================================================
Wpa_supplicant helps you to link with WPA/WPA2(include WPA Enterprise) AP,
in Linux with NetworkManger & UI, UI will help you to link with AP,
But if there is no UI & Networkmanger in your Linux, you can use
follwing method to link with WPA/WPA2 AP.

1. we suppose that your Linux have installed wpa_supplicant &
kernel build with WIRELESS_EXT, In fact, lots of distributions
have done like this.
But if some distribution not install wpa_supplicant,
please download wpa_supplicant from webset and install it.
2. Edit wpa1.conf to set up SSID and its passphrase.
For example, the following setting in "wpa1.conf"
means SSID to join is "BufAG54_Ch6" and its
passphrase is "87654321".
network={
ssid="BufAG54_Ch6"
#scan_ssid=1 //see note 3
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP WEP104 WEP40
psk="87654321"
priority=2
}
You can download wpa_supplicant and read wpa_supplicant.conf
for more examples.
3. Execute WPA supplicant:
wpa_supplicant -D wext -c wpa1.conf -i wlan0
4. To see detailed description for driver interface and wpa_supplicant,
please type:
man wpa_supplicant

Ne razumem ih najbolje i ne znam šta dalje da kucam u terminalu pa ako može neko pomoći…

u prilogu šaljem make i readme fajlove za oba drajvera

Da pojednostavim pricu jer ne mogu da povatam od tog silnog teksta.
Ako ti je sve isto kao sto si dao link na @Sretenov post, isto znaci ista kartica sve hardwerski isto.
Ako je to to onda skini ta dva fajla sa linkova.
Prvi faj otpakuj u neki dir kod sebe, krsti ga kako god oces pera, zika, mika.
Kad otpakujes u taj dir vidi da li pravi on svoj dir.
Setuj se na taj dir cd komada
ide komada make
ako dobro zavrsi sudo make install
Da bi uoste to radio moras da imas instaliran paket build-essential
Isto to za drugi file
Tako se otprilike radi ako ne pise drugacije, a u readme kod tebe pise da to radi za

Support kernel version 2.6.32~3.0.1

Kod tebe je sigurno novija verzija kernela.
Zatrpao si nas sa brdom teksta

Vidi ovo
http://askubuntu.com/questions/163141/drivers-for-realtek-wireless-module-for-toshiba-c850-a965
A ovo mu je navodno resenje
http://ubuntuforums.org/showthread.php?t=2017622
Prati pazljivo sta pise, komade se kucaju u terminalu

Uspeo sam da instaliram drajvere na jedvite jade uz pomoć dobrih ljudi sa lugons četa. Pratili smo baš uputstva koja si ti dragane dao. I evo sad mi prepoznaje karticu, prikazuje komšijske mreže. Ja nemam svoj wifi ruter za sad tako da sam pokušavao da se kačim na komšijske mreže koje nemaju šifru ali neće da se konektuje. A znam da su neki moji drugovi ranije uspevali da se konektuju na komšije. Probao sam i na faxu na nekoliko mreža i nije hteo. Sedim pored lika koji vata wifi a meni neće da se konektuje.
Krene da se konektuje, na sekund pokaže da je konektovan i onda se diskonektuje i ponovo krene da se konektuje na predhodnu mrežu i tako u krug.
Jedino sam jednom uspeo da se konektujem preko drugovog telefona na gprs.
Da li ja samo nemam sreće da pronaćem dobar wifi ili je nešto drugo?

Koja ti je tačna oznaka WiFi kartice i koji model je u pitanju?

Kolika ti je jacina signala na tim mrezama koje hvatas, mozes samo da se konektujes na “komsija net” ako je otkljucan i ako je dovoljno jak signal, ako je to AP iako stoji da je otkljucan on nije otkljucan.
Kad otvoris netwok manager i iskljucis zicnu vezu i ukljucis wi-fi trebao bi da pokaze sve raspolozive mreze i status, otkljucano ili zakljucano, prave AP pokazuje kao otkljucane ali to nije tako.
Wi-fi je lutrija kod mene u jednoj sobi nema signala a u drugoj radi ko lud, razlika 5 metara.

Ima jos zackoljica ali ne mogu da se setim komandi, provere se komadom drajveri da li su softwerski i hardwerski ukljuceni. I jos jedna caka ti drajveri koji se stave su skup drajvera, nekad sistem iz tog skupa ucita pogresan onda je potrebno blacklistovati ostale a samo ostaviti pravi, @neupuceni je imao taj problem

[email protected]:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: no
Kad prebacis na wi-fi (Wireless) trebalo bi da je NO Soft i Hard

[email protected]:~$ lsmod | grep rtl rtl8187 56912 0 mac80211 539908 1 rtl8187 cfg80211 206566 2 rtl8187,mac80211 eeprom_93cx6 13302 1 rtl8187

U ovom listanju treba da budu oznake tvog wi-fi drajvera, koliko se secam ako stoji drugo onda se vidi sta sve ima u toj kolekciji pa se /etc/modprobe.d/rtl.conf
edituje rtl.conf i ubace se drajverikoji ne trebaju iz te kolekcije. sitakasa ide:
blacklist rtlxxxx
blacklist rtlyyyy

mislim da je
Realtek Semiconductor Co., Ltd. Device 8723
to bar piše u mom prvom postu iz terminala

imam bar 4 mreže koje se kreću od 20 do 60%, sve su otključane i ne vidim da igde piše AP. Kažem ti na faxu gde je provereno otvorena mreža kolegi do mene je hteo da se konektuje i radio je a kod mene nije.

U načelu kontam šta mi govoriš ali ne razumem šta treba da radim, ja i terminal smo jedno na nivou neko mi kaže šta tačno da kucam i ja to kucam. stvarno se ne razumem u terminal… Može li neko da ide sa mnom korak po korak?

Da li si uradio ovo sto pise a ASKubuntu

For some reason the install script didn’t copy the firmware correctly, so I had to do it manually. I moved rtl8723fw.bin and rtl8723fw_B.bin from the rtlwifi folder in the source directory to /lib/firmware/rtlwifi/, rebooted and it worked.
Probaj pa onda trazi alternative, pitaj dalje ljude na lugos irc

Problem je sto i ja to ne znam napamet a trebali bi mi dani i dani da pronadjem.
To sto sam nasao to sam ti i postavio da ukucas u terminalu:

rfkill list all

i ovo drugo kucas u terminalu

lsmod | grep rtl

sad na osnovu toga neko ko vise zna od mene dao bi ti uputsvo sta dalje, moja kartica je legla iz cuga nista nisam morao da podesavam a
primarno koristim ADSL zicni. Ja sam se debelo raspitao pre nego sam uzeo USB wi-fi karticu, pregledao brdo nekih tabela da li je podrzano ili nije
Za pravi AP provajdera ti nigde ne pise da je AP moze da ima neko levo ime kao i “komsija net”
Nazalost ja vise od ovoga ne znam, ako ti je bas toliko vazan wi-fi koristi dual boot win-linux, iz linuxa idi preko kabla a iz wina na wi-fi.

RTL8188CE/RTL8192CE RTL8191SE/RTL8192SE RTL8192DE RTL8723AE
Najverovatnije imas ovu kolekciju ili sta si vec odradio po savetima na irc, vidi u tom fajli sta ima a tebi treba samo jedan

lsmod | grep rtl

Ovom komandom vidi sta imas iz ove kolekcje, ne mozes da se okacis znaci nije taj
Uzmes i ukucas u terminalu sudo gedit /etc/modprobe.d/rtl.conf
trazi password koji se ne vidi kad kucas
otovori se editor uzmes i ukucas blacklist RTLxxxx koju ti je ona komanda pokazla
save i reboot
Ponovo dignes masinu pa probas, sta drugo da ti napisem to je sistem po kom se radi dok ne ubodes pravi
a sve ostale strpas u rtl.conf da ih ne ucitava