Dev1 Galaxy Forum / Ryzen only old kernel boots

Re: Ryzen only old kernel boots

dummy@example.com (wdt) — Fri, 02 Feb 2018 06:18:41 +0000

So I figured it out, there was no initrd.img for 4.14 or 4.9, and also no reference in the grub.cfg either
I completly removed and re-installed and grub

uname -a
Linux devuan 4.14.0-0.bpo.3-amd64 #1 SMP Debian 4.14.13-1~bpo9+1 (2018-01-14) x86_64 GNU/Linux

Re: Ryzen only old kernel boots

dummy@example.com (wdt) — Thu, 01 Feb 2018 23:41:34 +0000

OK, I'm really stupid.. Looking at it again, it is a kernel panic because can't find root fs, (thinks it is 0,0 ???)
(the gigabyte line misled me)
But 3.16 boots OK, also fedora, 4.14.14 and 4.14.11 (on same stick)

Install,, booted usb, changed repositories (to ascii), updated, installed

d@devuan:~$ ls -l /boot/vm*
-rw-r--r-- 1 root root 3128768 Apr 30 2017 /boot/vmlinuz-3.16.0-4-amd64
-rw-r--r-- 1 root root 4843280 Jan 14 18:48 /boot/vmlinuz-4.14.0-0.bpo.3-amd64
-rw-r--r-- 1 root root 4216608 Jan 4 06:12 /boot/vmlinuz-4.9.0-5-amd64

Edit: I should be more precise,, changed to ascii, updated, upgraded, install
I don't think it is anything to do with grub2, when in fedora grub-install,, same results
Before devuan I had mint which I wiped out to replace with devuan, no problem booting

Further,, earlier I tried adding insmod ahci into a stanza of grub,,
it did ugly but temporary things to my computer,, black screen but live keyboard
(Booting devuan 4.14)
CAD worked, but then there was no access to bios or restart of grub
A power off was needed to restore normal operation, button reset was not enough

Re: Ryzen only old kernel boots

dummy@example.com (fsmithred) — Thu, 01 Feb 2018 18:50:15 +0000

Ryzen needs kernel 4.10 or newer. You can get 4.14 from ascii-backports. But I'm confused about what you actually did. Did you upgrade your cpu on an existing installation?

Ryzen only old kernel boots

dummy@example.com (wdt) — Wed, 31 Jan 2018 19:54:47 +0000

I did an upgade to ascii (csm, not UEFI) before installing, because ryzen
But then it would not boot, hard hang at .53 sec
Trying all the alternatives, 3.16 would boot
first I thought it was that grub2 had root=UUID for 3.16 and root=/dev/sdb2 for 4 series
That was not it
From the 3.16 boot, this is where (I think) it fails,
I can't be sure because the trace takes the whole screen and is hard locked
(one of the few advantages of systemd)

1.004068] mpls_gso: MPLS GSO support
[ 1.004356] ------------[ cut here ]------------
[ 1.004359] WARNING: CPU: 0 PID: 1 at /build/linux-2PgYgH/linux-3.16.43/lib/kobject.c:210 kobject_add_internal+
0x242/0x3e0()
[ 1.004360] kobject: (ffff88040bac5140): attempted to be registered with empty name!
[ 1.004360] Modules linked in:
[ 1.004362] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.16.0-4-amd64 #1 Debian 3.16.43-2
[ 1.004363] Hardware name: Gigabyte Technology Co., Ltd. AB350M-D3H/AB350M-D3H-CF, BIOS F10 12/01/2017
[ 1.004364] 0000000000000000 ffffffff81514201 ffff88041cddbd18 0000000000000009
[ 1.004366] ffffffff81068877 ffff88040bac5140 ffff88041cddbd68 ffff880408961010
[ 1.004367] 0000000000000000 0000000000000000 ffffffff810688dc ffffffff81749ef8
[ 1.004368] Call Trace:
[ 1.004370] [] ? dump_stack+0x5d/0x78
[ 1.004373] [] ? warn_slowpath_common+0x77/0x90
[ 1.004375] [] ? warn_slowpath_fmt+0x4c/0x50
[ 1.004376] [] ? kobject_add_internal+0x242/0x3e0
[ 1.004378] [] ? kobject_add+0x65/0xb0
[ 1.004379] [] ? kmem_cache_alloc_trace+0x23f/0x470
[ 1.004381] [] ? kobject_create_and_add+0x2e/0x70
[ 1.004383] [] ? threshold_create_device+0x105/0x360
[ 1.004385] [] ? severities_debugfs_init+0x37/0x37
[ 1.004386] [] ? threshold_init_device+0x2f/0x45
[ 1.004388] [] ? do_one_initcall+0xcc/0x200
[ 1.004390] [] ? parse_args+0x238/0x470
[ 1.004392] [] ? kernel_init_freeable+0x15f/0x1e1
[ 1.004393] [] ? initcall_blacklist+0xb2/0xb2
[ 1.004395] [] ? rest_init+0x80/0x80
[ 1.004396] [] ? kernel_init+0xa/0xf0
[ 1.004398] [] ? ret_from_fork+0x58/0x90
[ 1.004399] [] ? rest_init+0x80/0x80
[ 1.004403] ---[ end trace 1f2ee60de12dfc50 ]---
[ 1.004404] kobject_create_and_add: kobject_add error: -22
[ 1.004520] registered taskstats version 1

Edit: I don't know if it makes a difference, this is on an older nvme stick