Jump to content

Search the Community

Showing results for tags 'other'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. I think we should do exactly the opposite. As soon as the author realizes that his codebase has begun to create stable images for the family\branch, he can invite the most active members of this group to test and fix bugs. That is, errors, changes must be made in this branch. While the master should remain stable and not create problems for the current work.
  2. Hi, just got a Nanopi R5C (waiting for an RPi for more than a year, yet...) but I couldn't find any headless images for this little box. There's an official debian-image available running LDXE, but open media vault isn't able to run on an Desktop linux... Any chances there will be support for the Nano Pi R5C / Rockchip RK3568B2? btw: can't choose R5C or just 'others' from the drop-down when creating a new post...
  3. Hi, i can't get usbip work, there's a tutorial or something else that i can follow to make usbip working over that soc board? cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" #/usr/bin/usbip WARNING: usbip not found for kernel 4.14.84 You may need to install the following packages for this specific kernel: linux-tools-4.14.84-sunxi linux-cloud-tools-4.14.84-sunxi You may also want to install one of the following packages to keep up to date: linux-tools-sunxi linux-cloud-tools-sunxi The board is a orange pi r1 how i can make that working?
  4. Hi everyone, Here an idea: It may be useful to know which board and wich compilation environment has already been tested with armbian-next, i.e.: Board User space Kernel Interface Environment Compilation Boot Hardware peripherals Hardware features Apps uefi-x86 Bullseye Current Desktop XFCE ✅ ✅ uefi-x86 Bullseye Edge Desktop XFCE ✅ ✅ bananapim5 Bullseye Edge Desktop XFCE ✅ ❎ And for the compilation environment: Host Container Guest Compilation Windows 10 VirtualBox Ubuntu Jammy 22.04.1 Desktop amd64 ✅ Ubuntu Jammy 22.04.1 Desktop amd64 -- -- ✅ The goal would be not to test every possible combination, but just to not waste time (test something that has already been tested) and as a bonus have an overview. "We" neither should fix images in next that aren't working in master too, but next should be at least on par with master. The forum is probably not the right place to host such a document. Maybe Jira? What do you think about this idea? Feel free to reject it or propose modifications.
  5. Hi all, I'm trying to build @balbes150's risc-v branch of Armbian and put it into /dev/sdb 32GB SD card. I'm using Ubuntu 22.04. ./compile.sh BOARD=nezha BRANCH=current RELEASE=sid BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no CARD_DEVICE="/dev/sdb" It went well, the card seems OK to me. $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 931,5G 0 disk └─sda1 8:1 0 931,5G 0 part sdb 8:16 1 28,9G 0 disk ├─sdb1 8:17 1 256M 0 part └─sdb2 8:18 1 2,7G 0 part /media/slavek/c4be3c21-ec0c-4ccb-a9ec-f310583febf9 When I try to boot my MangoPi Pro (D1) from it, I see no output on HDMI. I might need to add a bootloader to the card? How do I do it? Could some of Armbian gurus help me please? Thank you, JP
  6. Hi everyone! I'm software developer but have no (or little) clue about electronics & electricity, and would like to dive into the SBC world. I still don't have a goal other than have fun and support this community during my free time. I probably need to buy some devices (my budget is limited): A voltmeter A soldering station. Which filler material is more appopriate? An USB-to-TTL adapter to debug the serial output. Specs? Last but not least: an SBC! Which one is good but currently lacks support from this community? Something else? Thank you for your advices!
  7. I am currently attempting to compile a device tree overlay, in connection with an OPi Zero 2. But my questions here are of rather general nature (with regards to DT compiling), so I posted it here. ------- Goal: Creating a DT overlay to enable certain hardware currently not working on the board: wifi and HDMI output. Alternatively, compiling a "full" .dtb file for the board, replacing the one currently used during boot. For completeness: In the below I experimented starting from the Armbian_22.08.7_Orangepizero2_bullseye_edge_5.19.16.img.xz image, 406585908 bytes. uname -a: "Linux orangepizero2 5.19.16-sunxi64 #22.08.6 SMP Tue Oct 18 06:56:22 UTC 2022 aarch64 GNU/Linux" Boot-up (at times shaky), UART and USB (via type A socket) is working with this image. ------- I have tried to assemble a dts file, to be made into an overlay, from snippets seen at https://github.com/jernejsk/linux-1/commit/e7222b1f0dfde22a3b60de7f3add6599fd942e84 But this runs into errors, as references are missing, in this case for example "reg_aldo2". I can look at the complete file, https://github.com/jernejsk/linux-1/blob/e7222b1f0dfde22a3b60de7f3add6599fd942e84/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts and see that it includes #include "sun50i-h616.dtsi", which I can copy from the tree. Further I can make additional code additions that all missing references are resolvable. Nevertheless, even then errors (or to be exact: warnings) remain that look as if the resulting .dtbo will not be functional. Thus: What is the typical workflow in compiling overlays? 1. How much of existing code needs to be included? (I also tried, as alternative to above, to decompile the existing dtb and use it as included file in my compilation - is this a reasonable avenue?) 2. What are negligible warnings? 3. If I compiled something resulting in an erroreous .dtbo, could it be harmful to the hardware? (Or asked differently: tinkering with what parts of the device tree is potentially damaging to the board?) ------- Example warnings: sun50i-h616.dtsi:109.6-1009.4: Warning (unit_address_vs_reg): /soc: node has a reg or ranges property, but no unit name also defined at orangepi-zero2_wifi_and_hdmi.dts:61.13-81.11 sun50i-h616.dtsi:375.21-395.5: Warning (avoid_unnecessary_addr_size): /soc/mmc@4021000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property also defined at orangepi-zero2_wifi_and_hdmi.dts:63.25-79.15 Thanks to the knowledgable.
  8. I was doing some testing today on aml-s9xx-box builds and noticed that with meson64-current (6.0.13) kernels the boot logo is showing, but with meson64-edge (6.1.0) kernels it does not. I know there was a recent commit that probably is causing this, something about removing the old way of handling boot logos. So my question is, what needs to change to convert to the new way? I suspect it has something to do with the append line that the build process is inserting into the extlinux.conf file: append root=UUID=0ffde9aa-5a6a-4d6f-bbef-0d8daf439537 rw no_console_suspend c onsoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=boo tsplash.armbian
  9. Hello, my name is Wolfgang and I´m from Germany and hope you can maybe help me. First I have no knowledge related to the nano PIs. I bought an R2D2 from Deagostini. The R2 has a board which looks like an nano PI air. It´s called DRCC H3 V2.0. The R2 has different sounds and video seqeunces which can be played by R2. My quetsion is now do you think it´s possible to change or add sounds to the board? Thanks in advance Wolfgang
  10. Hi Team, i have a lcd touchscreen android rockchip rk3288 ( armeabi-v7a ) and i want change the OS with armbian and install it on sd card , which image that should i use? regards, Adrian
  11. Hello dear armbianites, I'm trying to make the hc1 optimization for the odroid HC2 board permanent, every time the kernel is updated, armbiam loses the optimization and an admin action is needed to apply the optimization again via ambianconfig > System DTB > optimized board configuration, followed by a reboot. My Odroid HC2 suffers from temperature sensor problems, which can be easily bypassed. But I avoid restarts of this server which hosts an OMV instance for personal needs. I understand that the /boot/armbianEnv.txt file passes the information to /boot/boot.ini, but this file seems to be overwritten when the kernel is updated! is there any possibility of upstream action like 'first.boot' after update? konki
  12. Hi all, I have a bit of an odd application, but given the recent effort being put into UEFI boot, I thought I'd ask for some help. I have a Gigabyte R152-P30, which is an Ampere 80 core, single socket server. Flash drive boot works just fine, but nand-sata-install onto the server's NVMe SSD has been troublesome. I've tried several permutations of having partitions and not having partitions on the NVMe drive, but none seem to actually create a bootable result. I see on the generic armbian image page that it suggests creating an EFI partition which I do (nvme0n1p1). It then proceeds to leave that partition empty. I also have another btrfs partition on the same nvme drive (nvme0n1p2). The second partition is the one that shows up in the nand-sata-install config menu. The script sucessfully moves all files onto this new btrfs drive, and I can see it all when I mount it. If I remove the EFI partition, nothing shows up in the servers boot optoins menu. If I leave the EFI partition in, I get an option in the boot options menu, but it does nothing (black screen). I assume this is because the EFI partition is empty. I'm still pretty new to understanding the Linux boot sequence, so please forgive me if I've forgotten anything trivial. My best guess was simply CP-ing over the flash drives efi folder to the nvme drive's but naturally that didn't work (unknown filesystem) and just dropped me into grub rescue. Attaching logs from the servers BMC (apologies that they're screenshots). If needed I can figure out a way to get armbianmonitor -U out to you guys. Thanks! pics: https://imgur.com/a/yunzvJy
  13. Hi there, I have been using Ubuntu stock from Hardkernel but it is worse than a kick upon my jewels... As usual only Armbian is the way to go, however I personally dislike Ubuntu therefore I'd like to go with Debian but I didn't get the difference between CLI and Minimal. Can anyone advise me? Thanks in advance, F.
  14. I am new to arm devices. I'm trying to build a fully working armbian system for the pcduino8-uno which uses the Allwinner a83t/h8 soc. I know these are not the best, but I got it from amazon for $18 and it runs home assistant very well. I built a new u-boot which appears to initialize the hardware properly as it sees all the usb port as well as obtains an ip from my dhcp server. Using sun8i-a83t-allwinner-h8homlet-v2 as my starting point.. I built a new kernel from 6.1.0-rc6. Everything seems to work properly except the ethernet controller. I can use a usb ethernet dongle, but I would like to get the onboard working Dmesg shows " [ 1.594628] dwmac-sun8i 1c30000.ethernet: IRQ eth_wake_irq not found [ 1.594656] dwmac-sun8i 1c30000.ethernet: IRQ eth_lpi not found [ 1.594760] dwmac-sun8i 1c30000.ethernet: supply phy not found, using dummy regulator [ 1.595128] dwmac-sun8i 1c30000.ethernet: supply phy-io not found, using dummy regulator [ 1.595363] dwmac-sun8i: probe of 1c30000.ethernet failed with error -22 " I'm assuming something is incorrect in the ethernet driver. Any Ideas how to fix this ? Thanks
  15. https://gist.github.com/voltagex/1dae7c0bf153c76a49bea407f932be69 if anyone's interested.
  16. I would like to make myself more familiar with the early linx boot process on ARM (u-boot, device trees and co.) and my idea was that I will start tweaking with something which actually works. I tried to figure out how to obtain the source package for u-boot (in my case for linux-u-boot-orangepi3-lts-current) but the armbian package repository seem to contain obly binaries. Any idea wherethe source packages for this binaries are located (e.g. what deb-src line do I need to add to the armbian.list to make "apt-get source" to work)?
  17. does anyone know of a version of armbian that would work on a samsung galaxy book go with a snapdragon 7c gen2? i traid the generic version and it booted to the grub, and then it restarted like all other distros i've tried. i can not find a distro to boot on this dang thing. anyone have any ideas on what to do or try? i've hit a dead end i gotta dig deeper to figure something out, so any thoughts on this would be helpful .. thanks in advance
  18. I can't seem to get apt-get update to work, this is a fresh install anyone know the fix? mango@nezha:~$ sudo apt-get update Hit:3 http://ports.ubuntu.com jammy InRelease Hit:4 http://ports.ubuntu.com jammy-security InRelease Hit:5 http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu jammy InRelease Hit:6 http://ports.ubuntu.com jammy-updates InRelease Hit:7 http://ports.ubuntu.com jammy-backports InRelease Hit:1 https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease Hit:2 https://cli.github.com/packages stable InRelease Err:2 https://cli.github.com/packages stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 Reading package lists... Done N: Skipping acquire of configured file 'main/binary-riscv64/Packages' as repository 'http://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease' doesn't support architecture 'riscv64' W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://cli.github.com/packages stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 W: Failed to fetch http://cli.github.com/packages/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 W: Some index files failed to download. They have been ignored, or old ones used instead.
  19. Good afternoon! Tell me about the case, please, the post is great, but maybe I'm initially going the wrong way. Initial task: data exchange between a remote server and equipment with a USB interface and CDC RS-232 or HID protocols. Putting a computer / laptop next to it is not an option. I did not find any ready-made solutions, there are only options: 1. Single board computer. Fast, cheap, angry, easy to make a case and PoE power from ready-made components on the market. 2. Arduino - to assemble from prototyping boards is long, difficult and expensive. To develop something of my own - the navel will be untied with my knowledge. 3. Hardware "extension" USB over TCP / IP - expensive, redundant. 4. Ready-made USB print server / router - can you easily write your own firmware? I read that OpenWrt is installed on TP-Link TL-MR3020 ... I am leaning towards the first option with a single-payer based on a combination of factors - complexity, price, availability, etc. Question on the topic. If you choose a single boarder, is it possible to implement booting from an ISO image on an eMMC partition or SD card? How do I do it on industrial PC x86 architecture: 1. I deploy Linux in the usual way (in my case I use Debian) on the master computer. 2. Create an ISO image (snapshot) using Linux Live Kit (Tomas-M). 3. I mark up disks on working computers, install GRUB, copy the prepared ISO image and tell the bootloader to boot from it. Profit. We have a "firmware" version of the download. You need to update the operating system or programs - we do this on a master computer, create a new ISO image and simply copy it to all other working computers. On single-payers, I read, U-Boot is used mainly, but he does not know how to do this. but it seems like it is written that he can boot GRUB for the second time, which can already boot ISO ... Who has any thoughts?
  20. I just installed armbian buster on my NAS (odroid HC2). Everything works perfectly. However, as debian bullseye has become stable and I expect this to happen for armbian also in the near future, I am thinking about how to do the upgrade. This is mainly because all my other boxes run bullseye and administration becomes a lot easier if all systems run the same version. In addition, I will have to do the update anyways at some point in time and therefor I want do it when armbian bullseye becomes stable. Reading through the forum I found out it is not supported. However, I am using debian now since woody and have done a lot of upgrades since then, I think I will try it for armbian also (of course after making a full backup). I already read that i should do a freeze in armbian-config (disable kernel upgrades). Having done this, can I just start upgrading to bullseye the debian way (as it is described in the bullseye release notes). And after finishing this I would disable the freeze, which would allow the kernel update also? Any thoughts on this procedure? Anything else I have to do and that would be different to vanilla debian? Regards, Jürgen
  21. Hello. I have this old rk3188 based board with 32gb rom 1gb ram. The arduino is attached for console output. I wanted to install linux in it so i flashed rk3188 armbian to my sd card and it was able to boot up from sdcard successfully. But there is no hdmi signal. I tried to modify dtb file extlinux.conf file but it didnt work. Can anyone figure out what is the problem? This is my extlinux.conf: LABEL Armbian LINUX /boot/zImage INITRD /boot/uInitrd FDT /boot/dtb/rk3188-rbox-cs968.dtb APPEND root=UUID=61de6b0d-dcd6-4049-9fe8-3a15872992b5 console=uart8250,mmio32,0x20064000 console=tty0 coherent_pool=2M video=HDMI-A-1:e rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian And this is my serial output from the board: col :11 08:07:59.748 col :10 08:07:59.752 chn 0 col 10, row 15 08:07:59.752 sdram_init done 08:07:59.752 DTONE=0x1, DTERR=0x0, DTIERR=0x0, DTPASS=0x4, DGSL=1 extra clock, DGPS=90 08:07:59.760 DTONE=0x1, DTERR=0x0, DTIERR=0x0, DTPASS=0x4, DGSL=1 extra clock, DGPS=90 08:07:59.768 DTONE=0x1, DTERR=0x0, DTIERR=0x0, DTPASS=0x4, DGSL=1 extra clock, DGPS=90 08:07:59.772 DTONE=0x1, DTERR=0x0, DTIERR=0x0, DTPASS=0x4, DGSL=1 extra clock, DGPS=90 08:07:59.781 ZERR=0, ZDONE=0, ZPD=0x0, ZPU=0x0, OPD=0x0, OPU=0x0 08:07:59.784 DRV Pull‑Up=0xb, DRV Pull‑Dwn=0xb 08:07:59.789 ODT Pull‑Up=0x2, ODT Pull‑Dwn=0x2 08:07:59.789 08:07:59.789 U‑Boot SPL 2021.01‑armbian (Feb 05 2022 ‑ 10:21:35 +0300) 08:07:59.797 Trying to boot from BOOTROM 08:07:59.797 Returning to boot ROM... 08:08:00.989 08:08:00.989 08:08:00.989 U‑Boot 2021.01‑armbian (Feb 05 2022 ‑ 10:21:35 +0300) 08:08:00.993 08:08:00.993 Model: RK3188 rbox 08:08:00.996 DRAM: 1 GiB 08:08:01.082 MMC: dwmmc@10214000: 0 08:08:01.103 In: serial@20064000 08:08:01.108 Out: serial@20064000 08:08:01.108 Err: serial@20064000 08:08:01.108 Model: RK3188 rbox 08:08:01.115 Net: Net Initialization Skipped 08:08:01.115 No ethernet found. 08:08:01.120 Hit any key to stop autoboot: 0 08:08:01.123 starting USB... 08:08:01.127 Bus usb@10180000: USB DWC2 08:08:02.386 Bus usb@101c0000: USB DWC2 08:08:03.643 scanning bus usb@10180000 for devices... 1 USB Device(s) found 08:08:04.781 scanning bus usb@101c0000 for devices... 1 USB Device(s) found 08:08:05.922 scanning usb for storage devices... 0 Storage Device(s) found 08:08:05.924 08:08:05.924 Device 0: unknown device 08:08:05.929 MMC Device 1 not found 08:08:05.932 no mmc device at slot 1 08:08:06.052 switch to partitions #0, OK 08:08:06.052 mmc0 is current device 08:08:06.055 Scanning mmc 0:1... 08:08:06.077 Found /boot/extlinux/extlinux.conf 08:08:06.077 Retrieving file: /boot/extlinux/extlinux.conf 08:08:06.088 378 bytes read in 4 ms (91.8 KiB/s) 08:08:06.092 1:^IArmbian 08:08:06.092 Retrieving file: /boot/uInitrd 08:08:08.104 7357124 bytes read in 2001 ms (3.5 MiB/s) 08:08:08.104 Retrieving file: /boot/zImage 08:08:09.972 6819336 bytes read in 1856 ms (3.5 MiB/s) 08:08:09.972 append: root=UUID=61de6b0d‑dcd6‑4049‑9fe8‑3a15872992b5 console=uart8250,mmio32,0x20064000 console=tty0 coherent_pool=2M video=HDMI‑A‑1:e rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian 08:08:09.996 Retrieving file: /boot/dtb/rk3188‑rbox‑cs968.dtb 08:08:10.016 28737 bytes read in 13 ms (2.1 MiB/s) 08:08:10.020 ## Loading init Ramdisk from Legacy Image at 64000000 ... 08:08:10.024 Image Name: uInitrd 08:08:10.028 Image Type: ARM Linux RAMDisk Image (gzip compressed) 08:08:10.034 Data Size: 7357060 Bytes = 7 MiB 08:08:10.037 Load Address: 00000000 08:08:10.041 Entry Point: 00000000 08:08:10.041 Verifying Checksum ... OK 08:08:10.169 ## Flattened Device Tree blob at 61f00000 08:08:10.172 Booting using the fdt blob at 0x61f00000 08:08:10.176 Loading Ramdisk to 6f8fb000, end 6ffff284 ... OK 08:08:10.242 Loading Device Tree to 6f8f0000, end 6f8fa040 ... OK 08:08:10.250 08:08:10.250 Starting kernel ... 08:08:10.250 08:08:10.799 [ 0.000000] Booting Linux on physical CPU 0x0 08:08:10.804 [ 0.000000] Linux version 5.10.96‑rk3188 (root@vbox) (arm‑linux‑gnueabihf‑gcc (GNU Toolchain for the A‑profile Architecture 8.3‑2019.03 (arm‑rel‑8.36)) 8.3.0, GNU ld (GNU Toolchain for the A‑profile Architecture 8.3‑2019.03 (arm‑rel‑8.36)) #trunk SMP Sat Feb 5 11:11:22 MSK 2022 08:08:10.831 [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d 08:08:10.840 [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache 08:08:10.848 [ 0.000000] OF: fdt: Machine model: RK3188T CS968 08:08:10.852 [ 0.000000] earlycon: uart8250 at MMIO32 0x20064000 (options '') 08:08:10.860 [ 0.000000] printk: bootconsole [uart8250] enabled 08:08:10.864 [ 0.000000] Memory policy: Data cache writealloc 08:08:10.872 [ 0.000000] cma: Reserved 256 MiB at 0x90000000 08:08:10.876 [ 0.000000] Zone ranges: 08:08:10.880 [ 0.000000] Normal [mem 0x0000000060000000‑0x000000008fffffff] 08:08:10.885 [ 0.000000] HighMem [mem 0x0000000090000000‑0x000000009fffffff] 08:08:10.893 [ 0.000000] Movable zone start for each node 08:08:10.897 [ 0.000000] Early memory node ranges 08:08:10.901 [ 0.000000] node 0: [mem 0x0000000060000000‑0x000000009fffffff] 08:08:10.909 [ 0.000000] Initmem setup node 0 [mem 0x0000000060000000‑0x000000009fffffff] 08:08:10.971 [ 0.000000] percpu: Embedded 16 pages/cpu s33228 r8192 d24116 u65536 08:08:10.977 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260416 08:08:10.987 [ 0.000000] Kernel command line: root=UUID=61de6b0d‑dcd6‑4049‑9fe8‑3a15872992b5 console=uart8250,mmio32,0x20064000 console=tty0 coherent_pool=2M video=HDMI‑A‑1:e rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian 08:08:11.016 [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) 08:08:11.026 [ 0.000000] Inode‑cache hash table entries: 65536 (order: 6, 262144 bytes, linear) 08:08:11.032 [ 0.000000] mem auto‑init: stack:off, heap alloc:off, heap free:off 08:08:11.093 [ 0.000000] Memory: 752384K/1048576K available (10240K kernel code, 783K rwdata, 3328K rodata, 1024K init, 307K bss, 34048K reserved, 262144K cma‑reserved, 0K highmem) 08:08:11.114 [ 0.000000] SLUB: HWalign=64, Order=0‑3, MinObjects=0, CPUs=4, Nodes=1 08:08:11.119 [ 0.000000] rcu: Hierarchical RCU implementation. 08:08:11.126 [ 0.000000] ^ITracing variant of Tasks RCU enabled. 08:08:11.130 [ 0.000000] rcu: RCU calculated value of scheduler‑enlistment delay is 30 jiffies. 08:08:11.137 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 08:08:11.147 [ 0.000000] L2C: DT/platform modifies aux control register: 0x02050000 ‑> 0x32050000 08:08:11.155 [ 0.000000] L2C‑310 erratum 769419 enabled 08:08:11.159 [ 0.000000] L2C‑310 enabling early BRESP for Cortex‑A9 08:08:11.163 [ 0.000000] L2C‑310 full line of zeros enabled for Cortex‑A9 08:08:11.171 [ 0.000000] L2C‑310 ID prefetch enabled, offset 1 lines 08:08:11.175 [ 0.000000] L2C‑310 dynamic clock gating enabled, standby mode enabled 08:08:11.184 [ 0.000000] L2C‑310 cache controller enabled, 16 ways, 512 kB 08:08:11.192 [ 0.000000] L2C‑310: CACHE_ID 0x4100c0c8, AUX_CTRL 0x76050001 08:08:11.233 [ 0.000000] random: get_random_bytes called from start_kernel+0x5c8/0x788 with crng_init=0 08:08:11.237 [ 0.000000] clocksource: rk_timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns 08:08:11.249 [ 0.000009] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns 08:08:11.256 [ 0.009283] Console: colour dummy device 80x30 08:08:11.263 [ 0.014199] printk: console [tty0] enabled 08:08:11.269 [ 0.018726] printk: bootconsole [uart8250] disabled
  22. # apt-get update Stary:1 http://ports.ubuntu.com jammy InRelease Stary:2 http://ports.ubuntu.com jammy-security InRelease Stary:3 http://ports.ubuntu.com jammy-updates InRelease Stary:4 http://ports.ubuntu.com jammy-backports InRelease Ign:5 https://apt.armbian.com jammy InRelease Ign:5 https://apt.armbian.com jammy InRelease Ign:5 https://apt.armbian.com jammy InRelease Błąd:5 https://apt.armbian.com jammy InRelease 500 Internal Server Error [IP: 443] Czytanie list pakietów... Gotowe W: Nie udało się pobrać https://apt.armbian.com/dists/jammy/InRelease 500 Internal Server Error [IP: 443] W: Nie udało się pobrać niektórych plików indeksu, zostały one zignorowane lub użyto ich starszej wersji. i cant update my armbian uname -a 5.15.43-sunxi #22.05.1 SMP Sat May 28 08:17:47 UTC 2022 armv7l armv7l armv7l GNU/Linux
  23. Hi all. Here my video about the MangoPi MQ-Pro. It's not powerful, not cheap and not great at anything. But it is nice to see it works. Everybody started out as a baby. So it now needs to grow.
  24. What is the baud rate of s905w
  25. Hi, I need to install kernel headers to build a wifi driver. Using armbian-config to install the headers does not work ... After much searching came across a logical suggestion - i.e. install the 'linux-headers-current-sunxi' package ... When I install that package (on a fresh 22.08.1install), the package installed is for 22.05.03 ... which is, er, the wrong version? Where do I find the headers for 22.08.1 ? Many thanks!
  • Create New...