Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"The only reason I'm not convinced the problem might not be a hardware issue is because all the dysfunction started with the upgrade. But who knows"
-----------------------
I ran into similar issues attempting to install newer sistros on older laptop.
Ended up to be misaligned partitions on the SSD in one instance. With another, I thought it may be the opical disc drive (also an attempt at a 'buntu 16.04 install that failed) but was wrong, again! I took time to make sure of no overlapping partitions, changed out the RAM sticks (replacing them with an identical set) and made sure the optics on odd were clean, and tried again.
Results? any distro with systemd caused prolems on my old machine. One Debian distro that touts itself as 'non-systemd' left remnanats of a GPT tabel at end of hdd and I had to wipe it before attempting another install. Two different ubuntu-based distros (I wanted netflix) -- Lite and Mint -- failed me.
I think it is because, on upgrade, EFIs with apparently unbreakable 'dependencies' on systemd are installed. As you say, "Who knows!"
Upshot -- i am now using Scientific and Salix.
Debian/Ubuntu are now intertwined, it seems to me. I will treat them as such. (Aside: I wonder what Ian Murdoch would say?)
Re: kernel. Scientific 7.2 uses as 3.10 kernel ootb.
BTW, I have a new in-the-box SystemVinit desktop mobo (smaller form factor, I can't remember which) for AMD. If interested, private message me.
sidzen
Thanks Sidzen. Seems to me a lot of people had problems with the 16.04 upgrade. I was hoping the software updates would take care of it but no luck. Anyway, sorry for the delayed response--I lost track of the thread. And the computer is working good so for now I'm going to live with the delayed boot time. (And call this thread 'solved.') Thanks for mentioning the mobo you've got but like I said the computer works great so I'll stick with it for now. Appreciate it.
gregg bell, i helped you with one or two issues a while back.
when i noticed that you were amassing problems & threads, i thought: ok, he wants to learn the hard way. can't say i did much better in my early linux days.
...well, by now i get the impression that you're in over your head & suffering.
i think you should put a plug in it.
maybe try to install & actually use a system, instead of borking it over and over?
meaning, just stick to the defaults, and if you have a real problem (e.g. wifi) read & understand BEFORE you start messing around.
That looks like a link, but isn't, so I couldn't check out your history.
Custom built how long ago? What model motherboard, and power supply? Are they old enough for crud buildup to have made it time for cleaning and inspection? Delays are a common result of failing hardware, often electrolytic caps going or gone bad in the PS, especially if the PS was included in the price of a budget-priced case.
Thanks mrmazda and sorry about the delayed response. I did open the case and everything looked really new. (I didn't buy the computer. Windows crashed on it for somebody at work and they were going to throw it out.) I checked all the cable connections--everything was tight. Going to live with the delayed boot time because the computer works great.
Again you didn't report a computer or motherboard model, so it's impossible to make any suggestions based upon your hardware. Early on you said "custom", but later reported somebody at work was going to throw it out. So, it's age and what's in it are hard to guess. Could it be that it has a floppy drive? If so, disconnect it and turn it off in the BIOS. Apparently, few developers use machines with floppy drives any more, so if some patch causes a floppy-related problem, catching it is likely to be a matter of luck long after the bug is born. I've seen various delays in recent years caused because a floppy drive was present. I reported one in openSUSE's tracker about 4 years ago, and another 18 months ago. Maybe you have found one.
Ardvark, this is probably bordering on Linux heresy but I'm just living with the problem. At this point I'm figuring only a new computer will solve the problem and this computer works great once it boots up so I'm not getting a new computer. I lost track of this thread and apologize for the late reply.
No problem, I hope you get it resolved eventually, whichever direction you choose.
Thanks Ztcoracat. I tried to run the computer off a disc and even that was a hassle (including the 18 minute boot time). For right now I'm living with the boot time because besides that the computer runs great. Sorry for the late response--I lost track of the thread.
Your Welcome-
18 minutes to boot!?#:-::-?
Something is definitely not right and or became misconfigured.
This wouldn't be the first time that I've seen an upgrade break a Ubuntu based distro.It happened to me when I was running Ubuntu a long time ago. At that time an upgrade broke the fglrx driver and reinstalling it fixed it.
Try turning off things like bluetooth and other services that you don't need.
Disable unessary kernel modules, use a light weight window mgr instead of KDE or Gnome as they are RAM hogs.
If you have tried all of that that a fresh install may be the only answer.
Do you suspect that the config boot file or the bootloader is broken?
Have you tried boot repair?
Again you didn't report a computer or motherboard model, so it's impossible to make any suggestions based upon your hardware. Early on you said "custom", but later reported somebody at work was going to throw it out. So, it's age and what's in it are hard to guess. Could it be that it has a floppy drive? If so, disconnect it and turn it off in the BIOS. Apparently, few developers use machines with floppy drives any more, so if some patch causes a floppy-related problem, catching it is likely to be a matter of luck long after the bug is born. I've seen various delays in recent years caused because a floppy drive was present. I reported one in openSUSE's tracker about 4 years ago, and another 18 months ago. Maybe you have found one.
Thanks mrmazda. The computer is not a commercial typical brand like Dell. A computer tech guy built the computer in a generic case. There was no floppy drive. It has a DVD player/recorder instead. It's pretty new.
I've wondered about the BIOS being the culprit. Honestly, I've just gotten tired of battling it.
Something is definitely not right and or became misconfigured.
This wouldn't be the first time that I've seen an upgrade break a Ubuntu based distro.It happened to me when I was running Ubuntu a long time ago. At that time an upgrade broke the fglrx driver and reinstalling it fixed it.
Try turning off things like bluetooth and other services that you don't need.
Disable unessary kernel modules, use a light weight window mgr instead of KDE or Gnome as they are RAM hogs.
If you have tried all of that that a fresh install may be the only answer.
Do you suspect that the config boot file or the bootloader is broken?
Have you tried boot repair?
I did a million and a half things with this already. Some Linux master guy had me fixing packages, analyzing this and that and this and running all these diagnostic tests. Then it just got silly.
I did do a fresh install. The problem remained.
Really I'm just not going to stress about it anymore. The computer works great. So what--I have to turn it on and wait a bit. I can live with that.
P.S. I bookmarked the boot repair link. If I get the emotional wherewithal to tackle this again I'll give it a shot. Thanks!
I did a million and a half things with this already. Some Linux master guy had me fixing packages, analyzing this and that and this and running all these diagnostic tests. Then it just got silly.
I did do a fresh install. The problem remained.
Really I'm just not going to stress about it anymore. The computer works great. So what--I have to turn it on and wait a bit. I can live with that.
P.S. I bookmarked the boot repair link. If I get the emotional wherewithal to tackle this again I'll give it a shot. Thanks!
If the fresh install gives you the 18 minute boot delay you could always roll back to the previous kernel. One last thought; recompiling the kernel sometimes makes things go away.
Since you like Xubuntu you might like Voyager. Voyager ran great for me. http://voyagerlive.org/
If the fresh install gives you the 18 minute boot delay you could always roll back to the previous kernel. One last thought; recompiling the kernel sometimes makes things go away.
Since you like Xubuntu you might like Voyager. Voyager ran great for me. http://voyagerlive.org/
Good luck-
Thanks Ztcoracat. It got so funky with this thing. I don't know how to recompile a kernel but the computer would boot from an old kernel via the grubloader but after a while even that stopped working. Now I'm grateful that it's working properly (even with the delay). And that's the first I've heard of Voyager. Thanks for sharing that.
Thanks Ztcoracat. It got so funky with this thing. I don't know how to recompile a kernel but the computer would boot from an old kernel via the grubloader but after a while even that stopped working. Now I'm grateful that it's working properly (even with the delay). And that's the first I've heard of Voyager. Thanks for sharing that.
Your Welcome.
I ran Voyager for about a year. It's a lot like Xubuntu with a nice spin and lot's of beautiful wallpapers.
You are wonderfully sold out, friend. An inspiration and encouragement to the likes of me.
Thank you, I'm glad that the Lord has used me (and given to me of Himself) to be able to be that for you! Likewise, I look forward to seeing you on here and am glad I've gotten to know you a bit. Learning how to work on and fix computers can be challenging and you've definitely shown some persistence in your efforts.
Something else I want you to know, too. Jesus loves very much "the likes of you" and you are worth every bit to Him the sacrifice on the Cross He paid for all of us. I don't belong to an exclusive club and all that I've received in Him (which includes eternal and abundant life) is available to you and everyone else, as well. You're invited! It won't always be easy but every sin I've given up and am learning to walk away from has been well worth it, receiving His freedom instead.
I'm not sure if you've seen it yet but if you want to read about the "likes of me" before I received Him, you can see it here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
