<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  
  
  <channel>
    <title>chrisjrob: kubuntu</title>
    <link>https://chrisjrob.com</link>
    <atom:link href="https://chrisjrob.com/tag/kubuntu/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 - 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>
    
    <item>
      <title>Kubuntu to Debian Sid</title>
      <link>https://chrisjrob.com/2008/08/20/kubuntu-to-debian-sid/</link>
      <pubDate>Wed, 20 Aug 2008 00:00:00 +0000</pubDate>
      <author>chrisjrob@gmail.com (Chris Roberts)</author>
      <guid>https://chrisjrob.com/2008/08/20/kubuntu-to-debian-sid</guid>
      <description>
       <![CDATA[
         
           <img src="https://chrisjrob.com/assets/debian_logo.png" align="right" alt="Featured Image">
         
         <p>It’s been bothering me for some time that I am using Kubuntu instead of Debian on my work desktop PC.  Yesterday I had a drive failure necessitating a reinstall; what better excuse could there be?  Having decided to change to Debian, I decided to install Sid, and then I decided that, as KDE 4.1 is now out, why not go the whole hog.</p>

<p>The experience was pretty positive, really the only problem was that I needed to tweak the <code class="language-plaintext highlighter-rouge">xorg.conf</code> in order to get my keyboard and mouse working, other than that it was a pretty straightforward install.</p>

<!--more-->

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Section "ServerLayout"
    Identifier   "Default Layout"
    Screen       "Default Screen"
    Inputdevice  "Generic Keyboard"
    Inputdevice  "Configured Mouse"
EndSection
</code></pre></div></div>

<p>Installing VirtualBox was not such fun, but the following link sorted me out:</p>

<ul>
  <li><a href="http://chirale.wordpress.com/2007/12/23/virtualbox-ose-debian-install-howto/">Virtualbox OSE Debian Install</a></li>
</ul>

<p>So far I have installed Iceweasel3, OpenOffice3, NoMachine NX Client and VirtualBox, and it’s running really nicely.  I have activated the KDE4 compositing effects, which seem very slow, so hopefully some room for improvement there in subsequent releases.</p>

<p>So would I recommend Debian Sid KDE4.1 over Kubuntu?  Well I think that’s an unfair comparison, as I’ve installed a bleeding edge solution, but all-in-all it really wasn’t a scary installation at all.</p>

<p>Well done to the Debian team.</p>

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