You are not logged in.
In the past few days my system having problems boot about a third of the time. I think this is related to problems resuming from suspend, as discussed in a number of threads, but I'm not certain.
Alternatively, it could be the hardware failing
.
The system seems to boot, at least to some extent, but there is no output to the screen. I can get it to reboot by issuing ctrl+alt+del, although it doesn't always seem to work.
When examining the logs, I noticed that for failed boots there are claims of my graphics card being unsupported - these are not there for successful boots.
Is anyone seeing anything similar, or can anyone help?
Sep 28 18:28:36 mycomputer kernel: nvidia: module license 'NVIDIA' taints kernel.
Sep 28 18:28:36 mycomputer kernel: Disabling lock debugging due to kernel taint
Sep 28 18:28:36 mycomputer kernel: nvidia 0000:01:00.0: enabling device (0000 -> 0003)
Sep 28 18:28:36 mycomputer kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
Sep 28 18:28:36 mycomputer kernel: NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:0614)
mycomputer NVRM: installed in this system is not supported by the 340.32
mycomputer NVRM: NVIDIA Linux driver release. Please see 'Appendix
mycomputer NVRM: A - Supported NVIDIA GPU Products' in this release's
mycomputer NVRM: README, available on the Linux driver download page
mycomputer NVRM: at www.nvidia.com.
Sep 28 18:28:36 mycomputer kernel: nvidia: probe of 0000:01:00.0 failed with error -1
Sep 28 18:28:36 mycomputer kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).
Sep 28 18:28:36 mycomputer kernel: NVRM: None of the NVIDIA graphics adapters were initialized!
Sep 28 18:28:36 mycomputer kernel: [drm] Module unloaded
Sep 28 18:28:36 mycomputer kernel: NVRM: NVIDIA init module failed!
Sep 28 18:28:36 mycomputer kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
Sep 28 18:28:36 mycomputer kernel: iTCO_wdt: Found a ICH9DH TCO device (Version=2, TCOBASE=0x0460)
Sep 28 18:28:36 mycomputer kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Sep 28 18:28:36 mycomputer systemd-udevd[202]: renamed network interface eth0 to enp0s25
Sep 28 18:28:36 mycomputer kernel: coretemp coretemp.0: Using relative temperature scale!
Sep 28 18:28:36 mycomputer kernel: coretemp coretemp.0: Using relative temperature scale!
Sep 28 18:28:36 mycomputer kernel: coretemp coretemp.0: Using relative temperature scale!
Sep 28 18:28:36 mycomputer kernel: coretemp coretemp.0: Using relative temperature scale!Edit (more information):
I usually press the on button in passing, and wander off while the computer boots. I decided to stick around and noticed that when the screen doesn't work I get a different beep at start up, and according to this site it indicates a problem with the video subsystem.
This makes it sound like hardware failure, but, another thing I have noticed is that if I allow the computer to boot and blindly shut it down (takes a lot of random enter-pressing, I think there are some extra confirmation messages to get past) it will boot fine the next time. If I don't allow it to completely boot, it won't work unless I disconnect the mains power supply. I'm wondering (and going to investigate) if the graphics card isn't getting properly powered down on poweroff or something like that.
Last edited by parchd (2014-09-29 07:29:01)
Offline