LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 09-15-2011, 01:30 PM   #1
ordinary
Member
 
Registered: Apr 2007
Location: the Rocket City
Distribution: Debian, Ubuntu, CentOS; in days past Fedora, Solaris, SunOS, 4.2BSD, 4.3BSD, SVR4, AIX, HP-UX
Posts: 101

Rep: Reputation: Disabled
Swapping motherboard under an existing Debian squeeze install


Here's a naive question: Is it inadvisable to change out a motherboard under an existing Debian squeeze x86_64 installation? I don't know how much tailoring Debian does during installation, and I don't know how much nuisance I will cause myself. The machine in question is a household file server. It is not a particularly critical machine, and it is backed up.

The particulars are that I want to swap out a MSI K9N SLI and swap in a Gigabyte GA-M57SLI-S4, rev2. Both use the nForce 570 SLI chipset. Memory, CPU, and graphics card will stay with the computer, I just want to swap the board itself.

I understand that I could get in trouble if I tried to slide a 32 bit board in under a 64 bit OS, but that's not the case here. What problems will I encounter?

I'm sure this has been discussed before, at least the general idea, but I have not managed to come up with suitable search terms. My searches have produced a great many interesting but irrelevant results.
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 09-15-2011, 01:57 PM   #2
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,573

Rep: Reputation: 580Reputation: 580Reputation: 580Reputation: 580Reputation: 580Reputation: 580
It's no real bother.

Your home brewed initrd will be junk, but the board should stand up and start X, if the video card & monitor are the same. Either way, you'll get to runlevel 3. I would set initdefault in /etc/inittab to console level (3 usually).

Once running, optimise. check your correct modules are loading (don't forget sensors). Get the hd speed and stuff in /etc/modprobe.d right for the new system. Tell us if you notice any problems.
 
Old 09-15-2011, 04:01 PM   #3
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,619
Blog Entries: 2

Rep: Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076Reputation: 4076
Debian (and almost all derivatives) uses runlevel 2 by default and all other runlevels (except 0,1 and 6 of course) are the same. If you don't want to start X you have to disable the DM. But since this is a server I don't know if even a X environment is installed.
I doubt that it won't work perfectly out of the box after the change.
 
Old 09-15-2011, 05:33 PM   #4
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Rep: Reputation: 116Reputation: 116
One problem you will run into if ethernet ports are on the motherboard is that udev will have cached a rule assigning interface "eth0" to the MAC address of the old ethernet port. On the new motherboard, the new MAC address will be bumped up to be "eth1" and the network configuration for "eth0" will not be used on "eth1". Check file "/etc/udev/rules.d/70-persistent-net.rules". If you find "eth0" did not come up, but "eth1" did, you can simply delete "/etc/udev/rules.d/70-persistent-net.rules" and reboot. Then udev will re-create it, but now with the new MAC address, and use "eth0" appropriately.
 
2 members found this post helpful.
Old 09-16-2011, 09:11 AM   #5
ordinary
Member
 
Registered: Apr 2007
Location: the Rocket City
Distribution: Debian, Ubuntu, CentOS; in days past Fedora, Solaris, SunOS, 4.2BSD, 4.3BSD, SVR4, AIX, HP-UX
Posts: 101

Original Poster
Rep: Reputation: Disabled
Skaperen, that's good info about the ethernet interface naming, and just the sort of thing I was looking for. I will rename 70-persistent-net.rules, and watch what happens. I did think about enumeration order of device names for disks and partitions, and accounted for that in fstab. I wonder if there are 6 x 10^23 other similar considerations.

I'll get to it this weekend, I hope. Right now, my office (and radio shack, and library) is awash in computer parts.

Pass the beer nuts.
 
Old 09-16-2011, 03:33 PM   #6
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Rep: Reputation: 116Reputation: 116
I'm sure there are at least that many other considerations to make. Better get started now

If you just rename one of those sequentially numbered rules files, they will still be used, but maybe in a different order. If you want to disable some rules, move it out of that directory.
 
Old 09-21-2011, 09:12 AM   #7
ordinary
Member
 
Registered: Apr 2007
Location: the Rocket City
Distribution: Debian, Ubuntu, CentOS; in days past Fedora, Solaris, SunOS, 4.2BSD, 4.3BSD, SVR4, AIX, HP-UX
Posts: 101

Original Poster
Rep: Reputation: Disabled
Just for the record, the swap did not take place. The GA-M57SLI-S4, which had been carefully stored, had apparently not been stored carefully enough. It was dead. No POST, no nothing. I spent more hours than I care to admit excluding and swapping components. Finally, I had only a known good power supply, known good memory, a known good video card, a known good CPU, and the GA-M57SLI-S4. Still, no dice. When the board was powered up, the various fans spun up and the diagnostic speaker made two ticks and nothing else.

Two diagnostic ticks seems to mean a corrupt BIOS. I spent a great deal of time trying miracle cures, blind flashes, and other ineffective techniques. Finally I decided that keeping this up until I fried another component, although my natural inclination, wouldn't cause bliss, so I paid a visit to Newegg.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: How to add Debian Squeeze to your Debian Lenny FAI install server LXer Syndicated Linux News 0 09-08-2011 08:21 PM
Various segmentation faults Debian Squeeze Virtualbox running on Debian Squeeze host fordwrench Debian 1 07-21-2011 04:55 AM
install debian squeeze from a usb ring0 Linux - Laptop and Netbook 4 07-06-2011 07:40 AM
[SOLVED] Cannot install Debian squeeze Faithfully10 Debian 8 05-23-2011 07:30 PM
[SOLVED] Debian Squeeze - Can't install wine. Zaraphrax Linux - Software 59 01-27-2011 03:19 PM


All times are GMT -5. The time now is 11:59 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration