Автор Тема: Информика школьный мастер и Interwrite Board 1279 (Прочитано 6583 раз)

igorigor76 · « : 02.04.2013 15:23:58 »

[root@k-04-01 Desktop]# uname -a
Linux k-04-01.localdomain 3.0.69-std-def-alt0.M60P.1 #1 SMP Thu Mar 14 23:57:55 UTC 2013 i686 GNU/Linux

Софт для доски скачивал с _http://www.einstruction.com/
Установка софта нормально прошла в графическом режиме. Программа запускается а вот сама доска не работает.

ПО для настройки доски не запускается.
В терминале:

Код: [Выделить]

[rti@k-04-01 DeviceManager]$ ./LinuxLauncher.sh
Found eInstructionLogging.properties as resource - configuring logging
CONFIG
Can't load log handler "java.util.logging.FileHandler"
java.io.IOException: Couldn't get lock for %h/eInstruction/Device Manager/DeviceManager_%g.log
java.io.IOException: Couldn't get lock for %h/eInstruction/Device Manager/DeviceManager_%g.log
        at java.util.logging.FileHandler.openFiles(Unknown Source)
        at java.util.logging.FileHandler.<init>(Unknown Source)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at java.lang.Class.newInstance0(Unknown Source)
        at java.lang.Class.newInstance(Unknown Source)
        at java.util.logging.LogManager$3.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.util.logging.LogManager.loadLoggerHandlers(Unknown Source)
        at java.util.logging.LogManager.initializeGlobalHandlers(Unknown Source)
        at java.util.logging.LogManager.access$900(Unknown Source)
        at java.util.logging.LogManager$RootLogger.getHandlers(Unknown Source)
        at java.util.logging.Logger.log(Unknown Source)
        at java.util.logging.Logger.doLog(Unknown Source)
        at java.util.logging.Logger.log(Unknown Source)
        at einstruction.dm.DeviceManager.createPropertiesMap(Unknown Source)
        at einstruction.dm.DeviceManager.<clinit>(Unknown Source)
        at einstruction.dm.ui.Main.<clinit>(Unknown Source)
Apr 2, 2013 7:24:00 AM einstruction.dm.DeviceManager createPropertiesMap
INFO: SudoUserHome: /home/rti/
Apr 2, 2013 7:24:01 AM einstruction.dm.ui.Main <clinit>
INFO: Loading native support lib...
Apr 2, 2013 7:24:02 AM einstruction.dm.ui.Main <clinit>
INFO: Native support lib loaded
libNativeSupport[23128]: NATIVESUPPORT: Native Java subscribeUSBChangeEvents() JavaVM* = -1222728284
libNativeSupport[23128]: NATIVESUPPORT: Native Java subscribeUSBChangeEvents() JNIEnv = 134589720
libNativeSupport[23128]: NATIVESUPPORT: Native Java subscribeUSBChangeEvents() jclass = 135100728
libNativeSupport[23128]: NATIVESUPPORT: Native Java subscribeUSBChangeEvents() jmethodID = 140249228
libNativeSupport[23128]: NATIVESUPPORT: startDisplayChangedEventThread(): Entered.
libNativeSupport[23128]: NATIVESUPPORT: startDisplayChangedEventThread(): Entered.
libNativeSupport[23128]: NATIVESUPPORT: startDisplayChangedEventThread(): call back created.
Apr 2, 2013 7:24:02 AM java.util.logging.LogManager$RootLogger log
WARNING: Log Level Changed: WARNING
Apr 2, 2013 7:24:02 AM einstruction.dm.ui.Main main
WARNING: 

Device Manager Version: 7.1.91.70258
WorkSpace Version: 6.0.417.70042

Java Version: 1.6.0_21
OS Name: Linux, Version: 3.0.69-std-def-alt0.M60P.1, Arch: i386


libNativeSupport[23128]: NATIVESUPPORT: Found VID: 1d6b
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 1d6b
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 1d6b
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 1d6b
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 1d6b
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 192f
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 078c
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 04f2
libNativeSupport[23128]: NATIVESUPPORT: Found: 002/002-078c-0403-00-00
libNativeSupport[23128]: NATIVESUPPORT: getVid() Looking For : 002/002-078c-0403-00-00
libNativeSupport[23128]: NATIVESUPPORT: getVid() Found : 002/002
libNativeSupport[23128]: NATIVESUPPORT: getPid() Looking For : 002/002-078c-0403-00-00
libNativeSupport[23128]: NATIVESUPPORT: getPid() Found : 002/002
libNativeSupport[23128]: NATIVESUPPORT: open_Device() Looking For : 002/002-078c-0403-00-00
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 1d6b
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 1d6b
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 1d6b
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 1d6b
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 1d6b
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 192f
libNativeSupport[23128]: NATIVESUPPORT: Found VID: 078c
libNativeSupport[23128]: NATIVESUPPORT: open_Device() Found : 002/002-078c-0403-00-00
libNativeSupport[23128]: NATIVESUPPORT: Read thread is starting for device: DualBoard  40-00875 A  05/26/10
libNativeSupport[23128]: NATIVESUPPORT: write_Device Succeeded.  Bytes written (64).
Apr 2, 2013 7:24:04 AM einstruction.dm.connections.DBQueryCommandParser parse
WARNING: The dualboard is unable to communicate with the RFCOM device. If this happens after the firmware update please manually reset the device, or the dualboard must have an older firmware or the RFCOM device is off.
Apr 2, 2013 7:24:04 AM einstruction.dm.connections.USBRFCommDeviceIO initializeDevice
WARNING: FIRMWARE: DB RFCOM Revision: 
libNativeSupport[23128]: NATIVESUPPORT: write_Device Succeeded.  Bytes written (64).
libNativeSupport[23128]: NATIVESUPPORT: write_Device Succeeded.  Bytes written (64).
Apr 2, 2013 7:24:04 AM einstruction.dm.ui.InputDeviceListModel handleDeviceStateChanged
WARNING: FIRMWARE: Device Type(DUALBOARD) Device URL(002/002-078C-0403-00-00) Revision(4000875A)
Serialio Library: version 10.0.4: build 9212
Copyright (c) 1996-2009 Serialio.com, All Rights Reserved.
os.name="Linux"  os.arch="i386"
SerialPort class loaded: jspLux86
getPortList: using list created with addPortName
Serialio.com jspLux86 4.7
Copyright (C) Serialio.com 1996-2003. All rights reserved.
Apr 2, 2013 7:24:08 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS0
Apr 2, 2013 7:24:12 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS1
Apr 2, 2013 7:24:12 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS2
Apr 2, 2013 7:24:12 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS3
Apr 2, 2013 7:24:12 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyUSB0
Apr 2, 2013 7:24:12 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyUSB1
Apr 2, 2013 7:24:12 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM0
Apr 2, 2013 7:24:12 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM1
Apr 2, 2013 7:24:12 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM2
Apr 2, 2013 7:24:12 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS0
Apr 2, 2013 7:24:13 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS1
Apr 2, 2013 7:24:13 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS2
Apr 2, 2013 7:24:13 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS3
Apr 2, 2013 7:24:13 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyUSB0
Apr 2, 2013 7:24:13 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyUSB1
Apr 2, 2013 7:24:13 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM0
Apr 2, 2013 7:24:13 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM1
Apr 2, 2013 7:24:13 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM2
Apr 2, 2013 7:24:14 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS0
Apr 2, 2013 7:24:14 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS1
Apr 2, 2013 7:24:14 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS2
Apr 2, 2013 7:24:14 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS3
Apr 2, 2013 7:24:14 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyUSB0
Apr 2, 2013 7:24:14 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyUSB1
Apr 2, 2013 7:24:14 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM0
Apr 2, 2013 7:24:14 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM1
Apr 2, 2013 7:24:14 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM2
getPortList: using list created with addPortName
scanPort1
portNumber = -1
testReceiver1
testReceiver2
testReceiver3
testReceiver4
testReceiver(): Closed port.
Apr 2, 2013 7:24:19 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS0
scanPort1
portNumber = -1
testReceiver1
testReceiver2
testReceiver3
testReceiver4
testReceiver(): Closed port.
Apr 2, 2013 7:24:24 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS1
scanPort1
portNumber = -1
testReceiver1
testReceiver2
testReceiver3
testReceiver(): Closed port.
Apr 2, 2013 7:24:24 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS2
scanPort1
portNumber = -1
testReceiver1
testReceiver2
testReceiver3
testReceiver(): Closed port.
Apr 2, 2013 7:24:24 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyS3
scanPort1
portNumber = -1
testReceiver1
testReceiver2
testReceiver3
testReceiver(): Closed port.
Apr 2, 2013 7:24:24 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyUSB0
scanPort1
portNumber = -1
testReceiver1
testReceiver2
testReceiver3
testReceiver(): Closed port.
Apr 2, 2013 7:24:24 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyUSB1
scanPort1
portNumber = -1
testReceiver1
testReceiver2
testReceiver3
testReceiver(): Closed port.
Apr 2, 2013 7:24:24 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM0
scanPort1
portNumber = -1
testReceiver1
testReceiver2
testReceiver3
testReceiver(): Closed port.
Apr 2, 2013 7:24:24 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM1
scanPort1
portNumber = -1
testReceiver1
testReceiver2
testReceiver3
testReceiver(): Closed port.
Apr 2, 2013 7:24:24 AM einstruction.dm.DeviceBuilder processURL
WARNING: DeviceBuilder: Was unable to build InputDevice for /dev/ttyACM2
libNativeSupport[23128]: SHAREDMEMORY: Constructor Pushing Shared Memory Instance (2074713768)
libNativeSupport[23128]: SHAREDMEMORY: shmget was successful for key (5678).  Shared Memory ID Created (1540120)
libNativeSupport[23128]: SHAREDMEMORY: shmat was successful Shared Memory Address (2025062400)
libNativeSupport[23128]: SHAREDMEMORY: Successfully attached and created a new Shared Memory Instance (2074713768)
libNativeSupport[23128]: SHAREDMEMORY: Constructor Pushing Shared Memory Instance (2071872016)
libNativeSupport[23128]: SHAREDMEMORY: shmget was successful for key (5679).  Shared Memory ID Created (1572889)
libNativeSupport[23128]: SHAREDMEMORY: shmat was successful Shared Memory Address (2024800256)
libNativeSupport[23128]: SHAREDMEMORY: Successfully attached and created a new Shared Memory Instance (2071872016)
libNativeSupport[23128]: SHAREDMEMORY: retrieveSharedMemoryDirectByteBuffer() called for Shared Memory Instance (2074713768)
libNativeSupport[23128]: SHAREDMEMORY: Shared Memory Instance (2074713768) found.
libNativeSupport[23128]: SHAREDMEMORY: retrieveSharedMemoryDirectByteBuffer() called for Shared Memory Instance (2071872016)
libNativeSupport[23128]: SHAREDMEMORY: Shared Memory Instance (2071872016) found.
The program 'java' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 223 error_code 8 request_code 73 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[rti@k-04-01 DeviceManager]$

При включении отключении доски:

Код: [Выделить]

Apr  2 07:35:06 k-04-01 kernel: [ 1172.464049] usb 2-1: USB disconnect, device number 4
Apr  2 07:35:11 k-04-01 kernel: [ 1177.912015] usb 2-1: new full speed USB device number 5 using uhci_hcd
Apr  2 07:35:11 k-04-01 kernel: [ 1178.090873] usb 2-1: New USB device found, idVendor=078c, idProduct=0403
Apr  2 07:35:11 k-04-01 kernel: [ 1178.090878] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr  2 07:35:11 k-04-01 kernel: [ 1178.090881] usb 2-1: Product: DualBoard 
Apr  2 07:35:11 k-04-01 kernel: [ 1178.090884] usb 2-1: Manufacturer: eInstruction
Apr  2 07:35:11 k-04-01 mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-1" 
Apr  2 07:35:11 k-04-01 mtp-probe: bus: 2, device: 5 was not an MTP device

Помогите разобраться.

ruslandh · « **Ответ #1 :** 02.04.2013 19:22:29 »

Мне кажется, тут надо какие-то правила для udev создать, что-бы устройство виделось как /dev/USB0 или что-то аналогичное.
Ну и программа просит, что-бы её запускали в графическом окне

igorigor76 · « **Ответ #2 :** 02.04.2013 20:05:29 »

Цитата: ruslandh от 02.04.2013 19:22:29

Ну и программа просит, что-бы её запускали в графическом окне

При попытке запуска значок "прыгает" несколько секунд и все. Программа не запускается. Поэтому запустил в консоли, что бы показать вывод.

Skull · « **Ответ #3 :** 02.04.2013 20:50:33 »

Запустите из терминала графического сеанса.

igorigor76 · « **Ответ #4 :** 02.04.2013 23:00:18 »

Я извиняюсь, если ввел вас в заблуждение.

Цитата: igorigor76 от 02.04.2013 20:05:29

... запустил в консоли...

Имелось ввиду в сеансе KDE запустил терминал а потом уже

Код: [Выделить]

[rti@k-04-01 DeviceManager]$ ./LinuxLauncher.sh

igorigor76 · « **Ответ #5 :** 04.04.2013 12:57:45 »

Сегодня позвонил на горячую линию Interwrite. Посоветовали начать с инструкции. В ней написано, что нужно установить пакеты bluez и убедиться в запуске rfcomm сервиса. bluez установлен. А что с сервисом rfcomm?

Код: [Выделить]

# service rfcomm start
service: rfcomm: Unrecognized service

Skull · « **Ответ #6 :** 04.04.2013 14:29:09 »

Цитата: igorigor76 от 04.04.2013 12:57:45

Сегодня позвонил на горячую линию Interwrite. Посоветовали начать с инструкции. В ней написано, что нужно установить пакеты bluez и убедиться в запуске rfcomm сервиса. bluez установлен. А что с сервисом rfcomm?
Код: [Выделить]
# service rfcomm start service: rfcomm: Unrecognized service

Код: [Выделить]

service bluetoothd startrfcomm не служба, а программа из /usr/bin. Поэтому после запуска службы:

Код: [Выделить]

ps ax | grep rfcomm

igorigor76 · « **Ответ #7 :** 05.04.2013 12:04:03 »

Цитата: Skull от 04.04.2013 14:29:09

Код: [Выделить]
service bluetoothd startrfcomm не служба, а программа из /usr/bin. Поэтому после запуска службы:
Код: [Выделить]
ps ax | grep rfcomm

Код: [Выделить]

[root@k-04-01 ~]# service bluetoothd start
Service bluetoothd is already running.                                                                                                 [PASSED]
[root@k-04-01 ~]# ps ax | grep rfcomm
32168 pts/1    R+     0:00 grep --color=auto rfcomm 
[root@k-04-01 ~]#

Что дальше?

Skull · « **Ответ #8 :** 05.04.2013 16:19:26 »

Изучать http://manpages.ylsoftware.com/ru/rfcomm.1.html. Ну и обращаться в службу техподдержки оборудования.

igorigor76 · « **Ответ #9 :** 05.04.2013 21:12:11 »

Доска подключена через USB. rfcomm при этом может как-то повлиять на работоспособность доски?
В службу поддержки написал, указав ссылку на эту тему.

igorigor76 · « **Ответ #10 :** 07.05.2013 10:14:51 »

Вчера со службы поддержки ответили.
Были такие рекомендации:

Цитировать

Вот ответ разработчика

Although our products are not officially supported for this version of Ubuntu, please make sure that you have disabled Visual Effects , going to System > Preferences > Appearance

Пожалуйста, убедитесь, что визуальные эффекты отключены.

Это относится к настройкам KDE?
Я пробовал Минимальные настройки KDE.
Установил XFCE и GNOME.
Пока безрезультатно.

Форум сообщества
Альт Линукс