[Bug 101483] A10-8780P (Carrizo) + R7 M260/M265 does not boot without any "workaround" parameter.

[bugzilla-daemon@freedesktop.org]

[-- Attachment #1.1: Type: text/plain, Size: 3491 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=101483

--- Comment #16 from FFAB <lx@o2mail.de> ---

Testing amdgpu-pro dkms from amd.com 

as suggested by xorg(Ubuntu) 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639517/comments/30


Download: following  the direct link to the drive on site

https://support.amd.com/en-us/kb-articles/Pages/AMDGPU-PRO-Install.aspx





8.8.2017:

amdgpu-pro-17.30-458935.tar.gz  (for kernel 4.4 or 4.8)


27.08.2017:
amdgpu-pro-17.30-465504.tar.gz (for Ubuntu 16.04.3)



1. Testing amdgpu-pro-17.30-458935 - installed kernel  4.8.

Installing amdgpu-pro-17.30-458935 according link -and adding user to group
video 
After installing: logout.
Then - a Login wasn't possible:
login started - and was finished a short time later with login-screen.
Reboot without workaround parameters:
boot process started:
gray screen - flash - black screen - messages - splash screen - messages - read
in line:  maintenance or continue -> continue - error messages - stopped by
SysReq B - reboot without workaround parameter  - similar cycle.  stopped by
SysReq B.
Now reboot was not possible.
No item in EFI/esp. I tried to fix it using a live System and my "primary"
installation Kubuntu - it didn't work. So I reinstalled my "primary" System
Kubuntu.
Now  starting the test installation (workaround parameter nomodeset) failed -
file system repair of system and data partition.
I didn't repeat the test. I have no log files.


2017_09_15 - 2017_10_06
=======================

2. Testing amdgpu-pro-17.30-465504 - installed kernel  4.10.

I tested several times dkms in September and October 

A: Installing procedure
Playing back a saved system partition,

installing dkms according link- group video -> <actual user>.

A few times I installed the AMD proprietary microcode driver. 

After installing reboot (workaround parameter)
Login wasn't possible - a started login was finished with login screen.

B.Test

Boot without workaround parameter.
optional kernel parameter "noplymouth boot_delay=<up to 400>
As boot process was never finished, reboot using SysRq (-> C:)
Starting my "primary" installation Kubuntu and run fsck of the dkms system
partition,

C. results
The boot process was never finished;
reboot either SysRq + b or SysRq + r|e|i|s|u|b.
Results  were sometimes reproduced - but it was not predictable when they were.
Normally there was a never ending stream of messages incl. some error messages
or a loop of always the same messages - all these tests were stopped by SysRQ.
Some test runs ended with kernel panic - then a restart was only possible by
"hard off" (several seconds "power off" button).

The results of fsck also were not reproducible. Using SysRq + b : fsck shows
error messages.
Using SysRq + r|e|i|s|u|b: sometimes filesystem state was clean. Only in that
case boot runs of that installation were comparable. 

During some test runs (kernel parameter "boot_delay") I took series of photos -
but none of these series is complete (partly the messages on these photos are
not readable). I don't attach any.




A method how to redirect boot messages printed to the system console to a file
I didn't find, respectively I didn't manage to run bootlogd - available in the
repositories of Ubuntu; I couldn't find detailed tips, how to configurate 
bootlogd

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4609 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel