Hi,
Where you able to start kodi with these images? Not matter what I try I can’t seem to be able to do it.
Thanks!
I didn’t try it. I ended up with CoreELEC for now. It allows to easily run docker so it’s kind of workaround for me.
Here I was thinking that I could get it working this time… Got keep trying.
Thanks though.
I used the Khadas/fenix One-stop script to make an image, but WiFi Doesn’t work…
Can someone PLEASE help me get WiFi Working in mainline for the Khadas VIM2 Max (ARM SBC); it worked in legacy 3.14 but seemingly regressed in functionality in everything after especially in 5.0.4? I feel like I have all the pieces, but I’m not technical enough to put them all together: http://dpaste.com/32A5AW3
I’d specifically like Khadas VIM2 Max running Debian Stretch with Kernel 5.0.4 or later working and all hardware working appropriately, I also noticed issue with bluetooth but one issue at a time.
[DRIVERS]
It SHOULD be supported in mainline from…
https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts <= LINUS TORVALDS Master Branch
compatible = “khadas,vim2”, “amlogic,s912”, “amlogic,meson-gxm”;
model = “Khadas VIM2”;
http://linux-meson.com/doku.php?id=hardware
“ Khadas VIM2 (arch/arm64/boot/dts/amlogic/meson-gxm-khadas-vim2.dts) “
And from https://www.kernel.org/doc/Documentation/devicetree/bindings/arm/amlogic.txt
- “khadas,vim2” (Meson gxm s912)
[FIRMWARE]
I made a patch for the kernel a long time ago, the problem is the lack of new firmware (the old ones can not work with the new kernel). I asked @numbqq , he promised to find out in AML.
1 Like
Hello Oleg,
Amlogic doesn’t have such firmware, and we have asked the vendor as well, but we don’t have lucky to get such firmware…
Hello Nick.
This is a bad thing. Then you will have to think about porting the brcm driver, it may take a long time.
1 Like
THANK YOU, THANK YOU, THANK YOU so much for this response, this at least gives me some insight and understand as to the why. I also want to express my appreciation and gratitude for all your contributions and help supplied. This is most appreciated. Please continue to keep up the good work. This is exciting that since the problem can be identified, it can be addressed. Hopefully we’ll eventually again be able to use all the hardware on our devices, specifically WiFi. Thanks Again For All that you contribute and do. Kudos 
I noticed with One-stop script https://github.com/khadas/fenix that Debian doesn’t report Processor Information correct or as accurate as Ubuntu. Are All Eight Cores (2 Die) being used optimally ? I used the tools: screenfetch and inxi to determine this with an Official Khadas Ubuntu image: https://dl.khadas.com/Firmware/VIM2/Ubuntu/EMMC/VIM2_Ubuntu-xfce-bionic_Linux-4.9_arm64_EMMC_V20190319.7z and the described self made Debian image made using the One-stop script. Perhaps @numbqq can address this?
@numbqq, I LOVE 
your script, it was just what I was looking for a while back when I wanted to use Debian without Kodi or anything extra. It is highly well executed and organized. Thank you for making it. It’s been most helpful. I greatly appreciate it as I’m sure others do too. This is a terrific tool. And I look forward to the improvements and updates to come. Great Implementation. Best thing since sliced bread 
I just can’t express how wonderful this thing is. 
With all that said, can you make it run on “Linux Mint” (Ubuntu Core, and similar)? Cause as of now, I’m having to use a Docker session to build with.
1 Like
I don’t have Linux Mint environment to test, maybe can’t work well. My host PC is still Ubuntu 16.04, so I use docker to build image all the time, I think it’s a good choice to build on other platform with docker.
Please see my Problems with Armbian Images @ Armbian + KODI (Ubuntu\Debian) for SD & USB & eMMC
Please see: WiFi Doesn't Work in Mainline · Issue #33 · khadas/fenix · GitHub
They seem to have got it working in Manjaro
@CyberManifest the BCM4359 chip is used in both PCIe and SDIO implementations. The mainline kernel bcmhd driver supports the PCIe implementation only. The Manjaro forum posts appear to be blacklisting the “wl” (older, not in-kernel Broadcom) river to allow the in-kernel b43 driver to work, but neither wl or b43 supports SDIO cards so this will be a user getting a PCIe device to work.
3 Likes
@chewitt thank you for the information and explanation, it helps me understand better about what is going on. Although, this causes me concern, it makes me feel WiFi will never work on the Khadas VIM2 beyond kernel 4.9 (especially, given Khadas has new versions of the VIM2 board out now)(my board will fade into obscurity 
) 
. I guess this is the state on Khadas’s main Ubuntu build
( https://dl.khadas.com/Firmware/VIM2/Ubuntu/EMMC/VIM2_Ubuntu-xfce-bionic_Linux-4.9_arm64_EMMC_V20190319.7z ) as well. So the Khadas VIM2 Max (v1.2) with AP6359SA WiFi seems to peek at Kernel 4.9 
I’m experiencing sporadic disconnects from Bluetooth on Khadas VIM2 Max (v1.2) using https://github.com/khadas/fenix for all kernels 3.14, 4.9, and 5.0.4
My Bluetooth Keyboard is sometimes unresponsive and seems unpaired after reboot, my Bluetooth mouse is often unresponsive and is ALWAYS unresponsive after reboot (even showing paired, like data isn’t transferring), my Bluetooth Wireless Earbuds glitch in and out on audio playback, I can’t listen to a song without it being broken apart into increments of a few seconds (making the experience distorted). I’ve tried everything I know to troubleshoot this. I’ve disabled/re-enabled Bluetooth, I’ve removed and re-added the devices, I’ve made sure trust device was enabled. This is all a bit frustrating and concerning because I had intended to use the Khadas VIM2 Max for portability, to take with me on the road, and use Bluetooth devices, for input, to free up USB Ports for other peripherals. Can someone please advise or address this issue? I can’t remember if I’m affected by this issue on Khadas’s official Ubuntu images, so I’m going to go try and test it out now… I look forward to any responses. Thank You 
UPDATE: Yeah, it’s WORSE on the Ubuntu image, the “Setup New Device…” Bluetooth window crashes if “Devices…” Bluetooth window doesn’t and the “Devices…” Bluetooth window crashes if the “Setup New Device…” Bluetooth window doesn’t. If somehow you’re magically able to add / pair a device there is still connectivity disruptions; testing my Bluetooth earbuds again proved to have distorted and disrupted audio/music. only lasting 2 to 3 seconds. 
Hardware wise this is turning out to be the worst investment I’ve ever made in a SBC (What’s the point in 8 cores and more RAM, if everything else breaks and the software feels sluggish and cobbled together?); I may have to go back to my Overclocked Raspberry Pi 3 B+ running on a 32 bit OS 
It may be worth noting that I see errors on boot in regard to what appears to be the audio mixer / hardware. Like address or register or I/O errors or something. I’m too disheartened to dissect the details at the moment. Perhaps later if I can muster up enough ambition. (I may even take a picture with the camera on boot, so I can share and convey a more elaborate articulation of what I’m encountering.) These errors were present from the stock image so I can’t imagine Khadas not knowing about them. (If I’m not mistaken these errors went away in the 5.0.4 kernel on custom build images; but then WiFi breaks, guess you can’t gain something with the board without sacrificing something else )
UPDATE 2: Sharing the Photos: https://photos.app.goo.gl/B3TTtQKTudzQE2bNA appears to be hdmitx related so I guess it’s the audio sync with the HDMI monitor
UPDATE 3: Sharing Video of Experience: https://youtu.be/ugg0yLnMQrc
Hey @numbqq In your One-stop script… while building…
What is this all about: http://dpaste.com/0KQCQV6 ? What are the warnings and mentions of “Non-Trusted” and “not supported”?
Specifically: Non-Trusted Firmware BL3-3: offset=0x44000, size=0xA26F8 &&
drivers/net/wireless/bcmdhd/Kconfig:50:warning: defaults for choice values not supported
When I use the newly built image, I encounter the following after issuing the first command of ‘sudo apt update && sudo apt upgrade && sudo apt full-upgrade && sudo apt dist-upgrae’:
http://dpaste.com/1ZDHX4S
and it resizes my screen off the edges until I reboot.
It doesn’t matter.
Yes, when you update the system, some updates will trigger to recreate the initrd and some scripts of change the resolution will be executed, so it may broke the resolution, you will have to reboot the system…
1 Like