Posts Tagged ‘Kernel’

A tale of a gillion installs

January 21st, 2014 No comments

Install number one: LMDE 201303.  I was hoping for the best of both worlds, but I got driver issues instead.  LMDE has known ATI proprietary driver install issues.  I followed the Mint instructions and got it working, then got a blank screen after too much tinkering.  I was surprised that LMDE had this problem since Debian doesn’t, and LMDE should be a more polished version of LMDE.  This wasn’t a big deal, but I decided to give Debian a chance.

Install number two: debian stable (7.3).  The debian website has a convoluted maze of installation links, but it’s still fairly easy to find an ISO for the stable version you need.  I installed from the live ISO using a USB key.  The installation and ATI driver update went smoothly, and I thought all was well at first.  I soon realized that about 50% of reboots failed; the audio driver was the culprit.  I installed the latest driver from Realtec/ALSA and it sort of worked, but I was still getting some crap from # dmesg and the audio would crackle with some files.

LMDE.  I live booted LMDE to see if the same issue existed there and it did.

Time for Mint 16.  As expected everything worked.  Man I really wish Ubuntu hadn’t chosen the dark side – their OS is really good.  All of these distros use ALSA audio drivers, so why is Ubuntu the only one that works?   Kernel versions:

debian stable (7.3):
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.24.
Mint 16:
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k3.11.0-12-generic.

One more thing to check.  What kernel version is the real debian testing “jessie” using:

LMDE 201303 = 3.2
debian stable 7.3 = 3.2
Mint 16 = 3.11
debian testing “jessie - Jan 2014” = 3.12!

I determined to try debian testing before settling for Mint.  I tried a netinstall from USB key which killed my PC and grub bootloader.  The debian stable live iso usb key decided to stop working as well.   I finally got a real DVD debian stable install to work, changed the repositories to point to “jessie” and upgraded.  I was very surprised to see this worked!   I’m having some problems with bash, but all of my day to day software is up and running.  Nice.

TL;DR: LMDE was using an old kernel so I needed the real debian testing (jessie) to solve my driver problems.

Setting up a RocketRaid 2320 controller on Linux Mint 9

July 4th, 2010 7 comments

After the most recently recorded podcast, I decided to take a stab at running Linux on my primary media server. The machine sports a Highpoint RocketRaid 2320 storage controller, which has support for running up to eight SATA drives. Over the course of last evening, I found out that the solution wasn’t quite as plug-and-play as running the same card under Windows. Here’s what I found out and how you can avoid the same mistakes.

Remove the RocketRaid card when installing Mint.

Make sure you have decent physical access to the machine, as the Mint installer apparently does not play nicely with this card. I replicated a complete system freeze (no keyboard or mouse input) after progressing past the keyboard layout section during the installer. Temporarily removing the 2320 from its PCI-Express slot avoided this problem; I was then able to re-insert the card after installation was complete.

Compile the Open Source driver for best results.

Highpoint has a download page for their 2300-series cards, which points to Debian and Ubuntu (x86 and x64) compatible versions of the rr232x driver. Unfortunately, the Ubuntu 64-bit version did not seem to successfully initialize – the device just wasn’t present.

A post on the Ubuntu forums (for version 9.04) was quite helpful in pointing out the required steps, but had a broken link that wasn’t easy to find. To obtain the Open Source driver, click through to the “Archive Driver Downloads for Linux and FreeBSD” page, then scroll to the bottom and grab the 32/64-bit .tar.gz file with a penguin icon. I’ve mirrored version 1.10 here in case the URLs on the HighPoint site change again: rr232x-linux-src-v1.10-090716-0928.tar.gz

The process for building the driver is as in the original post:

  • Extract the .tar.gz file to a reasonably permanent location. I say this because you will likely need to rebuild the module for any kernel upgrades. I’m going to assume you’ve created something under /opt, such as /opt/rr232x.
  • Change to the extraction directory and run:cd product/rr232x/linux
    sudo make
    sudo make install
  • Reboot your system after the installation process and the kernel will load the rr232x driver as a module.

Install gnome-disk-utility to verify and mount your filesystem.

I’m not sure why this utility disappeared as a default between Mint 8 and 9, but gnome-disk-utility will display all connected devices and allow you to directly mount partitions. It will also let you know if it “sees” the RR2320 controller. In my case, after installing the driver and rebooting, I was able to click on the 3.5TB NTFS-formatted storage and assign it a mount point of /media/Raid5 in two clicks.

What’s next?

Most of the remaining complaints online revolve around booting to the RR2320 itself, which seems like more of a pain than it’s worth (even under Windows this would seem to be the case.) I personally run a separate system drive; the actual Ubuntu installation manual from Highpoint may have additional details on actually booting to your RAID volume.

I’ve yet to install the Web or CLI management interface for Linux, which should happen in the next few days. One of the really neat items about this controller is that it can email you if a disk falls out of the array, but I’ll need to get the Web interface running in order to change some outgoing mail servers.

I also haven’t done any performance testing or benchmarking with the controller versus Windows, or if there would be an improvement migrating the filesystem to ext4 as opposed to NTFS. I do plan to stick with NTFS as I’d like portability across all major platforms with this array. From initial observations, I can play back HD content from the array without stuttering while large files are being decompressed and checksummed, which is my main goal.

TrueCrypt, kernel compilation and where’d /boot go?

October 5th, 2009 1 comment

Since I’ve installed Gentoo, I haven’t had access to my other drives. One of them is an NTFS-formatted WD Raptor, and the other is a generic Seagate 300GB drive that contains my documents, pictures and Communist propaganda inside a TrueCrypt partition. Getting the Raptor to work was fairly simple (as far as Gentoo goes) – I added the entry to my /etc/fstab file and then manually mounted the partition:

/dev/sdb1               /mnt/raptor     ntfs-3g         noatime         0 0

The TrueCrypt drive proved to be more of an issue. After installing the software and attempting to mount the partition, I encountered an error:

device-mapper: reload ioctl failed: Invalid argument 
Command failed

A quick Bing and the Gentoo Wiki described this problem exactly, with the caveat that I had to recompile my kernel to add support for LRW and XTS support. Into the kernel configuration I went – the only difference I noticed is that LRW and XTS are considered “EXPERIMENTAL” but aren’t noted as such on the requirements page:

Kernel configuration options

(This may come down to an x64 vs. x86 issue, but I haven’t run into any issues with these options enabled (yet!))

Of course, then came the make && make modules_install commands, which didn’t take too long to complete. The question then became, how do I install the new kernel? Looking in my /boot partition, I only had a few template files – and not the kernel itself or any grub settings. Essentially, /boot had nothing in it but the system still launches properly!

I then tried mounting /dev/sda1 manually, and the kernel and grub.conf showed up properly in the mountpoint. Something is obviously wrong with the way my system remounts /boot during the startup process, but at least now I’m able to install the new kernel. After copying /arch/x86_64/boot/bzImage to the newly available directory, I rebooted and the new kernel was picked up properly. TrueCrypt now lets me open, create and delete files from /media/truecrypt1, and automatically uses ntfs-3g support to accomplish this.

Overall, I’m pretty pleased at how easily I can recompile a kernel, and installation was seamless once I figured out that /boot wasn’t pointing to the right location. I expect I’ll try and manually remove the directory from /dev/sda3 and see if that makes a difference.

I am currently running various *BSD variants for this Experiment.
I currently run a mix of Windows, OS X and Linux systems for both work and personal use.
For Linux, I prefer Ubuntu LTS releases without Unity and still keep Windows 7 around for gaming.
Check out my profile for more information.

WTF #17(qq)

October 2nd, 2009 No comments

It’s no secret that Linux, as with any other operating system (and yes, I realize that I just grouped all Linux distributions into a collective) has its idiosyncrasies.  The little things that just sort of make me cock my head to the side and wonder why I’m doing this to myself, or make me want to snap my entire laptop in half.

One of these things is something Tyler previously complained about – a kernel update on Fedora 11 that just happened to tank his graphics capabilities.  Now, I might just be lucky but why in the hell would Fedora release a kernel update before compatibility for two major graphics card manufacturers wasn’t released yet?

Fortunately for Tyler, a kmod-catalyst driver was released for his ATI graphics card yesterday (today?) and he’s now rocking the latest kernel with the latest video drivers.  Unfortunately for me, some slacker has yet to update my kmod-nvidia drivers to operate properly with the latest kernel.

While this is more of a rant than anything else, it’s still a valid point.  I’ve never had trouble on a Windows-based machine wherein a major update will cause a driver to no longer function (short of an actual version incrementation – so of course, I would expect Windows XP drivers to not function in Vista, and Vista drivers to not function in Windows 7; similarly, I would not expect Fedora 11 drivers to function in Fedora 12).

<end rant>

Update: I can have my cake and eat it too!

October 1st, 2009 No comments

If you have been following my posts on here you’ll know that I have a very… fragile setup. I am doing everything in my power to ensure that Linux and my ATi graphics card play together nicely. The other day when a new kernel update was pushed out my graphics card update was not ready and I was forced to make a decision: keep the old kernel or lose my graphics. I chose to keep the old kernel.

I just wanted to let everyone know that the code wizards have seen fit to push an update to my card and I know get to use both the newest kernel and to keep my 3D graphics and desktop effects too!

For reference the kernel was and the graphics module was kmod-catalyst with matching version number.

Another kernel update, another rebuild of my kernel

September 29th, 2009 No comments

Seriously, this is getting annoying

And just when I thought it couldn’t get anymore annoying… it seems as though there isn’t a kmod-catalyst for the newest version of the kernel that I just got updated to. Which means either I get the new kernel or I get to keep my graphics. I think for now I will be sticking with the latter and only move up to the new kernel when there is a kmod-catalyst ready for me.

The trouble with patching your kernel to fix a problem…

September 7th, 2009 No comments

If you remember a while back I was having a world of trouble trying to get my ATi drivers to play nicely with my desktop effects. The end result was me having to patch and rebuild my kernel to make things work the way I wanted them to. Well today I applied some system updates and hidden among them was a kernel update. It turns out that applying this update really messed with my system. Thankfully I was able to fix it by running through the original processes again. Unfortunately I think this means that every time a kernel update come down the pipe I will have to repatch and rebuild my kernel again to get things to work…

Ah well. On the plus side this kernel update fixed a lot of my sound issues!