 |
|
| UK diy (uk.d-i-y) For the discussion of all topics related to diy (do-it-yourself) in the UK. All levels of experience and proficency are welcome to join in to ask questions or offer solutions. |
| Reply |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
#1
Posted to uk.d-i-y
|
|||
|
|||
DTV server, RRi DTV 'Hat' not seen?
Hi all,
I've just got a DTV 'Hat' for my Raspberry Pi 3B+, downloaded, installed and updated Rasbian and installed the tvheadend software. However, during the setup Wizard it's supposed to show the 'Sony' DVT module but doesn't? ;-( I can access tvheadend from another PC on the LAN so that's all working ok etc. So, I installed lshw and ran that but that doesn't show it either but I'm not sure if it would? I was just wondering if any of the RPi owners here had also got the DTV module / hat and did it work for you? Would you expect lshw to show something on the GPIO interface (or how else might I see if the hardware has been 'seen'?) Cheers, T i m |
|
#2
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
T i m wrote:
I was just wondering if any of the RPi owners here had also got the DTV module / hat and did it work for you? Would you expect lshw to show something on the GPIO interface (or how else might I see if the hardware has been 'seen'?) It wouldn't show up - the CXD2880 is attached via SPI and that doesn't have a discovery mechanism (unlike, say, USB). The HAT system has a discovery mechanism (an EEPROM on the board) but that's something specific to the Pi and so won't appear in generic tools like lshw. You need to have i2c enabled in config.txt, and the i2c-dev kernel module loaded, and then you can use i2cdetect to look for the HAT EEPROM: https://www.raspberrypi.org/forums/v...c.php?t=165895 (should show up at 0x50) eepromutils will dump the contents of the EEPROM (which should tell you what kind of HAT it is, etc). Seems you can also look in /proc/device-tree/hat dmesg should also say something about the CXD2880 detected - but you might have to 'modprobe cxd2880' first Theo |
|
#3
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Sun, 21 Oct 2018 23:15:07 +0100, Theo wrote:
T i m wrote: I was just wondering if any of the RPi owners here had also got the DTV module / hat and did it work for you? Would you expect lshw to show something on the GPIO interface (or how else might I see if the hardware has been 'seen'?) It wouldn't show up - the CXD2880 is attached via SPI and that doesn't have a discovery mechanism (unlike, say, USB). The HAT system has a discovery mechanism (an EEPROM on the board) but that's something specific to the Pi and so won't appear in generic tools like lshw. Ah, thanks Theo. You need to have i2c enabled in config.txt, and the i2c-dev kernel module loaded, and then you can use i2cdetect to look for the HAT EEPROM: https://www.raspberrypi.org/forums/v...c.php?t=165895 (should show up at 0x50) Started to check / edit the files bit needed to launch the text editor (or file manager) as sudo and need to look that up. eepromutils will dump the contents of the EEPROM (which should tell you what kind of HAT it is, etc). Couldn't find that in the software packages or apt-get (probably looking at the same repo)? I'll check it out later. Seems you can also look in /proc/device-tree/hat Couldn't find that. ;-( dmesg should also say something about the CXD2880 detected - but you might have to 'modprobe cxd2880' first Ok, that profuced quite a bit but nothing relating to the DTV module that I could see? Thanks for your help so far Theo. Cheers, T i m (posted from the RPi) pi@raspberrypi:~ $ sudo modprobe cxd2880 pi@raspberrypi:~ $ sudo dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.14.71-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1145 SMP Fri Sep 21 15:38:35 BST 2018 [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 8 MiB at 0x3ac00000 [ 0.000000] On node 0 totalpages: 242688 [ 0.000000] free_area_init_node: node 0, pgdat 80c85280, node_mem_map ba39f000 [ 0.000000] Normal zone: 2133 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 242688 pages, LIFO batch:31 [ 0.000000] percpu: Embedded 17 pages/cpu @ba348000 s38720 r8192 d22720 u69632 [ 0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 240555 [ 0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1024 bcm2708_fb.fbheight=768 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=d69ebd8b-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [ 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] Memory: 940232K/970752K available (7168K kernel code, 576K rwdata, 2076K rodata, 1024K init, 698K bss, 22328K reserved, 8192K cma-reserved) [ 0.000000] Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xbb800000 - 0xff800000 (1088 MB) lowmem : 0x80000000 - 0xbb400000 ( 948 MB) modules : 0x7f000000 - 0x80000000 ( 16 MB) .text : 0x80008000 - 0x80800000 (8160 kB) .init : 0x80b00000 - 0x80c00000 (1024 kB) .data : 0x80c00000 - 0x80c9017c ( 577 kB) .bss : 0x80c97f10 - 0x80d468b0 ( 699 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] ftrace: allocating 25273 entries in 75 pages [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns [ 0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns [ 0.000019] Switching to timer-based delay loop, resolution 52ns [ 0.000272] Console: colour dummy device 80x30 [ 0.000289] console [tty1] enabled [ 0.000314] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000) [ 0.000330] pid_max: default: 32768 minimum: 301 [ 0.000644] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000658] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.001597] Disabling memory control group subsystem [ 0.001673] CPU: Testing write buffer coherency: ok [ 0.002088] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.002490] Setting up static identity map for 0x100000 - 0x10003c [ 0.002612] Hierarchical SRCU implementation. [ 0.003296] smp: Bringing up secondary CPUs ... [ 0.004079] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.004927] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.005756] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.005862] smp: Brought up 1 node, 4 CPUs [ 0.005873] SMP: Total of 4 processors activated (153.60 BogoMIPS). [ 0.005878] CPU: All CPU(s) started in HYP mode. [ 0.005882] CPU: Virtualization extensions available. [ 0.006766] devtmpfs: initialized [ 0.017177] random: get_random_u32 called from bucket_table_alloc+0xfc/0x24c with crng_init=0 [ 0.017951] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4 [ 0.018174] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.018191] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.018749] pinctrl co initialized pinctrl subsystem [ 0.019489] NET: Registered protocol family 16 [ 0.022230] DMA: preallocated 1024 KiB pool for atomic coherent allocations [ 0.027194] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.027201] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.027401] Serial: AMBA PL011 UART driver [ 0.029071] bcm2835-mbox 3f00b880.mailbox: mailbox enabled [ 0.029532] uart-pl011 3f201000.serial: could not find pctldev for node /soc/ gpio@7e200000/uart0_pins, deferring probe [ 0.061388] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb813000, dmachans=0x1 [ 0.062802] SCSI subsystem initialized [ 0.063030] usbco registered new interface driver usbfs [ 0.063083] usbco registered new interface driver hub [ 0.063166] usbco registered new device driver usb [ 0.070087] raspberrypi-firmware soc:firmwa Attached to firmware from 2018-09-21 15:43 [ 0.071498] clocksource: Switched to clocksource arch_sys_counter [ 0.148657] VFS: Disk quotas dquot_6.6.0 [ 0.148737] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.148921] FS-Cache: Loaded [ 0.149107] CacheFiles: Loaded [ 0.157113] NET: Registered protocol family 2 [ 0.157829] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.157939] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.158124] TCP: Hash tables configured (established 8192 bind 8192) [ 0.158251] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.158295] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.158519] NET: Registered protocol family 1 [ 0.158989] RPC: Registered named UNIX socket transport module. [ 0.158995] RPC: Registered udp transport module. [ 0.159000] RPC: Registered tcp transport module. [ 0.159005] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.160681] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available [ 0.163462] workingset: timestamp_bits=14 max_order=18 bucket_order=4 [ 0.171664] FS-Cache: Netfs 'nfs' registered for caching [ 0.172273] NFS: Registering the id_resolver key type [ 0.172303] Key type id_resolver registered [ 0.172309] Key type id_legacy registered [ 0.172324] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.174250] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 0.174383] io scheduler noop registered [ 0.174389] io scheduler deadline registered (default) [ 0.174671] io scheduler cfq registered [ 0.174678] io scheduler mq-deadline registered [ 0.174684] io scheduler kyber registered [ 0.176975] BCM2708FB: allocated DMA memory fad00000 [ 0.177001] BCM2708FB: allocated DMA channel 0 @ bb813000 [ 0.199300] Console: switching to colour frame buffer device 128x48 [ 0.213292] bcm2835-rng 3f104000.rng: hwrng registered [ 0.213417] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB) [ 0.213866] vc-sm: Videocore shared memory driver [ 0.214138] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000 [ 0.221522] NOHZ: local_softirq_pending 80 [ 0.223815] brd: module loaded [ 0.232607] loop: module loaded [ 0.232620] Loading iSCSI transport class v2.0-870. [ 0.233276] libphy: Fixed MDIO Bus: probed [ 0.233375] usbco registered new interface driver lan78xx [ 0.233429] usbco registered new interface driver smsc95xx [ 0.233444] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [ 0.261337] dwc_otg 3f980000.usb: base=0xf0980000 [ 0.401495] NOHZ: local_softirq_pending 80 [ 0.421494] NOHZ: local_softirq_pending 80 [ 0.441494] NOHZ: local_softirq_pending 80 [ 0.461595] Core Release: 2.80a [ 0.461603] Setting default values for core params [ 0.461634] Finished setting default values for core params [ 0.661878] Using Buffer DMA mode [ 0.661884] Periodic Transfer Interrupt Enhancement - disabled [ 0.661890] Multiprocessor Interrupt Enhancement - disabled [ 0.661897] OTG VER PARAM: 0, OTG VER FLAG: 0 [ 0.661907] Dedicated Tx FIFOs mode [ 0.662249] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xbad14000 dma = 0xfad14000 len=9024 [ 0.662274] FIQ FSM acceleration enabled for : Non-periodic Split Transactions Periodic Split Transactions High-Speed Isochronous Endpoints Interrupt/Control Split Transaction hack enabled [ 0.662281] dwc_otg: Microframe scheduler enabled [ 0.662334] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805e9c5c [ 0.662346] WARN::hcd_init_fiq:460: FIQ ASM at 0x805e9fc4 length 36 [ 0.662358] WARN::hcd_init_fiq:486: MPHI regs_base at 0xf0006000 [ 0.662413] dwc_otg 3f980000.usb: DWC OTG Controller [ 0.662443] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1 [ 0.662473] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000 [ 0.662521] Init: Port Power? op_state=1 [ 0.662526] Init: Power Port (0) [ 0.662728] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 0.662739] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.662748] usb usb1: Product: DWC OTG Controller [ 0.662756] usb usb1: Manufacturer: Linux 4.14.71-v7+ dwc_otg_hcd [ 0.662764] usb usb1: SerialNumber: 3f980000.usb [ 0.663378] hub 1-0:1.0: USB hub found [ 0.663418] hub 1-0:1.0: 1 port detected [ 0.663954] dwc_otg: FIQ enabled [ 0.663959] dwc_otg: NAK holdoff enabled [ 0.663964] dwc_otg: FIQ split-transaction FSM enabled [ 0.663974] Module dwc_common_port init [ 0.664211] usbco registered new interface driver usb-storage [ 0.664379] mousedev: PS/2 mouse device common for all mice [ 0.664449] IR NEC protocol handler initialized [ 0.664454] IR RC5(x/sz) protocol handler initialized [ 0.664460] IR RC6 protocol handler initialized [ 0.664465] IR JVC protocol handler initialized [ 0.664470] IR Sony protocol handler initialized [ 0.664475] IR SANYO protocol handler initialized [ 0.664481] IR Sharp protocol handler initialized [ 0.664486] IR MCE Keyboard/mouse protocol handler initialized [ 0.664490] IR XMP protocol handler initialized [ 0.665151] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer [ 0.665404] bcm2835-cpufreq: min=600000 max=1400000 [ 0.665746] sdhci: Secure Digital Host Controller Interface driver [ 0.665750] sdhci: Copyright(c) Pierre Ossman [ 0.666098] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe [ 0.666411] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [ 0.666499] sdhci-pltfm: SDHCI platform and OF driver helper [ 0.667917] ledtrig-cpu: registered to indicate activity on CPUs [ 0.668062] hidraw: raw HID events driver (C) Jiri Kosina [ 0.668216] usbco registered new interface driver usbhid [ 0.668220] usbhid: USB HID core driver [ 0.668819] vchiq: vchiq_init_state: slot_zero = bad80000, is_master = 0 [ 0.670250] [vc_sm_connected_init]: start [ 0.679139] [vc_sm_connected_init]: end - returning 0 [ 0.679713] Initializing XFRM netlink socket [ 0.679738] NET: Registered protocol family 17 [ 0.679834] Key type dns_resolver registered [ 0.680372] Registering SWP/SWPB emulation handler [ 0.680957] registered taskstats version 1 [ 0.686860] uart-pl011 3f201000.serial: cts_event_workaround enabled [ 0.686931] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2 [ 0.688800] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0 [ 0.688810] mmc-bcm2835 3f300000.mmc: DMA channel allocated [ 0.752126] sdhost: log_buf @ bad13000 (fad13000) [ 0.789979] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 0.791556] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 0.793106] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 0.795881] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 0.831520] mmc0: sdhost-bcm2835 loaded - DMA enabled (1) [ 0.832549] of_cfs_init [ 0.832630] of_cfs_init: OK [ 0.833174] Waiting for root device PARTUUID=d69ebd8b-02... [ 0.874022] random: fast init done [ 0.881244] mmc1: new high speed SDIO card at address 0001 [ 0.881752] Indeed it is in host mode hprt0 = 00021501 [ 1.011719] mmc0: host does not support reading read-only switch, assuming write- enable [ 1.015880] mmc0: new high speed SDXC card at address aaaa [ 1.016336] mmcblk0: mmc0:aaaa SB64G 59.5 GiB [ 1.018695] mmcblk0: p1 p2 [ 1.046534] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [ 1.046542] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [ 1.086060] NOHZ: local_softirq_pending 40 [ 1.091528] usb 1-1: new high-speed USB device number 2 using dwc_otg [ 1.091655] Indeed it is in host mode hprt0 = 00001101 [ 1.170617] NOHZ: local_softirq_pending 40 [ 1.176985] NOHZ: local_softirq_pending 40 [ 1.183360] NOHZ: local_softirq_pending 40 [ 1.189741] NOHZ: local_softirq_pending 40 [ 1.196105] NOHZ: local_softirq_pending 40 [ 1.331778] usb 1-1: New USB device found, idVendor=0424, idProduct=2514 [ 1.331790] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.332483] hub 1-1:1.0: USB hub found [ 1.332559] hub 1-1:1.0: 4 ports detected [ 1.651574] usb 1-1.1: new high-speed USB device number 3 using dwc_otg [ 1.738633] EXT4-fs (mmcblk0p2): recovery complete [ 1.740350] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 1.740409] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [ 1.742205] devtmpfs: mounted [ 1.745176] Freeing unused kernel memory: 1024K [ 1.781836] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514 [ 1.781850] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.782448] hub 1-1.1:1.0: USB hub found [ 1.782523] hub 1-1.1:1.0: 3 ports detected [ 2.101544] usb 1-1.1.3: new full-speed USB device number 4 using dwc_otg [ 2.123521] systemd[1]: System time before build time, advancing clock. [ 2.233537] usb 1-1.1.3: New USB device found, idVendor=0557, idProduct=8021 [ 2.233551] usb 1-1.1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.234376] hub 1-1.1.3:1.0: USB hub found [ 2.234889] hub 1-1.1.3:1.0: 4 ports detected [ 2.239958] NET: Registered protocol family 10 [ 2.241001] Segment Routing with IPv6 [ 2.251961] ip_tables: (C) 2000-2006 Netfilter Core Team [ 2.269409] random: systemd: uninitialized urandom read (16 bytes read) [ 2.274561] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [ 2.275141] systemd[1]: Detected architecture arm. [ 2.282962] systemd[1]: Set hostname to raspberrypi. [ 2.322264] random: systemd: uninitialized urandom read (16 bytes read) [ 2.354001] random: systemd-cryptse: uninitialized urandom read (16 bytes read) [ 2.561575] usb 1-1.1.1: new high-speed USB device number 5 using dwc_otg [ 2.692055] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800 [ 2.692071] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.746001] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 2.746929] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 2.747232] systemd[1]: Listening on udev Kernel Socket. [ 2.747602] systemd[1]: Listening on Journal Socket. [ 2.747883] systemd[1]: Listening on udev Control Socket. [ 2.748630] systemd[1]: Created slice User and Session Slice. [ 2.748883] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [ 2.792015] usb 1-1.1.3.1: new full-speed USB device number 6 using dwc_otg [ 2.868457] i2c /dev entries driver [ 2.956687] usb 1-1.1.3.1: New USB device found, idVendor=04d9, idProduct=1503 [ 2.956703] usb 1-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.956712] usb 1-1.1.3.1: Product: USB Keyboard [ 2.956724] usb 1-1.1.3.1: Manufacturer: [ 2.975335] input: USB Keyboard as /devices/platform/soc/3f980000.usb/ usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.1/1-1.1.3.1:1.0/0003:04D9:1503.0001/input/input0 [ 2.984219] libphy: lan78xx-mdiobus: probed [ 3.042631] hid-generic 0003:04D9:1503.0001: input,hidraw0: USB HID v1.10 Keyboard [ USB Keyboard] on usb-3f980000.usb-1.1.3.1/input0 [ 3.064656] input: USB Keyboard as /devices/platform/soc/3f980000.usb/ usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.1/1-1.1.3.1:1.1/0003:04D9:1503.0002/input/input1 [ 3.131860] hid-generic 0003:04D9:1503.0002: input,hidraw1: USB HID v1.10 Device [ USB Keyboard] on usb-3f980000.usb-1.1.3.1/input1 [ 3.145453] input: USB Keyboard as /devices/platform/soc/3f980000.usb/ usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.1/1-1.1.3.1:1.2/0003:04D9:1503.0003/input/input2 [ 3.145926] hid-generic 0003:04D9:1503.0003: input,hidraw2: USB HID v1.10 Mouse [ USB Keyboard] on usb-3f980000.usb-1.1.3.1/input2 [ 3.241557] usb 1-1.1.3.2: new low-speed USB device number 7 using dwc_otg [ 3.377806] usb 1-1.1.3.2: New USB device found, idVendor=045e, idProduct=0040 [ 3.377826] usb 1-1.1.3.2: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [ 3.377835] usb 1-1.1.3.2: Product: Microsoft 3-Button Mouse with IntelliEye(TM) [ 3.377846] usb 1-1.1.3.2: Manufacturer: Microsoft [ 3.386546] input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as / devices/platform/soc/3f980000.usb/ usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.2/1-1.1.3.2:1.0/0003:045E:0040.0004/input/input3 [ 3.387075] hid-generic 0003:045E:0040.0004: input,hidraw3: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-3f980000.usb-1.1.3.2/input0 [ 3.492636] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [ 3.581386] systemd-journald[89]: Received request to flush runtime journal from PID 1 [ 4.319016] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. [ 4.332293] bcm2835_alsa bcm2835_alsa: card created with 8 channels [ 4.491846] brcmfmac: F1 signature read @0x18000000=0x15264345 [ 4.503010] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455- sdio.bin for chip 0x004345(17221) rev 0x000006 [ 4.503478] usbco registered new interface driver brcmfmac [ 4.740261] random: crng init done [ 4.740283] random: 7 urandom warning(s) missed due to ratelimiting [ 4.889754] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 [ 4.891096] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09 18:56:28 [ 5.667200] uart-pl011 3f201000.serial: no DMA platform data [ 6.335045] lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped [ 6.335326] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 6.354283] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 7.333331] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS [ 12.329668] Bluetooth: Core ver 2.22 [ 12.329723] NET: Registered protocol family 31 [ 12.329726] Bluetooth: HCI device and connection manager initialized [ 12.329742] Bluetooth: HCI socket layer initialized [ 12.329749] Bluetooth: L2CAP socket layer initialized [ 12.329770] Bluetooth: SCO socket layer initialized [ 12.344241] Bluetooth: HCI UART driver ver 2.3 [ 12.344250] Bluetooth: HCI UART protocol H4 registered [ 12.344252] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 12.344376] Bluetooth: HCI UART protocol Broadcom registered [ 12.641718] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 12.641728] Bluetooth: BNEP filters: protocol multicast [ 12.641745] Bluetooth: BNEP socket layer initialized [ 12.699251] Bluetooth: RFCOMM TTY layer initialized [ 12.699276] Bluetooth: RFCOMM socket layer initialized [ 12.699302] Bluetooth: RFCOMM ver 1.11 [ 13.087668] fuse init (API version 7.26) [ 151.552404] usb 1-1.1.3.2: USB disconnect, device number 7 [ 184.640869] usb 1-1.1.3.2: new low-speed USB device number 8 using dwc_otg [ 184.776787] usb 1-1.1.3.2: New USB device found, idVendor=045e, idProduct=0040 [ 184.776802] usb 1-1.1.3.2: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [ 184.776811] usb 1-1.1.3.2: Product: Microsoft 3-Button Mouse with IntelliEye(TM) [ 184.776820] usb 1-1.1.3.2: Manufacturer: Microsoft [ 184.782959] input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as / devices/platform/soc/3f980000.usb/ usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.2/1-1.1.3.2:1.0/0003:045E:0040.0005/input/input4 [ 184.788704] hid-generic 0003:045E:0040.0005: input,hidraw3: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-3f980000.usb-1.1.3.2/input0 [ 346.104160] usb 1-1.1.3.2: USB disconnect, device number 8 [ 396.992422] usb 1-1.1.3.2: new low-speed USB device number 9 using dwc_otg [ 397.128536] usb 1-1.1.3.2: New USB device found, idVendor=045e, idProduct=0040 [ 397.128552] usb 1-1.1.3.2: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [ 397.128561] usb 1-1.1.3.2: Product: Microsoft 3-Button Mouse with IntelliEye(TM) [ 397.128569] usb 1-1.1.3.2: Manufacturer: Microsoft [ 397.141363] input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as / devices/platform/soc/3f980000.usb/ usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.2/1-1.1.3.2:1.0/0003:045E:0040.0006/input/input5 [ 397.144206] hid-generic 0003:045E:0040.0006: input,hidraw3: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-3f980000.usb-1.1.3.2/input0 pi@raspberrypi:~ $ |
|
#4
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
T i m wrote:
So, I installed lshw and ran that but that doesn't show it either but I'm not sure if it would? From discussions elsewhere, the tuner chip isn't presented to the Pi in the same way as it would be if there was e.g. a PCI bus involved, it's just hooked to some GPIO pins, so the it won't be seen as a device like USB or ethernet. |
|
#5
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
"T i m" wrote in message
... Hi all, I've just got a DTV 'Hat' for my Raspberry Pi 3B+, downloaded, installed and updated Rasbian and installed the tvheadend software. However, during the setup Wizard it's supposed to show the 'Sony' DVT module but doesn't? ;-( I can access tvheadend from another PC on the LAN so that's all working ok etc. So, I installed lshw and ran that but that doesn't show it either but I'm not sure if it would? I was just wondering if any of the RPi owners here had also got the DTV module / hat and did it work for you? Would you expect lshw to show something on the GPIO interface (or how else might I see if the hardware has been 'seen'?) Does the HAT device show up as a device in /dev/dvb and are there diagnostic lines produced by "dmesg" which relate to the device? My R Pi has a couple of USB DVB-T devices and I see: ls -lR /dev/dvb /dev/dvb: total 0 drwxr-xr-x 2 root root 120 Oct 21 12:21 adapter0 drwxr-xr-x 2 root root 120 Oct 21 12:21 adapter1 /dev/dvb/adapter0: total 0 crw-rw----+ 1 root video 212, 4 Oct 21 12:21 demux0 crw-rw----+ 1 root video 212, 5 Oct 21 12:21 dvr0 crw-rw----+ 1 root video 212, 3 Oct 21 12:21 frontend0 crw-rw----+ 1 root video 212, 7 Oct 21 12:21 net0 /dev/dvb/adapter1: total 0 crw-rw----+ 1 root video 212, 68 Oct 21 12:21 demux0 crw-rw----+ 1 root video 212, 69 Oct 21 12:21 dvr0 crw-rw----+ 1 root video 212, 67 Oct 21 12:21 frontend0 crw-rw----+ 1 root video 212, 71 Oct 21 12:21 net0 and (for devices PCTV 292e and Hauppauge Nova T-stick) dmesg .... [ 5.349387] em28xx 1-1.2:1.0: New device PCTV PCTV 292e @ 480 Mbps (2013:025f, interface 0, class 0) [ 5.349404] em28xx 1-1.2:1.0: DVB interface 0 found: isoc [ 5.350115] em28xx 1-1.2:1.0: chip ID is em28178 [ 5.462567] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware [ 5.462706] random: crng init done [ 5.462720] random: 7 urandom warning(s) missed due to ratelimiting [ 5.469714] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [ 5.568004] dib0700: firmware started successfully. [ 5.707651] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 [ 5.708246] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09 18:56:28 [ 6.081786] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. [ 6.082231] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 6.082368] dvbdev: DVB: registering new adapter (Hauppauge Nova-T Stick) [ 6.389507] usb 1-1.1.3: DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)... [ 6.657522] dib0070: DiB0070: successfully identified [ 6.657606] Registered IR keymap rc-dib0700-rc5 [ 6.677753] rc rc0: IR-receiver inside an USB DVB receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/rc/rc0 [ 6.687061] input: IR-receiver inside an USB DVB receiver as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/rc/rc0/input0 [ 6.687112] dvb-usb: schedule remote query interval to 50 msecs. [ 6.687132] dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected. [ 6.701473] usbco registered new interface driver dvb_usb_dib0700 [ 6.858055] uart-pl011 3f201000.serial: no DMA platform data [ 7.421007] em28xx 1-1.2:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xc013f904 [ 7.421023] em28xx 1-1.2:1.0: EEPROM info: [ 7.421033] em28xx 1-1.2:1.0: microcode start address = 0x0004, boot configuration = 0x01 [ 7.429936] em28xx 1-1.2:1.0: AC97 audio (5 sample rates) [ 7.429953] em28xx 1-1.2:1.0: 500mA max power [ 7.429978] em28xx 1-1.2:1.0: Table at offset 0x27, strings=0x146a, 0x1888, 0x0a7e [ 7.430482] em28xx 1-1.2:1.0: Identified as PCTV tripleStick (292e) (card=94) [ 7.430496] em28xx 1-1.2:1.0: dvb set to isoc mode. [ 7.434584] usbco registered new interface driver em28xx [ 7.457984] em28xx 1-1.2:1.0: Binding DVB extension [ 7.558124] i2c i2c-10: Added multiplexed i2c bus 11 [ 7.558147] si2168 10-0064: Silicon Labs Si2168-B40 successfully identified [ 7.558156] si2168 10-0064: firmware version: B 4.0.2 [ 7.582064] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS [ 7.606117] si2157 11-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached [ 7.606245] dvbdev: DVB: registering new adapter (1-1.2:1.0) [ 7.606262] em28xx 1-1.2:1.0: DVB: registering adapter 1 frontend 0 (Silicon Labs Si2168)... [ 7.607945] em28xx 1-1.2:1.0: DVB extension successfully initialized [ 7.607962] em28xx: Registered (Em28xx dvb Extension) extension [ 7.682613] em28xx 1-1.2:1.0: Registering input extension [ 7.683161] Registered IR keymap rc-pinnacle-pctv-hd [ 7.683684] rc rc1: 1-1.2:1.0 IR as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/rc/rc1 [ 7.683898] input: 1-1.2:1.0 IR as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/rc/rc1/input1 [ 7.684236] em28xx 1-1.2:1.0: Input extension successfully initialized [ 7.684245] em28xx: Registered (Em28xx Input Extension) extension [ 8.663982] lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped [ 8.664165] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 8.683171] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 10.163119] si2168 10-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw' [ 10.442320] si2168 10-0064: firmware version: B 4.0.11 [ 10.447357] si2157 11-0060: found a 'Silicon Labs Si2157-A30' [ 10.495863] si2157 11-0060: firmware version: 3.0.5 [ 10.495907] em28xx 1-1.2:1.0: DVB: adapter 1 frontend 0 frequency 0 out of range (42000000..870000000) [ 10.555471] usb 1-1.1.3: DVB: adapter 0 frontend 0 frequency 0 out of range (45000000..860000000) [ 12.481046] warning: process `colord-sane' used the deprecated sysctl system call with 8.1.2. I'd expect the HAT to show up similarly. |
|
#6
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 08:15:28 +0100, Andy Burns
wrote: T i m wrote: So, I installed lshw and ran that but that doesn't show it either but I'm not sure if it would? From discussions elsewhere, the tuner chip isn't presented to the Pi in the same way as it would be if there was e.g. a PCI bus involved, it's just hooked to some GPIO pins, so the it won't be seen as a device like USB or ethernet. So I understand Andy (Theo sneaked that info in earlier), but apparently there are ways of checking to 'see' the module but not that I have managed to get working yet. Theo mentioned 'eepromutils' and I've since found, downloaded, un archived and attempted to install / use it but as is often the case with such Linuxy things, the readme assumes more knowledge than I have. https://github.com/raspberrypi/hats 'Make' seemed to do something, not sure what to do with the 'makefile' instruction (if that was what it was, from memory). It may have worked (something happened) and I simply don't know how to launch the program? Also, I was concerned I might do some damage to any PROM. ;-( There was also suggestion of editing some config files but whilst I found the files and checked / edited / added the suggested text, I didn't have sufficient rights to be able to save those changes. Again, I'm guessing I need to launch the editor (or filemanager) as sudo but wasn't sure what the FM was called and didn't get as far as finding the name of the text editor (so I could launch it from the CLI with sudo)? On a more practical note, I'm not sure if the issue is an electro - mechanical one as I'm not sure of the contact between the (supplied) Pi header extender and the socket on the DTV hat is particularly good. The 'socket' is on the top of the hat so the pins of the header extender have to pass though the hat PCB to make connection and they only just do so (you only feel resistance to the insertion over the last .5mm or so)? https://thepihut.com/blogs/raspberry-pi-tutorials/how-to-stream-digital-tv-with-the-raspberry-pi-tv-hat#assembly Cheers, T i m p.s. Do you happen to know when the std DTV / Freeview switchoff might happen as this experiment was partly to see DTV-T2 and the eventual replacement of our Toppy boxes? |
|
#7
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
T i m wrote:
Andy Burns wrote: it won't be seen as a device like USB or ethernet. So I understand Andy (Theo sneaked that info in earlier), but apparently there are ways of checking to 'see' the module but not that I have managed to get working yet. Normally (on a PC rather than SoC) tuner chips are tied into I2C ports on the PCI bus, I've built and tweaked various V4L drivers over the years. Is there a special driver for the tuner which understands it's "behind" the GPIO pins, e.g. rpi-cxd2880.kz that you can modprobe? Theo mentioned 'eepromutils' and I've since found, downloaded, un archived and attempted to install / use it but as is often the case with such Linuxy things, the readme assumes more knowledge than I have. https://github.com/raspberrypi/hats 'Make' seemed to do something, not sure what to do with the 'makefile' instruction (if that was what it was, from memory). normally you'd run 'make' but it's likely you're expected to cross-compile it on a PC, rather then on the Pi itself which would be rather slow. p.s. Do you happen to know when the std DTV / Freeview switchoff might happen as this experiment was partly to see DTV-T2 and the eventual replacement of our Toppy boxes? The pressure will occur when the 700MHz bands are sold off (for 5G phones or whatever) the transmitters have been re-shuffling for the last year, and will continue next year, it's possible that COM7/COM8 will be allowed to live-on in the duplex gap between mobile RX and TX, or whoever buys the spetrum may have other ideas, and then I suspect arquiva would have to consider moving all (or maybe all bar one) muxes to DVB-T2 to maximize which channels could continue broadcasting |
|
#8
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
T i m wrote:
I installed lshw and ran that but that doesn't show it I doubt it would show, but lsdvb ought to (you might need to install dvb-apps or whatever package debian/raspbian calls it). I know you said you updated the O/S, are you sure that went ok? presume only the very latest will include the tuner driver. |
|
#9
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On 21/10/2018 22:35, T i m wrote:
Hi all, I've just got a DTV 'Hat' for my Raspberry Pi 3B+, downloaded, installed and updated Rasbian and installed the tvheadend software. However, during the setup Wizard it's supposed to show the 'Sony' DVT module but doesn't? ;-( I can access tvheadend from another PC on the LAN so that's all working ok etc. So, I installed lshw and ran that but that doesn't show it either but I'm not sure if it would? I was just wondering if any of the RPi owners here had also got the DTV module / hat and did it work for you? Would you expect lshw to show something on the GPIO interface (or how else might I see if the hardware has been 'seen'?) Did you see: https://thepihut.com/blogs/raspberry...erry-pi-tv-hat -- Cheers, John. /================================================== ===============\ | Internode Ltd - http://www.internode.co.uk | |-----------------------------------------------------------------| | John Rumm - john(at)internode(dot)co(dot)uk | \================================================= ================/ |
|
#10
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On 22/10/2018 09:10, T i m wrote:
There was also suggestion of editing some config files but whilst I found the files and checked / edited / added the suggested text, I didn't have sufficient rights to be able to save those changes. Again, I'm guessing I need to launch the editor (or filemanager) as sudo but wasn't sure what the FM was called and didn't get as far as finding the name of the text editor (so I could launch it from the CLI with sudo)? The editor "nano" is usually setup and ready to go on the pi. So nano filename or sudo nano filename etc. -- Cheers, John. /================================================== ===============\ | Internode Ltd - http://www.internode.co.uk | |-----------------------------------------------------------------| | John Rumm - john(at)internode(dot)co(dot)uk | \================================================= ================/ |
|
#11
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
"John Rumm" wrote in message
o.uk... On 22/10/2018 09:10, T i m wrote: There was also suggestion of editing some config files but whilst I found the files and checked / edited / added the suggested text, I didn't have sufficient rights to be able to save those changes. Again, I'm guessing I need to launch the editor (or filemanager) as sudo but wasn't sure what the FM was called and didn't get as far as finding the name of the text editor (so I could launch it from the CLI with sudo)? The editor "nano" is usually setup and ready to go on the pi. So nano filename or sudo nano filename etc. There is also the "Text Editor" (as described in (Raspberry button) | Accessories) which is also known as Leafpad. Leafpad is more like Notepad on Windows: it supports click-and-drag to select parts of lines so they can be copied (Ctrl-C), cut (Ctrl-V) or pasted (Ctrl-V), as for Windows. Nano is a bit more clunky and it probably a skinned version of vi, the standard Unix editor. The file manager is also in (Raspberry button) | Accessories, though I think as standard there's also a shortcut to it on the taskbar next to the Raspberry button. Depending on the edits that you need to make, it *may* be easier to copy a protected file to your own home directory, edit it with Leafpad and then use "sudo cp" to copy it back over the top of the original file, rather than mastering nano. |
|
#12
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 11:46:42 +0100, John Rumm
wrote: snip Did you see: https://thepihut.com/blogs/raspberry...erry-pi-tv-hat Hi John and yes (thanks), that was the walk through that 1) gave me the confidence to but the Hat in the first place and 2) followed (to the letter) to try to set it up (and I've fired off a question to The Pi Hut where I got it from etc). TBH, I haven't actually tried it near an aerial because at no point has the tuner showed itself ... and the wizard channel scan runs instantly ... so I assumed I would be wasting my time (but I still might). ;-( Cheers, T i m |
|
#13
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 09:35:38 +0100, Andy Burns
wrote: T i m wrote: Andy Burns wrote: it won't be seen as a device like USB or ethernet. So I understand Andy (Theo sneaked that info in earlier), but apparently there are ways of checking to 'see' the module but not that I have managed to get working yet. Normally (on a PC rather than SoC) tuner chips are tied into I2C ports on the PCI bus, I've built and tweaked various V4L drivers over the years. Ok. Is there a special driver for the tuner which understands it's "behind" the GPIO pins, e.g. rpi-cxd2880.kz that you can modprobe? I'm assuming there must be because I followed their tutorial (that looked like the Linux stuff shouldn't be an issue, even for me) but it just didn't work (as their tutorial suggested). https://thepihut.com/blogs/raspberry-pi-tutorials/how-to-stream-digital-tv-with-the-raspberry-pi-tv-hat Everything, other than the tuner hat showing itself ... works, even the remote access (LAN). Theo mentioned 'eepromutils' and I've since found, downloaded, un archived and attempted to install / use it but as is often the case with such Linuxy things, the readme assumes more knowledge than I have. https://github.com/raspberrypi/hats 'Make' seemed to do something, not sure what to do with the 'makefile' instruction (if that was what it was, from memory). normally you'd run 'make' but it's likely you're expected to cross-compile it on a PC, rather then on the Pi itself which would be rather slow. I don't care about slow as long as it (eventually) works Andy. ;-) p.s. Do you happen to know when the std DTV / Freeview switchoff might happen as this experiment was partly to see DTV-T2 and the eventual replacement of our Toppy boxes? The pressure will occur when the 700MHz bands are sold off (for 5G phones or whatever) the transmitters have been re-shuffling for the last year, and will continue next year, it's possible that COM7/COM8 will be allowed to live-on in the duplex gap between mobile RX and TX, or whoever buys the spetrum may have other ideas, and then I suspect arquiva would have to consider moving all (or maybe all bar one) muxes to DVB-T2 to maximize which channels could continue broadcasting Thanks ... so it's all happening but no deadlines as such? Cheers, T i m |
|
#14
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 11:48:55 +0100, John Rumm
wrote: On 22/10/2018 09:10, T i m wrote: There was also suggestion of editing some config files but whilst I found the files and checked / edited / added the suggested text, I didn't have sufficient rights to be able to save those changes. Again, I'm guessing I need to launch the editor (or filemanager) as sudo but wasn't sure what the FM was called and didn't get as far as finding the name of the text editor (so I could launch it from the CLI with sudo)? The editor "nano" is usually setup and ready to go on the pi. Yeah, I am lightly familiar with nano but I don't prefer it over a basic notepad like text editor (as supplied with Rasbaian). It was also late, I was frustrated that it didn't 'just work' n the first place etc ... ;-( So nano filename or sudo nano filename But you first have to navigate to the relevant folders or include the path in the cli? I would 'like' to be able to right click on a folder and open it as sudo (and therefore do what I like in there, as I have / can with Ubuntu / Mint) or run the Text editor from the menu as sudo and just do what I want when I've navigated to the file via the GUI. I appreciate it's only a RPi (that's actually as fast as this old XP Mac Mini g) but it is 2018 after all! ;-) Cheers, T i m |
|
#15
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 12:26:17 +0100, "NY" wrote:
"John Rumm" wrote in message snip sudo nano filename etc. There is also the "Text Editor" (as described in (Raspberry button) | Accessories) which is also known as Leafpad. Leafpad is more like Notepad on Windows: it supports click-and-drag to select parts of lines so they can be copied (Ctrl-C), cut (Ctrl-V) or pasted (Ctrl-V), as for Windows. Nano is a bit more clunky and it probably a skinned version of vi, the standard Unix editor. Ah, so, had I issued 'sudo leafpad' I could have started it with decent rights and then navigated to the files using the GUI? The file manager is also in (Raspberry button) | Accessories, though I think as standard there's also a shortcut to it on the taskbar next to the Raspberry button. Yes, but I couldn't find the name of it in any 'About' etc to know how to launch it from the CLI as sudo? ;-( Depending on the edits that you need to make, it *may* be easier to copy a protected file to your own home directory, edit it with Leafpad and then use "sudo cp" to copy it back over the top of the original file, rather than mastering nano. Whilst I get the kludge and have used similar from the GUI, I am much pore likely to succeed / be productive / finish the job if I can do it all from the GUI. Ok, I might 'sudo apt-get install program' from the CLI rather than bothering to launch the package manager or install / run synaptic etc but that's about it (out of choice). ;-) Cheers, T i m |
|
#16
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 09:05:45 +0100, NY wrote:
snip Does the HAT device show up as a device in /dev/dvb and are there diagnostic lines produced by "dmesg" which relate to the device? My R Pi has a couple of USB DVB-T devices and I see: ls -lR /dev/dvb /dev/dvb: total 0 drwxr-xr-x 2 root root 120 Oct 21 12:21 adapter0 drwxr-xr-x 2 root root 120 Oct 21 12:21 adapter1 pi@raspberrypi:~ $ ls -lR /dev/dvb bash: -lR: command not found /dev/dvb/adapter0: total 0 crw-rw----+ 1 root video 212, 4 Oct 21 12:21 demux0 crw-rw----+ 1 root video 212, 5 Oct 21 12:21 dvr0 crw-rw----+ 1 root video 212, 3 Oct 21 12:21 frontend0 crw-rw----+ 1 root video 212, 7 Oct 21 12:21 net0 /dev/dvb/adapter1: total 0 crw-rw----+ 1 root video 212, 68 Oct 21 12:21 demux0 crw-rw----+ 1 root video 212, 69 Oct 21 12:21 dvr0 crw-rw----+ 1 root video 212, 67 Oct 21 12:21 frontend0 crw-rw----+ 1 root video 212, 71 Oct 21 12:21 net0 and (for devices PCTV 292e and Hauppauge Nova T-stick) dmesg pi@raspberrypi:~ $ dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.14.71-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1145 SMP Fri Sep 21 15:38:35 BST 2018 [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] cma: Reserved 8 MiB at 0x3ac00000 [ 0.000000] On node 0 totalpages: 242688 [ 0.000000] free_area_init_node: node 0, pgdat 80c85280, node_mem_map ba39f000 [ 0.000000] Normal zone: 2133 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 242688 pages, LIFO batch:31 [ 0.000000] percpu: Embedded 17 pages/cpu @ba348000 s38720 r8192 d22720 u69632 [ 0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 240555 [ 0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1024 bcm2708_fb.fbheight=768 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=d69ebd8b-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [ 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] Memory: 940232K/970752K available (7168K kernel code, 576K rwdata, 2076K rodata, 1024K init, 698K bss, 22328K reserved, 8192K cma-reserved) [ 0.000000] Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xbb800000 - 0xff800000 (1088 MB) lowmem : 0x80000000 - 0xbb400000 ( 948 MB) modules : 0x7f000000 - 0x80000000 ( 16 MB) .text : 0x80008000 - 0x80800000 (8160 kB) .init : 0x80b00000 - 0x80c00000 (1024 kB) .data : 0x80c00000 - 0x80c9017c ( 577 kB) .bss : 0x80c97f10 - 0x80d468b0 ( 699 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] ftrace: allocating 25273 entries in 75 pages [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns [ 0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns [ 0.000018] Switching to timer-based delay loop, resolution 52ns [ 0.000267] Console: colour dummy device 80x30 [ 0.000285] console [tty1] enabled [ 0.000309] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000) [ 0.000324] pid_max: default: 32768 minimum: 301 [ 0.000637] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000652] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.001588] Disabling memory control group subsystem [ 0.001662] CPU: Testing write buffer coherency: ok [ 0.002074] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.002480] Setting up static identity map for 0x100000 - 0x10003c [ 0.002603] Hierarchical SRCU implementation. [ 0.003282] smp: Bringing up secondary CPUs ... [ 0.004064] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.004912] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.005742] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.005847] smp: Brought up 1 node, 4 CPUs [ 0.005858] SMP: Total of 4 processors activated (153.60 BogoMIPS). [ 0.005864] CPU: All CPU(s) started in HYP mode. [ 0.005868] CPU: Virtualization extensions available. [ 0.006747] devtmpfs: initialized [ 0.017163] random: get_random_u32 called from bucket_table_alloc+0xfc/0x24c with crng_init=0 [ 0.017933] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4 [ 0.018155] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.018173] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.018726] pinctrl co initialized pinctrl subsystem [ 0.019469] NET: Registered protocol family 16 [ 0.022218] DMA: preallocated 1024 KiB pool for atomic coherent allocations [ 0.027179] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.027186] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.027390] Serial: AMBA PL011 UART driver [ 0.029057] bcm2835-mbox 3f00b880.mailbox: mailbox enabled [ 0.029517] uart-pl011 3f201000.serial: could not find pctldev for node /soc/ gpio@7e200000/uart0_pins, deferring probe [ 0.061383] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb813000, dmachans=0x1 [ 0.062802] SCSI subsystem initialized [ 0.063029] usbco registered new interface driver usbfs [ 0.063081] usbco registered new interface driver hub [ 0.063165] usbco registered new device driver usb [ 0.070088] raspberrypi-firmware soc:firmwa Attached to firmware from 2018-09-21 15:43 [ 0.071503] clocksource: Switched to clocksource arch_sys_counter [ 0.148652] VFS: Disk quotas dquot_6.6.0 [ 0.148732] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.148917] FS-Cache: Loaded [ 0.149102] CacheFiles: Loaded [ 0.157109] NET: Registered protocol family 2 [ 0.157828] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.157938] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.158123] TCP: Hash tables configured (established 8192 bind 8192) [ 0.158250] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.158295] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.158518] NET: Registered protocol family 1 [ 0.158985] RPC: Registered named UNIX socket transport module. [ 0.158990] RPC: Registered udp transport module. [ 0.158996] RPC: Registered tcp transport module. [ 0.159001] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.160674] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available [ 0.163464] workingset: timestamp_bits=14 max_order=18 bucket_order=4 [ 0.171663] FS-Cache: Netfs 'nfs' registered for caching [ 0.172270] NFS: Registering the id_resolver key type [ 0.172302] Key type id_resolver registered [ 0.172308] Key type id_legacy registered [ 0.172323] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.174256] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 0.174389] io scheduler noop registered [ 0.174395] io scheduler deadline registered (default) [ 0.174672] io scheduler cfq registered [ 0.174679] io scheduler mq-deadline registered [ 0.174685] io scheduler kyber registered [ 0.176979] BCM2708FB: allocated DMA memory fad00000 [ 0.177005] BCM2708FB: allocated DMA channel 0 @ bb813000 [ 0.199300] Console: switching to colour frame buffer device 128x48 [ 0.213267] bcm2835-rng 3f104000.rng: hwrng registered [ 0.213392] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB) [ 0.213842] vc-sm: Videocore shared memory driver [ 0.214115] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000 [ 0.223825] brd: module loaded [ 0.232629] loop: module loaded [ 0.232642] Loading iSCSI transport class v2.0-870. [ 0.233316] libphy: Fixed MDIO Bus: probed [ 0.233413] usbco registered new interface driver lan78xx [ 0.233466] usbco registered new interface driver smsc95xx [ 0.233482] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [ 0.261867] dwc_otg 3f980000.usb: base=0xf0980000 [ 0.401500] NOHZ: local_softirq_pending 80 [ 0.421499] NOHZ: local_softirq_pending 80 [ 0.441499] NOHZ: local_softirq_pending 80 [ 0.461499] NOHZ: local_softirq_pending 80 [ 0.462098] Core Release: 2.80a [ 0.462107] Setting default values for core params [ 0.462138] Finished setting default values for core params [ 0.662386] Using Buffer DMA mode [ 0.662392] Periodic Transfer Interrupt Enhancement - disabled [ 0.662397] Multiprocessor Interrupt Enhancement - disabled [ 0.662403] OTG VER PARAM: 0, OTG VER FLAG: 0 [ 0.662415] Dedicated Tx FIFOs mode [ 0.662753] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xbad14000 dma = 0xfad14000 len=9024 [ 0.662777] FIQ FSM acceleration enabled for : Non-periodic Split Transactions Periodic Split Transactions High-Speed Isochronous Endpoints Interrupt/Control Split Transaction hack enabled [ 0.662784] dwc_otg: Microframe scheduler enabled [ 0.662838] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805e9c5c [ 0.662849] WARN::hcd_init_fiq:460: FIQ ASM at 0x805e9fc4 length 36 [ 0.662861] WARN::hcd_init_fiq:486: MPHI regs_base at 0xf0006000 [ 0.662914] dwc_otg 3f980000.usb: DWC OTG Controller [ 0.662946] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1 [ 0.662976] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000 [ 0.663024] Init: Port Power? op_state=1 [ 0.663028] Init: Power Port (0) [ 0.663233] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 0.663244] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.663252] usb usb1: Product: DWC OTG Controller [ 0.663261] usb usb1: Manufacturer: Linux 4.14.71-v7+ dwc_otg_hcd [ 0.663269] usb usb1: SerialNumber: 3f980000.usb [ 0.663880] hub 1-0:1.0: USB hub found [ 0.663920] hub 1-0:1.0: 1 port detected [ 0.664451] dwc_otg: FIQ enabled [ 0.664456] dwc_otg: NAK holdoff enabled [ 0.664461] dwc_otg: FIQ split-transaction FSM enabled [ 0.664471] Module dwc_common_port init [ 0.664721] usbco registered new interface driver usb-storage [ 0.664888] mousedev: PS/2 mouse device common for all mice [ 0.664959] IR NEC protocol handler initialized [ 0.664964] IR RC5(x/sz) protocol handler initialized [ 0.664969] IR RC6 protocol handler initialized [ 0.664974] IR JVC protocol handler initialized [ 0.664980] IR Sony protocol handler initialized [ 0.664985] IR SANYO protocol handler initialized [ 0.664990] IR Sharp protocol handler initialized [ 0.664995] IR MCE Keyboard/mouse protocol handler initialized [ 0.665001] IR XMP protocol handler initialized [ 0.665663] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer [ 0.665914] bcm2835-cpufreq: min=600000 max=1400000 [ 0.666256] sdhci: Secure Digital Host Controller Interface driver [ 0.666260] sdhci: Copyright(c) Pierre Ossman [ 0.666605] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe [ 0.666922] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe [ 0.667010] sdhci-pltfm: SDHCI platform and OF driver helper [ 0.668430] ledtrig-cpu: registered to indicate activity on CPUs [ 0.668574] hidraw: raw HID events driver (C) Jiri Kosina [ 0.668725] usbco registered new interface driver usbhid [ 0.668729] usbhid: USB HID core driver [ 0.669327] vchiq: vchiq_init_state: slot_zero = bad80000, is_master = 0 [ 0.670742] [vc_sm_connected_init]: start [ 0.679657] [vc_sm_connected_init]: end - returning 0 [ 0.680231] Initializing XFRM netlink socket [ 0.680255] NET: Registered protocol family 17 [ 0.680347] Key type dns_resolver registered [ 0.680886] Registering SWP/SWPB emulation handler [ 0.681464] registered taskstats version 1 [ 0.687382] uart-pl011 3f201000.serial: cts_event_workaround enabled [ 0.687452] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2 [ 0.689315] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0 [ 0.689325] mmc-bcm2835 3f300000.mmc: DMA channel allocated [ 0.742127] sdhost: log_buf @ bad13000 (fad13000) [ 0.775739] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 0.777309] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 0.778879] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 0.781705] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 0.821523] mmc0: sdhost-bcm2835 loaded - DMA enabled (1) [ 0.822569] of_cfs_init [ 0.822654] of_cfs_init: OK [ 0.823219] Waiting for root device PARTUUID=d69ebd8b-02... [ 0.858102] random: fast init done [ 0.866937] mmc1: new high speed SDIO card at address 0001 [ 0.881703] Indeed it is in host mode hprt0 = 00021501 [ 0.981725] mmc0: host does not support reading read-only switch, assuming write- enable [ 0.985888] mmc0: new high speed SDXC card at address aaaa [ 0.986369] mmcblk0: mmc0:aaaa SB64G 59.5 GiB [ 0.988774] mmcblk0: p1 p2 [ 1.016559] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [ 1.016568] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [ 1.042515] NOHZ: local_softirq_pending 40 [ 1.048884] NOHZ: local_softirq_pending 40 [ 1.091583] usb 1-1: new high-speed USB device number 2 using dwc_otg [ 1.091702] Indeed it is in host mode hprt0 = 00001101 [ 1.195817] EXT4-fs (mmcblk0p2): recovery complete [ 1.197525] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 1.197583] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [ 1.199088] devtmpfs: mounted [ 1.202086] Freeing unused kernel memory: 1024K [ 1.217421] NOHZ: local_softirq_pending 40 [ 1.219404] NOHZ: local_softirq_pending 40 [ 1.226904] NOHZ: local_softirq_pending 40 [ 1.238784] NOHZ: local_softirq_pending 40 [ 1.331830] usb 1-1: New USB device found, idVendor=0424, idProduct=2514 [ 1.331845] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.332497] hub 1-1:1.0: USB hub found [ 1.332592] hub 1-1:1.0: 4 ports detected [ 1.581099] systemd[1]: System time before build time, advancing clock. [ 1.661546] usb 1-1.1: new high-speed USB device number 3 using dwc_otg [ 1.697346] NET: Registered protocol family 10 [ 1.698404] Segment Routing with IPv6 [ 1.709209] ip_tables: (C) 2000-2006 Netfilter Core Team [ 1.726278] random: systemd: uninitialized urandom read (16 bytes read) [ 1.731363] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [ 1.732009] systemd[1]: Detected architecture arm. [ 1.732919] systemd[1]: Set hostname to raspberrypi. [ 1.772494] random: systemd: uninitialized urandom read (16 bytes read) [ 1.792067] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514 [ 1.792088] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.792873] hub 1-1.1:1.0: USB hub found [ 1.792993] hub 1-1.1:1.0: 3 ports detected [ 1.801223] random: systemd-gpt-aut: uninitialized urandom read (16 bytes read) [ 2.111592] usb 1-1.1.3: new full-speed USB device number 4 using dwc_otg [ 2.189707] systemd[1]: Listening on Journal Socket. [ 2.190130] systemd[1]: Reached target Swap. [ 2.190328] systemd[1]: Listening on fsck to fsckd communication Socket. [ 2.191075] systemd[1]: Created slice User and Session Slice. [ 2.191298] systemd[1]: Listening on udev Kernel Socket. [ 2.191687] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 2.192251] systemd[1]: Created slice System Slice. [ 2.253584] usb 1-1.1.3: New USB device found, idVendor=0557, idProduct=8021 [ 2.253599] usb 1-1.1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.254609] hub 1-1.1.3:1.0: USB hub found [ 2.255188] hub 1-1.1.3:1.0: 4 ports detected [ 2.365320] i2c /dev entries driver [ 2.551627] usb 1-1.1.1: new high-speed USB device number 5 using dwc_otg [ 2.682024] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800 [ 2.682064] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.782071] usb 1-1.1.3.1: new full-speed USB device number 6 using dwc_otg [ 2.904955] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [ 2.947217] usb 1-1.1.3.1: New USB device found, idVendor=04d9, idProduct=1503 [ 2.947235] usb 1-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.947244] usb 1-1.1.3.1: Product: USB Keyboard [ 2.947253] usb 1-1.1.3.1: Manufacturer: [ 2.974014] input: USB Keyboard as /devices/platform/soc/3f980000.usb/ usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.1/1-1.1.3.1:1.0/0003:04D9:1503.0001/input/input0 [ 2.976420] libphy: lan78xx-mdiobus: probed [ 2.996016] systemd-journald[101]: Received request to flush runtime journal from PID 1 [ 3.042828] hid-generic 0003:04D9:1503.0001: input,hidraw0: USB HID v1.10 Keyboard [ USB Keyboard] on usb-3f980000.usb-1.1.3.1/input0 [ 3.064920] input: USB Keyboard as /devices/platform/soc/3f980000.usb/ usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.1/1-1.1.3.1:1.1/0003:04D9:1503.0002/input/input1 [ 3.132092] hid-generic 0003:04D9:1503.0002: input,hidraw1: USB HID v1.10 Device [ USB Keyboard] on usb-3f980000.usb-1.1.3.1/input1 [ 3.145663] input: USB Keyboard as /devices/platform/soc/3f980000.usb/ usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.1/1-1.1.3.1:1.2/0003:04D9:1503.0003/input/input2 [ 3.146135] hid-generic 0003:04D9:1503.0003: input,hidraw2: USB HID v1.10 Mouse [ USB Keyboard] on usb-3f980000.usb-1.1.3.1/input2 [ 3.241583] usb 1-1.1.3.2: new low-speed USB device number 7 using dwc_otg [ 3.377862] usb 1-1.1.3.2: New USB device found, idVendor=045e, idProduct=0040 [ 3.377880] usb 1-1.1.3.2: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [ 3.377889] usb 1-1.1.3.2: Product: Microsoft 3-Button Mouse with IntelliEye(TM) [ 3.377900] usb 1-1.1.3.2: Manufacturer: Microsoft [ 3.382964] input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as / devices/platform/soc/3f980000.usb/ usb1/1-1/1-1.1/1-1.1.3/1-1.1.3.2/1-1.1.3.2:1.0/0003:045E:0040.0004/input/input3 [ 3.383558] hid-generic 0003:045E:0040.0004: input,hidraw3: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-3f980000.usb-1.1.3.2/input0 [ 3.765271] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. [ 3.773683] bcm2835_alsa bcm2835_alsa: card created with 8 channels [ 3.921744] brcmfmac: F1 signature read @0x18000000=0x15264345 [ 3.932211] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455- sdio.bin for chip 0x004345(17221) rev 0x000006 [ 3.932632] usbco registered new interface driver brcmfmac [ 4.185211] random: crng init done [ 4.185226] random: 7 urandom warning(s) missed due to ratelimiting [ 4.253643] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 [ 4.257708] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09 18:56:28 [ 5.015272] uart-pl011 3f201000.serial: no DMA platform data [ 5.849448] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 6.128521] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 6.852451] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS [ 11.630437] Bluetooth: Core ver 2.22 [ 11.630492] NET: Registered protocol family 31 [ 11.630495] Bluetooth: HCI device and connection manager initialized [ 11.630509] Bluetooth: HCI socket layer initialized [ 11.630515] Bluetooth: L2CAP socket layer initialized [ 11.630532] Bluetooth: SCO socket layer initialized [ 11.649853] Bluetooth: HCI UART driver ver 2.3 [ 11.649861] Bluetooth: HCI UART protocol H4 registered [ 11.649866] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 11.649990] Bluetooth: HCI UART protocol Broadcom registered [ 11.895208] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.895217] Bluetooth: BNEP filters: protocol multicast [ 11.895236] Bluetooth: BNEP socket layer initialized [ 11.979407] Bluetooth: RFCOMM TTY layer initialized [ 11.979435] Bluetooth: RFCOMM socket layer initialized [ 11.979450] Bluetooth: RFCOMM ver 1.11 [ 12.621738] fuse init (API version 7.26) pi@raspberrypi:~ $ snip I'd expect the HAT to show up similarly. I did post similar elsewhere but there it is agan in case it's different? Nope, I can't spot anything like yours in mine? ;-( Given the Pi is quite new, the DTV hat brand new, it was a fresh install on a 64GB 10x uSD and I had followed the walkthrough to the letter, I thought it was either faulty hardware (not impossible with a new product) or something was 'different' between the lasted version of Rasbian and whatever version they used / tested and wrote the walkthrough around. I recently had an issue (high CPU on a Dell laptop) which was down to a bug in the new kernel I just happened to get in the (latest) version I installed. ;-( Cheers, T i m |
|
#17
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 09:49:05 +0100, Andy Burns wrote:
T i m wrote: I installed lshw and ran that but that doesn't show it I doubt it would show, but lsdvb ought to (you might need to install dvb-apps or whatever package debian/raspbian calls it). I think that's installed Andy: "Applications and utilities geared towards the initial setup, testing and operation of an DVB device supporting the DVB-S, DVB-C, DVB-T, and ATSC standards. Main User Applications: . scan - Scan for channels on your digital TV device . dvbscan - Another frequency scanning tool . czap, szap, tzap - Tuning utilities for DVB-C, DVB-S, DVB-T . azap - Tuning utility for ATSC . gnutv - Tune, watch and stream your TV General Utilities: . dvbdate - Set your clock from digital TV . dvbnet - Control digital data network interfaces . dvbtraffic - Monitor traffic on a digital device . femon - Monitor the tuning on a digital TV device . zap - Just tunes a digital device . atsc_epg - Display ATSC Electronic Program Guide (next programs) . alevt - Teletext browser Hardware Specific Utilities: . util/av7110loadkeys - Load remote keys into an av7110 based card . util/dib3000-watch - Monitor DIB3000 demodulators . util/ dst-utils - Utilities for DST based cards . util/ttusbdec_reset - Reset a TechnoTrends TTUSB DEC device Libraries: . lib/libdvbapi - Interface library to digital TV devices . lib/libdvbcfg - Library to parse/create digital TV channel . lib/libdvbsec - Library for Satellite Equipment Control operations . lib/libucsi - Fast MPEG2 Transport Stream SI table parsing library . lib/libdvben50221- Implementation of a Cenelec EN 50221 CAM stack . lib/libdvbmisc - Miscellaneous utilities used by the other libraries" I know you said you updated the O/S, are you sure that went ok? Well, initially I used a fairly recent Rasbian install which I updated (as per the walkthrough) prior to installing tvheadend but also prior to getting the Hat. So I managed to purge tvheadend and re-install / configure but still it wouldn't see the tuner. Then I started wth a fresh Rasbian download, image, boot and FS resize and it applies the update at that time. I also ran the update from the CLI, as per the walkthrough and it said there was little to do (probably updates to the updates etc). This was just now: pi@raspberrypi:~ $ sudo apt-get update Hit:1 http://archive.raspberrypi.org/debian stretch InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease Reading package lists... Done pi@raspberrypi:~ $ pi@raspberrypi:~ $ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. pi@raspberrypi:~ $ I presume only the very latest will include the tuner driver. Well, you couldn't have got much fresher ... unless they have dropped support for it again. ;-( Cheers, T i m |
|
#18
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
T i m wrote:
I think that's installed Andy: but no lsdvb available? Well, you couldn't have got much fresher your earlier log showed kernel version 4.14.71 which seems right, but no mention of the TV hat in the release notes, and no mention of CXDnnnn tuner or other V4L drivers in your log. I tried to install a new raspbian, so I cold see what modules might exist, but on this laptop that now involves a stack of adapters from USB3typeC-USB2-SDcard-TFcard and Etcher wasn't very impressed. |
|
#19
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On 22/10/2018 12:52, T i m wrote:
On Mon, 22 Oct 2018 11:48:55 +0100, John Rumm So nano filename or sudo nano filename But you first have to navigate to the relevant folders or include the path in the cli? Yup... its fairly standard stuff, but its there on any version - even if running without the GUI. (I quite often use Pis in applications where there is no need for the GUI) I would 'like' to be able to right click on a folder and open it as sudo (and therefore do what I like in there, as I have / can with Ubuntu / Mint) or run the Text editor from the menu as sudo and just do what I want when I've navigated to the file via the GUI. Much like dropping to root in the CLI... I appreciate it's only a RPi (that's actually as fast as this old XP Mac Mini g) but it is 2018 after all! ;-) Something else you may want to consider for this application are the range of HDHomerun network aware tuners from silicon dust. They are probably no more expensive than the pi + HAT, but "just work" out of the box and can talk to most software platforms... They have 2 and 4 tuner versions for DVBT/T2 and DVBS https://www.silicondust.com/ (ideally you still DIY your own recording setup in Kodi or plex or similar) -- Cheers, John. /================================================== ===============\ | Internode Ltd - http://www.internode.co.uk | |-----------------------------------------------------------------| | John Rumm - john(at)internode(dot)co(dot)uk | \================================================= ================/ |
|
#20
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 14:10:16 +0100, Andy Burns wrote:
T i m wrote: I think that's installed Andy: but no lsdvb available? Sorry, forgot to answer .. pi@raspberrypi:~ $ lsdvb lsdvb: Simple utility to list PCI/PCIe DVB devices Version: 0.0.4 Copyright (C) Manu Abraham ERROR: Opening /sys/class/dvb directory Well, you couldn't have got much fresher your earlier log showed kernel version 4.14.71 which seems right, but no mention of the TV hat in the release notes, and no mention of CXDnnnn tuner or other V4L drivers in your log. Oh? (and thanks for looking). ;-( I tried to install a new raspbian, so I cold see what modules might exist, but on this laptop that now involves a stack of adapters from USB3typeC-USB2-SDcard-TFcard and Etcher wasn't very impressed. Hehe (and thanks again). I'm happy to try anything that might get me closer to a working machine (or reason why it isn't) so please keep asking. ;-) Cheers, T i m |
|
#21
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 14:40:19 +0100, John Rumm wrote:
snip I would 'like' to be able to right click on a folder and open it as sudo (and therefore do what I like in there, as I have / can with Ubuntu / Mint) or run the Text editor from the menu as sudo and just do what I want when I've navigated to the file via the GUI. Much like dropping to root in the CLI... Yes, but without going to the CLI (and back to Dikens times). ;-) I appreciate it's only a RPi (that's actually as fast as this old XP Mac Mini g) but it is 2018 after all! ;-) Something else you may want to consider for this application are the range of HDHomerun network aware tuners from silicon dust. They are probably no more expensive than the pi + HAT, but "just work" out of the box and can talk to most software platforms... They have 2 and 4 tuner versions for DVBT/T2 and DVBS https://www.silicondust.com/ checks them out Neat. Yes, that could be a better (cheaper / less complicated) soultion, subject to prices over here. (ideally you still DIY your own recording setup in Kodi or plex or similar) That was going to be my next question, the DVR bit as I'm not keen on renting any space in their cloud etc. Cheers, T i m |
|
#22
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On 22/10/2018 14:54, T i m wrote:
On Mon, 22 Oct 2018 14:40:19 +0100, John Rumm wrote: snip I would 'like' to be able to right click on a folder and open it as sudo (and therefore do what I like in there, as I have / can with Ubuntu / Mint) or run the Text editor from the menu as sudo and just do what I want when I've navigated to the file via the GUI. Much like dropping to root in the CLI... Yes, but without going to the CLI (and back to Dikens times). ;-) Indeed, but there is something to be said for Dickens when you are ssh'ed into it on a slow broadband connection ;-) I appreciate it's only a RPi (that's actually as fast as this old XP Mac Mini g) but it is 2018 after all! ;-) Something else you may want to consider for this application are the range of HDHomerun network aware tuners from silicon dust. They are probably no more expensive than the pi + HAT, but "just work" out of the box and can talk to most software platforms... They have 2 and 4 tuner versions for DVBT/T2 and DVBS https://www.silicondust.com/ checks them out Neat. Yes, that could be a better (cheaper / less complicated) soultion, subject to prices over here. Looks like they have gone up a bit since I got mine - Amazon have the 2 tuner one at £99 now (ISTR I paid about £70 for mine) (ideally you still DIY your own recording setup in Kodi or plex or similar) That was going to be my next question, the DVR bit as I'm not keen on renting any space in their cloud etc. There are number of ways of doing it - they supply software that will do the basics and record onto anything the machine running the software can write to. I went for a plex server running on my NAS. It stores to a network visible share, so recordings can be played back on anything that can see the share and interpret it as a file system. It can also be used by plex client on anything running that, and lastly can also be seen by anything with DLNA compatible playback, since my NAS also shares anything in the folder that way as well. (this gets round the usual problems created by TVs that can record to a attached USB drive - i.e. only that TV can playback the recording since its DRM locked to the platform that made it, and also it not available on the network) Recordings can then be scheduled from any reasonably recent plex client, or from any web browser talking to the plex server. (the client has not part in the recording process other than creating the request for it to happen - the server then talks to the streaming tuner and does the rest itself) I think for live TV and DVD capabilities you need the paid for version. They do a variety of monthly "plex pass" rental models, but I just went for the perpetual one off license. It downloads a full EPG appropriate for your TV region. You can make recordings based on channel and program, but it also presents a aggregated view of everything bundles together by category (e.g. shows, films[1], news etc), and "starting soon" etc. So if you want to record a program and you know the name, you just search the EPG for it, and say record (either this program or the whole series), and it will then create schedules for all the recordings over multiple channels if you want. It manages the tuners as required (and will highlight if scheduling conflicts mean you don't have enough tuners). There are some "advanced" options on the record selection to specify if you want all showings or just new transmissions, whether to limit to particular channels, if you add some padding time to the end of recordings, and also whether to automatically edit out the adverts (its a "beta" feature that works ok in some cases but not all). All in all it seems ok. It has the occasional quirk. [1] Being able to see and alphabetised list of say all the films being shown in a week on all the channels is quite nice - just browse and tell it to record what you want. -- Cheers, John. /================================================== ===============\ | Internode Ltd - http://www.internode.co.uk | |-----------------------------------------------------------------| | John Rumm - john(at)internode(dot)co(dot)uk | \================================================= ================/ |
|
#23
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
"John Rumm" wrote in message
... Recordings can then be scheduled from any reasonably recent plex client, or from any web browser talking to the plex server. (the client has not part in the recording process other than creating the request for it to happen - the server then talks to the streaming tuner and does the rest itself) Plex is good but it could be a whole lot better. Unfortunately it relies on transcoding on the fly at the server, rather than each client transcoding, if that's what it needs, at the point of display. Even with a fairly fast PC as the server, I find that streaming an HD recording (1920x1080, H264-encoded TS, as recorded off-air by NextPVR or TVHeadend) to a Plex client in a Roku box imposes a severe CPU load on the PC. Playing the same file in VLC on that server PC imposes much less load - hardly noticeable on the Windows Performance graph. Streaming two such files - or even two SD recordings (720x576, MPEG TS) is a dead loss, with stuttering and continuous CPU fan. A better solution would probably be to use a Raspberry Pi as a client, sucking the file that has been shared by Samba from the server. VLC will display an HD recording without stuttering. I imagine it will do an SD recording as well, if I bought an MPEG licence so it didn't have to do everything in software. In other words, have the client capable of playing any reasonable format, rather than requiring it to be massaged by the server into a single format that the client can play. |
|
#24
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 15:31:31 +0100, John Rumm
wrote: On 22/10/2018 14:54, T i m wrote: On Mon, 22 Oct 2018 14:40:19 +0100, John Rumm wrote: snip I would 'like' to be able to right click on a folder and open it as sudo (and therefore do what I like in there, as I have / can with Ubuntu / Mint) or run the Text editor from the menu as sudo and just do what I want when I've navigated to the file via the GUI. Much like dropping to root in the CLI... Yes, but without going to the CLI (and back to Dikens times). ;-) Indeed, but there is something to be said for Dickens when you are ssh'ed into it on a slow broadband connection ;-) Noted. ;-) I appreciate it's only a RPi (that's actually as fast as this old XP Mac Mini g) but it is 2018 after all! ;-) Something else you may want to consider for this application are the range of HDHomerun network aware tuners from silicon dust. They are probably no more expensive than the pi + HAT, but "just work" out of the box and can talk to most software platforms... They have 2 and 4 tuner versions for DVBT/T2 and DVBS https://www.silicondust.com/ checks them out Neat. Yes, that could be a better (cheaper / less complicated) soultion, subject to prices over here. Looks like they have gone up a bit since I got mine - Amazon have the 2 tuner one at £99 now (ISTR I paid about £70 for mine) Ok, thanks. So that is a bit more than say a RPi3B+DTV Hat + uSD, but only a bit (30 + 20 + 10). (ideally you still DIY your own recording setup in Kodi or plex or similar) That was going to be my next question, the DVR bit as I'm not keen on renting any space in their cloud etc. There are number of ways of doing it - they supply software that will do the basics and record onto anything the machine running the software can write to. Ok. I went for a plex server running on my NAS. Could that be a Synology? It stores to a network visible share, so recordings can be played back on anything that can see the share and interpret it as a file system. It can also be used by plex client on anything running that, and lastly can also be seen by anything with DLNA compatible playback, since my NAS also shares anything in the folder that way as well. I think that answers my previous question John. ;-) (this gets round the usual problems created by TVs that can record to a attached USB drive - i.e. only that TV can playback the recording since its DRM locked to the platform that made it, and also it not available on the network) Ah, I wasn't aware of that limitation (so thanks for the heads up). If I record something on my Toppy and transfer it to and with my WHS (remotely), anything on the LAN that can see the file can play it (I think I rename .rec to .avi or somesuch). Recordings can then be scheduled from any reasonably recent plex client, or from any web browser talking to the plex server. (the client has not part in the recording process other than creating the request for it to happen - the server then talks to the streaming tuner and does the rest itself) I think I follow that. I've not really ever got involved in any media serving as there wasn't really a need (Mrs and daughter do their own thing media wise). I think for live TV and DVD capabilities you need the paid for version. They do a variety of monthly "plex pass" rental models, but I just went for the perpetual one off license. Ok. I don't mind paying a reasonable amount once for something I use a lot. It downloads a full EPG appropriate for your TV region. You can make recordings based on channel and program, but it also presents a aggregated view of everything bundles together by category (e.g. shows, films[1], news etc), and "starting soon" etc. Sounds a bit like our NowTV boxes? So if you want to record a program and you know the name, you just search the EPG for it, and say record (either this program or the whole series), and it will then create schedules for all the recordings over multiple channels if you want. The best I do on the Toppy is 'Series search' but that seems to work ok. It manages the tuners as required (and will highlight if scheduling conflicts mean you don't have enough tuners). Ok. There are some "advanced" options on the record selection to specify if you want all showings or just new transmissions, whether to limit to particular channels, if you add some padding time to the end of recordings, and also whether to automatically edit out the adverts (its a "beta" feature that works ok in some cases but not all). Ok. All in all it seems ok. It has the occasional quirk. Doesn't most IT kit? [1] Being able to see and alphabetised list of say all the films being shown in a week on all the channels is quite nice - just browse and tell it to record what you want. Yeah, that does sound cool. ;-) So it's that sort of solution or sticking a couple of DTV cards and a big drive in a PC? Cheers, T i m |
|
#25
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On 22/10/2018 16:29, NY wrote:
"John Rumm" wrote in message ... Recordings can then be scheduled from any reasonably recent plex client, or from any web browser talking to the plex server. (the client has not part in the recording process other than creating the request for it to happen - the server then talks to the streaming tuner and does the rest itself) Plex is good but it could be a whole lot better. Unfortunately it relies on transcoding on the fly at the server, rather than each client transcoding, I run the sever on my NAS which has a Celeron N3150/N3160 1.6 GHz quad-core processor (so reasonably powerful for a NAS, but not a patch on an average PC). Can't say I have ever noticed a particularly high CPU load on that. I just tried streaming a HD recording to a web browser, and it did transcode, but did not seem to use any significant additional CPU on the NAS (I got a burst of 30% load for a second or so at the start of playback, then it settled down to in to the 2% to 5% range). Streaming another copy to my phone (that was shown in the status as "direct play", did not add to the load. What have you got your server transcoder options set to? (I have my quality setting at "Prefer higher quality recordings", and the number of simultaneous encodes set to unlimited). if that's what it needs, at the point of display. Even with a fairly fast PC as the server, I find that streaming an HD recording (1920x1080, H264-encoded TS, as recorded off-air by NextPVR or TVHeadend) to a Plex client in a Roku box imposes a severe CPU load on the PC. Playing the same file in VLC on that server PC imposes much less load - hardly noticeable on the Windows Performance graph. Streaming two such files - or even two SD recordings (720x576, MPEG TS) is a dead loss, with stuttering and continuous CPU fan. I wonder why you are seeing a much higher load...? A better solution would probably be to use a Raspberry Pi as a client, sucking the file that has been shared by Samba from the server. VLC will display an HD recording without stuttering. I imagine it will do an SD recording as well, if I bought an MPEG licence so it didn't have to do everything in software. In other words, have the client capable of playing any reasonable format, rather than requiring it to be massaged by the server into a single format that the client can play. You don't have to use plex client for playback if you have another way of getting at the file, either at the file system level or via DLNA. So for a PC, then use VLC (and if watching recorded stuff on a PC I usually do since the ability to skip forward is quicker and more flexible). On my TV I normally use the plex client, but I could equally use the TVs native video playback application, and play from DLNA. I think my DVD player can also play from a SMB/CIFS share as well. -- Cheers, John. /================================================== ===============\ | Internode Ltd - http://www.internode.co.uk | |-----------------------------------------------------------------| | John Rumm - john(at)internode(dot)co(dot)uk | \================================================= ================/ |
|
#26
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On 22/10/2018 17:16, T i m wrote:
On Mon, 22 Oct 2018 15:31:31 +0100, John Rumm wrote: On 22/10/2018 14:54, T i m wrote: On Mon, 22 Oct 2018 14:40:19 +0100, John Rumm wrote: snip I would 'like' to be able to right click on a folder and open it as sudo (and therefore do what I like in there, as I have / can with Ubuntu / Mint) or run the Text editor from the menu as sudo and just do what I want when I've navigated to the file via the GUI. Much like dropping to root in the CLI... Yes, but without going to the CLI (and back to Dikens times). ;-) Indeed, but there is something to be said for Dickens when you are ssh'ed into it on a slow broadband connection ;-) Noted. ;-) I appreciate it's only a RPi (that's actually as fast as this old XP Mac Mini g) but it is 2018 after all! ;-) Something else you may want to consider for this application are the range of HDHomerun network aware tuners from silicon dust. They are probably no more expensive than the pi + HAT, but "just work" out of the box and can talk to most software platforms... They have 2 and 4 tuner versions for DVBT/T2 and DVBS https://www.silicondust.com/ checks them out Neat. Yes, that could be a better (cheaper / less complicated) soultion, subject to prices over here. Looks like they have gone up a bit since I got mine - Amazon have the 2 tuner one at £99 now (ISTR I paid about £70 for mine) Ok, thanks. So that is a bit more than say a RPi3B+DTV Hat + uSD, but only a bit (30 + 20 + 10). If you add in a case and a PSU, then you are probably on par. (ideally you still DIY your own recording setup in Kodi or plex or similar) That was going to be my next question, the DVR bit as I'm not keen on renting any space in their cloud etc. There are number of ways of doing it - they supply software that will do the basics and record onto anything the machine running the software can write to. Ok. I went for a plex server running on my NAS. Could that be a Synology? Mine is a QNAP TS-453A, but there is a synology version of the server. It stores to a network visible share, so recordings can be played back on anything that can see the share and interpret it as a file system. It can also be used by plex client on anything running that, and lastly can also be seen by anything with DLNA compatible playback, since my NAS also shares anything in the folder that way as well. I think that answers my previous question John. ;-) (this gets round the usual problems created by TVs that can record to a attached USB drive - i.e. only that TV can playback the recording since its DRM locked to the platform that made it, and also it not available on the network) Ah, I wasn't aware of that limitation (so thanks for the heads up). If I record something on my Toppy and transfer it to and with my WHS (remotely), anything on the LAN that can see the file can play it (I think I rename .rec to .avi or somesuch). Yup, I used to use toppy for recordings, and had a modified Linksys NSL2 (aka "slug") hooked up to it via USB that then made the toppy file system available via FTP to the network. So you could start a copy going, and shortly after start playback in VLC while the copy carried on in the background (transfer speed was only about twice real time). Hence when going "modern" with HD and all that, I wanted a similar level of functionality. I had not found any of the native capabilities of the TVs etc to be up to much. Recordings can then be scheduled from any reasonably recent plex client, or from any web browser talking to the plex server. (the client has not part in the recording process other than creating the request for it to happen - the server then talks to the streaming tuner and does the rest itself) sorry typo - "the client has *no* part in the recording..." I think I follow that. I've not really ever got involved in any media serving as there wasn't really a need (Mrs and daughter do their own thing media wise). I think for live TV and DVD capabilities you need the paid for version. They do a variety of monthly "plex pass" rental models, but I just went for the perpetual one off license. Ok. I don't mind paying a reasonable amount once for something I use a lot. IIRC it was £4/month, or £32/year, or £95/"lifetime" (although how the work out you have croaked and left it to the kids is not explained ;-) It downloads a full EPG appropriate for your TV region. You can make recordings based on channel and program, but it also presents a aggregated view of everything bundles together by category (e.g. shows, films[1], news etc), and "starting soon" etc. Sounds a bit like our NowTV boxes? Could be - not seen on to be able to compare. So if you want to record a program and you know the name, you just search the EPG for it, and say record (either this program or the whole series), and it will then create schedules for all the recordings over multiple channels if you want. The best I do on the Toppy is 'Series search' but that seems to work ok. Yup same kind of idea, with a bit more flexibility... It manages the tuners as required (and will highlight if scheduling conflicts mean you don't have enough tuners). Ok. There are some "advanced" options on the record selection to specify if you want all showings or just new transmissions, whether to limit to particular channels, if you add some padding time to the end of recordings, and also whether to automatically edit out the adverts (its a "beta" feature that works ok in some cases but not all). Ok. All in all it seems ok. It has the occasional quirk. Doesn't most IT kit? Indeed. I had a couple of versions where music playback on the TV client was slightly broken (it played ok, but did not keep track of the elapsed track time correctly - so did not know when to cue up the next track). The current combo seems to be working, so I am leaving it mostly alone! I also get a problem sometimes where it seems to lose a schedule for recording if I make it on the TV, but it remembers it fine if done from the web browser (and that includes if I use the TV's web browser). [1] Being able to see and alphabetised list of say all the films being shown in a week on all the channels is quite nice - just browse and tell it to record what you want. Yeah, that does sound cool. ;-) So it's that sort of solution or sticking a couple of DTV cards and a big drive in a PC? Yup, that would work as well. There are a number of ways of going about it. I decided I liked the idea of having a network accessible tuner that everything could see (obviously the PC in the DTV card situation could act as one, as would your PI setup). -- Cheers, John. /================================================== ===============\ | Internode Ltd - http://www.internode.co.uk | |-----------------------------------------------------------------| | John Rumm - john(at)internode(dot)co(dot)uk | \================================================= ================/ |
|
#27
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Sun, 21 Oct 2018 22:35:59 +0100, T i m wrote:
I've just got a DTV 'Hat' for my Raspberry Pi 3B+, downloaded, installed and updated Rasbian and installed the tvheadend software. However, during the setup Wizard it's supposed to show the 'Sony' DVT module but doesn't? ;-( Wondering if it could be an issue with my Pi3B+, I dug out a 3B and transferred everything over to it and booted it, but then I noticed the yellow lightening flash in the top right hand corner that I understand indicates it's beng underpowered? I swapped out the 2.1A PSU for a 2.4 one, and tried different cables (I normally used a dedicated power cable with an on off switch) but no improvement. I then transferred the lot back to the B+ but the flash was still there? So I've just re-imaged the card and re-installed everything and It's not appeared since? I'm guessing this could be an incompatibility between the OS configuration between the B and the B+? Still no sign of the TV module and The Pi Hut have referred my no-working report to the Forums! Maybe they thought I was asking for technical support rather than reporting what could be a DOA? That said, if it looks like there is no support for the DTV Hat in any of the Raspian notes then ... ? Cheers, T i m |
|
#28
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Sun, 21 Oct 2018 22:35:59 +0100, T i m wrote:
Hi all, I've just got a DTV 'Hat' for my Raspberry Pi 3B+, downloaded, installed and updated Rasbian and installed the tvheadend software. However, during the setup Wizard it's supposed to show the 'Sony' DVT module but doesn't? ;-( Update: I posted a question on the RPi forum and Dougie kindly came back with: "Install tvheadend and kodi, kodi-bin & kodi-pvr-hts Add dtoverlay=rpi-tv gpu_mem=128 into /boot/config.txt and reboot." I did that on the Pi3B and the tuner was seen in tvheadend straight away (well, it did after I remembered to transfer the Tuner hat over to the 3B doh). Then I did a fresh install of Raspbian on the 3B+, installed tvheadend and just added the code into the file (eg I didn't install the kodi stuff) and again, it worked first time. ;-) So, anyone able explain what that code did and why it wouldn't have been in the walk through? Is it possible that others wouldn't need it? On a more practical level, it does seem to work streaming TV over our LAN but it doesn't seem to be able to do so smoothly. If you start a show running and then pause it for a while (using the tvheadend built in player) and then release it, it then seems to run smoothly for a while before hesitating again (suggesting a bandwidth issue somewhere)? FWIW, on the Pi it suggests it's running at about 30% CPU when streaming to a remote PC and my Mac Mini / XP here is showing about the same when playing same (network activity is quite light). I can easily stream video off my RPi NAS next to the PiTV fwiw. I'll do some more experiments ... Thanks to all who offered help etc. Cheers, T i m |
|
#29
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Mon, 22 Oct 2018 20:14:51 +0100, John Rumm
wrote: snip good stuff So it's that sort of solution or sticking a couple of DTV cards and a big drive in a PC? Yup, that would work as well. There are a number of ways of going about it. I decided I liked the idea of having a network accessible tuner that everything could see (obviously the PC in the DTV card situation could act as one, as would your PI setup). As mentioned elsewhere in this thread, it's now working but I still need to: Check out the hesitation issue when streaming a TV program. Find out how well things like the recording work. Work out to good the EPG is. Check what other software I might need to make it more refined. Check out alternative solutions to replace the Toppys, as / when they become US. Cheers, T i m |
|
#30
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
T i m wrote:
dtoverlay=rpi-tv gpu_mem=128 into /boot/config.txt and reboot." anyone able explain what that code did A SoC doesn't generally provide plug-n-play functionality, so the kernel is can't detect peripherals instead it's build with a text file to describe what peripherals a given board should have, the config.txt is a way to add stuff at runtime that wasn't included at compile time. https://www.raspberrypi.org/documentation/configuration/device-tree.md and why it wouldn't have been in the walk through? Presumably the developer forgot he'd had to do it! |
|
#31
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
T i m wrote:
I still need to Work out to good the EPG is. If you enable advanced view in tvheadend, there are different grabbers available under Configuration/Channels/EPP Grabber modules, I use "over-the-air UK freeview" (and "over-the-air UK freesat", but not relevant for the Pi) rather than the default "over-the-air EIT DVB grabber" |
|
#32
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Wed, 24 Oct 2018 13:01:12 +0100, Andy Burns
wrote: T i m wrote: I still need to Work out to good the EPG is. If you enable advanced view in tvheadend, there are different grabbers available under Configuration/Channels/EPP Grabber modules, I use "over-the-air UK freeview" (and "over-the-air UK freesat", but not relevant for the Pi) rather than the default "over-the-air EIT DVB grabber" Thanks for that Andy, I'll give it a go in a while. For the remote viewing (LAN) of this sort of thing, are there more efficient (but equally easy) ways than the using the tvheadend viewer do you know please? Cheers, T i m |
|
#33
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
T i m wrote:
For the remote viewing (LAN) of this sort of thing, are there more efficient (but equally easy) ways than the using the tvheadend viewer do you know please? VLC, two methods both launch a .m3u playlist from the tvheadend web interface 1) stream an entire mux, from config/inputs/muxes use the play icon, you can then switch channels within that mux using playback-programme within VLC, you might saturate your wifi by sending the whole 24-32Mbps transport stream. 2) stream a single channel from EPG, then the (i) icon, then the play icon, which just sends a 2-3Mbps programme stream. or you can use kodi on another PC or Pi as a front-end to tvheadend on the Pi |
|
#34
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Wed, 24 Oct 2018 12:55:53 +0100, Andy Burns
wrote: T i m wrote: dtoverlay=rpi-tv gpu_mem=128 into /boot/config.txt and reboot." anyone able explain what that code did A SoC doesn't generally provide plug-n-play functionality, so the kernel is can't detect peripherals instead it's build with a text file to describe what peripherals a given board should have, the config.txt is a way to add stuff at runtime that wasn't included at compile time. https://www.raspberrypi.org/documentation/configuration/device-tree.md Sounds a bit like config.sys on DOS from the 80's. ;-) and why it wouldn't have been in the walk through? Presumably the developer forgot he'd had to do it! I don't (specifically) attempt lots of solutions that involve Linux (even though they could be a perfectly good a cheap solution) because of how easily something unforeseen can catch out someone like me (and many here in this case etc). I mention Linux because with Windows the bigger userbase means that most things are fixed before ordinary people get to them (even though they might be less easy for a person *to* fix). So when I skimmed the walkthrough for this TV card I thought it looked very straightforward (like only 3-4 CLI steps) but how wrong was I. And without someo9ne else coming up with what appears to be the solution, I'd never have sorted it myself, not only because I'm not a coder but because of how much time I can afford / justify to playing with this sort of thing. But on the other hand I know how limited (and often un repairable) std commercial appliances are and how it remind me just how 'neat' a solution the Toppy is for my skills / needs. eg, It was functional enough OOTB but with tried and tested taps, could be made even better. ;-) Every time I limp though some slow / clumsy EPG I'm reminded again of how good the Toppy is. Cheers, T i m |
|
#35
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Wed, 24 Oct 2018 13:41:53 +0100, Andy Burns
wrote: T i m wrote: For the remote viewing (LAN) of this sort of thing, are there more efficient (but equally easy) ways than the using the tvheadend viewer do you know please? VLC, two methods both launch a .m3u playlist from the tvheadend web interface 1) stream an entire mux, from config/inputs/muxes use the play icon, you can then switch channels within that mux using playback-programme within VLC, you might saturate your wifi by sending the whole 24-32Mbps transport stream. 2) stream a single channel from EPG, then the (i) icon, then the play icon, which just sends a 2-3Mbps programme stream. or you can use kodi on another PC or Pi as a front-end to tvheadend on the Pi Thanks again Andy, I'll give that all a look this evening. I guess part of this is learning what you need and how it all could / should plug together. FWIW, I'm doing it all wired and should all be Gb (apart from the RPi). Cheers, T i m |
|
#36
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
T i m wrote:
I guess part of this is learning what you need and how it all could / should plug together. Yes, for years I used mythTV, initially with tuners in the PC in the lounge, that was a bit noisy, so then I split it into tuners in a backend hidden away upstairs, with a silent frontend downstairs myth development is not the fastest and it started to feel quite old-hat, so I swapped to tvheadend (and other stuff) on the server upstairs with a combination of kodi boxes (on Pi and Udoo x86) or VLC on laptops, it's much more of a "just works" setup ... though keeping netflix working in kodi on linux can be 'interesting' |
|
#37
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Wed, 24 Oct 2018 15:24:10 +0100, Andy Burns
wrote: T i m wrote: I guess part of this is learning what you need and how it all could / should plug together. Yes, for years I used mythTV, Whenever I've tried such things they often feel very clunky to me, in a user / swish sorta way. Like the Apple UI that is supposed to make things easier for most people but feels more complicated / backward to me. initially with tuners in the PC in the lounge, that was a bit noisy, My WHS is in the lounge (behind the TV) and is virtually silent, to the point where I can't hear if it's on, even with nothing else going on. ;-) so then I split it into tuners in a backend hidden away upstairs, with a silent frontend downstairs I like that idea ... as long as there are no downsides (like network bandwidth etc). myth development is not the fastest and it started to feel quite old-hat, so I swapped to tvheadend (and other stuff) on the server upstairs with a combination of kodi boxes (on Pi and Udoo x86) or VLC on laptops, it's much more of a "just works" setup ... My sort of solution. ;-) though keeping netflix working in kodi on linux can be 'interesting' I bet it can. ;-( So do you know the Toppys Andy? What split (front / backend) solution would give the two of us the sort of features we both enjoy with our Topfields and be equally 'Mrs friendly'? Ironically she watches 'her' TV via a video capture card in her PC fed from a Topfield (using headphones if I'm in) and I watch the main TV via my Topfield and that seems to work pretty well. I think we can record 2 (3?) channels simultaneously whilst watching / playing another? So would that would mean a potential of a streaming tuner that could allow use of 6/8 channels simultaneously? Two quad tuner cards in a PC? Cheers, T i m |
|
#38
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
"T i m" wrote in message
... On Wed, 24 Oct 2018 15:24:10 +0100, Andy Burns wrote: T i m wrote: I guess part of this is learning what you need and how it all could / should plug together. Yes, for years I used mythTV, Whenever I've tried such things they often feel very clunky to me, in a user / swish sorta way. Like the Apple UI that is supposed to make things easier for most people but feels more complicated / backward to me. I tried MythTV before I settled on TVHeadend. I found Myth's UI to be very amateurish and really over-complicated. There were forms where fields were too small to contain values, with no way of scrolling which parts of the field were visible. The concept of creating multiple virtual tuners per physical tuner, to allow simultaneous recordings from the same mux, seems OTT. NextPVR (on Windows) and TVHeadend (on Ubuntu and Raspian) doesn't have that extra layer of complexity. But Myth does have a decent EPG, as a grid with time horizontally and channel vertically. TVH has a list of events, sorted first by time and then by channel, but that's alphabetically by channel name, not by LCN - logical channel number :-( That EPG takes a little bit of getting used to, having to find programmes by channel and/or programme title, but i've got used to it now. The only thing you can't see is when programmes on different channels (and maybe different multiplexes) overlap. I could set Kodi as the front end for TVH, but that has one of those horrible Tellytubby "ten-foot interfaces" which is designed for people to see from across the room rather than sat right in front of their PC. i do all my scheduling from my PC, even if I sometimes use Plex to view programmes on the big TV via a Roku box; mostly I watch programmes on my PC because then I can use VLC which can play at 1.3, 1.5 or even 2x normal speed. TVH seems to be behaving itself fairly well, though occasionally I've found that an auto-rec (record whole series, including future episodes that are not yet in the EPG) fails to match future episodes, even though it did to begin with. I set up Public Eye and The Gentle Touch as autorecs and for a while they worked found, and even found episodes that were not in the EPG to begin with, but then both stopped, and deleting/re-adding the autorec hasn't helped, so I have to set all those individually by hand every few days as more episodes appear in the EPG. Incidentally, if anyone can work out the ending of last night's Public Eye (Slip Home in the Dark, about a woman who was receiving blackmailing phone calls) then you're better than me. I think the caller was someone the husband had been in jail with, but why was the wife so ready to pay up and why did she give the impression that she knew what the guilty secret was that the blackmailer threatened to reveal. OK, she'd lost a baby, which is a traumatic and harrowing experience, but not one that anyone could blackmail you about, surely. |
|
#39
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
On Wed, 24 Oct 2018 13:01:12 +0100, Andy Burns
wrote: T i m wrote: I still need to Work out to good the EPG is. If you enable advanced view in tvheadend, there are different grabbers available under Configuration/Channels/EPP Grabber modules, I use "over-the-air UK freeview" (and "over-the-air UK freesat", but not relevant for the Pi) rather than the default "over-the-air EIT DVB grabber" I had a quick look at this just now and I can't seem to see the options you reference Andy (even in Advanced View)? I see ConfigurationChannels or ConfigurationEPG Grabber but neither give me any such options? What have I missed? ;-( Cheers, T i m |
|
#40
Posted to uk.d-i-y
|
|||
|
|||
|
DTV server, RRi DTV 'Hat' not seen?
T i m wrote:
What have I missed? ;-( maybe it's expert view, rather than advanced |
| Reply |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Forum | |||
| OT - I'm sure Lew has seen this - he's seen everything... | Woodworking | |||
| You seen one bag of mortar, seen'em all?? | Home Repair | |||
| Tardis News Web Server inside Server Defies Laws of Nature | UK diy | |||
| Tardis News Web Server inside Server Defies Laws of Nature | Electronics Repair | |||
| Tardis News Web Server inside Server Defies Laws of Nature | Home Repair | |||
Linear Mode
