All Activity

This stream auto-updates

  1. Yesterday
  2. Could you please share or point to this default environment, as I don't have the board available for tests at the moment?
  3. Hmm, do you know when the software do the detection? Maybe I just need to upgrade the bootloader on NAND for other (?) ... Don't know.. I'm not using nand right now, because I'm usind SD card to use mainline, but I think the multiboot tool flashed something to bypass NAND, if I remember correctly... 🤔 But if the detection is made during the system boot process, maybe its some resistor configuration or the kernel just "dont like" my modules. They are 8 bit instead 4 bit, and double the original density, but thats the only diferrence. Original was Samsung, K4B2G0446C, and the replacemant is from Micron, HTTC4G83BFR: K4B: just Samsung marking. 2G: 2 Gigabites module (256 Megabytes) 04: 4 bit module 4: 8 internal banks *(3 = 4 banks, 4 = 8 banks, 5 = 16 banks) 6: Voltage *(6 = 1.5v) I took this data from Samsung datasheet... Micron is a little more dificult to find the right datasheet, but its fair to assume that this module has 4 Gigabites, 8 bytes, and for 4 internal banks, since its 4G83 The letters after that is just revision type, speed, power, etc, doesn't matter in this case. Anyway, if you know where its detected the DRAM, and where the profiles for then (assuming that is some kind of profiling table) maybe just need to edit this, a big maybe on that, because I dont know s**t about the software compared to you guys. Thanks @jock and @fabiobassa for the support until now 😃 Have a nice weekend.
  4. Ah, I did not understand you soldered bga chips directly on the board! Congrats, that's quite a skill! Anyway, DDR amount is detected automatically and there is no software switch to change the amount of memory the system will detect. The right amount is purely a hardware matter, so I don't know if there is a resistor or something more complex to let the hardware being detected 🤷‍♂️ ssv6051p driver suffers from an ARP request problem, so even if the wireless is connected, the device does not actually respond to requests from external hosts, even pings, until you let the wireless exchange a packet with the network, doing like a ping from the box to the router for example. This is just a hypothesis though, no one really dug into; that could be or not be related to your isssue. To use the NAND as system drive you need to use the legacy kernel, that's right. At the moment the NAND driver is not available for mainline kernels.
  5. usual user

    Odroid M1

    Thank you for providing your firmware. I borrowed it to use fedora on my ODROID-M1. I built my kernel only with the essential commits from tobetter's tree necessary for the ODROID-M1. If I switch to 5.19.0-rc1, I can skip more commits that have already landed. The firmware in the SPI flash supports distro-boot to a certain extent, but is ultimately not usable. Your firmware is usable, but has no HDMI and USB keyboard support. And also can't cope with a compressed kernel. Whether I build the firmware myself in a timely manner, I have not yet decided. Probably I will first take care of a stable working kernel and use your firmware until then.
  6. Description Trunk to next release version. View the full article
  7. Also, the "new bootscript" is no longer required with u-boot 2022.04. They include the distro_boot method which finds the boot.scr, and that loads the kernel. env default -a saveenv
  8. If you had a recent u-boot, you wouldn't have this problem. It can read gpt, it can read ext4. Of course, you can't flash recent u-boot until you solve this problem.
  9. @jock I bought another yesterday, brand new, left with stock android and workds for my father for now. On android at least he can see emails and youtube. 😅 about the backup, no I did not make it, I should have... I had this box laying arrond, and had the ideia for desktop replacement, but then I saw the limitations that you said, but I didnt made the backup of the NAND, and that's is why I made the first post.. I know my box have 2GB, because I installed it 😂 I'm work with GPU, bga etc, and was very easy to me find DDR3 laying around, I just swap the original samsung 256MB chips for the 512MB micron ones. Maybe I need to make other steps to unlock the memory. I already reflashed it from maskrom, still 1GB. Maybe you can help.I know the hardware stuff, but no so much about the software. 🤣 Yes, this issue about wireless exists, I could not access any inbound port from wireless. I noticed that if I just plug my etherned cable, and instantly try to access SSH using the wireless ip, works fine, but if I disconnect the cable, stop working. I "fixed" apparently by disabling the eth0 with ifconfig, but I dont know if it is a proper fix 😅 About the HDMI I tested it again and worked, but show as "built in audio" instead HDMI audio, like on the legacy one does show, differentiating built in, from HDMI. Yes, I noticed that, but its the only option if you dont want to use a SD card as system drive if you have NAND, right? Anyway, the problem that I mentioned on the media script existis, you can replicate if you want. But for me, about the box, no matter, I plan now to use this box as a home server as you said. I'm running main from SD card, mininal install without desktop. I already installed apache2, mariadb, php, working fine, very responsive, I liked. If I can make 2GB work, would be awesome.
  10. What does your extlinux/extlinux.conf file look like? Without seeing the contents I can't be sure, but on its face it looks like it can't load the files, because it can't find them. For example; since you are now booting from a boot partition, it shouldn't be checking for `/boot/$file. Instead it should be loading the files from the `/` of the boot partition.
  11. @Felipe Triana Hello, I don't understand if you did or didn't backup the original firmware and how many boxes you have. Anyway, replacing a notebook with the cheapest of the cheapest hardware around is not a wise idea; such tv boxes are much more suited for light server usage and they are definitely not suitable as desktop replacement. If the amount of detected ram is 1gb, then you have 1gb, no matter what the manufacturer says about. There are plenty of reports of fake specs just in this thread, so this is no surprise. For the other issues you mention, never experienced anything like that: network services are working perfectly fine and HDMI audio device is showing up for me. About youtube, it is worth mention that there is no video acceleration in browsers nowadays. Videos are accelerated when used with proper software, but surely can't be accelerated in browsers and you can't expect anything more than a 10-years old budget-class smartphone CPU. One thing that helps is disabling desktop composition (is a general recommendation as per Armbian documentation). Legacy flavour is receiving little to no attention due to recent advancements of mainline kernels, so you'd better switch to mainline kernel, but surely these cheap tvboxes are not suitable for desktop replacement.
  12. @Igor, I found the log showed: Retrieving file: /boot/uInitrd Failed to load '/boot/uInitrd' And I made the system without boot partition and boot successfully, it can retrieve the "/boot/uInitrd" successfully. So on the "ok system", I continue to type: "ls -l /boot", and it shows: root@renegade:/boot# ls -l total 60676 -rw-r--r-- 1 root root 1536 May 16 16:12 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 May 16 16:12 boot.bmp -rw-r--r-- 1 root root 232159 May 16 16:01 config-5.16.20-rockchip64 lrwxrwxrwx 1 root root 22 May 16 16:11 dtb -> dtb-5.16.20-rockchip64 drwxr-xr-x 6 root root 4096 May 16 16:11 dtb-5.16.20-rockchip64 drwxrwxr-x 2 root root 4096 May 16 16:10 extlinux lrwxrwxrwx 1 root root 26 May 16 16:11 Image -> vmlinuz-5.16.20-rockchip64 -rw-r--r-- 1 root root 12589167 May 16 16:16 initrd.img-5.16.20-rockchip64 -rw-r--r-- 1 root root 6331787 May 16 16:01 System.map-5.16.20-rockchip64 lrwxrwxrwx 1 root root 26 May 16 16:16 uInitrd -> uInitrd-5.16.20-rockchip64 -rw-r--r-- 1 root root 12589231 May 16 16:16 uInitrd-5.16.20-rockchip64 -rw-r--r-- 1 root root 30327296 May 16 16:01 vmlinuz-5.16.20-rockchip64 There is a file of "uInitrd-5.16.20-rockchip64" on the /boot direction. And on the system I add boot partition, there is no "uInitrd-5.16.20-rockchip64"! Maybe this is the key?
  13. Oh, so except the boot log I provided above, is there still other logs I can find?
  14. That is certainly not the reason. All hardware is released with some old private / BSP / Android / presentation kernel. It always takes years to get to the mainline. Some HW never came there and never all functions gets there. This is just how this world function and Armbian is also mitigating this problem to the best possible degree. Otherwise you would be destined to much lower quality / usability and have it much later. Welcome!
  15. Yes. You didn't read my answer. I said that "if it won't work properly, its on you to debug". I suspected this will happen since we are not paying attention to making FAT boot support This exists in the system with one reason only - in case some hardware can't be boot from ext4 directly, we use this and adopt boot scripts to meet this scenario. And this is your job - to adopt boot scripts - what boot log tells you?
  16. @Igor,thanks for your relpy! I tried to add the BOOTFS_TYPE="fat" to the end of the board config file. It really generated the boot partition! But after the bootloader boot, the kernel cannot boot successfully, the console shows like below: U-Boot 2021.07-armbian (May 28 2022 - 14:59:35 +0800) Model: Firefly roc-rk3328-cc DRAM: 1022 MiB PMIC: RK8050 (on=0x40, off=0x00) MMC: mmc@ff500000: 1 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Firefly roc-rk3328-cc Net: eth1: ethernet@ff550000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 349 bytes read in 4 ms (85 KiB/s) 1: Armbian Retrieving file: /boot/uInitrd Failed to load '/boot/uInitrd' Skipping Armbian for failure retrieving initrd SCRIPT FAILED: continuing... 64809 bytes read in 9 ms (6.9 MiB/s) 7[r[999;999H[6n8Scanning disk mmc@ff500000.blk... Found 3 disks No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image MMC Device 0 not found no mmc device at slot 0 starting USB... Bus usb@ff5c0000: USB EHCI 1.00 Bus usb@ff5d0000: USB OHCI 1.0 Bus usb@ff580000: USB DWC2 scanning bus usb@ff5c0000 for devices... 1 USB Device(s) found scanning bus usb@ff5d0000 for devices... 1 USB Device(s) found scanning bus usb@ff580000 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device Speed: 100, full duplex BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 BOOTP broadcast 4 BOOTP broadcast 5 BOOTP broadcast 6 BOOTP broadcast 7 BOOTP broadcast 8 BOOTP broadcast 9 BOOTP broadcast 10 BOOTP broadcast 11 BOOTP broadcast 12 BOOTP broadcast 13 BOOTP broadcast 14 BOOTP broadcast 15 BOOTP broadcast 16 BOOTP broadcast 17 Is there any step I haven't made?
  17. Yes, those has to be fat32. Strange. Otherwise instructions on download pages are working - but with most recent images only.
  18. @fabiobassa Hi, I'm only replying now, because the forum limts one post per day for me, for now a least. Ok. Back to the topic. Yesterday, I was trying to go back to the android because I was thinking in use the TV BOX as a temporary replacemant to my father's notebook, that stopped working and I already resoldered almost everything changed the SIO, SB etc.. Anyway, today I just boght another box, with android and installed for him, and worked fine... but would be nice to have a full backup of the nand anyway, if one day I wish to go back to original firmware, I should have done the backup. The box is a MXQ-4K, as i said, but now I will give details: It features a RK3228A, with 2GB of Micron DDR3 (2 chips on top, 2 on the back of board), a 8GB BGA NAND, and a SV6051 wireless chip and R329Q_V3.0 board revision. I took some photos for more details, right below here: Here a close up of the rockchip on this board, before I changed the heatsink Here is 2 of the 4 DDR3 ram chips, its HTTC4G83BGR (4 gigabites, or 512MB per module) The wireless chip, SV6051P, nothing special.. An overview of the back of the board, showing the nand and pcb shape And finely a overview of the board powered on, running main build from SD Card... Ok, things that I noticed, that can ou cannot be bugs: So far is what I noticed... I would be already happy if a least I could recognize the full 2GB of ram on board and wireless worked on inbound connections, a least I could use the box as a home server, for files, websites, etc. I found other issues that I think is maybe the hardware itself that cant cope with todays demands: main or legacy, even with multimedia tools installed, Youtube can't even play at 144p without dropping 20 to 40% of the frames, tested windowd, and fullscreen, same. Youtube keep rendering on CPU mode, with firefox or chromium, even if I run the browser with glrun command. So far thats it, I'm afraid that I will be able only to reply after 24 hours, because of forum limitation, so in this case, until tomorrow! Thank you for the attention,
  19. Kernel 5.19 (rc1 will be released in about one week) will have all drivers, but no DT. So 5.20 will presumably have initial support, with DT included. Probably USB too. However, patches exists for most features.
  20. Rock3A test with jammy build with kernel 5.17.5 WIFI: -Qualcomm QCA9377 (5ghz/2.4gz and bluetooth), RTL8821CU(5ghz and 2.4ghz) , MT7601U chipsets are working. QCA9377 is somehow chopped 6mbit/s transfer rate, the others have nice performance for common tasks like upgrading the system and browsing. It should work tools for monitoring wifi like tcpdump and hacking with aircrack-ng. -ethernet: its 1gbit/s, my router detects but I dont have gigabit internet provider to test downloads. -docker can be installed in the 3rd softy modules option without problem as was in other kernel versions 4.19 and 5.10. Didn't test it at the moment, but I will certainly test and use it. SYSTEM: -Since I plugedd a lot of adapters, power drain was more than the average, so it rebooted the board somehow with 5v voltage and 3 amps available from the powerbank. The board becomes more at stable above 9v. 5v is for tasks that are not really demanding, watching the load from htop helped to see that. -Using hdmi-vga adapter its still an issue, tried lower the resolution and the screen rate to 1366x768 60hz/30hz and 1650x1050 60/30hz but monitor still managed to turn off and on. Some stuff I will test more in this board, but at the time, this kernel suits well in this board for tasks using cli.
  21. Avnet RZBoard V2L is an Arm Linux SBC for AI vision applications that’s about the size of a business card (or a Raspberry Pi), and powered by a Renesas RZ/V2L Cortex-A55/M33 processor with an on-chip DRP-AI accelerator. The board also comes with 2GB DDR4, 32GB eMMC flash, 16MB QSPI flash, Gigabit Ethernet, WiFi 5 and Bluetooth 5.0, multiple USB ports, MIPI DSI/CSI interfaces, as well as a Pi HAT compatible 40-pin GPIO header. RZBoard V2L specifications: SoC – Renesas RZ/V2L with 2x Arm Cortex A55 cores @ up to 1.2 GHz, 1x Arm Cortex M33 real-time core @ 200 MHz, Arm Mali G31 GPU @ 500MHz, DRP-AI accelerator, DRP Simple ISP (full HD), and a H.264 Hardware Video Enc/Dec (full HD) System Memory – 2GB DDR4 (16-bit with ECC) Storage 32GB eMMC flash 16MB QSPI NOR Flash MicroSD card socket Video Output – MIPI DSI and HDMI (selectable) Camera I/F [...] The post RZBoard V2L – A business card-sized Renesas RZ/V2L SBC for AI vision applications appeared first on CNX Software - Embedded Systems News. View the full article
  22. Nevermind, 😙 kept trying reformatted stick again and it worked. So for those having this issue make sure to format your stick to MBR not GPT and then make a FAT32 partition.
  23. Getting stuck out of the gate (of course never goes as documented🤣) https://puhoy.github.io/posts/armbian_on_espressobin/ While attempting to flash the required uboot update I keep getting a "permission" type error I've tried with usb stick and sd card, formated ext4, formatted fat and various permutations including simple filename....all give the same error even though usb and mmc commands say the media is there This is a v5. I have an identical one I set up a few years ago with ubuntu 18 but I did not have to flash this new uboot. Any thoughts? Do one of the jumpers have to be set in order to flash? Marvell>> usb info 1: Hub, USB Revision 3.0 - U-Boot XHCI Host Controller - Class: Hub - PacketSize: 9 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 1.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms 1: Hub, USB Revision 2.0 - u-boot EHCI Host Controller - Class: Hub - PacketSize: 64 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 1.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms 2: Mass Storage, USB Revision 2.0 - SanDisk Corporation Staples Relay SNDK7E38850327C07602 - Class: (from Interface) Mass Storage - PacketSize: 64 Configurations: 1 - Vendor: 0x0781 Product 0x5202 Version 0.32 Configuration: 1 - Interfaces: 1 Bus Powered 200mA Interface: 0 - Alternate Setting 0, Endpoints: 2 - Class Mass Storage, Transp. SCSI, Bulk only - Endpoint 1 In Bulk MaxPacket 512 - Endpoint 1 Out Bulk MaxPacket 512 Marvell>> bubt flash-image-DDR3-2g_2cs_7-1000_800.bin spi usb Burning U-BOOT image "flash-image-DDR3-2g_2cs_7-1000_800.bin" from "usb" to "spi" USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found ** File not found flash-image-DDR3-2g_2cs_7-1000_800.bin ** Error: Failed to read file flash-image-DDR3-2g_2cs_7-1000_800.bin from usb exit not allowed from main input shell. Marvell>> mmc info Device: sdhci@d0000 Manufacturer ID: 3 OEM: 5344 Name: SU08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 7.4 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes Marvell>> bubt flash-image-DDR3-2g_2cs_7-1000_800.bin spi mmc Burning U-BOOT image "flash-image-DDR3-2g_2cs_7-1000_800.bin" from "mmc" to "spi" Card did not respond to voltage select! mmc_init: -95, time 42 MMC Device 1 not found No SD/MMC/eMMC card found Error: Failed to read file flash-image-DDR3-2g_2cs_7-1000_800.bin from mmc exit not allowed from main input shell.
  24. Last week
  25. Image building in ubuntu jammy on aarch64 platform breaks with diagnostic [ o.k. ] Calling image customization script [ customize-image.sh ] [ o.k. ] No longer needed packages [ purge ] [ o.k. ] Unmounting [ /root/armbian/.tmp/rootfs-4a58bdb8-aac0-472d-8f05-0d11ef0816e8 ] [ o.k. ] Preparing image file for rootfs [ odroidn2 jammy ] [ o.k. ] Current rootfs size [ 1285 MiB ] [ o.k. ] Creating blank image for rootfs [ 1612 MiB ] [ o.k. ] Creating partitions [ root: ext4 ] [ error ] ERROR in function check_loop_device [ main.sh:588 -> main.sh:549 -> debootstrap.sh:97 -> debootstrap.sh:658 -> image-helpers.sh:112 -> general.sh:0 ] [ error ] Device node /dev/loop0p1 does not exist [ o.k. ] Process terminated I found there no /dev/loop0p1 devices for partitions after loop mounting. Only on aarch64. On x64 devices for partitions are present. Then I found adding -P to losetup fixes it. How Has This Been Tested? [×] Build image for Rockpi-4a on Odroid-N2 Ubuntu Jammy, then boot Rockpi board from that image [×] Build image for Rockpi-4a on x64 Ubuntu Jammy, then boot Rockpi board from that image Checklist: [×] My code follows the style guidelines of this project [] I have performed a self-review of my own code [] I have commented my code, particularly in hard-to-understand areas [] I have made corresponding changes to the documentation [×] My changes generate no new warnings [] Any dependent changes have been merged and published in downstream modules View the full article
  26. Description This commit forces cgroup v1 usage as a workaround for docker / runc BPF issues until a proper fix is submitted Context Docker 20.10+ cannot run on our Asus Tinkerboard, it throws BPF related errors (Like opencontainers/runc#2959 , especially this comment). I tried a lot of armbian flavors (focal, jammy, bullseye + current, edge and legacy kernels), and even building an image with CONFIG_BPF_SYSCALL=y as suggested by this comment but it didn't fix the issue. The only thing that fixed docker was to add extraargs=systemd.unified_cgroup_hierarchy=0 to /boot/armbianEnv.txt. Until someone else does a proper fix to make cgroup v2 working, I suggest downgrading to cgroup v1 with this extraarg. How Has This Been Tested? [x] Tested on Asus Tinkerboard with latest 5.15 stable kernel from apt repository. [ ] :x: NOT tested with edge and legacy kernels (Sorry I had to quickly put the machine into production and didn't have time to test other kernels) Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation => Does it need a documentation change ? [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  1. Load more activity