Jump to content


Photo

Octagon SF8008 Wrong USB Tuner ID


  • Please log in to reply
78 replies to this topic

#1 el bandido

  • Senior Member
  • 364 posts

+13
Neutral

Posted 3 February 2022 - 19:04

Receiver: Octagon SF 8008, twin DVB-S2X
Image: Develop Branch (HomeBuild)
 

Maybe someone here will have a solution for this. The Octagon SF8008 identifies the Hauppauge 950Q ATSC usb tuner as DVB-C instead of ATSC. I have seen problems with other usb devices on other forums, so it doesn't seem like the Hauppauge is the only tuner with an identification issue.
 

The PULSe 4K is an almost identical receiver to the Octagon SF8008. The PULSe 4K identifies all of my Hauppauge ATSC usb tuners correctly. Shown below are the tuner information for the SF8008 and the PULSe 4K. I notice the SF8008 is labeling every tuner in the box as frontend 0 while the Pulse 4K assigns a different frontend for each tuner.

Pretty much anything can be changed in the image as it is a HomeBuild using the Develop branch. The Linux & Kernel files can also be altered if needed. I have spent some time changing things, but nothing works. Even if the USB device is forced to id correctly as ATSC, it still will not work. Any ideas on what can be done to fix this would be greatly appreciated.
 

Thanks for your time!
 

root@sf8008:~# dmesg | grep adapter
[    3.135062] virtual DVB adapter driver, version 1.4, © 2010-12 Honza Petrous, SmartImp.cz
[    3.208014] DVB: registering new adapter (nHi)
[    3.458570] DVB: registering adapter 0 frontend 0 (Si2166D)...
[    3.718129] DVB: registering adapter 0 frontend 0 (Si2166D)...
[    7.308034] DVB: registering new adapter (au0828)
[    7.311475] DVB: registering adapter 1 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
[   27.966549] DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
root@sf8008:~#
root@sf8008:~#
root@sf8008:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2X
Name: Si2166D
Has_Outputs: no
Frontend_Device: 0
I2C_Device: 0
NIM Socket 1:
Type: DVB-S2X
Name: Si2166D
Has_Outputs: no
Frontend_Device: 1
I2C_Device: 1
NIM Socket 2:
Type: DVB-C
Name: Auvitek AU8522 QAM/8VSB Frontend
Has_Outputs: no
Frontend_Device: 2
I2C_Device: 2
root@sf8008:~#

#############################################

root@pulse4k:~# dmesg | grep adapter
[    3.280455] DVB: registering new adapter (dvb0)
[    4.128900] platform dvb0.0: DVB: registering adapter 0 frontend 0 (DVB-S2)...
[    4.134973] platform dvb0.0: DVB: registering adapter 0 frontend 1 (DVB-S2)...
[    4.931029] DVB: registering new adapter (au0828)
[    4.934475] usb 1-1: DVB: registering adapter 1 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
[   19.476355] platform dvb0.0: DVB: registering adapter 0 frontend 2 (vtuner)...
[118986.849605] platform dvb0.0: DVB: registering adapter 0 frontend 2 (vtuner)...
[119037.115751] platform dvb0.0: DVB: registering adapter 0 frontend 2 (vtuner)...
root@pulse4k:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-S2X
        Name: Si2166D
        Has_Outputs: no
        Frontend_Device: 0
        I2C_Device: 0
        Supports_Blind_Scan: yes
NIM Socket 1:
        Type: DVB-S2X
        Name: Si2166D
        Has_Outputs: yes
        Frontend_Device: 1
        I2C_Device: 0
        Supports_Blind_Scan: yes
NIM Socket 2:
        Type: ATSC
        Name: WinTV HVR-950
        Has_Outputs: no
        Frontend_Device: 2
        I2C_Device: -1
root@pulse4k:~#
 

 



Re: Octagon SF8008 Wrong USB Tuner ID #2 Dimitrij

  • PLi® Core member
  • 10,020 posts

+338
Excellent

Posted 3 February 2022 - 19:13

openATV the same behaviour?


GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Octagon SF8008 Wrong USB Tuner ID #3 el bandido

  • Senior Member
  • 364 posts

+13
Neutral

Posted 3 February 2022 - 19:45

Yes. OE Alliance (ATV) has the same problem,
 



Re: Octagon SF8008 Wrong USB Tuner ID #4 Dimitrij

  • PLi® Core member
  • 10,020 posts

+338
Excellent

Posted 3 February 2022 - 20:58

Thinking out loud...

https://github.com/z...f8008/defconfig

https://github.com/C...lse4k/defconfig

 

https://discourse.os...working/90188/5


Edited by Dimitrij, 3 February 2022 - 21:10.

GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Octagon SF8008 Wrong USB Tuner ID #5 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 3 February 2022 - 21:30

an lsmod on both boxes might show which driver is missing.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Octagon SF8008 Wrong USB Tuner ID #6 el bandido

  • Senior Member
  • 364 posts

+13
Neutral

Posted 3 February 2022 - 21:49

Thanks!
I tried changing the Octagon defconfig file to the PULSe4k deconfig and got errors. I also went line-by line and edited the Octagon defconfig file with that of the PULSe4k, but still get the Hauppauge to id as dvb-c.
 

Everything seems to be correct with the firmware loading. Below are lsmod from PULSe and SF8008.

root@pulse4k:~# lsmod
Module                  Size  Used by
au8522_dig              7225  1
au8522_common           4002  1 au8522_dig
au0828                 19338  2
tveeprom               12040  1 au0828
mali                  278055  0
pulse4k_4            6435433  59 mali
pulse4k_3             430733  23 mali,pulse4k_4
pulse4k_2              31510  1 pulse4k_3
pulse4k_1              29576  3 pulse4k_2,pulse4k_3,pulse4k_4
root@pulse4k:~#

 

##########################################################

root@sf8008:~# lsmod
Module                  Size  Used by
au8522_dig              7225  1
au8522_common           4002  1 au8522_dig
8192eu               1262601  0
au0828                 19338  1
ahci_platform           2936  0
tveeprom               12040  1 au0828
hisi_encoder            4121  0
hisi_keys               2792  0
hisi_sci                9592  0
hisi_ir                 4230  0
libahci_platform        6390  1 ahci_platform
libahci                23341  2 libahci_platform,ahci_platform
hi_pmoc                73918  1
hi_vi                  71057  0
hi_sci                 56990  1 hisi_sci
hi_aenc                 7367  0
hi_venc               229263  1
hi_advca              228114  1
hi_png                 24106  0
hi_jpge                22436  0
hi_jpeg                16843  0
hi_dbe                  5734  0
mali                  284125  0
hi_fb                 197689  3
hi_dvb                928477  37
vtunerc                25550  3 hi_dvb
oled                    6203  2 hi_dvb
hi_keyled              79819  3 oled,hisi_keys,hi_dvb
hi_tuner              517464  0
hi_mce                  4402  0
hi_pvr                  4284  0
hi_sync                66760  1
hi_aiao               381932  4
hi_adsp               220281  0
hi_vdec              1251988  1
hi_vpss               400316  0
hi_vfmw              1827881  0
hi_adec                 9236  1
hi_demux              417073  2 hi_dvb
hi_otp                 24944  2 hi_pmoc
hi_tde                112944  0
hi_i2c                 19734  2 hi_tuner,hi_dvb
hi_gpio_i2c            14794  3 hi_tuner,hi_i2c,hi_dvb
hi_gpio                18564  1 hi_dvb
hi_vou               1245286  2
hi_hdmicec              5071  2 hi_dvb
hi_hdmi               900300  3 hi_hdmicec,hi_dvb
hi_cipher             264125  0
hi_pq                1656354  3 hi_vou,hi_vpss
hi_pdm                 25264  0
hi_common              94145  39 mali,hi_fb,hi_pq,hi_vi,hi_cipher,hi_keyled,hi_advca,hi_demux,hi_tuner,hi_i2c,hi_dvb,hi_mce,hi_pdm,hi_otp,hi_png,hi_pvr,hi_sci,hi_tde,hi_vou,hi_adec,hi_adsp,hi_aenc,hi_aiao,hi_hdmi,hi_gpio,hi_jpeg,hi_jpge,hi_pmoc,hi_sync,hi_vdec,hi_venc,hi_vfmw,hi_vpss,hisi_ir,hi_gpio_i2c
hi_mmz                 45984  22 hi_fb,hi_pq,hi_vi,hi_cipher,hi_common,hi_demux,hi_dvb,hi_png,hi_tde,hi_vou,hi_adec,hi_adsp,hi_aenc,hi_aiao,hi_jpeg,hi_jpge,hi_sync,hi_vdec,hi_venc,hi_vfmw,hi_vpss
hi_media                8732  25 hi_common,hi_mmz,hi_png,hi_tde,hi_jpeg,hi_jpge
root@sf8008:~#

 

 

Re: Octagon SF8008 Wrong USB Tuner ID #7 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 3 February 2022 - 22:04

No difference, so that isn't it.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Octagon SF8008 Wrong USB Tuner ID #8 el bandido

  • Senior Member
  • 364 posts

+13
Neutral

Posted 3 February 2022 - 22:30

I can make this change and the tuner will show ATSC instead of DVB-C in /proc/bus/nim_sockets
The usb tuner still does not work after this mod.

linux-4.4.35/drivers/media/dvb-frontends
#########ORIGINAL################
static struct dvb_frontend_ops au8522_ops = {
    .delsys = { SYS_ATSC, SYS_DVBC_ANNEX_B },
    .info = {
        .name            = "Auvitek AU8522 QAM/8VSB Frontend",
        .frequency_min        = 54000000,
        .frequency_max        = 858000000,
        .frequency_stepsize    = 62500,
        .caps = FE_CAN_QAM_64 | FE_CAN_QAM_256 | FE_CAN_8VSB
    },
    
#########MODDED#################

    static struct dvb_frontend_ops au8522_ops = {
    .delsys = { SYS_ATSC },
    .info = {
        .name            = "Auvitek AU8522 QAM/8VSB Frontend",
        .frequency_min        = 54000000,
        .frequency_max        = 858000000,
        .frequency_stepsize    = 62500,
        .caps = FE_CAN_8VSB
    },



Re: Octagon SF8008 Wrong USB Tuner ID #9 Dimitrij

  • PLi® Core member
  • 10,020 posts

+338
Excellent

Posted 4 February 2022 - 06:05

CONFIG_MEDIA_TUNER_XC5000=m

GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Octagon SF8008 Wrong USB Tuner ID #10 el bandido

  • Senior Member
  • 364 posts

+13
Neutral

Posted 4 February 2022 - 14:53

CONFIG_MEDIA_TUNER_XC5000=m


sf8008 login: root
root@sf8008:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2X
Name: Si2166D
Has_Outputs: no
Frontend_Device: 0
I2C_Device: 0
NIM Socket 1:
Type: DVB-S2X
Name: Si2166D
Has_Outputs: no
Frontend_Device: 1
I2C_Device: 1
NIM Socket 2:
Type: DVB-C
Name: Auvitek AU8522 QAM/8VSB Frontend
Has_Outputs: no
Frontend_Device: 2
I2C_Device: 2
root@sf8008:~# lsmod
Module                  Size  Used by
au8522_dig              7225  1
au8522_common           4002  1 au8522_dig
8192eu               1262601  0
au0828                 22779  0
tveeprom               12040  1 au0828
ahci_platform           2936  0
hisi_encoder            4121  0
hisi_keys               2792  0
hisi_sci                9592  0
hisi_ir                 4230  0
libahci_platform        6390  1 ahci_platform
libahci                23341  2 libahci_platform,ahci_platform
hi_pmoc                73918  1
hi_vi                  71057  0
hi_sci                 56990  1 hisi_sci
hi_aenc                 7367  0
hi_venc               229263  1
hi_advca              228114  1
hi_png                 24106  0
hi_jpge                22436  0
hi_jpeg                16843  0
hi_dbe                  5734  0
mali                  284125  0
hi_fb                 197689  1
hi_dvb                928477  9
vtunerc                25550  1 hi_dvb
oled                    6203  1 hi_dvb
hi_keyled              79819  3 oled,hisi_keys,hi_dvb
hi_tuner              517464  0
hi_mce                  4402  0
hi_pvr                  4284  0
hi_sync                66760  1
hi_aiao               381932  4
hi_adsp               220281  0
hi_vdec              1251988  1
hi_vpss               400316  0
hi_vfmw              1827881  0
hi_adec                 9236  0
hi_demux              417073  2 hi_dvb
hi_otp                 24944  2 hi_pmoc
hi_tde                112944  0
hi_i2c                 19734  2 hi_tuner,hi_dvb
hi_gpio_i2c            14794  3 hi_tuner,hi_i2c,hi_dvb
hi_gpio                18564  1 hi_dvb
hi_vou               1245286  2
hi_hdmicec              5071  1 hi_dvb
hi_hdmi               900300  3 hi_hdmicec,hi_dvb
hi_cipher             264125  0
hi_pq                1656354  3 hi_vou,hi_vpss
hi_pdm                 25264  0
hi_common              94145  39 mali,hi_fb,hi_pq,hi_vi,hi_cipher,hi_keyled,hi_advca,hi_demux,hi_tuner,hi_i2c,hi_dvb,hi_mce,hi_pdm,hi_otp,hi_png,hi_pvr,hi_sci,hi_tde,hi_vou,hi_adec,hi_adsp,hi_aenc,hi_aiao,hi_hdmi,hi_gpio,hi_jpeg,hi_jpge,hi_pmoc,hi_sync,hi_vdec,hi_venc,hi_vfmw,hi_vpss,hisi_ir,hi_gpio_i2c
hi_mmz                 45984  22 hi_fb,hi_pq,hi_vi,hi_cipher,hi_common,hi_demux,hi_dvb,hi_png,hi_tde,hi_vou,hi_adec,hi_adsp,hi_aenc,hi_aiao,hi_jpeg,hi_jpge,hi_sync,hi_vdec,hi_venc,hi_vfmw,hi_vpss
hi_media                8732  24 hi_common,hi_mmz,hi_png,hi_tde,hi_jpeg,hi_jpge
root@sf8008:~#  dmesg | grep adapter
[    3.742114] virtual DVB adapter driver, version 1.4, © 2010-12 Honza Petrous, SmartImp.cz
[    3.842161] DVB: registering new adapter (nHi)
[    4.052568] DVB: registering adapter 0 frontend 0 (Si2166D)...
[    4.290539] DVB: registering adapter 0 frontend 0 (Si2166D)...
[    7.891298] DVB: registering new adapter (au0828)
[    7.894748] DVB: registering adapter 1 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
[   29.029763] DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
[   70.712766] DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
[  120.582479] DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
[  132.378325] DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
root@sf8008:~#


Attached File  defconfig.zip   27.75KB   1 downloads



Re: Octagon SF8008 Wrong USB Tuner ID #11 Dimitrij

  • PLi® Core member
  • 10,020 posts

+338
Excellent

Posted 4 February 2022 - 17:50

No ideas.

Contact the manufacturer?

By the way, the old versions(7.3) are the same?


GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Octagon SF8008 Wrong USB Tuner ID #12 el bandido

  • Senior Member
  • 364 posts

+13
Neutral

Posted 4 February 2022 - 18:03

Others have contacted the manufacturer with no success. This problem has existed for some time.

Old versions are the same.

I was hoping it might could be fixed by altering a file somewhere, possibly in linux since the tuner works correctly in the PULSe4k.
Thanks..



Re: Octagon SF8008 Wrong USB Tuner ID #13 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 4 February 2022 - 19:56

The WinTV HVR-950 is a hybrid C/T tuner, does it show up in Enigma as such (i.e. do you get the option in the tuner config to switch from DVB-C to DVB-T)?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Octagon SF8008 Wrong USB Tuner ID #14 Dimitrij

  • PLi® Core member
  • 10,020 posts

+338
Excellent

Posted 4 February 2022 - 19:59

The WinTV HVR-950 is a hybrid C/T tuner, does it show up in Enigma as such (i.e. do you get the option in the tuner config to switch from DVB-C to DVB-T)?

 

NIM Socket 2:
Type: DVB-C
Name: Auvitek AU8522 QAM/8VSB Frontend
Has_Outputs: no
Frontend_Device: 2
I2C_Device: 2

 


GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Octagon SF8008 Wrong USB Tuner ID #15 el bandido

  • Senior Member
  • 364 posts

+13
Neutral

Posted 4 February 2022 - 20:38

In the comparisons of the PULSe4K and sf8008, both receivers have a Hauppauge 950Q installed. They are not exactly identical, but are the exact same model. Results are the same if the 950Q tuners are swapped.


It looks like the sf8008 is locked to DVB-C Annex A, which is I think DVB-C for Europe. North American DVB-C I think is DVB-C Annex B. Attached are two screencaps of the SF8008 and PULSe4K 950Q menus.

The two receivers also word the 950Q name different, and the PULSe4K has an indent in the description where the SF8008 does not.
PULSe4K:
NIM Socket 2:
        Type: ATSC
        Name: WinTV HVR-950
        Has_Outputs: no
        Frontend_Device: 2
        I2C_Device: -1
--------------------------------------------------------------
SF8008:
NIM Socket 2:
Type: DVB-C
Name: Auvitek AU8522 QAM/8VSB Frontend
Has_Outputs: no
Frontend_Device: 2

Tuner Menu for SF8008:
Attached File  sf8008-atsc-setup_20220204141342.jpg   80.18KB   1 downloads
Tuner Menu for PULSe4K:
Attached File  pulse4k-atsc-setup_20220204141459.jpg   76.94KB   1 downloads

EDIT: No option to switch from DVB-C to ATSC in either receiver.


Edited by el bandido, 4 February 2022 - 20:47.


Re: Octagon SF8008 Wrong USB Tuner ID #16 el bandido

  • Senior Member
  • 364 posts

+13
Neutral

Posted 4 February 2022 - 20:49

I find the SF8008 tuner name in linux files:

/linux-4.4.35/drivers/media/dvb-frontends/au8522_dig.c
static struct dvb_frontend_ops au8522_ops = {
    .delsys = { SYS_ATSC, SYS_DVBC_ANNEX_B },
    .info = {
        .name            = "Auvitek AU8522 QAM/8VSB Frontend",
        .frequency_min        = 54000000,
        .frequency_max        = 858000000,
        .frequency_stepsize    = 62500,
        .caps = FE_CAN_QAM_64 | FE_CAN_QAM_256 | FE_CAN_8VSB
    },

 
 

 

 



Re: Octagon SF8008 Wrong USB Tuner ID #17 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 4 February 2022 - 21:34

Can you do an lsub and give the USB-ID of the tuner?

 

I see that both the octagon and the abcom BSP have a linux kernel patch for the Haupppage, which explicitly names the HVR-950. But as an EM2883, not as an AU8522.

 

Can you check on the Pulse4K if this is installed?

opkg list-iunstalled | grep em28

It isn't on the SF8008 I have...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Octagon SF8008 Wrong USB Tuner ID #18 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 4 February 2022 - 21:42

The Pulse4K doesn't have

CONFIG_DVB_AU8522=m
CONFIG_DVB_AU8522_DTV=m
CONFIG_DVB_AU8522_V4L=m

which is maybe why it loads the correct driver there.

You can try blacklisting it on the SF8008 by creating /etc/modprobe.d/blacklist and adding "blacklist au8522" to it.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Octagon SF8008 Wrong USB Tuner ID #19 el bandido

  • Senior Member
  • 364 posts

+13
Neutral

Posted 4 February 2022 - 22:10

root@sf8008:~# lsusb
Bus 001 Device 002: ID 05e3:0608
Bus 001 Device 007: ID 0bda:818b
Bus 003 Device 002: ID 0781:5575
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0002
Bus 004 Device 001: ID 1d6b:0003
Bus 001 Device 003: ID 05e3:0608
Bus 001 Device 004: ID 2040:7200 ----->950Q
Bus 001 Device 005: ID 0781:5575
Bus 001 Device 006: ID 090c:1000

root@sf8008:~# opkg list-installed | grep em28
kernel-module-em28xx-4.4.35 - 4.4.35-r1
root@sf8008:~#

root@pulse4k:~# lsusb
Bus 001 Device 002: ID 2040:7200 ---->950Q
Bus 003 Device 002: ID 0781:5575
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0002
Bus 004 Device 001: ID 1d6b:0003
root@pulse4k:~#

root@pulse4k:~# opkg list-installed | grep em28
kernel-module-em28xx-4.4.35 - 4.4.35-r0r0.1
root@pulse4k:~#
Working on the blacklist.
 


Edited by el bandido, 4 February 2022 - 22:12.


Re: Octagon SF8008 Wrong USB Tuner ID #20 WanWizard

  • PLi® Core member
  • 68,614 posts

+1,739
Excellent

Posted 4 February 2022 - 22:14

So it is installed on the Pulse4k, and on the SF8008?

 

Perhaps it's not blacklisting the au8522, but loading the em28xx driver?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users