Dobrica Pavlinušić

  • Content Count

  • Joined

  • Last visited

About Dobrica Pavlinušić

  • Rank

Profile Information

  • Gender
  • Location
    Zagreb, Croatia
  • Interests
    Free software, ARM hardware etc...

Contact Methods

  • Website URL
  1. I'm experimenting with nand overlays and it seems to me that rootfs partition has wrong offset (in all overlays): I think that 0xa00000 should be 0x1400000 ? Am I correct, and should I prepare pull request to fix it?
  2. Finally, I managed to get to my goal of running newest kernel on my cubieboard: root@cubieboard2:~# uname -a Linux cubieboard2 4.4.0-rc6-sunxi #3 SMP Mon Dec 28 11:38:20 CET 2015 armv7l GNU/Linux So, how did I get there, you might ask? First, I noticed that my kernel on laptop was reporting bad geometry for sdcard so I re-created partition table to fix it. I also wrote u-boot again to card using dd if=u-boot-sunxi-with-spl.bin of=/dev/sdX bs=1024 seek=8 Have in mind also that I already re-created ext4 filesystem previously on this card. My conclusion is that cubieboard2 image
  3. Thanks for a hint, but I don't really think that SD card in my laptop is to blame. Why? Because legacy image works well on same card with same SD card writer. However, I did try to re-format the card with read-write check (basically mkfs.ext4 -c -c) and copy files over. Read/write check didn't return any errors, and kernel did start, but now I kernel stack-trace: The first line with "VFS: Unable to mount root fs on unknown-block(179,1)" seems to indicate that now kernel is having some problems with SD card. However, after this machine reboots and keeps rebooting right after u-
  4. Update: checking download file, it seems that I downloaded so it's not 4.81 no matter what the download pages said. I'm trying to install upstream kernel on Cubieboard 2 and kernel never starts. Attached is output from boot (I'm getting same on serial port). I did try different sdcard (to rule out problems with it) but I'm worried about ext4fs_devread read error and partition error. Is there something more that I can try? Legacy kernel works well, but I wasn't able to just upgrade kernel and u-boot on it, but that resulted in unbo