Hello forum members! I want to install Fedora KDE on my Toshiba Satellite L675 laptop. But after the installation is complete, the system won’t boot. The Toshiba BIOS asks me to select a boot disk, and when I select the disk I installed, the disk name appears on the same disk selection screen, along with the message “failed”. The laptop doesn’t support Secure Boot or UEFI. This applies not only to Fedora but to all Linux distros. I’ll try again with Ventoy now. Is there any special setup I need to do? What should I do if I encounter the same error again?
Say more about what was on the laptop, how you installed, are you dual booting etc.
Maybe you had Bitlocker turned on in Windoze. If so you will need to go back to Windoze and turn it off.
Im not dualbooting and not using bitlocker. I compeletly wiped ssd and now its installing. I used MBR scheme.
Oh it came with Windoze 7! So its not bitlocker 
Toshiba Online Detailed Specs for Satellite L675 (PSK3AC-06X00X) (English)
The CPU is supported as far as I can tell Intel Core i3-370M Specs | TechPowerUp CPU Database
Try F41?
I can’t tell from the linked article whether is it only re-installs, or any installs of F42 that failed to implement MBR support ‘in time’.
I think it must be only reinstallations, otherwise the thread would have been called something like “F42 Workstation installer doesn’t support MBR disks”.
How did you create the MBR partitions, and what partitions do you have?
It seems on reading up on a search, that GPT partitioning is supported in Legacy BIOS -
so why not use the Fedora installer to automatically allocate partitions as GPT?
What is the processor? ie , is it 32 bit?
I linked to it above for the OP
1 Like
Its a 64 bit i5 480m processor. I’m going to try to install it by manually partitioning to disk right now.
I think GPT would be better. I believe it is doable with legacy BIOS, and Grub2 should be able to handle BIOS Boot
Edit: It’s been quite awhile since I have had to use a legacy bios, so do some reading …
2 Likes
Ok lemme try
1 Like
Fedora will default to creating a GPT partition table even on legacy BIOS boot only systems. It just needs a bios boot partition which will hold parts of the grub2 code.
2 Likes
This should be automatically done during installation.
The catch seems to be that the drive must not already have a partition table created since the bios boot partition must exist at the very front of the drive, before anything else is added. It seems that the bios boot partition basically extends the length of the MBR at the beginning of the drive so it can hold more code.
I would first remove the partition table, then perform the installation on the bare drive and the installer should manage it with automatic partitioning.
1 Like
The bios bot partition comes somewhere after the GPT table, so the Bios Boot partition can’t follow directly after the protective mbr. Actually, the Grub code in sector zero have a table of sector addresses which points to the extension of Grub located in the Bios Boot table. And therefore the Bios Boot partition can be anywhere reachable by the BIOS code which is limited by 32 bit LBA sector addresses.
If you have time, you should try that on a Virtual Machine and put the Bios Boot partition as the second or third allocated partition, and see if that will work.
Don’t confuse that with the classical MBR partition table where there traditionally is a gab between the partition table in sector zero and the first allocated partition.