Brainboxes RS232 PC-Card

S

Stuttgarter

Member
Themenstarter
Registriert
15 Jan. 2008
Beiträge
136
Hallo,

ich würde gern mein Garmin-GPS (Geko 201) auslesen über die serielle Schnittstelle. Da mein T61 keinen seriellen Port hat, habe ich mir diese PC-Card besorgt.

Leider bekomme ich das Ding unter Ubuntu 10.04 nicht zum laufen. Auf der Treiber-CD sind zwar Linux-Treiber drauf, aber nur für Kernel 2.4.24 und 2.4.25, die sich logischerweise nicht installieren lassen.

lspci zeigt nichts an, aber der Gnome-Device Manager erkennt die Karte, genauso wie lshw:
Code: 
 *-serial UNCLAIMED
         	description: SMBus
         	product: 82801H (ICH8 Family) SMBus Controller
         	vendor: Intel Corporation
         	physical id: 1f.3
         	bus info: pci@0000:00:1f.3
         	version: 03
         	width: 32 bits
         	clock: 33MHz
         	configuration: latency=0
         	resources: memory:fe227400-fe2274ff ioport:1c60(size=32)

Wie bekomme ich die Karte zum laufen? Aktuelle Treiber sind nirgendwo zu finden ?(

Vielen Dank!

Gruß
Micha
 
Hi,

das halte ich für ein Gerücht, daß dieser Output deine Karte zeigt. Gib doch mal
Code: 
lspcmcia
 
ups :rolleyes:

Hier ist der gesamte Output von lspcmcia:

Code: 
~$ lspcmcia
Socket 0 Bridge:   	[yenta_cardbus] 	(bus ID: 0000:15:00.0)
Socket 0 Device 0:	[serial_cs]		(bus ID: 0.0)

Gruß
Micha
 
Und nun noch
Code: 
cat /proc/ioports | grep serial
cat /proc/interrupts  | grep serial
 
[quote='linrunner',index.php?page=Thread&postID=882045#post882045]Und nun noch
Code: 
cat /proc/ioports | grep serial
cat /proc/interrupts  | grep serial
[/quote]
Beide Male gibt's kein Ergebnis!

Der lspcmcia mit Option -v bringt diese Infos:

Code: 
lspcmcia -v
Socket 0 Bridge:   	[yenta_cardbus] 	(bus ID: 0000:15:00.0)
	Configuration:	state: on	ready: unknown
			Voltage: 5.0V Vcc: 5.0V Vpp: 0.0V
Socket 0 Device 0:	[serial_cs]		(bus ID: 0.0)
	Configuration:	state: on
	Product Name:   Brain Boxes 1-Port RS232 card r6 
	Identification:	manf_id: 0x0160	card_id: 0x0103
			function: 2 (serial)
			prod_id(1): "Brain Boxes" (0xee138382)
			prod_id(2): "1-Port RS232 card" (0x98f774fa)
			prod_id(3): "r6" (0xd2b38eed)
			prod_id(4): --- (---)

Gruß
Micha
 
Zeig mal bitte per http://paste.ubuntuusers.de den vollständigen Output von
Code: 
dmesg
wenn Du das ThinkPad mit eingesteckter Karte hochgefahren hast.

ps. es sieht so aus, als ob Du den internen seriellen Port (nur am Dock vefügbar) im BIOS (/Config/Serial Port) disabled hast. Richtig?
 
[quote='linrunner',index.php?page=Thread&postID=882123#post882123]Zeig mal bitte per http://paste.ubuntuusers.de den vollständigen Output von
Code: 
dmesg
wenn Du das ThinkPad mit eingesteckter Karte hochgefahren hast.

ps. es sieht so aus, als ob Du den internen seriellen Port (nur am Dock vefügbar) im BIOS (/Config/Serial Port) disabled hast. Richtig?[/quote]
So, hier steht der Output von dmesg: http://paste.ubuntuusers.de/398572/

Nein, "Serial" ist im BIOS enabled, mit Adresse 3F8 und IRQ4. Ist das falsch? Eine Dockingstation habe ich nicht.

Gruß
Micha
 
Deaktiviere COM1 im BIOS. Damit ist die Brainboxes Card frei für COM 1

Serial Port im BIOS nützt nur bei Verwendung einer Dock mit serieller Schnittstelle oder bei Verwendung der Ultrabay slim RS232/Paralell Adapter.
 
[quote='Mornsgrans',index.php?page=Thread&postID=882681#post882681]Deaktiviere COM1 im BIOS. Damit ist die Brainboxes Card frei für COM 1[/quote]
Der Tip war gut :) Jetzt sehe ich im Device Manager noch einen Eintrag mehr. Aber ich kann irgendwie doch noch nicht drauf zugreifen per gpsbabel bzw. Gebabbel. Da bekomme ich einen "Permission denied", und wenn ich's per sudo starte, einen "can't init /dev/ttyS0".

Anhang anzeigen 31487

Im Nautilus hat die ttyS0 die Zugriffsrechte 20600, die anderen ttySx (die wohl gar nicht existieren) haben 20660.

Mich wundert's ja, daß das so funktionieren soll, obwohl ich gar nichts installiert habe (Treiber...).

Viele Grüße
Micha
 

Anhänge

  • rs232.png
    rs232.png
    38,1 KB · Aufrufe: 9
Treiber installieren tut man unter Windows ;) .

Ein
Code: 
sudo chmod 660 /dev/ttyS0
sollte Abhilfe schaffen. Kann man auch als Workaround in /etc/rc.local einbauen (ohne das sudo!)

Ich würde aber noch gerne wissen welche udev-Regel da nicht zieht, um es ggf. sauber lösen zu können. Paste doch bitte noch:
Code: 
udevadm info -a -p $(udevadm info -q path -n ttyS0)
und
Code: 
sudo udevadm test  $(udevadm info -q path -n ttyS0)
 
Im Anschluss daran dürfte noch ein "setserial" erforderlich sein.
 
Ok, hier sind die Infos:

Code: 
udevadm info -a -p $(udevadm info -q path -n ttyS0)

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/tty/ttyS0':
    KERNEL=="ttyS0"
    SUBSYSTEM=="tty"
    DRIVER==""

  looking at parent device '/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0':
    KERNELS=="0.0"
    SUBSYSTEMS=="pcmcia"
    DRIVERS=="serial_cs"
    ATTRS{function}=="0x00"
    ATTRS{pm_state}=="on"
    ATTRS{func_id}=="0x02"
    ATTRS{manf_id}=="0x0160"
    ATTRS{card_id}=="0x0103"
    ATTRS{prod_id1}=="Brain Boxes"
    ATTRS{prod_id2}=="1-Port RS232 card"
    ATTRS{prod_id3}=="r6"
    ATTRS{modalias}=="pcmcia:m0160c0103f02fn00pfn00paEE138382pb98F774FApcD2B38EEDpd00000000"

  looking at parent device '/devices/pci0000:00/0000:00:1e.0/0000:15:00.0':
    KERNELS=="0000:15:00.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="yenta_cardbus"
    ATTRS{vendor}=="0x1180"
    ATTRS{device}=="0x0476"
    ATTRS{subsystem_vendor}=="0x17aa"
    ATTRS{subsystem_device}=="0x20c6"
    ATTRS{class}=="0x060700"
    ATTRS{irq}=="16"
    ATTRS{local_cpus}=="00000000,00000003"
    ATTRS{local_cpulist}=="0-1"
    ATTRS{modalias}=="pci:v00001180d00000476sv000017AAsd000020C6bc06sc07i00"
    ATTRS{numa_node}=="-1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:1e.0':
    KERNELS=="0000:00:1e.0"
    SUBSYSTEMS=="pci"
    DRIVERS==""
    ATTRS{vendor}=="0x8086"
    ATTRS{device}=="0x2448"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{class}=="0x060401"
    ATTRS{irq}=="0"
    ATTRS{local_cpus}=="00000000,00000003"
    ATTRS{local_cpulist}=="0-1"
    ATTRS{modalias}=="pci:v00008086d00002448sv00000000sd00000000bc06sc04i01"
    ATTRS{numa_node}=="-1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

und

Code: 
sudo udevadm test  $(udevadm info -q path -n ttyS0)
Password or swipe finger: 
run_command: calling: test
udevadm_test: version 151
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

parse_file: reading '/etc/udev/rules.d/10-vboxdrv.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-fuse-utils.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-gnupg.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-hplip.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-ia64.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-infiniband.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-isdn.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libgphoto2-2.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libpisock9.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-libsane.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-pilot-links.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-ppc.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-usb-media-players.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-xserver-xorg-video-intel.rules' as rules file
parse_file: reading '/lib/udev/rules.d/40-zaptel.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-fuse.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-libmtp8.rules' as rules file
parse_file: reading '/lib/udev/rules.d/45-libnjb5.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-firmware.rules' as rules file
parse_file: reading '/lib/udev/rules.d/50-udev-default.rules' as rules file
parse_file: reading '/lib/udev/rules.d/55-dm.rules' as rules file
parse_file: reading '/lib/udev/rules.d/56-hpmud_support.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-cdrom_id.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-floppy.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-alsa.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-input.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-serial.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage-dm.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage-tape.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-storage.rules' as rules file
parse_file: reading '/lib/udev/rules.d/60-persistent-v4l.rules' as rules file
parse_file: reading '/etc/udev/rules.d/60-thinkfinger.rules' as rules file
add_rule: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/60-thinkfinger.rules:13
parse_file: reading '/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-mobile-action.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-option-modem-modeswitch.rules' as rules file
parse_file: reading '/lib/udev/rules.d/61-persistent-storage-edd.rules' as rules file
parse_file: reading '/lib/udev/rules.d/64-device-mapper.rules' as rules file
parse_file: reading '/lib/udev/rules.d/64-xorg-xkb.rules' as rules file
parse_file: reading '/lib/udev/rules.d/66-xorg-synaptics.rules' as rules file
parse_file: reading '/lib/udev/rules.d/69-xorg-vmmouse.rules' as rules file
parse_file: reading '/lib/udev/rules.d/69-xserver-xorg-input-wacom.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-acl.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-hid2hci.rules' as rules file
parse_file: reading '/etc/udev/rules.d/70-persistent-cd.rules' as rules file
parse_file: reading '/etc/udev/rules.d/70-persistent-net.rules' as rules file
parse_file: reading '/lib/udev/rules.d/70-printers.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-cd-aliases-generator.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-net-description.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-persistent-net-generator.rules' as rules file
parse_file: reading '/lib/udev/rules.d/75-tty-description.rules' as rules file
parse_file: reading '/lib/udev/rules.d/77-mm-ericsson-mbm.rules' as rules file
parse_file: reading '/lib/udev/rules.d/77-mm-longcheer-port-types.rules' as rules file
parse_file: reading '/lib/udev/rules.d/77-mm-zte-port-types.rules' as rules file
parse_file: reading '/lib/udev/rules.d/78-graphics-card.rules' as rules file
parse_file: reading '/lib/udev/rules.d/78-sound-card.rules' as rules file
parse_file: reading '/lib/udev/rules.d/79-fstab_import.rules' as rules file
parse_file: reading '/lib/udev/rules.d/80-alsa.rules' as rules file
parse_file: reading '/lib/udev/rules.d/80-drivers.rules' as rules file
parse_file: reading '/lib/udev/rules.d/80-udisks.rules' as rules file
parse_file: reading '/lib/udev/rules.d/85-console-setup.rules' as rules file
parse_file: reading '/lib/udev/rules.d/85-hdparm.rules' as rules file
parse_file: reading '/lib/udev/rules.d/85-hplj10xx.rules' as rules file
parse_file: reading '/lib/udev/rules.d/85-pcmcia.rules' as rules file
parse_file: reading '/lib/udev/rules.d/85-regulatory.rules' as rules file
parse_file: reading '/lib/udev/rules.d/85-usbmuxd.rules' as rules file
parse_file: reading '/lib/udev/rules.d/90-hal.rules' as rules file
parse_file: reading '/lib/udev/rules.d/90-libgpod.rules' as rules file
parse_file: reading '/lib/udev/rules.d/90-pulseaudio.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-keyboard-force-release.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-keymap.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-udev-late.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-upower-battery-recall-dell.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-upower-battery-recall-gateway.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-upower-battery-recall-ibm.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-upower-csr.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-upower-hid.rules' as rules file
parse_file: reading '/lib/udev/rules.d/95-upower-wup.rules' as rules file
parse_file: reading '/lib/udev/rules.d/97-bluetooth.rules' as rules file
parse_file: reading '/dev/.udev/rules.d/root.rules' as rules file
udev_rules_new: rules use 208932 bytes tokens (17411 * 12 bytes), 33076 bytes buffer
udev_rules_new: temporary index used 55120 bytes (2756 * 20 bytes)
udev_device_new_from_syspath: device 0x7f4bfb69a8a0 has devpath '/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/tty/ttyS0'
udev_device_new_from_syspath: device 0x7f4bfb69ab50 has devpath '/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/tty/ttyS0'
udev_device_read_db: device 0x7f4bfb69ab50 filled with db file data
udev_device_new_from_syspath: device 0x7f4bfb69b230 has devpath '/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0'
udev_device_new_from_syspath: device 0x7f4bfb692990 has devpath '/devices/pci0000:00/0000:00:1e.0/0000:15:00.0'
udev_device_new_from_syspath: device 0x7f4bfb692c60 has devpath '/devices/pci0000:00/0000:00:1e.0'
udev_device_new_from_syspath: device 0x7f4bfb69c240 has devpath '/devices/pci0000:00'
udev_rules_apply_to_event: LINK 'char/4:64' /lib/udev/rules.d/50-udev-default.rules:4
udev_rules_apply_to_event: GROUP 20 /lib/udev/rules.d/50-udev-default.rules:15
udev_rules_apply_to_event: IMPORT 'pci-db /devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/tty/ttyS0' /lib/udev/rules.d/75-tty-description.rules:11
util_run_program: 'pci-db /devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/tty/ttyS0' started
util_run_program: '/lib/udev/pci-db' (stderr) 'libudev: udev_device_new_from_syspath: '
util_run_program: '/lib/udev/pci-db' (stderr) 'device 0x7f2368867130 has devpath '//devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/tty/ttyS0''
util_run_program: '/lib/udev/pci-db' (stderr) 'libudev: udev_device_new_from_syspath: '
util_run_program: '/lib/udev/pci-db' (stderr) 'device 0x7f23688674b0 has devpath '//devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/tty''
util_run_program: '/lib/udev/pci-db' (stderr) 'libudev: udev_device_new_from_syspath: '
util_run_program: '/lib/udev/pci-db' (stderr) 'device 0x7f23688676e0 has devpath '//devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0''
util_run_program: '/lib/udev/pci-db' (stderr) 'libudev: udev_device_new_from_syspath: '
util_run_program: '/lib/udev/pci-db' (stderr) 'device 0x7f23688679f0 has devpath '//devices/pci0000:00/0000:00:1e.0/0000:15:00.0''
util_run_program: '/lib/udev/pci-db' (stdout) 'ID_VENDOR_FROM_DATABASE=Ricoh Co Ltd'
util_run_program: '/lib/udev/pci-db' (stdout) 'ID_MODEL_FROM_DATABASE=RL5c476 II'
util_run_program: 'pci-db /devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/tty/ttyS0' returned with exitcode 0
udev_rules_apply_to_event: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2
udev_event_execute_rules: no node name set, will use kernel supplied name 'ttyS0'
udev_device_update_db: created db file for '/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/tty/ttyS0' in '/dev/.udev/db/tty:ttyS0'
udev_node_add: creating device node '/dev/ttyS0', devnum=4:64, mode=0660, uid=0, gid=20
udev_node_mknod: preserve file '/dev/ttyS0', because it has correct dev_t
node_symlink: preserve already existing symlink '/dev/char/4:64' to '../ttyS0'
udevadm_test: UDEV_LOG=6
udevadm_test: DEVPATH=/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/tty/ttyS0
udevadm_test: MAJOR=4
udevadm_test: MINOR=64
udevadm_test: DEVNAME=/dev/ttyS0
udevadm_test: ACTION=add
udevadm_test: SUBSYSTEM=tty
udevadm_test: DEVLINKS=/dev/char/4:64
udevadm_test: ID_VENDOR_FROM_DATABASE=Ricoh Co Ltd
udevadm_test: ID_MODEL_FROM_DATABASE=RL5c476 II
udevadm_test: ID_BUS=pci
udevadm_test: ID_VENDOR_ID=0x1180
udevadm_test: ID_MODEL_ID=0x0476
udevadm_test: run: 'socket:@/org/freedesktop/hal/udev_event'

(ohje, ist das viel)

Was ist der "setserial"? ?(

Ich frag' mich gerade, warum der Rechner ab und zu nicht mehr hochfährt. Seit gestern bleibt er öfters mal gleich zu Beginn des Bootens mit blinkendem Cursor hängen. Sehr merkwürdig.

Viele Grüße
Micha
 
Was Du nicht geschrieben hast: hat mein vorgeschlagener Workaround mit chmod funktioniert?

Diese Outputzeile zeigt allerdings, daß udev die Rechte auf 660 setzt, nicht auf 600 wie Du zuvor schriebst:
Code: 
udev_node_add: creating device node '/dev/ttyS0', devnum=4:64, mode=0660, uid=0, gid=20
gid=20 ist dabei die Gruppe dialout. Ist dein User in dieser Gruppe? Zeig mal bitte
Code: 
ls -l /dev/ttyS0
und
Code: 
id
 
Danke erstmal für Deine grenzenlose Geduld! :thumbup:

Also: der Workaround mit dem chmod hat nicht funktioniert:
Anhang anzeigen 31527

Nein, nach einem Neustart sind die Rechte auf 600:
Anhang anzeigen 31528
Das Kreuz über dem Icon ganz link bedeutet doch auch nichts gutes?!

Erster Befehl:
Code: 
micha@t61:~$ ls -l /dev/ttyS0
crw------- 1 root root 4, 64 2010-06-29 19:47 /dev/ttyS0
micha@t61:~$

Zweiter Befehl:
Code: 
micha@t61:~$ id
uid=1000(micha) gid=1000(micha) Gruppen=4(adm),5(tty),20(dialout),24(cdrom),46(plugdev),105(lpadmin),119(admin),122(sambashare),1000(micha),1001(fingerprint),1002(kismet)
micha@t61:~$

Viele Grüße
Micha
 

Anhänge

  • ttyS0permissiondenied.png
    ttyS0permissiondenied.png
    98,3 KB · Aufrufe: 7
  • ttyS0-600.png
    ttyS0-600.png
    40,6 KB · Aufrufe: 5
Also nochmal von vorn und bitte den Output beider Kommandos zeigen:
Code: 
sudo chmod 660 /dev/ttyS0
ls -l /dev/ttyS0
Danach GPS-Babel starten.

ps. Screenshots von den Rechten brauch ich nicht, dazu ist das ls-Statement da.
 
So, habe frisch gebootet, hier sind die Ergebnisse vor und nach dem chmod:
Code: 
micha@t61:~$ ls -l /dev/ttyS0
crw------- 1 root root 4, 64 2010-06-29 20:07 /dev/ttyS0
micha@t61:~$ sudo chmod 660 /dev/ttyS0
Password or swipe finger: 
micha@t61:~$ ls -l /dev/ttyS0
crw-rw---- 1 root root 4, 64 2010-06-29 20:07 /dev/ttyS0
micha@t61:~$

GPSBabel bringt weiterhin diesen Fehler:
Code: 
Die exakte Fehlermeldung von Gpsbabel lautete:
[ERROR] XSERIAL: Cannot open serial port '/dev/ttyS0': Permission denied
[ERROR] Cannot open serial port '/dev/ttyS0'
GARMIN:Can't init /dev/ttyS0

Gruß
Micha
 
Probier bitte nochmal, jedoch mit
Code: 
sudo chmod 666 /dev/ttyS0
 
Ok:
Code: 
micha@t61:~$ sudo chmod 666 /dev/ttyS0
micha@t61:~$ ls -l /dev/ttyS0
crw-rw-rw- 1 root root 4, 64 2010-06-29 20:19 /dev/ttyS0
micha@t61:~$

Jetzt läuft Gpsbabel immerhin kurz an, nach wenigen Sekunden kommt dann diese Fehlermeldung:
Code: 
Gpsbabel hat ein Problem festgestellt.
Initialisierung nicht möglich.

Die exakte Fehlermeldung von Gpsbabel lautete:
[ERROR] GPS_Packet_Read: Timeout.  No data received.
GARMIN:Can't init /dev/ttyS0

Gruß
Micha
 
Installiere das Paket setserial und zeig
Code: 
setserial -g -a /dev/ttyS0
 
Kein Problem...

Code: 
micha@t61:~$ setserial -g -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16750, Port: 0x8100, IRQ: 16
	Baud_base: 115200, close_delay: 50, divisor: 0
	closing_wait: 3000
	Flags: spd_normal skip_test

micha@t61:~$

Gruß
Micha
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
  • ok1.de
  • ok2.de
  • thinkstore24.de
  • Preiswerte-IT - Gebrauchte Lenovo Notebooks kaufen

Werbung

Zurück
Oben