Jump to content

Armbian Build for Nexbox A95X with AP6330.


ZuiMelanieForno

Recommended Posts

Hello @all.

 

I Have a Nexbox A95X With 2GB RAM and 16GB ROM.

Also it has a AP6330 Wifi Chip.

 

What I want to achive, is to have a running Server, as a private Git-Server.

I Used a Gog-Server on a Raspberry Zero W, but i wanted to see if I can get a Gitlab to run, and maybe more Server thingies like Webservers etc.

 

I used the Premade "Armbian_20.05.0_Arm-64_buster_current_5.6.0-rc4_desktop_20200320" and got it working.

I had to set in the "uEnv.txt" following DTB:

 

# aml s9xxx
FDT=/dtb/amlogic/meson-gxl-s905x-nexbox-a95x.dtb
APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

It Boots up and has no Wifi, and no Sound.

Fixes I tested and got Working:

sudo mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
sudo ln -s  /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt

The Upper Commands are  to get the Wifi working correctly. (^^^)

 

To enable the Sound I used this Script:

sudo /root/gx_sound.sh

And of cause it needs a Reboot to take effect.

 

What I could not activate is Bluetooth, and I still have no Hint or Clue, how to do that at all.

It is not mendatory for me, but would be nice to have.


I tried other DTB´s:

nope nothin:   meson-gxbb-nexbox-a95x.dtb -> No lifesigns after Boot Logo

nope nothin:   meson-gxl-s905x-hwacom-amazetv.dtb -> no Boot :(
booting Yeah: meson-gxl-s905x-khadas-vim.dtb -> looks like nexbox95x to me...
booting Yeah: meson-gxl-s905x-libretech-cc.dtb -> No Wifi displayed, No Bluetooth displayed etc.
booting Yeah: meson-gxl-s905x-nexbox-a95x.dtb -> Works good, but no Bluetooth Symbol is shown. Maybe it is supposed to be this way.
booting Yeah: meson-gxl-s905x-p212.dtb -> Shows always Bluetooth Symbol regardless of Driver.

 

I just got a Build done with the 150Balbes github Repo.

 

I had issues with setting up a Virtual Machine, that can do the Job.

 

Now I am stuck with VirtualBox, but no Vagrant. Messes more up then working for me.

I created a VM in VirtualBox manually, and after three Days fiddeling with Hyper-V and Vagrant and such Stuff, i got it working.

 

I had Build, that worked "arm-64 - Universal image ARM 64". It looks like the premade one i Mentioned above. (Exept the Video on the Desktop)

 

So I thought I could try a nother one, which maybe has the right DTB or Script, to fix the missing AP6330-Driver and Bluetooth, Infrared etc.

 

I have a Build-Error, when I used the "aml-s9xxx" in the Armbian-Build-Script-Tool.:

 

  CC [M]  drivers/staging/rtl8723bs/hal/HalBtc8723b1Ant.o
  LD [M]  drivers/hid/hid-wiimote.o
  AR      drivers/hid/built-in.a
  CC [M]  drivers/staging/rtl8723bs/hal/HalHWImg8723B_BB.o
  CC [M]  drivers/staging/rtl8723bs/hal/HalHWImg8723B_MAC.o
  CC [M]  drivers/staging/rtl8723bs/hal/HalHWImg8723B_RF.o
  CC [M]  drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.o
  CC [M]  drivers/staging/rtl8723bs/hal/HalPhyRf_8723B.o
  CC [M]  drivers/staging/rtl8723bs/os_dep/ioctl_linux.o
  CC [M]  drivers/staging/rtl8723bs/os_dep/mlme_linux.o
  CC [M]  drivers/staging/rtl8723bs/os_dep/osdep_service.o
  CC [M]  drivers/staging/rtl8723bs/os_dep/os_intfs.o
  CC [M]  drivers/staging/rtl8723bs/os_dep/recv_linux.o
  CC [M]  drivers/staging/rtl8723bs/os_dep/sdio_intf.o
  CC [M]  drivers/staging/rtl8723bs/os_dep/sdio_ops_linux.o
  CC [M]  drivers/staging/rtl8723bs/os_dep/xmit_linux.o
  CC [M]  drivers/staging/rtl8723bs/os_dep/wifi_regd.o
  LD [M]  drivers/staging/rtl8723bs/r8723bs.o
Makefile:1683: recipe for target 'drivers' failed
[ error ] ERROR in function compile_kernel [ compilation.sh:381 ]
[ error ] Kernel was not built [ @host ]
[ o.k. ] Process terminated 

 

So. I have no Clue, what is happening. At all... Never, Always whatever... ;)

 

My Linux Skills are Groundbreaking. So I always fall thrue a Hole...

 

But I have the Willpower and a Keyboard. I can do the DoubleClick but i dunno heave a Linux Background. I am a Microsoftie. :)

 

Please be patient with me, I am shy...

 

I want to solve the issues as good as Possible.

And if i can get it working to fix my own Builds, that would be nice.

I would emmidietly post here my Results. I swear By my Bricked TvBox...

 

My questions are these:

 

1. Where can Put a Shellscript to Trigger all the Fixes?

 1a. In a Premade Image,

 1b. or somewhere in a Buildprocess?

 

2. Did I missed the Bluetoothdriver mentioned in this Forum? I can assure i used the Search function, but i had no Search-Term.

 

3. If a want to add something while/before the Buildprocess? Where should I start?

 

4. Do I need a Soldering Iron to do the Debugging? I have two or three here, and a TTL-USB Adapter or a Arduino if needed to get the Serial out.

 4a. Am I right that that is the UART?

 

5. Is it possible to change the Wifi Driver before the Build? Instead of using the Script?

 5a. And if so, where should i start to Read about it, and where is the folder a have to put it in?

 5b. AndAnd does it needs a File to be created/adjusted to make it happen?

 

6. Did You enjoed the Questions 1 to 5? If so thank You for Your Time. :)

6a. Very Much

 6b. I mean it...

 

For some reason, I dont get the Full Picture how all things work together.

 

Maybe I missed a Tutorial?

 

I watched the YT Video of that bearded fella from the Netherlands.

You know that Guy with the Hat. ;)

 

If You Folks can help me with my Box of wunders, I would asure You I will live long and in prosper.

And that would be a Huge benefit to Your Carma-Account. At least two or three less reincarnation Cycles. ;)

I know that for a Fakt.

 

Funny greetings from Hamburg Germany.

 

Special Greetings to the Armbians and 150Balbes.

 

 

 

 

 

 

 

 

Link to comment
Share on other sites

1 hour ago, ZuiMelanieForno said:

1. Where can Put a Shellscript to Trigger all the Fixes?

 1a. In a Premade Image,

 1b. or somewhere in a Buildprocess?

 

2. Did I missed the Bluetoothdriver mentioned in this Forum? I can assure i used the Search function, but i had no Search-Term.

 

3. If a want to add something while/before the Buildprocess? Where should I start?

 

4. Do I need a Soldering Iron to do the Debugging? I have two or three here, and a TTL-USB Adapter or a Arduino if needed to get the Serial out.

 4a. Am I right that that is the UART?

 

5. Is it possible to change the Wifi Driver before the Build? Instead of using the Script?

 5a. And if so, where should i start to Read about it, and where is the folder a have to put it in?

 5b. AndAnd does it needs a File to be created/adjusted to make it happen?

 

6. Did You enjoed the Questions 1 to 5? If so thank You for Your Time. :)

6a. Very Much

 6b. I mean it...

https://docs.armbian.com/Developer-Guide_User-Configurations/

Link to comment
Share on other sites

Thank You Mr./Mrs./Div. balbes150.

 

I am Honored to get a direct Line to the "Builder".

 

I already have 3 Tabs in my Browser opened, with the Documentation.

The nonfunctional Pointer in my Database named Brain (or was it Brian?),

jumped to a wrong Heap address, where the Select-Case-Statements are all the same: Case Whaaa == '???' :)

 

Ok. I like making Jokes. But I can take it seriously, if I want to...

And back in the Days, when Linus Trovalds was invented, I already had read Articles an the Amiga Newspapers,

and there where only the Bulletinboards. But who had back then a Modem?

So Linux invented Linus, uups it was the other Way arround. Silly me...

 

I really have issues to understand where to do Things in Linux/Debilian uuups Debian...

Like me sad, I is from the Darkside, Windows his named. (Imagine it in a Yoda-Voice)

 

I would assume that according to this Section on the Documentation for Armbian-Build.

https://github.com/150balbes/Build-Armbian#build-tools-overview

I would have to do something in the "userpatches -> lib.config".

 

But what?

Where should I start reading about Linux Kernel Development, because I already was redirected to Linus Trovalds Repository.

It was my first Time. So exciting! :blink:

 

If I want to exchange the used brcm-Driver-Blob, should I try to use the Commands mv and ln in the "lib.config"?

 

My first try was to create a Shellscript. (My wunderfully choosen Name: "armbian_ap6330_patch_switch.sh")

#!/bin/bash

mv /lib/firmware/brcm/brcmfmac4330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt.old
ln -s  /lib/firmware/brcm/brcmfmac-ap6330-sdio.txt /lib/firmware/brcm/brcmfmac4330-sdio.txt

You Experts already see the User-Rights and Chmodie-Thingies would not apply here, to get my Script running.

 

I Just copied this Script into the Root folder of the SD-Card, and it is shown in the "/boot"-Folder

I thought, if the Wifi (armbian_first_run.txt) credentials can be put here, maybe I can put something additional here.

The Credentials are working, even the Wifi was not working and after the Broadcom-AP6330-Patch and the Reboot.

Wunderfully executed this Credential System.

 

Remember I came from tha Days of "autoexec.bat". ;)

 

And till I found out I have to remove the CarriageReturns out of the Script, 2 hours passed.

Windows-Users are not allowed to carry it to the Returns. GotIt :thumbup:

You can only feed the Lions, uuups Lines I ment.

 

So I undersand somehow the "sudo" thing. For Sure if not i could not execute the "./compile.sh".

 

But it seems someone needs to take my Hand, and show me the Linux-Compiler-World.

 

I don´t want to occupy "Your Majesty Balbes", you should be working with the Experts, not a Newbee like me. :)

But if You can find me a Mentor, I would obbey (mostly not, hihi..).

 

And a Sidenote:

I tried to open a DTB file and see how it is Composed.

So the dtB stands for Binary.

 

Slowly I geting somewhere.

 

c.u. Zui

 

 

 

 

 

 

 

 

Link to comment
Share on other sites

Hi.

 

I make progress...

Here is the Way I have completed a Build with Wifi Driver AP6330 in the Imagefile.

 

EDIT: I forgot to give Infos about the Build Options.

          ./compile.sh  BOARD=arm-64 BRANCH=current RELEASE=buster BUILD_MINIMAL=no BUILD_DESKTOP=yes KERNEL_ONLY=no KERNEL_CONFIGURE=no

 

 

I used the File: "brcmfmac-add-ap6330-firmware.patch"

The Directory Location I found it was: "/Build-Armbian/patch/kernel/rockchip-dev/brcmfmac-add-ap6330-firmware.patch"

I placed the File into this Folder: "/Build-Armbian/userpatches/kernel/arm-64-current/brcmfmac-add-ap6330-firmware.patch"

 

So Now the Wifi is Working on My Device.

 

Somehow I get another Wifi-Device listed by "hwinfo".

I assume it is the Bluetooth-Part of the Driver, or another Bandwith (5GHz) ?

I gonna find out what is happening in this Strange Box... ;)

 

I used a "locate" command with Wildcards. (Wonders can happen in the Shell. What happens in the Shell, stays in the Shell!)

 

zui@zui-VirtualBox:~/Build-Armbian$ locate *brcm*6330*
/home/zui/Build-Armbian/cache/sources/armbian-firmware/lib/firmware/brcm/brcmfmac-ap6330-sdio.bin
/home/zui/Build-Armbian/cache/sources/armbian-firmware/lib/firmware/brcm/brcmfmac-ap6330-sdio.txt
/home/zui/Build-Armbian/cache/sources/armbian-firmware-full/lib/firmware/brcm/brcmfmac-ap6330-sdio.bin
/home/zui/Build-Armbian/cache/sources/armbian-firmware-full/lib/firmware/brcm/brcmfmac-ap6330-sdio.txt
/home/zui/Build-Armbian/cache/sources/armbian-firmware-git/brcm/brcmfmac-ap6330-sdio.bin
/home/zui/Build-Armbian/cache/sources/armbian-firmware-git/brcm/brcmfmac-ap6330-sdio.txt
/home/zui/Build-Armbian/patch/kernel/rockchip-current/brcmfmac-add-ap6330-firmware.patch
/home/zui/Build-Armbian/patch/kernel/rockchip-dev/brcmfmac-add-ap6330-firmware.patch
/home/zui/Build-Armbian/patch/kernel/rockchip-legacy/brcmfmac-add-ap6330-firmware.patch
/home/zui/Build-Armbian/userpatches/kernel/arm-64-current/brcmfmac-add-ap6330-firmware.patch

 

 

The Content of the File:

diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
index a907d7b06..ec71996c7 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
@@ -619,13 +619,17 @@ BRCMF_FW_DEF(4354, "brcmfmac4354-sdio");
 BRCMF_FW_DEF(4356, "brcmfmac4356-sdio");
 BRCMF_FW_DEF(4373, "brcmfmac4373-sdio");
 
+/* AMPAK */
+BRCMF_FW_DEF(AP6330, "brcmfmac-ap6330-sdio");
+
 static const struct brcmf_firmware_mapping brcmf_sdio_fwnames[] = {
 	BRCMF_FW_ENTRY(BRCM_CC_43143_CHIP_ID, 0xFFFFFFFF, 43143),
 	BRCMF_FW_ENTRY(BRCM_CC_43241_CHIP_ID, 0x0000001F, 43241B0),
 	BRCMF_FW_ENTRY(BRCM_CC_43241_CHIP_ID, 0x00000020, 43241B4),
 	BRCMF_FW_ENTRY(BRCM_CC_43241_CHIP_ID, 0xFFFFFFC0, 43241B5),
 	BRCMF_FW_ENTRY(BRCM_CC_4329_CHIP_ID, 0xFFFFFFFF, 4329),
-	BRCMF_FW_ENTRY(BRCM_CC_4330_CHIP_ID, 0xFFFFFFFF, 4330),
+	BRCMF_FW_ENTRY(BRCM_CC_4330_CHIP_ID, 0xFFFFFFEF, 4330),
+	BRCMF_FW_ENTRY(BRCM_CC_4330_CHIP_ID, 0x10, AP6330),
 	BRCMF_FW_ENTRY(BRCM_CC_4334_CHIP_ID, 0xFFFFFFFF, 4334),
 	BRCMF_FW_ENTRY(BRCM_CC_43340_CHIP_ID, 0xFFFFFFFF, 43340),
 	BRCMF_FW_ENTRY(BRCM_CC_43341_CHIP_ID, 0xFFFFFFFF, 43340),

It was already Discussed here: @jock was here and there, to write about AP6330 Wifi Patch.

 

 

Now only Bluetooth, and IR-Remote is Missing.

 

If I connect a Bluetooth USB-Dongle it works like Charm.

But BlueZ is Saying it has no Adapters found (without the Dongle).

So I miss the Drivers for the AP6330 Bluetooth Part.

 

zui@zui-VirtualBox:~/Build-Armbian$ locate *6330-bluetooth*
/home/zui/Build-Armbian/packages/bsp/arm-64/ap6330-bluetooth.service
/home/zui/Build-Armbian/packages/bsp/rockchip/ap6330-bluetooth.service

Hmmm, what is this?

 

Ok then Armbian Lovers and /or Haters.

 

I need more tinkering. I will be behind the Keyboard. :)

 

c.u. Zui

 

Edited by ZuiMelanieForno
Forgot the Build Options, added Infos
Link to comment
Share on other sites

Hello. Me Again...

 

I am still in the same Stage as before, no changes since the Post from March 30 2020.

 

But I soldered four Cables to the Debug UART.

Connected them to a USB-To-TTL, had issues and Bluescreens with the old crappy thingie... Zui sad.

 

But the ArduinoUno came to the Rescue.

 

Nexbox A95X AP6330 Debug UART Arduino

 

I used Putty with these Settings, and it was convinient, but i wanted more. (So greedy...)

 

I just Opened a New WPf Application and Voila, I can now read in the UART Serial Transmission.

Transmissions are very good, in my humble Opinion.

This is just for me, to have a Debugging Input where I can Search for things... :)

Here I use a Filter to search in a ListBox filled with every Line of the UART /Serial Output.

grafik.thumb.png.cfdc6fa56a6ea310269b8eb3f7a3e1e3.png

 

So here is a Question I have, about redirecting the Screen Output to the ttyAML0.

Is it the ttly0 that needs to be redircted?

Is ist done with an Overlay?

So what I see when the System boots up, should also be sent to the Debug/UART/SerialOutput.

 

I hope I got it somehow explained.

 

It is displaying till this Line "Armbian 20.05.0 buster ttyAML0".

 

Another thing I tested, was a LibreElec Build, and all Devices where installed and usable as intented.

I tried to dig into the BRCM Stuff, and there was a Comlete different File Structure.

So I started dabbling with modprobe and lsmod and such.

But where are the Windows settings? OK. Just wanted to get You on your Toes... Are you awake Now?

 

Okily dokily.

 

Fact is I lost the Track and also alot of Data, so now I can not reproduce what I was testing.

 

I am gonna Test the LibreElec build to see how the Drivers are Structured over there...

 

It is like on the Other Side of the Ocean. BTW I never saw an Ocean.. :(

 

See You Folks, My Springcleaning is long overdoe...

 

ttnt0 = tillthenexttime0

 

Zui from Hamburg

 

 

 

 

 

 

 

 

 

 

Link to comment
Share on other sites

Hello, sorry for replying so late, but didn't get the mention from your previous post.

 

The service file you quoted in that post contains the systemd service that activates the bluetooth userspace service.

It contains the invocation to hciattach

/usr/bin/hciattach /dev/ttyS0 bcm43xx 1500000

that will create the bluetooth device for use of other applications.

 

First you need the firmware file in the right place. Unfortunately hciattach is a legacy program, it wants the firmware file in /etc/firmware, so:

  1. create the directory with mkdir -p /etc/firmware
  2. symlink the firmware wth ln -sf /lib/firmware/brcm/BCM4330B1.hcd /etc/firmware

At this point I suggest you to do some tests using hciattach command above. You may need to modify the command line because /dev/ttyS0 device is the serial device the bluetooth is attached on rockchip boards.

You should first find which is the UART the bluetooth is attached to on your board. Be sure it is active in the device tree (so it is exposed as /dev/ttyS* file in the filesystem) and then change it in hciattach command line above.

Use hciconfig -a to see if the device is exposed to the system and hcitool scan to scan for bluetooth devices.

 

Once you have found the right serial device:

  1. modify ap6330-bluetooth.service to use the right serial device
  2. copy ap6330-bluetooth.service file in /etc/systemd/system
  3. to make systemd aware of the new service, run systemctl daemon-reload
  4. to make the service run at every boot, run systemctl enable ap6330-bluetooth

 

You can find the references in armbian scripts of above steps here

Link to comment
Share on other sites

@jock

Hallihallo or <abrv>Hi.

 

Report:

Directory Created: Check.

Symbolic Link Created: Check.

 

Testing /dev/ttyS0: Nope, Nada, Niente, Njet, Nix... :(

 

So I tried to figure out all "tty????"´s.

Of course manually. What a waste of Time.

 

So results are somehow like this:

 

If Timouts are reported by hciattach, I assume it is something to work on, but not the right one.

 

Quote

 

"/dev/tty" on its own should never, ever be tried in the first Place.

I needed a reboot, to get the Console working again. (I was thinking it is not a good idea, but was too eager to try what happens.)


 

 


 

From tty0 to tty63 always the Same result:

bcm43xx_init

Initialization timed out.

 

From ttyp1 to ttypf:

Can´t open serial port: Input/output error

Can´t initialize device: Input/output error

 

From ttyS0 to ttypS4:

Can´t get port settings: Input/output error

Can´t initialize device: Input/output error

 

And finaly /dev/ttyAML0:

bcm43xx_init

Initialization timed out.

 

I asume two causes:

1. ttyS0 to ttyS4 are not configured right.

2. The Devicetree is not correct. So the Proper tty?? is not there.

 

Because you mentioned the Devicetree, I need to find out how to activate the Device in the Tree, as a Branch or Leave or a Bug on a Leave on a Branch... ;)

 

I also was capable to Type in the Console "hciattach -l". Wonders can happen...

 

So the result is this:

...

bcm2035     0x0a5c,0x2035

bcm43xx     0x0000,0x0000

...

 

Thank You jock for helping me with this.

It took me some time to get the ARM to get up... (Right ARM to the mouse Command is not Working! You are Old... Wierd, when Computers got a Personality.)

 

I lost the Build-Environment on an SSD, so I recreated a Hyper-V Machine.

 

Now I am stuck, and can´t Build... I will manage that one Day.

 

And I made a Notice to myself: "Don´t Buy a new HDD, and try to finish other Tasks. It will take time to Copy Data and Stuff."

 

So I was not replying to You fast enough, for my Taste. lol

 

c.u. Zui, dabbling with Linux and such...

 

Link to comment
Share on other sites

Hello, me again...

 

It is outside the PostTopic, but i don´t want to open a New one.

 

I had setup an Hyper-V-Machine, and tried for 3 Days now and got always a Build error.

 

Von https://github.com/ChalesYu/rtl8822bs-aml
 * branch            master     -> FETCH_HEAD
 * [neuer Branch]    master     -> origin/master
[ .... ] Checking out 
[ o.k. ] * applying wireless-rtl8822bs.patch 
[ o.k. ] * applying wireless-rtl8822bs-1.patch 
[ o.k. ] Adding [ Wireless drivers for Realtek 8822CS chipsets branch:master ]
cp: Aufruf von stat für '/home/zui/Build-Armbian/cache/sources/rtl8822cs/master/core' nicht möglich: Datei oder Verzeichnis nicht gefunden
cp: Aufruf von stat für '/home/zui/Build-Armbian/cache/sources/rtl8822cs/master/hal' nicht möglich: Datei oder Verzeichnis nicht gefunden
cp: Aufruf von stat für '/home/zui/Build-Armbian/cache/sources/rtl8822cs/master/include' nicht möglich: Datei oder Verzeichnis nicht gefunden
cp: Aufruf von stat für '/home/zui/Build-Armbian/cache/sources/rtl8822cs/master/os_dep' nicht möglich: Datei oder Verzeichnis nicht gefunden
cp: Aufruf von stat für '/home/zui/Build-Armbian/cache/sources/rtl8822cs/master/platform' nicht möglich: Datei oder Verzeichnis nicht gefunden
cp: Aufruf von stat für '/home/zui/Build-Armbian/cache/sources/rtl8822cs/master/halmac.mk' nicht möglich: Datei oder Verzeichnis nicht gefunden
cp: Aufruf von stat für '/home/zui/Build-Armbian/cache/sources/rtl8822cs/master/rtl8822c.mk' nicht möglich: Datei oder Verzeichnis nicht gefunden
cp: Aufruf von stat für '/home/zui/Build-Armbian/cache/sources/rtl8822cs/master/Makefile' nicht möglich: Datei oder Verzeichnis nicht gefunden
cp: Aufruf von stat für '/home/zui/Build-Armbian/cache/sources/rtl8822cs/master/Kconfig' nicht möglich: Datei oder Verzeichnis nicht gefunden
[ o.k. ] Started patching process for [ kernel arm-64-current ]
[ o.k. ] Looking for user patches in [ userpatches/kernel/arm-64-current ]
[ o.k. ] * [l][c] packages-current.patch 
[ o.k. ] Compiling current kernel [ 5.7.0-rc1 ]
[ o.k. ] Compiler version [ aarch64-linux-gnu-gcc 8.3.0 ]
[ o.k. ] Using kernel config file [ config/kernel/linux-arm-64-current.config ]
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/confdata.o
  HOSTCC  scripts/kconfig/expr.o
  LEX     scripts/kconfig/lexer.lex.c
  YACC    scripts/kconfig/parser.tab.[ch]
  HOSTCC  scripts/kconfig/lexer.lex.o
  HOSTCC  scripts/kconfig/parser.tab.o
  HOSTCC  scripts/kconfig/preprocess.o
  HOSTCC  scripts/kconfig/symbol.o
  HOSTCC  scripts/kconfig/util.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf  --olddefconfig Kconfig
drivers/net/wireless/Kconfig:48: can't open file "drivers/net/wireless/rtl8822cs/Kconfig"
scripts/kconfig/Makefile:71: recipe for target 'olddefconfig' failed
make[1]: *** [olddefconfig] Error 1
Makefile:588: recipe for target 'olddefconfig' failed
make: *** [olddefconfig] Error 2
scripts/kconfig/conf  --syncconfig Kconfig
scripts/kconfig/Makefile:71: recipe for target 'syncconfig' failed
Makefile:588: recipe for target 'syncconfig' failed
Makefile:699: recipe for target 'include/config/auto.conf.cmd' failed
[ error ] ERROR in function compile_kernel [ compilation.sh:381 ]
[ error ] Kernel was not built [ @host ]
[ o.k. ] Process terminated 
zui@zui-Virtual-Machine:~$ 

"What I had done wrong? I promise, I didn´t, did and not ever do something... :)"

 

 

@balbes150

 

Is it based on the missing files or wrong script?

 

It is in German, but it says: No File or Directory Error.

 

Is it too early to have the new Driver from @chalesY incooperated?

 

I need to mention I used Hyper-V before succesfully, then Switched to VirtualBox and Vagrant.

I removed VirtualBox, I got headakes of the Configuration Vagratzations and it was Complicated.

I don´t assume it has to do with the VM-Host(-ing).

 

And I really miss the Menuentry for s905x. Zui sad... sniff

 

Thank You all for reading this and have a good one.

 

 

Link to comment
Share on other sites

Hi, 

 

I have a Csa93 S912 device with 3GB DDR3 and 32GB ROM with 32GB SD. 

 

Gigabit Ethernet and HDMI sound is working with newest Armbian Bionic Desktop Image and meson-gxm-q200. dtb

 

There is also the Bluetooth icon, but no possibility to get Bluetooth and/or wireless working. 

 

Gigabit Ethernet is working, test video works with sound, but very laggy. 

 

The wireless chip should be the AP6330 with dual wifi. 

 

I tried the thing what was suggested in the top with using the AP4330 files and did a reboot, but did not work. 

 

Could you please give me some help to get wifi working? 

 

USB HDD is also working, haven't done performance test, but NTFS seems to work out of the box. 

 

Would love to use the device it as NAS, embedded jdownloader.org device, wireguard endpoint, tvheadend and wireless router. 

Link to comment
Share on other sites

2 hours ago, Alex1983 said:

Hi, 

 

I have a Csa93 S912 device with 3GB DDR3 and 32GB ROM with 32GB SD. 

 

Gigabit Ethernet and HDMI sound is working with newest Armbian Bionic Desktop Image and meson-gxm-q200. dtb 

 

There is also the Bluetooth icon, but no possibility to get Bluetooth and/or wireless working. 

 

Gigabit Ethernet is working, test video works with sound, but very laggy. 

 

The wireless chip should be the AP6330 with dual wifi. 

 

I tried the thing what was suggested in the top with using the AP4330 files and did a reboot, but did not work. 

 

Could you please give me some help to get wifi working? 

 

USB HDD is also working, haven't done performance test, but NTFS seems to work out of the box. 

 

Would love to use the device it as NAS, embedded jdownloader.org device, wireguard endpoint, tvheadend and wireless router. 

Edit: I made a Iperf3 test. 

 

Unfortunately there is just a performance of 100Mbit/s interface, not of 1000 Mbit/s

 

<code>

Connecting to host 192.168.178.169, port 5201
Reverse mode, remote host 192.168.178.169 is sending
[  4] local 192.168.178.189 port 39424 connected to 192.168.178.169 port 5201
[  6] local 192.168.178.189 port 39425 connected to 192.168.178.169 port 5201
[  8] local 192.168.178.189 port 39426 connected to 192.168.178.169 port 5201
[ 10] local 192.168.178.189 port 39427 connected to 192.168.178.169 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  1.80 MBytes  15.1 Mbits/sec                  
[  6]   0.00-1.00   sec  3.04 MBytes  25.4 Mbits/sec                  
[  8]   0.00-1.00   sec  3.07 MBytes  25.7 Mbits/sec                  
[ 10]   0.00-1.00   sec  3.10 MBytes  26.0 Mbits/sec                  
[SUM]   0.00-1.00   sec  11.0 MBytes  92.2 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   1.00-2.00   sec  1.85 MBytes  15.5 Mbits/sec                  
[  6]   1.00-2.00   sec  3.03 MBytes  25.5 Mbits/sec                  
[  8]   1.00-2.00   sec  3.17 MBytes  26.6 Mbits/sec                  
[ 10]   1.00-2.00   sec  3.07 MBytes  25.8 Mbits/sec                  
[SUM]   1.00-2.00   sec  11.1 MBytes  93.3 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   2.00-3.00   sec  1.69 MBytes  14.2 Mbits/sec                  
[  6]   2.00-3.00   sec  2.99 MBytes  25.0 Mbits/sec                  
[  8]   2.00-3.00   sec  3.33 MBytes  27.9 Mbits/sec                  
[ 10]   2.00-3.00   sec  3.09 MBytes  25.9 Mbits/sec                  
[SUM]   2.00-3.00   sec  11.1 MBytes  93.1 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   3.00-4.00   sec  1.76 MBytes  14.8 Mbits/sec                  
[  6]   3.00-4.00   sec  3.08 MBytes  25.8 Mbits/sec                  
[  8]   3.00-4.00   sec  3.20 MBytes  26.8 Mbits/sec                  
[ 10]   3.00-4.00   sec  3.04 MBytes  25.4 Mbits/sec                  
[SUM]   3.00-4.00   sec  11.1 MBytes  92.9 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   4.00-5.00   sec  1.75 MBytes  14.7 Mbits/sec                  
[  6]   4.00-5.00   sec  3.08 MBytes  25.8 Mbits/sec                  
[  8]   4.00-5.00   sec  3.12 MBytes  26.2 Mbits/sec                  
[ 10]   4.00-5.00   sec  3.15 MBytes  26.4 Mbits/sec                  
[SUM]   4.00-5.00   sec  11.1 MBytes  93.2 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   5.00-6.00   sec  1.85 MBytes  15.5 Mbits/sec                  
[  6]   5.00-6.00   sec  3.20 MBytes  26.8 Mbits/sec                  
[  8]   5.00-6.00   sec  2.99 MBytes  25.1 Mbits/sec                  
[ 10]   5.00-6.00   sec  2.86 MBytes  24.0 Mbits/sec                  
[SUM]   5.00-6.00   sec  10.9 MBytes  91.4 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   6.00-7.00   sec  2.06 MBytes  17.3 Mbits/sec                  
[  6]   6.00-7.00   sec  3.67 MBytes  30.8 Mbits/sec                  
[  8]   6.00-7.00   sec  2.68 MBytes  22.5 Mbits/sec                  
[ 10]   6.00-7.00   sec  2.69 MBytes  22.5 Mbits/sec                  
[SUM]   6.00-7.00   sec  11.1 MBytes  93.1 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   7.00-8.00   sec  2.10 MBytes  17.6 Mbits/sec                  
[  6]   7.00-8.00   sec  3.67 MBytes  30.7 Mbits/sec                  
[  8]   7.00-8.00   sec  2.67 MBytes  22.3 Mbits/sec                  
[ 10]   7.00-8.00   sec  2.67 MBytes  22.4 Mbits/sec                  
[SUM]   7.00-8.00   sec  11.1 MBytes  93.1 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   8.00-9.00   sec  2.18 MBytes  18.3 Mbits/sec                  
[  6]   8.00-9.00   sec  3.57 MBytes  29.9 Mbits/sec                  
[  8]   8.00-9.00   sec  2.67 MBytes  22.4 Mbits/sec                  
[ 10]   8.00-9.00   sec  2.68 MBytes  22.5 Mbits/sec                  
[SUM]   8.00-9.00   sec  11.1 MBytes  93.0 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[  4]   9.00-10.00  sec  2.37 MBytes  19.9 Mbits/sec                  
[  6]   9.00-10.00  sec  3.25 MBytes  27.2 Mbits/sec                  
[  8]   9.00-10.00  sec  2.68 MBytes  22.5 Mbits/sec                  
[ 10]   9.00-10.00  sec  2.78 MBytes  23.3 Mbits/sec                  
[SUM]   9.00-10.00  sec  11.1 MBytes  92.9 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  19.7 MBytes  16.6 Mbits/sec    0             sender
[  4]   0.00-10.00  sec  19.4 MBytes  16.3 Mbits/sec                  receiver
[  6]   0.00-10.00  sec  33.2 MBytes  27.8 Mbits/sec    0             sender
[  6]   0.00-10.00  sec  32.7 MBytes  27.4 Mbits/sec                  receiver
[  8]   0.00-10.00  sec  30.0 MBytes  25.2 Mbits/sec    0             sender
[  8]   0.00-10.00  sec  29.6 MBytes  24.8 Mbits/sec                  receiver
[ 10]   0.00-10.00  sec  29.6 MBytes  24.8 Mbits/sec    0             sender
[ 10]   0.00-10.00  sec  29.1 MBytes  24.4 Mbits/sec                  receiver
[SUM]   0.00-10.00  sec   112 MBytes  94.3 Mbits/sec    0             sender
[SUM]   0.00-10.00  sec   111 MBytes  92.9 Mbits/sec                  receiver

iperf Done.

</code>

Link to comment
Share on other sites

  • Werner locked this topic
Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines