On Fri, Feb 25, 2000 at 11:27:35AM +0100, Matthias Drochner wrote:
> 
> riz@boogers.sf.ca.us said:
> > When I try to start the X server, even after setting wscons to YES in
> > rc.conf, it won't start. 
> 
> What happens? Some diagnostic output?
> 
> best regards
> Matthias
> 
> 

Sorry... I had just re-used that system for another purpose, but I've re-built
it.  (output is below, but not entirely helpful.)

The problem appears to be that, when booting with serial console, ttyE0 does
not get configured.  (I can't start a getty on it from /etc/ttys) ttyE1
*does* get configured with the default wscons setup, and I can start
a getty on it just fine, but I don't know the magic incantation
to get X to use it.

output of startx follows:

XFree86 Version 3.3.6 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: January 8 1999
        If the server is older than 6-12 months, or if your card is newer
        than the above date, look for a newer version before reporting
        problems.  (see http://www.XFree86.Org/FAQ)
Operating System: NetBSD/i386 1.4.2_ALPHA The NetBSD Foundation, Inc.
Configured drivers:
  SVGA: server for SVGA graphics adaptors (Patchlevel 0):
      NV1, STG2000, RIVA 128, RIVA TNT, RIVA TNT2, RIVA ULTRA TNT2,
      RIVA VANTA, RIVA ULTRA VANTA, RIVA INTEGRATED, GeForce 256,
      GeForce DDR, Quadro, ET4000, ET4000W32, ET4000W32i, ET4000W32i_rev_b,
      ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a, ET4000W32p_rev_b,
      ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000, ET6100, et3000, pvga1,
      wd90c00, wd90c10, wd90c30, wd90c24, wd90c31, wd90c33, gvga, r128, ati,
      sis86c201, sis86c202, sis86c205, sis86c215, sis86c225, sis5597,
      sis5598, sis6326, sis530, sis620, sis300, sis630, sis540, tvga8200lx,
      tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga8900d, tvga9000,
      tvga9000i, tvga9100b, tvga9200cxr, tgui9400cxi, tgui9420, tgui9420dgi,
      tgui9430dgi, tgui9440agi, cyber9320, tgui9660, tgui9680, tgui9682,
      tgui9685, cyber9382, cyber9385, cyber9388, cyber9397, cyber9520,
      cyber9525, 3dimage975, 3dimage985, cyber9397dvd, blade3d, cyberblade,
      clgd5420, clgd5422, clgd5424, clgd5426, clgd5428, clgd5429, clgd5430,
      clgd5434, clgd5436, clgd5446, clgd5480, clgd5462, clgd5464, clgd5465,
      clgd6205, clgd6215, clgd6225, clgd6235, clgd7541, clgd7542, clgd7543,
      clgd7548, clgd7555, clgd7556, ncr77c22, ncr77c22e, cpq_avga, mga2064w,
      mga1064sg, mga2164w, mga2164w AGP, mgag200, mgag100, mgag400, oti067,
      oti077, oti087, oti037c, al2101, ali2228, ali2301, ali2302, ali2308,
      ali2401, cl6410, cl6412, cl6420, cl6440, video7, ark1000vl, ark1000pv,
      ark2000pv, ark2000mt, mx, realtek, s3_virge, AP6422, AT24, AT3D,
      s3_svga, NM2070, NM2090, NM2093, NM2097, NM2160, NM2200, ct65520,
      ct65525, ct65530, ct65535, ct65540, ct65545, ct65546, ct65548,
      ct65550, ct65554, ct65555, ct68554, ct69000, ct64200, ct64300,
      mediagx, V1000, V2100, V2200, p9100, spc8110, i740, i740_pci,
      Voodoo Banshee, Voodoo3, smi, generic

Fatal server error:
xf86OpenConsole: No console driver found
        Supported drivers: pccons (with X support), pcvt
        Check your kernel's console driver configuration and /dev entries


When reporting a problem related to a server crash, please send
the full server output, not just the last messages

X connection to :0.0 broken (explicit kill or server shutdown).


-- 
Jeff Rizzo                                         http://boogers.sf.ca.us/~riz