On 02/08/2015 10:02 AM, Nuno Magalhães wrote:
Some guys at the WD forum suggested this could be a BIOS issue, which
kinda sucks as i'm not in the mood to get a new mobo.
I was under the impression linux doesn't really need the BIOS to
operate, but i'm not versed in the art of bootloading. Can anyone
point me to some reading material on this (just curious really)?
Funny this is mentioned. I just blew up my onboard eth controller
hot-plugging in a monitor. I know. I got to keep both pieces. But here's
the weird thing, Debian Jessie went ape with scrolling error messages
during boot, about eth0 being broken. It never stopped. I rebooted into
my Ubuntu partition, and it booted normally and gave me a notification
that my network was down and unavailable. That was it.
I jammed in a network controller card, after disabling the onboard one
in the bios, and everything went back to normal. But, I've never
experienced a fail-to-boot like that one. It's not like Linux won't run
without a network connection. Or, do the overlords demand it now so we
can be searched, coded and compartmentalized, as Mulder would say?
<grins> Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54d81bab.7080...@gmail.com