Gregg's Nearly Interminable Adventures in Linux Land - Page 44

DMcCunney · 04-07-2016, 09:48 PM

Quote:

Originally Posted by Dngrsone

Well... when's the last time a big name ISP sold a decent modem/router to the consumer market?

Mine does. They also actually encourage you to use your own, and publish a list of makes/models known to be compatible. (They want to provide service to your premises, but don't want to be responsible for anything in your premises. If it's your modem/router, you replace it when it fails.)

Quote:

And now with the new FCC rules, I doubt that any consumer-grade modem/router will allow custom firmware installation.

If those are the same rules I see talk about elsewhere, I believe there is a fair bit of misunderstanding about what they cover and permit. The proposed rules were specific to the 5ghz spectrum (and AFAIK, have not actually been implemented as official rules.) Meanwhile, Linksys is now officially supporting third party DD-WRT firmware on their open source firmware line: http://www.zdnet.com/article/dd-wrt-...nksys-routers/

Linksys had a line (the aforementioned WRT54G series) using a Linux kernel. Cisco bought them in 2003 and removed support. Belkin bought them from Cisco ten years later, and is finally keeping promises to return to making open source firmware available on their products.
______
Dennis

Gregg Bell · 04-25-2016, 10:37 PM

Okay. I'm pretty stuck on this one. If anybody can take a look at this and advise me I'd really appreciate it.

What happened is I did an upgrade from Xubuntu 15.10 to Xubuntu 16.04LTS. It went as expected until I got to the 'reboot' point. I clicked on the reboot button and the computer started to reboot but then it didn't come back up the way it normally does. The screen had no input signal and did the power shut down thing. I thought the computer was off (it wasn't) so I hit the power button, which of course did nothing. I left the computer alone and in about a half hour the computer came on and was fully functional.

I noticed a warning icon (you can kind of see it in the attachment--it's a red ball with a white line thru it) in the toolbar and clicked on it. (see screenshot attached). I clicked on 'Start Package Manager' and it opened the Synaptic Package Manager but it gave no instructions, so I didn't know what to do.

The next morning I turned on the computer and there was a software update (saying 'distro info data') waiting, so I ran it. And whether it was before or after the update I don't know, but the warning icon in the toolbar was gone, so I thought the update might have fixed the problem, but it didn't.

When I start the computer now it starts like it's going to work normally but the screen stays blank and I get 'no input signal' on the monitor. But in a half hour or so the computer is on properly and it works fine.

I have Googled around (I have 'aptitude' installed.) and am tempted to try:

Code:

sudo apt-get update

or

Code:

sudo apt-get upgrade

or

Code:

sudo aptitude update

or

Code:

sudo aptitude safe-upgrade

but I'm just guessing. (And I don't want to screw things up as this is my main work computer.) Any ideas? Thanks.

eschwartz · 04-25-2016, 10:47 PM

I am no Ubuntu expert (I use Arch Linux/pacman instead of Ubuntu/apt) but it looks like it might be a harmless error message indicating a failure to properly retrieve the list of packages available for download.

The monitor thing is almost definitely unrelated. And I have no idea why the monitor would say no input -- it should certainly show the BIOS menu even before booting. And that firmware is low-level and pretty foolproof.
Maybe check the cable connection?

Gregg Bell · 04-26-2016, 12:29 PM

Quote:

Originally Posted by eschwartz

I am no Ubuntu expert (I use Arch Linux/pacman instead of Ubuntu/apt) but it looks like it might be a harmless error message indicating a failure to properly retrieve the list of packages available for download.

The monitor thing is almost definitely unrelated. And I have no idea why the monitor would say no input -- it should certainly show the BIOS menu even before booting. And that firmware is low-level and pretty foolproof.
Maybe check the cable connection?

Thanks eschwartz. I checked the cables. They are all tight. The thing is it takes at least 40 minutes for the computer to come on. And looking at the error message it's talking about the cache not opening. So that would make sense why it takes so long to open the computer. (Because the computer does start opening properly, but then when it gets to the point where the Xubuntu screen should come on there's nothing.) And the thing is that error message is telling me what to do. So I ran the Package Manager but that told me nothing. So I just ran apt-get update and this is what is said:

Code:

gregg@LG:~/Desktop$ apt-get update
W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
gregg@LG:~/Desktop$

So now the question is how do I overcome all this stuff?

I made a screen shot of all the apt-get commands. I don't know that I should use any of them but I'm thinking one of them might be a possibility. And I did not do "sudo" or answer its question 'are you root?' Would running

Code:

sudo apt-get update

maybe be the way to go? Thanks.

avantman42 · 04-26-2016, 12:35 PM

apt-get and aptitude both have to be run as root. Prefixing a command with sudo will run it as root. I'm not convinced that the commands you posted earlier will help, but they won't do any harm if you want to try them and prove me wrong

eschwartz · 04-26-2016, 12:58 PM

Yes, it all needs to be run with sudo -- administrative commands always do.

But I'd just like to confirm that the monitor does indeed claim there is no input signal the whole time.
If the OS was simply displaying nothing at the moment, the monitor would be accepting input (of a black square without the usual Window Manager widgets).

arjaybe · 04-26-2016, 01:12 PM

Try this command:

sudo apt-get -f install and/or
sudo dpkg --configure -a

They're both on your list. They will both try to sort out problems with software installs and upgrades.

Gregg Bell · 04-26-2016, 03:29 PM

Quote:

Originally Posted by avantman42

apt-get and aptitude both have to be run as root. Prefixing a command with sudo will run it as root. I'm not convinced that the commands you posted earlier will help, but they won't do any harm if you want to try them and prove me wrong

Thanks Russell. That helps because I was concerned I might make matters worse by running them.

Gregg Bell · 04-26-2016, 03:35 PM

Quote:

Originally Posted by eschwartz

But I'd just like to confirm that the monitor does indeed claim there is no input signal the whole time.
If the OS was simply displaying nothing at the moment, the monitor would be accepting input (of a black square without the usual Window Manager widgets).

Thanks eschwartz. Here's what happens. I turn the computer on and it's all normal. The data comes up with the RAM etc. And all against the background of a black screen. Then still against that background it says 'Operating System is loading.' But then the screen goes black-black (as in 'no power black'). The monitor says: "No input signal" and within a second or two powers off. When I turn the monitor back on, it again shows the "No input signal" and then turns back off.

During all of this the computer is still on and showing occasional signs of activity (via a red light on it that shows either loading or some other sort of activity).

Gregg Bell · 04-26-2016, 03:41 PM

Quote:

Originally Posted by arjaybe

Try this command:

sudo apt-get -f install and/or
sudo dpkg --configure -a

They're both on your list. They will both try to sort out problems with software installs and upgrades.

Thanks rjb. I saw those guys too and thought they were the way to go. But I'm chicken. LOL I'm holding out to try them if I need to though.

Here's what I did do though. I ran sudo apt-get update and got: (and actually, as you'll see, I ran it twice--once before a software update and then I installed the software update and then ran the sudo apt-get update again.)

Code:

gregg@LG:~/Desktop$ sudo apt-get update
[sudo] password for gregg: 
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease                   
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [92.2 kB]   
Hit:4 http://dl.google.com/linux/chrome/deb stable Release                     
Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [92.2 kB]    
Hit:6 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease           
Get:8 http://us.archive.ubuntu.com/ubuntu xenial-updates/main Sources [3,416 B]
Get:9 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe Sources [920 B]
Get:10 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [5,400 B]
Get:11 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [5,404 B]
Get:12 http://us.archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [2,828 B]
Get:13 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [3,796 B]
Get:14 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [3,792 B]
Get:15 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [2,788 B]
Get:16 http://security.ubuntu.com/ubuntu xenial-security/main Sources [1,612 B]
Get:17 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [920 B]
Get:18 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [2,920 B]
Get:19 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [2,924 B]
Get:20 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en [1,288 B]
Get:21 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [188 B]
Get:22 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [1,584 B]
Get:23 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [1,588 B]
Get:24 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [1,080 B]
Get:25 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [190 B]
Fetched 227 kB in 1s (159 kB/s)     
AppStream cache update completed, but some metadata was ignored due to errors.
Reading package lists... Done
W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak digest algorithm (SHA1)
gregg@LG:~/Desktop$ sudo apt-get update
Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease               
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease       
Hit:5 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:6 http://dl.google.com/linux/chrome/deb stable Release
Reading package lists... Done                      
W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak digest algorithm (SHA1)
gregg@LG:~/Desktop$

Then I ran sudo apt-get upgrade and got:

Code:

gregg@LG:~/Desktop$ sudo apt-get upgrade
[sudo] password for gregg: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libapt-inst1.7 libapt-pkg4.16 libboost-regex1.58.0 libcdaudio1 libenca0
  libept1.4.16 libgtop2-10 libidl-2-0 libisl13 libkf5waylandserver5
  libkwineffects7 libkwinglutils6 libkwinxrenderutils6 libkwinxrenderutils7
  libllvm3.5v5 liborbit2 libpgm-5.1-0 libslv2-9 libsoundtouch0 libvpx2
  linux-headers-4.2.0-30 linux-headers-4.2.0-34 python-gnome2 python-pyorbit
  python3-ply
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
gregg@LG:~/Desktop$

Does this shed any light on the situation (and I guess the only way I'll know for sure is if the computer turns on normally, right?) or do you think I should proceed with those commands you mentioned?

Thanks.

Gregg Bell · 04-26-2016, 04:03 PM

Update: the problem might be part of a bug found when upgrading from 15.10 to 16.04.
https://bugs.launchpad.net/ubuntu/+s...t/+bug/1558331

arjaybe · 04-26-2016, 05:42 PM

Quote:

Originally Posted by Gregg Bell

Thanks rjb. I saw those guys too and thought they were the way to go. But I'm chicken. LOL I'm holding out to try them if I need to though.

Here's what I did do though. I ran sudo apt-get update and got: (and actually, as you'll see, I ran it twice--once before a software update and then I installed the software update and then ran the sudo apt-get update again.)

Code:

gregg@LG:~/Desktop$ sudo apt-get update
[sudo] password for gregg: 
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease                   
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [92.2 kB]   
Hit:4 http://dl.google.com/linux/chrome/deb stable Release                     
Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [92.2 kB]    
Hit:6 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease           
Get:8 http://us.archive.ubuntu.com/ubuntu xenial-updates/main Sources [3,416 B]
Get:9 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe Sources [920 B]
Get:10 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [5,400 B]
Get:11 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [5,404 B]
Get:12 http://us.archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [2,828 B]
Get:13 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [3,796 B]
Get:14 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [3,792 B]
Get:15 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [2,788 B]
Get:16 http://security.ubuntu.com/ubuntu xenial-security/main Sources [1,612 B]
Get:17 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [920 B]
Get:18 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [2,920 B]
Get:19 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [2,924 B]
Get:20 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en [1,288 B]
Get:21 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [188 B]
Get:22 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [1,584 B]
Get:23 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [1,588 B]
Get:24 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [1,080 B]
Get:25 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [190 B]
Fetched 227 kB in 1s (159 kB/s)     
AppStream cache update completed, but some metadata was ignored due to errors.
Reading package lists... Done
W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak digest algorithm (SHA1)
gregg@LG:~/Desktop$ sudo apt-get update
Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease               
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease       
Hit:5 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:6 http://dl.google.com/linux/chrome/deb stable Release
Reading package lists... Done                      
W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak digest algorithm (SHA1)
gregg@LG:~/Desktop$

Then I ran sudo apt-get upgrade and got:

Code:

gregg@LG:~/Desktop$ sudo apt-get upgrade
[sudo] password for gregg: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libapt-inst1.7 libapt-pkg4.16 libboost-regex1.58.0 libcdaudio1 libenca0
  libept1.4.16 libgtop2-10 libidl-2-0 libisl13 libkf5waylandserver5
  libkwineffects7 libkwinglutils6 libkwinxrenderutils6 libkwinxrenderutils7
  libllvm3.5v5 liborbit2 libpgm-5.1-0 libslv2-9 libsoundtouch0 libvpx2
  linux-headers-4.2.0-30 linux-headers-4.2.0-34 python-gnome2 python-pyorbit
  python3-ply
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
gregg@LG:~/Desktop$

Does this shed any light on the situation (and I guess the only way I'll know for sure is if the computer turns on normally, right?) or do you think I should proceed with those commands you mentioned?

Thanks.

Your updates ran successfully. The "W" message means the chrome repo has a weak signing key. Yes, run autoremove. It probably won't affect your black screen problem, though. It just removes old, unneeded packages.

Yes, run the -f install command. Long shot, but might help. I don't see any indication that anything's broken in your updates.

Check for disk space and RAM overload. The delay might be caused by swapping.

Gregg Bell · 04-26-2016, 06:26 PM

Quote:

Originally Posted by arjaybe

Your updates ran successfully. The "W" message means the chrome repo has a weak signing key. Yes, run autoremove. It probably won't affect your black screen problem, though. It just removes old, unneeded packages.

Yes, run the -f install command. Long shot, but might help. I don't see any indication that anything's broken in your updates.

Check for disk space and RAM overload. The delay might be caused by swapping.

Thanks so much, rjb. I think this is winding down. I ran the install command.

Code:

gregg@LG:~/Desktop$ sudo apt -f install
[sudo] password for gregg: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

The disk space is less than half used. The RAM was 55% free and Swap was 100% free.

I'm starting to feel like the problem may be solved. Unless it's tied into the bug, and if that's the case, it's on their end and there's nothing I can do about it (so I'll just wait it out). I've got to use the computer for a couple hours but when I'm done I'll attempt a re-start and report back. Thanks!

Glorfindel · 04-26-2016, 08:15 PM

Next time the screen goes blank try wiggling the mouse too, just in case it's turning off the monitor for lack of activity right away for some odd reason

Gregg Bell · 04-27-2016, 12:39 AM

Quote:

Originally Posted by Glorfindel

Next time the screen goes blank try wiggling the mouse too, just in case it's turning off the monitor for lack of activity right away for some odd reason

Thanks for the reminder, Glorfindel. Yeah, I wiggled the mouse a few times and it was still dead.

But I did a restart and rather than having to wait 40 minutes, the computer came back on in 15. So, progress.

I'll see (it's my work computer) what happens when I start it in the morning and report back.

Have a good night!

04-25-2016, 10:37 PM	#647
Gregg Bell Gregg Bell Posts: 2,266 Karma: 3917598 Join Date: Jan 2013 Location: Itasca, Illinois Device: Kindle Touch 7, Sony PRS300, Fire HD8 Tablet	Okay. I'm pretty stuck on this one. If anybody can take a look at this and advise me I'd really appreciate it. What happened is I did an upgrade from Xubuntu 15.10 to Xubuntu 16.04LTS. It went as expected until I got to the 'reboot' point. I clicked on the reboot button and the computer started to reboot but then it didn't come back up the way it normally does. The screen had no input signal and did the power shut down thing. I thought the computer was off (it wasn't) so I hit the power button, which of course did nothing. I left the computer alone and in about a half hour the computer came on and was fully functional. I noticed a warning icon (you can kind of see it in the attachment--it's a red ball with a white line thru it) in the toolbar and clicked on it. (see screenshot attached). I clicked on 'Start Package Manager' and it opened the Synaptic Package Manager but it gave no instructions, so I didn't know what to do. The next morning I turned on the computer and there was a software update (saying 'distro info data') waiting, so I ran it. And whether it was before or after the update I don't know, but the warning icon in the toolbar was gone, so I thought the update might have fixed the problem, but it didn't. When I start the computer now it starts like it's going to work normally but the screen stays blank and I get 'no input signal' on the monitor. But in a half hour or so the computer is on properly and it works fine. I have Googled around (I have 'aptitude' installed.) and am tempted to try: Code: sudo apt-get update or Code: sudo apt-get upgrade or Code: sudo aptitude update or Code: sudo aptitude safe-upgrade but I'm just guessing. (And I don't want to screw things up as this is my main work computer.) Any ideas? Thanks. Attached Thumbnails

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
gregg from ectaco	ProDigit	Ectaco jetBook	6	02-14-2012 08:17 PM
Gregg Byron -- Nuke em in Je$u$' name...	Gregg Byron	Introduce Yourself	4	08-20-2011 01:06 PM
History Berry, Robert Lee: Adventures in the Land of Canaan v1 02.jan.2009	ProDigit	BBeB/LRF Books	0	01-04-2009 09:29 AM

04-25-2016, 10:47 PM	#648
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	I am no Ubuntu expert (I use Arch Linux/pacman instead of Ubuntu/apt) but it looks like it might be a harmless error message indicating a failure to properly retrieve the list of packages available for download. The monitor thing is almost definitely unrelated. And I have no idea why the monitor would say no input -- it should certainly show the BIOS menu even before booting. And that firmware is low-level and pretty foolproof. Maybe check the cable connection?

04-26-2016, 12:35 PM	#650
avantman42 Wizard Posts: 1,090 Karma: 6058305 Join Date: Sep 2010 Location: UK Device: Kindle Paperwhite	apt-get and aptitude both have to be run as root. Prefixing a command with sudo will run it as root. I'm not convinced that the commands you posted earlier will help, but they won't do any harm if you want to try them and prove me wrong

04-26-2016, 12:58 PM	#651
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	Yes, it all needs to be run with sudo -- administrative commands always do. But I'd just like to confirm that the monitor does indeed claim there is no input signal the whole time. If the OS was simply displaying nothing at the moment, the monitor would be accepting input (of a black square without the usual Window Manager widgets).

04-26-2016, 01:12 PM	#652
arjaybe Wizard Posts: 1,073 Karma: 12500000 Join Date: Aug 2013 Location: Okanagan Device: Sony PRS-650, Kobo Clara	Try this command: sudo apt-get -f install and/or sudo dpkg --configure -a They're both on your list. They will both try to sort out problems with software installs and upgrades.

04-26-2016, 04:03 PM	#656
Gregg Bell Gregg Bell Posts: 2,266 Karma: 3917598 Join Date: Jan 2013 Location: Itasca, Illinois Device: Kindle Touch 7, Sony PRS300, Fire HD8 Tablet	Update: the problem might be part of a bug found when upgrading from 15.10 to 16.04. https://bugs.launchpad.net/ubuntu/+s...t/+bug/1558331

04-26-2016, 08:15 PM	#659
Glorfindel Force-Aware Elf Posts: 4,762 Karma: 11557898 Join Date: Feb 2014 Location: Valinor Device: Kindle 4 w/SO	Next time the screen goes blank try wiggling the mouse too, just in case it's turning off the monitor for lack of activity right away for some odd reason

Advert

Advert