Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #189036 > unrolled thread

New Motherboard installation question

Started by"J.W. Foster" <jfoster81747@yahoo.com>
First post2017-11-16 18:00 +0100
Last post2017-11-16 18:20 +0100
Articles 3 — 3 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  New Motherboard installation question "J.W. Foster" <jfoster81747@yahoo.com> - 2017-11-16 18:00 +0100
    Re: New Motherboard installation question Roberto C. Sánchez <roberto@debian.org> - 2017-11-16 18:20 +0100
    Re: New Motherboard installation question "Alexander V. Makartsev" <avbetev@gmail.com> - 2017-11-16 18:20 +0100

#189036 — New Motherboard installation question

From"J.W. Foster" <jfoster81747@yahoo.com>
Date2017-11-16 18:00 +0100
SubjectNew Motherboard installation question
Message-ID<uMvG9-1Ro-13@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

I installed a new motherboard on a system that I run as as a server. Same system has 3 1tb disks with Debian stable installed, and 1 with Windows 10 installed, all booting at my discretion from grub. I was able to get all of the drives to operate, and Im using one for this. However I have noticed a crap load of boot error messages when I watch the system boot on anything except Windows, as it does not display any boot messages. As I said it's working but those error messages were not there before I replaced the motherboard, which was in fact defective. Both the old board and the new one are ASUS. I figure that I need to do some type of Linux maintenance reset, but as I have never done a replacement without doing a complete reinstall of all the software, I have no idea what to do. Any tips are welcome, and no I have not researched this online. I'm just seeking info from folks that have done this before.ThanksJohn

[toc] | [next] | [standalone]


#189037

FromRoberto C. Sánchez <roberto@debian.org>
Date2017-11-16 18:20 +0100
Message-ID<uMvZv-2d2-1@gated-at.bofh.it>
In reply to#189036
On Thu, Nov 16, 2017 at 04:57:28PM +0000, J.W. Foster wrote:
>    Any tips are welcome, and no I have not researched this online.

I would say that if you want specific suggestions, posting the actual
error messages is a good start.

>    I'm just seeking info from folks that have done this before.

I have a server now that runs Stretch (HP microserver) that began life
in 2002 running Debian 3.0 (Woody).  The original machine was a Pentium
Pro 200 MHz with maybe 16 MB RAM.  It went from that box into a new
small form factor case with a mini-ATX (or was it micro-ATX?)
motherboard and a VIA C7 CPU.  That motherboard eventually failed and
was replaced, then the power supply later failed and that was when I
acquired the HP, which necessitated switching from 32-bit to 64-bit.

My main workstation is in a similar situation.  It started life in 2003
with an AMD Athlon XP CPU on a BioStar motherboard.  That machine went
through 4 motherboards from different manufacturers until a few years
ago I went to another Biostar motherboard with an Intel Core i5 CPU.

In every case, the main things which ended up being factors in the
migration were:

- kernel modules (my configuration either unconditionally loaded
  incompatible modules or blacklisted modules I needed)
- device naming assumptions that were not constant (e.g., references to
  things under /dev/disk/by-uuid)
- Left-over semi-persistent state files (e.g., in /var)

It is difficult to be more specific without the specific error messages
you are seeing.

Regards,

-Roberto

-- 
Roberto C. Sánchez

[toc] | [prev] | [next] | [standalone]


#189038

From"Alexander V. Makartsev" <avbetev@gmail.com>
Date2017-11-16 18:20 +0100
Message-ID<uMvZv-2d2-5@gated-at.bofh.it>
In reply to#189036

[Multipart message — attachments visible in raw view] — view raw

On 16.11.2017 21:57, J.W. Foster wrote:
> I installed a new motherboard on a system that I run as as a server.
> Same system has 3 1tb disks with Debian stable installed, and 1 with
> Windows 10 installed, all booting at my discretion from grub. I was
> able to get all of the drives to operate, and Im using one for this.
> However I have noticed a crap load of boot error messages when I watch
> the system boot on anything except Windows, as it does not display any
> boot messages. As I said it's working but those error messages were
> not there before I replaced the motherboard, which was in fact
> defective. Both the old board and the new one are ASUS. I figure that
> I need to do some type of Linux maintenance reset, but as I have never
> done a replacement without doing a complete reinstall of all the
> software, I have no idea what to do. Any tips are welcome, and no I
> have not researched this online. I'm just seeking info from folks that
> have done this before.
> Thanks
> John
Can you show us what error messages exactly look like? It will be a good
start.
Use this command to get system logs:
    $ sudo journalctl -b

Also, post full specs of your computer.

It is probably a good idea to check ASUS support site for a BIOS update
for your motherboard, as recent hardware is likely to be rushed to the
market asap and patched later.

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀ 

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web