I had to disconnect my desktop PC recently (see news on hurricane Florence ) and upon reassembly it wouldn't boot to KDEneon 16.04, or KDEneon 18.04 or Kubuntu 18.04! What gives?
I even tried a rollback to a previous snapshot with the same results. After about 12 different kernels and finally figuring out that I could only boot to "upstart" mode or else I got a black screen and no TTYs. Unfortunately, with upstart mode (instead of systemd) I got no X. Xorg.0.log revealed an "no screens found" and dmesg showed an odd error referring a systemd being unable to load the user profile (or something like that). Nothing really connected.
Then I looked at my pile of cables on my desk and I noticed a second Display Port cable there. I had been having sound card issues and odd screen blanking behavior earlier in the month and had acquired a second DP cable to see if that was the issue or the monitor.
Well, swapping the cables took a minute or so and I rebooted normally and not only did it boot and load the log in screen, but the sound worked and the screen blanking issue is solved.
Lesson here is when error messages and behaviors don't make sense - go back to the basics and look at the hardware. A simple $5 cable caused all these issues.
I even tried a rollback to a previous snapshot with the same results. After about 12 different kernels and finally figuring out that I could only boot to "upstart" mode or else I got a black screen and no TTYs. Unfortunately, with upstart mode (instead of systemd) I got no X. Xorg.0.log revealed an "no screens found" and dmesg showed an odd error referring a systemd being unable to load the user profile (or something like that). Nothing really connected.
Then I looked at my pile of cables on my desk and I noticed a second Display Port cable there. I had been having sound card issues and odd screen blanking behavior earlier in the month and had acquired a second DP cable to see if that was the issue or the monitor.
Well, swapping the cables took a minute or so and I rebooted normally and not only did it boot and load the log in screen, but the sound worked and the screen blanking issue is solved.
Lesson here is when error messages and behaviors don't make sense - go back to the basics and look at the hardware. A simple $5 cable caused all these issues.
Comment