[mythtv-users] Upgrade to 0.18 / 7174 Problem
Matt Redmon
mythtv-user at comcast.net
Sun Apr 24 06:51:16 UTC 2005
All at once, I decided to upgrade to 0.18 and do a dist-upgrade on my FC3
system. That upgraded many things (over 150 updates), including my nvidia
drivers (from 6629 to 7174). Immediately after doing this, I had quite a
few problems. Most of the problems were due to the new packaging layout at
atrpms. One wasn't. Whenever I tried to go to the previously-recorded
programs screen, the frontend would freeze, X would take up 99.7+% CPU time,
and all would stay like that until killed. I got errors like:
Apr 22 22:14:37 mythbox kernel: NVRM: loading NVIDIA Linux x86 NVIDIA Kernel
Module 1.0-7174 Tue Mar 22 06:44:39 PST 2005
Apr 22 22:14:37 mythbox kernel: NVRM: not using NVAGP, an AGPGART backend is
loaded!
Apr 22 22:14:37 mythbox kernel: NVRM: not using NVAGP, an AGPGART backend is
loaded!
which suggested an agp driver problem (though I didn't change kernels and
wasn't getting these errors with the same xorg.conf) and
Apr 23 00:42:22 mythbox kernel: irq 9: nobody cared (try booting with the
"irqpoll" option.
Apr 23 00:42:22 mythbox kernel: [<c013e190>] __report_bad_irq+0x2b/0x68
Apr 23 00:42:22 mythbox kernel: [<c013e259>] note_interrupt+0x73/0x96
Apr 23 00:42:22 mythbox kernel: [<c013d7bc>] __do_IRQ+0x1bd/0x249
Apr 23 00:42:22 mythbox kernel: [<c0104de8>] do_IRQ+0x42/0x4f
Apr 23 00:42:22 mythbox kernel: [<c01035b2>] common_interrupt+0x1a/0x20
Apr 23 00:42:22 mythbox kernel: [<c010103b>] default_idle+0x23/0x29
Apr 23 00:42:22 mythbox kernel: [<c010108f>] cpu_idle+0x1f/0x34
Apr 23 00:42:22 mythbox kernel: [<c03a6665>] start_kernel+0x16b/0x16d
Apr 23 00:42:22 mythbox kernel: handlers:
Apr 23 00:42:22 mythbox kernel: [<c01ef903>] (acpi_irq+0x0/0x14)
Apr 23 00:42:22 mythbox kernel: [<c027c690>] (usb_hcd_irq+0x0/0x4b)
Apr 23 00:42:22 mythbox kernel: [<dec70eb7>] (ivtv_irq_handler+0x0/0x5b7
[ivtv])
Apr 23 00:42:22 mythbox kernel: Disabling IRQ #9
which suggested a problem with a device on IRQ 9 (such as my M179 card,
which worked fine for cat > test.mpg).
Mythfrontend and backend where curiously silent about a problem that only
seemed to crop up while accessing the recorded programs screen. Realizing
that I could playback things using xine and mplayer, and that I could watch
livetv, it seemed like there could be a problem with accessing the database
to display information on the saved programs. But dropping the database and
starting from scratch didn't help. So, all my google searches were for
naught. Nothing helped in the least. Just for kicks, I started re-reading
Jarod's guide, to see if there was something that I might have to reset
after doing a dist-upgrade. While doing so, I noticed an interesting thing:
>>
Not sure exactly what has changed in the nvidia driver, but most folks no
longer seem to be able to use the RenderAccel line without having problems.
However, I'm not sure what added benefit it provides anymore, since contrary
to my earlier belief, it isn't necessary for me to use XvMC... With 6629, I
didn't have any problems with it on any of my motherboards with VIA chipset
or nVidia's own nForce2 chipset, none of which play nice with RenderAccel
enabled anymore, but it doesn't seem to make any difference, I can still
play back even HDTV video just fine without it.
<<
And what do you know - commenting out that line in my xorg.conf solved the
problem right away. For what ever reason, having RenderAccel on didn't
affect my ability to play back video at all, unless I was trying to access
that one screen.
So, the short version: 7174 and RenderAccel don't seem to play nice on the
Chaintech 7NIF2's built-in graphics card.
Now that it's working, I'm off to have fun with 0.18!
Matt
More information about the mythtv-users
mailing list