CryBaby

  • Posts

    44
  • Joined

  • Last visited

Recent Profile Visitors

893 profile views

CryBaby's Achievements

  1. I also had problems with cifs (on OSMC which is debian based like armbian). Using sshfs works well though: share@ccb-adm035:/home/share /mnt/ccb_adm035 fuse.sshfs noauto,x-systemd.automount,_netdev,users,idmap=user,follow_symlinks,allow_other,reconnect 0 0 You need to have sshfs installed. Check you can ssh to the remote machine and ssh-copy-id to it so it doesn't need a password.
  2. The problem is a bug in the xserver, not your HDMI to VGA unit. The bug has been fixed but the fixed version has not yet reached the standard repos. Voka is offering a version of Armbian which includes the fix. That is a good option if you have not invested much effort in configuring your existing install.
  3. I just did a firmware update and got xorg 1.20.13 but it still does not work. Looks like we'll have a wait a bit longer for the next version. @Nico: if you Ctrl-Alt-F2 you will get a login prompt. Once logged in you can type sudo armbian-config and under System->Firmware do a full update. Try this once a week until things improve
  4. I have been following Quartz64_Development as I believe it will also mostly apply to RK3568 support. If I interepret it correctly almost everything needed will be in kernel 5.16 except VOP2 which is necessary for HDMI output. So a headless Armbian is probably feasible.
  5. A simple sudo apt install. I had that error before I installed it, after I get AIGLX: Screen 0 is not DRI2 capable. I assume this would be fixed if I installed the mali blob. I still have the original X.Org X Server 1.20.11, maybe you have a different one?
  6. I found I get a desktop if I install xserver-xorg-video-fbturbo. The performance is pretty poor though. Is this still the preferred option or has it been superceded?
  7. I just tried Armbian_21.08.1_Cubietruck_focal_current_5.10.60_xfce_desktop.img The desktop is still not working, just a black screen on HDMI. I posted the armbianmonitor output here if anyone wants to look at it. There's some lima errors. There's also some bluetooth errors. $ sudo bluetoothctl show Controller 8A:AB:7E:0F:6F:FB (public) Name: cubietruck Alias: cubietruck Class: 0x001c0000 Powered: yes Discoverable: no DiscoverableTimeout: 0x000000b4 Pairable: yes UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb) UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb) UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001) UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0535 Discovering: no Advertising Features: ActiveInstances: 0x00 SupportedInstances: 0x05 SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name So looks like the same old. I'm happy to try out any suggestions but without a desktop I've not much incentive to start researching again.
  8. Thank you balbes150, my P2 is running nicely with your image. I would like to get DVB running too but the modules don't seem to be included (my DVB tuner is listed by lsusb). So i'm trying to build the kernel myself. I am following https://docs.armbian.com/Developer-Guide_Build-Preparation/ using https://github.com/150balbes/build but it doesn't offer any rk3568 kernel options. What else should I be doing?
  9. Usually u-boot will pause briefly to allow you to interrupt it by hitting Enter or Ctrl-C (either on the console or serial terminal). You then get a command line. The boot order will be set in an 'environment variable' which you can view, edit and save. Useful commands are printenv, setenv, saveenv and help. The most interesting environment variable is bootcmd which you probably want to change to 'sdcard'. I think you are specifying a function here rather than a device so it will depend on what functions are available. I would not assume that there is a boot order by default. If not then an empty eMMC might just mean no boot. It might even mean no u-boot. I believe Station OS is a version of Android. If there is an app store maybe you can install an ssh server or terminal program from there. Alternatively, you may be able to get a shell using ADB from your PC.
  10. Perusing the wiki again I get the impression that booting from the SD card is not something they expect people to do. The instructions are for using it to upgrade the firmware, ie. overwrite the eMMC with a new OS. The images they provide may therefore not be bootable. On the other hand I just noticed an "SD Boot" option in their firmware upgrade tool. You might experiment with that, if you manage to download it.
  11. The wiki vaguely describes a procedure for installing Ubuntu, the images are provided here: http://en.t-firefly.com/doc/download/94.html My P2 arrived today. Unfortunately I am in another country entirely and will be for about a month, or longer if Covid has its way. So let us know how you get on with it.
  12. Looks like it has moved again: /sys/power/axp_pmu/ac on Armbian 21.08.0-trunk.77 Focal The old battery info is at /sys/power/axp_pmu/axp20x-battery-power-supply/power_supply/axp20x-battery "A foolish consistency is the hobgoblin of little minds."
  13. Nah, using brcmfmac43362-sdio.bin and brcmfmac43362-sdio.cubietech,cubietruck.txt from linux-firmware with no hcd gives a (non-functioning) controller on cold boot only. Adding in ap6210/bcm20710a1.hcd gives no controller. Also, none of the 54 hcd files from github match ap6210/bcm20710a1.hcd I don't know what to try next.