Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 May 2004 18:36:59 -0500 (CDT)
From:      Michael Eads <eads@niuhep.physics.niu.edu>
To:        freebsd-x11@freebsd.org
Cc:        eads@physics.niu.edu
Subject:   xf86MapVidMem: Could not mmap /dev/vga (Invalid argument)
Message-ID:  <Pine.LNX.4.44L0.0405201831180.10112-100000@niuhep.physics.niu.edu>

next in thread | raw e-mail | index | archive | help
I recently installed FreeBSD 4.9 on an old pentium 166 machine with an Ark
Logic PCI video card (2MB RAM). The installation went without a hitch,
but I am having some trouble getting XFree86 to work. I ran the X
configuration and the config file was generated, but I am unable to start
the x server:

$ startx
Using authority file /home/eads/.Xauthority
Writing authority file /home/eads/.Xauthority
Using authority file /home/eads/.Xauthority
Writing authority file /home/eads/.Xauthority


XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: FreeBSD 4.9 i386 [ELF]
Build Date: 07 October 2003
        Before reporting problems, check http://www.XFree86.Org/
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Sun May 20 18:40:52 2018
(==) Using config file: "/etc/X11/XF86Config"

Fatal server error:
xf86MapVidMem: Could not mmap /dev/vga (Invalid argument)


When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to xfree86@xfree86.org.

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


I checked the archives of this mailing list and the lists at xfree86.org
but I couldn't find any similar reports. A "google" found a couple of
reports of similar problems for Net/OpenBSD. The suggested solution was to
recompile the kernel with the "INSECURE" option. However, I couldn't find
any documentation for such a kernel option in FreeBSD.

Any suggestions would be appreciated.

Thanks in advance.

Mike Eads



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.44L0.0405201831180.10112-100000>