1 ... 16 17 [18] 19 20 ... 38 >>> Archiv / MLD 4.x / Raspberry PI / Test MLD-4 RPI tgz
 

Offline gkd-berlin

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 1402
    • View Profile
Test MLD-4 RPI tgz
« Reply #255 on: April 22, 2014, 21:27:01 »
Hallo,

Neuinstallation der MLD-4.0.0-rpi_rpi_2014.04.22-56.tar  vom 22.4. 1:27h

Kaltstart von SD-Karte:
Nach Hochfahren:
Code: [Select]
/var/log/sysinit

Searching for boot device: /
Boot device is: /dev/mmcblk0p1
...
modprobe: can't open 'modules.dep': No such file or directory             done
...
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for suspend:
* libcec *
* opkg_install_cmd: Cannot install package suspend.                       failed

Vom TV abgeschrieben:
Code: [Select]
Copy initramfs to tmpfs:
/etc/init.d/rc.sysinit: /etc/profile: line 13: /opt/vc/lib: Permission denied
Import filesystems
Die 2. Zeile fehlt in der Sysinit.

Keine Fehlermeldungen in der Messages:
Code: [Select]
/var/log/messages
Jan  1 00:02:34 (none) user.info kernel: [  154.963612] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input2
Jan  1 00:02:34 (none) user.info kernel: [  155.147221] input: lircd as /devices/virtual/input/input3
Es reagieren 7 Tasten auf der zum DVB-Stick mitgelieferten FB, aber völlig falsch.

Installation auf Festplatte
Nach 1. reboot
Die Sysinit ist leer !
In der Messages jede Menge Fehlermeldungen:
Code: [Select]
/var/log/messages
Jan  1 00:02:26 (none) syslog.info syslogd started: BusyBox v1.22.1
Jan  1 00:02:29 (none) user.info kernel: [  150.285702] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 00:02:29 (none) user.info kernel: [  150.333517] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input2
Jan  1 00:02:30 (none) user.info kernel: [  150.533530] input: lircd as /devices/virtual/input/input3
Jan  1 00:02:31 (none) user.info kernel: [  151.992857] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Jan  1 00:03:25 (none) user.info kernel: [  205.641479] btrfs: device fsid 597eaba3-43ef-424c-ab24-017901f58880 devid 1 transid 57 /dev/sda1
Jan  1 00:03:25 (none) user.info kernel: [  205.660299] btrfs: disk space caching is enabled
Jan  1 00:03:28 (none) user.notice kernel: [  209.291674] XFS (sda2): Mounting Filesystem
Jan  1 00:03:29 (none) user.info kernel: [  209.585342] XFS (sda2): Ending clean mount
Jan  1 01:04:15 (none) auth.info login[6822]: root login on 'tty2'
Jan  1 01:04:15 (none) auth.info login[6829]: root login on 'tty4'
Jan  1 01:04:15 (none) auth.info login[6821]: root login on 'tty1'
Jan  1 01:04:15 (none) auth.info login[6825]: root login on 'tty3'
Jan  1 00:09:31 (none) user.info kernel: [  572.263517] btrfs: device fsid 4dec4903-635a-498f-b38f-f309c439d413 devid 1 transid 4 /dev/sda1
Jan  1 00:09:31 (none) user.info kernel: [  572.276798] btrfs: disk space caching is enabled
Jan  1 00:09:31 (none) user.info kernel: [  572.398806] btrfs: creating UUID tree
Jan  1 00:09:32 (none) user.info kernel: [  572.704108] btrfs: setting 2 feature flag
Jan  1 01:00:16 (none) syslog.info syslogd started: BusyBox v1.22.1
Jan  1 01:00:20 (none) user.info kernel: [   21.830792] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input2
Jan  1 01:00:21 (none) user.info kernel: [   22.554038] input: lircd as /devices/virtual/input/input3
Jan  1 01:00:22 (none) user.info kernel: [   23.633892] input: Sundtek Ltd. Remote Control (lircd bypass) as /devices/virtual/input/input4
Jan  1 01:00:23 (none) user.info kernel: [   24.586671] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 01:00:25 (none) user.info kernel: [   26.102226] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Apr 22 18:48:40 (none) user.err vdr: [1975] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 22 18:48:40 (none) user.err vdr: [1975] ERROR: remote control LIRC not ready!
Apr 22 18:48:40 (none) user.err vdr: [2004] ERROR: lircd connection broken, trying to reconnect every 3,0 seconds
Apr 22 18:48:43 (none) user.err vdr: [2004] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 22 18:48:46 (none) user.err vdr: [2004] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 22 18:48:49 (none) user.err vdr: [2004] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 22 18:48:52 (none) user.err vdr: [2004] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
und immer so weiter.

Nach 2. reboot
Code: [Select]
/var/log/sysinit
Import filesystems:
Turn on DMA:
Checking:
Btrfs Btrfs v0.19
done
Mounting:
done
Setting up logging: level 1
Setting up netware:
done
btrfs:                 
locales:                 
Setting timezone:
done
Load keymap: de-latin1
done

ntp-client:                 
rpi:                 
network:                 
eventlircd:                 
Starting eventlircd
done

Init networking
Starting DHCP-client
done
done
Starting ntp client:
22 Apr 19:12:00 ntpdate[1771]: step time server 5.9.80.114 offset 1398186679.299177 sec
done
vdr:                 
lirc:                 
Starting VDR
done
opkg:                 
alsa:                 
hdparm:                 
irxevent:                 
irexec:                 
ntfs-3g:                 
sensors:                 
ssh:                 
devmon:                 
vdr-plugin-opkg:                 
setup:                 
vdradmin-am:                 
webserver:                 
# Sensors

Starting devmon
done
Setting up storage devices
done
[2206] Apr 22 19:12:25 Running in background
Init sound card:
Restore sound settings:
done

Starting sshd:
Listen on IP: 192.168.2.101
done
Starting webserver:
done

[2616] Apr 22 19:12:57 Child connection from 192.168.2.102:1675
[2616] Apr 22 19:13:03 Password auth succeeded for 'root' from 192.168.2.102:1675
Starting vdradmin server:
done

In der Messages wieder Fehlermeldungen:
Code: [Select]
/var/log/messages
Jan  1 01:00:16 (none) syslog.info syslogd started: BusyBox v1.22.1
Jan  1 01:00:21 (none) user.info kernel: [   21.823767] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input2
Jan  1 01:00:21 (none) user.info kernel: [   22.613852] input: lircd as /devices/virtual/input/input3
Jan  1 01:00:22 (none) user.info kernel: [   23.695302] input: Sundtek Ltd. Remote Control (lircd bypass) as /devices/virtual/input/input4
Jan  1 01:00:23 (none) user.info kernel: [   24.346211] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 01:00:25 (none) user.info kernel: [   25.893125] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Apr 22 19:12:11 (none) user.err vdr: [1967] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 22 19:12:11 (none) user.err vdr: [1967] ERROR: remote control LIRC not ready!
Apr 22 19:12:11 (none) user.err vdr: [1996] ERROR: lircd connection broken, trying to reconnect every 3,0 seconds
Apr 22 19:12:14 (none) user.err vdr: [1996] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 22 19:12:17 (none) user.err vdr: [1996] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 22 19:12:20 (none) user.err vdr: [1996] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 22 19:12:23 (none) user.err vdr: [1996] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 22 19:12:26 (none) user.err vdr: [1996] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 22 19:12:29 (none) user.err vdr: [1996] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
usw.
Die /var/log/vdr ist immer leer.
Ich glaube, beim Herunterfahren nach dem 1. reboot, erscheinen 3 Fehlermeldungen. Zeile 50 ... in rc.----- mehr konnte ich mir nicht merken. Vielleicht liegt es daran.

WIN-TV-Fernbedienung an GPIO:
Meine lircd.conf nach /etc kopiert
In der rc.config steht jetzt:
Code: [Select]
# Lirc Aufruf Argumente
LIRC_ARGS=""
# Lirc modul to use
LIRC_MODUL="rpi on GPIO"
Code: [Select]
MLD> evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      HID 04d9:1400
/dev/input/event1:      HID 04d9:1400
/dev/input/event2:      Sundtek Ltd. Remote Control
/dev/input/event3:      lircd
/dev/input/event4:      Sundtek Ltd. Remote Control (lircd bypass)
Select the device event number [0-4]: 3
K e i n e Reaktion    Ist aber egal, es funktioniert ja.

irw gestartet:
Code: [Select]
MLD> irw
00000000000017e0 00 KEY_UP lircd.conf
00000000000017e1 00 KEY_DOWN lircd.conf
00000000000017e1 01 KEY_DOWN lircd.conf
00000000000017d0 00 KEY_RIGHT lircd.conf
Hurra es läuft und läuft.

Nun muß ich nur noch ein wenig die Tastenbelegung nach meinen Wünschen abändern.
Wenn ich noch einmal eine lircd.conf anlegen will, klappt das nicht mehr.
Mit:
Code: [Select]
MLD> irrecord -n lircd.conf -d /dev/lirc0

irrecord -  application for recording IR-codes for usage with lirc

Copyright (C) 1998,1999 Christoph Bartelmus(lirc@bartelmus.de)

irrecord: could not open /dev/lirc0
irrecord: default_init(): Device or resource busy
irrecord: could not init hardware (lircd running ? --> close it, check permissions)

Nach einem stop lirc fehlt lirc_rpi.
Code: [Select]
MLD> lsmod
Module                  Size  Used by    Tainted: G
uinput                  6548  1
i2c_bcm2708             4005  0
snd_bcm2835            18182  0
snd_pcm                82038  1 snd_bcm2835
snd_page_alloc          5164  1 snd_pcm
snd_timer              20413  1 snd_pcm
snd                    59096  3 snd_bcm2835,snd_pcm,snd_timer
fuse                   80405  0
MLD>

Was muß ich eingeben, um eine lircd.conf zu erzeugen?

Ein besonderes Lob an Claus, Du hast es wieder einmal gepackt.

Und, epgsearch fehlt noch in der Pluginliste.

Gruß Gerhard

@Claus: Ih habe Deinen Beitrag eben erst gelesen. Kann ich für den Test das jetzt installierte System benutzen ?
« Last Edit: April 22, 2014, 21:32:46 by gkd-berlin »
Meine VDR:
Spoiler (show / hide)

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20535
    • View Profile
    • ClausMuus.de
Test MLD-4 RPI tgz
« Reply #256 on: April 22, 2014, 23:56:16 »
Hi,

die Fehler am Anfang Deines Reports sollten inzwischen behoben sein.

Für den Test musst Du ne ältere Version als Ausgangspunkt nehmen.

Um irrecord nutzen zu können, musst Du nach dem stoppen von lirc das Modul lirc_rpi laden: "modprobe lirc_rpi"

Claus
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 6.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 22TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline gkd-berlin

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 1402
    • View Profile
Test MLD-4 RPI tgz
« Reply #257 on: April 23, 2014, 02:12:33 »
Hallo Claus,

Upgrade-Test mit MLD-4.0.0-rpi_rpi_2014.04.14-56.tar  vom 14.4.  23:48h

UPGRADES:
opkg, busybox, base, eventlircd, dvb-sundtek, rpihddevice, vc, sensors, lirc, vdr, suspend, ntfs-3g, network, udev, alsa, kernel, setup, dvb und  mld-remote.
Installiert mit: All packages.

Statusmeldungen während der Installation (nur der letzte Block):
Code: [Select]
setup:                 
Configuring opkg.
Configuring busybox.
Configuring base.
Configuring kernel.
Configuring eventlircd.
Configuring alsa.
Configuring dvb-sundtek.
Configuring vdr.
Configuring vc.
Configuring vdr-plugin-rpihddevice.
Configuring sensors.
Configuring liblockdev1.
Configuring lirc.
Configuring libcec2.
Configuring suspend.
Configuring ntfs-3g.
Configuring network.
Configuring udev.
Configuring vdr-plugin-setup.
Configuring dvb.
Configuring mld-remote.
Collected errors:
* resolve_conffiles: Existing conffile /etc/fstab is different from the conffile in the new package. The new conffile will be placed at /etc/fstab-opkg.
* resolve_conffiles: Existing conffile /etc/hosts is different from the conffile in the new package. The new conffile will be placed at /etc/hosts-opkg.
* resolve_conffiles: Existing conffile /etc/rc.config is different from the conffile in the new package. The new conffile will be placed at /etc/rc.config-opkg.
* resolve_conffiles: Existing conffile /etc/vdr/setup.conf is different from the conffile in the new package. The new conffile will be placed at /etc/vdr/setup.conf-opkg.
* resolve_conffiles: Existing conffile /etc/modprobe.d/custom.conf is different from the conffile in the new package. The new conffile will be placed at /etc/modprobe.d/custom.conf-opkg.
* file_md5sum_alloc: Failed to open file /etc/setup/modules: No such file or directory.
* resolve_conffiles: Existing conffile /etc/vdr/plugins/setup/setup.xml is different from the conffile in the new package. The new conffile will be placed at /etc/vdr/plugins/setup/setup.xml-opkg.

REBOOT

Code: [Select]
/var/log/sysinit

Import filesystems:
Turn on DMA:
Checking:
Btrfs Btrfs v0.19
done
Mounting:
done
Setting up logging: level 1
Setting up netware:
done
btrfs:                 
locales:                 
Setting timezone:
done
Load keymap: de-latin1
done

ntp-client:                 
rpi:                 
network:                 
eventlircd:                 
Starting eventlircd
done

Init networking
Starting DHCP-client
done
done
Starting ntp client:
23 Apr 01:49:35 ntpdate[1813]: step time server 176.9.253.76 offset 1398210532.691199 sec
done
vdr:                 
lirc:                 
Starting VDR
done
hdparm:                 
ssh:                 
devmon:                 
vdr-plugin-opkg:                 
vdradmin-am:                 
webserver:                 
opkg:                 
sensors:                 
irxevent:                 
irexec:                 
ntfs-3g:                 
alsa:                 
setup:                 
# Sensors

Starting devmon
done
[2291] Apr 23 01:50:00 Running in background
Setting up storage devices
done


Init sound card:
done
Starting sshd:
Listen on IP: 192.168.2.101
done

Starting webserver:
done

Starting vdradmin server:
done
[2589] Apr 23 01:50:42 Child connection from 192.168.2.102:1883
[2589] Apr 23 01:50:48 Password auth succeeded for 'root' from 192.168.2.102:1883

Code: [Select]
/var/log/messages
Jan  1 01:00:18 (none) syslog.info syslogd started: BusyBox v1.22.1
Jan  1 01:00:22 (none) user.info kernel: [   22.614648] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input2
Jan  1 01:00:22 (none) user.info kernel: [   23.284284] input: lircd as /devices/virtual/input/input3
Jan  1 01:00:23 (none) user.info kernel: [   24.352387] input: Sundtek Ltd. Remote Control (lircd bypass) as /devices/virtual/input/input4
Jan  1 01:00:25 (none) user.info kernel: [   25.604393] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 01:00:26 (none) user.info kernel: [   27.160151] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Apr 23 01:49:47 (none) user.err vdr: [2042] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:49:47 (none) user.err vdr: [2042] ERROR: remote control LIRC not ready!
Apr 23 01:49:47 (none) user.err vdr: [2081] ERROR: lircd connection broken, trying to reconnect every 3,0 seconds
Apr 23 01:49:50 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:49:53 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:49:56 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:49:59 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:02 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:05 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:08 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:11 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:14 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:17 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:20 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:23 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:26 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:29 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:31 (none) auth.info login[2565]: root login on 'tty3'
Apr 23 01:50:31 (none) auth.info login[2562]: root login on 'tty2'
Apr 23 01:50:31 (none) auth.info login[2561]: root login on 'tty1'
Apr 23 01:50:31 (none) auth.info login[2568]: root login on 'tty4'
Apr 23 01:50:32 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:35 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:38 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:41 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:44 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 23 01:50:47 (none) user.err vdr: [2081] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory

usw.

Die Kiste läuft!
Ich hoffe, es hilft Dir weiter.

Gruß Gerhard
Meine VDR:
Spoiler (show / hide)

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20535
    • View Profile
    • ClausMuus.de
Test MLD-4 RPI tgz
« Reply #258 on: April 23, 2014, 11:14:26 »
Danke,

ja, nun weiß ich das die Änderung auch nen fehlerfreien Upgrade des Kernel ermöglicht.

Claus
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 6.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 22TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline gkd-berlin

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 1402
    • View Profile
Test MLD-4 RPI tgz
« Reply #259 on: April 23, 2014, 12:14:16 »
Hallo,

Test: MLD-4.0.0-rpi_rpi_2014.04.22-56.tar  vom 22.4. 20:53h

Kaltstart von der SD-Karte. Hier taucht die Fehlermeldung
Code: [Select]
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for suspend:
* libcec *
* opkg_install_cmd: Cannot install package suspend.                       failed
auf.

Nach Installation auf Festplatte ist suspend nicht aktiv. Es erscheint nicht in der System info.
F12 geht in Poweroff.

Wird suspend danach über Putty installiert, gibt es diese Fehlermeldung:
Code: [Select]
MLD> opkg install suspend
Installing suspend (0-13) to root...
Downloading http://www.minidvblinux.de/download/4.0.0-rpi/files/base/suspend_0-13.opk.
Installing libcec2 (2.1.4-4) to root...
Downloading http://www.minidvblinux.de/download/4.0.0-rpi/files/libs/libcec2_2.1.4-4.opk.
Installing liblockdev1 (1.0.3-1) to root...
Downloading http://www.minidvblinux.de/download/4.0.0-rpi/files/libs/liblockdev1_1.0.3-1.opk.
Configuring liblockdev1.
Configuring libcec2.
Configuring suspend.
Collected errors:
 * resolve_conffiles: Existing conffile /etc/rc.shutdown is different from the conffile in the new package. The new conffile will be placed at /etc/rc.shutdown-opkg.
MLD>
Suspend ist in der System info zu sehen und wird korrekt ausgeführt.

epgsearch ist wieder da.
Putty ist auch ok.

Die Fernbedienung am GPIO funktioniert ebenfalls.
Einfach meine lircd.conf nach /etc kopiert und es klappt.

Gruß Gerhard
Meine VDR:
Spoiler (show / hide)

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20535
    • View Profile
    • ClausMuus.de
Test MLD-4 RPI tgz
« Reply #260 on: April 23, 2014, 12:30:12 »
Sag mal, die erste (libcec) Fehlermeldung, wann kommt die? Direkt beim booten vom frisch herunter geladenen rpi Image? Oder hast Du nen individuelles Image genommen?

Claus
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 6.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 22TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline gkd-berlin

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 1402
    • View Profile
Test MLD-4 RPI tgz
« Reply #261 on: April 23, 2014, 12:46:23 »
Hallo Claus,

die Fehlermeldung kommt beim booten von einem frisch geladenen angepassten Image.
Diese angepasste Imagezusammenstellung verwende ich schon seit Wochen.

Code: [Select]
Gewählte Addons

    xrpi
    xlocales
    xinstall
    xdvb
    xmld-remote
    xlirc
    xeventlircd
    xirkeytable
    xnetwork
    xntp-client
    xwebserver
    xssh
    xalsa
    xvc
    xvdr
    xvdr-plugin-opkg
    xvdr-plugin-setup
    xvdr-plugin-rpihddevice
    xdvb-sundtek
    xhdparm
    xmc
    xsuspend
    xudevil
    xvdradmin-am
    xvdr-plugin-clock
    xvdr-plugin-devstatus
    xvdr-plugin-epgsearch
    xvdr-plugin-extrecmenu
    xvdr-plugin-femon
    xvdr-plugin-systeminfo

Um die Zusammenstellung nicht ständig neu eingeben zu müssen und um Auswahlfehler zu vermeiden, habe ich extra den Firefox installiert.
Nur von hier wird das angepasste RPI-Image runtergeladen.

Gruß Gerhard
Meine VDR:
Spoiler (show / hide)

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20535
    • View Profile
    • ClausMuus.de
Test MLD-4 RPI tgz
« Reply #262 on: April 23, 2014, 14:42:38 »
Das lag an nem Fehler in der Abhängigkeits Liste und betraf noch ein paar andere Pakete. Es sollte Morgen behoben sein.

Claus
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 6.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 22TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline gkd-berlin

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 1402
    • View Profile
Test MLD-4 RPI tgz
« Reply #263 on: April 27, 2014, 21:28:17 »
Hallo,

Test: MLD-4.0.0-rpi_rpi_2014.04.26-57.tar  vom 27.4. 10:10h

Beim Booten von SD-Karte aus sysinit:
Code: [Select]
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for alsa:
* kernel (>= 3.13.11.49) *
* opkg_install_cmd: Cannot install package alsa.
* satisfy_dependencies_for: Cannot satisfy the following dependencies for dvb:
* kernel (>= 3.13.11.49) *
* opkg_install_cmd: Cannot install package dvb.
* satisfy_dependencies_for: Cannot satisfy the following dependencies for eventlircd:
* kernel (>= 3.13.11.49) *
* opkg_install_cmd: Cannot install package eventlircd.
* satisfy_dependencies_for: Cannot satisfy the following dependencies for lirc:
* kernel (>= 3.13.11.49) *
* opkg_install_cmd: Cannot install package lirc.
* satisfy_dependencies_for: Cannot satisfy the following dependencies for network:
* kernel (>= 3.13.11.49) *
* opkg_install_cmd: Cannot install package network.
* satisfy_dependencies_for: Cannot satisfy the following dependencies for ntfs-3g:
* kernel (>= 3.13.11.49) *
* opkg_install_cmd: Cannot install package ntfs-3g.
* satisfy_dependencies_for: Cannot satisfy the following dependencies for sensors:
* kernel (>= 3.13.11.49) *
* opkg_install_cmd: Cannot install package sensors.                                        failed

Nach Installation auf Festplatte und 1. reboot
In der sysinit steht nur: "vdr ... seems to hang"
In der messages steht:
Code: [Select]
Jan  1 00:02:30 (none) syslog.info syslogd started: BusyBox v1.22.1
Jan  1 00:02:33 (none) user.info kernel: [  154.613578] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input2
Jan  1 00:02:33 (none) user.info kernel: [  154.626640] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 00:02:33 (none) user.info kernel: [  154.841531] input: lircd as /devices/virtual/input/input3
Jan  1 00:02:35 (none) user.info kernel: [  156.145925] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Apr 27 18:27:14 (none) user.info kernel: [  205.665851] btrfs: device fsid 3d376a08-5cdf-48ee-b234-91d41a1115ba devid 1 transid 309 /dev/sda1
Apr 27 18:27:14 (none) user.info kernel: [  205.679265] btrfs: disk space caching is enabled
Apr 27 18:27:17 (none) user.notice kernel: [  208.730478] XFS (sda2): Mounting Filesystem
Apr 27 18:27:18 (none) user.notice kernel: [  209.915139] XFS (sda2): Starting recovery (logdev: internal)
Apr 27 18:27:18 (none) user.notice kernel: [  210.113705] XFS (sda2): Ending recovery (logdev: internal)
Apr 27 20:28:10 (none) auth.info login[8926]: root login on 'tty1'
Apr 27 20:28:10 (none) auth.info login[8931]: root login on 'tty3'
Apr 27 20:28:10 (none) auth.info login[8927]: root login on 'tty2'
Apr 27 20:28:10 (none) auth.info login[8934]: root login on 'tty4'
Apr 27 18:40:05 (none) user.info kernel: [  976.814958] btrfs: device fsid 36756efe-ea58-4eeb-b16f-4beeb740ce26 devid 1 transid 4 /dev/sda1
Apr 27 18:40:05 (none) user.info kernel: [  976.828693] btrfs: disk space caching is enabled
Apr 27 18:40:05 (none) user.info kernel: [  976.959274] btrfs: creating UUID tree
Apr 27 18:40:05 (none) user.info kernel: [  977.263304] btrfs: setting 2 feature flag
Jan  1 01:00:17 (none) syslog.info syslogd started: BusyBox v1.22.1
Jan  1 01:00:21 (none) user.info kernel: [   22.159448] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input2
Jan  1 01:00:21 (none) user.info kernel: [   22.574095] input: lircd as /devices/virtual/input/input3
Jan  1 01:00:22 (none) user.info kernel: [   23.630888] input: Sundtek Ltd. Remote Control (lircd bypass) as /devices/virtual/input/input4
Jan  1 01:00:24 (none) user.info kernel: [   24.956820] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 01:00:25 (none) user.info kernel: [   26.514698] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Apr 27 20:43:44 (none) user.err vdr: [2051] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 27 20:43:44 (none) user.err vdr: [2051] ERROR: remote control LIRC not ready!
Apr 27 20:43:44 (none) user.err vdr: [2088] ERROR: lircd connection broken, trying to reconnect every 3,0 seconds
Apr 27 20:43:47 (none) user.err vdr: [2088] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 27 20:43:50 (none) user.err vdr: [2088] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 27 20:43:53 (none) user.err vdr: [2088] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 27 20:43:56 (none) user.err vdr: [2088] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 27 20:43:59 (none) user.err vdr: [2088] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Apr 27 20:44:02 (none) user.err vdr: [2088] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
usw.

Nach 2. reboot, /var/log/messages:
Code: [Select]
Jan  1 01:00:17 (none) syslog.info syslogd started: BusyBox v1.22.1
Jan  1 01:00:21 (none) user.info kernel: [   22.208745] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input2
Jan  1 01:00:21 (none) user.info kernel: [   22.599085] input: lircd as /devices/virtual/input/input3
Jan  1 01:00:23 (none) user.info kernel: [   23.683846] input: Sundtek Ltd. Remote Control (lircd bypass) as /devices/virtual/input/input4
Jan  1 01:00:24 (none) user.info kernel: [   24.846595] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 01:00:25 (none) user.info kernel: [   26.396398] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Jan  1 01:00:57 (none) user.err vdr: [2070] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Jan  1 01:00:57 (none) user.err vdr: [2070] ERROR: remote control LIRC not ready!
Jan  1 01:00:57 (none) user.err vdr: [2109] ERROR: lircd connection broken, trying to reconnect every 3,0 seconds
Jan  1 01:01:00 (none) user.err vdr: [2109] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Jan  1 01:01:03 (none) user.err vdr: [2109] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Jan  1 01:01:06 (none) user.err vdr: [2109] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Jan  1 01:01:09 (none) user.err vdr: [2109] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Jan  1 01:01:12 (none) user.err vdr: [2109] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Jan  1 01:01:15 (none) user.err vdr: [2109] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Jan  1 01:01:18 (none) user.err vdr: [2109] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
Jan  1 01:01:21 (none) user.err vdr: [2109] ERROR (lirc.c,43): /var/run/lirc/lircd: No such file or directory
usw.

/var/log/vdr ist leer.

Bild ist da, Ton fehlt immer. Auch ein mehrmaliger "restart vdr", der sonst geholfen hat, bringt den Ton nicht zurück.

Gruß Gerhard
Meine VDR:
Spoiler (show / hide)

Offline det

  • Profi Member
  • ****
  • Posts: 343
    • View Profile
Test MLD-4 RPI tgz
« Reply #264 on: April 27, 2014, 22:12:44 »
hi

lirc baut nicht

mld@mld400:~/mld-entw/MLD.4.0.0$ cd lirc
mld@mld400:~/mld-entw/MLD.4.0.0/lirc$ make clean
mld@mld400:~/mld-entw/MLD.4.0.0/lirc$ make
lirc:
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./config.guess'
libtoolize: copying file `./config.sub'
libtoolize: copying file `./install-sh'
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure.ac:17: installing `./compile'
configure.ac:10: installing `./missing'
daemons/Makefile.am: installing `./depcomp'
Makefile.am: installing `./INSTALL'
Creating setup-driver.sh ...
        Use patch ../10_lirc-0.9.0_ya_usbir_v3.5.patch
patching file configure.ac
Hunk #1 FAILED at 316.
Hunk #2 succeeded at 455 (offset 9 lines).
Hunk #3 succeeded at 476 (offset 9 lines).
Hunk #4 succeeded at 693 (offset 9 lines).
Hunk #5 succeeded at 1423 (offset 9 lines).
Hunk #6 succeeded at 1464 (offset 9 lines).
Hunk #7 succeeded at 1524 (offset 9 lines).
Hunk #8 succeeded at 1690 (offset 4 lines).
1 out of 8 hunks FAILED -- saving rejects to file configure.ac.rej
patching file daemons/hw-types.c
patching file daemons/hw_ya_usbir.c
patching file daemons/Makefile.am
Hunk #1 succeeded at 57 (offset 1 line).
patching file daemons/transmit.c
patching file setup.data
make[2]: *** [patch] Fehler 1
make[1]: *** [src/lirc/configure] Fehler 2
make: *** [_all] Fehler 2
mld@mld400:~/mld-entw/MLD.4.0.0/lirc$
mfg det
Jeder sollte sein Leben so leben können wie er/sie es möchte, frei und
unabhängig, in der Not anderen zur Seite stehend, nie vergessen was man
ist, eben einfach nur Mensch sein mit allen Schwächen und Stärken
Lieber stehend sterben als ewig gebückt leben

Offline MegaX

  • Administrator
  • Expert Member
  • ********
  • Posts: 1822
    • View Profile
Test MLD-4 RPI tgz
« Reply #265 on: April 27, 2014, 23:03:14 »
Hab ich schon gefixt und baut auch.


MegaX
Gruß MegaX

Hardware (show / hide)

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20535
    • View Profile
    • ClausMuus.de
Test MLD-4 RPI tgz
« Reply #266 on: April 27, 2014, 23:43:24 »
Hi,

es gibt nachher neue Images. Da war mir nen Fehler beim Build Aufruf unterlaufen.

Claus
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 6.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 22TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline gkd-berlin

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 1402
    • View Profile
Test MLD-4 RPI tgz
« Reply #267 on: April 28, 2014, 03:40:24 »
Hallo,

Test: MLD-4.0.0-rpi_rpi_2014.04.27-57.tar  vom 28.4. 0:08h

einige Fehler sind behoben, aber noch nicht alle.

Beim Booten von SD-Karte:
Code: [Select]
...
Creating ssh rsa key:
modprobe: can't open 'modules.dep': No such file or directory                      done
Creating ssh dss key:
...
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for mld-remote:
* lirc *
* opkg_install_cmd: Cannot install package mld-remote.                             failed

Nach Installation auf Festplatte und 1. reboot:
Code: [Select]
/var/log/sysinit
setup seems to hang! continue now...
Code: [Select]
/var/log/messages
Jan  1 01:00:20 (none) user.info kernel: [   21.877624] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input2
Jan  1 01:00:20 (none) daemon.err udevd[1599]: failed to execute '/lib/udev/lircd_helper' 'lircd_helper': No such file or directory
Jan  1 01:00:20 (none) daemon.err udevd[1600]: failed to execute '/lib/udev/lircd_helper' 'lircd_helper': No such file or directory
Jan  1 01:00:23 (none) user.info kernel: [   24.306883] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 01:00:24 (none) user.info kernel: [   25.942341] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

Nach 2. reboot:
Code: [Select]
/var/log/messages
Jan  1 01:00:16 (none) syslog.info syslogd started: BusyBox v1.22.1
Jan  1 01:00:21 (none) user.info kernel: [   21.783650] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input2
Jan  1 01:00:21 (none) daemon.err udevd[1603]: failed to execute '/lib/udev/lircd_helper' 'lircd_helper': No such file or directory
Jan  1 01:00:21 (none) daemon.err udevd[1605]: failed to execute '/lib/udev/lircd_helper' 'lircd_helper': No such file or directory
Jan  1 01:00:23 (none) user.info kernel: [   23.657053] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 01:00:24 (none) user.info kernel: [   25.189335] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

Der Ton fehlt immer.

Im WebIf Quick Setup fehlt die Auswahl für "rpi on GPIO".
In Setup – Remote control gibt nur die Möglichkeit Install CEC support: auszuwählen.
Ich kann "rpi on GPIO" nirgends einstellen.

Gruß Gerhard
Meine VDR:
Spoiler (show / hide)

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20535
    • View Profile
    • ClausMuus.de
Test MLD-4 RPI tgz
« Reply #268 on: April 28, 2014, 10:29:22 »
Hi,

der lirc Fehler irritiert mich nun ein wenig. Ich hatte das selbe Image gestern Abend getestet und keinen Fehler.
Möglicherweise war auf Deiner SD Karte nicht genug freier Platz für das Image, nachdem Du die letzte Version nicht installieren konntest. Magst Du das bitte noch einmal testen?

Ich werde mir das heute Abend auch noch mal genauer anschauen.

Claus
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 6.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 22TB HDD - Lian Li PC-C37B - Samsung LE40A559

Offline gkd-berlin

  • MLD-Tester
  • Expert Member
  • ******
  • Posts: 1402
    • View Profile
Test MLD-4 RPI tgz
« Reply #269 on: April 28, 2014, 16:11:10 »
Hallo Claus,

auf der SD-Karte sind jetzt, nach Installation auf Festplatte, noch 3,67 GB frei (WinXP).
Code: [Select]
MLD> fdisk -l

Disk /dev/mmcblk0: 3965 MB, 3965190144 bytes
49 heads, 48 sectors/track, 3292 cylinders
Units = cylinders of 2352 * 512 = 1204224 bytes

        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk0p1               4        3293     3868160   b Win95 FAT32

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1        1275    10241406   c Win95 FAT32 (LBA)
/dev/sda2            1276       60801   478142595  83 Linux
MLD>
Es ist eine SanDisk SDHC Extreme 4 GB, Lesen max. 30 MB/sec. - Schreiben:max. 20 MB/sec. - Aufbau:Class 10 - UHS I.

Heute noch einmal ein frisches Image von gestern, MLD-4.0.0-rpi_rpi_2014.04.27-57.tar vom 28.4. 0:08h, gestartet:
Code: [Select]
/var/log/sysinit
...
Creating ssh rsa key:
modprobe: can't open 'modules.dep': No such file or directory                            done
Creating ssh dss key:
done
...
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for mld-remote:
* lirc *
* opkg_install_cmd: Cannot install package mld-remote.                                   failed
Belegter Speicher: 46,7 MB - Freier Speicher 3,63 GB (WinXP).

Gruß Gerhard


Ich hab noch etwas gefunden. Das hat nichts mit den anderen Fehlermeldungen zu tun.
Ich habe gestern nicht bemerkt, daß die Datei ellenlang geladen wird und war der Meinung sie ist leer.
Code: [Select]
/var/log/vdr

No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
ERROR: root: can't determine bus type (or this bus type is unknown)
ERROR: root: can't determine bus type (or this bus type is unknown)
ERROR: root: can't determine bus type (or this bus type is unknown)
ERROR: root: can't determine bus type (or this bus type is unknown)
/dev/drwxrwxr-x: open: No such file or directory

4: open: No such file or directory

33: open: No such file or directory

Jan: open: No such file or directory

1: open: No such file or directory

1970: open: No such file or directory

cache: open: No such file or directory

drwxrwxr-x: open: No such file or directory

4: open: No such file or directory

85: open: No such file or directory

Apr: open: No such file or directory

28: open: No such file or directory

44: open: No such file or directory

tv: open: No such file or directory

No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
ERROR: root: can't determine bus type (or this bus type is unknown)
ERROR: root: can't determine bus type (or this bus type is unknown)
ERROR: root: can't determine bus type (or this bus type is unknown)
ERROR: root: can't determine bus type (or this bus type is unknown)
/dev/drwxrwxr-x: open: No such file or directory

4: open: No such file or directory

33: open: No such file or directory

Jan: open: No such file or directory

1: open: No such file or directory

1970: open: No such file or directory

cache: open: No such file or directory

drwxrwxr-x: open: No such file or directory

4: open: No such file or directory

85: open: No such file or directory

Apr: open: No such file or directory

28: open: No such file or directory

44: open: No such file or directory

tv: open: No such file or directory

No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
ERROR: root: can't determine bus type (or this bus type is unknown)
ERROR: root: can't determine bus type (or this bus type is unknown)
ERROR: root: can't determine bus type (or this bus type is unknown)
ERROR: root: can't determine bus type (or this bus type is unknown)
/dev/drwxrwxr-x: open: No such file or directory

4: open: No such file or directory

33: open: No such file or directory

Jan: open: No such file or directory

1: open: No such file or directory

1970: open: No such file or directory

cache: open: No such file or directory

drwxrwxr-x: open: No such file or directory

4: open: No such file or directory

85: open: No such file or directory

Apr: open: No such file or directory

28: open: No such file or directory

44: open: No such file or directory

tv: open: No such file or directory
Das geht immer so weiter!

Nach meiner Meinung müßte die Sensorabfrage unterbunden werden. Die Sensoren können ja nicht gefunden werden.
Es macht nur Systemlast und müllt diese Datei voll. Nach ca. 30 Minuten ist die Datei schon 23KB groß.
« Last Edit: April 28, 2014, 18:26:33 by gkd-berlin »
Meine VDR:
Spoiler (show / hide)

1 ... 16 17 [18] 19 20 ... 38 >>> Archiv / MLD 4.x / Raspberry PI / Test MLD-4 RPI tgz
 



Users Online Users Online

0 Members and 1 Guest are viewing this topic.