|
Bugzilla – Full Text Bug Listing |
| Summary: | Radeon R7 Graphics [1002:130f] 15.2 build 581.2 Installer crash with certain combination of integrated graphics and monitor | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Walter Zimmer <walter.zimmer> |
| Component: | X.Org | Assignee: | E-mail List <xorg-maintainer-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <xorg-maintainer-bugs> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | jreidinger, snwint, walter.zimmer |
| Version: | Leap 15.2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
boot.txt (from supportconfig)
x.txt (from supportconfig) /var/log/messages from 581.2 (without nomodeset) /var/log/messages from 581.2 (with nomodeset) /var/log/Xorg.0.log from 581.2 (with nomodeset, after Yast started up) |
||
|
Description
Walter Zimmer
2020-02-24 15:45:22 UTC
Can you try to setup remote logging as described at [1] and attach such logs there? So we will see where crash happens ( hopefully). Thanks [1] https://en.opensuse.org/SDB:YaST_remote_logging_during_installation Tried the NFS thing, didn't work; had network up, ping and SSH to nfs server were working, firewall on server disabled. But mount said (after requesting nolock which I then provided): "requested protocol version or transport protocol not available." Then I gave up, version mismatch between identical distributions is unlikely, but I have no idea what the real error could be. Sorry for that! On the bright side: "nomodeset" helps to skip the crash and provides a blurry, but usable install screen. as nomodeset helps it looks like problem with graphical drivers which is more limited in installation environment. Steffen do you have idea how to more debug this issue? Looks like an xorg issue to me. Let's move this to the xorg team. Hmm. Since it crashes with installation kernel, but obviously not with the kernel on installed system, the issue might already be fixed assuming the kernel has been updated during installation to a newer release/version. This would mean a newer build would already fix the issue. Still it would be helpful for me to see some logfiles, so I know more about the hardware and kernel detectections. Could you install supportutils package, run supportconfig and provide the results here? Thanks! (In reply to Stefan Dirsch from comment #5) > Still it would be helpful for me to see some logfiles, so I know more about > the hardware and kernel detectections. Could you install supportutils > package, run supportconfig and provide the results here? Thanks! This on the installed system of course. :-) Created attachment 831633 [details]
boot.txt (from supportconfig)
Created attachment 831634 [details]
x.txt (from supportconfig)
That facilitates things :) Attached boot.txt and x.txt from the running system, I guess this is what you need. 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] Logfiles are from an older system, right? Kernel 4.12 doesn't sound like Leap 15.2 to me ... I propose to try again with a newer build. Build 595.1 apparently will ship/ships with 5.3.18-lp152.4.6. I don't know whether this is newer than the one on Build 581.2. I can't find images for this any longer. Sorry for the confusion! The system is indeed 15.1. But that one shows the same symptom (installer crashes, switch afterwards is fine), so I thought the hardware info should still be helpful. So I'll download the 585.1 this evening and try it... Maybe I'll try to copy the supportutils binary on a USB stick and execute on the install system (with startshell=1), since it seems to be a statically linked one. Hmm. Now I'm completely confused. Hardware information has been from the affected system you initially reported or not? I would have hoped for logs from the installed 15.2 system of build 581.2, since then I would also have seen the kernel information and could have told you if a newer build comes with a newer kernel ... only with an updated kernel it makes sense to test again ... but maybe you no longer have this system avalable. Using supportconfig on a USB stick may work. Not sure I ever have tried this before ... Created attachment 831739 [details]
/var/log/messages from 581.2 (without nomodeset)
Created attachment 831740 [details]
/var/log/messages from 581.2 (with nomodeset)
Created attachment 831741 [details]
/var/log/Xorg.0.log from 581.2 (with nomodeset, after Yast started up)
Hardware info has been from the system, but extracted via the installed 15.1, not the 15.2 beta. But it doesn't matter: I've put in the 581.2 stick again, supportconfig didn't work as it tries to read some config from /usr/lib, so in my desperation I copied the /var/log/messages from the normal boot (without nomodeset option), and then from a boot with the nomodeset option active (see attachments above). From this second boot which allowed Yast to start (because of nomodeset), I also attached the Xorg.0.log. I hope you can now extract all the information you need? Seems 581.2 comes with 5.3.18-lp152.4-default, where you still need "nomodeset". So I'm afraid Build 595.1 with 5.3.18-lp152.4.6 won't help either, but who knows ... No Problem, I'm happy to know that nomodeset saves me from getting into the basement to pull out my old monitor when I'll install the final 15.2. :) Anything else I can do? Already the installed system from 15.1 boots without nomodeset, so in general the support for this monitor is working since some time - just not in the 15.1/15.2 installer. So it seems the answer to the riddle is hidden in the xorg.0.log from the case where it's aborting. Maybe I'll try that NFS logging again... or maybe just plain to a USB stick? Ok. I suggest to try from time to time an updated installer. It still sounds weird to me that graphics on the installed system works but not with the installer. It should be the same driver. But indeed workaround for now is to install with nomodeset and then remove this kernel option again for the installed system. Ok, there is an Xorg.0.log and a YaST2/y2start.log on the stick. After the crash I waited for 5 mins and prayed the disk blocks make it to the stick, but unfortunately, both have exactly 0 bytes length, so no use. If there are any new ideas, please tell, in the meantime I'll try again when the official release is out, but I'm happy anyway. Thanks a lot! Yeah. Just let me know, whether it works with the final release. :-) I hope so ... Update ate my 15.2, so I installed new from the Build 632.2 iso and the installer worked flawless without need for nomodeset workaround. So it is as you predicted. :) Thanks a bunch! Happy to hear this. Thanks for confirmation! Considered fixed. |