| 1 |
On Mon, 2011-09-26 at 11:15 -0500, Dale wrote: |
| 2 |
> So buy a mobo without it or that can disable it. Got it. It'll be a |
| 3 |
> good while before I buy a new mobo tho. I'm sure they will have a |
| 4 |
> nice |
| 5 |
> fix by then but this is something I need to remember just in |
| 6 |
> case. ;-) |
| 7 |
|
| 8 |
Ok, I'll bite... |
| 9 |
|
| 10 |
It depends on who makes your system. For example, I've got a new |
| 11 |
laptop, with UEFI BIOS and SATA HDD, but if you go in the UEFI settings |
| 12 |
and change a couple of settings, you'll be able to boot into DOS. Why? |
| 13 |
Because, surprisingly, they still have quite a few corporate customers |
| 14 |
that need to use DOS. So if you can boot DOS you can boot Linux. |
| 15 |
|
| 16 |
Some manufacturers still provide firmware and BIOS updates via DOS boot |
| 17 |
cds. If you can boot from a non-signed CD, you can boot Linux. Some |
| 18 |
manufactures still consider it a competitive advantage to offer |
| 19 |
"fast-boot" linux-based firmware. Likely those would be able to be |
| 20 |
manipulated in order to to boot Linux from disk. |
| 21 |
|
| 22 |
On the server side, I don't think there is any major server manufacturer |
| 23 |
dumb enough to sell a system not capable of running Linux. |
| 24 |
|
| 25 |
In short, it's probably less of a problem then than people make it out |
| 26 |
to be. It's akin to the old(?) days when Broadcom cards didn't work |
| 27 |
with Linux. The solution is always simple: don't buy a system that has |
| 28 |
a Broadcom card. |
Archives