I discovered something new on my old server running Linux Mint, where everything works properly:

The USB sticks are detected the same way, regardless of their ID.

Bus 001 Device 005: ID 2013:0258 PCTV Systems PCTV 461

Bus 001 Device 006: ID 2013:0462 PCTV Systems PCTV 461

On the system running Unraid, however, the two sticks are detected differently.
Bus 001 Device 003 Port 1-6 ID 2013:0258 PCTV Systems DVB-S2 Stick 461e

Bus 001 Device 006 Port 1-1 ID 2013:0462 PCTV Systems PCTV 461

They are probably different hardware revisions.

On the Linux Mint system, all sticks work regardless of the revision.

Under Unraid, only the 461e works, but I have no idea why.

So now to clarify. Stick 461e works with unraid but Stick 461 not.
No Idea why and where are the different.
But maybe we can't find together I way to figure out the reason for this.

I run now Unraid 7.2.3

Edited January 8Jan 8 by Ballzauber

Hello guys,

I’m having an issue with the DVB plugin on Unraid, as my DVB card is not starting correctly.

I’m running Unraid 6.12.10 with the DVB plugin and a Digital Devices Max M2 card.

The PCI device is detected correctly:

• 0a:00.0 Multimedia controller [0480]: Digital Devices GmbH Device [dd01:0025]

• Subsystem: [dd01:0054]

Current behavior:

• the ddbridge module loads successfully

• the device can be bound to ddbridge

• /dev/ddbridge/card0 exists

• but no /dev/dvb devices are created

Logs:

• ddbridge 0000:0a:00.0: unknown Digital Devices device, install newer driver

• ddbridge 0000:0a:00.0: HW 00000136 REGMAP 00010004 FW 0.310

• ddbridge 0000:0a:00.0: link 0 vendor dd01 device 0025 subvendor ffff subdevice 0054

• ddbridge 0000:0a:00.0: 0 netstream channels

Also, the following command returns no match:

• modinfo ddbridge | grep -i '^alias:.*dd01.*0025'

Is this behavior resolved in Unraid 7 and the newer DVB plugin version?

Thank you very much for your help.

EDIT:

Forgot to attach the diagnostics file

Edited February 27Feb 27 by Denisio

27 minutes ago, Denisio said:

I’m running Unraid 6.12.10 with the DVB plugin and a Digital Devices Max M2 card.

Please upgrade to 7.2.4, otherwise you won't get a newer driver.

I'm trying to add TBS5530 to TVheadend in unraid, passthrough USB device as instructed, i can see the device, but no results when scanning.

I then installed DVB viewer to another PC under windows and connected TBS device and it picks up channels fine. So something is wrong in Unraid, I also noticed green light in TBS device for "Locked" doesnot power on when scanning under UNRAID but does every time when scanning frequencies in windows.

can someone help me please?

12 hours ago, Gayanll said:

can someone help me please?

I think this is more of an issue with TVHeadend or the configuration since the card is detected and in a working state, otherwise it wouldn't be detected at all, however you can post your Diagnostics and I look through the files if there is something missing but even if there would be something missing the card wouldn't be detected usually.

I also can't help with ISDB-T since we don't have that standard over here, however as said, it seems like some other configuration issue or an issue with TVHeadend.

1 hour ago, ich777 said:

I think this is more of an issue with TVHeadend or the configuration since the card is detected and in a working state, otherwise it wouldn't be detected at all, however you can post your Diagnostics and I look through the files if there is something missing but even if there would be something missing the card wouldn't be detected usually.

I also can't help with ISDB-T since we don't have that standard over here, however as said, it seems like some other configuration issue or an issue with TVHeadend.

Thanks, so Card is properly installed. i will check with TVH forum then.

On 4/2/2026 at 12:08 PM, ich777 said:

I think this is more of an issue with TVHeadend or the configuration since the card is detected and in a working state, otherwise it wouldn't be detected at all, however you can post your Diagnostics and I look through the files if there is something missing but even if there would be something missing the card wouldn't be detected usually.

I also can't help with ISDB-T since we don't have that standard over here, however as said, it seems like some other configuration issue or an issue with TVHeadend.

I checked with TVheadend and TBS5530 works perfectly in a separate Linux machine running TVheadend. So it must be a driver communication issue. I noticed my plugin page also shows like below.

I Have attached Diagnostic Zip file you requested too.

unraid-diagnostics-20260410-1420.zip

12 minutes ago, Gayanll said:

I Have attached Diagnostic Zip file you requested too.

I see that in your log, it mentions an overcurrent:

Apr 8 19:00:42 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in cold state, will try to load a firmware

Apr 8 19:00:42 Unraid kernel: dvb-usb: downloading firmware from file 'dvb-usb-id5530.fw'

Apr 8 19:00:42 Unraid kernel: tbs5530: start downloading tbs5530 firmware

Apr 8 19:00:42 Unraid kernel: usb 1-2: USB disconnect, device number 4

Apr 8 19:00:43 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in warm state.

Apr 8 19:00:43 Unraid kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.

### [PREVIOUS LINE REPEATED 1 TIMES] ###

Apr 8 19:00:43 Unraid kernel: dvbdev: DVB: registering new adapter (TurboSight TBS 5530)

Apr 8 19:00:43 Unraid kernel: tbs5530: read eeprom failed.

Apr 8 19:00:43 Unraid kernel: dvb-usb: MAC address reading failed.

Apr 8 19:00:43 Unraid kernel: i2c i2c-8: cxd2878:Can not detect the chip.

Apr 8 19:00:43 Unraid kernel: i2c i2c-8: cxd2878:error attaching frontend.

Apr 8 19:00:43 Unraid kernel: dvb-usb: no frontend was attached by 'TurboSight TBS 5530'

Apr 8 19:00:43 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully initialized and connected.

Apr 8 19:00:43 Unraid kernel: usbcore: registered new interface driver tbs5530

Apr 8 19:00:43 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully deinitialized and disconnected.

Apr 8 19:00:44 Unraid kernel: usb 1-2: new high-speed USB device number 5 using xhci_hcd

Apr 8 19:00:44 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in cold state, will try to load a firmware

Apr 8 19:00:44 Unraid kernel: dvb-usb: downloading firmware from file 'dvb-usb-id5530.fw'

Apr 8 19:00:44 Unraid kernel: tbs5530: start downloading tbs5530 firmware

Apr 8 19:00:44 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in warm state.

Apr 8 19:00:44 Unraid kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.

### [PREVIOUS LINE REPEATED 1 TIMES] ###

Apr 8 19:00:44 Unraid kernel: dvbdev: DVB: registering new adapter (TurboSight TBS 5530)

Apr 8 19:00:45 Unraid kernel: dvb-usb: MAC address: 00:22:ab:c0:7c:c7

Apr 8 19:00:45 Unraid kernel: i2c i2c-8: Detect CXD2878/CXD6822(SiP2) chip.

Apr 8 19:00:45 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 0 (TurboSight TBS 5530 DVB-T/T2/C/C2,ISDB-T/C,ATSC,J83B)...

Apr 8 19:00:45 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in cold state

Apr 8 19:00:45 Unraid kernel: i2c i2c-8: downloading firmware from file 'dvb-demod-m88rs6060.fw'

Apr 8 19:00:46 Unraid kernel: e1000e 0000:01:00.0 eth1: NIC Link is Down

Apr 8 19:00:46 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in warm state

Apr 8 19:00:46 Unraid kernel: i2c i2c-8: firmware version:30

Apr 8 19:00:46 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 1 (TurboSight TBS 5530 DVB-S/S2/S2X)...

Apr 8 19:00:46 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully initialized and connected.
Apr 8 22:55:27 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 0 (TurboSight TBS 5530 DVB-T/T2/C/C2,ISDB-T/C,ATSC,J83B)...

Apr 8 22:55:28 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in cold state

Apr 8 22:55:28 Unraid kernel: i2c i2c-8: downloading firmware from file 'dvb-demod-m88rs6060.fw'

Apr 8 22:55:29 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in warm state

Apr 8 22:55:29 Unraid kernel: i2c i2c-8: firmware version:30

Apr 8 22:55:29 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 1 (TurboSight TBS 5530 DVB-S/S2/S2X)...

Apr 8 22:55:29 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully initialized and connected.

Apr 8 22:59:52 Unraid kernel: usb usb2-port1: over-current condition

In your testing was the USB TV Tuner connected to the same USB Port?

You also have a lot of that in your log:

Apr 10 09:01:49 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:01:49 Unraid kernel: usb usb1-port10: over-current condition

Apr 10 09:01:49 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:01:50 Unraid kernel: usb usb1-port10: over-current condition

### [PREVIOUS LINE REPEATED 5 TIMES] ###

Apr 10 09:01:50 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:01:51 Unraid kernel: usb usb1-port10: over-current condition

Apr 10 09:01:51 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:01:52 Unraid kernel: usb usb1-port10: over-current condition

Apr 10 09:01:52 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:01:52 Unraid kernel: usb usb1-port10: over-current condition

### [PREVIOUS LINE REPEATED 1 TIMES] ###

Apr 10 09:01:53 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:02:15 Unraid kernel: usb usb1-port10: over-current condition

Apr 10 09:02:15 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:02:15 Unraid kernel: usb usb1-port10: over-current condition

### [PREVIOUS LINE REPEATED 4 TIMES] ###

Apr 10 09:02:16 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:02:17 Unraid kernel: usb usb1-port10: over-current condition

Apr 10 09:02:17 Unraid kernel: usb usb2-port1: over-current condition

1 hour ago, ich777 said:

I see that in your log, it mentions an overcurrent:

Apr 8 19:00:42 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in cold state, will try to load a firmware

Apr 8 19:00:42 Unraid kernel: dvb-usb: downloading firmware from file 'dvb-usb-id5530.fw'

Apr 8 19:00:42 Unraid kernel: tbs5530: start downloading tbs5530 firmware

Apr 8 19:00:42 Unraid kernel: usb 1-2: USB disconnect, device number 4

Apr 8 19:00:43 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in warm state.

Apr 8 19:00:43 Unraid kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.

### [PREVIOUS LINE REPEATED 1 TIMES] ###

Apr 8 19:00:43 Unraid kernel: dvbdev: DVB: registering new adapter (TurboSight TBS 5530)

Apr 8 19:00:43 Unraid kernel: tbs5530: read eeprom failed.

Apr 8 19:00:43 Unraid kernel: dvb-usb: MAC address reading failed.

Apr 8 19:00:43 Unraid kernel: i2c i2c-8: cxd2878:Can not detect the chip.

Apr 8 19:00:43 Unraid kernel: i2c i2c-8: cxd2878:error attaching frontend.

Apr 8 19:00:43 Unraid kernel: dvb-usb: no frontend was attached by 'TurboSight TBS 5530'

Apr 8 19:00:43 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully initialized and connected.

Apr 8 19:00:43 Unraid kernel: usbcore: registered new interface driver tbs5530

Apr 8 19:00:43 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully deinitialized and disconnected.

Apr 8 19:00:44 Unraid kernel: usb 1-2: new high-speed USB device number 5 using xhci_hcd

Apr 8 19:00:44 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in cold state, will try to load a firmware

Apr 8 19:00:44 Unraid kernel: dvb-usb: downloading firmware from file 'dvb-usb-id5530.fw'

Apr 8 19:00:44 Unraid kernel: tbs5530: start downloading tbs5530 firmware

Apr 8 19:00:44 Unraid kernel: dvb-usb: found a 'TurboSight TBS 5530' in warm state.

Apr 8 19:00:44 Unraid kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.

### [PREVIOUS LINE REPEATED 1 TIMES] ###

Apr 8 19:00:44 Unraid kernel: dvbdev: DVB: registering new adapter (TurboSight TBS 5530)

Apr 8 19:00:45 Unraid kernel: dvb-usb: MAC address: 00:22:ab:c0:7c:c7

Apr 8 19:00:45 Unraid kernel: i2c i2c-8: Detect CXD2878/CXD6822(SiP2) chip.

Apr 8 19:00:45 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 0 (TurboSight TBS 5530 DVB-T/T2/C/C2,ISDB-T/C,ATSC,J83B)...

Apr 8 19:00:45 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in cold state

Apr 8 19:00:45 Unraid kernel: i2c i2c-8: downloading firmware from file 'dvb-demod-m88rs6060.fw'

Apr 8 19:00:46 Unraid kernel: e1000e 0000:01:00.0 eth1: NIC Link is Down

Apr 8 19:00:46 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in warm state

Apr 8 19:00:46 Unraid kernel: i2c i2c-8: firmware version:30

Apr 8 19:00:46 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 1 (TurboSight TBS 5530 DVB-S/S2/S2X)...

Apr 8 19:00:46 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully initialized and connected.
Apr 8 22:55:27 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 0 (TurboSight TBS 5530 DVB-T/T2/C/C2,ISDB-T/C,ATSC,J83B)...

Apr 8 22:55:28 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in cold state

Apr 8 22:55:28 Unraid kernel: i2c i2c-8: downloading firmware from file 'dvb-demod-m88rs6060.fw'

Apr 8 22:55:29 Unraid kernel: i2c i2c-8: found a 'Montage m88rs6060' in warm state

Apr 8 22:55:29 Unraid kernel: i2c i2c-8: firmware version:30

Apr 8 22:55:29 Unraid kernel: usb 1-2: DVB: registering adapter 0 frontend 1 (TurboSight TBS 5530 DVB-S/S2/S2X)...

Apr 8 22:55:29 Unraid kernel: dvb-usb: TurboSight TBS 5530 successfully initialized and connected.

Apr 8 22:59:52 Unraid kernel: usb usb2-port1: over-current condition

In your testing was the USB TV Tuner connected to the same USB Port?

You also have a lot of that in your log:

Apr 10 09:01:49 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:01:49 Unraid kernel: usb usb1-port10: over-current condition

Apr 10 09:01:49 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:01:50 Unraid kernel: usb usb1-port10: over-current condition

### [PREVIOUS LINE REPEATED 5 TIMES] ###

Apr 10 09:01:50 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:01:51 Unraid kernel: usb usb1-port10: over-current condition

Apr 10 09:01:51 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:01:52 Unraid kernel: usb usb1-port10: over-current condition

Apr 10 09:01:52 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:01:52 Unraid kernel: usb usb1-port10: over-current condition

### [PREVIOUS LINE REPEATED 1 TIMES] ###

Apr 10 09:01:53 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:02:15 Unraid kernel: usb usb1-port10: over-current condition

Apr 10 09:02:15 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:02:15 Unraid kernel: usb usb1-port10: over-current condition

### [PREVIOUS LINE REPEATED 4 TIMES] ###

Apr 10 09:02:16 Unraid kernel: usb usb2-port1: over-current condition

Apr 10 09:02:17 Unraid kernel: usb usb1-port10: over-current condition

Apr 10 09:02:17 Unraid kernel: usb usb2-port1: over-current condition

Yes its connected to USB port of the UNRAID PC. I dont see a reason to show over current, USB Tuner is not even powered by external power adapter, just by USB power.

Try another USB port, this one might be damaged/have dirt in it that creates a short.

Edited April 10Apr 10 by Kilrah

Ok i changed, and restarted. Now USB Tuner is detected.

But still cannot search for channels, scan fails.

1 minute ago, Gayanll said:

But still cannot search for channels, scan fails.

Sorry but this is not really helpful, no Diagnostics, no logs, nothing... Don't know what to tell you other than:

I think that might be a configuration issue in TVHeadend when the tuner is detected and scan fails (at least that's most of the times the issue).

1 hour ago, Gayanll said:

Yes its connected to USB port of the UNRAID PC. I dont see a reason to show over current, USB Tuner is not even powered by external power adapter, just by USB power.

That was probably the error because it was drawing to much current from the USB Port and therefore it was reset by the system, some controllers are a bit more sensible to over current protection than others.

Hello, I m experiencing some issues with my digital devices tunners. I have a cine ct v6 + duoflex ct setup.

Since this morning the cine ct tunners are no longer visible in tvhedend.

The syslog has these errors :

May  5 19:30:33 blitz kernel: ddbridge 0000:01:00.0: I2C bus error
May  5 19:30:33 blitz kernel: ddbridge 0000:01:00.0: I2C bus error
May  5 19:30:33 blitz kernel: ddbridge 0000:01:00.0: I2C bus error
May  5 19:30:33 blitz kernel: ddbridge 0000:01:00.0: I2C bus error
May  5 19:30:33 blitz kernel: ddbridge 0000:01:00.0: I2C bus error
May  5 19:30:33 blitz kernel: ddbridge 0000:01:00.0: I2C bus error
May  5 19:30:33 blitz kernel: ddbridge 0000:01:00.0: I2C bus error
May  5 19:30:33 blitz kernel: ddbridge 0000:01:00.0: I2C bus error

I was on unraid 6.12 and now I went to 7.2.5 and the error is still there.

I tried adding the "ddbridge.msi=0" as was mentioned at the start of this thread and the error persists.

Myabe somebody has has a similar issue ?

4 hours ago, suyac said:

I tried adding the "ddbridge.msi=0" as was mentioned at the start of this thread and the error persists.

This is sometimes an issue with the FPGA which doesn't reset properly and was reported a few times in this thread and not only DigitalDevices cards are affected.

To solve your issue please do the following:

1. Shutdown your server

2. Pull the power plug from the wall

3. Press the power and reset button a few times (to empty the caps)

4. Wait for at least 1 minute

5. Plug the server back in

6. Start the server

15 hours ago, ich777 said:

This is sometimes an issue with the FPGA which doesn't reset properly and was reported a few times in this thread and not only DigitalDevices cards are affected.

To solve your issue please do the following:

1. Shutdown your server

2. Pull the power plug from the wall

3. Press the power and reset button a few times (to empty the caps)

4. Wait for at least 1 minute

5. Plug the server back in

6. Start the server

This fixed the issue, many thanks for your help !

The Plugin Update Helper said i should visit this thread to avoid plugin issues.

What to do now?

2 hours ago, sonic6 said:

The Plugin Update Helper said i should visit this thread to avoid plugin issues.

What to do now?

TBS seems to have not made their drivers compatible with the latest LTS Kernel, the are only supporting up to Kernel version 6.14.x currently.

Please try the LibreELEC drivers for now and see if they work with your Card.

On 5/13/2026 at 6:48 PM, ich777 said:

TBS seems to have not made their drivers compatible with the latest LTS Kernel, the are only supporting up to Kernel version 6.14.x currently.

Please try the LibreELEC drivers for now and see if they work with your Card.

Hi,

I have the same problem. I switched to the LibreELEC Drivers, but that doest't seem to work.

lspci -v
07:00.0 Multimedia controller: TBS Technologies DVB Tuner PCIe Card
Subsystem: Device 6904:0020
Flags: fast devsel, IRQ 5, IOMMU group 15
Memory at f7100000 (32-bit, non-prefetchable) [disabled] [size=256K]
Capabilities: [50] Power Management version 3
Capabilities: [70] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [90] Express Endpoint, IntMsgNum 0
Capabilities: [100] Device Serial Number 00-00-00-00-00-00-00-00

So, I just can go back to Unraid 7.2.6, until the release of new drivers. Do I have any other options?

34 minutes ago, Redskyer said:

I have the same problem. I switched to the LibreELEC Drivers, but that doest't seem to work.

Yes, TBS doesn't work with the newest LTS Kernel which Unraid is using, I would strongly recommend that you write a mail to the listed email address here:
https://github.com/tbsdtv/linux_media/wiki#support

and ask when they plan to support 6.18.x

There it listens even that the driver is only compatible with Linux v4.19-6.14 however from what they've said they will support the latest LTS Kernels which they currently don't (please also do keep in mind 6.14 was never a LTS Kernel so I'm not 100% sure what's going on there.

EDIT: Forgot to say, the LibreELEC drivers support a wide range from DVB Adapters (even TBS ones) but not all.

7 minutes ago, ich777 said:

Yes, TBS doesn't work with the newest LTS Kernel which Unraid is using, I would strongly recommend that you write a mail to the listed email address here:
https://github.com/tbsdtv/linux_media/wiki#support

and ask when they plan to support 6.18.x

There it listens even that the driver is only compatible with Linux v4.19-6.14 however from what they've said they will support the latest LTS Kernels which they currently don't (please also do keep in mind 6.14 was never a LTS Kernel so I'm not 100% sure what's going on there.

Thanks for the advice, I wrote an email to the support and will post the answer from the support here.

EDIT: Forgot to say, the LibreELEC drivers support a wide range from DVB Adapters (even TBS ones) but not all.

It seems that my card "DVB-S2X/-S Quad-Tuner TV-Card PCIe" isn't supported ☹️

There is a new installation method reported at https://github.com/tbsdtv/linux_media/issues/424

curl -sSf https://www.tbsdtv.com/download/document/linux/drv-tbs.sh | sh

The actual latest driver is downloaded from another source within the script. Could this driver packaged with you plugin somehow?

Did anyone test it on unraid?

23 minutes ago, enabler said:

There is a new installation method reported at https://github.com/tbsdtv/linux_media/issues/424

curl -sSf https://www.tbsdtv.com/download/document/linux/drv-tbs.sh | sh

The actual latest driver is downloaded from another source within the script. Could this driver packaged with you plugin somehow?

Did anyone test it on unraid?

I know about that method but have you actually looked into who the domain owns?

I'm not too sure if this is an official link from TBS, I would be very cautious with such scripts since you'll never know what it does and even more because this is a driver an you'll never know what's inside the driver since it has whole system access.

Also, TBS doesn't even list that on their homepage.

I would rather like to have confirmation from TBS that this is the new official method for installing the drivers.

Please don't get me wrong, if this is the new official method I'm more than happy to compile the drivers.

I am also suspicious about it. I did write an email to TBS asking for official 6.18.x support.

6 minutes ago, enabler said:

I am also suspicious about it. I did write an email to TBS asking for official 6.18.x support.

No worries, I just found out that you actually have to click help center, I'm currently in the process of creating the packages, please give me about 30 minutes and the TBS package should be compiled for 7.3.0 and 7.2.6

20 hours ago, ich777 said:

No te preocupes, acabo de descubrir que tienes que hacer clic en el centro de ayuda. Actualmente estoy creando los paquetes; dame unos 30 minutos y el paquete TBS debería estar compilado para las versiones 7.3.0 y 7.2.6.

Hi, I'm having the same problem as you with the new update. I wrote to technical support and this is what they replied:

Hello 

for the kernel 6.18.x , please use this command to install the drivers(with the root permission)

curl -sSf https://www.tbsdtv.com/download/document/linux/drv-tbs.sh | sh