**** BEGIN LOGGING AT Thu Mar 24 02:59:58 2016
Mar 24 11:11:31 <zGrr> moin :)
Mar 24 11:21:25 <DocScrutinizer05> moin
Mar 24 11:32:39 <HRH_H_Crab> im trying to set up uboot. i have a vfat partition on mmcblk1p1 and my rootfs on mmcblk1p2.
Mar 24 11:33:12 <HRH_H_Crab> i have converted my kernel and initrd to uboot format and copied them to /media/mmc1/boot (which is on the vfat mmcblk1p1 partition).
Mar 24 11:33:41 <HRH_H_Crab> im now trying to figure out what needs to go in boot.scr and where that should be saved. i think its implied it should sit in the root of the vfat partition.
Mar 24 11:34:41 <HRH_H_Crab> so i have something like this:
Mar 24 11:34:53 <HRH_H_Crab> setenv bootcmd 'mmc init; ext2load mmc1 0 0x82000000 /boot/uImage; ext2load mmc1 0 0x83000000 /boot/uInitrd; bootm 0x82000000 0x83000000'
Mar 24 11:35:06 <HRH_H_Crab> and then:
Mar 24 11:35:09 <HRH_H_Crab> setenv bootcmd 'mmc init; ext2load mmc1 0 0x82000000 /boot/uImage; ext2load mmc1 0 0x83000000 /boot/uInitrd; bootm 0x82000000 0x83000000'
Mar 24 11:35:20 <HRH_H_Crab> oops: setenv bootargs 'root=/dev/mmcblk0p1 rootwait console=tty0 omapfb.vram=0:2M,1:2M,2:2M mtdoops.mtddev=2 nosplash'
Mar 24 11:35:40 <HRH_H_Crab> these clearly need some fixing up - but im not entirely sure what goes where...
Mar 24 11:35:42 <HRH_H_Crab> can anyone advise?
Mar 24 11:36:17 <HRH_H_Crab> i guess the latter one i need to change the root device to /dev/mmcblk1p2
Mar 24 11:36:40 <HRH_H_Crab> but im not sure where exactly it thinks the uImage should be in the first one.
Mar 24 11:37:05 <HRH_H_Crab> and since the first partition of my mmc1 is vfat i guess i dont need ext2load?!
Mar 24 11:53:03 <Maxdamantus> Yes, you'd use something other than ext2load.
Mar 24 11:53:23 <Maxdamantus> fatload
Mar 24 11:54:43 <DocScrutinizer05> watch out for mmcblk1/mmcblk2 confusion, depending on whether or not you have a uSD inserted during boot, the naming might be messed up in linux
Mar 24 11:55:11 <kerio> fat load
Mar 24 11:55:13 <kerio> ( ͡° ͜ʖ ͡°)
Mar 24 11:55:36 * Maxdamantus wonders why anyone would use fat anyway.
Mar 24 11:55:51 <kerio> because pali's uboot doesn't support extfs
Mar 24 11:56:04 <HRH_H_Crab> kerio: that is the strange thing
Mar 24 11:56:05 <Maxdamantus> My u-boot works off ext2.
Mar 24 11:56:15 <kerio> :o
Mar 24 11:56:17 <Maxdamantus> though I compiled it myself.
Mar 24 11:56:25 <kerio> ...so how's that relevant
Mar 24 11:56:26 <Maxdamantus> I'd be surprised if it were disabled in pali's distribution though.
Mar 24 11:57:23 <Maxdamantus> well, "pali's u-boot" might refer to an obsolete branch of u-boot (his N900 support is merged into mainline now).
Mar 24 11:57:41 <Maxdamantus> or it might refer to a binary distribution he's made.
Mar 24 11:58:17 * Maxdamantus also modified his to use Dvorak instead of QWERTY>
Mar 24 11:59:56 <DocScrutinizer05> (messed up) IOW maemo kernel detects uSD as mmcblk1 if present, and only later on those devices get renamed to show consistent mmcblk1 = eMMC
Mar 24 12:00:57 <Maxdamantus> Do you mean the other way round?
Mar 24 12:01:33 <HRH_H_Crab> i think about half of the documents and how to's ive read were written during a time that it did not support ext*
Mar 24 12:01:39 <HRH_H_Crab> and half were written after
Mar 24 12:01:46 <HRH_H_Crab> which is probably why im in the mess i am.
Mar 24 12:03:51 * Maxdamantus just figured it out once then wrote some scripts to generate the .scr and uimage crap.
Mar 24 12:04:13 <DocScrutinizer05> err sorry, 0 and 1 of course
Mar 24 12:04:28 <DocScrutinizer05> mmcblk0=eMMC
Mar 24 12:04:52 <HRH_H_Crab> so i now have done s/ext2load/fatload for my bootcmd line
Mar 24 12:05:33 <HRH_H_Crab> and those paths for the kernel / initrd are deffo going to be looking at /dev/mmcblk1p1 ?
Mar 24 12:05:54 <DocScrutinizer05> however compare cat /proc/partitions
Mar 24 12:06:06 <Maxdamantus> Does the kernel even know about mmcblk1?
Mar 24 12:06:24 <Maxdamantus> I have a feeling it's meant to be mmc1p1
Mar 24 12:07:25 <HRH_H_Crab> well im logged in to the machine now and i have: /dev/mmcblk1p1 on /media/mmc1 type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0133,rodir)
Mar 24 12:07:54 <HRH_H_Crab> so the "boot" i am trying to refer to in that bootcmd line is /media/mmc1/boot
Mar 24 12:08:03 <DocScrutinizer05> compare cat /proc/partitions
Mar 24 12:08:07 <HRH_H_Crab> to what?
Mar 24 12:08:18 <HRH_H_Crab>  179        9   28315648 mmcblk1p1
Mar 24 12:08:31 <HRH_H_Crab> that the line in /proc/partitions that relates to the partition i think im talking about
Mar 24 12:08:33 <DocScrutinizer05> that's all?
Mar 24 12:08:51 <HRH_H_Crab> but that bootcmd example doesnt seem to refer to use that syntax at all
Mar 24 12:08:58 <HRH_H_Crab> the whole thing is
Mar 24 12:09:06 <HRH_H_Crab> major minor  #blocks  name
Mar 24 12:09:06 <HRH_H_Crab>  179        0   15558144 mmcblk0
Mar 24 12:09:06 <HRH_H_Crab>  179        1    1048576 mmcblk0p1
Mar 24 12:09:06 <HRH_H_Crab>  179        2   14508544 mmcblk0p2
Mar 24 12:09:06 <HRH_H_Crab>  179        8   31264768 mmcblk1
Mar 24 12:09:09 <HRH_H_Crab>  179        9   28315648 mmcblk1p1
Mar 24 12:09:11 <HRH_H_Crab>  179       10    2097152 mmcblk1p2
Mar 24 12:09:14 <HRH_H_Crab>  179       11     786432 mmcblk1p3
Mar 24 12:09:17 <DocScrutinizer05> I dunno what uBoot does regarding enum of mmc devices
Mar 24 12:09:18 <Maxdamantus> ah yeah, it is mmcblk
Mar 24 12:09:58 <HRH_H_Crab> i guess i could rephrase my entire question as: 
Mar 24 12:10:27 <HRH_H_Crab> does anyone know wtf whoever wrote this:  setenv bootcmd 'mmc init; ext2load mmc1 0 0x82000000 /boot/uImage; ext2load mmc1 0 0x83000000 /boot/uInitrd; bootm 0x82000000 0x83000000'
Mar 24 12:10:30 <DocScrutinizer05> you see mmcblk1p1 is maemo root partition, and you prolly got a 15GB uSD as mmcblk0
Mar 24 12:10:31 <HRH_H_Crab> meant by that "mmc1"
Mar 24 12:10:40 <HRH_H_Crab> and is it the same thing that i mean by mmcblk1p1 ?!
Mar 24 12:10:41 <HRH_H_Crab> ;)
Mar 24 12:10:58 <DocScrutinizer05> later during boot these get renamed so eMMC is mmcblk0 and uSD is mmcblk1
Mar 24 12:11:07 <HRH_H_Crab> aaah
Mar 24 12:11:33 <parazyd> anyone got DRI working with pali's kernel?
Mar 24 12:11:39 <HRH_H_Crab> so mmc1 is the name for mmcblk1p1 at uboot point in the process?
Mar 24 12:12:33 <Maxdamantus> setenv bootmenu_1 zImage-2.6.28.10-cssu1='setenv setup_omap_atag 1; setenv bootcmd '\''ext2load mmc 1:1 0x86008000 /k/zImage-2.6.28.10-cssu1.u; setenv bootargs '\'''\\''\'''\''init=/sbin/preinit ubi.mtd=rootfs root=ubi0:rootfs rootfstype=ubifs rootflags=bulk_read,no_chk_data_crc rw console=ttyMTD,log console=tty0 snd-soc-rx51.hp_lim=42 snd-soc-tlv320aic3x.hp_dac_lim=6'\'''\\''\'''\''; bootm 0x86008000'\''; boot'
Mar 24 12:12:54 <Maxdamantus> Fun quotes.
Mar 24 12:14:58 <HRH_H_Crab> so confused. :(
Mar 24 12:15:00 <HRH_H_Crab> anyway...
Mar 24 12:15:16 <HRH_H_Crab> just got to man up when i get home and randomly pump partition notation in to this bad boy until it submits.
Mar 24 12:15:19 <DocScrutinizer05> try mmc0 and mmc1, one of both will work ;-)
Mar 24 12:15:50 <HRH_H_Crab> mmm.
Mar 24 12:18:50 <DocScrutinizer05> ""setenv bootargs 'root=/dev/mmcblk0p1"" prolly points to 1st partition on uSD
Mar 24 12:19:28 <HRH_H_Crab> interesting.
Mar 24 12:19:35 <HRH_H_Crab> so id need to make that p2.
Mar 24 12:19:57 <DocScrutinizer05> ""setenv bootcmd 'mmc init; ext2load mmc1"" migth point to uSD too, or to eMMC, dunno what uBoot does
Mar 24 12:21:34 <DocScrutinizer05> but I'm pretty sure for bootargs the kernel will use that initial numbering which means mmcblk0 is eMMC when no uSD insterted, otherwise it's uSD
Mar 24 12:22:05 <DocScrutinizer05> ask pali!
Mar 24 12:24:11 <HRH_H_Crab> well i looked at that root=/dev/mmcblk0p1 and was sure it must mean the eMMC but now that you've sown the seed in my head that there could be insane ennumeration shenanigans, it is all sort of making sense (for certain values of sense)
Mar 24 12:25:46 <DocScrutinizer05> cat /proc/partitions is a remnant from early boot times before devices got renamed
Mar 24 12:26:17 <HRH_H_Crab> interesting.
Mar 24 12:26:52 <HRH_H_Crab> so i can look at the majors and minors and see if they have changed
Mar 24 12:27:34 <DocScrutinizer05> some script (prolly /sbin/preinit) renames them then, *after* kernel mounted rootfs
Mar 24 12:28:32 <HRH_H_Crab> et. voila:
Mar 24 12:28:45 <HRH_H_Crab>  /proc/partitions has  179        9   28315648 mmcblk1p1
Mar 24 12:28:51 <HRH_H_Crab> and /dev has:
Mar 24 12:29:01 <HRH_H_Crab> brw-rw----    1 root     floppy   179,   9 Jan  1  1970 mmcblk0p1
Mar 24 12:29:09 <HRH_H_Crab> i think ive just learned something
Mar 24 12:29:13 <HRH_H_Crab> (or ive got a migraine)
Mar 24 12:29:15 <HRH_H_Crab> one of the two.
Mar 24 13:15:50 <parazyd> how do i remove the stock kernel entry from uboot?
Mar 24 14:15:44 <DocScrutinizer05> why would you?
Mar 24 14:21:22 <parazyd> because i ahve kernel power
Mar 24 14:24:15 <kerio> parazyd: edit the script
Mar 24 14:24:29 <kerio> u-boot-update-bootmenu
Mar 24 14:24:49 <kerio> or just set a default entry
Mar 24 14:24:55 <parazyd> ah thanks
Mar 24 15:33:52 <DocScrutinizer05> uBoot comes with stock kernel attached anyway (siamese twins), so I'd suggest to keep the stock kernel plus NAND (mtd) as rescue system, and just make the new powerkernel system (on eMMC or uSD) dualboot default
Mar 24 15:38:51 <DocScrutinizer05> when you keep the screen.cfg(?) uboot config and the uboot.dpk on eMMC resp uSD, you even can do a full reflash (without eMMC) of N900 and you only need to dpkg -i /media/card/uboot.dpk to have your previous settings back
Mar 24 18:55:55 <Gadgetoid> KotCzarny: :D
Mar 24 18:59:01 <Gadgetoid> KotCzarny: revived my N810, charged it up, installed oscp, shiny :D
Mar 24 18:59:16 <KotCzarny> woo-hoo, it has many features you might like
Mar 24 18:59:33 <Gadgetoid> KotCzarny: pretty sure I've broken the power socket slightly though, although I always remember the cable flapping in the breeze
Mar 24 19:02:28 * DocScrutinizer05 wonders how the power socket could be 'broken slightly'
Mar 24 19:02:47 <KotCzarny> remember you can control your n810's oscp with any device with pygtk (via oscp-remote.py)
Mar 24 19:03:14 <KotCzarny> or ssh ;)
Mar 24 19:04:57 <KotCzarny> also, it can play network links (http/rtsp/mms) and video clips (audio part)
**** ENDING LOGGING AT Fri Mar 25 02:59:59 2016