F5F Stay Refreshed Hardware Desktop The updated linux version isn't starting up with the old Gigabyte board.

The updated linux version isn't starting up with the old Gigabyte board.

The updated linux version isn't starting up with the old Gigabyte board.

Pages (2): 1 2 Next
A
Abbatia17
Member
51
08-10-2016, 09:23 AM
#1
Hey there. My old PC has a gigabyte motherboard running a Core 2 Duo E7500 CPU. The BIOS is from Award Software, and the GTX 1650 is present but seems unrelated to the issue. All the HDDs are functioning properly. I followed these steps: first, I wiped everything clean, then I installed void linux on one of the drives (160GB, MBR format). After booting, I tried installing again on another drive and got the same error. I attempted to install Void Linux manually, but it worked without issues during the Grub setup. Then I tried Debian, which also failed with the same BIOS error. I attempted to create a GPT HDD with a 1MB partition for the BIOS boot sector on void linux, but still encountered the problem. I’m not sure what’s causing it and am feeling exhausted. If anyone needs help, I’ll share photos of the BIOS settings soon. UPD: BIOS model is GA-P43-ES3G.
A
Abbatia17
08-10-2016, 09:23 AM #1

Hey there. My old PC has a gigabyte motherboard running a Core 2 Duo E7500 CPU. The BIOS is from Award Software, and the GTX 1650 is present but seems unrelated to the issue. All the HDDs are functioning properly. I followed these steps: first, I wiped everything clean, then I installed void linux on one of the drives (160GB, MBR format). After booting, I tried installing again on another drive and got the same error. I attempted to install Void Linux manually, but it worked without issues during the Grub setup. Then I tried Debian, which also failed with the same BIOS error. I attempted to create a GPT HDD with a 1MB partition for the BIOS boot sector on void linux, but still encountered the problem. I’m not sure what’s causing it and am feeling exhausted. If anyone needs help, I’ll share photos of the BIOS settings soon. UPD: BIOS model is GA-P43-ES3G.

U
unormal2
Member
125
08-10-2016, 04:40 PM
#2
Show me an image of your bios settings—they might not be accurate
U
unormal2
08-10-2016, 04:40 PM #2

Show me an image of your bios settings—they might not be accurate

T
Tomerony
Junior Member
16
08-10-2016, 09:23 PM
#3
Here you are, all the settings I possess.
T
Tomerony
08-10-2016, 09:23 PM #3

Here you are, all the settings I possess.

Z
Zarbat2000
Junior Member
6
08-16-2016, 01:53 PM
#4
Use only the HDD as the boot choice and switch SATA mode from IDE to ACHI
Z
Zarbat2000
08-16-2016, 01:53 PM #4

Use only the HDD as the boot choice and switch SATA mode from IDE to ACHI

K
Kaisetsu
Senior Member
651
08-16-2016, 06:19 PM
#5
I encountered problems with a Gigabyte 870 board and a 770 board that started booting into ACI without launching IDE.
K
Kaisetsu
08-16-2016, 06:19 PM #5

I encountered problems with a Gigabyte 870 board and a 770 board that started booting into ACI without launching IDE.

C
Caribbean_Blue
Senior Member
609
08-20-2016, 08:49 PM
#6
The HD appears as a SLAVE and likely has connectors at the end for switching between SLAVE and MASTER modes. It might only require a jumper replacement or removal.
C
Caribbean_Blue
08-20-2016, 08:49 PM #6

The HD appears as a SLAVE and likely has connectors at the end for switching between SLAVE and MASTER modes. It might only require a jumper replacement or removal.

M
maxis11111
Member
143
08-23-2016, 05:50 PM
#7
No idea or SATA SSD?
M
maxis11111
08-23-2016, 05:50 PM #7

No idea or SATA SSD?

D
DMDan
Junior Member
22
08-25-2016, 04:13 AM
#8
The HD I use for installing Linux is master. I plan to switch it to slave and have another HD become master, then attempt to boot Linux again. Both IDEs are involved. I believe I've tried this before and it didn't succeed.
D
DMDan
08-25-2016, 04:13 AM #8

The HD I use for installing Linux is master. I plan to switch it to slave and have another HD become master, then attempt to boot Linux again. Both IDEs are involved. I believe I've tried this before and it didn't succeed.

J
Juan2610
Posting Freak
875
08-28-2016, 03:31 PM
#9
IDE drives have long been a legacy feature, rarely needed today. You could try unsetting jumpers on both drives and letting the system handle it, or simply remove the jumper from the affected drive. It might also require configuring the MBR instead of using GPT.
J
Juan2610
08-28-2016, 03:31 PM #9

IDE drives have long been a legacy feature, rarely needed today. You could try unsetting jumpers on both drives and letting the system handle it, or simply remove the jumper from the affected drive. It might also require configuring the MBR instead of using GPT.

R
Redstoner137
Posting Freak
811
08-28-2016, 08:29 PM
#10
Thank you, I'll attempt it later. At the moment I've swapped slave for master and vice versa to check if a different disk functions.
R
Redstoner137
08-28-2016, 08:29 PM #10

Thank you, I'll attempt it later. At the moment I've swapped slave for master and vice versa to check if a different disk functions.

Pages (2): 1 2 Next