Your Problems Are Fixed in the Next Release: Mint 7

Back in January I posted about installing Ubuntu 8.10 on my dad's HP DV9000 laptop. There was also a followup to that post about DOSBOX .

At the end of the Ubuntu Install, and after using it for a few weeks, there were three issues:

1. Wifi: it worked, but with a work-around
2. DOSBOX was slower than DOSEMU, but DOSEMU required manual setup: Another workaround
3. On reboot, Dad had to hit enter about 30 times to get past various hangs being caused by the oddball ACPI on the DV9000. If I understood this correctly, it only showed up as a problem when the AMD CPU's were being used in the DV9000. Those are what Dad had of course...

I had tested the first two points at length with my research into Ubuntu 9.04: I knew that once I upgraded Dad's computer that those two issues would be resolved. I do not have an HP DV9000 though, so I had no way of verifying that the third point would be taken care of as well.

If you noticed the infrequency of my recent posting (both here and at BMC), you might have guessed I had been kidnapped by space aliens, but the truth is I was just working 70-90 hour weeks getting ready and implementing a data center migration. With that in the past, it was time to rest, and then to catch back up on all the other things I had been letting fall to the side.

In the mean time, not only had Ubuntu 9.04 GA'ed, but Mint 7 after that. I took both on USB fobs to Dad's house, and test booted both. Both worked fine: no ACPI hangs at all.

I talked about it with Dad, and we decided to put in Mint 7: Same as my brothers Linux system will be getting soon.

The install was straightforward, other than the install complaining about not having a swap partition. with 4GB of RAM, I just did not want to have to add an LVM to the boot disk in order to get the 5th partition on it. Dads disk already had 4 partitions: 2 NTFS (Vista and the recover partition) and 2 Linux: '/' and '/home'.

I set '/' to format, '/windows' as ntfs, and '/home' as ext3, and both to mount at boot. Once the gparted was done, it took about 4 or 5 minutes to install Mint 7.

Once up, we updated the packages, and installed DOSEMU.

DOSEMU, as delivered, configured the 'D' drive as /home/dad already, and the vbdos programs were already installed there, so it was a simple matter to cd to D, then to the programs, and then to run his NASA stuff.

What DOSBOX takes 30 seconds to run, DOSEMU takes 3. And it is graphical data, so Dad was interested in how to print it and screen capture it so it could be emailed. It turns out that this is easy under DOSEMU as well: Just full screen by clicking the center box on the upper right hand corner, and then fn-prtscrn, and Gnome pops up the screen, all captured and ready to save. A quick trip through GIMP to crop out the tool bars and the graphical display on the DOSEMU screen is ready to email or print to be added to a report.

One interesting thing: If we full screened the DOEMU window *before* we ran the program, then it would run more slowly: Maybe 20 seconds rather than 3. Faster than DOSBOX still, but much slower than EMU was normally. Dad made the easy decision to always run the programs first, then to full-screen them.

Everything works:

Display: Mint prompted for the install of the NVidia drivers, and we told it to go do it.

The Wireless stuff just works now.

We plugged in the HP printer, and Mint saw and configured it instantly. We also tried a Lexmark multifunction (resold by Dell), but that did not. I did not expect it to, since Lexmark printers are one of the few anymore that ship without Linux capabilities from the vendor.

Sound: The Altec Lansing speaker make all the right sounds: I am not sure that Altec Lansing should be claiming these speakers as theirs, but that is another story. They sound equally tinny on Vista. I fired up Rhythmbox and we listened to some Internet Radio for a bit.

Boot Speed: Fedora 11 is making a lot of noise about their new 20 second boot speed. I tested it, and on my desktop Dell 945, it is 30 seconds: Same as Mint 7 on Dad's DV9000.

Battery: This dv9000 is only 9 months old now, but Linux reported that its battery was only able to charge up to 80% of its design capacity: Something Vista was reporting as 100%.

And so forth: What a difference 6 months makes in Linux land. Dad was thrilled with the computer, and said that, other than to play a RealArcade game called WordSlinger, he did not see ever having to go back to Vista. I tried briefly to get that going under WINE, but it was acting very weird: Another thing to research!

Ubuntu 9.04 Alpha 3 First Impressions

With Linux making slow, tiny, incremental inroads all over the place: In Netbooks, phones, embedded appliances, in the BIOS, not to mention Splashtop, and being credited (over credited I think, but whatever) with the recent malaise at Microsoft (although I liked this interview with Jim Zemlin about the issue), it seemed time to have a look at see what Ubuntu was cooking up for its next major release.

I rarely start this early in a release, but there are a few things cooking at I am very curious about right now. Issues in the current Linux versions that I want to see fixed or software features I need added.

DOSEMU

First up is DOSEMU. In Ubuntu 8.10 it is busted, and the problem is not actually DOSEMU but they way in the Ubuntu 8.10 sets up security (SELinux strikes) for the application. DOSEMU. See bug 216398 for details.

I wanted DOSEMU to work, because according to my benchmarking it is far far faster at running VBDOS programs than DOSBOX. One of my dad's programs (see previous posts) takes 20 seconds in DOSBOX takes 3 in DOSEMU.

As of Alpha 3, DOSEMU is fixed!

HP DV9000 Boot Hangs

Next, there is my dad's HP DV9000 itself. It does not boot well under Ubuntu 8.10. Poorly in fact. It appears that the AMD 64 bit Turion processors, a high precision timer, and the HP BIOS all get together for a timeout party that requires keyboard interrupts to get past. Like about 24 of them to finish a boot. Ick. Appears to be this AMD C1E issue, as documented over at Kernel Trap. The workaround is to add noipic noirqdebug, irqpoll, and perhaps some other stuff to the boot line in Grub. Nice guide on changing all that here. This nastiness appears to have entered around kernel 2.6.19, and is still there in 8.10's 2.6.27. Right now 9.04 has 2.6.28, and so I am hoping it will fix some of this without having to do workarounds on the boot options. I will, but that is not the same thing as it working the way it should.

Quick aside here: This DV9000 appears to have been a particularly problematic model of computer for Linux. In point of fact, it was recalled (at least some models) for BIOS issues, so it was no great shakes for anyone for a while. I don't know why Vista does not hang on boot like Linux does, but I assume without any facts to support this that it is because Linux is seeing hardware features (like the high precision timer) and trying to use them, where Vista does not.

I do not yet know what will happen on the DV9000. I installed it on a Dell D620, and there it boots in under 30 seconds.

Netbooks and MAPI

Those are all reasons I wanted to see where Ubuntu 9.04 was going for my Dad's sake. I have another couple. Netbooks. and MAPI.

As noted here, I have an Acer Aspire One, running Mint 6 right now. I like Mint and all, but there are now and again some issues with certain Gnome dialogs being larger then 600 pixels in length. The account set up for Evolution is one of them. Rumor has it that the new version of Gnome, 2.26, that will ship with 9.04 is more Netbook friendly.

The MAPI thing is for work, and revolves around the fact that we are moving to MS Exchange 2007. I will be losing WebDAV access to email, which means I'm back to using IMAP. That is fine as far as it goes, but my calendar will only be on the so-called Outlook Web Interface. So far, Microsoft has not looked at any lightweight web mail clients and ported them to MS Exchange, meaning I have to use the heavy client they supply for calendaring. Double Ick.

Fortunately the EU has forced MS to publish information about MAPI, and the Evolution folks are working hard on making its namesake work against MS Exchange using the same protocol as Outlook. All this is supposed to ship in Ubuntu 9.04, but as of Alpha 3 Evolution is still back level at 2.24.3. 2.26 (same as the Gnome release number these days) is where the MAPI functionality should ship. There will more about all this over at TalkBMCin the near future.

Other General Impressions

It would not be fair to deeply judge Ubuntu 9.04's current state at Alpha three as being totally indicative of what it will be in April when it releases. Everything that is in is working, and smoothly. The boots seem faster. I'll give it a whirl on the Acer Aspire soon, and see how it works there, but I expect that it will be faster than the current Ubuntu 8.10 based Mint 6 is.

I was slightly disappointed when Ubuntu 8.10 shipped without OpenOffice 3.0, and that has been fixed in 9.04. Firefox, at 3.05 is current, but since FF 3.1 is at Beta 2, hopefully it will be at 3.1 by Ubuntu release day. This is probably less critical on Linux than on OS.X. I have not had any real issues with FF on Linux. The Mac is a whole other story, and a whole other post...

Dosbox followup

A quick followup to my last post.

Dosbox has not been a 100% troublefree for my dad. The main problem was that the cursor would go away, never to return, after a screenshot. This did not happen on my Acer, so I could not recreate the issue.

Before I made an on-site visit we tried one thing: installing ksnapshot. That fixed it.

I don't know what the problem was, but ksnapshot is better in any case, because it allows just the window under the cursor to be captured, and without the window borders. No editing required.

It is funny in a way that the KDE screen capture works better on Gnome than the Gnome one does, but that is the beauty of interoperable open standards: best of both can be used.

The other problem is that a new mouse he bought is not working. A Microsoft wireless mouse.

I don't have one of those at home to test either, but I do at the office, and that one works OK. I am thinking bad hardware here, but if he trades it out I hope he gets something I have: Kingston or Logitech. Easier to do remote support when I can replicate the environment. That's why our labs at the office are so big!

[Posted with iBlogger from my iPhone]

Ubuntu 8.10, DOSBOX, and the single HP dv9000.

It would be fair to say that my dad is an intimidating person. Not because he is 6'3", an athlete, or any of those things. Because (to my way of thinking) he is brilliant. Rachel Maddow Brilliant, but without the liberal side. He is technically intimidating. He has 22 patents, and has filed for another 10. Normally I could care less about such a thing, but his are non-obvious patents, and deserve the protection of a patent and the patent system. His are the reason that there even is a patent system. He is not trying patent goofy things like mouse clicks on menu items but very technical stuff, like how much microwave energy, and what kind of antenna (size, shape, power) is required to fuse moon dust to a particular depth.

I knew growing up that I was never going to equal my dad in technical accomplishment. It was not something that made me sad or anything. I was always too much a mix of my parents (Mom being a Nurse, and very brilliant as well) to ever be one or the other. Mix the two and you get a Linux / Open Source person, more or less.

Over the holidays I was at Dad's house and I came to ask him about some programs he had written and how they were backed up. It turned out that the following was true:

1. Dad had a series of engineering programs
2. The programs were in VBDOS
3. VBDOS barely worked in Windows 2000, less well in Windows XP, and not at all in Vista.

Visual Basic has left DOS way behind, but VBDOS did everything Dad needed it to do. Why waste time learning the new program, and all its goofy new things. VBDOS worked. VBDOS was a tool. A means to an end. Visual Basic 6 offers nothing that VBDOS did not, at least as far as Dads programs are concerned. Dad needs to know that then X amount of power is applied via an antenna of a particular design, how deep is the moonrock melted? Nothing in VB 6 adds to that. Taking time to learn the new programming paradigms of GUI based VB is time taken away from pursueing the knowledge.

Enter DOSBOX. http://www.dosbox.com/

With DOSBOX (and probably but not tested, DOSEMU), VBDOS lives on.

The Acer Apsire One

While at my dads house over the holidays, I asked him how the project to keep VBDOS running was going, and how he backed up his programs. The answer was that his program directory from his Windows 2000 computer was copied to a Windows XP computer, and a new Windows Vista HP laptop, and a USB fob. With XP the VBDOS programs ran but did not print. With Vista, they were just dead.

I asked for the fob. I copied them to my Acer Aspire One (because, is not the point of having the AAO that you always have it with you?). I then installed DOSBOX, and read the install info for it quickly. Mounting Dads programs in DOSBOX, they ran at once, without issue, and were printable. Editable screen shots via GIMP even.

I have never tried to convert my Dad to Linux. He has always run Windows, and while I have rebuilt his computers a few times when they were infected with things, in general it seemed wrong to try and get Dad to convert. He is much smarter than me, and an engineer par excellence. If MS Windows works for him, then there is no need to convert him.

I had watched the VBDOS stuff over the years and had wondered is MS was going to maintain their compatibility... and while I doubted it, there was no need to talk about it as long as it worked.

The HP dv9000 changed all that.

Dad bought the dv9000 with Vista Home Premium. He had no choice in that matter, or at least he thought. Vista worked for email, and Flock worked for browsing (Dad knows better than to use IE) but his VBDOS programs were busted. Dead flat broken. VBDOS had left the building. It was an Ex-programming language. 20,000 volts would would not revive it.

Dad saw the Acer running the programs. He asked if his HP dv9000 laptop could do the same. 20,000 volts: No. Linux / DOSBOX? Yes.

The DV9000 was new: less than 3 months old. It had a AMD Turion 2.1 Ghz dual core 64 bit processor, and an Atheros 5007 chipset for wireless. The latter bit was the same as the Acer Aspire One. I said it probably would work and was put to the test two days later when I came back over to install it.

dv9000

The HP dv9000 has a 1440x1024 screen, a ton of USB slots, an NVIDIA graphics card, and other fun things. I looked it over and decided to try Ubuntu 8.10 as my first pass. All Dad needed was DOSBOX, but I wanted it all to work. I was going to set it up as dual boot Ubuntu 8.10 / Vista, but I wanted Ubuntu to be all Dad ever needed. Mint 6 was also an option, but I was worried that it might barf on the recent hardware. In my recent experience, Ubuntu had done better than Mint on new hardware.

According to things I found on the Internet, the dv9000 used to have, in older configurations, Broadcom wireless cards. HP has recently embraced Linux though, and it appears that part of that is using Linux friendly gear like Atheros. Or maybe it just worked out that way. Maybe Atheros was just the less expensive card at the time this dv9000 was built. Worked for me either way. Broadcom cards can be made to work under Linux, but Atheros had open sourced their HAL, and I like to support companies that support Linux / Open Source.

The good and the bad of the hardware support of Ubunti 8.10 for the HP dv9000 ultimately came down to the 802.11 card. Once installed, Ubuntu was not happy with the Atheros card. When I used the hardware managers and *disabled* Atheros support, all was well. I had to do the exact same thing on the Acer Aspire One.

I ran the Ubunut upgrades. The Atheros support crapped out. Same as the Acer Aspire One. It appears to me that it all worked out this way:

1. Linux reverse engineered the HAL for Atheros cards, and they worked.
2. Atheros released the specs for the HAL and the firmware of their cards.
3. The MADWIFI project released a bad series of drivers for Atheros cards... based on the newly Opened drivers and HAL. Go figure.

It may be more complicated that that. That is just what it looked like out in end-user land. It matters not for this project: I have documented getting the Atheros cards going via NDIS in one post and via the new native drivers in another post.

Installing Ubuntu 8.10 was not hard, although it was confusing a bit at times. The dv9000 had two partitions as it arrived from HP: SDA1 was Vista, and SDA2 was the recovery partition. 52 GB and 10 GB used in total and respectively. 160 Gb hard drive. Plenty of room.

I had Ubuntu shrink SDA1 from about 148 GB down to 72 GB. With 52 GB in use, that left 20 GB for growth. I left SDA2 alone: 12 GB with 10 Gb in use. Here we hit an oddity of the installer. It looked stuck. Like nothing was happening during the resize. I popped open a terminal, and started 'top', and could see 'ntfsresize' was hopping all over the place. It was clearly doing things, and was not stuck. The on screen graphic progress bar just had no insight into what it was doing.

I inserted a new SDA2 and SDA3: SDA2 was '/' and was 10 GB. SDA3 was '/home' and was about 62 GB. SDA 2 of old became SDA4 of new, but was not re-sized or moved. SDA4 (The Vista recovery partition) lives at the end of the disk.

GRUB thought the SDA1 and SDA4 were both Vista partitions, so as a post-install step I went into /boot/grub/menu.1st and made SDA1 Vista and SDA4 Vista Recovery. Just labels, but important. I booted both to be sure that they still worked.

I booted Ubuntu and applied all the service, and installed a few more programs like Avahi, Macutils, HFS support, Sensors/hddtemp, and set up monitors in the Gnome taskbar for system speed and temp. I like to watch that kind of thing, and I was very interested in having it on this computer so I could watch it while the VBDOS programs were running.

This was the first computer I have ever set up without a swap partition. Another reason for having all the system status stuff enabled on the task bar was to watch memory usage. With 3GB of RAM, and the primary mission being to run 16 bit VBDOS programs, I did not think that it would ever have memory issues. It was just a theory though, and I wanted to be able to watch it. So far, so good.

DOSBOX

Once everything was up and running and all the service has been installed I installed DOSBOX using Synaptic. Nothing major or weird there. Then I copied Dad's programs into his home directory from the USB fob. They were put into a new subdirectory called 'vbdosprograms'. Next I started DOSBOX (from "Applications / Games"), and mounted the programs to the 'C' drive:

mount c ~/vbdosprograms
c:

'alt-enter' toggles DOSBOX to full screen and when running like that it looks just like a DOS computer of old.

The rest, as they say, is history. It all worked, and better than than it ever had under XP. Screen caps with Fn-PrtScrn worked like a champ. GIMP could edit those to whatever was required. They could be saved in whichever directory made sense from that point on.

From a technical point of view, this capability exceeds anything Dad has ever had before. He can now run on the latest, fastest hardware, and has far more control over the results. He now also has Linux support. It is not that I did not support him on MS Windows. It is just that for me MS Windows is just another computer platform and I often have to sit a mess with it to figure out why it is broken, whereas Linux is something I know fairly well.