suse 9.3 professional on dell latitude d610 - Printable Version +- Linux-Noob Forums (https://www.linux-noob.com/forums) +-- Forum: Distro Noob (https://www.linux-noob.com/forums/forum-10.html) +--- Forum: SUSE (https://www.linux-noob.com/forums/forum-98.html) +--- Thread: suse 9.3 professional on dell latitude d610 (/thread-2763.html) |
suse 9.3 professional on dell latitude d610 - anyweb - 2005-04-05 hi, getting wireless to work was a pain, it identified the Intel 2200bg card just fine but yast was no help in setting up wireless. Finally after much trying, and some googling i discovered that there was a message in /var/log/messages which read Quote:Kill Switch must be turned off for wireless networking to workwhich is great, at least now i can see why i wasted hours trying to get wireless to work. so some more googling explains the following:- [/url][url=http://marc.theaimsgroup.com/?l=suse-amd64...69505013930&w=2]http://marc.theaimsgroup.com/?l=suse-amd64...69505013930&w=2 Code: cat /sys/bus/pci/drivers/ipw2200/0000\:03\:03.0/rf_kill will return a value, explained below... so on a Latitude D610, if you cycle through FN+F2 the value reported by the code above will give a number corresponding to below. You need a '0' (zero) to get wireless working. 0 = RF kill not enabled (radio on) 1 = SW based RF kill active (radio off) 2 = HW based RF kill active (radio off) 3 = Both HW and SW RF kill active (radio off) to quickly get this info i made a simple bash script which tells me what the state is when run, simply fire up vi and paste this in Code: #!/bin/sh then chmod +x wireless_state (or whatever you called the file). sh wireless_state will then return a value. once you get it working iwconfig will hopefully look like this Quote:eth0 IEEE 802.11b ESSID:"wireless" Nickname:"linux" Mode:Managed Frequency:2.437 GHz Access Point: 00:05:5D:99:CF:4D cheers anyweb suse 9.3 professional on dell latitude d610 - kabifff - 2006-03-29 Holyyyyyyyyyyy crap Anyweb, I have a latitude D610 and I've been digging for this for months. You, sir, are the man. suse 9.3 professional on dell latitude d610 - kabifff - 2006-04-05 .....But I still can't get it to work. VIM won't let me past anything into it, and if I can get it to, it says "pattern not found: sys". Frustrating. suse 9.3 professional on dell latitude d610 - anyweb - 2006-04-05 to use vi try the following: to INSERT text press 'i' or the INSERT key on your keyboard to REPLACE text press the INSERT key again to save your changes (write) press the ESCape key followed by : and then 'w' ie: Code: :w to quit Code: :q to save and then quit Code: :wq pressing ESC will go from 'INSERT/REPLACE' mode to interactive mode allowing you to enter commands good luck cheers anyweb suse 9.3 professional on dell latitude d610 - kabifff - 2006-04-05 Does this work even if I don't have the centrino chipset, but just the pentium m? suse 9.3 professional on dell latitude d610 - anyweb - 2006-04-05 centrino is not a chipset, its a marketing term from intel to denote that there is an intel wireless card in your laptop (along with an intel cpu) so if your latitude has an intel wireless card in it then at boot time, you'll see a 'centrino' logo on the bios screen if however, your latitude has a broadcom wireless card then you'll just see 'pentium M' on the same dell bios screen so are you sure that you have an intel card in this or not ? lspci will show you what card you have, post it here cheers anyweb suse 9.3 professional on dell latitude d610 - kabifff - 2006-05-05 Quote:centrino is not a chipset, its a marketing term from intel to denote that there is an intel wireless card in your laptop (along with an intel cpu) Hey anyweb, sorry about the delay. What is LSPCI? I know I don't have an intel wireless card, I believe it's a broadcom by origin, but it has the dell label on it. It's a dell 1470 wireless A/G card. suse 9.3 professional on dell latitude d610 - anyweb - 2006-05-05 well if you have the broadcom card then you'll need to use ndiswrapper to get it to work, checkout the ndiswrapper howto in the wireless section of linux-noob.com for more details and in linux, commands are case sensitive, so its not LSPCI its lspci (all lowercase) cheers anyweb |