Comments on: One step forwards, two steps back – hardware support for Linux http://blog.stuart.shelton.me/archives/48 Normal service will be resumed shortly... Mon, 23 Jan 2012 20:24:47 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Stuart http://blog.stuart.shelton.me/archives/48/comment-page-1#comment-2874 Stuart Mon, 23 Apr 2007 21:46:26 +0000 http://blog.srcshelton.miltonroad.net/?p=48#comment-2874 Seek and ye shall find: <a href="http://www.phoronix.com/" rel="nofollow">http://www.phoronix.com/</a> - GNU/Linux & Solaris Reviews :D Seek and ye shall find:

http://www.phoronix.com/ – GNU/Linux & Solaris Reviews :D

]]> By: Stuart http://blog.stuart.shelton.me/archives/48/comment-page-1#comment-2555 Stuart Thu, 12 Apr 2007 10:11:50 +0000 http://blog.srcshelton.miltonroad.net/?p=48#comment-2555 <b>Update</b>: I managed to bootstrap the Intel (Gigabyte) motherboard far enough to allow it to reboot under its own steam - and with a 2.6.19 kernel things are much improved. The SATA and IDE controllers are now both recognised, and the board boots correctly without having to pass the kernel lots of hack-ish arguments. Firewire still doesn't appear to work, and the on-board NIC isn't detected. Having said this, I put in a generic Intel e1000-based card to bootstrap the system, and I've seen cases before where having multiple identical NICs in the same system results in only one being detected - so this may not be (entirely) Intel's fault. Update:

I managed to bootstrap the Intel (Gigabyte) motherboard far enough to allow it to reboot under its own steam – and with a 2.6.19 kernel things are much improved.

The SATA and IDE controllers are now both recognised, and the board boots correctly without having to pass the kernel lots of hack-ish arguments.

Firewire still doesn’t appear to work, and the on-board NIC isn’t detected. Having said this, I put in a generic Intel e1000-based card to bootstrap the system, and I’ve seen cases before where having multiple identical NICs in the same system results in only one being detected – so this may not be (entirely) Intel’s fault.

]]>