I have just finished a successful upgrade from R5F1 to R5F27.

The one thing that is not right is that the console fonts are difficult to read and the video has visible stairstep jaggies (like on diagonal lines). All text in the Mythtv menus in X is also affected to one extent or another (I consider this to all be the same issue). None of this happened with R5F1.

The garbled font starts when the nvidia driver loads at boot time and displays The boot up console font is fine before that.

Even in console (Ctrl-Alt-F1) when you display the same text on every line, it looks different.

Old recordings appear to have this issue too, so it is a display issue, not a capture issue.

This started during setup, but seems related to a change in the nvidia driver. I noticed in the text mode part of setup in X (before setup-mythtv) that I could read the unreadable lines if I moved the window up or down a little (some lines being more readable than others).

I do not believe this is an X issue as the console fonts are bad in addition to the stairstepping in the video under X; thus I have not persued xorg.conf or nvidia-settings.

Am I right in assuming that if it affects console fonts, that xorg.conf and nvidia-settings are both out of the equation?

Is anti-aliasing turned on by default in R5F1?

I remember seeing some older patcher script that turned off Anti-Aliasing. Should I attempt to cut out part of the R5F1 patcher and run it to remove AA or is AA only done under X?

Should I attempt to downgrade the nvidia driver to the one from R5F1? Any advice on how?

GeForce MX-440 (rev a3) with SVideo tvout to a TV (no monitor connected)
HD-5500 analog capture from NTSC Sat receiver
Older dual core 3.0ghz Intel CPU
Asus P5PE-VM Motherboard
512 meg ram
1 TB LVM2[/quote]

Did the live patcher run? Check to see if switching from:
to:

in /home/mythtv/.qt/qtrc and then restarting the X server (pkill xinit) helps.

I am pretty sure the live patcher ran. I saw a lot of stuff scroll by after seeing it download the patcher.sh.

The font was already changed as you suggested. Should I try it the other way?

Would the even the console fonts be affected by this?

Cliff

I tried and it didn't help.

<edit> It didn't actually install 8776 according to dmsg after the next boot. </edit>

All I saw was it downloading 12 meg of source and restarting X. No error messages, but no obvious compillation going on either.

<edit> I am going to try dpkg -i
on /usr/src/debs/nvidia/1.0-8776/* before I give up and go back to R5F1. </edit>

Cliff

Warning!!! The following could hose your system!!! This needs to be re-validated by someone who knows more about what this will break.

I HIGHLY suggest that you back up your 5 gig boot partition (usually hda1 or sda1) before doing this so that you can put it back later.

Well I got the problems to go away by doing:
- init 1
- pkill xinit
- mounting an old R5F1 <edit> hard drive </edit> to \media\tmp (to get to the R5F1 debs)
- going to \media\tmp\usr\src\debs\nvidia\latest
- doing a dpkg -i --force-conflicts --force-overwrite *.deb

dpkg gave me a divert error with either (I forget which):
- nvidia-kernel-legacy-96xx
- or nvidia-glx-legacy-96xx
I don't remember which. I did a dpkg -P on that package.
EDIT: Timtech says it is the glx package.

After that it let me do the dpkg -i --force-conflicts --force-overwrite *.deb with no errors.

I rebooted and all the jaggies and unreadable font problems were gone. This proves that it is a problem with the R5F27 nvidia drivers. I am guessing that the interlacing was bad. Other posters in this and other threads seem to be having problems with GeForce MX-4xx cards.

EDIT: Later on when I tried to use apt-get to install a favorite tool, it gave me an error, and told me to try (as I recall) I did as it suggested and it fixed the error and allowed me to install my program.

EDIT: Hmmm... Didn't I read somewhere that Cecil made a change to the kernel for R5F27. Does that mean something is broken now? EDITEDIT: Been running for several days now and other people report success doing it too.

To let you know how bad it the jaggies were, the back side of the box on the X desktop (the one with the penguin, the couch, etc) had 5 stairsteps in it. That is how big the stairsteps were. I now see 0 stairsteps. The text in an xterm was unreadable, not just bad.

_________________
R5F27 using R5F1 Nvidia drivers
HD-5500 analog from NTSC Sat Rx, with OTA DVB too
GeForce MX-440 SVideo tvout to a TV
Older dual core 3.4ghz Intel CPU
Asus P5PE-VM Motherboard
2 GB RAM
1 TB LVM2
VirtualBox
Samba

Known and harmless.

Loading the nvidia drivers from R5F1 fixed my issue with an nforce2 mb as well that would not even show X with an int10 error.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

This cured me of the issue too...

When you mount the image, how do you mount it in such a way that you can read it, when I mount the .iso I get a Knoppix folder and Boot folder, just as if I had burned the cd.

Thank You

I got my R5F1 drivers from a hard drive with R5F1 installed on it because I had it handy and didn't want to research how to get access to the files inside the R5F1 CD compressed file system.

Actually it was from an image I copied off just before upgrading. I image my root partition before upgrade to make it easy to put back if something goes wrong.

The brute force way would be to slap an old 10 gig hard drive in and do a quick install of R5F1, then maybe copy the files off to a thumb drive or just move the 10 gig drive to a hard drive cable (don't forget the HD jumpers) that is not otherwise used when running your standard setup. Get your standard setup running again and install the files from the thumb drive or the 10 gig drive.

_________________
R5F27 using R5F1 Nvidia drivers
HD-5500 analog from NTSC Sat Rx, with OTA DVB too
GeForce MX-440 SVideo tvout to a TV
Older dual core 3.4ghz Intel CPU
Asus P5PE-VM Motherboard
2 GB RAM
1 TB LVM2
VirtualBox
Samba

I did the dpkg -i --force-conflicts etc... and that did give me errors:



So when you say do a dpkg -P on that package, I tried both:

dpkg -P nvidia-glx_1.0.8776-1_i386.deb

and

dpkg -P nvidia-glx-dev

without success (running the first dpkg again just gives the same results). what am I doing wrong?

I got the same thing as greywire. I am considering removing the libgl1-mesa-dev and next of kin to see if nvidia will slide in that way. It would appear that if blow away the mesa files, that Xorg won't work anymore. Thoughts? Help? Note that I used the force options and got

root@videobaby2:/myth/vcard_fix/nvidia/latest# dpkg -i --force-conflicts --force-overwrite *.deb
dpkg: regarding nvidia-glx-dev_1.0.8776-1_i386.deb containing nvidia-glx-dev:
nvidia-glx-dev conflicts with libgl-dev
libgl1-mesa-dev provides libgl-dev and is installed.
dpkg: warning - ignoring conflict, may proceed anyway !
dpkg: regarding nvidia-glx-dev_1.0.8776-1_i386.deb containing nvidia-glx-dev:
nvidia-glx-dev conflicts with mesa-common-dev
mesa-common-dev (version 6.5.1-0.6) is installed.
dpkg: warning - ignoring conflict, may proceed anyway !
dpkg: regarding nvidia-glx-dev_1.0.8776-1_i386.deb containing nvidia-glx-dev:
nvidia-glx-dev conflicts with libgl-dev
libgl1-mesa-dev provides libgl-dev and is installed.
dpkg: warning - ignoring conflict, may proceed anyway !
dpkg: regarding nvidia-glx-dev_1.0.8776-1_i386.deb containing nvidia-glx-dev:
libgl1-mesa-dev conflicts with libgl-dev
nvidia-glx-dev provides libgl-dev and is to be installed.
dpkg: warning - ignoring conflict, may proceed anyway !
(Reading database ... 85583 files and directories currently installed.)
Preparing to replace nvidia-glx-dev 1.0.8776-1 (using nvidia-glx-dev_1.0.8776-1_i386.deb) ...
Unpacking replacement nvidia-glx-dev ...
dpkg: regarding nvidia-glx_1.0.8776-1_i386.deb containing nvidia-glx:
nvidia-glx-legacy-96xx conflicts with nvidia-glx
nvidia-glx (version 1.0.8776-1) is to be installed.
dpkg: warning - ignoring conflict, may proceed anyway !
Unpacking nvidia-glx (from nvidia-glx_1.0.8776-1_i386.deb) ...
dpkg-divert: `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx' clashes with `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx-legacy-96xx'
dpkg: error processing nvidia-glx_1.0.8776-1_i386.deb (--install):
subprocess pre-installation script returned error exit status 2
Preparing to replace nvidia-kernel-2.6.18-chw-13 1.0.8776-1+2.6.18-chw-13-10.00.Custom (using nvidia-kernel-2.6.18-chw-13_1.0.8776-1+2.6.18-chw-13-10.00.Custom_i386.deb) ...
Unpacking replacement nvidia-kernel-2.6.18-chw-13 ...
dpkg: dependency problems prevent configuration of nvidia-glx-dev:
nvidia-glx-dev depends on nvidia-glx (>= 1.0.8776); however:
Package nvidia-glx is not installed.
dpkg: error processing nvidia-glx-dev (--install):
dependency problems - leaving unconfigured
Setting up nvidia-kernel-2.6.18-chw-13 (1.0.8776-1+2.6.18-chw-13-10.00.Custom) ...

Errors were encountered while processing:
nvidia-glx_1.0.8776-1_i386.deb
nvidia-glx-dev

Still can't get my box back up (backend is working fine, happily recording shows and grabbing program guides from schedules direct, so nice job guys on getting that squared away!). I just can't watch any shows (the streaming in mythweb seems to work, though the quality is low..).

I have an nforce2 motherboard (chaintech 7NIF2) which I believe is an integrated Gforce 2 MX video.

I've tried the method above with no success, I also tried going directly to several versions of the nvidia drivers from nvidia's website, none of which would install.

I tried do another install (an auto upgrade) and I did briefly see the menus, even played a bit of video, and then it went back to black and I haven't seen anything since...

I'm lost! Please help!

The fix for me was:

Errors were encountered while processing: nvidia-glx_1.0.8776-1_i386.deb nvidia-glx-dev

dpkg -P nvidia-kernel-2.6.18-chw-13
dpkg -P nvidia-glx-legacy-96xx

Then
dpkg -i --force-conflicts --force-overwrite *.deb
worked properly... Answer was in the error messages... as usual...

works for me! thank you.