OQO
From [WearLab]
Contents |
OQO Configuration:
External Sources:
- Screen Rotation works as described on [1]
External Monitor:
The external monitor unter GNU/Linux works fine and can be changed with the OQO Display Tool. Nevertheless the keys Fn video does not work to change the OQO display.
Mouse and Powermanagement:
udev must be running to support the tracpoint and powermanagement functions.
Powerlevel:
Using the kernel from the OQOLinux enables the powerstepping functionality. The OQO will switch to 33% if it is idle.
The maximal powerlevel can be controled with longrun. Make sure that the modules cpuid and msr are loaded.
Setting up Grub for dual boot System:
Since the OQO overwrites the MBR everytime time Windows is started you can set up a dual boot system, adding grub to the windows boot loader. There are two possibilities. You can use an image of the GNU/Linux Grub or use the Windows Grub.
GNU/Linux Grub:
Configure grub:
After you set up your grub config (/boot/grub/menu.lst) which should look something like
timeout 5 default GNU[[/Linux]] title GNU[[/Linux]] root (hd0,5) kernel /vmlinuz root=/dev/hda6 resume=/dev/hda5 initrd /initrd.img title Windows XP chainloader (hd0,0)+1
do a
grub-install /dev/hda2
to install grub so the root partition of your GNU/Linux distribution.
Get grub image:
Get an image of the mbr of that partition with
dd if=/dev/hda2 of=grub.bin bs=512 count=1
and save it on an extern disk or host in order to copy it to your windows partition.
Integrate grub into Windows bootloader:
- Copy the grub.bin to C:\
- Make the C:\boot.ini writable with
ATTRIB -R -H -S C:\boot.ini
- Edit the c:\boot.ini and set the timeout to something larger than 0.
- and add a new line c:\grub.bin="Linux" as seen below.
[boot loader] timeout=5 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons c:\grub.bin="Linux"
- Change back the rights of C:\boot.ini
ATTRIB +R +H +S C:\boot.ini
Note: Make sure that you remove and add the writelock of the c:\boot.ini from the same comandshell.
Windows Grub:
If you don't want to get the grub images and copy it to the Windows partition you can use the Windows Grub.
Integrate grub into Windows bootloader:
- Make the
C:\boot.iniwritable with
ATTRIB -R -H -S C:\boot.ini
- Edit the
C:\boot.iniand set the timeout to something larger than 0. - and add a new line
C:\boot\stage1="Linux"as seen below.
[boot loader] timeout=5 default=C:\boot\stage1 [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons C:\boot\stage1="Linux"
- Change back the rights of
C:\boot.ini
ATTRIB +R +H +S C:\boot.ini
Note: Make sure that you remove and add the writelock of the C:\boot.ini from the same comandshell.
Configure grub:
Open a command shell (Start -> Run and enter cmd)
Go to C:\boot if you unpackt your Grub there (default).
Set up your menu.lst as you would for the GNU/Linux Grub.
Do a
grubinstall.exe -m menu.lst
to install grub.
Wireless LAN
The wireless LAN on the OQO was so far unreliable under linux and only worked when windows was booted before and a warm start was used to boot linux. Aparently this changed since Mai 2nd: [Posting on handtops]
Psinewave: I didn't notice it mentioned in this thread but it looks like the current CVS version (2006-05-03) of the Berlios Atmel at76c505a wireless LAN driver is now stable on the OQO 01+ with Fedora Core 4 and a reasonably standard (apart from the Transmeta stuff) 2.6.15 kernel ... I've had it sitting on my desk pinging away with SSH sessions for a couple of hours without dropping any packets ... the only change I needed to make was to add the vendor and product IDs (1557:0002) as mentioned in the original post.
Tom: I got the new WLAN driver running on our machine. Everything looks fine.
Use the kernel module usbvnet5A.
Update: According to tom, there is a problem with the driver on OQO 01. 01+ seems to work fine. --Kenn 15:11, 12 December 2006 (CET)
Power Button
Edit /etc/acpi/events/powerbtn to halt.
Ethernet
The OQO 01+ has a different Ethernet module than the OQO 01. I patched the rtl8150.c to include the product id 7720, but it does not work.
Does anybody have a solution to this problem?
Update: according to http://www.handtops.com/forum/752/4//OQO_Linux_Installation_amp_Configurati.html# there is a driver called "asix" that can be patched with the 1557:7720 vendor and product id to make the ethernet work on the oqo 01+. The driver is contained in the current 2.6.19 kernel, but not in the 2.6.10-oqo-5 kernel. --Kenn 15:54, 12 December 2006 (CET)
See Also
see also: OQOWearable
