Results 1 to 7 of 7

Thread: Problems with new Hardware

  1. #1

    Question Problems with new Hardware

    Hi.

    I did recently changed the complete Hardware of my OpenSuse Leap 4.3 64bit Installation.

    The old Hardware was:
    - HP Compaq dc7600
    - Intel P4 650
    - Graphic Intel 945G GMCH (on-board)

    The new Hardware is:
    - ASUS z270-p Mainboard
    - Intel i5 7500
    - Graphic Intel HD Graphic (Integrated)

    The swap itself was mainly without any error. The new System was booting with the "old" disk immediately. It is fast and after 3 days running I haven't had any problem/freeze/crash. That's good news.

    Now the bad news:
    - I am unable to get Hardware Information via YAST. During the initialization process it hangs at "Framebuffers"
    - Running the command "hwinfo --framebuffer" also hangs (just says "> bios.4.2: mode info")
    - I have noticed, that moving the mouse sends some "crackles" to the audio output (constantly)

    If anyone has any idea where to look at or what else I have to do after the change it would really be of help. If you need any more information please let me know. And, please, apologize my english

    Thanks, Chris

  2. #2

    Default Re: Problems with new Hardware

    Quote Originally Posted by muech011 View Post
    - I am unable to get Hardware Information via YAST. During the initialization process it hangs at "Framebuffers"
    - Running the command "hwinfo --framebuffer" also hangs (just says "> bios.4.2: mode info")
    Forgot to mention: Both, the "hwinfo --framebuffer" and the YAST Hardware Information are consuming 100% on one of the cores.

  3. #3
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,287

    Default Re: Problems with new Hardware

    Did you run mkinird after the hardware change? Need that to discover new hardware

  4. #4

    Default Re: Problems with new Hardware

    Quote Originally Posted by gogalthorp View Post
    Did you run mkinird after the hardware change? Need that to discover new hardware
    Thanks for the answer. And yes, I did that. I was thinking there may be a problem since the new MoBo is UEFI booting. So I spent the last day with moving from MBR to GPT booting. Was a bit of a nightmare since there's allways stated "that's simple, just change your disk from mbr to gpt" but the only description I found was for UBUNTU and LEAP Live-DVDs are also difficult to get. Anyway: Change is completed, ran mkinitrd again -> same result. Here's the log of the mkinitrd, maybe it is of help:

    Code:
    I: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force --force-drivers "ahci thermal ata_piix ata_generic processor fan xennet xenblk" /boot/initrd-4.4.87-25-default 4.4.87-25-default
    I: *** Including module: bash ***
    I: *** Including module: systemd ***
    I: *** Including module: warpclock ***
    I: *** Including module: systemd-initrd ***
    I: *** Including module: i18n ***
    I: *** Including module: drm ***
    I: *** Including module: plymouth ***
    I: *** Including module: kernel-modules ***
    I: *** Including module: resume ***
    I: *** Including module: rootfs-block ***
    I: *** Including module: suse-btrfs ***
    I: *** Including module: suse-xfs ***
    I: *** Including module: terminfo ***
    I: *** Including module: udev-rules ***
    I: Skipping udev rule: 40-redhat.rules
    I: Skipping udev rule: 50-firmware.rules
    I: Skipping udev rule: 50-udev.rules
    I: Skipping udev rule: 91-permissions.rules
    I: Skipping udev rule: 80-drivers-modprobe.rules
    I: *** Including module: dracut-systemd ***
    I: *** Including module: haveged ***
    I: *** Including module: usrmount ***
    I: *** Including module: base ***
    I: *** Including module: fs-lib ***
    I: *** Including module: shutdown ***
    I: *** Including module: suse ***
    I: *** Including modules done ***
    I: *** Installing kernel module dependencies and firmware ***
    I: *** Installing kernel module dependencies and firmware done ***
    I: *** Resolving executable dependencies ***
    I: *** Resolving executable dependencies done***
    I: *** Hardlinking files ***
    I: *** Hardlinking files done ***
    I: *** Stripping files ***
    I: *** Stripping files done ***
    I: *** Generating early-microcode cpio image ***
    I: *** Constructing GenuineIntel.bin ****
    I: *** Store current command line parameters ***
    I: Stored kernel commandline:
    I: rd.driver.pre=ahci
    rd.driver.pre=thermal
    rd.driver.pre=ata_piix
    rd.driver.pre=ata_generic
    rd.driver.pre=processor
    rd.driver.pre=fan
    rd.driver.pre=xennet
    rd.driver.pre=xenblk
    I:  resume=UUID=38b9ce86-f26e-462e-b5c7-8b37565afe73
    I:  root=UUID=4d21173c-1822-4c24-bd55-1f909d962ed5 rootfstype=ext4 rootflags=rw,relatime,data=ordered
    I: *** Creating image file '/boot/initrd-4.4.87-25-default' ***
    I: *** Creating initramfs image file '/boot/initrd-4.4.87-25-default' done ***

  5. #5

    Default Re: Problems with new Hardware

    Hm, really no one has an idea?

  6. #6
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,287

    Default Re: Problems with new Hardware

    MBR and GPT are two different things MBR is a boot method GPT is a partitioning method. The old partitioning way is DOS. The new boot is EFI. When doing these low level type changes it is far easier to reinstall. The new Intel CPU/GPUs can be a problem and may require a newer kernel.

  7. #7

    Default Re: Problems with new Hardware

    Quote Originally Posted by gogalthorp View Post
    MBR and GPT are two different things MBR is a boot method GPT is a partitioning method. The old partitioning way is DOS. The new boot is EFI. When doing these low level type changes it is far easier to reinstall. The new Intel CPU/GPUs can be a problem and may require a newer kernel.
    Thanks for the answer. Yes, I have noticed the incompatibility between the Kaby Lake and the 4.4 Kernel of OpenSuse. From what I have read it should have been fixed with the backported kernel modules. I did anyway install the kernel

    Code:
    Linux SUSE-01 4.13.9-2.ge7d7106-default #1 SMP PREEMPT Mon Oct 23 09:44:25 UTC 2017 (e7d7106) x86_64 x86_64 x86_64 GNU/Linux
    I did the change of MBR/DOS to GPT/EFI because it is the first time that I have been in touch with an UEFI BIOS. So the main reason was to boot the system in UEFI-only mode. So it was a bit of education. The system is running pretty good. Fast and (what I can say after 10 days) reliable. The only things that do not work are:

    1. YAST -> BOOTLOADER (freezes if going to tab "kernel parameter")
    2. PC-speaker (line out is working, system beeps at POST so I asume speaker is connected corretly)
    3. YAST -> Hardware (stalled at "Framebuffer", the same with "hwinfo --framebuffer")


    So beside the experiences I had with moving the system from an older hardware to a new hardware just by swapping the disk, I also want to solve this problems.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •