All Activity

This stream auto-updates     

  1. Past hour
  2. ...ahh,, that was it, @wdtz mmc supply voltage is the problem... now fixed thxs [ 3.047452] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff5f0000[0]' [ 3.048324] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff5f0000[0]' [ 3.049176] dwmmc_rockchip ff5f0000.dwmmc: using lookup tables for GPIO lookup [ 3.049857] dwmmc_rockchip ff5f0000.dwmmc: No GPIO consumer wp found [ 3.050502] dwmmc_rockchip ff5f0000.dwmmc: allocated mmc-pwrseq [ 3.051051] mmc_host mmc2: card is non-removable. [ 3.060702] vcc_arm: ramp_delay not set [ 3.064330] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 3.067231] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 3.068218] mmc0: new high speed SDHC card at address aaaa [ 3.070820] mmcblk0: mmc0:aaaa SL08G 7.40 GiB [ 3.073398] mmcblk0: p1 now mmc is working fine although still having another errors, @balbes150 USB+SD just a good ideas, at some case may this is tricks what i needed,, but for now i'll just continue on using SD,,, thxs
  3. @piter75 Have you had a chance to add the eMMC tweaks for the board in the project? Is there an issue in github I can follow? Thanks
  4. After pulling my hair out, it looks as though the sd card slot on my OP+ is bad. I've tried writing armbian, to multiple micro sd cards (including a new 32GB I just bought), and either doesn't boot, or armbian boots partially, and gets partially booted, and errors with read/write error. I managed to boot via USB with Armbian, and tried to run nand-sata-install to install to emmc, but it errors that it can only be run from sd card. Is there any way to run nand-sata-install from usb to install to emmc?
  5. Today
  6. That's the error for a misconfigured dtb, the voltage supply to mmc, @500000 and 5100000 A non-standard regulator setup, like t9 or h96max+
  7. BTW, about PinebookPro display issue, to make sure it is not a u-boot related issue, I've took the working 4.4.198 image, and I've copied the 5.4.13 into same SDCard, and switched the symbolic links in /boot back and forth between 4.4.198 and 5.4.13, and the issue is present only in latest one, confirming that it is not u-boot related ...
  8. Hi @karlitos script is already set to pull that kernel.
  9. Hi @guidol @Igor It has been a while since I did a build and did not notice this change. My environment relies on jessie thus I compile with this. sudo ./compile.sh SET_EXPERT=yes RELEASE=jessie When tried a build got these errors during compile Err http://httpredir.debian.org jessie-backports/main armhf Packages 404 Not Found [IP: ::1 3142] Err http://httpredir.debian.org jessie-backports/contrib armhf Packages 404 Not Found [IP: ::1 3142] Err http://apt.armbian.com jessie/main armhf Packages 404 Not Found [IP: ::1 3142] Err http://httpredir.debian.org jessie-backports/non-free armhf Packages 404 Not Found [IP: ::1 3142] Err http://apt.armbian.com jessie/jessie-utils armhf Packages 404 Not Found [IP: ::1 3142] Err http://apt.armbian.com jessie/jessie-desktop armhf Packages 404 Not Found [IP: ::1 3142] Fetched 10.1 MB in 8s (1187 kB/s) W: Failed to fetch http://apt.armbian.com/dists/jessie/main/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://apt.armbian.com/dists/jessie/jessie-utils/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://apt.armbian.com/dists/jessie/jessie-desktop/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/main/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/contrib/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/non-free/binary-armhf/Packages 404 Not Found [IP: ::1 3142] E: Some index files failed to download. They have been ignored, or old ones used instead. [ o.k. ] Upgrading base packages [ Armbian ] And after a while the compilation stopped with this Processing triggers for libc-bin (2.19-18+deb8u10) ... Processing triggers for ca-certificates (20141019+deb8u4) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d....done. [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware E: Unable to locate package mmc-utils [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated Then I searched through the forum and seen this thread. Is there a way to reference the archived jessie when performing a build ? It seems that the build scripts use the previous place of jessie. Can someone change the build scripts and when they refer to jessie to automatically point/refer to the new place you puted them ? regards, Christos PS My build is OrangePiPC default/legacy 3.114, jessie, console/server.
  10. Hiya everybody, Could I add a Reply to the drop down menu? If not, could somebody put this in there for everybody else, please... Thank you so much....
  11. Great! Thank you so much fr your effort! I would love to try. I assume I can try the build script from https://github.com/GavinBa/build/tree/v9-a64-dsi and should be using the https://github.com/amarula/linux-amarula/tree/v9-a64-dsi kernel ? How do I tell the script to use the kernel ? I tried to find the answer in https://docs.armbian.com/Developer-Guide_Build-Options/ but no luck
  12. and well done you can say. It works perfectly!
  13. Try running in combined mode (burn an image to two SD+USB media at once, configure it, and connect them simultaneously). Most likely, your DTB doesn't have support for the SD card.
  14. If after adding u-boot does not start, add UART and see what happens.
  15. Update - Touch panel is now working :) 20200122_102315.mp4
  16. last week i was working on H6 tvb, but unfortunatly i broke the hardware... so now back to rk-3328 tvb,,, i was try to build linux 5.4.13 on it, last time it was working fine on 4.4.208... using the same kernel config, here errors what i got... (somehow it seems cant mount/find the rootfs) hope someone can help me figure it out... thanks... tvb-rk3328-model-x88-pro-armbian-linux-5.4.13.log linux-5.4.13-rk3328.config
  17. I can confirm the same on a Banana Pi M64 with the latest available image and the one before. Panic is always random, and sometimes U-Boot can't even find the SD Card. Verified reproducible on a second board, and the Fedora image with kernel 5.3 available from BPI's site boots fine every time.
  18. so i'll just wait with upgrading my sopine :-)
  19. You know that the official support for Debian Jessie ends in June 2020, do you? So I am not sure if it is worth playing around with backports....
  20. Some people think the problem around the pcie is related to a bug in the rockchip uboot. uboot from 2020 seems to fix the problem. I havent tried it. With the "standard" card you can buy with the rockpro64 i could not see any sata disks but in OMV i got the famous: ata1: hard resetting link - And the sata card was not visible at all, and i did try almost everything. Nothing postive happened at all. I was getting tired and did buy a cheap StarTech 2X ESATA + 2X SATA III 6 GB but still with chipset ASMedia - ASM1061 I was surprised it worked. Because everyone was sure the chipset was the fault, i has been told the Marvell 88SE9215 chipset was way better. I have now been writing on 6TB in a row, no errors yet. 10 DL in progress at same time, with each DL around 8.7 - 9.3 MB/s with the cheap StarTech with chipset ASMedia - ASM1061. Tested with Armbian image and OMV installed - very pleased with the result. ROCKPro64 Board ver. 2.0, dated 2018-04-11. Both 2GB and 4GB version. On these models PCIe 3.3V power is not supplied and the PCIe are therefore not functional. (Remove R89538 resistor that affects U7109 TCS4484B power regulator, it will supply 3.3V to PCIe bus) - Not tested by myself. Just to be clear this fix is ONLY for ROCKPro64 Board ver. 2.0, dated 2018-04-11. Both 2GB and 4GB version.
  21. I think at this point I can say: Done
  22. I do not know about hdmi as I use all of my boards headless. Though having issues with network connectivity makes things slightly complicated. Anyway. Check your ifconfig if it is properly configured and if not try to assign a free static address of your LAN to the board using /etc/network/interfaces file. You find tons of information and how-tos about this through search engines.
  23. While newest LE builds boot and all armbian images up to 19.11.4 (I tested) work(and install) nice -like always with usb sound and ETH- on x96mini 2/16 test box, I didn't manage to get any of the 19.11.5 builds working..on the earlier .5 builds device booted(with usual meson-gxl-s905w-p281.dtb set) but there was no usb keyboard working. On newer builds I get just black screen flickering slightly for some seconds until tv switches to "no signal". Is there any trick to get the video output back like the video=HDMI-A-1:e tweak on (some) allwinner h6 devices? Until now I also had no luck booting any build on the flowfon f1 4/32 H6 box I got. The pcb is 3rd revision of H6mini board used also on Eachlink H6mini, Eachlink H6max(yes same board, but on max always 4 gb ram) and several other petrel-p1-h6 boxes. Just once after an alert that cpu is too hot I could boot tanix' tx6 LE from card. Everything I tested worked(HDMI + sound, network, playback, radio/tv streams..), but I never could get the card reboot again. Like on other builds (LE/armbian)I tried try to boot from card, it give just blank screen(no signal). Maybe it is the odd ram timing this device uses-when comparing dts files extracted from tx6 android rom and from a rom that works on this device there are slight differences, but could also be u-boot. Are there any (working) dtb's for these h6mini boards or other approaches to get this beast boot anything useful?!
  24. Yesterday
  25. well you've no chance I already set up the pinebook in rk3399 with u-boot 2020: U-Boot 2020.01-armbian (Jan 21 2020 - 23:08:47 +0100) Model: Pine64 Pinebook Pro DRAM: 3.9 GiB PMIC: RK808 MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0 In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Pine64 Pinebook Pro ## Error: Can't overwrite "serial#" ## Error inserting "serial#" variable, errno=1 rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2940 bytes read in 6 ms (478.5 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 143 bytes read in 6 ms (22.5 KiB/s) 7118384 bytes read in 752 ms (9 MiB/s) 20722176 bytes read in 2178 ms (9.1 MiB/s) 72693 bytes read in 17 ms (4.1 MiB/s) 2698 bytes read in 9 ms (292 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7118320 Bytes = 6.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f5853000, end f5f1cdf0 ... OK Loading Device Tree to 00000000f57d8000, end 00000000f5852fff ... OK Starting kernel ... [ 2.647157] Internal error: Oops: 96000004 [#1] PREEMPT SMP it seems it doesn't like my new DT.. but u-boot works fine and blobfree..
  26. No complaints from me, once I get kernel hell straightened out on renegade and friends I want to circle around and u-boot 2020 the tinker as well, and I might see if the MiQi will survive it, it seemed to dislike 2018+ last time ... Sent from my Pixel using Tapatalk
  27. right that one is on my todo list as well.. I got fooled by their documentation which mentioned a way to reset clock of eMMC to enter maskroom but then I couldn't erase it.. @piter75 wrote how he did it with the buttons so that I'm soon ready to test it. I've the patches for integrating it into rockchip64 family (u-boot and 4v4 kenel) laying around since days.. (if we will base it on nanopi m4v2 we would have to change them a bit cause different bsp kernel and u-boot) but not tested cause the stock firmware didn't try do boot SD card for me. Will be tested once pinebooks display doesn't fool me anymore.. btw @TonyMac32 I might switch to upstram 2020 u-boot with the pinebook if you don't mind. orangepi4_uboot.patch orangepi4_kernel.patch
  1. Load more activity