Talk:Ubuntu Gutsy On OLPC XO

From OLPC
Revision as of 18:58, 12 May 2008 by Twt (talk | contribs) (added notes about wpa_supplicant, answered disk question)
Jump to: navigation, search

Please ask your questions and post comments about installation of Ubuntu on the XO here so that all may benefit :D

- I'm finding a few discrepancies regarding wpa_supplicant but before I correct the actual page I'll put a couple of notes here. On this version of wpa_supplicant there's no space between -c and the path, so the actual string should be:

$ sudo wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf -B

- The reason I'm not updating the page yet is because although I can get networking going when I issue these commands, I can't get it to start automagically on boot OR using wifi-radar. When I issue the terminal commands I get some odd error messages, but the networking starts anyway. So there's something wrong with what I'm doing. Google searches imply it's some funkiness in the wext driver. Twt 18:58, 12 May 2008 (EDT)

So what's the disk drive driver on the XO? During the QEMU installation it doesn't detect a hard disk and asks me to choose from a list. Any ideas?

  • It sounds like you didn't specify an image to install to -- go back to the beginning and check your qemu settings very carefully. Twt 18:58, 12 May 2008 (EDT)


- How much of these instructions are Ubuntu-Specific? Could another distribution, such as DSL or Puppy, be made to work the same way?

  • I think any recent linux could work. For Ubuntu I used the kernel from the original Red Hat and the modified xorg packages based from Debian as it was being developed to use the hardware display accelleration. Ubuntu had to be modified to use sysvinit instead of upstart because of how the kernel was configured. - Freelikegnu

- So basically If I had a working recent distro on a USB I could do step 7 (copy boot and other files from the XO) and it would most likely work?


When I install sysvinit, at the end I get "init: timeout opening/writing control channel /dev/initctl". I assume this is related to the note that upstart wants to be PID 1. Is this error important, or can I forge on despite it? 206.248.174.6 11:30, 3 February 2008 (EST)

So I forged on despite the error, and in the middle of installing xorg/xfce I started getting error messages every 2 seconds that start with ata2.00. I assume these are the ata errors that the instructions say are harmless. However, when I try to shutdown (sudo halt) I get "shutdown: timeout opening/writing control channel /dev/initctl". I rebooted with reboot -f and the ata errors reappear during startup (right after the "starting system log daemon" line, I think). 206.248.174.6 12:05, 3 February 2008 (EST)

Cleaning up Sugar afterwards?

Any instructions on how to get rid of all the bloat associated with Sugar and activities, after we've successfully installed Ununtu? After all, no point in having 2 OSes taking up space, is there? 207.34.120.71 12:55, 5 February 2008 (EST)

Speed of boot?

I just tried this using an 8 GB SDHC card from PQI. It's a 66X card. How quickly should the XO boot? For me, I see OpenFirmware load sd:\boot\olpc.fth with the correct command line, then it stops. No text scrolling, no advancement past that screen. I let it sit for a while, too: at least 10 minutes. I've followed the instructions to the T. I was using OLPC firmware 656 while readying it. Any ideas? Colin 01:59, 19 February 2008 (EST)

You need to force into check mode or you won't get prompt at the end of boot (it might still be working behind the scenes). Hold the check mark key at startup to force it, I ended up editing out the alternate option so it would only go in check mode (one of the .fth files had an extra option that seemed to get in the way).

Installing back-ported xorg drivers

I'm having problems installing the new xorg drivers that Holger Levsen back ported. When I start apt-get update, it throws the error about no public key for the layer-acht etch release, and says run apt-get update to correct the problem, which obviously doesn't work. If I go ahead and try to install it anyway, I get a broken packages error. Any ideas?

No new ideas here, but that is exactly what I ran into as well...

Issues using Hardy

  • I've opted to install Hardy on my SD card. I've got it running fairly well and even Network Manager is functioning properly. However, I've got gigantic fonts in XFCE and all X programs. I am unsure of how to correct this. I can get a "normal" sized terminal by using a font size of roughly 7, but changing the XFCE DPI setting had no effect. Running 'xdpyinfo' shows that the DPI is 201 which is the same as when running under Sugar. Any ideas on how to fix this?

Differences for using a 1GB UDB?

  • I assume we should make the initial partition smaller for if using a 1GB usb drive?

Issues using Ubuntu in VMware

  • Any issues one might foresee? I'm plugging along on it now, and have had only minor blips.

Error with custom olpc.fth : "unrecognized program format"

A solution comes from here: http://www.olpcnews.com/forum/index.php?topic=1436.150

User linuxspice says, "...for olpc.fth this first line must start with a "\ " - i.e., a backslash followed by a space character. So a single "\" won't work, but a line such as "\ My olpc.fth file" will. ... If the firmware finds a "\ " (backslash, space) at the beginning of the olpc.fth file, it will treat it as a real Forth script, otherwise it will treat it as a binary executable."

Multiple Partitions

I am using an 8GB USB stick, and I do not want to install this into the first partition. At first, I (foolishly?) thought I could get away with making the dd outfile of=/dev/sda3. Unfortunately, that created an unreadable partition within partition 3 (/dev/sda3p1). I already have an alternate boot on sda1 that I want to keep (and it is only one GB, anyway), so what do I do? Is there some way to copy the image into partition 3 or do I have to emulate that somehow? If I use the emulator, and there are two empty partitions, dd will most likely overwrite empty partitions to my device -- replacing my partitions, right?

So, to restate: Is there a way to write the image to anything but the raw usb device?

--LuYu 14:24, 9 May 2008 (EDT)