Same Manufacturer, Brand, and same Model. (New one has faster clock speeds and Bluetooth.)
My company uses these (Panasonic Toughbooks.) for field work. They are tough, durable, rugged, travel well and have removable/slide out, swappable hard drives.
I slid-out my Linux drive from the older machine and slid it into the new one.
Everything looks and works the same EXCEPT for wifi. It does NOT even see it.
I started it with a Live CD of 11.2, it works great and the wifi connects perfectly.
So I know I must tweak the WiFi settings on my current install to make it work in the new machine,
This is where I need help! How do I do it? And if I get it working in the new machine will it still work in the older model? (I keep that one as a back-up/spare machine.)
I am trying NOT to buy another hard drive or do a re-install.
You say that wifi works with the 11.2 Live CD. What version is on the hard drive?
Does the dmesg output show you anything? Please do not post the entire output. I
do not care about all the memory allocation, etc.
You could also go to http://tinyurl.com/cvz7t9, download the script from
that site, run it, and post the results. The resulting file may exceed the
character limit here. If so, use pastebin, or some similar site and post the
link. The script output will tell us what device you have, and should indicate
how to get it working.
Same Live CD was used to install OpenSuse 11.2 in the present machine. New machine, (Same model, brand and model.) has faster clock speeds, bluetooth and the WiFi card is “WiFi Link 5100”.
Present machine (slightly older version same (Toughbook CF-52) has PRO/Wireless 4965 AG wifi card. AND it is working fine, I’m trying to use the same removable Hard Drive on the new slightly newer machine without having to re-install.
I think I need to tell the new machine we now have a NEW wifi card that way we can don’t have to do a whole new installation.
WHAT a Moron am I!
(I qualify as the fourth Stooge!!! And would have made the other three look BRILLIANT!!! )
All I had to do is go into Network Card Setup and Activate it!!!
Now I tell WICD to use WLAN1 instead of WLAN0.
And for $USERS who want a clean solution, a close look into /etc/udev/rules.d/70-persistent-net.rules would be the right thing to do (preferably with $TEXT_EDITOR as root).
On 03/26/2010 09:46 AM, riberto wrote:
>
> Same Live CD was used to install OpenSuse 11.2 in the present machine.
> New machine, (Same model, brand and model.) has faster clock speeds,
> bluetooth and the WiFi card is “WiFi Link 5100”.
> Present machine (slightly older version same (Toughbook CF-52) has
> PRO/Wireless 4965 AG wifi card. AND it is working fine, I’m trying to
> use the same removable Hard Drive on the new slightly newer machine
> without having to re-install.
>
> I think I need to tell the new machine we now have a NEW wifi card that
> way we can don’t have to do a whole new installation.
You don’t have to tell the machine that you have a new wifi card. You just have
to satisfy the requirements of the new card. For instance, I think the iwl-5100
needs external firmware. Have you installed it?
Another thing is that the 5100 driver may have been significantly improved since
the 2.6.31 kernel of 11.2. Using the compat-wireless package from Packman would
cover that case.
All I had to do is go into:
Network Devices / Network Settings
Choose the Overview Tab
And there it was!
I highlighted it, clicked <EDIT> then <NEXT> and finally <OK>
Now I can use this OpenSuSE 11.2 install on both laptops even though they have different WiFi cards.
(same removable Harddrive fits both laptops.)
It pays to have Packman as a source Software Repository.
That is where I got the “compat-wireless” package.
certainly not for compat-wireless as it is not available from Packman (and I should know if it were, because I had the idea of hosting compat-wireless on Packman and dropped it for several reasons).
On 03/26/2010 10:06 AM, Akoellh wrote:
>
> And for $USERS who want a clean solution, a close look into
> /etc/udev/rules.d/70-persistent-net.rules would be the right thing to
> do (preferably with $TEXT_EDITOR as root).
Yes, and if you used NetworkManager, it wouldn’t care if it was wlan0, wlan1, or
even wlan13 as I generated yesterday while working on a solution to a problem
with BCM43XX devices that do not have an SPROM. As a result, they have no MAC
address. The solution was a set of udev rules, but in the process, my hardware
device got a series of random addresses. Each time, the system generated a new
wlanX for it, but NM just kept on plugging.
I have not gone back and read the thread, but I do not think you disclosed that
you use wicd.
Yeah, such buggy hardware is really a PITA when dealing with udev setting up networking devices (some nvidia NICs are/were infamous for that and did this “by default”, IIRC the “record” I found for such a device was “eth128”, as a “side effect” one would approximately know, how oftne the machine was rebooted since install :-)).
Anyway, to prevent that for hardware connected via PCI/PCIE, I switched to identification based on PCI-BUS number some time ago.
lspci -nn |grep -i net
**0e:00.0** Network controller [0280]: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection [8086:4235]
**14:00.0** Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02)
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single line.
# PCI device 0x10ec:0x8168 (r8169)
# PCI device 0x8086:0x4235 (iwlagn)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", KERNELS=="**0000:0e:00.0**", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", KERNELS=="**0000:14:00.0**", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
although my hardware is generally known to “behave well” in this context.
I think this can be even done via YaST but I am too lazy to check now.
I am NOT the expert here, on a previous post lwfinger wrote to get “compat-wireless” from packman.
Since I use packman as a repository and I saw “compat-wireless” was already in my system…
I assumed that is where I got it. (of course you know what happens to those who assUme)
)