View previous topic :: View next topic |
Author |
Message |
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Mon Jun 22, 2020 10:59 am Post subject: Xorg/intel Hangs on Black Screen with Blinking Cursor |
|
|
This is a message.
Last edited by TheScientist on Wed Jul 29, 2020 9:25 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54578 Location: 56N 3W
|
Posted: Mon Jun 22, 2020 12:56 pm Post subject: |
|
|
TheScientist,
Welcome to Gentoo
There are no errors in your Xorg.0.log file. It looks like X did not configure a display as it normally logs all the EDID data and that's missing.
Xorg has a lot of auto detection these days.
Rename your xorg.conf file so its not used then try Xorg again.
The missing EDID data suggests that there may be no display connected to the Intel GPU.
As you have two graphics cards, we need to know how they are arranged. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Mon Jun 22, 2020 3:08 pm Post subject: |
|
|
This is a message.
Last edited by TheScientist on Wed Jul 29, 2020 9:26 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54578 Location: 56N 3W
|
Posted: Mon Jun 22, 2020 5:06 pm Post subject: |
|
|
TheScientist,
Your dmesg is interesting for what it does not say.
You appear to have the Intel kernel module installed correctly as Xorg does not shout about /dev/dri/... missing.
Pleas check that's its there. You should have an entry for the Intel GPU and possibly for the AMD chip too.
Your console should be using inteldrmfb but its using
Code: | [ 3.090914] efifb: probing for efifb
[ 3.090956] efifb: framebuffer at 0xb0300000, using 29440k, total 29440k
[ 3.090957] efifb: mode is 3360x2100x32, linelength=14336, pages=1
[ 3.090958] efifb: scrolling: redraw
[ 3.090959] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 3.091026] Console: switching to colour frame buffer device 210x65
[ 3.103659] fb0: EFI VGA frame buffer device |
The Intel system starts later.
Code: | [ 3.128524] i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x20000000] (bogus alignment)
[ 3.128525] i915 0000:00:02.0: [drm] Failed to find VBIOS tables (VBT)
[ 3.138547] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[ 3.140177] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2
[ 3.140180] i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime power management.
[ 3.140181] i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 |
The missing firmware is not the problem. There should be a lot more, including the console switching to inteldrmfb.
Xorg won't work until the intel kernel module starts properly.
Your Xorg.0.log file says
Code: | [ 2930.911] (--) PCI: (0@0:2:0) 8086:3e9b:106b:0176 rev 0, Mem @ 0x80000000/16777216, 0xa0000000/268435456, I/O @ 0x00004000/64
[ 2930.911] (--) PCI:*(1@0:0:0) 1002:67ef:106b:0190 rev 227, Mem @ 0xb0000000/268435456, 0xc0000000/2097152, 0x81500000/262144, I/O @ 0x00003000/256, BIOS @ 0x????????/131072 |
So your Intel chipset is 8086:3e9b
The modesetting Xorg driver depends on the kernel modesetting working and yours isn't yet.
Add your missing firmware to the kernel binary, and reinstall your kernel.
I don't think its that but maybe something else has been snuck in with it.
Compare your before and after the new kernel is is use.
The date/time will have changed. If not, the old kernel is still in use. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Wed Jun 24, 2020 2:49 am Post subject: |
|
|
This is a message.
Last edited by TheScientist on Wed Jul 29, 2020 9:26 pm; edited 1 time in total |
|
Back to top |
|
|
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Wed Jun 24, 2020 4:51 pm Post subject: |
|
|
This is a message.
Last edited by TheScientist on Wed Jul 29, 2020 9:26 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54578 Location: 56N 3W
|
Posted: Wed Jun 24, 2020 5:01 pm Post subject: |
|
|
TheScientist,
interdrmfb is free with i915 DRM but its not working for you ... yet.
CONFIG_FB_INTEL ... all the _FB_ options should be off except VESA, Simple and EFI.
They are for hardware over 20 years old.
VESA, Simple and EFI framebuffers use the hardware as is, without trying to take control.
With VESA Framebuffer and i915 DRM the kernel may start with VESA and move to i915 DRM later.
That's harmless.
Go into your BIOS and check that the intel card is Default, Boot or whatever its called.
Can you disable the Radeon GPU there too?
Please put your new dmesg and kernel .config onto pastebins.
Its either BIOS or kernel. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Wed Jun 24, 2020 6:07 pm Post subject: |
|
|
This is a message.
Last edited by TheScientist on Wed Jul 29, 2020 9:27 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54578 Location: 56N 3W
|
Posted: Wed Jun 24, 2020 6:58 pm Post subject: |
|
|
TheScientist,
The options you mentioned are fine.
Have you ever changed .config with a text editor? _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Wed Jun 24, 2020 7:01 pm Post subject: |
|
|
This is a message.
Last edited by TheScientist on Wed Jul 29, 2020 9:27 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54578 Location: 56N 3W
|
Posted: Wed Jun 24, 2020 7:35 pm Post subject: |
|
|
TheScientist,
Good.
Pastebin the current .config and dmesg please. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Wed Jun 24, 2020 7:36 pm Post subject: |
|
|
This is a message.
Last edited by TheScientist on Wed Jul 29, 2020 9:27 pm; edited 2 times in total |
|
Back to top |
|
|
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Wed Jun 24, 2020 7:45 pm Post subject: |
|
|
This is a message.
Last edited by TheScientist on Wed Jul 29, 2020 9:27 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54578 Location: 56N 3W
|
Posted: Wed Jun 24, 2020 8:19 pm Post subject: |
|
|
TheScientist,
I noticed your two GPUs.
Code: | [ 2930.911] (--) PCI: (0@0:2:0) 8086:3e9b:106b:0176 rev 0, Mem @ 0x80000000/16777216, 0xa0000000/268435456, I/O @ 0x00004000/64
[ 2930.911] (--) PCI:*(1@0:0:0) 1002:67ef:106b:0190 rev 227, Mem @ 0xb0000000/268435456, 0xc0000000/2097152, 0x81500000/262144, I/O @ ... |
8086:3e9b is the Intel one. 8086 being Intels PCI vendor ID.
If you plug Quote: | 8086:3e9b linux kernel | into your favourite search engine, one of the top hits is https://cateee.net/lkddb/web-lkddb/DRM_I915.html
Doing a find on that page for the 3e9b device ID shows
Quote: | vendor: 8086 ("Intel Corporation"), device: 3e9b ("UHD Graphics 630 (Mobile)"), class: 03 ("Display controller") | which confirms that
Code: | CONFIG_DRM_I915: Intel 8xx/9xx/G3x/G4x/HD Graphics | is correct for your Intel GPU.
Device IDs keep getting added, and we cant tell when supports for your card was added. However, you have an up to date kernel, so you are probably OK.
You can grep the kernel source tree Code: | grep -i 3e9b -R /usr/src/linux | if yo want to check.
There will be lots of hits, you are only interested in source code i915 hits.
Code: | /usr/src/linux/include/drm/i915_pciids.h: INTEL_VGA_DEVICE(0x3E9B, info), /* Halo GT2 */ \ |
Is what you want to see. If that's missing, your kernel is too old for your GPU.
Heh ... from your original dmesg ...
Code: | [ 2.284515] pci 0000:00:02.0: vgaarb: setting as boot VGA device
[ 2.284515] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[ 2.284515] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
[ 2.284515] pci 0000:00:02.0: vgaarb: no bridge control possible
[ 2.284515] pci 0000:01:00.0: vgaarb: bridge control possible
[ 2.284515] pci 0000:01:00.0: vgaarb: overriding boot device |
0000:00:02.0 Is your Intel GPU
0000:01:00.0 Is your Radeon GPU
What that tells is that the kernel start off using the Intel GPU and changes to the Radeon GPU.
However, you don't have any drivers in the kernel for the Radeon GPU.
Can you disable the Radeon GPU in the BIOS?
This does not explain why inteldrmfb is missing from dmesg though.
Only the kernel is involved. The initramfs is unpacked at
Code: | [ 2.435687] Trying to unpack rootfs image as initramfs... |
My next thought is to turn off vgaarb and see what happens. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Wed Jun 24, 2020 9:01 pm Post subject: |
|
|
This is a message.
Last edited by TheScientist on Wed Jul 29, 2020 9:28 pm; edited 1 time in total |
|
Back to top |
|
|
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Wed Jun 24, 2020 9:23 pm Post subject: |
|
|
This is a message.
Last edited by TheScientist on Wed Jul 29, 2020 9:28 pm; edited 1 time in total |
|
Back to top |
|
|
TheScientist n00b
Joined: 22 Jun 2020 Posts: 11
|
Posted: Thu Jun 25, 2020 4:09 am Post subject: |
|
|
This is a message. |
|
Back to top |
|
|
|