Forums

Resolved
0 votes
Hi Friends,

I wanted to up my hardware capability a bit and so looked for a MB for my COS 7 server. I decided thought I've had good luck with consumer MBs, I'd be professional and get something server oriented. It's ITX sized, so the selection is limited.

This approach has been frought with problems. Every item I have purchased used the 222, 224 or 226 chipsets. Another common link is the inclusion of a IPMI port, and the ASpeed server chipset. Nothing but error messages, video problems, and instability. The ASRock Rack boards were especially problematic.

I'm now using a 222 based board from MSI. Here are the strange symptoms:

Starts to boot OK.

GIves error: TSC_Deadline disabled due to errata. Please update microcode....etc
Then error i8042: No controller found

Then the boot progress stripe starts and looks normal. Part way through, the video mode changes as I expect, but then the progress stripe has bizarre colors.

When the progress stripe finishes, there is no video. The system stays that way for approximately 5 to minutes. Then, suddenly I get the sign on screen. I can sign in, and the graphic interface seems normal. However, it does not seem stable and often reboots upon changes.

There are boards that supposedly support Linux well. I am using a Xeon E3-1200 v3 series processor. No luck at all. I've tried quite a few "ordinary consumer" boards and every one seems fine.

Is there some major problem with that ASpeed support device, or the 22x Intel server chipset series? Any ideas out there?


Thanks,
Drew VS
Tuesday, January 01 2019, 09:42 PM
Share this post:
Responses (10)
  • Accepted Answer

    Wednesday, January 02 2019, 01:15 AM - #Permalink
    Resolved
    0 votes
    Drew - are the boards you are testing certified by Redhat? Redhat Hardware List

    If not - then maybe they have a problem with Redhat like distributions and not put on the list, or never tested...
    If yes - wonder if it is something different ClearOS has done... as should be OK

    If they are all complete systems - some are built from commonly available retail boards - do any of these have the chipsets you are having problems with?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, January 02 2019, 01:52 PM - #Permalink
    Resolved
    0 votes
    Hi Tony,

    All MB, no complete systems. Some are on the list (e.g. the ASRock Rack items), and some are not. But it strokes me as odd that 4/4 server boards have been epic fails when probably 8 or the last 9 unrated consumer boards I have tried have been 100% fine. Only one recent SOC Atom board was an exception.

    They always seem to have the same odd video problems, and they all use that ASpeed server chipset for IPMI and video.

    I was hoping the very odd symptom of no video at all for 5 minutes, right after the progress bar, and then suddenly video....100% repeatable...was a hint to someone of the issue. Very odd!

    Thanks,
    Drew
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, January 02 2019, 03:19 PM - #Permalink
    Resolved
    0 votes
    IMPI is very useful - see, for example, Here for software and a desciption... It has been around since about 2001 - ipmitool.x86_64 version 1.8.18-7.el7 is available from clearos-centos as is OpenIPMI-modalias-2.0.23-2.el7.x86_64.

    Might be worthwhile doing a quick simple install of the current CentOS Version 7 - if that works OK, then it is something about ClearOS that is tripping you up... but read below first.

    ASpeed is not just a chipset - it is a SoC - a complete ARM processor system that runs independently of the main processor, usually with its own NIC for remote access, which monitors the main system, performs a number of useful functions such as powering up the main system, remote installing an OS on the main system, monitoring the main system health such as temperature, fans etc. Very useful for enterprise administrators to control systems all over the world from a central location. The graphics in the SoC is very basic - 2D only. ASpeed have a driver to get the best from the graphics for some OS... Intel also supplies a special graphics driver for its server boards when using Redhat V7 - see Here for an older (v7.3) sample giving an idea of the requirements...

    Note also that some servers may require setting certain kernel parameters eg "acpi=force" or black-listing a driver...

    Sorry - cannot be of much more help. I have been retired now for over 5 years and no longer "in the game". However, if you want to run server hardware and use all its fuctions, you probably need to be a "server" admininstator :p
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 03 2019, 12:25 AM - #Permalink
    Resolved
    0 votes
    Hi Tony,

    This was a simple install of the current COS 7.

    I'm generally familiar with IPMI and the SOC for it...I just mentioned that as a common factor in all the problematic boards in case it struck a note. Especially since it contains a VGA solution. The installation seems to be generally working, but I don't trust it given the odd video symptoms and earlier instability.

    I have always been suspicious that the OEM engineers never seem to be able to explain to me when the VGA solution on chip is used, and when the integrated VGA on the CPU is used. I think this is somehow part of the mess I keep encountering.

    I'm not clear on the relevance of that video driver for specific Intel boards to mine...can you explain?

    I follow regarding blacklisting drivers, kernel parameters, etc. but wouldn't have a clue where to begin determining that.

    Thanks,
    Drew

    Tony Ellis wrote:

    IMPI is very useful - see, for example, Here for software and a desciption... It has been around since about 2001 - ipmitool.x86_64 version 1.8.18-7.el7 is available from clearos-centos as is OpenIPMI-modalias-2.0.23-2.el7.x86_64.

    Might be worthwhile doing a quick simple install of the current CentOS Version 7 - if that works OK, then it is something about ClearOS that is tripping you up... but read below first.

    ASpeed is not just a chipset - it is a SoC - a complete ARM processor system that runs independently of the main processor, usually with its own NIC for remote access, which monitors the main system, performs a number of useful functions such as powering up the main system, remote installing an OS on the main system, monitoring the main system health such as temperature, fans etc. Very useful for enterprise administrators to control systems all over the world from a central location. The graphics in the SoC is very basic - 2D only. ASpeed have a driver to get the best from the graphics for some OS... Intel also supplies a special graphics driver for its server boards when using Redhat V7 - see Here for an older (v7.3) sample giving an idea of the requirements...

    Note also that some servers may require setting certain kernel parameters eg "acpi=force" or black-listing a driver...

    Sorry - cannot be of much more help. I have been retired now for over 5 years and no longer "in the game". However, if you want to run server hardware and use all its fuctions, you probably need to be a "server" admininstator :p
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 03 2019, 02:33 AM - #Permalink
    Resolved
    0 votes
    Simply mentioned the Intel case to prompt you to see if MSI had similar requirements for your "222" board (CSM-C222-89?)... Just did a search and all the links to the detailed information about this board on the MSI site. None worked (404) - old discontinued board? Worth contacting MSI support? Maybe you already have...

    ASpeed have a 'ASPEED Graphics Linux/FreeBSD/Solaris Package' available - maybe worth investigating if ClearOS is using the ASpeed SoC in the ClearOS distribution... What graphics driver is ClearOS loading? This may provide the clue as to which Graphics ClearOS is using.

    when the integrated VGA on the CPU is used

    Technically with the Intel Xeon E3-1200 v3 series processors the VGA graphics is provided by the Intel "222" PCH which is part of the two-chip package. Follow several CentOS forums - and never seen this type of graphics problem mentioned within those forums...Good Luck...
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, January 06 2019, 07:05 PM - #Permalink
    Resolved
    0 votes
    Thanks Tony,

    For you or anyone else following, I gave up on the subject MB and used a more consumer oriented one for my server...all is now OK there. But I did put the subject board into another case and have been experimenting with it. Whatever the issue is with video, it does NOT occur under CentOS 7. Interesting.

    While ClearOS definitely shifts video modes to a tiny font (and I did use nomodeset), CentOS leaves it in the large character mode and boots with no loss of video. There is something different between them. I thought CentOS would be a good "almost ClearOS" experiment. By the way, video does return after about 5 minutes, and I think the system is basically working then. Very repeatable. I don;t know what would cauase the video to eventually recover.

    Looking through logs has not given me a clue. I don't know what video driver ClearOS is using, but I would be happy to check if someone can tell me how.

    I tried loading the ASPEED driver but instructions with it are very poor. When I got the .sh to run, I received an error message with the instruction to "install manually". Note that the ASPEED package (two chips) includes not only the IPMI SoC, but also a VGA solution and other IO.

    Thanks,
    Drew VS

    Tony Ellis wrote:

    Simply mentioned the Intel case to prompt you to see if MSI had similar requirements for your "222" board (CSM-C222-89?)... Just did a search and all the links to the detailed information about this board on the MSI site. None worked (404) - old discontinued board? Worth contacting MSI support? Maybe you already have...

    ASpeed have a 'ASPEED Graphics Linux/FreeBSD/Solaris Package' available - maybe worth investigating if ClearOS is using the ASpeed SoC in the ClearOS distribution... What graphics driver is ClearOS loading? This may provide the clue as to which Graphics ClearOS is using.

    when the integrated VGA on the CPU is used

    Technically with the Intel Xeon E3-1200 v3 series processors the VGA graphics is provided by the Intel "222" PCH which is part of the two-chip package. Follow several CentOS forums - and never seen this type of graphics problem mentioned within those forums...Good Luck...
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 07 2019, 04:08 AM - #Permalink
    Resolved
    0 votes
    Drew, would have thought the output of "lsmod" would have provided a clue...
    Using it on the systems here shows a mixture of nouveau, i915 and radeon
    Incidentally, what board are you now using for the server - if you don't mind me asking...

    Edit: There are some nice utilities around to provide this and more information if you take the time to install the required utilities.. e.g. HW Probe
    An example of one of the systems here Linux Workstation - shows an i915 under devices...
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, January 09 2019, 08:41 PM - #Permalink
    Resolved
    0 votes
    Thanks Tony,

    I have left that system set up and will follow your advice on some of those utilities as a learning tool. Thanks for the help...I don't mean to sound helpless, I just usually need a push in the right direction from a software tools standpoint. I'm a hardware guy (EE).

    The board I ended up using for the server was a used ASRock IMB-181 I had around. This is a commercial imbedded application board based on socket LGA1150 and Q87 chipset. Dual Intel LAN, old fashioned VGA port plus HDMI, and a pile of serial ports. So pretty optimal for this. I put a reclaimed Xeon in it. No issues at all so far.

    Cheers,
    Drew

    Tony Ellis wrote:

    Drew, would have thought the output of "lsmod" would have provided a clue...
    Using it on the systems here shows a mixture of nouveau, i915 and radeon
    Incidentally, what board are you now using for the server - if you don't mind me asking...

    Edit: There are some nice utilities around to provide this and more information if you take the time to install the required utilities.. e.g. HW Probe
    An example of one of the systems here Linux Workstation - shows an i915 under devices...
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, January 09 2019, 09:35 PM - #Permalink
    Resolved
    0 votes
    OK - looked up that ASRock board - nice - but a bit pricey for a retired guy like me...

    My roots are also in hardware - the 1970s installing and maintaining IBM System 360/370 mainframes. Loved the model 145 - with all the switches and lights on the console you could single step the CPU and read and see the changes to the contents of memory, registers, ALU etc - very instructive... 145 Console Could also write programs on punch cards and load them from the card reader and watch your program run a single instruction at a time... Programming using punch cards...
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 14 2019, 07:11 PM - #Permalink
    Resolved
    0 votes
    You may have a driver that is specifically tuned to an old ABI. What ClearOS media are you using to install? You need to make sure that you are using ClearOS 7.5 release media (or later). You can also pass parameters to make your install text only as well as simply scripting the install with a .ks file. Here is an example of one I've used before on a system where the recovery partition contained the ISO and the ks file here:


    cat scripts/clearos/install.ks


    ################################################
    # MAIN Process
    ################################################
    #version=.001
    # System authorization information
    auth --enableshadow --passalgo=sha512

    # Keyboard layouts
    keyboard --vckeymap=us --xlayouts='us'
    # System language
    lang en_US.UTF-8

    # Automatically reboot when finished
    reboot

    # Root password
    #uncomment to set to 'password'
    #rootpw --iscrypted $6$VqbYdwIsrUcu74Xd$6iTnlg1ifx16wfvGyL1Q.Wkrj5BXPnfpV5/fLYeWC0tcwJ3JFscQO/TBNUL8IPFw4f.c8s.h1m6k3NEC8EAcK0
    #generated with: echo 'import crypt,getpass; print crypt.crypt(getpass.getpass(), "MySuperSecretPassword")' | python -
    rootpw --iscrypted $xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/

    # System services
    services --enabled="chronyd"
    # System timezone
    timezone --utc Etc/UTC
    # Set Text Install
    text

    ### ## Network options (created in pre-script)
    %include /tmp/ks.network

    ## Volume options (created in pre-script)
    %include /tmp/ks.volumes

    ################################################
    # MAIN Process - End - Begin Phase Definitions
    ################################################


    ################################################
    # Packages Process
    ################################################
    %packages
    @base
    @core

    ## Optional packages
    %include /tmp/ks.packages

    %end
    ################################################
    # Packages Process End
    ################################################



    ################################################
    # Anaconda Process - mostly unused for now
    ################################################
    %anaconda
    %end
    ################################################
    # Anaconda Process End
    ################################################


    %pre --interpreter=/bin/bash

    ## Ensure files exist
    touch /tmp/ks.network /tmp/ks.packages /tmp/ks.volumes

    ## Remove Ubuntu Core or previous ClearOS partitions
    parted /dev/mmcblk0 rm 4
    parted /dev/mmcblk0 rm 3
    parted /dev/mmcblk0 rm 2

    ## Set flags and variables used in rest of pre script
    NICS=( $(ls -d /sys/class/net/[ep]* | sed -e 's,.*/,,g' | sort) )
    if grep -q '\bpreserve\b' /proc/cmdline; then preserve=true; else preserve=false; fi

    # Dell IoT
    rm -rf /tmp/ks.volumes
    touch /tmp/ks.volumes
    echo "ignoredisk --drives=mmcblk0boot0,mmcblk0boot1,mmcblk0rpmb" > /tmp/ks.volumes
    cat << __EOF__ >> /tmp/ks.volumes
    zerombr
    bootloader --location=mbr --boot-drive=mmcblk0 --driveorder=mmcblk0
    clearpart --linux
    part /boot/utilities --fstype="ext4" --onpart=mmcblk0p1 --noformat --label=ESP
    part /boot/efi --size=64 --fstype="efi" --ondisk=mmcblk0 --fsoptions="umask=0077,shortname=winnt" --label=system-boot
    part swap --size=2048 --ondisk=mmcblk0
    part / --fstype=ext4 --size=22000 --grow --ondisk=mmcblk0
    __EOF__

    serialnumber=$(dmidecode | sed -n -e '/System Information/,$p' | sed -e '/^$/,$d' | grep "Serial Number: " | awk '{ print $3 }')
    if [ "${serialnumber}" = "" ]; then installhostname=${serialnumber}; fi
    [[ $installhostname =~ ^[a-z][A-Z][0-9]+$ ]] && true || installhostname=system


    if [ ${#NICS[@]} -gt 1 ]
    then
    cat << __EOF__ >> /tmp/ks.network
    network --onboot yes --device p4p1 --bootproto dhcp
    network --onboot yes --device p4p2 --bootproto static --ip 172.22.23.1 --netmask 255.255.255.0 --hostname ${installhostname}.domain.lan
    __EOF__
    else
    cat << __EOF__ >> /tmp/ks.network
    network --onboot yes --device p4p1 --bootproto dhcp
    __EOF__
    fi
    if [ ${#NICS[0]}="wwp0s20u3" ]
    then
    cat << __EOF__ >> /tmp/ks.network
    network --onboot no --device wwp0s20u3 --bootproto dhcp
    __EOF__



    %end


    ################################################
    # Post-install processes
    ################################################
    %post --interpreter=/bin/bash

    ## Set flags and variables used in rest of post script
    NICS=( $(ls -d /sys/class/net/[e*|p\d+p*] | sed -e 's,.*/,,g' | sort) )
    distname=$(awk '{ print $1 }' /etc/system-release | sed 's,\([a-z]\)OS$,\1BOX,')

    ## Setup bind mounts for centralized data support
    #cat << __EOF__ >> /etc/fstab
    #
    #/store/data0/live/server1/home /home none bind,rw 0 0
    #/store/data0/live/server1/imap /var/spool/imap none bind,rw 0 0
    #/store/data0/live/server1/mysql /var/lib/mysql none bind,rw 0 0
    #/store/data0/live/server1/root-support /root/support none bind,rw 0 0
    #/store/data0/live/server1/samba-drivers /var/samba/drivers none bind,rw 0 0
    #/store/data0/live/server1/samba-netlogon /var/samba/netlogon none bind,rw 0 0
    #/store/data0/live/server1/samba-profiles /var/samba/profiles none bind,rw 0 0
    #/store/data0/live/server1/shares /var/flexshare/shares none bind,rw 0 0
    #/store/data0/live/server1/www-cgi-bin /var/www/cgi-bin none bind,rw 0 0
    #/store/data0/live/server1/www-default /var/www/html none bind,rw 0 0
    #/store/data0/live/server1/www-virtual /var/www/virtual none bind,rw 0 0
    #__EOF__

    ## Create root support directory
    mkdir /root/support
    chown root:root /root/support
    chmod 750 /root/support

    ## Create samba directories (if necessary)
    #if [ -d /var/samba ]; then
    # mkdir -p /var/samba/{drivers,netlogon,profiles}
    # chown 302:1000513 /var/samba/{drivers,netlogon,profiles}
    # chmod 2755 /var/samba/{drivers,netlogon,profiles}
    # chmod g+w /var/samba/profiles
    #fi

    ## Create and fix up owner/permissions on bind mounts
    #grep '^/store/.*bind' /etc/fstab | while read dest src junk
    #do
    # if [ -d $src ]; then
    # mkdir -p $dest
    # chown --reference=$src $dest
    # chmod --reference=$src $dest
    # elif [ -d $dest ]; then
    # mkdir -p $src
    # chown --reference=$dest $src
    # chmod --reference=$dest $src
    # else
    # sed -i -e "s,^${dest},#delete,;/#delete/d" \
    # /etc/fstab
    # fi
    #done

    ## Correct domain name in dnsmasq
    sed -i -e 's/^domain=.*/domain=domain.lan/' \
    /etc/dnsmasq.conf

    ## Add nameservers for dns resolution
    cat << __EOF__ >> /etc/resolv.conf
    nameserver 8.8.8.8
    nameserver 8.8.4.4
    __EOF__

    ## make sure dhcp doesn't wipe out dns settings
    sed -i -e '$aPEERDNS=no' \
    /etc/sysconfig/network-scripts/ifcfg-${NICS[0]}

    if [ ${#NICS[@]} -gt 1 ]; then
    ## Create management dhcp range
    cat << __EOF__ > /etc/dnsmasq.d/dhcp.conf
    dhcp-option=p4p2,1,255.255.255.0
    dhcp-option=p4p2,28,172.22.23.255
    dhcp-option=p4p2,3,172.22.23.1
    dhcp-option=p4p2,6,172.22.23.1
    dhcp-range=p4p2,172.22.23.100,172.22.23.254,12h
    read-ethers
    __EOF__
    fi

    ## Fixup gateway
    [[ $(grep -m1 GATEWAYDEV /etc/sysconfig/network) =~ \"wwp[0-9a-z]+\"$ ]] && { NICNAME=$(grep -m1 GATEWAYDEV /etc/sysconfig/network | awk -F\" '{ print $2 }'); sed -i "s/$NICNAME/p4p1/g" /etc/sysconfig/network; }
    # "

    [[ $(grep -m1 EXTIF /etc/clearos/network.conf) =~ wwp[0-9a-z]+ && ! $(grep -m1 EXTIF /etc/clearos/network.conf) =~ p4p1 ]] && { EXTNAME=$(grep -m1 EXTIF /etc/clearos/network.conf | awk -F\" '{ print $2 }'); sed -i "s/$EXTNAME/p4p1 $EXTNAME/g" /etc/clearos/network.conf; }
    # "

    ## Populate SSH keys and other files from image
    mkdir -p /mnt/installmount
    mount /dev/mmcblk0p1 /mnt/installmount

    while read entry; do
    file=$(echo ${entry} | awk -F, '{ print $1 }')
    fileperm=$(echo ${entry} | awk -F, '{ print $2 }')
    dir=$(echo ${entry} | awk -F, '{ print $3 }')
    dirperm=$(echo ${entry} | awk -F, '{ print $4 }')
    mkdir -p ${dir} && chmod ${dirperm} ${dir} && cp /mnt/installmount/files/image/${file} ${dir} && chmod ${fileperm} ${dir}/${file}
    done </mnt/installmount/files/MANIFEST
    sync
    umount /mnt/installmount
    rmdir /mnt/installmount

    #Cleanup

    %end
    #
    ###############################################
    # Post-install processes - Finished
    ################################################
    The reply is currently minimized Show
Your Reply