|
Bugzilla – Full Text Bug Listing |
| Summary: | Kernel 4.19 did not boot and gives a black screen | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Seppe hoogzaad <seppe.hoogzaad> |
| Component: | Kernel | Assignee: | E-mail List <kernel-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | the .config used to compile the 4.20 kernel for the Dell D420 | ||
Bug 1116425 is also the same, looking at the posted video. I just tried it again with the latest kernel-pae-4.19.11-1.3.i686. This gives the same result. Black screen, and than a reboot. My bug is a duplicate of Bug 1120186. I just tried kernel-default-4.19.11-1.3.i586 as suggested in Bug 1120186. This kernel works with me also. Sorry, I should have looked in all the bugs.... *** This bug has been marked as a duplicate of bug 1120186 *** |
Created attachment 793716 [details] the .config used to compile the 4.20 kernel for the Dell D420 The kernel 4.19 did not boot, giving a black screen after a distribution update. I used the old 4.18 kernel to boot. This worked. I compiled the new 4.20 kernel myself. This worked. Since the kernels 4.18 and 4.20 both worked, i suspect that something in the .config of the 4.19 kernel is wrong. I can not boot the 4.19 kernel, so reading the /proc/config.gz is not possible for me. I therefore find it difficult to check this myself. I have included the .config i used to compile my working 4.20 kernel. This is a striped version of the .config of the 4.18 kernel. I have a Dell D420 with a Intel Mobile 945GM graphics controller, driven by the i915 kernel module. I use the X window, in case this might be relevant. Possible Duplicates: 1119621 I just bought a Dell Chromebook witch had a similar problem and might be a duplicate. The chromebook is a 64 bit machine, so this will get a separate bug.