Michael W. Oliver
freebsd-current at gargantuan.com
Fri Aug 13 17:34:45 PDT 2004
On 2004-08-13T17:19:40-0700, Eric Anholt wrote:
> On Fri, 2004-08-13 at 17:06, Michael W. Oliver wrote:
> > 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
> last one.
I wouldn't know what I was looking at if I did look at the code, but
xorg did complain about missing /dev/io before I added 'io' to the
kernel config. Then, xorg complained about missing /dev/vga. So, it
seems to me that adding 'io' fixed the 'missing /dev/io' message, and
adding 'mem' fixed the 'missing /dev/vga' issue, with regards to xorg.
You guys are teaching me a lot! :)
perl -e 'print unpack("u","88V]N=&%C=\"!I;F9O(&EN(&AE861E<G,*");'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040813/9d16f1f8/attachment.bin
More information about the freebsd-current