stolpiller
Member
Posts: 23
|
 |
« on: May 07, 2010, 07:53:55 am » |
|
Hello My wifi card is detected (lspci shows it), and the right modules ar loadded (lsmod shows iee80211). But still VASM says wlan0 no such interface / no wireless interface... Tried to do all in the guide here on VL. But i'm stuck  Computer IBM R51 and Intel ProW 2200BG Thanks in advance |
|
|
|
« Last Edit: May 08, 2010, 05:28:32 am by stolpiller »
|
Logged
|
|
|
|
|
newt
|
|
« Reply #1 on: May 07, 2010, 08:36:37 am » |
|
Can you provide the output from the following:
ifconfig -a
iwconfig
lspci
lsmod
I think iee80211 is a "helper" module but not the actual chipset module which is why it would be good to see the entire list of modules (lsmod).
|
|
|
|
|
Logged
|
|
|
|
stolpiller
Member
Posts: 23
|
|
« Reply #2 on: May 07, 2010, 05:21:13 pm » |
|
Ok, here we go....
ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:11:25:49:26:f4
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth1 Link encap:Ethernet HWaddr 00:12:f0:6a:2b:b9
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4374 errors:0 dropped:0 overruns:0 frame:0
TX packets:292 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:11 Base address:0x8000 Memory:d0204000-d0204fff
irda0 Link encap:IrLAP HWaddr 00:00:00:00
NOARP MTU:2048 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:8
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
iwconfig
lo no wireless extensions.
irda0 no wireless extensions.
eth0 no wireless extensions.
eth1 unassociated ESSID:off/any
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
lspci (truncated)
02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
lsmod (truncated)
ieee80211 28488 1 ipw2200
ieee80211_crypt 5380 1 ieee80211
|
|
|
|
|
Logged
|
|
|
|
|
bigpaws
|
|
« Reply #3 on: May 07, 2010, 06:56:29 pm » |
|
The wireless interface name is eth1 not wlan0. In VASM try using eth1 vs wlan0.
Bigpaws
|
|
|
|
|
Logged
|
|
|
|
|
newt
|
|
« Reply #4 on: May 07, 2010, 06:58:54 pm » |
|
It looks like your hardware is present and recognized by the system. I'm not familiar with the KDE Classic variation of VL, but most likely it has the wicd network manager included. I would use the wicd client to set up your network connection. Make sure you're using eth1 as your device name rather than wlan0. Recollection tells me that either the default wicd or wpasupplicant device name is 'wlan0' which means you should check all Preferences of wicd, and if you use wpasupplicant then check it's settings (from within wicd) as well. Let us know how it comes along.
|
|
|
|
|
Logged
|
|
|
|
stolpiller
Member
Posts: 23
|
|
« Reply #5 on: May 08, 2010, 01:14:22 am » |
|
The wireless interface name is eth1 not wlan0. In VASM try using eth1 vs wlan0.
Bigpaws
Confusing, with the naming... Anyways, tried eth1, in vasm. Seems now interface is correct, but i'm not connected... must be some other settings. Read last night that, with this machine, 1M Fixed rate, is a must... So i'll try different settings and see what happens  |
|
|
|
|
Logged
|
|
|
|
stolpiller
Member
Posts: 23
|
|
« Reply #6 on: May 08, 2010, 01:23:44 am » |
|
It looks like your hardware is present and recognized by the system. I'm not familiar with the KDE Classic variation of VL, but most likely it has the wicd network manager included. I would use the wicd client to set up your network connection. Make sure you're using eth1 as your device name rather than wlan0. Recollection tells me that either the default wicd or wpasupplicant device name is 'wlan0' which means you should check all Preferences of wicd, and if you use wpasupplicant then check it's settings (from within wicd) as well. Let us know how it comes along.
Wicd is run within KDE? I think kde-classic is just about the same as free SOHO (when 6.0 version is out), but with KDE 3.5 Ok, I will try that and present the results... EDIT:::: Working now! Strange I could not get the network up in VASM. But worked in Wicd (figured out the dark arrow to add encryption, with some help from google). I guess I only have wireless working within KDE? Thanks for help guys! |
|
|
|
« Last Edit: May 08, 2010, 03:02:14 am by stolpiller »
|
Logged
|
|
|
|
|
nightflier
|
|
« Reply #7 on: May 08, 2010, 05:04:40 am » |
|
Wicd is included and activated in KDE-Classic because it makes network configuration easy. However, you don't need wicd, or KDE. Manual configuration is a little more involved, you would need to disable the wicd service (use vasm), stop the wicd client from launching, and run "VLwifi" as root.
|
|
|
|
|
Logged
|
|
|
|
stolpiller
Member
Posts: 23
|
|
« Reply #8 on: May 08, 2010, 05:28:09 am » |
|
Wicd is included and activated in KDE-Classic because it makes network configuration easy. However, you don't need wicd, or KDE. Manual configuration is a little more involved, you would need to disable the wicd service (use vasm), stop the wicd client from launching, and run "VLwifi" as root.
First time using wifi under linux, glad it works. But wich is to prefer? Manual or via KDE? I'm thinking of major upgrades (new kernel, etc).. then I guess it's safe to be at runlevel 2? |
|
|
|
|
Logged
|
|
|
|
|
bigpaws
|
|
« Reply #9 on: May 08, 2010, 06:19:57 am » |
|
You can use any Window Manager/Desktop environment for Wicd. It is a
gui front end for wireless tools.
As far as preference it does not make a difference. Wicd is designed
to make setting up wireless easier. VASM does the same thing as
WICD, in that it calls the same commands.
The gui interface (Window Manager/Desktop Environment) as all
front ends to the Command Line.
You do not need a gui to do anything in Linux.
Bigpaws
|
|
|
|
« Last Edit: May 08, 2010, 06:24:06 am by bigpaws »
|
Logged
|
|
|
|
|
nightflier
|
|
« Reply #10 on: May 08, 2010, 07:21:46 am » |
|
wich is to prefer? Manual or via KDE?
If it is working for you now, leave it as it is. |
|
|
|
|
Logged
|
|
|
|
retired1af
Packager
Vectorian
Posts: 1083
|
|
« Reply #11 on: May 08, 2010, 07:30:52 am » |
|
If it is working for you now, leave it as it is.
Let's get real here! Leaving it alone is akin to telling a Harley rider to stop tinkering with his bike. It can't be done!  |
|
|
|
|
Logged
|
ASUS K73 Intel i3 Dual Core 2.3GHz
|
|
|
stolpiller
Member
Posts: 23
|
|
« Reply #12 on: May 09, 2010, 02:53:44 am » |
|
If it is working for you now, leave it as it is.
Let's get real here! Leaving it alone is akin to telling a Harley rider to stop tinkering with his bike. It can't be done! Haha, yeah that's exactly what I mean!  |
|
|
|
|
Logged
|
|
|
|
GrannyGeek
Packager
Vectorian
Posts: 2567
|
|
« Reply #13 on: May 09, 2010, 11:33:46 am » |
|
I'm thinking of major upgrades (new kernel, etc).. then I guess it's safe to be at runlevel 2?
I use runlevel 2 for all my versions of VectorLinux. I prefer it because when I exit the desktop, I'm back at a command prompt and don't have to do tricks to get into an environment where X is not running. It's just one additional step at startup (type startx or startxfce4 or whatever command starts the desktop environment I want to use). --GrannyGeek |
|
|
|
|
Logged
|
Registered Linux User #397786
Happily running VL 7 Gold on a Sempron LE-1300 desktop (2.3 GHz), 4 G RAM, GeForce 6150 SE onboard graphics and on an HP Pavilion dv7 i7, 6 gigs, Intel 2nd Generation Integrated Graphics Controller
|
|
|
|
