Re: startx hard locks machine

["Mika Ullgren" <mika.ullgren@lemonplanet.com>]

Hi.

I have a ASUS A7V333 at home with a identical processor. The only
differece is that I am using a PC2700 memory module, I used a GeForce 2
GTS card. I had the same problem as you did. I still have some problems
but at least I got X to run. The problem I have now is that X says that
it can't allocate som colors.

I used "xf86cfg" to configure X, here i could see that the colors wasn't
right. I ignored that and configured X after my machines specs. After i
did that i copied /root/XF86Config.new to /etc/X11/XF86Config and then
created .xinitrc and included "fvwm" in it and then started X. It
worked. But as I said earlier I have som problems with some colors. 

I have the config at home. I will try to remember to mail it to the you
and the list when I get home from work.

I used a ftp install for 3.1.

// Mika  

> -----Original Message-----
> From: mlists [mailto:mlists@konjz.org] 
> Sent: den 19 augusti 2002 04:47
> To: tedu
> Cc: misc@openbsd.org
> Subject: Re: startx hard locks machine
> 
> 
> On Sun, Aug 18, 2002 at 12:03:16PM -0700, tedu wrote:
> > On Sun, 18 Aug 2002, mlists wrote:
> > 
> > > I'm trying to install OpenBSD on a A7V333 board with AMD 
> XP 1800+ and
> > > starting X hard-locks the machine every time. I've tried 
> 3 different
> > > cards so far, all AGP: Matrox G200, Riva TNT2 and Geforce 2 GTS. I
> > > tried nv driver for NVidias, and also vesa and vga. The 
> machine has 256
> > > megs of PC2100 ram (1 chip), a hard drive and a floppy. I did a
> > > network install off of my fileserver of 3.1-release, and 
> 3.1-snapshot.
> > 
> > try to get matrox running first, they have better support.  make sue
> > your're using the mga driver.  and look in /var/log.  there 
> may a record
> > detailing where everything stopped.  it may also be that only the
> > console is locked, and remote access is still possible.
> 
> i used mga driver. the log in /var/log is 0 size (X log) and there is
> nothing in other logs. the machine hard locks, i tested with being
> remotely logged with ssh while startx-ing. it doesn't even ping
> afterwards.