Настроика Lirc 0.9.0 в минт 17.2 mate 64х (Проблеммы с запуском Lirc 0.9.0 в mint 17.2 mate)

Выбор и настройка HardWare

Модератор: Модераторы разделов

Ответить
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

Здравствуйте.
Наверняка моя тема многим покажется не актуальной и заезженной как старая пластинка, но для меня она действительно актуальна!
Теперь по делу: Я собрал себе для управления через пульт ДУ от телевизора ИК- приемник/передатчик для СОМ- порта по приведенной здесь схеме:http://meandr.org/archives/2076 правда там вроде не совсем к тем контактам СОМ-порта подведены сигналы Rx и Tx поэтому я развел их как положено согласно распиновки RS232 интерфейса на 2 и 3 контакт соответственно.
Так, как в современных компьютерах нет Сом- портов, я собрал себе 2 переходника Com-Usb один на FT232RL и один на FT232BL все эти переходники заработали и определились в линуксе как ttyUSB0 и ttyUSB1 порты. Все оба переходника и сам ик-приемник/передатчик были проверены в windows при помощи программы для проверки сом- портов serialNetTools c пультом от телевизора и камеры мобильника, все работает как часы. Затем аналогичная проверка с тем же комплектом была проведена в Wine и тоже все работает как часы.
Вот краткая информация о системе: у меня установлен Linux mint 17.2 mate 64x, ядро 4.1.5-040105-generic. Сам Lirc 0.9.0 установлен из репов без ошибок. Также установлен пакет irda-utils и Ircp Tray 0.7.6.Вот вывод команды lsusb:

Код: Выделить всё

Bus 002 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0ac8:c33f Z-Star Microelectronics Corp. Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 09da:000a A4 Tech Co., Ltd Optical Mouse Opto 510D
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Вот ответ команды dmesg:

Код: Выделить всё

[    0.923461] usb usb8: SerialNumber: 0000:00:1d.2
[    0.923631] hub 8-0:1.0: USB hub found
[    0.923639] hub 8-0:1.0: 2 ports detected
[    0.923839] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PSM1] at 0x60,0x64 irq 1,12
[    0.926536] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.926542] serio: i8042 AUX port at 0x60,0x64 irq 12
[    0.926766] mousedev: PS/2 mouse device common for all mice
[    0.927279] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[    0.927315] rtc_cmos 00:03: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[    0.927341] i2c /dev entries driver
[    0.927423] device-mapper: uevent: version 1.0.3
[    0.927529] device-mapper: ioctl: 4.31.0-ioctl (2015-3-12) initialised: dm-devel@redhat.com
[    0.927555] ledtrig-cpu: registered to indicate activity on CPUs
[    0.927785] PCCT header not found.
[    0.928091] NET: Registered protocol family 10
[    0.928392] NET: Registered protocol family 17
[    0.928409] Key type dns_resolver registered
[    0.928873] Loading compiled-in X.509 certificates
[    0.930127] Loaded X.509 cert 'Build time autogenerated kernel key: 46fd0f30f3bd8f146803e982177aac2d077a899c'
[    0.930146] registered taskstats version 1
[    0.932911] Key type trusted registered
[    0.938046] Key type encrypted registered
[    0.938060] AppArmor: AppArmor sha1 policy hashing enabled
[    0.938065] ima: No TPM chip found, activating TPM-bypass!
[    0.938095] evm: HMAC attrs: 0x1
[    0.938621]   Magic number: 8:895:819
[    0.938778] rtc_cmos 00:03: setting system clock to 2016-03-08 05:50:38 UTC (1457416238)
[    0.938886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    0.938888] EDD information not available.
[    0.938985] PM: Hibernation image not present or could not be loaded.
[    0.939670] Freeing unused kernel memory: 1424K (ffffffff81d38000 - ffffffff81e9c000)
[    0.939675] Write protecting the kernel read-only data: 12288k
[    0.939963] Freeing unused kernel memory: 124K (ffff8800017e1000 - ffff880001800000)
[    0.940293] Freeing unused kernel memory: 316K (ffff880001bb1000 - ffff880001c00000)
[    0.958827] systemd-udevd[105]: starting version 204
[    0.961044] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
[    1.001084] sky2: driver version 1.30
[    1.001440] sky2 0000:04:00.0: Yukon-2 FE+ chip revision 0
[    1.002606] sky2 0000:04:00.0 eth0: addr 00:24:54:c4:a6:db
[    1.007773] ahci 0000:00:1f.2: version 3.0
[    1.007991] ahci 0000:00:1f.2: SSS flag set, parallel bus scan disabled
[    1.008059] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 3 Gbps 0x33 impl SATA mode
[    1.008063] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part ccc ems sxs
[    1.025199] [drm] Initialized drm 1.1.0 20060810
[    1.048120] scsi host0: ahci
[    1.052111] scsi host1: ahci
[    1.059754] scsi host2: ahci
[    1.064066] scsi host3: ahci
[    1.068162] scsi host4: ahci
[    1.075276] scsi host5: ahci
[    1.075408] ata1: SATA max UDMA/133 abar m2048@0xfc704000 port 0xfc704100 irq 28
[    1.075413] ata2: SATA max UDMA/133 abar m2048@0xfc704000 port 0xfc704180 irq 28
[    1.075415] ata3: DUMMY
[    1.075417] ata4: DUMMY
[    1.075420] ata5: SATA max UDMA/133 abar m2048@0xfc704000 port 0xfc704300 irq 28
[    1.075423] ata6: SATA max UDMA/133 abar m2048@0xfc704000 port 0xfc704380 irq 28
[    1.076360] [drm] Memory usable by graphics device = 2048M
[    1.076366] checking generic (d0000000 300000) vs hw (d0000000 10000000)
[    1.076368] fb: switching to inteldrmfb from VESA VGA
[    1.076397] Console: switching to colour dummy device 80x25
[    1.076502] [drm] Replacing VGA console driver
[    1.083940] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.083943] [drm] Driver supports precise vblank timestamp query.
[    1.084073] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    1.158783] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    1.158984] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input7
[    1.159114] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0
[    1.232065] [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
[    1.232092] usb 2-3: new high-speed USB device number 2 using ehci-pci
[    1.272082] usb 1-4: new high-speed USB device number 3 using ehci-pci
[    1.277356] fbcon: inteldrmfb (fb0) is primary device
[    1.365452] usb 2-3: New USB device found, idVendor=05e3, idProduct=0608
[    1.365454] usb 2-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.365456] usb 2-3: Product: USB2.0 Hub
[    1.365913] hub 2-3:1.0: USB hub found
[    1.366267] hub 2-3:1.0: 4 ports detected
[    1.400058] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.405935] ata1.00: ATA-8: SAMSUNG HM321HI, 2AJ10002, max UDMA/133
[    1.405936] ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    1.411861] ata1.00: configured for UDMA/133
[    1.412026] scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HM321HI  0002 PQ: 0 ANSI: 5
[    1.412373] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.412411] sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[    1.412513] sd 0:0:0:0: [sda] Write Protect is off
[    1.412515] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.412549] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.419084] usb 1-4: New USB device found, idVendor=0ac8, idProduct=c33f
[    1.419086] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.419088] usb 1-4: Product: WebCam SCB-0340N
[    1.419089] usb 1-4: Manufacturer: Namuga.
[    1.564060] usb 3-1: new low-speed USB device number 2 using uhci_hcd
[    1.565060]  sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 >
[    1.566000] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.636035] usb 2-3.1: new full-speed USB device number 3 using ehci-pci
[    1.732070] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.733837] ata2.00: ATAPI: TSSTcorp CDDVDW TS-L633J, SC00, max UDMA/100
[    1.734451] ata2.00: configured for UDMA/100
[    1.737135] usb 3-1: New USB device found, idVendor=09da, idProduct=000a
[    1.737137] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.737139] usb 3-1: Product: PS/2+USB Mouse
[    1.737141] usb 3-1: Manufacturer: A4Tech
[    1.738265] scsi 1:0:0:0: CD-ROM            TSSTcorp CDDVDW TS-L633J  SC00 PQ: 0 ANSI: 5
[    1.754249] hidraw: raw HID events driver (C) Jiri Kosina
[    1.759750] sr 1:0:0:0: [sr0] scsi3-mmc drive: 16x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[    1.759752] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.759936] sr 1:0:0:0: Attached scsi CD-ROM sr0
[    1.760058] sr 1:0:0:0: Attached scsi generic sg1 type 5
[    1.768220] usbcore: registered new interface driver usbhid
[    1.768221] usbhid: USB HID core driver
[    1.770413] input: A4Tech PS/2+USB Mouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/0003:09DA:000A.0001/input/input8
[    1.770598] a4tech 0003:09DA:000A.0001: input,hidraw0: USB HID v1.10 Mouse [A4Tech PS/2+USB Mouse] on usb-0000:00:1a.0-1/input0
[    1.820032] clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x1e3216103cd, max_idle_ns: 440795240010 ns
[    1.861764] psmouse serio1: elantech: assuming hardware version 2 (with firmware version 0x040215)
[    1.898741] psmouse serio1: elantech: Synaptics capabilities query result 0x08, 0x14, 0x0c.
[    2.039296] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6
[    2.084077] ata5: SATA link down (SStatus 0 SControl 300)
[    2.092114] Console: switching to colour frame buffer device 170x48
[    2.095337] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    2.095339] i915 0000:00:02.0: registered panic notifier
[    2.111343] usb 2-3.1: New USB device found, idVendor=0403, idProduct=6001
[    2.111347] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.111349] usb 2-3.1: Product: FT232R USB UART
[    2.111352] usb 2-3.1: Manufacturer: FTDI
[    2.111354] usb 2-3.1: SerialNumber: A9U9LFFR
[    2.404046] ata6: SATA link down (SStatus 0 SControl 300)
[    3.149120] random: nonblocking pool is initialized
[    4.479680] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    5.882023] init: ureadahead main process (276) terminated with status 5
[    7.129683] Adding 976556k swap on /dev/sda8.  Priority:-1 extents:1 across:976556k FS
[    8.739687] systemd-udevd[391]: starting version 204
[   10.093582] usbcore: registered new interface driver usbserial
[   10.093605] usbcore: registered new interface driver usbserial_generic
[   10.093623] usbserial: USB Serial support registered for generic
[   10.396752] lp: driver loaded but no devices found
[   10.450440] ppdev: user-space parallel port driver
[   12.362142] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   12.482915] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
[   12.482924] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   12.482928] ACPI Warning: SystemIO range 0x00000000000011B0-0x00000000000011BF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\GPIO) (20150410/utaddress-254)
[   12.482933] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   12.482935] ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\GPIO) (20150410/utaddress-254)
[   12.482939] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   12.482941] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   12.759317] cfg80211: Calling CRDA to update world regulatory domain
[   13.212711] ath: phy0: Enable LNA combining
[   13.225842] ath: phy0: ASPM enabled: 0x42
[   13.225848] ath: EEPROM regdomain: 0x65
[   13.225849] ath: EEPROM indicates we should expect a direct regpair map
[   13.225852] ath: Country alpha2 being used: 00
[   13.225854] ath: Regpair used: 0x65
[   13.229469] device-mapper: multipath: version 1.9.0 loaded
[   13.404596] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   13.405168] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc90000820000, irq=17
[   13.771563] usbcore: registered new interface driver ftdi_sio
[   13.771590] usbserial: USB Serial support registered for FTDI USB Serial Device
[   13.771700] ftdi_sio 2-3.1:1.0: FTDI USB Serial Device converter detected
[   13.771744] usb 2-3.1: Detected FT232RL
[   13.772431] usb 2-3.1: FTDI USB Serial Device converter now attached to ttyUSB0
[   13.784674] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC269VB: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   13.784680] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   13.784683] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[   13.784685] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[   13.784687] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[   13.784691] snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x19
[   13.784693] snd_hda_codec_realtek hdaudioC0D0:      Mic=0x18
[   13.794042] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[   13.794206] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[   13.958192] media: Linux media interface: v0.10
[   13.994712] Linux video capture interface: v2.00
[   14.036911] samsung_laptop: enabled workaround for brightness stepping quirk
[   14.038697] samsung_laptop: detected SABI interface: SwSmi@
[   14.499870] uvcvideo: Found UVC 1.00 device WebCam SCB-0340N (0ac8:c33f)
[   14.505718] input: WebCam SCB-0340N as /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.0/input/input11
[   14.506588] usbcore: registered new interface driver uvcvideo
[   14.506593] USB Video Class driver (1.1.1)
[   15.061789] cfg80211: World regulatory domain updated:
[   15.061794] cfg80211:  DFS Master region: unset
[   15.061796] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   15.061799] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   15.061802] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   15.061805] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[   15.061807] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   15.061810] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   20.239688] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   22.588762] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[   22.770001] EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: (null)
[   23.005960] EXT4-fs (sda13): mounted filesystem with ordered data mode. Opts: (null)
[   23.087266] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[   23.147106] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[   23.297305] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[   23.397591] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[   24.155284] init: failsafe main process (918) killed by TERM signal
[   26.057091] ttyS1: LSR safety check engaged!
[   26.057912] ttyS1: LSR safety check engaged!
[   29.010463] Bluetooth: Core ver 2.20
[   29.010492] NET: Registered protocol family 31
[   29.010494] Bluetooth: HCI device and connection manager initialized
[   29.010501] Bluetooth: HCI socket layer initialized
[   29.010505] Bluetooth: L2CAP socket layer initialized
[   29.010517] Bluetooth: SCO socket layer initialized
[   29.113896] Bluetooth: RFCOMM TTY layer initialized
[   29.113909] Bluetooth: RFCOMM socket layer initialized
[   29.113923] Bluetooth: RFCOMM ver 1.11
[   29.184146] init: cups main process (1090) killed by HUP signal
[   29.184165] init: cups main process ended, respawning
[   29.210331] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   29.210336] Bluetooth: BNEP filters: protocol multicast
[   29.210344] Bluetooth: BNEP socket layer initialized
[   32.447181] lirc_dev: IR Remote Control driver registered, major 248
[   33.019442] lirc_serial: module is from the staging directory, the quality is unknown, you have been warned.
[   33.019881] lirc_serial lirc_serial.0: port 02f8 already in use
[   33.019886] lirc_serial lirc_serial.0: use 'setserial /dev/ttySX uart none'
[   33.019888] lirc_serial lirc_serial.0: or compile the serial port driver as module and
[   33.019890] lirc_serial lirc_serial.0: make sure this module is loaded first
[   33.019904] lirc_serial: probe of lirc_serial.0 failed with error -16
[   33.019979] platform lirc_serial.0: lirc_dev: driver lirc_serial registered at minor = 0
[   35.682248] NET: Registered protocol family 23
[   36.469461] sky2 0000:04:00.0 eth0: enabling interface
[   36.469994] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   36.492835] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   36.568860] init: samba-ad-dc main process (1251) terminated with status 1
[   37.919474] init: plymouth-upstart-bridge main process ended, respawning
[   37.927962] init: plymouth-upstart-bridge main process (1473) terminated with status 1
[   37.927990] init: plymouth-upstart-bridge main process ended, respawning
[   38.034976] sky2 0000:04:00.0 eth0: Link is up at 100 Mbps, full duplex, flow control both
[   38.035011] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   43.980000] NET: Registered protocol family 24
[   59.486243] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[   59.492128] vboxdrv: Found 2 processor cores
[   59.493416] vboxdrv: fAsync=0 offMin=0x1c4 offMax=0x41d4
[   59.593614] vboxdrv: TSC mode is Synchronous, tentative frequency 2094746999 Hz
[   59.593619] vboxdrv: Successfully loaded version 5.0.12 (interface 0x00240000)
[   59.830451] VBoxNetFlt: Successfully started.
[   59.860671] VBoxNetAdp: Successfully started.
[   59.888715] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.888730] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.888870] pci_bus 0000:08: Allocating resources
[   59.888895] pci 0000:00:1e.0: bridge window [io  0x1000-0x0fff] to [bus 08] add_size 1000
[   59.888899] pci 0000:00:1e.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 08] add_size 200000 add_align 100000
[   59.888903] pci 0000:00:1e.0: bridge window [mem 0x00100000-0x000fffff] to [bus 08] add_size 200000 add_align 100000
[   59.888906] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.888915] pci 0000:00:1e.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
[   59.888918] pci 0000:00:1e.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
[   59.888921] pci 0000:00:1e.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
[   59.888923] pci 0000:00:1e.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
[   59.888926] pci 0000:00:1e.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[   59.888929] pci 0000:00:1e.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
[   59.888936] pci 0000:00:1e.0: BAR 14: assigned [mem 0xc0100000-0xc02fffff]
[   59.888942] pci 0000:00:1e.0: BAR 15: assigned [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.888948] pci 0000:00:1e.0: BAR 13: assigned [io  0x6000-0x6fff]
[   59.888951] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.888955] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.888961] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.888967] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.889481] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.889488] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.889492] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.889499] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.889505] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.889657] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.889662] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.889666] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.889673] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.889679] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.889808] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.889813] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.889821] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.889833] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.889842] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.889880] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.889888] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.889893] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.889905] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.889913] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.890085] pci_bus 0000:02: Allocating resources
[   59.890103] pci_bus 0000:04: Allocating resources
[   59.890142] pci_bus 0000:06: Allocating resources
[   59.890162] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.890167] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.890170] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.890177] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.890182] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.897376] VBoxPciLinuxInit
[   59.929752] vboxpci: IOMMU not found (not registered)
[   67.018170] init: plymouth-stop pre-start process (2396) terminated with status 1
[   89.688530] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   89.795744] Netfilter messages via NETLINK v0.30.
[   89.804159] ctnetlink v0.93: registering with nfnetlink.
[   89.875292] ip_tables: (C) 2000-2006 Netfilter Core Team
[  169.279278] perf interrupt took too long (2511 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[  200.827091] CE: hpet increased min_delta_ns to 20115 nsec
[  710.018955] perf interrupt took too long (5001 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
[13349.451445] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[13349.521174] usb 2-3.1: USB disconnect, device number 3
[13349.521360] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[13349.521367] ftdi_sio ttyUSB0: urb failed to clear flow control
[13349.548095] ftdi_sio ttyUSB0: urb failed to clear flow control
[13349.552464] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[13349.552479] ftdi_sio 2-3.1:1.0: device disconnected
[16979.172073] usb 2-3.1: new full-speed USB device number 4 using ehci-pci
[16979.646438] usb 2-3.1: New USB device found, idVendor=0403, idProduct=6001
[16979.646443] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[16979.646450] usb 2-3.1: Product: FT232R USB UART
[16979.646453] usb 2-3.1: Manufacturer: FTDI
[16979.646455] usb 2-3.1: SerialNumber: A9U9LFFR
[16979.693459] ftdi_sio 2-3.1:1.0: FTDI USB Serial Device converter detected
[16979.693533] usb 2-3.1: Detected FT232RL
[16979.694275] usb 2-3.1: FTDI USB Serial Device converter now attached to ttyUSB1
[16992.894487] usb 2-3.1: USB disconnect, device number 4
[16992.894703] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[16992.894720] ftdi_sio 2-3.1:1.0: device disconnected
[16994.216065] usb 2-3.1: new full-speed USB device number 5 using ehci-pci
[16994.686691] usb 2-3.1: New USB device found, idVendor=0403, idProduct=6001
[16994.686700] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[16994.686703] usb 2-3.1: Product: FT232R USB UART
[16994.686705] usb 2-3.1: Manufacturer: FTDI
[16994.686708] usb 2-3.1: SerialNumber: A9U9LFFR
[16994.733946] ftdi_sio 2-3.1:1.0: FTDI USB Serial Device converter detected
[16994.734001] usb 2-3.1: Detected FT232RL
[16994.734650] usb 2-3.1: FTDI USB Serial Device converter now attached to ttyUSB1
[18245.805574] CE: hpet increased min_delta_ns to 30172 nsec
[21421.148249] CE: hpet increased min_delta_ns to 45258 nsec
[21561.631934] ttyS1: LSR safety check engaged!
[22936.040063] usb 2-1: new high-speed USB device number 6 using ehci-pci
[22936.178530] usb 2-1: New USB device found, idVendor=6000, idProduct=dec0
[22936.178539] usb 2-1: New USB device strings: Mfr=16, Product=32, SerialNumber=64
[22936.178542] usb 2-1: Product: Behold TV Wander
[22936.178544] usb 2-1: Manufacturer: Beholder Intl. Ltd.
[22936.178546] usb 2-1: SerialNumber: 000000BB58
[22936.452242] tm6000: alt 0, interface 0, class 255
[22936.452247] tm6000: alt 0, interface 0, class 255
[22936.452250] tm6000: Bulk IN endpoint: 0x82 (max size=512 bytes)
[22936.452252] tm6000: alt 0, interface 0, class 255
[22936.452253] tm6000: alt 1, interface 0, class 255
[22936.452255] tm6000: ISOC IN endpoint: 0x81 (max size=3072 bytes)
[22936.452257] tm6000: alt 1, interface 0, class 255
[22936.452259] tm6000: alt 1, interface 0, class 255
[22936.452260] tm6000: INT IN endpoint: 0x83 (max size=4 bytes)
[22936.452262] tm6000: alt 2, interface 0, class 255
[22936.452264] tm6000: alt 2, interface 0, class 255
[22936.452266] tm6000: alt 2, interface 0, class 255
[22936.452267] tm6000: alt 3, interface 0, class 255
[22936.452269] tm6000: alt 3, interface 0, class 255
[22936.452271] tm6000: alt 3, interface 0, class 255
[22936.452273] tm6000: New video device @ 480 Mbps (6000:dec0, ifnum 0)
[22936.452274] tm6000: Found Beholder Wander DVB-T/TV/FM USB2.0
[22936.458881] Found tm6010
[22937.163978] tm6000 #0: i2c eeprom 00: 42 59 54 45 12 01 00 02 00 00 00 40 00 60 c0 de  BYTE.......@.`..
[22937.278082] tm6000 #0: i2c eeprom 10: 01 00 10 20 40 01 28 03 42 00 65 00 68 00 6f 00  ... @.(.B.e.h.o.
[22937.392065] tm6000 #0: i2c eeprom 20: 6c 00 64 00 65 00 72 00 20 00 49 00 6e 00 74 00  l.d.e.r. .I.n.t.
[22937.506410] tm6000 #0: i2c eeprom 30: 6c 00 2e 00 20 00 4c 00 74 00 64 00 2e 00 ff ff  l... .L.t.d.....
[22937.622180] tm6000 #0: i2c eeprom 40: 22 03 42 00 65 00 68 00 6f 00 6c 00 64 00 20 00  ".B.e.h.o.l.d. .
[22937.736068] tm6000 #0: i2c eeprom 50: 54 00 56 00 20 00 57 00 61 00 6e 00 64 00 65 00  T.V. .W.a.n.d.e.
[22937.850078] tm6000 #0: i2c eeprom 60: 72 00 ff ff ff ff ff ff ff ff 1a 03 56 00 69 00  r...........V.i.
[22937.963071] tm6000 #0: i2c eeprom 70: 64 00 65 00 6f 00 43 00 61 00 70 00 74 00 75 00  d.e.o.C.a.p.t.u.
[22938.077562] tm6000 #0: i2c eeprom 80: 72 00 65 00 ff ff ff ff ff ff ff ff ff ff ff ff  r.e.............
[22938.191557] tm6000 #0: i2c eeprom 90: ff ff ff ff 16 03 30 00 30 00 30 00 30 00 30 00  ......0.0.0.0.0.
[22938.305553] tm6000 #0: i2c eeprom a0: 30 00 42 00 42 00 35 00 38 00 ff ff ff ff ff ff  0.B.B.5.8.......
[22938.419560] tm6000 #0: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
[22938.533559] tm6000 #0: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
[22938.647694] tm6000 #0: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
[22938.762834] tm6000 #0: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
[22938.880097] tm6000 #0: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................
[22939.014039] tuner 8-0061: Tuner -1 found with type(s) Radio TV.
[22939.022813] xc5000 8-0061: creating new instance
[22939.053065] xc5000: Successfully identified at address 0x61
[22939.053069] xc5000: Firmware has not been loaded previously
[22942.403164] xc5000: Firmware dvb-fe-xc5000-1.6.114.fw loaded and running.
[22943.690704] tm6000 #0: registered device video1
[22943.691864] tm6000 #0: registered device radio0
[22943.691869] Trident TVMaster TM5600/TM6000/TM6010 USB2 board (Load status: 0)
[22943.691927] usbcore: registered new interface driver tm6000
[22943.745891] tm6000 #0: Initialized (TM6000 Audio Extension) extension
[22943.863092] DVB: registering new adapter (Trident TVMaster 6000 DVB-T)
[22943.863103] usb 2-1: DVB: registering adapter 0 frontend 0 (Zarlink ZL10353 DVB-T)...
[22943.863246] xc5000 8-0061: attaching existing instance
[22943.889082] xc5000: Successfully identified at address 0x61
[22943.889086] xc5000: Firmware has been loaded previously
[22943.889088] tm6000: XC5000 asked to be attached to frontend!
[22943.891153] tm6000 #0: Initialized (TM6000 dvb Extension) extension
[31209.056445] init: nmbd main process (1719) killed by TERM signal
[31209.377532] init: smbd main process (888) killed by TERM signal
[31235.519803] init: samba-ad-dc main process (9615) terminated with status 1
[37257.270194] traps: ircp-tray[3987] trap int3 ip:7f8fda578c13 sp:7fffcf2ff520 error:0
[42157.309885] usb 2-1: USB disconnect, device number 6
[42157.309986] tm6000: disconnecting tm6000 #0
[42157.371924] xc5000 8-0061: destroying instance

Это ответ на команду lsmod | grep lirc:

Код: Выделить всё

lirc_serial            20480  0
lirc_dev               20480  1 lirc_serial
rc_core                28672  2 lirc_dev,tm6000

Это ответ на команду sudo service lirc start:

Код: Выделить всё

* Loading LIRC modules                                                  [ OK ]
find: `/sys/class/rc/*/': Нет такого файла или каталога
 * Starting remote control daemon(s) :                                   [ OK ]

В папке rc действительно нет никаких файлов и она абсолютно пустая. файлы Hardware.conf и Lircd.conf с конфигом моего пульта для ик приемника/передатчика, номер порта соответственно меняется в зависимости от номера под которым опознается мой переходник:

Код: Выделить всё

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="JVC"
REMOTE_MODULES="lirc_dev lirc_serial"
REMOTE_DRIVER="default"
REMOTE_DEVICE="/dev/ttyUSB0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="/etc/lirc/lircd.conf"
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="Custom"
TRANSMITTER_MODULES="lirc_dev lirc_serial"
TRANSMITTER_DRIVER="default"
TRANSMITTER_DEVICE="/dev/ttyUSB0"
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF="/etc/lirc/lircd.conf"
TRANSMITTER_LIRCD_ARGS=""

#Disable kernel support.
#Typically, lirc will disable in-kernel support for ir devices in order to
#handle them internally.  Set to false to prevent lirc from disabling this
#in-kernel support.
#DISABLE_KERNEL_SUPPORT="true"

#Enable lircd
START_LIRCD="true"

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF="true"

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD="false"


Код: Выделить всё

#This configuration has been automatically generated via
#the Ubuntu LIRC package maintainer scripts.
#
#It includes the default configuration for the remote and/or
#transmitter that you have selected during package installation.
#
#Feel free to add any custom remotes to the configuration
#via additional include directives or below the existing
#Ubuntu include directives from your selected remote and/or
#transmitter.

#Configuration for the Custom transmitter:
include "/etc/lirc/lircd.conf"
# this config file was automatically generated
# using WinLIRC 0.6.4 (LIRC 0.6.1pre3) on Thu Mar 20 17:11:44 2003
#
# contributed by
#
# brand:             JVC
# model:             RM-C462 / RM-C457
# supported devices: TV
#

begin remote

  name  RM-C462
  bits            8
  flags SPACE_ENC|NO_HEAD_REP|CONST_LENGTH
  eps            30
  aeps          100

  header       8492  4182
  one           558  1555
  zero          558   496
  ptrail        559
  pre_data_bits   8
  pre_data       0xC0
  gap          46464
  min_repeat      1
  toggle_bit      0


      begin codes
          TV/VIDEO                 0x00000000000000C8
          KEY_POWER                0x00000000000000E8        #  Was: POWER
          COLOUR_SYSTEM            0x0000000000000049
          SOUND_SYSTEM             0x000000000000002D
          DISPLAY                  0x0000000000000020
          KEY_1                    0x0000000000000084        #  Was: 1
          KEY_2                    0x0000000000000044        #  Was: 2
          KEY_3                    0x00000000000000C4        #  Was: 3
          CH_PRESET                0x0000000000000099
          KEY_4                    0x0000000000000024        #  Was: 4
          KEY_5                    0x00000000000000A4        #  Was: 5
          KEY_6                    0x0000000000000064        #  Was: 6
          OFF_TIMER                0x00000000000000C0
          KEY_7                    0x00000000000000E4        #  Was: 7
          KEY_8                    0x0000000000000014        #  Was: 8
          KEY_9                    0x0000000000000094        #  Was: 9
          KEY_0                    0x0000000000000004        #  Was: 0
          KEY_MAX                  0x00000000000000B9        #  Was: MAX_CH
          PICTURE_MODE             0x000000000000009E
          PICTURE_ADJUST-          0x00000000000000DA
          PICTURE_ADJUST           0x00000000000000DE
          PICTURE_ADJUST+          0x000000000000005A
          KEY_MUTE                 0x0000000000000038        #  Was: MUTE
          KEY_CHANNELDOWN          0x0000000000000018        #  Was: CHANNEL-
          KEY_CHANNELUP            0x0000000000000098        #  Was: CHANNEL+
          KEY_VOLUMEDOWN           0x00000000000000F8        #  Was: VOLUME-
          KEY_VOLUMEUP             0x0000000000000078        #  Was: VOLUME+
      end codes

end remote

Ответ на команду sudo setserial /dev/ttyS0 uart none в ответ съел. Далее modprobe lirc_serial также съел. Еще mode2 -d /dev/lirc0 в ответ:

Код: Выделить всё

mode2: could not open /dev/lirc0
mode2: default_init(): Permission denied

Ответ команды sudo cat /etc/init.d/lirc:

Код: Выделить всё

#! /bin/sh
### BEGIN INIT INFO
# Provides:          lirc
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Starts LIRC daemon.
# Description:       LIRC is used to control different
#                    infrared receivers and transceivers.
### END INIT INFO

load_modules ()
{
    MODULES_MISSING=false

    log_daemon_msg "Loading LIRC modules"
    for mod in $*; do
        if [ $mod = "udev" ]; then
            log_end_msg 0
            log_success_msg "Restarted via udev, don't reload modules"
            break
        else
            modprobe $mod 2> /dev/null || MODULES_MISSING=true
        fi
    done
    log_end_msg $?

    if $MODULES_MISSING; then
        log_failure_msg "Unable to load LIRC kernel modules. Verify your"
        log_failure_msg "selected kernel modules in /etc/lirc/hardware.conf"
        START_LIRCMD=false
        START_LIRCD=false
    fi
}

build_remote_args ()
{
    REMOTE_ARGS="$*"

    #For remote only detection support, we need
    #both REMOTE_DEVICE and TRANSMITTER_DEVICE undefined
    if [ -z "$REMOTE_DEVICE" ] && [ -z "$TRANSMITTER_DEVICE" ] && [ -c $dev ]; then
        REMOTE_DEVICE="$dev"
    fi

    #If we have a REMOTE_DEVICE or REMOTE_DRIVER defined (either because no devices
    #were defined, OR if we explicitly did), then populate REMOTE_ARGS
    if [ -n "$REMOTE_DEVICE" ] || [ -n "$REMOTE_DRIVER" ]; then
        if [ -n "$REMOTE_DEVICE" ] && [ "$REMOTE_DEVICE" != "none" ]; then
            REMOTE_ARGS="--device=$REMOTE_DEVICE $REMOTE_ARGS"
        fi
        if [ -n "$REMOTE_DRIVER" ] && [ "$REMOTE_DRIVER" != "none" ]; then
            REMOTE_ARGS="--driver=$REMOTE_DRIVER $REMOTE_ARGS"
        fi

        #Now, if we ALSO have a transmitter defined, add some args
        #To make the first lircd listen up
        if [ -n "$TRANSMITTER_DEVICE" ] || [ -n "$TRANSMITTER_DRIVER" ]; then
            REMOTE_ARGS="$REMOTE_ARGS --connect=localhost:8765"
        fi
        REMOTE_ARGS="--output=$REMOTE_SOCKET $REMOTE_ARGS"
    fi
    REMOTE_PID="--pidfile=/run/lirc/lircd.pid"
    echo $REMOTE_ARGS
}

build_transmitter_args ()
{
    TRANSMITTER_ARGS="$*"

    #Transmitters must be explicitly be defined
    if [ -n "$TRANSMITTER_DEVICE" ] || [ -n "$TRANSMITTER_DRIVER" ]; then
        if [ -n "$TRANSMITTER_DEVICE" ] && [ "$TRANSMITTER_DEVICE" != "none" ]; then
            TRANSMITTER_ARGS="--device=$TRANSMITTER_DEVICE $TRANSMITTER_ARGS"
        fi
        if [ -n "$TRANSMITTER_DRIVER" ] && [ "$TRANSMITTER_DRIVER" != "none" ]; then
            TRANSMITTER_ARGS="--driver=$TRANSMITTER_DRIVER $TRANSMITTER_ARGS"
        fi

        #Now, if we ALSO have a remote defined, add some args
        #To make the second lircd connect
        if [ -n "$REMOTE_DEVICE" ] || [ -n "$REMOTE_DRIVER" ]; then
            TRANSMITTER_ARGS="$TRANSMITTER_ARGS --listen --pidfile=/run/lirc/lircd1.pid"
            TRANSMITTER_PID="--pidfile=/run/lirc/lircd1.pid"
        else
            TRANSMITTER_PID="--pidfile=/run/lirc/lircd.pid"
        fi
        TRANSMITTER_ARGS="--output=$TRANSMITTER_SOCKET $TRANSMITTER_ARGS"
    fi
    echo $TRANSMITTER_ARGS
}

in_kernel_support() {
    if [ -d /sys/class/rc ] && [ "$DISABLE_KERNEL_SUPPORT" = "true" ]; then
        for file in `find /sys/class/rc/*/ -name protocols`; do
            if [ "$1" = "disable" ]; then
                echo "lirc" > $file
            else
                echo "none" > $file
                for protocol in `cat $file`; do
                    echo "+${protocol}" > $file
                done
            fi
        done
    fi
}
. /lib/lsb/init-functions

test -f /usr/sbin/lircd || exit 0
test -f /usr/sbin/lircmd || exit 0

START_LIRCMD=true
START_LIRCD=true
START_IREXEC=true
DISABLE_KERNEL_SUPPORT=true


if [ -f /etc/lirc/hardware.conf ];then
    . /etc/lirc/hardware.conf
fi

if [ ! -f /etc/lirc/lircd.conf ] || grep -q "^#UNCONFIGURED" /etc/lirc/lircd.conf; then
    if [ "$1" = "start" ]; then
        log_success_msg "No valid /etc/lirc/lircd.conf has been found."
        log_success_msg "Remote control support has been disabled."
        log_success_msg "Reconfigure LIRC or manually replace /etc/lirc/lircd.conf to enable."
    fi

    START_LIRCD=false
    START_LIRCMD=false
    START_IREXEC=false
fi

if [ ! -f /etc/lirc/lircmd.conf ] || grep -q "^#UNCONFIGURED" /etc/lirc/lircmd.conf; then
    START_LIRCMD=false
fi

if [ ! -f /etc/lirc/lircrc ] || grep -q "^#UNCONFIGURED" /etc/lirc/lircrc; then
    START_IREXEC=false
fi

#We need default socket locations
OLD_SOCKET="/dev/lircd"
if [ -z "$REMOTE_SOCKET" ]; then
    REMOTE_SOCKET="/run/lirc/lircd"
fi
if [ -z "$TRANSMITTER_SOCKET" ]; then
    TRANSMITTER_SOCKET="/run/lirc/lircd"
    #Now, if we ALSO have a remote defined,
    #change the default transmitter socket
    if [ -n "$REMOTE_DEVICE" ] || [ -n "$REMOTE_DRIVER" ]; then
        TRANSMITTER_SOCKET="${TRANSMITTER_SOCKET}1"
    fi
fi

case "$1" in
    start)
        if [ "$LOAD_MODULES" = "true" ] && [ "$START_LIRCD" = "true" ]; then
            load_modules $2 $REMOTE_MODULES $TRANSMITTER_MODULES $MODULES
            in_kernel_support "disable"
        fi

        if [ "$START_LIRCD" = "true" ]; then
            mkdir -p "/run/lirc"
            log_daemon_msg "Starting remote control daemon(s) : "
            REMOTE_LIRCD_ARGS=`build_remote_args $REMOTE_LIRCD_ARGS`
            TRANSMITTER_LIRCD_ARGS=`build_transmitter_args $TRANSMITTER_LIRCD_ARGS`

            RES=1
            #if we have a transmitter defined, start it first
            if [ -n "$TRANSMITTER_LIRCD_ARGS" ]; then
                log_progress_msg "LIRC (transmitter)"
                start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/lircd --pidfile=$TRANSMITTER_PID -- $TRANSMITTER_LIRCD_ARGS < /dev/null
                RES=$?
            fi
            if [ -n "$REMOTE_LIRCD_ARGS" ]; then
                log_progress_msg "LIRC (remote)"
                start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/lircd --pidfile=$REMOTE_PID -- $REMOTE_LIRCD_ARGS < /dev/null
                RES=$?
            fi
            log_end_msg $RES

            #Set up symlinks, starting with the remote if present.
            if [ -n "$REMOTE_LIRCD_ARGS" ]; then
                if [ -S "$REMOTE_SOCKET" -a "$OLD_SOCKET" != "$REMOTE_SOCKET" ]; then
                    rm -f $OLD_SOCKET && ln -s $REMOTE_SOCKET $OLD_SOCKET
                fi
                if [ -n "$TRANSMITTER_LIRCD_ARGS" ]; then
                    if [ -S "$TRANSMITTER_SOCKET" ]; then
                        rm -f ${OLD_SOCKET}1 && ln -s $TRANSMITTER_SOCKET ${OLD_SOCKET}1
                    fi
                fi
            elif [ -n "$TRANSMITTER_LIRCD_ARGS" ]; then
                if [ -S "$TRANSMITTER_SOCKET" -a "$OLD_SOCKET" != "$TRANSMITTER_SOCKET" ]; then
                    rm -f $OLD_SOCKET && ln -s $TRANSMITTER_SOCKET $OLD_SOCKET
                fi
            fi
        fi

        if [ "$START_LIRCMD" = "true" ]; then
            mkdir -p "/run/lirc"
            log_daemon_msg "Starting remote control mouse daemon : LIRCMD "
            start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/lircmd < /dev/null
            log_end_msg $?
        fi

        if [ "$START_IREXEC" = "true" ]; then
            mkdir -p "/run/lirc"
            log_daemon_msg "Starting execution daemon: irexec"
            start-stop-daemon --start --quiet --oknodo --exec /usr/bin/irexec -- -d /etc/lirc/lircrc < /dev/null
            log_end_msg $?
        fi
        ;;
    stop)
        in_kernel_support "enable"
        if [ "$START_IREXEC" = "true" ]; then
            log_daemon_msg "Stopping execution daemon: irexec"
            start-stop-daemon --stop --oknodo --quiet --exec /usr/bin/irexec
            log_end_msg $?
        fi

        if [ "$START_LIRCMD" = "true" ]; then
            log_daemon_msg "Stopping remote control mouse daemon: LIRCMD"
            start-stop-daemon --stop --oknodo --quiet --exec /usr/sbin/lircmd
            log_end_msg $?
        fi

        if [ "$START_LIRCD" = "true" ]; then
            log_daemon_msg "Stopping remote control daemon(s): LIRC"
            start-stop-daemon --stop --oknodo --quiet --exec /usr/sbin/lircd --pidfile /run/lirc/lircd.pid
            start-stop-daemon --stop --oknodo --quiet --exec /usr/sbin/lircd --pidfile /run/lirc/lircd1.pid
            log_end_msg $?
            [ -h "$OLD_SOCKET" ] && rm -f $OLD_SOCKET
            [ -h "${OLD_SOCKET}1" ] && rm -f ${OLD_SOCKET}1
        fi
        ;;
    reload|force-reload)
        if [ "$START_IREXEC" = "true" ]; then
            start-stop-daemon --stop --quiet --signal 1 --exec /usr/bin/irexec
        fi

        if [ "$START_LIRCD" = "true" ]; then
            start-stop-daemon --stop --quiet --signal 1 --exec /usr/sbin/lircd
        fi

        if [ "$START_LIRCMD" = "true" ]; then
            start-stop-daemon --stop --quiet --signal 1 --exec /usr/sbin/lircmd
        fi
        ;;
    restart)
        $0 stop
        #passes parameter $2 which is possibly our udev paramater
        $0 start $2
        ;;
    *)
        echo "Usage: /etc/init.d/lircd {start|stop|reload|restart|force-reload}"
    exit 1
esac

exit 0


Подскажите пожалуйста какие еще нужны ритуалы чтобы заставить эту программу работать с этими ппортами и как сделать возможность поддержки помимо этого моего ик-приемника/передатчика и пульта ду от тв тюнера. Спасибо
Спасибо сказали:
Аватара пользователя
Bizdelnick
Модератор
Сообщения: 20752
Статус: nulla salus bello
ОС: Debian GNU/Linux

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение Bizdelnick »

sdv555 писал(а):
08.03.2016 21:30
Я собрал себе для управления через пульт ДУ от телевизора ИК- приемник/передатчик для СОМ- порта по приведенной здесь схеме:http://meandr.org/archives/2076 правда там вроде не совсем к тем контактам СОМ-порта подведены сигналы Rx и Tx поэтому я развел их как положено согласно распиновки RS232 интерфейса на 2 и 3 контакт соответственно.

То, что Вы сделали, это не RS232. Не вздумайте подключать к настоящему COM-порту — спалите, там совсем другой диапазон напряжений. Через переходник USB-UART, как Вы, насколько я понимаю, сделали, по идее должно работать. Но на всякий случай покажите схему своих переходников.

sdv555 писал(а):
08.03.2016 21:30
modprobe lirc_serial также съел

А после этого в /sys/class/rc/ ничего не появилось?
Пишите правильно:
в консоли
вку́пе (с чем-либо)
в общем
вообще
в течение (часа)
новичок
нюанс
по умолчанию
приемлемо
проблема
пробовать
трафик
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

Bizdelnick писал(а):
08.03.2016 22:20
sdv555 писал(а):
08.03.2016 21:30
Я собрал себе для управления через пульт ДУ от телевизора ИК- приемник/передатчик для СОМ- порта по приведенной здесь схеме:http://meandr.org/archives/2076 правда там вроде не совсем к тем контактам СОМ-порта подведены сигналы Rx и Tx поэтому я развел их как положено согласно распиновки RS232 интерфейса на 2 и 3 контакт соответственно.

То, что Вы сделали, это не RS232. Не вздумайте подключать к настоящему COM-порту — спалите, там совсем другой диапазон напряжений. Через переходник USB-UART, как Вы, насколько я понимаю, сделали, по идее должно работать. Но на всякий случай покажите схему своих переходников.

sdv555 писал(а):
08.03.2016 21:30
modprobe lirc_serial также съел

А после этого в /sys/class/rc/ ничего не появилось?


Здравствуйте. Переходники собраны по стандартной схеме включения для указанных выше микросхем согласно даташиту+преобразователь уровня ттл на микросхеме Max232. Первый переходник собран согласно этой схеме http://sprinter4wd.narod.ru/poleznye_melochi/usbrs232/ + добавлен туда согласно даташиту переключатель уровня сигнала и преобразователь уровня ТТЛ на Max 232 согласно его даташиту. второй переходник также собран податашиту на микросхему только без переключателя уровня но с преобразователем уровня ТТЛ. Без преобразователя схема не работает а с ним и отдельно от Сом порта все работает. Как я ранее написал там на схеме есть ошибки касаемо выводов подключения к разъему Сом порта на рисунке 2. Я их вывел как положено на выводы 2 и 3 разъема Сом- порта и все нормально заработало. Так что с железом все в полном порядке и все работает и реагирует на пульт и передает при тестировании как описано выше. Кроме того прежде чем подключать мой ик-девайс, я проверил работу переходников при помощи заглушки для сом-порта.

После
sdv555 писал(а):
08.03.2016 21:30
modprobe lirc_serial также съел
в указанной папке абсолютно пусто ни скрытых файлов ни каких других нет. Утилита Ircp Tray 0.7.6 также не видит никаких активных устройств. Сами эти микросхемы согласно описаниям на сайте Lirc. org поддерживаются системой. Оба конфигурационных файла пультов есть на указанном сайте.
Сам лирц судя по всему видит и понимает эти порты, но, что-то не дает загружатся daemond и на этом все тормозится. В нете переодически упоминается о каких-то функциях необходимых для работы лирца, которые якобы по умолчанию отключены в модулях ядра, но какие и как их активировать нигде не описано. Также у других всплывали подобные ошибки, но описанные методики устранения либо очень устарели, либо описаны для совершенно других дистрибутивов.
Спасибо сказали:
Аватара пользователя
Bizdelnick
Модератор
Сообщения: 20752
Статус: nulla salus bello
ОС: Debian GNU/Linux

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение Bizdelnick »

sdv555 писал(а):
09.03.2016 20:30
преобразователь уровня ттл на микросхеме Max232

Не понял, что Вы куда преобразуете? В схеме из http://meandr.org/archives/2076 уже TTL-уровни используются.
Пишите правильно:
в консоли
вку́пе (с чем-либо)
в общем
вообще
в течение (часа)
новичок
нюанс
по умолчанию
приемлемо
проблема
пробовать
трафик
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

Bizdelnick писал(а):
09.03.2016 20:41
sdv555 писал(а):
09.03.2016 20:30
преобразователь уровня ттл на микросхеме Max232

Не понял, что Вы куда преобразуете? В схеме из http://meandr.org/archives/2076 уже TTL-уровни используются.

В указанной по ссылке теме уровню логической 1 соответствует уровень -5...9 В, для ТТЛ логики логической 1 соответствует уровень +5 В. В стандартном Сом порту уровень логической единицы может быть в диапазоне от -11 до -15 В, поэтому выпускаются промышленные преобразователи на Max232 которые ивертируют сигналы сом-порта в сигналы уровня ТТЛ. Если мой девайс подключить непосредственно к этому переходнику или Сом-порту без преобразователя то будет оновременно идти и передача и прием и ничто не будет ни на что реагировать и транзистор в этом девайсе может раскалиться как печка. Когда подключаешь через преобразователь уровня ТТЛ все работает как часы. Я как раз первый переходник и преобразователь ТТЛ сделал в разных корпусах и поэтому я мог проверить работу этого девайса как без преобразователя так и с ним. Единственное, что выяснилось в процессе экспериментов это то, что практически в большинстве схем включения Max232 есть ошибка в том,что там на вход подают один сигнал например Тх а выход этого входа подключают к Rx при таком включении ничего не работает. Нужно,чтобы какой сигнал на входе, такой же должен сниматься на выходе т.е. ТХ вход ТХ выход и тогда все работает как часы.
Кстати вот автор четко указывает, что там нет преобразователя уровня ТТЛ
В этой схеме отсутствует преобразователь уровней TTL-RS232
, просто он не везде нужен, но для этого девайса он нужен обязательно. Я для удобства в этот девайс добавил светодиоды через токоограничивающие резисторы и поэтому я теперь могу без лишнего гемороя контролировать и питание и чтение и передачу, как на самом переходнике так и на девайсе. Питание на девайс и на преобразователь я вывел отдельными кабелями с ЮСБ вилками и запиттываю все это от внешнего БП через HUB.
Спасибо сказали:
Аватара пользователя
Bizdelnick
Модератор
Сообщения: 20752
Статус: nulla salus bello
ОС: Debian GNU/Linux

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение Bizdelnick »

sdv555 писал(а):
08.03.2016 21:30
Еще mode2 -d /dev/lirc0 в ответ:

Код: Выделить всё

mode2: could not open /dev/lirc0
mode2: default_init(): Permission denied

А если запустить через sudo, что говорит?
Пишите правильно:
в консоли
вку́пе (с чем-либо)
в общем
вообще
в течение (часа)
новичок
нюанс
по умолчанию
приемлемо
проблема
пробовать
трафик
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

Bizdelnick писал(а):
09.03.2016 22:48
sdv555 писал(а):
08.03.2016 21:30
Еще mode2 -d /dev/lirc0 в ответ:

Код: Выделить всё

mode2: could not open /dev/lirc0
mode2: default_init(): Permission denied

А если запустить через sudo, что говорит?


Здравствуйте.
Ввожу sudo mode2 -d /dev/lirc0
[sudo] password for dmitriy:

В ответ тишина и только мигающий курсор в ожидании чего-то. При нажатии кнопок пульта на экране ничего. Аналогичная ситуация и при использовании программы Irw для проверки опроса пульта, только там еще и подвисания присутствуют. :unsure:
Спасибо сказали:
Аватара пользователя
bormant
Сообщения: 1354

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение bormant »

sdv555 писал(а):
10.03.2016 19:12
мигающий курсор в ожидании чего-то
Это чего-то суть "password for dmitriy", там же написано, что на великом и могучем может быть истолковано как "Будьте так любезны, если вас не затруднит, введите, пожалуйста, пароль пользователя dmitry".
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

bormant писал(а):
10.03.2016 21:55
sdv555 писал(а):
10.03.2016 19:12
мигающий курсор в ожидании чего-то
Это чего-то суть "password for dmitriy", там же написано, что на великом и могучем может быть истолковано как "Будьте так любезны, если вас не затруднит, введите, пожалуйста, пароль пользователя dmitry".


Здравствуйте.
Я не настолько глуп чтобы не понять, что нужно ввести после команды sudo нужно ввести паспорт пользователя root, я сам и выставлен и как пользователь и как root . Поэтому имеется ввиду мигание курсора и ожидание ввода после того как был введен паспорт root.
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

Неужели все специалисты способные хоть как-то помочь в решении данной проблеммы вымерли? :unsure:
Спасибо сказали:
Аватара пользователя
alkesta
Сообщения: 345
ОС: Fedora

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение alkesta »

sdv555 писал(а):
09.03.2016 20:30
переходник собран согласно этой схеме http://sprinter4wd.narod.ru/poleznye_melochi/usbrs232/ + добавлен туда согласно даташиту переключатель уровня сигнала и преобразователь уровня ТТЛ на Max 232 согласно его даташиту.


Что-то перемудрил ты со схемой. http://www.huitsing.nl/irftdi/
Изображение
Написано: Current LIRC versions support this FTDI based hardware out of the box.

So for my receiver I start mode2 with:

mode2 -Hftdi -dserial=FTRVA1T9

в твоем случае, если я правильно посмотрел:
mode2 -Hftdi -dserial==A9U9LFFR
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

Что-то перемудрил ты со схемой. http://www.huitsing.nl/irftdi/


Здравствуйте.
Схем самих ик-приемников/ передатчиков великое множество. Предложенный вами вариант один из них и он является только приемником, схема которую я использую является и приемником и передатчиком и связывается она через COM-порт. Т.к. на ноутбуке нет COM-порта, я сделал переходник как было описано выше. Преобразователь уровня ТТЛ нужен чтобы инвертировать сигнал от FT232, т.к. без него не получается полного аналога стандартного COM- порта с должными уровнями сигнала и полярностью. Все связанное с вариантом схемы к данной проблемме никакого отношения не имеет, поскольку как я уже писал все было проверенно на прием и передачу как в windows, так и в линуксе через Wine. Поддержка FT232 в самом LIRC реализована и об этом четко написано на сайте этой программы.

Написано: Current LIRC versions support this FTDI based hardware out of the box.

So for my receiver I start mode2 with:

mode2 -Hftdi -dserial=FTRVA1T9

в твоем случае, если я правильно посмотрел:
mode2 -Hftdi -dserial==A9U9LFFR


Можно подробнее объяснить, где указанна эта строка и что мне необходимо изменить, чтобы Demond начал нормально загружаться? Еще можно ли как-то автоматизировать освобождение занятых Com-портов перед работой Lirc или эта программа должна сама как-то освобождать порт к которому подключен интерфейс в данный момент?
Спасибо.
Спасибо сказали:
Аватара пользователя
alkesta
Сообщения: 345
ОС: Fedora

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение alkesta »


mode2 -Hftdi -dserial=A9U9LFFR строка - это команда, которую можно в консоли выполнить.

www.lirc.org/html/mode2.html

www.lirc.org/html/configuration-guide.html

все должно быть понятно.
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

alkesta писал(а):
10.04.2016 10:30
mode2 -Hftdi -dserial=A9U9LFFR строка - это команда, которую можно в консоли выполнить.

www.lirc.org/html/mode2.html

www.lirc.org/html/configuration-guide.html

все должно быть понятно.


Спасибо.
Попробуем.
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

mode2 -Hftdi -dserial=A9U9LFFR строка - это команда, которую можно в консоли выполнить.

www.lirc.org/html/mode2.html

www.lirc.org/html/configuration-guide.html

все должно быть понятно.


Ввожу в командной строке команду:mode2 -Hftdi -dserial=A9U9LFFR и получаю:

Код: Выделить всё

 mode2: Initializing FTDI: serial=A9U9LFFR
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK

Это все длится бесконечно и не останавливается.
Далее перехожу по указанным ссылкам: 1. www.lirc.org/html/mode2.html
Ввожу в командной строке команду: sudo xmode2 --driver default --device /dev/lirc0 получаю ответ:mode2:
Далее ввожу: sudo mode2 --raw /dev/lirc0 получаю ответ:

Код: Выделить всё

mode2: too many arguments

Может я что-то не так делаю?
Спасибо сказали:
Аватара пользователя
alkesta
Сообщения: 345
ОС: Fedora

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение alkesta »

sdv555 писал(а):
23.04.2016 20:15
Ввожу в командной строке команду:mode2 -Hftdi -dserial=A9U9LFFR и получаю:

Код: Выделить всё

 mode2: Initializing FTDI: serial=A9U9LFFR
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK

Это все длится бесконечно и не останавливается.


нажатия кнопок пульта регистрируются в консоли, во время этой команды?
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

alkesta писал(а):
26.04.2016 12:37
sdv555 писал(а):
23.04.2016 20:15
Ввожу в командной строке команду:mode2 -Hftdi -dserial=A9U9LFFR и получаю:

Код: Выделить всё

 mode2: Initializing FTDI: serial=A9U9LFFR
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK

Это все длится бесконечно и не останавливается.


нажатия кнопок пульта регистрируются в консоли, во время этой команды?


Нет вообще никакой реакции ни на пульт ни на клавиатуру. Все тупо зависает и приходится принудительно выходить из командной строки. Отсоединять и снова подсоединять переходник к ЮСБ и только тогда все возвращается в нормальное состояние.
Спасибо сказали:
Аватара пользователя
alkesta
Сообщения: 345
ОС: Fedora

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение alkesta »

попробуй убрать все то, что ты наконфигурировал и начни с начала.

у тебя такая каша получилась. В dmesg ttyUSB1, а в железо.конф - ttyUSB0. Драйверы направо и налево разные суешь, а драйвер должен быть ftdi.

Добейся регистрации в консоли нажатий пульта. А после уже конфирурируй.
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

alkesta писал(а):
26.04.2016 14:14
попробуй убрать все то, что ты наконфигурировал и начни с начала.

у тебя такая каша получилась. В dmesg ttyUSB1, а в железо.конф - ttyUSB0. Драйверы направо и налево разные суешь, а драйвер должен быть ftdi.

Добейся регистрации в консоли нажатий пульта. А после уже конфирурируй.


Т.е. если я правильно понимаю мой ход действий следующий:
1. Полная переустановка Lirc из репов.
2. Не меняя файлов Hardware. conf и cd. conf пробую в консоле ввести эту команду :mode2 -Hftdi -dserial=A9U9LFFR и пока она выполняется, смотрю реакцию на нажатие кнопок на пульте. Если нет реакции в файл cd. conf добавляю текст файла конфигурации моего пульта и все повторяю снова.
3. В файле Hardware. conf вместо ttyUSB0 забиваю Hftdi -dserial все остальное как было ранее написано.
Поправьте если что-то неправильно.
Спасибо сказали:
Аватара пользователя
alkesta
Сообщения: 345
ОС: Fedora

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение alkesta »

Попробуй убрать все лишнее из hardware.conf, укажи только драйвер и устройство:

Код: Выделить всё

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="JVC"
REMOTE_MODULES=""
REMOTE_DRIVER="ftdi"
REMOTE_DEVICE="serial=A9U9LFFR"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF=""
REMOTE_LIRCD_ARGS=""
#Chosen IR Transmitter
TRANSMITTER="Custom"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""
#Disable kernel support.
#Typically, lirc will disable in-kernel support for ir devices in order to
#handle them internally.  Set to false to prevent lirc from disabling this
#in-kernel support.
#DISABLE_KERNEL_SUPPORT="true"
#Enable lircd
START_LIRCD="true"
#Don't start lircmd even if there seems to be a good config file
START_LIRCMD="false"
#Try to load appropriate kernel modules
#LOAD_MODULES="true"
# Default configuration files for your hardware if any
#LIRCMD_CONF="true"
#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"


сделай рестарт lirc
и пробуй в консоли нажатия
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »


alkesta писал(а):
26.04.2016 15:32
Попробуй убрать все лишнее из hardware.conf, укажи только драйвер и устройство:

Код: Выделить всё

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="JVC"
REMOTE_MODULES=""
REMOTE_DRIVER="ftdi"
REMOTE_DEVICE="serial=A9U9LFFR"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF=""
REMOTE_LIRCD_ARGS=""
#Chosen IR Transmitter
TRANSMITTER="Custom"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""
#Disable kernel support.
#Typically, lirc will disable in-kernel support for ir devices in order to
#handle them internally.  Set to false to prevent lirc from disabling this
#in-kernel support.
#DISABLE_KERNEL_SUPPORT="true"
#Enable lircd
START_LIRCD="true"
#Don't start lircmd even if there seems to be a good config file
START_LIRCMD="false"
#Try to load appropriate kernel modules
#LOAD_MODULES="true"
# Default configuration files for your hardware if any
#LIRCMD_CONF="true"
#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"


сделай рестарт lirc
и пробуй в консоли нажатия


Сделал следующие действия: 1. Переустановил Лирц при установке, когда он запрашивает устройства приема и передачи, в качестве приемника я указал FTDI R232.... приемник и Custom передатчик.
2. Открыл файл Hardware conf. и дописал строку в REMOTE_DEVICE как вы указали serial=A9U9LFFR вот текст этого файла:

Код: Выделить всё

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="FTDI FT232-based IR Receiver"
REMOTE_MODULES=""
REMOTE_DRIVER="ftdi"
REMOTE_DEVICE="serial=A9U9LFFR"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF=""
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="Custom"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

#Disable kernel support.
#Typically, lirc will disable in-kernel support for ir devices in order to
#handle them internally.  Set to false to prevent lirc from disabling this
#in-kernel support.
#DISABLE_KERNEL_SUPPORT="true"

#Enable lircd
START_LIRCD="true"

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

#Forcing noninteractive reconfiguration
#If lirc is to be reconfigured by an external application
#that doesn't have a debconf frontend available, the noninteractive
#frontend can be invoked and set to parse REMOTE and TRANSMITTER
#It will then populate all other variables without any user input
#If you would like to configure lirc via standard methods, be sure
#to leave this set to "false"
FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD=""


После этого в консоле ввожу команду:sudo service lirc start получаю

Код: Выделить всё

[sudo] password for dmitriy:
 * Loading LIRC modules                                                        [ OK ]
 * Starting remote control daemon(s) :
lircd: there seems to already be a lircd process with pid 4729
lircd: otherwise delete stale lockfile /var/run/lirc/lircd.pid
                                                                                            [fail]

Далее ввожу команду dmesg получаю ответ:

Код: Выделить всё

[    0.924130] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    0.924133] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.924136] usb usb2: Product: EHCI Host Controller
[    0.924138] usb usb2: Manufacturer: Linux 4.1.5-040105-generic ehci_hcd
[    0.924140] usb usb2: SerialNumber: 0000:00:1d.7
[    0.924317] hub 2-0:1.0: USB hub found
[    0.924326] hub 2-0:1.0: 6 ports detected
[    0.924580] ehci-platform: EHCI generic platform driver
[    0.924601] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.924609] ohci-pci: OHCI PCI platform driver
[    0.924628] ohci-platform: OHCI generic platform driver
[    0.924640] uhci_hcd: USB Universal Host Controller Interface driver
[    0.924759] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[    0.924767] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[    0.924775] uhci_hcd 0000:00:1a.0: detected 2 ports
[    0.924811] uhci_hcd 0000:00:1a.0: irq 16, io base 0x00001820
[    0.924871] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    0.924874] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.924876] usb usb3: Product: UHCI Host Controller
[    0.924878] usb usb3: Manufacturer: Linux 4.1.5-040105-generic uhci_hcd
[    0.924881] usb usb3: SerialNumber: 0000:00:1a.0
[    0.925038] hub 3-0:1.0: USB hub found
[    0.925047] hub 3-0:1.0: 2 ports detected
[    0.925268] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[    0.925275] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
[    0.925284] uhci_hcd 0000:00:1a.1: detected 2 ports
[    0.925316] uhci_hcd 0000:00:1a.1: irq 21, io base 0x00001840
[    0.925375] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    0.925378] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.925380] usb usb4: Product: UHCI Host Controller
[    0.925383] usb usb4: Manufacturer: Linux 4.1.5-040105-generic uhci_hcd
[    0.925385] usb usb4: SerialNumber: 0000:00:1a.1
[    0.925547] hub 4-0:1.0: USB hub found
[    0.925555] hub 4-0:1.0: 2 ports detected
[    0.925782] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[    0.925790] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
[    0.925798] uhci_hcd 0000:00:1a.2: detected 2 ports
[    0.925822] uhci_hcd 0000:00:1a.2: irq 19, io base 0x00001860
[    0.925881] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[    0.925884] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.925886] usb usb5: Product: UHCI Host Controller
[    0.925889] usb usb5: Manufacturer: Linux 4.1.5-040105-generic uhci_hcd
[    0.925891] usb usb5: SerialNumber: 0000:00:1a.2
[    0.926052] hub 5-0:1.0: USB hub found
[    0.926060] hub 5-0:1.0: 2 ports detected
[    0.926276] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[    0.926286] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
[    0.926295] uhci_hcd 0000:00:1d.0: detected 2 ports
[    0.926318] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001880
[    0.926378] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[    0.926381] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.926383] usb usb6: Product: UHCI Host Controller
[    0.926386] usb usb6: Manufacturer: Linux 4.1.5-040105-generic uhci_hcd
[    0.926388] usb usb6: SerialNumber: 0000:00:1d.0
[    0.926554] hub 6-0:1.0: USB hub found
[    0.926562] hub 6-0:1.0: 2 ports detected
[    0.926779] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[    0.926788] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
[    0.926798] uhci_hcd 0000:00:1d.1: detected 2 ports
[    0.926822] uhci_hcd 0000:00:1d.1: irq 19, io base 0x000018a0
[    0.926882] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
[    0.926885] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.926887] usb usb7: Product: UHCI Host Controller
[    0.926890] usb usb7: Manufacturer: Linux 4.1.5-040105-generic uhci_hcd
[    0.926892] usb usb7: SerialNumber: 0000:00:1d.1
[    0.927051] hub 7-0:1.0: USB hub found
[    0.927059] hub 7-0:1.0: 2 ports detected
[    0.927286] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    0.927294] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
[    0.927302] uhci_hcd 0000:00:1d.2: detected 2 ports
[    0.927336] uhci_hcd 0000:00:1d.2: irq 18, io base 0x000018c0
[    0.927396] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
[    0.927399] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.927401] usb usb8: Product: UHCI Host Controller
[    0.927404] usb usb8: Manufacturer: Linux 4.1.5-040105-generic uhci_hcd
[    0.927406] usb usb8: SerialNumber: 0000:00:1d.2
[    0.927562] hub 8-0:1.0: USB hub found
[    0.927571] hub 8-0:1.0: 2 ports detected
[    0.927773] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PSM1] at 0x60,0x64 irq 1,12
[    0.931406] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.931412] serio: i8042 AUX port at 0x60,0x64 irq 12
[    0.931635] mousedev: PS/2 mouse device common for all mice
[    0.932165] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[    0.932201] rtc_cmos 00:03: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[    0.932233] i2c /dev entries driver
[    0.932317] device-mapper: uevent: version 1.0.3
[    0.932428] device-mapper: ioctl: 4.31.0-ioctl (2015-3-12) initialised: dm-devel@redhat.com
[    0.932453] ledtrig-cpu: registered to indicate activity on CPUs
[    0.932673] PCCT header not found.
[    0.932955] NET: Registered protocol family 10
[    0.933265] NET: Registered protocol family 17
[    0.933282] Key type dns_resolver registered
[    0.933729] Loading compiled-in X.509 certificates
[    0.934970] Loaded X.509 cert 'Build time autogenerated kernel key: 46fd0f30f3bd8f146803e982177aac2d077a899c'
[    0.934990] registered taskstats version 1
[    0.937787] Key type trusted registered
[    0.942747] Key type encrypted registered
[    0.942759] AppArmor: AppArmor sha1 policy hashing enabled
[    0.942763] ima: No TPM chip found, activating TPM-bypass!
[    0.942793] evm: HMAC attrs: 0x1
[    0.943281]   Magic number: 12:873:793
[    0.943440] rtc_cmos 00:03: setting system clock to 2016-04-26 16:46:18 UTC (1461689178)
[    0.943546] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    0.943548] EDD information not available.
[    0.943647] PM: Hibernation image not present or could not be loaded.
[    0.944376] Freeing unused kernel memory: 1424K (ffffffff81d38000 - ffffffff81e9c000)
[    0.944381] Write protecting the kernel read-only data: 12288k
[    0.944690] Freeing unused kernel memory: 124K (ffff8800017e1000 - ffff880001800000)
[    0.944968] Freeing unused kernel memory: 316K (ffff880001bb1000 - ffff880001c00000)
[    0.963566] systemd-udevd[104]: starting version 204
[    0.965586] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
[    0.996362] [drm] Initialized drm 1.1.0 20060810
[    1.025027] sky2: driver version 1.30
[    1.025339] sky2 0000:04:00.0: Yukon-2 FE+ chip revision 0
[    1.026532] sky2 0000:04:00.0 eth0: addr 00:24:54:c4:a6:db
[    1.027351] [drm] Memory usable by graphics device = 2048M
[    1.027357] checking generic (d0000000 300000) vs hw (d0000000 10000000)
[    1.027359] fb: switching to inteldrmfb from VESA VGA
[    1.027390] Console: switching to colour dummy device 80x25
[    1.027527] [drm] Replacing VGA console driver
[    1.035605] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.035609] [drm] Driver supports precise vblank timestamp query.
[    1.035695] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    1.114274] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    1.114481] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input7
[    1.114621] [drm] Initialized i915 1.6.0 20150327 for 0000:00:02.0 on minor 0
[    1.114668] ahci 0000:00:1f.2: version 3.0
[    1.114898] ahci 0000:00:1f.2: SSS flag set, parallel bus scan disabled
[    1.114944] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 3 Gbps 0x33 impl SATA mode
[    1.114948] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part ccc ems sxs
[    1.140081] scsi host0: ahci
[    1.140510] scsi host1: ahci
[    1.140673] scsi host2: ahci
[    1.140836] scsi host3: ahci
[    1.140992] scsi host4: ahci
[    1.141133] scsi host5: ahci
[    1.141216] ata1: SATA max UDMA/133 abar m2048@0xfc704000 port 0xfc704100 irq 29
[    1.141220] ata2: SATA max UDMA/133 abar m2048@0xfc704000 port 0xfc704180 irq 29
[    1.141221] ata3: DUMMY
[    1.141223] ata4: DUMMY
[    1.141226] ata5: SATA max UDMA/133 abar m2048@0xfc704000 port 0xfc704300 irq 29
[    1.141229] ata6: SATA max UDMA/133 abar m2048@0xfc704000 port 0xfc704380 irq 29
[    1.236088] usb 2-1: new high-speed USB device number 2 using ehci-pci
[    1.257393] fbcon: inteldrmfb (fb0) is primary device
[    1.276096] usb 1-4: new high-speed USB device number 3 using ehci-pci
[    1.364054] usb 3-1: new low-speed USB device number 2 using uhci_hcd
[    1.381341] usb 2-1: New USB device found, idVendor=1c9e, idProduct=9605
[    1.381343] usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[    1.381345] usb 2-1: Product: Modem Configuration
[    1.381346] usb 2-1: Manufacturer: USB Modem
[    1.381348] usb 2-1: SerialNumber: 1234567890ABCDEF
[    1.422978] usb 1-4: New USB device found, idVendor=0ac8, idProduct=c33f
[    1.422980] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.422982] usb 1-4: Product: WebCam SCB-0340N
[    1.422983] usb 1-4: Manufacturer: Namuga.
[    1.450676] usb-storage 2-1:1.4: USB Mass Storage device detected
[    1.451138] scsi host6: usb-storage 2-1:1.4
[    1.451265] usbcore: registered new interface driver usb-storage
[    1.453286] usbcore: registered new interface driver uas
[    1.460058] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.465930] ata1.00: ATA-8: SAMSUNG HM321HI, 2AJ10002, max UDMA/133
[    1.465932] ata1.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    1.471851] ata1.00: configured for UDMA/133
[    1.538139] usb 3-1: New USB device found, idVendor=09da, idProduct=000a
[    1.538141] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.538143] usb 3-1: Product: PS/2+USB Mouse
[    1.538144] usb 3-1: Manufacturer: A4Tech
[    1.555292] hidraw: raw HID events driver (C) Jiri Kosina
[    1.556067] usb 2-3: new high-speed USB device number 3 using ehci-pci
[    1.570234] usbcore: registered new interface driver usbhid
[    1.570235] usbhid: USB HID core driver
[    1.572561] input: A4Tech PS/2+USB Mouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/0003:09DA:000A.0001/input/input8
[    1.572757] a4tech 0003:09DA:000A.0001: input,hidraw0: USB HID v1.10 Mouse [A4Tech PS/2+USB Mouse] on usb-0000:00:1a.0-1/input0
[    1.689468] usb 2-3: New USB device found, idVendor=05e3, idProduct=0608
[    1.689470] usb 2-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.689472] usb 2-3: Product: USB2.0 Hub
[    1.689903] hub 2-3:1.0: USB hub found
[    1.690211] hub 2-3:1.0: 4 ports detected
[    1.820041] clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x1e31bf07a96, max_idle_ns: 440795208811 ns
[    1.890762] psmouse serio1: elantech: assuming hardware version 2 (with firmware version 0x040215)
[    1.927325] psmouse serio1: elantech: Synaptics capabilities query result 0x08, 0x14, 0x0c.
[    1.960051] usb 2-3.1: new full-speed USB device number 4 using ehci-pci
[    2.068103] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6
[    2.104136] Console: switching to colour frame buffer device 170x48
[    2.107347] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    2.107349] i915 0000:00:02.0: registered panic notifier
[    2.108246] scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HM321HI  0002 PQ: 0 ANSI: 5
[    2.108599] sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[    2.108609] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    2.108646] sd 0:0:0:0: [sda] Write Protect is off
[    2.108650] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.108672] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.259224]  sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 >
[    2.260256] sd 0:0:0:0: [sda] Attached SCSI disk
[    2.428075] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    2.429922] ata2.00: ATAPI: TSSTcorp CDDVDW TS-L633J, SC00, max UDMA/100
[    2.430519] ata2.00: configured for UDMA/100
[    2.432216] scsi 1:0:0:0: CD-ROM            TSSTcorp CDDVDW TS-L633J  SC00 PQ: 0 ANSI: 5
[    2.434604] usb 2-3.1: New USB device found, idVendor=0403, idProduct=6001
[    2.434607] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.434609] usb 2-3.1: Product: FT232R USB UART
[    2.434612] usb 2-3.1: Manufacturer: FTDI
[    2.434614] usb 2-3.1: SerialNumber: A9U9LFFR
[    2.451485] scsi 6:0:0:0: Direct-Access     USBModem Disk             2.31 PQ: 0 ANSI: 2
[    2.451828] sd 6:0:0:0: Attached scsi generic sg1 type 0
[    2.455977] sr 1:0:0:0: [sr0] scsi3-mmc drive: 16x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[    2.455982] cdrom: Uniform CD-ROM driver Revision: 3.20
[    2.456253] sr 1:0:0:0: Attached scsi CD-ROM sr0
[    2.456358] sr 1:0:0:0: Attached scsi generic sg2 type 5
[    2.456503] sd 6:0:0:0: [sdb] 3805184 512-byte logical blocks: (1.94 GB/1.81 GiB)
[    2.459478] sd 6:0:0:0: [sdb] Write Protect is off
[    2.459487] sd 6:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[    2.462458] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.482274]  sdb: sdb1
[    2.501094] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[    2.784039] ata5: SATA link down (SStatus 0 SControl 300)
[    2.846707] random: nonblocking pool is initialized
[    3.104038] ata6: SATA link down (SStatus 0 SControl 300)
[    5.562083] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    7.057799] init: ureadahead main process (278) terminated with status 5
[    8.592467] Adding 976556k swap on /dev/sda8.  Priority:-1 extents:1 across:976556k FS
[   10.123138] systemd-udevd[393]: starting version 204
[   11.652985] usbcore: registered new interface driver usbserial
[   11.653005] usbcore: registered new interface driver usbserial_generic
[   11.653032] usbserial: USB Serial support registered for generic
[   12.022698] lp: driver loaded but no devices found
[   12.098614] ppdev: user-space parallel port driver
[   13.812491] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   13.921116] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
[   13.921126] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   13.921131] ACPI Warning: SystemIO range 0x00000000000011B0-0x00000000000011BF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\GPIO) (20150410/utaddress-254)
[   13.921135] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   13.921137] ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\GPIO) (20150410/utaddress-254)
[   13.921141] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   13.921143] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   14.403437] cfg80211: Calling CRDA to update world regulatory domain
[   14.491973] device-mapper: multipath: version 1.9.0 loaded
[   14.815016] ath: phy0: Enable LNA combining
[   14.817694] ath: phy0: ASPM enabled: 0x42
[   14.817697] ath: EEPROM regdomain: 0x65
[   14.817699] ath: EEPROM indicates we should expect a direct regpair map
[   14.817702] ath: Country alpha2 being used: 00
[   14.817703] ath: Regpair used: 0x65
[   14.988513] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   14.989178] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc900007e0000, irq=17
[   14.999732] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC269VB: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   14.999738] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   14.999741] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[   14.999743] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[   14.999745] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[   14.999748] snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x19
[   14.999751] snd_hda_codec_realtek hdaudioC0D0:      Mic=0x18
[   15.007351] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[   15.007498] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[   15.260301] usbcore: registered new interface driver option
[   15.260325] usbserial: USB Serial support registered for GSM modem (1-port)
[   15.260481] option 2-1:1.0: GSM modem (1-port) converter detected
[   15.260614] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
[   15.260675] option 2-1:1.1: GSM modem (1-port) converter detected
[   15.260773] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[   15.260824] option 2-1:1.2: GSM modem (1-port) converter detected
[   15.260914] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
[   15.260965] option 2-1:1.3: GSM modem (1-port) converter detected
[   15.261062] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3
[   15.266243] usbcore: registered new interface driver ftdi_sio
[   15.266270] usbserial: USB Serial support registered for FTDI USB Serial Device
[   15.266424] ftdi_sio 2-3.1:1.0: FTDI USB Serial Device converter detected
[   15.266490] usb 2-3.1: Detected FT232RL
[   15.267211] usb 2-3.1: FTDI USB Serial Device converter now attached to ttyUSB4
[   15.306993] media: Linux media interface: v0.10
[   15.360104] Linux video capture interface: v2.00
[   15.522610] samsung_laptop: enabled workaround for brightness stepping quirk
[   15.523951] samsung_laptop: detected SABI interface: SwSmi@
[   15.681846] uvcvideo: Found UVC 1.00 device WebCam SCB-0340N (0ac8:c33f)
[   15.683955] input: WebCam SCB-0340N as /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.0/input/input11
[   15.684105] usbcore: registered new interface driver uvcvideo
[   15.684108] USB Video Class driver (1.1.1)
[   16.953926] cfg80211: World regulatory domain updated:
[   16.953931] cfg80211:  DFS Master region: unset
[   16.953933] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   16.953936] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   16.953939] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   16.953941] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[   16.953944] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   16.953946] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   21.333124] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   24.907894] EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: (null)
[   25.557720] EXT4-fs (sda13): mounted filesystem with ordered data mode. Opts: (null)
[   26.313032] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[   26.422829] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[   26.640187] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[   26.746612] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[   28.038382] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[   28.916789] init: failsafe main process (921) killed by TERM signal
[   35.783700] Bluetooth: Core ver 2.20
[   35.783728] NET: Registered protocol family 31
[   35.783730] Bluetooth: HCI device and connection manager initialized
[   35.783737] Bluetooth: HCI socket layer initialized
[   35.783741] Bluetooth: L2CAP socket layer initialized
[   35.783761] Bluetooth: SCO socket layer initialized
[   35.872435] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   35.872440] Bluetooth: BNEP filters: protocol multicast
[   35.872446] Bluetooth: BNEP socket layer initialized
[   35.910178] Bluetooth: RFCOMM TTY layer initialized
[   35.910195] Bluetooth: RFCOMM socket layer initialized
[   35.910208] Bluetooth: RFCOMM ver 1.11
[   36.181607] init: cups main process (1176) killed by HUP signal
[   36.181627] init: cups main process ended, respawning
[   41.806375] init: samba-ad-dc main process (1363) terminated with status 1
[   42.320767] init: plymouth-upstart-bridge main process ended, respawning
[   42.330328] init: plymouth-upstart-bridge main process (1411) terminated with status 1
[   42.330348] init: plymouth-upstart-bridge main process ended, respawning
[   43.518873] sky2 0000:04:00.0 eth0: enabling interface
[   43.519363] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   43.541427] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   57.640152] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[   57.645185] vboxdrv: Found 2 processor cores
[   57.646822] vboxdrv: fAsync=0 offMin=0x1c3 offMax=0x34f3
[   57.747043] vboxdrv: TSC mode is Synchronous, tentative frequency 2094748327 Hz
[   57.747046] vboxdrv: Successfully loaded version 5.0.12 (interface 0x00240000)
[   57.969805] VBoxNetFlt: Successfully started.
[   58.302866] VBoxNetAdp: Successfully started.
[   58.339500] VBoxPciLinuxInit
[   58.481985] vboxpci: IOMMU not found (not registered)
[   59.734509] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.734525] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.734635] pci_bus 0000:08: Allocating resources
[   59.734650] pci 0000:00:1e.0: bridge window [io  0x1000-0x0fff] to [bus 08] add_size 1000
[   59.734655] pci 0000:00:1e.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 08] add_size 200000 add_align 100000
[   59.734658] pci 0000:00:1e.0: bridge window [mem 0x00100000-0x000fffff] to [bus 08] add_size 200000 add_align 100000
[   59.734661] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.734668] pci 0000:00:1e.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
[   59.734671] pci 0000:00:1e.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
[   59.734674] pci 0000:00:1e.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
[   59.734677] pci 0000:00:1e.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
[   59.734680] pci 0000:00:1e.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[   59.734683] pci 0000:00:1e.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
[   59.734690] pci 0000:00:1e.0: BAR 14: assigned [mem 0xc0100000-0xc02fffff]
[   59.734697] pci 0000:00:1e.0: BAR 15: assigned [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.734703] pci 0000:00:1e.0: BAR 13: assigned [io  0x6000-0x6fff]
[   59.734707] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.734711] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.734718] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.734723] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.735315] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.735330] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.735335] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.735343] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.735349] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.735517] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.735525] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.735529] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.735536] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.735542] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.735686] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.735694] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.735698] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.735705] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.735710] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.735737] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.735741] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.735745] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.735752] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.735757] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.735928] pci_bus 0000:02: Allocating resources
[   59.735948] pci_bus 0000:04: Allocating resources
[   59.735987] pci_bus 0000:06: Allocating resources
[   59.736051] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.736060] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.736067] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.736077] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.736086] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   68.520841] init: plymouth-stop pre-start process (2257) terminated with status 1
[   93.026307] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   93.150231] Netfilter messages via NETLINK v0.30.
[   93.158670] ctnetlink v0.93: registering with nfnetlink.
[   93.228494] ip_tables: (C) 2000-2006 Netfilter Core Team
[  126.954212] NET: Registered protocol family 23
[  151.967900] wlan0: authenticate with 18:62:2c:bc:2c:31
[  151.988181] wlan0: send auth to 18:62:2c:bc:2c:31 (try 1/3)
[  151.990230] wlan0: authenticated
[  151.996076] wlan0: associate with 18:62:2c:bc:2c:31 (try 1/3)
[  152.000451] wlan0: RX AssocResp from 18:62:2c:bc:2c:31 (capab=0x411 status=0 aid=2)
[  152.000561] wlan0: associated
[  152.000610] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  153.015810] perf interrupt took too long (2516 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[  159.063589] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[  160.093475] wlan0: deauthenticated from 18:62:2c:bc:2c:31 (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
[  160.160658] cfg80211: Calling CRDA to update world regulatory domain
[  160.169124] cfg80211: World regulatory domain updated:
[  160.169133] cfg80211:  DFS Master region: unset
[  160.169135] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[  160.169138] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[  160.169141] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[  160.169145] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[  160.169147] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[  160.169150] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[  165.136656] systemd-hostnamed[3507]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[  177.826196] PPP BSD Compression module registered
[  177.878613] PPP Deflate Compression module registered
[  183.807972] traps: mate-notificati[3447] trap int3 ip:7fad55f71c13 sp:7fff679fe250 error:0
[  381.140982] CE: hpet increased min_delta_ns to 20115 nsec
[  658.720854] ftdi_sio ttyUSB4: FTDI USB Serial Device converter now disconnected from ttyUSB4
[  658.720873] ftdi_sio 2-3.1:1.0: device disconnected
[  761.596210] usb usb2-port3: disabled by hub (EMI?), re-enabling...
[  761.596224] usb 2-3: USB disconnect, device number 3
[  761.596227] usb 2-3.1: USB disconnect, device number 4
[  764.000054] usb 2-3: new high-speed USB device number 5 using ehci-pci
[  764.133500] usb 2-3: New USB device found, idVendor=05e3, idProduct=0608
[  764.133509] usb 2-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[  764.133512] usb 2-3: Product: USB2.0 Hub
[  764.134288] hub 2-3:1.0: USB hub found
[  764.135264] hub 2-3:1.0: 4 ports detected
[  764.408064] usb 2-3.1: new full-speed USB device number 6 using ehci-pci
[  764.882901] usb 2-3.1: New USB device found, idVendor=0403, idProduct=6001
[  764.882907] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  764.882909] usb 2-3.1: Product: FT232R USB UART
[  764.882917] usb 2-3.1: Manufacturer: FTDI
[  764.882919] usb 2-3.1: SerialNumber: A9U9LFFR
[  764.930230] ftdi_sio 2-3.1:1.0: FTDI USB Serial Device converter detected
[  764.930287] usb 2-3.1: Detected FT232RL
[  764.930904] usb 2-3.1: FTDI USB Serial Device converter now attached to ttyUSB4
[  765.669111] ftdi_sio ttyUSB4: FTDI USB Serial Device converter now disconnected from ttyUSB4
[  765.669133] ftdi_sio 2-3.1:1.0: device disconnected
[  988.394385] usb 2-1: USB disconnect, device number 2
[  988.394640] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[  988.394666] option 2-1:1.0: device disconnected
[  988.394821] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  988.394826] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  988.394829] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  988.394835] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  988.395568] option1 ttyUSB3: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  988.396755] option1 ttyUSB3: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  988.398029] option1 ttyUSB3: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  988.398744] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[  988.398786] option 2-1:1.1: device disconnected
[  988.399276] option1 ttyUSB3: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  988.399289] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[  988.399318] option 2-1:1.2: device disconnected
[  988.402776] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[  988.402795] option 2-1:1.3: device disconnected
[  988.407111] sd 6:0:0:0: [sdb] Synchronizing SCSI cache
[  988.407370] sd 6:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  993.924075] usb 2-1: new high-speed USB device number 7 using ehci-pci
[  994.069330] usb 2-1: New USB device found, idVendor=1c9e, idProduct=f000
[  994.069338] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[  994.069341] usb 2-1: Product: USB Modem
[  994.069344] usb 2-1: Manufacturer: USB Modem
[  994.069346] usb 2-1: SerialNumber: 000000000000
[  994.073692] usb-storage 2-1:1.0: USB Mass Storage device detected
[  994.073886] scsi host7: usb-storage 2-1:1.0
[  995.075519] scsi 7:0:0:0: CD-ROM            USBModem Disk             2.31 PQ: 0 ANSI: 2
[  995.086519] sr 7:0:0:0: [sr1] scsi-1 drive
[  995.088363] sr 7:0:0:0: Attached scsi CD-ROM sr1
[  995.088522] sr 7:0:0:0: Attached scsi generic sg1 type 5
[  997.690677] usb 2-1: USB disconnect, device number 7
[  998.060092] usb 2-1: new high-speed USB device number 8 using ehci-pci
[  998.205453] usb 2-1: New USB device found, idVendor=1c9e, idProduct=9605
[  998.205462] usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[  998.205465] usb 2-1: Product: Modem Configuration
[  998.205467] usb 2-1: Manufacturer: USB Modem
[  998.205470] usb 2-1: SerialNumber: 1234567890ABCDEF
[  998.271724] option 2-1:1.0: GSM modem (1-port) converter detected
[  998.271860] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
[  998.271996] option 2-1:1.1: GSM modem (1-port) converter detected
[  998.272176] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[  998.272321] option 2-1:1.2: GSM modem (1-port) converter detected
[  998.272430] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
[  998.272559] option 2-1:1.3: GSM modem (1-port) converter detected
[  998.272664] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3
[  998.272788] usb-storage 2-1:1.4: USB Mass Storage device detected
[  998.272929] scsi host8: usb-storage 2-1:1.4
[ 1003.372614] scsi 8:0:0:0: Direct-Access     USBModem Disk             2.31 PQ: 0 ANSI: 2
[ 1003.373015] sd 8:0:0:0: Attached scsi generic sg1 type 0
[ 1003.377625] sd 8:0:0:0: [sdb] 3805184 512-byte logical blocks: (1.94 GB/1.81 GiB)
[ 1003.380749] sd 8:0:0:0: [sdb] Write Protect is off
[ 1003.380760] sd 8:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[ 1003.384584] sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1003.403662]  sdb: sdb1
[ 1003.423381] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 1004.624470] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 1056.130342] traps: mate-notificati[5225] trap int3 ip:7f5e600fcc13 sp:7ffe63050660 error:0
[ 1060.952389] perf interrupt took too long (5002 > 5000), lowering kernel.perf_event_max_sample_rate to 25000

Ввожу команду mode2 -Hftdi -dserial=A9U9LFFR и получаю ответ опять сплошное зацикливание команды и никакой реакции на кнопки пульта

Код: Выделить всё

mode2: Initializing FTDI: serial=A9U9LFFR
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK
mode2: opened FTDI device 'serial=A9U9LFFR' OK

Следующий этап добавляю в lircd. conf текст конфигурационного файла моего пульта и ввожу команду в консоле sudo service lirc restart получаю ответ:

Код: Выделить всё

 * Stopping remote control daemon(s): LIRC              [ OK ]
 * Loading LIRC modules                                                  [ OK ]
 * Starting remote control daemon(s) :                              [ OK ]

Это ответ на команду sudo cat /etc/init.d/lirc:

Код: Выделить всё

#! /bin/sh
### BEGIN INIT INFO
# Provides:          lirc
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Starts LIRC daemon.
# Description:       LIRC is used to control different
#                    infrared receivers and transceivers.
### END INIT INFO

load_modules ()
{
    MODULES_MISSING=false

    log_daemon_msg "Loading LIRC modules"
    for mod in $*; do
        if [ $mod = "udev" ]; then
            log_end_msg 0
            log_success_msg "Restarted via udev, don't reload modules"
            break
        else
            modprobe $mod 2> /dev/null || MODULES_MISSING=true
        fi
    done
    log_end_msg $?

    if $MODULES_MISSING; then
        log_failure_msg "Unable to load LIRC kernel modules. Verify your"
        log_failure_msg "selected kernel modules in /etc/lirc/hardware.conf"
        START_LIRCMD=false
        START_LIRCD=false
    fi
}

build_remote_args ()
{
    REMOTE_ARGS="$*"

    #For remote only detection support, we need
    #both REMOTE_DEVICE and TRANSMITTER_DEVICE undefined
    if [ -z "$REMOTE_DEVICE" ] && [ -z "$TRANSMITTER_DEVICE" ] && [ -c $dev ]; then
        REMOTE_DEVICE="$dev"
    fi

    #If we have a REMOTE_DEVICE or REMOTE_DRIVER defined (either because no devices
    #were defined, OR if we explicitly did), then populate REMOTE_ARGS
    if [ -n "$REMOTE_DEVICE" ] || [ -n "$REMOTE_DRIVER" ]; then
        if [ -n "$REMOTE_DEVICE" ] && [ "$REMOTE_DEVICE" != "none" ]; then
            REMOTE_ARGS="--device=$REMOTE_DEVICE $REMOTE_ARGS"
        fi
        if [ -n "$REMOTE_DRIVER" ] && [ "$REMOTE_DRIVER" != "none" ]; then
            REMOTE_ARGS="--driver=$REMOTE_DRIVER $REMOTE_ARGS"
        fi

        #Now, if we ALSO have a transmitter defined, add some args
        #To make the first lircd listen up
        if [ -n "$TRANSMITTER_DEVICE" ] || [ -n "$TRANSMITTER_DRIVER" ]; then
            REMOTE_ARGS="$REMOTE_ARGS --connect=localhost:8765"
        fi
        REMOTE_ARGS="--output=$REMOTE_SOCKET $REMOTE_ARGS"
    fi
    REMOTE_PID="--pidfile=/run/lirc/lircd.pid"
    echo $REMOTE_ARGS
}

build_transmitter_args ()
{
    TRANSMITTER_ARGS="$*"

    #Transmitters must be explicitly be defined
    if [ -n "$TRANSMITTER_DEVICE" ] || [ -n "$TRANSMITTER_DRIVER" ]; then
        if [ -n "$TRANSMITTER_DEVICE" ] && [ "$TRANSMITTER_DEVICE" != "none" ]; then
            TRANSMITTER_ARGS="--device=$TRANSMITTER_DEVICE $TRANSMITTER_ARGS"
        fi
        if [ -n "$TRANSMITTER_DRIVER" ] && [ "$TRANSMITTER_DRIVER" != "none" ]; then
            TRANSMITTER_ARGS="--driver=$TRANSMITTER_DRIVER $TRANSMITTER_ARGS"
        fi

        #Now, if we ALSO have a remote defined, add some args
        #To make the second lircd connect
        if [ -n "$REMOTE_DEVICE" ] || [ -n "$REMOTE_DRIVER" ]; then
            TRANSMITTER_ARGS="$TRANSMITTER_ARGS --listen --pidfile=/run/lirc/lircd1.pid"
            TRANSMITTER_PID="--pidfile=/run/lirc/lircd1.pid"
        else
            TRANSMITTER_PID="--pidfile=/run/lirc/lircd.pid"
        fi
        TRANSMITTER_ARGS="--output=$TRANSMITTER_SOCKET $TRANSMITTER_ARGS"
    fi
    echo $TRANSMITTER_ARGS
}

in_kernel_support() {
    if [ -d /sys/class/rc ] && [ "$DISABLE_KERNEL_SUPPORT" = "true" ]; then
        for file in `find /sys/class/rc/*/ -name protocols`; do
            if [ "$1" = "disable" ]; then
                echo "lirc" > $file
            else
                echo "none" > $file
                for protocol in `cat $file`; do
                    echo "+${protocol}" > $file
                done
            fi
        done
    fi
}
. /lib/lsb/init-functions

test -f /usr/sbin/lircd || exit 0
test -f /usr/sbin/lircmd || exit 0

START_LIRCMD=true
START_LIRCD=true
START_IREXEC=true
DISABLE_KERNEL_SUPPORT=true


if [ -f /etc/lirc/hardware.conf ];then
    . /etc/lirc/hardware.conf
fi

if [ ! -f /etc/lirc/lircd.conf ] || grep -q "^#UNCONFIGURED" /etc/lirc/lircd.conf; then
    if [ "$1" = "start" ]; then
        log_success_msg "No valid /etc/lirc/lircd.conf has been found."
        log_success_msg "Remote control support has been disabled."
        log_success_msg "Reconfigure LIRC or manually replace /etc/lirc/lircd.conf to enable."
    fi

    START_LIRCD=false
    START_LIRCMD=false
    START_IREXEC=false
fi

if [ ! -f /etc/lirc/lircmd.conf ] || grep -q "^#UNCONFIGURED" /etc/lirc/lircmd.conf; then
    START_LIRCMD=false
fi

if [ ! -f /etc/lirc/lircrc ] || grep -q "^#UNCONFIGURED" /etc/lirc/lircrc; then
    START_IREXEC=false
fi

#We need default socket locations
OLD_SOCKET="/dev/lircd"
if [ -z "$REMOTE_SOCKET" ]; then
    REMOTE_SOCKET="/run/lirc/lircd"
fi
if [ -z "$TRANSMITTER_SOCKET" ]; then
    TRANSMITTER_SOCKET="/run/lirc/lircd"
    #Now, if we ALSO have a remote defined,
    #change the default transmitter socket
    if [ -n "$REMOTE_DEVICE" ] || [ -n "$REMOTE_DRIVER" ]; then
        TRANSMITTER_SOCKET="${TRANSMITTER_SOCKET}1"
    fi
fi

case "$1" in
    start)
        if [ "$LOAD_MODULES" = "true" ] && [ "$START_LIRCD" = "true" ]; then
            load_modules $2 $REMOTE_MODULES $TRANSMITTER_MODULES $MODULES
            in_kernel_support "disable"
        fi

        if [ "$START_LIRCD" = "true" ]; then
            mkdir -p "/run/lirc"
            log_daemon_msg "Starting remote control daemon(s) : "
            REMOTE_LIRCD_ARGS=`build_remote_args $REMOTE_LIRCD_ARGS`
            TRANSMITTER_LIRCD_ARGS=`build_transmitter_args $TRANSMITTER_LIRCD_ARGS`

            RES=1
            #if we have a transmitter defined, start it first
            if [ -n "$TRANSMITTER_LIRCD_ARGS" ]; then
                log_progress_msg "LIRC (transmitter)"
                start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/lircd --pidfile=$TRANSMITTER_PID -- $TRANSMITTER_LIRCD_ARGS < /dev/null
                RES=$?
            fi
            if [ -n "$REMOTE_LIRCD_ARGS" ]; then
                log_progress_msg "LIRC (remote)"
                start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/lircd --pidfile=$REMOTE_PID -- $REMOTE_LIRCD_ARGS < /dev/null
                RES=$?
            fi
            log_end_msg $RES

            #Set up symlinks, starting with the remote if present.
            if [ -n "$REMOTE_LIRCD_ARGS" ]; then
                if [ -S "$REMOTE_SOCKET" -a "$OLD_SOCKET" != "$REMOTE_SOCKET" ]; then
                    rm -f $OLD_SOCKET && ln -s $REMOTE_SOCKET $OLD_SOCKET
                fi
                if [ -n "$TRANSMITTER_LIRCD_ARGS" ]; then
                    if [ -S "$TRANSMITTER_SOCKET" ]; then
                        rm -f ${OLD_SOCKET}1 && ln -s $TRANSMITTER_SOCKET ${OLD_SOCKET}1
                    fi
                fi
            elif [ -n "$TRANSMITTER_LIRCD_ARGS" ]; then
                if [ -S "$TRANSMITTER_SOCKET" -a "$OLD_SOCKET" != "$TRANSMITTER_SOCKET" ]; then
                    rm -f $OLD_SOCKET && ln -s $TRANSMITTER_SOCKET $OLD_SOCKET
                fi
            fi
        fi

        if [ "$START_LIRCMD" = "true" ]; then
            mkdir -p "/run/lirc"
            log_daemon_msg "Starting remote control mouse daemon : LIRCMD "
            start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/lircmd < /dev/null
            log_end_msg $?
        fi

        if [ "$START_IREXEC" = "true" ]; then
            mkdir -p "/run/lirc"
            log_daemon_msg "Starting execution daemon: irexec"
            start-stop-daemon --start --quiet --oknodo --exec /usr/bin/irexec -- -d /etc/lirc/lircrc < /dev/null
            log_end_msg $?
        fi
        ;;
    stop)
        in_kernel_support "enable"
        if [ "$START_IREXEC" = "true" ]; then
            log_daemon_msg "Stopping execution daemon: irexec"
            start-stop-daemon --stop --oknodo --quiet --exec /usr/bin/irexec
            log_end_msg $?
        fi

        if [ "$START_LIRCMD" = "true" ]; then
            log_daemon_msg "Stopping remote control mouse daemon: LIRCMD"
            start-stop-daemon --stop --oknodo --quiet --exec /usr/sbin/lircmd
            log_end_msg $?
        fi

        if [ "$START_LIRCD" = "true" ]; then
            log_daemon_msg "Stopping remote control daemon(s): LIRC"
            start-stop-daemon --stop --oknodo --quiet --exec /usr/sbin/lircd --pidfile /run/lirc/lircd.pid
            start-stop-daemon --stop --oknodo --quiet --exec /usr/sbin/lircd --pidfile /run/lirc/lircd1.pid
            log_end_msg $?
            [ -h "$OLD_SOCKET" ] && rm -f $OLD_SOCKET
            [ -h "${OLD_SOCKET}1" ] && rm -f ${OLD_SOCKET}1
        fi
        ;;
    reload|force-reload)
        if [ "$START_IREXEC" = "true" ]; then
            start-stop-daemon --stop --quiet --signal 1 --exec /usr/bin/irexec
        fi

        if [ "$START_LIRCD" = "true" ]; then
            start-stop-daemon --stop --quiet --signal 1 --exec /usr/sbin/lircd
        fi

        if [ "$START_LIRCMD" = "true" ]; then
            start-stop-daemon --stop --quiet --signal 1 --exec /usr/sbin/lircmd
        fi
        ;;
    restart)
        $0 stop
        #passes parameter $2 which is possibly our udev paramater
        $0 start $2
        ;;
    *)
        echo "Usage: /etc/init.d/lircd {start|stop|reload|restart|force-reload}"
    exit 1
esac

exit 0

Ввод строки mode2 -Hftdi -dserial=A9U9LFFR приводит только зацикливанию и никакой реакции на пульт нет. Также нет реакции и в утилите irw на пульт и у самого переходника нет при этом связи с девайсом все тупо зависает.
Спасибо сказали:
Аватара пользователя
alkesta
Сообщения: 345
ОС: Fedora

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение alkesta »

в ~/.cache/mode2.log что-то есть?

для общего понимания, тебе нужно эту часть сделать:

Код: Выделить всё

Basic setup flow
------------
|  remote  |
------------
(air gap)
------------
! capture  !
! device   !
------------
     |
     v
     |
------------
! kernel   !                   Sometimes needs
! driver   !                   modprobe(1) configuration.
------------
     |
     v       IR pulse data
     |
------------
|  lirc    |                   Configure hardware.conf
|  driver  |                   with driver and usually also device.
------------
     |
     v        IR pulse data          Use mode2(1) to debug


а потом уже конфигурацию пульта настраивать.
Спасибо сказали:
sdv555
Сообщения: 13
ОС: Linux mint 17.2 mate 64x

Re: Настроика Lirc 0.9.0 в минт 17.2 mate 64х

Сообщение sdv555 »

alkesta писал(а):
27.04.2016 10:22
в ~/.cache/mode2.log что-то есть?

для общего понимания, тебе нужно эту часть сделать:

Код: Выделить всё

Basic setup flow
------------
|  remote  |
------------
(air gap)
------------
! capture  !
! device   !
------------
     |
     v
     |
------------
! kernel   !                   Sometimes needs
! driver   !                   modprobe(1) configuration.
------------
     |
     v       IR pulse data
     |
------------
|  lirc    |                   Configure hardware.conf
|  driver  |                   with driver and usually also device.
------------
     |
     v        IR pulse data          Use mode2(1) to debug


а потом уже конфигурацию пульта настраивать.


Здравствуйте.
Что касается файла ~/.cache/mode2.log, то у меня такого файла нет нигде ни в корневом каталоге ни в домашней папке пользователя и когда эту команду набираешь в комендной строке выдается сообщение, что нет такого файла или каталога.
Что касается приведенной вами схемы, то как я понимаю у меня первые два пункта ее работают касаемо определения девайса. Об этом свидетельствуют ответ команды lsusb и dmesg:

Код: Выделить всё

 dmitriy@dmitriy-RV408-RV508 ~ $ lsusb
Bus 002 Device 013: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 012: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 009: ID 1c9e:9605 OMEGA TECHNOLOGY
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0ac8:c33f Z-Star Microelectronics Corp. Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 09da:000a A4 Tech Co., Ltd Optical Mouse Opto 510D
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Код: Выделить всё

[    1.562327] input: A4Tech PS/2+USB Mouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/0003:09DA:000A.0001/input/input8
[    1.562496] a4tech 0003:09DA:000A.0001: input,hidraw0: USB HID v1.10 Mouse [A4Tech PS/2+USB Mouse] on usb-0000:00:1a.0-1/input0
[    1.625348] usb 2-3: New USB device found, idVendor=05e3, idProduct=0608
[    1.625350] usb 2-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.625352] usb 2-3: Product: USB2.0 Hub
[    1.625795] hub 2-3:1.0: USB hub found
[    1.626093] hub 2-3:1.0: 4 ports detected
[    1.712055] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.712413] ata2.00: ATAPI: TSSTcorp CDDVDW TS-L633J, SC00, max UDMA/100
[    1.712989] ata2.00: configured for UDMA/100
[    1.716828] scsi 1:0:0:0: CD-ROM            TSSTcorp CDDVDW TS-L633J  SC00 PQ: 0 ANSI: 5
[    1.739788] sr 1:0:0:0: [sr0] scsi3-mmc drive: 16x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[    1.739790] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.739968] sr 1:0:0:0: Attached scsi CD-ROM sr0
[    1.740211] sr 1:0:0:0: Attached scsi generic sg1 type 5
[    1.812093] clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x1e320bd2e44, max_idle_ns: 440795309093 ns
[    1.884211] psmouse serio1: elantech: assuming hardware version 2 (with firmware version 0x040215)
[    1.923554] psmouse serio1: elantech: Synaptics capabilities query result 0x08, 0x14, 0x0c.
[    2.028108] Console: switching to colour frame buffer device 170x48
[    2.031371] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    2.031373] i915 0000:00:02.0: registered panic notifier
[    2.060044] ata5: SATA link down (SStatus 0 SControl 300)
[    2.063540] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6
[    2.380057] ata6: SATA link down (SStatus 0 SControl 300)
[    2.395494] scsi 6:0:0:0: CD-ROM            USBModem Disk             2.31 PQ: 0 ANSI: 2
[    2.403358] sr 6:0:0:0: [sr1] scsi-1 drive
[    2.403594] sr 6:0:0:0: Attached scsi CD-ROM sr1
[    2.403698] sr 6:0:0:0: Attached scsi generic sg2 type 5
[    2.575281] random: nonblocking pool is initialized
[    4.526693] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    6.085799] init: ureadahead main process (283) terminated with status 5
[    7.323342] Adding 976556k swap on /dev/sda8.  Priority:-1 extents:1 across:976556k FS
[    9.075980] systemd-udevd[398]: starting version 204
[    9.985331] usbcore: registered new interface driver usbserial
[    9.985352] usbcore: registered new interface driver usbserial_generic
[    9.985370] usbserial: USB Serial support registered for generic
[   10.288455] lp: driver loaded but no devices found
[   10.353220] ppdev: user-space parallel port driver
[   12.522505] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   12.773903] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20150410/utaddress-254)
[   12.773912] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   12.773917] ACPI Warning: SystemIO range 0x00000000000011B0-0x00000000000011BF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\GPIO) (20150410/utaddress-254)
[   12.773922] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   12.773923] ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001180-0x00000000000011FF (\GPIO) (20150410/utaddress-254)
[   12.773928] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   12.773929] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   13.196084] cfg80211: Calling CRDA to update world regulatory domain
[   13.236048] device-mapper: multipath: version 1.9.0 loaded
[   13.598270] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC269VB: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   13.598275] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   13.598278] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[   13.598280] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[   13.598282] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[   13.598285] snd_hda_codec_realtek hdaudioC0D0:      Internal Mic=0x19
[   13.598288] snd_hda_codec_realtek hdaudioC0D0:      Mic=0x18
[   13.608895] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[   13.608992] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[   13.636165] ath: phy0: Enable LNA combining
[   13.638776] ath: phy0: ASPM enabled: 0x42
[   13.638780] ath: EEPROM regdomain: 0x65
[   13.638781] ath: EEPROM indicates we should expect a direct regpair map
[   13.638784] ath: Country alpha2 being used: 00
[   13.638785] ath: Regpair used: 0x65
[   13.794625] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   13.795177] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc900008c0000, irq=17
[   14.182976] media: Linux media interface: v0.10
[   14.217574] Linux video capture interface: v2.00
[   14.306019] samsung_laptop: enabled workaround for brightness stepping quirk
[   14.307375] samsung_laptop: detected SABI interface: SwSmi@
[   14.626328] uvcvideo: Found UVC 1.00 device WebCam SCB-0340N (0ac8:c33f)
[   14.635866] input: WebCam SCB-0340N as /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4:1.0/input/input11
[   14.636093] usbcore: registered new interface driver uvcvideo
[   14.636097] USB Video Class driver (1.1.1)
[   15.514571] cfg80211: World regulatory domain updated:
[   15.514576] cfg80211:  DFS Master region: unset
[   15.514578] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   15.514581] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   15.514584] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   15.514587] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[   15.514589] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   15.514591] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[   18.073036] usb 2-1: USB disconnect, device number 2
[   18.440040] usb 2-1: new high-speed USB device number 4 using ehci-pci
[   18.585213] usb 2-1: New USB device found, idVendor=1c9e, idProduct=9605
[   18.585222] usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[   18.585225] usb 2-1: Product: Modem Configuration
[   18.585229] usb 2-1: Manufacturer: USB Modem
[   18.585231] usb 2-1: SerialNumber: 1234567890ABCDEF
[   18.651235] usb-storage 2-1:1.4: USB Mass Storage device detected
[   18.651356] scsi host7: usb-storage 2-1:1.4
[   18.964823] usbcore: registered new interface driver option
[   18.965309] usbserial: USB Serial support registered for GSM modem (1-port)
[   18.965942] option 2-1:1.0: GSM modem (1-port) converter detected
[   18.966265] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
[   18.966334] option 2-1:1.1: GSM modem (1-port) converter detected
[   18.966610] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[   18.966676] option 2-1:1.2: GSM modem (1-port) converter detected
[   18.966993] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
[   18.967063] option 2-1:1.3: GSM modem (1-port) converter detected
[   18.967295] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3
[   19.651374] scsi 7:0:0:0: Direct-Access     USBModem Disk             2.31 PQ: 0 ANSI: 2
[   19.652633] sd 7:0:0:0: Attached scsi generic sg2 type 0
[   19.656240] sd 7:0:0:0: [sdb] 3805184 512-byte logical blocks: (1.94 GB/1.81 GiB)
[   19.659443] sd 7:0:0:0: [sdb] Write Protect is off
[   19.659450] sd 7:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[   19.662251] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   19.682133]  sdb: sdb1
[   19.700982] sd 7:0:0:0: [sdb] Attached SCSI removable disk
[   20.310339] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   22.478276] EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: (null)
[   23.393841] EXT4-fs (sda13): mounted filesystem with ordered data mode. Opts: (null)
[   24.678248] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[   24.744654] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[   24.977979] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
[   25.122468] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[   26.801765] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[   27.594671] init: failsafe main process (935) killed by TERM signal
[   32.517859] Bluetooth: Core ver 2.20
[   32.517901] NET: Registered protocol family 31
[   32.517903] Bluetooth: HCI device and connection manager initialized
[   32.517914] Bluetooth: HCI socket layer initialized
[   32.517919] Bluetooth: L2CAP socket layer initialized
[   32.517930] Bluetooth: SCO socket layer initialized
[   32.555325] Bluetooth: RFCOMM TTY layer initialized
[   32.555336] Bluetooth: RFCOMM socket layer initialized
[   32.555351] Bluetooth: RFCOMM ver 1.11
[   32.829631] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   32.829637] Bluetooth: BNEP filters: protocol multicast
[   32.829644] Bluetooth: BNEP socket layer initialized
[   34.554499] init: cups main process (1137) killed by HUP signal
[   34.554519] init: cups main process ended, respawning
[   40.282968] init: samba-ad-dc main process (1386) terminated with status 1
[   41.320692] init: plymouth-upstart-bridge main process ended, respawning
[   41.331398] init: plymouth-upstart-bridge main process ended, respawning
[   41.394558] sky2 0000:04:00.0 eth0: enabling interface
[   41.395093] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   41.417283] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   59.832987] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.833002] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.833106] pci_bus 0000:08: Allocating resources
[   59.833120] pci 0000:00:1e.0: bridge window [io  0x1000-0x0fff] to [bus 08] add_size 1000
[   59.833124] pci 0000:00:1e.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 08] add_size 200000 add_align 100000
[   59.833127] pci 0000:00:1e.0: bridge window [mem 0x00100000-0x000fffff] to [bus 08] add_size 200000 add_align 100000
[   59.833130] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.833136] pci 0000:00:1e.0: res[14]=[mem 0x00100000-0x000fffff] res_to_dev_res add_size 200000 min_align 100000
[   59.833139] pci 0000:00:1e.0: res[14]=[mem 0x00100000-0x002fffff] res_to_dev_res add_size 200000 min_align 100000
[   59.833142] pci 0000:00:1e.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
[   59.833145] pci 0000:00:1e.0: res[15]=[mem 0x00100000-0x002fffff 64bit pref] res_to_dev_res add_size 200000 min_align 100000
[   59.833148] pci 0000:00:1e.0: res[13]=[io  0x1000-0x0fff] res_to_dev_res add_size 1000 min_align 1000
[   59.833150] pci 0000:00:1e.0: res[13]=[io  0x1000-0x1fff] res_to_dev_res add_size 1000 min_align 1000
[   59.833157] pci 0000:00:1e.0: BAR 14: assigned [mem 0xc0100000-0xc02fffff]
[   59.833164] pci 0000:00:1e.0: BAR 15: assigned [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.833169] pci 0000:00:1e.0: BAR 13: assigned [io  0x6000-0x6fff]
[   59.833173] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.833176] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.833183] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.833189] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.833719] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.833726] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.833731] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.833738] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.833743] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.833894] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.833900] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.833903] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.833910] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.833915] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.834043] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.834048] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.834052] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.834059] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.834064] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.834090] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.834095] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.834098] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.834105] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.834110] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   59.834275] pci_bus 0000:02: Allocating resources
[   59.834294] pci_bus 0000:04: Allocating resources
[   59.834333] pci_bus 0000:06: Allocating resources
[   59.834354] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[   59.834358] pci 0000:00:1e.0: PCI bridge to [bus 08]
[   59.834362] pci 0000:00:1e.0:   bridge window [io  0x6000-0x6fff]
[   59.834368] pci 0000:00:1e.0:   bridge window [mem 0xc0100000-0xc02fffff]
[   59.834373] pci 0000:00:1e.0:   bridge window [mem 0xc0300000-0xc04fffff 64bit pref]
[   60.154297] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[   60.159269] vboxdrv: Found 2 processor cores
[   60.160670] vboxdrv: fAsync=0 offMin=0x1ce offMax=0x2032
[   60.260851] vboxdrv: TSC mode is Synchronous, tentative frequency 2094748505 Hz
[   60.260855] vboxdrv: Successfully loaded version 5.0.12 (interface 0x00240000)
[   60.487594] VBoxNetFlt: Successfully started.
[   60.506655] VBoxNetAdp: Successfully started.
[   60.554365] VBoxPciLinuxInit
[   60.607895] vboxpci: IOMMU not found (not registered)
[   68.903682] init: plymouth-stop pre-start process (2260) terminated with status 1
[   95.112042] usb 2-3.1: new full-speed USB device number 5 using ehci-pci
[   95.401065] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   95.509511] Netfilter messages via NETLINK v0.30.
[   95.551161] ctnetlink v0.93: registering with nfnetlink.
[   95.592356] usb 2-3.1: New USB device found, idVendor=0403, idProduct=6001
[   95.592364] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   95.592367] usb 2-3.1: Product: FT232R USB UART
[   95.592370] usb 2-3.1: Manufacturer: FTDI
[   95.592372] usb 2-3.1: SerialNumber: A9U9LFFR
[   95.618704] ip_tables: (C) 2000-2006 Netfilter Core Team
[   95.817779] usbcore: registered new interface driver ftdi_sio
[   95.817806] usbserial: USB Serial support registered for FTDI USB Serial Device
[   95.817960] ftdi_sio 2-3.1:1.0: FTDI USB Serial Device converter detected
[   95.818014] usb 2-3.1: Detected FT232RL
[   95.820624] usb 2-3.1: FTDI USB Serial Device converter now attached to ttyUSB4
[  155.382585] usb 2-1: USB disconnect, device number 4
[  155.382827] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[  155.382845] option 2-1:1.0: device disconnected
[  155.383016] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[  155.383032] option 2-1:1.1: device disconnected
[  155.383190] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[  155.383206] option 2-1:1.2: device disconnected
[  155.383387] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[  155.383403] option 2-1:1.3: device disconnected
[  155.383876] sd 7:0:0:0: [sdb] Synchronizing SCSI cache
[  155.383936] sd 7:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  164.804047] usb 2-1: new high-speed USB device number 6 using ehci-pci
[  164.949264] usb 2-1: New USB device found, idVendor=1c9e, idProduct=f000
[  164.949273] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[  164.949275] usb 2-1: Product: USB Modem
[  164.949278] usb 2-1: Manufacturer: USB Modem
[  164.949280] usb 2-1: SerialNumber: 000000000000
[  164.953624] usb-storage 2-1:1.0: USB Mass Storage device detected
[  164.953771] scsi host8: usb-storage 2-1:1.0
[  165.957213] scsi 8:0:0:0: CD-ROM            USBModem Disk             2.31 PQ: 0 ANSI: 2
[  165.968564] sr 8:0:0:0: [sr1] scsi-1 drive
[  165.970463] sr 8:0:0:0: Attached scsi CD-ROM sr1
[  165.970633] sr 8:0:0:0: Attached scsi generic sg2 type 5
[  168.424750] usb 2-1: USB disconnect, device number 6
[  168.796075] usb 2-1: new high-speed USB device number 7 using ehci-pci
[  168.941382] usb 2-1: New USB device found, idVendor=1c9e, idProduct=9605
[  168.941390] usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[  168.941393] usb 2-1: Product: Modem Configuration
[  168.941396] usb 2-1: Manufacturer: USB Modem
[  168.941398] usb 2-1: SerialNumber: 1234567890ABCDEF
[  169.007273] option 2-1:1.0: GSM modem (1-port) converter detected
[  169.007404] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
[  169.007529] option 2-1:1.1: GSM modem (1-port) converter detected
[  169.007630] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[  169.007751] option 2-1:1.2: GSM modem (1-port) converter detected
[  169.007852] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
[  169.007974] option 2-1:1.3: GSM modem (1-port) converter detected
[  169.008223] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3
[  169.008349] usb-storage 2-1:1.4: USB Mass Storage device detected
[  169.008482] scsi host9: usb-storage 2-1:1.4
[  174.092673] scsi 9:0:0:0: Direct-Access     USBModem Disk             2.31 PQ: 0 ANSI: 2
[  174.094545] sd 9:0:0:0: Attached scsi generic sg2 type 0
[  174.097793] sd 9:0:0:0: [sdb] 3805184 512-byte logical blocks: (1.94 GB/1.81 GiB)
[  174.101148] sd 9:0:0:0: [sdb] Write Protect is off
[  174.101155] sd 9:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[  174.104184] sd 9:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  174.125498]  sdb: sdb1
[  174.143844] sd 9:0:0:0: [sdb] Attached SCSI removable disk
[  180.806600] NET: Registered protocol family 23
[  203.162205] perf interrupt took too long (2506 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[  212.284613] wlan0: authenticate with 18:62:2c:bc:2c:31
[  212.309993] wlan0: send auth to 18:62:2c:bc:2c:31 (try 1/3)
[  212.311871] wlan0: authenticated
[  212.316042] wlan0: associate with 18:62:2c:bc:2c:31 (try 1/3)
[  212.319566] wlan0: RX AssocResp from 18:62:2c:bc:2c:31 (capab=0x411 status=0 aid=7)
[  212.319683] wlan0: associated
[  212.319732] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  213.126693] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[  220.398750] wlan0: deauthenticated from 18:62:2c:bc:2c:31 (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
[  220.477692] cfg80211: Calling CRDA to update world regulatory domain
[  220.492174] cfg80211: World regulatory domain updated:
[  220.492181] cfg80211:  DFS Master region: unset
[  220.492183] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[  220.492187] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[  220.492190] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[  220.492192] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[  220.492195] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[  220.492197] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[  224.546183] systemd-hostnamed[3774]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[  243.442103] PPP BSD Compression module registered
[  243.489595] PPP Deflate Compression module registered
[  283.272428] CE: hpet increased min_delta_ns to 20115 nsec
[  301.578847] usb 2-1: USB disconnect, device number 7
[  301.579120] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[  301.579146] option 2-1:1.0: device disconnected
[  301.579424] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  301.579432] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  301.579442] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  301.579446] option1 ttyUSB1: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  301.580281] option1 ttyUSB3: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  301.581668] option1 ttyUSB3: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  301.582702] option1 ttyUSB3: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  301.583161] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[  301.583206] option 2-1:1.1: device disconnected
[  301.584087] option1 ttyUSB3: usb_wwan_indat_callback: resubmit read urb failed. (-19)
[  301.584443] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[  301.584469] option 2-1:1.2: device disconnected
[  301.586903] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[  301.586916] option 2-1:1.3: device disconnected
[  301.588194] sd 9:0:0:0: [sdb] Synchronizing SCSI cache
[  301.588252] sd 9:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  307.588056] usb 2-1: new high-speed USB device number 8 using ehci-pci
[  307.733292] usb 2-1: New USB device found, idVendor=1c9e, idProduct=f000
[  307.733300] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[  307.733302] usb 2-1: Product: USB Modem
[  307.733305] usb 2-1: Manufacturer: USB Modem
[  307.733307] usb 2-1: SerialNumber: 000000000000
[  307.737659] usb-storage 2-1:1.0: USB Mass Storage device detected
[  307.737857] scsi host10: usb-storage 2-1:1.0
[  308.739439] scsi 10:0:0:0: CD-ROM            USBModem Disk             2.31 PQ: 0 ANSI: 2
[  308.749225] sr 10:0:0:0: [sr1] scsi-1 drive
[  308.750585] sr 10:0:0:0: Attached scsi CD-ROM sr1
[  308.752552] sr 10:0:0:0: Attached scsi generic sg2 type 5
[  311.231363] usb 2-1: USB disconnect, device number 8
[  311.596071] usb 2-1: new high-speed USB device number 9 using ehci-pci
[  311.741419] usb 2-1: New USB device found, idVendor=1c9e, idProduct=9605
[  311.741424] usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[  311.741426] usb 2-1: Product: Modem Configuration
[  311.741429] usb 2-1: Manufacturer: USB Modem
[  311.741431] usb 2-1: SerialNumber: 1234567890ABCDEF
[  311.807066] option 2-1:1.0: GSM modem (1-port) converter detected
[  311.807205] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
[  311.807333] option 2-1:1.1: GSM modem (1-port) converter detected
[  311.807430] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[  311.807552] option 2-1:1.2: GSM modem (1-port) converter detected
[  311.807653] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
[  311.807778] option 2-1:1.3: GSM modem (1-port) converter detected
[  311.807886] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3
[  311.808026] usb-storage 2-1:1.4: USB Mass Storage device detected
[  311.808286] scsi host11: usb-storage 2-1:1.4
[  316.903567] scsi 11:0:0:0: Direct-Access     USBModem Disk             2.31 PQ: 0 ANSI: 2
[  316.904483] sd 11:0:0:0: Attached scsi generic sg2 type 0
[  316.910203] sd 11:0:0:0: [sdb] 3805184 512-byte logical blocks: (1.94 GB/1.81 GiB)
[  316.912347] sd 11:0:0:0: [sdb] Write Protect is off
[  316.912358] sd 11:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[  316.915351] sd 11:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  316.935253]  sdb: sdb1
[  316.954877] sd 11:0:0:0: [sdb] Attached SCSI removable disk
[  318.045819] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[  365.191972] traps: mate-notificati[4124] trap int3 ip:7f35e1a35c13 sp:7fff50390cd0 error:0
[  601.589257] ftdi_sio ttyUSB4: FTDI USB Serial Device converter now disconnected from ttyUSB4
[  601.589278] ftdi_sio 2-3.1:1.0: device disconnected
[  741.216175] usb 2-3.1: usbfs: USBDEVFS_CONTROL failed cmd mode2 rqt 128 rq 6 len 255 ret -71
[  741.216472] usb 2-3: USB disconnect, device number 3
[  741.216475] usb 2-3.1: USB disconnect, device number 5
[  741.218709] usb 2-3: clear tt 1 (8050) error -71
[  742.980028] usb 2-3: new high-speed USB device number 10 using ehci-pci
[  743.113401] usb 2-3: New USB device found, idVendor=05e3, idProduct=0608
[  743.113406] usb 2-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[  743.113409] usb 2-3: Product: USB2.0 Hub
[  743.114123] hub 2-3:1.0: USB hub found
[  743.114501] hub 2-3:1.0: 4 ports detected
[  743.388083] usb 2-3.1: new full-speed USB device number 11 using ehci-pci
[  743.862460] usb 2-3.1: New USB device found, idVendor=0403, idProduct=6001
[  743.862470] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  743.862473] usb 2-3.1: Product: FT232R USB UART
[  743.862475] usb 2-3.1: Manufacturer: FTDI
[  743.862478] usb 2-3.1: SerialNumber: A9U9LFFR
[  743.909678] ftdi_sio 2-3.1:1.0: FTDI USB Serial Device converter detected
[  743.909736] usb 2-3.1: Detected FT232RL
[  743.910426] usb 2-3.1: FTDI USB Serial Device converter now attached to ttyUSB4
[  744.621052] ftdi_sio ttyUSB4: FTDI USB Serial Device converter now disconnected from ttyUSB4
[  744.621077] ftdi_sio 2-3.1:1.0: device disconnected
[  771.994483] perf interrupt took too long (5012 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
[  952.608779] lirc_dev: IR Remote Control driver registered, major 248
[  952.626134] lirc_serial: module is from the staging directory, the quality is unknown, you have been warned.
[  952.626673] lirc_serial: port existence test failed, cannot continue
[  952.627742] platform lirc_serial.0: lirc_dev: driver lirc_serial registered at minor = 0
[ 1096.686992] usb 2-3: USB disconnect, device number 10
[ 1096.686998] usb 2-3.1: USB disconnect, device number 11
[ 1098.952042] usb 2-3: new high-speed USB device number 12 using ehci-pci
[ 1099.085574] usb 2-3: New USB device found, idVendor=05e3, idProduct=0608
[ 1099.085582] usb 2-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1099.085585] usb 2-3: Product: USB2.0 Hub
[ 1099.086312] hub 2-3:1.0: USB hub found
[ 1099.087262] hub 2-3:1.0: 4 ports detected
[ 1099.360054] usb 2-3.1: new full-speed USB device number 13 using ehci-pci
[ 1099.834977] usb 2-3.1: New USB device found, idVendor=0403, idProduct=6001
[ 1099.834983] usb 2-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1099.834991] usb 2-3.1: Product: FT232R USB UART
[ 1099.834993] usb 2-3.1: Manufacturer: FTDI
[ 1099.834996] usb 2-3.1: SerialNumber: A9U9LFFR
[ 1099.882463] ftdi_sio 2-3.1:1.0: FTDI USB Serial Device converter detected
[ 1099.882527] usb 2-3.1: Detected FT232RL
[ 1099.883094] usb 2-3.1: FTDI USB Serial Device converter now attached to ttyUSB4
[ 1100.639326] ftdi_sio ttyUSB4: FTDI USB Serial Device converter now disconnected from ttyUSB4
[ 1100.639348] ftdi_sio 2-3.1:1.0: device disconnected
dmitriy@dmitriy-RV408-RV508 ~ $

При этом почему-то как мне кажется не происходит освобождение порта ни перед выполнением обращения лирца ни после выполнения каких либо команд. Это проявляется тем, что после выполнения команды mode2 -Hftdi -dserial=A9U9LFFR и принудительном выходе из командной строки, постоянно висит команда порта на передачу и исчезает только после рестарта системы.
Что касается второго шага, то как раз тут все и стопорится!!! Как на сайте лирца так и в других источниках в интерет мельком проскакивают высказывания о том, что где-то в ядре есть какие-то ключи для работы с ик-портами и которые якобы отключены по умолчанию начиная какой-то не помнюточно с какой версии ядра дистрибутива. Я полагаю пока я не смогу каким-то образом (через скрипт запускаемый перед запуском лирца или принудительно настроить через конфиг эти ключи) у меня не будут запускаться daemond и дальше ничего не запустится. Сейчас как я уже описывал раньше все стопорится именно на этом шаге!!! Как настроить эти ключи я нигде не смог найти.
Спасибо сказали:
Ответить