pcHDTV :: View topic - HD-5500 2.6.18.6 Kernel Oops

kbocek

I'm attempting to install a HD-5500 on an SMP host under 2.6.18.6. I'm using the drivers that came with the 2.6.18.6 source. Doing anything causes a crash:

$ dtvscan /dev/video
dtvscan for kernel 2.6.18 - by Jack Kelliher (c) 2002,2005,2006
Attempting to open /dev/video
channel = 2
# CHANNEL 2 ###### signal = 100
Signal: 04 ####
look for sync
Can't find synca) 63
entry {
majorchannelnumber = 2;
minorchannelnumber = 1;
stationchannel = 2;
stationidentifier = unknown;
programnumber = 2;
disabled = 1;
};
channel = 3
# CHANNEL 3 ###### signal = 100
Signal: 04 ####
look for sync
Can't find synca) 140
entry {
majorchannelnumber = 3;
minorchannelnumber = 1;
stationchannel = 3;
stationidentifier = unknown;
programnumber = 2;
disabled = 1;
};
channel = 4
# CHANNEL 4 ###### signal = 100
Signal: 04 ####
look for sync
Can't find synca) 82
entry {
majorchannelnumber = 4;
minorchannelnumber = 1;
stationchannel = 4;
stationidentifier = unknown;
programnumber = 2;
disabled = 1;
};
channel = 5
# CHANNEL 5 ###### signal = 100
Signal: 04 ####
look for sync
Can't find synca) 65
entry {
majorchannelnumber = 5;
minorchannelnumber = 1;
stationchannel = 5;
stationidentifier = unknown;
programnumber = 2;
disabled = 1;
};
channel = 6
# CHANNEL 6 ###### signal = 100
Signal: 04 ####
look for sync
Can't find synca) 56
entry {
majorchannelnumber = 6;
minorchannelnumber = 1;
stationchannel = 6;
stationidentifier = unknown;
programnumber = 2;
disabled = 1;
};
channel = 7
channel = 8
channel = 9
# CHANNEL 9 ###### signal = 100
Signal: 04 ####
look for sync
Killednc byte (a) 0

Yeilding this message on the terminal:

Message from syslogd@beryl at Thu Jan 11 12:05:24 2007 ...
beryl kernel: Oops: 0000 [5] SMP

Message from syslogd@beryl at Thu Jan 11 12:05:24 2007 ...
beryl kernel: CR2: ffff80ff0568f458

And this to the ring buffer:

$ dmesg
Unable to handle kernel paging request at ffff80ff0568f458 RIP:
[<ffffffff802fb6d6>] sync_single+0x1d/0x7e
PGD 0
Oops: 0000 [5] SMP
CPU 0
Modules linked in: nfsd exportfs lockd nfs_acl parport_pc lp parport autofs4 tun sunrpc ipmi_devintf ipmi_si ipmi_msghandler xt_state xt_tcpudp iptable_filter iptable_nat ip_nat ip_conntrack nfnetlink ip_tables x_tables tsdev joydev xfs video button battery asus_acpi ac usb_storage uhci_hcd ehci_hcd cx88_alsa snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc cx88_blackbird cx8802 cx2341x tuner cx8800 cx88xx ir_common i2c_algo_bit video_buf tveeprom compat_ioctl32 btcx_risc videodev v4l1_compat v4l2_common i2c_i801 i2c_core shpchp via_rhine e1000 floppy dm_snapshot dm_zero dm_mirror ext3 jbd dm_mod 3w_9xxx sd_mod scsi_mod
Pid: 28737, comm: dtvscan Not tainted 2.6.18.6smp-beryl-04 #1
<SNIP>

Can anyone shed any light on this?

Thanks,
Kirk Bocek

kbocek

I'm slowly figuring out some of this myself.

First, I'm not sure dtvscan should be used on /dev/videoX. That device is for the standard channels. I *think* dtvscan is only for the HD channels.

Next, CentOS 4.4 was loading the cx8800 driver but *not* the cx88-dvb driver which is needed for the HD channels. Once I loaded it manually, I *think* that fixed my Oops problem.

Now if I can figure out how to get the HD channel I think Astound cable is broadcasting.