Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  (solved) kernel 4.17  (Read 7612 times)

Offline titan

  • User
  • Posts: 312
Re: kernel 4.17
« Reply #15 on: 2018/06/15, 10:26:18 »
Just tried 4.17.1-towo.4 still no joy  :(

Code: [Select]
ian@sid2:~$ journalctl -b -1
-- Logs begin at Sat 2018-05-05 12:47:44 BST, end at Fri 2018-06-15 09:21:28 BST. --
Jun 15 09:19:06 sid2 kernel: Linux version 4.17.1-towo.4-siduction-amd64 (towo@siduction.org) (gcc version 7.3.0 (Debian 7.3.0-21)) #1
Jun 15 09:19:06 sid2 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.17.1-towo.4-siduction-amd64 root=UUID=6782f1a8-05e4-4d77-addd-bb2
Jun 15 09:19:06 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun 15 09:19:06 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun 15 09:19:06 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun 15 09:19:06 sid2 kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jun 15 09:19:06 sid2 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Jun 15 09:19:06 sid2 kernel: e820: BIOS-provided physical RAM map:
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000003ffffff] usable
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x0000000004000000-0x0000000004009fff] ACPI NVS
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000000400a000-0x0000000009bfffff] usable
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x0000000009c00000-0x0000000009ffffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000affffff] usable
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000000b020000-0x000000009a598fff] usable
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000009a599000-0x000000009a6b0fff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000009a6b1000-0x000000009a6cbfff] ACPI data
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000009a6cc000-0x000000009a7cefff] usable
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000009a7cf000-0x000000009ab86fff] ACPI NVS
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000009ab87000-0x000000009b8abfff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000009b8ac000-0x000000009b94cfff] type 20
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000009b94d000-0x000000009dffffff] usable
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x000000009e000000-0x00000000dfffffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000fd800000-0x00000000fdffffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jun 15 09:19:06 sid2 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021f33ffff] usable
Jun 15 09:19:06 sid2 kernel: NX (Execute Disable) protection: active
Jun 15 09:19:06 sid2 kernel: efi: EFI v2.60 by American Megatrends
Jun 15 09:19:06 sid2 kernel: efi:  ACPI 2.0=0x9a6b3000  ACPI=0x9a6b3000  SMBIOS=0x9b81a000  SMBIOS 3.0=0x9b819000  ESRT=0x97eb6018  MEM
Jun 15 09:19:06 sid2 kernel: SMBIOS 3.1.1 present.
Jun 15 09:19:06 sid2 kernel: DMI: System manufacturer System Product Name/PRIME B350M-E, BIOS 4011 04/19/2018
Jun 15 09:19:06 sid2 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jun 15 09:19:06 sid2 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jun 15 09:19:06 sid2 kernel: e820: last_pfn = 0x21f340 max_arch_pfn = 0x400000000
Jun 15 09:19:06 sid2 kernel: MTRR default type: uncachable
Jun 15 09:19:06 sid2 kernel: MTRR fixed ranges enabled:
Jun 15 09:19:06 sid2 kernel:   00000-9FFFF write-back
Jun 15 09:19:06 sid2 kernel:   A0000-BFFFF write-through
Jun 15 09:19:06 sid2 kernel:   C0000-FFFFF write-protect
Jun 15 09:19:06 sid2 kernel: MTRR variable ranges enabled:
Jun 15 09:19:06 sid2 kernel:   0 base 000000000000 mask FFFF80000000 write-back
Jun 15 09:19:06 sid2 kernel:   1 base 000080000000 mask FFFFC0000000 write-back
Jun 15 09:19:06 sid2 kernel:   2 base 0000C0000000 mask FFFFE0000000 write-back
Jun 15 09:19:06 sid2 kernel:   3 disabled
Jun 15 09:19:06 sid2 kernel:   4 disabled
Jun 15 09:19:06 sid2 kernel:   5 disabled
Jun 15 09:19:06 sid2 kernel:   6 disabled
Jun 15 09:19:06 sid2 kernel:   7 disabled
Jun 15 09:19:06 sid2 kernel: TOM2: 0000000220000000 aka 8704M
Jun 15 09:19:06 sid2 kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
Jun 15 09:19:06 sid2 kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
Jun 15 09:19:06 sid2 kernel: e820: last_pfn = 0x9e000 max_arch_pfn = 0x400000000
Jun 15 09:19:06 sid2 kernel: esrt: Reserving ESRT space from 0x0000000097eb6018 to 0x0000000097eb6050.
lines 1-67


DuckHunting

  • Guest
Re: kernel 4.17
« Reply #16 on: 2018/06/16, 14:56:20 »
Titan,

Just wanted to let you know that you are not alone. I am using a RX470 AMD GPU. My screen freezes during boot with the most recent kernels. The last 4.17-Kernel working for me is 4.17.1-towo.1-siduction-amd64.

Code: [Select]
System:    Host: linux Kernel: 4.17.1-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.12.5           Distro: siduction 17.1.0 Patience - kde - (201703051755)
CPU:       Quad Core: Intel Core i7-7700 type: MT MCP speed: 800 MHz min/max: 800/4200 MHz
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480] driver: amdgpu v: kernel
           Display: x11 server: X.Org 1.20.0 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa
           resolution: 3840x2160~60Hz
           OpenGL:
           renderer: AMD Radeon RX 480 Graphics (POLARIS10 DRM 3.25.0 4.17.1-towo.1-siduction-amd64 LLVM 6.0.0)
           v: 4.5 Mesa 18.1.1
Drives:    HDD Total Size: 10.47 TiB used: 1.15 TiB (11.0%)
Info:      Processes: 243 Uptime: 1m Memory: 15.62 GiB used: 1.44 GiB (9.2%) Shell: bash inxi: 3.0.12

I had the same boot failure / screen freezing issue with the 4.15-Kernel series (see https://forum.siduction.org/index.php?topic=7077.0). No 4.15-Kernel worked for me. 4.16 and 4.17 did, until 4.17.1-towo.1-siduction-amd64.
I am not sure what is causing it.

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.920
Re: kernel 4.17
« Reply #17 on: 2018/06/17, 12:45:29 »
I don't have a clue, what's going wrong. The only AMD system i have available here does not have any problem.
Code: [Select]
towo@Thinkpad:~$ inxi -SG
System:    Host: Thinkpad Kernel: 4.17.1-towo.4-siduction-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.4
           Distro: siduction 18.2.0 Patience - xfce - (201803080000)
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R6/R7 Graphics] driver: radeon v: kernel
           Card-2: Advanced Micro Devices [AMD/ATI] Jet PRO [Radeon R5 M230] driver: radeon v: kernel
           Display: x11 server: X.Org 1.20.0 driver: ati,radeon unloaded: fbdev,modesetting,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: AMD KAVERI (DRM 2.50.0 4.17.1-towo.4-siduction-amd64 LLVM 6.0.0)
           v: 4.5 Mesa 18.1.1
But that's radeon, not amdgpu. The latest kernel in our repo is equal to the aptosid kernel, which i have builded at least for testing. But since i do not have any polaris or vega hardware, especialy no Ryzen G, i can't test anything myself.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

DuckHunting

  • Guest
Re: kernel 4.17
« Reply #18 on: 2018/06/18, 14:54:43 »
Thank you, towo. That is well understood.

My issue appears to relate to the outdated firmware-amd-graphics package of August 2017 in sid and the fact that any newer firmware from github does not seem to resolve the problem. My hope is that a newer firmware will eventually enter sid which fixes the issue.

Offline titan

  • User
  • Posts: 312
Re: kernel 4.17
« Reply #19 on: 2018/06/18, 15:26:07 »
If you don't have a clue Towo then there is little hope for the rest of us. I will be happy as long as the rc3 keeps working until a better solution is found.

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.920
Re: kernel 4.17
« Reply #20 on: 2018/06/18, 15:37:54 »
At the moment a new kernel build is running for 4.17.2. In that build the kernelconfig from 4.17-rc3 is used. You are saying, that kernel was working. If the new kernel is not working, there must be a regression in the upstream kernel itself.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline titan

  • User
  • Posts: 312
Re: kernel 4.17
« Reply #21 on: 2018/06/18, 22:28:19 »
Just tried 4.17.2 it does boot     :D    but only into 640 x 480 with no other option available.   :(   PC boots back into rc3 fine.

Offline titan

  • User
  • Posts: 312
Re: kernel 4.17
« Reply #22 on: 2018/06/19, 10:42:53 »
journalctl -b -1 for 4.17.2-towo2

Code: [Select]
ian@sid2:~$ journalctl -b -1
-- Logs begin at Sat 2018-05-05 12:47:44 BST, end at Tue 2018-06-19 09:29:13 BST. --
Jun 19 09:26:34 sid2 kernel: Linux version 4.17.2-towo.2-siduction-amd64 (towo@siduction.org) (gcc version 7.3.0 (Debian 7.3.0-23)) #1 SMP siduction 4.17-8 (2018-06-18
Jun 19 09:26:34 sid2 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.17.2-towo.2-siduction-amd64 root=UUID=6782f1a8-05e4-4d77-addd-bb28b77c32ea ro quiet resume=UUID=2
Jun 19 09:26:34 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jun 19 09:26:34 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jun 19 09:26:34 sid2 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jun 19 09:26:34 sid2 kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jun 19 09:26:34 sid2 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Jun 19 09:26:34 sid2 kernel: e820: BIOS-provided physical RAM map:
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000003ffffff] usable
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x0000000004000000-0x0000000004009fff] ACPI NVS
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000000400a000-0x0000000009bfffff] usable
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x0000000009c00000-0x0000000009ffffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000affffff] usable
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000000b020000-0x000000009a598fff] usable
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000009a599000-0x000000009a6b0fff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000009a6b1000-0x000000009a6cbfff] ACPI data
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000009a6cc000-0x000000009a7cefff] usable
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000009a7cf000-0x000000009ab86fff] ACPI NVS
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000009ab87000-0x000000009b8abfff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000009b8ac000-0x000000009b94cfff] type 20
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000009b94d000-0x000000009dffffff] usable
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x000000009e000000-0x00000000dfffffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000fd800000-0x00000000fdffffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jun 19 09:26:34 sid2 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021f33ffff] usable
Jun 19 09:26:34 sid2 kernel: NX (Execute Disable) protection: active
Jun 19 09:26:34 sid2 kernel: efi: EFI v2.60 by American Megatrends
Jun 19 09:26:34 sid2 kernel: efi:  ACPI 2.0=0x9a6b3000  ACPI=0x9a6b3000  SMBIOS=0x9b81a000  SMBIOS 3.0=0x9b819000  ESRT=0x97eb6018  MEMATTR=0x97f1c018
Jun 19 09:26:34 sid2 kernel: SMBIOS 3.1.1 present.
Jun 19 09:26:34 sid2 kernel: DMI: System manufacturer System Product Name/PRIME B350M-E, BIOS 4011 04/19/2018
Jun 19 09:26:34 sid2 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jun 19 09:26:34 sid2 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jun 19 09:26:34 sid2 kernel: e820: last_pfn = 0x21f340 max_arch_pfn = 0x400000000
Jun 19 09:26:34 sid2 kernel: MTRR default type: uncachable
Jun 19 09:26:34 sid2 kernel: MTRR fixed ranges enabled:
Jun 19 09:26:34 sid2 kernel:   00000-9FFFF write-back
Jun 19 09:26:34 sid2 kernel:   A0000-BFFFF write-through
Jun 19 09:26:34 sid2 kernel:   C0000-FFFFF write-protect
Jun 19 09:26:34 sid2 kernel: MTRR variable ranges enabled:
Jun 19 09:26:34 sid2 kernel:   0 base 000000000000 mask FFFF80000000 write-back
Jun 19 09:26:34 sid2 kernel:   1 base 000080000000 mask FFFFC0000000 write-back
Jun 19 09:26:34 sid2 kernel:   2 base 0000C0000000 mask FFFFE0000000 write-back
Jun 19 09:26:34 sid2 kernel:   3 disabled
Jun 19 09:26:34 sid2 kernel:   4 disabled
Jun 19 09:26:34 sid2 kernel:   5 disabled
Jun 19 09:26:34 sid2 kernel:   6 disabled
Jun 19 09:26:34 sid2 kernel:   7 disabled
Jun 19 09:26:34 sid2 kernel: TOM2: 0000000220000000 aka 8704M
Jun 19 09:26:34 sid2 kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT 
Jun 19 09:26:34 sid2 kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
Jun 19 09:26:34 sid2 kernel: e820: last_pfn = 0x9e000 max_arch_pfn = 0x400000000


Offline melmarker

  • User
  • Posts: 2.799
    • g-com.eu
Re: kernel 4.17
« Reply #23 on: 2018/06/19, 17:14:27 »
@titan - we have lost all hope too - for meaningful bug reports. I'll try to translate yours into something meaningful:

The machine starts fine without any problems. Grub is shown and work fine. The only annoying thing is that the X server in the current versions don't work well with my graphic card/built in graphics.

That would give us the chance to say: Shit happend, your hardware plays not well with the currently available things - if no other thing work, please blacklist the radeon/amdgpu stuff or deinstall it and use plain xvesa instead until these things are fixed.

Edit: But the bug - or the situations that triggered the bug for some fresh installations have a very positive side effect - i will write a bug against calamares - god damn, i really want the updates and upgrades within the installation optional - i only had to check first if such a switch exists. Esp. in rolling cutting and bleeding edge distributions sometimes auto-updating a fresh installations isn't the thing one really want.
« Last Edit: 2018/06/19, 17:23:13 by melmarker »
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

Offline titan

  • User
  • Posts: 312
Re: kernel 4.17
« Reply #24 on: 2018/06/19, 17:34:51 »
melmarker your translation failed, try reading the theads again. I am not a dev just a user I appreciate all the work and help I get from this forum. if you feel I have some other information I can supply to try to help I am very happy to do that but you will need to tell me what you need. The problem is the current kernel and video driver amdgpu ( the only one for Ryzen) do not work. I have spent hours   Googling looking for a solution and many others have had this problem although it seems many now find kernel 4.17.0 kernel with my mobo and bios are stable and work OK with Ryzen 5 2400G but not siduction so we are trying to find a solution.
Also why do you suggest I use xvisa when I have said several times kernel rc3 work fine with amdgpu

Offline melmarker

  • User
  • Posts: 2.799
    • g-com.eu
Re: kernel 4.17
« Reply #25 on: 2018/06/19, 18:37:37 »
i think i can read and translate things in the very most situations just fine. You have several problems that are all not primary related to the kernel. Let's try to list them up:
* The iso boots, you get a working graphical environment and can install - fine.
One problem: within the installation there run some upgrades and throw in a new X and maybe the new kernel with modified drivers. Result: Not so good user experience with the installed system.
it would help to have a full inxi -v7 output of the live system - please use our paste service or a github gist.

* I recommend xvesa because it is the lowest common nominator for all graphics - it might be that the normal modesetting kernel just works too - but the amdgpu driver is used instead, i guess i linked the releveant phoronix thread with the maybe helpful patches in the driver - not a thing a user should do.

* And yes, i differ between boot problems and display problems of any kind. For me a system is running absolutly fine as long the kernel starts and i get a kind of working prompt. Display problems are secondary - they can  be solved if the rest of the system is working fine.
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

Offline melmarker

  • User
  • Posts: 2.799
    • g-com.eu
Re: kernel 4.17
« Reply #26 on: 2018/06/19, 21:36:27 »
https://www.phoronix.com/scan.php?page=article&item=ryzen3-2200g-vega8&num=4 - regarding moronix one should be able to run the ryzens vega with the vulkan driver - lucky me, no hardware to test this.
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

Offline titan

  • User
  • Posts: 312
Re: kernel 4.17
« Reply #27 on: 2018/06/19, 21:38:21 »
From your list
iso boots into working graphical environment. no it did not neither did a later iso you supplied via irc. I detailed all the install problems in another thread. I eventually got a working system using the rc3 from experimental.
there have been quite a few updates since then including X and mesa but rc3 continues to work OK
towo says there have not been any changes to amdgpu since rc3 but no kernel since then will fully boot into a working graphical desktop.
towo has just built 4.17.2 using the kernel build code from rc3 and this does fully boot but only with 640 x480 graphics no other option is available.
There is not really much I can do only report the problems and whatever information that may help.
here is inxi -v7 as requested. it is not a large file.

Code: [Select]
ian# inxi -v7
System:    Host: sid2 Kernel: 4.17.0-rc3-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0
           Desktop: KDE Plasma 5.12.5 tk: Qt 5.10.1 dm: sddm
           Distro: siduction 18.2.0 Patience - kde - (201803072323)
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B350M-E v: Rev X.0x serial: 170501830700266
           UEFI: American Megatrends v: 4011 date: 04/19/2018
Memory:    Array-1: capacity: 256 GiB note: check slots: 2 EC: None max module size: 128 GiB note: est.
           Device-1: DIMM_A1 size: 4 GiB speed: 2400 MT/s type: DDR4
           detail: synchronous unbuffered (unregistered) bus width: 64 bits total: 64 bits manufacturer: N/A
           part-no: TEAMGROUP-UD4-2400 serial: 01040D66
           Device-2: DIMM_B1 size: 4 GiB speed: 2400 MT/s type: DDR4
           detail: synchronous unbuffered (unregistered) bus width: 64 bits total: 64 bits manufacturer: N/A
           part-no: TEAMGROUP-UD4-2400 serial: 01040D65
CPU:       Topology: Quad Core model: AMD Ryzen 5 2400G with Radeon Vega Graphics bits: 64 type: MT MCP
           arch: Zen L2 cache: 2048 KiB bogomips: 57493
           Speed: 1466 MHz min/max: 1600/3600 MHz Core speeds (MHz): 1: 1419 2: 1418 3: 1419 4: 1415 5: 1419
           6: 1418 7: 1509 8: 1596
           Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 bmi2 bpext clflush
           clflushopt clzero cmov cmp_legacy constant_tsc cpuid cr8_legacy cx16 cx8 de decodeassists extapic
           extd_apicid f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb irperf lahf_lm lbrv lm
           mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw
           overflow_recov pae pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold
           pge pni popcnt pse pse36 rdrand rdseed rdtscp rep_good sep sev sha_ni skinit smap smca sme smep sse
           sse2 sse4_1 sse4_2 sse4a ssse3 succor svm svm_lock syscall tce topoext tsc tsc_scale v_vmsave_vmload
           vgif vmcb_clean vme vmmcall wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
Graphics:  Card-1: AMD Raven Bridge [Radeon Vega Series / Radeon Vega Mobile Series] driver: amdgpu v: kernel
           bus ID: 08:00.0 chip ID: 1002:15dd
           Display: x11 server: X.Org 1.20.0 driver: amdgpu unloaded: fbdev,modesetting,vesa tty: N/A
           OpenGL: renderer: AMD RAVEN (DRM 3.25.0 4.17.0-rc3-siduction-amd64 LLVM 6.0.0) v: 4.5 Mesa 18.1.1
           compat-v: 3.1 direct render: Yes
Audio:     Card-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel v: kernel bus ID: 08:00.1
           chip ID: 1002:15de
           Card-2: Advanced Micro Devices [AMD] driver: snd_hda_intel v: kernel bus ID: 08:00.6
           chip ID: 1022:15e3
           Sound Server: ALSA v: k4.17.0-rc3-siduction-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: 2.3LK-NAPI
           port: f000 bus ID: 06:00.0 chip ID: 10ec:8168
           IF: enp6s0 state: up speed: 100 Mbps duplex: full mac: 10:7b:44:4d:b7:99
           IP v4: 192.168.1.214/24 scope: global broadcast: 192.168.1.255
           IP v6: fd90:ecee:dfdb::df1/64 scope: global
           IP v6: fd90:ecee:dfdb:0:127b:44ff:fe4d:b799/64 type: dynamic mngtmpaddr scope: global
           IP v6: fe80::127b:44ff:fe4d:b799/64 scope: link
           IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
           IP v4: 10.4.25.19/16 scope: global broadcast: 10.4.255.255
           IP v6: fe80::82e9:bd5e:d478:979d/64 virtual: stable-privacy scope: link
           WAN IP: 185.103.96.143
Drives:    HDD Total Size: 1.34 TiB used: 230.43 GiB (16.8%)
           ID-1: /dev/sda model: FCCT960M500SSD1 size: 894.25 GiB speed: 6.0 Gb/s serial: 14250C5FCB20
           rev: MU05 temp: 36 C scheme: GPT
           ID-2: /dev/sdb vendor: Crucial model: CT512MX100SSD1 size: 476.94 GiB speed: 6.0 Gb/s
           serial: 14500E0A424C rev: MU01 temp: 33 C scheme: MBR
           Message: No Optical or Floppy data was found.
RAID:      Message: No RAID data was found.
Partition: ID-1: / size: 870.26 GiB used: 17.49 GiB (2.0%) fs: ext4 dev: /dev/sda2 label: N/A
           uuid: 6782f1a8-05e4-4d77-addd-bb28b77c32ea
           ID-2: /boot/efi size: 299.4 MiB used: 256 KiB (0.1%) fs: vfat dev: /dev/sda1 label: N/A
           uuid: 866D-E7F2
           ID-3: /media/ian size: 468.45 GiB used: 212.94 GiB (45.5%) fs: ext4 dev: /dev/sdb1 label: N/A
           uuid: 9b1ee317-c6f0-4b0d-9bcc-e359f709a035
           ID-4: swap-1 size: 8.80 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 label: N/A
           uuid: 2018e83a-a247-44d0-ac84-0f93fb1d3c3f
Unmounted: Message: No unmounted partitions found.
USB:       Hub: 1:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002
           Device-1: Pixart Imaging Optical Mouse bus ID: 1:2 usb: 1.1 type: Mouse chip ID: 093a:2521
           Hub: 2:1 usb: 3.1 type: Full speed (or root) hub chip ID: 1d6b:0003
           Hub: 3:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002
           Device-2: Cherry CyMotion Expert Combo bus ID: 3:2 usb: 2.0 type: Keyboard chip ID: 046a:0021
           Hub: 4:1 usb: 3.1 type: Full speed (or root) hub chip ID: 1d6b:0003
           Hub: 5:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002
           Hub: 6:1 usb: 3.1 type: Full speed (or root) hub chip ID: 1d6b:0003
Sensors:   System Temperatures: cpu: 44.2 C mobo: N/A
           Fan Speeds (RPM): cpu: 0
Info:      Processes: 242 Uptime: 11h 08m Memory: 6.80 GiB used: 3.22 GiB (47.3%) Init: systemd v: 238
           runlevel: 5 Compilers: gcc: 7.3.0 alt: 7 Shell: bash (su) v: 4.4.23 running in: konsole inxi: 3.0.12


Offline titan

  • User
  • Posts: 312
Re: kernel 4.17
« Reply #28 on: 2018/06/19, 22:09:51 »
Thanks for the link, I have seen the phoronix article I dont think the Vulcan they mention is a driver but a games test renderer. The article say the amdgpu is needed
"Using the Vega graphics on the Ryzen 3 2200G or Ryzen 5 2400G will require a fairly updated Linux graphics stack, which won't be found out-of-the-box on most Linux distributions at this time: - The Linux 4.15 kernel is an absolute minimum requirement if using the open-source driver stack due to needing AMDGPU DC for Raven Ridge, which was only mainlined for this newly-released kernel. Linux 4.15 is a must but with Linux 4.16 are a number of Raven Ridge fixes. Linux 4.16 will be released as stable in April i "
There also is the AMD provided amdgpu-pro but at the moment I would prefer the open driver through Debian.
there was a link I posted upthread showing phoronix think the Ryzen 5 2400G is stable with kernel 4.17 ,amdgpu using my mobo and BIOS and mesa 18, it should all be working fine.
https://www.phoronix.com/scan.php?page=article&item=ryzen-2400g-may&num=1

fred108

  • Guest
Re: kernel 4.17
« Reply #29 on: 2018/07/19, 08:46:53 »
Hi all,
I have just started to use Siduction in the last week. I am a arch/manjaro user who just found Siduction as a replacement for tumbleweed on my spare hard drives. After having problems on the 4.17 kernel I am staying on the last 4.16 kernel as my needs are just exploratory and nothing else. Siduction has changed my former low impression of debian/ubuntu.