Jump to content

lampra

  • Posts

    158
  • Joined

  • Last visited

Recent Profile Visitors

2191 profile views
  1. I am not sure as I do not follow the development at the moment. Before going for a full build, for a non-productive machine, I would start by editing the dts (there is an armbian-config tool for that). Then the driver might exist in the full firmware package (check it in the github rerpo). If not, then I would try to build the driver, or I would go for a full build as mentioned by Werner
  2. Probably missing the dts parts for wifi and/or driver. The dts parts and the driver are available here (last 2 commits) if you want to test it.
  3. Could you please share or point to this default environment, as I don't have the board available for tests at the moment?
  4. I am posting at this topic as per the download page instructions. If a new topic is needed, please split I want to try Armbian on an old Intel Atom Z3735F (Mele PCG03) with burned emmc, and I am wondering if the Generic Intel / AMD image will boot from usb. Z3735F uses 32b efi with 64b processor. With my previous tests, I was able to install only debian from the net image. The other images (installers) as well as Ubuntu installers could not identify & install 32bit efi. PS: It seems that (probably due to burned emmc) POST is failing at boot (even if I disable emmc from BIOS), so I can't boot without a monitor attached (though I could boot headless windows10 with the emmc). Any hint or pointers how to deal with this in order to boot linux without monitor?
  5. Is this using uwe5622 driver? If yes, then zero2 benefited from this commit
  6. Can you please test if the internal Bluetooth works with this kernel?
  7. Thank you, then it is only a mater of availability in the download page for the moment.
  8. To my understanding, these firmware files would need to be rebuilt based on the mainline TFA and uboot.
  9. My understanding from a user point of view is that if one needs to boot from media other than sd card, she/he needs to back up the uboot environment and then flash a firmware according to CPU and DDR (analog to the named trusted firmware supplementary files provided by openwrt here). SD card images (with different .dtb for v5 and v7) will probably have boot parameters set in boot.scr which a user may override. So I would propose, with the permission of @Pali, to include his two previous posts in the download page. Then, firmware files would be the only thing missing. As I see (please correct me if I am wrong) the default environment supports distroboot. Just one question; what is preventing armbian from being able to support distroboot (other than lack of resources) so that a user does not have to tweak the uboot environment in order to boot from sata?
  10. Here are the instructions from the download page (https://www.armbian.com/espressobin/): "Version 7 EspressoBIN (identifiable by sata power connection instead of molex) has ethernet ports in the reverse order. This can be fixed by passing the espressobin-v7.dtb in the boot script at /boot/boot.cmd" Does this still hold, or there is one uboot now that may identify different versions of the board and memory? "manual flashing to latest u-boot is mandatory! Download the right boot flash for your board: 512,1G,2G, number of RAM chips (if your board is older than a few months it has two RAM chips – one on each side of the PCB opposite to each other. Recent 1GB models have only one chip at the bottom) and appropriate memory speeds. You can obtain numbers from the current boot prompt. Also choose right memory: ddr3 are for V3-V5 EspressoBin’s (i.e. V5, 1g-2cs) and ddr4 images are for v7 EspressoBin’s. Insert ‘ddr3’ or ‘ddr4’ into the bubt command string. Copy this flash-image-ddr3/ddr4-MEM-RAM_CHIPS-CPU_DDR.bin to your FAT formatted USB key, plug it into USB3.0 port and execute from u-boot prompt:" Is this mandatory now? If yes, the download page does not redirect correctly "In case you experience instability reflash boot loader with lower CPU speed values!" Probably not relevant anymore? "Updated u-boot needs new default boot environment and new boot script (overwrite the one on your /boot media – needed only if you upgrade from < v5.59). This is what you need to copy/paste into u-boot prompt:" Probably not relevant anymore? The rest seem to be still relevant. "Boot priority with this script is: 1. USB, 2. SATA, 3. SD card, 4. eMMC If you manage to crash your SPI flash, get appropriate files and proceed with one of the rescue options: SATA, UART, UART console is broken on legacy kernel 4.14.y if you need USB2 port on your mPCI slot (for Bluetooth or 4G/LTE modems) you need to move both jumpers near to the USB2 port. Position for this function is: away from the port."
  11. @Heisath @ManoftheSeaAfter espressobin (v5 & v7) was added to supported targets, and by the time that it will hit the download page, It seems to me that the download page would need updated instructions at least for uboot
  12. Does wifi and Bluetooth work now on opi zero2?
  13. You could revisit this after the upgrade to Bullseye if needed. I had to do this after an upgrade on a running system. Turns out nothing scary happened.
  14. I just noticed that you seem to be on "Buster" not on "Bullseye", so the message is probably correct. You only upgraded the kernel
  15. Try root@cubietruck:~# apt-cache search armbian-bsp-cli-cubietruck armbian-bsp-cli-cubietruck - Tweaks for Armbian bullseye on cubietruck If it exists, you could try apt remove armbian-bsp-cli-cubietruck && apt install armbian-bsp-cli-cubietruck
×
×
  • Create New...