All Activity

Nice! Enable SDHCI + emmc1 + emmc2 + emmc3 on DTS and recompile Check if usb*_dphy it's OTG or HOST on DTS

Never mind, still broken, 23.8.1 worked.

134 views and no Idea? Should I reinstall the old image? Regards, Holm Ok.. forget about that above, it's simply the wrong xrandr output )false DISPLAY variable). I can switch to HDMI1-1 and get a picture, but the default generated config for the Xserver seems to be wrong after the update.. One Question left: How can I switch the Video Output to VGA or HDMI or LCD on Armbian? Originally this was possible with a u-boot kernel Variable..but the original u-boot can't write to a fat partition..since there is none..? Regards, Holm

That is O.K., but Armbian build framework does not accept HW related tickets. Forum is right place where you can bring this up and discuss what to do. Then open a PR if solution emerges ... Without this patch, PCI probing will randomly fail. Which is worse then 100% going up in 1x. This is my 2c. I understand that you would like to have a perfect functioning PCI system on this hardware platform and if you cover someone several weeks of R&D, this can probably be done. Since this will not happen, we have partial solution/workaround in place, this forum and we have each other.

Hi there, I have been using a nanopi m4v2 for openmediavault for 4 years. In that time my SD card has died once. Now I have ordered an emmc module to do a full clean install of my server. So my questions are, is it wise to boot from the SD card and have the system on the emmc because the sd card can die faster? And if I boot from the SD card and it needs to be replaced, can I just insert a new one and everything will work as before? (With a freshly installed Armbian) If I do a backup of the emmc with win32 disk imager, can I burn the backup to a new emmc with a different sd-card as boot? When I do an armbian install, does it copy the system files to the emmc each time? Thanks and Greetings!

Fixed it!

Pardon me for asking here. I need to re-install OPi PC 2 -which I use as a firewall/router- because the old Ubuntu from 2020 is EOL. - Is the kernel problem stated here still an issue? Latest DL is Armbian_community_24.5.0-trunk.667_Orangepipc2_jammy_current_6.6.31_gnome_desktop.img.xz - I also have Armbian_23.8.1_Orangepipc2_jammy_current_6.1.47_xfce_desktop.img.xz from the archives. Which one is to go? When I start, I'll probably lose my Internet connection...

Hi, I've build an SD card image with in a buildroot myself, used the stable branch as suggested. "For stable branch use --branch=v23.11"..and that all worked good so far. I'm no linux guy at all and begun some investigations, installed packages and configured the system, this was an desktop variant with xfce. Somewhere in the middle of work I've got the message that a security update is available and I should do an apt upgrade..done that. Interresting for me was, that I've got an Update to Armbian 24.2.1 jammy.. ok ..then this is so. I've noticed later that I don't have any video output from X11 anymore, after the login prompt the screen gets black with an cursor above left and later is shut off entirely, but the Xserver is still running, [pre] 1125 tty7 Ssl+ 0:06 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/ru n/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [/pre] xrandr output: [pre] xrandr Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 16384 x 16384 DVI-I-0 disconnected primary (normal left inverted right x axis y axis) DVI-I-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 59.93 1680x1050 59.95 1600x1200 60.00 1440x900 74.98 59.89 1280x1024 75.02 72.00 60.02 1024x768 75.03 70.07 60.00 800x600 75.00 72.19 60.32 640x480 75.00 72.81 65.99 59.94 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DVI-D-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.00*+ 50.00 1680x1050 59.95 1600x900 60.00 1440x900 59.89 1280x1024 75.02 60.02 1280x800 59.81 1280x720 60.00 50.00 1152x864 75.00 1024x768 75.03 70.07 60.00 800x600 75.00 72.19 60.32 56.25 720x576 50.00 720x480 59.94 640x480 75.00 72.81 59.94 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) [/pre] I've fiddeled around with some commands, but I'm unable to restore the Xserver Output on the DVI Output of the Cubieboard2. I have an DVI to VGA Connector plugged in and an TFT Display with the VGA Input to the converter. I'm unable to use the vga output that is provided at the DVK521 Board (WaveShare) too and already had planned to ask here how I can switch between the Video connectors with an actual Armbian. The last thing I've done where some entries in the armbianEnv to get an 2nd uart and the 1wire Interface enabled, that worked so far, but I was logged in with ssh from my host and haven't seen the X-Display from the Cubieboard2 since the monitor was switched to DVI which is connected to the host as 2nd monitor. I don't think that there is something wrong: [pre] armbianEnv: verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 rootdev=UUID=42951d58-2c17-42a5-af83-c6eaf7357967 rootfstype=ext4 overlay_prefix=sun7i-a20 overlays=uart3 w1-gpio param_uart2_rtscts=1 param_w1_pin=PB10 param_w1_pin_int_pullup=1 #extraargs=video=HDMI-A-1:1920x1080M@60 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u [/pre] The commented out extraargs line was from Igor suggested in another thread for a problem w/o connected monitor..but changed nothing. Can someone help me please? I hadn't much todo with Xserver setup in the last years..I'm tapping around pretty much in the dark.. Kind Regards, Holm

I get all working with USB Tethering, after install miniarch WiFi works...

I just bought 3 of these, 2 for me and one for a friend. I should have them by next week and can follow line by line instructions.

Oh thanks a lot! I could probably use the 1st patch to the armbianEnv.txt file: the root volume is on a usb drive, so the 2nd option would not work for me. But I still believe there is some hardware issue because even when USB ports work, the voltage supplied to is far below 5V. And the issue I have has been getting worse over the years, as if a component was wearing out. I'll report back when I can give it a try.

wifi operational with: ln -sf /lib/firmware/brcm/brcmfmac4330.bin /lib/firmware/brcm/brcmfmac4330-sdio.rockchip,rk3528-demo1-lp4-v10.bin ln -sf /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.rockchip,rk3528-demo1-lp4-v10.txt and a reboot, then nmtui to set up a connection

Thank for the idea of the usb wifi i didn't buy it, i try a other dc power with 400ma i already have around originally I was using 300ma, now the wifi works like a charms, how high you think I can go 1a ? I want to add a fan

base-files: hardcoded cache of base-files version per RELEASE/ARCH, as of 20240522 base-files: hardcoded cache of base-files version per RELEASE/ARCH, as of 20240522 packages.debian.org and packages.ubuntu.com are having a meltdown and builds are stuck this is a quick & dirty fix to get builds going we should urgently replace this with the 'right thing' trying to maintain this manually will cause insanity View the full article

Mesa 24.1 is out, and the graphics team at Collabora has been working hard to bring a slew of new features and bug fixes to Panfrost, Zink, NVK, and Mesa in general. Here's a look at their contributions for this release cycle. View the full article

Thanks. Now it works fine Thank you

did you check this?

Purchase Link This should be a fun one. Bought the 4GB/128GB variant. AP6330 Wifi Stock software is a really, really bad Android TV port. Looks like a Google Pixel 5 image that has had RK3528 support hacked into it. Some parts report the device as Pixel 5, others MX10. RKdumper wouldn't work. Wifi is hardcoded to China region in the kernel commandline, so wifi doesn't work in North America. Boots into a setup wizard that can't be closed, and forces an internet connection. Since wifi is broken out of the box, had to use ethernet to get past the setup wizard. Transpeed does not have a website or offer stock firmware. The vendor I purchased it from refused to supply a stock image. Image was pre-rooted, so used ethernet+adb to adb pull the entire flash chip. Unfortunately the Android partitions appear to be encrypted and only show gibberish directory names. Was able to use extract-dtb on one of the raw binary partitions to get the stock DTB, which is all I cared about anyway. It is pretty close to an existing one in Armbian (rk3528-demo1-lp4-v10) Located and soldered the tiny UART pads without destroying the box. Tried my different garbage clone USB UART adapters to find one that could handle RockChip 1.5 megabit over serial, fake CH340G did the job, fake CP2102 would not. May the best fake product win! Followed @Hqnicolas guidance from this thread and used the hinlink-h28k trunk release with 5.10 kernel as a base, and changed the dtb referenced in armbianenv to the stock android DTB extracted from the device, and of course it would not boot. Lots of errors, kernel panics on UART, errors from SD reader. Changed to Kernel 6.1 base hinlink-h28k image, and tried rk3528-demo1-lp4-v10.dtb, that one almost boots but doesn't see the SD card so can't mount root filesystem. Began DTB surgery, added pieces of the SD card initialization from the factory DTB to the rk3528-demo1-lp4-v10.dtb, got it to boot. Black USB port dead, Blue USB port working. No HDMI output on console (only UART) but does load XFCE when the GUI autostarts. Will keep slicing and dicing DTB to gain functions. Will need to drop in proper NVRAM file to get AP6330 working as I've had to do on other boards. //rk3528-demo1-lp4-v10.dts SD Not Detected mmc@ffc30000 { compatible = "rockchip,rk3528-dw-mshc\0rockchip,rk3288-dw-mshc"; reg = <0x00 0xffc30000 0x00 0x4000>; interrupts = <0x00 0x85 0x04>; max-frequency = <0x8f0d180>; clocks = <0x02 0x198 0x02 0x197 0x7a 0x01 0x7a 0x02>; clock-names = "biu\0ciu\0ciu-drive\0ciu-sample"; fifo-depth = <0x100>; resets = <0x02 0x2a9>; reset-names = "reset"; rockchip,use-v2-tuning; status = "disabled"; phandle = <0x10e>; }; //Factory DTB - SD reader stuck Busy, can't select voltage etc. mmc@ffc30000 { compatible = "rockchip,rk3528-dw-mshc\0rockchip,rk3288-dw-mshc"; reg = <0x00 0xffc30000 0x00 0x4000>; interrupts = <0x00 0x85 0x04>; max-frequency = <0x8f0d180>; clocks = <0x02 0x198 0x02 0x197 0x68 0x01 0x68 0x02>; clock-names = "biu\0ciu\0ciu-drive\0ciu-sample"; fifo-depth = <0x100>; resets = <0x02 0x2a9>; reset-names = "reset"; rockchip,use-v2-tuning; //status = "disabled" status = "okay"; bus-width = <0x04>; cap-mmc-highspeed; cap-sd-highspeed; disable-wp; pinctrl-names = "default"; pinctrl-0 = <0x6d 0x6e 0x6f 0x70>; rockchip,default-sample-phase = <0x5a>; supports-sd; sd-uhs-sdr12; sd-uhs-sdr25; sd-uhs-sdr50; sd-uhs-sdr104; phandle = <0xff>; }; //Combo that works enough to boot mmc@ffc30000 { compatible = "rockchip,rk3528-dw-mshc\0rockchip,rk3288-dw-mshc"; reg = <0x00 0xffc30000 0x00 0x4000>; interrupts = <0x00 0x85 0x04>; max-frequency = <0x8f0d180>; //clocks = <0x02 0x198 0x02 0x197 0x7a 0x01 0x7a 0x02>; clocks = <0x02 0x198 0x02 0x197 0x68 0x01 0x68 0x02>; clock-names = "biu\0ciu\0ciu-drive\0ciu-sample"; fifo-depth = <0x100>; resets = <0x02 0x2a9>; reset-names = "reset"; rockchip,use-v2-tuning; //status = "disabled"; //from stock dtb status = "okay"; bus-width = <0x04>; //cap-mmc-highspeed; //cap-sd-highspeed; disable-wp; pinctrl-names = "default"; pinctrl-0 = <0x6d 0x6e 0x6f 0x70>; //rockchip,default-sample-phase = <0x5a>; supports-sd; //sd-uhs-sdr12; //sd-uhs-sdr25; //sd-uhs-sdr50; //sd-uhs-sdr104; //end from stock dtb phandle = <0x10e>; }; rk3528-transpeed-8k-ultra-hd-mx10.dts

@Nick A, Despite of your long instructions, several tries, spending hours with studying related topics, practically I could not reach any success. The most annoying thing is that when trying to boot the device from sdcard (using the uboot button), nothing happens, not even a single character appears on the console output. How the boot process supposed to work? My understanding, that the beginning part of the sdcard image contains an uboot, which is able to work with a partly initialized (powered up) hardware (starting to use SoC internal RAM), and would make minimal further hardware initialization, and load modules from the boot partition, like kernel, root-fs, device tree. Is it a valid assumption, that uboot should echoe the start of boot process already? (At least when the stock firmware starts, I see uboot messages.) Is it possible, that the uboot on the sdcard is not compatible with my hardware? Or simply the external boot is restricted by the software of the T95H android box? I also downloaded firmware for the box (found e.g. T95H-H616-X22.img), and checked, what file structure it shows: it is "PhoenixSuite image file", different format than an armbian (or other os) image...

Whow..worked "out of the Box" with Overlays. Good Job Guys! Does anyone know if that Toch-LCD that is coming with that DVK521 Kit for the Cubieboards is working with armbian? I don't know anything about the hardware or even the original Software that came with the Cubieboard2 .. and the examples. The 3 boards I have are all used and none was complete with the original software to try out something. Regards, Holm