**** BEGIN LOGGING AT Sat Jun 04 02:59:56 2011
Jun 04 15:10:05 <PBeck> hi
Jun 04 16:35:47 <chrisign> try to change the bootargs_base, but breaks at the loglevel-command: Unknown command 'loglevel=4'
Jun 04 16:36:16 <chrisign> http://nopaste.info/847b8553fb.html
Jun 04 16:39:31 <PaulFertser> chrisign: what are you talking about?
Jun 04 16:39:38 <PaulFertser> chrisign: some u-boot configuration issue?
Jun 04 16:42:08 <chrisign> PaulFertser: right I try to get my OM started with a micoSD-card, but does not work. the kernel can be loaded but with a kernelpanic
Jun 04 16:42:15 <chrisign> because of no root-fs
Jun 04 16:43:14 <PaulFertser> chrisign: let me see your pastebin
Jun 04 16:44:24 <PaulFertser> chrisign: can you rephrase your question please?
Jun 04 16:48:57 <chrisign> the entry I try to edit, can you see above, and this the whole enviroment of my u-boot, dumped with printenv: 
Jun 04 16:48:58 <chrisign> http://nopaste.info/bd9cfff421.html
Jun 04 16:50:04 <chrisign> so the problem is, that I want to install shr on a microSD. this microSD is divided into two partitions
Jun 04 16:50:26 <chrisign> one vfat with the kernel and one etx2 with the whole fs
Jun 04 16:51:07 <chrisign> the kernel can be found by u-boot, but then I get an kernelpanic
Jun 04 16:51:24 <chrisign> unable to mount root-fs
Jun 04 16:56:01 <PaulFertser> chrisign: is this the current version of your env?
Jun 04 16:57:40 <chrisign> PaulFertser: yep just now. after I tryed to set this bootargs_base variable
Jun 04 16:57:59 <PaulFertser> chrisign: but there's no bootargs_base variable in your paste.
Jun 04 16:59:48 <chrisign> its destroyed right now
Jun 04 17:01:03 <PaulFertser> chrisign: when you want to set a long complex variable do it like this: setenv variablename "variablevalue; including; all possible; strange symbols"
Jun 04 17:03:47 <chrisign> as i mentioned I try to write this entry as bootargs_base into my u-boot-shell: http://nopaste.info/529e0801b0.html
Jun 04 17:03:59 <chrisign> PaulFertser: ahhh okay I try it
Jun 04 17:06:34 <chrisign> no doesn't work either
Jun 04 17:07:09 <chrisign> it stops each time after the line with the loglevel-command
Jun 04 17:09:05 <PaulFertser> chrisign: probably you press enter before it?
Jun 04 17:09:12 <PaulFertser> chrisign: do you paste it from somewhere?
Jun 04 17:09:20 <PaulFertser> chrisign: try typing it in manually
Jun 04 17:09:27 <chrisign> http://nopaste.info/3f1f976f0e.html
Jun 04 17:09:40 <PaulFertser> chrisign: i seem to remember it needed slow pasting to work.
Jun 04 17:10:03 <PaulFertser> chrisign: ah
Jun 04 17:10:07 <PaulFertser> chrisign: do not use \
Jun 04 17:10:15 <PaulFertser> chrisign: just type the whole command in one line.
Jun 04 17:10:30 <chrisign>  PaulFertser: no double \ -> \\
Jun 04 17:10:32 <PaulFertser> chrisign: i'm not sure what made you think u-boot allows you to continue lines with backslash :)
Jun 04 17:11:11 <PaulFertser> chrisign: just type it in one long command, without backslashes and linefeeds at all.
Jun 04 17:11:27 <chrisign> okay u-boot is very spartan :)
Jun 04 17:11:55 <chrisign> PaulFertser: I'll try it
Jun 04 17:14:00 <chrisign> PaulFertser: by the way, is the "neo1973-nand: "-adress valid, because I have a gta02?
Jun 04 17:28:03 <PaulFertser> chrisign: only gta02 has nor
Jun 04 17:47:35 <chrisign> okay I put in the whole entry, but got anoter kernelpanic. After log into the u-boot shell everthing was forgotten
Jun 04 17:47:52 <DocScrutinizer> o/
Jun 04 17:47:56 <PaulFertser> chrisign: i guess you forgot to "saveenv"
Jun 04 17:48:01 <PaulFertser> DocScrutinizer: yo :)
Jun 04 17:48:24 <chrisign> No I wrote saveenv bootargs_base
Jun 04 17:49:07 <PaulFertser> chrisign: just "saveenv" is the right command.
Jun 04 17:49:10 <DocScrutinizer> I recall uBoot is a bitch with editing env, as you need to escape everything for your shell  on PC
Jun 04 17:49:31 <chrisign> PaulFertser: ahh not everthing was forgotten, these are the new shell values:
Jun 04 17:49:39 <DocScrutinizer> sth like that
Jun 04 17:50:08 <chrisign> http://nopaste.info/0734cd7bf2.html
Jun 04 17:50:29 <PaulFertser> DocScrutinizer: i usually just use quoting and do it from minicom manually (but i used u-boot on other boards, not on FR).
Jun 04 17:52:41 <DocScrutinizer> the most  annoying thing: me never got uboot-envedit or what's the name to work on FR userland
Jun 04 17:52:51 <chrisign> PaulFertser: I forgotten to escape the ";"
Jun 04 17:58:40 <chrisign> why I need to write all these bootargs? I mean there are two different bootargs in this entry.
Jun 04 17:59:38 <chrisign> starting with rootfstype=jffs2 root=/dev/mtdblock6 with fits for booting from NAND? 
Jun 04 18:00:04 <chrisign> but not for booting with microSD? or am I wrong?
Jun 04 18:01:17 <chrisign> it looks  as u-boot only remember the first bootenv entry and forget the second
Jun 04 18:02:28 <chrisign> which are the proper entries for booting with a microSD rootfstype=ext2 root=/dev/mmcblk0p2
Jun 04 18:02:46 <PaulFertser> chrisign: yes, those are
Jun 04 18:03:33 <PaulFertser> chrisign: but you also need other bootargs (except for the root and rootfstype for NAND). So i'd suggest using bootargs_base but appending those two parameters (they'll override the previous ones).
Jun 04 18:07:57 <PaulFertser> chrisign: btw, using u-boot is considered "advanced" topic and so Qi is recommended for more simple hassleless scenarious.
Jun 04 18:13:22 <DocScrutinizer> mtdparts
Jun 04 18:13:34 <DocScrutinizer> nasty little sucker
Jun 04 18:14:16 <DocScrutinizer> I once messed up all of it, mtdparts and bootargs
Jun 04 18:14:35 <DocScrutinizer> by missing to escape one of the many chars I had to escape
Jun 04 18:14:50 <DocScrutinizer> so I reverted to NOR boot for that device ;-P
Jun 04 18:15:00 * DocScrutinizer <--lazy bugger
Jun 04 18:15:26 <DocScrutinizer> honestly uBoot console is kinda PITA
Jun 04 18:16:56 <chrisign> okay I tried it several ways, it does not work, still kernel panic
Jun 04 18:19:39 <chrisign> this is how it looks right after I put the bootargs_base: http://nopaste.info/7a692006ae.html
Jun 04 18:20:51 <chrisign> and this after I made an reset: http://nopaste.info/bfcf8bc35d.html
Jun 04 18:21:24 <chrisign> I'll try now Qi
Jun 04 18:23:27 <chrisign> is my expectation right? I push the aux button and then the power button, after that I connect with the console
Jun 04 18:23:52 <chrisign> but is this the right bootloader for microSD?
Jun 04 18:24:41 <PaulFertser> chrisign: i use it every day for uSD.
Jun 04 18:24:50 <PaulFertser> chrisign: read more at openmoko wiki.
Jun 04 18:24:59 <PaulFertser> chrisign: ohoho
Jun 04 18:25:28 <PaulFertser> chrisign: if you power the device on when you're holding the aux button, you're getting into NOR u-boot. It never saves any environment anywhere.
Jun 04 18:29:08 <chrisign> oookayyy =-O
Jun 04 18:29:11 <chrisign> ?
Jun 04 18:29:46 <chrisign> so first push power then, aux? this another enviroment
Jun 04 18:31:32 <PaulFertser> chrisign: read about NOR vs NAND booting options...
Jun 04 18:31:37 <PaulFertser> It's all on the wiki.
Jun 04 18:33:11 <chrisign> okay I read about it several mouth ago, these are the env: http://nopaste.info/8e015ba112.html
Jun 04 18:33:22 <chrisign> so I can start from scratch
Jun 04 18:57:08 <chrisign> one question left, I wrote a env variable named menu1 instead of menu_1, how can I delet this unneeded env variable?
Jun 04 19:01:36 <PaulFertser> chrisign: i do not remember, i'd look at "help"
Jun 04 19:01:46 <PaulFertser> And if it wouldn't help, i'd read official u-boot docs.
Jun 04 19:42:04 <chrisign> one step further: no init found
Jun 04 19:43:15 <PaulFertser> chrisign: for Qi the kernel and the rootfs should be on the same uSD partition.
Jun 04 19:44:37 <chrisign> PaulFertser: I still use it with u-boot. I just write it on the NAND, and NAND reallly remember waht I write
Jun 04 19:44:50 <PaulFertser> chrisign: :)))
Jun 04 19:44:53 <PaulFertser> no wonder
Jun 04 19:46:00 <PaulFertser> chrisign: no init found probably means you specified some wrong partition for rootfs in the kernel command line.
Jun 04 19:46:55 <chrisign> but it is on the 2.nd partiotion of the microSD. I can read from ext2ls
Jun 04 19:48:04 <chrisign> ext2ls mmc 0:2
Jun 04 19:49:52 <PaulFertser> chrisign: so root=/dev/mmcblk0p2 ? strange, init should be there. How did you untar the image?
Jun 04 19:53:26 <chrisign> PaulFertser: with tar xzvf full-om-gta02.tar.gz
Jun 04 19:54:56 <PaulFertser> chrisign: i'm not sure if ``p'' (--preserve) is default, but i'd use it.
Jun 04 19:55:27 <PaulFertser> Probably it's default for root and non-default for others, there was some trick iirc.
Jun 04 20:03:58 <DocScrutinizer> hehe
Jun 04 20:05:11 <DocScrutinizer> uBoot > msdos
Jun 04 20:05:39 <DocScrutinizer> and at least as hostile ;-D
Jun 04 20:07:32 <chrisign> sorry I was just distracted from this video: http://www.youtube.com/watch?v=3KnJc7eImQ4&feature=channel_video_title
Jun 04 20:07:54 <chrisign> :)
Jun 04 20:09:36 * PaulFertser hoped for some cool music video :)
Jun 04 20:10:49 <chrisign> no, otherwise I wouldn't it dump here, its about gta04 with the beagle/pada-board
Jun 04 20:12:11 <SpeedEvil> Does it have cool music?
Jun 04 20:12:45 * SpeedEvil stabs flash.
Jun 04 20:12:56 <SpeedEvil> (or the i810 audio driver)
Jun 04 20:12:59 <SpeedEvil> I'm unsure which)
Jun 04 20:13:10 <SpeedEvil> Umm.
Jun 04 20:13:17 <SpeedEvil> GTA04 has omap4?
Jun 04 20:13:20 <SpeedEvil> Or 3?
Jun 04 20:13:23 <SpeedEvil> pandaboard is omap3
Jun 04 20:13:25 <SpeedEvil> err
Jun 04 20:13:29 <SpeedEvil> beagle is omap3
Jun 04 20:13:32 <SpeedEvil> panda is omap4
Jun 04 20:13:55 <SpeedEvil> Oh. That wasn't flash screwing up - it's meant to be like that sound.
Jun 04 20:13:57 <SpeedEvil> Neat.
Jun 04 20:13:58 <PaulFertser> No music, alas.
Jun 04 20:14:29 <PaulFertser> SpeedEvil: luckily, i avoid it by using youtube-dl + mplayer for streaming from youtube. There's also a cool extension for firefox users.
Jun 04 20:14:55 <SpeedEvil> Yeah - one of my primary reasons for using flash is a site that won't work like that.
Jun 04 20:15:02 <SpeedEvil> chrisign: Awesome.
Jun 04 20:15:44 <SpeedEvil> In some ways things are back to before the n900 decapitated the gta04 project - as there anre no new n900s. :/
Jun 04 20:18:58 <chrisign> okay, in the mean time I tared the whole archive with a preserve flag, no I have dozens of error
Jun 04 20:19:44 <chrisign> ext2_lookup: deleted inode referenced.... and this 6 times
Jun 04 20:20:46 <chrisign> tar xzvfp full-om....
Jun 04 20:24:32 <chrisign> very very strange, maybe I should really give up with u-boot and give Qi an chance?
Jun 04 20:29:00 <PaulFertser> chrisign: hm, dozens of errors is strange, probably corrupted FS?
Jun 04 20:29:26 <PaulFertser> chrisign: or problems with FR accessing this particular card (it's known FR doesn't like some cards :( )
Jun 04 20:34:09 <chrisign> PaulFertser: http://wiki.openmoko.org/wiki/Supported_microSD_cards
Jun 04 20:34:32 <chrisign> I have two cards, but non of them are metioned here
Jun 04 20:34:34 <PaulFertser> It doesn't mean much.
Jun 04 20:34:59 <PaulFertser> Also, it somehow happened none of the devs capable of low-level kernel debugging had a "faulty" card :(
Jun 04 20:40:50 <chrisign> okay, as it seems, I'll send them two
Jun 04 20:45:05 <chrisign> this is maybe interesting: I couldn't eighter of them format with /dev/mmcblk0
Jun 04 20:45:40 <chrisign> they were both linked with the node /dev/sdb, a normal disk.
Jun 04 20:45:58 <chrisign> maybe this has something to do with udev of debian sid?
Jun 04 21:05:24 <chrisign> so whom I should send these two microSD-cards? onist.
**** ENDING LOGGING AT Sun Jun 05 02:59:56 2011