Tag Archives: Debian

Linux on the HP Pavilion g6-2210us — today’s tests: Debian Wheezy and Xubuntu 13.04

I swapped an old hard drive into the HP Pavilion g6-2210us and gave a few Linux distros a spin today.

Why a separate drive? I’m not at all confident about a successful Linux-Windows 8 dual boot. For those keeping score, this laptop features an AMD A4-4300M APU processor with AMD Radeon HD 7420G graphics. The wireless NIC is by Atheros, and the wired NIC is a Realtek. (I’ll report later on specific NIC chips for wired and wireless Ethernet.)

First up was Debian Wheezy. I had to turn off Secure Boot because Debian doesn’t support it. That was no problem. You can toggle Secure Boot on this HP Pavilion g6, and you can also toggle UEFI and “legacy” BIOS mode. So really I’m only limited by what “works” with the hardware itself. Given my angst lately over video (no GNOME 3 due to shaky 3D acceleration support for this newish AMD chip), that’s cold comfort.

Debian seemed to install perfectly. Except that, early in the install, it wanted me to supply nonfree firmware for the wired networking port (a Realtek NIC) on removable media. I actually got the nonfree .deb package (all Wheezy firmware is here, unpacked it and put the required files on a USB flash drive (formatted as FAT), plugged it in and continued with the install. That didn’t work. Debian didn’t “see” the firmware.

Give what happened later (the laptop stalled during boot), this was strange because the system continued installing from the netboot image — using that very NIC to download all of the required files.

I knew I would have trouble with the 3D acceleration in GNOME 3 (and I later confirmed that the proprietary 3D driver for ATI/AMD does not work on this video card), but I was doing a test install and could always bring in Xfce later.

That wouldn’t matter.

I did the entire installation. But as I hinted above, Debian Wheezy wouldn’t reboot into the new system. It hung during configuration of the wired Ethernet port. I guess I can try again with install media that includes the nonfree firmware.

Later: I did look at the installation guide for Wheezy, where I saw that you need to leave the firmware in .deb package form. I also found install images with the firmware included.

Next up was Xubuntu.

The install went fine with Secure Boot turned on. But on reboot, I had to turn off Secure Boot to get the system up and running. It could have had something to do with the fully encrypted LVM option that I chose during the install. I’ll have to do an install without encrypted LVM to see if it makes a difference in Xubuntu’s ability to run with Secure Boot enabled.

Everything looked good once I was in the system. I installed a boatload of updates. I brought in Skype with the service’s own .deb package. I managed to get audio working in Skype. But upon reboot it was not to be. The audio left Skype, as did the configuration options I had to choose from to make it work in the first place. it might come back on the next boot. Who knows?

Unfortunately I need Skype to work at the moment. I never had such trouble in Debian Wheezy on my now-dead Lenovo G555. Until it died, that is.

Otherwise I was happy with audio. That was a major concern of mine. However, I was able to boost audio levels with the Pulse Audio Volume Control, and audio was every bit as good as it is in Windows 8.

Alas, the day’s experimenting had to come to an end. I swapped back in the Windows 8 hard drive, re-enabled Secure Boot and had a working Win 8 system once again. Yep, it’s as exciting as you thought it was.

Catching up with WordPress

I believe that it’s fairly easy to turn just about any Linux server into a WordPress installation. There is even a port of WordPress for OpenBSD. I thought that I’d try to run Movable Type on OpenBSD, but getting PHP and Perl working with the Web server looks incredibly difficult. If somebody else did this and laid out how they managed it (like How to Forge), I could probably follow along, but the difficulty of dealing with the chroot environment in OpenBSD’s default Apache Web server — which isolates the Web server’s files from the rest of the computer for security purposes — makes it extremely difficult for mortals to set up services in the Web server environment.

For a normal Web server with nothing but HTML pages (and no PHP, Perl/CGI), OpenBSD couldn’t be an easier system to use. It’s when things get more complicated that this that the non-OpenBSD geek is especially challenged.

But as I say, there is a WordPress port for OpenBSD, as well as WordPress packages for GNU/Linux systems such as Debian. I also seem to remember talk about a Movable Type package for Debian Lenny, and if it made the installation and configuration of the blogging system easier, I’d be all for it.

As it is now, between installing and configuring MySQL (or PostgreSQL), making sure PHP and Perl are running and getting all the directory permissions correctly set, putting together one of these blogging systems, even on Linux, is no trivial matter. The last time I set up Movable Type, all the MySQL issues I was having prompted me to dump it and use SQLite as my database software. At least MT gives you some options in this regard.