|
|
Post by alexham36 on Apr 21, 2016 20:10:36 GMT
 As of this morning none of my Linux OSs will boot, yet they worked well last night. PCLinuxOS gives the message .....Grub loading, please wait and then the cursor continues flashing for ever. Puppy is more informative, see attachment, but it still will not boot. I have 2 usbs with Puppy and neither will boot. Windows 10 works OK. I am not good enough to use the information given by Puppy, so I am hoping that you can tell me what is causing these problems. Thanks, Alex |
|
|
|
Post by mikkh on Apr 22, 2016 22:52:29 GMT
Never seen that error before, but it looks like some kind of graphics card or graphics card driver error.
Linux is a bit more thorough than Windows when checking hardware, so the fact that Windows loads does not rule that out - but that's just a guess or a possibility
You could try some of the suggested command line options for Puppy - where the boot: and flashing cursor is type the following....
puppy pfix=ram
(to ignore saved sessions (and saved drivers which may be causing the problem))
Two others look worth trying
puppy pfix=clean
and (after trying the above, and it doesn't work)
puppy pfix=purge
The PClinuxOS grub error looks more familiar and knowing your many drive setup, I would suspect it's looking for a drive that is no longer there and that has halted grub in it's tracks
Did you remove a drive recently?
|
|
|
|
Post by alexham36 on Apr 24, 2016 14:06:11 GMT
Thank you Mikkh. Tried what you suggested but it did not help. I changed the graphics card to NVidia GT 730 when I upgraded to Win10. It has its own cooling fan, so there are now 4 fans in my computer - if it does not work, at least I should be able to fly it as a drone.  You are also right about the drives, because I unplugged the one where Win7 was and plugged in another with PCLinuxOS KDE. When I installed Linux on that drive all other drives were unplugged, because I did not want Linux MBR to become the interface at start up. Surprizingly, after the RedoMBR finished it showed that I had two MBRs on that drive at SDA1 and SDA7. When I tried to boot from SDA7 it came up with Localhost log on!!! That is the CUPs printing URL and I don't know why or how it got there. So, in desperation, I unplugged all the drives except the Linux one and started with Live CD and used RedoMBR option. It worked after that. With all the drives still unplugged, I tried Puppy and it to worked instantly and still does. I have reconnected HD with WinHP and the SSD with Win10 and everything is working. By the way, logging on into localhost:631 in Puppy, I have configured Puppy to use WiFi printer/scanner connection. Very satisfying, but there is a problem. Epson address is currently 192.168.1.151, but the 3 last numbers change frequently and then the printer stops working. I have to go into XSane where the scanner shows what the Epson address changed to and the back into localhost to amend the the printer. Then it works again. Thanks again for your help, Alex |
|
|
|
Post by mikkh on Apr 25, 2016 0:36:59 GMT
Glad you got it sorted |
|
You are also right about the drives, because I unplugged the one where Win7 was and plugged in another with PCLinuxOS KDE. When I installed Linux on that drive all other drives were unplugged, because I did not want Linux MBR to become the interface at start up. Surprizingly, after the RedoMBR finished it showed that I had two MBRs on that drive at SDA1 and SDA7. When I tried to boot from SDA7 it came up with Localhost log on!!! That is the CUPs printing URL and I don't know why or how it got there.
