[Openchrome-devel] [Bug 91966] No signal to monitor with X and openchrome using VX855 chipset graphics

[Svenska]

Hi,

> The viafb driver is broken on my Neoware CA19, at least as implemented in
> TahrPup. Within one second of being invoked, the system hangs, frozen solid.

Don't use viafb, then.
There is no need for viafb, and it actually interferes with other 
drivers (on my system, OpenChrome crashes when viafb is active).

You can prevent viafb to start by adding
modprobe.blacklist=viafb
to your kernel command line. Additionally, you can add
vga=ask
to the command line as well, which makes the kernel ask for a mode.

I wonder why you are so fixed on Puppy Linux. It seems too much like a 
dead end to me.

There are other distributions which might work better (i.e. a full-blown 
KNOPPIX can be installed on a USB drive as well and it might come up; 
you can try the text-based ADRIANE interface, which does not start a 
full desktop environment either).

> I *do* have one other system, but it's not at all useful -- it's a different
> WYSE (an Sx0-series) with a 366MHz Geode (!) inside, and it turns off the IDE
> as soon as the kernel fires up, unless said kernel has had some adjustments
> made to it... and recompiling kernels is waaaaaaaaaay over my little head!

Seems like a bug which requires not only a kernel recompile, but a 
kernel source code change as well. Baking a kernel binary is not too 
hard, but I wouldn't be able to test it.

If the WYSE can boot from USB, the same applies. Install KNOPPIX on a 
USB drive (possible from within KNOPPIX), and try if it works.

Best Regards,
Sebastian