Jump to content

Jojo

Members
  • Posts

    34
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Jojo got a reaction from jiri in Odroid M1S Image Planned ?   
    @SteeManI partially agree with you. So far, that you say, that people like @Igormight have more important things to do, than to answer (apparent) n00b questions in forums and I also agree that it is highly important, that there are more volunteering people who try to contribute.
    But on the other hand I think, that the perspective of you and many other "higher" developers (not only at Armbian) shifts with the level of expertise. What I mean by that is, that when people like me want to start to contribute, we have very limited knowledge in many fields. So many things are mysterious and sometimes we don't even know what we should look after or what we should search for when problems occur.
    You are right, that many questions arise regularly and sometimes this is annoying and a reference to the documentation is totally appropriate! But I have the feeling, that particularly here at Armbian, the demands for a question to be posted is very high (compared to the knowledge that beginners come with). And it happens VERY often, that it feels like a slap in the face when I have the courage to ask something and I get told "please stfu, here's a link to the source code."
    And I can tell you, that it is exactly this behavior, that brought me to the point, where I thought "well, f**k it. I just wait for my problems to be solved by others, if my request for help to help myself is treated like a request to get my b**t whipped for free". I've felt this quite often here. But I am STILL here, because Armbian is important to me - not only as the OS of my choice, but also as a project that is worth to be supported! But you should also know, that the willingness to contribute (as far as a n00b like me can) will go down rapidly, when you get slapped often enough. And to complain, that people don't want to contribute after slapping them is not fair.
     
    After that said, there the main topic:
    I was able to build Armbian with vendor kernel and extensions. I did this by adding the corresponding options to the build command. In my case, my build command looked like this:
    ./compile.sh build BOARD=odroidm1s NO_HOST_RELEASE_CHECK=yes KERNEL_BTF=no BRANCH=vendor RELEASE=noble BUILD_DESKTOP=yes DESKTOP_ENVIRONMENT=gnome KERNEL_CONFIGURE=no BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers internet multimedia desktop_tools editors' ENABLE_EXTENSIONS="v4l2loopback-dkms,mesa-vpu"  
    First of all, I hope that this was the correct way to do it. Because my other option would have been to modify the board config file. But that didn't feel right...
     
    The problem now is, that the board just does not boot. After waiting some time the board falls back to the system I have installed on eMMC. Using another non-vendor system on SD card works.
    I have the feeling that there is something wrong between u-boot and the vendor-image. Maybe the vendor kernel image expects petitboot and does not work with u-boot? Is there a way to proof that (without overriding u-boot with petitboot)?
    You see... n00b question AGAIN. But I try to come as far as possible on my own...
     
    Cheers and have a very nice and joyful xmas season!
     
  2. Like
    Jojo reacted to Werner in Odroid M1S Image Planned ?   
    Yes
     
    That's on us
  3. Like
    Jojo reacted to Werner in Odroid M1S Image Planned ?   
    Yes. In the past everything was added as patch. The problem was (and still is for other reasons) that some patches modifying a dt build on top of each other or stuff breaks. Now the dt can be edited directly and using git blame it is documented who edited what for whatever reason.
    Of course sometimes there is an almost perfect dt upstream that needs minor adjustments. Those can be perfectly fine done with a patch.
    Also both patches and our dt files only stay for as long as there is no proper equivalent upstream. Once everything is in mainline they are no longer needed.
  4. Like
    Jojo got a reaction from Leonardo Martins Marques in Odroid M1S Image Planned ?   
    Hey guys,
     
    I just wanted to mention, that I have not forgotten this topic .
     
    I just have currently no time to drive this further because of real-life stuff going. Additionally I currently have no hardware in spare which i could perform the tests on. So either you guys wait for a non-specified time or try something on your own.
     
    So long... Cheers
  5. Like
    Jojo got a reaction from manuti in Odroid M1S Image Planned ?   
    Hey guys,
     
    I just wanted to mention, that I have not forgotten this topic .
     
    I just have currently no time to drive this further because of real-life stuff going. Additionally I currently have no hardware in spare which i could perform the tests on. So either you guys wait for a non-specified time or try something on your own.
     
    So long... Cheers
  6. Like
    Jojo got a reaction from lanefu in Odroid M1S Image Planned ?   
    Hey guys,
     
    I just wanted to mention, that I have not forgotten this topic .
     
    I just have currently no time to drive this further because of real-life stuff going. Additionally I currently have no hardware in spare which i could perform the tests on. So either you guys wait for a non-specified time or try something on your own.
     
    So long... Cheers
  7. Like
    Jojo got a reaction from MaxT in Odroid M1S Image Planned ?   
    Hi,
    I'd also like to see armbian running on my M1S.
    It arrived today and honestly I ordered it in the hope to see it being supported one day.
    Afaik none of the devs currently own an M1S yet, what makes development somewhat more difficult. So I would be happy to contribute by providing my M1S for tests.
    So if anyone without an own M1S can provide an Armbian image with modified device tree and so on I will try to perform the desired tests.
     
    Cheers and thank you!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines