| 10:46 | maniac | hi all, can someone direct me please to latest uboot and spl for Cubox 4x4 which will support 4GB of RAM ? It was working for me previously, but with latest update i have done this weekend i can see only 2GB of RAM ... |
| 12:51 | topi` | jnettlet: what's the "good" way of changing the resolution of framebuffer? I tried "fbset 1024x768-60" and it does the job, but if I put it to /etc/rc.local, then no difference |
| 12:52 | topi` | console and all still at 1920x1080 |
| 12:52 | topi` | maybe something magical to /etc/defaults ? |
| 13:07 | jnettlet | topi`, you can change it via the kernel commandline in /boot/uEnv.txt, or you can change the device-tree entry for it. |
| 13:15 | maniac | any clue where can i find latest UBOOT and SPL files for Cubox 4x4 (with 4GB RAM support enabled) ? |
| 13:19 | bencoh | /66/66 |
| 13:19 | bencoh | (nevermind) |
| 13:20 | Artox | maniac: in the solidrun repos, package u-boot-cubox-i, files in /boot |
| 13:20 | Artox | we never overwrite your boot sector |
| 13:21 | maniac | Artox: thx, would you have url for the repo please? the old one i had is giving me 404 :( |
| 13:21 | maniac | i can manage to write it with the dd to the SD card ofc |
| 13:25 | Artox | maniac: just unpack that .deb: http://repo.solid-build.xyz/debian/jessie/bsp-imx6/armhf/u-boot-cubox-i_2013.10.1464952045-1_armhf.deb |
| 13:26 | Artox | just make sure whatever distro you are running doesn't depend on u-boot features later than 2013.10 |
| 13:26 | maniac | oh this is the old one from 2013 - i had trouble with latest archlinuxarm kernel (3.14.79-1-ARCH) to boot with this old UBOOT. Then i have found somewhere newer one (2015 i think) which now boots, but shows only 2GB of RAM |
| 13:31 | Artox | maniac: I see |
| 13:31 | Artox | u-boot mainling was never completed sadly |
| 13:31 | maniac | hmm |
| 13:31 | Artox | and memory configuration is one of those undone pieces |
| 13:32 | maniac | seems you are well informed so maybe you know if there are plans to include Cubox 4x4 memory confing into the newer uboot? |
| 13:33 | jnettlet | maniac, our github repo. |
| 13:34 | maniac | jnettlet: url please? does it contain compiled binary version also or i would need to compile it 1st ? |
| 13:35 | jnettlet | maniac, it is the same that Artox pointed out. There should be nothing stopping it from booting the ARCH kernel. |
| 13:38 | maniac | jnettlet: ok, i'll test it again. here are some details from my original test: https://archlinuxarm.org/forum/viewtopic.php?f=23&t=10789 when it was not booting with kernel newer than 3.14.58-1 |
| 13:38 | maniac | (with that particular uboot&spl images) |
| 13:40 | jnettlet | maniac, you have to make sure both the kernel and dtbs are upgraded in kernels newer than .58 |
| 13:40 | jnettlet | we had to revert some Freescale patches and device-tree changes that were causing some issues with certain pcie cards. |
| 13:41 | maniac | jnettlet: i would be very thankfull for link to some guide so i will doublecheck on that as i'm not sure what are DTBS :) |
| 13:41 | maniac | i'm coming from X86 world... :) |
| 13:42 | jnettlet | maniac, I am unfortunately not the person to help you. I don't use ARCH myself. There are usually a few ARCH people hanging around here that will hopefully point you in the right direction. |
| 13:42 | jnettlet | welcome :) |
| 13:42 | Artox | maniac: the one mentioned in your boot log: Loaded imx6q-cubox-i.dtb |
| 13:43 | maniac | hmm this may be the culprit |
| 13:43 | maniac | i can see i have two such files in /boot |
| 13:43 | maniac | -rw-r--r-- 1 root root 34808 Sep 13 09:25 /boot/dtbs/imx6q-cubox-i.dtb |
| 13:43 | maniac | -rw-r--r-- 1 root root 33907 Dec 12 2015 /boot/imx6q-cubox-i.dtb |
| 13:43 | maniac | i guess only one is required and also only one is the correct one |
| 13:44 | maniac | md5 |
| 13:44 | maniac | db085b5482b41e825a05890639e5b829 /boot/imx6q-cubox-i.dtb |
| 13:44 | maniac | 381776036acc44b9235c36a8f0ee743c /boot/dtbs/imx6q-cubox-i.dtb |
| 13:44 | Artox | our u-boot looks directly in /boot |
| 13:44 | Artox | no subfoldering |
| 13:44 | maniac | Artox: thx! |
| 13:44 | Artox | unless there is a boot script |
| 13:45 | Artox | or overwrites in some uenv.txt |
| 13:45 | maniac | [root@localhost boot]# file boot.scr ; strings boot.scr |
| 13:45 | maniac | boot.scr: u-boot legacy uImage, U-Boot boot script, Linux/ARM, Script File (Not compressed), 673 bytes, Sat Feb 11 04:02:48 2017, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0x078C3CB8, Data CRC: 0x928FCE00 |
| 13:45 | maniac | U-Boot boot script |
| 13:45 | maniac | # After modifying, run ./mkscr |
| 13:45 | maniac | if test -n ${distro_bootpart}; then setenv bootpart ${distro_bootpart}; else setenv bootpart 1; fi |
| 13:46 | maniac | part uuid ${devtype} ${devnum}:${bootpart} uuid |
| 13:46 | maniac | setenv bootargs console=${console},${baudrate} root=PARTUUID=${uuid} rw rootwait |
| 13:46 | maniac | if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /boot/zImage; then |
| 13:46 | maniac | if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /boot/dtbs/${fdtfile}; then |
| 13:46 | maniac | if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /boot/initramfs-linux.img; then |
| 13:46 | maniac | bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}; |
| 13:46 | maniac | else |
| 13:46 | maniac | bootz ${kernel_addr_r} - ${fdt_addr_r}; |
| 13:46 | maniac | fi; |
| 13:46 | maniac | fi; |
| 13:46 | maniac | based on the boot.scr file (i guess this the boot script?) it's looking into /boot/dtbs folder |
| 13:47 | maniac | in the /boot/uEnv.txt i have only this: |
| 13:47 | maniac | mmcargs=setenv bootargs root=/dev/sda1 rootwait rw console=tty1 console=ttymxc0,115200 consoleblank=0 video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24,bpp=16 dmfc=3 ahci_imx.hotplug=1 pci=nomsi loop.max_part=15 ipv6.disable_ipv6=1 |
| 14:01 | Artox | [13:46] based on the boot.scr file (i guess this the boot script?) it's looking into /boot/dtbs folder |
| 14:01 | Artox | right |
| 14:01 | Artox | and based on the output of ls you pasted earlier, the one in /boot is more recent |
| 14:05 | maniac | Artox: yup, thanks for confirmation. once i'll be home i will try to use latest one from the /boot |
| 14:06 | maniac | will let you guys know! :) i am very happy the community is alive! |
| 14:08 | maniac | Artox: regarding which one is more recent - you have checked file creation date visible in ls output? |
| 14:09 | Artox | yes |
| 14:09 | maniac | ok, thx |
| 14:09 | Artox | but ideally you would check with your distro which file was part of the kernel update |