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.
I have a unique 'booting' problem I haven't come across previously with installation of any OS.
I have installed MX-Linux on my old Toshiba Satellite laptop which previously ran Windows 7 since then the drive has been reformatted.
Initially MX Linux was installed then I tried Mint Cinnamon and back again to MX-18 , all from the 'Live' iso-USB using Rufus then Yumi.
The problem is I cannot get it to boot normally no matter what OS I use.
I have found a work around - booting into BIOS - enter setup – exit with/out saving changes – reboots - starts normally.
When I restart from a normal running it reboots normally.
The problem begins when I shutdown and start from fresh - this message appears on the screen.
“no booting device – insert boot disk and press any key”.
I have tried many online advice tips.
partitioning setup using Gparted.
Boot re installation and repair using MX Linux.
boot-repair-disk,... super_grub2,... rescatux,...grub customizer.
reinstalling both OS's multiple times
Edit. Re-reading your post. Bios chip may need a reset. You might need pull the cmos battery and leave it out for a minute or 2. It will reset bios to defaults. Reset the time and boot options and see what happens. Is all I can figure.
2nd edit. Depending on age of cmos battery. It might need replacing also if settings don't stick.
Apart from the boot up everything is running perfectly fine.
I've considered the comments above and can discount a problem with the HDD (ran smart and passed ok).
No USB's connected nothing at all.
The links rokytnji posted suggested Toshiba laptop's have a history of problems (haven't finished reading all the posts yet).
Did a test myself. Took a snapshot of the updated MX-18 from the laptop, made a liveUSB disk and plugged into my workstation that is dual booted with windows 10 & windows 7.
Booted up without a hitch, everything worked instantly.
Since you indicate that you have used the 'boot repair disk', what is preventing you from running it with the Create BootInfo Summary option and posting a link to the output here? That would give members a lot more informati0n to work with.
The links rokytnji posted suggested Toshiba laptop's have a history of problems (haven't finished reading all the posts yet).
erm, sorry but no.
i think rokytnji posted these as encouragement, to show that many people run linux succesfully on this hardware.
you have to consider that people never post just to say that everything is fine. they only ever post when they have a problem.
this might create a distorted view of how well the hardware is actually supported.
When I booted my Dell Touchscreen dual core XT2 for some beta testing .
It failed because the bios clock is off.
Reset time and date.
Booted up OK.
Looks like I will need to take my own advise on the cmos battery on that laptop. I bet if I put a VOM on the battery + & - contacts. I will be dis-appointed in voltages shown.
Because I bet if I let that Dell off the power brick for a few days. I wil have to reset the time again in bios.
Edit: errr.... forgot to mention. Dell gives you a keystroke to go ahead and reboot without fixing incorrect bios clock settings
I'm sorry to report the issue is not yet resolved as I had so confidently predicted.
Lesson learnt, don't make predictions before posting!!
Even with the new cmos battery the same problem occurred.
I am still researching a fix - next I am going to try "efibootmgr" which conveniently is installed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.