> >> Gary Kline <[EMAIL PROTECTED]> wrote: > >>> The xorg.conf I created on 09jun07 was around 1K bytes. The > >>> new one is around 4 times that size. My logs clued me in -- > >>> partly. In /var/log/gdm/:0.log was the problem. An (EE) > >>> that said I was missing some required module. > >> > >> this probably was due to your old xorg.conf having the wrong paths in > >> it. The errors should be pretty obvious, otherwise using xorgcfg > >> should make a good one and you can, at least, use it to compare the > >> differences. > > > > Ah, this is the new scriptthat creates xorg.conf, correct? > > A bit easier than typing X -configure and messing with the > > /root files. What I don't understand is all the output about > > missing modules to stderr. ...but .... ... . > > Which modules does it say are missing? I went through a very similar > situation earlier today, where the X log file reported that mouse and > kbd modules were not found. A bit of dragging through the ports tree, > and I found that they are installed as ports in their own right these > days. I'm not certain why they didn't get installed as part of the huge > Xorg upgrade as detailed in UPDATING, but installing them by hand made > the errors go away. > > So, the moral of the story is, I suppose, if you're happy that all your > paths are correct in your xorg.conf, and that you have followed Kris' > upgrade instructions, try looking for an individual port that installs > the missing module.
I had the same problem. But it was my mistake. Are you sure you had x11/xorg meta port installed before you started upgrading xorg? I didn't. After I got into trouble, I installed the meta port, so it added all the modules xorg was missing, and it fixed everything. Andriy _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
