"Next X86" dev (Kernel/ Hardware/ Debian stretch/buster)

in other words, you bricked the Alfawise by replacing the BIOS?
As a word of warning for other users, there is no need to replace a BIOS to boot anything other than Windows.
The only thing one needs to do is disable Windows’ fastboot, which will allow you to interrupt the boot process with DEL, F2 or whatever key is reserved for that.

Thank You! I will give this a try!

Sent from my SM-G950U using Tapatalk

yes, i did - therefore that “Still-Life” :wink:

I think it is not completly right. :blush:
the BIOS-Updates directly from Beelink for the AZW Z83 II are identical to the BIOS-Updates a Beelink Z83 II,
the only difference are the INTEL-Logo / Beelink-Logo.
my last found version of the AZW-Z83 II-BIOS were: Z83II_V20
But the BIOS from Alfawise X5 is not the same BIOS.
In the AZW Z83 II-BIOS you can say like the older PC-BIOS “start PC from USB / start PC from internal hdd” permantly.
In the Alfawise-BIOS there is no switch to start permanently from USB3.0-Port or sdcard.
So the AZW Z83 II BIOS is more completely.
The Alfawise-X-BIOS will every time show a graphic symbol “Start Android / Start Win10”.

if we are kill the win10-image with dd, everthing will ok. But if i will let the image on the internal disk, i may
prefer an permantly switch in the BIOS “start PC from USB”

Hello Gé,

what a mess! My x86 hardware is broken. It won’t start anymore. Not even the bios is reachable. When connected to power only the power led is blinking - that’s all. I sent a message to the Trekstor service this morning and I hope they can help me soon or maybe send me a new device if it is impossible to repair my old one I bought just three months ago.

I’m sorry but I cannot support you with tests at the moment…

Best regards,
Robert

oh, that looks bad. another bricked device???

Don’t worry about testing, there is still a lot to be done and I am not convinced we will get any progress with audio anytime soon.
Audio on the Intel Apollo Baytrail/ Cherrytrail platform is clearly still Work-In-Progress.
The unfortunate thing is, these devices are hardly supported by suppliers (so cheap, they can’t afford).
Just thrown on the market with a (legal???) Windows license, off you go.
This also means there is hardly any documentation/ information, apart from internet posts/ threads from peer developers looking for the same clues.

Other than that, I think the version itself seems OK with the platform. Mini PC’s run perfectly with USB Audio.
Tested on my “old” systems today, no problem sofar…

Expecting to get more feedback from the others.

tried on a Mac mini , so far so good.
my two cents below

  1. NAS setup for CIFS does no work (adding vers=1.0) in options fixed it.

  2. Seems like sources are still on Jessie not stretch, so are the packages

deb ftp.nl.debian.org/debian/ jessie main contrib non-free

Thanks for your feedback, much appreciated.

Please point me to the post where I said we would have Debian stretch :smiley:
We are preparing for Debian stretch, using this channel to do a lot a prerequisite testing with kernel and firmware.
For a complete stretch port we need to have recompiled, Volumio -specific packages and building the OS with all stretch packages.
I have not done that yet.

The CIFS problem is not ours, having to add “vers=” is the result of a security hardening procedure that took place, where the kernel developers decided to set SMB 3.0 as the default.
So it also counts for other Volumio portings using newer kernels, there are a number of reports in this forum.

Haha, I just go by the post title, too excited to notice the fine print of “ preparation”

Never mind, all in all works same as official release with 3.18kernel.

Now wait for the fully updated stretch then.

Cheers.

Thank You!
Module for gpio work fine under su.

Good, Thanks for your feedback.

In the first time, a big thank you to gkkpch. Thank you for your investment and for your work.

I just discovered volumio. I give you my first feedback.

Hardware / Configuration :

Intel NUC5PGYH : This model is interesting for its price and its optical output (SSD WD 120Go / 8Go DDR)
Marantz PM6005 : Amplifier with DAC 24/192 and 2 digital inputs (optical and coaxial)
Generic optical cable

The NUC and the amplifier are connected by the optical cable. Quite simply.
Installation on the internal HD

Out of the box :

Ethernet OK
Wifi OK (Intel Wireless-AC 3165)
Optical output NO

Nothing more to report

Activation of the optical output :

The “problem” is a classic. In the alsamixer, we have 3 SPDIF outputs:

  • S / PDIF
  • S / PDIF Default
  • S / PDIF 16

The first two were active, unlike the last one, which was in mute.

I just turned on the last (S / PDIF 16).

For those who are in this case, in SSH / alsamixer / when we are on the S / PDIF 16 we press the key “M”.

I don’t know what the other 2 correspond to. I can put them in mute. I see no consequence as long as S / PDIF 16 is enabled.

Informations on the system :


volumio@volumio:~$ cat /proc/asound/modules
 0 snd_hda_intel
volumio@volumio:~$  cat /proc/asound/cards
 0 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0x81414000 irq 121
volumio@volumio:~$ cat /proc/asound/pcm
00-00: ALC283 Analog : ALC283 Analog : playback 1 : capture 1
00-01: ALC283 Digital : ALC283 Digital : playback 1
00-03: HDMI 0 : HDMI 0 : playback 1
volumio@volumio:/etc$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC283 Analog [ALC283 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC283 Digital [ALC283 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
volumio@volumio:/etc$ aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
default:CARD=PCH
    HDA Intel PCH, ALC283 Analog
    Default Audio Device
sysdefault:CARD=PCH
    HDA Intel PCH, ALC283 Analog
    Default Audio Device
front:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    Front speakers
surround21:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Digital
    IEC958 (S/PDIF) Digital Audio Output
hdmi:CARD=PCH,DEV=0
    HDA Intel PCH, HDMI 0
    HDMI Audio Output
dmix:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    Direct sample mixing device
dmix:CARD=PCH,DEV=1
    HDA Intel PCH, ALC283 Digital
    Direct sample mixing device
dmix:CARD=PCH,DEV=3
    HDA Intel PCH, HDMI 0
    Direct sample mixing device
dsnoop:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    Direct sample snooping device
dsnoop:CARD=PCH,DEV=1
    HDA Intel PCH, ALC283 Digital
    Direct sample snooping device
dsnoop:CARD=PCH,DEV=3
    HDA Intel PCH, HDMI 0
    Direct sample snooping device
hw:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    Direct hardware device without any conversions
hw:CARD=PCH,DEV=1
    HDA Intel PCH, ALC283 Digital
    Direct hardware device without any conversions
hw:CARD=PCH,DEV=3
    HDA Intel PCH, HDMI 0
    Direct hardware device without any conversions
plughw:CARD=PCH,DEV=0
    HDA Intel PCH, ALC283 Analog
    Hardware device with all software conversions
plughw:CARD=PCH,DEV=1
    HDA Intel PCH, ALC283 Digital
    Hardware device with all software conversions
plughw:CARD=PCH,DEV=3
    HDA Intel PCH, HDMI 0
    Hardware device with all software conversions

The tests & solution :

Some elements remain today still vague. Everything is working now but I can’t explain some things.

I used the “aplay -l” command at first to identify the optical output.

So I targeted this line :

card 0: PCH [PCH Intel HDH], device 1: ALC283 Digital [ALC283 Digital]

Peripheral: hw0.1

When I consult :

/volumio/app/plugins/audio_interface/alsa_controller/cards.json

I notice that the file is incomplete:

 {"name": "HDA Intel PCH", "multidevice": true, "devices": [{"number": 0, "prettyname": "Analog Out", "defaultmixer": ""}, {"number" : 3, "prettyname": "HDMI", "defaultmixer": ""}]},

I don’t see this exit # 1, only # 0 and # 3.

I make the necessary modifications and the interface appears on volumio.

But no result. I have nothing out. I don’t understand why.

I continue my debug and I use this time “aplay -L”.

I get this information:

iec958: CARD = PCH, DEV = 0
    HDA Intel PCH, ALC283 Digital
    IEC958 (S / PDIF) Digital Audio Output

particularly interesting.

I’m doing some reading tests with “aplay -D hw: 0.1 file.wav”. I don’t go headlong anymore ! :slight_smile:

The tests are conclusive. I have the signal on the optical output.

Back on the cards.json file.

I change the volumio configuration using the “Analog out” parameter. It’s a digital output but it’s only a language defect.

Et voilà. The optical output works.

Be careful though ! No volume control.

Sorry for my english … I’m french. :slight_smile:

Thanks for your very interesting and helpful feedback.
I’m on the road at the moment and will have a closer look at in the weekend when I get back.

Hi Gkkpch

One more feedback, my system can only see 2g memory out of my total 4g.

Same for 3.18 and your 4.16 kernel.

Is it possible to enable PAE in the new kernel to use full memory?

Thank you

That seems somewhat risky.
I would have to switch High Memory Support (currently set to 4GB) to “off” in order to get to the PAE (Physical Address Extension) Support prompt.
I’m not sure what that will lead to on all other installations we have.
Is the 2Gb limitation a problem for you? Or having High Memory Support set to 4GB?
Please elaborate a little on that subject so that I know what you are trying to do…

I don’t think the problem comes from PAE. The displayed memory would be equivalent to 3.2GB (approximately) and not 2GB.
Can you give us the return of the commands :

1 - sudo lshw -C memory
2 - sudo free -m

What is your hardware configuration ? CPU ? Motherboard ? …

We did not add package ‘lshw’, image size is huge as it is already.
But I’ll add it, seeing we have lots of new configurations coming up, thanks for the hint.

Quickly topped up my memory on my dev tester from 2 to 4GB looked at it with “free -m”
Definitely reported as 3.2GB, so we must have another issue here.

On the other hand, 2GB should not be a problem at all.
Volumio works perfectly with plenty setups like that.

Mine machine is the lowest config Mac mini as below link

apple.com/mac-mini/specs/

Confirmed in osx it has 4g memory.

  • sudo lshw -C memory results:

description: System memory
physical id: 0
size: 1825MiB

sudo free -m
total used free shared buffers cached
Mem: 1825 533 1292 5 72 263
-/+ buffers/cache: 196 1628
Swap: 0 0 0

It behaves the same using official 3.18 kernel image.

For PAE, I was under the impression that you need it for memory bigger than 2GB. I don’t need PAE specifically, just need to use the full 4G ram my machine has.

And for why more than 2G,

I compiled customized MPD, try to maximize the audio buffer to make MPD play from memory, rather than continuously reading disk. with the 1836MB limit, I can set the buffer to around 500MB with no problem, however, bigger buffer will cause the system to run out of memory.
Trying to squeeze all out all possible ways for better audio. Memory play back seems to be helpful.

hopefully this is clear enough.

1 or 2 banks for the RAM ?

The result of ‘lshw’ is incompleted.

Try to boot on the live linux CD (AMD64) to testing your configuration.

Tried on OS X and Debian 9 (amd64)both show 4GB