[gentoo-user] Via vb7001 mini-itx vrs Gentoo

["list-catcher" <list-catcher@hellburner.com>]

Hello,

I just bought a via vb7001 mini-itx:

http://www.via.com.tw/en/products/mainboards/motherboards.jsp?motherboard_id=490#spec
     or
http://tinyurl.com/364jg3

I did manage to get Gentoo installed on it, however while everything was
compiling I read the docs for the bios to get the CRT and Composite to
work.
A few ebuilds didn't compile, always the same ones, looking for i486
glibc.  Thinking (still not entirely sure, but it seems logical to me)
that I used the x86 stage3 rather than the 686 stage3 I decided to do a
clean install.  So I rebooted it, changed the bios to get CRT and
Composite to work (and they do), and to reinstall and it died immediately
after loading the kernel from the 2007.0 minimal cd.  Tried gentoo-nofb,
nada, tried gentoo-nofb noapic, nada.

So, I decided that I just screwed something up in the BIOS so did the
jumper thing as described in the docs to reset the bios to factory
defaults.  It booted CRT only.  Then I carefully set only the settings
that I thought were necessary to get composite and CRT to work. It booted
and I got this:

http://www.hellburner.com/kernel_oops_VB7001/ while fscking the partition.

I thought, ok, so I killed the install, wrong stage3, live and learn,
reboot, reinstall. So I rebooted but now whenever I try to mkfs.ext3 it
locks up and displays garbage on the screen like a busted atari.  So, I
tried the pin trick.  Same result.  mkfs starts up, formats the first 1/3
or so of the partition (60gig) and belches out atari.

I've had Gentoo running on my PII and my athlon64 3000+ just fine for
quite some time and have reinstalled them several times when the cruft
gets out of control.

I let it sit for a few hours and then decided to run memtest86.  Memtest86
ran for slightly more than a second then I got atari.  I don't have
anything else that accepts that type of ram so I have no way to isolate
it.

Any ideas?


-- 
gentoo-user@lists.gentoo.org mailing list