F5F Stay Refreshed Software Operating Systems Unusual issues arise during OS installation disk startup.

Unusual issues arise during OS installation disk startup.

Unusual issues arise during OS installation disk startup.

O
OMGitsFyreUS
Junior Member
5
10-15-2016, 01:04 PM
#1
I recently discovered two outdated computers priced at $5 each. One is a Compaq Deskpro EP/SB and the other is a custom-built PC equipped with a 1GHz AMD Athlon processor. The machine I’m currently using is the custom-built one. Initially, I intended to convert it into a Linux Box by installing a Linux distribution. Since I already have disks for Ubuntu 15.04 and Elementary OS, I first attempted to boot the Ubuntu CD, expecting slow performance but it failed. Instead, a kernel panic occurred before the Ubuntu screen appeared. I also tried Elementary OS, which produced the same error. Then I switched to Xubuntu, hoping its lighter profile would work better. However, it triggered another kernel panic. I considered booting Windows XP Professional to clear the drive, but even that crashed unexpectedly. Once the installer loaded and asked what I wanted to do, I pressed enter to start Windows XP so I could erase the disk. But it also crashed. It seems the problem isn’t with Linux or my hardware—it’s likely a configuration or BIOS issue. I’ve shared this issue on the Ubuntu forums, but haven’t received any replies.
O
OMGitsFyreUS
10-15-2016, 01:04 PM #1

I recently discovered two outdated computers priced at $5 each. One is a Compaq Deskpro EP/SB and the other is a custom-built PC equipped with a 1GHz AMD Athlon processor. The machine I’m currently using is the custom-built one. Initially, I intended to convert it into a Linux Box by installing a Linux distribution. Since I already have disks for Ubuntu 15.04 and Elementary OS, I first attempted to boot the Ubuntu CD, expecting slow performance but it failed. Instead, a kernel panic occurred before the Ubuntu screen appeared. I also tried Elementary OS, which produced the same error. Then I switched to Xubuntu, hoping its lighter profile would work better. However, it triggered another kernel panic. I considered booting Windows XP Professional to clear the drive, but even that crashed unexpectedly. Once the installer loaded and asked what I wanted to do, I pressed enter to start Windows XP so I could erase the disk. But it also crashed. It seems the problem isn’t with Linux or my hardware—it’s likely a configuration or BIOS issue. I’ve shared this issue on the Ubuntu forums, but haven’t received any replies.

Z
zimm_matt987
Member
52
10-20-2016, 11:20 PM
#2
Consider resetting the CMOS by following the jumper instructions on the motherboard. Turn it on, then off, and back again to see if it improves the issue. Also, verify that RAM and CPU are correctly installed, apply thermal paste to the CPU, and perform a RAM test with Memtest to ensure no faults.
Z
zimm_matt987
10-20-2016, 11:20 PM #2

Consider resetting the CMOS by following the jumper instructions on the motherboard. Turn it on, then off, and back again to see if it improves the issue. Also, verify that RAM and CPU are correctly installed, apply thermal paste to the CPU, and perform a RAM test with Memtest to ensure no faults.

M
Mano_Guister
Member
60
10-22-2016, 03:23 PM
#3
I'll examine the system's inner workings. Studies indicated a potential issue with the hard disk, though I'm uncertain since my research focused mainly on Linux aspects. I won't waste time with Memtest86; I'm too tired to wait that long. Instead, I'll attempt to swap in reliable memory modules. If none are compatible, I'll proceed with Memtest86. Before doing anything else, I'll reset the CMOS to observe the outcome.
M
Mano_Guister
10-22-2016, 03:23 PM #3

I'll examine the system's inner workings. Studies indicated a potential issue with the hard disk, though I'm uncertain since my research focused mainly on Linux aspects. I won't waste time with Memtest86; I'm too tired to wait that long. Instead, I'll attempt to swap in reliable memory modules. If none are compatible, I'll proceed with Memtest86. Before doing anything else, I'll reset the CMOS to observe the outcome.

O
Olly_is_Epic
Member
127
10-22-2016, 08:52 PM
#4
I've seen that before, but I wouldn't have expected it to impact booting a Live CD. You might attempt disconnecting the hard drive and check if you can boot at least the live CD.
O
Olly_is_Epic
10-22-2016, 08:52 PM #4

I've seen that before, but I wouldn't have expected it to impact booting a Live CD. You might attempt disconnecting the hard drive and check if you can boot at least the live CD.

I
ICHIROfan51
Member
76
10-24-2016, 03:58 AM
#5
That would make sense. Based on how I evaluate things, I often reuse the same device for testing, even when it's not the best choice. If you hadn't recommended disconnecting the hard drive, I would have switched to a different one. If the situation hadn't improved, I'd revert to the original. Really efficient, wouldn't you say?
I
ICHIROfan51
10-24-2016, 03:58 AM #5

That would make sense. Based on how I evaluate things, I often reuse the same device for testing, even when it's not the best choice. If you hadn't recommended disconnecting the hard drive, I would have switched to a different one. If the situation hadn't improved, I'd revert to the original. Really efficient, wouldn't you say?

G
garm1606
Member
64
10-29-2016, 01:28 AM
#6
So, I reset the CMOS settings. That didn't change anything besides some BIOS settings, and I will now try disconnecting the hard drive to see if it will work that way. Just tried it, and no, that made no difference. Actually, that's not true. Attempting to boot my Xubuntu CD would yield a more user-friendly error, instead it just yields an error identical to the one I encountered trying to boot Ubuntu and Elementary OS. Now, to try new RAM. With the new memory, I receive a new error, likely having something to do with the low amount I was able to find. I was only able to find a total of 96MB, whereas before it had some oddball number around 450MB. I am going to grudgingly rip a module out of my Compaq Deskpro (which also uses the same type) to see if I can get it to boot. In case you're curious, here's the new error I get: As I stated earlier, it's probably a result of having only 96MB of RAM, not the required 192MB or so in order to get the installation going. Looks like the Xubuntu installation process is beginning now, with the random capacity of 352MB of RAM. I guess it's an issue with one of the other modules. Unless of course one of them wasn't installed properly (and simply needed to be reseated), which I will also check.
G
garm1606
10-29-2016, 01:28 AM #6

So, I reset the CMOS settings. That didn't change anything besides some BIOS settings, and I will now try disconnecting the hard drive to see if it will work that way. Just tried it, and no, that made no difference. Actually, that's not true. Attempting to boot my Xubuntu CD would yield a more user-friendly error, instead it just yields an error identical to the one I encountered trying to boot Ubuntu and Elementary OS. Now, to try new RAM. With the new memory, I receive a new error, likely having something to do with the low amount I was able to find. I was only able to find a total of 96MB, whereas before it had some oddball number around 450MB. I am going to grudgingly rip a module out of my Compaq Deskpro (which also uses the same type) to see if I can get it to boot. In case you're curious, here's the new error I get: As I stated earlier, it's probably a result of having only 96MB of RAM, not the required 192MB or so in order to get the installation going. Looks like the Xubuntu installation process is beginning now, with the random capacity of 352MB of RAM. I guess it's an issue with one of the other modules. Unless of course one of them wasn't installed properly (and simply needed to be reseated), which I will also check.