belfastraven

  • Content Count

    60
  • Joined

  • Last visited

About belfastraven

  • Rank
    Advanced Member

Recent Profile Visitors

1051 profile views
  1. @piter85, here's result of testing with official build, which uses 20.7, u-boot, I see: Bourd booted fine without all of those""Timeout poll on interrupt endpoint" spams, using nand-sata-install overwrote the spi_flash just fine ( as you can see :-) ) and without this error, which I imagine would have been fixed by your most recent patch anyway? Loading Environment from SPIFlash... Invalid bus 0 (err=-19) *** Warning - spi_flash_probe_bus_cs() failed, using default environment
  2. @Piter75, Just FYI, Booting a a Samsumg pm980 nvme from spi_flash with your new 20.10 u-boot (from your rockchip64-u-boot-v2020.10 branch ) works most of the time. This is a build made from playing with the desktop stuff, hirsute with gnome... It normally works--every once in a while it seems to not get past Booting using the fdt blob at 0x1f00000 not sure what is causing that yet, or the constant : Timeout poll on interrupt endpoint I did manually clear previous spi_flash and used nand-sata-install to inst
  3. @Igor, I am happy to help with documentation--I have been playing with the desktop branch (I'm now running hirsute with gnome on wayland on my pinebook pro--which I doubt you will be recommending to users, (but have tried various other combinations). I still don't understand whether this desktop/package flexibility is just for builders or will in someway available to people who would normally be downloading just images, or perhaps assembling pre-built images using native builds? Anyway, I am volunteering documentation assistance...
  4. Happy to help test any desktop (building pinebookpro. 5.91 dev build currently) I tried KDE with all boxes checked--unfortunately build kept failing at the very end because of failure to get gnu pg key for oibaf ppa. I'll try again without enabling whatever uses that ppa.... Is there a set of activities/checklist to try for the testing? I can build reasonably quickly and am actually using the PBP with SPI u-boot booting NVME, so I can do anything on an SD card without hurting anything....
  5. Re building different desktops: The capability to build various desktops through the build system is being worked on and tested now. From my initial look, it seems like many desktops including gnome, kde, cinnamon, lxde xfce and various others are being thought about for inclusion. I just started to try to play a bit with desktop (as opposed to master) branch of the github. Obviously, this is not released yet...
  6. Hmmm if your Ctrl-Alt-F2 prints a #, I believe it is somehow using the us (or perhaps ANSI) keyboard layout. That is what all of my other keyboards show by default--the PBP is my only ISO keyboard device. I'm certainly not an expert on any of this. If you want to build groovy, I believe you need to used EXPERT=yes on the ./compile.sh command. I have done a dev build, which builds kernel 5.9(.1 right now) . I did a console rather than a desktop build so I could play with installing a different desktop. Groovy runs very well so far for me. I am booting the NVME from SPI flash.
  7. When you speak about opening a terminal window, do you mean on the desktop? or do you mean opening a terminal console with CNTL-ALT-F(some-number). The mechanisms are different. For the CNTL-ALT-F(some-number) , if I set the /etc/default/keyboard file so that XDBMODEL="pc105" XDBLAYOUT="gb" XDBVARIANT="intl" I get the pound sign at shift-3. For the desktop console, it is controlled by whatever desktop manager you are using, I believe. So if in the desktop settings you have the pc105 UK keyboard selected, that should be working. If it works
  8. Are you trying to build a kind of "kiosk" application? XFCE is a much less resource intensive desktop than gnome and it actually has a kiosk mode-- you also have the capability of controlling the color of the desktop and what appears on a panel: see here: https://docs.xfce.org/xfce/xfconf/start. I am excited about the project that @Igor has mentioned; for now, I tend to build a "server" version of software and then install a desktop on the running system. I imagine that would not work for you even if you used clonezilla or a like program to copy the configured image, sinc
  9. Given the gsettings you are running, I assume you are using a GNOME desktop? if so can you try, gsettings set org.gnome.desktop.background picture-options 'none' gsettings set org.gnome.desktop.background primary-color '#000000' Assuming that since you know the user and you are using autologin ( as that won't change the background for the display manager) that will set a black background. If this is e.g. an xfce, lxde , etc. desktop, that will not work. there are other gsettings keys that you can set to eliminate de
  10. If anyone wants instructions for updating on debian/ubuntu as well as arch see: latest keyboard updater  with instructions for debian and arch.. Also, I have been running the pcm720 u-boot that @lanefu mentioned since the end of July, since it allows me to boot my nvme. I have played a bit with trying to work the patches/versions into the build system, but haven't been successful as of yet. . See here for the source https://github.com/pcm720/u-boot-build-scripts. There is one atf patch (which we may already have) and 4 u-boot p
  11. I can test, too. I have been running with (currently) an armbian dev build with 5.8.9 kernel on focal with a gnome desktop and pcm720's uboot on spi flash, botting an nvme. The only strangeness that I have been running across is that if I boot off of an SD card, rebooting without shutting down seems to boot the NVME. I haven't spent much time investigating, though--I was just so excited to be using armbian builds again..:-)
  12. Thanks for your response. I thought it that was so, but then, perhaps that test for it should be removed from main.sh. ? Otherwise, the build system will go ahead and download the sources anyway, even though it had said previously it would not., so the user documentation doesn't match what is happening. (this is not theoretical--it happened to me--twice before I figured out what was happening--:-) ) If you are using BUILD_ALL, what would now be considered the proper way to avoid having sources downloaded?.. If everyone who builds anything is just supposed t
  13. I've noticed that in order to be able to build offline, I need not only to specify OFFLINE_WORK=yes as per this documentation: OFFLINE_WORK ( yes | no ): skip downloading and updating sources as well as time and host check. Set to “yes” and you can collect packages without accessing the internet but also IGNORE_UPDATES=yes. Probably because of this is main.sh: # ignore updates help on building all images - for internal purposes if [[ $IGNORE_UPDATES != yes ]]; then display_alert "Downloading sources" "" "info" I don't see here in m
  14. @Igor, I've been playing with the Cubox builds and everything is working well. On WIndows, I am thinking about suggesting the built-in powershell tool Get-FIlehash for verification and explaining how to write the hash into a file to check it. gnupg, which installs gpg, and gpg4win, its windows graphic frontend with extra bells and whistles, work fine for authentication, and the command line use is the same as on linux. If we have any windows experts here who would like to weigh in, I'd love to here from them. Of course, if people are running WSL , they can just do th