x11/xorg update.
Guys,
My portupgrade -aP was stll going full tilt late this morning
after my 27th cup of French roast, so good thing I didn't wait.
After only 8 or 9 days, there's obv'ly been lots of mods.
Read: 'hard work' by volunteers.
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. I searched all
*.ko files and even looked for the source. NADA. Then I
ran another X -configure. That spat out a slew of warnings and
errors but it did create an xorg.conf.new. It worked as a test
and today worked to bring up gdm without any errors. (!!)
I can find out my searching around what new kinds of features are
in xorg-7.x, but it looks like it has better probes at least.
So, to anybody who is dreading the xorg mess, there is hope.
FBSD is still the best open-src group in the {known:)} universe.
gary
--
Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/xorg update.
On Mon, 18 Jun 2007 23:50:38 -0700
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.
good to hear u're back into X :)
_
{Beto|Norberto|Numard} Meijome
He uses statistics as a drunken man uses lamp-posts ... for support rather
than illumination. Andrew Lang (1844-1912)
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/xorg update.
On Tue, Jun 19, 2007 at 11:17:43PM +1000, Norberto Meijome wrote:
On Mon, 18 Jun 2007 23:50:38 -0700
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 ... .
good to hear u're back into X :)
Me too!
gary
_
{Beto|Norberto|Numard} Meijome
He uses statistics as a drunken man uses lamp-posts ... for support rather
than illumination. Andrew Lang (1844-1912)
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
--
Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/xorg update.
Gary Kline wrote: On Tue, Jun 19, 2007 at 11:17:43PM +1000, Norberto Meijome wrote: On Mon, 18 Jun 2007 23:50:38 -0700 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. HTH. Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/xorg update.
On Tue, 19 Jun 2007 09:44:23 -0700
Gary Kline [EMAIL PROTECTED] wrote:
Ah, this is the new scriptthat creates xorg.conf, correct?
Hi Gary,
man script
(not related with X)
AFAIK, xorgcfg has been around since Xorg has existed. and before that,
xfree86cfg (which has existed since 1995 at least). btw, if you replace 'cfg'
with 'conf' you get a text-based version of the same tool, in case the
autodetect doesnt work.
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 ... .
It would do it if you start X by hand (as opposed to start it via /etc/ttys
with XDM or via gdm/kdm)...it would put all the info in /var/log/Xorg.0.log too.
_
{Beto|Norberto|Numard} Meijome
Any intelligent fool can make things bigger and more complex...
It takes a touch of genius - and a lot of courage to move in the opposite
direction.
Albert Einstein
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/xorg update.
On Tue, Jun 19, 2007 at 08:33:07PM +0100, Daniel Bye wrote: Gary Kline wrote: On Tue, Jun 19, 2007 at 11:17:43PM +1000, Norberto Meijome wrote: On Mon, 18 Jun 2007 23:50:38 -0700 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. Yes, the err mentioned something about the mouse as well. I figured the file would stay in /var/log/dgm/ so I didn't save. I had planned to go back and grab the error output and re-create the stderr's from the X -configure. But when everything had been portupgraded (-aP), everything Just Worked. The error file was missing, and I launched full-tilt into getting thngs back up. 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. For me, I had to re portupgrade -aP at least four times. Maybe last night was the 5th. And the symlink script took several runs before tehrer was in /usr, X11R6 - /usr/local ... 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 will run xorgcfg (sp?) and another X -configure in, oh, 30 years. Next time I powercycle the new server :-) No missing modules tihs time, thankfully. We've had it relatively easy, as users, I think. I's beeen on the other side, so hat's off to the ports guys. gary HTH. Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/xorg update.
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]
Re: x11/xorg update.
On Wed, Jun 20, 2007 at 12:01:56PM +1000, Norberto Meijome wrote:
On Tue, 19 Jun 2007 09:44:23 -0700
Gary Kline [EMAIL PROTECTED] wrote:
Ah, this is the new scriptthat creates xorg.conf, correct?
Hi Gary,
man script
(not related with X)
Right; did use it last time.
But them I fergot i was in script; finaaly I ^D out of it, then I
forgot what I'd named it... .
AFAIK, xorgcfg has been around since Xorg has existed. and before that,
xfree86cfg (which has existed since 1995 at least). btw, if you replace 'cfg'
with 'conf' you get a text-based version of the same tool, in case the
autodetect doesnt work.
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 ... .
It would do it if you start X by hand (as opposed to start it via /etc/ttys
with XDM or via gdm/kdm)...it would put all the info in /var/log/Xorg.0.log
too.
Ok, that's why nothing was in X.org.0.log, then last night. I
kept trying the X disp manager or kdm, or gdm.
I remrmber configuring X back in v2.0.5 ith xfree86conf. and *cfg when
it'd work.
Yet another hassle last night was settingthe hardware of this Hitachi. 8
or 10 buttons and two hours of mucking-with, i'm pretty close. There used
to be an GUI program to fine tune your CRT. Sometime RSN I'm going to
buy an LCD display and lighten my carbon footprint by 50 tons/year!
(*mumble*)
_
{Beto|Norberto|Numard} Meijome
Any intelligent fool can make things bigger and more complex...
It takes a touch of genius - and a lot of courage to move in the opposite
direction.
Albert Einstein
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
--
Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
