[MythDora] ATrpms - Yum question

[gchris]

Dennis Hand wrote:
> On 10/3/07, gchris <gchris at bellsouth.net> wrote:
>> Dennis Hand wrote:
>>>> Now Xorg in MD3.2
>>>> had no problems recognizing my monitor, but ever since MD4.0 it has had
>>>> trouble with that, probably because it's 6 years old and Xorg has purged
>>>> it from its monitor tables.   In any case, I think now that my problems
>>>> were due to an old nvidia driver combined with a new Xorg with an
>>>> unrecognized monitor.
>>> This could very well be. It's happened to me before.
>>>
>>>> What does seem a little odd though - I just tried to change back to 9755
>>>> by editing modprobe.conf (2 places) but that had no effect on a reboot,
>>>> 8776 still loaded.  I then tried changing to 9755 with the
>>>> nvidia-graphics-switch command, but when I restarted X couldn't load the
>>>> driver and wound up putting me back in nv.  It looks like the only way
>>>> to get back to 9755 is going to be to re-install it with MythDora Tools.
>>>> Right now running in nv cat /var/log/Xorg.0.log | grep EE tells me:
>>>> (EE) AIGLX: Screen 0 is not DRI capable
>>>> but I can't say for sure whether that came from the inability to load
>>>> 9755 or not.
>>>> Chris
>>> That is very odd. I would have thought simply editing modprobe.conf to
>>> change to 8776 and an X restart would be it. And I thought it only had
>>> it listed once. The graphics switch command should have worked too.
>>> Sounds like it tried but threw in nv which isn't what we want. There
>>> has got to be a cleaner way of changing without reinstalling. Have you
>>> by chance looked at your install.log located in /root to see if you
>>> got a scriplet error when doing an initial install regarding the
>>> nvidia driver?
>>>
>> I'm back on my live system now because I'm going to record Leno shortly
>> but I checked the install log on this drive and sure enough it contains
>> the following sequence:
>>
>> Installing nvidia-graphics9755-kmdl-2.6.20-1.2944.fc6 -
>> 1:1.0_9755-86.fc6.at.i686
>> Installing nvidia-graphics9755 - 1:1.0_9755-86.fc6.at.i386
>> Traceback (most recent call last):
>>    File "/usr/lib/nvidia-graphics-helpers/nvidia-config-x.py", line 61, in ?
>>      if os.access(xconfigpath, os.F_OK):
>> TypeError: coercing to Unicode: need string or buffer, NoneType found
>> error: %post(nvidia-graphics9755-1.0_9755-86.fc6.at.i386) scriptlet
>> failed, exit status 1
>>
>> I'll check the other drive tomorrow.
>>
>> Now, at the risk of convincing you that I've really lost it, let me tell
>> you a little story.  After the misadventure with the RPM the other day I
>> noticed that this system was posting a new error on shutdown.  The error
>> is that /proc/acpi/alarm is not found, and sure enough that file is not
>> there although there are many others in /proc/acpi.  I've never been in
>> that directory before so I have no clue what happened there.
>>
>> Tonight, when I reconnected this drive and booted it, I noticed the
>> kernel number looked funny.  Sure enough, this machine is now running
>> 2.6.22.7-57.fc6!!!!  The only things I've installed on this machine
>> recently are the myth yum upgrade and the nvidia rpms.  If I had to
>> guess, my guess would be that the kernel got upgraded when I reinstalled
>> 9755 using MythDora tools.  The reason I say that is downloading that
>> rpm seemed to take a very, very long time - long enough to download both
>> the rpm and a new kernel.  Tomorrow I'll take a look at the other drive
>> and see what state it is in because I left it running nv and hadn't yet
>> reinstalled the 9755 rpm.
>> Chris
>> P.S. Surer than shit, here's this systems /var/log/yum.log for that day:
>> Sep 30 15:33:00 Installed: kernel.i686 2.6.22.7-57.fc6
>> Sep 30 15:33:07 Updated: nvidia-graphics9755-libs.i386 1:1.0_9755-87.fc6
>> Sep 30 15:33:07 Installed: nvidia-graphics9755-kmdl-2.6.22.7-57.fc6.i686
>> 1:1.0_9755-87.fc6
>> Sep 30 15:33:13 Updated: nvidia-graphics9755.i386 1:1.0_9755-87.fc6
>> Sep 30 15:33:13 Installed: lirc-kmdl-2.6.22.7-57.fc6.i686
>> 0.8.3-70_cvs20070827.fc6
>> Sep 30 15:33:14 Installed: nvidia-graphics8776-kmdl-2.6.22.7-57.fc6.i686
>> 1:1.0_8776-80.fc6
>> Sep 30 15:33:14 Installed: ivtv-kmdl-2.6.22.7-57.fc6.i686 1:1.0.2-134.fc6
>>
>> What a mess!  You can see from the timestamp it was all done in one
>> transaction.  No wonder this system was unhappy!
>>
> Holy crap that is a mess. Something has changed. This shouldn't be
> doing that and I have emailed Axel on this very problem but no reply.
> There is no reason at all for ivtv and lirc to be added for an Nvidia
> rpm.
I suspect the ivtv and lirc rpms were pulled in to satisfy dependencies 
in the kernel rpm.  The question is why was the kernel updated.
Chris