Aktuelle Treiber für Octopus(ddbridge), CineS2(ngene/ddbridge), DuoFlex-S2, DuoFlex-CT, CineCT sowie TT S2-6400 (Teil 2)

suheyl · 2. Juli 2013

Zitat von UFO

Is anything else connected to the ports of the card?

Please provide the output of 'lspci -vnn'.

Hi. No there is nothing else connected to the card. I have the lspci attached. Thank you for your help!

Falls jemand mich helfen kann, aber nur auf Deutsch, Ich verstehe Deutsch, aber Englisch ist mir einfacher Ich lebe nähe Deutschland auf die Grenze.

UFO · 2. Juli 2013

Zitat von suheyl

Hi. No there is nothing else connected to the card. I have the lspci attached. Thank you for your help!

Zitat

04:00.0 Multimedia controller [0480]: Digital Devices GmbH Octopus LE DVB adapter [dd01:0003]
Subsystem: Digital Devices GmbH Device [dd01:0030]
Flags: bus master, fast devsel, latency 0, IRQ 52
Memory at fcff0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: DDBridge
Kernel modules: ddbridge

Alles anzeigen

Zitat

[ 9.047541] Digital Devices PCIE bridge driver, Copyright (C) 2010-11 Digital Devices GmbH
[ 9.047592] DDBridge driver detected: Digital Devices DVBCT V6.1 DVB adapter
[ 9.047610] HW 0001000d REG 00010004
[ 9.047667] DDBridge 0000:04:00.0: irq 52 for MSI/MSI-X
[ 9.047824] Port 0 (TAB 1): NO MODULE
[ 9.048594] Port 1 (TAB 2): NO MODULE
[ 9.049373] Port 2 (TAB 3): NO MODULE

Alles anzeigen

Looks like a broken card.
Could you re-test it on a different system, if possible on a Windows machine?

CU
Oliver

suheyl · 2. Juli 2013

Zitat von UFO

Looks like tha card is broken.
Could you re-test it on a different system, if possible on a Windows machine?

Hi Oliver,

I've already tried that. The card works fine on Windows 7... It's a brand new card.
I've first installed it on a Windows machine. This did not perform well. I could not get everything intergrated in XBMC on Windows. That's why I reverted to Linux.

UFO · 2. Juli 2013

Zitat von suheyl

Hi Oliver,

I've already tried that. The card works fine on Windows 7... It's a brand new card.

Sorry, I have no idea why the module is not detected.

Maybe it will help if you disable the MSI interrupt for the card.
Change line 70 in v4l/ddbridge-core.c from

Code

/* #undef CONFIG_PCI_MSI */

to

Code

#undef CONFIG_PCI_MSI

Then type

Code

make
make install

Finally reboot the machine.

CU
Oliver

suheyl · 2. Juli 2013

Quellcode
1

/* #undef CONFIG_PCI_MSI */

to

Quellcode
1

#undef CONFIG_PCI_MSI

Unfortunately this didn´t help either. Do I have to install some additional modules, like dvb e.g.?

I'm completely new in Linux, so I'm sorry if I ask "stupid" things...

suheyl · 3. Juli 2013

After mailing several times with Digital Devices support, they promised me to look into the issues with the driver! Finally!

If there are more people complaining about the driver, please make a ticket at http://support.digital-devices.de/
Maybe then the pressure will be bigger to do something about it. They cannot sell useless cards!

UFO · 3. Juli 2013

Zitat von suheyl

If there are more people complaining about the driver, please make a ticket at http://support.digital-devices.de/
Maybe then the pressure will be bigger to do something about it. They cannot sell useless cards!

The cards are not useless and they work fine with this driver.
Otherwise there would be tons of complaints from other users!

My guess is that either
- the card is broken,
- there is a strange compatibility problem, or
- the problem is sitting in front of the computer.

Whatever the problem is, I am really tired of reading your rants.

This driver repository is provided as a service to the community. I am doing this in my spare time, i.e. I am not an employee of Digital Devices. If you do not like this driver or think that you can do better, do not use it!

Oliver

suheyl · 3. Juli 2013

Zitat von UFO

The cards are not useless and they work fine with this driver.
Otherwise there would be tons of complaints from other users!

My guess is that either
- the card is broken,
- there is a strange compatibility problem, or
- the problem is sitting in front of the computer.

Whatever the problem is, I am really tired of reading your rants.

This driver repository is provided as a service to the community. I am doing this in my spare time, i.e. I am not an employee of Digital Devices. If you do not like this driver or think that you can do better, do not use it!

Oliver

Alles anzeigen

Hi Oliver,

I'm sorry. I didn't want to offend you.
I'm just frustrated it's still not working. As I'm a total noob in Linux I don't know where to begin. I just hoped for some official support from the producer.

UFO · 3. Juli 2013

Zitat von suheyl

I'm sorry. I didn't want to offend you.
I'm just frustrated it's still not working. As I'm a total noob in Linux I don't know where to begin. I just hoped for some official support from the producer.

As a noob it is probably better to use a distribution (like yaVDR) which shippes a pre-compiled driver package.
Unfortunately this will not help in case of broken hardware...

Anyway, let's look at the I2C bus and see whether we can identify a problem there.

1) Login as root (or use sudo for all commands below).

2) Install the i2c-tools on your machine.

3) Load I2C helper driver

Code

modprobe i2c-dev

4) Run

Code

i2cdetect -l

and post the result.
Identify the buses used by the ddbridge driver.

5) For each of these buses, run

Code

i2cdetect -y  N

and post the results.
Note that N is the number of the bus (example: 3 for i2c-3).

CU
Oliver

suheyl · 3. Juli 2013

Hi Oliver!

Thanx for your efforts man! I really do appreciate this!

I've first installed this card on the same PC but on WIN7. The card was detected then and I had 67 channels found. But they were, of course, encrytped. I've decided to use XBCMUbuntu because it runs much smoother. More efficient. Except for the tuner

I've installed i2c and here are the results:
As a noob, I find all those "--" kind of alarming... Am I right?

i2cdetect -l

i2c-0 smbus ddbridge SMBus adapter
i2c-1 smbus ddbridge SMBus adapter
i2c-2 smbus ddbridge SMBus adapter

i2cdetect -y

Bus 0

i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Bus 1

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Bus 2

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Because I was curious about the other used buses:
4 buses for my videocard:
i2c-3 i2c NVIDIA i2c adapter 0 at 5:00.0 I2C adapter

result:

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Isn't that weird? That same result is for all four buses. That card is running fine. Or do I misinterpret this?

Cheers man

thedon · 4. Juli 2013

suheyl

That is strange. I have a Digital Device Cine CT V6.1 too and my outputs are:

Code

sysadmin@xbmcbuntu:~$ sudo lspci -vvnn -s 03:00

Code

03:00.0 Multimedia controller [0480]: Digital Devices GmbH Octopus LE DVB adapter [dd01:0003]
	Subsystem: Digital Devices GmbH Device [dd01:0030]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 16 bytes
	Interrupt: pin A routed to IRQ 46
	Region 0: Memory at caef0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [70] MSI: Enable+ Count=1/2 Maskable- 64bit+
		Address: 00000000fee0300c  Data: 41a1
	Capabilities: [90] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 unlimited, L1 <1us
			ClockPM- Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range A, TimeoutDis+
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [100 v1] Vendor Specific Information: ID=0000 Rev=0 Len=00c <?>
	Kernel driver in use: DDBridge
	Kernel modules: ddbridge

Alles anzeigen

Code

sysadmin@xbmcbuntu:~$ dmesg | less

Code

...
[    7.587001] Digital Devices PCIE bridge driver, Copyright (C) 2010-11 Digital Devices GmbH
[    7.587141] DDBridge driver detected: Digital Devices DVBCT V6.1 DVB adapter
[    7.587179] HW 0001000d REG 00010004
[    7.587266] DDBridge 0000:03:00.0: irq 46 for MSI/MSI-X
[    7.590128] Port 0 (TAB 1): DUAL DVB-C/T
[    7.590973] Port 1 (TAB 2): CI
[    7.592776] Port 2 (TAB 3): NO MODULE
[    7.594618] DVB: registering new adapter (DDBridge)
[    7.594624] DVB: registering new adapter (DDBridge)
[    7.594629] DVB: registering new adapter (DDBridge)
...

Alles anzeigen

Code

sysadmin@xbmcbuntu:~$ sudo i2cdetect -l

Code

i2c-0	smbus     	ddbridge                        	SMBus adapter
i2c-1	smbus     	ddbridge                        	SMBus adapter
i2c-2	smbus     	ddbridge                        	SMBus adapter
i2c-3	i2c       	NVIDIA i2c adapter 0 at 5:00.0  	I2C adapter
i2c-4	i2c       	NVIDIA i2c adapter 1 at 5:00.0  	I2C adapter
i2c-5	i2c       	NVIDIA i2c adapter 2 at 5:00.0  	I2C adapter

Code

sysadmin@xbmcbuntu:~$ sudo i2cdetect -y 0

Code

0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- 1e 1f 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

Code

sysadmin@xbmcbuntu:~$ sudo i2cdetect -y 1

Code

0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: 40 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

Code

sysadmin@xbmcbuntu:~$ sudo i2cdetect -y 2

Code

0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

Code

sysadmin@xbmcbuntu:~$ sudo i2cdetect -y 3

Code

0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- 26 -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: 50 51 52 53 -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

UFO · 4. Juli 2013

suheyl
There is not a single device on any of the I2C buses.

thedon
This is the correct output for a working Cine CT with a CI module.
- Two demods at 0x1e and 0x1f.
- CI chip at 0x40.

CU
Oliver

suheyl · 4. Juli 2013

@ Oliver
Which means? That both of the card are not working? But my Nvidia works fine, I thought... I've got a working screen...

Or do I have to install something else? Time to read about it

Thanx Oliver and thedon

thedon · 4. Juli 2013

Hello,

Zitat von suheyl

That both of the card are not working?

Indeed, it is strange that you do not get any output on the nvidia i2c bus. I have made a Testsetup which worked here.

Hardware (it is an ancient one):

Asus P5LD2
Pentium 4@3GHz
1GB
250GB Seagate ST3250820A PATA
NVIDIA Geforce 6600

I installed XMBCbuntu 12.2 Intel-NVIDIA without updates and without 3rd party software during the installation. Then I did the following procedure to get the driver working and tvheadend find them as TV adapters.

Exit XMBC
login with a user on the XBMCbuntu desktop (not on XBMC!)
open a terminal (XTerm)

Update the system:

Code

sudo apt-get update
sudo apt-get dist-upgrade
sudo reboot

The XBMCbuntu desktop is active after the reboot. In a terminal do:

Code

sudo apt-get install mercurial build-essential libproc-processtable-perl
mkdir dvb
cd dvb
hg clone http://linuxtv.org/hg/~endriss/media_build_experimental
cd media_build_experimental
make download
make untar
sudo make

Before installing the new modules, moving the old one to a save place

Code

sudo mv /lib/modules/3.5.0-34-generic/kernel/drivers/media/ ~/media/

Install the modules

Code

sudo make install
sudo reboot

suheyl · 4. Juli 2013

Hi thedon!

Thank you for your efforts!

Here are the outputs:

suheyl@mediacenter:~$ sudo lspci -vvnn -s 04:00
04:00.0 Multimedia controller [0480]: Digital Devices GmbH Octopus LE DVB adapter [dd01:0003]
Subsystem: Digital Devices GmbH Device [dd01:0030]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 52
Region 0: Memory at fcff0000 (64-bit, non-prefetchable)
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [70] MSI: Enable+ Count=1/2 Maskable- 64bit+
Address: 00000000fee3f00c Data: 41b9
Capabilities: [90] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 unlimited, L1 <1us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive - BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range A, TimeoutDis+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v1] Vendor Specific Information: ID=0000 Rev=0 Len=00 c <?>
Kernel driver in use: DDBridge
Kernel modules: ddbridge

dmesg | less

8.408901] Digital Devices PCIE bridge driver, Copyright (C) 2010-11 Digital Devices GmbH
[ 8.408943] DDBridge driver detected: Digital Devices DVBCT V6.1 DVB adapter
[ 8.408962] HW 0001000d REG 00010004
[ 8.409019] DDBridge 0000:04:00.0: irq 52 for MSI/MSI-X
[ 8.409171] Port 0 (TAB 1): NO MODULE
[ 8.409859] Port 1 (TAB 2): NO MODULE
[ 8.410698] Port 2 (TAB 3): NO MODULE
[ 8.606679] microcode: CPU0: patch_level=0x010000bf
[ 8.652157] device-mapper: multipath: version 1.4.0 loaded

sudo i2cdetect -l
i2c-0 smbus ddbridge SMBus adapter
i2c-1 smbus ddbridge SMBus adapter
i2c-2 smbus ddbridge SMBus adapter
i2c-3 i2c NVIDIA i2c adapter 0 at 5:00.0 I2C adapter
i2c-4 i2c NVIDIA i2c adapter 1 at 5:00.0 I2C adapter
i2c-5 i2c NVIDIA i2c adapter 2 at 5:00.0 I2C adapter
i2c-6 i2c NVIDIA i2c adapter 6 at 5:00.0 I2C adapter

sudo i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

sudo i2cdetect -y 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

sudo i2cdetect -y 3
Error: Can't use SMBus Quick Write command on this bus

sudo i2cdetect -y 4
Error: Can't use SMBus Quick Write command on this bus

sudo i2cdetect -y 5
Error: Can't use SMBus Quick Write command on this bus

sudo i2cdetect -y 6
Error: Can't use SMBus Quick Write command on this bus

I think something went wrong with the NVIDIA driver.... I'm reinstalling it now.

But no change at all...

Is there a possibility that I have to install Ubuntu completely? I mean not the XBMCUbuntu version but Ubuntu itself?
I'm going to start all over after work. A clean and fresh install. Let's see what happens then.

thedon · 4. Juli 2013

Zitat von suheyl

Is there a possibility that I have to install Ubuntu completely? I mean not the XBMCUbuntu version but Ubuntu itself?
I'm going to start all over after work. A clean and fresh install. Let's see what happens then.

I have used a fresh XBMCbuntu 12.2 Intel-NVIDIA for my tests and installed it from an USB drive.

Dr. Seltsam · 9. Juli 2013

@ UFO:
ist eine Integration der Treiber in linuxtv bzw. den Kernel eigentlich noch in Arbeit, bzw. wo liegen die Probleme?

suheyl · 9. Juli 2013

Hi all,

I've tried a clean install after updating the BIOS once again. I still get the same result when I do i2cdetect -y 0.

I've read about manually setting these things.
http://www.lm-sensors.org/wiki/i2cToolsDocumentation

What I understand is that I can use the i2cset command. Correct me if I'm wrong.
i2cset <bus> <chip> <register> <value>

So can I use the command like this?

sudo i2cset 0 ddbridge 0x1e 1e
sudo i2cset 0 ddbridge 0x1f 1f
sudo i2cset 1 ddbridge 0x40 40

I found these values in thedon´s post.

UFO · 10. Juli 2013

Zitat von suheyl

I've read about manually setting these things.
http://www.lm-sensors.org/wiki/i2cToolsDocumentation

What I understand is that I can use the i2cset command. Correct me if I'm wrong.
i2cset <bus> <chip> <register> <value>

So can I use the command like this?

sudo i2cset 0 ddbridge 0x1e 1e
sudo i2cset 0 ddbridge 0x1f 1f
sudo i2cset 1 ddbridge 0x40 40

I found these values in thedon´s post.

Alles anzeigen

No, do not do that! Never use i2cset, unless you know what you are doing.

You cannot fix your problem this way.

CU
Oliver

suheyl · 10. Juli 2013

Hi Oliver,

Apparently I don't...

I'm kind of desperate now. Maybe back to Windows 7...

Aktuelle Treiber für Octopus(ddbridge), CineS2(ngene/ddbridge), DuoFlex-S2, DuoFlex-CT, CineCT sowie TT S2-6400 (Teil 2)

Jetzt mitmachen!

Teilen

Tags