**** BEGIN LOGGING AT Thu Dec 17 02:59:58 2009 Dec 17 17:05:24 ok does anyone have any how to's on install Linux on Palm Treo 650? I have read that GPE was running on them but not able to find any how to. Dec 17 17:41:09 shane_: get Treo650 kernel and get GPE image from auryn Dec 17 17:41:49 hm, auryn seems to be dead Dec 17 17:42:02 |miska|: does auryn works for you? Dec 17 17:43:27 |miska|: server is alive, but web seems to be down Dec 17 17:45:28 Sleep_Walker, well, I managed to get opie working, based on this: http://blog.mikeasoft.com/2007/06/30/im-in-ur-treo-linuxin-ur-phonez/ but was kind of interested in the gpe Dec 17 17:46:03 does one work better than the other? I mean, opie doesn't run the phone, so, that is kind of useless, it is neat, but not really usable. Dec 17 17:47:00 Sleep_Walker, what is auryn? sorry this is all new to me, I do run Linux on desktop, but just started playing around with linux for mobile Dec 17 17:47:49 http://auryn.karlin.mff.cuni.cz Dec 17 17:48:08 it's server where miska built his images Dec 17 17:48:16 but it's offline Dec 17 17:48:32 GPE is almost same pain as OPIE Dec 17 17:48:37 try Illume instead Dec 17 17:48:49 raster's illume image Dec 17 17:49:02 ok, where can I get illume, I have got cocoboot working Dec 17 17:51:49 http://hackndev.com/node/212 <-- now this is looking a little more familiar! I'm liking the looks of that Dec 17 17:54:04 Sleep_Walker, ok, found it Dec 17 17:54:40 Illume is really great Dec 17 17:54:54 I have it on my Treo680 and finally it is usable :) Dec 17 17:55:04 how about debian? I'm a Debian fellow anyway, well Ubuntu Dec 17 17:55:12 downloading now Dec 17 17:59:06 ubuncrap != debian ... it just fscks debian up, pity Dec 17 17:59:14 :D Dec 17 17:59:34 shane_: I've got debian on Treo680 and it's quite fine Dec 17 17:59:51 it's slow, but stable and there is lot of programs :b Dec 17 17:59:51 * marex has debian on his protoboard and it's awesome Dec 17 18:00:00 KDE4 runs fine ;-) Dec 17 18:00:21 I'm using E17 on my notebook too :b Dec 17 18:00:25 KDE4 is evil Dec 17 18:00:32 sloooow Dec 17 18:00:38 slooooooooow Dec 17 18:00:44 diiiiiiiiiiieeeeeeeeeee Dec 17 18:00:47 0verkill ? Dec 17 18:00:59 I can run KDE4 applications in E17 faster than in KDE4 :b Dec 17 18:01:11 nope, I finally got to Treo hacking again Dec 17 18:01:25 Sleep_Walker, lil' Lobo fell asleep ? Dec 17 18:01:33 I'm at work Dec 17 18:01:37 :D Dec 17 18:01:59 btw. suspend works again, udc/g_ether too Dec 17 18:02:26 I'll try also TX and LD, but I have both a bit disassembled :b Dec 17 18:02:42 I can lend you some TX if you need one ... Dec 17 18:02:42 TX - prepared for adding another (true) reset button Dec 17 18:02:53 LD is somehow dead Dec 17 18:02:57 Sleep_Walker, you're not soldering it, Metan is, right ? Dec 17 18:03:08 well, we'll see Dec 17 18:03:14 Sleep_Walker, do it not ! Dec 17 18:03:17 I won't wait till Metan returns :b Dec 17 18:03:25 Sleep_Walker, you can kill yourself (and maybe even someone else) if you do so ... Dec 17 18:03:33 but Yokotashi can help too Dec 17 18:03:36 maybe Dec 17 18:03:42 Sleep_Walker, you're useless with soldering gun/iron Dec 17 18:03:50 Sleep_Walker, hm ... oh well Dec 17 18:03:50 really? Dec 17 18:03:54 I never tried :b Dec 17 18:05:53 Sleep_Walker, really, I will have to give debian a try, maybe later, ok, gotta run for now, thanks!!! Dec 17 18:06:49 you're welcome Dec 17 18:26:24 <_01000101_> I'm new to coding for ARM devices. I'm trying to get a "bootloader" going for the PXA270 chipset (using QEMU as the emulator) and can't figure out how to read/write to anything but the ROM, any advice/ideas? Dec 17 18:57:37 ask marex when he gets back Dec 17 18:57:55 <_01000101_> Sleep_Walker: Ok, thanks. :) Dec 17 18:59:37 np Dec 17 19:37:07 Sleep_Walker, is the illume thing setup for 3 partitions on the SD card like this: http://hackndev.com/node/212 Dec 17 19:38:01 I can't remember :b Dec 17 19:38:27 Sleep_Walker, no prob, I will tinker around with it a bit, if I can't get it I will go straight for Debian. :) Dec 17 19:40:08 use emfox's release as default and update it Dec 17 19:40:26 in FSO debian repo you can find Illume as well - that is my current configuration Dec 17 23:08:58 ok, following this guide: http://hackndev.com/node/212 but using emfox's release, how long should it take to boot up? roughly? Dec 17 23:09:31 in cocoboot I hit boot, and it seems as though it locks up, and I'm not sure how long to let it set and cook. Dec 17 23:10:26 With opie, it went straight to a command prompt, and started running through a normal boot up, this just stays on the cocoboot screen, and doesn't respond to any buttons. Dec 17 23:16:15 same kernel? Dec 17 23:16:38 these coco things are bundled right? Dec 17 23:35:28 tmzt, who me? I think that is part I'm having trouble with, I'm not 100% sure what I'm doing Dec 17 23:35:49 yes Dec 17 23:36:32 well, the other issue is that I have a treo 650, and emfox has info for the 680, and I'm using SleepWalker 's 680 kernel stuff, or tried to Dec 17 23:37:04 perhaps I should just go back to the alex's old 650 how to, and strictly follow that? Dec 17 23:37:09 then you need the correct keernel Dec 17 23:37:27 can you can configure which zImage to use with coco? Dec 17 23:37:35 tmzt, kernel in the mobile lingo is the zImage file? Dec 17 23:37:40 I don't know, not worked with arm based palm much Dec 17 23:37:49 in the mobile lingo? Dec 17 23:38:01 zImage is a linux kernel image Dec 17 23:38:07 mobile linux linguistics? :) Dec 17 23:38:34 mobile linux language Dec 17 23:38:38 there that is it. Dec 17 23:38:58 wow, probably dating myself there Dec 17 23:39:38 with sleep walker's kernel, cocoboot doesn't recognize it, even with the config file pointing there, it says no kernel found. Dec 17 23:40:06 do I need to rename his kernel to strictly zImage, and delete the .T680.sw5 stuff? Dec 17 23:40:57 tmzt, ^^^^ Dec 17 23:41:49 I guess Dec 17 23:41:56 linguistics is old? Dec 17 23:42:16 no I thought perhaps lingo was no longer used, therefore you lingo? :) Dec 17 23:42:21 you have 680? what is the package for Dec 17 23:42:35 simple thing, take zImage of working package and rename Dec 17 23:42:37 no I have a 650, and the package is for 680 Dec 17 23:42:41 copy to broken one Dec 17 23:42:53 then you need a 650 kernel Dec 17 23:43:32 tmzt, ok, that is what I was thinking, I have a working zImage, that I used with opie, is that a completely different kernel? Dec 17 23:44:01 it's for 650 Dec 17 23:44:05 you need it Dec 17 23:44:11 tmzt, correct Dec 17 23:44:15 different than the broken one? yes Dec 17 23:44:22 both are linux Dec 17 23:44:28 opie is just a userland Dec 17 23:44:41 either kernel would work on the correct hardware most likely Dec 17 23:44:54 unless you need modules then you probably have to mount root Dec 17 23:44:59 or repack the initrd Dec 17 23:45:00 well, that is where I start to get confused, because I don't know who opie, gpe, ect are, I suspect they are arm based linux things Dec 17 23:45:09 no Dec 17 23:45:36 they are X desktop environments (except opie) that are crosscompiled for arm linux Dec 17 23:45:52 ahh, see, that is where I'm lacking my education. Dec 17 23:46:11 anyway, running debian is something much more familiar to me. Dec 17 23:46:21 same as on desktop, same kernel works with gnome, kde, enlightenment etc. Dec 17 23:46:29 so run debian :) Dec 17 23:46:54 wiki.mameo.org/Mer and #mer Dec 17 23:47:01 but you need a working kernel first Dec 17 23:47:02 right, that is what I'm trying to do. :) Dec 17 23:47:20 then don't worry about opie Dec 17 23:47:21 so the kernel that worked with opie should in theory work? Dec 17 23:47:26 yes Dec 17 23:47:31 it's all linux Dec 17 23:47:49 I know that linux in general shares the same kernel pool, Gentoo, Debian, Fedora etc. Dec 17 23:49:00 yes Dec 17 23:49:06 same on mobile Dec 17 23:49:26 ok, now we are getting somewhere,: could not mount root fs: init failed! Dec 17 23:49:35 okay Dec 17 23:49:42 what is your cmdline? Dec 17 23:49:48 add rootdelay=5 Dec 17 23:49:56 root=/dev/mmcblk0p1 Dec 17 23:49:58 or 2 Dec 17 23:50:33 ok,, I think it is the rootdelay I need, I have mmcblk0p2 because I have 3 partitions on the sd card Dec 17 23:51:13 oh, to my surprise I have rootdelay=1 I'm uping that to 5 and try again Dec 17 23:52:00 oh here is the fancy line from SleepWalker: cmdline = init=/sbin/init root=/dev/mmcblk0p2 psplash=false rootwait Dec 17 23:52:17 perhaps rootwait would work? Dec 17 23:53:33 maybe Dec 17 23:53:40 what kernel version? Dec 17 23:53:54 you have an armel root on sd card? Dec 17 23:54:19 hmm, I'm not sure what kernel version, and armel root? not sure either. Dec 17 23:54:53 all I really know is I got opie to boot, with over simplified instructions. Dec 17 23:56:40 ok, I keep adding one thing from his line above, to see if that helps, still getting the error. Dec 17 23:57:23 no, what os is on the sd card? Dec 17 23:57:38 oh, the debian one Dec 17 23:57:55 ah, that error means it doesn't see the card or can't mount root at all Dec 17 23:58:03 from here: http://hackndev.com/trac/wiki/DebianOnTreo680 Dec 17 23:58:30 ok, so my card is not being seen! we can guess? Dec 17 23:58:34 does it list partitions in the error? Dec 17 23:58:36 yeah Dec 17 23:58:38 likely Dec 17 23:58:45 increase rootdelay=7 Dec 17 23:59:05 remove and reinsert if you can during boot Dec 17 23:59:10 maybe try 20 even Dec 17 23:59:17 what kernel version? Dec 17 23:59:51 hmm, I'm not sure about the kernel version Dec 18 00:00:17 I can try this kernel: http://releases.hackndev.com/palmt650-20081005/ Dec 18 00:00:41 need to know Dec 18 00:00:48 otherwise you need an initrd Dec 18 00:01:00 try people.openezx.org/tmzt/initfs.img Dec 18 00:02:46 ok, tried a new kernel, from the one I just posted, it gives me a different error: unable to mount root fs on unknown -b10ck(1.) I think, the font is super tiny Dec 18 00:03:10 ok Dec 18 00:03:16 still doesn't see it Dec 18 00:03:20 1,x ? Dec 18 00:03:22 not likely Dec 18 00:03:33 what root= did you use? Dec 18 00:03:58 I tried the mccxxxxx2 trying 1 now Dec 18 00:04:30 ok, with one it just hangs there on the cocoboot, and I don't get a kernel loading or nothing, or doesn't seem to. Dec 18 00:05:21 ok, with the img file, I just put that in the root directory of the card too? Dec 18 00:05:53 and edit my cocoboot.conf file accordingly? Dec 18 00:06:18 yes Dec 18 00:06:21 as initrd Dec 18 00:06:39 ok Dec 18 00:07:49 ahh, I think I left it as 1 Dec 18 00:09:01 ahh, Sleep_Walker do you have a 650? or 680? I guessing you have a 680? Dec 18 00:09:28 tmzt, no go with the img file Dec 18 00:09:30 I have both Dec 18 00:09:42 Sleep_Walker, ok, I need a working kernel and os for the 650 Dec 18 00:10:03 Sleep_Walker: he's trying to get a debian root working Dec 18 00:10:13 what kernel version is 650 on? Dec 18 00:10:19 I think you mentioned you used emfox's I tried that one, and didn't get anywhere. Dec 18 00:10:33 or, I messed it up, which is possible too Dec 18 00:10:37 and I need some sleep to be conscious to feed son Dec 18 00:10:48 what does it mean? Dec 18 00:10:53 didn't get anywhere? Dec 18 00:11:10 you mean you couldn't run some nice GUI? Dec 18 00:11:12 understood Dec 18 00:11:22 Sleep_Walker, no, if I could get a terminal I would be happy Dec 18 00:11:35 so - where did you got stuck? Dec 18 00:11:40 It won't boot past kernel, keep getting kernel panic Dec 18 00:11:56 and cant mount root fs. Dec 18 00:12:05 try add rootwait on kernel command line (in cocoboot) Dec 18 00:12:12 did that, didn't help Dec 18 00:12:20 version would help Dec 18 00:12:32 if it's too old no rootwait or rootdelay in kernel Dec 18 00:12:33 also added your init=/sbin/init line or something like that Dec 18 00:12:45 it's not my line :D Dec 18 00:12:48 I gave him a basic initfs that adds them at least to 2.6.21 Dec 18 00:13:07 and swaproots to the mmc card Dec 18 00:13:09 2.6.21 kernel? Dec 18 00:13:17 hmmm Dec 18 00:13:18 tmzt, I'm not really sure how to what kernel version, because the files are just named zImage, Dec 18 00:13:19 handhelds.org Dec 18 00:13:42 I'm downloading most stuff from the hackndev.com site, user accounts Dec 18 00:13:49 which some are old, or appear to be Dec 18 00:13:50 shane_: please, ask me again when I'm at work Dec 18 00:13:58 Sleep_Walker, ok, no prob Dec 18 00:14:13 now is 1:13 here, I'll be at work tomorrow around 13:00 Dec 18 00:14:20 I'll keep tinkering away with it, perhaps I will stumble across the right combo Dec 18 00:14:28 does coco support initrd? Dec 18 00:14:32 yeah, get some sleep, thanks Sleep_Walker Dec 18 00:14:34 tmzt: yes Dec 18 00:14:42 * Sleep_Walker is sleepwalking Dec 18 00:14:46 what kernel version is hnd now? Dec 18 00:14:48 sorry man Dec 18 00:15:27 tmzt: 2.6.21 is latest working, 2.6.27 is quite rewritten and I was working on arm-devel tree few months ago Dec 18 00:15:50 tmzt Sleep_Walker thanks for the help, I gotta run downstairs and check on the kids, I will log in down there. brb Dec 18 00:17:11 oh Dec 18 00:17:26 the. he needs initrd unless zImage has initramfs appended Dec 18 00:17:33 night then sleep Dec 18 01:31:10 tmzt, ok, do you know how to make this work with an ext2 file? rather than a kernel persay? Dec 18 01:31:29 uh Dec 18 01:31:34 why ext2? Dec 18 01:31:45 have you tried my initrd yet Dec 18 01:31:49 it supports loop Dec 18 01:31:56 the issue is your kernel Dec 18 01:32:11 hmm, what initrd? Dec 18 01:32:31 the img file, I did try that earlier Dec 18 01:33:10 well, because illume has an ext2 file see here: http://hackndev.com/trac/wiki/Bootpacks That is where I'm getting all my downloads from. :) Dec 18 01:34:02 tmzt, illume's file is an ext2, which consequently worked for opie, however, I'm more than willing to try about anything. :) Dec 18 01:35:04 how did you try it? Dec 18 01:35:18 I don't k.ow the config file systax Dec 18 01:35:22 syntax Dec 18 01:35:30 it needs to be the initrd Dec 18 01:35:58 right, I don't know the syntax either, but Sleep_Walker has a nicely commented file Dec 18 01:36:15 paste your initrd line Dec 18 01:36:21 tmzt, I used, initrd=initfs.img on it's own line Dec 18 01:36:33 is that right? Dec 18 01:36:47 what does kernel line look like Dec 18 01:36:48 ohh, typo, I mean initrd=/initfs.img Dec 18 01:36:55 no Dec 18 01:36:59 no slash? Dec 18 01:37:06 that is what the comment file shows. Dec 18 01:37:07 the initfs.img must be in the vfat with coco Dec 18 01:37:12 for? Dec 18 01:37:18 tmzt, right, that is where it is located Dec 18 01:37:27 paste kernel line Dec 18 01:37:47 cmdline= init=/sbin/init root=/dev/mmcblk0p2 rootdelay=7 Dec 18 01:38:01 no command line? Dec 18 01:38:03 hmm Dec 18 01:38:08 try " around it Dec 18 01:38:15 if you get the 1,x panic Dec 18 01:38:39 well, I only got the panic, once, the rest of the time, it cannot mount root fs Dec 18 01:38:43 or was it find Dec 18 01:38:49 can't find root fs Dec 18 01:38:58 cmdline="root=/dev/mmcblk0p2 irootdelay=7" Dec 18 01:39:08 cmdline="root=/dev/mmcblk0p2 rootdelay=7" Dec 18 01:39:11 try that Dec 18 01:39:13 ok, I will give that a try Dec 18 01:39:42 also, one other tech question, I assume that the ext3 partition I made doesn't need to be flagged for boot? Dec 18 01:39:58 no Dec 18 01:40:00 part1=vfat 16 part2=ext3 and part3=swap Dec 18 01:40:02 that's ignored Dec 18 01:40:11 ok, that is what I figured Dec 18 01:40:16 type doesn't matter either Dec 18 01:40:18 that caught me once with linux. :) Dec 18 01:40:24 that's only used by an mbr on pc Dec 18 01:40:31 not on arm or by linux Dec 18 01:42:06 ok, that gives me the kernel panic Dec 18 01:42:46 can you recommend a kernel to use? or are we using a funcioning kernel? Dec 18 01:43:03 it functions Dec 18 01:43:05 I think Dec 18 01:43:10 just no rootdelay Dec 18 01:43:14 :) Dec 18 01:43:17 what's the panic? Dec 18 01:43:18 same? Dec 18 01:43:41 wait, my initrd gave you can't find rootfs? Dec 18 01:43:47 or without it Dec 18 01:43:52 yes, couldn't find something at block1 or something, super small font, almost need a magnifying glass Dec 18 01:44:06 hmm Dec 18 01:44:16 and now? what's the message Dec 18 01:44:47 hang on, let me get rid of spaces, and try it again on the initrd line Dec 18 01:44:57 okay Dec 18 01:45:02 and drop / Dec 18 01:45:08 if it's in the same directory Dec 18 01:45:15 yeah, let me try that Dec 18 01:45:23 the bootloader (coco) reads it not the kernel Dec 18 01:45:41 kernel=zImage Dec 18 01:45:46 is another line? Dec 18 01:46:06 lol, I'm missing that line altogether Dec 18 01:46:12 the kernel=zImage Dec 18 01:46:14 lol Dec 18 01:46:28 odd Dec 18 01:46:33 must be the default Dec 18 01:47:57 ok, here is the error: Kernel Panic - not syncing: VFS: unable to mount root fs on unknown-block(1,0) Dec 18 01:48:22 also coco is not finding the intird.gz file, do I need to tar it? can it read raw img instead of a gz file? Dec 18 01:48:48 on the coco screen it says, kernel found, and initrd not found Dec 18 01:49:18 even with that line edited to initrd=initfs.img Dec 18 01:49:25 kernel can read gz, coco shouldn't care Dec 18 01:49:32 ok Dec 18 01:49:45 1,0 is hda? Dec 18 01:50:15 right, so, it isn't accessing or looking for the os at the 2nd partition Dec 18 01:50:46 perhaps, the mccxxxxp2 isn't right? back to 1, or maybe 3? Dec 18 01:51:04 1 causes coco to hang on that screen and not do anything. Dec 18 01:51:06 can you cat /proc/devices on a host please Dec 18 01:51:20 host, my pc? Dec 18 01:52:20 http://pastebin.com/m49537c26 Dec 18 01:52:26 there it is. :) Dec 18 01:56:28 ok, the opie had a linux.boot.cfg file with this: ROOT_DEV=$FILES_MNT/AngstromOPIE_t650-v01.ext2 Dec 18 01:57:38 as the only line, and the cocoboot.conf file was the same, ant the Angstromopie.ext2 file was on the vfat partition, and that booted, that is all there was too it Dec 18 01:58:28 so, I'm thinking that somehow it is not recognizing the part2, or somehow I don't have it right in the config file Dec 18 02:06:42 tmzt, did I loose ya? Dec 18 02:17:11 no Dec 18 02:17:37 shane2peru: just block major 1 from that file Dec 18 02:18:12 ok, what does that mean? Dec 18 02:18:23 where is linux.boot.cfg ? Dec 18 02:18:27 I was playing around with illume's ext2 file, Dec 18 02:18:36 on vfat partition Dec 18 02:18:42 from /proc/devices Dec 18 02:18:44 ok Dec 18 02:18:54 so something sources it Dec 18 02:19:10 what is the block device with major 1 Dec 18 02:19:14 major number Dec 18 02:19:16 thats silliness Dec 18 02:19:23 hey raster Dec 18 02:19:27 help please Dec 18 02:19:27 loopback fs moutns give u a pretty good performance hit Dec 18 02:19:35 ok, with illumes ext2 file, I get kernel panic - not syhncing, attempted to kill init Dec 18 02:19:46 I'm so lost with this cocoboot stuff Dec 18 02:20:11 in other news, there's an X driver for msm devices now and 2.6.32 boots on g1 and magic Dec 18 02:20:18 you! tmzt you have a better handle on this than I do. lol Dec 18 02:22:13 tmzt, perhaps it is seeing that as the treo, and device 2 would be the card? I'm not sure how to specify that in the root= line though Dec 18 02:23:01 no Dec 18 02:23:09 did you check for me Dec 18 02:23:53 not sure what I'm supposed to check, you lost me with that block 1 stuff. Dec 18 02:24:09 I did post my cat /proc/devices Dec 18 02:25:06 just find 1 under block section please Dec 18 02:25:19 I just did it is ramdevice Dec 18 02:25:24 wait, it's scsi isn't Dec 18 02:25:25 oh Dec 18 02:25:26 oh, ramdisk Dec 18 02:25:31 ok Dec 18 02:25:44 I seen somewhere else, ram0 was specified as root? perhaps that? Dec 18 02:25:45 so it's looking for it as an initrd not initramfs Dec 18 02:25:52 hold on Dec 18 02:26:06 how many files are in the folder with coco now? Dec 18 02:26:22 I renamed that file to initrd.img :) as a trial too Dec 18 02:26:27 hmm, quite a few Dec 18 02:26:33 I have other files there too Dec 18 02:26:44 it must match the config file Dec 18 02:28:08 right, ok, I just got rid of all those other files, that will make it easier for me Dec 18 02:29:00 okay, config is called what? Dec 18 02:29:06 make the only lines Dec 18 02:29:15 ok, I have a cocoboot.conf and a linux.boot.cfg, a zImage file initrd.img file and Dec 18 02:29:18 kernel="zImage" Dec 18 02:29:26 no linux.boot.cfg Dec 18 02:29:35 ok, deleting linux.boot.cfg Dec 18 02:29:37 initrd=initfs.img" Dec 18 02:30:01 cmdline="root=/dev/mmcblk0p2 rootdelay=7" Dec 18 02:30:05 that's all Dec 18 02:30:14 name zImage as zImage Dec 18 02:30:25 name my initrd as initfs.img Dec 18 02:30:35 only that and cocoboot.prc Dec 18 02:30:41 try it Dec 18 02:30:55 tell me the result if coco find the initrd and the kernel or not Dec 18 02:31:00 and the panic message Dec 18 02:31:15 also, how is p2 formatted what fs and what distro Dec 18 02:31:23 and is init /sbini/init Dec 18 02:31:27 and is init /sbin/init Dec 18 02:32:42 oh, I have found that mem=32M on the cmd line helps too. Dec 18 02:33:01 how much ram do you have? Dec 18 02:33:03 oh Dec 18 02:33:10 only 32 on the 650 Dec 18 02:33:13 well that could explain some things Dec 18 02:33:26 because initramfs and initrd's bboth take ram Dec 18 02:33:29 perhaps, sorry I forgot about that, that was a key for opie Dec 18 02:33:30 but not that much Dec 18 02:33:40 doesn't explain the panic Dec 18 02:33:49 we have to solve that first Dec 18 02:34:23 ok, what is the init /sbin/init part? I don't understand that part. Dec 18 02:34:42 ignore that Dec 18 02:34:46 ok Dec 18 02:34:47 what os Dec 18 02:34:54 are you trying to boot Dec 18 02:34:57 debian, sid, Dec 18 02:34:59 and what filesystem Dec 18 02:35:05 how did you install it? Dec 18 02:35:06 part2 is ext3 Dec 18 02:35:10 ok Dec 18 02:35:27 how much of the dmesg can you read before pnaic? Dec 18 02:35:32 unpacked someone elses 'pre-cooked' Dec 18 02:35:50 quite a bit, let me give that a go and I will look for any other clues Dec 18 02:36:54 ok, coco is still saying /initrd.gz not found! (-3) before I ever hit the boot button Dec 18 02:37:01 get rid of / Dec 18 02:37:11 I don't have that in my config file Dec 18 02:37:21 restart coco Dec 18 02:37:25 seems like it is completely ignoring that line in my config file Dec 18 02:37:27 see if you get the error Dec 18 02:37:39 I did, just inserted the card, and started coco, and that is what it always says Dec 18 02:37:51 coco version is 0.5.3 Dec 18 02:37:58 root of card? Dec 18 02:38:03 where is the prc? Dec 18 02:38:16 prc has to be in /palm/launcher or it doesn't work Dec 18 02:38:25 all the other files are in root of card Dec 18 02:38:28 ah right Dec 18 02:38:30 ok Dec 18 02:38:34 hmm Dec 18 02:38:55 palmos cards are weitd Dec 18 02:38:57 weird Dec 18 02:39:02 what does boot? Dec 18 02:39:02 yes Dec 18 02:39:30 ok, lots of text here to look at, lots of errors Dec 18 02:40:17 insmod: cannot insert `/lib/modules/led-class.ko`: invalid module format (-1) there are several like these Dec 18 02:40:38 mounting rootfs: not a file or a block device. Dec 18 02:41:53 /media/hdd/gpe-imiage......rootfs.ext2 Dec 18 02:42:13 ls: /media/hdd/gpe*: No such file or directory Dec 18 02:42:16 failed Dec 18 02:42:41 ok, that is a few of the problems, seems as though 1. it is not seeing the partition Dec 18 02:42:59 2. I have the wrong OS setup for 650? maybe? Dec 18 02:43:11 can't be 2 Dec 18 02:43:14 it's 1 Dec 18 02:43:24 what? Dec 18 02:43:27 ohh, here is an interesting line: Dec 18 02:43:55 where is gpe coming from? Dec 18 02:44:22 palmid_ide:version magic `2.6.20-hnd0 mod_unload ARMv5 should be `2.6.21-hnd2 preempt mod_unload ARMv5 Dec 18 02:44:39 so, kernel is not lining up with OS Dec 18 02:44:43 not interesting Dec 18 02:44:48 not os, modules Dec 18 02:44:53 oh Dec 18 02:44:57 (kernel drivers) Dec 18 02:45:01 well, I thought it was interesting. :) Dec 18 02:45:18 are you booting gpe then? Dec 18 02:45:30 that error is on here twice, I don't know where the gpe is coming from Dec 18 02:45:34 start with it's conf file Dec 18 02:45:39 perhaps the zImage Dec 18 02:45:54 cocoboot.conf Dec 18 02:46:07 is there an initrd? Dec 18 02:46:13 hmm, default cmdline Dec 18 02:46:15 possibly Dec 18 02:46:30 is there an extension on your cocoboot.conf? Dec 18 02:46:39 it's on vfat Dec 18 02:46:55 ok, here is the best cocoboot.conf file, documented. http://pastebin.com/m2905f8cd Dec 18 02:46:58 start with thissomewhat working gpe package Dec 18 02:47:03 no Dec 18 02:47:07 start with this one Dec 18 02:47:14 type the relevant lines here Dec 18 02:47:21 kernel, initrd, cmdline Dec 18 02:47:25 cocoboot.conf is named that Dec 18 02:47:33 ok Dec 18 02:47:37 that is all this one is, just has nice comments Dec 18 02:47:57 please Dec 18 02:48:12 paste those lines from the working gpe for 650 package Dec 18 02:48:36 cmdline ="root=/dev/mmcblk0p1 rootdelay=7 mem=32M" Dec 18 02:48:45 kernel=zImage Dec 18 02:48:54 initrd="initfs.img" Dec 18 02:49:02 noprompt = 0 Dec 18 02:49:09 ok Dec 18 02:49:14 cool Dec 18 02:49:15 everything else is fluff Dec 18 02:49:32 yes, but those are mine not the gpe one Dec 18 02:49:36 I need those Dec 18 02:49:43 wait Dec 18 02:49:48 huh Dec 18 02:49:51 that is all there is, everything else is commented out Dec 18 02:49:52 p1? Dec 18 02:50:03 yeah, I noticed that too, and it booted. Dec 18 02:50:09 that boots to the module error? Dec 18 02:50:15 odd, I don't think it is paying attention to that too much Dec 18 02:50:19 I' confusedm Dec 18 02:50:24 want to try 2? :) Dec 18 02:50:34 please paste the lines from the gpe package Dec 18 02:50:35 you and me both, I think the OS is incorrect Dec 18 02:50:43 that booted to the module error Dec 18 02:50:45 gpe package? where do I find that? Dec 18 02:50:55 the one you just booted Dec 18 02:51:03 with the format error Dec 18 02:51:14 there is nothting else, everything else is on part2=ext3 Dec 18 02:51:34 all of that is a /usr /sys /bin etc. the standard linux stuff Dec 18 02:51:41 where is this part2 line? Dec 18 02:51:56 no, that isn't in the config file Dec 18 02:51:56 I'm not understanding you Dec 18 02:52:14 where is initfs.img from, is it mine? Dec 18 02:52:28 I don't know where to find the gpe stuff it was refering too Dec 18 02:52:29 yes Dec 18 02:52:34 your initfs.img file Dec 18 02:52:41 odd Dec 18 02:52:48 try booting this Dec 18 02:52:55 tell me the last output Dec 18 02:53:01 the only other stuff I have is all on the partition which is ext3 and typical linux files Dec 18 02:53:18 ignore that Dec 18 02:53:28 can you scrollback in the boot messages? Dec 18 02:53:31 probably not Dec 18 02:53:53 hmm, didn't try, but I don't think so, let me try again, I will try and put 2 in there this time Dec 18 02:54:09 no Dec 18 02:54:18 make it do what it did before Dec 18 02:55:12 no, can't scroll back up, and too late I used 2 and get all the same errors Dec 18 02:56:02 hey, I can type, but it seems to ignore all typing Dec 18 02:56:07 all the same? Dec 18 02:56:11 my initfs.img? Dec 18 02:56:16 yep Dec 18 02:56:21 anything at all about gpe? Dec 18 02:56:46 yes, same errors as before, regardless of 1 or 2 in the root= line Dec 18 02:56:49 the last line? Dec 18 02:57:13 ide? Dec 18 02:57:21 kernel panic, same as before Dec 18 02:57:27 is it booting as alifedrive or something? Dec 18 02:57:37 I already reset it, but it was all the same as before Dec 18 02:58:04 anything like /media/hdd/gpe-image* ? Dec 18 02:58:05 nope, Dec 18 02:58:13 yep, that is what it said\ Dec 18 02:58:21 it did? Dec 18 02:58:28 so it gets to root somehow Dec 18 02:58:34 this makes no sense Dec 18 02:58:48 same as before: /media/hdd/gpe-imiage......rootfs.ext2 Dec 18 02:58:48 ls: /media/hdd/gpe*: No such file or directory Dec 18 02:59:11 I think the OS must be the wrong setup, let me try and replace that Dec 18 02:59:32 actually, just format it Dec 18 02:59:33 p2 Dec 18 02:59:37 and try this again Dec 18 02:59:44 need to know what's going on Dec 18 02:59:50 ahh, with nothing in p2 good idea **** ENDING LOGGING AT Fri Dec 18 02:59:56 2009