- This topic has 6 replies, 3 voices, and was last updated Aug 3-6:30 pm by mikey777.
-
Posts
-
mikey777
Yesterday, I thought I would try Proteus, an interesting looking distro as it appears extremely lightweight and therefore, one imagines, would be a good for older and/or low-powered machines.
So, I removed the dual-booted antiX/LXLE SSD from my 14-year-old Asus X71Q, and replaced it with an empty freshly formatted SSD. Then, used the ‘dd’ command to copy Proteus v5 onto a USB stick. So far so good. Then, booted to the live environment for Proteus. First thing I noticed was that the command uname -a revealed the kernel to be 5.18, which obviously is unsuitable for significantly older machines.
Even though my Asus has a kernel limit of 5.4, Proteus seemed to work smoothly in the live environment despite being prepackaged with 5.18. Proteus has an onscreen warning about installation: if the bootloader is downloaded, only Proteus will boot from the machine: so I ticked the bootloader, assuming the warning only applies when Proteus remains installed on the machine, but not following it’s removal. I was in for a surprise …
So Proteus installation went ahead, but the Asus rebooted to a blank black screen, with the cursor flashing endlessly in the top lefthand corner. On this machine, this failure to fully reboot is the same experience I’ve had with kernel 5.10 with antiX, so assume Proteus’ 5.18 is the cause of boot failure.
Feeling a bit disappointed with the ‘Proteus experience’, I removed the Proteus SSD from the laptop & put back the antiX/LXLE dual-booted SSD. However, though Proteus is no longer present, the laptop wouldn’t boot automatically anymore to the grubscreen. Instead, I had to do a manual workaround, i.e. press the Esc key, then select the SSD from the boot-order-list, before finally arriving at the grubscreen.
So what has Proteus done to my machine, to not let it boot automatically to the grubscreen, as it did before? Proteus is no longer on my machine, but how does it still cast it’s ‘shadow’ over it?
Interested to hear your feedback and comments on this, as well as seeing if this can be fixed …
- This topic was modified 9 months, 1 week ago by mikey777.
- This topic was modified 9 months, 1 week ago by mikey777.
- This topic was modified 9 months, 1 week ago by mikey777.
▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.
dolphin_oracle
does the X71Q boot via UEFI? if so, its very possible that the Proteus setup made a entry in your UEFI, so you’ll need to remove that likely and point your system back to the antiX installation.
mikey777
does the X71Q boot via UEFI? if so, its very possible that the Proteus setup made a entry in your UEFI, so you’ll need to remove that likely and point your system back to the antiX installation.
Thanks for this suggestion, but the laptop is a non-UEFI one. But it’s made think – it must have made some kind of entry somewhere …
- This reply was modified 9 months, 1 week ago by mikey777.
▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.
christophe
Change bios settings perhaps, to reorder which boots first?
confirmed antiX frugaler, since 2019
mikey777
Change bios settings perhaps, to reorder which boots first?
Thanks Christophe.
The BIOS settings and options for boot order, in this legacy laptop, are quite basic.
I changed boot order so that the first on the list is the hard drive instead of the CD/DVD drive
(see attachment) – unfortunately, this hasn’t fixed it.Attachments:
▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.christophe
I don’t know if this will help, but I have a laptop that (many months ago) had a problem (I can’t remember what now). But in desperation I reset the bios to defaults. (Normally in my experience there’s a button to click to reset it in bios settings somewhere.) It didn’t seem appropriate to my issue at the time, but I had no idea on how it went wrong nor how to fix it.
But resetting the bios to defaults fixed my problem.(From your picture it looks like F9 will load defaults.)
Maybe that’s worth a try in your case?
- This reply was modified 9 months, 1 week ago by christophe.
confirmed antiX frugaler, since 2019
mikey777
(From your picture it looks like F9 will load defaults.) Maybe that’s worth a try in your case?
Christophe, many thanks – F9 worked !
So installing Proteus’ bootloader alters the BIOS settings …▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.
- You must be logged in to reply to this topic.
