eta at lclark.edu
Fri Aug 13 17:19:43 PDT 2004
On Fri, 2004-08-13 at 17:06, Michael W. Oliver wrote:
> On 2004-08-13T15:50:46-0700, Kris Kennaway wrote:
> > On Fri, Aug 13, 2004 at 10:01:08PM +0000, Julian Elischer wrote:
> > > I think kkldload mem is the answer...
> > > I borowed a passing laptop and looked in teh archives..
> > >
> > > how come UPDATING doesn't mention this...
> > >
> > > it mentions mem but it should mention vga too.
> > s/vga/io/? The previous respondent mentioned that the /dev/vga error
> > from X is bogus.
> At first, I didn't have 'io' or 'mem' in my kernel config file, and xorg
> complained about missing /dev/io. So, not knowing that I needed 'mem',
> too, I added 'io' to my kernel config file and rebuilt/installed. After
> reboot, xorg then complained about missing /dev/vga. This stumped me,
> so I went to cvsweb and compared the GENERIC that my customer kernel was
> based on versus the latest GENERIC to see what "GENERIC" stuff I was
> missing. The only thing that was missing was 'mem'. So, I added mem,
> did the dance again, and now xorg works like a champ.
> FYI, even with 'io' and 'mem' in my kernel, there is still no /dev/vga,
> but xorg doesn't seem to mind anymore.
I haven't gone through the code, but I'm assuming that /dev/vga on
something (linux?) provides the capabilities that the normal /dev/io
did, and it was trying to use that as a fallback. The error, rather
than saying "your /dev/io or /dev/vga are missing" only reported the
Eric Anholt eta at lclark.edu
http://people.freebsd.org/~anholt/ anholt at FreeBSD.org
More information about the freebsd-current