View previous topic :: View next topic |
Author |
Message |
wenk hsub n00b
Joined: 21 Jun 2007 Posts: 27
|
Posted: Sun Jul 22, 2007 9:27 am Post subject: how to keep all important messages when updating? |
|
|
After a recent update, my X display stopped working.
The culprit was a warning message that occurred somewhere in the middle of thousands of
lines of messages. Is there some way to keep these messages, and more importantly,
an easy way for a n00bie to understand which of them require me to take some action?
(I'm on a dialup connection, so I can't babysit it for several hours while it updates.)
The issue was that the updated nvidia-drivers doesn't support my older graphics card.
unmerging nvidia-drivers and installing nvidia-legacy-drivers didn't work properly;
the screen resolution was wrong. I saw many messages in the forum that seemed
relevant, but it took about 50 tries to finally get everything right. What worked was:
switching back to nvidia-drivers,
using "Modeline" in /etc/X11/xorg.conf,
using /etc/portage/package.mask to un-update to nvidia-drivers-1.0.9639,
using modprobe -r to remove the old module.
OK, now it finally works. I'm almost afraid to ask: will I be able to use this driver forever
(or for at least the next 50 years)? Or is the inevitable answer that I should get a better
graphics card and/or driver combo? |
|
Back to top |
|
|
mark_alec Bodhisattva
Joined: 11 Sep 2004 Posts: 6066 Location: Melbourne, Australia
|
Posted: Sun Jul 22, 2007 9:49 am Post subject: |
|
|
Moved from Documentation, Tips & Tricks to Other Things Gentoo.
If you want to store the messages during an emerge, look at ELOG _________________ www.gentoo.org.au || #gentoo-au |
|
Back to top |
|
|
di1bert l33t
Joined: 16 May 2002 Posts: 963 Location: Oslo, Norway
|
Posted: Wed Jul 25, 2007 7:37 am Post subject: |
|
|
Check out app-portage/elogviewer, it might be the answer you're looking for.
-m |
|
Back to top |
|
|
wenk hsub n00b
Joined: 21 Jun 2007 Posts: 27
|
Posted: Wed Jul 25, 2007 8:01 am Post subject: |
|
|
Thanks, I think I have logging working now.
(The documentation on that page is a big sparse, could really
help to be fleshed out a bit.) And maybe a good idea to recommend
setting PORT_LOGDIR before doing any updating.
By the way, I could not delete the logs using eread because I got this error
Code: | /usr/bin/eread: line 57: /usr/bin/rm: No such file or directory |
Well, at least the fix was easy. I just hope there are no subtle issues that might
arise by changing it to /bin/rm . Did I make a mistake with my installation that
caused not having /usr/bin/rm ?? |
|
Back to top |
|
|
di1bert l33t
Joined: 16 May 2002 Posts: 963 Location: Oslo, Norway
|
Posted: Wed Jul 25, 2007 8:08 am Post subject: |
|
|
Quote: |
Did I make a mistake with my installation that
caused not having /usr/bin/rm ??
|
I doubt it. On my system /usr/bin/rm is just a symlink to /bin/rm so perhaps just do
that.
I've never really bothered too much with dmesg and firewall logs so I don't
know how much more use I can be
-m |
|
Back to top |
|
|
|