Hi! > > > > https://github.com/hackerspace/olpc-xo175-linux/wiki/How-to-run-an-up-to-date-Linux-on-a-XO-1.75 > > > > > > > > I didn't test it yet -- will do when I get home in the evening. > > > > But > > > > chances are it's good enough and I guess you'd be able to get it > > > > working even if I messed up some details. > > > > Instruction say make, but you really need to do make zImage and make > > mmp2-olpc-xo-1-75.dtb . > > Have you tried? I'm typically doing just a plain "make". > > According to "make help", a plain "make" (assuming it's equivalent to > "make all") includes "zImage" and "dtbs" targets. I believe I did, but not 100% sure. > > Instructions say "make -j", which is nice way to crash a machine. I > > suggest "make -j 8" :-). > > Holy... what sort of a machine do you have? Thinkpad X220. Is it too big or too small? :-). 4 threads, so I usually use -j 5, but -j 8 should be for my notebook and also bigger servers. > > Ok, I think I followed the instructions. I am using empty root > > filesystem, just with /boot -- want to see kernel messages first > > before I mess with the userland. > > > > But I don't get kernel messages during boot: > > > > OLPC 1B1, 512 MiB memory... > > OpenFirmware Q4C02 EC Frimware 0.3.02 > > "Frimware" -- I assume you don't have a serial console hooked on? :) Not :-(. Altrough.. maybe I do have that cable somewhere, I just never used it. > > Type any key to interrupt... > > (but keys do not interrupt anything, ouch). > > In my version of the OLPC OF the routine is replaced with one that only > accepts the Escape key, because kids like to press random keys without > really wanting a shell. Maybe try that one? Ok, will try. > > And that's it, cursor and no kernel messages. > > > > Any ideas? > > > > Could I get prepared binary zImage for testing? > > https://github.com/hackerspace/olpc-xo175-buildroot/releases > > Here's a SD card image that works for me. The topmost commit in the > same repository is the build configuration that was used to generate > it: Kernel works for me with this one. (First boot userland boots, then blinking cursor; next boot filesystem is corrupted. Hmm.) Feel free to add "Tested-by:" to patches this uses. > Note it is only going to boot off the SD card, because the root= > argument is hardwired in the devicetree. Sorry about that -- I built > the image before I noticed you're booting off an USB stick and I don't > have the resources to regenerate the image at the moment. No problem, I have SD cards here, too. > If this won't boot for you, we may need fixes for older FW. Until then > it might be a good idea if you just update to the latest one (it is as > easy as booting the last version of the stock distro with a charged > battery pack). I'd need more instructions for firmware update. Or maybe ... lets ignore that. SD card is fine, and I don't want to brick it. I already broken it enough that keys need to be held during boot (or it does not boot). Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
