search

ceton / infinitv_pcie

Linux driver for the Ceton InfiniTV PCIe
15 stars 16 forks source link

dmesg shows "tx timeout" and no data streams from device #14

Closed grummp closed 3 years ago

grummp commented 3 years ago

Not sure if someone else has run into this or perhaps you can point me in the right direction...

I'm trying to switch my main system from Windows to Linux. The Ceton card works fine in Windows, so not likely to be a hardware issue.

The driver compiles fine (with fix for SUBDIRS issue in Makefile or using the JamesRHarris fork). For some reason, "make install" did not work correctly -- it copied the driver into /lib/modules/5.4.75, even though the kernel I'm running is 5.4.0-65. Not sure what that's about, but no big deal, I just moved the .ko to the right place and re-ran depmod. After that, I could modprobe the driver just fine.

According to dmesg, the network device was renamed from ctn0 to enp5s0. And the 192.168.200.1 IP address was not set by default, which I did not expect. The first I understand, but I was kind of expecting the IP address to be set automatically, but perhaps not. The provided instructions suggest I can give it a static IP address, so I assigned 192.168.200.2.

I can ping that IP address, but if I try browsing to that IP, then the connection is refused.

As suggested in the README, I try using mplayer to render the stream. That just hangs with this:

Playing /dev/ceton/ctn91xx_mpeg0_0.
Cache fill:  0.00% (0 bytes)

Likewise with just trying to use cat. No data.

The only clue is a message from dmesg:

[Jan30 16:55] ctn91xx_net_tx_timeout:200 : (0) tx timeout (eth_pend=1, tx_pen=1 recv=1 skb=1 valid=1)
[ +12.031897] ctn91xx_net_tx_timeout:200 : (0) tx timeout (eth_pend=1, tx_pen=1 recv=1 skb=1 valid=1)
[ +11.775712] ctn91xx_net_tx_timeout:200 : (0) tx timeout (eth_pend=1, tx_pen=1 recv=1 skb=1 valid=1)
[  +6.143966] ctn91xx_net_tx_timeout:200 : (0) tx timeout (eth_pend=1, tx_pen=1 recv=1 skb=1 valid=1)

That message repeats forever, every 6 or 12 seconds.

Any ideas on how to debug this issue?

Thanks in advance.

grummp commented 3 years ago

This is no longer an issue. Not sure what fixed it. Maybe a simple reboot...