Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates     

  1. Past hour
  2. I assume you have U-Boot running on your board, because you posted what appears to be the console output and it included: "U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 19 2018 - 11:18:51 +0800)" And also that the CPU was running at 1000 and the 1 gig of DDR at 800. I do not understand why you want to "load" the bootloader, and whether you are distinguishing that from "flashing" the bootloader. You are required to have a bootloader on the board itself. The USB flashing directions indicate a FAT-formatted USB drive. You mentioned an unformatted raw SD, and an EXT4 formatted SD, which are both wrong. I would suggest you try a FAT-formatted SD card, and put the flash-image-ddr3-MEM-RAM_CHIPS-CPU_DDR.bin in the FAT-formatted partition. Then, your flash command is bubt flash-image.bin spi mmc
  3. Hey Guys, i own a Lemaker Banana Pro device. The hardware itself is very fine, no issues with it, but the software support is pretty low. When i check internet, i see at least two images for it: Armbian Bionic - mainline based kernel 4.19.y Armbian Stretch- mainline based kernel 4.19.y I recognize that Armbian Stretch is based on Debian 9, which is the old Debian Version at all, so i am not willing to install it. But i wonder how it is with Bionic? Is Armbian Bionic based on Ubuntu Bionic Beaver? Is it that what i means? How long will the support run for this Bionic image? For me it doesnt matter if i install debian or ubuntu on my BPro, since its stable & software supported. thanks guys!
  4. Hi, I just updated my pine64 1Gb today (so 190916), it restarted perfectly with 5.3.0 kernel but I lost eth0 with `no phy at addr -1` in dmesg (wlan0 still works fine). Anybody can confirm ? I remember reading about this on irc about 5.3 and pine64 some weeks ago , I'll try to find it again.
  5. Is anyone else getting "Input/output error" when transferring data between two external drives? I thought the issues regarding IO errors were fixed in kernel 5.3... I'm on 5.3.0-rc6-aml-g12 so perhaps I should give the final version a try
  6. Yesterday I compiled Armbian_5.97_Pinebook-a64_Debian_buster_dev_5.3.0-rc8_desktop for my non-Pro Pinebook. While booting the screen was very dim So I searched on the net for a command and came to the one you had in your error-message above But the value 51 for brightness was too high to be set. I did read out the actual dim value as 2: #read-out display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --get-brightness 2 and I did set (via /etc/rc.local) a for-me-default value of 8: #set display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --set-brightness 8 A value of 10 was to bright for me
  7. Today
  8. If they are not in archive, you have to build them.
  9. I recently wanted to buy a tv box, but I don't know much about the technical parameters, h96 max vs h96 max plus, I feel that these two products are similar, the main difference seems to be that the chipset is not the same. So rk3328 vs rk3318 Which one should I choose?
  10. If you get this working, send a PR (to dev and next) and you don't need to worry about In case board works well, we could also add an image ... we have it for some other CSC targets as well.
  11. 01_dtbdump_rockchip,rk3328-evb.dts Hi I have been working for a while in order to get wifi working on my H96+.From the Android dts the wifi chip is ap6330. And it has a strange silk screen . I see that this driver is included in the firmware. But I still can't make it work.Should I change some settings in dts? Or I need to recompile the entire firmware? I have read some of the contents of Rockchip's official website. Can you tell me how to build my own firmware?And the dts file is here.
  12. Yesterday
  13. FYI, I also missed this module, so it's done:
  14. For what it's worth, I gave up on OPi.GPIO some time back, and switched to the standard libgpiod instead (e.g., see Use of libgpiod eliminates almost all pain in terms of permissions to manage GPIOs for non-root users. If you don't want to build your own copy, libgpiod is available in Debian buster; see package libgpiod2 ( Python bindings are available via the python3-libgpiod package (see All that is needed for user access to GPIOs is to set the group of /dev/gpiochip* to a group that the user is a member of - e.g., I use a "gpio" group, and then "chgrp gpio /dev/gpiochip*"), and set the permissions of /dev/gpiochip* to group read/write (e.g., "chmod g+rw /dev/gpiochip*") so that the "gpio" group can read/write to it. After doing this the user has full access to the GPIOs (in C, in Python, at the command line, etc.) without having to run as root. Here's a simple Python example that illustrates controlling a LED that wired to H5 GPIO PA12: import gpiod PA12 = 12 # LED is wired to GPIO PA12 # configure GPIOs chip = gpiod.Chip('1', gpiod.Chip.OPEN_BY_NUMBER) led_line = chip.get_line(PA12) led_line.request(consumer="test", type=gpiod.LINE_REQ_DIR_OUT) led_line.set_value(1) # turn on LED led_line.set_value(0) # turn off LED libgpiod also comes with some handy utilities to track GPIO pin usage as well (e.g., "gpioinfo"). I hope this helps...!
  15. You can refer to this patch: If this works for banana pi it will work for orange pi. DO NOT MERGE is there for a reason. ov5640_read_reg: error: reg=300a. It usually means it cannot communicate with the sensor. Use this: PE12/CSI_SCK/TWI2_SCK ==> CSI-SCK PE13/CSI_SDA/TWI2_SDA ==> CSI-SDA PE14 ==> CSI-RESET# PE15 ==> CSI-STBY-EN
  16. @devman: Good point. And I think you are right. Out of curiosity I have placed another sensor in the case, directly beneath the disks. It is not very precise though, but I thought it might at least give a hint. I have no others at the moment (HomeMatic IP HmIP-STH). @gprovost: Thanks for the clarification on ECC! That is good to know - and also very reassuring. Regarding the delta I think it was a temporary glitch. And yes, I agree that the HDD temps should be the main point. The new numbers are below, and they support your configuration. Come to think of it, I am not sure if I would like to see the HDD temps rise above another five degrees or so. The last summers were hot here and room temperature could easily climb above 30°C. I think ich will reverse these reversed fans again. But it was at least fun to test! Yes, I like the Helios4 for it's possibilities. - By the way, when you announced that you would ship each order with an OLED display (as I read it), I meant to ask for another one for the second unit. I was more than happy to learn that each one would be shipped with it. So, identical hardware. Small things, but they look cool, especially in the dark. 12 hs idling: Room temperature: 21,70°C Humidity: 55% Unit #1: Unit #2: Fan J10 RPM: 74 Fan J10 RPM: 39 Fan J17 RPM: 74 Fan J17 RPM: 41 SoC core temp.: 48,456 SoC core temp.: 42,267 Ambient temp.: 34,812 Ambient temp.: 31,250 Case: 24,10 Case: 24,20 Humidity: 48% Humidity: 48% /dev/sda temp.: 23 /dev/sda temp.: 23 /dev/sdb temp.: 23 /dev/sdb temp.: 24 /dev/sdc temp.: 23 /dev/sdc temp.: 24 /dev/sdd temp.: 23 /dev/sdd temp.: 25 /dev/sda state: standby /dev/sda state: standby /dev/sdb state: standby /dev/sdb state: standby /dev/sdc state: standby /dev/sdc state: standby /dev/sdd state: standby /dev/sdd state: standby 30 mins. after reboot: Room temperature: 22,00°C Humidity: 54% Unit #1: Unit #2: Fan J10 RPM: 74 Fan J10 RPM: 52 Fan J17 RPM: 76 Fan J17 RPM: 49 SoC core temp.: 49,408 SoC core temp.: 44,171 Ambient temp.: 35,500 Ambient temp.: 32,500 Case: 23,80 Case: 25,10 Humidity: 50% Humidity: 49% /dev/sda temp.: 27 /dev/sda temp.: 29 /dev/sdb temp.: 27 /dev/sdb temp.: 29 /dev/sdc temp.: 27 /dev/sdc temp.: 30 /dev/sdd temp.: 27 /dev/sdd temp.: 31 /dev/sda state: active/idle /dev/sda state: active/idle /dev/sdb state: active/idle /dev/sdb state: active/idle /dev/sdc state: active/idle /dev/sdc state: active/idle /dev/sdd state: active/idle /dev/sdd state: active/idle
  17. add KERNEL_CONFIGURE="yes" to the build config or as a parameter to ./compile
  18. Fair enough. It depends on how I configure the routing, to be sure. This is going to be much more capable than a raspberry PI in a like configuration which was the other likely candidate. While I could configure a PI4 as a single-armed router, the EB design provides for more direct routing configuration.
  19. The Emulator compiled even on a Pinebook A64, but is slower than on the NanoPi K1 Plus
  20. 1234
  21. Hi there, I'm currently struggling to get the Cedrus VPU up and running. I have downloaded the specific version from bootlin and got the kernel up and running, however the V3s isn't supported by the Sunxi SRAM driver. This driver is important to get the VPU going. I tried altering the devicetree of the V3s to match a SoC that is somehow similiar, but it clearly failed for obvious reasons. I get this error message: [ 1.035259] cedrus Failed to claim SRAM [ 1.040990] cedrus Failed to probe hardware [ 2.478247] cedrus Failed to claim SRAM [ 2.484047] cedrus Failed to probe hardware [ 2.505765] cedrus Failed to claim SRAM [ 2.511591] cedrus Failed to probe hardware [ 8.595278] cedrus Failed to claim SRAM [ 8.601112] cedrus Failed to probe hardware I tried to understand whats going on in the linux/drivers/soc/sunxi/sunxi_sram.c file to adapt this driver to the V3s, but in the end I don't know how to do that. I hope somebody can help me with that or can give me a hint.
  22. RPI does not have any internal storage, it boots mainly on the SD card, I did not change any partitions, I just described the partitions in the dtb file to match the original dtb, I think that the kernel does not see the /dev/system partition, I don't know why, here the modified dtb file that I have updated, not the original one. gxl_p281_1g.dts
  23. Wifi device not ready fix by copying from previous version fw_bcm4356a2_ag.bin & nvram_ap6356.txt into /lib/firmware/brcm
  24. Oh i think you use the SD cards indeed al little bit (mean a lot!!) more intensive then i should do. Otherwise is in the dashcam's my idea also that the Samsung's has a longer lifetime than the Sandisk. But i agree with you: the only correct way to check it is to buy a lot and do all the same things and see how long the SD cards live. Offcourse with originals. But even then could there be a bad batch of a brand... 'SD cards are consumable items' do i read somewhere on the internet. And i think we should agree. Btw: is the lifetime of a onboard eMMC better than a SD card?
  25. Finally solved this issue. The first thermal zone tripping point is at 70C with a hysteresis of 10. One would expect to kick a throttle in at 70C and lift the throttle at 60C. However throttling occurs at 60C. So I adapted a script found elsewhere and raised the first two tripping points. echo 'setting cpu temperature limits ...' i=0 while [ $i -lt 4 ]; do sudo bash -c "echo \"85000\">/sys/devices/virtual/thermal/thermal_zone""$i""/trip_point_0_temp" sudo bash -c "echo \"95000\">/sys/devices/virtual/thermal/thermal_zone""$i""/trip_point_1_temp" i=$[$i+1] done
  26. Last week
  27. I done some test with a bananapi M1 with Armbian_5.91_Bananapipro_Debian_stretch_next_4.19.59 In this case, the display working
  28. In case, both IP address are static, write your your DNS sever in /etc/resolv.conf : nameserver 'dns_IP_address' If one IP address from DHCP, network-manager will re-write resolv.conf with data from DHCP If the DNS from DHCP is not good, you must fix a static address one each interface and write manually resolv.conf What is this ?????? internet access blocking port 80 and 443 Are you sur port 8000 or 8001 are open ; for user, prefer port 8080, some internet browser block no standard port ( i have had this problem with port 8000 and must move to 8080 ) For the firewall, normally all Armbian have installed IPTABLES ( il the native linux firewall ) but it's only on command line I never used webmin but i think it said "not installed" because there are not filtering rules
  29. @lex

    Updated htop

    According to this: , it is not related to CPU temp. My guess is just a missing kernel config.
  1. Load more activity