Archiv > Raspberry PI
Test MLD-4 RPI tgz
MegaX:
Hab ich schon gefixt und baut auch.
MegaX
clausmuus:
Hi,
es gibt nachher neue Images. Da war mir nen Fehler beim Build Aufruf unterlaufen.
Claus
gkd-berlin:
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: ---...
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
--- End code ---
Nach Installation auf Festplatte und 1. reboot:
--- Code: ---/var/log/sysinit
setup seems to hang! continue now...
--- End code ---
--- Code: ---/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
--- End code ---
Nach 2. reboot:
--- Code: ---/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
--- End code ---
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
clausmuus:
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
gkd-berlin:
Hallo Claus,
auf der SD-Karte sind jetzt, nach Installation auf Festplatte, noch 3,67 GB frei (WinXP).
--- Code: ---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>
--- End code ---
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: ---/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
--- End code ---
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: ---/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
--- End code ---
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ß.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version