Quote:
Originally Posted by DMcCunney
From the average user's point of view, 32 bit vs 64 bit is mostly irrelevant. The difference between them is the address space supported. 32bit tops out at 4GB. 64bit is an order of magnitude larger. 64bit machines will permit you to install more RAM and have more programs loaded simultaneously. But you likely don't care if the programs are 64bit - an application that needs more than 4GB address space is unusual. I run 64bit programs if there is a 64 bit version, but don't care if there isn't.
|
So you can run 64 bit programs on 32 it computers unless the program is bigger than 4GB?
Quote:
Originally Posted by DMcCunney
What are the specs on the machines?
|
All three of the laptops I have are Dell Latitude D505. But the issue with the delayed booting is with my desktop.
Quote:
Originally Posted by DMcCunney
Nothing happens. The computer gyrates (the red light comes on intermittently as if it's loading) for about 2-3 minutes and then the "No Input Signal" window comes on and then the monitor shuts off.
You get that because the system isn't generating anything to display on the screen. It doesn't necessarily mean nothing is actually happening - only that if something is happening it isn't creating visible progress indicators.
|
But I've rolled the mouse when the red light is flashing and the screen still shows nothing (except the "No input signal" window).
Quote:
Originally Posted by DMcCunney
I don't need to preserve much. I would be more concerned about the stuff that syncs, like Mega (cloud storage), Dropbox, the favorites in the Firefox browser and a few other things.
Those are easy enough to preserve.
|
That's good to know. (If I have to do it I'll probably back here asking for help! LOL)
Quote:
Originally Posted by DMcCunney
I know. But if you did wipe and redo from scratch, and 16.04 didn't work, I'd use 15.04 as it's also an LTS release. As a rule, I recommend LTS releases for most cases. You still get security fixes and installed program updates, but you don't get a new version of Ubuntu until the next LTS version is ready. Unless you have special needs or like to stay bleeding edge, I see no reason to got for "point" releases of Ubuntu itself.
|
I'm not sure what you mean by this. This is what I've got on the computer:
Code:
gregg@LG:~/Desktop$ aptitude search linux-image |grep '^i'
i A linux-image-4.2.0-35-generic - Linux kernel image for version 4.2.0 on 64
i A linux-image-4.4.0-21-generic - Linux kernel image for version 4.4.0 on 64
i A linux-image-4.4.0-22-generic - Linux kernel image for version 4.4.0 on 64
i A linux-image-extra-4.2.0-35-gene - Linux kernel extra modules for version 4.2
i A linux-image-extra-4.4.0-21-gene - Linux kernel extra modules for version 4.4
i A linux-image-extra-4.4.0-22-gene - Linux kernel extra modules for version 4.4
i A linux-image-generic - Generic Linux kernel image
gregg@LG:~/Desktop$ uname -r
4.4.0-22-generic
gregg@LG:~/Desktop$
And so the 4.4.0-22-generic is what is running and it's 16.04LTS. So is 4.4.0-21-generic. But 4.2.0-35-generic is 15.10 short term. (I think. As far as I know I've never had an LTS on it till 16.04LTS.)
And I've always enjoyed getting the 6 month upgrades. You get the new Libreoffice and don't most of the other apps get upgraded, as well?
I'm obviously not a beta guy, but if I get the LTS I feel like I'm missing out.
Quote:
Originally Posted by DMcCunney
The question is what happens if you shutdown/reboot. Do you still see the 17minute delay before you finally get a usable screen?
|
Here's the latest. Today I did the power switch turn on. After about 6 minutes of nothing the red activity light came on for about 20 seconds and after it went out I scrolled the mouse to see if perchance the computer had come on. No luck. Then, as I had experienced before, when I got to 18 minutes (to be safe) I scrolled the mouse again and nothing.
So, I powered the computer off and waited till the 18 minute mark without touching the mouse and it was on.
Quote:
Originally Posted by DMcCunney
The fact that you performed your operation and did successfully boot up into a 16.04 release indicates it's not a kernel problem. Something else is causing the delay, and we're trying to isolate what.
______
Dennis
|
Thanks.