Active threads
Showing topics posted in for the last 365 days.
- Past hour
-
He works as ili9341 and as ili9486. I use it now as ili9486. I`ll go further to make it work as native device.
- Today
-
KickPi K2B not booting up: DRAM setup not supported
chuanzz replied to chuanzz's topic in KickPi K2B
I build a u-boot with it dd latest armbian.img and this u-boot, it showed: ▒[40]HELLO! BOOT0 is starting!r = 0x1d3 [43]BOOT0 commit : 4b34f2890a [46]set pll start [48]periph0 has been enabled [51]set pll end [54]unknow PMU [56]unknow PMU [59]PMU: AXP1530 [64]vaild para:15 select dram para1 [68]board init ok [69]enable_jtag [71]DRAM BOOT DRIVE INFO: V0.651 [74]the chip id is 0x2000 [77]chip id check OK [80]DRAM_VCC set to 1500 mv [86]read_calibration error [92]read_calibration error [98]read_calibration error [104]read_calibration error [110]read_calibration error [116]read_calibration error [122]read_calibration error [128]read_calibration error [135]read_calibration error [141]read_calibration error [143]retraining final error [152][AUTO DEBUG]32bit,1 ranks training success! [164]DRAM CLK =648 MHZ [166]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [174]Actual DRAM SIZE =2048 M [177]DRAM SIZE =2048 MBytes, para1 = 310a, para2 = 8000000, dram_tpr13 = 6041 [190]DRAM simple test OK. [193]rtc standby flag is 0x0, super standby flag is 0x0 [198]dram size =2048 [201]Use rtc to store dram tuning para [205]card no is 0 [207]sdcard 0 line count 4 [209][mmc]: mmc driver ver 2021-10-12 13:56 [214][mmc]: b mmc 0 bias 4 [222][mmc]: Wrong media type 0x0 [225][mmc]: ***Try SD card 0*** [240][mmc]: HSSDR52/SDR25 4 bit [243][mmc]: 50000000 Hz [245][mmc]: 119850 MB [247][mmc]: ***SD/MMC 0 init OK!!!*** [319]Loading boot-pkg Succeed(index=0). [323][mmc]: b mmc 0 bias 4 [325]Entry_name = u-boot [332]Entry_name = monitor [336]Entry_name = dtbo [339]Entry_name = optee [343]Entry_name = dtb [346]mmc not para [347]Jump to second Boot. NOTICE: BL3-1: v1.0(debug):54937d5 NOTICE: BL3-1: Built : 17:44:59, 2021-12-13 NOTICE: BL3-1 commit: 8 NOTICE: cpuidle init version V2.0 NOTICE: secure os exist MESSAGE: [0x0] TEE-CORE: OP-TEE version: 81ab7a47 #1 2020年 05月 06日 星期三 02:40:04 UTC arm NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3 and I found this: [177]DRAM SIZE =2048 MBytes, para1 = 310a, para2 = 8000000, dram_tpr13 = 6041 is this para what we need? -
@Jeeva Kandasamy I would freeze your kernel updates using armbian-config. I’m using a custom kernel so it might break your system. This might help fix your error. https://github.com/MichaIng/DietPi/issues/4600
-
I don't know if this relates, but I recently discovered an issue with a Debian Trixie file system package xfsprogs on the 25.8.1 edge kernel for the Orange PI 5 Plus: https://forum.armbian.com/topic/55599-bug-report-armbian-edge-kernel-6164-xfsprogs-trixie-package-failure-to-start-low-memory-monitorservice/
-
Just compiled and flashed a Cinnamon desktop image. Boots fine Video over HDMI working. Audio over HDMI working. The video experience is not that much satisfying. There seems to be no graphic acceleration, yet. WebGL aquarium runs at 5 FPS with 500 fishes, 15 FPS with 100 fishes. Youtube videos are relatively laggy and you'll experience high CPU load. All the GPIO hardware stuff has not been tested, yet. No clue how to do it... Now I'd like to have some more people on board to support me by adding graphic acceleration and how to merge the M1S support now into the Armbian repo. Greetings. EDIT 1: transferring the OS from SD card do eMMC works by using armbian-install tool EDIT 2: graphic acceleration IS kind of working, glmar2-es2 gives me a score of ~177. But the web browser seems not to be accelerated. also the desktop environment seems to have problems Cinnamon is not able to load applets, which means that the "Start" menue icon is missing...
-
Hello, has anyone managed to get this camera to work on zero 3?
-
Request to update distro: park heads of hard disk(s) before shutdown....
ean365 replied to ean365's topic in Odroid XU4
Hmmm. Never mind, maybe. I see that Armbian has it included here, but for some reason it was not installed automatically. https://github.com/armbian/build/tree/main/packages/bsp/odroid -
Sorry for the late feedback. I was waiting for a new kernel update (6.12.54-bcm2711) to confirm it was all right. Just as what @Werner said, in the `/etc/initramfs/post-update.d/z50-raspi-firmware` contains snippets of the code that prints out the error. And it's indeed no actual harm. Also, without setting on-hold of the `raspi-firmware`, kernel updates works just fine. We are good. Thank you all!
- Yesterday
-
Hi! I dont know if anyone else mentioned this here but here is my issue: My RK3229 boots into armbian fine but after like 60sec the screen turns black and both blue LED stays on. Is there a fix for this?
-
If anyone in interested in a lightweight wayland desktop, inspired by openbox, you should try labwc. In orange pi zero 3, we need to stay in bookworm to get video acceleration, so this guide helps build labwc in bookworm As a greeter, I chose pi-greeter, because it is the lightest login manager I could setup, without any X11 https://github.com/robertojguerra/opiz3-labwc-setup I am open to read any improvements, or show me how I could make deb packages. In the near future, I will make a step-by-step video tutorial in Youtube.
-
Request: Lightweight XFCE Desktop Image for Orange Pi Zero 3
robertoj replied to mfoo's topic in Allwinner sunxi
For video acceleration, you need to stick with Bookworm. -
I don't think you understand how Armbian works. This board is community supported. It does not and hasn't been an Armbian supported board. Given the hundreds of boards out there Armbian only has the resources to officially support a handful. The rest end up being supported by the user community like this board. Thus support is only as good as the community volunteers who have the board and wish to volunteer their time to support it. Armbian provides the tools and infrastruction to make supporting boards easier, but the work still needs to be done by someone for community supported boards like this.
-
Anyone have Armbian 24.11 image for Jetson Nano?
lyevod79 replied to ArmOnJetson's topic in Other families
Can I still find the image somewhere? I would like to run Armbian on my Jetson Nano 2 GB, but Armbian_community_25.11.0-trunk.367_Jetson-nano_trixie_current_6.12.54_minimal.img and older images won't boot. I have tried images repeatedly over the past six weeks, but none of them will boot. It would be a shame if the Jetson Nano 2 GB ended up as electronic waste. -
Yep enabled the module and it's working now, Just sent a PR. Thank you.
-
install bookworm 6.6.63 on x96q pro+ h728
Nick A replied to hamidreza h's topic in Allwinner CPU Boxes
@MeJune A523/T527 support still needs a lot of work. There is no HDMI support yet. So you will need to install a usb serial device to your uart to interact with your box. You can find details at the botton of the site you posted https://linux-sunxi.org/X96QPro%2B. You could try warpme minimyth2 or miniarch. He has the latest support for these boxes. I don't own a X96q pro+ so I can't help you. -
@Unrealchex The base-files error is a known issue. You'll need to run the ./compile command a second time and it should continue where it left off. Here's a post that show's you how to create patches. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-227058 You want to edit u-boot and kernel dts. Remove the x96q code and add the wifi code from x98h. The x96h U-boot and kernel code might be different double check it. remove (Existing x96q wifi code.) reg_vcc_wifi: reg_vcc_wifi { compatible = "regulator-fixed"; regulator-name = "vcc-wifi"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; gpio = <&pio 6 18 GPIO_ACTIVE_HIGH>; /* PG18 WL_REG_ON */ regulator-always-on; enable-active-high; status = "okay"; }; wifi_pwrseq: wifi_pwrseq { compatible = "mmc-pwrseq-simple"; clocks = <&rtc CLK_OSC32K_FANOUT>; clock-names = "ext_clock"; pinctrl-names = "default"; pinctrl-0 = <&x32clk_fanout_pin>; /* PG10 with MUX3 set */ }; &mmc1 { vmmc-supply = <®_dldo1>; vqmmc-supply = <®_vcc_wifi>; mmc-pwrseq = <&wifi_pwrseq>; bus-width = <4>; non-removable; status = "okay"; wlan: wifi@1 { reg = <1>; interrupt-parent = <&pio>; interrupts = <6 15 IRQ_TYPE_EDGE_RISING>; /* PG15 WL_HOSTWAKE*/ interrupt-names = "host-wake"; local-mac-address = [dc 44 6d c0 ff 02]; }; }; Add (code borrowed from x98h) reg_vcc3v3: vcc3v3 { /* discrete 3.3V regulator */ compatible = "regulator-fixed"; regulator-name = "vcc-3v3"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; }; reg_3v3_wifi: vcc3v3-wifi { compatible = "regulator-fixed"; regulator-name = "vcc-3v3-wifi"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; }; }; &mmc1 { vmmc-supply = <®_vcc3v3>; bus-width = <4>; non-removable; max-frequency = <35000000>; status = "okay"; wlan: wifi@1 { reg = <1>; }; }; You don't need to create a patch for build/config/boards. Edit the file x96q-lpddr3.csc and add this to the bottom of display_alert "$BOARD" "Using ${BOOT_FDT_FILE} for ${BRANCH}" "info" display_alert "Applying wifi firmware" pushd "$SDCARD/lib/firmware" ln -s "aic8800/SDIO/aic8800D80" "aic8800_sdio" # use armbian-firmware cp -R $SRC/packages/blobs/sunxi/h618/armbian-audio-config $SDCARD/usr/lib/armbian cp -R $SRC/packages/blobs/sunxi/h618/armbian-audio-config $SDCARD/lib/armbian popd
-
Installing SliTaz on a TV Box with Rockchip RK3229
Hqnicolas replied to MXT5's topic in Rockchip CPU Boxes
Sorry, I didn't take my medicines. where did you find the link between SliTaz and armbian? Do you intend to be the maintainer of this link? you need help writing SliTaz documentation? -
https://github.com/manjaro-arm/opi5-plus-images/issues/22#issuecomment-3340442272
-
The strange thing is that, as far as I can see, this issue doesn’t occur on the vendor kernel. Continuing from our earlier discussion, I’ve just noticed that my variant shows the same problems as well only when i write stuff. I’ll get in touch with FriendlyELEC to clarify this. If the only solution is to scale down the frequency, then it would actually make more sense to modify it directly in the DTS rather than through an overlay.
-
Gaming experience with Orange Pi 5 (RK3588) on Armbian
KhanhDTP replied to KhanhDTP's topic in Orange Pi 5
@Fredrik I got like ~80fps at 720p. I sometimes get the gamepad not working. For me, just remove the wineprefix and it will work again! - Last week
-
If any of you have experienced skipping and popping when seeking with vlc, you can try setting the audio sink to ALSA and one of the rockchip-es8316 options. That will smooth out the audio playback BUT you will quickly discover that anything pulseaudio related is locked out of using the soundcard while vlc is up. Instead, try this. Set vlc audio back to pulseaudio (or automatic, seems to map to the same thing) and then change these two lines in /etc/pulse/daemon.conf: -; default-sample-rate = 44100 -; alternate-sample-rate = 48000 +default-sample-rate = 48000 +alternate-sample-rate = 44100 Restart pulseaudio with systemctl --user restart pulseaudio and see if vlc plays nice with everything else as well as supporting smooth playback after seeking. It does for me. It seems that forcing pulseaudio to resample causes all sorts of hilarity (vlc seems to like putting everything out at 48000). I'm sure there's a reason why. I'm also sure if I know, I'll be sorry I do. I wonder, how hard is it to get the Vulkan video hardware decoding working? Has anyone gotten it to work?
-
After many days spent wondering why is my OPI Zero2w 1.5GB not booting some Armbian images (xfce desktop version for example), I have found there is a "bug" or difference in uboot models 1.5GB + 4GB vs 1GB+2GB. Fix that might work for Zero2w is here https://forum.armbian.com/topic/31654-orange-pi-zero-2w/ (planning to test it soon) Can somebody confirm Opi Zero2W 1.5GB has still this issue with some Armbian images ? Armbian minimal boots without aby issues. Not sure why it works and desktop doesnt.
