can't move drive to identical laptop
NOTE - "Similar Threads" did not help me with this.
I have two identical laptops. One has an installed Ubuntu and parts that I want to use. The box itself is all beat up. The other box is newer but has a stale edition of linux. (Stale software means "seldom used.") I thought to be clever I would pull drive-A from box-A and install it into box-B. Likewise, I would install drive-B into box-A. This will leave my clunky software on my battered box and my newer software on the newer box. Mechanically it works (doh!). However, neither box will see the network. When I look at the logs, I find a "rename wlan0 to wlan1" entry among others. If I put the drives back into their original box, all works correctly. What could be going on that I cannot move the drives and have things just boot and run? I thought that system start would detect the installed hardware, load the required drivers and all is right with the world. The "rename" log entry suggests that the old hardware details are somehow in the way of the new hardware discovery and configuration. Is there some command I need to use or utility that I ought to run that says, "rediscover my hardware" or similar? I already know how to use clonezilla and other ways to duplicate a drive contents to a second drive. (Note to reader: laptop drive to usb drive clonezilla takes quite some amount of time.) Another reason that this is important lies in the ability to move a drive from in-use but failed hardware to stand-by working hardware in a fail soft recovery situation. I know that win-doze knows about the installed hardware and demands a re-install or "repair" to the alternate box... but this is linux not win-doze. Merci d'avance, ~~~ 0;-Dan |
Quote:
Try running "ifconfig" in a terminal to get something like: ("iwconfig" for wireless) Code:
eth0 Link encap:Ethernet HWaddr 00:13:d3:ec:00:99 Swap the disk into the other system and try again. I'd reckon you're probably set for DHCP so should just get an IP dished out to you but there may be a network config file which is no longer valid in the other machine. Nope, I don't know what it would be... I'm into concepts, don't bother me with details! :D Might be somewhere to start looking? :twocents: Play Bonny! :hattip: |
You can try find "wlan1" in file /etc/udev/rules.d/70-persistent-net.rules and rename it to "wlan0" and then restart. Maybe it help, but network also depends on other things.
|
Quote:
Quote:
... is Bonny your daughter or cat :scratch: Cheers, ~~~ 0;-Dan |
Quote:
So, Er... Play Bonny! :hattip: Oh! Forgot to ask, have you managed to get your wireless enabled before and after you swap the disks? If so, does it fix the problem? |
Quote:
I've not played with net config from the command line and all of the gooey tools fail to see any wifi to configure. This fail is likely due to the "radio off" issue that I cannae find how to turn on manually. |
Quote:
Play Bonny Y'All! :hattip: |
Quote:
Code:
diff dmidecode1.log dmidecode2.log Is some other "report" and diff more helpful? ~~~ 0;-Dan |
I was thinking more about checking within the BIOS of each machine.
Play Bonny! :hattip: |
According to the man page:
man dmidecode Here is what I see: Code:
# dmidecode 2.9 ~~~ 0;-Dan |
Quote:
Apologies, I didn't do enough research on the above, I'll be interested in seeing what differences, if any, you have between the machines. Play Bonny! :hattip: |
Here are some difference details between my two laptops -- both are Lenovo Thinkpad X61-tablets identified as 7764-CTO.
Code:
prompt$ diff sysinfo_1.log sysinfo_2.log Notice that these differences are so minor as to be meaningless. I ran a second comparison with these results: Code:
prompt$ diff dmidecode_1.log dmidecode_2.log Stumpled, ~~~ 0;-Dan |
All times are GMT -5. The time now is 04:40 PM. |