• Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by belfastraven

  1. @Werner, I was perhaps not being clear enough in my suggestion. I don't have any experience with managing forum software, but was wondering if you could actually stop people from generating new topics in the bug system except by their using the bug reporting link. So If someone tires to create a new topic without going through the bug reporting link, they are directed to the community forum. or their post is automativally moved there. .... One could even add that that fact to the header.... It might actually come across as "friendlier" and probably would be less work for moderators, but, as I said, I don't know enough about the forum software to know if that is even possible...... Is Armbian still using the Invision Community software? IS the documentation for it available ? I'd be happy to look into further trying to automate things if it would help...
  2. Would it perhaps help to add the link to the bug reporting form to the heading for "Bug tracker - supported boards and images only" e.g. "Bug tracker for supported boards and images only- please use the bug reporting form found here for your initial posting. " and if the form is not filled out, just move the post to the "community supported" forum. Might that not make it easier for @Werner to moderate? It would certainly be "friendlier". Saying "invalid" and telling people that they may have "refused" to do something comes across as sounding a bit hostile--I think perhaps this is somewhat of caused by having different ways of expressing things in different languages. I think it is sometimes difficult to understand where to ask a question i you are just trying to ask for help in figuring something out, rather than reporting a bug. FWIW.
  3. @lukaszDid you try running glxinfo? I was just trying to indicate that there seems to be a difference in gnome settings in terms of what is reported for X rather than Wayland, but in both cases glxinfo shows panfrost as the extended renderer.
  4. @lukasz are you running on X11 For me , using self built hirsute/gnome (as opposed to just downloading) , using gnome on Wayland shows proper " mali T860 (Panfrost)" where gnome on Xorg shows " unknown, but in in either case glxinfo extended renderer section shows panfrost is used. Perhaps there is a bug in the settings program? Desktop sort of works for me on my 4k monitor (usbc dock-hdmi connection--same as on other distributions--the geometry is wrong and that also effects the display on the pinebook itself, but it has worked that way on any distribution I have tried) Natural scrolling setting seems to work on Wayland...
  5. @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
  6. @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 install the build and new spi flash. I've also noticed that when asked to update spi flash, it seems like the script will error if it doesn't find an spi_flash, but does not try to erase it if it has been written, andwill fail without any error message if a program already exists there... I apologize in advance if the spoiler is not hide-able--I can't seem to make that happen
  7. @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...
  8. 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....
  9. 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...
  10. 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 ./ 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. I installed an armbian uboot myself on on SPI flash ,, but I can see that armbian-config is being enabled to do that, too. Right now, I am running without sound, since I have the UART switch flipped, and am very much "over" removing 10 tiny screws every time I want to open the back. Someone on the Pine64 forum just posted that he had been able to use a spare internal uart and a micro usb-uart adapter to bring uart out without using the switch. I think THAT would be really advantageous:-)
  11. 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 elsewhere on the desktop, but not in the desktop terminal--could it have something to do with the particular font or character set used for the terminal? just FYI I am using groovy with a cinnamon desktop, I have an ISO keyboard, and I can indeed display the GBP
  12. 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: 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, since you may need different network parameters for each installation... but I thought I would mention it.
  13. 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 desktop icons, etc. Your best bet would be to google gsettings
  14. 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 There is one atf patch (which we may already have) and 4 u-boot patches. It is using u-boot 20.07, and a reasonably recent atf. I am rather confused about in which confs/patch directories I need to make the changes for current and dev builds. Is it possible for someone more up on the build system to take a look?
  15. 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..:-)
  16. Thanks for your response. I thought it that was so, but then, perhaps that test for it should be removed from ? 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 to use OFFLINE_WORK, I could try making the change in (pull request) , but as you know, I am not very good with shell scripts , and the build system isn't simple.
  17. 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 # 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 where is is checking for build-all..... so it seems that unless i specify IGNORE_UPDATES=yes, the system still downloads sources. No big problem, but I thought someone more familiar with how the scripts are supposed to work could look into it....
  18. @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 this with the linux commands anyway... I will see what I come up with over the weekend and THEN make the pull request. :-)
  19. @igor, I'm very glad you finished it--I don't think anyone wants me to mess around with the build system. I am back to working on the doc. I'm trying to determine the best tool to use on windows to shasum the xz file. certutil, e.g. expects the user to compare the hashes (not very friendly, I think) , Microsoft has a tool which I haven't tried yet, but will try tonight. Also, the doc still says builds for supported desktops are bionic and buster--wasn't sure that was still true. This is where I am currently, if anyone wants to look: If I check tomorrow, I'm assuming that I will see the newly generated dowload files? I will test again. P.S. I'm just trying to help. I am never offended about code, documentation changes, etc. I dual boot my desktop Ubuntu and Windows, but don't have a Mac, so when this is finalized, perhaps someone with a Mac can test....
  20. @Igor (and anyone else who wants to weigh in on the changes for xz compression) Could you take a look here at the section toward which you pointed me. This now will do compression first and then the shasum and gpg stuff. The shasum stuff is working (I tried it twice :-) ) I left "the "yes" option and the "no compression" options the way they were. I wasn't sure what everyone wanted --whether we should now use xz,sha,gpg by default, or what. I was not able to properly test the asc file generation because I am apparently not setting GPG_PASS properly. Perhaps I will figure that out tomorrow. I realize that I propabably should have given the branch the Atlassian assignment number. I'll do better next time....
  21. @Igor one last issue. When I downloaded the odroid 4c files ,(The .img.xz, .asc and .sha for bionic current desktop) I realized that no program that i can find will verify/validate the download or authenticity of the xz when the sha or asc generation is run against the uncompressed image , which seems to have been the case. Is it possible to generate the sha and asc file using the .img.xz files? If not, is it the intention the users should uncompress the xz files before running the checks? They obviously don't need to do that to write the file with Etcher or USBImager. Once I know what the intention is here, I can finish this piece of documentation. By the way, those builds seemed to be using 20.02. When I build locally, the build does seem to use 20.05. I found (grep is my friend) that I could specify xz on the COMPRESS_IMAGE build parameter but it does seem that the sha and asc files are generated from the .img file, not the compressed file....but shell scripts are not my strong point....
  22. Okay, thanks Igor, I am working on it and I did sign up for the Alsassian project management stuff.
  23. OK sorry--brain obviously not working. So am I understanding correctly that three files will need to be downloaded, the .img.xz, the .asc. and the .sha and that the new way of checking authentity and validating are gpg --verify "some-name".img.asc sha256sum --check "some-name".img.sha ? Also, the page I saw only mentioned etcher and not USBImager. SHould it also mention USBImager? Could someone point me to a download that has everything in place for the new system: I'd like to test what I am writing. I normally build things and when I tried to download some RockPro64 files I was getting Nginx errors for the SAH and ASC files. Any board with the new setup will do, its just for documentation testing purposes.... thanks.
  24. Igor, re your first request, I looked at the linked page, but didn't see anywhere there anything that indicates that the compressed file would be 7z. It says to use 7-zip or p7zip to uncompress the file, which should also work for xz files. Did you want to indicate that the compressed files would be .xz? Do you have a preference that a different tool be used?