ChanServ changed the topic of #radxa to: http://radxa.com/ - Logs: http://irclog.whitequark.org/radxa
<gb_master> so, I generated boot.img by taking the line from the google groups thread
<gb_master> mkbootimg --kernel /tmp/kernel.img --ramdisk /dev/null --cmdline "console=ttyFIQ0 console=tty0 root=/dev/mmcblk0p1 rootfstype=ext4 init=/sbin/init" -o /tmp/boot.img
<gb_master> but there's nothing about the partitions in the cmdline
<naobsd> gb_master: I don't know that kernel image uses cmdline from mkbootimg
<gb_master> well, I don't know
<naobsd> gb_master: but anyway what you need is partition specified by root=
<gb_master> yep
<naobsd> gb_master: if you made 1st partition on SD and did mkfs.ext4, it should be ok
<gb_master> totally
<naobsd> well
<naobsd> --kernel /tmp/kernel.img <- what's this?
<naobsd> is there any reason not to use boot.img in that package?
<gb_master> I don't know
<naobsd> well
<gb_master> first post of 27th October
<naobsd> ah
<naobsd> but I guess boot.img doesn't boot if "boot.img (kernel.img plus a null initrd via mkbootimg)" is true :(
<naobsd> mkbootimg uses (z)Image, not kernel.img
<naobsd> ^as input
<gb_master> ah
<naobsd> so I guess his system is booted with kernel.img
<naobsd> well
<gb_master> ok, so I can re-do the boot.img by using zImage
<naobsd> you have working zImage?
<gb_master> I compiled one, yes
<gb_master> in the same way he did
<naobsd> (I'm sorry, actually I didn't try his package)
<gb_master> don't worry
<naobsd> gb_master: I see, try it and see result
<gb_master> me neither... I'm just redoing his steps
<naobsd> please don't forget you're trying 2 new things, sd boot and mainline kernel. don't mix them
<gb_master> can't I use sd_miniroot and kernel+boot from mainline?
<naobsd> 2 independent things
<naobsd> well
<naobsd> sd_miniroot?
<gb_master> sdboot_rk3188.img
<gb_master> (sorry)
<naobsd> it's just for "sd boot"
<naobsd> no relation to mainline(or non-) kernel
<gb_master> so I write sdboot+parameters+mainlinekernel+mainlineboot
<naobsd> try it, you can get result
<gb_master> :)
<naobsd> e.g. if you can see kernel message and error, sd boot worked, problem is in kernel or rootfs
<gb_master> I wish I could... I don't have UART
<naobsd> oops
<gb_master> yep
<gb_master> I mean, I have the stuff and things, but not here
<naobsd> how do you access it?
<naobsd> ah
<gb_master> that's why I go on with backups (for now)
<naobsd> but it's hard to see "result" :(
<gb_master> I know
<naobsd> I think LED blinks if kernel is booted
<naobsd> ^if you're using my modified dts
<gb_master> mmm
<gb_master> rk3188-radxarock-full.dtb
<naobsd> snapshot-20140928 include my change
<gb_master> :)
<gb_master> I kept ramdisk "/dev/null"
<gb_master> and I recreated boot.img with zImage
<naobsd> ah I found "cat arch/arm/boot/zImage arch/arm/boot/dts/rk3188-radxarock-full.dtb > /tmp/kernel.img "
<naobsd> sorry, his kernel.img is fine
<gb_master> ah
<naobsd> did you append dtb to zImage?
<gb_master> I'm going to
<gb_master> I create the boot.img off the kernel.img, instead of zImage?
<naobsd> and his procedure doesn't touch cmdline, it should be defined in kernel config
<naobsd> kernel.img sounds it has RK header, not good name :(
<gb_master> mmm
<naobsd> what you need is zImage+dtb file for mkbootimg input
<gb_master> good
<naobsd> he named it kernel.img
<gb_master> ok done
<gb_master> cmdline defined in the menuconfig?
<naobsd> you have to use boot.img. his "kernel.img" doesn't have RK header, it cannot boot if you write it to NAND/SD as is
<gb_master> ok
<naobsd> somewhere in menuconfig == in rk30_rk31_defconfig/.config
<gb_master> console=ttyS2,115200 earlyprintk init=/sbin/init root=/dev/mmcblk0p1 rootwait
<gb_master> I think
<naobsd> it will be used, seems fine for you too
<gb_master> :)
<gb_master> so
<gb_master> it's time for some dd
<naobsd> can you paste parameter (CMDLINE)?
<gb_master> I set both seek=1 skip=1 for sdboot, right?
<gb_master> mmm
<naobsd> right
<gb_master> well, in the kernel, as I said there was " console=ttyS2,115200 earlyprintk init=/sbin/init root=/dev/mmcblk0p1 rootwait" defined
<naobsd> what I asked is parameter
<gb_master> in parameters I wrote "console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 mac_addr=12:21:34:43:56:65 init=/sbin/init"
<naobsd> well, no, a line start with CMDLINE in parameter file
<gb_master> CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 mac_addr=12:21:34:43:56:65 init=/sbin/init
<naobsd> you erased mtdpart?
<gb_master> a-ehm
<naobsd> partition info in parameter is required to read kernel etc by loader
<gb_master> ok
<naobsd> (other part is ignored if you're using kernel config with fixed command line)
<naobsd> what I said is, try as is, then add/update some things
<naobsd> you're trying 2 new things
<gb_master> CMDLINE:console=console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 mac_addr=12:21:34:43:56:65 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x00008000@0x00004000(kernel),0x00008000@0x0000c000(boot)
<naobsd> yes
<gb_master> :)
<gb_master> so, if I should not use my kernel.img, what do I use?
<naobsd> boot.img has kernel, it's enough
<gb_master> ok
<naobsd> you may use ramdisk-only ramdisk, then you need kernel.img (<- with RK header)
<naobsd> ^ramdisk-only boot.img
<gb_master> ok
<gb_master> so I skip the dd kernel.img line
<gb_master> nope, doesn't boot
<naobsd> you need serial console ;)
<gb_master> I know
<naobsd> how about LED?
<gb_master> I'll get that on Xmas
<gb_master> when I get back home
<gb_master> no LED
<naobsd> hm
<naobsd> how about boot.img from google groups?
<gb_master> I can flash that
<naobsd> I'm not sure but LED may not be blinked if kernel panics very soon...
<naobsd> my snapshot is old
<naobsd> it worked but it should be updated :(
<gb_master> you have newer ones?
<naobsd> no
<naobsd> but you can try latest mainline at any time ;)
<gb_master> I'd like to have some new kernel before :)
<gb_master> but, after, I totally will
<gb_master> btw, what's the status? just the video stuff doesn't work?
<naobsd> not sure for now
<gb_master> and 3.10? is it OK?
<naobsd> personally 3.10 is not ok
<gb_master> just 3.0 is
<naobsd> good for android
<gb_master> less good for other stuff, maybe
<naobsd> RK kernel has a lot of bugs
<gb_master> any news about a new release from rockchip about kernel stuff?
<naobsd> new kernel? 3.10 or mainline for rk3188? no
<gb_master> it's all up to the community
<naobsd> 3.0 is latest for rk3188, RK still update some
<naobsd> rockchip community is very weak
<naobsd> ah, there are many mainline developers
<naobsd> but not for 3.0/3.10/etc
<gb_master> :(
<gb_master> I'm writing the boot.img from the group
<naobsd> RR is dev board, but most user is not developer
<naobsd> (I know some amount of people doing his own product/project with RR and get good result)
<naobsd> but not so much(very few) "community developer"
<gb_master> yes, I know
<gb_master> weird
<gb_master> so, it's booting
<gb_master> which is GREAT
<gb_master> but I can't ssh
<naobsd> gb_master: weird, but you got working example
<gb_master> I know
<naobsd> I think eth0 should work with my snapshot
<gb_master> when I type the password, I get "connection to 192.168.x.x closed"
<naobsd> it seems working ;)
<gb_master> I know
<gb_master> :D
<gb_master> but if I can't ssh
<naobsd> ethernet support has some bugs
<naobsd> but I think ssh worked
<naobsd> I think you can see logs on SD card :)
<naobsd> which rootfs are you using? /dev/* may not be populated properly for ssh
<naobsd> sshd
<naobsd> anyway, it shouldn't be difficult
<gb_master> mmm MAC address changes everytime
<gb_master> :S
<naobsd> ^I think
<gb_master> :S
<naobsd> ah, yes
<gb_master> why?
<gb_master> I put the line in parameter.img
<naobsd> because there is no MAC address is stored on RR board
<naobsd> ah, mainline kernel doesn't support it
<gb_master> yes, but why it's not using the one I wrote in the parameter.img?
<naobsd> I think it can be specified in dts
<gb_master> ah
<gb_master> ok
<naobsd> mainline kernel doesn't use the one in the parameter
<gb_master> ok ok, now I got it
<gb_master> well, I think I have to go to sleep now
<gb_master> but I did great things tonight thanks to you guys
<naobsd> gb_master: good night
<gb_master> thanks again
gb_master has quit [Remote host closed the connection]
mrcan has joined #radxa
mrcan has joined #radxa
mrcan has quit [Changing host]
mrcan_ has quit [Ping timeout: 256 seconds]
naobsd has quit [Quit: Page closed]
naobsd has joined #radxa
Astralix1 has joined #radxa
Astralix has quit [Ping timeout: 250 seconds]
Bludot has quit [Quit: Connection closed for inactivity]
naobsd has quit [Quit: Page closed]
AstralixNB has joined #radxa
naobsd has joined #radxa
hramrach_ has quit [Ping timeout: 250 seconds]
hramrach_ has joined #radxa
naobsd has quit [Quit: Page closed]
bengal has joined #radxa
Bludot has joined #radxa
mrcan has quit [Quit: pai]
Bludot has quit [Quit: Connection closed for inactivity]
AstralixNB has left #radxa [#radxa]
bengal has quit [Ping timeout: 265 seconds]
orangecms has joined #radxa
bengal has joined #radxa
Bludot has joined #radxa
mrcan has joined #radxa
Bludot has quit [Quit: Connection closed for inactivity]
gb_master has joined #radxa
gb_master has quit [Quit: Leaving]
mrcan has quit [Read error: Connection reset by peer]
akaizen has quit [Remote host closed the connection]
akaizen has joined #radxa
akaizen has quit [Ping timeout: 244 seconds]
Bludot has joined #radxa
orangecms has quit [Quit: Leaving]
bengal has quit [Quit: Leaving]
akaizen has joined #radxa
naobsd has joined #radxa
akaizen_ has joined #radxa
akaizen has quit [Ping timeout: 244 seconds]