Linux driver for a very old ASUS TV Tuner Card 880 NTSC (cx23880)?
Ant
I have a very old ASUS TV Tuner Card 880 NTSC (cx23880; PCI) in my old,
updated Debian box with its kernel v2.6.32-5-686 #1 SMP Fri Dec 10
16:12:40 UTC 2010 i686 GNU/Linux. My friend (gave it to me for free
since he doesn't use it anymore) and I used to use it in Windows XP Pro.
SP3 with PowerVCR II with no problems.
However, it doesn't seem to work in Debian/Linux. I noticed dmesg showed
it not having drivers for it:
$ dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32-5-686 (Debian 2.6.32-29)
(b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri
Dec 10 16:12:40 UTC 2010
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007ff90000 (usable)
[ 0.000000] BIOS-e820: 000000007ff90000 - 000000007ff9e000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007ff9e000 - 000000007ffe0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007ffe0000 - 0000000080000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[ 0.000000] DMI present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working
around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000
(usable) ==> (reserved)
[ 0.000000] last_pfn = 0x7ff90 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-DFFFF uncachable
[ 0.000000] E0000-EFFFF write-through
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 disabled
[ 0.000000] 2 disabled
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[ 0.000000] initial memory mapped : 0 - 01800000
[ 0.000000] init_memory_mapping: 0000000000000000-00000000373fe000
[ 0.000000] 0000000000 - 0000400000 page 4k
[ 0.000000] 0000400000 - 0037000000 page 2M
[ 0.000000] 0037000000 - 00373fe000 page 4k
[ 0.000000] kernel direct mapping tables up to 373fe000 @ 10000-16000
[ 0.000000] RAMDISK: 3784a000 - 37fef3ed
[ 0.000000] Allocated new RAMDISK: 00100000 - 008a53ed
[ 0.000000] Move RAMDISK from 000000003784a000 - 0000000037fef3ec to
00100000 - 008a53ec
[ 0.000000] ACPI: RSDP 000f9aa0 00014 (v00 ACPIAM)
[ 0.000000] ACPI: RSDT 7ff90000 0003C (v01 7514MS A7514200 20090904
MSFT 00000097)
[ 0.000000] ACPI: FACP 7ff90200 00084 (v01 7514MS A7514200 20090904
MSFT 00000097)
[ 0.000000] ACPI: DSDT 7ff90440 063EE (v01 A7514 A7514200 00000200
INTL 20051117)
[ 0.000000] ACPI: FACS 7ff9e000 00040
[ 0.000000] ACPI: APIC 7ff90390 0006C (v01 7514MS A7514200 20090904
MSFT 00000097)
[ 0.000000] ACPI: MCFG 7ff90400 0003C (v01 7514MS OEMMCFG 20090904
MSFT 00000097)
[ 0.000000] ACPI: OEMB 7ff9e040 00072 (v01 7514MS A7514200 20090904
MSFT 00000097)
[ 0.000000] ACPI: HPET 7ff98440 00038 (v01 7514MS OEMHPET 20090904
MSFT 00000097)
[ 0.000000] ACPI: SSDT 7ff9e8c0 00A7C (v01 DpgPmm CpuPm 00000012
INTL 20051117)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] 1163MB HIGHMEM available.
[ 0.000000] 883MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 373fe000
[ 0.000000] low ram: 0 - 373fe000
[ 0.000000] node 0 low ram: 00000000 - 373fe000
[ 0.000000] node 0 bootmap 00012000 - 00018e80
[ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 00373fe000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==>
[0000000000 - 0000001000]
[ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==>
[0000001000 - 0000002000]
[ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==>
[0000006000 - 0000007000]
[ 0.000000] #3 [0001000000 - 00014c9bb4] TEXT DATA BSS ==>
[0001000000 - 00014c9bb4]
[ 0.000000] #4 [000009fc00 - 0000100000] BIOS reserved ==>
[000009fc00 - 0000100000]
[ 0.000000] #5 [00014ca000 - 00014d0195] BRK ==>
[00014ca000 - 00014d0195]
[ 0.000000] #6 [0000010000 - 0000012000] PGTABLE ==>
[0000010000 - 0000012000]
[ 0.000000] #7 [0000100000 - 00008a53ed] NEW RAMDISK ==>
[0000100000 - 00008a53ed]
[ 0.000000] #8 [0000012000 - 0000019000] BOOTMAP ==>
[0000012000 - 0000019000]
[ 0.000000] found SMP MP-table at [c00ff780] ff780
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x000373fe
[ 0.000000] HighMem 0x000373fe -> 0x0007ff90
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x0007ff90
[ 0.000000] On node 0 totalpages: 524063
[ 0.000000] free_area_init_node: node 0, pgdat c13b2860, node_mem_map
c14d2200
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 3951 pages, LIFO batch:0
[ 0.000000] Normal zone: 1736 pages used for memmap
[ 0.000000] Normal zone: 220470 pages, LIFO batch:31
[ 0.000000] HighMem zone: 2328 pages used for memmap
[ 0.000000] HighMem zone: 295546 pages, LIFO batch:31
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
[ 0.000000] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI
0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0xffffffff base: 0xfed00000
[ 0.000000] SMP: Allowing 4 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 24
[ 0.000000] PM: Registered nosave memory: 000000000009f000 -
00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 -
00000000000e0000
[ 0.000000] PM: Registered nosave memory: 00000000000e0000 -
0000000000100000
[ 0.000000] Allocating PCI resources starting at 80000000 (gap:
80000000:7ee00000)
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages/cpu @c2800000 s34296 r0 d23048
u1048576
[ 0.000000] pcpu-alloc: s34296 r0 d23048 u1048576 alloc=1*4194304
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 519967
[ 0.000000] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686
root=UUID=fe4a1af1-1979-49fb-9668-314a24b12890 ro quiet nouveau.modeset=0
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] Initializing HighMem for node 0 (000373fe:0007ff90)
[ 0.000000] Memory: 2064768k/2096704k available (2500k kernel code,
30236k reserved, 1324k data, 376k init, 1191496k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xffd56000 - 0xfffff000 (2724 kB)
[ 0.000000] pkmap : 0xff400000 - 0xff800000 (4096 kB)
[ 0.000000] vmalloc : 0xf7bfe000 - 0xff3fe000 ( 120 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf73fe000 ( 883 MB)
[ 0.000000] .init : 0xc13bd000 - 0xc141b000 ( 376 kB)
[ 0.000000] .data : 0xc12713d9 - 0xc13bc460 (1324 kB)
[ 0.000000] .text : 0xc1000000 - 0xc12713d9 (2500 kB)
[ 0.000000] Checking if this processor honours the WP bit even in
supervisor mode...Ok.
[ 0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0,
CPUs=4, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:1280
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] HPET: 4 timers in total, 0 timers will be used for
per-cpu timer
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 2339.173 MHz processor.
[ 0.004004] Calibrating delay loop (skipped), value calculated using
timer frequency.. 4678.34 BogoMIPS (lpj=9356692)
[ 0.004016] Security Framework initialized
[ 0.004020] SELinux: Disabled at boot.
[ 0.004025] Mount-cache hash table entries: 512
[ 0.004115] Initializing cgroup subsys ns
[ 0.004118] Initializing cgroup subsys cpuacct
[ 0.004122] Initializing cgroup subsys devices
[ 0.004123] Initializing cgroup subsys freezer
[ 0.004125] Initializing cgroup subsys net_cls
[ 0.004143] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.004145] CPU: L2 cache: 2048K
[ 0.004147] CPU: Physical Processor ID: 0
[ 0.004148] CPU: Processor Core ID: 0
[ 0.004151] mce: CPU supports 6 MCE banks
[ 0.004157] CPU0: Thermal monitoring enabled (TM2)
[ 0.004160] using mwait in idle threads.
[ 0.004165] Performance Events: Core2 events, Intel PMU driver.
[ 0.004170] ... version: 2
[ 0.004171] ... bit width: 40
[ 0.004173] ... generic registers: 2
[ 0.004174] ... value mask: 000000ffffffffff
[ 0.004175] ... max period: 000000007fffffff
[ 0.004177] ... fixed-purpose events: 3
[ 0.004178] ... event mask: 0000000700000003
[ 0.004181] Checking 'hlt' instruction... OK.
[ 0.021040] ACPI: Core revision 20090903
[ 0.026926] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.027230] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.066920] CPU0: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.068001] Booting processor 1 APIC 0x1 ip 0x6000
[ 0.008000] Initializing CPU#1
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.008000] CPU: L2 cache: 2048K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 1
[ 0.008000] CPU1: Thermal monitoring enabled (TM2)
[ 0.152044] CPU1: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.152050] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
[ 0.156102] Booting processor 2 APIC 0x2 ip 0x6000
[ 0.008000] Initializing CPU#2
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.008000] CPU: L2 cache: 2048K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 2
[ 0.008000] CPU2: Thermal monitoring enabled (TM2)
[ 0.244096] CPU2: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.244102] checking TSC synchronization [CPU#0 -> CPU#2]: passed.
[ 0.248081] Booting processor 3 APIC 0x3 ip 0x6000
[ 0.008000] Initializing CPU#3
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.008000] CPU: L2 cache: 2048K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 3
[ 0.008000] CPU3: Thermal monitoring enabled (TM2)
[ 0.336034] CPU3: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.336039] checking TSC synchronization [CPU#0 -> CPU#3]: passed.
[ 0.340036] Brought up 4 CPUs
[ 0.340038] Total of 4 processors activated (18713.07 BogoMIPS).
[ 0.341231] CPU0 attaching sched-domain:
[ 0.341234] domain 0: span 0-1 level MC
[ 0.341236] groups: 0 1
[ 0.341239] domain 1: span 0-3 level CPU
[ 0.341241] groups: 0-1 (cpu_power = 2048) 2-3 (cpu_power = 2048)
[ 0.341247] CPU1 attaching sched-domain:
[ 0.341249] domain 0: span 0-1 level MC
[ 0.341250] groups: 1 0
[ 0.341253] domain 1: span 0-3 level CPU
[ 0.341255] groups: 0-1 (cpu_power = 2048) 2-3 (cpu_power = 2048)
[ 0.341260] CPU2 attaching sched-domain:
[ 0.341261] domain 0: span 2-3 level MC
[ 0.341263] groups: 2 3
[ 0.341266] domain 1: span 0-3 level CPU
[ 0.341268] groups: 2-3 (cpu_power = 2048) 0-1 (cpu_power = 2048)
[ 0.341272] CPU3 attaching sched-domain:
[ 0.341274] domain 0: span 2-3 level MC
[ 0.341276] groups: 3 2
[ 0.341278] domain 1: span 0-3 level CPU
[ 0.341280] groups: 2-3 (cpu_power = 2048) 0-1 (cpu_power = 2048)
[ 0.341385] devtmpfs: initialized
[ 0.341385] regulator: core version 0.5
[ 0.341385] NET: Registered protocol family 16
[ 0.341385] ACPI: bus type pci registered
[ 0.341385] PCI: MCFG configuration 0: base e0000000 segment 0 buses
0 - 255
[ 0.341385] PCI: Not using MMCONFIG.
[ 0.341385] PCI: Using configuration type 1 for base access
[ 0.341385] bio: create slab <bio-0> at 0
[ 0.341385] ACPI: EC: Look up EC in DSDT
[ 0.345925] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.350193] ACPI: Interpreter enabled
[ 0.350202] ACPI: (supports S0 S3 S4 S5)
[ 0.350223] ACPI: Using IOAPIC for interrupt routing
[ 0.350264] PCI: MCFG configuration 0: base e0000000 segment 0 buses
0 - 255
[ 0.352886] PCI: MCFG area at e0000000 reserved in ACPI motherboard
resources
[ 0.352888] PCI: Using MMCONFIG for extended config space
[ 0.360155] ACPI Warning: Incorrect checksum in table [OEMB] - BB,
should be B2 (20090903/tbutils-314)
[ 0.360259] ACPI: No dock devices found.
[ 0.360384] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.360461] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.360464] pci 0000:00:01.0: PME# disabled
[ 0.360522] pci 0000:00:1a.0: reg 20 io port: [0x8800-0x881f]
[ 0.360580] pci 0000:00:1a.1: reg 20 io port: [0x8480-0x849f]
[ 0.360637] pci 0000:00:1a.2: reg 20 io port: [0x8400-0x841f]
[ 0.360698] pci 0000:00:1a.7: reg 10 32bit mmio: [0xf7fff400-0xf7fff7ff]
[ 0.360744] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[ 0.360748] pci 0000:00:1a.7: PME# disabled
[ 0.360782] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf7ff8000-0xf7ffbfff]
[ 0.360816] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.360820] pci 0000:00:1b.0: PME# disabled
[ 0.360871] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.360874] pci 0000:00:1c.0: PME# disabled
[ 0.360926] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.360929] pci 0000:00:1c.1: PME# disabled
[ 0.360984] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[ 0.360987] pci 0000:00:1c.5: PME# disabled
[ 0.361032] pci 0000:00:1d.0: reg 20 io port: [0x9000-0x901f]
[ 0.361090] pci 0000:00:1d.1: reg 20 io port: [0x8c00-0x8c1f]
[ 0.361147] pci 0000:00:1d.2: reg 20 io port: [0x8880-0x889f]
[ 0.361208] pci 0000:00:1d.7: reg 10 32bit mmio: [0xf7fff800-0xf7fffbff]
[ 0.361254] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.361258] pci 0000:00:1d.7: PME# disabled
[ 0.361401] pci 0000:00:1f.2: reg 10 io port: [0xac00-0xac07]
[ 0.361406] pci 0000:00:1f.2: reg 14 io port: [0xa880-0xa883]
[ 0.361411] pci 0000:00:1f.2: reg 18 io port: [0xa800-0xa807]
[ 0.361416] pci 0000:00:1f.2: reg 1c io port: [0xa480-0xa483]
[ 0.361421] pci 0000:00:1f.2: reg 20 io port: [0xa400-0xa40f]
[ 0.361426] pci 0000:00:1f.2: reg 24 io port: [0xa080-0xa08f]
[ 0.361463] pci 0000:00:1f.3: reg 10 64bit mmio: [0xf7fffc00-0xf7fffcff]
[ 0.361475] pci 0000:00:1f.3: reg 20 io port: [0x400-0x41f]
[ 0.361511] pci 0000:00:1f.5: reg 10 io port: [0x9c00-0x9c07]
[ 0.361516] pci 0000:00:1f.5: reg 14 io port: [0x9880-0x9883]
[ 0.361521] pci 0000:00:1f.5: reg 18 io port: [0x9800-0x9807]
[ 0.361525] pci 0000:00:1f.5: reg 1c io port: [0x9480-0x9483]
[ 0.361530] pci 0000:00:1f.5: reg 20 io port: [0x9400-0x940f]
[ 0.361535] pci 0000:00:1f.5: reg 24 io port: [0x9080-0x908f]
[ 0.361581] pci 0000:05:00.0: reg 10 32bit mmio: [0xfd000000-0xfdffffff]
[ 0.361588] pci 0000:05:00.0: reg 14 64bit mmio pref:
[0xd0000000-0xdfffffff]
[ 0.361595] pci 0000:05:00.0: reg 1c 64bit mmio: [0xfa000000-0xfbffffff]
[ 0.361600] pci 0000:05:00.0: reg 24 io port: [0xec00-0xec7f]
[ 0.361605] pci 0000:05:00.0: reg 30 32bit mmio pref: [0x000000-0x01ffff]
[ 0.361692] pci 0000:00:01.0: bridge io port: [0xe000-0xefff]
[ 0.361695] pci 0000:00:01.0: bridge 32bit mmio: [0xfa000000-0xfebfffff]
[ 0.361698] pci 0000:00:01.0: bridge 64bit mmio pref:
[0xd0000000-0xdfffffff]
[ 0.361779] pci 0000:02:00.0: reg 24 32bit mmio: [0xf9efe000-0xf9efffff]
[ 0.361815] pci 0000:02:00.0: PME# supported from D3hot
[ 0.361819] pci 0000:02:00.0: PME# disabled
[ 0.361867] pci 0000:02:00.1: reg 10 io port: [0xcc00-0xcc07]
[ 0.361876] pci 0000:02:00.1: reg 14 io port: [0xc880-0xc883]
[ 0.361884] pci 0000:02:00.1: reg 18 io port: [0xc800-0xc807]
[ 0.361892] pci 0000:02:00.1: reg 1c io port: [0xc480-0xc483]
[ 0.361900] pci 0000:02:00.1: reg 20 io port: [0xc400-0xc40f]
[ 0.361963] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device.
You can enable it with 'pcie_aspm=force'
[ 0.362024] pci 0000:00:1c.0: bridge io port: [0xc000-0xcfff]
[ 0.362028] pci 0000:00:1c.0: bridge 32bit mmio: [0xf9e00000-0xf9efffff]
[ 0.362106] pci 0000:04:00.0: reg 10 io port: [0xd800-0xd8ff]
[ 0.362125] pci 0000:04:00.0: reg 18 64bit mmio pref:
[0xcffff000-0xcfffffff]
[ 0.362137] pci 0000:04:00.0: reg 20 64bit mmio pref:
[0xcffe0000-0xcffeffff]
[ 0.362145] pci 0000:04:00.0: reg 30 32bit mmio pref:
[0xf9ff0000-0xf9ffffff]
[ 0.362180] pci 0000:04:00.0: supports D1 D2
[ 0.362182] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.362186] pci 0000:04:00.0: PME# disabled
[ 0.368096] pci 0000:00:1c.5: bridge io port: [0xd000-0xdfff]
[ 0.368100] pci 0000:00:1c.5: bridge 32bit mmio: [0xf9f00000-0xf9ffffff]
[ 0.368105] pci 0000:00:1c.5: bridge 64bit mmio pref:
[0xcff00000-0xcfffffff]
[ 0.368138] pci 0000:01:00.0: reg 10 32bit mmio: [0xf8000000-0xf8ffffff]
[ 0.368222] pci 0000:01:02.0: reg 10 32bit mmio: [0xf9dff000-0xf9dfffff]
[ 0.368228] pci 0000:01:02.0: reg 14 io port: [0xbc00-0xbc3f]
[ 0.368234] pci 0000:01:02.0: reg 18 32bit mmio: [0xf9c00000-0xf9cfffff]
[ 0.368251] pci 0000:01:02.0: reg 30 32bit mmio pref:
[0xf9b00000-0xf9bfffff]
[ 0.368267] pci 0000:01:02.0: supports D1 D2
[ 0.368269] pci 0000:01:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.368272] pci 0000:01:02.0: PME# disabled
[ 0.368315] pci 0000:00:1e.0: transparent bridge
[ 0.368318] pci 0000:00:1e.0: bridge io port: [0xb000-0xbfff]
[ 0.368322] pci 0000:00:1e.0: bridge 32bit mmio: [0xf8000000-0xf9dfffff]
[ 0.368341] pci_bus 0000:00: on NUMA node 0
[ 0.368345] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.368516] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[ 0.368663] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
[ 0.368727] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
[ 0.368787] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT]
[ 0.383253] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12
14 15)
[ 0.383348] ACPI: PCI Interrupt Link [LNKB] (IRQs *5)
[ 0.383437] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12 14
*15)
[ 0.383530] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 *11 12
14 15)
[ 0.383622] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14
15) *0, disabled.
[ 0.383715] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 *7 10 11 12
14 15)
[ 0.383807] ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 6 7 10 11 12
14 15)
[ 0.383899] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 10 11 12
*14 15)
[ 0.383987] vgaarb: device added:
PCI:0000:05:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.383991] vgaarb: loaded
[ 0.384046] PCI: Using ACPI for IRQ routing
[ 0.384202] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[ 0.384206] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[ 0.392018] Switching to clocksource tsc
[ 0.393133] pnp: PnP ACPI init
[ 0.393148] ACPI: bus type pnp registered
[ 0.396341] pnp: PnP ACPI: found 18 devices
[ 0.396343] ACPI: ACPI bus type pnp unregistered
[ 0.396347] PnPBIOS: Disabled by ACPI PNP
[ 0.396356] system 00:01: iomem range 0xfed14000-0xfed19fff has been
reserved
[ 0.396359] system 00:01: iomem range 0xfed90000-0xfed93fff has been
reserved
[ 0.396366] system 00:08: ioport range 0x4c0-0x4ff has been reserved
[ 0.396369] system 00:08: ioport range 0x4d0-0x4d1 has been reserved
[ 0.396371] system 00:08: ioport range 0x800-0x87f has been reserved
[ 0.396373] system 00:08: ioport range 0x480-0x4bf has been reserved
[ 0.396376] system 00:08: iomem range 0xfed1c000-0xfed1ffff has been
reserved
[ 0.396379] system 00:08: iomem range 0xfed20000-0xfed3ffff has been
reserved
[ 0.396381] system 00:08: iomem range 0xfed40000-0xfed8ffff has been
reserved
[ 0.396386] system 00:0b: iomem range 0xffc00000-0xffefffff has been
reserved
[ 0.396391] system 00:0c: iomem range 0xfec00000-0xfec00fff could not
be reserved
[ 0.396393] system 00:0c: iomem range 0xfee00000-0xfee00fff has been
reserved
[ 0.396398] system 00:0f: ioport range 0xa00-0xadf has been reserved
[ 0.396401] system 00:0f: ioport range 0xae0-0xaef has been reserved
[ 0.396405] system 00:10: iomem range 0xe0000000-0xefffffff has been
reserved
[ 0.396410] system 00:11: iomem range 0x0-0x9ffff could not be reserved
[ 0.396412] system 00:11: iomem range 0xc0000-0xcffff could not be
reserved
[ 0.396415] system 00:11: iomem range 0xe0000-0xfffff could not be
reserved
[ 0.396417] system 00:11: iomem range 0x100000-0x7fffffff could not
be reserved
[ 0.396420] system 00:11: iomem range 0xfed90000-0xffffffff could not
be reserved
[ 0.431197] pci 0000:01:02.0: BAR 6: address space collision on of
device [0xf9b00000-0xf9bfffff]
[ 0.431276] pci 0000:00:01.0: PCI bridge, secondary bus 0000:05
[ 0.431279] pci 0000:00:01.0: IO window: 0xe000-0xefff
[ 0.431282] pci 0000:00:01.0: MEM window: 0xfa000000-0xfebfffff
[ 0.431285] pci 0000:00:01.0: PREFETCH window:
0x000000d0000000-0x000000dfffffff
[ 0.431289] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
[ 0.431292] pci 0000:00:1c.0: IO window: 0xc000-0xcfff
[ 0.431296] pci 0000:00:1c.0: MEM window: 0xf9e00000-0xf9efffff
[ 0.431300] pci 0000:00:1c.0: PREFETCH window:
0x00000080000000-0x000000801fffff
[ 0.431305] pci 0000:00:1c.1: PCI bridge, secondary bus 0000:03
[ 0.431307] pci 0000:00:1c.1: IO window: 0x1000-0x1fff
[ 0.431311] pci 0000:00:1c.1: MEM window: 0x80200000-0x803fffff
[ 0.431315] pci 0000:00:1c.1: PREFETCH window:
0x00000080400000-0x000000805fffff
[ 0.431320] pci 0000:00:1c.5: PCI bridge, secondary bus 0000:04
[ 0.431323] pci 0000:00:1c.5: IO window: 0xd000-0xdfff
[ 0.431327] pci 0000:00:1c.5: MEM window: 0xf9f00000-0xf9ffffff
[ 0.431330] pci 0000:00:1c.5: PREFETCH window:
0x000000cff00000-0x000000cfffffff
[ 0.431336] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:01
[ 0.431339] pci 0000:00:1e.0: IO window: 0xb000-0xbfff
[ 0.431343] pci 0000:00:1e.0: MEM window: 0xf8000000-0xf9dfffff
[ 0.431347] pci 0000:00:1e.0: PREFETCH window: 0x80600000-0x806fffff
[ 0.431358] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.431361] pci 0000:00:01.0: setting latency timer to 64
[ 0.431369] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 0.431373] pci 0000:00:1c.0: setting latency timer to 64
[ 0.431379] pci 0000:00:1c.1: enabling device (0104 -> 0107)
[ 0.431382] pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[ 0.431386] pci 0000:00:1c.1: setting latency timer to 64
[ 0.431392] pci 0000:00:1c.5: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[ 0.431395] pci 0000:00:1c.5: setting latency timer to 64
[ 0.431401] pci 0000:00:1e.0: setting latency timer to 64
[ 0.431404] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
[ 0.431406] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
[ 0.431408] pci_bus 0000:05: resource 0 io: [0xe000-0xefff]
[ 0.431410] pci_bus 0000:05: resource 1 mem: [0xfa000000-0xfebfffff]
[ 0.431413] pci_bus 0000:05: resource 2 pref mem [0xd0000000-0xdfffffff]
[ 0.431415] pci_bus 0000:02: resource 0 io: [0xc000-0xcfff]
[ 0.431417] pci_bus 0000:02: resource 1 mem: [0xf9e00000-0xf9efffff]
[ 0.431419] pci_bus 0000:02: resource 2 pref mem [0x80000000-0x801fffff]
[ 0.431421] pci_bus 0000:03: resource 0 io: [0x1000-0x1fff]
[ 0.431423] pci_bus 0000:03: resource 1 mem: [0x80200000-0x803fffff]
[ 0.431425] pci_bus 0000:03: resource 2 pref mem [0x80400000-0x805fffff]
[ 0.431427] pci_bus 0000:04: resource 0 io: [0xd000-0xdfff]
[ 0.431429] pci_bus 0000:04: resource 1 mem: [0xf9f00000-0xf9ffffff]
[ 0.431431] pci_bus 0000:04: resource 2 pref mem [0xcff00000-0xcfffffff]
[ 0.431434] pci_bus 0000:01: resource 0 io: [0xb000-0xbfff]
[ 0.431436] pci_bus 0000:01: resource 1 mem: [0xf8000000-0xf9dfffff]
[ 0.431438] pci_bus 0000:01: resource 2 pref mem [0x80600000-0x806fffff]
[ 0.431440] pci_bus 0000:01: resource 3 io: [0x00-0xffff]
[ 0.431442] pci_bus 0000:01: resource 4 mem: [0x000000-0xffffffff]
[ 0.431468] NET: Registered protocol family 2
[ 0.431542] IP route cache hash table entries: 32768 (order: 5,
131072 bytes)
[ 0.431755] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[ 0.432054] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.432195] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.432197] TCP reno registered
[ 0.432256] NET: Registered protocol family 1
[ 0.432380] pci 0000:05:00.0: Boot video device
[ 0.432392] pci 0000:01:02.0: Firmware left e100 interrupts enabled;
disabling
[ 0.432437] Unpacking initramfs...
[ 0.622805] Freeing initrd memory: 7828k freed
[ 0.625750] audit: initializing netlink socket (disabled)
[ 0.625761] type=2000 audit(1293174203.623:1): initialized
[ 0.628756] highmem bounce pool size: 64 pages
[ 0.628760] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[ 0.630027] VFS: Disk quotas dquot_6.5.2
[ 0.630072] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
^[[3~[ 0.630130] msgmni has been set to 1723
[ 0.630454] alg: No test for stdrng (krng)
[ 0.630508] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 253)
[ 0.630511] io scheduler noop registered
[ 0.630513] io scheduler anticipatory registered
[ 0.630514] io scheduler deadline registered
[ 0.630545] io scheduler cfq registered (default)
[ 0.630640] pcieport 0000:00:01.0: irq 24 for MSI/MSI-X
[ 0.630645] pcieport 0000:00:01.0: setting latency timer to 64
[ 0.630723] pcieport 0000:00:1c.0: irq 25 for MSI/MSI-X
[ 0.630730] pcieport 0000:00:1c.0: setting latency timer to 64
[ 0.630822] pcieport 0000:00:1c.1: irq 26 for MSI/MSI-X
[ 0.630828] pcieport 0000:00:1c.1: setting latency timer to 64
[ 0.630925] pcieport 0000:00:1c.5: irq 27 for MSI/MSI-X
[ 0.630931] pcieport 0000:00:1c.5: setting latency timer to 64
[ 0.631068] isapnp: Scanning for PnP cards...
[ 0.983913] isapnp: No Plug & Play device found
[ 0.984983] Linux agpgart interface v0.103
[ 0.985095] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.985178] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.985435] 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.985642] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at
0x60,0x64 irq 1,12
[ 0.988323] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.988328] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.988372] mice: PS/2 mouse device common for all mice
[ 0.988415] rtc_cmos 00:03: RTC can wake from S4
[ 0.988440] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 0.988461] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 0.988473] cpuidle: using governor ladder
[ 0.988474] cpuidle: using governor menu
[ 0.988478] No iBFT detected.
[ 0.988734] TCP cubic registered
[ 0.988843] NET: Registered protocol family 10
[ 0.989182] lo: Disabled Privacy Extensions
[ 0.989418] Mobile IPv6
[ 0.989420] NET: Registered protocol family 17
[ 0.989430] Using IPI No-Shortcut mode
[ 0.989477] PM: Resume from disk failed.
[ 0.989488] registered taskstats version 1
[ 0.989885] rtc_cmos 00:03: setting system clock to 2010-12-24
07:03:24 UTC (1293174204)
[ 0.989912] Initalizing network drop monitor service
[ 0.989939] Freeing unused kernel memory: 376k freed
[ 0.990088] Write protecting the kernel text: 2504k
[ 0.990117] Write protecting the kernel read-only data: 920k
[ 0.998078] udev[76]: starting version 164
[ 1.016767] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input0
[ 1.054575] usbcore: registered new interface driver usbfs
[ 1.054595] usbcore: registered new interface driver hub
[ 1.057063] usbcore: registered new device driver usb
[ 1.065356] SCSI subsystem initialized
[ 1.080030] libata version 3.00 loaded.
[ 1.081180] Floppy drive(s): fd0 is 1.44M
[ 1.082989] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 1.082992] e100: Copyright(c) 1999-2006 Intel Corporation
[ 1.083031] e100 0000:01:02.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 1.085989] ahci 0000:02:00.0: version 3.0
[ 1.086010] ahci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.087959] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.087973] r8169 0000:04:00.0: PCI INT A -> GSI 17 (level, low) ->
IRQ 17
[ 1.088005] r8169 0000:04:00.0: setting latency timer to 64
[ 1.088063] r8169 0000:04:00.0: irq 28 for MSI/MSI-X
[ 1.088548] eth0: RTL8168c/8111c at 0xf7e9c000, 00:21:85:1a:c6:72,
XID 1c4000c0 IRQ 28
[ 1.089884] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.089912] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low)
-> IRQ 18
[ 1.089923] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[ 1.089926] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[ 1.089942] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned
bus number 1
[ 1.089964] ehci_hcd 0000:00:1a.7: debug port 1
[ 1.093849] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
[ 1.093862] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xf7fff400
[ 1.101203] FDC 0 is a post-1991 82077
[ 1.104543] ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps
0x3 impl SATA mode
[ 1.104547] ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio
slum part
[ 1.104553] ahci 0000:02:00.0: setting latency timer to 64
[ 1.104672] scsi0 : ahci
[ 1.104763] scsi1 : ahci
[ 1.104836] ata1: SATA max UDMA/133 abar m8192@0xf9efe000 port
0xf9efe100 irq 16
[ 1.104840] ata2: SATA max UDMA/133 abar m8192@0xf9efe000 port
0xf9efe180 irq 16
[ 1.107169] e100 0000:01:02.0: PME# disabled
[ 1.107660] e100: eth1: e100_probe: addr 0xf9dff000, irq 21, MAC addr
00:d0:b7:85:0a:3f
[ 1.112036] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 1.112057] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.112060] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.112063] usb usb1: Product: EHCI Host Controller
[ 1.112065] usb usb1: Manufacturer: Linux 2.6.32-5-686 ehci_hcd
[ 1.112067] usb usb1: SerialNumber: 0000:00:1a.7
[ 1.112138] usb usb1: configuration #1 chosen from 1 choice
[ 1.112166] hub 1-0:1.0: USB hub found
[ 1.112173] hub 1-0:1.0: 6 ports detected
[ 1.112236] ata_piix 0000:00:1f.2: version 2.13
[ 1.112252] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low)
-> IRQ 19
[ 1.112256] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 1.112291] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 1.112353] scsi2 : ata_piix
[ 1.112410] scsi3 : ata_piix
[ 1.113471] ata3: SATA max UDMA/133 cmd 0xac00 ctl 0xa880 bmdma
0xa400 irq 19
[ 1.113476] ata4: SATA max UDMA/133 cmd 0xa800 ctl 0xa480 bmdma
0xa408 irq 19
[ 1.113519] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low)
-> IRQ 23
[ 1.113538] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 1.113541] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 1.113553] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned
bus number 2
[ 1.113574] ehci_hcd 0000:00:1d.7: debug port 1
[ 1.117469] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 1.117479] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf7fff800
[ 1.136006] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 1.136020] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.136023] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.136026] usb usb2: Product: EHCI Host Controller
[ 1.136028] usb usb2: Manufacturer: Linux 2.6.32-5-686 ehci_hcd
[ 1.136030] usb usb2: SerialNumber: 0000:00:1d.7
[ 1.136087] usb usb2: configuration #1 chosen from 1 choice
[ 1.136113] hub 2-0:1.0: USB hub found
[ 1.136125] hub 2-0:1.0: 6 ports detected
[ 1.136189] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low)
-> IRQ 19
[ 1.136193] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[ 1.136221] ata_piix 0000:00:1f.5: setting latency timer to 64
[ 1.136249] scsi4 : ata_piix
[ 1.136320] scsi5 : ata_piix
[ 1.137245] ata5: SATA max UDMA/133 cmd 0x9c00 ctl 0x9880 bmdma
0x9400 irq 19
[ 1.137249] ata6: SATA max UDMA/133 cmd 0x9800 ctl 0x9480 bmdma
0x9408 irq 19
[ 1.152772] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.152810] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low)
-> IRQ 16
[ 1.152816] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[ 1.152819] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[ 1.152828] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned
bus number 3
[ 1.152850] uhci_hcd 0000:00:1a.0: irq 16, io base 0x00008800
[ 1.152878] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.152880] usb usb3: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.152882] usb usb3: Product: UHCI Host Controller
[ 1.152884] usb usb3: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.152886] usb usb3: SerialNumber: 0000:00:1a.0
[ 1.152994] usb usb3: configuration #1 chosen from 1 choice
[ 1.153019] hub 3-0:1.0: USB hub found
[ 1.153026] hub 3-0:1.0: 2 ports detected
[ 1.153067] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low)
-> IRQ 21
[ 1.153072] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[ 1.153075] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[ 1.153081] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned
bus number 4
[ 1.153108] uhci_hcd 0000:00:1a.1: irq 21, io base 0x00008480
[ 1.153132] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.153135] usb usb4: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.153136] usb usb4: Product: UHCI Host Controller
[ 1.153138] usb usb4: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.153140] usb usb4: SerialNumber: 0000:00:1a.1
[ 1.153193] usb usb4: configuration #1 chosen from 1 choice
[ 1.153215] hub 4-0:1.0: USB hub found
[ 1.153220] hub 4-0:1.0: 2 ports detected
[ 1.153258] uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low)
-> IRQ 19
[ 1.153263] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[ 1.153266] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[ 1.153274] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned
bus number 5
[ 1.153295] uhci_hcd 0000:00:1a.2: irq 19, io base 0x00008400
[ 1.153320] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.153322] usb usb5: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.153324] usb usb5: Product: UHCI Host Controller
[ 1.153325] usb usb5: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.153327] usb usb5: SerialNumber: 0000:00:1a.2
[ 1.153391] usb usb5: configuration #1 chosen from 1 choice
[ 1.153414] hub 5-0:1.0: USB hub found
[ 1.153419] hub 5-0:1.0: 2 ports detected
[ 1.153459] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low)
-> IRQ 23
[ 1.153465] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 1.153468] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 1.153474] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned
bus number 6
[ 1.153496] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00009000
[ 1.153526] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.153527] usb usb6: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.153528] usb usb6: Product: UHCI Host Controller
[ 1.153530] usb usb6: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.153532] usb usb6: SerialNumber: 0000:00:1d.0
[ 1.153586] usb usb6: configuration #1 chosen from 1 choice
[ 1.153609] hub 6-0:1.0: USB hub found
[ 1.153614] hub 6-0:1.0: 2 ports detected
[ 1.153651] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low)
-> IRQ 19
[ 1.153656] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 1.153659] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 1.153666] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned
bus number 7
[ 1.153687] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00008c00
[ 1.153715] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.153717] usb usb7: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.153719] usb usb7: Product: UHCI Host Controller
[ 1.153720] usb usb7: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.153722] usb usb7: SerialNumber: 0000:00:1d.1
[ 1.153780] usb usb7: configuration #1 chosen from 1 choice
[ 1.153803] hub 7-0:1.0: USB hub found
[ 1.153808] hub 7-0:1.0: 2 ports detected
[ 1.153844] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low)
-> IRQ 18
[ 1.153849] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 1.153852] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 1.153857] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned
bus number 8
[ 1.153879] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00008880
[ 1.153906] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.153908] usb usb8: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.153910] usb usb8: Product: UHCI Host Controller
[ 1.153912] usb usb8: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.153913] usb usb8: SerialNumber: 0000:00:1d.2
[ 1.153963] usb usb8: configuration #1 chosen from 1 choice
[ 1.153986] hub 8-0:1.0: USB hub found
[ 1.153990] hub 8-0:1.0: 2 ports detected
[ 1.180915] pata_jmicron 0000:02:00.1: enabling device (0000 -> 0001)
[ 1.180922] pata_jmicron 0000:02:00.1: PCI INT B -> GSI 17 (level,
low) -> IRQ 17
[ 1.180950] pata_jmicron 0000:02:00.1: setting latency timer to 64
[ 1.181024] scsi6 : pata_jmicron
[ 1.181112] scsi7 : pata_jmicron
[ 1.181602] ata7: PATA max UDMA/100 cmd 0xcc00 ctl 0xc880 bmdma
0xc400 irq 17
[ 1.181605] ata8: PATA max UDMA/100 cmd 0xc800 ctl 0xc480 bmdma
0xc408 irq 17
[ 1.420029] ata2: SATA link down (SStatus 0 SControl 300)
[ 1.425023] ata1: SATA link down (SStatus 0 SControl 300)
[ 1.463541] ata6: SATA link down (SStatus 0 SControl 300)
[ 1.474052] ata5: SATA link down (SStatus 0 SControl 300)
[ 1.522219] ata7.00: ATA-6: ST380011A, 8.01, max UDMA/100
[ 1.522223] ata7.00: 156301488 sectors, multi 16: LBA48
[ 1.522569] ata7.01: ATA-5: QUANTUM FIREBALLP LM15, A35.0700, max UDMA/66
[ 1.522573] ata7.01: 29336832 sectors, multi 16: LBA
[ 1.536763] ata7.00: configured for UDMA/100
[ 1.552875] ata7.01: configured for UDMA/66
[ 1.604009] usb 4-2: new low speed USB device using uhci_hcd and
address 2
[ 1.767073] ata4.00: SATA link down (SStatus 0 SControl 300)
[ 1.767084] ata4.01: SATA link down (SStatus 0 SControl 300)
[ 1.908053] ata3.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.908065] ata3.01: SATA link down (SStatus 0 SControl 300)
[ 1.908075] ata3.01: link offline, clearing class 3 to NONE
[ 1.909126] usb 4-2: New USB device found, idVendor=051d, idProduct=0002
[ 1.909129] usb 4-2: New USB device strings: Mfr=3, Product=1,
SerialNumber=2
[ 1.909132] usb 4-2: Product: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8
[ 1.909134] usb 4-2: Manufacturer: American Power Conversion
[ 1.909136] usb 4-2: SerialNumber: QB0512132444
[ 1.909207] usb 4-2: configuration #1 chosen from 1 choice
[ 1.917686] ata3.00: ATAPI: PIONEER DVD-RW DVR-218L, 1.02, max UDMA/100
[ 1.933703] ata3.00: configured for UDMA/100
[ 1.936750] scsi 2:0:0:0: CD-ROM PIONEER DVD-RW DVR-218L
1.02 PQ: 0 ANSI: 5
[ 1.937024] scsi 6:0:0:0: Direct-Access ATA ST380011A
8.01 PQ: 0 ANSI: 5
[ 1.937163] scsi 6:0:1:0: Direct-Access ATA QUANTUM FIREBALL
A35. PQ: 0 ANSI: 5
[ 2.107125] usbcore: registered new interface driver hiddev
[ 2.112204] sd 6:0:0:0: [sda] 156301488 512-byte logical blocks:
(80.0 GB/74.5 GiB)
[ 2.112283] sd 6:0:1:0: [sdb] 29336832 512-byte logical blocks: (15.0
GB/13.9 GiB)
[ 2.112338] sd 6:0:0:0: [sda] Write Protect is off
[ 2.112341] sd 6:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.112379] sd 6:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 2.112508] sda:
[ 2.117340] sd 6:0:1:0: [sdb] Write Protect is off
[ 2.117344] sd 6:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[ 2.117347] sda1 sda2 <sr0: scsi3-mmc drive: 40x/40x writer dvd-ram
cd/rw xa/form2 cdda tray
[ 2.124595] Uniform CD-ROM driver Revision: 3.20
[ 2.124677] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 2.127567] sda5
[ 2.127573] sd 6:0:1:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 2.137836] sda6 sda7 sda8 sda9
[ 2.178389] sdb: sda10 sdb1
[ 2.196039] sda11 sda12 >
[ 2.203196] sd 6:0:1:0: [sdb] Attached SCSI disk
[ 2.203539] sd 6:0:0:0: [sda] Attached SCSI disk
[ 2.207342] sr 2:0:0:0: Attached scsi generic sg0 type 5
[ 2.207375] sd 6:0:0:0: Attached scsi generic sg1 type 0
[ 2.207401] sd 6:0:1:0: Attached scsi generic sg2 type 0
[ 3.175194] generic-usb 0003:051D:0002.0001: hiddev0,hidraw0: USB HID
v1.10 Device [American Power Conversion Back-UPS RS 1500 FW:8.g8 .D USB
FW:g8 ] on usb-0000:00:1a.1-2/input0
[ 3.175223] usbcore: registered new interface driver usbhid
[ 3.175225] usbhid: v2.6:USB HID core driver
[ 3.251923] PM: Starting manual resume from disk
[ 3.251926] PM: Resume from partition 8:10
[ 3.251927] PM: Checking hibernation image.
[ 3.252151] PM: Error -22 checking image file
[ 3.252153] PM: Resume from disk failed.
[ 3.267654] kjournald starting. Commit interval 5 seconds
[ 3.267662] EXT3-fs: mounted filesystem with ordered data mode.
[ 5.200312] udev[499]: starting version 164
[ 5.360701] input: Power Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[ 5.360707] ACPI: Power Button [PWRB]
[ 5.360752] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 5.360755] ACPI: Power Button [PWRF]
[ 5.572041] ACPI: SSDT 7ff9e0c0 001F3 (v01 DpgPmm P001Ist 00000011
INTL 20051117)
[ 5.572269] processor LNXCPU:00: registered as cooling_device0
[ 5.572727] ACPI: SSDT 7ff9e2c0 001F3 (v01 DpgPmm P002Ist 00000012
INTL 20051117)
[ 5.572933] processor LNXCPU:01: registered as cooling_device1
[ 5.573246] ACPI: SSDT 7ff9e4c0 001F3 (v01 DpgPmm P003Ist 00000012
INTL 20051117)
[ 5.573448] processor LNXCPU:02: registered as cooling_device2
[ 5.573810] ACPI: SSDT 7ff9e6c0 001F3 (v01 DpgPmm P004Ist 00000012
INTL 20051117)
[ 5.574022] processor LNXCPU:03: registered as cooling_device3
[ 5.643771] input: PC Speaker as /devices/platform/pcspkr/input/input3
[ 6.535506] nvidia: module license 'NVIDIA' taints kernel.
[ 6.535509] Disabling lock debugging due to kernel taint
[ 7.301290] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low)
-> IRQ 18
[ 7.542723] nvidia 0000:05:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 7.542732] nvidia 0000:05:00.0: setting latency timer to 64
[ 7.542736] vgaarb: device changed decodes:
PCI:0000:05:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[ 7.542843] NVRM: loading NVIDIA UNIX x86 Kernel Module 260.19.29
Wed Dec 8 12:09:09 PST 2010
[ 7.593043] Linux video capture interface: v2.00
[ 7.896891] cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
[ 7.896927] cx8800 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 7.897409] cx88[0]: Your board isn't known (yet) to the driver. You can
[ 7.897410] cx88[0]: try to pick one of the existing card configs via
[ 7.897411] cx88[0]: card=<n> insmod option. Updating to the latest
[ 7.897412] cx88[0]: version might help as well.
[ 7.897629] cx88[0]: Here is a list of valid choices for the card=<n>
insmod option:
[ 7.897694] cx88[0]: card=0 -> UNKNOWN/GENERIC
[ 7.897744] cx88[0]: card=1 -> Hauppauge WinTV 34xxx models
[ 7.897795] cx88[0]: card=2 -> GDI Black Gold
[ 7.897844] cx88[0]: card=3 -> PixelView
[ 7.897892] cx88[0]: card=4 -> ATI TV Wonder Pro
[ 7.897942] cx88[0]: card=5 -> Leadtek Winfast 2000XP Expert
[ 7.897994] cx88[0]: card=6 -> AverTV Studio 303 (M126)
[ 7.898044] cx88[0]: card=7 -> MSI TV-@nywhere Master
[ 7.898095] cx88[0]: card=8 -> Leadtek Winfast DV2000
[ 7.898146] cx88[0]: card=9 -> Leadtek PVR 2000
[ 7.898196] cx88[0]: card=10 -> IODATA GV-VCP3/PCI
[ 7.898247] cx88[0]: card=11 -> Prolink PlayTV PVR
[ 7.898297] cx88[0]: card=12 -> ASUS PVR-416
[ 7.898345] cx88[0]: card=13 -> MSI TV-@nywhere
[ 7.898395] cx88[0]: card=14 -> KWorld/VStream XPert DVB-T
[ 7.898445] cx88[0]: card=15 -> DViCO FusionHDTV DVB-T1
[ 7.898495] cx88[0]: card=16 -> KWorld LTV883RF
[ 7.898544] cx88[0]: card=17 -> DViCO FusionHDTV 3 Gold-Q
[ 7.898595] cx88[0]: card=18 -> Hauppauge Nova-T DVB-T
[ 7.898645] cx88[0]: card=19 -> Conexant DVB-T reference design
[ 7.898696] cx88[0]: card=20 -> Provideo PV259
[ 7.898745] cx88[0]: card=21 -> DViCO FusionHDTV DVB-T Plus
[ 7.898796] cx88[0]: card=22 -> pcHDTV HD3000 HDTV
[ 7.898845] cx88[0]: card=23 -> digitalnow DNTV Live! DVB-T
[ 7.898896] cx88[0]: card=24 -> Hauppauge WinTV 28xxx (Roslyn) models
[ 7.898948] cx88[0]: card=25 -> Digital-Logic MICROSPACE
Entertainment Center (MEC)
[ 7.899013] cx88[0]: card=26 -> IODATA GV/BCTV7E
[ 7.899062] cx88[0]: card=27 -> PixelView PlayTV Ultra Pro (Stereo)
[ 7.899114] cx88[0]: card=28 -> DViCO FusionHDTV 3 Gold-T
[ 7.900069] cx88[0]: card=29 -> ADS Tech Instant TV DVB-T PCI
[ 7.900120] cx88[0]: card=30 -> TerraTec Cinergy 1400 DVB-T
[ 7.900170] cx88[0]: card=31 -> DViCO FusionHDTV 5 Gold
[ 7.900220] cx88[0]: card=32 -> AverMedia UltraTV Media Center PCI 550
[ 7.900272] cx88[0]: card=33 -> Kworld V-Stream Xpert DVD
[ 7.900323] cx88[0]: card=34 -> ATI HDTV Wonder
[ 7.900372] cx88[0]: card=35 -> WinFast DTV1000-T
[ 7.900421] cx88[0]: card=36 -> AVerTV 303 (M126)
[ 7.900470] cx88[0]: card=37 -> Hauppauge Nova-S-Plus DVB-S
[ 7.900527] cx88[0]: card=38 -> Hauppauge Nova-SE2 DVB-S
[ 7.900577] cx88[0]: card=39 -> KWorld DVB-S 100
[ 7.900626] cx88[0]: card=40 -> Hauppauge WinTV-HVR1100 DVB-T/Hybrid
[ 7.900678] cx88[0]: card=41 -> Hauppauge WinTV-HVR1100
DVB-T/Hybrid (Low Profile)
[ 7.900743] cx88[0]: card=42 -> digitalnow DNTV Live! DVB-T Pro
[ 7.900794] cx88[0]: card=43 -> KWorld/VStream XPert DVB-T with
cx22702
[ 7.900847] cx88[0]: card=44 -> DViCO FusionHDTV DVB-T Dual Digital
[ 7.900898] cx88[0]: card=45 -> KWorld HardwareMpegTV XPert
[ 7.900949] cx88[0]: card=46 -> DViCO FusionHDTV DVB-T Hybrid
[ 7.901016] cx88[0]: card=47 -> pcHDTV HD5500 HDTV
[ 7.901066] cx88[0]: card=48 -> Kworld MCE 200 Deluxe
[ 7.901115] cx88[0]: card=49 -> PixelView PlayTV P7000
[ 7.901166] cx88[0]: card=50 -> NPG Tech Real TV FM Top 10
[ 7.901216] cx88[0]: card=51 -> WinFast DTV2000 H
[ 7.901265] cx88[0]: card=52 -> Geniatech DVB-S
[ 7.901314] cx88[0]: card=53 -> Hauppauge WinTV-HVR3000 TriMode
Analog/DVB-S/DVB-T
[ 7.901379] cx88[0]: card=54 -> Norwood Micro TV Tuner
[ 7.901429] cx88[0]: card=55 -> Shenzhen Tungsten Ages Tech
TE-DTV-250 / Swann OEM
[ 7.901494] cx88[0]: card=56 -> Hauppauge WinTV-HVR1300
DVB-T/Hybrid MPEG Encoder
[ 7.901559] cx88[0]: card=57 -> ADS Tech Instant Video PCI
[ 7.901610] cx88[0]: card=58 -> Pinnacle PCTV HD 800i
[ 7.901660] cx88[0]: card=59 -> DViCO FusionHDTV 5 PCI nano
[ 7.901710] cx88[0]: card=60 -> Pinnacle Hybrid PCTV
[ 7.901760] cx88[0]: card=61 -> Leadtek TV2000 XP Global
[ 7.901810] cx88[0]: card=62 -> PowerColor RA330
[ 7.901859] cx88[0]: card=63 -> Geniatech X8000-MT DVBT
[ 7.901910] cx88[0]: card=64 -> DViCO FusionHDTV DVB-T PRO
[ 7.901960] cx88[0]: card=65 -> DViCO FusionHDTV 7 Gold
[ 7.902010] cx88[0]: card=66 -> Prolink Pixelview MPEG 8000GT
[ 7.902061] cx88[0]: card=67 -> Kworld PlusTV HD PCI 120 (ATSC 120)
[ 7.902113] cx88[0]: card=68 -> Hauppauge WinTV-HVR4000
DVB-S/S2/T/Hybrid
[ 7.902165] cx88[0]: card=69 -> Hauppauge WinTV-HVR4000(Lite) DVB-S/S2
[ 7.902217] cx88[0]: card=70 -> TeVii S460 DVB-S/S2
[ 7.902267] cx88[0]: card=71 -> Omicom SS4 DVB-S/S2 PCI
[ 7.902317] cx88[0]: card=72 -> TBS 8920 DVB-S/S2
[ 7.902366] cx88[0]: card=73 -> TeVii S420 DVB-S
[ 7.902416] cx88[0]: card=74 -> Prolink Pixelview Global Extreme
[ 7.902467] cx88[0]: card=75 -> PROF 7300 DVB-S/S2
[ 7.902517] cx88[0]: card=76 -> SATTRADE ST4200 DVB-S/S2
[ 7.902567] cx88[0]: card=77 -> TBS 8910 DVB-S
[ 7.902616] cx88[0]: card=78 -> Prof 6200 DVB-S
[ 7.902665] cx88[0]: card=79 -> Terratec Cinergy HT PCI MKII
[ 7.902716] cx88[0]: card=80 -> Hauppauge WinTV-IR Only
[ 7.902766] cx88[0]: card=81 -> Leadtek WinFast DTV1800 Hybrid
[ 7.902817] cx88[0]: card=82 -> WinFast DTV2000 H rev. J
[ 7.902868] cx88[0]: subsystem: 1043:4820, board: UNKNOWN/GENERIC
[card=0,autodetected], frontend(s): 0
[ 7.902870] cx88[0]: TV tuner type -1, Radio tuner type -1
[ 8.103416] input: ImPS/2 Generic Wheel Mouse as
/devices/platform/i8042/serio1/input/input4
[ 8.208914] All bytes are equal. It is not a TEA5767
[ 8.208966] tuner 1-0060: chip found @ 0xc0 (cx88[0])
[ 8.261603] cx88[0]/0: found at 0000:01:00.0, rev: 3, irq: 16,
latency: 64, mmio: 0xf8000000
[ 8.261611] IRQ 16/cx88[0]: IRQF_DISABLED is not guaranteed on shared
IRQs
[ 8.261670] cx88[0]/0: registered device video0 [v4l2]
[ 8.261690] cx88[0]/0: registered device vbi0
[ 8.261703] tuner 1-0060: tuner type not set
[ 8.322316] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low)
-> IRQ 22
[ 8.322345] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 9.000791] hda_codec: ALC888: BIOS auto-probing.
[ 9.002140] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input5
[ 9.531118] Adding 2361512k swap on /dev/sda10. Priority:-1
extents:1 across:2361512k
[ 10.220891] EXT3 FS on sda1, internal journal
[ 10.310001] loop: module loaded
[ 10.353889] fuse init (API version 7.13)
[ 10.440366] f71882fg: Found f71882fg chip at 0xa00, revision 32
[ 10.440747] f71882fg f71882fg.2560: Fan: 1 is in duty-cycle mode
[ 10.440749] f71882fg f71882fg.2560: Fan: 2 is in duty-cycle mode
[ 10.440751] f71882fg f71882fg.2560: Fan: 3 is in duty-cycle mode
[ 10.440753] f71882fg f71882fg.2560: Fan: 4 is in duty-cycle mode
[ 13.804999] kjournald starting. Commit interval 5 seconds
[ 13.805222] EXT3 FS on sda5, internal journal
[ 13.805226] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.884006] kjournald starting. Commit interval 5 seconds
[ 13.884235] EXT3 FS on sda6, internal journal
[ 13.884238] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.964617] kjournald starting. Commit interval 5 seconds
[ 13.964880] EXT3 FS on sda7, internal journal
[ 13.964883] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.321677] kjournald starting. Commit interval 5 seconds
[ 14.321953] EXT3 FS on sda8, internal journal
[ 14.321958] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.420728] kjournald starting. Commit interval 5 seconds
[ 14.421031] EXT3 FS on sda9, internal journal
[ 14.421035] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.787337] kjournald starting. Commit interval 5 seconds
[ 14.787631] EXT3 FS on sda11, internal journal
[ 14.787635] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.999960] kjournald starting. Commit interval 5 seconds
[ 15.000215] EXT3 FS on sda12, internal journal
[ 15.000219] EXT3-fs: mounted filesystem with ordered data mode.
[ 15.058534] kjournald starting. Commit interval 5 seconds
[ 15.058869] EXT3 FS on sdb1, internal journal
[ 15.058872] EXT3-fs: mounted filesystem with ordered data mode.
[ 16.097019] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 16.130104] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 16.130310] CONFIG_NF_CT_ACCT is deprecated and will be removed soon.
Please use
[ 16.130312] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack
module option or
[ 16.130314] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 17.222471] r8169: eth0: link up
[ 17.222476] r8169: eth0: link up
[ 28.012503] eth0: no IPv6 routers present
[ 34.538181] vboxdrv: Found 4 processor cores.
[ 34.538297] vboxdrv: fAsync=0 offMin=0x3f7 offMax=0x41ae
[ 34.538337] vboxdrv: TSC mode is 'synchronous', kernel timer mode is
'normal'.
[ 34.538339] vboxdrv: Successfully loaded version 4.0.0 (interface
0x00160000).
[ 895.970803] warning: `VirtualBox' uses 32-bit capabilities (legacy
support in use)
[ 910.787660] device eth0 entered promiscuous mode
[ 959.830291] device eth0 left promiscuous mode
[ 959.832794] device eth0 entered promiscuous mode
[ 1163.666513] device eth0 left promiscuous mode
[ 1163.668893] device eth0 entered promiscuous mode
[ 1513.840251] device eth0 left promiscuous mode
I was surprised that kernel doesn't have a driver for it. I guess this
TV tuner card isn't popular. :(
$ lspci
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller
(rev 02)
00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root
Port (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #4
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #5
00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #6
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2
EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio
Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
Root Port 1
00:1c.1 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
Port 2
00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express
Root Port 6
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #3
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2
EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIB (ICH10) LPC Interface
Controller
00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port
SATA IDE Controller #1
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port
SATA IDE Controller #2
01:00.0 Multimedia video controller: Conexant Systems, Inc.
CX23880/1/2/3 PCI Video and Audio Decoder (rev 03)
01:02.0 Ethernet controller: Intel Corporation 82559 InBusiness 10/100
(rev 08)
02:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial
ATA Controller (rev 03)
02:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA
Controller (rev 03)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
05:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800
GT] (rev a2)
I looked online for drivers, including ASUS' web site, but no luck. I do
have the original CDs (copyrighted 2002), but it is for Windows only. I
also have never done TV stuff under Linux/Debian (only Windows), so I
might be doing this wrong/incorrectly or not looking in the right places?
Thank you in advance. :)
--
"It's kind of an insane case ... 6,000 ants dressed up as rice and
robbed a Chinese restaurant." --Steven Wright
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.
J G Miller
> so I might be doing this wrong/incorrectly
> or not looking in the right places?
Yes you are looking in the wrong place.
You need to look at
<http://www.linuxtv.ORG/wiki/index.php/Cx88_devices_(cx2388x)>
Incidentally are there still any sources of analog NTSC broadcasts
in your area, or will you be using the card to capture analog video
from an analog video device?
Ant
>> so I might be doing this wrong/incorrectly
>> or not looking in the right places?
>
> Yes you are looking in the wrong place.
>
> You need to look at
>
> <http://www.linuxtv.ORG/wiki/index.php/Cx88_devices_(cx2388x)>
Thanks. I will look into that.
> Incidentally are there still any sources of analog NTSC broadcasts
> in your area, or will you be using the card to capture analog video
> from an analog video device?
Just analog video devices like VCR.
--
"The little ant at its hole is full of courage." --African
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is/was listening to a song on this computer: Superman (Theme)
Ant
> On 12/24/2010 10:10 AM PT, J G Miller typed:
>
>>> so I might be doing this wrong/incorrectly
>>> or not looking in the right places?
>>
>> Yes you are looking in the wrong place.
>>
>> You need to look at
>>
>> <http://www.linuxtv.ORG/wiki/index.php/Cx88_devices_(cx2388x)>
>
> Thanks. I will look into that.
Hmm, I must be doing this wrong as a newbie or its installation
instructions/steps are outdated (mentions kernel v2.6.20 and I am at
v2.6.32) since it is not working:
# modprobe cx88-dvb
FATAL: Error inserting cx88_dvb
(/lib/modules/2.6.32-5-686/kernel/drivers/media/video/cx88/cx88-dvb.ko):
No such device
# locate cc88-dvb.ko
# ls /lib/modules/2.6.32-5-686/kernel/drivers/media/video/cx88
cx8800.ko cx8802.ko cx88-alsa.ko cx88-blackbird.ko cx88-dvb.ko
cx88-vp3054-i2c.ko cx88xx.ko
Which one should I use? I see no ...880. :(
--
"This is what metaphor is. It is not saying that an ant is an elephant.
Perhaps; both are alive. No. Metaphor is saying the ant is an elephant.
Now, logically speaking, I know there is a difference. If you put
elephants and ants before me, I believe that every time I will correctly
identify the elephant and the ant. So metaphor must come from a very
different place than that of the logical, intelligent mind. It comes
from a place that is very courageous, willing to step out of our
preconceived ways of seeing things and open so large that it can see the
oneness in an ant and in an elephant." --Natalie Goldberg
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is/was listening to a song on this computer: American Cinema
Orchestra - Superman II
J G Miller
> # modprobe cx88-dvb
> FATAL: Error inserting cx88_dvb
As you have an analog device, there is no point in even trying to
load a DVB module.
> Which one should I use? I see no ...880. :(
You do not need one.
DVB = Digital Video Broadcast
And North America uses ATSC for digital television broadcasts rather than DVB.
But this card is analog NTSC only.
The modules you do need to load are the ones for analog, namely those
providing
QUOTE
Conexant 2388x (bt878 successor) support
Conexant 2388x DMA audio support
UNQUOTE
Now if you had bothered to actually read the dmesg output, you would have seen
what it is you need to do.
The appropriate cx2388 modules are automagically being loaded but you have to
tell the cx2388x kernel module which type of card you have, because it is
unable to detect the type of card automatically.
QUOTE
[ 7.897409] cx88[0]: Your board isn't known (yet) to the driver. You can
[ 7.897410] cx88[0]: try to pick one of the existing card configs via
[ 7.897411] cx88[0]: card=<n> insmod option. Updating to the latest
[ 7.897412] cx88[0]: version might help as well.
[ 7.897629] cx88[0]: Here is a list of valid choices for the card=<n>
insmod option:
UNQUOTE
So in /etc/modprobe.d you need to create a configuration file, perhaps
named
cx2388.conf
with the entry
options cx2388 card=<number>
where number is the number listed in the dmesg output specific to your card.
Now if you had done a web search, you would have found that the number that
is suggested one use from
since an exact match from the list is not possible, is 12.
This may or may not work, and using another number for a similar card from
another manufacturer may give better results.
A good place to ask if other people have experience of setting this card up
under Linux is at the Linux sub-forum at
Ant
>> # modprobe cx88-dvb
>> FATAL: Error inserting cx88_dvb
>
> As you have an analog device, there is no point in even trying to
> load a DVB module.
Ah OK. I thought it was needed even though I don't use digital. In fact,
this TV tuner card doesn't do digital. It's very old.
>> Which one should I use? I see no ...880. :(
>
> You do not need one.
>
> DVB = Digital Video Broadcast
>
> And North America uses ATSC for digital television broadcasts rather than DVB.
Ah.
> But this card is analog NTSC only.
>
> The modules you do need to load are the ones for analog, namely those
> providing
>
> QUOTE
>
> Conexant 2388x (bt878 successor) support
> Conexant 2388x DMA audio support
>
> UNQUOTE
>
> Now if you had bothered to actually read the dmesg output, you would have seen
> what it is you need to do.
>
> The appropriate cx2388 modules are automagically being loaded but you have to
> tell the cx2388x kernel module which type of card you have, because it is
> unable to detect the type of card automatically.
Ah.
> QUOTE
> [ 7.897409] cx88[0]: Your board isn't known (yet) to the driver. You can
> [ 7.897410] cx88[0]: try to pick one of the existing card configs via
> [ 7.897411] cx88[0]: card=<n> insmod option. Updating to the latest
> [ 7.897412] cx88[0]: version might help as well.
> [ 7.897629] cx88[0]: Here is a list of valid choices for the card=<n>
> insmod option:
> UNQUOTE
>
> So in /etc/modprobe.d you need to create a configuration file, perhaps
> named
>
> cx2388.conf
>
> with the entry
>
> options cx2388 card=<number>
>
> where number is the number listed in the dmesg output specific to your card.
>
> Now if you had done a web search, you would have found that the number that
> is suggested one use from
>
> <http://www.linuxquestions.ORG/questions/linux-hardware-18/help-me-configure-a-asus-tv-tuner-in-ubuntu-344884/>
>
> since an exact match from the list is not possible, is 12.
>
> This may or may not work, and using another number for a similar card from
> another manufacturer may give better results.
# pwd
/etc/modprobe.d
# ls -all
total 23
drwxr-xr-x 2 root root 1024 Dec 24 11:37 .
drwxr-xr-x 148 root root 10240 Dec 24 11:04 ..
-rw-r--r-- 1 root root 4832 Mar 12 2010 aliases.conf
-rw-r--r-- 1 root root 281 Sep 6 2009 alsa-base-blacklist.conf
-rw-r--r-- 1 root root 1183 Jun 2 2010 alsa-base.conf
-rw-r--r-- 1 root root 776 Jun 4 2010 blacklist.conf
-rw-r--r-- 1 root root 65 Dec 24 11:37 cx2388.conf
-rw-r--r-- 1 root root 456 Feb 18 2010 fbdev-blacklist.conf
lrwxrwxrwx 1 root root 41 Nov 3 07:36 linux-sound-base_noOSS.conf
-> /lib/linux-sound-base/noOSS.modprobe.conf
lrwxrwxrwx 1 root root 21 Apr 3 2009 oss-compat.conf ->
/lib/oss-compat/linux
-rw-r--r-- 1 root root 26 May 14 2010 radeon-kms.conf
# cat cx2388.conf
# ASUS TV Tuner Card 880 NTSC (cx23880)
options cx2388 card=12
Do I have to reboot for this or can't I just tell my Debian/Linux to
look for this (don't know the command). I thought it was insmod command,
but it didn't work:
# insmod cx2388
insmod: can't read 'cx2388': No such file or directory
> A good place to ask if other people have experience of setting this card up
> under Linux is at the Linux sub-forum at
>
> <http://www.tv-cards.COM/messageboard/viewforum.php?id=27>
Thanks and bookmarked. At least I got a good start now. :)
--
"Ants can lift up to 50 times their own weight. And your monitor is
missing. Time to bring out the bugspray." --BBspot's Geek Horoscopes
(2/28/2003)
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
J G Miller
> # cat cx2388.conf
> # ASUS TV Tuner Card 880 NTSC (cx23880)
>
> options cx2388 card=12
Looks good!
> Do I have to reboot for this
Unless something is messed up in the kernel or electronics of the card,
requiring a reboot, or even power down, a reboot should not be necessary.
> I thought it was insmod command, but it didn't work:
insmod is a "low level" command and requires the full path to
the kernel module and its extension to be specified.
It is better to use modprobe, and with the -a flag, to pull
in anything else which may be needed. This does however require
the modules dependency file to be up to date but since you have
not been doing any custom kernel or module building you will not
need to worry about doing a depmod -a.
So just try
modprobe -a cx2388
and then immediately do a dmesg to see if that indicates a
successfully loading of the module with the appropriate parameter.
If it does, then you will have to worry about installing something
like xawtv to make use of your card.
Ant
> > # ASUS TV Tuner Card 880 NTSC (cx23880)
> >
> > options cx2388 card=12
> Looks good!
Cool. :)
> > Do I have to reboot for this
> Unless something is messed up in the kernel or electronics of the card,
> requiring a reboot, or even power down, a reboot should not be necessary.
OK.
> > I thought it was insmod command, but it didn't work:
> insmod is a "low level" command and requires the full path to
> the kernel module and its extension to be specified.
> It is better to use modprobe, and with the -a flag, to pull
> in anything else which may be needed. This does however require
> the modules dependency file to be up to date but since you have
> not been doing any custom kernel or module building you will not
> need to worry about doing a depmod -a.
Before I tried modprobe, I wanted to see what I had before it:
# lsmod
Module Size Used by
acpi_cpufreq 4951 0
cpufreq_powersave 602 0
cpufreq_userspace 1480 0
cpufreq_stats 1940 0
cpufreq_conservative 4018 0
cx88_vp3054_i2c 1264 0
cx8802 9405 0
videobuf_dvb 3390 0
dvb_core 62650 1 videobuf_dvb
vboxnetadp 5254 0
vboxnetflt 15384 0
vboxdrv 144401 2 vboxnetadp,vboxnetflt
xt_tcpudp 1743 92
xt_limit 1088 2
nf_conntrack_ipv4 7597 59
nf_defrag_ipv4 779 1 nf_conntrack_ipv4
xt_state 927 59
ipt_LOG 3570 2
ipt_REJECT 1517 2
nf_conntrack_irc 2535 0
nf_conntrack_ftp 4272 0
nf_conntrack 38075 4
nf_conntrack_ipv4,xt_state,nf_conntrack_irc,nf_conntrack_ftp
iptable_filter 1790 1
ip_tables 7690 1 iptable_filter
x_tables 8327 6
xt_tcpudp,xt_limit,xt_state,ipt_LOG,ipt_REJECT,ip_tables
f71882fg 18898 0
coretemp 3401 0
adt7473 8792 0
fuse 43941 1
loop 9765 0
snd_hda_codec_realtek 163282 1
snd_hda_intel 16787 1
snd_hda_codec 46002 2 snd_hda_codec_realtek,snd_hda_intel
tea5767 4529 0
snd_hwdep 4054 1 snd_hda_codec
snd_pcm_oss 28671 0
snd_mixer_oss 10461 1 snd_pcm_oss
tuner 14428 1
snd_pcm 47222 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi 3576 0
cx8800 20155 0
snd_rawmidi 12513 1 snd_seq_midi
cx88xx 59092 2 cx8802,cx8800
snd_seq_midi_event 3684 1 snd_seq_midi
ir_common 22187 1 cx88xx
snd_seq 35463 2 snd_seq_midi,snd_seq_midi_event
i2c_algo_bit 3497 2 cx88_vp3054_i2c,cx88xx
snd_timer 12258 2 snd_pcm,snd_seq
tveeprom 9393 1 cx88xx
snd_seq_device 3673 3 snd_seq_midi,snd_rawmidi,snd_seq
v4l2_common 9820 3 tuner,cx8800,cx88xx
videodev 25545 4 tuner,cx8800,cx88xx,v4l2_common
v4l1_compat 10250 1 videodev
videobuf_dma_sg 7203 3 cx8802,cx8800,cx88xx
videobuf_core 10476 5
cx8802,videobuf_dvb,cx8800,cx88xx,videobuf_dma_sg
snd 34375 13
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 3450 1 snd
snd_page_alloc 5045 2 snd_hda_intel,snd_pcm
btcx_risc 2499 3 cx8802,cx8800,cx88xx
i2c_i801 6462 0
psmouse 44657 0
nvidia 9222163 38
i2c_core 12696 12
cx88_vp3054_i2c,adt7473,tea5767,tuner,cx8800,cx88xx,i2c_algo_bit,tveeprom,v4l2_common,videodev,i2c_i801,nvidia
pcspkr 1207 0
serio_raw 2916 0
evdev 5609 7
processor 26327 1 acpi_cpufreq
button 3598 0
ext3 94204 9
jbd 32169 1 ext3
mbcache 3762 1 ext3
sg 15968 0
sr_mod 10770 0
sd_mod 25969 12
cdrom 26487 1 sr_mod
crc_t10dif 1012 1 sd_mod
usbhid 28008 2
hid 50873 1 usbhid
ata_generic 2067 0
pata_jmicron 1452 11
uhci_hcd 16057 0
ata_piix 17736 0
ehci_hcd 27851 0
r8169 24860 0
ahci 27270 0
e100 22317 0
floppy 40923 0
libata 115753 4 ata_generic,pata_jmicron,ata_piix,ahci
thermal 9206 0
thermal_sys 9378 2 processor,thermal
scsi_mod 101421 4 sg,sr_mod,sd_mod,libata
mii 2714 2 r8169,e100
usbcore 98453 6 usbhid,uhci_hcd,ehci_hcd
nls_base 4541 1 usbcore
# dmesg
...
[13212.745955] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.7
loaded
[13212.758940] cx88/2: cx2388x dvb driver version 0.0.7 loaded
[13212.758943] cx88/2: registering cx8802 driver, type: dvb access:
shared
...
I assume that dvb isn't it since I didn't run the command yet. :)
> So just try
> modprobe -a cx2388
> and then immediately do a dmesg to see if that indicates a
> successfully loading of the module with the appropriate parameter.
# modprobe -a cx2388
WARNING: Module cx2388 not found.
Failed. :(
--
Merry Christmas/Happy Holidays/Season's Greetings! :)
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.
J G Miller
> I assume that dvb isn't it since I didn't run the command yet. :)
Why do you want to load a DVB related module?
> # modprobe -a cx2388
> WARNING: Module cx2388 not found.
Sorry I slipped up there, confusing the chip with the module name.
cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
The name of the module is cx8800.ko
So obviously you need to change the name of the module in the
conf file in /etc/modprobe.d to
module cx8800 card=12
The name of the conf file is not critical -- it can have any
name .conf, but you may want to change it to cx8800.conf to
be consistent, or you could consider a more generic name
eg v4l2.conf in which to keep all your video for linux module
parameters, should you have more than one card or more than
one module to configure).
Now since from your dmesg you already have cx8800 loaded, you
will need to unload it with
modprobe -r cx8800
and the other related modules as well just to be on the safe
side, or if you are feeling lazy, just reboot.
Ant
>> I assume that dvb isn't it since I didn't run the command yet. :)
>
> Why do you want to load a DVB related module?
I think it is autoloaded?
>> # modprobe -a cx2388
>> WARNING: Module cx2388 not found.
>
> Sorry I slipped up there, confusing the chip with the module name.
>
> cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
>
> The name of the module is cx8800.ko
Yeah, I can see why you got confused. I would to! :(
> So obviously you need to change the name of the module in the
> conf file in /etc/modprobe.d to
>
> module cx8800 card=12
>
> The name of the conf file is not critical -- it can have any
> name .conf, but you may want to change it to cx8800.conf to
> be consistent, or you could consider a more generic name
> eg v4l2.conf in which to keep all your video for linux module
> parameters, should you have more than one card or more than
> one module to configure).
OK, I renamed the .conf file in my /etc/modprobe.d: mv cx2388.conf
cx8800.conf.
> Now since from your dmesg you already have cx8800 loaded, you
> will need to unload it with
>
> modprobe -r cx8800
>
> and the other related modules as well just to be on the safe
> side, or if you are feeling lazy, just reboot.
# mv cx2388.conf cx8800.conf
# nano cx8800.conf
# modprobe -r cx8800
# modprobe -a cx8800
# dmesg
...
[28115.724525] cx8800 0000:01:00.0: PCI INT A disabled
[28132.899438] cx8800: Unknown parameter `card'
Then, I noticed you had "module" instead of "option" in
/etc/modprobe.d/cx8800.conf so I fixed that to show:
# cat cx8800.conf
# ASUS TV Tuner Card 880 NTSC (cx23880)
module cx8800 card=12
I retried:
# modprobe -a cx8800
WARNING: /etc/modprobe.d/cx8800.conf line 3: ignoring bad line starting
with 'module'
dmesg showed:
...
[28246.942845] cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
[28246.942882] cx8800 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[28246.943351] cx88[0]: Your board isn't known (yet) to the driver. You can
[28246.943353] cx88[0]: try to pick one of the existing card configs via
[28246.943354] cx88[0]: card=<n> insmod option. Updating to the latest
[28246.943355] cx88[0]: version might help as well.
[28246.943358] cx88[0]: Here is a list of valid choices for the card=<n>
insmod option:
[28246.943360] cx88[0]: card=0 -> UNKNOWN/GENERIC
[28246.943362] cx88[0]: card=1 -> Hauppauge WinTV 34xxx models
[28246.943364] cx88[0]: card=2 -> GDI Black Gold
[28246.943366] cx88[0]: card=3 -> PixelView
[28246.943368] cx88[0]: card=4 -> ATI TV Wonder Pro
[28246.943370] cx88[0]: card=5 -> Leadtek Winfast 2000XP Expert
[28246.943372] cx88[0]: card=6 -> AverTV Studio 303 (M126)
[28246.943374] cx88[0]: card=7 -> MSI TV-@nywhere Master
[28246.943376] cx88[0]: card=8 -> Leadtek Winfast DV2000
[28246.943378] cx88[0]: card=9 -> Leadtek PVR 2000
[28246.943380] cx88[0]: card=10 -> IODATA GV-VCP3/PCI
[28246.943382] cx88[0]: card=11 -> Prolink PlayTV PVR
[28246.943384] cx88[0]: card=12 -> ASUS PVR-416
[28246.943386] cx88[0]: card=13 -> MSI TV-@nywhere
[28246.943388] cx88[0]: card=14 -> KWorld/VStream XPert DVB-T
[28246.943390] cx88[0]: card=15 -> DViCO FusionHDTV DVB-T1
[28246.943392] cx88[0]: card=16 -> KWorld LTV883RF
[28246.943394] cx88[0]: card=17 -> DViCO FusionHDTV 3 Gold-Q
[28246.943396] cx88[0]: card=18 -> Hauppauge Nova-T DVB-T
[28246.943398] cx88[0]: card=19 -> Conexant DVB-T reference design
[28246.943400] cx88[0]: card=20 -> Provideo PV259
[28246.943403] cx88[0]: card=21 -> DViCO FusionHDTV DVB-T Plus
[28246.943405] cx88[0]: card=22 -> pcHDTV HD3000 HDTV
[28246.943407] cx88[0]: card=23 -> digitalnow DNTV Live! DVB-T
[28246.943409] cx88[0]: card=24 -> Hauppauge WinTV 28xxx (Roslyn) models
[28246.943411] cx88[0]: card=25 -> Digital-Logic MICROSPACE
Entertainment Center (MEC)
[28246.943414] cx88[0]: card=26 -> IODATA GV/BCTV7E
[28246.943416] cx88[0]: card=27 -> PixelView PlayTV Ultra Pro (Stereo)
[28246.943418] cx88[0]: card=28 -> DViCO FusionHDTV 3 Gold-T
[28246.943420] cx88[0]: card=29 -> ADS Tech Instant TV DVB-T PCI
[28246.943422] cx88[0]: card=30 -> TerraTec Cinergy 1400 DVB-T
[28246.943424] cx88[0]: card=31 -> DViCO FusionHDTV 5 Gold
[28246.943427] cx88[0]: card=32 -> AverMedia UltraTV Media Center PCI 550
[28246.943429] cx88[0]: card=33 -> Kworld V-Stream Xpert DVD
[28246.943431] cx88[0]: card=34 -> ATI HDTV Wonder
[28246.943433] cx88[0]: card=35 -> WinFast DTV1000-T
[28246.943435] cx88[0]: card=36 -> AVerTV 303 (M126)
[28246.943437] cx88[0]: card=37 -> Hauppauge Nova-S-Plus DVB-S
[28246.943439] cx88[0]: card=38 -> Hauppauge Nova-SE2 DVB-S
[28246.943441] cx88[0]: card=39 -> KWorld DVB-S 100
[28246.943444] cx88[0]: card=40 -> Hauppauge WinTV-HVR1100 DVB-T/Hybrid
[28246.943446] cx88[0]: card=41 -> Hauppauge WinTV-HVR1100
DVB-T/Hybrid (Low Profile)
[28246.943448] cx88[0]: card=42 -> digitalnow DNTV Live! DVB-T Pro
[28246.943450] cx88[0]: card=43 -> KWorld/VStream XPert DVB-T with
cx22702
[28246.943453] cx88[0]: card=44 -> DViCO FusionHDTV DVB-T Dual Digital
[28246.943455] cx88[0]: card=45 -> KWorld HardwareMpegTV XPert
[28246.943457] cx88[0]: card=46 -> DViCO FusionHDTV DVB-T Hybrid
[28246.943459] cx88[0]: card=47 -> pcHDTV HD5500 HDTV
[28246.943461] cx88[0]: card=48 -> Kworld MCE 200 Deluxe
[28246.943463] cx88[0]: card=49 -> PixelView PlayTV P7000
[28246.943465] cx88[0]: card=50 -> NPG Tech Real TV FM Top 10
[28246.943468] cx88[0]: card=51 -> WinFast DTV2000 H
[28246.943470] cx88[0]: card=52 -> Geniatech DVB-S
[28246.943472] cx88[0]: card=53 -> Hauppauge WinTV-HVR3000 TriMode
Analog/DVB-S/DVB-T
[28246.943474] cx88[0]: card=54 -> Norwood Micro TV Tuner
[28246.943476] cx88[0]: card=55 -> Shenzhen Tungsten Ages Tech
TE-DTV-250 / Swann OEM
[28246.943478] cx88[0]: card=56 -> Hauppauge WinTV-HVR1300
DVB-T/Hybrid MPEG Encoder
[28246.943481] cx88[0]: card=57 -> ADS Tech Instant Video PCI
[28246.943483] cx88[0]: card=58 -> Pinnacle PCTV HD 800i
[28246.943485] cx88[0]: card=59 -> DViCO FusionHDTV 5 PCI nano
[28246.943487] cx88[0]: card=60 -> Pinnacle Hybrid PCTV
[28246.943489] cx88[0]: card=61 -> Leadtek TV2000 XP Global
[28246.943491] cx88[0]: card=62 -> PowerColor RA330
[28246.943493] cx88[0]: card=63 -> Geniatech X8000-MT DVBT
[28246.943495] cx88[0]: card=64 -> DViCO FusionHDTV DVB-T PRO
[28246.943498] cx88[0]: card=65 -> DViCO FusionHDTV 7 Gold
[28246.943500] cx88[0]: card=66 -> Prolink Pixelview MPEG 8000GT
[28246.943502] cx88[0]: card=67 -> Kworld PlusTV HD PCI 120 (ATSC 120)
[28246.943504] cx88[0]: card=68 -> Hauppauge WinTV-HVR4000
DVB-S/S2/T/Hybrid
[28246.943506] cx88[0]: card=69 -> Hauppauge WinTV-HVR4000(Lite) DVB-S/S2
[28246.943509] cx88[0]: card=70 -> TeVii S460 DVB-S/S2
[28246.943511] cx88[0]: card=71 -> Omicom SS4 DVB-S/S2 PCI
[28246.943513] cx88[0]: card=72 -> TBS 8920 DVB-S/S2
[28246.943515] cx88[0]: card=73 -> TeVii S420 DVB-S
[28246.943517] cx88[0]: card=74 -> Prolink Pixelview Global Extreme
[28246.943519] cx88[0]: card=75 -> PROF 7300 DVB-S/S2
[28246.943521] cx88[0]: card=76 -> SATTRADE ST4200 DVB-S/S2
[28246.943523] cx88[0]: card=77 -> TBS 8910 DVB-S
[28246.943525] cx88[0]: card=78 -> Prof 6200 DVB-S
[28246.943527] cx88[0]: card=79 -> Terratec Cinergy HT PCI MKII
[28246.943529] cx88[0]: card=80 -> Hauppauge WinTV-IR Only
[28246.943532] cx88[0]: card=81 -> Leadtek WinFast DTV1800 Hybrid
[28246.943534] cx88[0]: card=82 -> WinFast DTV2000 H rev. J
[28246.943537] cx88[0]: subsystem: 1043:4820, board: UNKNOWN/GENERIC
[card=0,autodetected], frontend(s): 0
[28246.943539] cx88[0]: TV tuner type -1, Radio tuner type -1
[28247.072914] All bytes are equal. It is not a TEA5767
[28247.072985] tuner 1-0060: chip found @ 0xc0 (cx88[0])
[28247.125229] cx88[0]/0: found at 0000:01:00.0, rev: 3, irq: 16,
latency: 64, mmio: 0xf8000000
[28247.125239] IRQ 16/cx88[0]: IRQF_DISABLED is not guaranteed on shared
IRQs
[28247.125300] cx88[0]/0: registered device video0 [v4l2]
[28247.125324] cx88[0]/0: registered device vbi0
[28247.125337] tuner 1-0060: tuner type not set
Um, does that mean I can test it now?
--
"It's kind of an insane case ... 6,000 ants dressed up as rice and
robbed a Chinese restaurant." --Steven Wright
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
Ant
I looked at this place. Its Linux forum seems to get little activities
and its home page (http://www.tv-cards.com/) seems to be broken. :(
--
"Whenever I see an old lady slip and fall on a wet sidewalk, my first
instinct is to laugh. But then I think, what if I was an ant, and she
fell on me. Then it wouldn't seem quite so funny." --Saturday Night Live
FAQ: Deep Thoughts
J G Miller
> Then, I noticed you had "module" instead of "option" in
> /etc/modprobe.d/cx8800.conf so I fixed that to show: # cat cx8800.conf
> # ASUS TV Tuner Card 880 NTSC (cx23880)
>
> module cx8800 card=12
Yes sorry again -- that of course should be
options cx8800 card=12
> I retried:
> # modprobe -a cx8800
> WARNING: /etc/modprobe.d/cx8800.conf line 3: ignoring bad line starting
> with 'module'
Exactly -- you need to change module to options, as shewn above.
Ensure that all of the v4l2 modules are unloaded, and try again with
modprobe -a cx8000
or just reboot.
And then if that is working, you will need to adjust your alsa-base.conf file
to ensure that the the cx8000 device is always loaded as the second, or third
or whatever sound device
Ant
>> Then, I noticed you had "module" instead of "option" in
>> /etc/modprobe.d/cx8800.conf so I fixed that to show: # cat cx8800.conf
>> # ASUS TV Tuner Card 880 NTSC (cx23880)
>>
>> module cx8800 card=12
>
> Yes sorry again -- that of course should be
>
> options cx8800 card=12
NP. I make lots of silly mistakes/errors too. Ah, with a "s" this time. :)
>> I retried:
>> # modprobe -a cx8800
>> WARNING: /etc/modprobe.d/cx8800.conf line 3: ignoring bad line starting
>> with 'module'
>
> Exactly -- you need to change module to options, as shewn above.
>
> Ensure that all of the v4l2 modules are unloaded, and try again with
Uh, how do I know which ones are v412 modules? I did a lsmod |grep v412
and saw nothing matching.
> modprobe -a cx8000
I ran without any errors or texts. Nothing added in dmesg too! Weird. So
I installed and ran xawtv for kicks to see what happens.
> or just reboot.
>
> And then if that is working, you will need to adjust your alsa-base.conf file
> to ensure that the the cx8000 device is always loaded as the second, or third
> or whatever sound device
For now, I only want to worry about video/picture. I played with xawtv
for a bit, but only statics. I tried other three composite options and
they gave me blue screens (not Windows' :P), so I assume the first
static ones is the correct one. Here is a screen capture/shot of it in
action:
Also, I ran xawtv in terminal to see anything errors which I did:
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
Warning: Cannot convert string
"-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*" to type FontStruct
v4l2: read: Input/output error
Then I exited the xawtv. I also noticed new lines in dmesg:
...
[36637.108099] tuner 1-0060: tuner type not set
[36729.880005] cx88[0]: video y / packed - dma channel status dump
[36729.880010] cx88[0]: cmds: initial risc: 0x0b6ca000
[36729.880014] cx88[0]: cmds: cdt base : 0x00180440
[36729.880017] cx88[0]: cmds: cdt size : 0x0000000c
[36729.880019] cx88[0]: cmds: iq base : 0x00180400
[36729.880022] cx88[0]: cmds: iq size : 0x00000010
[36729.880025] cx88[0]: cmds: risc pc : 0x0b6caa48
[36729.880028] cx88[0]: cmds: iq wr ptr : 0x00000106
[36729.880031] cx88[0]: cmds: iq rd ptr : 0x0000010a
[36729.880034] cx88[0]: cmds: cdt current : 0x00000488
[36729.880037] cx88[0]: cmds: pci target : 0x0b558660
[36729.880040] cx88[0]: cmds: line / byte : 0x00f00000
[36729.880043] cx88[0]: risc0: 0x80008200 [ sync resync count=512 ]
[36729.880048] cx88[0]: risc1: 0x1c0005a0 [ write sol eol count=1440 ]
[36729.880053] cx88[0]: risc2: 0x0b47f5a0 [ arg #1 ]
[36729.880056] cx88[0]: risc3: 0x1c0005a0 [ write sol eol count=1440 ]
[36729.880061] cx88[0]: iq 0: 0x140001c0 [ write eol count=448 ]
[36729.880066] cx88[0]: iq 1: 0x0b47d000 [ arg #1 ]
[36729.880069] cx88[0]: iq 2: 0x1c0005a0 [ write sol eol count=1440 ]
[36729.880074] cx88[0]: iq 3: 0x0b47d760 [ arg #1 ]
[36729.880077] cx88[0]: iq 4: 0x1c0005a0 [ write sol eol count=1440 ]
[36729.880082] cx88[0]: iq 5: 0x0b47c2a0 [ arg #1 ]
[36729.880085] cx88[0]: iq 6: 0x0b557580 [ INVALID sol irq2 irq1 22 20
18 cnt0 14 13 12 count=1408 ]
[36729.880093] cx88[0]: iq 7: 0x1c0005a0 [ write sol eol count=1440 ]
[36729.880098] cx88[0]: iq 8: 0x0b5580c0 [ arg #1 ]
[36729.880101] cx88[0]: iq 9: 0x80008200 [ sync resync count=512 ]
[36729.880105] cx88[0]: iq a: 0x1c0005a0 [ write sol eol count=1440 ]
[36729.880110] cx88[0]: iq b: 0x0b47f5a0 [ arg #1 ]
[36729.880113] cx88[0]: iq c: 0x1c0005a0 [ write sol eol count=1440 ]
[36729.880118] cx88[0]: iq d: 0x0b47e0e0 [ arg #1 ]
[36729.880121] cx88[0]: iq e: 0x180003e0 [ write sol count=992 ]
[36729.880126] cx88[0]: iq f: 0x0b47ec20 [ arg #1 ]
[36729.880128] cx88[0]: fifo: 0x00180c00 -> 0x183400
[36729.880130] cx88[0]: ctrl: 0x00180400 -> 0x180460
[36729.880133] cx88[0]: ptr1_reg: 0x00180c00
[36729.880135] cx88[0]: ptr2_reg: 0x00180448
[36729.880138] cx88[0]: cnt1_reg: 0x00000000
[36729.880140] cx88[0]: cnt2_reg: 0x00000000
[36729.880147] cx88[0]/0: [f2160d80/0] timeout - dma=0x0b6ca000
[36729.880149] cx88[0]/0: [f21609c0/1] timeout - dma=0x0c860000
[36748.413938] tuner 1-0060: tuner type not set
[36749.912006] cx88[0]: video y / packed - dma channel status dump
[36749.912011] cx88[0]: cmds: initial risc: 0x0b7c9000
[36749.912014] cx88[0]: cmds: cdt base : 0x00180440
[36749.912017] cx88[0]: cmds: cdt size : 0x0000000c
[36749.912020] cx88[0]: cmds: iq base : 0x00180400
[36749.912023] cx88[0]: cmds: iq size : 0x00000010
[36749.912026] cx88[0]: cmds: risc pc : 0x30aab768
[36749.912029] cx88[0]: cmds: iq wr ptr : 0x00000107
[36749.912031] cx88[0]: cmds: iq rd ptr : 0x0000010b
[36749.912034] cx88[0]: cmds: cdt current : 0x00000468
[36749.912037] cx88[0]: cmds: pci target : 0x0b6cd200
[36749.912040] cx88[0]: cmds: line / byte : 0x023b0000
[36749.912043] cx88[0]: risc0: 0x1c000300 [ write sol eol count=768 ]
[36749.912048] cx88[0]: risc1: 0x0b6cd500 [ arg #1 ]
[36749.912052] cx88[0]: risc2: 0x1c000300 [ write sol eol count=768 ]
[36749.912057] cx88[0]: risc3: 0x0b6cdb00 [ arg #1 ]
[36749.912060] cx88[0]: iq 0: 0x0b6cc700 [ INVALID sol irq2 irq1 22 21
19 18 resync 14 count=1792 ]
[36749.912068] cx88[0]: iq 1: 0x1c000300 [ write sol eol count=768 ]
[36749.912074] cx88[0]: iq 2: 0x0b6ccd00 [ arg #1 ]
[36749.912076] cx88[0]: iq 3: 0x1c000300 [ write sol eol count=768 ]
[36749.912082] cx88[0]: iq 4: 0x2dfbf300 [ arg #1 ]
[36749.912085] cx88[0]: iq 5: 0x1c000300 [ write sol eol count=768 ]
[36749.912090] cx88[0]: iq 6: 0x2dfbf900 [ arg #1 ]
[36749.912093] cx88[0]: iq 7: 0x14000200 [ write eol count=512 ]
[36749.912097] cx88[0]: iq 8: 0x0b6cd000 [ arg #1 ]
[36749.912100] cx88[0]: iq 9: 0x1c000300 [ write sol eol count=768 ]
[36749.912105] cx88[0]: iq a: 0x0b6cd500 [ arg #1 ]
[36749.912108] cx88[0]: iq b: 0x1c000300 [ write sol eol count=768 ]
[36749.912116] cx88[0]: iq c: 0x0b6cdb00 [ arg #1 ]
[36749.912119] cx88[0]: iq d: 0x1c000300 [ write sol eol count=768 ]
[36749.912124] cx88[0]: iq e: 0x0b6cc100 [ arg #1 ]
[36749.912127] cx88[0]: iq f: 0x1c000300 [ write sol eol count=768 ]
[36749.912132] cx88[0]: iq 10: 0x00180c00 [ arg #1 ]
[36749.912134] cx88[0]: fifo: 0x00180c00 -> 0x183400
[36749.912136] cx88[0]: ctrl: 0x00180400 -> 0x180460
[36749.912139] cx88[0]: ptr1_reg: 0x00181620
[36749.912141] cx88[0]: ptr2_reg: 0x00180478
[36749.912144] cx88[0]: cnt1_reg: 0x0000002d
[36749.912146] cx88[0]: cnt2_reg: 0x00000000
[36749.912153] cx88[0]/0: [f21b5240/1] timeout - dma=0x30aab000
[36749.912155] cx88[0]/0: [f21b5900/0] timeout - dma=0x0b7c9000
[36754.363551] tuner 1-0060: tuner type not set
[36791.764718] tuner 1-0060: tuner type not set
[36797.956904] tuner 1-0060: tuner type not set
[36804.484203] tuner 1-0060: tuner type not set
[36812.445581] tuner 1-0060: tuner type not set
[36847.628006] cx88[0]: video y / packed - dma channel status dump
[36847.628010] cx88[0]: cmds: initial risc: 0x14a12000
[36847.628013] cx88[0]: cmds: cdt base : 0x00180440
[36847.628016] cx88[0]: cmds: cdt size : 0x0000000a
[36847.628019] cx88[0]: cmds: iq base : 0x00180400
[36847.628022] cx88[0]: cmds: iq size : 0x00000010
[36847.628024] cx88[0]: cmds: risc pc : 0x14a12034
[36847.628027] cx88[0]: cmds: iq wr ptr : 0x0000010d
[36847.628030] cx88[0]: cmds: iq rd ptr : 0x00000101
[36847.628033] cx88[0]: cmds: cdt current : 0x00000448
[36847.628036] cx88[0]: cmds: pci target : 0x00000000
[36847.628039] cx88[0]: cmds: line / byte : 0x00000000
[36847.628041] cx88[0]: risc0: 0x80008000 [ sync resync count=0 ]
[36847.628046] cx88[0]: risc1: 0x1c000780 [ write sol eol count=1920 ]
[36847.628051] cx88[0]: risc2: 0x0b568000 [ arg #1 ]
[36847.628055] cx88[0]: risc3: 0x18000100 [ write sol count=256 ]
[36847.628059] cx88[0]: iq 0: 0x80008000 [ sync resync count=0 ]
[36847.628064] cx88[0]: iq 1: 0x1c000780 [ write sol eol count=1920 ]
[36847.628069] cx88[0]: iq 2: 0x0b568000 [ arg #1 ]
[36847.628072] cx88[0]: iq 3: 0x18000100 [ write sol count=256 ]
[36847.628077] cx88[0]: iq 4: 0x0b568f00 [ arg #1 ]
[36847.628079] cx88[0]: iq 5: 0x14000680 [ write eol count=1664 ]
[36847.628084] cx88[0]: iq 6: 0x0b567000 [ arg #1 ]
[36847.628087] cx88[0]: iq 7: 0x18000200 [ write sol count=512 ]
[36847.628092] cx88[0]: iq 8: 0x0b567e00 [ arg #1 ]
[36847.628094] cx88[0]: iq 9: 0x14000580 [ write eol count=1408 ]
[36847.628099] cx88[0]: iq a: 0x0c951000 [ arg #1 ]
[36847.628102] cx88[0]: iq b: 0x18000300 [ write sol count=768 ]
[36847.628107] cx88[0]: iq c: 0x0c951d00 [ arg #1 ]
[36847.628110] cx88[0]: iq d: 0x0c951e00 [ INVALID sol eol 23 20 18
cnt0 12 count=3584 ]
[36847.628117] cx88[0]: iq e: 0x14000400 [ write eol count=1024 ]
[36847.628122] cx88[0]: iq f: 0x0b567000 [ arg #1 ]
[36847.628124] cx88[0]: fifo: 0x00180c00 -> 0x183400
[36847.628125] cx88[0]: ctrl: 0x00180400 -> 0x180460
[36847.628128] cx88[0]: ptr1_reg: 0x00181f28
[36847.628131] cx88[0]: ptr2_reg: 0x00180468
[36847.628133] cx88[0]: cnt1_reg: 0x0000009d
[36847.628136] cx88[0]: cnt2_reg: 0x00000000
[36847.628142] cx88[0]/0: [f2f47540/0] timeout - dma=0x14a12000
Those did not look good. :(
I decided to reboot to see if it helps at all. Here is what I saw in
dmesg before doing anything else in X and KDE v3.5.10:
[ 0.000000] Detected 2339.278 MHz processor.
[ 0.004004] Calibrating delay loop (skipped), value calculated using
timer frequency.. 4678.55 BogoMIPS (lpj=9357112)
[ 0.004016] Security Framework initialized
[ 0.004020] SELinux: Disabled at boot.
[ 0.004025] Mount-cache hash table entries: 512
[ 0.004117] Initializing cgroup subsys ns
[ 0.004119] Initializing cgroup subsys cpuacct
[ 0.004123] Initializing cgroup subsys devices
[ 0.004124] Initializing cgroup subsys freezer
[ 0.004126] Initializing cgroup subsys net_cls
[ 0.004144] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.004145] CPU: L2 cache: 2048K
[ 0.004148] CPU: Physical Processor ID: 0
[ 0.004149] CPU: Processor Core ID: 0
[ 0.004152] mce: CPU supports 6 MCE banks
[ 0.004158] CPU0: Thermal monitoring enabled (TM2)
[ 0.004161] using mwait in idle threads.
[ 0.004166] Performance Events: Core2 events, Intel PMU driver.
[ 0.004171] ... version: 2
[ 0.004172] ... bit width: 40
[ 0.004173] ... generic registers: 2
[ 0.004175] ... value mask: 000000ffffffffff
[ 0.004176] ... max period: 000000007fffffff
[ 0.004177] ... fixed-purpose events: 3
[ 0.004179] ... event mask: 0000000700000003
[ 0.004182] Checking 'hlt' instruction... OK.
[ 0.021041] ACPI: Core revision 20090903
[ 0.026946] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.027249] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.066941] CPU0: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.068001] Booting processor 1 APIC 0x1 ip 0x6000
[ 0.008000] Initializing CPU#1
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.008000] CPU: L2 cache: 2048K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 1
[ 0.008000] CPU1: Thermal monitoring enabled (TM2)
[ 0.152031] CPU1: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.152037] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
[ 0.156103] Booting processor 2 APIC 0x2 ip 0x6000
[ 0.008000] Initializing CPU#2
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.008000] CPU: L2 cache: 2048K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 2
[ 0.008000] CPU2: Thermal monitoring enabled (TM2)
[ 0.244084] CPU2: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.244090] checking TSC synchronization [CPU#0 -> CPU#2]: passed.
[ 0.248081] Booting processor 3 APIC 0x3 ip 0x6000
[ 0.008000] Initializing CPU#3
[ 0.008000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 0.008000] CPU: L2 cache: 2048K
[ 0.008000] CPU: Physical Processor ID: 0
[ 0.008000] CPU: Processor Core ID: 3
[ 0.008000] CPU3: Thermal monitoring enabled (TM2)
[ 0.336030] CPU3: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping 07
[ 0.336035] checking TSC synchronization [CPU#0 -> CPU#3]: passed.
[ 0.340036] Brought up 4 CPUs
[ 0.340038] Total of 4 processors activated (18713.27 BogoMIPS).
[ 0.341228] CPU0 attaching sched-domain:
[ 0.341230] domain 0: span 0-1 level MC
[ 0.341232] groups: 0 1
[ 0.341236] domain 1: span 0-3 level CPU
[ 0.341238] groups: 0-1 (cpu_power = 2048) 2-3 (cpu_power = 2048)
[ 0.341243] CPU1 attaching sched-domain:
[ 0.341245] domain 0: span 0-1 level MC
[ 0.341247] groups: 1 0
[ 0.341250] domain 1: span 0-3 level CPU
[ 0.341251] groups: 0-1 (cpu_power = 2048) 2-3 (cpu_power = 2048)
[ 0.341256] CPU2 attaching sched-domain:
[ 0.341258] domain 0: span 2-3 level MC
[ 0.341259] groups: 2 3
[ 0.341262] domain 1: span 0-3 level CPU
[ 0.341264] groups: 2-3 (cpu_power = 2048) 0-1 (cpu_power = 2048)
[ 0.341269] CPU3 attaching sched-domain:
[ 0.341270] domain 0: span 2-3 level MC
[ 0.341272] groups: 3 2
[ 0.341275] domain 1: span 0-3 level CPU
[ 0.341276] groups: 2-3 (cpu_power = 2048) 0-1 (cpu_power = 2048)
[ 0.341381] devtmpfs: initialized
[ 0.341381] regulator: core version 0.5
[ 0.341381] NET: Registered protocol family 16
[ 0.341381] ACPI: bus type pci registered
[ 0.341381] PCI: MCFG configuration 0: base e0000000 segment 0 buses
0 - 255
[ 0.341381] PCI: Not using MMCONFIG.
[ 0.341381] PCI: Using configuration type 1 for base access
[ 0.341381] bio: create slab <bio-0> at 0
[ 0.341381] ACPI: EC: Look up EC in DSDT
[ 0.345931] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.350196] ACPI: Interpreter enabled
[ 0.350205] ACPI: (supports S0 S3 S4 S5)
[ 0.350225] ACPI: Using IOAPIC for interrupt routing
[ 0.350266] PCI: MCFG configuration 0: base e0000000 segment 0 buses
0 - 255
[ 0.352874] PCI: MCFG area at e0000000 reserved in ACPI motherboard
resources
[ 0.352876] PCI: Using MMCONFIG for extended config space
[ 0.360138] ACPI Warning: Incorrect checksum in table [OEMB] - BB,
should be B2 (20090903/tbutils-314)
[ 0.360242] ACPI: No dock devices found.
[ 0.360368] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.360445] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.360447] pci 0000:00:01.0: PME# disabled
[ 0.360505] pci 0000:00:1a.0: reg 20 io port: [0x8800-0x881f]
[ 0.360563] pci 0000:00:1a.1: reg 20 io port: [0x8480-0x849f]
[ 0.360620] pci 0000:00:1a.2: reg 20 io port: [0x8400-0x841f]
[ 0.360681] pci 0000:00:1a.7: reg 10 32bit mmio: [0xf7fff400-0xf7fff7ff]
[ 0.360727] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[ 0.360731] pci 0000:00:1a.7: PME# disabled
[ 0.360764] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf7ff8000-0xf7ffbfff]
[ 0.360798] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.360802] pci 0000:00:1b.0: PME# disabled
[ 0.360852] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.360856] pci 0000:00:1c.0: PME# disabled
[ 0.360908] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.360911] pci 0000:00:1c.1: PME# disabled
[ 0.360965] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
[ 0.360968] pci 0000:00:1c.5: PME# disabled
[ 0.361013] pci 0000:00:1d.0: reg 20 io port: [0x9000-0x901f]
[ 0.361071] pci 0000:00:1d.1: reg 20 io port: [0x8c00-0x8c1f]
[ 0.361128] pci 0000:00:1d.2: reg 20 io port: [0x8880-0x889f]
[ 0.361189] pci 0000:00:1d.7: reg 10 32bit mmio: [0xf7fff800-0xf7fffbff]
[ 0.361235] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.361239] pci 0000:00:1d.7: PME# disabled
[ 0.361381] pci 0000:00:1f.2: reg 10 io port: [0xac00-0xac07]
[ 0.361386] pci 0000:00:1f.2: reg 14 io port: [0xa880-0xa883]
[ 0.361391] pci 0000:00:1f.2: reg 18 io port: [0xa800-0xa807]
[ 0.361396] pci 0000:00:1f.2: reg 1c io port: [0xa480-0xa483]
[ 0.361401] pci 0000:00:1f.2: reg 20 io port: [0xa400-0xa40f]
[ 0.361406] pci 0000:00:1f.2: reg 24 io port: [0xa080-0xa08f]
[ 0.361443] pci 0000:00:1f.3: reg 10 64bit mmio: [0xf7fffc00-0xf7fffcff]
[ 0.361455] pci 0000:00:1f.3: reg 20 io port: [0x400-0x41f]
[ 0.361490] pci 0000:00:1f.5: reg 10 io port: [0x9c00-0x9c07]
[ 0.361495] pci 0000:00:1f.5: reg 14 io port: [0x9880-0x9883]
[ 0.361500] pci 0000:00:1f.5: reg 18 io port: [0x9800-0x9807]
[ 0.361505] pci 0000:00:1f.5: reg 1c io port: [0x9480-0x9483]
[ 0.361510] pci 0000:00:1f.5: reg 20 io port: [0x9400-0x940f]
[ 0.361515] pci 0000:00:1f.5: reg 24 io port: [0x9080-0x908f]
[ 0.361560] pci 0000:05:00.0: reg 10 32bit mmio: [0xfd000000-0xfdffffff]
[ 0.361567] pci 0000:05:00.0: reg 14 64bit mmio pref:
[0xd0000000-0xdfffffff]
[ 0.361574] pci 0000:05:00.0: reg 1c 64bit mmio: [0xfa000000-0xfbffffff]
[ 0.361579] pci 0000:05:00.0: reg 24 io port: [0xec00-0xec7f]
[ 0.361584] pci 0000:05:00.0: reg 30 32bit mmio pref: [0x000000-0x01ffff]
[ 0.361671] pci 0000:00:01.0: bridge io port: [0xe000-0xefff]
[ 0.361674] pci 0000:00:01.0: bridge 32bit mmio: [0xfa000000-0xfebfffff]
[ 0.361677] pci 0000:00:01.0: bridge 64bit mmio pref:
[0xd0000000-0xdfffffff]
[ 0.361758] pci 0000:02:00.0: reg 24 32bit mmio: [0xf9efe000-0xf9efffff]
[ 0.361793] pci 0000:02:00.0: PME# supported from D3hot
[ 0.361798] pci 0000:02:00.0: PME# disabled
[ 0.361846] pci 0000:02:00.1: reg 10 io port: [0xcc00-0xcc07]
[ 0.361855] pci 0000:02:00.1: reg 14 io port: [0xc880-0xc883]
[ 0.361863] pci 0000:02:00.1: reg 18 io port: [0xc800-0xc807]
[ 0.361871] pci 0000:02:00.1: reg 1c io port: [0xc480-0xc483]
[ 0.361879] pci 0000:02:00.1: reg 20 io port: [0xc400-0xc40f]
[ 0.361942] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device.
You can enable it with 'pcie_aspm=force'
[ 0.362003] pci 0000:00:1c.0: bridge io port: [0xc000-0xcfff]
[ 0.362006] pci 0000:00:1c.0: bridge 32bit mmio: [0xf9e00000-0xf9efffff]
[ 0.362085] pci 0000:04:00.0: reg 10 io port: [0xd800-0xd8ff]
[ 0.362103] pci 0000:04:00.0: reg 18 64bit mmio pref:
[0xcffff000-0xcfffffff]
[ 0.362116] pci 0000:04:00.0: reg 20 64bit mmio pref:
[0xcffe0000-0xcffeffff]
[ 0.362123] pci 0000:04:00.0: reg 30 32bit mmio pref:
[0xf9ff0000-0xf9ffffff]
[ 0.362158] pci 0000:04:00.0: supports D1 D2
[ 0.362160] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.362164] pci 0000:04:00.0: PME# disabled
[ 0.368096] pci 0000:00:1c.5: bridge io port: [0xd000-0xdfff]
[ 0.368100] pci 0000:00:1c.5: bridge 32bit mmio: [0xf9f00000-0xf9ffffff]
[ 0.368105] pci 0000:00:1c.5: bridge 64bit mmio pref:
[0xcff00000-0xcfffffff]
[ 0.368138] pci 0000:01:00.0: reg 10 32bit mmio: [0xf8000000-0xf8ffffff]
[ 0.368222] pci 0000:01:02.0: reg 10 32bit mmio: [0xf9dff000-0xf9dfffff]
[ 0.368228] pci 0000:01:02.0: reg 14 io port: [0xbc00-0xbc3f]
[ 0.368234] pci 0000:01:02.0: reg 18 32bit mmio: [0xf9c00000-0xf9cfffff]
[ 0.368251] pci 0000:01:02.0: reg 30 32bit mmio pref:
[0xf9b00000-0xf9bfffff]
[ 0.368267] pci 0000:01:02.0: supports D1 D2
[ 0.368268] pci 0000:01:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.368272] pci 0000:01:02.0: PME# disabled
[ 0.368314] pci 0000:00:1e.0: transparent bridge
[ 0.368318] pci 0000:00:1e.0: bridge io port: [0xb000-0xbfff]
[ 0.368321] pci 0000:00:1e.0: bridge 32bit mmio: [0xf8000000-0xf9dfffff]
[ 0.368341] pci_bus 0000:00: on NUMA node 0
[ 0.368345] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.368515] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[ 0.368663] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
[ 0.368727] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
[ 0.368787] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT]
[ 0.383239] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12
14 15)
[ 0.383335] ACPI: PCI Interrupt Link [LNKB] (IRQs *5)
[ 0.383424] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12 14
*15)
[ 0.383516] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 *11 12
14 15)
[ 0.383608] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14
15) *0, disabled.
[ 0.383701] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 *7 10 11 12
14 15)
[ 0.383793] ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 6 7 10 11 12
14 15)
[ 0.383885] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 10 11 12
*14 15)
[ 0.383973] vgaarb: device added:
PCI:0000:05:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.383977] vgaarb: loaded
[ 0.384048] PCI: Using ACPI for IRQ routing
[ 0.384213] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[ 0.384218] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[ 0.392018] Switching to clocksource tsc
[ 0.393134] pnp: PnP ACPI init
[ 0.393150] ACPI: bus type pnp registered
[ 0.396345] pnp: PnP ACPI: found 18 devices
[ 0.396347] ACPI: ACPI bus type pnp unregistered
[ 0.396350] PnPBIOS: Disabled by ACPI PNP
[ 0.396360] system 00:01: iomem range 0xfed14000-0xfed19fff has been
reserved
[ 0.396362] system 00:01: iomem range 0xfed90000-0xfed93fff has been
reserved
[ 0.396369] system 00:08: ioport range 0x4c0-0x4ff has been reserved
[ 0.396372] system 00:08: ioport range 0x4d0-0x4d1 has been reserved
[ 0.396374] system 00:08: ioport range 0x800-0x87f has been reserved
[ 0.396376] system 00:08: ioport range 0x480-0x4bf has been reserved
[ 0.396379] system 00:08: iomem range 0xfed1c000-0xfed1ffff has been
reserved
[ 0.396382] system 00:08: iomem range 0xfed20000-0xfed3ffff has been
reserved
[ 0.396384] system 00:08: iomem range 0xfed40000-0xfed8ffff has been
reserved
[ 0.396389] system 00:0b: iomem range 0xffc00000-0xffefffff has been
reserved
[ 0.396394] system 00:0c: iomem range 0xfec00000-0xfec00fff could not
be reserved
[ 0.396397] system 00:0c: iomem range 0xfee00000-0xfee00fff has been
reserved
[ 0.396402] system 00:0f: ioport range 0xa00-0xadf has been reserved
[ 0.396404] system 00:0f: ioport range 0xae0-0xaef has been reserved
[ 0.396408] system 00:10: iomem range 0xe0000000-0xefffffff has been
reserved
[ 0.396413] system 00:11: iomem range 0x0-0x9ffff could not be reserved
[ 0.396416] system 00:11: iomem range 0xc0000-0xcffff could not be
reserved
[ 0.396418] system 00:11: iomem range 0xe0000-0xfffff could not be
reserved
[ 0.396421] system 00:11: iomem range 0x100000-0x7fffffff could not
be reserved
[ 0.396423] system 00:11: iomem range 0xfed90000-0xffffffff could not
be reserved
[ 0.431198] pci 0000:01:02.0: BAR 6: address space collision on of
device [0xf9b00000-0xf9bfffff]
[ 0.431277] pci 0000:00:01.0: PCI bridge, secondary bus 0000:05
[ 0.431280] pci 0000:00:01.0: IO window: 0xe000-0xefff
[ 0.431283] pci 0000:00:01.0: MEM window: 0xfa000000-0xfebfffff
[ 0.431286] pci 0000:00:01.0: PREFETCH window:
0x000000d0000000-0x000000dfffffff
[ 0.431290] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
[ 0.431293] pci 0000:00:1c.0: IO window: 0xc000-0xcfff
[ 0.431297] pci 0000:00:1c.0: MEM window: 0xf9e00000-0xf9efffff
[ 0.431301] pci 0000:00:1c.0: PREFETCH window:
0x00000080000000-0x000000801fffff
[ 0.431306] pci 0000:00:1c.1: PCI bridge, secondary bus 0000:03
[ 0.431308] pci 0000:00:1c.1: IO window: 0x1000-0x1fff
[ 0.431312] pci 0000:00:1c.1: MEM window: 0x80200000-0x803fffff
[ 0.431316] pci 0000:00:1c.1: PREFETCH window:
0x00000080400000-0x000000805fffff
[ 0.431321] pci 0000:00:1c.5: PCI bridge, secondary bus 0000:04
[ 0.431324] pci 0000:00:1c.5: IO window: 0xd000-0xdfff
[ 0.431328] pci 0000:00:1c.5: MEM window: 0xf9f00000-0xf9ffffff
[ 0.431331] pci 0000:00:1c.5: PREFETCH window:
0x000000cff00000-0x000000cfffffff
[ 0.431337] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:01
[ 0.431340] pci 0000:00:1e.0: IO window: 0xb000-0xbfff
[ 0.431344] pci 0000:00:1e.0: MEM window: 0xf8000000-0xf9dfffff
[ 0.431347] pci 0000:00:1e.0: PREFETCH window: 0x80600000-0x806fffff
[ 0.431359] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.431362] pci 0000:00:01.0: setting latency timer to 64
[ 0.431370] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 0.431374] pci 0000:00:1c.0: setting latency timer to 64
[ 0.431380] pci 0000:00:1c.1: enabling device (0104 -> 0107)
[ 0.431383] pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[ 0.431387] pci 0000:00:1c.1: setting latency timer to 64
[ 0.431393] pci 0000:00:1c.5: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[ 0.431397] pci 0000:00:1c.5: setting latency timer to 64
[ 0.431402] pci 0000:00:1e.0: setting latency timer to 64
[ 0.431405] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
[ 0.431407] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
[ 0.431410] pci_bus 0000:05: resource 0 io: [0xe000-0xefff]
[ 0.431412] pci_bus 0000:05: resource 1 mem: [0xfa000000-0xfebfffff]
[ 0.431414] pci_bus 0000:05: resource 2 pref mem [0xd0000000-0xdfffffff]
[ 0.431416] pci_bus 0000:02: resource 0 io: [0xc000-0xcfff]
[ 0.431418] pci_bus 0000:02: resource 1 mem: [0xf9e00000-0xf9efffff]
[ 0.431420] pci_bus 0000:02: resource 2 pref mem [0x80000000-0x801fffff]
[ 0.431422] pci_bus 0000:03: resource 0 io: [0x1000-0x1fff]
[ 0.431424] pci_bus 0000:03: resource 1 mem: [0x80200000-0x803fffff]
[ 0.431426] pci_bus 0000:03: resource 2 pref mem [0x80400000-0x805fffff]
[ 0.431429] pci_bus 0000:04: resource 0 io: [0xd000-0xdfff]
[ 0.431431] pci_bus 0000:04: resource 1 mem: [0xf9f00000-0xf9ffffff]
[ 0.431433] pci_bus 0000:04: resource 2 pref mem [0xcff00000-0xcfffffff]
[ 0.431435] pci_bus 0000:01: resource 0 io: [0xb000-0xbfff]
[ 0.431437] pci_bus 0000:01: resource 1 mem: [0xf8000000-0xf9dfffff]
[ 0.431439] pci_bus 0000:01: resource 2 pref mem [0x80600000-0x806fffff]
[ 0.431441] pci_bus 0000:01: resource 3 io: [0x00-0xffff]
[ 0.431443] pci_bus 0000:01: resource 4 mem: [0x000000-0xffffffff]
[ 0.431469] NET: Registered protocol family 2
[ 0.431544] IP route cache hash table entries: 32768 (order: 5,
131072 bytes)
[ 0.431759] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[ 0.432057] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.432199] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.432201] TCP reno registered
[ 0.432260] NET: Registered protocol family 1
[ 0.432384] pci 0000:05:00.0: Boot video device
[ 0.432396] pci 0000:01:02.0: Firmware left e100 interrupts enabled;
disabling
[ 0.432440] Unpacking initramfs...
[ 0.622833] Freeing initrd memory: 7828k freed
[ 0.625786] audit: initializing netlink socket (disabled)
[ 0.625797] type=2000 audit(1293211535.623:1): initialized
[ 0.628789] highmem bounce pool size: 64 pages
[ 0.628793] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[ 0.630059] VFS: Disk quotas dquot_6.5.2
[ 0.630104] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.630161] msgmni has been set to 1723
[ 0.630489] alg: No test for stdrng (krng)
[ 0.630541] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 253)
[ 0.630544] io scheduler noop registered
[ 0.630546] io scheduler anticipatory registered
[ 0.630547] io scheduler deadline registered
[ 0.630578] io scheduler cfq registered (default)
[ 0.630674] pcieport 0000:00:01.0: irq 24 for MSI/MSI-X
[ 0.630679] pcieport 0000:00:01.0: setting latency timer to 64
[ 0.630757] pcieport 0000:00:1c.0: irq 25 for MSI/MSI-X
[ 0.630763] pcieport 0000:00:1c.0: setting latency timer to 64
[ 0.630855] pcieport 0000:00:1c.1: irq 26 for MSI/MSI-X
[ 0.630861] pcieport 0000:00:1c.1: setting latency timer to 64
[ 0.630957] pcieport 0000:00:1c.5: irq 27 for MSI/MSI-X
[ 0.630964] pcieport 0000:00:1c.5: setting latency timer to 64
[ 0.631100] isapnp: Scanning for PnP cards...
[ 0.983913] isapnp: No Plug & Play device found
[ 0.984985] Linux agpgart interface v0.103
[ 0.985097] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.985180] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.985437] 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.985644] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at
0x60,0x64 irq 1,12
[ 0.988287] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.988292] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.988335] mice: PS/2 mouse device common for all mice
[ 0.988377] rtc_cmos 00:03: RTC can wake from S4
[ 0.988402] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 0.988423] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 0.988435] cpuidle: using governor ladder
[ 0.988436] cpuidle: using governor menu
[ 0.988440] No iBFT detected.
[ 0.988696] TCP cubic registered
[ 0.988805] NET: Registered protocol family 10
[ 0.989144] lo: Disabled Privacy Extensions
[ 0.989380] Mobile IPv6
[ 0.989382] NET: Registered protocol family 17
[ 0.989393] Using IPI No-Shortcut mode
[ 0.989440] PM: Resume from disk failed.
[ 0.989451] registered taskstats version 1
[ 0.989847] rtc_cmos 00:03: setting system clock to 2010-12-24
17:25:36 UTC (1293211536)
[ 0.989873] Initalizing network drop monitor service
[ 0.989900] Freeing unused kernel memory: 376k freed
[ 0.990048] Write protecting the kernel text: 2504k
[ 0.990072] Write protecting the kernel read-only data: 920k
[ 0.998077] udev[76]: starting version 164
[ 1.008475] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input0
[ 1.051547] usbcore: registered new interface driver usbfs
[ 1.051569] usbcore: registered new interface driver hub
[ 1.051881] usbcore: registered new device driver usb
[ 1.061990] SCSI subsystem initialized
[ 1.075606] libata version 3.00 loaded.
[ 1.077133] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.077171] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low)
-> IRQ 18
[ 1.077190] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[ 1.077193] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[ 1.077216] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned
bus number 1
[ 1.077239] ehci_hcd 0000:00:1a.7: debug port 1
[ 1.078297] pata_jmicron 0000:02:00.1: enabling device (0000 -> 0001)
[ 1.078304] pata_jmicron 0000:02:00.1: PCI INT B -> GSI 17 (level,
low) -> IRQ 17
[ 1.078339] pata_jmicron 0000:02:00.1: setting latency timer to 64
[ 1.078399] scsi0 : pata_jmicron
[ 1.078527] scsi1 : pata_jmicron
[ 1.079050] ata1: PATA max UDMA/100 cmd 0xcc00 ctl 0xc880 bmdma
0xc400 irq 17
[ 1.079053] ata2: PATA max UDMA/100 cmd 0xc800 ctl 0xc480 bmdma
0xc408 irq 17
[ 1.080724] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.080743] r8169 0000:04:00.0: PCI INT A -> GSI 17 (level, low) ->
IRQ 17
[ 1.080778] r8169 0000:04:00.0: setting latency timer to 64
[ 1.080842] r8169 0000:04:00.0: irq 28 for MSI/MSI-X
[ 1.081132] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
[ 1.081144] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xf7fff400
[ 1.081349] eth0: RTL8168c/8111c at 0xf7e52000, 00:21:85:1a:c6:72,
XID 1c4000c0 IRQ 28
[ 1.081999] Floppy drive(s): fd0 is 1.44M
[ 1.084296] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 1.084298] e100: Copyright(c) 1999-2006 Intel Corporation
[ 1.084330] e100 0000:01:02.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 1.090341] ahci 0000:02:00.0: version 3.0
[ 1.090359] ahci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.097006] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 1.097025] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.097027] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.097029] usb usb1: Product: EHCI Host Controller
[ 1.097031] usb usb1: Manufacturer: Linux 2.6.32-5-686 ehci_hcd
[ 1.097033] usb usb1: SerialNumber: 0000:00:1a.7
[ 1.097105] usb usb1: configuration #1 chosen from 1 choice
[ 1.097132] hub 1-0:1.0: USB hub found
[ 1.097137] hub 1-0:1.0: 6 ports detected
[ 1.097193] ata_piix 0000:00:1f.2: version 2.13
[ 1.097208] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low)
-> IRQ 19
[ 1.097212] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 1.097249] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 1.097302] scsi2 : ata_piix
[ 1.097358] scsi3 : ata_piix
[ 1.098411] ata3: SATA max UDMA/133 cmd 0xac00 ctl 0xa880 bmdma
0xa400 irq 19
[ 1.098416] ata4: SATA max UDMA/133 cmd 0xa800 ctl 0xa480 bmdma
0xa408 irq 19
[ 1.098455] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low)
-> IRQ 23
[ 1.098472] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 1.098476] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 1.098484] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned
bus number 2
[ 1.098510] ehci_hcd 0000:00:1d.7: debug port 1
[ 1.102400] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 1.102412] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf7fff800
[ 1.104299] FDC 0 is a post-1991 82077
[ 1.108044] ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps
0x3 impl SATA mode
[ 1.108048] ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio
slum part
[ 1.108053] ahci 0000:02:00.0: setting latency timer to 64
[ 1.108189] scsi4 : ahci
[ 1.108248] scsi5 : ahci
[ 1.108318] ata5: SATA max UDMA/133 abar m8192@0xf9efe000 port
0xf9efe100 irq 16
[ 1.108322] ata6: SATA max UDMA/133 abar m8192@0xf9efe000 port
0xf9efe180 irq 16
[ 1.108754] e100 0000:01:02.0: PME# disabled
[ 1.109248] e100: eth1: e100_probe: addr 0xf9dff000, irq 21, MAC addr
00:d0:b7:85:0a:3f
[ 1.117009] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 1.117025] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.117028] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.117030] usb usb2: Product: EHCI Host Controller
[ 1.117032] usb usb2: Manufacturer: Linux 2.6.32-5-686 ehci_hcd
[ 1.117035] usb usb2: SerialNumber: 0000:00:1d.7
[ 1.117094] usb usb2: configuration #1 chosen from 1 choice
[ 1.117127] hub 2-0:1.0: USB hub found
[ 1.117132] hub 2-0:1.0: 6 ports detected
[ 1.117200] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low)
-> IRQ 19
[ 1.117204] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[ 1.117240] ata_piix 0000:00:1f.5: setting latency timer to 64
[ 1.117270] scsi6 : ata_piix
[ 1.117318] scsi7 : ata_piix
[ 1.118265] ata7: SATA max UDMA/133 cmd 0x9c00 ctl 0x9880 bmdma
0x9400 irq 19
[ 1.118269] ata8: SATA max UDMA/133 cmd 0x9800 ctl 0x9480 bmdma
0x9408 irq 19
[ 1.149922] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.149952] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low)
-> IRQ 16
[ 1.149957] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[ 1.149960] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[ 1.149968] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned
bus number 3
[ 1.149989] uhci_hcd 0000:00:1a.0: irq 16, io base 0x00008800
[ 1.150016] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.150018] usb usb3: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.150020] usb usb3: Product: UHCI Host Controller
[ 1.150022] usb usb3: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.150024] usb usb3: SerialNumber: 0000:00:1a.0
[ 1.150080] usb usb3: configuration #1 chosen from 1 choice
[ 1.150103] hub 3-0:1.0: USB hub found
[ 1.150108] hub 3-0:1.0: 2 ports detected
[ 1.150149] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low)
-> IRQ 21
[ 1.150154] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[ 1.150156] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[ 1.150162] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned
bus number 4
[ 1.150189] uhci_hcd 0000:00:1a.1: irq 21, io base 0x00008480
[ 1.150212] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.150214] usb usb4: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.150216] usb usb4: Product: UHCI Host Controller
[ 1.150218] usb usb4: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.150220] usb usb4: SerialNumber: 0000:00:1a.1
[ 1.150269] usb usb4: configuration #1 chosen from 1 choice
[ 1.150293] hub 4-0:1.0: USB hub found
[ 1.150298] hub 4-0:1.0: 2 ports detected
[ 1.150341] uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low)
-> IRQ 19
[ 1.150345] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[ 1.150348] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[ 1.150353] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned
bus number 5
[ 1.150374] uhci_hcd 0000:00:1a.2: irq 19, io base 0x00008400
[ 1.150399] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.150401] usb usb5: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.150403] usb usb5: Product: UHCI Host Controller
[ 1.150404] usb usb5: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.150406] usb usb5: SerialNumber: 0000:00:1a.2
[ 1.150455] usb usb5: configuration #1 chosen from 1 choice
[ 1.150480] hub 5-0:1.0: USB hub found
[ 1.150484] hub 5-0:1.0: 2 ports detected
[ 1.150522] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low)
-> IRQ 23
[ 1.150527] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 1.150530] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 1.150538] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned
bus number 6
[ 1.150559] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00009000
[ 1.150582] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.150584] usb usb6: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.150586] usb usb6: Product: UHCI Host Controller
[ 1.150588] usb usb6: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.150590] usb usb6: SerialNumber: 0000:00:1d.0
[ 1.150639] usb usb6: configuration #1 chosen from 1 choice
[ 1.150662] hub 6-0:1.0: USB hub found
[ 1.150668] hub 6-0:1.0: 2 ports detected
[ 1.150703] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low)
-> IRQ 19
[ 1.150708] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 1.150711] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 1.150716] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned
bus number 7
[ 1.150735] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00008c00
[ 1.150758] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.150761] usb usb7: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.150763] usb usb7: Product: UHCI Host Controller
[ 1.150764] usb usb7: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.150766] usb usb7: SerialNumber: 0000:00:1d.1
[ 1.150811] usb usb7: configuration #1 chosen from 1 choice
[ 1.150835] hub 7-0:1.0: USB hub found
[ 1.150842] hub 7-0:1.0: 2 ports detected
[ 1.150878] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low)
-> IRQ 18
[ 1.150883] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 1.150886] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 1.150891] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned
bus number 8
[ 1.150911] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00008880
[ 1.150934] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.150936] usb usb8: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.150938] usb usb8: Product: UHCI Host Controller
[ 1.150940] usb usb8: Manufacturer: Linux 2.6.32-5-686 uhci_hcd
[ 1.150941] usb usb8: SerialNumber: 0000:00:1d.2
[ 1.150991] usb usb8: configuration #1 chosen from 1 choice
[ 1.151015] hub 8-0:1.0: USB hub found
[ 1.151020] hub 8-0:1.0: 2 ports detected
[ 1.420758] ata1.00: ATA-6: ST380011A, 8.01, max UDMA/100
[ 1.420762] ata1.00: 156301488 sectors, multi 16: LBA48
[ 1.421134] ata1.01: ATA-5: QUANTUM FIREBALLP LM15, A35.0700, max UDMA/66
[ 1.421138] ata1.01: 29336832 sectors, multi 16: LBA
[ 1.424035] ata5: SATA link down (SStatus 0 SControl 300)
[ 1.424039] ata6: SATA link down (SStatus 0 SControl 300)
[ 1.446635] ata7: SATA link down (SStatus 0 SControl 300)
[ 1.446647] ata1.00: configured for UDMA/100
[ 1.457112] ata8: SATA link down (SStatus 0 SControl 300)
[ 1.464871] ata1.01: configured for UDMA/66
[ 1.464973] scsi 0:0:0:0: Direct-Access ATA ST380011A
8.01 PQ: 0 ANSI: 5
[ 1.465118] scsi 0:0:1:0: Direct-Access ATA QUANTUM FIREBALL
A35. PQ: 0 ANSI: 5
[ 1.600008] usb 4-2: new low speed USB device using uhci_hcd and
address 2
[ 1.751063] ata4.00: SATA link down (SStatus 0 SControl 300)
[ 1.751083] ata4.01: SATA link down (SStatus 0 SControl 300)
[ 1.904057] ata3.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.904069] ata3.01: SATA link down (SStatus 0 SControl 300)
[ 1.904078] ata3.01: link offline, clearing class 3 to NONE
[ 1.909169] usb 4-2: New USB device found, idVendor=051d, idProduct=0002
[ 1.909172] usb 4-2: New USB device strings: Mfr=3, Product=1,
SerialNumber=2
[ 1.909175] usb 4-2: Product: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8
[ 1.909177] usb 4-2: Manufacturer: American Power Conversion
[ 1.909179] usb 4-2: SerialNumber: QB0512132444
[ 1.909258] usb 4-2: configuration #1 chosen from 1 choice
[ 1.916198] ata3.00: ATAPI: PIONEER DVD-RW DVR-218L, 1.02, max UDMA/100
[ 1.928711] ata3.00: configured for UDMA/100
[ 1.933545] scsi 2:0:0:0: CD-ROM PIONEER DVD-RW DVR-218L
1.02 PQ: 0 ANSI: 5
[ 1.937310] usbcore: registered new interface driver hiddev
[ 1.942692] sd 0:0:0:0: [sda] 156301488 512-byte logical blocks:
(80.0 GB/74.5 GiB)
[ 1.942737] sd 0:0:1:0: [sdb] 29336832 512-byte logical blocks: (15.0
GB/13.9 GiB)
[ 1.942791] sd 0:0:0:0: [sda] Write Protect is off
[ 1.942794] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.942813] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 1.942848] sd 0:0:1:0: [sdb] Write Protect is off
[ 1.942851] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.942871] sd 0:0:1:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 1.942956] sda: sda1 sda2 < sda5
[ 1.971512] sdb: sda6 sdb1
[ 1.990021] sda7 sda8 sda9 sda10 sda11 sda12 >
[ 2.064081] sd 0:0:1:0: [sdb] Attached SCSI disk
[ 2.068878] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.081206] sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw
xa/form2 cdda tray
[ 2.081209] Uniform CD-ROM driver Revision: 3.20
[ 2.081285] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 2.084915] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 2.084947] sd 0:0:1:0: Attached scsi generic sg1 type 0
[ 2.084970] sr 2:0:0:0: Attached scsi generic sg2 type 5
[ 3.002198] generic-usb 0003:051D:0002.0001: hiddev0,hidraw0: USB HID
v1.10 Device [American Power Conversion Back-UPS RS 1500 FW:8.g8 .D USB
FW:g8 ] on usb-0000:00:1a.1-2/input0
[ 3.002227] usbcore: registered new interface driver usbhid
[ 3.002229] usbhid: v2.6:USB HID core driver
[ 3.085554] PM: Starting manual resume from disk
[ 3.085557] PM: Resume from partition 8:10
[ 3.085558] PM: Checking hibernation image.
[ 3.103259] PM: Error -22 checking image file
[ 3.103261] PM: Resume from disk failed.
[ 3.134596] kjournald starting. Commit interval 5 seconds
[ 3.134605] EXT3-fs: mounted filesystem with ordered data mode.
[ 5.058844] udev[494]: starting version 164
[ 5.210993] input: Power Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[ 5.210999] ACPI: Power Button [PWRB]
[ 5.211043] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 5.211046] ACPI: Power Button [PWRF]
[ 5.502278] input: PC Speaker as /devices/platform/pcspkr/input/input3
[ 6.518680] nvidia: module license 'NVIDIA' taints kernel.
[ 6.518683] Disabling lock debugging due to kernel taint
[ 7.281186] ACPI: SSDT 7ff9e0c0 001F3 (v01 DpgPmm P001Ist 00000011
INTL 20051117)
[ 7.281506] processor LNXCPU:00: registered as cooling_device0
[ 7.281830] ACPI: SSDT 7ff9e2c0 001F3 (v01 DpgPmm P002Ist 00000012
INTL 20051117)
[ 7.282087] processor LNXCPU:01: registered as cooling_device1
[ 7.282422] ACPI: SSDT 7ff9e4c0 001F3 (v01 DpgPmm P003Ist 00000012
INTL 20051117)
[ 7.283546] processor LNXCPU:02: registered as cooling_device2
[ 7.283908] ACPI: SSDT 7ff9e6c0 001F3 (v01 DpgPmm P004Ist 00000012
INTL 20051117)
[ 7.284118] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low)
-> IRQ 18
[ 7.284551] processor LNXCPU:03: registered as cooling_device3
[ 7.526117] nvidia 0000:05:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 7.526124] nvidia 0000:05:00.0: setting latency timer to 64
[ 7.526128] vgaarb: device changed decodes:
PCI:0000:05:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[ 7.526233] NVRM: loading NVIDIA UNIX x86 Kernel Module 260.19.29
Wed Dec 8 12:09:09 PST 2010
[ 8.141063] input: ImPS/2 Generic Wheel Mouse as
/devices/platform/i8042/serio1/input/input4
[ 8.467172] Linux video capture interface: v2.00
[ 8.569198] cx8800: Unknown parameter `card'
[ 8.711602] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low)
-> IRQ 22
[ 8.711632] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 8.800874] hda_codec: ALC888: BIOS auto-probing.
[ 8.802221] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input5
[ 9.322864] Adding 2361512k swap on /dev/sda10. Priority:-1
extents:1 across:2361512k
[ 10.020883] EXT3 FS on sda1, internal journal
[ 10.126561] loop: module loaded
[ 10.187118] fuse init (API version 7.13)
[ 10.265354] f71882fg: Found f71882fg chip at 0xa00, revision 32
[ 10.265717] f71882fg f71882fg.2560: Fan: 1 is in duty-cycle mode
[ 10.265720] f71882fg f71882fg.2560: Fan: 2 is in duty-cycle mode
[ 10.265722] f71882fg f71882fg.2560: Fan: 3 is in duty-cycle mode
[ 10.265724] f71882fg f71882fg.2560: Fan: 4 is in duty-cycle mode
[ 13.571563] kjournald starting. Commit interval 5 seconds
[ 13.571779] EXT3 FS on sda5, internal journal
[ 13.571783] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.625563] kjournald starting. Commit interval 5 seconds
[ 13.625782] EXT3 FS on sda6, internal journal
[ 13.625785] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.689546] kjournald starting. Commit interval 5 seconds
[ 13.689776] EXT3 FS on sda7, internal journal
[ 13.689780] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.738509] kjournald starting. Commit interval 5 seconds
[ 13.738742] EXT3 FS on sda8, internal journal
[ 13.738746] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.153072] kjournald starting. Commit interval 5 seconds
[ 14.153380] EXT3 FS on sda9, internal journal
[ 14.153384] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.503900] kjournald starting. Commit interval 5 seconds
[ 14.504198] EXT3 FS on sda11, internal journal
[ 14.504202] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.644168] kjournald starting. Commit interval 5 seconds
[ 14.644414] EXT3 FS on sda12, internal journal
[ 14.644417] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.690279] kjournald starting. Commit interval 5 seconds
[ 14.690614] EXT3 FS on sdb1, internal journal
[ 14.690617] EXT3-fs: mounted filesystem with ordered data mode.
[ 15.821857] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 15.854908] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 15.855149] CONFIG_NF_CT_ACCT is deprecated and will be removed soon.
Please use
[ 15.855155] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack
module option or
[ 15.855155] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 16.738919] r8169: eth0: link up
[ 16.738928] r8169: eth0: link up
[ 27.729504] eth0: no IPv6 routers present
[ 34.548734] vboxdrv: Found 4 processor cores.
[ 34.548834] vboxdrv: fAsync=0 offMin=0x460 offMax=0x13ef
[ 34.548874] vboxdrv: TSC mode is 'synchronous', kernel timer mode is
'normal'.
[ 34.548876] vboxdrv: Successfully loaded version 4.0.0 (interface
0x00160000).
$ xawtv
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
v4l2: open /dev/video0: No such file or directory
v4l2: open /dev/video0: No such file or directory
v4l: open /dev/video0: No such file or directory
no video grabber device available
Weird. As root/su, I reran: modprobe -a cx8800 and saw no errors. Then,
this again in my dmesg: [ 565.399799] cx8800: Unknown parameter `card'
What the heck? I think I broke it, did something wrong, or forgot
something! Sheesh, this is difficult. :(
# lsmod
Module Size Used by
vboxnetadp 5254 0
vboxnetflt 15384 0
vboxdrv 144401 2 vboxnetadp,vboxnetflt
acpi_cpufreq 4951 0
cpufreq_powersave 602 0
cpufreq_userspace 1480 0
cpufreq_stats 1940 0
cpufreq_conservative 4018 0
xt_tcpudp 1743 92
xt_limit 1088 2
nf_conntrack_ipv4 7597 59
nf_defrag_ipv4 779 1 nf_conntrack_ipv4
xt_state 927 59
ipt_LOG 3570 2
ipt_REJECT 1517 2
nf_conntrack_irc 2535 0
nf_conntrack_ftp 4272 0
nf_conntrack 38075 4
nf_conntrack_ipv4,xt_state,nf_conntrack_irc,nf_conntrack_ftp
iptable_filter 1790 1
ip_tables 7690 1 iptable_filter
x_tables 8327 6
xt_tcpudp,xt_limit,xt_state,ipt_LOG,ipt_REJECT,ip_tables
f71882fg 18898 0
coretemp 3401 0
adt7473 8792 0
fuse 43941 1
loop 9765 0
snd_hda_codec_realtek 163282 1
snd_hda_intel 16787 1
snd_hda_codec 46002 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 4054 1 snd_hda_codec
snd_pcm_oss 28671 0
snd_mixer_oss 10461 1 snd_pcm_oss
snd_pcm 47222 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi 3576 0
snd_rawmidi 12513 1 snd_seq_midi
snd_seq_midi_event 3684 1 snd_seq_midi
snd_seq 35463 2 snd_seq_midi,snd_seq_midi_event
snd_timer 12258 2 snd_pcm,snd_seq
cx88xx 59092 0
snd_seq_device 3673 3 snd_seq_midi,snd_rawmidi,snd_seq
ir_common 22187 1 cx88xx
i2c_algo_bit 3497 1 cx88xx
tveeprom 9393 1 cx88xx
v4l2_common 9820 1 cx88xx
videodev 25545 2 cx88xx,v4l2_common
v4l1_compat 10250 1 videodev
videobuf_dma_sg 7203 1 cx88xx
snd 34375 13
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
videobuf_core 10476 2 cx88xx,videobuf_dma_sg
soundcore 3450 1 snd
psmouse 44657 0
snd_page_alloc 5045 2 snd_hda_intel,snd_pcm
btcx_risc 2499 1 cx88xx
i2c_i801 6462 0
serio_raw 2916 0
evdev 5609 7
processor 26327 1 acpi_cpufreq
nvidia 9222163 38
pcspkr 1207 0
i2c_core 12696 8
adt7473,cx88xx,i2c_algo_bit,tveeprom,v4l2_common,videodev,i2c_i801,nvidia
button 3598 0
ext3 94204 9
jbd 32169 1 ext3
mbcache 3762 1 ext3
sg 15968 0
sr_mod 10770 0
cdrom 26487 1 sr_mod
sd_mod 25969 12
crc_t10dif 1012 1 sd_mod
usbhid 28008 2
hid 50873 1 usbhid
ata_generic 2067 0
uhci_hcd 16057 0
ahci 27270 0
ata_piix 17736 0
e100 22317 0
floppy 40923 0
r8169 24860 0
mii 2714 2 e100,r8169
pata_jmicron 1452 11
ehci_hcd 27851 0
libata 115753 4 ata_generic,ahci,ata_piix,pata_jmicron
scsi_mod 101421 4 sg,sr_mod,sd_mod,libata
usbcore 98453 6 usbhid,uhci_hcd,ehci_hcd
nls_base 4541 1 usbcore
thermal 9206 0
thermal_sys 9378 2 processor,thermal
ANTian:/home/ant/download# lsmod
Module Size Used by
vboxnetadp 5254 0
vboxnetflt 15384 0
vboxdrv 144401 2 vboxnetadp,vboxnetflt
acpi_cpufreq 4951 0
cpufreq_powersave 602 0
cpufreq_userspace 1480 0
cpufreq_stats 1940 0
cpufreq_conservative 4018 0
xt_tcpudp 1743 92
xt_limit 1088 2
nf_conntrack_ipv4 7597 59
nf_defrag_ipv4 779 1 nf_conntrack_ipv4
xt_state 927 59
ipt_LOG 3570 2
ipt_REJECT 1517 2
nf_conntrack_irc 2535 0
nf_conntrack_ftp 4272 0
nf_conntrack 38075 4
nf_conntrack_ipv4,xt_state,nf_conntrack_irc,nf_conntrack_ftp
iptable_filter 1790 1
ip_tables 7690 1 iptable_filter
x_tables 8327 6
xt_tcpudp,xt_limit,xt_state,ipt_LOG,ipt_REJECT,ip_tables
f71882fg 18898 0
coretemp 3401 0
adt7473 8792 0
fuse 43941 1
loop 9765 0
snd_hda_codec_realtek 163282 1
snd_hda_intel 16787 1
snd_hda_codec 46002 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 4054 1 snd_hda_codec
snd_pcm_oss 28671 0
snd_mixer_oss 10461 1 snd_pcm_oss
snd_pcm 47222 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi 3576 0
snd_rawmidi 12513 1 snd_seq_midi
snd_seq_midi_event 3684 1 snd_seq_midi
snd_seq 35463 2 snd_seq_midi,snd_seq_midi_event
snd_timer 12258 2 snd_pcm,snd_seq
cx88xx 59092 0
snd_seq_device 3673 3 snd_seq_midi,snd_rawmidi,snd_seq
ir_common 22187 1 cx88xx
i2c_algo_bit 3497 1 cx88xx
tveeprom 9393 1 cx88xx
v4l2_common 9820 1 cx88xx
videodev 25545 2 cx88xx,v4l2_common
v4l1_compat 10250 1 videodev
videobuf_dma_sg 7203 1 cx88xx
snd 34375 13
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
videobuf_core 10476 2 cx88xx,videobuf_dma_sg
soundcore 3450 1 snd
psmouse 44657 0
snd_page_alloc 5045 2 snd_hda_intel,snd_pcm
btcx_risc 2499 1 cx88xx
i2c_i801 6462 0
serio_raw 2916 0
evdev 5609 7
processor 26327 1 acpi_cpufreq
nvidia 9222163 38
pcspkr 1207 0
i2c_core 12696 8
adt7473,cx88xx,i2c_algo_bit,tveeprom,v4l2_common,videodev,i2c_i801,nvidia
button 3598 0
ext3 94204 9
jbd 32169 1 ext3
mbcache 3762 1 ext3
sg 15968 0
sr_mod 10770 0
cdrom 26487 1 sr_mod
sd_mod 25969 12
crc_t10dif 1012 1 sd_mod
usbhid 28008 2
hid 50873 1 usbhid
ata_generic 2067 0
uhci_hcd 16057 0
ahci 27270 0
ata_piix 17736 0
e100 22317 0
floppy 40923 0
r8169 24860 0
mii 2714 2 e100,r8169
pata_jmicron 1452 11
ehci_hcd 27851 0
libata 115753 4 ata_generic,ahci,ata_piix,pata_jmicron
scsi_mod 101421 4 sg,sr_mod,sd_mod,libata
usbcore 98453 6 usbhid,uhci_hcd,ehci_hcd
nls_base 4541 1 usbcore
thermal 9206 0
thermal_sys 9378 2 processor,thermal
--
"One day he sprained an ankle rather than crush an ant." --Les Miserables
Kevin Snodgrass
> On 12/24/2010 3:42 PM PT, J G Miller typed:
>
>>> Then, I noticed you had "module" instead of "option" in
>>> /etc/modprobe.d/cx8800.conf so I fixed that to show: # cat cx8800.conf
>>> # ASUS TV Tuner Card 880 NTSC (cx23880)
>>>
>>> module cx8800 card=12
>>
>> Yes sorry again -- that of course should be
>>
>> options cx8800 card=12
>
> NP. I make lots of silly mistakes/errors too. Ah, with a "s" this time.
I don't have any .conf files with the keyword "options" in them. What I
do see are the keywords "alias" and "install". I'm thinking you might
need to change "options" to "install" here.
> I ran without any errors or texts. Nothing added in dmesg too! Weird. So
> I installed and ran xawtv for kicks to see what happens.
Just check for /dev/video0. When the module loads correctly that
character device special will appear. (Like magic! :-)) On this machine
I have 1 Hauppauge PVR-250 and here are the /dev/ entries that matter:
$ ls -l /dev/video*
crw-rw----+ 1 root video 81, 0 Dec 24 12:16 /dev/video0
crw-rw----+ 1 root video 81, 3 Dec 24 12:16 /dev/video24
crw-rw----+ 1 root video 81, 1 Dec 24 12:16 /dev/video32
At one time I actually knew what /dev/video24 and /dev/video32 were for,
but unfortunately my gray matter seems to be leaking out.
> For now, I only want to worry about video/picture. I played with xawtv
> for a bit, but only statics. I tried other three composite options and
xawtv will not be of much use without /dev/video0. That is the device it
will try to read from.
J G Miller
(It really would help if you just posted the relevant lines
and not reams of dmesg output)
[ 8.467172] Linux video capture interface: v2.00
[ 8.569198] cx8800: Unknown parameter `card'
This I do not understand since in the previous dmesg
[ 7.897629] cx88[0]: Here is a list of valid choices for the card=<n>
insmod option:
[ 7.897694] cx88[0]: card=0 -> UNKNOWN/GENERIC
...
So you really do have a line
options cx8800 card=12
in your /etc/modprobe.d configuration file?
*But* a further web search indicates that the card option
must be applied not to the cx8800 module but the cx88xx module.
So please try again with your modprobe.d file changed to
options cx88xx card=12
reboot and check the dmesg again.
If it works, the device /dev/video should then appear, and
xawtv will not complain about the non-existent interface device
not being present.
PS when I said do a modprobe -r of all the loaded v4l2 modules,
v4l2 is the generic term Video For Linux Version 2 modules, which
in your case are all of the cx88* modules and maybe the tuner module
as well. In your lsmod output you also see the lower layer
v4l2_common and v4l1_compat modules which are used by the cx88* modules.
It is also possible that you may need to add a tuner type option,
as well as adding some options to cx8800 itself.
QUOTE
options cx8800 video_nr=0 radio_nr=0
options cx88xx card=27 tuner=44
UNQUOTE
NB The card number is different to 12 because it is for a different cx88 chip based card
(PixelView Ultra Pro)
Ant
>>>> Then, I noticed you had "module" instead of "option" in
>>>> /etc/modprobe.d/cx8800.conf so I fixed that to show: # cat cx8800.conf
>>>> # ASUS TV Tuner Card 880 NTSC (cx23880)
>>>>
>>>> module cx8800 card=12
>>>
>>> Yes sorry again -- that of course should be
>>>
>>> options cx8800 card=12
>>
>> NP. I make lots of silly mistakes/errors too. Ah, with a "s" this time.
>
> I don't have any .conf files with the keyword "options" in them. What I
> do see are the keywords "alias" and "install". I'm thinking you might
> need to change "options" to "install" here.
Hmm. Maybe?
>> I ran without any errors or texts. Nothing added in dmesg too! Weird. So
>> I installed and ran xawtv for kicks to see what happens.
>
> Just check for /dev/video0. When the module loads correctly that
> character device special will appear. (Like magic! :-)) On this machine
> I have 1 Hauppauge PVR-250 and here are the /dev/ entries that matter:
>
> $ ls -l /dev/video*
> crw-rw----+ 1 root video 81, 0 Dec 24 12:16 /dev/video0
> crw-rw----+ 1 root video 81, 3 Dec 24 12:16 /dev/video24
> crw-rw----+ 1 root video 81, 1 Dec 24 12:16 /dev/video32
>
> At one time I actually knew what /dev/video24 and /dev/video32 were for,
> but unfortunately my gray matter seems to be leaking out.
Hmm:
$ ls /dev/video*
ls: cannot access /dev/video*: No such file or directory
>> For now, I only want to worry about video/picture. I played with xawtv
>> for a bit, but only statics. I tried other three composite options and
>
> xawtv will not be of much use without /dev/video0. That is the device it
> will try to read from.
OK. Shoot, I had it working even though it was a static video before I
rebooted. Grr.
--
"An ant is a wise creature for itself, but it is a shrewd thing in an
orchard or garden." --Francis Bacon
Ant
> On Friday, December 24th, 2010 at 17:43:32h -0800, Ant wrote:
>
> (It really would help if you just posted the relevant lines
> and not reams of dmesg output)
>
> [ 8.467172] Linux video capture interface: v2.00
> [ 8.569198] cx8800: Unknown parameter `card'
>
> This I do not understand since in the previous dmesg
[shrugs] I had xawtv working with that static video/picture before
rebooting. Grr.
> [ 7.897629] cx88[0]: Here is a list of valid choices for the card=<n>
> insmod option:
> [ 7.897694] cx88[0]: card=0 -> UNKNOWN/GENERIC
> ...
> So you really do have a line
>
> options cx8800 card=12
>
> in your /etc/modprobe.d configuration file?
Here:
$ cat /etc/modprobe.d/cx8800.conf
# ASUS TV Tuner Card 880 NTSC (cx23880)
options cx8800 card=12
See anything weird including my comment? :)
> *But* a further web search indicates that the card option
> must be applied not to the cx8800 module but the cx88xx module.
>
> So please try again with your modprobe.d file changed to
>
> options cx88xx card=12
>
> reboot and check the dmesg again.
OK, but I tried it before rebooting:
[ 8673.400326] cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
[ 8673.400362] cx8800 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 8673.400833] cx88[0]: Your board isn't known (yet) to the driver. You can
[ 8673.400835] cx88[0]: try to pick one of the existing card configs via
[ 8673.400836] cx88[0]: card=<n> insmod option. Updating to the latest
[ 8673.400837] cx88[0]: version might help as well.
[ 8673.400840] cx88[0]: Here is a list of valid choices for the card=<n>
insmod option:
[ 8673.400842] cx88[0]: card=0 -> UNKNOWN/GENERIC
[ 8673.400844] cx88[0]: card=1 -> Hauppauge WinTV 34xxx models
[ 8673.400846] cx88[0]: card=2 -> GDI Black Gold
[ 8673.400848] cx88[0]: card=3 -> PixelView
[ 8673.400850] cx88[0]: card=4 -> ATI TV Wonder Pro
[ 8673.400852] cx88[0]: card=5 -> Leadtek Winfast 2000XP Expert
[ 8673.400854] cx88[0]: card=6 -> AverTV Studio 303 (M126)
[ 8673.400856] cx88[0]: card=7 -> MSI TV-@nywhere Master
[ 8673.400858] cx88[0]: card=8 -> Leadtek Winfast DV2000
[ 8673.400860] cx88[0]: card=9 -> Leadtek PVR 2000
[ 8673.400862] cx88[0]: card=10 -> IODATA GV-VCP3/PCI
[ 8673.400864] cx88[0]: card=11 -> Prolink PlayTV PVR
[ 8673.400866] cx88[0]: card=12 -> ASUS PVR-416
[ 8673.400868] cx88[0]: card=13 -> MSI TV-@nywhere
[ 8673.400870] cx88[0]: card=14 -> KWorld/VStream XPert DVB-T
[ 8673.400872] cx88[0]: card=15 -> DViCO FusionHDTV DVB-T1
[ 8673.400874] cx88[0]: card=16 -> KWorld LTV883RF
[ 8673.400876] cx88[0]: card=17 -> DViCO FusionHDTV 3 Gold-Q
[ 8673.400878] cx88[0]: card=18 -> Hauppauge Nova-T DVB-T
[ 8673.400881] cx88[0]: card=19 -> Conexant DVB-T reference design
[ 8673.400883] cx88[0]: card=20 -> Provideo PV259
[ 8673.400885] cx88[0]: card=21 -> DViCO FusionHDTV DVB-T Plus
[ 8673.400887] cx88[0]: card=22 -> pcHDTV HD3000 HDTV
[ 8673.400889] cx88[0]: card=23 -> digitalnow DNTV Live! DVB-T
[ 8673.400891] cx88[0]: card=24 -> Hauppauge WinTV 28xxx (Roslyn) models
[ 8673.400894] cx88[0]: card=25 -> Digital-Logic MICROSPACE
Entertainment Center (MEC)
[ 8673.400896] cx88[0]: card=26 -> IODATA GV/BCTV7E
[ 8673.400898] cx88[0]: card=27 -> PixelView PlayTV Ultra Pro (Stereo)
[ 8673.400900] cx88[0]: card=28 -> DViCO FusionHDTV 3 Gold-T
[ 8673.400902] cx88[0]: card=29 -> ADS Tech Instant TV DVB-T PCI
[ 8673.400904] cx88[0]: card=30 -> TerraTec Cinergy 1400 DVB-T
[ 8673.400906] cx88[0]: card=31 -> DViCO FusionHDTV 5 Gold
[ 8673.400909] cx88[0]: card=32 -> AverMedia UltraTV Media Center PCI 550
[ 8673.400911] cx88[0]: card=33 -> Kworld V-Stream Xpert DVD
[ 8673.400913] cx88[0]: card=34 -> ATI HDTV Wonder
[ 8673.400915] cx88[0]: card=35 -> WinFast DTV1000-T
[ 8673.400917] cx88[0]: card=36 -> AVerTV 303 (M126)
[ 8673.400919] cx88[0]: card=37 -> Hauppauge Nova-S-Plus DVB-S
[ 8673.400921] cx88[0]: card=38 -> Hauppauge Nova-SE2 DVB-S
[ 8673.400923] cx88[0]: card=39 -> KWorld DVB-S 100
[ 8673.400925] cx88[0]: card=40 -> Hauppauge WinTV-HVR1100 DVB-T/Hybrid
[ 8673.400927] cx88[0]: card=41 -> Hauppauge WinTV-HVR1100
DVB-T/Hybrid (Low Profile)
[ 8673.400930] cx88[0]: card=42 -> digitalnow DNTV Live! DVB-T Pro
[ 8673.400932] cx88[0]: card=43 -> KWorld/VStream XPert DVB-T with
cx22702
[ 8673.400934] cx88[0]: card=44 -> DViCO FusionHDTV DVB-T Dual Digital
[ 8673.400936] cx88[0]: card=45 -> KWorld HardwareMpegTV XPert
[ 8673.400938] cx88[0]: card=46 -> DViCO FusionHDTV DVB-T Hybrid
[ 8673.400940] cx88[0]: card=47 -> pcHDTV HD5500 HDTV
[ 8673.400942] cx88[0]: card=48 -> Kworld MCE 200 Deluxe
[ 8673.400945] cx88[0]: card=49 -> PixelView PlayTV P7000
[ 8673.400947] cx88[0]: card=50 -> NPG Tech Real TV FM Top 10
[ 8673.400949] cx88[0]: card=51 -> WinFast DTV2000 H
[ 8673.400951] cx88[0]: card=52 -> Geniatech DVB-S
[ 8673.400953] cx88[0]: card=53 -> Hauppauge WinTV-HVR3000 TriMode
Analog/DVB-S/DVB-T
[ 8673.400955] cx88[0]: card=54 -> Norwood Micro TV Tuner
[ 8673.400957] cx88[0]: card=55 -> Shenzhen Tungsten Ages Tech
TE-DTV-250 / Swann OEM
[ 8673.400959] cx88[0]: card=56 -> Hauppauge WinTV-HVR1300
DVB-T/Hybrid MPEG Encoder
[ 8673.400961] cx88[0]: card=57 -> ADS Tech Instant Video PCI
[ 8673.400963] cx88[0]: card=58 -> Pinnacle PCTV HD 800i
[ 8673.400965] cx88[0]: card=59 -> DViCO FusionHDTV 5 PCI nano
[ 8673.400967] cx88[0]: card=60 -> Pinnacle Hybrid PCTV
[ 8673.400969] cx88[0]: card=61 -> Leadtek TV2000 XP Global
[ 8673.400971] cx88[0]: card=62 -> PowerColor RA330
[ 8673.400973] cx88[0]: card=63 -> Geniatech X8000-MT DVBT
[ 8673.400975] cx88[0]: card=64 -> DViCO FusionHDTV DVB-T PRO
[ 8673.400977] cx88[0]: card=65 -> DViCO FusionHDTV 7 Gold
[ 8673.400979] cx88[0]: card=66 -> Prolink Pixelview MPEG 8000GT
[ 8673.400982] cx88[0]: card=67 -> Kworld PlusTV HD PCI 120 (ATSC 120)
[ 8673.400984] cx88[0]: card=68 -> Hauppauge WinTV-HVR4000
DVB-S/S2/T/Hybrid
[ 8673.400986] cx88[0]: card=69 -> Hauppauge WinTV-HVR4000(Lite) DVB-S/S2
[ 8673.400988] cx88[0]: card=70 -> TeVii S460 DVB-S/S2
[ 8673.400990] cx88[0]: card=71 -> Omicom SS4 DVB-S/S2 PCI
[ 8673.400992] cx88[0]: card=72 -> TBS 8920 DVB-S/S2
[ 8673.400994] cx88[0]: card=73 -> TeVii S420 DVB-S
[ 8673.400996] cx88[0]: card=74 -> Prolink Pixelview Global Extreme
[ 8673.400999] cx88[0]: card=75 -> PROF 7300 DVB-S/S2
[ 8673.401001] cx88[0]: card=76 -> SATTRADE ST4200 DVB-S/S2
[ 8673.401003] cx88[0]: card=77 -> TBS 8910 DVB-S
[ 8673.401005] cx88[0]: card=78 -> Prof 6200 DVB-S
[ 8673.401007] cx88[0]: card=79 -> Terratec Cinergy HT PCI MKII
[ 8673.401009] cx88[0]: card=80 -> Hauppauge WinTV-IR Only
[ 8673.401011] cx88[0]: card=81 -> Leadtek WinFast DTV1800 Hybrid
[ 8673.401013] cx88[0]: card=82 -> WinFast DTV2000 H rev. J
[ 8673.401016] cx88[0]: subsystem: 1043:4820, board: UNKNOWN/GENERIC
[card=0,autodetected], frontend(s): 0
[ 8673.401019] cx88[0]: TV tuner type -1, Radio tuner type -1
[ 8673.557707] All bytes are equal. It is not a TEA5767
[ 8673.557768] tuner 4-0060: chip found @ 0xc0 (cx88[0])
[ 8673.609770] cx88[0]/0: found at 0000:01:00.0, rev: 3, irq: 16,
latency: 64, mmio: 0xf8000000
[ 8673.609779] IRQ 16/cx88[0]: IRQF_DISABLED is not guaranteed on shared
IRQs
[ 8673.609848] cx88[0]/0: registered device video0 [v4l2]
[ 8673.609872] cx88[0]/0: registered device vbi0
[ 8673.609890] tuner 4-0060: tuner type not set
I ran xwatv and got the same results from earlier before I rebooted that
session. Again more dmesg lines:
[ 8722.038583] tuner 4-0060: tuner type not set
[ 8729.144605] tuner 4-0060: tuner type not set
[ 8737.320007] cx88[0]: video y / packed - dma channel status dump
[ 8737.320013] cx88[0]: cmds: initial risc: 0x32b9c000
[ 8737.320016] cx88[0]: cmds: cdt base : 0x00180440
[ 8737.320019] cx88[0]: cmds: cdt size : 0x0000000a
[ 8737.320022] cx88[0]: cmds: iq base : 0x00180400
[ 8737.320025] cx88[0]: cmds: iq size : 0x00000010
[ 8737.320028] cx88[0]: cmds: risc pc : 0x32b9c034
[ 8737.320031] cx88[0]: cmds: iq wr ptr : 0x0000010d
[ 8737.320034] cx88[0]: cmds: iq rd ptr : 0x00000101
[ 8737.320036] cx88[0]: cmds: cdt current : 0x00000488
[ 8737.320039] cx88[0]: cmds: pci target : 0x00000000
[ 8737.320042] cx88[0]: cmds: line / byte : 0x00000000
[ 8737.320045] cx88[0]: risc0: 0x80008000 [ sync resync count=0 ]
[ 8737.320050] cx88[0]: risc1: 0x1c000780 [ write sol eol count=1920 ]
[ 8737.320055] cx88[0]: risc2: 0x32fbd000 [ arg #1 ]
[ 8737.320058] cx88[0]: risc3: 0x18000100 [ write sol count=256 ]
[ 8737.320063] cx88[0]: iq 0: 0x80008000 [ sync resync count=0 ]
[ 8737.320067] cx88[0]: iq 1: 0x1c000780 [ write sol eol count=1920 ]
[ 8737.320072] cx88[0]: iq 2: 0x32fbd000 [ arg #1 ]
[ 8737.320075] cx88[0]: iq 3: 0x18000100 [ write sol count=256 ]
[ 8737.320080] cx88[0]: iq 4: 0x32fbdf00 [ arg #1 ]
[ 8737.320082] cx88[0]: iq 5: 0x14000680 [ write eol count=1664 ]
[ 8737.320087] cx88[0]: iq 6: 0x329b8000 [ arg #1 ]
[ 8737.320090] cx88[0]: iq 7: 0x18000200 [ write sol count=512 ]
[ 8737.320095] cx88[0]: iq 8: 0x329b8e00 [ arg #1 ]
[ 8737.320097] cx88[0]: iq 9: 0x14000580 [ write eol count=1408 ]
[ 8737.320102] cx88[0]: iq a: 0x329b9000 [ arg #1 ]
[ 8737.320105] cx88[0]: iq b: 0x18000300 [ write sol count=768 ]
[ 8737.320110] cx88[0]: iq c: 0x329b9d00 [ arg #1 ]
[ 8737.320112] cx88[0]: iq d: 0x329b9e00 [ INVALID irq2 23 20 19 cnt1
cnt0 resync 12 count=3584 ]
[ 8737.320120] cx88[0]: iq e: 0x14000400 [ write eol count=1024 ]
[ 8737.320125] cx88[0]: iq f: 0x329b8000 [ arg #1 ]
[ 8737.320127] cx88[0]: fifo: 0x00180c00 -> 0x183400
[ 8737.320128] cx88[0]: ctrl: 0x00180400 -> 0x180460
[ 8737.320131] cx88[0]: ptr1_reg: 0x00181568
[ 8737.320134] cx88[0]: ptr2_reg: 0x00180458
[ 8737.320136] cx88[0]: cnt1_reg: 0x00000054
[ 8737.320139] cx88[0]: cnt2_reg: 0x00000000
[ 8737.320145] cx88[0]/0: [f2c75b40/0] timeout - dma=0x32b9c000
:/ OK, so I rebooted again to see if the automatic card detection works.
Whole dmesg: http://pastie.org/1404218 ... I saw:
[ 8.688295] cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
[ 8.688326] cx8800 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 8.688703] cx88[0]: subsystem: 1043:4820, board: ASUS PVR-416
[card=12,insmod option], frontend(s): 0
[ 8.688705] cx88[0]: TV tuner type 43, Radio tuner type -1
[ 8.878918] tuner 1-0060: chip found @ 0xc0 (cx88[0])
[ 8.965047] cx88[0]/0: found at 0000:01:00.0, rev: 3, irq: 16,
latency: 64, mmio: 0xf8000000
[ 8.965106] cx88[0]/0: registered device video0 [v4l2]
[ 8.965125] cx88[0]/0: registered device vbi0
[ 8.965148] cx88[0]/0: registered device radi
I saw /dev/video0 and xawtv loaded, but same old static
video/screen/picture. dmesg had errors again while I was playing with it:
[ 295.924914] cx88[0]/0: tvaudio support needs work for this tv norm
[NTSC-443], sorry
[ 297.624004] cx88[0]: video y / packed - dma channel status dump
[ 297.624008] cx88[0]: cmds: initial risc: 0x33ff6000
[ 297.624012] cx88[0]: cmds: cdt base : 0x00180440
[ 297.624015] cx88[0]: cmds: cdt size : 0x0000000c
[ 297.624017] cx88[0]: cmds: iq base : 0x00180400
[ 297.624020] cx88[0]: cmds: iq size : 0x00000010
[ 297.624023] cx88[0]: cmds: risc pc : 0x33ff6548
[ 297.624026] cx88[0]: cmds: iq wr ptr : 0x00000104
[ 297.624029] cx88[0]: cmds: iq rd ptr : 0x00000108
[ 297.624032] cx88[0]: cmds: cdt current : 0x00000448
[ 297.624034] cx88[0]: cmds: pci target : 0x33fc1d00
[ 297.624037] cx88[0]: cmds: line / byte : 0x00900000
[ 297.624040] cx88[0]: risc0: 0x80008200 [ sync resync count=512 ]
[ 297.624045] cx88[0]: risc1: 0x1c000300 [ write sol eol count=768 ]
[ 297.624050] cx88[0]: risc2: 0x33a21300 [ arg #1 ]
[ 297.624053] cx88[0]: risc3: 0x1c000300 [ write sol eol count=768 ]
[ 297.624058] cx88[0]: iq 0: 0x1c000300 [ write sol eol count=768 ]
[ 297.624064] cx88[0]: iq 1: 0x33ff5500 [ arg #1 ]
[ 297.624066] cx88[0]: iq 2: 0x1c000300 [ write sol eol count=768 ]
[ 297.624072] cx88[0]: iq 3: 0x33ff5b00 [ arg #1 ]
[ 297.624074] cx88[0]: iq 4: 0x33fc1400 [ INVALID irq2 irq1 23 22 21
20 19 18 12 count=1024 ]
[ 297.624082] cx88[0]: iq 5: 0x1c000300 [ write sol eol count=768 ]
[ 297.624087] cx88[0]: iq 6: 0x33fc1a00 [ arg #1 ]
[ 297.624090] cx88[0]: iq 7: 0x80008200 [ sync resync count=512 ]
[ 297.624094] cx88[0]: iq 8: 0x1c000300 [ write sol eol count=768 ]
[ 297.624100] cx88[0]: iq 9: 0x33a21300 [ arg #1 ]
[ 297.624102] cx88[0]: iq a: 0x1c000300 [ write sol eol count=768 ]
[ 297.624108] cx88[0]: iq b: 0x33a21900 [ arg #1 ]
[ 297.624110] cx88[0]: iq c: 0x18000100 [ write sol count=256 ]
[ 297.624115] cx88[0]: iq d: 0x33a21f00 [ arg #1 ]
[ 297.624118] cx88[0]: iq e: 0x14000200 [ write eol count=512 ]
[ 297.624123] cx88[0]: iq f: 0x33ff5000 [ arg #1 ]
[ 297.624125] cx88[0]: fifo: 0x00180c00 -> 0x183400
[ 297.624127] cx88[0]: ctrl: 0x00180400 -> 0x180460
[ 297.624129] cx88[0]: ptr1_reg: 0x00181190
[ 297.624132] cx88[0]: ptr2_reg: 0x00180458
[ 297.624134] cx88[0]: cnt1_reg: 0x00000052
[ 297.624137] cx88[0]: cnt2_reg: 0x00000000
[ 297.624143] cx88[0]/0: [f3c63cc0/0] timeout - dma=0x33ff6000
[ 297.624145] cx88[0]/0: [f3c63f00/1] timeout - dma=0x339c4000
[ 355.376004] cx88[0]: video y / packed - dma channel status dump
[ 355.376008] cx88[0]: cmds: initial risc: 0x33ca6000
[ 355.376012] cx88[0]: cmds: cdt base : 0x00180440
[ 355.376015] cx88[0]: cmds: cdt size : 0x0000000a
[ 355.376017] cx88[0]: cmds: iq base : 0x00180400
[ 355.376020] cx88[0]: cmds: iq size : 0x00000010
[ 355.376023] cx88[0]: cmds: risc pc : 0x33ca6034
[ 355.376026] cx88[0]: cmds: iq wr ptr : 0x0000010d
[ 355.376029] cx88[0]: cmds: iq rd ptr : 0x00000101
[ 355.376032] cx88[0]: cmds: cdt current : 0x00000468
[ 355.376034] cx88[0]: cmds: pci target : 0x00000000
[ 355.376037] cx88[0]: cmds: line / byte : 0x00000000
[ 355.376040] cx88[0]: risc0: 0x80008000 [ sync resync count=0 ]
[ 355.376045] cx88[0]: risc1: 0x1c000780 [ write sol eol count=1920 ]
[ 355.376050] cx88[0]: risc2: 0x33feb000 [ arg #1 ]
[ 355.376053] cx88[0]: risc3: 0x18000100 [ write sol count=256 ]
[ 355.376058] cx88[0]: iq 0: 0x80008000 [ sync resync count=0 ]
[ 355.376062] cx88[0]: iq 1: 0x1c000780 [ write sol eol count=1920 ]
[ 355.376067] cx88[0]: iq 2: 0x33feb000 [ arg #1 ]
[ 355.376070] cx88[0]: iq 3: 0x18000100 [ write sol count=256 ]
[ 355.376075] cx88[0]: iq 4: 0x33febf00 [ arg #1 ]
[ 355.376078] cx88[0]: iq 5: 0x14000680 [ write eol count=1664 ]
[ 355.376083] cx88[0]: iq 6: 0x33fec000 [ arg #1 ]
[ 355.376085] cx88[0]: iq 7: 0x18000200 [ write sol count=512 ]
[ 355.376090] cx88[0]: iq 8: 0x33fece00 [ arg #1 ]
[ 355.376093] cx88[0]: iq 9: 0x14000580 [ write eol count=1408 ]
[ 355.376098] cx88[0]: iq a: 0x33fed000 [ arg #1 ]
[ 355.376100] cx88[0]: iq b: 0x18000300 [ write sol count=768 ]
[ 355.376105] cx88[0]: iq c: 0x33fedd00 [ arg #1 ]
[ 355.376108] cx88[0]: iq d: 0x33fede00 [ INVALID irq2 irq1 23 22 21
20 19 18 cnt1 resync 14 12 count=3584 ]
[ 355.376117] cx88[0]: iq e: 0x14000400 [ write eol count=1024 ]
[ 355.376122] cx88[0]: iq f: 0x33fec000 [ arg #1 ]
[ 355.376124] cx88[0]: fifo: 0x00180c00 -> 0x183400
[ 355.376125] cx88[0]: ctrl: 0x00180400 -> 0x180460
[ 355.376128] cx88[0]: ptr1_reg: 0x00182e48
[ 355.376131] cx88[0]: ptr2_reg: 0x00180488
[ 355.376133] cx88[0]: cnt1_reg: 0x000000a0
[ 355.376136] cx88[0]: cnt2_reg: 0x00000000
[ 355.376142] cx88[0]/0: [f39c43c0/0] timeout - dma=0x33ca6000
[ 361.232005] cx88[0]: video y / packed - dma channel status dump
[ 361.232009] cx88[0]: cmds: initial risc: 0x33852000
[ 361.232012] cx88[0]: cmds: cdt base : 0x00180440
[ 361.232015] cx88[0]: cmds: cdt size : 0x0000000a
[ 361.232018] cx88[0]: cmds: iq base : 0x00180400
[ 361.232021] cx88[0]: cmds: iq size : 0x00000010
[ 361.232024] cx88[0]: cmds: risc pc : 0x33852034
[ 361.232027] cx88[0]: cmds: iq wr ptr : 0x0000010d
[ 361.232030] cx88[0]: cmds: iq rd ptr : 0x00000101
[ 361.232033] cx88[0]: cmds: cdt current : 0x00000468
[ 361.232036] cx88[0]: cmds: pci target : 0x00000000
[ 361.232039] cx88[0]: cmds: line / byte : 0x00000000
[ 361.232041] cx88[0]: risc0: 0x80008000 [ sync resync count=0 ]
[ 361.232046] cx88[0]: risc1: 0x1c000780 [ write sol eol count=1920 ]
[ 361.232051] cx88[0]: risc2: 0x33d77000 [ arg #1 ]
[ 361.232055] cx88[0]: risc3: 0x18000100 [ write sol count=256 ]
[ 361.232059] cx88[0]: iq 0: 0x80008000 [ sync resync count=0 ]
[ 361.232064] cx88[0]: iq 1: 0x1c000780 [ write sol eol count=1920 ]
[ 361.232069] cx88[0]: iq 2: 0x33d77000 [ arg #1 ]
[ 361.232072] cx88[0]: iq 3: 0x18000100 [ write sol count=256 ]
[ 361.232077] cx88[0]: iq 4: 0x33d77f00 [ arg #1 ]
[ 361.232079] cx88[0]: iq 5: 0x14000680 [ write eol count=1664 ]
[ 361.232084] cx88[0]: iq 6: 0x34e1d000 [ arg #1 ]
[ 361.232087] cx88[0]: iq 7: 0x18000200 [ write sol count=512 ]
[ 361.232092] cx88[0]: iq 8: 0x34e1de00 [ arg #1 ]
[ 361.232094] cx88[0]: iq 9: 0x14000580 [ write eol count=1408 ]
[ 361.232099] cx88[0]: iq a: 0x338cc000 [ arg #1 ]
[ 361.232102] cx88[0]: iq b: 0x18000300 [ write sol count=768 ]
[ 361.232107] cx88[0]: iq c: 0x338ccd00 [ arg #1 ]
[ 361.232109] cx88[0]: iq d: 0x338cce00 [ INVALID irq2 irq1 23 19 18
resync 14 count=3584 ]
[ 361.232116] cx88[0]: iq e: 0x14000400 [ write eol count=1024 ]
[ 361.232121] cx88[0]: iq f: 0x34e1d000 [ arg #1 ]
[ 361.232123] cx88[0]: fifo: 0x00180c00 -> 0x183400
[ 361.232125] cx88[0]: ctrl: 0x00180400 -> 0x180460
[ 361.232128] cx88[0]: ptr1_reg: 0x001828c0
[ 361.232130] cx88[0]: ptr2_reg: 0x00180478
[ 361.232133] cx88[0]: cnt1_reg: 0x000000df
[ 361.232135] cx88[0]: cnt2_reg: 0x00000000
[ 361.232142] cx88[0]/0: [f39c4000/0] timeout - dma=0x33852000
[ 373.269879] cx88[0]/0: tvaudio support needs work for this tv norm
[NTSC-443], sorry
[ 373.768005] cx88[0]: video y / packed - dma channel status dump
[ 373.768010] cx88[0]: cmds: initial risc: 0x34e11000
[ 373.768013] cx88[0]: cmds: cdt base : 0x00180440
[ 373.768016] cx88[0]: cmds: cdt size : 0x0000000c
[ 373.768019] cx88[0]: cmds: iq base : 0x00180400
[ 373.768022] cx88[0]: cmds: iq size : 0x00000010
[ 373.768025] cx88[0]: cmds: risc pc : 0x34e11034
[ 373.768027] cx88[0]: cmds: iq wr ptr : 0x0000010d
[ 373.768030] cx88[0]: cmds: iq rd ptr : 0x00000101
[ 373.768033] cx88[0]: cmds: cdt current : 0x00000468
[ 373.768036] cx88[0]: cmds: pci target : 0x00000000
[ 373.768039] cx88[0]: cmds: line / byte : 0x00000000
[ 373.768042] cx88[0]: risc0: 0x80008000 [ sync resync count=0 ]
[ 373.768046] cx88[0]: risc1: 0x1c000300 [ write sol eol count=768 ]
[ 373.768051] cx88[0]: risc2: 0x33899000 [ arg #1 ]
[ 373.768055] cx88[0]: risc3: 0x1c000300 [ write sol eol count=768 ]
[ 373.768060] cx88[0]: iq 0: 0x80008000 [ sync resync count=0 ]
[ 373.768064] cx88[0]: iq 1: 0x1c000300 [ write sol eol count=768 ]
[ 373.768069] cx88[0]: iq 2: 0x33899000 [ arg #1 ]
[ 373.768072] cx88[0]: iq 3: 0x1c000300 [ write sol eol count=768 ]
[ 373.768077] cx88[0]: iq 4: 0x33899600 [ arg #1 ]
[ 373.768080] cx88[0]: iq 5: 0x1c000300 [ write sol eol count=768 ]
[ 373.768085] cx88[0]: iq 6: 0x33899c00 [ arg #1 ]
[ 373.768088] cx88[0]: iq 7: 0x1c000300 [ write sol eol count=768 ]
[ 373.768093] cx88[0]: iq 8: 0x3397c200 [ arg #1 ]
[ 373.768096] cx88[0]: iq 9: 0x1c000300 [ write sol eol count=768 ]
[ 373.768101] cx88[0]: iq a: 0x3397c800 [ arg #1 ]
[ 373.768104] cx88[0]: iq b: 0x18000200 [ write sol count=512 ]
[ 373.768109] cx88[0]: iq c: 0x3397ce00 [ arg #1 ]
[ 373.768112] cx88[0]: iq d: 0x33d82e00 [ INVALID irq2 irq1 23 22 20
19 13 count=3584 ]
[ 373.768119] cx88[0]: iq e: 0x14000400 [ write eol count=1024 ]
[ 373.768124] cx88[0]: iq f: 0x3397c000 [ arg #1 ]
[ 373.768125] cx88[0]: fifo: 0x00180c00 -> 0x183400
[ 373.768127] cx88[0]: ctrl: 0x00180400 -> 0x180460
[ 373.768130] cx88[0]: ptr1_reg: 0x00181800
[ 373.768133] cx88[0]: ptr2_reg: 0x00180488
[ 373.768135] cx88[0]: cnt1_reg: 0x00000000
[ 373.768138] cx88[0]: cnt2_reg: 0x00000000
[ 373.768144] cx88[0]/0: [f39c4c00/0] timeout - dma=0x34e11000
[ 373.768147] cx88[0]/0: [f39c43c0/1] timeout - dma=0x34e9b000
I noticed screen capture/shot failed (no wonder I couldn't file the
files) when I ran xawtv from a terminal:
$ cat xawtv.txt
$ xawtv
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
Warning: Cannot convert string
"-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*" to type FontStruct
ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0
[];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
Input/output error
scroll by 122 length 150 shown 0.000000 top 0.498039 => 0.660706
v4l2: read: Input/output error
v4l2: read: Input/output error
ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0
[];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
Input/output error
v412 lines were from my screen capturing attempts.
> If it works, the device /dev/video should then appear, and
> xawtv will not complain about the non-existent interface device
> not being present.
Yeah, no complaints this time.
> PS when I said do a modprobe -r of all the loaded v4l2 modules,
> v4l2 is the generic term Video For Linux Version 2 modules, which
> in your case are all of the cx88* modules and maybe the tuner module
> as well. In your lsmod output you also see the lower layer
> v4l2_common and v4l1_compat modules which are used by the cx88* modules.
Ah, it did tell me I couldn't remove it because of my cx88 so I guess we
can't do that unless I did it wrong. FYI with xawtv not complaining:
$ lsmod
tuner_simple 9694 1
tuner_types 7537 1 tuner_simple
snd_hda_codec_realtek 163282 1
tea5767 4529 0
tuner 14428 1
snd_hda_intel 16787 1
snd_hda_codec 46002 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 4054 1 snd_hda_codec
snd_pcm_oss 28671 0
snd_mixer_oss 10461 1 snd_pcm_oss
snd_pcm 47222 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_midi 3576 0
snd_rawmidi 12513 1 snd_seq_midi
snd_seq_midi_event 3684 1 snd_seq_midi
snd_seq 35463 2 snd_seq_midi,snd_seq_midi_event
cx8800 20155 0
snd_timer 12258 2 snd_pcm,snd_seq
cx88xx 59092 1 cx8800
snd_seq_device 3673 3 snd_seq_midi,snd_rawmidi,snd_seq
ir_common 22187 1 cx88xx
i2c_algo_bit 3497 1 cx88xx
tveeprom 9393 1 cx88xx
v4l2_common 9820 3 tuner,cx8800,cx88xx
videodev 25545 4 tuner,cx8800,cx88xx,v4l2_common
v4l1_compat 10250 1 videodev
videobuf_dma_sg 7203 2 cx8800,cx88xx
videobuf_core 10476 3 cx8800,cx88xx,videobuf_dma_sg
snd 34375 13
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 3450 1 snd
psmouse 44657 0
btcx_risc 2499 2 cx8800,cx88xx
nvidia 9222163 38
i2c_i801 6462 0
i2c_core 12696 12
adt7473,tuner_simple,tea5767,tuner,cx8800,cx88xx,i2c_algo_bit,tveeprom,v4l2_common,videodev,nvidia,i2c_i801
snd_page_alloc 5045 2 snd_hda_intel,snd_pcm
evdev 5609 7
serio_raw 2916 0
pcspkr 1207 0
processor 26327 1 acpi_cpufreq
button 3598 0
ext3 94204 9
jbd 32169 1 ext3
mbcache 3762 1 ext3
sg 15968 0
sd_mod 25969 12
crc_t10dif 1012 1 sd_mod
sr_mod 10770 0
cdrom 26487 1 sr_mod
usbhid 28008 2
hid 50873 1 usbhid
ata_generic 2067 0
uhci_hcd 16057 0
pata_jmicron 1452 11
ahci 27270 0
e100 22317 0
thermal 9206 0
floppy 40923 0
ata_piix 17736 0
r8169 24860 0
mii 2714 2 e100,r8169
ehci_hcd 27851 0
libata 115753 4 ata_generic,pata_jmicron,ahci,ata_piix
scsi_mod 101421 4 sg,sd_mod,sr_mod,libata
thermal_sys 9378 2 processor,thermal
usbcore 98453 6 usbhid,uhci_hcd,ehci_hcd
nls_base 4541 1 usbcore
> It is also possible that you may need to add a tuner type option,
> as well as adding some options to cx8800 itself.
>
> See<http://www.linuxquestions.ORG/questions/slackware-14/problem-in-installing-tv-tuner-chipset-cx88xx-449575/>
>
> QUOTE
> options cx8800 video_nr=0 radio_nr=0
> options cx88xx card=27 tuner=44
> UNQUOTE
>
> NB The card number is different to 12 because it is for a different cx88 chip based card
> (PixelView Ultra Pro)
Hmm, I can try it. So in my /etc/modprobe.d/cx8800.conf, I have:
# ASUS TV Tuner Card 880 NTSC (cx23880)
options cx88xx card=12 tuner=44
Let me know before I attempt it in case I mess up. :D
--
"Don't be no Ant-Man. An Ant-Man has very low horizons." --Forrest Gump
J G Miller
> So in my /etc/modprobe.d/cx8800.conf, I have: # ASUS
> TV Tuner Card 880 NTSC (cx23880)
>
> options cx88xx card=12 tuner=44
Leave out the tuner=44 for the time being. The 44 may only be
the correct tuner number for the PixelView Ultra Pro card.
Ant
>> So in my /etc/modprobe.d/cx8800.conf, I have: # ASUS
>> TV Tuner Card 880 NTSC (cx23880)
>>
>> options cx88xx card=12 tuner=44
>
> Leave out the tuner=44 for the time being. The 44 may only be
> the correct tuner number for the PixelView Ultra Pro card.
OK. So, now what do I do with /etc/modprobe.d/cx8800.conf that didn't
work last night? It currently shows:
# ASUS TV Tuner Card 880 NTSC (cx23880)
options cx88xx card=12
Did you want me to add "options cx8800 video_nr=0 radio_nr=0 "
line to it too?
BTW, Merry Christmas if you celebrate it. :)
--
"Not to engage in the pursuit of ideas is to live like ants instead of
men." --Mortimer J. Adler
J G Miller
> So, now what do I do with /etc/modprobe.d/cx8800.conf that didn't
> work last night? It currently shows:
>
> # ASUS TV Tuner Card 880 NTSC (cx23880)
>
> options cx88xx card=12
For the time being delete.
> Did you want me to add "options cx8800 video_nr=0 radio_nr=0 "
> line to it too?
These parameters would replace the card=12 parameter since the card
parameter as you are now well aware is not valid for the cx8800 module.
It may be appropriate to have these parameters for your card if there
is no video and no radio, but it is best to just try and get the
cx88xx configuration working first. Then once that works, you can
then try adding these options and see if it continues to work.
> BTW, Merry Christmas if you celebrate it. :)
Thanks for the greetings, but ss Oliver Cromwell is said to have remarked
"nowhere has God called upon mankind to celebrate Christ’s nativity in this way."
Ant
> On Sat, 25 Dec 2010 06:51:01 -0800, Ant wrote:
> > So, now what do I do with /etc/modprobe.d/cx8800.conf that didn't
> > work last night? It currently shows:
> >
> > # ASUS TV Tuner Card 880 NTSC (cx23880)
> >
> > options cx88xx card=12
> For the time being delete.
OK I will add # before that line so we know we tried it already.
>
> > Did you want me to add "options cx8800 video_nr=0 radio_nr=0 "
> > line to it too?
> These parameters would replace the card=12 parameter since the card
> parameter as you are now well aware is not valid for the cx8800 module.
> It may be appropriate to have these parameters for your card if there
> is no video and no radio, but it is best to just try and get the
> cx88xx configuration working first. Then once that works, you can
> then try adding these options and see if it continues to work.
OK, I added that line so it now looks like:
# cat /etc/modprobe.d/cx8800.conf
# ASUS TV Tuner Card 880 NTSC (cx23880)
#options cx88xx card=12
options cx8800 video_nr=0 radio_nr=0
I reran "modprobe -a cx8800" and it showed nothing. dmesg showed nothing
new as well.
xawtv results looked the same to me:
$ xawtv
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
Warning: Cannot convert string
"-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*" to type FontStruct
ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0
[];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
Input/output error
Same for dmesg after I exited it:
...
[46557.401505] cx88[0]: video y / packed - dma channel status dump
[46557.401510] cx88[0]: cmds: initial risc: 0x06ef6000
[46557.401513] cx88[0]: cmds: cdt base : 0x00180440
[46557.401516] cx88[0]: cmds: cdt size : 0x0000000c
[46557.401519] cx88[0]: cmds: iq base : 0x00180400
[46557.401522] cx88[0]: cmds: iq size : 0x00000010
[46557.401525] cx88[0]: cmds: risc pc : 0x06ced6f0
[46557.401531] cx88[0]: cmds: iq wr ptr : 0x0000010f
[46557.401534] cx88[0]: cmds: iq rd ptr : 0x00000105
[46557.401537] cx88[0]: cmds: cdt current : 0x00000468
[46557.401540] cx88[0]: cmds: pci target : 0x06cc9000
[46557.401543] cx88[0]: cmds: line / byte : 0x02300000
[46557.401546] cx88[0]: risc0: 0x1c000300 [ write sol eol count=768 ]
[46557.401551] cx88[0]: risc1: 0x06cc9300 [ arg #1 ]
[46557.401555] cx88[0]: risc2: 0x1c000300 [ write sol eol count=768 ]
[46557.401560] cx88[0]: risc3: 0x06cc9900 [ arg #1 ]
[46557.401563] cx88[0]: iq 0: 0x06ccab00 [ INVALID eol irq2 23 22 19
18 resync 13 count=2816 ]
[46557.401571] cx88[0]: iq 1: 0x1c000300 [ write sol eol count=768 ]
[46557.401576] cx88[0]: iq 2: 0x06ccb100 [ arg #1 ]
[46557.401579] cx88[0]: iq 3: 0x1c000300 [ write sol eol count=768 ]
[46557.401584] cx88[0]: iq 4: 0x06cc8d00 [ arg #1 ]
[46557.401587] cx88[0]: iq 5: 0x1c000300 [ write sol eol count=768 ]
[46557.401592] cx88[0]: iq 6: 0x06cc9300 [ arg #1 ]
[46557.401595] cx88[0]: iq 7: 0x1c000300 [ write sol eol count=768 ]
[46557.401600] cx88[0]: iq 8: 0x06cc9900 [ arg #1 ]
[46557.401603] cx88[0]: iq 9: 0x18000100 [ write sol count=256 ]
[46557.401608] cx88[0]: iq a: 0x06cc9f00 [ arg #1 ]
[46557.401610] cx88[0]: iq b: 0x14000200 [ write eol count=512 ]
[46557.401615] cx88[0]: iq c: 0x06cca000 [ arg #1 ]
[46557.401618] cx88[0]: iq d: 0x1c000300 [ write sol eol count=768 ]
[46557.401623] cx88[0]: iq e: 0x06cca500 [ arg #1 ]
[46557.401626] cx88[0]: iq f: 0x1c000300 [ write sol eol count=768 ]
[46557.401631] cx88[0]: iq 10: 0x00180c00 [ arg #1 ]
[46557.401633] cx88[0]: fifo: 0x00180c00 -> 0x183400
[46557.401635] cx88[0]: ctrl: 0x00180400 -> 0x180460
[46557.401642] cx88[0]: ptr1_reg: 0x00181500
[46557.401645] cx88[0]: ptr2_reg: 0x00180478
[46557.401647] cx88[0]: cnt1_reg: 0x00000004
[46557.401650] cx88[0]: cnt2_reg: 0x00000000
[46557.401657] cx88[0]/0: [f5681e40/1] timeout - dma=0x06ced000
[46557.401659] cx88[0]/0: [f5681180/0] timeout - dma=0x06ef6000
:( Unless I forgot something? I did not reboot.
> > BTW, Merry Christmas if you celebrate it. :)
> Thanks for the greetings, but ss Oliver Cromwell is said to have remarked
> "nowhere has God called upon mankind to celebrate Christ???s nativity in this way."
:)
--
Merry Christmas/Happy Holidays/Season's Greetings! :)
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.
J G Miller
> In comp.os.linux.setup J G Miller <mil...@yoyo.org> wrote:
>> On Sat, 25 Dec 2010 06:51:01 -0800, Ant wrote:
>
>> > So, now what do I do with /etc/modprobe.d/cx8800.conf that didn't
>> > work last night? It currently shows:
>> >
>> > # ASUS TV Tuner Card 880 NTSC (cx23880)
>> >
>> > options cx88xx card=12
>
>> For the time being delete.
>
> OK I will add # before that line so we know we tried it already.
Sorry I misread that - I was still thinking because of the file name
that you still had the line options cx8800, because you had not changed
the name of the file to xc88xx to reflect the
fact that its contents had been changed from
options cx8000 card=12
to
options cx88xx card=12
You definitely need a file containing
options cx88xx card=<appropriate_number>
in order for the cx88* modules to be correctly configured for
your card, possibly with a tuner=<appropriate_number> added as well.
> I reran "modprobe -a cx8800" and it showed nothing. dmesg showed nothing
> new as well.
Because you did not unload the already loaded cx* modules.
If they are already loaded then they will not re-load because you
have changed the modprobe configuration file, and thus dmesg will
not show any change.
As for
options cx8800 video_nr=0 radio_nr=0
you should only try this *once* the options cx88xx card=<number>
has been tried and found to work correctly.
Seeing as you are probably goind to put options for bot cx8800
and cx88xx in the same file, I suggest you rename it from
cx8000.conf to v4l2.conf so it is clear that it contains
options not just for a single module.
Sorry for any confusion ...
Ant
>>>> So, now what do I do with /etc/modprobe.d/cx8800.conf that didn't
>>>> work last night? It currently shows:
>>>>
>>>> # ASUS TV Tuner Card 880 NTSC (cx23880)
>>>>
>>>> options cx88xx card=12
>>
>>> For the time being delete.
>>
>> OK I will add # before that line so we know we tried it already.
>
> Sorry I misread that - I was still thinking because of the file name
> that you still had the line options cx8800, because you had not changed
> the name of the file to xc88xx to reflect the
> fact that its contents had been changed from
>
> options cx8000 card=12
>
> to
>
> options cx88xx card=12
>
> You definitely need a file containing
>
> options cx88xx card=<appropriate_number>
>
> in order for the cx88* modules to be correctly configured for
> your card, possibly with a tuner=<appropriate_number> added as well.
>
>> I reran "modprobe -a cx8800" and it showed nothing. dmesg showed nothing
>> new as well.
>
> Because you did not unload the already loaded cx* modules.
Ah.
> If they are already loaded then they will not re-load because you
> have changed the modprobe configuration file, and thus dmesg will
> not show any change.
>
> As for
>
> options cx8800 video_nr=0 radio_nr=0
>
> you should only try this *once* the options cx88xx card=<number>
> has been tried and found to work correctly.
OK.
> Seeing as you are probably goind to put options for bot cx8800
> and cx88xx in the same file, I suggest you rename it from
> cx8000.conf to v4l2.conf so it is clear that it contains
> options not just for a single module.
>
> Sorry for any confusion ...
Ha, no worries. I am also getting confused with this since I am new at
this. :( Let's see if I got this right from your comments:
I renamed the .conf to v412.conf in /etc/modprobe.d to avoid confusions.
Its contents now shows:
# ASUS TV Tuner Card 880 NTSC (cx23880)
options cx88xx card=12
options cx8800 video_nr=0 radio_nr=0
I decided to reboot instead of doing removing modules since I want this
to work on reboots. The results looked similar/the same as before (full
dmesg is at http://pastie.org/1405833 up to xawtv's manual exit/quit
with its static video screen):
...
[ 7.416211] Linux video capture interface: v2.00
[ 7.501558] cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
[ 7.501593] cx8800 0000:01:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 7.501989] cx88[0]: subsystem: 1043:4820, board: ASUS PVR-416
[card=12,insmod option], frontend(s): 0
[ 7.501992] cx88[0]: TV tuner type 43, Radio tuner type -1
...
[ 8.185575] tuner 1-0060: chip found @ 0xc0 (cx88[0])
[ 8.254057] tuner-simple 1-0060: creating new instance
[ 8.254060] tuner-simple 1-0060: type set to 43 (Philips NTSC MK3
(FM1236MK3 or FM1236/F))
[ 8.254850] cx88[0]/0: found at 0000:01:00.0, rev: 3, irq: 16,
latency: 64, mmio: 0xf8000000
...
[ 8.254907] cx88[0]/0: registered device video0 [v4l2]
[ 8.254927] cx88[0]/0: registered device vbi0
[ 8.254945] cx88[0]/0: registered device radio0
...
Sorry for the late reply/response. I was busy with Christmas events. ;)
--
"I used to command a battalion of German ants." --Tom
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
J G Miller
> I am also getting confused with this since I am new at
> this.
The confusion arises because of all the modules named cx<something> ;)
> I renamed the .conf to v412.conf in /etc/modprobe.d to avoid confusions.
> Its contents now shows:
>
> # ASUS TV Tuner Card 880 NTSC (cx23880)
>
> options cx88xx card=12
> options cx8800 video_nr=0 radio_nr=0
Great! That is exactly what is needed except as I kept repeating
you should have waited with the cx8800 line until you knew the
cx88xx line worked.
> I decided to reboot instead of doing removing modules since I want this
> to work on reboots.
That is fine. When things get confused with which modules are loaded
and which are not, a reboot will always get things back to an even keel.
> The results looked similar/the same as before (full
> dmesg is at http://pastie.org/1405833 up to xawtv's manual exit/quit
> with its static video screen)
Okay, that may be a different issue.
> [ 7.416211] Linux video capture interface: v2.00 [ 7.501558]
> cx88/0: cx2388x v4l2 driver version 0.0.7 loaded [ 7.501593] cx8800
> 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [ 7.501989] cx88[0]: subsystem: 1043:4820, board: ASUS PVR-416
> [card=12,insmod option], frontend(s): 0 [ 7.501992] cx88[0]: TV tuner
> type 43, Radio tuner type -1 ...
> [ 8.185575] tuner 1-0060: chip found @ 0xc0 (cx88[0]) [ 8.254057]
> tuner-simple 1-0060: creating new instance [ 8.254060] tuner-simple
> 1-0060: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F))
> [ 8.254850] cx88[0]/0: found at 0000:01:00.0, rev: 3, irq: 16,
> latency: 64, mmio: 0xf8000000
> ...
> [ 8.254907] cx88[0]/0: registered device video0 [v4l2] [ 8.254927]
> cx88[0]/0: registered device vbi0 [ 8.254945] cx88[0]/0: registered
> device radio0 ...
Now here in dmesg we see what we were hoping to see --
the hardware has been found, the appropriate modules have received the
configuration information and the interface device files including
/dev/video0 (the all important one for xawtv) has been created.
Now to tidy this up, a couple of important questions
1) Does your card have a radio tuner?
In the above dmesg, a /dev/radio0 has been created even though radio_nr=0
has been set.
2) Does your card have a video input?
In the above dmesg, a /dev/vbi0 has been created even though video_nr=0
has been set.
3) And the all important question -- do you know what type of tuner
your card has? Is Philips NTSC MK3 (FM1236MK3 or FM1236/F
the correct tuner type?
The module is automagically using tuner=43 --
"tuner-simple 1-0060: type set to 43"
If this is not correct, then the tuner=<someothernumber>
will have to be set in the v4l2.conf file.
Ant
> On Saturday, December 25th, 2010 at 18:42:05h -0800, Ant explained:
>
>> I am also getting confused with this since I am new at
>> this.
>
> The confusion arises because of all the modules named cx<something> ;)
Heh. Yeah, that doesn't help either. :(
>> I renamed the .conf to v412.conf in /etc/modprobe.d to avoid confusions.
>> Its contents now shows:
>>
>> # ASUS TV Tuner Card 880 NTSC (cx23880)
>>
>> options cx88xx card=12
>> options cx8800 video_nr=0 radio_nr=0
>
> Great! That is exactly what is needed except as I kept repeating
> you should have waited with the cx8800 line until you knew the
> cx88xx line worked.
>
>> I decided to reboot instead of doing removing modules since I want this
>> to work on reboots.
>
> That is fine. When things get confused with which modules are loaded
> and which are not, a reboot will always get things back to an even keel.
>
>> The results looked similar/the same as before (full
>> dmesg is at http://pastie.org/1405833 up to xawtv's manual exit/quit
>> with its static video screen)
>
> Okay, that may be a different issue.
OK. Hopefully, easy to fix. It worked fine in old, updated Windows XP
Pro. SP3 with PowerVCR II in the past (several weeks ago).
>> [ 7.416211] Linux video capture interface: v2.00 [ 7.501558]
>> cx88/0: cx2388x v4l2 driver version 0.0.7 loaded [ 7.501593] cx8800
>> 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>> [ 7.501989] cx88[0]: subsystem: 1043:4820, board: ASUS PVR-416
>> [card=12,insmod option], frontend(s): 0 [ 7.501992] cx88[0]: TV tuner
>> type 43, Radio tuner type -1 ...
>> [ 8.185575] tuner 1-0060: chip found @ 0xc0 (cx88[0]) [ 8.254057]
>> tuner-simple 1-0060: creating new instance [ 8.254060] tuner-simple
>> 1-0060: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F))
>> [ 8.254850] cx88[0]/0: found at 0000:01:00.0, rev: 3, irq: 16,
>> latency: 64, mmio: 0xf8000000
>> ...
>> [ 8.254907] cx88[0]/0: registered device video0 [v4l2] [ 8.254927]
>> cx88[0]/0: registered device vbi0 [ 8.254945] cx88[0]/0: registered
>> device radio0 ...
>
> Now here in dmesg we see what we were hoping to see --
> the hardware has been found, the appropriate modules have received the
> configuration information and the interface device files including
> /dev/video0 (the all important one for xawtv) has been created.
Awesome. :)
> Now to tidy this up, a couple of important questions
>
> 1) Does your card have a radio tuner?
Um, I have no idea! Even if it did, I don't use it. Is that
important/required? I just want video and audio from this card.
Basically, I want to use it as a SD (obviously) video capture card. ;)
> In the above dmesg, a /dev/radio0 has been created even though radio_nr=0
> has been set.
>
> 2) Does your card have a video input?
Yes, currently from the VCR that is hooked up to a DTV Pal converter box
and TV. I believe it uses composite cables. I am not using its coax
cable since I don't watch TV on it (why bother since I have HDTV tuner
cards ;)).
> In the above dmesg, a /dev/vbi0 has been created even though video_nr=0
> has been set.
>
> 3) And the all important question -- do you know what type of tuner
> your card has? Is Philips NTSC MK3 (FM1236MK3 or FM1236/F
> the correct tuner type?
I have no idea. :( I don't have the manuals if it came with one. The
driver CD doesn't have any PDFs for its manual.
However, I did some digging like an ant since I have all the old
original CD-ROMs and remote control that came with this card so I assume
this is correct.
Maybe these three drivers' *.inf will give us more clues about the drivers:
cx88tune.inf -- http://pastie.org/1406941 (mentions Philips and FI1236
NTSC [I am in USA so NTSC and not PAL]). It matches what you said.
cx88vid.inf -- http://pastie.org/1406936 (mentions Philips)
cx88xbar.inf -- http://pastie.org/1406938
> The module is automagically using tuner=43 --
>
> "tuner-simple 1-0060: type set to 43"
>
> If this is not correct, then the tuner=<someothernumber>
> will have to be set in the v4l2.conf file.
I think that detection was correct based on the above Windows drivers'
INF files.
OK, now what? :)
--
"I do not believe that the Great Society is the ordered, changeless and
sterile battalion of the ants. It is the excitement of becoming--always
becoming, trying, probing, falling, resting and trying again--but always
trying and always gaining. In each generation--with toil and tears--we
have had to earn our heritage again." --Lyndon B. Johnson
J G Miller
> Um, I have no idea! Even if it did, I don't use it. Is that
> important/required?
It is just useful to know, since why is a /dev/radio0 being created,
especially as you have radio_nr=0 in the configuration file.
Okay a further web search reveals that I misunderstood the parameter --
it is radio_*nr*=0
I was thiking that this was telling the module that there was no radio,
but the nr means number, so it means, create the radio interface device
as (nr) *number* 0, hence /dev/radio0
Since as far as I can tell you do not have an FM radio tuner on your card,
you should *remove* this parameter from the modprobe.d configuration file.
A quick easy check you could do, is to look on the card and see how many
antenna input sockets are on the card.
Also, does it have a socket for an IR device?
As you say you do not have the user manual, you may want to download a
copy in PDF form from
<http://support.asus.COM/download/Download.aspx?SLanguage=en-us>
> Yes, currently from the VCR that is hooked up to a DTV Pal converter box
> and TV.
That is fine, and as explained above the interface /dev/video0 and
/dev/vbi0 are in fact correctly being created.
> I believe it uses composite cables.
With an S-VHS type connector?
> However, I did some digging like an ant since I have all the old
> original CD-ROMs and remote control that came with this card so I assume
> this is correct.
From that, it does look like the cx88 module is correctly auto-detecting the
type of tuner in the card, so trying to use a tuner=<tuner_number>
parameter appears to be unecessary.
> OK, now what? :)
So after reviewing and implementing the change I suggested above,
the error with xawtv needs to be addressed, which I think from your previous
message was specifically
X Error of failed request: XF86DGANoDirectVideoMode
What graphics card are you using, and do you have your DISPLAY set to
the local display?
From <http://ubuntuforums.ORG/showthread.php?t=334508>
you should try running
xawtv -nodga -device /dev/video0
From <http://us.download.nvidia.COM/XFree86/Linux-x86/169.04/README/chapter-07.html#id2546686>
QUOTE
Why do applications that use DGA graphics fail?
The NVIDIA driver does not support the graphics component of the XFree86-DGA
(Direct Graphics Access) extension. Applications can use the XDGASelectInput()
function to acquire relative pointer motion, but graphics-related functions
such as XDGASetMode() and XDGAOpenFramebuffer() will fail.
The graphics component of XFree86-DGA is not supported because it requires a
CPU mapping of framebuffer memory. As graphics cards ship with increasing
quantities of video memory, the NVIDIA X driver has had to switch to a more
dynamic memory mapping scheme that is incompatible with DGA. Furthermore, DGA
does not cooperate with other graphics rendering libraries such as Xlib and
OpenGL because it accesses GPU resources directly.
NVIDIA recommends that applications use OpenGL or Xlib, rather than DGA,
for graphics rendering. Using rendering libraries other than DGA will yield
better performance and improve interoperability with other X applications.
UNQUOTE
Note that this explanation is for XFree86 not Xorg, but this will apply to
the Xorg server as well in fact.
Ant
>> Um, I have no idea! Even if it did, I don't use it. Is that
>> important/required?
>
> It is just useful to know, since why is a /dev/radio0 being created,
> especially as you have radio_nr=0 in the configuration file.
>
> Okay a further web search reveals that I misunderstood the parameter --
> it is radio_*nr*=0
>
> I was thiking that this was telling the module that there was no radio,
> but the nr means number, so it means, create the radio interface device
> as (nr) *number* 0, hence /dev/radio0
>
> Since as far as I can tell you do not have an FM radio tuner on your card,
> you should *remove* this parameter from the modprobe.d configuration file.
OK, I removed the parameter so /etc/modprobe.d/v412.conf now looks like:
# ASUS TV Tuner Card 880 NTSC (cx23880)
options cx88xx card=12
options cx8800 video_nr=0
I will reboot for this.
> A quick easy check you could do, is to look on the card and see how many
> antenna input sockets are on the card.
Just two: one coax input (middle and unused) and AV input with its ASUS
AV adapter connected to the old VCR (connected to the CRT TV). See
http://www.overclockers.com.au/article.php?id=112645 for the images and
other details. I am missing that yellow CD (XP?) in
http://www.overclockers.com.au/image.php?pic=articles/112645/cd.jpg, but
it looks useless. FYI, audio out is connected to my motherboard's
onboard sound as well.
> Also, does it have a socket for an IR device?
No, but it uses an USB connection for that for its ASUS remote control.
See
http://www.overclockers.com.au/image.php?pic=articles/112645/remote.jpg
for a photograph/photo. I have never used it before and have no plan to
use it as well. :)
> As you say you do not have the user manual, you may want to download a
> copy in PDF form from
>
> <http://support.asus.COM/download/Download.aspx?SLanguage=en-us>
I can't seem to find it through its search and pulldown menus
(peripherals & accessories, components, etc.). See if you can find it.
If you can find it, then please kindly list how you got there. It seems
like this TV tuner card was not popular at all hence the difficulities
we're having. :(
>> Yes, currently from the VCR that is hooked up to a DTV Pal converter box
>> and TV.
>
> That is fine, and as explained above the interface /dev/video0 and
> /dev/vbi0 are in fact correctly being created.
>
>> I believe it uses composite cables.
>
> With an S-VHS type connector?
Uhh, I am not sure. All I remember was seeing red, yellow labeled
cables. Too many darn cables and connectors! :(
>> However, I did some digging like an ant since I have all the old
>> original CD-ROMs and remote control that came with this card so I assume
>> this is correct.
>
> From that, it does look like the cx88 module is correctly auto-detecting the
> type of tuner in the card, so trying to use a tuner=<tuner_number>
> parameter appears to be unecessary.
>
>> OK, now what? :)
>
> So after reviewing and implementing the change I suggested above,
> the error with xawtv needs to be addressed, which I think from your previous
> message was specifically
>
> X Error of failed request: XF86DGANoDirectVideoMode
>
> What graphics card are you using, and do you have your DISPLAY set to
> the local display?
I am using a NVIDIA GeForce 8800 GT video card (PCIe, 512 MB of RAM,
latest binary drivers from NVIDIA.com). Also, using Compiz (don't think
that should cause this error?
What did you mean by "DISPLAY set to the local display?" Is that
directly to my 19" LCD monitor through its VGA connection with an old
KVM? If so, then yes.
> From<http://ubuntuforums.ORG/showthread.php?t=334508>
> you should try running
>
> xawtv -nodga -device /dev/video0
http://pastie.org/1407230 after the reboot, trying xawtv with Compiz,
exitng X, restarting X (exit to console and then startx command; yeah I
am old school) without Compiz. It looks like the same results.
FYI without Compiz:
$ xawtv
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
Warning: Cannot convert string
"-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*" to type FontStruct
ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0
[];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
Input/output error
$ xawtv -nodga -device /dev/video0
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
Warning: Cannot convert string
"-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*" to type FontStruct
ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0
[];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
Input/output error
Also, dmesg showed a bunch of "cx88[0]" lines but are those bad?
> From<http://us.download.nvidia.COM/XFree86/Linux-x86/169.04/README/chapter-07.html#id2546686>
>
> QUOTE
>
> Why do applications that use DGA graphics fail?
>
> The NVIDIA driver does not support the graphics component of the XFree86-DGA
> (Direct Graphics Access) extension. Applications can use the XDGASelectInput()
> function to acquire relative pointer motion, but graphics-related functions
> such as XDGASetMode() and XDGAOpenFramebuffer() will fail.
>
> The graphics component of XFree86-DGA is not supported because it requires a
> CPU mapping of framebuffer memory. As graphics cards ship with increasing
> quantities of video memory, the NVIDIA X driver has had to switch to a more
> dynamic memory mapping scheme that is incompatible with DGA. Furthermore, DGA
> does not cooperate with other graphics rendering libraries such as Xlib and
> OpenGL because it accesses GPU resources directly.
>
> NVIDIA recommends that applications use OpenGL or Xlib, rather than DGA,
> for graphics rendering. Using rendering libraries other than DGA will yield
> better performance and improve interoperability with other X applications.
>
> UNQUOTE
>
> Note that this explanation is for XFree86 not Xorg, but this will apply to
> the Xorg server as well in fact.
Hmm. Interesting. Is that the problem why I am only getting static? Hmm.
--
"An ant is a wise creature for itself, but it is a shrewd thing in an
orchard or garden." --Francis Bacon
J G Miller
> # ASUS TV Tuner Card 880 NTSC (cx23880)
>
> options cx88xx card=12
> options cx8800 video_nr=0
Looks good! (Apart from being tidy and aligning the parameter columns.)
> No, but it uses an USB connection for that for its ASUS remote control.
It may be possible to get it to work with lirc, which would be useful
if you have no other IR device on your PC.
> I can't seem to find it through its search and pulldown menus
> (peripherals & accessories, components, etc.).
What I thought was the appropriate manual (sadly Asus does
not allow a direct link) is
Select Product --> Multimedia
Select Series --> TV-Tuner
Select Models --> ASUS TV TUNER CARD(NTSC)
[Popup] Operating System: WinXP
Click on [Search] button
Expand menu [+] Manual (15)
Version E2583
Description TV Tuner User's Manual for English Edtion(E2583)
Click on Download from Global(DLM)
Et voila!
> Uhh, I am not sure. All I remember was seeing red, yellow labeled
> cables. Too many darn cables and connectors! :(
From the diagram at
<http://www.overclockers.com.au/image.php?pic=articles/112645/diagram.jpg>
that looks like a custom connector, but the interface box according to the
description on the web page has
Video-in cable box (S-video and composite) for connection to VHS or video camera
So using composite as you are doing will provide the best quality possible
with the card.
> What did you mean by "DISPLAY set to the local display?"
I meant the value of the DISPLAY environmental variable being set to :0.0
and not your_hostname.your_domain:0.0
> $ xawtv -nodga -device /dev/video0
> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686) xinerama
> 0: 1280x1024+0+0
> X Error of failed request: XF86DGANoDirectVideoMode
> Major opcode of failed request: 130 (XFree86-DGA) Minor opcode of
> failed request: 1 (XF86DGAGetVideoLL) Serial number of failed
> request: 15
> Current serial number in output stream: 15
> v4l-conf had some trouble, trying to continue anyway
Still giving the same error, so perhaps you need to manually run v4l-conf with the
all important -nodga option to set up the configuration first before running xawtv.
/usr/bin/v4l-conf is found in the v4l-conf package.
Description: tool to configure video4linux drivers
This package provides a small tool to configure a video4linux
device driver. It is required to make the video
overlay work in fbtv and xawtv.
> Warning: Cannot convert string
> "-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*" to type FontStruct
You need to tell xawtv to use another font ie one you have installed
or install the package tv-fonts which contains
/usr/share/fonts/X11/misc/led-iso10646-1.pcf.gz etc
> Also, dmesg showed a bunch of "cx88[0]" lines but are those bad?
This has already been covered -- you want dmesg to show a bunch of
cx88 lines saying that the video0 and vbi0 device [interface file]
has been set up.
> Is that the problem why I am only getting static? Hmm.
It is the problem why you are getting the fatal error
Ant
> On Sun, 26 Dec 2010 13:42:09 -0800, Ant wrote:
>
>> # ASUS TV Tuner Card 880 NTSC (cx23880)
>>
>> options cx88xx card=12
>> options cx8800 video_nr=0
>
> Looks good! (Apart from being tidy and aligning the parameter columns.)
Haha. :)
>> No, but it uses an USB connection for that for its ASUS remote control.
>
> It may be possible to get it to work with lirc, which would be useful
> if you have no other IR device on your PC.
Yeah, but I never do use them. :)
>> I can't seem to find it through its search and pulldown menus
>> (peripherals& accessories, components, etc.).
>
> What I thought was the appropriate manual (sadly Asus does
> not allow a direct link) is
>
> Select Product --> Multimedia
Ah hah! I didn't try that one. :/
> Select Series --> TV-Tuner
>
> Select Models --> ASUS TV TUNER CARD(NTSC)
>
> [Popup] Operating System: WinXP
>
> Click on [Search] button
>
> Expand menu [+] Manual (15)
>
> Version E2583
> Description TV Tuner User's Manual for English Edtion(E2583)
>
> Click on Download from Global(DLM)
>
> Et voila!
Thanks. :)
>> Uhh, I am not sure. All I remember was seeing red, yellow labeled
>> cables. Too many darn cables and connectors! :(
>
> From the diagram at
>
> <http://www.overclockers.com.au/image.php?pic=articles/112645/diagram.jpg>
>
> that looks like a custom connector, but the interface box according to the
> description on the web page has
>
> Video-in cable box (S-video and composite) for connection to VHS or video camera
>
> So using composite as you are doing will provide the best quality possible
> with the card.
Good. I am not expecting HD quality. :)
>> What did you mean by "DISPLAY set to the local display?"
>
> I meant the value of the DISPLAY environmental variable being set to :0.0
> and not your_hostname.your_domain:0.0
I am not sure how to find that, but maybe this is it?
$ w
17:36:46 up 4:18, 2 users, load average: 0.00, 0.39, 0.80
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
ant tty1 16:35 1:01m 0.05s 0.00s xinit
/etc/X11/xinit/xinitrc -- /etc/X11/xinit/xserverrc :0 -auth
/tmp/serverauth.1
ant pts/0 xp 17:36 0.00s 0.01s 0.00s w
>> $ xawtv -nodga -device /dev/video0
>> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686) xinerama
>> 0: 1280x1024+0+0
>> X Error of failed request: XF86DGANoDirectVideoMode
>> Major opcode of failed request: 130 (XFree86-DGA) Minor opcode of
>> failed request: 1 (XF86DGAGetVideoLL) Serial number of failed
>> request: 15
>> Current serial number in output stream: 15
>> v4l-conf had some trouble, trying to continue anyway
>
> Still giving the same error, so perhaps you need to manually run v4l-conf with the
> all important -nodga option to set up the configuration first before running xawtv.
>
> /usr/bin/v4l-conf is found in the v4l-conf package.
>
> Description: tool to configure video4linux drivers
> This package provides a small tool to configure a video4linux
> device driver. It is required to make the video
> overlay work in fbtv and xawtv.
I already had it installed. :)
$ /usr/bin/v4l-conf
v4l-conf: using X11 display :0.0
dga: version 2.0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
$ /usr/bin/v4l-conf -nodga
/usr/bin/v4l-conf: invalid option -- 'n'
usage: /usr/bin/v4l-conf [ options ]
options:
-q quiet
-d <dpy> X11 Display [:0.0]
-c <dev> video device [/dev/video0]
-b <n> displays color depth is <n> bpp
-s <n> shift display by <n> bytes
-f query frame buffer device for info
-a <addr> set framebuffer address to <addr>
(in hex, root only, successful autodetect
will overwrite this address)
-1 force v4l API
-2 force v4l2 API
>> Warning: Cannot convert string
>> "-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*" to type FontStruct
>
> You need to tell xawtv to use another font ie one you have installed
> or install the package tv-fonts which contains
>
> /usr/share/fonts/X11/misc/led-iso10646-1.pcf.gz etc
Installed, but I still see the errors.
>> Also, dmesg showed a bunch of "cx88[0]" lines but are those bad?
>
> This has already been covered -- you want dmesg to show a bunch of
> cx88 lines saying that the video0 and vbi0 device [interface file]
> has been set up.
OK. They just look scary. :)
>> Is that the problem why I am only getting static? Hmm.
>
> It is the problem why you are getting the fatal error
Hmm.
FYI, I got a screen show/capture of my desktop in action:
http://img64.imageshack.us/img64/3069/screenshotk.gif so you can see
what I see with xawtv.
--
"Maybe it's like an ant hive..." "Bees man, bees have hives." "You know
what I mean. It's like one female that runs the whole show." "Yes, the
queen." "Yeah the mamma. She is bad*ss, man. I mean big." "These things
ain't ants estupido." "I know that." --Aliens movie
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is/was listening to a song on this computer: Annakin - The Trooper
Kevin Snodgrass
> FYI, I got a screen show/capture of my desktop in action:
> http://img64.imageshack.us/img64/3069/screenshotk.gif so you can see
> what I see with xawtv.
I don't use xawtv, I use mplayer. I don't use this video capture card or
it's relatives, I use Hauppauge PVRs. Therefore I don't know how to
accomplish many things with your setup. With that noted, I looked at
your screenshot from above and wondered if you had set the driver to a
valid channel. The output might look like that if the card/driver is set
to a channel that doesn't "exist" on your feed. Find out how to change
channels and do so to a known valid channel and see what happens.
Ant
Even if I am not using an antenna?
--
"Oh bother", said Winnie the Pooh, "There's an ant on my foot..."
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Kevin Snodgrass
> On 12/26/2010 9:06 PM PT, Kevin Snodgrass typed:
>
>>> FYI, I got a screen show/capture of my desktop in action:
>>> http://img64.imageshack.us/img64/3069/screenshotk.gif so you can see
>>> what I see with xawtv.
>>
>> I don't use xawtv, I use mplayer. I don't use this video capture card
>> or it's relatives, I use Hauppauge PVRs. Therefore I don't know how to
>> accomplish many things with your setup. With that noted, I looked at
>> your screenshot from above and wondered if you had set the driver to a
>> valid channel. The output might look like that if the card/driver is
>> set to a channel that doesn't "exist" on your feed. Find out how to
>> change channels and do so to a known valid channel and see what
>> happens.
>
> Even if I am not using an antenna?
Not sure what you mean there. You have to use either an antenna or be
hooked up to an operational cable or satellite feed. Regardless, not all
channels carry a signal and you have to have the driver/card set to a
specific, valid channel to get a signal lock.
One exception would be if you are using the component inputs on the card,
like from a VCR. If you are doing that you still have to tell the driver/
card to use that input source instead of the coax input source.
J G Miller
>> I meant the value of the DISPLAY environmental variable being set to
>> :0.0 and not your_hostname.your_domain:0.0
>
> I am not sure how to find that, but maybe this is it?
How many years have you been using Unix or Linux systems?
To see the value to which an environmental variable is set, do
echo "${ENV_NAME}"
In this case echo "${DISPLAY}"
The reason to put the variable name in quotes is because say
for some reason a variable had the value *. Without the
double quotes the shell would expand (unless globbing was turned off)
the * to a list of the all the files in the current working directory.
> $ /usr/bin/v4l-conf -nodga
So it does not take that option. Have you tried doing
man v4l-conf
to see what it actually does?
As I do not have it installed, I did not check, but now having a look at
<http://linux.die.net/man/8/v4l-conf>
it seems that running it manually is not going to help to do anything anyways.
> Installed, but I still see the errors.
So have you run xlsfonts to see if the font is available via the
Xorg server, even though the package has been installed?
If not, you will have to add the directory
/usr/share/fonts/X11/misc
in which the led font has been installed to the fontpath in
/etc/X11/xorg.conf (if you have one).
When I do an xlsfonts | egrep led I do see amongst the entries
-xxl-ledfixed-medium-r-semicondensed--39-120-75-75-c-180-iso10646-1
...
-xxl-ledfixed-medium-r-semicondensed--39-120-75-75-c-180-koi8-r
which match the pattern
"-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*"
that xawtv is trying to use as per your error message,
Warning: Cannot convert string "string_above" to type FontStruct
> OK. They just look scary. :)
dmesg lines only look scary when they contain "WARNING",
"ERROR", "FAILED", or the worst "Call Trace".
> FYI, I got a screen show/capture of my desktop in action
Looks like a fuzzy "snow" picture because xawtv is looking at
probably VHF channel 2. You need to tell xawtv to display
the "video input" and not the "VHF/UHF tuner".
See image at
<http://screenshots.debian.net/package/xawtv>
There it shows the video source as "Television"
You need to read the manual page to discover
"verify the settings in the options menu (right mouse button)
and adjust the settings (TV norm, *Video source*, freqency table)."
Ant
>>> I don't use xawtv, I use mplayer. I don't use this video capture card
>>> or it's relatives, I use Hauppauge PVRs. Therefore I don't know how to
>>> accomplish many things with your setup. With that noted, I looked at
>>> your screenshot from above and wondered if you had set the driver to a
>>> valid channel. The output might look like that if the card/driver is
>>> set to a channel that doesn't "exist" on your feed. Find out how to
>>> change channels and do so to a known valid channel and see what
>>> happens.
>>
>> Even if I am not using an antenna?
>
> Not sure what you mean there. You have to use either an antenna or be
> hooked up to an operational cable or satellite feed. Regardless, not all
> channels carry a signal and you have to have the driver/card set to a
> specific, valid channel to get a signal lock.
I am not using cable, satellite, etc. I am only using it to capture
videos from old VCRs, camcorders, etc. That's all it does. I have
another computer with two HDTV tuner cards connected to rabbit ears. Old
non-HDTV tuner card is just for old stuff.
> One exception would be if you are using the component inputs on the card,
> like from a VCR. If you are doing that you still have to tell the driver/
> card to use that input source instead of the coax input source.
Ah OK. Thanks. :)
--
"If you're an ant, and you're walking along across the top of a cup of
pudding, you probably have no idea that the only thing between you and
disaster is the strength of that pudding skin." --Jack Handy from
Saturday Night Live
Ant
>>> I meant the value of the DISPLAY environmental variable being set to
>>> :0.0 and not your_hostname.your_domain:0.0
>>
>> I am not sure how to find that, but maybe this is it?
>
> How many years have you been using Unix or Linux systems?
Over a decade, but I don't use command line much. I mostly use GUI
desktops like KDE v3.5.10. And if I do command line, then it is just the
basics. Look at this way, I still don't understand that chmod stuff,
regexp, scripting, etc. I am definitely not a coder/programmer (hated
it). :)
> To see the value to which an environmental variable is set, do
>
> echo "${ENV_NAME}"
It shows nothing.
> In this case echo "${DISPLAY}"
It showed ":0.0" without quotation marks so that's good!
> The reason to put the variable name in quotes is because say
> for some reason a variable had the value *. Without the
> double quotes the shell would expand (unless globbing was turned off)
> the * to a list of the all the files in the current working directory.
>
>> $ /usr/bin/v4l-conf -nodga
>
> So it does not take that option. Have you tried doing
>
> man v4l-conf
>
> to see what it actually does?
Here is what it says: http://pastie.org/1410437 ... Nothing about having
no dga that I could see.
> As I do not have it installed, I did not check, but now having a look at
>
> <http://linux.die.net/man/8/v4l-conf>
>
> it seems that running it manually is not going to help to do anything anyways.
Oh well. It was worth a shot. :(
>> Installed, but I still see the errors.
>
> So have you run xlsfonts to see if the font is available via the
> Xorg server, even though the package has been installed?
No, I did not run it. I thought it added fonts for xawtv to have. I ran
and posted its very long results in here: http://paste2.org/p/1165804
... After seeing that list, I did not see ledfixed-medium-r and
searching in Debian packages on http://www.debian.org/distrib/packages
did not show any.
> If not, you will have to add the directory
>
> /usr/share/fonts/X11/misc
>
> in which the led font has been installed to the fontpath in
> /etc/X11/xorg.conf (if you have one).
I do have one, but where and what do I add this path/directory?
# cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder75) Sun Nov 8
21:50:38 PST 2009
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 30.0 - 110.0
VertRefresh 50.0 - 150.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
> When I do an xlsfonts | egrep led I do see amongst the entries
>
> -xxl-ledfixed-medium-r-semicondensed--39-120-75-75-c-180-iso10646-1
> ...
> -xxl-ledfixed-medium-r-semicondensed--39-120-75-75-c-180-koi8-r
>
> which match the pattern
>
> "-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*"
>
> that xawtv is trying to use as per your error message,
> Warning: Cannot convert string "string_above" to type FontStruct
OK, I will try that when I get xorg.conf with the path/directory.
>> OK. They just look scary. :)
>
> dmesg lines only look scary when they contain "WARNING",
> "ERROR", "FAILED", or the worst "Call Trace".
OK. That's new to me. They all look scary to me. More like too technical. :)
>> FYI, I got a screen show/capture of my desktop in action
>
> Looks like a fuzzy "snow" picture because xawtv is looking at
> probably VHF channel 2. You need to tell xawtv to display
> the "video input" and not the "VHF/UHF tuner".
>
> See image at
>
> <http://screenshots.debian.net/package/xawtv>
>
> There it shows the video source as "Television"
>
> You need to read the manual page to discover
>
> "verify the settings in the options menu (right mouse button)
> and adjust the settings (TV norm, *Video source*, freqency table)."
Ah. When I change from TV to S-Video, then I get a blue video.
Frequency's options (broadcast, cable, etc.) doesn't seem to have match
anything for my old VCR. It seems to be for TV stuff. I think that's a
good sign even though I don't see anything from my VCR? I recall getting
blue screen for VCR stuff.
I will need to play with this later (don't have time now due to back to
work). I will go in details during the long New Year's Day weekend. :)
I'll be back soon. :)
--
"An ant can do more than an ox that is lying down." --unknown
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Kevin Snodgrass
> On 12/27/2010 1:24 PM PT, Kevin Snodgrass typed:
>
>>>> I don't use xawtv, I use mplayer. I don't use this video capture
>>>> card or it's relatives, I use Hauppauge PVRs. Therefore I don't know
>>>> how to accomplish many things with your setup. With that noted, I
>>>> looked at your screenshot from above and wondered if you had set the
>>>> driver to a valid channel. The output might look like that if the
>>>> card/driver is set to a channel that doesn't "exist" on your feed.
>>>> Find out how to change channels and do so to a known valid channel
>>>> and see what happens.
>>>
>>> Even if I am not using an antenna?
>>
>> Not sure what you mean there. You have to use either an antenna or be
>> hooked up to an operational cable or satellite feed. Regardless, not
>> all channels carry a signal and you have to have the driver/card set to
>> a specific, valid channel to get a signal lock.
>
> I am not using cable, satellite, etc. I am only using it to capture
> videos from old VCRs, camcorders, etc. That's all it does. I have
> another computer with two HDTV tuner cards connected to rabbit ears. Old
> non-HDTV tuner card is just for old stuff.
OK. How are these devices connected to the card? If with coax then you
need to tell the driver/card to use the coax input (which is probably the
default, but ...) and set it to the channel that the device is playing
back on, generally channel 4 but could also be channel 3.
If with component or composite cables then you need to tell the card/
driver to use those inputs, there are no "channels" on component or
composite cables.
Ant
> OK. How are these devices connected to the card? If with coax then you
> need to tell the driver/card to use the coax input (which is probably the
> default, but ...) and set it to the channel that the device is playing
> back on, generally channel 4 but could also be channel 3.
The old TV tuner is connected to a VCR. VCR is connected to the old CRT TV.
> If with component or composite cables then you need to tell the card/
> driver to use those inputs, there are no "channels" on component or
> composite cables.
I did not see any component or composite listed in xawtv. Did I miss
something?
--
"This isn't a war. It never was a war, any more than there's war between
man and ants." --artilleryman from H.G. Wells' The War of the Worlds
Kevin Snodgrass
> On 12/28/2010 11:25 AM PT, Kevin Snodgrass typed:
>
>> OK. How are these devices connected to the card? If with coax then
>> you need to tell the driver/card to use the coax input (which is
>> probably the default, but ...) and set it to the channel that the
>> device is playing back on, generally channel 4 but could also be
>> channel 3.
>
> The old TV tuner is connected to a VCR. VCR is connected to the old CRT
> TV.
So it looks something like this:
|------------|
| VCR |
|------------|
| |
|--------------| | | |-----------------|
| TV |------| |------| ASUS Tuner Card |
|--------------| |-----------------|
What type of cables go from the VCR to the tuner card? Coax?
Composite? Component? S-Video + component audio? HDMI? Something else?
>> If with component or composite cables then you need to tell the card/
>> driver to use those inputs, there are no "channels" on component or
>> composite cables.
>
> I did not see any component or composite listed in xawtv. Did I miss
> something?
Has nothing to do with a user space application like xawtv. This is a
card/driver issue only. The modprobe stuff you were working on. xawtv
probably doesn't "know" anything about setting an input source or
changing channels, it just reads data from the character special file /
dev/video0 and displays it in an X window (and plays the sound on your
speakers).
Ant
>>> OK. How are these devices connected to the card? If with coax then
>>> you need to tell the driver/card to use the coax input (which is
>>> probably the default, but ...) and set it to the channel that the
>>> device is playing back on, generally channel 4 but could also be
>>> channel 3.
>>
>> The old TV tuner is connected to a VCR. VCR is connected to the old CRT
>> TV.
>
> So it looks something like this:
>
> |------------|
> | VCR |
> |------------|
> | |
> |--------------| | | |-----------------|
> | TV |------| |------| ASUS Tuner Card |
> |--------------| |-----------------|
Yes.
> What type of cables go from the VCR to the tuner card? Coax?
I believe TV tuner -> S-Video -> a cable connection adapter -> composite
cable -> VCR. Definitely not coax.
> Composite? Component? S-Video + component audio? HDMI? Something else?
Definitely not HDMI. There are red and black cable ends/plugs.
>>> If with component or composite cables then you need to tell the card/
>>> driver to use those inputs, there are no "channels" on component or
>>> composite cables.
>>
>> I did not see any component or composite listed in xawtv. Did I miss
>> something?
>
> Has nothing to do with a user space application like xawtv. This is a
> card/driver issue only. The modprobe stuff you were working on. xawtv
> probably doesn't "know" anything about setting an input source or
> changing channels, it just reads data from the character special file /
> dev/video0 and displays it in an X window (and plays the sound on your
> speakers).
Ah OK.
--
"They are like the ant... They start one way and turn around and go the
other way... They look all the time at the ground and never see the
sky." --Davi Kopenawa Yanomami, Amazonian Indian (Newsweek 117(17):5, 1991)
J G Miller
> xawtv probably doesn't "know" anything about setting an input source
> or changing channels
So explain why the screen shot of xawtv at
<http://screenshots.debian.NET/package/xawtv>
shows the option to change the input source, and why the manual page
for xawtv
<http://linux.die.NET/man/1/xawtv>
states
QUOTE
Then verify the settings in the options menu (right mouse button)
and adjust the settings (TV norm, Video source, freqency table).
UNQUOTE
And why if xawtv does not know anything about changing channels
Keyboard Shortcuts
include
C Popup Channels Window
E Popup Channel Editor
Z Channel Hopper (zapping, tune in every
station a few seconds)
Ctrl+Z Fast Channel Hopping (grab the images for the
Channel Bottons)
up/down tune up/down one channel
pgup/pgdown station up/down (the ones you have in the config file)
Would it be more accurate to say that Kevin Snodgrass doesn't "know"
anything about xawtv (probably because he has never used it)?
Kevin Snodgrass
> Would it be more accurate to say that Kevin Snodgrass doesn't "know"
> anything about xawtv (probably because he has never used it)?
Exactly. I assumed that xawtv was similar to mplayer and was wrong. As
I said in an early post, I don't use xawtv, I use mplayer.
Now a question to an expert on xawtv. Is there a unified method for
changing channels on the various tuner cards/chips/drivers/etc? In other
words, does it matter what tuner/capture card one has? I have all
Hauppauge cards (with uses the ivtv driver), some may have cards that use
the bttv driver, ANT has one that uses the cx8800 driver, there may be
others, some may have a mixture of cards. Do they all use the same IOCTLs
for changing channels, selecting inputs and all, so a userspace app like
xawtv doesn't care which driver or does xawtv "know" how to handle each
and every driver setup out there?
Kevin Snodgrass
> On 12/28/2010 10:01 PM PT, Kevin Snodgrass typed:
>
> I believe TV tuner -> S-Video -> a cable connection adapter -> composite
> cable -> VCR. Definitely not coax.
OK. Are you sure the "cable connection adapter" works?
>> Composite? Component? S-Video + component audio? HDMI? Something
>> else?
>
> Definitely not HDMI. There are red and black cable ends/plugs.
Sounds like composite cables. But I think the important point is the S-
Video connector being used on the tuner card. Somehow, you need to make
sure the tuner card "knows" to use that input. My experience with
Hauppauge cards is they default to using coax.
I did some looking around on my system. Since I originally set this up,
5 or 6 years ago (more? Back when Fedora Core 1 or 2 was current!) many
things have changed, for the better it appears. When I updated to more
recent versions of Fedora if something didn't work as expected, I just
figured out how to make things work. Now I see some useful things, like
v4l2.
There is a program called v4l2-ctl that (appearently) handles a lot of
stuff I wrote scripts to do years ago. It can set the tuner to use a
specific input source (v4l2-ctl -i, use v4l2-ctl -n to list available
input sources), set frequency (v4l2-ctl -f) which you shouldn't need if
using S-video or composite inputs since there are no channels on those
sources (nor on component or HDMI).
I forget if, in this long thread, you had v4l2 stuff installed. Make
sure you have v4l2-ctl installed from some package as it appears to
handle most (all?) driver settings issues.
>>> I did not see any component or composite listed in xawtv. Did I miss
>>> something?
>>
>> Has nothing to do with a user space application like xawtv. This is a
>> card/driver issue only. The modprobe stuff you were working on. xawtv
>> probably doesn't "know" anything about setting an input source or
>> changing channels, it just reads data from the character special file /
>> dev/video0 and displays it in an X window (and plays the sound on your
>> speakers).
>
> Ah OK.
As Mr. Miller pointed out, I don't know xawtv. It does "know" about
inputs and channels and maybe it uses v4l2-ctl to deal with those issues.
Ant
> On Wed, 29 Dec 2010 00:03:46 -0800, Ant wrote:
> > On 12/28/2010 10:01 PM PT, Kevin Snodgrass typed:
> >> What type of cables go from the VCR to the tuner card? Coax?
> >
> > I believe TV tuner -> S-Video -> a cable connection adapter -> composite
> > cable -> VCR. Definitely not coax.
> OK. Are you sure the "cable connection adapter" works?
Hmm, it was working on my other PC. Maybe it broke when I swapped. I
will look into it again later.
> >> Composite? Component? S-Video + component audio? HDMI? Something
> >> else?
> >
> > Definitely not HDMI. There are red and black cable ends/plugs.
> Sounds like composite cables. But I think the important point is the S-
> Video connector being used on the tuner card. Somehow, you need to make
> sure the tuner card "knows" to use that input. My experience with
> Hauppauge cards is they default to using coax.
OK.
> I did some looking around on my system. Since I originally set this up,
> 5 or 6 years ago (more? Back when Fedora Core 1 or 2 was current!) many
> things have changed, for the better it appears. When I updated to more
> recent versions of Fedora if something didn't work as expected, I just
> figured out how to make things work. Now I see some useful things, like
> v4l2.
> There is a program called v4l2-ctl that (appearently) handles a lot of
> stuff I wrote scripts to do years ago. It can set the tuner to use a
> specific input source (v4l2-ctl -i, use v4l2-ctl -n to list available
> input sources), set frequency (v4l2-ctl -f) which you shouldn't need if
> using S-video or composite inputs since there are no channels on those
> sources (nor on component or HDMI).
> I forget if, in this long thread, you had v4l2 stuff installed. Make
> sure you have v4l2-ctl installed from some package as it appears to
> handle most (all?) driver settings issues.
I don't have v4l2-ctl anywhere on my on two old IDE/PATA HDDs. Based on
http://packages.debian.org/search?searchon=contents&keywords=v4l2-ctl&mode=path&suite=unstable&arch=any
I need ivtv-utils package, BUT:
# apt-get install ivtv-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
kppp kwifimanager kcharselect kruler ksnapshot kfloppy kpager kcalc
klipper kmenuedit khexedit
ksysv kfind esound-clients kget kdeaddons-kfile-plugins kmix
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
at autopoint build-essential dctrl-tools debhelper debian-keyring
devscripts diffstat dpkg
dpkg-dev dput equivs exiv2 fakeroot gettext html2text intltool-debian
kaboom kdebase-bin
kdebase-data kdebase-runtime kdebase-runtime-data kdelibs-bin
kdelibs5-data kdelibs5-plugins
kdoctools konqueror konqueror-nsplugins libalgorithm-diff-perl
libalgorithm-diff-xs-perl
libalgorithm-merge-perl libattica0 libauthen-sasl-perl
libclass-inspector-perl libclucene0ldbl
libcommon-sense-perl libconfig-inifiles-perl libconvert-binhex-perl
libcrypt-ssleay-perl
libdevel-symdump-perl libdpkg-perl libexiv2-9 libfcgi-perl
libgraphicsmagick3
libio-socket-ssl-perl libio-stringy-perl libiodbc2 libipc-run-perl
libjson-perl libjson-xs-perl
libkde3support4 libkdecore5 libkdesu5 libkdeui5 libkdnssd4 libkfile4
libkhtml5 libkio5 libkjsapi4
libkjsembed4 libkmediaplayer4 libknewstuff2-4 libknewstuff3-4
libknotifyconfig4 libkntlm4 libkonq5
libkonq5-templates libkonqsidebarplugin4a libkparts4 libkpty4
libkrosscore4 libktexteditor4
libkutils4 libmail-sendmail-perl libmime-tools-perl libmysqlclient16
libnepomuk4 libnepomukquery4a
libnet-libidn-perl libnet-ssleay-perl libossp-uuid-perl libossp-uuid16
libparse-debcontrol-perl
libphonon4 libplasma3 libpod-coverage-perl libpolkit-qt-1-0 libqca2
libqt4-qt3support libqt4-sql
libqt4-sql-mysql libqt4-webkit libqt4-xmlpatterns libsoap-lite-perl
libsolid4 libsoprano4 libssh-4
libstreamanalyzer0 libstreams0 libsys-hostname-long-perl
libtask-weaken-perl libterm-size-perl
libtest-pod-perl libthreadweaver4 libtie-ixhash-perl libunistring0
libvideo-capture-v4l-perl
libvideo-ivtv-perl libvirtodbc0 libxcb-shape0 libxine1 libxine1-bin
libxine1-console
libxine1-ffmpeg libxine1-misc-plugins libxine1-plugins libxine1-x
lintian mysql-common
oxygen-icon-theme patchutils perl-tk phonon phonon-backend-xine
plasma-scriptengine-javascript
po-debconf shared-desktop-ontologies soprano-daemon ttf-dejavu
ttf-dejavu-extra virtuoso-minimal
virtuoso-opensource-6.1-bin virtuoso-opensource-6.1-common wdiff
xz-utils
Suggested packages:
debtags dh-make cvs-buildpackage devscripts-el gnuplot
libfile-desktopentry-perl
libnet-smtp-ssl-perl svn-buildpackage mini-dinstall yaclc gettext-doc
djvulibre-bin icoutils
konq-plugins libdigest-hmac-perl libgssapi-perl graphicsmagick-dbg
libio-socket-inet6-perl hspell
uuid libqca2-plugin-cyrus-sasl libqca2-plugin-gnupg
libqca2-plugin-ossl libqca2-plugin-pkcs11
libqt4-dev libapache2-mod-perl2 libnet-jabber-perl libmime-lite-perl
gxine xine-ui libxine1-doc
libxine-doc libxine1-gnome binutils-multiarch libtext-template-perl
phonon-backend-gstreamer
phonon-backend-vlc phonon-backend-mplayer libmail-box-perl xz-lzma
Recommended packages:
debian-maintainers dolphin
The following packages will be REMOVED:
kcontrol kdebase-bin-kde3 kdebase-kio-plugins kdesktop kicker
kicker-applets kpersonalizer ksplash
The following NEW packages will be installed:
at autopoint build-essential dctrl-tools debhelper debian-keyring
devscripts diffstat dpkg-dev
dput equivs exiv2 fakeroot gettext html2text intltool-debian
ivtv-utils kaboom kdebase-runtime
kdebase-runtime-data kdelibs-bin kdelibs5-data kdelibs5-plugins
kdoctools libalgorithm-diff-perl
libalgorithm-diff-xs-perl libalgorithm-merge-perl libattica0
libauthen-sasl-perl
libclass-inspector-perl libclucene0ldbl libcommon-sense-perl
libconfig-inifiles-perl
libconvert-binhex-perl libcrypt-ssleay-perl libdevel-symdump-perl
libdpkg-perl libexiv2-9
libfcgi-perl libgraphicsmagick3 libio-socket-ssl-perl
libio-stringy-perl libiodbc2 libipc-run-perl
libjson-perl libjson-xs-perl libkde3support4 libkdecore5 libkdesu5
libkdeui5 libkdnssd4 libkfile4
libkhtml5 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4
libknewstuff2-4 libknewstuff3-4
libknotifyconfig4 libkntlm4 libkonq5 libkonq5-templates
libkonqsidebarplugin4a libkparts4 libkpty4
libkrosscore4 libktexteditor4 libkutils4 libmail-sendmail-perl
libmime-tools-perl libmysqlclient16
libnepomuk4 libnepomukquery4a libnet-libidn-perl libnet-ssleay-perl
libossp-uuid-perl
libossp-uuid16 libparse-debcontrol-perl libphonon4 libplasma3
libpod-coverage-perl
libpolkit-qt-1-0 libqca2 libqt4-qt3support libqt4-sql libqt4-sql-mysql
libqt4-webkit
libqt4-xmlpatterns libsoap-lite-perl libsolid4 libsoprano4 libssh-4
libstreamanalyzer0 libstreams0
libsys-hostname-long-perl libtask-weaken-perl libterm-size-perl
libtest-pod-perl libthreadweaver4
libtie-ixhash-perl libunistring0 libvideo-capture-v4l-perl
libvideo-ivtv-perl libvirtodbc0
libxcb-shape0 libxine1 libxine1-bin libxine1-console libxine1-ffmpeg
libxine1-misc-plugins
libxine1-plugins libxine1-x lintian mysql-common oxygen-icon-theme
patchutils perl-tk phonon
phonon-backend-xine plasma-scriptengine-javascript po-debconf
shared-desktop-ontologies
soprano-daemon ttf-dejavu ttf-dejavu-extra virtuoso-minimal
virtuoso-opensource-6.1-bin
virtuoso-opensource-6.1-common wdiff xz-utils
The following packages will be upgraded:
dpkg kdebase-bin kdebase-data konqueror konqueror-nsplugins
5 upgraded, 131 newly installed, 8 to remove and 17 not upgraded.
Need to get 120 MB of archives.
After this operation, 218 MB of additional disk space will be used.
Do you want to continue [Y/n]?
I do not want to upgrade my old KDE v3.5.10. :(
> >>> I did not see any component or composite listed in xawtv. Did I miss
> >>> something?
> >>
> >> Has nothing to do with a user space application like xawtv. This is a
> >> card/driver issue only. The modprobe stuff you were working on. xawtv
> >> probably doesn't "know" anything about setting an input source or
> >> changing channels, it just reads data from the character special file /
> >> dev/video0 and displays it in an X window (and plays the sound on your
> >> speakers).
> >
> > Ah OK.
> As Mr. Miller pointed out, I don't know xawtv. It does "know" about
> inputs and channels and maybe it uses v4l2-ctl to deal with those issues.
Hmm...
--
Quote of the Week: "Any spoke will lead the ant to the hub." --unknown
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.
Ant
> > Would it be more accurate to say that Kevin Snodgrass doesn't "know"
> > anything about xawtv (probably because he has never used it)?
> Exactly. I assumed that xawtv was similar to mplayer and was wrong. As
> I said in an early post, I don't use xawtv, I use mplayer.
I should try Mplayer with my TV tuner card later. Do I have to do
anything special with it? I have both mplayer and gmplayer installed.
--
Quote of the Week: "Any spoke will lead the ant to the hub." --unknown
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.
Ant
> > sure you have v4l2-ctl installed from some package as it appears to
> > handle most (all?) driver settings issues.
> I don't have v4l2-ctl anywhere on my on two old IDE/PATA HDDs. Based on
> http://packages.debian.org/search?searchon=contents&keywords=v4l2-ctl&mode=path&suite=unstable&arch=any
> I need ivtv-utils package, BUT:
Wait. I am an idiot! I read that search results wrong. It also mentioned
v4l-utils package and that I was OK to install which was not already
installed:
# apt-get install v4l-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
kppp kwifimanager kcharselect kruler ksnapshot kfloppy
konqueror-nsplugins kpager kcalc klipper
kmenuedit kicker-applets khexedit ksplash ksysv esound-clients kget
kdeaddons-kfile-plugins kmix
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
v4l-utils
0 upgraded, 1 newly installed, 0 to remove and 22 not upgraded.
Need to get 81.9 kB of archives.
After this operation, 250 kB of additional disk space will be used.
Get:1 http://ftp.debian.org/debian/ testing/main v4l-utils i386 0.8.0-1
[81.9 kB]
Fetched 81.9 kB in 1s (71.5 kB/s)
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Selecting previously deselected package v4l-utils.
(Reading database ... 121823 files and directories currently installed.)
Unpacking v4l-utils (from .../v4l-utils_0.8.0-1_i386.deb) ...
Setting up v4l-utils (0.8.0-1) ...
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB
localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB
localepurge: Disk space freed in /usr/share/omf: 0 KiB
localepurge: Disk space freed in /usr/share/doc/kde/HTML: 0 KiB
Total disk space freed by localepurge: 0 KiB
I am not at the PC to try it again. Maybe it will work with it installed
now?
J G Miller
> Exactly.
Fair enough -- it is just a bit dangerous to make assumptions and suggestions
on something with which you are unfamiliar and have not checked.
It has been a long time since I have actually used xawtv but I used to use
it quite a lot with a Hauppauge TV and radio card, and it was the utilitarian
Linux equivalent of WinTV/WinTv2000 with which I think you are probably familiar.
> I assumed that xawtv was similar to mplayer and was wrong.
xawtv and mplayer are very different. Remember that mplayer started
out as a media file player and that the DVB decoding was bolted on
afterwards. Remember that DVB-t transport stream is basically MPEG-2
so since mplayer already could do standard MPEG-2 decoding using ffmpeg
(I think), so getting it to handle streams was probably not a very big
job for the developpers.
xawtv was as far as I recall specifically written as a TV card application
and only later got more wider use as a means of viewing web cam and other
video images.
> Now a question to an expert on xawtv. Is there a unified method for
> changing channels on the various tuner cards/chips/drivers/etc? In
> other words, does it matter what tuner/capture card one has? I have all
> Hauppauge cards (with uses the ivtv driver), some may have cards that
> use the bttv driver, ANT has one that uses the cx8800 driver, there may
> be others, some may have a mixture of cards.
> Do they all use the same IOCTLs for changing channels, selecting inputs
> and all, so a userspace app like xawtv doesn't care which driver or
> does xawtv "know" how to handle each and every driver setup out there?
Well my understanding is as follows --
xawtv uses the v4l (video for linux, formerly bttv) library.
The various kernel modules you have mentioned are all written to provide
an interface for that hardware with the base layer kernel module
v4l2-common.ko and for older applications such as xawtv, v4l1-compat.ko
So roughly speaking, xawtv talks to v4l1-compat, which may translate calls
to v4l2 for the v4l2-common module which then talks to the specific
hardware module.
Thus the important thing is that the user application uses v4l, and that
the hardware device module is written for v4l.
A similar situation exists for ALSA and the various hardware device
modules (emu10k1, sbawe, usb_audio etc etc).
So if you were to go to the Creative site and download their commercial
linux module, that I do not think will work with ALSA sound applications,
because I think, it is written with the OSS library (but I maybe wrong on
that).
This is why kernel standard library interfaces are so important, such that
the user application can talk to the device regardless of the hardware
model and brand.
JEDIDIAH
> On Wednesday, December 29th, 2010 at 20:01:36h +0000, Kevin Snodgrass wrote:
>
>> Exactly.
>
> Fair enough -- it is just a bit dangerous to make assumptions and suggestions
> on something with which you are unfamiliar and have not checked.
>
> It has been a long time since I have actually used xawtv but I used to use
> it quite a lot with a Hauppauge TV and radio card, and it was the utilitarian
> Linux equivalent of WinTV/WinTv2000 with which I think you are probably familiar.
>
>> I assumed that xawtv was similar to mplayer and was wrong.
>
> xawtv and mplayer are very different. Remember that mplayer started
> out as a media file player and that the DVB decoding was bolted on
> afterwards. Remember that DVB-t transport stream is basically MPEG-2
> so since mplayer already could do standard MPEG-2 decoding using ffmpeg
> (I think), so getting it to handle streams was probably not a very big
> job for the developpers.
>
> xawtv was as far as I recall specifically written as a TV card application
> and only later got more wider use as a means of viewing web cam and other
> video images.
xawtv was originally written to support analog tuner cards that did
not have onboard digital compression hardware. It was actually a TV
viewing app rather than a media player. There's a bit of a difference,
one key one being the ability to change the channel on the tuner.
Streaming video from a raw device through a pipe and into a media
player is a fairly mundane sort of thing in Unix terms. Mplayer can play
input from a capture card because that's just how devices work on Unix.
It doesn't matter where the file comes from. It's just a file.
--
If some college kid can replicate your "invention" without seeing |||
any of the details of your patent then you have been granted a patent / | \
on the "idea" and not the actual implementation.
Kevin Snodgrass
> On Wednesday, December 29th, 2010 at 20:01:36h +0000, Kevin Snodgrass
> wrote:
>
>> Exactly.
>
> Fair enough -- it is just a bit dangerous to make assumptions and
> suggestions on something with which you are unfamiliar and have not
> checked.
>
> It has been a long time since I have actually used xawtv but I used to
> use it quite a lot with a Hauppauge TV and radio card, and it was the
> utilitarian Linux equivalent of WinTV/WinTv2000 with which I think you
> are probably familiar.
What is WinTV/WinTV2000? Never heard of it/them... If that is some sort
of Winders software I will be gloriously ignorant. Haven't used anything
Winders since 1997. (Not exactly true, trying to get a Winders app
running under wine right now. Misbehaving, poorly written crap
software! SIGSEGV every few minutes...)
>> I assumed that xawtv was similar to mplayer and was wrong.
>
> xawtv and mplayer are very different. Remember that mplayer started out
> as a media file player and that the DVB decoding was bolted on
> afterwards. Remember that DVB-t transport stream is basically MPEG-2 so
> since mplayer already could do standard MPEG-2 decoding using ffmpeg (I
> think), so getting it to handle streams was probably not a very big job
> for the developpers.
I think mplayer used to use ffmpeg, but now faad2-libs handles MPEG2 and
MPEG-4 decoding.
> xawtv was as far as I recall specifically written as a TV card
> application and only later got more wider use as a means of viewing web
> cam and other video images.
Hmm, maybe the "tv" part of the name should have been a clue...
>> Now a question to an expert on xawtv. Is there a unified method for
>> changing channels on the various tuner cards/chips/drivers/etc? In
>> other words, does it matter what tuner/capture card one has? I have
>> all Hauppauge cards (with uses the ivtv driver), some may have cards
>> that use the bttv driver, ANT has one that uses the cx8800 driver,
>> there may be others, some may have a mixture of cards.
>
>> Do they all use the same IOCTLs for changing channels, selecting inputs
>> and all, so a userspace app like xawtv doesn't care which driver or
>> does xawtv "know" how to handle each and every driver setup out there?
>
> Well my understanding is as follows --
>
> xawtv uses the v4l (video for linux, formerly bttv) library.
Thanks for the info.
Been reading about v4l. When I first was setting up my own PVR system,
Fedora Core 1 or 2 timeframe (might have even been pre-Fedora time, can't
really remember), much of this stuff either didn't exist or was too
unstable. I just wanted a VCR replacement. Once I got the IVTV driver
working (it was not part of the kernel then, you had to download and
compile it on your own) and got mplayer running, I just wrote some
control scripts to handle channel changes, timing, capture file naming,
etc... Setup the .ivtv-tune (might have been called something different
years ago, but was the same idea) for my hardware and then went on with
life. Things have progressed quite a bit since then. :-)
Kevin Snodgrass
> In comp.os.linux.hardware Kevin Snodgrass <kdsno...@yahoo.com> wrote:
>> > Would it be more accurate to say that Kevin Snodgrass doesn't "know"
>> > anything about xawtv (probably because he has never used it)?
>
>> Exactly. I assumed that xawtv was similar to mplayer and was wrong.
>> As I said in an early post, I don't use xawtv, I use mplayer.
>
> I should try Mplayer with my TV tuner card later. Do I have to do
> anything special with it? I have both mplayer and gmplayer installed.
Once you have the driver working, just type "mplayer /dev/video0" and
watch. I've never trying the gmplayer frontend, don't need it since I
use xterms all the time. :-) You can check mplayer/gmplayer by just
trying any old .mpg, and it should also work on any .mp4, .wmv, .asf, .mov
or whatever video files. It's possible that you will need additional
codecs installed, but from what I can tell, at least on Fedora,
installing mplayer will require the installation of most all other
necessary stuff, like codecs to play Winders proprietary formats...
faad2-libs handles the MPEG2 (.mpg) and MPEG-4 (.mp4) files and mplayer
utilizes faad2-libs. This is for Fedora, hopefully Debian uses the same
package names.
Kevin Snodgrass
>> OK. Are you sure the "cable connection adapter" works?
>
> Hmm, it was working on my other PC. Maybe it broke when I swapped. I
> will look into it again later.
It probably does work, but it is something to check.
> I don't have v4l2-ctl anywhere on my on two old IDE/PATA HDDs. Based on
> http://packages.debian.org/search?searchon=contents&keywords=v4l2-
ctl&mode=path&suite=unstable&arch=any
> I need ivtv-utils package, BUT:
>
> # apt-get install ivtv-utils
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer
> required:
[snippage]
> I do not want to upgrade my old KDE v3.5.10. :(
Interesting. Not being a Debian user and all... Why does ivtv-utils
need anything KDE or Gnome or anything X related? I realize you, ANT,
may not have the answer. Somebody that packages stuff for Debian needs
to answer. Doesn't make any sense to me.
On Fedora, I get this:
(rpm -ql lists files in the package, rpm -q --requires lists the
requiements that must be met for the package)
$ rpm -ql ivtv-utils
/usr/bin/cx25840ctl
/usr/bin/ivtv-ctl
/usr/bin/ivtv-mpegindex
/usr/bin/ivtv-radio
/usr/bin/ivtv-tune
/usr/bin/ivtvplay
/usr/bin/radio-ivtv
/usr/bin/v4l2-ctl
/usr/share/doc/ivtv-utils-1.4.0
/usr/share/doc/ivtv-utils-1.4.0/README.devices
/usr/share/doc/ivtv-utils-1.4.0/README.install
/usr/share/doc/ivtv-utils-1.4.0/README.lirc
/usr/share/doc/ivtv-utils-1.4.0/README.radio
/usr/share/doc/ivtv-utils-1.4.0/README.utils
/usr/share/doc/ivtv-utils-1.4.0/README.vbi
/usr/share/doc/ivtv-utils-1.4.0/conversion.txt
/usr/share/doc/ivtv-utils-1.4.0/fw-readme.txt
/usr/share/doc/ivtv-utils-1.4.0/video-quality.txt
/usr/share/ivtv
/usr/share/ivtv/ivtvfwextract.pl
$ rpm -q --requires ivtv-utils
/usr/bin/perl
ivtv-firmware
libc.so.6
libc.so.6(GLIBC_2.0)
libc.so.6(GLIBC_2.1)
libc.so.6(GLIBC_2.1.3)
libc.so.6(GLIBC_2.3)
libc.so.6(GLIBC_2.3.4)
libc.so.6(GLIBC_2.4)
libgcc_s.so.1
libgcc_s.so.1(GCC_3.0)
libm.so.6
libm.so.6(GLIBC_2.0)
libpthread.so.0
libpthread.so.0(GLIBC_2.0)
libpthread.so.0(GLIBC_2.1)
libpthread.so.0(GLIBC_2.2)
libstdc++.so.6
libstdc++.so.6(CXXABI_1.3)
libstdc++.so.6(GLIBCXX_3.4)
perl(Getopt::Long)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(VersionedDependencies) <= 3.0.3-1
rtld(GNU_HASH)
rpmlib(PayloadIsXz) <= 5.2-1
There is NOTHING X related, let alone KDE or Gnome related there...
Are you comfortable with compiling your own stuff? If so, download the
source code here:
http://ivtvdriver.org/index.php/Download
Pick the correct version according to your kernel version. Then just
compile the v4l2-ctl program, not the ivtv driver code. Might just
work. :-)
Also, it would be nice if the v4l2-ctl program were on it's own or
included with the libv4l package instead of being part of ivtv, since ivtv
is a driver specific to a certain group of tuner cards and/or chipsets on
tuner cards.
/rant
Kevin Snodgrass
> Wait. I am an idiot! I read that search results wrong. It also mentioned
:-)
> v4l-utils package and that I was OK to install which was not already
> installed:
>
> # apt-get install v4l-utils
[snippage]
> I am not at the PC to try it again. Maybe it will work with it installed
> now?
OK. And I should have read this, second post before posting my rant
about KDE requirements, et al...
Ant
>>> I forget if, in this long thread, you had v4l2 stuff installed. Make
>>> sure you have v4l2-ctl installed from some package as it appears to
>>> handle most (all?) driver settings issues.
>
>> I don't have v4l2-ctl anywhere on my on two old IDE/PATA HDDs. Based on
>> http://packages.debian.org/search?searchon=contents&keywords=v4l2-ctl&mode=path&suite=unstable&arch=any
>> I need ivtv-utils package, BUT:
>
> Wait. I am an idiot! I read that search results wrong. It also mentioned
> v4l-utils package and that I was OK to install which was not already
> installed:
...
> I am not at the PC to try it again. Maybe it will work with it installed
> now?
Hmm, xawtv still didn't work from my quick tests. I don't have time to
play with it right now. I will try again in a few days. :)
--
"I look at an ant and I see myself: a native South African, endowed by
nature with a strength much greater than my size so I might cope with
the weight of a racism that crushes my spirit." --Miriam Makeba
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
Ant
> On Wed, 29 Dec 2010 14:44:28 -0600, Ant wrote:
>
>> In comp.os.linux.hardware Kevin Snodgrass<kdsno...@yahoo.com> wrote:
>>>> Would it be more accurate to say that Kevin Snodgrass doesn't "know"
>>>> anything about xawtv (probably because he has never used it)?
>>
>>> Exactly. I assumed that xawtv was similar to mplayer and was wrong.
>>> As I said in an early post, I don't use xawtv, I use mplayer.
>>
>> I should try Mplayer with my TV tuner card later. Do I have to do
>> anything special with it? I have both mplayer and gmplayer installed.
>
> Once you have the driver working, just type "mplayer /dev/video0" and
> watch. I've never trying the gmplayer frontend, don't need it since I
It didn't work:
$ mplayer /dev/video0
MPlayer SVN-r31918 (C) 2000-2010 MPlayer Team
Can't open joystick device /dev/input/js0: No such file or directory
Can't init input joystick
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote
control.
Playing /dev/video0.
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
Cannot seek backward in linear streams!
Seek failed
<<then I hit Q to quit mplayer>>
Exiting... (End of file)
Hopefully, that's a new clue?
> use xterms all the time. :-) You can check mplayer/gmplayer by just
> trying any old .mpg, and it should also work on any .mp4, .wmv, .asf, .mov
> or whatever video files. It's possible that you will need additional
> codecs installed, but from what I can tell, at least on Fedora,
> installing mplayer will require the installation of most all other
> necessary stuff, like codecs to play Winders proprietary formats...
> faad2-libs handles the MPEG2 (.mpg) and MPEG-4 (.mp4) files and mplayer
> utilizes faad2-libs. This is for Fedora, hopefully Debian uses the same
> package names.
I have used mplayer before. I do use its GUI frontend too (gmplayer)
since I need GUI. ;)
--
"Whoops, there goes another ambulance ant." --Seymour and Pepe (Rick
Moranis episode from The Muppets)
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
Ant
> :-)
> [snippage]
NP. My bad earlier for not reading carefully. :( FYI, I try to avoid
compiling. :)
Kevin Snodgrass
> It didn't work:
> $ mplayer /dev/video0
> MPlayer SVN-r31918 (C) 2000-2010 MPlayer Team Can't open joystick device
> /dev/input/js0: No such file or directory Can't init input joystick
> mplayer: could not connect to socket
> mplayer: No such file or directory
> Failed to open LIRC support. You will not be able to use your remote
> control.
Don't worry about the above errors. If you want them to go away you need
to make a couple minor changes to the mplayer config file. Use your
favorite editor to open ~/.mplayer/config and make it look something like
this:
-------------------------------------------
# Write your default config options here!
# No LIRC
nolirc=yes
# No joystick
nojoystick=yes
-------------------------------------------
There are many other options, but these two will quite the errors about
joystick and lirc.
> Playing /dev/video0.
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> Cannot seek backward in linear streams! Seek failed
> <<then I hit Q to quit mplayer>>
>
> Exiting... (End of file)
>
> Hopefully, that's a new clue?
Did a new window appear with anything in it?
mplayer found /dev/video0, which is good. The messages about "Cannot
seek backwards..." are nothing to worry about. mplayer allows you to
seek both forward and backward (with left arrow and right arrow for 10
second seek, up arrow and down arrow for 1 minute seek, and pageup and
pagedown for 10 minute seek) and that is not possible on a live stream.
I.e., this is normal.
Just for kicks, is it possible to attach a functioning cable connection
to the tuner card? My guess is you still need to get the driver to
switch to reading from the S-video input and it is currently reading from
the coax. By attaching a working cable connection you might get a valid
picture and know for sure that things work as is, just need to make the
driver change to a different input.
Ant
>> It didn't work:
>> $ mplayer /dev/video0
>> MPlayer SVN-r31918 (C) 2000-2010 MPlayer Team Can't open joystick device
>> /dev/input/js0: No such file or directory Can't init input joystick
>> mplayer: could not connect to socket
>> mplayer: No such file or directory
>> Failed to open LIRC support. You will not be able to use your remote
>> control.
>
> Don't worry about the above errors. If you want them to go away you need
> to make a couple minor changes to the mplayer config file. Use your
> favorite editor to open ~/.mplayer/config and make it look something like
> this:
> -------------------------------------------
> # Write your default config options here!
> # No LIRC
> nolirc=yes
>
> # No joystick
> nojoystick=yes
> -------------------------------------------
>
> There are many other options, but these two will quite the errors about
> joystick and lirc.
Thanks! Much cleaner. I wonder why MPlayer didn't include these by
default, but whatever.
> Did a new window appear with anything in it?
Nope for mplayer command. Gmplayer showed its usual GUI with nothing in
the video screen (well, light blue color -- think it is part of the
theme/skin and not the same blue on TV you see; then, it turned black
with still nothing [no statics like xawtv]).
I found something else with:
$ mplayer /dev/video0
MPlayer SVN-r31918 (C) 2000-2010 MPlayer Team
Playing /dev/video0.
Exiting... (Quit)
I noticed Gmplayer didn't respond quickly and didn't want to exit right
away. Also, a long dmesg (didn't even show me the old ones):
http://pastebin.ca/2034538 ...
> mplayer found /dev/video0, which is good. The messages about "Cannot
> seek backwards..." are nothing to worry about. mplayer allows you to
> seek both forward and backward (with left arrow and right arrow for 10
> second seek, up arrow and down arrow for 1 minute seek, and pageup and
> pagedown for 10 minute seek) and that is not possible on a live stream.
> I.e., this is normal.
OK. Scary errors to me. :)
> Just for kicks, is it possible to attach a functioning cable connection
> to the tuner card? My guess is you still need to get the driver to
> switch to reading from the S-video input and it is currently reading from
> the coax. By attaching a working cable connection you might get a valid
> picture and know for sure that things work as is, just need to make the
> driver change to a different input.
You mean like from my DTV Pal converter box to test its live TV feed
through its rabbit ears antenna? If so, then I could do that later.
--
"Bother," said Winnie the Pooh, as he stepped on an ant.
Kevin Snodgrass
> Thanks! Much cleaner. I wonder why MPlayer didn't include these by
> default, but whatever.
mplayer assumes many things, including a full fledged MythTV or similar
setup, which includes a remote control (lirc). Never have understood a
joystick with a media player.
>> Did a new window appear with anything in it?
>
> Nope for mplayer command. Gmplayer showed its usual GUI with nothing in
> the video screen (well, light blue color -- think it is part of the
> theme/skin and not the same blue on TV you see; then, it turned black
> with still nothing [no statics like xawtv]).
Not sure why mplayer (CLI) didn't pop up a window with either static or a
valid picture.
> I noticed Gmplayer didn't respond quickly and didn't want to exit right
> away. Also, a long dmesg (didn't even show me the old ones):
> http://pastebin.ca/2034538 ...
Don't know how to interpret that. Almost looks like the driver is trying
to lock on to a channel and can't. If this is the case, then it is
trying to lock on to a channel on the coax feed, which isn't live.
>> Just for kicks, is it possible to attach a functioning cable connection
>> to the tuner card? My guess is you still need to get the driver to
>> switch to reading from the S-video input and it is currently reading
>> from the coax. By attaching a working cable connection you might get a
>> valid picture and know for sure that things work as is, just need to
>> make the driver change to a different input.
>
> You mean like from my DTV Pal converter box to test its live TV feed
> through its rabbit ears antenna? If so, then I could do that later.
PAL? Are you in Europe?
What I'm trying to get at is a functioning coax feed. Anything. Coax is
probably what the card defaults to using. As long as you can provide an
NTSC signal on the coax feed then you just change channels to find a
valid one. Otherwise you MUST tell the card/driver that you are using a
different feed. That "should" be possible with v4l.
I'm trying to get you to understand two things:
1) Tuner cards that have multiple inputs, like coax and S-video/
composite, will default to using one of them. I believe most will
default to coax.
2) You either must provide a signal on the coax feed OR figure out how to
tell the card/driver to use the S-video/composite input. If you can't do
one or the other of these, you won't get a valid signal.
Ant
> On Thu, 30 Dec 2010 13:14:25 -0800, Ant wrote:
>> Thanks! Much cleaner. I wonder why MPlayer didn't include these by
>> default, but whatever.
>
> mplayer assumes many things, including a full fledged MythTV or similar
> setup, which includes a remote control (lirc). Never have understood a
> joystick with a media player.
Does anyone actually use a joystick for media players? I have never seen
one in action. :D
>>> Did a new window appear with anything in it?
>>
>> Nope for mplayer command. Gmplayer showed its usual GUI with nothing in
>> the video screen (well, light blue color -- think it is part of the
>> theme/skin and not the same blue on TV you see; then, it turned black
>> with still nothing [no statics like xawtv]).
>
> Not sure why mplayer (CLI) didn't pop up a window with either static or a
> valid picture.
Yeah, weird.
>> I noticed Gmplayer didn't respond quickly and didn't want to exit right
>> away. Also, a long dmesg (didn't even show me the old ones):
>> http://pastebin.ca/2034538 ...
>
> Don't know how to interpret that. Almost looks like the driver is trying
> to lock on to a channel and can't. If this is the case, then it is
> trying to lock on to a channel on the coax feed, which isn't live.
Good theory. :)
>>> Just for kicks, is it possible to attach a functioning cable connection
>>> to the tuner card? My guess is you still need to get the driver to
>>> switch to reading from the S-video input and it is currently reading
>>> from the coax. By attaching a working cable connection you might get a
>>> valid picture and know for sure that things work as is, just need to
>>> make the driver change to a different input.
>>
>> You mean like from my DTV Pal converter box to test its live TV feed
>> through its rabbit ears antenna? If so, then I could do that later.
>
> PAL? Are you in Europe?
No, DTV Pal converter box that I got a couple years ago due to DTV
changeover from analog (thanks FCC :P):
http://www.dishnetwork.com/dtvpal/ ...
> What I'm trying to get at is a functioning coax feed. Anything. Coax is
> probably what the card defaults to using. As long as you can provide an
> NTSC signal on the coax feed then you just change channels to find a
> valid one. Otherwise you MUST tell the card/driver that you are using a
> different feed. That "should" be possible with v4l.
Ah OK. I will try that later.
> I'm trying to get you to understand two things:
>
> 1) Tuner cards that have multiple inputs, like coax and S-video/
> composite, will default to using one of them. I believe most will
> default to coax.
>
> 2) You either must provide a signal on the coax feed OR figure out how to
> tell the card/driver to use the S-video/composite input. If you can't do
> one or the other of these, you won't get a valid signal.
Ah OK. Understood. I will mess with it more later (not today). Thanks. :)
--
"Really. And do these lions eat ants?" --John Cleese in Monty Python's
Flying Circus
Ant
I had my computer friend, who used to have this ASUS TV tuner card and
gave it to me years ago, to come over to check out my video cable setup
briefly. However, he is not a Linux user so he can't help me with that
OS and its software area. I did show him the symptoms and xawtv program.
He said my cables and hookups looked fine. We briefly fiddled with xawtv
settings too and he said they looked OK to him.
He wanted to ask if xawtv software can select the right hardware
pinstrap for composite input. He said Windows driver could do this or
something. Um, can Linux driver/module/software do this? This is a bit
technical to me, so I don't know where to check/look for it.
Thank you in advance. :)
--
"Everything tastes better at a picnic... the ants, the sand,
everything." --unknown
J G Miller
> He wanted to ask if xawtv software can select the right hardware
> pinstrap for composite input. He said Windows driver could do this or
> something. Um, can Linux driver/module/software do this? This is a bit
> technical to me, so I don't know where to check/look for it.
Your question was answered on Tuesday, December 28th, 2010 at 00:10:02 +0000,
at the bottom of message <ifb9sq$em5$2...@news.eternal-september.org>
and explained fully in Wednesday, December 29th, 2010 at
13:11:14h +0000 in message <iffc1i$m7a$2...@news.eternal-september.org>
> Thank you in advance. :)
Yes, your question had been answered in advance.
Ant
>> He wanted to ask if xawtv software can select the right hardware
>> pinstrap for composite input. He said Windows driver could do this or
>> something. Um, can Linux driver/module/software do this? This is a bit
>> technical to me, so I don't know where to check/look for it.
>
> Your question was answered on Tuesday, December 28th, 2010 at 00:10:02 +0000,
> at the bottom of message<ifb9sq$em5$2...@news.eternal-september.org>
I assume you are referring to "Looks like a fuzzy 'snow' picture because
xawtv is looking at probably VHF channel 2. You need to tell xawtv to
display the 'video input' and not the 'VHF/UHF tuner'." Oh, I forgot to
reply to that part I think. Anyways, my friend and I did mess with it
last night, but no luck. See
http://img207.imageshack.us/img207/864/screenshotssettings.gif for
screen shots/captures of those settings. Did I miss anything else in
xawtv's options?
> and explained fully in Wednesday, December 29th, 2010 at
> 13:11:14h +0000 in message<iffc1i$m7a$2...@news.eternal-september.org>
>
>> Thank you in advance. :)
>
> Yes, your question had been answered in advance.
Sorry. This is sure frustrating and confusing! :(
--
"If someone makes you angry, I think the thing to do is tie them down to
the ground, cover them in honey, and then release a swarm of killer ants
on them. That way, you can hit them over and over again and say, 'Hey!
I'm just trying to help!' and they can't really get mad at you." --R.M.
Weiner
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
Ant is/was listening to a song on this computer: Vitamin String Quartet
- You Know My Name (Chris Cornell Solo)
J G Miller
> Anyways, my friend and I did mess with it last night, but no luck.
But you did not explain that you had "messed" with it, or checked
the input setting.
> http://img207.imageshack.us/img207/864/screenshotssettings.gif for
> screen shots/captures of those settings.
So xawtv is recognising the S-Video input because the setting is there.
> Did I miss anything else in xawtv's options?
Yes.
Why did you launch xawtv *without* the -nodga parameter, as explained
on Sunday, December 26th, 2010 at 10:58:10h -0800 in message
<if85eu$974$2...@news.eternal-september.org>
> This is sure frustrating and confusing! :(
Because you are not taking one step at a time to resolve each issue.
And when you are trying xawtv, are you feeding it a video signal from
something, and presumably not a video cassette protected with Macrovision?
Ant
>> Anyways, my friend and I did mess with it last night, but no luck.
>
> But you did not explain that you had "messed" with it, or checked
> the input setting.
Just changing/messing the settings. None of them seem to show what I
should be getting like I did in my other Windows PC like in the past. :(
>> http://img207.imageshack.us/img207/864/screenshotssettings.gif for
>> screen shots/captures of those settings.
>
> So xawtv is recognising the S-Video input because the setting is there.
I assume that's a good sign?
>> Did I miss anything else in xawtv's options?
>
> Yes.
>
> Why did you launch xawtv *without* the -nodga parameter, as explained
Didn't I already do that back then? Here's the results when I tried it:
$ xawtv -nodga
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
Also for kicks, I tried the same as root. Same results. :(
> on Sunday, December 26th, 2010 at 10:58:10h -0800 in message
> <if85eu$974$2...@news.eternal-september.org>
>
>> This is sure frustrating and confusing! :(
>
> Because you are not taking one step at a time to resolve each issue.
>
> And when you are trying xawtv, are you feeding it a video signal from
> something, and presumably not a video cassette protected with Macrovision?
I am feeding from my old VCR. However, I never had problems with this
TV tuner when it was in old, updated Windows XP Pro. SP3 with PowerVCR II.
--
"What is this? A center for ants?!" "...What?" "How can we be expected
to teach children to learn how read, if they can't even fit inside the
building?" "Derek, it's just a--" "I don't want to hear your excuses!
The center has to be at least... three times bigger than this!" "...He's
absolutely right!" --Zoolander movie
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
J G Miller
> Just changing/messing the settings. None of them seem to show what I
> should be getting like I did in my other Windows PC like in the past. :(
Exactly: if you messs about with settings you will just get a mess.
> I assume that's a good sign?
Is there a reason to consider it a bad sign?
> Didn't I already do that back then?
No, in the screenshot it clearly shows that you launched xawtv without
the -nodga parameter and got an X Error complaining about no direct
video mode.
> Here's the results when I tried it:
"Results" is plural, so you should write "Here are ..."
> $ xawtv -nodga
> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686) xinerama
> 0: 1280x1024+0+0
> X Error of failed request: XF86DGANoDirectVideoMode
This indicates that xawtv is apparently ignoring the command line flag.
This could be due to one of a number of reasons which means you should
consider at least the following points
1) In the xawtv configuration file for the user, is there a setting explicitly
stating dga should be used which could be overriding the command line?
2) xawtv has an X11 application defaults file, in /etc/X11/app-defaults/xawtv
which may have an entry forcing the use of dga.
You should check the file and even if there is not an entry, put one in
xawtv.dga false
and try again with xawtv to see if the error message persists
3) There is a bug in the version of xawtv which you are using.
If none of the above works to force non dga, you may need to send an
e-mail to Axel Thimm requesting assistance on this matter.
If your xawtv is installed from a Debian package, before contacting
Axel Thimm, you should submit a bug report.
> v4l-conf had some trouble, trying to continue anyway
Have you read the man page for v4l-conf and tried running it manually to
set things up and to see if it complains?
> I am feeding from my old VCR.
Yes that is clear, but what are you playing on the VCR?
Also as another possible check of your installation, does your VCR have
a VHF/UHF modulator so that it could play out a video as a TV channel via
a coaxial cable to connect to the VCR?
> However, I never had problems with this TV tuner when it was in old,
> updated Windows XP Pro. SP3 with PowerVCR II.
You appear to prefer Windows anyways.
Ant
> > should be getting like I did in my other Windows PC like in the past. :(
> Exactly: if you messs about with settings you will just get a mess.
Yeah, that's not surprise. Even upgrading can mess with the settings
when I haven't changed any configurations manually. Ugh!
> > I assume that's a good sign?
> Is there a reason to consider it a bad sign?
I don't know. :)
> > Didn't I already do that back then?
> No, in the screenshot it clearly shows that you launched xawtv without
> the -nodga parameter and got an X Error complaining about no direct
> video mode.
> > Here's the results when I tried it:
> "Results" is plural, so you should write "Here are ..."
Oops, you're right. English isn't my strong area. :(
> > $ xawtv -nodga
> > This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686) xinerama
> > 0: 1280x1024+0+0
> > X Error of failed request: XF86DGANoDirectVideoMode
> This indicates that xawtv is apparently ignoring the command line flag.
> This could be due to one of a number of reasons which means you should
> consider at least the following points
> 1) In the xawtv configuration file for the user, is there a setting explicitly
> stating dga should be used which could be overriding the command line?
I assume these are configuration files for xawtv:
$ locate xawtv.conf
/var/lib/dpkg/info/xawtv.conffiles
/var/lib/dpkg/info/xawtv.config
$ ls -all /var/lib/dpkg/info/xawtv*
-rw-r--r-- 1 root root 28 Sep 5 13:30 /var/lib/dpkg/info/xawtv.conffiles
-rwxr-xr-x 1 root root 868 Sep 5 13:29 /var/lib/dpkg/info/xawtv.config
-rw-r--r-- 1 root root 1640 Dec 24 17:10 /var/lib/dpkg/info/xawtv.list
-rw-r--r-- 1 root root 2532 Sep 5 13:30 /var/lib/dpkg/info/xawtv.md5sums
-rw-r--r-- 1 root root 1537 Dec 24 17:10 /var/lib/dpkg/info/xawtv-plugins.list
-rw-r--r-- 1 root root 2918 Sep 5 13:30 /var/lib/dpkg/info/xawtv-plugins.md5sums
-rwxr-xr-x 1 root root 1239 Sep 5 13:30 /var/lib/dpkg/info/xawtv.postinst
-rwxr-xr-x 1 root root 349 Sep 5 13:30 /var/lib/dpkg/info/xawtv.postrm
-rw-r--r-- 1 root root 20176 Sep 5 13:29 /var/lib/dpkg/info/xawtv.templates
$ cat /var/lib/dpkg/info/xawtv.config
#!/bin/sh
# debconf lib
. /usr/share/debconf/confmodule
# init variables
mode="$1"
mkdev="true"
mkcfg="true"
tvnorm=""
freqtab=""
doscan=""
# create v4l devices ?
test -c /dev/.devfsd -o -c /dev/video0 && mkdev="false"
if test "$mkdev" = "true"; then
db_input medium xawtv/makedev
db_go
db_get xawtv/makedev
mkdev="$RET"
fi
# build xawtv config?
if test -s /etc/X11/xawtvrc; then
mkcfg="false"
fi
if test "$mode" = "reconfigure"; then
mkcfg="true"
fi
if test "$mkcfg" = "true"; then
db_input medium xawtv/build-config
db_go
db_get xawtv/build-config
mkcfg="$RET"
fi
if test "$mkcfg" = "true"; then
# configuration
db_input medium xawtv/tvnorm
db_go
db_get xawtv/tvnorm
tvnorm="$RET"
db_input medium xawtv/freqtab
db_go
db_get xawtv/freqtab
freqtab="$RET"
db_input medium xawtv/channel-scan
db_go
db_get xawtv/channel-scan
doscan="$RET"
fi
$ cat /var/lib/dpkg/info/xawtv.conffiles
/etc/X11/app-defaults/Xawtv
I did not see any dga references in that one.
> 2) xawtv has an X11 application defaults file, in /etc/X11/app-defaults/xawtv
> which may have an entry forcing the use of dga.
> You should check the file and even if there is not an entry, put one in
> xawtv.dga false
> and try again with xawtv to see if the error message persists
/etc/X11/app-defaults/Xawtv showed a long result. You can see it in
http://pastie.org/1426422 ... No dga in there too.
So I added "xawtv.dga false" line to the beginning of the file. I hope
that's OK. I made a backup copy of this file just in case I mess up
again. :P I can't test this change right now since I am not at the local
PC and doing this through SSH2. I will try running xawtv later. :)
> 3) There is a bug in the version of xawtv which you are using.
Interesting. I wonder why it hasn't been fixed. Where did you see this?
> If none of the above works to force non dga, you may need to send an
> e-mail to Axel Thimm requesting assistance on this matter.
OK.
> If your xawtv is installed from a Debian package, before contacting
> Axel Thimm, you should submit a bug report.
Yes, it is from Debian package:
$ apt-cache show xawtv
Package: xawtv
Priority: extra
Section: video
Installed-Size: 708
Maintainer: Krzysztof Burghardt <krzy...@burghardt.pl>
Architecture: i386
Source: xawtv (3.95.dfsg.1-8.1)
Version: 3.95.dfsg.1-8.1+b1
Depends: libasound2 (>> 1.0.18), libc6 (>= 2.7), libfontconfig1 (>=
2.8.0), libgl1-mesa-glx | libgl1, libice6 (>= 1:1.0.0), libjpeg62 (>=
6b1), liblircclient0, libncurses5 (>= 5.7+20100313), libpng12-0 (>=
1.2.13-4), libsm6, libx11-6, libxaw7, libxext6, libxft2 (>> 2.1.1),
libxinerama1, libxmu6, libxpm4, libxrandr2, libxrender1, libxt6, libxv1,
libxxf86dga1, libxxf86vm1, libzvbi0 (>= 0.2.11), zlib1g (>= 1:1.1.4),
debconf (>= 0.5) | debconf-2.0, v4l-conf, xutils, scantv, xawtv-plugins
(= 3.95.dfsg.1-8.1+b1), pia
Suggests: xawtv-plugin-qt (= 3.95.dfsg.1-8.1+b1), tv-fonts
Filename: pool/main/x/xawtv/xawtv_3.95.dfsg.1-8.1+b1_i386.deb
Size: 250424
MD5sum: a424f6f88c2edd7a836ec814907e192a
SHA1: 8eb20ec1a8cdaccf9f2175a3b90930d6297385e4
SHA256: 24945429f25cb3ef27acb04457e18b939826f34654c272691671a17fd92ec401
Description: television viewer - X11 application
XawTV is an X11 application which displays television channels. It
supports video4linux devices and the Xvideo extension.
Tag: hardware::video, role::program, scope::application,
uitoolkit::athena, uitoolkit::ncurses, use::playing, works-with::video,
x11::application
Package: xawtv
Priority: extra
Section: x11
Installed-Size: 704
Maintainer: Krzysztof Burghardt <krzy...@burghardt.pl>
Architecture: i386
Version: 3.95.dfsg.1-8
Depends: debconf (>= 0.5) | debconf-2.0, libasound2 (>> 1.0.14), libc6
(>= 2.7-1), libfontconfig1 (>= 2.4.0), libgl1-mesa-glx | libgl1, libice6
(>= 1:1.0.0), libjpeg62, liblircclient0, libncurses5 (>=
5.6+20071006-3), libpng12-0 (>= 1.2.13-4), libsm6, libx11-6, libxaw7,
libxext6, libxft2 (>> 2.1.1), libxinerama1, libxmu6, libxpm4, libxrandr2
(>= 2:1.2.0), libxrender1, libxt6, libxv1, libxxf86dga1, libxxf86vm1,
libzvbi0 (>= 0.2.11), pia, scantv, v4l-conf, xawtv-plugins (=
3.95.dfsg.1-8), xutils, zlib1g
Suggests: tv-fonts, xawtv-plugin-qt (= 3.95.dfsg.1-8)
Filename: pool/main/x/xawtv/xawtv_3.95.dfsg.1-8_i386.deb
Size: 247612
MD5sum: b1e8249ad089ef350611dfaebcdd9f9e
SHA1: 3421fb9113307baf01ee3e33e55484afbee4b485
SHA256: 0d82467726edbe7e332f932b03f38d31cf27d7cff077bbdc37cc76188f9f1e53
Description: television viewer - X11 application
XawTV is an X11 application which displays television channels. It
supports video4linux devices and the Xvideo extension.
Tag: hardware::video, role::program, scope::application,
uitoolkit::athena, uitoolkit::ncurses, use::playing, works-with::video,
x11::application
> > v4l-conf had some trouble, trying to continue anyway
> Have you read the man page for v4l-conf and tried running it manually to
> set things up and to see if it complains?
Just very briefly and it was too technical/overwhelming to understand
how to use it for my situation. :(
> > I am feeding from my old VCR.
> Yes that is clear, but what are you playing on the VCR?
From the VCR, my DTV Pal for live TV feeds, a VHS tape with recording,
and VCR's menus. None of those showed up.
> Also as another possible check of your installation, does your VCR have
> a VHF/UHF modulator so that it could play out a video as a TV channel via
> a coaxial cable to connect to the VCR?
Umm, I am not sure. All I know is the old CRT TV has one input (coax)
for antennae, cable, etc. VCR connects to this box. DTV Pal converter
box with its rabbit ears antenna connect to VCR for live TV. Then, I
have video and audio cables to the TV tuner.
> > However, I never had problems with this TV tuner when it was in old,
> > updated Windows XP Pro. SP3 with PowerVCR II.
> You appear to prefer Windows anyways.
I use Mac OS X too. I prefer to use all. :)
I think I forgot to mention my VCR brand and model earlier: Toshiba
W-627. I can't find any photographs/photos. of the rear. I will probably
have to take digital pictures of mine if you need them. I did find a 1
MB PDF manual, with drawings, if you're interested:
http://tacpservice.toshiba.com/ConsumerProductSupport/Manuals/vcr/w627_ownman.pdf
... :D
--
Quote of the Week: "It doesn't matter what your D&D manual says, you did
not get 5 experience points for killing the giant ant in your kitchen."
--BBspot's Geek Horoscopes (7/30/2004)
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.
J G Miller
>> 1) In the xawtv configuration file for the user, is there a setting
>> explicitly
>> stating dga should be used which could be overriding the command
>> line?
>
> I assume these are configuration files for xawtv:
>
> $ locate xawtv.conf
> /var/lib/dpkg/info/xawtv.conffiles
> /var/lib/dpkg/info/xawtv.config
...
No I said the xawtv configuration file for the user, not dpkg configuration
files for the installation of xawtv.
The xawtv configuration file for the user, if it has been created, will
be in ${HOME}/.xawtv. The system wide one, if it exists is /etc/xawtvrc.
See the manual page for xawtvrc
user_prompt> man 5 xawtvrc
Also at <http://linux.die.net/man/5/xawtvrc>
> So I added "xawtv.dga false" line to the beginning of the file. I hope
> that's OK.
Yes that should be fine.
> I made a backup copy of this file just in case I mess up again.
That is a wise policy to follow. What I do, because I heavily customize
is alter configuration files on my system is to make a copy of the file
under an equivalent file hierarchy at /usr/local/archive. Then when a
new update for the package arrives, I can compare the new configuration
file with the old in order to ascertain if I need to make any changes
to my installed version.
> Interesting. I wonder why it hasn't been fixed. Where did you see this?
I did not say that there was a bug, but that there may be a bug since I
do not understand why invoking xawtv -nodga still appears to be
giving the error because it is trying to use dga.
> Yes, it is from Debian package:
So have you checked the Debian bugs page for this package to see if
there are any reported bugs related to your problem?
Which version of Xorg X11 server are you running?
Have you read this bug report from Friday, May 5th, 2006 at 17:19:07h +0200
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=366144>
which is still unresolved?
If you are using Xorg X11 server version 7 or above, since you are using
xawtv version 3.95.dfsg.1-8.1+b1, it looks like you will have to change to
xawtv version 4 and above.
> All I know is the old CRT TV has one input (coax) for antennae, cable, etc.
> VCR connects to this box. DTV Pal converter box with its rabbit ears antenna
> connect to VCR for live TV. Then, I have video and audio cables to the TV tuner.
I asked about the output from the VCR not the TV input.
> http://tacpservice.toshiba.com/ConsumerProductSupport/Manuals/vcr/w627_ownman.pdf
So did you look at Page 9 which shows an RF output jack and a switch to select
whether to modulate the signal on the RF output jack either on VHF Channel 3
or VHF Channel 4?
Hope that helps to put you in the picture.
Kevin Snodgrass
>> This indicates that xawtv is apparently ignoring the command line flag.
>
>> This could be due to one of a number of reasons which means you should
>> consider at least the following points
>
>> 1) In the xawtv configuration file for the user, is there a setting
>> explicitly
>> stating dga should be used which could be overriding the command
>> line?
>
> I assume these are configuration files for xawtv:
As Mr. Miller pointed out earlier this afternoon, these are the package
config files. Look in your home directory, something like ~/.xawtv. Try
doing this:
$ ls -al ~/.xawtv*
And see what shows up.
>> If none of the above works to force non dga, you may need to send an
>> e-mail to Axel Thimm requesting assistance on this matter.
>
> OK.
Axel is a very bright coder. He has his own package repository for
RedHat/Fedora and it's cousins at http://atrpms.net/ . But you use
Debian, so that doesn't really matter. Didn't know he had anything to do
with xawtv, though...
>> If your xawtv is installed from a Debian package, before contacting
>> Axel Thimm, you should submit a bug report.
>
> Yes, it is from Debian package:
> $ apt-cache show xawtv
> Package: xawtv
> Priority: extra
> Section: video
> Installed-Size: 708
> Maintainer: Krzysztof Burghardt <krzy...@burghardt.pl> Architecture:
And that is the maintainer, of your package.
> Version: 3.95.dfsg.1-8.1+b1
I see from http://packages.debian.org/search?keywords=xawtv that this is
the most recent version available on debian. I think Mr. Miller
suggested upgrading to Version 4.x, which doesn't show up anywhere in the
search results. Therefore, I guess you are stuck with this one.
>> > v4l-conf had some trouble, trying to continue anyway
>
>> Have you read the man page for v4l-conf and tried running it manually
>> to set things up and to see if it complains?
>
> Just very briefly and it was too technical/overwhelming to understand
> how to use it for my situation. :(
Something isn't right with v4l and/or xawtv communication to v4l. Not a
debian user, not an xawtv user so I'm at a loss on how to proceed.
But I did look at the online man page for xawtv here:
http://linux.die.net/man/1/xawtv
Things that might be interesting and enlightening are:
1) Run xawtv from the command line like this:
$ xawtv -hwscan
This might provide some clue. Depends on how detailed the information...
2) Run xawtv from the command line like this:
$ xawtv -device /dev/video0 -debug 2
Then run it like this:
$ xawtv -debug 2
Reasoning: From the man page it says the specifying the device on the
command line disables Xvideo support. This might force it to use dga to
have an output path. I'm not sufficiently versed in X to know if that
even makes sense, just something *I* would try...
The "-debug 2" parameter should show max debug info. It could be
useful...
Then I read the xawtvrc man page at:
http://linux.die.net/man/5/xawtvrc
This is valid both for the system wide config file at /etc/X11/xawtvrc
and $HOME/.xawtv . If it was me. I would only modify $HOME/.xawtv since
if that make things all FUBAR, it can be deleted and start over.
From the man page:
"Applications
The following applications use these config files:
xawtv
The classic X11 TV application.
motv
A better, motif-based GUI for xawtv ... "
Just a shot, but maybe motv will be easier to work with.
Options you may want to include in the $HOME/.xawtv config file:
norm = ntsc
#input = Television
input = Composite1
#input = Composite2
Depending on which cables you have connected will alter the "input ="
line to uncomment. According to the man page:
"The valid choices depend on the hardware driver, the values above are
just examples. You can use "v4lctl list" to get a list of valid choices."
If you have the v4lctl program run it (as "v4lctl list") and show the
output.
>> > I am feeding from my old VCR.
>
>> Yes that is clear, but what are you playing on the VCR?
>
> From the VCR, my DTV Pal for live TV feeds, a VHS tape with recording,
> and VCR's menus. None of those showed up.
Just for clarification, the "DTV Pal" device has NOTHING to do with the
PAL TV standard used in Europe. This is a device sold by DishNetwork to
allow analogue TVs to receive the new Federally dictated digital TV
signals. I.e., a digital TV converter box.
<rant>
Really torques me off when a company names their product with a confusing
name when trying to be "cute". "DTV Pal", as in "DTV Best Friend" or "DTV
Buddy". Since "PAL" is the analogue broadcast standard used in Europe,
naming a device "DTV Pal" causes confusion for some who actually know
about the different standards since it has *NOTHING* to do with PAL, it
is just your "friend". [rolls eyes]
</rant>
>> Also as another possible check of your installation, does your VCR have
>> a VHF/UHF modulator so that it could play out a video as a TV channel
>> via a coaxial cable to connect to the VCR?
>
> Umm, I am not sure. All I know is the old CRT TV has one input (coax)
> for antennae, cable, etc. VCR connects to this box. DTV Pal converter
> box with its rabbit ears antenna connect to VCR for live TV. Then, I
> have video and audio cables to the TV tuner.
What he is asking here is "Does your VCR have a coax output?" Most do
and if I remember correctly you said that was how it was hooked up to
your TV.
This may be useful if you can't get anything working with the S-video/
composite cabling. But you will have to move the coax cable from the TV
to the tuner card.
J G Miller
> Didn't know he had anything to do with xawtv, though...
Axel Thimm is a major contributor to the video4linux mailing list and
has done a lot of work with xawtv.
However I got the attribution wrong, and I should have said "Gerd Knorr"
who is the principle author of xawtv and much of the bttv/v4l software,
including the cx88 modules which is highly relevant to this discussion.
> I see from http://packages.debian.org/search?keywords=xawtv that this is
> the most recent version available on debian.
Even Debian Unstable (sid) is on the same version, so time to download
the source, unpack, configure and compile? ;)
> but maybe motv will be easier to work with.
It will need the openmotif libraries installing though.
However, just changing the appearance of the application from
X11 library to Motif is probably not going to do anything for
the problem of the X11 video extension / dga display error.
> Something isn't right with v4l and/or xawtv communication to v4l.
Indeed -- could be something to do with the reported issue with Xorg
X11 version 7 server.
> Reasoning: From the man page it says the specifying the device on the
> command line disables Xvideo support. This might force it to use dga to
> have an output path.
Eh? I think you are missing the point that we do not want xawtv to use
dga because the latest video cards no longer have the dga capability,
as explained in an earlier message.
> Really torques me off when a company names their product with a
> confusing name when trying to be "cute". "DTV Pal", as in "DTV Best
> Friend" or "DTV Buddy".
> Since "PAL" is the analogue broadcast standard used in Europe
But most Americans will not know their PAL from their SECAM,
only NTSC and ATSC, and even then, probably the vast majority
do not know what those initialisms actually mean.
> naming a device "DTV Pal"
Is cute and hopefully sells more units, which is about the only
thing that they are really concerned.
> What he is asking here is "Does your VCR have a coax output?" Most do
As confirmed on Page 9 of the instruction manual.
> This may be useful if you can't get anything working with the S-video/
> composite cabling.
Exactly -- this is a good test to see if the demodulation side of the
card is working and that the kernel module and xawtv are at least
correctly configured for that.
Ant
> The xawtv configuration file for the user, if it has been created, will
> be in ${HOME}/.xawtv. The system wide one, if it exists is /etc/xawtvrc.
# locate .xawtv
# ls /etc/xawtvrc
ls: cannot access /etc/xawtvrc: No such file or directory
# ls /etc/xawtv*
ls: cannot access /etc/xawtv*: No such file or directory
# locate xawtvrc
/usr/share/man/man5/xawtvrc.5.gz
I assume the gzipped one has it so I extracted it. Here is what it says
untouched by me:
$ cat xawtvrc.5
.TH xawtvrc 5
.SH NAME
xawtvrc -- TV apps config file
.SH SYNOPSIS
/etc/X11/xawtvrc
.br
$HOME/.xawtv
.SH DESCRIPTION
.B xawtvrc
is the config file originally used by xawtv only (that's why the name
xawtvrc). These days a number of other TV applications / utilities
read it too to get configuration information from it.
.P
Both a global (/etc/X11/xawtvrc) and personal ($HOME/.xawtv) config
file are used by the applications. Settings in the personal config
file will overwrite the global ones.
.SS Applications
The following applications use these config files:
.TP
.B xawtv
The classic X11 TV application.
.TP
.B motv
A better, motif-based GUI for xawtv ...
.TP
.B fbtv
TV application for the linux framebuffer console.
.TP
.B ttv
aalib-based TV application for any terminal.
.TP
.B v4lctl
command line tool to control video4linux devices.
.SS Create a config file
.B xawtv
and
.B motv
both provide some functions to edit the channels and save the
configuration. The save function will \fBnot\fP preserve any comments
you might have put into the config file throught ...
.P
You can also use your favorite text editor and modify the config file
directly.
.P
You can use the command line utility
.B scantv
to create a initial config file. scantv will automatically scan all
channels for TV stations and write the ones it has found to the config
file.
.SH SYNTAX
.B xawtvrc
uses the same syntax like smb.conf: sections starting with [name],
followed by lines with option = value pairs.
.P
There are four special sections: [global], [launch], [eventmap] and
[defaults]. All other sections describe a TV station each.
.SS TV station options.
The following options are allowed for TV stations and the [defaults]
section. The options from the [defaults] sections are used -- as the
name suggests -- as defaults for all other channels. You can put
everything which is common for all TV stations (like the TV norm which
is used in your country) into the [defaults] section, so you don't have
to specify it for every single channel.
.P
With a reasonable [defaults] section you usually only need to specify
the channel for each TV station, like this:
.nf
[ORB]
channel = 27
.fi
The other options are:
.TP
.B fine = n
finetuning (what left+right keys do within xawtv), default: 0
.TP
.B norm = pal | ntsc | secam
which TV norm, default is pal
.TP
.B key = keysym
Hotkey for the channel. All X11 keysyms allowed here. You can prefix
a keysym with Modifier+, "Ctrl+F" for example.
.TP
.B capture = off | overlay | grabdisplay
capture mode: off, overlay (default, TV card => video, 0% cpu) or
grabdisplay (TV card => main memory => X-Server => video, frame rate
depends on load and picture size). Default is overlay. If it is not
possible to use overlay for some reason (remote display, not supported
by the hardware, whatever) the applications will automatically fallback
to grabdisplay.
.TP
.B input = Television | Composite1 | Composite2 | SVHS
input source. The valid choices depend on the hardware driver, the
values above are just examples. You can use "v4lctl list" to get a
list of valid choices.
.TP
.B color = n
.TP
.B bright = n
.TP
.B hue = n
.TP
.B contrast = n
Valid range is 0-65535, default is 32768. Adding a percent symbol
changes the range to 0-100, i.e. "50%" has the same effect like
"32768".
.TP
.B audio = mono | stereo | lang1 | lang2
Set the audio mode for the given channel.
.TP
.B freq = n
Specify the frequency for the given station (MHz, video carrier). You
shouldn't need this for normal operation, all your channels should be
listed in the frequency table for your area (if not, mail me a patch).
Maybe unless you live near the border and the foreign country uses
another channel scheme.
.TP
.B midi = note
Use midi noteon event for <note> as hotkey for the channel.
.TP
.B group = name
Put the channel into the group <name>. motv uses that to create
submenus per channel group.
.P
.SS Global options
A number of not channel-related settings go to the "[global]" section:
.TP
.B fullscreen = width x height
specify which video mode should be used for full-screen. Works with
XFree only, and of course you need a valid modeline for this mode in
your XF86Config file. You also have to enable the VidMode extension
(option -vm, see above) to make this work.
.TP
.B wm-off-by = [+-]x[+-]y
Some WM's handle static gravity incorrectly (I know mwm and
kwm). This is somewhat boring with fullscreen mode. With this
option you can correct this with a displacement for moving
windows. For example, wm-off-by = -4-24 does the trick for kwm (the
KDE1 window manager).
.TP
.B freqtab =
select a channel-to-freqency mapping. Options window->Frequency table
(in xawtv) brings up a menu with all valid entries (and allows
table-switching at runtime).
.TP
.B pixsize = width x height
size of the channel pixmaps (within Channels window). 0x0 disables this
feature.
.TP
.B pixcols = n
number of columns the channel window should use. Defaults to 1.
.TP
.B mixer = ctl | device:ctl
This allows volume control using the sound card mixer. ctl is the
mixer control, i.e. "vol" for the master volume. "line1" is a good
candidate for the TV card. device is the mixer device (defaults to
/dev/mixer in unspecified). Volume-control works with the keypad: +
is up, - is down, Enter is mute.
.TP
.B jpeg-quality = n
set the quality for (M)JPEG images/frames. As usual the valid range
for n is [0 .. 100] with 75 as default.
.TP
.B keypad-ntsc = on | off
Configure keypad mode. Default is off. When set to on, numbers typed
on the keypad are interpreted as channel numbers (this is like NTSC TV
sets work). Otherwise they are interpreted as programmed station,
i.e. 1 is the first station from $HOME/.xawtv, ...
.TP
.B keypad-partial = on | off
Another configuration of keypad mode. Default is on. When set to off,
typing one digit on the keypad doesn't change the station number when
there are two-digit station numbers starting with that digit.
.TP
.B osd = on | off
Enable/disable the onscreen display in fullscreen mode. Default is
on.
.TP
.B osd-position = x , y
Position the onscreen display, in pixels. Default is 30,20.
.TP
.B use-wm-fullscreen = on | off
Enter fullscreen mode by asking the window manager to handle that via
_NET_WM_STATE_FULLSCREEN (if supported by the wm). Default is on.
.TP
.B ratio = x:y
Set a fixed aspect ratio for the TV image. Default is 4:3. Use 0:0
if you don't want a fixed aspect ratio.
.TP
.B mov-driver = files | raw | avi | mov
.TP
.B mov-video = ppm | pgm | jpeg | rgb | gray | 422 | 422p | rgb15 |
rgb24 | mjpeg | jpeg | raw | mjpa | png
.TP
.B mov-fps = fps
.TP
.B mov-audio = mono8 | mono16 | stereo
.TP
.B mov-rate = rate
Set defaults for movie recording. Not all possible combinations are
valid choices. "streamer -h" will print a nice list.
.TP
.B midi = port
You can specify a ALSA port where xawtv should receive midi events
from. If configured this way, you can program your midi keyboard keys
as station hotkeys and use midi controller events to control settings
like volume, bright etc. Check the [eventmap] description below for
details.
.TP
.B filter = name
Enable the specified filter.
.SS The [launch] section
You can start other programs from within xawtv. This is configured
with entries in the "[launch]" section:
.TP
.B label = key, command line
The specified hotkey will run the configured program. Calling the
Action "Launch(label)" works too. If you want to play with the Xt
translation tables, feel free to do so. But don't complain if you
broke something while doing so...
.SS The [eventmap] section
The eventmap simply has a number of "event = action" lines. "action"
can be any command which xawtv understands (check the xawtv-remote man
page for a list). "event" is some event generated by any input device
xawtv listens to. An event might have some argument, the midi-ctrl
events for example have one. If present the argument is appended to
the action.
.P
There are default mappings for lirc and joystick input events, so you
don't have to create an eventmap to use them. But if you don't like
the defaults you can change them easily.
.P
Here is a list of valid events:
.TP
.B lirc-key-<name>
The key <name> was pressed on the IR remote control.
.TP
.B joy-button-<n>
Joystick button <n> was pressed.
.TP
.B joy-axis-<left|right|up|down>
Joystick was moved into the given direction.
.TP
.B midi-note-<n>
noteon event for note <n> was received (i.e. you probably pressed some
key on the midi keyboard).
.TP
.B midi-ctrl-<n>
midi controller message for control <n> was received. This event has
an argument (the current value of the control).
.TP
.B kbd-key-<name>
Key <name> was pressed on the keyboard.
.SS sample config file
.nf
# this is a comment
# empty lines are ignored too
[global]
freqtab = europe-west
#mixer = line
jpeg-quality = 75
midi = 64:0
fullscreen = 768x576
# for /etc/XF86Config
# Modeline "pal" 50.00 768 832 856 1000 576 590 595 630 -hsync -vsync
[launch]
mixer = M, gtkaumix
AleVT = Ctrl+A, alevt
[eventmap]
midi-ctrl-7 = volume
kbd-key-h = msg "hello world"
[defaults]
input = television
norm = pal
[ZDF]
channel=33
key=F1
[ORB]
channel = 27
key = F2
# more stations follow here
[Camera]
input = Composite1
key = K
.fi
.SH SEE ALSO
scantv(1), xawtv(1), motv(1), fbtv(1), ttv(1), v4lctl(1)
I renamed and moved it to ~/.xawtv. I tried it and got plenty of new errors:
$ xawtv
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
/home/ant/.xawtv:1: syntax error
/home/ant/.xawtv:2: syntax error
/home/ant/.xawtv:3: syntax error
/home/ant/.xawtv:4: syntax error
/home/ant/.xawtv:5: syntax error
/home/ant/.xawtv:6: syntax error
/home/ant/.xawtv:7: syntax error
/home/ant/.xawtv:8: syntax error
/home/ant/.xawtv:9: syntax error
/home/ant/.xawtv:10: syntax error
/home/ant/.xawtv:11: syntax error
/home/ant/.xawtv:12: syntax error
/home/ant/.xawtv:13: syntax error
/home/ant/.xawtv:14: syntax error
/home/ant/.xawtv:15: syntax error
/home/ant/.xawtv:16: syntax error
/home/ant/.xawtv:17: syntax error
/home/ant/.xawtv:18: syntax error
/home/ant/.xawtv:19: syntax error
/home/ant/.xawtv:20: syntax error
/home/ant/.xawtv:21: syntax error
/home/ant/.xawtv:22: syntax error
/home/ant/.xawtv:23: syntax error
/home/ant/.xawtv:24: syntax error
/home/ant/.xawtv:25: syntax error
/home/ant/.xawtv:26: syntax error
/home/ant/.xawtv:27: syntax error
/home/ant/.xawtv:28: syntax error
/home/ant/.xawtv:29: syntax error
/home/ant/.xawtv:30: syntax error
/home/ant/.xawtv:31: syntax error
/home/ant/.xawtv:32: syntax error
/home/ant/.xawtv:33: syntax error
/home/ant/.xawtv:34: syntax error
/home/ant/.xawtv:35: syntax error
/home/ant/.xawtv:36: syntax error
/home/ant/.xawtv:37: syntax error
/home/ant/.xawtv:38: syntax error
/home/ant/.xawtv:39: syntax error
/home/ant/.xawtv:40: syntax error
/home/ant/.xawtv:41: syntax error
/home/ant/.xawtv:42: syntax error
/home/ant/.xawtv:43: syntax error
/home/ant/.xawtv:44: syntax error
/home/ant/.xawtv:45: syntax error
/home/ant/.xawtv:46: syntax error
/home/ant/.xawtv:47: syntax error
/home/ant/.xawtv:48: syntax error
/home/ant/.xawtv:49: syntax error
/home/ant/.xawtv:50: syntax error
/home/ant/.xawtv:51: syntax error
/home/ant/.xawtv:52: syntax error
/home/ant/.xawtv:53: syntax error
/home/ant/.xawtv:54: syntax error
/home/ant/.xawtv:55: syntax error
/home/ant/.xawtv:57: syntax error
/home/ant/.xawtv:58: syntax error
/home/ant/.xawtv:59: syntax error
/home/ant/.xawtv:60: syntax error
/home/ant/.xawtv:61: syntax error
/home/ant/.xawtv:62: syntax error
/home/ant/.xawtv:63: syntax error
/home/ant/.xawtv:64: syntax error
/home/ant/.xawtv:65: syntax error
/home/ant/.xawtv:66: syntax error
/home/ant/.xawtv:68: syntax error
/home/ant/.xawtv:71: syntax error
/home/ant/.xawtv:73: syntax error
/home/ant/.xawtv:74: syntax error
/home/ant/.xawtv:75: syntax error
/home/ant/.xawtv:76: syntax error
/home/ant/.xawtv:77: syntax error
/home/ant/.xawtv:78: syntax error
/home/ant/.xawtv:79: syntax error
/home/ant/.xawtv:80: syntax error
/home/ant/.xawtv:81: syntax error
/home/ant/.xawtv:82: syntax error
/home/ant/.xawtv:83: syntax error
/home/ant/.xawtv:84: syntax error
/home/ant/.xawtv:85: syntax error
/home/ant/.xawtv:86: syntax error
/home/ant/.xawtv:87: syntax error
/home/ant/.xawtv:88: syntax error
/home/ant/.xawtv:89: syntax error
/home/ant/.xawtv:90: syntax error
/home/ant/.xawtv:91: syntax error
/home/ant/.xawtv:92: syntax error
/home/ant/.xawtv:93: syntax error
/home/ant/.xawtv:94: syntax error
/home/ant/.xawtv:95: syntax error
/home/ant/.xawtv:96: syntax error
/home/ant/.xawtv:97: syntax error
/home/ant/.xawtv:98: syntax error
/home/ant/.xawtv:99: syntax error
/home/ant/.xawtv:100: syntax error
/home/ant/.xawtv:101: syntax error
/home/ant/.xawtv:102: syntax error
/home/ant/.xawtv:103: syntax error
/home/ant/.xawtv:104: syntax error
/home/ant/.xawtv:105: syntax error
/home/ant/.xawtv:106: syntax error
/home/ant/.xawtv:107: syntax error
/home/ant/.xawtv:108: syntax error
/home/ant/.xawtv:109: syntax error
/home/ant/.xawtv:110: syntax error
/home/ant/.xawtv:111: syntax error
/home/ant/.xawtv:112: syntax error
/home/ant/.xawtv:113: syntax error
/home/ant/.xawtv:114: syntax error
/home/ant/.xawtv:115: syntax error
/home/ant/.xawtv:116: syntax error
/home/ant/.xawtv:117: syntax error
/home/ant/.xawtv:118: syntax error
/home/ant/.xawtv:119: syntax error
/home/ant/.xawtv:120: syntax error
/home/ant/.xawtv:121: syntax error
/home/ant/.xawtv:122: syntax error
/home/ant/.xawtv:123: syntax error
/home/ant/.xawtv:124: syntax error
/home/ant/.xawtv:125: syntax error
/home/ant/.xawtv:126: syntax error
/home/ant/.xawtv:127: syntax error
/home/ant/.xawtv:128: syntax error
/home/ant/.xawtv:129: syntax error
/home/ant/.xawtv:130: syntax error
/home/ant/.xawtv:131: syntax error
/home/ant/.xawtv:132: syntax error
/home/ant/.xawtv:133: syntax error
/home/ant/.xawtv:134: syntax error
/home/ant/.xawtv:135: syntax error
/home/ant/.xawtv:136: syntax error
/home/ant/.xawtv:137: syntax error
/home/ant/.xawtv:138: syntax error
/home/ant/.xawtv:139: syntax error
/home/ant/.xawtv:140: syntax error
/home/ant/.xawtv:141: syntax error
/home/ant/.xawtv:142: syntax error
/home/ant/.xawtv:143: syntax error
/home/ant/.xawtv:144: syntax error
/home/ant/.xawtv:145: syntax error
/home/ant/.xawtv:146: syntax error
/home/ant/.xawtv:147: syntax error
/home/ant/.xawtv:148: syntax error
/home/ant/.xawtv:149: syntax error
/home/ant/.xawtv:150: syntax error
/home/ant/.xawtv:151: syntax error
/home/ant/.xawtv:152: syntax error
/home/ant/.xawtv:153: syntax error
/home/ant/.xawtv:154: syntax error
/home/ant/.xawtv:155: syntax error
/home/ant/.xawtv:156: syntax error
/home/ant/.xawtv:157: syntax error
/home/ant/.xawtv:158: syntax error
/home/ant/.xawtv:159: syntax error
/home/ant/.xawtv:160: syntax error
/home/ant/.xawtv:161: syntax error
/home/ant/.xawtv:162: syntax error
/home/ant/.xawtv:163: syntax error
/home/ant/.xawtv:164: syntax error
/home/ant/.xawtv:165: syntax error
/home/ant/.xawtv:166: syntax error
/home/ant/.xawtv:167: syntax error
/home/ant/.xawtv:168: syntax error
/home/ant/.xawtv:169: syntax error
/home/ant/.xawtv:170: syntax error
/home/ant/.xawtv:171: syntax error
/home/ant/.xawtv:172: syntax error
/home/ant/.xawtv:173: syntax error
/home/ant/.xawtv:174: syntax error
/home/ant/.xawtv:175: syntax error
/home/ant/.xawtv:176: syntax error
/home/ant/.xawtv:177: syntax error
/home/ant/.xawtv:178: syntax error
/home/ant/.xawtv:179: syntax error
/home/ant/.xawtv:180: syntax error
/home/ant/.xawtv:181: syntax error
/home/ant/.xawtv:182: syntax error
/home/ant/.xawtv:183: syntax error
/home/ant/.xawtv:184: syntax error
/home/ant/.xawtv:185: syntax error
/home/ant/.xawtv:186: syntax error
/home/ant/.xawtv:187: syntax error
/home/ant/.xawtv:188: syntax error
/home/ant/.xawtv:189: syntax error
/home/ant/.xawtv:190: syntax error
/home/ant/.xawtv:191: syntax error
/home/ant/.xawtv:192: syntax error
/home/ant/.xawtv:193: syntax error
/home/ant/.xawtv:194: syntax error
/home/ant/.xawtv:195: syntax error
/home/ant/.xawtv:196: syntax error
/home/ant/.xawtv:197: syntax error
/home/ant/.xawtv:198: syntax error
/home/ant/.xawtv:199: syntax error
/home/ant/.xawtv:200: syntax error
/home/ant/.xawtv:201: syntax error
/home/ant/.xawtv:202: syntax error
/home/ant/.xawtv:203: syntax error
/home/ant/.xawtv:204: syntax error
/home/ant/.xawtv:205: syntax error
/home/ant/.xawtv:206: syntax error
/home/ant/.xawtv:207: syntax error
/home/ant/.xawtv:208: syntax error
/home/ant/.xawtv:209: syntax error
/home/ant/.xawtv:210: syntax error
/home/ant/.xawtv:211: syntax error
/home/ant/.xawtv:212: syntax error
/home/ant/.xawtv:213: syntax error
/home/ant/.xawtv:214: syntax error
/home/ant/.xawtv:215: syntax error
/home/ant/.xawtv:216: syntax error
/home/ant/.xawtv:217: syntax error
/home/ant/.xawtv:218: syntax error
/home/ant/.xawtv:219: syntax error
/home/ant/.xawtv:220: syntax error
/home/ant/.xawtv:221: syntax error
/home/ant/.xawtv:222: syntax error
/home/ant/.xawtv:223: syntax error
/home/ant/.xawtv:224: syntax error
/home/ant/.xawtv:225: syntax error
/home/ant/.xawtv:226: syntax error
/home/ant/.xawtv:227: syntax error
/home/ant/.xawtv:228: syntax error
/home/ant/.xawtv:229: syntax error
/home/ant/.xawtv:230: syntax error
/home/ant/.xawtv:231: syntax error
/home/ant/.xawtv:232: syntax error
/home/ant/.xawtv:233: syntax error
/home/ant/.xawtv:234: syntax error
/home/ant/.xawtv:235: syntax error
/home/ant/.xawtv:236: syntax error
/home/ant/.xawtv:237: syntax error
/home/ant/.xawtv:238: syntax error
/home/ant/.xawtv:239: syntax error
/home/ant/.xawtv:240: syntax error
/home/ant/.xawtv:241: syntax error
/home/ant/.xawtv:242: syntax error
/home/ant/.xawtv:243: syntax error
/home/ant/.xawtv:244: syntax error
/home/ant/.xawtv:245: syntax error
/home/ant/.xawtv:246: syntax error
/home/ant/.xawtv:247: syntax error
/home/ant/.xawtv:248: syntax error
/home/ant/.xawtv:249: syntax error
/home/ant/.xawtv:250: syntax error
/home/ant/.xawtv:251: syntax error
/home/ant/.xawtv:252: syntax error
/home/ant/.xawtv:253: syntax error
/home/ant/.xawtv:254: syntax error
/home/ant/.xawtv:255: syntax error
/home/ant/.xawtv:294: syntax error
/home/ant/.xawtv:296: syntax error
/home/ant/.xawtv:297: syntax error
midi: snd_seq_subscribe_port: Invalid argument
config: invalid value for norm: pal
valid choices for "norm": "NTSC-M", "NTSC-M-JP", "NTSC-443", "PAL-BG",
"PAL-I", "PAL-DK", "PAL-M", "PAL-N", "PAL-Nc", "PAL-60", "SECAM-B",
"SECAM-G", "SECAM-H", "SECAM-DK", "SECAM-L"
config: invalid value for input: Composite1
valid choices for "input": "Television", "S-Video"
Um, is this file correct?
> See the manual page for xawtvrc
>
> user_prompt> man 5 xawtvrc
>
> Also at<http://linux.die.net/man/5/xawtvrc>
Ooh, new commands to try:
motv A better, motif-based GUI for xawtv ...
fbtv TV application for the linux framebuffer console.
ttv aalib-based TV application for any terminal.
I couldn't find motv in Debian's apt-get. fbtv gave me an error:
$ fbtv
using linux console font "/usr/share/consolefonts/lat1-16.psf.gz"
ioctl VT_GETSTATE: Invalid argument (not a linux console?)
Isn't my old KDE v3.5.10's Terminal considered a Linux console?
>> So I added "xawtv.dga false" line to the beginning of the file. I hope
>> that's OK.
>
> Yes that should be fine.
OK. That doesn't seem to make any differences.
>> Interesting. I wonder why it hasn't been fixed. Where did you see this?
>
> I did not say that there was a bug, but that there may be a bug since I
> do not understand why invoking xawtv -nodga still appears to be
> giving the error because it is trying to use dga.
OK.
>> Yes, it is from Debian package:
>
> So have you checked the Debian bugs page for this package to see if
> there are any reported bugs related to your problem?
Not yet.
> Which version of Xorg X11 server are you running?
$ dpkg -l | grep ^ii |grep Xorg
ii xserver-xorg-core 2:1.7.7-10
Xorg X server - core server
> Have you read this bug report from Friday, May 5th, 2006 at 17:19:07h +0200
>
> <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=366144>
>
> which is still unresolved?
>
> If you are using Xorg X11 server version 7 or above, since you are using
> xawtv version 3.95.dfsg.1-8.1+b1, it looks like you will have to change to
> xawtv version 4 and above.
Hmm, I will have to find a newer Debian package of it. Is xawtv not
popular or something?
>> All I know is the old CRT TV has one input (coax) for antennae, cable, etc.
>> VCR connects to this box. DTV Pal converter box with its rabbit ears antenna
>> connect to VCR for live TV. Then, I have video and audio cables to the TV tuner.
>
> I asked about the output from the VCR not the TV input.
>
>> http://tacpservice.toshiba.com/ConsumerProductSupport/Manuals/vcr/w627_ownman.pdf
>
> So did you look at Page 9 which shows an RF output jack and a switch to select
> whether to modulate the signal on the RF output jack either on VHF Channel 3
> or VHF Channel 4?
>
> Hope that helps to put you in the picture.
I always used channel 3 and is still channel 3.
FYI for more clues? I tried a bunch of parameters in xawtv:
$ xawtv -hwscan
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
looking for available devices
port 310-341
type : Xvideo, image scaler
name : NV17 Video Texture
/dev/video0: OK [ -device /dev/video0 ]
type : v4l2
name : ASUS PVR-416
flags: capture tuner
PVR-416? Is that right?
$ xawtv -fb
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
ioctl VT_GETSTATE: Invalid argument
v4l-conf had some trouble, trying to continue anyway
$ xawtv -xv
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
$ xawtv -noxv
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
$ xawtv -xv-video
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
$ xawtv -noxv-video
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
$ xawtv -xv-image
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
$ xawtv -noxv-image
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
$ xawtv -vm
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
$ xawtv -novm
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
$ xawtv -nodga
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 15
Current serial number in output stream: 15
v4l-conf had some trouble, trying to continue anyway
$ xawtv -dga
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 69
Current serial number in output stream: 69
$ xawtv -dga
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
xinerama 0: 1280x1024+0+0
X Error of failed request: XF86DGANoDirectVideoMode
Major opcode of failed request: 130 (XFree86-DGA)
Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
Serial number of failed request: 69
Current serial number in output stream: 69
I am going to go have to look at http://bytesex.org/xawtv/ later on. I
wished it had a forum. Its FAQs were not helpful. :(
Also, I noticed dmesg no wonder shows errors about my TV tuner like last
week. Weird.
--
"Yeah, what's left of it. I was in the militia -- national guard...
That's good! Wasn't any war any more than there's war between men and
ants." --stranger; "And we're eat-able ants. I found that out... What
will they do with us?" --Pierson from H.G. Wells' The War of the Worlds
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
Ant
> As Mr. Miller pointed out earlier this afternoon, these are the package
> config files. Look in your home directory, something like ~/.xawtv. Try
> doing this:
> $ ls -al ~/.xawtv*
>
> And see what shows up.
I had none. :(
>> Version: 3.95.dfsg.1-8.1+b1
>
> I see from http://packages.debian.org/search?keywords=xawtv that this is
> the most recent version available on debian. I think Mr. Miller
> suggested upgrading to Version 4.x, which doesn't show up anywhere in the
> search results. Therefore, I guess you are stuck with this one.
:( I wonder if there are any Debian packages outside of there.
>>>> v4l-conf had some trouble, trying to continue anyway
>>
>>> Have you read the man page for v4l-conf and tried running it manually
>>> to set things up and to see if it complains?
>>
>> Just very briefly and it was too technical/overwhelming to understand
>> how to use it for my situation. :(
>
> Something isn't right with v4l and/or xawtv communication to v4l. Not a
> debian user, not an xawtv user so I'm at a loss on how to proceed.
>
> But I did look at the online man page for xawtv here:
> http://linux.die.net/man/1/xawtv
>
> Things that might be interesting and enlightening are:
>
> 1) Run xawtv from the command line like this:
> $ xawtv -hwscan
>
> This might provide some clue. Depends on how detailed the information...
I just discovered that:
$ xawtv -hwscan
This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
looking for available devices
port 310-341
type : Xvideo, image scaler
name : NV17 Video Texture
/dev/video0: OK [ -device /dev/video0 ]
type : v4l2
name : ASUS PVR-416
flags: capture tuner
I am not sure if that PVR-416 is even correct.
> 2) Run xawtv from the command line like this:
> $ xawtv -device /dev/video0 -debug 2
>
> Then run it like this:
> $ xawtv -debug 2
>
> Reasoning: From the man page it says the specifying the device on the
> command line disables Xvideo support. This might force it to use dga to
> have an output path. I'm not sufficiently versed in X to know if that
> even makes sense, just something *I* would try...
>
> The "-debug 2" parameter should show max debug info. It could be
> useful...
I get screen flood of errors when running "xawtv -o -d 2". I tried to
use -o parameter but I can't find its output and still get flooding.
Here are a lot of repeating lines with S-Video input and seeing a blue
video screen:
...
blit: putframe
ioctl: VIDIOC_QBUF(index=1;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
ioctl:
VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
blit: putframe
ioctl: VIDIOC_QBUF(index=0;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
ioctl:
VIDIOC_DQBUF(index=1;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
blit: putframe
ioctl: VIDIOC_QBUF(index=1;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
ioctl:
VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
blit: putframe
ioctl: VIDIOC_QBUF(index=0;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
ioctl:
VIDIOC_DQBUF(index=1;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
blit: putframe
ioctl: VIDIOC_QBUF(index=1;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
ioctl:
VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
blit: putframe
ioctl: VIDIOC_QBUF(index=0;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
ioctl:
VIDIOC_DQBUF(index=1;type=VIDEO_CAPTURE;bytesused=221184;flags=0x1
[MAPPED];field=INTERLACED;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP):
ok
blit: putframe
ioctl: VIDIOC_S_CTRL(id=9963785;value=1): ok
cmd: "capture" "off"
gd: stop
v4l2: buf 0: video-cap 0x0+221184, used 221184
v4l2: buf 1: video-cap 0x36000+221184, used 221184
ioctl:
VIDIOC_S_FMT(type=VIDEO_CAPTURE;fmt.pix.width=384;fmt.pix.height=288;fmt.pix.pixelformat=0x34524742
[BGR4];fmt.pix.field=INTERLACED;fmt.pix.bytesperline=1536;fmt.pix.sizeimage=442368;fmt.pix.colorspace=unknown;fmt.pix.priv=0):
ok
v4l2: new capture params (384x288, BGR4, 442368 byte)
setformat: 32 bit TrueColor (LE: bgr-) (384x288): ok
ioctl:
VIDIOC_S_FMT(type=VIDEO_CAPTURE;fmt.pix.width=384;fmt.pix.height=288;fmt.pix.pixelformat=0x34524742
[BGR4];fmt.pix.field=INTERLACED;fmt.pix.bytesperline=1536;fmt.pix.sizeimage=442368;fmt.pix.colorspace=unknown;fmt.pix.priv=0):
ok
v4l2: new capture params (384x288, BGR4, 442368 byte)
v4l2: close
when I exited.
>
>
> Then I read the xawtvrc man page at:
> http://linux.die.net/man/5/xawtvrc
>
> This is valid both for the system wide config file at /etc/X11/xawtvrc
> and $HOME/.xawtv . If it was me. I would only modify $HOME/.xawtv since
> if that make things all FUBAR, it can be deleted and start over.
>
> From the man page:
> "Applications
> The following applications use these config files:
>
> xawtv
> The classic X11 TV application.
> motv
> A better, motif-based GUI for xawtv ... "
>
> Just a shot, but maybe motv will be easier to work with.
>
> Options you may want to include in the $HOME/.xawtv config file:
> norm = ntsc
> #input = Television
> input = Composite1
> #input = Composite2
>
> Depending on which cables you have connected will alter the "input ="
> line to uncomment. According to the man page:
> "The valid choices depend on the hardware driver, the values above are
> just examples. You can use "v4lctl list" to get a list of valid choices."
>
> If you have the v4lctl program run it (as "v4lctl list") and show the
> output.
Good one. That looks correct?
$ v4lctl list
attribute | type | current | default | comment
-----------+--------+---------+---------+-------------------------------------
norm | choice | NTSC-M | NTSC-M | NTSC-M NTSC-M-JP NTSC-443
PAL-BG PAL-I PAL-DK PAL-M PAL-N PAL-Nc PAL-60 SECAM-B SECAM-G SECAM-H
SECAM-DK SECAM-L
input | choice | S-Video | Televis | Television S-Video
audio mode | choice | mono | mono | mono stereo lang1 lang2
bright | int | 127 | 127 | range is 0 => 255
contrast | int | 63 | 63 | range is 0 => 255
color | int | 127 | 127 | range is 0 => 255
hue | int | 127 | 127 | range is 0 => 255
volume | int | 63 | 63 | range is 0 => 63
Balance | int | 64 | 64 | range is 0 => 127
mute | bool | on | on |
Chroma AGC | bool | on | on |
Color kill | bool | on | on |
>>>> I am feeding from my old VCR.
>>
>>> Yes that is clear, but what are you playing on the VCR?
>>
>> From the VCR, my DTV Pal for live TV feeds, a VHS tape with recording,
>> and VCR's menus. None of those showed up.
>
> Just for clarification, the "DTV Pal" device has NOTHING to do with the
> PAL TV standard used in Europe. This is a device sold by DishNetwork to
> allow analogue TVs to receive the new Federally dictated digital TV
> signals. I.e., a digital TV converter box.
Correct. It's a name. Actually, there is no space. My bad. DTVPal.
> <rant>
> Really torques me off when a company names their product with a confusing
> name when trying to be "cute". "DTV Pal", as in "DTV Best Friend" or "DTV
> Buddy". Since "PAL" is the analogue broadcast standard used in Europe,
> naming a device "DTV Pal" causes confusion for some who actually know
> about the different standards since it has *NOTHING* to do with PAL, it
> is just your "friend". [rolls eyes]
> </rant>
You know what else is lame? Its logo has a smiley mouth like TiVo's logo.
>>> Also as another possible check of your installation, does your VCR have
>>> a VHF/UHF modulator so that it could play out a video as a TV channel
>>> via a coaxial cable to connect to the VCR?
>>
>> Umm, I am not sure. All I know is the old CRT TV has one input (coax)
>> for antennae, cable, etc. VCR connects to this box. DTV Pal converter
>> box with its rabbit ears antenna connect to VCR for live TV. Then, I
>> have video and audio cables to the TV tuner.
>
> What he is asking here is "Does your VCR have a coax output?" Most do
> and if I remember correctly you said that was how it was hooked up to
> your TV.
Output to the TV? Yes with a coax cable since the TV only has a coax
input port. No other ports on it! It's just one connection on it.
> This may be useful if you can't get anything working with the S-video/
> composite cabling. But you will have to move the coax cable from the TV
> to the tuner card.
So VCR's coax cable to TV tuner? Hmm! That could work, but then I have
to rewire all this (messy and crowded at the moment). Ugh.
--
"Still we live meanly, like ants;... like pygmies we fight with
cranes;... Our life is frittered away by detail. Simplify...
simplify..." --Henry Thoreau
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
Ant
> However I got the attribution wrong, and I should have said "Gerd Knorr"
> who is the principle author of xawtv and much of the bttv/v4l software,
> including the cx88 modules which is highly relevant to this discussion.
>
> <http://linux.bytesex.ORG/>
Cool. I found https://www.redhat.com/mailman/listinfo/video4linux-list
... I will have to post my issue there soon.
>> I see from http://packages.debian.org/search?keywords=xawtv that this is
>> the most recent version available on debian.
>
> Even Debian Unstable (sid) is on the same version, so time to download
> the source, unpack, configure and compile? ;)
Ugh. I hate doing that. :/
>> but maybe motv will be easier to work with.
>
> It will need the openmotif libraries installing though.
>
> However, just changing the appearance of the application from
> X11 library to Motif is probably not going to do anything for
> the problem of the X11 video extension / dga display error.
>
>> Something isn't right with v4l and/or xawtv communication to v4l.
>
> Indeed -- could be something to do with the reported issue with Xorg
> X11 version 7 server.
>
>> Reasoning: From the man page it says the specifying the device on the
>> command line disables Xvideo support. This might force it to use dga to
>> have an output path.
>
> Eh? I think you are missing the point that we do not want xawtv to use
> dga because the latest video cards no longer have the dga capability,
> as explained in an earlier message.
>
>
>> Really torques me off when a company names their product with a
>> confusing name when trying to be "cute". "DTV Pal", as in "DTV Best
>> Friend" or "DTV Buddy".
>
>> Since "PAL" is the analogue broadcast standard used in Europe
>
> But most Americans will not know their PAL from their SECAM,
> only NTSC and ATSC, and even then, probably the vast majority
> do not know what those initialisms actually mean.
Yea, I didn't know those things in the past until I started dealing with
TV tuner cards that have settings. Even PowerVCR II and other video
programs ask which one!
>> naming a device "DTV Pal"
>
> Is cute and hopefully sells more units, which is about the only
> thing that they are really concerned.
Yeah, marketing brand. No space BTW. My bad.
>> What he is asking here is "Does your VCR have a coax output?" Most do
>
> As confirmed on Page 9 of the instruction manual.
>
>> This may be useful if you can't get anything working with the S-video/
>> composite cabling.
>
> Exactly -- this is a good test to see if the demodulation side of the
> card is working and that the kernel module and xawtv are at least
> correctly configured for that.
I will deal with that in the future. My cabling is messy and don't have
time to deal with it at this time. Good idea though! However, I had it
like that with this TV tuner in my Windows box (don't have it anymore). Grr.
--
"... [Let us inquire] what glory there was in an omnipotent being
torturing forever a puny little creature who could in no way defend
himself? Would it be to the glory of a man to fry ants?" --Charlotte
Perkins Gilman
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
Ant
> However I got the attribution wrong, and I should have said "Gerd Knorr"
> who is the principle author of xawtv and much of the bttv/v4l software,
> including the cx88 modules which is highly relevant to this discussion.
It looks like Mr. Knorr left in 2005 according to
http://linux.bytesex.org/v4l2/maintainer.txt ... :(
--
"Whence we see spiders, flies, or ants entombed and preserved forever in
amber, a more than royal tomb." --Sir Francis Bacon in Historia Vitæ et
Mortis; Sylva Sylvarum, Cent. i. Exper. 100.
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
Kevin Snodgrass
> # locate
> xawtvrc
> /usr/share/man/man5/xawtvrc.5.gz
>
> I assume the gzipped one has it so I extracted it. Here is what it says
> untouched by me:
No. that is the man page for xawtvrc. Everything in /usr/share/man/* are
man pages. You now know what a troff file looks like. Enjoy!
Type man xawtvrc to see the contents in a more human readable format.
> I renamed and moved it to ~/.xawtv. I tried it and got plenty of new
> errors: $ xawtv
[snippage]
> Um, is this file correct?
Of course not. That's because that wasn't a config file. It was a troff
formatted man page.
> I couldn't find motv in Debian's apt-get. fbtv gave me an error: $ fbtv
It "should" be included with the xawtv package you already have.
> using linux console font "/usr/share/consolefonts/lat1-16.psf.gz" ioctl
> VT_GETSTATE: Invalid argument (not a linux console?) Isn't my old KDE
> v3.5.10's Terminal considered a Linux console?
No, that is an xterm. This application doesn't use xterms. It is for
playing video files/streams from the console, i.e. without X-windows
loaded.
> FYI for more clues? I tried a bunch of parameters in xawtv:
>
> $ xawtv -hwscan
> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686) looking
> for available devices
> port 310-341
> type : Xvideo, image scaler
> name : NV17 Video Texture
This is the output v4l device, i.e. part of X-windows. xawtv will play
the video "into" this device.
> /dev/video0: OK [ -device /dev/video0 ]
> type : v4l2
> name : ASUS PVR-416
> flags: capture tuner
>
> PVR-416? Is that right?
Exactly. This makes me believe v4l and the kernel modules are loaded
correctly.
> $ xawtv -fb
> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686) xinerama
> 0: 1280x1024+0+0
> ioctl VT_GETSTATE: Invalid argument
Probably shouldn't use anything frame buffer related while in X-windows.
> $ xawtv -noxv
Don't do that. xv might be used.
> $ xawtv -xv-video
> $ xawtv -noxv-video
> $ xawtv -xv-image
> $ xawtv -noxv-image
> $ xawtv -vm
> $ xawtv -novm
None of these will help, but make make playback impossible. Your
problems here are NOT playback related, they appear to me to be input
related.
> Also, I noticed dmesg no wonder shows errors about my TV tuner like last
> week. Weird.
That must mean we fixed the kernel module loading issues.
Now we have to figure out how to get xawtv to read from the proper video
input on the card. I'm still pretty sure it is reading from the coax
input.
Kevin Snodgrass
> On Monday, January 3rd, 2011 at 23:31:04h +0000, Kevin Snodgrass wrote:
>
>> Didn't know he had anything to do with xawtv, though...
>
> Axel Thimm is a major contributor to the video4linux mailing list and
> has done a lot of work with xawtv.
Cool. He does A LOT of work on video related things for Linux.
> However I got the attribution wrong, and I should have said "Gerd Knorr"
> who is the principle author of xawtv and much of the bttv/v4l software,
> including the cx88 modules which is highly relevant to this discussion.
>
> <http://linux.bytesex.ORG/>
Yeah, I figured that out.
>> I see from http://packages.debian.org/search?keywords=xawtv that this
>> is the most recent version available on debian.
>
> Even Debian Unstable (sid) is on the same version, so time to download
> the source, unpack, configure and compile? ;)
Not sure about hand-holding ANT through that...
>
>> but maybe motv will be easier to work with.
>
> It will need the openmotif libraries installing though.
Really? I thought it was included with the xawtv package, and therefore
all requirements were already met. I must not have understood the
webpage...
> However, just changing the appearance of the application from X11
> library to Motif is probably not going to do anything for the problem of
> the X11 video extension / dga display error.
I don't understand that error. Do you think it is really important? I
know a way to find out. Can xawtv play a standard .mpg, .avi, .wmv, or
similar? If so we just need to find one for ANT and have him try playing
it. If it plays then that error can probably be ignored...
>> Something isn't right with v4l and/or xawtv communication to v4l.
>
> Indeed -- could be something to do with the reported issue with Xorg X11
> version 7 server.
>
>> Reasoning: From the man page it says the specifying the device on the
>> command line disables Xvideo support. This might force it to use dga
>> to have an output path.
>
> Eh? I think you are missing the point that we do not want xawtv to use
> dga because the latest video cards no longer have the dga capability, as
> explained in an earlier message.
Oh, I understand that we don't want dga. Don't know much about it, but
it seems to cause an error, so... My point is, according to the online
man page when you specify the device, e.g. /dev/video0, on the command
line it will disable Xvideo. If Xvideo is disabled I am guessing that
xawtv drops back to using dga for output and trying to disable it via a
command line switch might not work. I am throwing darts in the dark here
you know...
>> Really torques me off when a company names their product with a
>> confusing name when trying to be "cute". "DTV Pal", as in "DTV Best
>> Friend" or "DTV Buddy".
>
>> Since "PAL" is the analogue broadcast standard used in Europe
>
> But most Americans will not know their PAL from their SECAM, only NTSC
> and ATSC, and even then, probably the vast majority do not know what
> those initialisms actually mean.
True. Still, some of us DO know what NTSC, ATSC, PAL, SECAM, etc mean
(not necessarily the technical details, but what they mean practically)
and the product name "DTV Pal" completely threw me off in the wrong
direction. It's totally unnecessary for them to choose that name, but
marketing types don't care about logic or anything. They just want a
snazzy name...
>> What he is asking here is "Does your VCR have a coax output?" Most do
>
> As confirmed on Page 9 of the instruction manual.
>
>> This may be useful if you can't get anything working with the S-video/
>> composite cabling.
>
> Exactly -- this is a good test to see if the demodulation side of the
> card is working and that the kernel module and xawtv are at least
> correctly configured for that.
And my guess is the card/driver are defaulting to coax input and maybe
channel 4. Since no live coax feed is attached, you get snow for a
picture.
Kevin Snodgrass
> On 1/3/2011 3:31 PM PT, Kevin Snodgrass typed:
>
>> As Mr. Miller pointed out earlier this afternoon, these are the package
>> config files. Look in your home directory, something like ~/.xawtv.
>> Try doing this:
>> $ ls -al ~/.xawtv*
>>
>> And see what shows up.
>
> I had none. :(
OK, if need be just make one. Use your favorite text editor, vi, emacs,
gedit, whatever. We'll get to that someday.
>>> Version: 3.95.dfsg.1-8.1+b1
>>
>> I see from http://packages.debian.org/search?keywords=xawtv that this
>> is the most recent version available on debian. I think Mr. Miller
>> suggested upgrading to Version 4.x, which doesn't show up anywhere in
>> the search results. Therefore, I guess you are stuck with this one.
>
> :( I wonder if there are any Debian packages outside of there.
It is possible that someone else has packaged up .debs for a newer
version. I'm not a Debian user so I don't even know where to start.
Google I guess...
> I just discovered that:
> $ xawtv -hwscan
> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686) looking
> for available devices
> port 310-341
> type : Xvideo, image scaler
> name : NV17 Video Texture
>
> /dev/video0: OK [ -device /dev/video0 ]
> type : v4l2
> name : ASUS PVR-416
> flags: capture tuner
As noted in my other replay this looks good.
> I am not sure if that PVR-416 is even correct.
Pretty sure it is.
>> 2) Run xawtv from the command line like this: $ xawtv -device
>> /dev/video0 -debug 2
> >
>> Then run it like this:
>> $ xawtv -debug 2
>>
>> Reasoning: From the man page it says the specifying the device on the
>> command line disables Xvideo support. This might force it to use dga
>> to have an output path. I'm not sufficiently versed in X to know if
>> that even makes sense, just something *I* would try...
>>
>> The "-debug 2" parameter should show max debug info. It could be
>> useful...
>
> I get screen flood of errors when running "xawtv -o -d 2". I tried to
I didn't say ANYTHING about "xawtv -o -d 2". Not even sure if xawtv will
"like" that parameter string as -o requires a file name for output and
there is no -d that I can find.
> use -o parameter but I can't find its output and still get flooding.
The -o parameter requires a filename to dump output too. I don't
understand the terminology in the man page, it says this is for "snapshot
output files". YOU DON"T NEED TO MESS WITH THIS NOW! Whatever it is.
> Here are a lot of repeating lines with S-Video input and seeing a blue
> video screen:
Run it as I asked above. First:
$ xawtv -device /dev/video0 -debug 2
Then:
$ xawtv -debug 2
I have a very specific purpose for this. I want to find something out.
Adding other parameters, trying your own thing, whatever will not answer
my question. This might be very useful if my hunch is correct. I need
to compare the output from the two different executions to see if
something is happening.
> Good one. That looks correct?
> $ v4lctl list
> attribute | type | current | default | comment
Grr.. My newsgroup reader, Pan, word wraps your comment into a mess for
my reply. It came through fine in your post, but all the columns are
messed up in my reply. I'll soldier on though...
> -----------+--------+---------+---------
+-------------------------------------
> norm | choice | NTSC-M | NTSC-M | NTSC-M NTSC-M-JP NTSC-443
> PAL-BG PAL-I PAL-DK PAL-M PAL-N PAL-Nc PAL-60 SECAM-B SECAM-G SECAM-H
> SECAM-DK SECAM-L
That looks good.
> input | choice | S-Video | Televis | Television S-Video audio mode
That looks good. And as I thought, the default was "Television", i.e.
the coax cable jack. But it IS set to read from the S-video jack. Now
I'm not sure what to try next, since you are reading from the correct
input. Must think about this one...
The rest won't matter...
>> <rant>
>> Really torques me off when a company names their product with a
>> confusing name when trying to be "cute". "DTV Pal", as in "DTV Best
>> Friend" or "DTV Buddy". Since "PAL" is the analogue broadcast standard
>> used in Europe, naming a device "DTV Pal" causes confusion for some who
>> actually know about the different standards since it has *NOTHING* to
>> do with PAL, it is just your "friend". [rolls eyes]
>> </rant>
>
> You know what else is lame? Its logo has a smiley mouth like TiVo's
> logo.
Don't know that logo, but that *could* be a TradeMark violation.
Assuming Tivo (TM)'ed their smiley mouth, it that is even possible...
>> This may be useful if you can't get anything working with the S-video/
>> composite cabling. But you will have to move the coax cable from the
>> TV to the tuner card.
>
> So VCR's coax cable to TV tuner? Hmm! That could work, but then I have
> to rewire all this (messy and crowded at the moment). Ugh.
Exactly. Don't know what kind of wiring mess you have there (as I look
at the bundle of about 20 cables on MY floor), but that might be the
trick at this point.
Ant
>> # locate
>> xawtvrc
>> /usr/share/man/man5/xawtvrc.5.gz
>>
>> I assume the gzipped one has it so I extracted it. Here is what it says
>> untouched by me:
>
> No. that is the man page for xawtvrc. Everything in /usr/share/man/* are
> man pages. You now know what a troff file looks like. Enjoy!
Ah! I have never heard of troff format before. Thanks. :)
> Type man xawtvrc to see the contents in a more human readable format.
>
>> I renamed and moved it to ~/.xawtv. I tried it and got plenty of new
>> errors: $ xawtv
> [snippage]
>> Um, is this file correct?
>
> Of course not. That's because that wasn't a config file. It was a troff
> formatted man page.
>
>> I couldn't find motv in Debian's apt-get. fbtv gave me an error: $ fbtv
>
> It "should" be included with the xawtv package you already have.
Hmm! "locate motv" found nothing on my box.
http://packages.debian.org/search?searchon=contents&keywords=motv&mode=path&suite=stable&arch=any
http://packages.debian.org/search?searchon=contents&keywords=motv&mode=path&suite=experimental&arch=any
http://packages.debian.org/search?searchon=contents&keywords=motv&mode=filename&suite=unstable&arch=any
http://packages.debian.org/search?searchon=contents&keywords=motv&mode=filename&suite=testing&arch=any
None of them can find motv filename inside all packages. :(
I looked at every packages for motv inside on
http://packages.debian.org/search?keywords=xawtv&searchon=names&suite=all§ion=all
, and nothing! What the frak?
>> using linux console font "/usr/share/consolefonts/lat1-16.psf.gz" ioctl
>> VT_GETSTATE: Invalid argument (not a linux console?) Isn't my old KDE
>> v3.5.10's Terminal considered a Linux console?
>
> No, that is an xterm. This application doesn't use xterms. It is for
> playing video files/streams from the console, i.e. without X-windows
> loaded.
Oh, so I can't use fbtv.
>> FYI for more clues? I tried a bunch of parameters in xawtv:
>>
>> $ xawtv -hwscan
>> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686) looking
>> for available devices
>> port 310-341
>> type : Xvideo, image scaler
>> name : NV17 Video Texture
>
> This is the output v4l device, i.e. part of X-windows. xawtv will play
> the video "into" this device.
I assume that's fine.
>> /dev/video0: OK [ -device /dev/video0 ]
>> type : v4l2
>> name : ASUS PVR-416
>> flags: capture tuner
>>
>> PVR-416? Is that right?
>
> Exactly. This makes me believe v4l and the kernel modules are loaded
> correctly.
OK! Good.
>> $ xawtv -fb
>> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686) xinerama
>> 0: 1280x1024+0+0
>> ioctl VT_GETSTATE: Invalid argument
>
> Probably shouldn't use anything frame buffer related while in X-windows.
>
>> $ xawtv -noxv
>
> Don't do that. xv might be used.
>
>> $ xawtv -xv-video
>> $ xawtv -noxv-video
>> $ xawtv -xv-image
>> $ xawtv -noxv-image
>> $ xawtv -vm
>> $ xawtv -novm
>
> None of these will help, but make make playback impossible. Your
> problems here are NOT playback related, they appear to me to be input
> related.
>
>> Also, I noticed dmesg no wonder shows errors about my TV tuner like last
>> week. Weird.
>
> That must mean we fixed the kernel module loading issues.
Sweet!
> Now we have to figure out how to get xawtv to read from the proper video
> input on the card. I'm still pretty sure it is reading from the coax
> input.
Yeah, hmm!
--
"The ants are my friends, they're blowin' in the wind. The ant, sir, is
blowin' in the wind." --the misheard lyrics to Bob Dylan's "Blowin' in
the Wind"
Ant
>> Even Debian Unstable (sid) is on the same version, so time to download
>> the source, unpack, configure and compile? ;)
>
> Not sure about hand-holding ANT through that...
Yeah, I am already struggling with Linux GUI stuff. :D
>>> but maybe motv will be easier to work with.
>>
>> It will need the openmotif libraries installing though.
>
> Really? I thought it was included with the xawtv package, and therefore
> all requirements were already met. I must not have understood the
> webpage...
Or Debian does it weird.
>> However, just changing the appearance of the application from X11
>> library to Motif is probably not going to do anything for the problem of
>> the X11 video extension / dga display error.
>
> I don't understand that error. Do you think it is really important? I
> know a way to find out. Can xawtv play a standard .mpg, .avi, .wmv, or
> similar? If so we just need to find one for ANT and have him try playing
> it. If it plays then that error can probably be ignored...
I can play those in (g)mplayer and VLC. :)
> True. Still, some of us DO know what NTSC, ATSC, PAL, SECAM, etc mean
> (not necessarily the technical details, but what they mean practically)
> and the product name "DTV Pal" completely threw me off in the wrong
> direction. It's totally unnecessary for them to choose that name, but
> marketing types don't care about logic or anything. They just want a
> snazzy name...
Yep, a happy TV logo like TiVo's.
> And my guess is the card/driver are defaulting to coax input and maybe
> channel 4. Since no live coax feed is attached, you get snow for a
> picture.
Doesn't using S-Video not use coax? It should be pointing to my S-Video
(TV tuner's connection) that is connected to composite adapters (VCR).
--
"When you turn on a light in a room, what happens?" Shaw said. "The
roaches scatter, but the ants keep marching. You can step on them, throw
water on them, but they keep on marching. I want ants for my defense."
--Willy Shaw
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
Ant
>>> Try doing this:
>>> $ ls -al ~/.xawtv*
>>>
>>> And see what shows up.
>>
>> I had none. :(
>
> OK, if need be just make one. Use your favorite text editor, vi, emacs,
> gedit, whatever. We'll get to that someday.
Nano (formerly Pico). :)
>>>> Version: 3.95.dfsg.1-8.1+b1
>>>
>>> I see from http://packages.debian.org/search?keywords=xawtv that this
>>> is the most recent version available on debian. I think Mr. Miller
>>> suggested upgrading to Version 4.x, which doesn't show up anywhere in
>>> the search results. Therefore, I guess you are stuck with this one.
>>
>> :( I wonder if there are any Debian packages outside of there.
>
> It is possible that someone else has packaged up .debs for a newer
> version. I'm not a Debian user so I don't even know where to start.
> Google I guess...
I will look into it later. I am sleepy now, so I don't want to fiddle
with it for now.
>> I just discovered that:
>> $ xawtv -hwscan
>> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686) looking
>> for available devices
>> port 310-341
>> type : Xvideo, image scaler
>> name : NV17 Video Texture
>>
>> /dev/video0: OK [ -device /dev/video0 ]
>> type : v4l2
>> name : ASUS PVR-416
>> flags: capture tuner
>
> As noted in my other replay this looks good.
:)
>> I am not sure if that PVR-416 is even correct.
>
> Pretty sure it is.
OK. :) PVR throws me off. ;)
>>> 2) Run xawtv from the command line like this: $ xawtv -device
>>> /dev/video0 -debug 2
>> >
>>> Then run it like this:
>>> $ xawtv -debug 2
>>>
>>> Reasoning: From the man page it says the specifying the device on the
>>> command line disables Xvideo support. This might force it to use dga
>>> to have an output path. I'm not sufficiently versed in X to know if
>>> that even makes sense, just something *I* would try...
>>>
>>> The "-debug 2" parameter should show max debug info. It could be
>>> useful...
>>
>> I get screen flood of errors when running "xawtv -o -d 2". I tried to
>
> I didn't say ANYTHING about "xawtv -o -d 2". Not even sure if xawtv will
> "like" that parameter string as -o requires a file name for output and
> there is no -d that I can find.
Crap (damn lack of sleep -- woke up at 4 AM PST :P), I meant "xawtv -o
-v 2" since I wanted debugging go to a file. I even tried a filename
(e.g., xawtv -v 2 -o log), but nothing.
>> use -o parameter but I can't find its output and still get flooding.
>
> The -o parameter requires a filename to dump output too. I don't
> understand the terminology in the man page, it says this is for "snapshot
> output files". YOU DON"T NEED TO MESS WITH THIS NOW! Whatever it is.
OK! There's so much crap the -d 2 is showing. That's why I wanted to
capture all that to a file for you guys. :(
>> Here are a lot of repeating lines with S-Video input and seeing a blue
>> video screen:
>
> Run it as I asked above. First:
>
> $ xawtv -device /dev/video0 -debug 2
> Then:
>
> $ xawtv -debug 2
For both, I ran it really quick, waited a second on blue video screen,
and exited.
> I have a very specific purpose for this. I want to find something out.
> Adding other parameters, trying your own thing, whatever will not answer
> my question. This might be very useful if my hunch is correct. I need
> to compare the output from the two different executions to see if
> something is happening.
OK.
>> Good one. That looks correct?
>> $ v4lctl list
>> attribute | type | current | default | comment
>
> Grr.. My newsgroup reader, Pan, word wraps your comment into a mess for
> my reply. It came through fine in your post, but all the columns are
> messed up in my reply. I'll soldier on though...
>
>> -----------+--------+---------+---------
> +-------------------------------------
>> norm | choice | NTSC-M | NTSC-M | NTSC-M NTSC-M-JP NTSC-443
>> PAL-BG PAL-I PAL-DK PAL-M PAL-N PAL-Nc PAL-60 SECAM-B SECAM-G SECAM-H
>> SECAM-DK SECAM-L
>
> That looks good.
Cool. :)
>> input | choice | S-Video | Televis | Television S-Video audio mode
>
> That looks good. And as I thought, the default was "Television", i.e.
> the coax cable jack. But it IS set to read from the S-video jack. Now
> I'm not sure what to try next, since you are reading from the correct
> input. Must think about this one...
OK. Let's take a break and call it the night because I am going to sleep!
> The rest won't matter...
OK!
>>> <rant>
>>> Really torques me off when a company names their product with a
>>> confusing name when trying to be "cute". "DTV Pal", as in "DTV Best
>>> Friend" or "DTV Buddy". Since "PAL" is the analogue broadcast standard
>>> used in Europe, naming a device "DTV Pal" causes confusion for some who
>>> actually know about the different standards since it has *NOTHING* to
>>> do with PAL, it is just your "friend". [rolls eyes]
>>> </rant>
>>
>> You know what else is lame? Its logo has a smiley mouth like TiVo's
>> logo.
>
> Don't know that logo, but that *could* be a TradeMark violation.
> Assuming Tivo (TM)'ed their smiley mouth, it that is even possible...
Dish Network had that for YEARS.
>>> This may be useful if you can't get anything working with the S-video/
>>> composite cabling. But you will have to move the coax cable from the
>>> TV to the tuner card.
>>
>> So VCR's coax cable to TV tuner? Hmm! That could work, but then I have
>> to rewire all this (messy and crowded at the moment). Ugh.
>
> Exactly. Don't know what kind of wiring mess you have there (as I look
> at the bundle of about 20 cables on MY floor), but that might be the
> trick at this point.
Heh. :)
--
"I don't know how good ants are at swimmin', but I'd be willing to bet
that a good fire'd get their attention." --MacGyver in Trumbo's World
episode
J G Miller
> Not sure about hand-holding ANT through that...
How difficult is it to enter
wget {SOME_URL}/package_archive.tar.gz
tar xvzf package_archive.tar.gz
cd package_directory
./configure {some options maybe}
make
make install
> Really? I thought it was included with the xawtv package, and therefore
> all requirements were already met.
Why would the xawtv package include openmotif libraries, even if it did use
motif, and especially as it does not used motif widgets?
> I don't understand that error. Do you think it is really important?
It is important if the message is being truthful, which it may not be
since apparently xawtv does display something on the screen despite the
near fatal error message.
> Can xawtv play a standard .mpg, .avi, .wmv, or similar?
xawtv is not a media player. It gets its input from /dev/video
not from a file, and what format that video is in, I do not know.
Perhaps it could be possible to stream something which writes to
/dev/video and then xawtv reads that, but this is pure conjecture.
> My point is, according to the online man page when you specify the device,
> e.g. /dev/video0, on the command line it will disable Xvideo.
But so far, /dev/video0 has not been specified on the command line,
so Xvideo should be be disabled.
> but marketing types don't care about logic or anything.
They may not care about logic but they do care about sales. And since
most consumers do not use logic in making purchases, other than essentials
most are compulsive "looks good, sounds nice, nice packaging" type decisions,
the actual meaning of the name is irrelevant.
Is an iPod some type of rocket fuel pod? ;)
> They just want a snazzy name...
Exactly the point I was making.
> And my guess is the card/driver are defaulting to coax input and maybe
> channel 4.
Not if the option menu has been used to select S-VHS input.
J G Miller
> It looks like Mr. Knorr left in 2005 according to
And in that text he states that he will still be available to answer
questions, does it not?
After all his web site
QUOTE
The kernel drivers maintained my me (bttv, saa7134 and cx88)
can be found there as well.
UNQUOTE
which presumably you have visited by now, is still active.
J G Miller
> Ugh. I hate doing that. :/
Why?
> I had it like that with this TV tuner in my Windows box
Why do you keep bringing Windows into the discussion?
If you are more comfortable using Windows, then ...
J G Miller
> input | choice | S-Video | Televis | Television S-Video
This looks good. xawtv is now configured by default to use the
S-Video input.
The only problem remaining is for xawtv to show something meaningful
on the display using this input.
The outstanding issue may be as previously suggested a problem of
xawtv version 3 no longer working with Xorg X11 server version 7
and above.
Which part of
QUOTE
See the manual page for xawtvrc
user_prompt> man 5 xawtvrc
Also at <http://linux.die.net/man/5/xawtvrc>
UNQUOTE
in any way suggested what you just did?
Even the command for viewing the manual page was provided.
man 5 xawtvrc
Why was that so difficult to type in at the command line prompt?
> $ dpkg -l | grep ^ii |grep Xorg
> ii xserver-xorg-core 2:1.7.7-10
> Xorg X server - core server
So you are using Xorg X11 server with version greater than 7,
thus the possibility of xawtv not working as per the bug report.
But then you say
> Ooh, new commands to try:
> motv A better, motif-based GUI for xawtv ...
> fbtv TV application for the linux framebuffer console.
> ttv aalib-based TV application for any terminal.
So you did view the manual page.
Which prompts the question why did you try to use the
manual page contents as a configuration file?
> fbtv gave me an error:
> $ fbtv
> using linux console font "/usr/share/consolefonts/lat1-16.psf.gz"
> ioctl VT_GETSTATE: Invalid argument (not a linux console?)
> Isn't my old KDE v3.5.10's Terminal considered a Linux console?
No it is not. It is a X11 Windows Terminal emulation program.
A "Linux console" or more correctly "virtual console" is to be
found by using the key combinations
<CTRL><ALT>F1
...
<CTRL><ALT>F6
To get back to the X11 session which runs by default on virtual
console 7, you would obviously use the combination
<CTRL><ALT>F7
fbtv is a *f*rame *b*uffer device program so you have to be on
a virtual console terminal in order to use it.
> I always used channel 3 and is still channel 3.
So when I asked you if you had an coaxial RF modulated output on the VCR,
why did you not tell me that you did not know and told me to go read the
manual for your VCR in order to find the answer?
Ant
> On Monday, January 3rd, 2011 at 22:00:03h -0800, Ant wrote:
> > Ugh. I hate doing that. :/
> Why?
Because it's complex (requiring dependencies, trying to find what it
wants, etc.) and ugly. Much easier with packages. :(
> > I had it like that with this TV tuner in my Windows box
> Why do you keep bringing Windows into the discussion?
> If you are more comfortable using Windows, then ...
I wished I could, but my Windows box doesn't have a PCI card slot. Only
Express exist. I would have to build/buy another older box that has
one. :(
--
Quote of the Week: "It doesn't matter what your D&D manual says, you did
not get 5 experience points for killing the giant ant in your kitchen."
--BBspot's Geek Horoscopes (7/30/2004)
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.
Ant
> QUOTE
Yeah, I went there. cx88-0.0.4.tar.gz was last updated in 4/21/2004.
I also posted on my issue on video4li...@redhat.com mailing list. I
hope that's the right place. So far, no replies and no other posts. It
is very quiet. :)
--
Quote of the Week: "It doesn't matter what your D&D manual says, you did
not get 5 experience points for killing the giant ant in your kitchen."
--BBspot's Geek Horoscopes (7/30/2004)
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.
Ant
> How difficult is it to enter
> wget {SOME_URL}/package_archive.tar.gz
> tar xvzf package_archive.tar.gz
> cd package_directory
> ./configure {some options maybe}
> make
> make install
That's fine if it works. However, things get ugly when dependencies or
some other errors. We can try it. I will need some help when I run into
problems. I also need to be able to uninstall the installations/messes.
:)
Where should we start with the compilation? Which packages to try?
J G Miller
> I also posted on my issue on video4li...@redhat.com mailing list.
That is probably okay, but since you are running Debian, have you
filed a bug report with Debian Bugs?
Ant
> > input | choice | S-Video | Televis | Television S-Video
> This looks good. xawtv is now configured by default to use the
> S-Video input.
> The only problem remaining is for xawtv to show something meaningful
> on the display using this input.
> The outstanding issue may be as previously suggested a problem of
> xawtv version 3 no longer working with Xorg X11 server version 7
> and above.
OK, so basically I need to download xawtv v4 and compile it since no v4
Debian package exist. Am I correct? First, I am going to post in Debian
newsgroups to see if it exist so I don't have to compile.
> Which part of
> QUOTE
> See the manual page for xawtvrc
> user_prompt> man 5 xawtvrc
> Also at <http://linux.die.net/man/5/xawtvrc>
> UNQUOTE
> in any way suggested what you just did?
> Even the command for viewing the manual page was provided.
> man 5 xawtvrc
> Why was that so difficult to type in at the command line prompt?
Why can't I just type "man xawtvrc"? I never had to use numbers.
> > $ dpkg -l | grep ^ii |grep Xorg
> > ii xserver-xorg-core 2:1.7.7-10
> > Xorg X server - core server
> So you are using Xorg X11 server with version greater than 7,
> thus the possibility of xawtv not working as per the bug report.
OK.
> But then you say
> > Ooh, new commands to try:
> > motv A better, motif-based GUI for xawtv ...
> > fbtv TV application for the linux framebuffer console.
> > ttv aalib-based TV application for any terminal.
> So you did view the manual page.
> Which prompts the question why did you try to use the
> manual page contents as a configuration file?
Again, this is new and confusing to me.
> > fbtv gave me an error:
> > $ fbtv
> > using linux console font "/usr/share/consolefonts/lat1-16.psf.gz"
> > ioctl VT_GETSTATE: Invalid argument (not a linux console?)
> > Isn't my old KDE v3.5.10's Terminal considered a Linux console?
> No it is not. It is a X11 Windows Terminal emulation program.
Oh.
> A "Linux console" or more correctly "virtual console" is to be
> found by using the key combinations
> <CTRL><ALT>F1
> ...
> <CTRL><ALT>F6
> To get back to the X11 session which runs by default on virtual
> console 7, you would obviously use the combination
> <CTRL><ALT>F7
Ah, so it is the text mode before I use "startx" command. And yes, I
boot to text mode first.
> fbtv is a *f*rame *b*uffer device program so you have to be on
> a virtual console terminal in order to use it.
So if I run it from text mode, it runs fbtv GUI?
> > I always used channel 3 and is still channel 3.
> So when I asked you if you had an coaxial RF modulated output on the VCR,
> why did you not tell me that you did not know and told me to go read the
> manual for your VCR in order to find the answer?
The terms are confusing like RF modulation. I didn't know what that
meant. I am not an AV person. :(
--
Quote of the Week: "It doesn't matter what your D&D manual says, you did
not get 5 experience points for killing the giant ant in your kitchen."
--BBspot's Geek Horoscopes (7/30/2004)
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.
Ant
Not yet. I want to research more before doing it.
J G Miller
> That's fine if it works. However, things get ugly when dependencies or
> some other errors.
Yeah, I carelessly forgot to add that the difficult part is first making sure that all
of the header files (development packages) are present on the system.
> We can try it.
If you are prepared to learn and not to get frustrated because it takes a bit
of effort, then I am prepared to help.
> I also need to be able to uninstall the installations/messes.
Anything that you install will be put under /usr/local and if you want to keep
it really neat, then stow should be used.
So the first thing you should do is, if not already installed
apt-get install build-essential stow
Looks like version 4 of xawtv is not yet released so it is a CVS snapshot
Again as root
cd /usr/src/
mkdir apps
cd apps
wget "http://dl.bytesex.org/cvs-snapshots/xawtv-20081014-100645.tar.gz"
tar xvzf xawtv-20081014-100645.tar.gz
cd xawtv
sh autogen
apt-get install libzvbi-dev
./configure
This is where things will now get scary with error and warning messages.
Easiest thing is for your to copy the output from configure to a "pastie"
if you do now understand how to resolve the missing files that are needed
using apt-file missing_header_filename and then apt-get development-package
We then have to keep repeating the above ./configure step after installing
the needed development packages and repeat as necessary until ./configure
completes without a serious complaint.
At the very least the ALSA development package and probably the openmotif
development pacakge should be installed.
Looks like you will also need GTK libraries because, wow, xawtv has entered
the modern age and is now a GTK program. (I just successfully compiled
the above source code.)
J G Miller
>(I just successfully compiled the above source code.)
I really am impressed -- the *new* xawtv (version 4) now does DVB
and it is now happily scanning for stations on Astra 1 cluster at 19,2 East
as I have a DVB-s card in this machine.
J G Miller
> OK, so basically I need to download xawtv v4 and compile it since no v4
> Debian package exist.
Correct.
> Am I correct?
You are correct.
> First, I am going to post in Debian newsgroups to see if it exist so I don't have to compile.
As you are correct that it does not exist, why would you do this?
Or do you not believe Kevin Snodgrass or myself when we tell you that it does not exist?
> Why can't I just type "man xawtvrc"? I never had to use number.
You can just type man xawtvrc, which you did do.
>> Which prompts the question why did you try to use the manual page
>> contents as a configuration file?
>
> Again, this is new and confusing to me.
Are you really claiming that you have never looked at a manual page before today?
> Ah, so it is the text mode before I use "startx" command. And yes, I
> boot to text mode first.
No frame buffer is not text mode, the virtual console on which you have
text mode to run startx runs on the frame buffer.
> So if I run it from text mode, it runs fbtv GUI?
Text mode on a virtual console running on the frame buffer device,
then yes.
> I am not an AV person. :(
Neither am I.
But you have the VCR which came with an instruction manual and has
the output jacks labeled. Is it really so difficult to look at the
output jacks on the VCR and consult the instruction manual?
Kevin Snodgrass
>>> I couldn't find motv in Debian's apt-get. fbtv gave me an error: $
>>> fbtv
>>
>> It "should" be included with the xawtv package you already have.
>
> Hmm! "locate motv" found nothing on my box.
OK, like I said I'm not a Debian or xawtv user. I made *another*
incorrect assumption, based on the online man page for xawtv. When it
said the same config file would be used by motv I guess that put a bug in
my (leaking) gray matter that motv was part of the same package. Doesn't
look to be the case...
>>> using linux console font "/usr/share/consolefonts/lat1-16.psf.gz"
>>> ioctl VT_GETSTATE: Invalid argument (not a linux console?) Isn't my
>>> old KDE v3.5.10's Terminal considered a Linux console?
>>
>> No, that is an xterm. This application doesn't use xterms. It is for
>> playing video files/streams from the console, i.e. without X-windows
>> loaded.
>
> Oh, so I can't use fbtv.
Not from an xterm. From a virtual console you can. This will lead us
off into the weeds. Just don't worry about trying anything "frame
buffer" related...
>>> FYI for more clues? I tried a bunch of parameters in xawtv:
>>>
>>> $ xawtv -hwscan
>>> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
>>> looking for available devices
>>> port 310-341
>>> type : Xvideo, image scaler
>>> name : NV17 Video Texture
>>
>> This is the output v4l device, i.e. part of X-windows. xawtv will play
>> the video "into" this device.
>
> I assume that's fine.
Yes.
>>> Also, I noticed dmesg no wonder shows errors about my TV tuner like
>>> last week. Weird.
>>
>> That must mean we fixed the kernel module loading issues.
>
> Sweet!
Onward...
Kevin Snodgrass
> On Tue, 04 Jan 2011 07:18:15 +0000, Kevin Snodgrass wrote:
>
>> Not sure about hand-holding ANT through that...
>
> How difficult is it to enter
>
> wget {SOME_URL}/package_archive.tar.gz
>
> tar xvzf package_archive.tar.gz
>
> cd package_directory
>
> ./configure {some options maybe}
>
> make
>
> make install
Oh that's easy when it works without a hitch. Something tells me it
won't.
>> Really? I thought it was included with the xawtv package, and
>> therefore all requirements were already met.
>
> Why would the xawtv package include openmotif libraries, even if it did
> use motif, and especially as it does not used motif widgets?
Guess I didn't read close enough... As I mentioned to ANT in previous
message tonight, when I read the online version of the xawtv man page it
mentioned that motv used the same config file, and I made the leap to
that meaning motv was included in the xawtv package. Never could leap
worth a hoot... :-)
>> I don't understand that error. Do you think it is really important?
>
> It is important if the message is being truthful, which it may not be
> since apparently xawtv does display something on the screen despite the
> near fatal error message.
mplayer does something similar:
----->cut here<------
$ mplayer Tiger_\&_Frank.wmv
MPlayer SVN-r31628-4.4.4 (C) 2000-2010 MPlayer Team
Playing Tiger_&_Frank.wmv.
ASF file format detected.
[asfheader] Audio stream found, -aid 1
[asfheader] Video stream found, -vid 2
VIDEO: [WMV3] 320x240 24bpp 1000.000 fps 138.7 kbps (16.9 kbyte/s)
Clip info:
title:
author:
copyright:
comments:
==========================================================================
Opening video decoder: [dmo] DMO video codecs
Win32 LoadLibrary failed to load: wmv9dmod.dll, /usr/lib/codecs/
wmv9dmod.dll
IMediaObject ERROR: 0x874b221 could not open DMO DLL (0x0 : 0)
Failed to create DMO filter
ERROR: Could not open required DirectShow codec wmv9dmod.dll.
You need to upgrade/install the binary codecs package.
Go to http://www.mplayerhq.hu/dload.html
VDecoder init failed :(
Opening video decoder: [dmo] DMO video codecs
Win32 LoadLibrary failed to load: wmvdmod.dll, /usr/lib/codecs/wmvdmod.dll
IMediaObject ERROR: 0x874b221 could not open DMO DLL (0x0 : 0)
Failed to create DMO filter
ERROR: Could not open required DirectShow codec wmvdmod.dll.
You need to upgrade/install the binary codecs package.
Go to http://www.mplayerhq.hu/dload.html
VDecoder init failed :(
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
[wmv3 @ 0x87bd580]Extra data: 8 bits left, value: 0
Selected video codec: [ffwmv3] vfm: ffmpeg (FFmpeg WMV3/WMV9)
==========================================================================
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, s16le, 64.0 kbit/4.54% (ratio: 8005->176400)
Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg))
==========================================================================
AO: [pulse] 44100Hz 2ch s16le (2 bytes per sample)
Starting playback...
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 320x240 => 320x240 Planar YV12
A: 10.0 V: 10.0 A-V: -0.005 ct: -0.043 150/150 3% 1% 0.2% 0
0
Exiting... (Quit)
----->cut here<------
A list of "errors":
Win32 LoadLibrary failed to load: ...
IMediaObject ERROR: ...
Failed to create DMO filter ...
ERROR: Could not open required ...
VDecoder init failed :(
Some of those could be considered "fatal" but the vid clip plays just
fine.
>> Can xawtv play a standard .mpg, .avi, .wmv, or similar?
>
> xawtv is not a media player. It gets its input from /dev/video not from
> a file, and what format that video is in, I do not know.
OK. That's unfortunate. I was going to suggest running xawtv and
playing a vid clip, of anything, just to make sure it could play
something to the screen. No joy...
> Perhaps it could be possible to stream something which writes to
> /dev/video and then xawtv reads that, but this is pure conjecture.
Never tried something like that. Driver might not be happy...
>> My point is, according to the online man page when you specify the
>> device, e.g. /dev/video0, on the command line it will disable Xvideo.
>
> But so far, /dev/video0 has not been specified on the command line, so
> Xvideo should be be disabled.
Some of the time ANT has specified /dev/video0 on the command line. From
what I can see that isn't necessary. If I remember correctly from the
online man page, xawtv "defaults" to using /dev/video0. That's good!
>> but marketing types don't care about logic or anything.
>
> They may not care about logic but they do care about sales. And since
Yeah, yeah... I'm your typical old school computer geek that has an
innate dislike for marketing types. Used to have a master marketer for a
room mate. Yes, we were kind of the modern version of the "Odd
Couple". :-)
> Is an iPod some type of rocket fuel pod? ;)
I thought it was a new soybean variety... :-) (I'm from Nebraska, where
corn, soybeans, and cattle are the primary component of our gross state
product!)
>> And my guess is the card/driver are defaulting to coax input and maybe
>> channel 4.
>
> Not if the option menu has been used to select S-VHS input.
Well yes, but as we have seen elsewhere we got the driver to look at S-
video input. Your catch on the version 3.x having a problem with newer
xorg versions might be spot on...
Kevin Snodgrass
> Yeah, I am already struggling with Linux GUI stuff. :D
Looks to me like you are struggling more with command line Linux stuff.
And understanding of basic Linux/Unix stuff.
>> I don't understand that error. Do you think it is really important? I
>> know a way to find out. Can xawtv play a standard .mpg, .avi, .wmv, or
>> similar? If so we just need to find one for ANT and have him try
>> playing it. If it plays then that error can probably be ignored...
>
> I can play those in (g)mplayer and VLC. :)
OK, I use mplayer all the time and am familiar with it's quirks and error
messages. With some Winders video clips it will kick out several error
messages, but play the clip just fine.
But according to Mr. Miller, xawtv doesn't play files, just streams,
a.k.a. /dev/video0.
Kevin Snodgrass
> I will look into it later. I am sleepy now, so I don't want to fiddle
> with it for now.
Ah, come on! Sleep is for weenies! ;-)
>>> I am not sure if that PVR-416 is even correct.
>>
>> Pretty sure it is.
>
> OK. :) PVR throws me off. ;)
PVR = Personal Video Recorder. Common descriptor for capture/tuner cards.
> Crap (damn lack of sleep -- woke up at 4 AM PST :P), I meant "xawtv -o
> -v 2" since I wanted debugging go to a file. I even tried a filename
> (e.g., xawtv -v 2 -o log), but nothing.
Well, I don't really understand the man page fully, but I think it means
to use "-o filename" to write "snapshots" to the file. Now, to me a
snapshot would be like a still frame, probably a .jpg picture file. Of
course I may be wrong on that...
> OK! There's so much crap the -d 2 is showing. That's why I wanted to
> capture all that to a file for you guys. :(
Oh, in that case... Try something like this:
$ xawtv -d 2 > xawtvmsg.txt 2> xawtverr.txt
Then the standard "informational" type messages will go to xawtvmsg.txt
and the errors will go to xawtverr.txt.
Note the EXACT syntax there...
Explanation:
$ xawtv -d 2
That is the command you are actually running.
> xawtvmsg.txt
That tells the shell (bash or ksh or whatever) to send the "standard
output" to the file xawtvmsg.txt. "Standard output" is term used in
programming to refer to messages printed to the screen via the "standard
output" file pointer.
2> xawtverr.txt
That tells the shell to send the "standard error" output to the file
xawtverr.txt. "Standard error" is the term used in programming to refer
to messages printed to the screen via the "standard error" file pointer.
Probably not the best description, but, not sure how to explain C
programming concepts to a non-programmer. Read Kernighan and Ritchie. :-)
http://www.amazon.com/Programming-Language-2nd-Brian-Kernighan/
dp/0131103628
>> Run it as I asked above. First:
>>
>> $ xawtv -device /dev/video0 -debug 2
>
> http://pastebin.ca/2038034
>
>> Then:
>>
>> $ xawtv -debug 2
>
> http://pastebin.ca/2038035
>
> For both, I ran it really quick, waited a second on blue video screen,
> and exited.
OK. Was hoping to see something more cluefull. :-) Was worth a try at
least.
And I noticed you switched the two around, i.e. the first output goes to
the second command line. :-)
>> I have a very specific purpose for this. I want to find something out.
>> Adding other parameters, trying your own thing, whatever will not
>> answer my question. This might be very useful if my hunch is correct.
>> I need to compare the output from the two different executions to see
>> if something is happening.
>
> OK.
It didn't happen, therefore my understanding of the online version of the
man page for xawtv is incomplete...
>> That looks good. And as I thought, the default was "Television", i.e.
>> the coax cable jack. But it IS set to read from the S-video jack. Now
>> I'm not sure what to try next, since you are reading from the correct
>> input. Must think about this one...
>
> OK. Let's take a break and call it the night because I am going to
> sleep!
I'm out of ideas. So I will defer to Mr. Miller and his suggestion of
downloading the source for V4.x and compiling. Good luck!
>>>> This may be useful if you can't get anything working with the
>>>> S-video/ composite cabling. But you will have to move the coax cable
>>>> from the TV to the tuner card.
>>>
>>> So VCR's coax cable to TV tuner? Hmm! That could work, but then I have
>>> to rewire all this (messy and crowded at the moment). Ugh.
>>
>> Exactly. Don't know what kind of wiring mess you have there (as I look
>> at the bundle of about 20 cables on MY floor), but that might be the
>> trick at this point.
>
> Heh. :)
OK, I just did a quick count and came up with 37 cables, power cords,
etc... I probably missed a couple... :-)
Kevin Snodgrass
> So you did view the manual page.
>
> Which prompts the question why did you try to use the manual page
> contents as a configuration file?
I don't think ANT knew that /usr/share/man/* were man pages. Some of us
have so much Unix knowledge from 20-30 years ago we forget others don't
just "know" what a man page is and where it can be found in the
filesystem.
>> I always used channel 3 and is still channel 3.
>
> So when I asked you if you had an coaxial RF modulated output on the
> VCR, why did you not tell me that you did not know and told me to go
> read the manual for your VCR in order to find the answer?
Again, ANT probably didn't know what "RF modulated output" meant. I use
the more consumer oriented term "coax" since most people know that is the
type of cable commonly used to connect all things "TV". That is starting
to change with HDMI and component cabling...
Kevin Snodgrass
> Why can't I just type "man xawtvrc"? I never had to use numbers.
You can. But if there are multiple man pages for the same "word" you
might not get the correct one. "man 5 xawtvrc" tells man to use the
"chapter 5 manual". This is all old school Unix stuff.
There are some commands that have an equal in the programming manual.
Example: mount
There is a man page in "chapter 2" for mount, and one in "chapter 8".
The "chapter 2" stuff is for people writing programs in C. You should
have that one if you have the developement stuff from Debian installed.
The "chapter 8" man page is for the mount command, located in /bin/
mount. All Unix and Unix-like systems should have that one.
> Again, this is new and confusing to me.
Some of us have used Unix and Unix-like systems for a LONG time. About
25 years for me. Sometimes we forget that not everyone speaks Unix
fluently.
Kevin Snodgrass
>> First, I am going to post in Debian newsgroups to see if it exist so I
>> don't have to compile.
>
> As you are correct that it does not exist, why would you do this?
>
> Or do you not believe Kevin Snodgrass or myself when we tell you that it
> does not exist?
Well first, don't trust me completely on Debian issues. :-) I just
searched for "debian xawtv" or some such and snooped around for a few
minutes. :-)
On another note, are there "other" repositories of Debian software?
Example, for RedHat/Fedora there are RPMFusion, DAGWiers, ATRPMS and
others. Is it possible that someone, somewhere, has compiled xawtv V4.x
for Debian and put it up on an outside repo?
>> I am not an AV person. :(
>
> Neither am I.
But are you an electrical engineer? "RF modulated output" sounds very EE
to me.
J G Miller
> Oh that's easy when it works without a hitch.
Yes, it works without a hitch once you have got everything
set up correctly ;)
I have put together my own build system of shell scripts with
shell script library functions and once a source package has
been tidied up if necessary and put into my $SRC directories,
I can just run the script to unpack, configure, compile,
and install with stow.
> Something tells me it won't.
You are correct as these things rarely do work out of the box.
In the case of the "new" xawtv, for compiling on Debian/Mint/Ubuntu,
if you want Quicktime support, the paths for the Quicktime headers
have to be edited in the read and write files because the headers
are installed under /usr/include/lqt not /usr/include/quicktime.
> ERROR: Could not open required DirectShow codec wmv9dmod.dll. You need
> to upgrade/install the binary codecs package. Go to
> http://www.mplayerhq.hu/dload.html VDecoder init failed :(
No that is a completely different type of error than the xawtv DGA
X11 server issue.
mplayer is complaining that it cannot find the codec file, not that
it cannot use the DGA on the X11 server which does not exist with
newer ATI and nVidia hardware.
Have you installed the win32 codecs package?
> Some of those could be considered "fatal" but the vid clip plays just
> fine.
This is because mplayer's first choice of codec cannot be found so
it then tries something else which happens to work.
> If I remember correctly from the online man page, xawtv "defaults"
> to using /dev/video0.
That is standard behavior. When there exists the possibility of
multiple hardware interface device files eg video0, video1 etc,
applications default to the first one, numbered 0, unless told
otherwise ;)
> I thought it was a new soybean variety... :-)
This made me laugh. Of course the pods you should be watching out
for are those alien ones on the back of the truck ;)
<http://www.tcm.COM/mediaroom/index.jsp?cid=90206>
> Your catch on the version 3.x having a problem with newer
> xorg versions might be spot on...
Well that is the only thing I have seen so far which appears to explain
the problem
I am glad I have been pushed into getting xawtv version 4 though since
it works as a very lightweight viewer for my DVB-s satellite card.
Kaffeine used to be okay but since the upgrade to the newer version,
it has become bloated and using pulse audio and now frequently stutters
and often the sound dies after abour 2-3 minutes, whereas xawtv is
lightweight and uses ALSA directly, and the channel list can be customized
using a text editor. So all of this has been beneficial for me.
Ant
> incorrect assumption, based on the online man page for xawtv. When it
> said the same config file would be used by motv I guess that put a bug in
> my (leaking) gray matter that motv was part of the same package. Doesn't
> look to be the case...
No problems, dude. This is new to me too. We're just working together to
figure this out. Sheesh, this is way more difficult than I expected.
Heh.
> Not from an xterm. From a virtual console you can. This will lead us
> off into the weeds. Just don't worry about trying anything "frame
> buffer" related...
OK.
> >>> FYI for more clues? I tried a bunch of parameters in xawtv:
> >>>
> >>> $ xawtv -hwscan
> >>> This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.32-5-686)
> >>> looking for available devices
> >>> port 310-341
> >>> type : Xvideo, image scaler
> >>> name : NV17 Video Texture
> >>
> >> This is the output v4l device, i.e. part of X-windows. xawtv will play
> >> the video "into" this device.
> >
> > I assume that's fine.
> Yes.
Cool. :)
> >>> Also, I noticed dmesg no wonder shows errors about my TV tuner like
> >>> last week. Weird.
> >>
> >> That must mean we fixed the kernel module loading issues.
> >
> > Sweet!
> Onward...
:)
--
Quote of the Week: "It doesn't matter what your D&D manual says, you did
not get 5 experience points for killing the giant ant in your kitchen."
--BBspot's Geek Horoscopes (7/30/2004)
/\___/\ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail. If crediting,
( ) then please kindly use Ant nickname and AQFL URL/link.