| View previous topic :: View next topic |
| Author |
Message |
Latrina
n00b
Joined: 13 Aug 2017
Posts: 67
Location: Cambridge, UK
|
 Posted: Sat Sep 08, 2018 10:45 am Post subject: Suddenly black screen K1000M |
 |
|
Hello folks,
the other day upon restarting my ThinkPad W530 I noticed the screen would stay black with backlight leds on and the mic and micrphone leds off as well when booting using the Nvidia K1000M.
I really do not understand the reason since I didn't do anything in particular.
After a complete kernel rebuild and playing around with some nvidia-drivers versions I ultimately gave up and booted back with the HD4000M.
Xorg.0.log would look fine to me, seems like the K1000M is recognized and the appropriate modules assigned, though no X, nothing. In dmesg I noticed the following errors:
| Code: | [ 1.167016] ACPI: \_SB_.PCI0.LPC_.EC__: GPE=0x11, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[ 1.168000] ACPI: \_SB_.PCI0.LPC_.EC__: Used as boot DSDT EC to handle transactions and events
[ 19.040317] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\_SB.PCI0.LPC.PMIO) (20170728/utaddress-247)
[ 19.040323] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 19.040326] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPC.LPIO) (20170728/utaddress-247)
[ 19.040330] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 27.163597] ACPI Warning: \_SB.PCI0.PEG.VID._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170728/nsarguments-100)
[ 27.256156] ACPI Error: Field [TBF3] at bit offset/length 356352/32768 exceeds size of target
Buffer (368640 bits) (20170728/dsopcode-235)
[ 27.256164] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG.VID.GETB, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
[ 27.256173] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG.VID._ROM, AE_AML_BUFFER_LIMIT (20170728/psparse-550)
|
Full dmesg can be found here https://paste.pound-python.org/show/kqBsYRa3UfWtev6NUK1P
The setup has been done according to https://wiki.gentoo.org/wiki/NVIDIA/Optimus and has always worked before.
Kernel I am using is gentoo-sources-4.14.65 with nvidia-drivers-390.87.
Also, full kernel config can be found here https://paste.pound-python.org/show/FkgG5eW0TtivwPjXzXmZ .
As always, any help will be much appreciated 
_________________
Enslaved by Systemd and all the linuxisms that come with it.  |
|
| Back to top |
|
 |
Keruskerfuerst
Advocate
Joined: 01 Feb 2006
Posts: 2289
Location: near Augsburg, Germany
|
| Posted: Mon Sep 10, 2018 10:33 am Post subject: |
|
|
| Does work another OS (like Win) ? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54813
Location: 56N 3W
|
| Posted: Mon Sep 10, 2018 1:20 pm Post subject: |
|
|
Latrina,
From dmesg
| Code: | [ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled |
Thats good, the good old text only console.
| Code: | [ 2.166663] nvidiafb: Device ID: 10de0ffc
[ 2.166937] nvidiafb: unknown NV_ARCH |
That's bad, the nvidiafb seems to have loaded.
As an aside
| Code: | [ 18.907286] vboxdrv: loading out-of-tree module taints kernel.
[ 18.907472] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[ 18.907482] vboxdrv: disagrees about version of symbol __put_page
[ 18.907484] vboxdrv: Unknown symbol __put_page (err -22) |
so the kernel and vboxdrv don't match. VirtualBox won't work until you fix that.
The nvidia driver module loaded with some ACRI errors. I don't think that's fatal.
| Code: | | [ 27.141620] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 (using threaded interrupts) |
From your kernel .config.
You may not select any framebuffer hardware drivers except maybe VESA, which is on, CONFIG_FB_SIMPLE, which only drives an existing already set up framebuffer and EFI, if you are using UEFI mode.
I say maybe VESA as the nVidia driver does not play nicely with a framebuffer console.
| Code: | CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
CONFIG_LOGO=y |
only makes sense if you expect to use a framebuffer console.
From your dmesg you are not doing that.
If this is the same system we we discussing in IRC yesterday, its not Optimus as it has a MUX.
The Xory log you posted there showed that the nvidia driver loaded, so the kernel module isn't fighting for the GPU but that the nvidia GPU had not connection to the display, at least, it could not read the EDID from the display.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
