Jump to content

giri@nwrk.biz

Members
  • Posts

    63
  • Joined

  • Last visited

Posts posted by giri@nwrk.biz

  1. On 2/7/2021 at 7:47 PM, guybrushthreepwood said:

    I can confirm that allwinner_tvout_manipulator works like a charm. I've downloaded the latest version, built it and solved the overlay issue. Thanks to yam1 for pointing it out! This should be the thread on the forum where it was mentioned with a detailed usage explanation too.

    Unfortunately, I can also confirm that the resolution can't be changed by just editing disp_mode in /boot/armbianEnv.txt because, no matter what value I input there, I get no changes at all nor the .fex approach which was valid for the older kernels applies (but I knew that since the opening post of this thread). I need to go deeper on that.

     

    @jernej

     

    Yes, you're completely right and this was the reason why I've written I was just playing. Bearing in mind what you've already told me in the previous posts, this is the fartest thing from an enjoyable Kodi experience and unfortunately I know that. Still a lot to do...

    'Just' a question... You've talked about the heavy need for patching, both on kernel side and on the sources for Kodi and ffmpeg and this has already been done for LibreELEC: does this mean that digging on the forum there I could scour some hints? I'm not asking for the links to the threads, just if it is actually the right place to search. If, instead, the answers are inside the sources for LibreELEC, then it is definitively beyond my knowledge unfortunately.

     

    The tool envolved from here:

     

    forum.armbian.com/topic/3837-psa-orange-pi-zero-expansion-board-tv-out-not-working-solution/

  2. Polluting a Linux Distro Release with foreign packages is always a very very bad idea. It may lead to unforeseen library upgrades which may break  library ABIs and also may completely mess up your installation. This is one of the reasons why Debian freezes package versions on a per release basis. The Debian model is extremely conservative, but it works. My servers are up and running since Wheezy and upgrades worked flawlessly.

    BTW: this package sideloading done by the armbian repos got me in trouble two or three times (quite some time ago). By the time this really pissed me off, so I switched hardware and moved to a proper distro.

    Nevertheless, if you really want to pull a package from a foreign release here is how to do the safest way:

    Set default release by creating following file:

    $ nano /etc/apt/apt.conf.d/10defaultRelease

    Add this line and save:

    APT::Default-Release "stretch";

    Now add repo to pull the package from by editing:

    $ nano /etc/apt/sources.list

    Add following line and save:

    deb http://ftp.debian.org/debian/ buster main contrib non-free

    Now update package list and install:
     

    $ sudo apt update
    $ sudo apt install proftpd-basic -t buster


    PS: I have no clue about the current state, just stumbled across this thread and totally get the point of some others in here.

  3. 2 hours ago, dony71 said:

     

    I compile devmem2 but cannot write to register. It shows register value still the same

    I have Banana Pi M2+ which has allwinner H3

     

    root@bananapim2plus:~/Download/devmem# devmem2 0x01E00130 w 0x00140028
    /dev/mem opened.
    Memory mapped at address 0xb6fe2000.
    Value at address 0x1E00130 (0xb6fe2130): 0xEBD771BF
    Written 0x140028; readback 0xEBD771BF
     

    Try to use following tool: https://projects.nwrk.biz/projects/allwinner-tvout

  4. On 7/1/2018 at 12:58 PM, Brun0 said:

    Now I just need to learn how to run the tvout command through rc.local But that's just a matter of getting familiar with the linux syntax. I would appreciate help with this.

     

    The rc.local script is a simple bash script which is executed after boot. Just open it with an editor and paste the tvout command that fixed your resulution in there.

    Should work somehow like this:

     

    First copy tvout to /usr/local/bin, so it is in your PATH:

    $ sudo cp /path/to/tvout /usr/local/bin

     

    Now edit rc.local:

    $ sudo nano /etc/rc.local

     

    Should look something like this:

    #! /bin/bash
    
    tvout -m -x55 -y10
    On 7/1/2018 at 12:58 PM, Brun0 said:

    Unfortunately, in the Armbian provided in the RetrOrangePi image I had the same problem of the quotes below:

    For RetrOrangePi related problems you should contact their froum/devs. They seem to have my tvout program included in their image and labeled overscanning issues fixed within their release notes, so I guess they know how to handle it.

  5. On 10/14/2017 at 7:25 PM, Igor said:


    No.

     

    FriendlyARM produces nice boards but their software support is very basic. Some would simply say - it sucks. They use the kernel from chip maker which never received any fix or update. It's a common "feature" of most board makers since they usually can't allocate/afford to provide good (Linux = community-based) software on their own. It costs much more than designing a hardware. Armbian project was started because there is a need. A need to have a good, much better Linux on those boards than board makers can provide. (initially, there was a personal need only for one particular board)

     

    In Allwinner community I have to mention a group/project Linux- sunxi who is focused mostly on low-level drivers and mainlining. Armbian is somehow mixed with this group since we do similar stuff but our focus goes from kernel drivers to userspace. Our output is a clean Debian like Linux distribution and powerful tools to make it. The result is on a much higher level than anything from board makers whatever they name it: Raspbian, Ubuntu Core, ... and even something provided from mainstream distributions. That latter is anyway barely existing.

     

    Bottom line. You are wasting time using their images. They have to make them to sell boards which apparently can run "Debian" "Ubuntu" or whatever but after that ... they move to new design. Community/we support boards for years. For example, we still support Cubietruck, which is already around for 4 years and H3 chip will surely be supported many many years. It's popular. Modern kernel (4.13.x) is getting on those boards which means another big jump forward. Board makers are not much present in this game.

     

    I guess he ment the tool pointed out by @RagnerBG:

     

    Yes this tool should be compatible with any kernel version, because it is directly mapping and manipulating hardware registers responsible for the composite video output. This is more a hack, but it works.

  6. On 12.10.2017 at 9:48 PM, zador.blood.stained said:

    If you patch the kernel (throwing away the default 8192cu and adding a better one) and open a pull request it should be accepted without problems.

     

    Little Update:
    I replaced the kernel driver with the one from https://github.com/dz0ny/rt8192cu (->the one installed by the buid script) and found out, that this seems to be the faulty one! (Installed to /lib/modules/$VER-$LINUXFAMILY/kernel/net/wireless/ by default with the help of extras/rtl8192cu.sh, loaded at boot)! The stock driver from the linux-sunxi kernel (drivers/net/wireless/rtl8192cu) works without problems (Installed to /lib/modules/$VER-$LINUXFAMILY/kernel/drivers/net/wireless/ by default, not loaded at boot).

     

    I should mention that I do have a internal wireless module.

  7. 20 hours ago, zador.blood.stained said:

    Any error or error-looking messages earlier?

     

    I started a custom desktop build with a smaller set of packages so I do not have to scroll through the whole history.

     

    Here is the error:

    Preparing to unpack .../libmali-sunxi-r3p0_1.0-1~armbian5.31+1_armhf.deb ... 
    Mali binary driver can be used only on sunxi hardware 
    dpkg: error processing archive /var/cache/apt/archives/libmali-sunxi-r3p0_1.0-1~armbian5.31+1_armhf.deb (--unpack):  
      subprocess new pre-installation script returned error 
    exit status 1 

    Seems like the package checks the hardware during install...

    Workaround could be to fetch the deb and manually unpack it with dpkg -x, I am not happy with that approach though.

  8. 1 hour ago, zador.blood.stained said:

    In preinst or later? No error code? Did you modify /etc/armbian-release in any way?

    The process fails with following error:

     

    Processing triggers for systemd (229-4ubuntu19) ... 
    Processing triggers for ureadahead (0.100.0-19) ...
    Errors were encountered while processing:  /var/cache/apt/archives/libmali-sunxi-r3p0_1.0-1~armbian5.31+1_armhf.deb 
    E: Sub-process /usr/bin/dpkg returned an error code (1)

     

  9. 2 minutes ago, zador.blood.stained said:

    Installing glshim for all applications doesn't really work - it doesn't provide full OpenGL implementation so i.e. web browsers and other heavy applications will crash with it, and it's no a good thing.

    It can (and should) be used with individual applications by adding the private directory to LD_LIBRARY_PATH (at the beginning), or by preloading a special library.

    Well this explains why parole stopped working with glshim. Thank you for pointing this out.

  10. 17 hours ago, zador.blood.stained said:

    If you patch the kernel (throwing away the default 8192cu and adding a better one) and open a pull request it should be accepted without problems.

    Ok I'll try to do that. But I am not sure if the default driver is faulty or if the problem is related to my hardware.

     

    17 hours ago, zador.blood.stained said:

    You need to either tweak their install conditions in packages/extras-buildpkgs/*.conf or add apt-get install ... commands to customize-image.sh, apt.armbian.com is configured at this point and existing packages should be pulled from it without issues.

     

    I tried it by simply adding the packages to userpatches/lib.config, and it seemed to work (except for the libmali-sunxi-r3p0, but apt didn't really tell me why. I will look into that and try your suggestion with the customize-image.sh script).

     

    There is one thing I recognized with the libglshim package. It installs the libraries to an 'lgshim' subdirectory but I think they should be installed to an 'mesa' subdirectory. I needed an symlink to get OpenGL based applications to work. But I am really impressed about the glshim performance :).

  11. Here you go (clonable git url): https://code.nwrk.biz/armbian-giri.git

    I tested everything I could test with an orangepizero and with the CSC topwise tablet.
    Some background information: I am trying to make a custom image for my tablet with different packages (matchbox environment for touch mode, pseudo desktop environment using lwm, idesk and some other packages for desktop mode), this is why I need an custom skel folder for some preconfigured settings and scripts.

     

    By the way, xdm can start a customized session with the help of an .xsession script in the users home directory.

     

    Oh and I recognized, there are two kernel modules for the 8192cu wireless adapter. By default the image loaded the wrong one on my topwise board. (I thought I should mention this and don't expect any support here.)

     

    Is it somehow possible to install packages from the apt.armbian.com repository with the build scripts? (I want to avoid cross compiling :D, Needed packages: libmali-sunxi-r3p0, libglshim)

     

    EDIT1: To fix this wireless module issue, "depmod -a" needs to be executed.

  12. I made some changes in the build scripts and wanted to ask if some of you may find them useful...

     

    • ability to use custom skel folder in /userpatches directory
    • support for xdm display manager (with graphical keyboard)
    • selectable display manager in expert mode (lightdm, xdm or nodm)

     

    Especially the custom skel folder gives much more flexability for modders to generate images for wip or scs boards. I am currently testing different configurations, all seems good so far.

    What do you think about these changes? Would a pull request make sense?

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines