Beiträge von Oli_K76

Hallo nokia2,

die Box hat keine tasten mehr, nur touch.
Anbei der Output der Konsole:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2020.08.06 17:20:20 =~=~=~=~=~=~=~=~=~=~=~=
CPU 01
Dreambox DM920


AVS init...
AVS init OK
AVS load:select_image: addr_offset: 00051000 part_offset: 00000000 bootStatus: 2a002b00
AVS load_code offset =00051000
LOADED
AVS: overtemp mon ON


single board
select_image: addr_offset: 00055000 part_offset: 00000000 bootStatus: 3d2b2500
MEMSYS-STD
SHMOO 02010000 BLD:11138M HW:hpf0_b1p6 V:2.1.0.0
MCB: FLEX
AVS start:status=000000ff
STB: Current voltage=00000390(912)
 temperature=0000d502(54530)
 PV=0000034e(846)
 MV=00000390(912)
AVS FW rev=30333278 [0.3.2.x]
OK
DDR0: !@ ffe0e780 <= ffe0df10 MEMSYS-0 @ f1100000 OK
DDR1: =@ ffe0e780 <= ffe0df10 MEMSYS-1 @ f1180000 OK
Sdram Scramble OTP = 0x00000001 
Sdram Scramble OK
select_image: addr_offset: 00020000 part_offset: 00000000 bootStatus: 1b25252b
BFW load mode OTP = 0x0000000f 
bfw_hash_locked = 0x00000000 
BFW key3 OK, BFW load OK
BFW v2.1.0
COPY CODE... DONE
MICH: disable success
SSBL
PINMUX
CACHE FLUSH OK
MMU ...key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDHCGGlHWmO+15JfrcdP4CsV92UT1oQduCmYM1VeLM4uNFvSrX1cwXkVA96j5fRqS6gZ7eL6V527Wf4M2GV5xNtJdgPi7nDl/zVHv5FvJmFnNUY8yjJdNVIQuDD8h1qOwyBrsfAqZigIkHrP1V/Wp77Yut1W0CIvT+6lsyIXWnev14EovlM8Es1GFLi04vVcLS569ry18i50Z4PqKNsyMvkivDxMFP2GMUOFiYLQW1E29jXn64Dzb/anAguANjBKMiX9XyeClx5rpd0I/u1GS5NhHW4Rt8qAqqsT8tfWta2RxTTqraOVn/VMb6GIL9HB60bMmnxjdklTF8bF60kGIvH root@dm920
Fingerprint: md5 54:5c:c1:1f:9e:a2:45:22:d7:bc:4f:63:31:60:f9:32
dropbear.
Starting autoflashd.
Starting recovery-ui.
Starting tpmd.
Starting internet superserver: xinetd.
[   13.196052] random: nonblocking pool is initialized
Starting Lighttpd Web Server: lighttpd.
2017-11-07 20:06:34: (../../lighttpd-1.4.39/src/log.c.194) server started 




opendreambox 2.5.0 dm920 /dev/ttyS0






>>> Your Dreambox has booted into RESCUE MODE.


>>> Please log in as user 'root' (no password required),


>>> then run 'help' to get further information.


dm920 login:

So wie ich vermutet habe:
Normal bootup
Default boot device not found!
Booting failed. Running recovery

Kann jemand helfen?

Besten Dank

Grüße
Olli

Also Images zu flashen versucht habe ich oZZooN, Gemini und Original.

bootlog ist leider leer:

root@dm920:~# ls -laF /var/log/
drwxr-xr-x    2 root     root           100 Jan  1  1970 ./
drwxr-xr-x    5 root     root           100 Jan  1  1970 ../
-rw-r--r--    1 root     root             0    Jan  1  1970 boot
-rw-r--r--    1 root     root         20963 Jan  1  1970 dmesg
-rw-rw-r--    1 root     root          3072 Nov  7 20:12 wtmp

Aber in dmesg habe ich was gefunden:

[    0.586039] ALSA device list:
[    0.586044]   No soundcards found.
[    0.586091] Warning: unable to open an initial console.
[    0.647141] mmc1: BKOPS_EN bit is not set
[    0.656966] mmc1: new high speed MMC card at address 0001
[    0.657337] mmcblk0: mmc1:0001 8GME4R 7.28 GiB
[    0.657460] mmcblk0boot0: mmc1:0001 8GME4R partition 1 4.00 MiB
[    0.657558] mmcblk0boot1: mmc1:0001 8GME4R partition 2 4.00 MiB
[    0.657671] mmcblk0rpmb: mmc1:0001 8GME4R partition 3 512 KiB
[    0.662331]  mmcblk0: p1 p2 p3
[    0.665653]  mmcblk0boot1: unknown partition table
[    0.666395]  mmcblk0boot0: unknown partition table
[    0.687569] systemd-udevd[95]: starting version 230
[    0.689505] random: systemd-udevd: uninitialized urandom read (16 bytes read, 28 bits of entropy available)
[    0.689855] random: systemd-udevd: uninitialized urandom read (16 bytes read, 28 bits of entropy available)
[    0.689903] random: systemd-udevd: uninitialized urandom read (16 bytes read, 28 bits of ent...18]: failed to execute '/lib/systemd/systemd-sysctl' '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/eth0 --prefix=/net/ipv4/neigh/eth0 --prefix=/net/ipv6/conf/eth0 --prefix=/net/ipv6/neigh/eth0': No su
ch file or directory
[    0.860530] systemd-udevd[106]: Process '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/eth0 --prefix=/net/ipv4/neigh/eth0 --prefix=/net/ipv6/conf/eth0 --prefix=/net/ipv6/neigh/eth0' failed with exit code 2.
[    0.915965] systemd-udevd[119]: failed to execute '/lib/systemd/systemd-vconsole-setup' '/lib/systemd/systemd-vconsole-setup': No such file or directory
[    0.916581] systemd-udevd[106]: Process '/lib/systemd/systemd-vconsole-setup' failed with exit code 2.
[    1.020712] bcmdriver: module license 'Proprietary' taints kernel.
[    1.020722] Disabling lock debugging due to kernel taint
[    1.021125] BCMDRV: Initializing bcmdriver version $ 8
[    1.021137] BCMDRV: Total intc words=4,Total Irqs=129
[    1.021815] BCMDRV: Initialization complete

So wie es aussieht ist das Boot Device dahin.

root@dm920:~# fsck.ext4 /dev/mmcblk0p2
e2fsck 1.43-WIP (18-May-2015)
dreambox-rootfs: clean, 14795/63488 files, 100416/253952 blocks


root@dm920:~# fsck.ext4 /dev/mmcblk0p3
e2fsck 1.43-WIP (18-May-2015)
dreambox-data: clean, 17/412080 files, 82298/1646587 blocks


root@dm920:~# mount /dev/mmcblk0p2 /data/


root@dm920:~# ls -alF /data/
drwxr-xr-x   19 root     root          4096 Nov  7  2017 ./
drwxr-xr-x   19 root     root             0 Nov  7 20:13 ../
drwxr-xr-x    2 root     root          4096 Nov  7  2017 bin/
drwxr-xr-x    2 root     root          4096 Nov  7  2017 boot/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 dev/
drwxr-xr-x   45 root     root          4096 Nov  7  2017 etc/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 home/
drwxr-xr-x    8 root     root          4096 Nov  7  2017 lib/
drwx------    2 root     root         16384 Nov  7  2017 lost+found/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 media/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 mnt/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 proc/
drwx------    2 root     root          4096 Apr 20  2018 root/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 run/
drwxr-xr-x    2 root     root          4096 Nov  7  2017 sbin/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 sys/
drwxrwxrwt    2 root     root          4096 Apr 20  2018 tmp/
drwxr-xr-x   10 root     root          4096 Nov  7  2017 usr/
drwxr-xr-x    8 root     root          4096 Nov  7  2017 var/


root@dm920:~# ls -alF /data/boot/
drwxr-xr-x    2 root     root          4096 Nov  7  2017 ./
drwxr-xr-x   19 root     root          4096 Nov  7  2017 ../
-rw-r--r--    1 root     root         48398 Apr 20  2018 devicetree-zImage-dreambox-dm900.dtb
lrwxrwxrwx    1 root     root            36 Nov  7  2017 dreambox-dm900.dtb -> /etc/alternatives/dreambox-dm900.dtb
lrwxrwxrwx    1 root     root            24 Nov  7  2017 zImage -> /etc/alternatives/zImage
-rw-r--r--    1 root     root       4248912 Apr 20  2018 zImage-3.14-1.17-dm920

root@dm920:~# fdisk /dev/mmcblk0
Found valid GPT with protective MBR; using GPT




Command (m for help): p
Disk /dev/mmcblk0: 15269888 sectors, 3360M
Logical sector size: 512
Disk identifier (GUID): 88250523-0901-4fe5-96ea-e2a7b9cc409c
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15269854


Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048           65535       31.0M   0700  kernel
   2           65536         2097151        992M   0700  rootfs
   3         2097152        15269854       6431M   0700  data


Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy


root@dm920:~# fdisk /dev/mmcblk0boot0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.




Command (m for help): q


root@dm920:~# fdisk /dev/mmcblk0boot1
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.




Command (m for help): q




root@dm920:~# mount /dev/mmcblk0boot0 /data/
mount: /dev/mmcblk0boot0 is write-protected, mounting read-only
mount: unknown filesystem type


root@dm920:~# mount /dev/mmcblk0boot1 /data/
mount: /dev/mmcblk0boot1 is write-protected, mounting read-only
mount: unknown filesystem type

Ich denke, dass der bootloader das boot Device nicht mounten kann. Wahrscheinlich muss ich doch mit der Console ran um zu sehen was passiert.
Das Rescue System schreibt ja nur in die Datenpartitionen, Partitionstabellen erstellt er dabei nicht. Gibt es hierzu ein Workaround oder kann mir jemand sagen wie die Bootpartitionen aussehen müssen?

Vielleicht liege ich auch falsch und es gibt noch einen anderen Ansatz?

Danke

Hallo Zusammen,

leider bootet meine DM920 seit heute in den Rescue Mode. Es hat sich bereits abgezeichnet weil z.B. EPG nicht mehr gespeichert wurde, etc.

Laut Log wird sie auch geflashed, meine Erachtens auch alles sauber auf die richtigen Partitionen, aber sie geht trotzdem wieder in den Rescue Mode. Habe auch verschiedene Images und normales Recovery versucht:

[*] Remounting '/dev/mmcblk0p3' to '/data'
[*] Downloading 'http://dreamboxupdate.com/download/recovery/dm920/release/recovery.sig'
[*] Copying 'recovery' from local storage
[*] Verifying signature of 'recovery'
gpgv: Signature made Mon Dec 11 21:41:43 2017 UTC using RSA key ID B3C5B1A3
gpgv: Good signature from "Dreambox DM920 Recovery <dm920@recovery.dreambox.de>"
[*] Unmounting '/data'
[*] Running './recovery'
[*] Options '-v'
[*] Mounting '/dev/mmcblk0p3' to '/data'
[*] Downloading 'http://dreamboxupdate.com/download/recovery/dm920/release/dreambox-image-dm920.tar.xz.sig'
[*] Copying 'dreambox-image-dm920.tar.xz' from local storage
[*] Verifying signature of 'dreambox-image-dm920.tar.xz'
gpgv: Signature made Thu Nov 14 16:42:13 2019 UTC using RSA key ID B3C5B1A3
gpgv: Good signature from "Dreambox DM920 Recovery <dm920@recovery.dreambox.de>"
[*] Creating ext4 filesystem 'dreambox-rootfs' on /dev/mmcblk0p2
mke2fs 1.43-WIP (18-May-2015)
Discarding device blocks:   4096/253952             done                            
Creating filesystem with 253952 4k blocks and 63488 inodes
Filesystem UUID: 44ce5a99-e9f5-4fa0-b8d7-ab6f30adddf1
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376


Allocating group tables: 0/8   done                            
Writing inode tables: 0/8   done                            
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/8   done


[*] Mounting '/dev/mmcblk0p2' to '/mnt'
[*] Extracting 'dreambox-image-dm920.tar.xz' to '/mnt'
[*] Mounting '/dev' to '/mnt/dev'
[*] Mounting '/proc' to '/mnt/proc'
[*] Mounting '/run' to '/mnt/run'
[*] Mounting '/sys' to '/mnt/sys'
[*] Mounting '/tmp' to '/mnt/tmp'
update-alternatives: error: cannot append to '/var/log/alternatives.log': No such file or directory
[*] Writing /boot/zImage-3.14-1.17-dm920 to /dev/mmcblk0p1
64+1 records in
64+1 records out
4248912 bytes (4.1MB) copied, 1.942312 seconds, 2.1MB/s
[*] Unmounting '/mnt/dev'
[*] Unmounting '/mnt/proc'
[*] Unmounting '/mnt/run'
[*] Unmounting '/mnt/sys'
[*] Unmounting '/mnt/tmp'
[*] Unmounting '/mnt'
[*] Unmounting '/data'
[*] Finished successfully. You may reboot now.
[*] Initiating reboot

Das sieht eigentlich alles gut aus, dies irritiert ein wenig, habe ich so unter Linux noch nicht wahrgenommen "Discarding device blocks: 4096/253952"

Dass kein /var/log/alternatives.log vorhanden ist, sollte eigentlich auch kein Problem sein, habe es aber auch mal angelegt ohne Unterschied.

root@dm920:~# blkid
/dev/mmcblk0: PTUUID="88250523-0901-4fe5-96ea-e2a7b9cc409c" PTTYPE="gpt"
/dev/mmcblk0p1: PARTLABEL="kernel" PARTUUID="ed288b57-3a2a-48ac-9fd8-af839664b4cf"
/dev/mmcblk0p2: LABEL="dreambox-rootfs" UUID="5fd2e976-36ba-4934-8b48-054a4032dd65" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="7e4551e2-1959-4d0d-8902-fd2e690e74c3"
/dev/mmcblk0p3: LABEL="dreambox-data" UUID="4659a3e8-c50b-4660-9165-8704436cc5a6" TYPE="ext4" PARTLABEL="data" PARTUUID="6b06369f-e834-4cd1-a83c-a54e821c3e86"

Ich werde mich aber auch mal seriel verbinden um mir die Ausgabe mal auf die Konsole zu holen.

Hat jemand gerade einen Ansatzpunkt bevor ich an ein USB recovery gehe?
https://board.newnigma2.to/wbb…M920-DM7080-USB-Recovery/

Besten Dank

Grüße
Oli_K76

Hallo,

ich habe gerade das neue OoZooN-Image 3.0 getestet.
Natürlich habe ich wieder das Problem mit dem ftdi_sio Modul.

Wenn ich das Modul per modprobe laden will, kommt immer "modprobe: module ftdi_si not found in modules.dep"

Ich muss diesen Weg gehen:
insmod /lib/modules/2.6.18-7.4-dm800/kernel/drivers/usb/serial/usbserial.ko
modeprobe usbserial
insmod /lib/modules/2.6.18-7.4-dm800/kernel/drivers/usb/serial/ftdi_sio.ko
modprobe ftdi_sio

Dies habe ich jetzt in der /etc/init.d/bootup eingetragen und es funzt.
Anderweitig läd er nicht das ftdi_sio Modul und erstellt den Link zum Atmolight nicht.

Gibt es hier nicht einen anderen Weg?

Besten Dank

Gruß
Oli_K76

Hallo Mamba,

leider nach wie vor das Selbe:
root@dm800:~# opkg install kernel-module-ftdi-sio
Package kernel-module-ftdi-sio (2.6.18-r5.0) installed in root is up to date.

root@dm800:~# ipkg install kernel-module-ftdi-sio
Package kernel-module-ftdi-sio (2.6.18-r5.0) installed in root is up to date.

Muss ich die Kernelmodule erst noch aktivieren?

root@dm800:~# dmesg | grep usb
drivers/usb/host/ehci-brcm.c: starting brcm EHCI USB Controller
usb usb1: configuration #1 chosen from 1 choice
drivers/usb/host/ohci-brcm.c: starting brcm OHCI USB Controller
usb usb2: configuration #1 chosen from 1 choice
drivers/usb/host/ohci-brcm.c: starting brcm OHCI USB Controller
usb usb3: configuration #1 chosen from 1 choice
usb 1-2: new high speed USB device using brcm-ehci and address 2
usb 1-2: configuration #1 chosen from 1 choice
usbcore: registered new driver usb-storage
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete

usb 2-1: new full speed USB device using brcm-ohci-0 and address 2
usb 2-1: configuration #1 chosen from 1 choice

Aktuell teste ich mit Gemini 5.1 im Multiboot BA + WW von einem USB-Stick. Gestern habe ich auch noch den Bootprozess nach Anleitung beschleunigt.
atmolightd-dm800-0.3j.tar.gz
atmolight_plugin_OE1.6.zip
DM 800
600 GB Samsung
2 GB Transcend USB-Stick

Syslog bekomme ich grad nicht zum Laufen, versuche es morgen weiter.

Noch irgendwelche Ideen?

Besten Dank

Gruß
Oli

Hallo,

bekomme es leider nicht zum Laufen.
Ich habe den Controller von Carsten Presser, dazu entsprechende LED-Leisten.
Ich vermute dass er den USB-Controller nicht ansteuern kann.
Aktuellstes OoZooN-Image auf Dreambox 800.

Bei mir gibt es weder /dev/usb/tts/0 noch /dev/ttyUSB0

root@dm800:~# ls -alF /dev/
drwxr-xr-x 18 root root 4520 Sep 26 12:44 ./
drwxr-xr-x 16 root root 1024 Sep 26 04:44 ../
drwxr-xr-x 5 root root 120 Sep 26 12:40 .udev/
lrwxrwxrwx 1 root root 9 Jan 1 2000 MAKEDEV -> /bin/true*
lrwxrwxrwx 1 root root 4 Jan 1 2000 XOR -> null
crw-rw---- 1 root audio 14, 4 Jan 1 2000 audio
drwxr-xr-x 3 root root 60 Jan 1 2000 bus/
crw------- 1 root root 5, 1 Jan 1 2000 console
lrwxrwxrwx 1 root root 11 Jan 1 2000 core -> /proc/kcore
drwxr-xr-x 2 root root 60 Jan 1 2000 dbox/
drwxr-xr-x 5 root root 100 Jan 1 2000 disk/
crw-rw---- 1 root audio 14, 3 Jan 1 2000 dsp
drwxr-xr-x 3 root root 60 Jan 1 2000 dvb/
drwxr-xr-x 2 root root 60 Jan 1 2000 fb/
crw-rw---- 1 root video 29, 0 Jan 1 2000 fb0
lrwxrwxrwx 1 root root 13 Jan 1 2000 fd -> /proc/self/fd/
crw-rw-rw- 1 root root 1, 7 Jan 1 2000 full
drwxr-xr-x 2 root root 140 Jan 1 2000 i2c/
crw-rw---- 1 root root 89, 0 Jan 1 2000 i2c-0
crw-rw---- 1 root root 89, 1 Jan 1 2000 i2c-1
crw-rw---- 1 root root 89, 2 Jan 1 2000 i2c-2
crw-rw---- 1 root root 89, 3 Jan 1 2000 i2c-3
crw-rw---- 1 root root 89, 4 Jan 1 2000 i2c-4
prw------- 1 root root 0 Sep 26 12:34 initctl|
drwxr-xr-x 2 root root 140 Jan 1 2000 input/
crw-r----- 1 root kmem 1, 2 Jan 1 2000 kmem
crw-rw---- 1 root root 1, 11 Jan 1 2000 kmsg
srw-rw-rw- 1 root root 0 Jan 1 2000 log=
drwxr-xr-x 2 root root 60 Jan 1 2000 loop/
crw-r----- 1 root kmem 1, 1 Jan 1 2000 mem
drwxr-xr-x 2 root root 80 Jan 1 2000 misc/
crw-rw---- 1 root audio 14, 0 Jan 1 2000 mixer
crw-rw---- 1 root root 90, 0 Jan 1 2000 mtd0
crw-rw---- 1 root root 90, 1 Jan 1 2000 mtd0ro
crw-rw---- 1 root root 90, 2 Jan 1 2000 mtd1
crw-rw---- 1 root root 90, 3 Jan 1 2000 mtd1ro
crw-rw---- 1 root root 90, 4 Jan 1 2000 mtd2
crw-rw---- 1 root root 90, 5 Jan 1 2000 mtd2ro
crw-rw---- 1 root root 90, 6 Jan 1 2000 mtd3
crw-rw---- 1 root root 90, 7 Jan 1 2000 mtd3ro
drwxr-xr-x 2 root root 120 Jan 1 2000 mtdblock/
brw-r----- 1 root disk 31, 0 Jan 1 2000 mtdblock0
brw-r----- 1 root disk 31, 1 Jan 1 2000 mtdblock1
brw-r----- 1 root disk 31, 2 Jan 1 2000 mtdblock2
brw-r----- 1 root disk 31, 3 Jan 1 2000 mtdblock3
drwxr-xr-x 2 root root 60 Jan 1 2000 net/
crw-rw-rw- 1 root root 1, 3 Jan 1 2000 null
crw-r----- 1 root kmem 1, 4 Jan 1 2000 port
crw------- 1 root root 108, 0 Jan 1 2000 ppp
crw-rw-rw- 1 root tty 5, 2 Sep 26 14:33 ptmx
drwxr-xr-x 2 root root 0 Jan 1 2000 pts/
crw-rw-rw- 1 root root 1, 8 Jan 1 2000 random
crw-rw---- 1 root root 10, 62 Jan 1 2000 sci0
brw-r----- 1 root disk 8, 0 Jan 1 2000 sda
brw-r----- 1 root disk 8, 1 Jan 1 2000 sda1
brw-r----- 1 root floppy 8, 16 Jan 1 2000 sdb
brw-r----- 1 root floppy 8, 17 Jan 1 2000 sdb1
brw-r----- 1 root floppy 8, 26 Jan 1 2000 sdb10
brw-r----- 1 root floppy 8, 27 Jan 1 2000 sdb11
brw-r----- 1 root floppy 8, 28 Jan 1 2000 sdb12
brw-r----- 1 root floppy 8, 18 Jan 1 2000 sdb2
brw-r----- 1 root floppy 8, 19 Jan 1 2000 sdb3
brw-r----- 1 root floppy 8, 21 Jan 1 2000 sdb5
brw-r----- 1 root floppy 8, 22 Jan 1 2000 sdb6
brw-r----- 1 root floppy 8, 23 Jan 1 2000 sdb7
brw-r----- 1 root floppy 8, 24 Jan 1 2000 sdb8
brw-r----- 1 root floppy 8, 25 Jan 1 2000 sdb9
crw-r----- 1 root disk 21, 0 Jan 1 2000 sg0
crw-r----- 1 root disk 21, 1 Jan 1 2000 sg1
drwxr-xr-x 2 root root 40 Jan 1 2000 shm/
drwxr-xr-x 2 root root 100 Jan 1 2000 snd/
lrwxrwxrwx 1 root root 24 Jan 1 2000 sndstat -> /proc/asound/oss/sndstat
lrwxrwxrwx 1 root root 15 Jan 1 2000 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root root 15 Jan 1 2000 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root root 15 Jan 1 2000 stdout -> /proc/self/fd/1
crw-rw---- 1 root root 10, 61 Jan 1 2000 tpm0
crw-rw-rw- 1 root tty 5, 0 Jan 1 2000 tty
crw--w---- 1 root tty 4, 0 Sep 26 14:33 tty0
crw--w---- 1 root tty 4, 1 Jan 1 2000 tty1
crw--w---- 1 root tty 4, 10 Jan 1 2000 tty10
crw--w---- 1 root tty 4, 11 Jan 1 2000 tty11
crw--w---- 1 root tty 4, 12 Jan 1 2000 tty12
crw--w---- 1 root tty 4, 13 Jan 1 2000 tty13
crw--w---- 1 root tty 4, 14 Jan 1 2000 tty14
crw--w---- 1 root tty 4, 15 Jan 1 2000 tty15
crw--w---- 1 root tty 4, 16 Jan 1 2000 tty16
crw--w---- 1 root tty 4, 17 Jan 1 2000 tty17
crw--w---- 1 root tty 4, 18 Jan 1 2000 tty18
crw--w---- 1 root tty 4, 19 Jan 1 2000 tty19
crw--w---- 1 root tty 4, 2 Jan 1 2000 tty2
crw--w---- 1 root tty 4, 20 Jan 1 2000 tty20
crw--w---- 1 root tty 4, 21 Jan 1 2000 tty21
crw--w---- 1 root tty 4, 22 Jan 1 2000 tty22
crw--w---- 1 root tty 4, 23 Jan 1 2000 tty23
crw--w---- 1 root tty 4, 24 Jan 1 2000 tty24
crw--w---- 1 root tty 4, 25 Jan 1 2000 tty25
crw--w---- 1 root tty 4, 26 Jan 1 2000 tty26
crw--w---- 1 root tty 4, 27 Jan 1 2000 tty27
crw--w---- 1 root tty 4, 28 Jan 1 2000 tty28
crw--w---- 1 root tty 4, 29 Jan 1 2000 tty29
crw--w---- 1 root tty 4, 3 Jan 1 2000 tty3
crw--w---- 1 root tty 4, 30 Jan 1 2000 tty30
crw--w---- 1 root tty 4, 31 Jan 1 2000 tty31
crw--w---- 1 root tty 4, 32 Jan 1 2000 tty32
crw--w---- 1 root tty 4, 33 Jan 1 2000 tty33
crw--w---- 1 root tty 4, 34 Jan 1 2000 tty34
crw--w---- 1 root tty 4, 35 Jan 1 2000 tty35
crw--w---- 1 root tty 4, 36 Jan 1 2000 tty36
crw--w---- 1 root tty 4, 37 Jan 1 2000 tty37
crw--w---- 1 root tty 4, 38 Jan 1 2000 tty38
crw--w---- 1 root tty 4, 39 Jan 1 2000 tty39
crw--w---- 1 root tty 4, 4 Jan 1 2000 tty4
crw--w---- 1 root tty 4, 40 Jan 1 2000 tty40
crw--w---- 1 root tty 4, 41 Jan 1 2000 tty41
crw--w---- 1 root tty 4, 42 Jan 1 2000 tty42
crw--w---- 1 root tty 4, 43 Jan 1 2000 tty43
crw--w---- 1 root tty 4, 44 Jan 1 2000 tty44
crw--w---- 1 root tty 4, 45 Jan 1 2000 tty45
crw--w---- 1 root tty 4, 46 Jan 1 2000 tty46
crw--w---- 1 root tty 4, 47 Jan 1 2000 tty47
crw--w---- 1 root tty 4, 48 Jan 1 2000 tty48
crw--w---- 1 root tty 4, 49 Jan 1 2000 tty49
crw--w---- 1 root tty 4, 5 Jan 1 2000 tty5
crw--w---- 1 root tty 4, 50 Jan 1 2000 tty50
crw--w---- 1 root tty 4, 51 Jan 1 2000 tty51
crw--w---- 1 root tty 4, 52 Jan 1 2000 tty52
crw--w---- 1 root tty 4, 53 Jan 1 2000 tty53
crw--w---- 1 root tty 4, 54 Jan 1 2000 tty54
crw--w---- 1 root tty 4, 55 Jan 1 2000 tty55
crw--w---- 1 root tty 4, 56 Jan 1 2000 tty56
crw--w---- 1 root tty 4, 57 Jan 1 2000 tty57
crw--w---- 1 root tty 4, 58 Jan 1 2000 tty58
crw--w---- 1 root tty 4, 59 Jan 1 2000 tty59
crw--w---- 1 root tty 4, 6 Jan 1 2000 tty6
crw--w---- 1 root tty 4, 60 Jan 1 2000 tty60
crw--w---- 1 root tty 4, 61 Jan 1 2000 tty61
crw--w---- 1 root tty 4, 62 Jan 1 2000 tty62
crw--w---- 1 root tty 4, 63 Jan 1 2000 tty63
crw--w---- 1 root tty 4, 7 Jan 1 2000 tty7
crw--w---- 1 root tty 4, 8 Jan 1 2000 tty8
crw--w---- 1 root tty 4, 9 Jan 1 2000 tty9
crw-rw---- 1 root dialout 4, 64 Jan 1 2000 ttyS0
crw-rw---- 1 root dialout 4, 65 Jan 1 2000 ttyS1
crw-rw---- 1 root dialout 4, 74 Jan 1 2000 ttyS10
crw-rw---- 1 root dialout 4, 75 Jan 1 2000 ttyS11
crw-rw---- 1 root dialout 4, 76 Jan 1 2000 ttyS12
crw-rw---- 1 root dialout 4, 77 Jan 1 2000 ttyS13
crw-rw---- 1 root dialout 4, 78 Jan 1 2000 ttyS14
crw-rw---- 1 root dialout 4, 79 Jan 1 2000 ttyS15
crw-rw---- 1 root dialout 4, 80 Jan 1 2000 ttyS16
crw-rw---- 1 root dialout 4, 81 Jan 1 2000 ttyS17
crw-rw---- 1 root dialout 4, 82 Jan 1 2000 ttyS18
crw-rw---- 1 root dialout 4, 83 Jan 1 2000 ttyS19
crw-rw---- 1 root dialout 4, 66 Jan 1 2000 ttyS2
crw-rw---- 1 root dialout 4, 84 Jan 1 2000 ttyS20
crw-rw---- 1 root dialout 4, 85 Jan 1 2000 ttyS21
crw-rw---- 1 root dialout 4, 86 Jan 1 2000 ttyS22
crw-rw---- 1 root dialout 4, 87 Jan 1 2000 ttyS23
crw-rw---- 1 root dialout 4, 88 Jan 1 2000 ttyS24
crw-rw---- 1 root dialout 4, 89 Jan 1 2000 ttyS25
crw-rw---- 1 root dialout 4, 90 Jan 1 2000 ttyS26
crw-rw---- 1 root dialout 4, 91 Jan 1 2000 ttyS27
crw-rw---- 1 root dialout 4, 92 Jan 1 2000 ttyS28
crw-rw---- 1 root dialout 4, 93 Jan 1 2000 ttyS29
crw-rw---- 1 root dialout 4, 67 Jan 1 2000 ttyS3
crw-rw---- 1 root dialout 4, 94 Jan 1 2000 ttyS30
crw-rw---- 1 root dialout 4, 95 Jan 1 2000 ttyS31
crw-rw---- 1 root dialout 4, 96 Jan 1 2000 ttyS32
crw-rw---- 1 root dialout 4, 97 Jan 1 2000 ttyS33
crw-rw---- 1 root dialout 4, 98 Jan 1 2000 ttyS34
crw-rw---- 1 root dialout 4, 99 Jan 1 2000 ttyS35
crw-rw---- 1 root dialout 4, 100 Jan 1 2000 ttyS36
crw-rw---- 1 root dialout 4, 101 Jan 1 2000 ttyS37
crw-rw---- 1 root dialout 4, 102 Jan 1 2000 ttyS38
crw-rw---- 1 root dialout 4, 103 Jan 1 2000 ttyS39
crw-rw---- 1 root dialout 4, 68 Jan 1 2000 ttyS4
crw-rw---- 1 root dialout 4, 104 Jan 1 2000 ttyS40
crw-rw---- 1 root dialout 4, 105 Jan 1 2000 ttyS41
crw-rw---- 1 root dialout 4, 106 Jan 1 2000 ttyS42
crw-rw---- 1 root dialout 4, 107 Jan 1 2000 ttyS43
crw-rw---- 1 root dialout 4, 108 Jan 1 2000 ttyS44
crw-rw---- 1 root dialout 4, 109 Jan 1 2000 ttyS45
crw-rw---- 1 root dialout 4, 110 Jan 1 2000 ttyS46
crw-rw---- 1 root dialout 4, 111 Jan 1 2000 ttyS47
crw-rw---- 1 root dialout 4, 112 Jan 1 2000 ttyS48
crw-rw---- 1 root dialout 4, 113 Jan 1 2000 ttyS49
crw-rw---- 1 root dialout 4, 69 Jan 1 2000 ttyS5
crw-rw---- 1 root dialout 4, 114 Jan 1 2000 ttyS50
crw-rw---- 1 root dialout 4, 115 Jan 1 2000 ttyS51
crw-rw---- 1 root dialout 4, 116 Jan 1 2000 ttyS52
crw-rw---- 1 root dialout 4, 117 Jan 1 2000 ttyS53
crw-rw---- 1 root dialout 4, 118 Jan 1 2000 ttyS54
crw-rw---- 1 root dialout 4, 119 Jan 1 2000 ttyS55
crw-rw---- 1 root dialout 4, 120 Jan 1 2000 ttyS56
crw-rw---- 1 root dialout 4, 121 Jan 1 2000 ttyS57
crw-rw---- 1 root dialout 4, 122 Jan 1 2000 ttyS58
crw-rw---- 1 root dialout 4, 123 Jan 1 2000 ttyS59
crw-rw---- 1 root dialout 4, 70 Jan 1 2000 ttyS6
crw-rw---- 1 root dialout 4, 124 Jan 1 2000 ttyS60
crw-rw---- 1 root dialout 4, 125 Jan 1 2000 ttyS61
crw-rw---- 1 root dialout 4, 126 Jan 1 2000 ttyS62
crw-rw---- 1 root dialout 4, 127 Jan 1 2000 ttyS63
crw-rw---- 1 root dialout 4, 71 Jan 1 2000 ttyS7
crw-rw---- 1 root dialout 4, 72 Jan 1 2000 ttyS8
crw-rw---- 1 root dialout 4, 73 Jan 1 2000 ttyS9
lrwxrwxrwx 1 root root 14 Sep 26 12:44 ttyUSB0 -> /dev/usb/tts/2@
-rw-r--r-- 1 root root 8 Jan 1 2000 udev_network_queue
crw-rw-rw- 1 root root 1, 9 Jan 1 2000 urandom
crw-rw---- 1 root root 442, 0 Jan 1 2000 usbdev1.1_ep00
crw-rw---- 1 root root 442, 0 Jan 1 2000 usbdev1.1_ep81
crw-rw---- 1 root root 442, 2 Jan 1 2000 usbdev1.3_ep00
crw-rw---- 1 root root 442, 2 Jan 1 2000 usbdev1.3_ep01
crw-rw---- 1 root root 442, 2 Jan 1 2000 usbdev1.3_ep82
crw-rw---- 1 root root 442, 2048 Jan 1 2000 usbdev2.1_ep00
crw-rw---- 1 root root 442, 2048 Jan 1 2000 usbdev2.1_ep81
crw-rw---- 1 root root 442, 2050 Sep 26 12:21 usbdev2.3_ep00
crw-rw---- 1 root root 442, 2050 Sep 26 12:21 usbdev2.3_ep02
crw-rw---- 1 root root 442, 2050 Sep 26 12:21 usbdev2.3_ep81
crw-rw---- 1 root root 442, 4096 Jan 1 2000 usbdev3.1_ep00
crw-rw---- 1 root root 442, 4096 Jan 1 2000 usbdev3.1_ep81
drwxr-xr-x 2 root root 1320 Jan 1 2000 vc/
crw-rw---- 1 root tty 7, 0 Jan 1 2000 vcs
crw-rw---- 1 root tty 7, 1 Jan 1 2000 vcs1
crw-rw---- 1 root tty 7, 128 Jan 1 2000 vcsa
crw-rw---- 1 root tty 7, 129 Jan 1 2000 vcsa1
crw-rw-rw- 1 root root 1, 5 Jan 1 2000 zero

Trotzdem verlinken vom nicht vorhandenen /dev/usb/tts/0 bzw. /dev/usb/tts/1 auf /dev/ttyUSB0 ?
Hier ist es auf /dev/usb/tts/2 verlinkt.

Kann ansonsten anbieten:
root@dm800:~# ls -alF /dev/bus/usb/
drwxr-xr-x 5 root root 100 Jan 1 2000 ./
drwxr-xr-x 3 root root 60 Jan 1 2000 ../
drwxr-xr-x 2 root root 80 Jan 1 2000 001/
drwxr-xr-x 2 root root 100 Sep 26 12:21 002/
drwxr-xr-x 2 root root 60 Jan 1 2000 003/

Nach einstecken des Controllers kommt folgender Eintrag dazu:
/dev/bus/usb/002/004

Aus- / Einstecken

dmesg:
usb 2-1: USB disconnect, address 4
usb 2-1: new full speed USB device using brcm-ohci-0 and address 5
usb 2-1: configuration #1 chosen from 1 choice

root@dm800:~# /dev/bus/usb/002/005

Wie steuere ich den Controller an?

Besten Dank

Gruß
Oli_K76