Mailing List Archive

Andy Walls wrote:

On Sun, 2009-04-12 at 10:17 -0600, Ronal B Morse wrote:

I haven't seen any similar reports in the archives, but my Hauppauge HVR1600 does not produce usable output with mplayer or VLC in Ubuntu Linux (9.04 beta/2.6.28-11 amd64) until after I have used the card in a Windows XP session with Hauppague's WinTV software. Booting straight to Linux from a power off state results in a black screen and no audio from both players. ivti-tune and v4l2-ctl set--frequency both produce normal output and indicate the card has been set to the proper channel/frequency (3/61.125) DMSG and the kernel logs appear to be nominal. I don't see any obvious errors. lsmod indicates all of the required modules are loaded. The only anomaly I see is that v4l2-ctl --all indicates signal strength is 0, which is consistent with what I see from mplayer. If I command a system restart and boot into Windows XP, or boot directly into XP from a power off condition, the card works fine with the Hauppauge WinTV software. After I do that, I can command a system restart and boot into Linux and the card then works as expected. v4l2-ctl --all indicates signal strength of 100%. It seems that Ubuntu isn't initializing something on startup, but once whatever it is gets set it persists through a warm reboot. I'm really trying to avoid XP as much as possible and would appreciate any suggestions on how I might make the card work when I boot straight to Ubuntu.

What version of the cx18 driver does your distro have? $ /sbin/modinfo cx18 filename: /lib/modules/2.6.27.9-159.fc10.x86_64/kernel/drivers/media/video/cx18/cx18.ko version: 1.1.0 license: GPL description: CX23418 driver Versions earlier than 1.0.4 won't work reliably. If you have an early version, follow the steps here to get the latest: http://www.ivtvdriver.org/index.php/Cx18#Obtaining_the_driver"]http://www.ivtvdriver.org/index.php/Cx18#Obtaining_the_driver If you do have a v1.0.4 or later version of the driver, please ensure you have the firmware files: http://dl.ivtvdriver.org/ivtv/firmware/cx18-firmware.tar.gz"]http://dl.ivtvdriver.org/ivtv/firmware/cx18-firmware.tar.gz untarred and stored in the directory in which your distribution expects them. If all that is OK. Try $ sudo /sbin/modprobe -r cx18 $ sudo /sbin/modporbe cx18 debug=15 And send the logs from module load to after the start of the first capture.

Thank you. I had the 1.0.1 driver installed, have updated to 1.1.0 as per the link you were kind enough to provide. I can't power the machine down right now, but we'll see if that fixes what ailed it.

Ron Morse

On Sun, 2009-04-12 at 10:17 -0600, Ronal B Morse wrote:
> I haven't seen any similar reports in the archives, but my Hauppauge
> HVR1600 does not produce usable output with mplayer or VLC in Ubuntu
> Linux (9.04 beta/2.6.28-11 amd64) until after I have used the card in a
> Windows XP session with Hauppague's WinTV software.
>
> Booting straight to Linux from a power off state results in a black
> screen and no audio from both players. ivti-tune and v4l2-ctl
> set--frequency both produce normal output and indicate the card has been
> set to the proper channel/frequency (3/61.125)
>
> DMSG and the kernel logs appear to be nominal. I don't see any obvious
> errors.
>
> lsmod indicates all of the required modules are loaded.
>
> The only anomaly I see is that v4l2-ctl --all indicates signal strength
> is 0, which is consistent with what I see from mplayer.
>
> If I command a system restart and boot into Windows XP, or boot directly
> into XP from a power off condition, the card works fine with the
> Hauppauge WinTV software. After I do that, I can command a system
> restart and boot into Linux and the card then works as expected.
> v4l2-ctl --all indicates signal strength of 100%.
>
> It seems that Ubuntu isn't initializing something on startup, but once
> whatever it is gets set it persists through a warm reboot.
>
> I'm really trying to avoid XP as much as possible and would appreciate
> any suggestions on how I might make the card work when I boot straight
> to Ubuntu.

What version of the cx18 driver does your distro have?

$ /sbin/modinfo cx18
filename: /lib/modules/2.6.27.9-159.fc10.x86_64/kernel/drivers/media/video/cx18/cx18.ko
version: 1.1.0
license: GPL
description: CX23418 driver


Versions earlier than 1.0.4 won't work reliably. If you have an early
version, follow the steps here to get the latest:

http://www.ivtvdriver.org/index.php/Cx18#Obtaining_the_driver


If you do have a v1.0.4 or later version of the driver, please ensure
you have the firmware files:

http://dl.ivtvdriver.org/ivtv/firmware/cx18-firmware.tar.gz

untarred and stored in the directory in which your distribution expects
them.


If all that is OK. Try

$ sudo /sbin/modprobe -r cx18
$ sudo /sbin/modporbe cx18 debug=15

And send the logs from module load to after the start of the first
capture.


Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Andy Walls wrote:

On Sun, 2009-04-12 at 10:17 -0600, Ronal B Morse wrote:

I haven't seen any similar reports in the archives, but my Hauppauge HVR1600 does not produce usable output with mplayer or VLC in Ubuntu Linux (9.04 beta/2.6.28-11 amd64) until after I have used the card in a Windows XP session with Hauppague's WinTV software. Booting straight to Linux from a power off state results in a black screen and no audio from both players. ivti-tune and v4l2-ctl set--frequency both produce normal output and indicate the card has been set to the proper channel/frequency (3/61.125) DMSG and the kernel logs appear to be nominal. I don't see any obvious errors. lsmod indicates all of the required modules are loaded. The only anomaly I see is that v4l2-ctl --all indicates signal strength is 0, which is consistent with what I see from mplayer. If I command a system restart and boot into Windows XP, or boot directly into XP from a power off condition, the card works fine with the Hauppauge WinTV software. After I do that, I can command a system restart and boot into Linux and the card then works as expected. v4l2-ctl --all indicates signal strength of 100%. It seems that Ubuntu isn't initializing something on startup, but once whatever it is gets set it persists through a warm reboot. I'm really trying to avoid XP as much as possible and would appreciate any suggestions on how I might make the card work when I boot straight to Ubuntu.

What version of the cx18 driver does your distro have? $ /sbin/modinfo cx18 filename: /lib/modules/2.6.27.9-159.fc10.x86_64/kernel/drivers/media/video/cx18/cx18.ko version: 1.1.0 license: GPL description: CX23418 driver Versions earlier than 1.0.4 won't work reliably. If you have an early version, follow the steps here to get the latest: http://www.ivtvdriver.org/index.php/Cx18#Obtaining_the_driver"]http://www.ivtvdriver.org/index.php/Cx18#Obtaining_the_driver If you do have a v1.0.4 or later version of the driver, please ensure you have the firmware files: http://dl.ivtvdriver.org/ivtv/firmware/cx18-firmware.tar.gz"]http://dl.ivtvdriver.org/ivtv/firmware/cx18-firmware.tar.gz untarred and stored in the directory in which your distribution expects them. If all that is OK. Try $ sudo /sbin/modprobe -r cx18 $ sudo /sbin/modporbe cx18 debug=15 And send the logs from module load to after the start of the first capture. Regards, Andy _______________________________________________ ivtv-users mailing list ivtv-users@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-users"]http://ivtvdriver.org/mailman/listinfo/ivtv-users

Hi Andrew.

I shut the machine down for about three hours. When I brought it up again, directly into Ubuntu, instead of a black screen with no audio I got a nice red screen with no audio. Unloading and reloading the module as you requested results in a working installation. Odd.

Here's the log from the session where I unload then reload the cx18 module. The two warnings at the end of the log are new to me.

Apr 12 20:09:03 jaunty64 kernel: [ 320.837288] cx18-0: unregister DVB
Apr 12 20:09:03 jaunty64 kernel: [ 320.839472] tuner-simple 1-0061: destroying instance
Apr 12 20:09:03 jaunty64 kernel: [ 320.839498] tda9887 1-0043: destroying instance
Apr 12 20:09:03 jaunty64 kernel: [ 320.839919] cx18 0000:05:01.0: PCI INT A disabled
Apr 12 20:09:03 jaunty64 kernel: [ 320.839921] cx18-0: Removed Hauppauge HVR-1600
Apr 12 20:09:21 jaunty64 kernel: [ 339.327128] cx18: Start initialization, version 1.1.0
Apr 12 20:09:21 jaunty64 kernel: [ 339.327163] cx18-0: Initializing card 0
Apr 12 20:09:21 jaunty64 kernel: [ 339.327165] cx18-0: Autodetected Hauppauge card
Apr 12 20:09:21 jaunty64 kernel: [ 339.327197] cx18-0: info: base addr: 0xd4000000
Apr 12 20:09:21 jaunty64 kernel: [ 339.327198] cx18-0: info: Enabling pci device
Apr 12 20:09:21 jaunty64 kernel: [ 339.327208] cx18 0000:05:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Apr 12 20:09:21 jaunty64 kernel: [ 339.327217] cx18-0: info: cx23418 (rev 0) at 05:01.0, irq: 19, latency: 64, memory: 0xd4000000
Apr 12 20:09:21 jaunty64 kernel: [ 339.327220] cx18-0: info: attempting ioremap at 0xd4000000 len 0x04000000
Apr 12 20:09:21 jaunty64 kernel: [ 339.329799] cx18-0: cx23418 revision 01010000 (B)
Apr 12 20:09:21 jaunty64 kernel: [ 339.425520] cx18-0: info: GPIO initial dir: 0000cffe/0000ffff out: 00003001/00000000
Apr 12 20:09:21 jaunty64 kernel: [ 339.425538] cx18-0: info: activating i2c...
Apr 12 20:09:21 jaunty64 kernel: [ 339.546155] tveeprom 0-0050: Hauppauge model 74541, rev C6B6, serial# 5384124
Apr 12 20:09:21 jaunty64 kernel: [ 339.546158] tveeprom 0-0050: MAC address is 00-0D-FE-52-27-BC
Apr 12 20:09:21 jaunty64 kernel: [ 339.546160] tveeprom 0-0050: tuner model is Philips FM1236 MK5 (idx 116, type 43)
Apr 12 20:09:21 jaunty64 kernel: [ 339.546162] tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
Apr 12 20:09:21 jaunty64 kernel: [ 339.546164] tveeprom 0-0050: audio processor is CX23418 (idx 38)
Apr 12 20:09:21 jaunty64 kernel: [ 339.546166] tveeprom 0-0050: decoder processor is CX23418 (idx 31)
Apr 12 20:09:21 jaunty64 kernel: [ 339.546167] tveeprom 0-0050: has radio
Apr 12 20:09:21 jaunty64 kernel: [ 339.546169] cx18-0: Autodetected Hauppauge HVR-1600
Apr 12 20:09:21 jaunty64 kernel: [ 339.546170] cx18-0: info: NTSC tuner detected
Apr 12 20:09:21 jaunty64 kernel: [ 339.546172] cx18-0: Simultaneous Digital and Analog TV capture supported
Apr 12 20:09:21 jaunty64 kernel: [ 339.649851] tuner 1-0043: chip found @ 0x86 (cx18 i2c driver #0-1)
Apr 12 20:09:21 jaunty64 kernel: [ 339.649917] tda9887 1-0043: creating new instance
Apr 12 20:09:21 jaunty64 kernel: [ 339.649918] tda9887 1-0043: tda988[5/6/7] found
Apr 12 20:09:21 jaunty64 kernel: [ 339.652047] tuner 1-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
Apr 12 20:09:21 jaunty64 kernel: [ 339.653119] cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
Apr 12 20:09:21 jaunty64 kernel: [ 339.655190] tuner-simple 1-0061: creating new instance
Apr 12 20:09:21 jaunty64 kernel: [ 339.655192] tuner-simple 1-0061: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F))
Apr 12 20:09:21 jaunty64 kernel: [ 339.656977] cx18-0: info: Allocate encoder MPEG stream: 64 x 32768 buffers (2048kB total)
Apr 12 20:09:21 jaunty64 kernel: [ 339.657684] cx18-0: info: Allocate TS stream: 32 x 32768 buffers (1024kB total)
Apr 12 20:09:21 jaunty64 kernel: [ 339.658055] cx18-0: info: Allocate encoder YUV stream: 16 x 131072 buffers (2048kB total)
Apr 12 20:09:21 jaunty64 kernel: [ 339.658865] cx18-0: info: Allocate encoder VBI stream: 20 x 51984 buffers (1015kB total)
Apr 12 20:09:21 jaunty64 kernel: [ 339.659319] cx18-0: info: Allocate encoder PCM audio stream: 256 x 4096 buffers (1024kB total)
Apr 12 20:09:21 jaunty64 kernel: [ 339.659894] cx18-0: info: Allocate encoder IDX stream: 32 x 32768 buffers (1024kB total)
Apr 12 20:09:21 jaunty64 kernel: [ 339.660439] cx18-0: Registered device video0 for encoder MPEG (64 x 32 kB)
Apr 12 20:09:21 jaunty64 kernel: [ 339.660443] DVB: registering new adapter (cx18)
Apr 12 20:09:21 jaunty64 kernel: [ 339.676024] cx18 0000:05:01.0: firmware: requesting v4l-cx23418-cpu.fw
Apr 12 20:09:21 jaunty64 kernel: [ 339.728697] MXL5005S: Attached at address 0x63
Apr 12 20:09:21 jaunty64 kernel: [ 339.728701] DVB: registering adapter 0 frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)...
Apr 12 20:09:21 jaunty64 kernel: [ 339.728759] cx18-0: DVB Frontend registered
Apr 12 20:09:21 jaunty64 kernel: [ 339.728761] cx18-0: Registered DVB adapter0 for TS (32 x 32 kB)
Apr 12 20:09:21 jaunty64 kernel: [ 339.728783] cx18-0: Registered device video32 for encoder YUV (16 x 128 kB)
Apr 12 20:09:21 jaunty64 kernel: [ 339.728802] cx18-0: Registered device vbi0 for encoder VBI (20 x 51984 bytes)
Apr 12 20:09:21 jaunty64 kernel: [ 339.728821] cx18-0: Registered device video24 for encoder PCM audio (256 x 4 kB)
Apr 12 20:09:21 jaunty64 kernel: [ 339.728841] cx18-0: Registered device radio0 for encoder radio
Apr 12 20:09:21 jaunty64 kernel: [ 339.728843] cx18-0: Initialized card: Hauppauge HVR-1600
Apr 12 20:09:21 jaunty64 kernel: [ 339.728859] cx18: End initialization
Apr 12 20:09:22 jaunty64 kernel: [ 339.804802] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes)
Apr 12 20:09:22 jaunty64 kernel: [ 339.830416] cx18 0000:05:01.0: firmware: requesting v4l-cx23418-apu.fw
Apr 12 20:09:22 jaunty64 kernel: [ 339.836328] cx18-0: info: load segment a00000-a07fff
Apr 12 20:09:22 jaunty64 kernel: [ 339.859046] cx18-0: info: load segment ae0000-ae00ff
Apr 12 20:09:22 jaunty64 kernel: [ 339.859223] cx18-0: info: load segment b00000-b1a65f
Apr 12 20:09:22 jaunty64 kernel: [ 339.933677] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 bytes)
Apr 12 20:09:22 jaunty64 kernel: [ 339.938480] cx18-0: info: 1 MiniMe Encoder Firmware 0.0.74.0 (Release 2007/03/12)
Apr 12 20:09:22 jaunty64 kernel: [ 339.938483] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
Apr 12 20:09:22 jaunty64 kernel: [ 340.144010] cx18-0: api: CX18_CPU_DEBUG_PEEK32^Icmd 0x20000003 args 0x00000000
Apr 12 20:09:22 jaunty64 kernel: [ 340.144071] cx18-0: api: CX18_APU_START^Icmd 0x10000001 args 0x000000b9 0x00000000
Apr 12 20:09:22 jaunty64 kernel: [ 340.145227] cx18-0: api: CX18_APU_RESETAI^Icmd 0x10000005 args
Apr 12 20:09:22 jaunty64 kernel: [ 340.145661] cx18-0: api: CX18_APU_STOP^Icmd 0x10000002 args 0x00000000
Apr 12 20:09:22 jaunty64 kernel: [ 340.148029] cx18 0000:05:01.0: firmware: requesting v4l-cx23418-cpu.fw
Apr 12 20:09:22 jaunty64 kernel: [ 340.285925] cx18 0000:05:01.0: firmware: requesting v4l-cx23418-apu.fw
Apr 12 20:09:22 jaunty64 kernel: [ 340.289228] cx18-0: info: load segment a00000-a07fff
Apr 12 20:09:22 jaunty64 kernel: [ 340.311769] cx18-0: info: load segment ae0000-ae00ff
Apr 12 20:09:22 jaunty64 kernel: [ 340.311949] cx18-0: info: load segment b00000-b1a65f
Apr 12 20:09:22 jaunty64 kernel: [ 340.392393] cx18-0: info: 1 MiniMe Encoder Firmware 0.0.74.0 (Release 2007/03/12)
Apr 12 20:09:22 jaunty64 kernel: [ 340.596013] cx18-0: api: CX18_CPU_DEBUG_PEEK32^Icmd 0x20000003 args 0x00000000
Apr 12 20:09:22 jaunty64 kernel: [ 340.596075] cx18-0: api: CX18_APU_START^Icmd 0x10000001 args 0x000000b9 0x00000000
Apr 12 20:09:22 jaunty64 kernel: [ 340.597240] cx18-0: api: CX18_APU_RESETAI^Icmd 0x10000005 args
Apr 12 20:09:22 jaunty64 kernel: [ 340.597675] cx18-0: api: CX18_APU_STOP^Icmd 0x10000002 args 0x00000000
Apr 12 20:09:22 jaunty64 kernel: [ 340.597742] cx18 0000:05:01.0: firmware: requesting v4l-cx23418-dig.fw
Apr 12 20:09:22 jaunty64 kernel: [ 340.783199] cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
Apr 12 20:09:22 jaunty64 kernel: [ 340.783243] cx18-0: info: Changing input from 1 to 0
Apr 12 20:09:22 jaunty64 kernel: [ 340.783245] cx18-0: info: Mute
Apr 12 20:09:22 jaunty64 kernel: [ 340.783247] cx18-0 843: info: decoder set video input 7, audio input 8
Apr 12 20:09:22 jaunty64 kernel: [ 340.783314] cx18-0 843: info: decoder set video input 7, audio input 8
Apr 12 20:09:22 jaunty64 kernel: [ 340.783380] cx18-0: info: Unmute
Apr 12 20:09:22 jaunty64 kernel: [ 340.783381] cx18-0: info: Switching standard to 1000.
Apr 12 20:09:22 jaunty64 kernel: [ 340.783383] cx18-0 843: info: changing video std to fmt 1
Apr 12 20:09:22 jaunty64 kernel: [ 340.783399] cx18-0 843: info: PLL regs = int: 15, frac: 2876158, post: 4
Apr 12 20:09:22 jaunty64 kernel: [ 340.783401] cx18-0 843: info: PLL = 107.999999 MHz
Apr 12 20:09:22 jaunty64 kernel: [ 340.783402] cx18-0 843: info: PLL/8 = 13.499999 MHz
Apr 12 20:09:22 jaunty64 kernel: [ 340.783404] cx18-0 843: info: ADC Sampling freq = 14.317382 MHz
Apr 12 20:09:22 jaunty64 kernel: [ 340.783405] cx18-0 843: info: Chroma sub-carrier freq = 3.579545 MHz
Apr 12 20:09:22 jaunty64 kernel: [ 340.783408] cx18-0 843: info: hblank 122, hactive 720, vblank 26, vactive 481, vblank656 38, src_dec 543, burst 0x5b, luma_lpf 1, uv_lpf 1, comb 0x66, sc 0x087c1f
Apr 12 20:09:22 jaunty64 kernel: [ 340.786577] cx18-0: info: Mute
Apr 12 20:09:22 jaunty64 kernel: [ 340.786579] cx18-0: info: v4l2 ioctl: set frequency 1076
Apr 12 20:09:22 jaunty64 kernel: [ 340.789244] cx18-0: info: Unmute
Apr 12 20:09:22 jaunty64 kernel: [ 340.790245] cx18-0: info: Mute
Apr 12 20:09:22 jaunty64 kernel: [ 340.793107] cx18-0 843: info: decoder set video input 7, audio input 0
Apr 12 20:09:22 jaunty64 kernel: [ 340.793172] cx18-0: info: Unmute
Apr 12 20:09:23 jaunty64 kernel: [ 340.799380] cx18-0: info: Mute
Apr 12 20:09:23 jaunty64 kernel: [ 340.799383] cx18-0 843: info: changing video std to fmt 1
Apr 12 20:09:23 jaunty64 kernel: [ 340.799398] cx18-0 843: info: PLL regs = int: 15, frac: 2876158, post: 4
Apr 12 20:09:23 jaunty64 kernel: [ 340.799399] cx18-0 843: info: PLL = 107.999999 MHz
Apr 12 20:09:23 jaunty64 kernel: [ 340.799400] cx18-0 843: info: PLL/8 = 13.499999 MHz
Apr 12 20:09:23 jaunty64 kernel: [ 340.799401] cx18-0 843: info: ADC Sampling freq = 14.317382 MHz
Apr 12 20:09:23 jaunty64 kernel: [ 340.799402] cx18-0 843: info: Chroma sub-carrier freq = 3.579545 MHz
Apr 12 20:09:23 jaunty64 kernel: [ 340.799404] cx18-0 843: info: hblank 122, hactive 720, vblank 26, vactive 481, vblank656 38, src_dec 543, burst 0x5b, luma_lpf 1, uv_lpf 1, comb 0x66, sc 0x087c1f
Apr 12 20:09:23 jaunty64 kernel: [ 340.802149] cx18-0 843: info: decoder set video input 7, audio input 8
Apr 12 20:09:23 jaunty64 kernel: [ 340.802222] cx18-0: info: Unmute
Apr 12 20:09:36 jaunty64 kernel: [ 354.282254] cx18-0: info: Mute
Apr 12 20:09:36 jaunty64 kernel: [ 354.282257] cx18-0: info: v4l2 ioctl: set frequency 980
Apr 12 20:09:36 jaunty64 kernel: [ 354.284958] cx18-0: info: Unmute
Apr 12 20:09:36 jaunty64 kernel: [ 354.308573] cx18-0: info: Start encoder stream encoder MPEG
Apr 12 20:09:36 jaunty64 kernel: [ 354.308578] cx18-0: api: CX18_CREATE_TASK^Icmd 0x40000001 args 0x20020000
Apr 12 20:09:36 jaunty64 kernel: [ 354.308641] cx18-0: api: CX18_CPU_SET_CHANNEL_TYPE^Icmd 0x20020001 args 0x00000000 0x00000001
Apr 12 20:09:36 jaunty64 kernel: [ 354.308700] cx18-0: api: CX18_CPU_SET_VER_CROP_LINE^Icmd 0x2002001b args 0x00000000 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.308756] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS^Icmd 0x20020015 args 0x00000000 0x00000003 0x00000001
Apr 12 20:09:36 jaunty64 kernel: [ 354.308815] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS^Icmd 0x20020015 args 0x00000000 0x00000008 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.308870] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS^Icmd 0x20020015 args 0x00000000 0x00000004 0x00000001
Apr 12 20:09:36 jaunty64 kernel: [ 354.308924] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS^Icmd 0x20020015 args 0x00000000 0x0000000c
Apr 12 20:09:36 jaunty64 kernel: [ 354.308976] cx18-0: api: CX18_CPU_SET_CAPTURE_LINE_NO^Icmd 0x20020017 args 0x00000000 0x00000138 0x00000139
Apr 12 20:09:36 jaunty64 kernel: [ 354.309038] cx18-0 843: info: PLL regs = int: 15, frac: 2876158, post: 4
Apr 12 20:09:36 jaunty64 kernel: [ 354.309040] cx18-0 843: info: PLL = 107.999999 MHz
Apr 12 20:09:36 jaunty64 kernel: [ 354.309042] cx18-0 843: info: PLL/8 = 13.499999 MHz
Apr 12 20:09:36 jaunty64 kernel: [ 354.309044] cx18-0 843: info: ADC Sampling freq = 14.317382 MHz
Apr 12 20:09:36 jaunty64 kernel: [ 354.309045] cx18-0 843: info: Chroma sub-carrier freq = 3.579545 MHz
Apr 12 20:09:36 jaunty64 kernel: [ 354.309048] cx18-0 843: info: hblank 122, hactive 720, vblank 26, vactive 481, vblank656 38, src_dec 543, burst 0x5b, luma_lpf 1, uv_lpf 1, comb 0x66, sc 0x087c1f
Apr 12 20:09:36 jaunty64 kernel: [ 354.309097] cx18-0: info: Setup VBI h: 0 lines c000c bpl 1444 fr 1 20602060 307090d0
Apr 12 20:09:36 jaunty64 kernel: [ 354.309100] cx18-0: api: CX18_CPU_SET_RAW_VBI_PARAM^Icmd 0x20020016 args 0x00000000 0x000c000c 0x000005a4 0x00000001 0x20602060 0x307090d0
Apr 12 20:09:36 jaunty64 kernel: [ 354.608010] cx18-0: api: CX18_CPU_SET_INDEXTABLE^Icmd 0x20020010 args 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.608069] cx18-0: api: CX18_CPU_SET_VIDEO_IN^Icmd 0x20020004 args 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.608138] cx18-0: api: CX18_CPU_SET_VIDEO_RESOLUTION^Icmd 0x20020006 args 0x00000000 0x000002d0 0x000001e0
Apr 12 20:09:36 jaunty64 kernel: [ 354.608204] cx18-0: api: CX18_CPU_SET_STREAM_OUTPUT_TYPE^Icmd 0x20020012 args 0x00000000 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.608260] cx18-0: api: CX18_CPU_SET_ASPECT_RATIO^Icmd 0x2002001e args 0x00000000 0x00000002
Apr 12 20:09:36 jaunty64 kernel: [ 354.608315] cx18-0: api: CX18_CPU_SET_GOP_STRUCTURE^Icmd 0x2002001c args 0x00000000 0x0000000f 0x00000003
Apr 12 20:09:36 jaunty64 kernel: [ 354.608369] cx18-0: api: CX18_CPU_SET_AUDIO_PARAMETERS^Icmd 0x20020011 args 0x00000000 0x000000b9
Apr 12 20:09:36 jaunty64 kernel: [ 354.608432] cx18-0: api: CX18_CPU_SET_AUDIO_MUTE^Icmd 0x20020014 args 0x00000000 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.608499] cx18-0: api: CX18_CPU_SET_VIDEO_RATE^Icmd 0x20020005 args 0x00000000 0x00000000 0x005b8d80 0x00004e20 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.608563] cx18-0: api: CX18_CPU_SET_FILTER_PARAM^Icmd 0x20020009 args 0x00000000 0x00000001 0x00000000 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.608619] cx18-0: api: CX18_CPU_SET_FILTER_PARAM^Icmd 0x20020009 args 0x00000000 0x00000000 0x00000001 0x00000008
Apr 12 20:09:36 jaunty64 kernel: [ 354.608675] cx18-0: api: CX18_CPU_SET_FILTER_PARAM^Icmd 0x20020009 args 0x00000000 0x00000002 0x00000000 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.608732] cx18-0: api: CX18_CPU_SET_MEDIAN_CORING^Icmd 0x2002000e args 0x00000000 0x00000000 0x000000ff 0x00000000 0x000000ff
Apr 12 20:09:36 jaunty64 kernel: [ 354.608796] cx18-0: api: CX18_CPU_SET_SPATIAL_FILTER_TYPE^Icmd 0x2002000c args 0x00000000 0x00000001 0x00000001
Apr 12 20:09:36 jaunty64 kernel: [ 354.608853] cx18-0: api: CX18_CPU_SET_FILTER_PARAM^Icmd 0x20020009 args 0x00000000 0x00000001 0x00000000 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.608909] cx18-0: api: CX18_CPU_SET_FILTER_PARAM^Icmd 0x20020009 args 0x00000000 0x00000000 0x00000001 0x00000008
Apr 12 20:09:36 jaunty64 kernel: [ 354.608964] cx18-0: api: CX18_CPU_SET_FILTER_PARAM^Icmd 0x20020009 args 0x00000000 0x00000002 0x00000000 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.609020] cx18-0: api: CX18_CPU_SET_SKIP_INPUT_FRAME^Icmd 0x2002001f args 0x00000000 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.609071] cx18-0: api: CX18_CPU_SET_VIDEO_MUTE^Icmd 0x20020013 args 0x00000000 0x00808000
Apr 12 20:09:36 jaunty64 kernel: [ 354.609124] cx18-0: api: CX18_CPU_SET_MISC_PARAMETERS^Icmd 0x20020015 args 0x00000000 0x00000007 0x00000000 0x00000000
Apr 12 20:09:36 jaunty64 kernel: [ 354.609184] cx18-0: api: CX18_CPU_DE_SET_MDL_ACK^Icmd 0x20040002 args 0x00000000 0x00dc0c40 0x00dc0c48
Apr 12 20:09:36 jaunty64 kernel: [ 354.613443] cx18-0: api: CX18_CPU_CAPTURE_START^Icmd 0x20020002 args 0x00000000
Apr 12 20:09:37 jaunty64 kernel: [ 355.418462] 2:1:1: cannot get freq at ep 0x1
Apr 12 20:10:08 jaunty64 kernel: [ 386.233200] cx18-0: warning: Possibly falling behind: CPU self-ack'ed our incoming CPU to EPU mailbox (sequence no. 1274) while processing
Apr 12 20:11:18 jaunty64 kernel: [ 456.462458] cx18-0: warning: sending CX18_CPU_DE_SET_MDL timed out waiting 12 msecs for RPU acknowledgement

On Sun, 2009-04-12 at 10:17 -0600, Ronal B Morse wrote:

I haven't seen any similar reports in the archives, but my Hauppauge HVR1600 does not produce usable output with mplayer or VLC in Ubuntu Linux (9.04 beta/2.6.28-11 amd64) until after I have used the card in a Windows XP session with Hauppague's WinTV software. Booting straight to Linux from a power off state results in a black screen and no audio from both players. ivti-tune and v4l2-ctl set--frequency both produce normal output and indicate the card has been set to the proper channel/frequency (3/61.125) DMSG and the kernel logs appear to be nominal. I don't see any obvious errors. lsmod indicates all of the required modules are loaded. The only anomaly I see is that v4l2-ctl --all indicates signal strength is 0, which is consistent with what I see from mplayer. If I command a system restart and boot into Windows XP, or boot directly into XP from a power off condition, the card works fine with the Hauppauge WinTV software. After I do that, I can command a system restart and boot into Linux and the card then works as expected. v4l2-ctl --all indicates signal strength of 100%. It seems that Ubuntu isn't initializing something on startup, but once whatever it is gets set it persists through a warm reboot. I'm really trying to avoid XP as much as possible and would appreciate any suggestions on how I might make the card work when I boot straight to Ubuntu.

As a follow-up I've determined that the sequence of commands:

sudo modprobe -r cx18
sudo modprobe cx18

will enable the card, after which it will perform normally until the machine is powered off. Should this be necessary?

On Mon, 2009-04-13 at 08:02 -0600, Ronal B Morse wrote:

> > > Booting straight to Linux from a power off state results in a black
> > > screen and no audio from both players. ivti-tune and v4l2-ctl
> > > set--frequency both produce normal output and indicate the card has been
> > > set to the proper channel/frequency (3/61.125)

> > > It seems that Ubuntu isn't initializing something on startup, but once
> > > whatever it is gets set it persists through a warm reboot.
> > >
> > >
> As a follow-up I've determined that the sequence of commands:
>
> sudo modprobe -r cx18
> sudo modprobe cx18
>
> will enable the card, after which it will perform normally until the
> machine is powered off. Should this be necessary?

In a perfect world no. A very busy PCI bus while the module is setting
up the chip registers and doing a firmware load can cause PCI bus errors
though. At boot-up, a high load on PCI bus in more recent kernels is
not uncommon.

I have some debugging code from 3 weeks ago at this repo:

http://linuxtv.org/hg/~awalls/cx18-init-debug/
http://linuxtv.org/hg/~awalls/cx18-init-debug/archive/tip.tar.gz

to get more insight into what may be going wrong and to also verify the
digitizer firmware load.

If you could use the driver from this repository and, IIRC, add an

options cx18 debug=15

to /etc/modprobe.conf, that will let me see if PCI MMIO writes are
failing as the module is being loaded at boot up. It will also tell me
if the digitizer firmware is getting loaded properly.


Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Andy Walls wrote:

On Mon, 2009-04-13 at 08:02 -0600, Ronal B Morse wrote:

Booting straight to Linux from a power off state results in a black screen and no audio from both players. ivti-tune and v4l2-ctl set--frequency both produce normal output and indicate the card has been set to the proper channel/frequency (3/61.125)

It seems that Ubuntu isn't initializing something on startup, but once whatever it is gets set it persists through a warm reboot.

As a follow-up I've determined that the sequence of commands: sudo modprobe -r cx18 sudo modprobe cx18 will enable the card, after which it will perform normally until the machine is powered off. Should this be necessary?

In a perfect world no. A very busy PCI bus while the module is setting up the chip registers and doing a firmware load can cause PCI bus errors though. At boot-up, a high load on PCI bus in more recent kernels is not uncommon. I have some debugging code from 3 weeks ago at this repo: http://linuxtv.org/hg/~awalls/cx18-init-debug/"]http://linuxtv.org/hg/~awalls/cx18-init-debug/ http://linuxtv.org/hg/~awalls/cx18-init-debug/archive/tip.tar.gz"]http://linuxtv.org/hg/~awalls/cx18-init-debug/archive/tip.tar.gz to get more insight into what may be going wrong and to also verify the digitizer firmware load. If you could use the driver from this repository and, IIRC, add an options cx18 debug=15 to /etc/modprobe.conf, that will let me see if PCI MMIO writes are failing as the module is being loaded at boot up. It will also tell me if the digitizer firmware is getting loaded properly. Regards, Andy _______________________________________________ ivtv-users mailing list ivtv-users@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-users"]http://ivtvdriver.org/mailman/listinfo/ivtv-users

Will do. Thanks.

Quick question: I'm running a 64-bit version of the O/S. Does that matter?

Ron Morse

On Mon, 2009-04-13 at 17:29 -0600, Ronal B Morse wrote:
> Andy Walls wrote:
> > On Mon, 2009-04-13 at 08:02 -0600, Ronal B Morse wrote:
> >
> >
> > > > > Booting straight to Linux from a power off state results in a black
> > > > > screen and no audio from both players. ivti-tune and v4l2-ctl
> > > > > set--frequency both produce normal output and indicate the card has been
> > > > > set to the proper channel/frequency (3/61.125)
> > > > >
> >
> >
> > > > > It seems that Ubuntu isn't initializing something on startup, but once
> > > > > whatever it is gets set it persists through a warm reboot.
> > > > >
> > > > >
> > > > >
> > > As a follow-up I've determined that the sequence of commands:
> > >
> > > sudo modprobe -r cx18
> > > sudo modprobe cx18
> > >
> > > will enable the card, after which it will perform normally until the
> > > machine is powered off. Should this be necessary?
> > >
> >
> > In a perfect world no. A very busy PCI bus while the module is setting
> > up the chip registers and doing a firmware load can cause PCI bus errors
> > though. At boot-up, a high load on PCI bus in more recent kernels is
> > not uncommon.
> >
> > I have some debugging code from 3 weeks ago at this repo:
> >
> > http://linuxtv.org/hg/~awalls/cx18-init-debug/
> > http://linuxtv.org/hg/~awalls/cx18-init-debug/archive/tip.tar.gz
> >
> > to get more insight into what may be going wrong and to also verify the
> > digitizer firmware load.
> >
> > If you could use the driver from this repository and, IIRC, add an
> >
> > options cx18 debug=15
> >
> > to /etc/modprobe.conf, that will let me see if PCI MMIO writes are
> > failing as the module is being loaded at boot up. It will also tell me
> > if the digitizer firmware is getting loaded properly.
> >
> >
> > Regards,
> > Andy
> >
> >
> > _______________________________________________
> > ivtv-users mailing list
> > ivtv-users@ivtvdriver.org
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
> >
> >
> Will do. Thanks.
>
> Quick question: I'm running a 64-bit version of the O/S. Does that
> matter?

No. The motherboard PCI chipset probably matters more.

-Andy

> Ron Morse
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Andy Walls wrote:

(redacted)

As a follow-up I've determined that the sequence of commands: sudo modprobe -r cx18 sudo modprobe cx18 will enable the card, after which it will perform normally until the machine is powered off. Should this be necessary?

In a perfect world no. A very busy PCI bus while the module is setting up the chip registers and doing a firmware load can cause PCI bus errors though. At boot-up, a high load on PCI bus in more recent kernels is not uncommon. I have some debugging code from 3 weeks ago at this repo: http://linuxtv.org/hg/~awalls/cx18-init-debug/"]http://linuxtv.org/hg/~awalls/cx18-init-debug/ http://linuxtv.org/hg/~awalls/cx18-init-debug/archive/tip.tar.gz"]http://linuxtv.org/hg/~awalls/cx18-init-debug/archive/tip.tar.gz to get more insight into what may be going wrong and to also verify the digitizer firmware load. If you could use the driver from this repository and, IIRC, add an options cx18 debug=15 to /etc/modprobe.conf, that will let me see if PCI MMIO writes are failing as the module is being loaded at boot up. It will also tell me if the digitizer firmware is getting loaded properly.

Andy,

I've loaded the driver you pointed to in the link. This particular version of Ubuntu (9.04B) doesn't have a folder at /etc/modprobe.conf and I've asked what they're using now. In the meantime I loaded the driver with modprobe cx18 debug=15.

After sitting overnight, when I powered up the machine this morning, mplayer brought the video and audio right up (i.e., it works!). We'll see if this continues.

Below find what I believe are the relevant sections of the log with the cx18 info. This was taken after a fresh boot and with mplayer playing some TV.

Ron Morse

Apr 14 07:39:53 jaunty64 kernel: [ 13.653961] cx18: Start initialization, version 1.1.0
Apr 14 07:39:53 jaunty64 kernel: [ 13.654040] cx18-0: Initializing card 0
Apr 14 07:39:53 jaunty64 kernel: [ 13.654041] cx18-0: Autodetected Hauppauge card
Apr 14 07:39:53 jaunty64 kernel: [ 13.654297] cx18 0000:05:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Apr 14 07:39:53 jaunty64 kernel: [ 13.654305] cx18-0: Unreasonably low latency timer, setting to 64 (was 32)
Apr 14 07:39:53 jaunty64 kernel: [ 13.656003] cx18-0: cx23418 revision 01010000 (B)
Apr 14 07:39:53 jaunty64 kernel: [ 13.723033] 2:1:1: cannot get freq at ep 0x1
Apr 14 07:39:53 jaunty64 kernel: [ 13.733648] HDA Intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Apr 14 07:39:53 jaunty64 kernel: [ 13.748299] usbcore: registered new interface driver snd-usb-audio
Apr 14 07:39:53 jaunty64 kernel: [ 13.874376] tveeprom 0-0050: Hauppauge model 74541, rev C6B6, serial# 5384124
Apr 14 07:39:53 jaunty64 kernel: [ 13.874378] tveeprom 0-0050: MAC address is 00-0D-FE-52-27-BC
Apr 14 07:39:53 jaunty64 kernel: [ 13.874380] tveeprom 0-0050: tuner model is Philips FM1236 MK5 (idx 116, type 43)
Apr 14 07:39:53 jaunty64 kernel: [ 13.874381] tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
Apr 14 07:39:53 jaunty64 kernel: [ 13.874382] tveeprom 0-0050: audio processor is CX23418 (idx 38)
Apr 14 07:39:53 jaunty64 kernel: [ 13.874384] tveeprom 0-0050: decoder processor is CX23418 (idx 31)
Apr 14 07:39:53 jaunty64 kernel: [ 13.874385] tveeprom 0-0050: has radio
Apr 14 07:39:53 jaunty64 kernel: [ 13.874386] cx18-0: Autodetected Hauppauge HVR-1600
Apr 14 07:39:53 jaunty64 kernel: [ 13.874387] cx18-0: Simultaneous Digital and Analog TV capture supported
Apr 14 07:39:53 jaunty64 kernel: [ 14.033070] tuner 1-0043: chip found @ 0x86 (cx18 i2c driver #0-1)
Apr 14 07:39:53 jaunty64 kernel: [ 14.036754] tda9887 1-0043: creating new instance
Apr 14 07:39:53 jaunty64 kernel: [ 14.036755] tda9887 1-0043: tda988[5/6/7] found
Apr 14 07:39:53 jaunty64 kernel: [ 14.038707] tuner 1-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
Apr 14 07:39:53 jaunty64 kernel: [ 14.044924] cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
Apr 14 07:39:53 jaunty64 kernel: [ 14.051839] tuner-simple 1-0061: creating new instance
Apr 14 07:39:53 jaunty64 kernel: [ 14.051841] tuner-simple 1-0061: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F))
Apr 14 07:39:53 jaunty64 kernel: [ 14.057375] cx18-0: Registered device video0 for encoder MPEG (64 x 32 kB)
Apr 14 07:39:53 jaunty64 kernel: [ 14.057378] DVB: registering new adapter (cx18)
Apr 14 07:39:53 jaunty64 kernel: [ 14.133815] MXL5005S: Attached at address 0x63
Apr 14 07:39:53 jaunty64 kernel: [ 14.133817] DVB: registering adapter 0 frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)...
Apr 14 07:39:53 jaunty64 kernel: [ 14.133994] cx18-0: DVB Frontend registered
Apr 14 07:39:53 jaunty64 kernel: [ 14.133996] cx18-0: Registered DVB adapter0 for TS (32 x 32 kB)
Apr 14 07:39:53 jaunty64 kernel: [ 14.134025] cx18-0: Registered device video32 for encoder YUV (16 x 128 kB)
Apr 14 07:39:53 jaunty64 kernel: [ 14.134055] cx18-0: Registered device vbi0 for encoder VBI (20 x 51984 bytes)
Apr 14 07:39:53 jaunty64 kernel: [ 14.134083] cx18-0: Registered device video24 for encoder PCM audio (256 x 4 kB)
Apr 14 07:39:53 jaunty64 kernel: [ 14.134110] cx18-0: Registered device radio0 for encoder radio
Apr 14 07:39:53 jaunty64 kernel: [ 14.134112] cx18-0: Initialized card: Hauppauge HVR-1600
Apr 14 07:39:53 jaunty64 kernel: [ 14.134137] cx18: End initialization
Apr 14 07:39:53 jaunty64 kernel: [ 14.155883] logips2pp: Detected unknown logitech mouse model 60
Apr 14 07:39:53 jaunty64 kernel: [ 14.238446] lp: driver loaded but no devices found
Apr 14 07:39:53 jaunty64 kernel: [ 14.263262] it87: Found IT8718F chip at 0x290, revision 5
Apr 14 07:39:53 jaunty64 kernel: [ 14.263269] it87: in3 is VCC (+5V)
Apr 14 07:39:53 jaunty64 kernel: [ 14.270123] coretemp coretemp.0: Using relative temperature scale!
Apr 14 07:39:53 jaunty64 kernel: [ 14.270144] coretemp coretemp.1: Using relative temperature scale!
Apr 14 07:39:53 jaunty64 kernel: [ 14.311297] Adding 8385920k swap on /dev/sdb2. Priority:-1 extents:1 across:8385920k
Apr 14 07:39:53 jaunty64 kernel: [ 14.643173] input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input5
Apr 14 07:39:53 jaunty64 kernel: [ 14.831832] EXT3 FS on sda5, internal journal
Apr 14 07:39:53 jaunty64 kernel: [ 15.543419] kjournald starting. Commit interval 5 seconds
Apr 14 07:39:53 jaunty64 kernel: [ 15.543570] EXT3 FS on sdb1, internal journal
Apr 14 07:39:53 jaunty64 kernel: [ 15.543574] EXT3-fs: mounted filesystem with ordered data mode.
Apr 14 07:39:53 jaunty64 kernel: [ 15.767551] kjournald starting. Commit interval 5 seconds
Apr 14 07:39:53 jaunty64 kernel: [ 15.768290] EXT3 FS on sdc1, internal journal
Apr 14 07:39:53 jaunty64 kernel: [ 15.768294] EXT3-fs: mounted filesystem with ordered data mode.
Apr 14 07:39:53 jaunty64 kernel: [ 15.905922] type=1505 audit(1239716392.578:2): operation="profile_load" name="/usr/share/gdm/guest-session/Xsession" name2="default" pid=2249
Apr 14 07:39:53 jaunty64 kernel: [ 15.928662] type=1505 audit(1239716392.602:3): operation="profile_load" name="/sbin/dhclient-script" name2="default" pid=2253
Apr 14 07:39:53 jaunty64 kernel: [ 15.928711] type=1505 audit(1239716392.602:4): operation="profile_load" name="/sbin/dhclient3" name2="default" pid=2253
Apr 14 07:39:53 jaunty64 kernel: [ 15.928734] type=1505 audit(1239716392.602:5): operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" name2="default" pid=2253
Apr 14 07:39:53 jaunty64 kernel: [ 15.928758] type=1505 audit(1239716392.602:6): operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" name2="default" pid=2253
Apr 14 07:39:53 jaunty64 kernel: [ 15.990535] type=1505 audit(1239716392.662:7): operation="profile_load" name="/usr/lib/cups/backend/cups-pdf" name2="default" pid=2258
Apr 14 07:39:53 jaunty64 kernel: [ 15.990626] type=1505 audit(1239716392.662:8): operation="profile_load" name="/usr/sbin/cupsd" name2="default" pid=2258
Apr 14 07:39:53 jaunty64 kernel: [ 16.012817] type=1505 audit(1239716392.686:9): operation="profile_load" name="/usr/sbin/tcpdump" name2="default" pid=2262
Apr 14 07:39:56 jaunty64 kernel: [ 19.466101] usb 2-6.2: configuration #1 chosen from 1 choice
Apr 14 07:39:56 jaunty64 kernel: [ 19.471443] generic-usb 0003:05AC:921C.0002: hiddev97,hidraw1: USB HID v1.11 Device [Apple Computer, Inc. Apple Cinema HD Display] on usb-0000:00:1d.7-6.2/input0
Apr 14 07:39:56 jaunty64 kernel: [ 19.512516] cx18 0000:05:01.0: firmware: requesting v4l-cx23418-cpu.fw
Apr 14 07:39:56 jaunty64 kernel: [ 19.768457] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes)
Apr 14 07:39:56 jaunty64 kernel: [ 19.793229] cx18 0000:05:01.0: firmware: requesting v4l-cx23418-apu.fw
Apr 14 07:39:56 jaunty64 kernel: [ 19.893876] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 bytes)
Apr 14 07:39:56 jaunty64 kernel: [ 19.900066] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
Apr 14 07:39:56 jaunty64 kernel: [ 20.108017] cx18 0000:05:01.0: firmware: requesting v4l-cx23418-cpu.fw
Apr 14 07:39:56 jaunty64 kernel: [ 20.241485] cx18 0000:05:01.0: firmware: requesting v4l-cx23418-apu.fw
Apr 14 07:39:57 jaunty64 kernel: [ 20.553680] cx18 0000:05:01.0: firmware: requesting v4l-cx23418-dig.fw
Apr 14 07:39:57 jaunty64 kernel: [ 20.751568] cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
Apr 14 07:39:57 jaunty64 kernel: [ 20.770833] cx18-0 843: verified load of v4l-cx23418-dig.fw firmware (16382 bytes)
Apr 14 07:39:59 jaunty64 kernel: [ 22.694363] ppdev: user-space parallel port driver