Jump to content

xXx

Members
  • Posts

    62
  • Joined

  • Last visited

Recent Profile Visitors

2881 profile views
  1. @everyone A friend got this box: Beelink GT1 Ultimate GPU: ARM Mali-T820MP3 System: Android 7.1 CPU: Amlogic S912 Core: 2.0GHz,Octa Core RAM: 3G RAM DDR4 ROM: 32G ROM 5G WiFi: Yes Bluetooth: Bluetooth4.0 Power Supply: External 5V Interface: DC 5V,HDMI,LAN,Micro SD Card Slot,SPDIF,USB2.0 What image is best for this box? Thanks!
  2. So for the planned IceWM variant, which is all (and only) fresh packages from debian stretch arm64, what version of the packages is better to use? 5.27 or 5.34?
  3. @balbes150 Hello! If i type in my terminal: dpkg -l | grep aml i get: aml-amremote-905 5.37 arm64 IR amremote S905 aml-kodi-905 5.37 arm64 aml-kodi-905 aml-mali-905 5.37 arm64 lib mali S905 firmware-aml 5.37 arm64 Linux firmware-aml linux-dtb-amlogics905x 5.37 arm64 Linux DTB, version 3.14.29 linux-image-amlogics905x 5.37 arm64 Linux kernel, version 3.14.29 linux-u-boot-amlogic-s905x-default 5.37 arm64 Uboot loader 2015.01 linux-xenial-root-amlogic-s905x 5.37 arm64 Armbian tweaks for xenial on amlogic-s905x (default branch) but in yandex drive i find only 5.27 5.34 and next. Is this a typo in yandex disk? If not, where can i find these 5.37 versioned packages? Thanks.
  4. @balbes150 Hi again. I manage to have everything working in my bootstrapped USB ROOTFS except: Video resolution shows only part of the image. xorg log says 1920x1080 virtual size glxgears gives ~250.000 FPS glxinfo says "direct rendering yes" Any tips on how to solve this, or what am i doing wrong? All packages i have installed came from debian stretch arm64 official repositories (no backports though), and some packages from your debs in yandex deb directory (kernel and firmwares). No packages at all from armbian repos are installed (maybe i'm missing something from there?) If this resolution problem gets solved i'll start tweaking IceWM to the last detail, and then i'll start creating an auto-build script according to the notes i have taken so far. Thanks.
  5. If you are talking about official repositories, the sources has to be send to package maintainers, audited and approved and if all goes well, it will be added to official repositories at some point. If you are talking for you own repository, there is a method: dpkg-scanpackages packagedir | gzip > packagedir/Packages.gz for local directory, but this can be a network directory too (apache,nginx,lighttpd etc). and supplement your sources.list with the url (or file://packagedir in case of local offline repo). By the way... the debootsrap method works fine, and the project will be much easier than i thought I already have a minimal USB thumb with only a base debian stretch system that is 353MB (this cannot be the final projec, but i think will fit in 1GB USB/SD). I will soon have something to show, and an automated script at a bit later point.
  6. Thanks for the update. i'll destroy the USB with mate 2018 and i will start using it for my IceWM idea.
  7. I forgot to mention 3 things about my previous post with IceWM livecd: 1) The live cd has the following users:passwords user:user root:root 2) No drivers for virtualbox etc are included, so virtualbox etc will be sluggish with this livecd. Booting in a real system via a fast USB thumb should be lightning fast. 3) The dpkg database is deleted before squashfs-ing (to save space) so... in order to install any software via apt-get will need an apt-get update first. ################################ IDEA #################################### i'll start scratching my head about the idea of making a pure/light/fast/goodlooking image of armbian stretch with IceWM for my box (and maybe others if that goes well) in the next days. The idea is to start using debootstrap, and then create an image from the bootstrapped directory (only time will tell if this is even possible). ################################ IDEA ####################################
  8. @balbes150 INFO: I made a USB thumb with Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20180116.img. I copied and renamed /boot/dtb/gxbb_p200_2G_100M as /boot/dtb.img (looks the same as kszaq to me and worked ok). I booted the USB (NOTE: Only the back USB port can boot in this BOX [MiniM8S] the one that is between DC/IN and HDMI). Everything worked at first boot (changing pass etc). I edited /etc/modules (i put wifi_dummy in there) and instructed a reboot from mate menu. Reboot hanged for more than 3 minutes so i did a POWER CYCLE (forced reboot). Next boot was OK, i did wifi connection, all OK. Sound via HDMI OK. Bluetooth NO ADAPTER (as always with this box). Video playback windowed with mpv ACCEPTABLE. Video playback fullscreen with mpv NOT GOOD but no HANGUPS or anything, just UNWATCHABLE. I did: sudo apt-get update (ALL OK) sudo apt-get upgrade (i had to do apt-get -f install but after that OK) sudo apt-get upgrade (ALL OK) sudo apt-get dist-upgrade (NO HELD PACKAGES = ALL OK) sudo apt-get install dmz-cursor-theme (ALL OK) sudo apt-get clean (ALL OK) logout and login again via mate menu (ALL OK) sudo armbian-config (did some configurations as tzdata and keyboard-configuration OK -- but motd messages was NOT OK -- infinite LOOP and NO CHANGES SAVED ever) logout and login again (ALL OK) sudo armbian-config (change hosname) (ALL OK) logout and login again (ALL OK) shutdown via mate menus (took more than 4 minutes, i lost focus at some point but finally the box did shutdown) (NOT OK) The messages that kept shutdown back was systemd messages about "SAVING AUDIO" and "C3 STATE" Right now i have these RED MESSAGES in sudo dmesg --ctime | egrep -i '(error|fail|abort|timeout)': Now the box is back again and will remain UP for some more time. The image in the USB will be kept for 1-2 days in case you want any more info from me and my MiniM8S box. That's about all.
  9. Here is a screenshot from my MiniM8S desktop right now.
  10. Yes, i am . And i'm creating a livecd-only debian "distro" with only a minimal set of applications, and IceWM as a window manager, for use as a thinclient. The uploaded cd is x86_64 only at the link below, but fully functional (and good looking also), and the script can also produce x86_32 images of lenny|squeeze|wheezy|stretch (and x86_64 ofcourse) with some manual troubleshooting (like missing packages in ancient debian releases). You can test it from here https://mega.nz/#F!rdFxwKKQ!_9aRWe2rfZaMt7LNQK_R1Q I'm giving you this link, because i was thinking to do the same with armbian for my MiniM8S box, but i don't know how to start. The livecd is generated by a script that i am developing lately. The script needs debian as host system and deboostrap squashfs xorriso and some modifications. If you try the livecd, and you like the look and feel of it, i can give you the script (lh-icewm.sh) to see if you can implement any of it to your images or help me to modify the script so it will be able to produce an armbian image for flashing to our boxes. This could become the ultimate IceWM armbian distro of all times . About your images now: 1) YES... i had the same reboot/shutdown issue (that i forgot to mention) with non-testing images myself, up to the point i changed the dtb with the kszaq one. After that all issues disappeared. 2) YES... i will try the latest testing images soon, and let you know. Thanks again.
  11. @balbes150 Hello again, after a very long time of inactivity of me. I'm writing to inform you about this small problem: No matters what image i tried to use, and most of the dtb's that was used to work in the past for me, i always had problems with wifi and system misbehavior. in general. Right now i'm using the dtb from https://kszaq.libreelec.tv/s905/8.2/device_trees/S905/gxbb_p200_2G_100M.dtb and all the problems seem to have gone for ever. My box is MiniM8S (not II or Pro) as always. I'm writing this message from my MiniM8S with "Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_icewm_20171226.img.xz" and using the previously mentioned dtb from kszaq and everything is fine. Thanks for the IceWM images, as i am a great fan of this window manager, and also IceWM makes this boxes fly literally. The problems with the dtb's coming with your images was: 1) No wifi at all (after "sudo modprobe wifi_dummy" [and before ofcourse]) 2) Wifi disconnections or no internet at all, although i have had IP DNS and GATEWAY correctly. 3) Very slow and unresponsive system in general. 4) System hangs after sudo modprobe dhd (only mouse movement and nothing else alive in the system). So... maybe something is wrong OR missing with the provided dtb's in your images? Thanks again for all your efforts.
  12. Thanks for the advice, but... 1) My box is not moving at all, so i have no need for wicd ( i trust good old /etc/network/interfaces much better ). 2) I wanted to be as close to balbes150 vanilla image ( but i had many problems so i was forced to change some things ) as possible, in order to give accurate results. Thanks again!
  13. I can confirm that kodi works as expected. All kodi functions worked for me ( scanning my samba shares, adding my videos to collection, etc ) Playing 1080p and 720p videos was a pleasant experience. The only thing ( unrelated to kodi ) is that my wifi died after 10-15 minutes again, and kodi started buffering for ever. Since then the system become extremely laggy and unresponsive and took me about 10 minutes to get out of kodi without unplugging the power cord. Eventually it did manage to get out of kodi, and the system is almost usable again, but with one core to be 100% and no internet/network access again. So the biggest problem in my system seems to be wifi stability. The image as i said before is the same Armbian_5.27_S9xxx_Ubuntu_xenial_3.14.29_mate_KODI_20170623.img and the box is MiniM8S. Anyone else had better luck with this image?
  14. This image was EXTREMELY unstable for my box. I changed only 6 thigs so far: 1) Added the "wifi_dummy" in /etc/modules 2) Removed tsched=0 from /etc/pulse/default.pa 3) Stopped NetworkManager service ( sudo service NetworkManager stop) 4) Removed network-manager from startup to save me ~6 minutes delay ( update-rc.d network-manager remove ) 5) Added my wifi details in /etc/network/interfaces: source /etc/network/interfaces.d/* # Local loopback auto lo iface lo inet loopback auto wlan0 iface wlan0 inet dhcp wpa-ssid MyAccesPointName wpa-psk mycopmplexpassword 6) removed nodm and added lightdm Right now the system seems stable and the one core was 100% is gone ( all cores are in sane percentages ) Now lets test some HD videos with kodi :-)
  15. found a solution with the wifi issues: i made /etc/network/interfaces like this: user@amlogic:~$ cat /etc/network/interfaces source /etc/network/interfaces.d/* # Local loopback auto lo iface lo inet loopback user@amlogic:~$ Now is connecting without problems... In fact i'm writing this message straight from the box. I'm in the 6th forced reboot by unplugging the power adapter.
×
×
  • Create New...