Search results

The thing I always run into when having a seperate home partition (or anything else really), is that I'll always run out of space on one partition , and have loads of it left on the other. This only gets worse when the space is relatively limited, like on the emmc. The seperate boot partition...

u-boot and some distros are in the middle of trying to find a unified way of handling booting on all arm devices. There are still a lot of things to be decided, but extlinux.conf seems to be the way to go. hns his work is really for all his different devices, while mine is for a more...

It's not really fixed to one partition, it just expects that all the files specified in the extlinux.conf are on the same partition as where it found the extlinux.conf itself. I think u-boot digs through the first 4 partitions of a device to find an extlinux.conf before moving on to the next...

Yeah, that's a bit of a problem with the 3.8 kernel, it just doesn't work when compiled with a more recent gcc. I crosscompiled my working 3.8 igep kernel with gcc-linaro-arm-linux-gnueabihf-4.7

Not really, u-boot's bootz command can handle dtb files, the appending is more a hack for older bootloaders that don't have native support for it.  

I'm not using mainline, I'm using the hns kernel from http://dev.pyra-handheld.com/cgi-bin/gitweb.cgi?p=pyra-kernel.git;a=summary Which is probably not too far from the mainline kernel, but I never really looked at all the differences in detail. I'm not that deep into kernel stuff anyway, I...

Not really, Wally has the same board, and the same problem. He did ask igep, but they just point at that officially supported 3.8 kernel, and can't seem to be bothered to upgrade their dts for later kernels. The dts stuff in the kernel changes about quite a bit, so it's not really something...

Screenshots don't say that much about the current state of the OS anyway. What you currently see is mostly the settings that I got tired of having to configure each time I boot a clean image, and that background image is so I can instantly see that everything is in place. The "official"...

That's probably me. Was already busy thinking up my own input daemon, and are discussing things with B-ZaR on irc. What his program currently does is just the absolute basics, things get a LOT more complex when you want to read from multiple input devices, have some events turned into others...

the first run wizard does actually work, but since i've built the last image using the pyra repo instead of my own packages, it ended up using some ancient version that only really shows the welcome screen. I'll fix that, and see if i can update the pandora stuff a bit.

i've been building debian packages and kernels on my board with a sata hd (no ssd) connected since forever. It obviously speeds up everything quite a bit. Swap isn't really needed for most things, when there's 2gb of ram available. Don't expect any miracles though, it still takes 15-20 minutes...

fbturbo is used because it speeds up the 2d bits quite a bit, and there isn't an official debian package for it. the xorg there is obsolete, it's just the debian one, but it compiles it with thumb code disabled. the xorg in debian itself used to crash regularly without that "fix", but it seems...

it should work, but just like booting from a normal sd card, the partitioning and formatting and copying of files has to be EXACTLY right, or it won't do anything. You might have to change the switches on the board to make it boot from emmc though. igep should have some docs on them somewhere.

ignore the boot0 and boot1 partitions, the rest just behaves like a normal sd card, just one you can't remove.

login/password is root/root The normal users are set up in the first-run-wizard I don't remember wally having these issues with his board. The most weirdness he had was caused by him not extracting the rootfs to the sd card as root. Are you sure you're using, and booting, the right kernel...

weird, does the first run wizard show up on the hdmi output ? And did you make sure to copy all the kernel modules and firmware to /lib ?

default parameters are compiled into u-boot itself. usb 3.0 otg not working is normal, TI don't really seem to support it, or have bothered to implement it properly. http://e2e.ti.com/support/omap/f/885/t/275115 and http://e2e.ti.com/support/omap/f/885/t/277258...

u-boot just has a lot of different ways of configuring boot parameters. And every board seems to use a different one. They are trying to make it more standardized though. Just use whatever the example images of your board use, since not all methods are compiled/supported in the version that...

My version of the igep0050 kernel can be found here : http://next.openpandora.org/omap5/kernel/igep0050-3.8.13-0-omap5-a.tar.xz It enables a few options to make systemd work properly, and has aufs patched in for the dbp stuff. This archive adds a lot of wifi modules to the kernel, if you need...

Wifi is just as bad on mine as it is in the normal OS.. in fact, it's worse if i don't run "iwconfig wlan0 power off" first. It also doesn't set the cpu speed, so it's left at the default speed, which is probably slower than what's normally used. No nubs in there either, so you'll have to set...