<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  
  
  <channel>
    <title>chrisjrob: nvidia</title>
    <link>https://chrisjrob.com</link>
    <atom:link href="https://chrisjrob.com/tag/nvidia/feed/index.xml" rel="self" type="application/rss+xml" />
    <description>GNU Linux, Perl and FLOSS</description>
    <language>en-gb</language>
    <pubDate>Fri, 13 Feb 2026 17:22:31 +0000</pubDate>
    <lastBuildDate>Fri, 13 Feb 2026 17:22:31 +0000</lastBuildDate>
    
    <item>
      <title>Kubuntu Lucid Lynx 10.04 Nvidia Installation</title>
      <link>https://chrisjrob.com/2011/03/04/kubuntu-lucid-lynx-10-04-nvidia-installation/</link>
      <pubDate>Fri, 04 Mar 2011 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2011/03/04/kubuntu-lucid-lynx-10-04-nvidia-installation</guid>
      <description>
       <![CDATA[
         
         <p>After updating my Kubuntu Mythbuntu Home Theatre PC, it
failed to boot into KDE, leaving me instead at a text login.  Fixing the
problem was not difficult, but I actually had problems finding the
correct instructions, and all the instructions that I did find left out
a crucial step.  I thought I would write up what I did largely for my
own benefit:</p>

<!--more-->

<p>Firstly, I tried to load the nvidia module:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>NVIDIA: Failed to load the NVIDIA kernel module. Please check your
system's kernel log for additional error messages.
Failed to load module  "nvidia"
</code></pre></div></div>

<p>Clearly the correct nvidia driver for this kernel is missing.  If it was
working and an update has messed it up for you, then possibly you have
had a kernel update and don’t have the correct kernel headers installed.
 The kernel headers are needed by dkms to rebuild the nvidia module.  If
you’re lucky, you may just be able to install the Linux kernel headers
and reboot:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get install linux-headers-`uname -r`
$ sudo shutdown -r now
</code></pre></div></div>

<p>With luck dkms will have rebuilt the nvidia module and all will be well.
 If it hasn’t worked, then we need to take more dramatic action.  Let’s
start with an nvidia-free zone:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get purge nvidia*
</code></pre></div></div>

<p>Next we should ensure that the nouveau module is blacklisted, so that we
do not end up fighting the open source nouveau driver:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo vim /etc/modprobe.d/blacklist.conf
blacklist nouveau
blacklist vga16fb
</code></pre></div></div>

<p>Now we can install the latest nvidia modules:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo apt-get install nvidia-current nvidia-settings nvidia-kernel-common
</code></pre></div></div>

<p>And run the nvidia configurator:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo nvidia-xconfig
</code></pre></div></div>

<p>Finally reboot, and in theory the nvidia module should be rebuilt by
dkms:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ sudo shutdown -r now
</code></pre></div></div>

<p>After the reboot, it may be all working, but we can check that the
nvidia module has been loaded:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ lsmod | grep nvidia
nvidia 10832442 28
</code></pre></div></div>

<p>If this returns nothing, then it has not worked, if it returns “nvidia”
as above, then you should have a working system.</p>


       ]]>
      </description>
    </item>
    
    <item>
      <title>Home Theatre PC - Configuring Hauppauge HVR2200 TV Card</title>
      <link>https://chrisjrob.com/2010/05/22/home-theatre-pc-configuring-hauppage-hvr2200-tv-card/</link>
      <pubDate>Sat, 22 May 2010 00:00:02 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2010/05/22/home-theatre-pc-configuring-hauppage-hvr2200-tv-card</guid>
      <description>
       <![CDATA[
         
           <img src="https://chrisjrob.com/assets/hvr2200_board_s_200.jpg" align="right" alt="Featured Image">
         
         <p>Wow, this really is a second post in one day!</p>

<p>Following on from the DPI issue, I decided to throw science to the wind and just set DPI to 96x96 rather than 50x50, and the login screen looks better and the font size is improved (slightly larger).</p>

<!--more-->

<p>Next, I decided that I ought to check that the TV Tuner was properly detected, but whilst it was detected correctly, it was unsure of the card number, and was unable to download the firmware.  This is not entirely surprising as this TV card is fairly recent and (as usual) Hauppauge do not themselves support Linux.</p>

<p><a href="http://ubuntuforums.org/showpost.php?p=9219191&amp;postcount=212">This link</a> provided me with the basis for fixing this issue, but in the event I only needed the following:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ cd ~
$ wget http://www.steventoth.net/linux/hvr22xx/22xxdrv_27086.zip
$ wget http://www.steventoth.net/linux/hvr22xx/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
$ wget http://www.steventoth.net/linux/hvr22xx/extract.sh
$ sh extract.sh
$ sudo su
# cp *.fw /lib/firmware/`uname -r`/
# echo "options saa7164 card=4" &gt;&gt; /etc/modprobe.d/options.conf
# exit
</code></pre></div></div>

<p>Then reboot.  Hopefully tomorrow I will have some time to continue setting up the TV card under MythTV; but for now the aerial input is required by our old MythTV system in order to record Doctor Who :).</p>


       ]]>
      </description>
    </item>
    
    <item>
      <title>Home Theatre PC - Setting DPI in Xorg</title>
      <link>https://chrisjrob.com/2010/05/22/home-theatre-pc-setting-dpi-in-xorg/</link>
      <pubDate>Sat, 22 May 2010 00:00:01 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2010/05/22/home-theatre-pc-setting-dpi-in-xorg</guid>
      <description>
       <![CDATA[
         
         <p>A second post on the same day, has hell frozen over?  No, actually I put the wrong date on yesterday’s post.  Oops.</p>

<p>The DPI problem was fixed very easily by following the instructions on the link I provided in my previous post, I calculated that my Sony Bravia KDL 32S3000 had dimensions of 700mm x 390mm and a native resolution of 1366x768.</p>

<!--more-->

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ xdpyinfo | grep dimensions
$ xdpyinfo | grep "dots per inch"
</code></pre></div></div>

<p>Converting the millimetres to inches and dividing the resolution by the inches dimensions gave me DPI of 50x50, surprisingly low.  I believe this is because the KDL 32S3000 is not a full HD TV but only 1080i.  Setting this in <code class="language-plaintext highlighter-rouge">/etc/X11/xorg.conf</code> cured the problem with the KDM login manager.</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Section "Monitor"
    Identifier "Monitor0"
    Option   "DPI" "50 x 50"
EndSection
</code></pre></div></div>


       ]]>
      </description>
    </item>
    
    <item>
      <title>Home Theatre PC - Test Boot II</title>
      <link>https://chrisjrob.com/2010/05/22/home-theatre-pc-test-boot-ii/</link>
      <pubDate>Sat, 22 May 2010 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2010/05/22/home-theatre-pc-test-boot-ii</guid>
      <description>
       <![CDATA[
         
         <p>Changing the connectors around corrected the problem, I had assumed that the arrows on the connectors indicated +ve, when clearly they must indicate -ve, fixed and the LEDs all work fine.</p>

<!--more-->

<p>Installed the Nvidia binary driver, which worked fine, except that, as I’ve found on a few installs recently the KDE screen DPI defaults to something absurd, resulting in unreadably small fonts.  Easily fixed in KDE, via System Settings (as long as you know your way around!), but haven’t yet found out how to do it in KDM (the login manager).  This is not a huge problem, as it is easy enough to type in your password, and anyway on a home theatre PC you probably want it automatically logging in.  That said, I am determined to fix this problem when I have some time.  Interestingly this was also the case on our existing mythbox, which has completely different hardware, the common thread being the nvidia driver.  I suspect the issue may be related to the KDE virtual desktop, and the nvidia driver calculating this back to a reasonable DPI.  <a href="http://wiki.archlinux.org/index.php/Xorg#Display_Size_and_DPI">This link</a> may help, I will give this a go when I have some time.</p>

<p>Anyway, the good news is that, with the binary driver installed, the standard KDE compositing is working beautifully.</p>

<p>As to sound, this is still not working via HDMI, but is working fine through the sound outputs.  This seems to be a widespread issue, which I think has been resolved, so it’s just a matter of waiting for the fix to filter downstream.  In the meantime, I will continue to work as we do on our existing mythbox, with a 2.1 speaker system plugged into the HTPC.</p>


       ]]>
      </description>
    </item>
    
    <item>
      <title>Home Theatre PC - Test Boot</title>
      <link>https://chrisjrob.com/2010/05/13/home-theatre-test-boot/</link>
      <pubDate>Thu, 13 May 2010 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2010/05/13/home-theatre-test-boot</guid>
      <description>
       <![CDATA[
         
         <p>At last the 24-pin ATX PSU extension cable has arrived - enabling me to perform a test boot.</p>

<p>It switched on okay, but the front LEDs were not working, neither the power nor the disk LED; so it seems that they are not wired up correctly, although I really can’t see how I could have got it wrong.</p>

<!--more-->

<p>It booted into a Kubuntu 10.04 USB stick without any problems.  The network card was detected correctly and I was able to browse the Internet without any configuration.  The Nvidia card was detected correctly, using the open source driver, obviously I will install the Nvidia binary driver.  The only strangeness was the lack of sound via the HDMI cable, but looking in the BIOS afterward I noticed an option “Audio via HDMI” which I have enabled, it was set to auto, but maybe that’ll make a difference.</p>

<p>It is difficult to say how quiet it is at present, as any sound it was making was being drowned out by our noisy old mythbox.</p>

<p>I can’t wait to have a decent chunk of time to start the installation.</p>


       ]]>
      </description>
    </item>
    
  </channel> 
</rss>
