Archiv > Development
Test MLD-4 ISO
MegaX:
--- Quote from: MarMic on February 06, 2014, 20:04:22 ---Also jetzt doch? Gestern lief doch noch alles bei dir???
--- End quote ---
Mit dem ISO vom Mittwoch ging ja auch alles, egal was ich gemacht habe. Haste ja Live gesehen ;)
MegaX
gkd-berlin:
Hallo,
Test: MLD-4.0.0_ff-hd_2014.02.07-38.iso vom 7.2. 12:21h
ich bekomme weder Bild noch Ton.
--- Code: ---/var/log/messages
Feb 7 14:51:34 (MLD) syslog.info syslogd started: BusyBox v1.22.1
Feb 7 15:51:44 (MLD) user.err vdr: [1692] ERROR: invalid primary device number: 1
Feb 7 15:51:44 (MLD) user.err vdr: [1692] ERROR: no primary device found - using first device!
Feb 7 15:51:44 (MLD) user.err vdr: [1692] ERROR: invalid primary device number: 1
Feb 7 14:51:45 (MLD) user.info kernel: r8169 0000:01:00.0 eth0: link down
Feb 7 14:51:45 (MLD) user.info kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 7 14:51:45 (MLD) user.info kernel: r8169 0000:01:00.0 eth0: link down
Feb 7 14:51:47 (MLD) user.info kernel: r8169 0000:01:00.0 eth0: link up
Feb 7 14:51:47 (MLD) user.info kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 7 15:51:54 (MLD) user.err vdr: [2690] ERROR: invalid primary device number: 1
Feb 7 15:51:54 (MLD) user.err vdr: [2690] ERROR: no primary device found - using first device!
Feb 7 15:51:54 (MLD) user.err vdr: [2690] ERROR: invalid primary device number: 1
Feb 7 15:51:55 (MLD) auth.info login[2717]: root login on 'tty1'
Feb 7 15:51:55 (MLD) auth.info login[2718]: root login on 'tty2'
Feb 7 15:51:55 (MLD) auth.info login[2719]: root login on 'tty3'
Feb 7 15:51:55 (MLD) auth.info login[2720]: root login on 'tty4'
Feb 7 15:52:04 (MLD) user.err vdr: [2793] ERROR: invalid primary device number: 1
Feb 7 15:52:04 (MLD) user.err vdr: [2793] ERROR: no primary device found - using first device!
Feb 7 15:52:04 (MLD) user.err vdr: [2793] ERROR: invalid primary device number: 1
Feb 7 15:52:14 (MLD) user.err vdr: [2873] ERROR: invalid primary device number: 1
Feb 7 15:52:14 (MLD) user.err vdr: [2873] ERROR: no primary device found - using first device!
Feb 7 15:52:14 (MLD) user.err vdr: [2873] ERROR: invalid primary device number: 1
Feb 7 15:52:25 (MLD) user.err vdr: [2953] ERROR: invalid primary device number: 1
Feb 7 15:52:25 (MLD) user.err vdr: [2953] ERROR: no primary device found - using first device!
Feb 7 15:52:25 (MLD) user.err vdr: [2953] ERROR: invalid primary device number: 1
Feb 7 15:52:35 (MLD) user.err vdr: [3033] ERROR: invalid primary device number: 1
Feb 7 15:52:35 (MLD) user.err vdr: [3033] ERROR: no primary device found - using first device!
Feb 7 15:52:35 (MLD) user.err vdr: [3033] ERROR: invalid primary device number: 1
Feb 7 15:52:45 (MLD) user.err vdr: [3118] ERROR: invalid primary device number: 1
Feb 7 15:52:45 (MLD) user.err vdr: [3118] ERROR: no primary device found - using first device!
Feb 7 15:52:45 (MLD) user.err vdr: [3118] ERROR: invalid primary device number: 1
Feb 7 14:52:45 (MLD) user.info kernel: [3142]: segfault at 5b18c483 ip 5b18c483 sp b601a2ec error 4
Feb 7 15:52:55 (MLD) user.err vdr: [6304] ERROR: invalid primary device number: 1
Feb 7 15:52:55 (MLD) user.err vdr: [6304] ERROR: no primary device found - using first device!
Feb 7 15:52:55 (MLD) user.err vdr: [6304] ERROR: invalid primary device number: 1
Feb 7 15:53:05 (MLD) user.err vdr: [6384] ERROR: invalid primary device number: 1
Feb 7 15:53:05 (MLD) user.err vdr: [6384] ERROR: no primary device found - using first device!
Feb 7 15:53:05 (MLD) user.err vdr: [6384] ERROR: invalid primary device number: 1
--- End code ---
Gruß Gerhard
clausmuus:
OK, da hatte ich übersehen, das die dvb Treiber nicht gebaut werden konnten. Mal sehen was sich da machen lässt.
Claus
clausmuus:
Ich hab nun nen Kernel 3.13 Patch für die dvb Treiber erstellt. Mit etwas Glück funktionieren die Treiber damit wieder.
Du solltest also Morgen wider testen können.
Claus
skippy:
Hier mal ein Test von mir, mit einem individuellem ISO von heute. Grundlage ist das client-shd-iso. Insgesamt enthalten sind:
--- Code: ---locales, install, dvb-remote, eventlircd, irkeytable, network, webserver, wakeup, alsa, xorg, xorg-autodetect,
vdr, vdr-plugin-opkg, vdr-plugin-setup, xvdr-plugin-softhddevice, vdr-plugin-streamdev-client, vdr-plugin-svdrpservice,
vdr-plugin-remoteosd, vdr-plugin-remotetimers, ssh, xorg-nvidia
--- End code ---
Beim Starten vom Stick mit "normal" hängt die MLD. Ursache ist, dass die Abfrage nach der Channellist nicht angezeigt wird. Es ist weiterhin der MLD-Schirm mit dem Laufbalken zu sehen. Er wenn mann die Konsolen durchschaltet, ist die Abfrage bei "F2" sichtbar. Danach muss man wieder auf "F7" wechseln, damit die Tatatatureingabe angenommen wird.
Bild und Ton erhalte ich nicht, dafür in der Messages folgende Meldungen:
--- Code: ---Feb 8 11:45:37 (MLD) syslog.info syslogd started: BusyBox v1.22.1
Feb 8 11:45:40 (MLD) user.info kernel: r8169 0000:02:00.0 eth0: link down
Feb 8 11:45:40 (MLD) user.info kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 8 11:45:40 (MLD) user.info kernel: r8169 0000:02:00.0 eth0: link down
Feb 8 11:45:41 (MLD) user.info kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 8 11:45:41 (MLD) user.info kernel: r8169 0000:02:00.0 eth0: link up
Feb 8 11:45:46 (MLD) user.warn kernel: nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
Feb 8 11:45:49 (MLD) user.warn kernel: nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
Feb 8 11:45:49 (MLD) user.warn kernel: nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
Feb 8 11:45:50 (MLD) user.warn kernel: nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
Feb 8 11:46:01 (MLD) user.warn kernel: nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
Feb 8 12:46:01 (MLD) user.err vdr: video/vdpau: Can't create vdp device on display ':0.0'
Feb 8 12:46:02 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 11:46:02 (MLD) user.warn kernel: nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
Feb 8 12:46:13 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:46:14 (MLD) auth.info login[9668]: root login on 'tty1'
Feb 8 12:46:14 (MLD) auth.info login[9669]: root login on 'tty2'
Feb 8 12:46:14 (MLD) auth.info login[9670]: root login on 'tty3'
Feb 8 12:46:14 (MLD) auth.info login[9671]: root login on 'tty4'
Feb 8 12:46:24 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:46:35 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 11:46:45 (MLD) user.warn kernel: nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
Feb 8 12:46:46 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:46:57 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:47:08 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:47:19 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:47:30 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:47:41 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:47:52 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:48:03 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 11:48:05 (MLD) user.err kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Feb 8 11:48:05 (MLD) user.err kernel: sd 6:0:0:0: [sdc] No Caching mode page found
Feb 8 11:48:05 (MLD) user.info kernel: sdc: sdc1 sdc2
Feb 8 11:48:05 (MLD) user.err kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Feb 8 11:48:05 (MLD) user.err kernel: sd 6:0:0:0: [sdc] No Caching mode page found
Feb 8 11:48:05 (MLD) user.info kernel: sdc: sdc1 sdc2
Feb 8 12:48:14 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 11:48:22 (MLD) user.info kernel: btrfs: device fsid b102467d-d572-4840-a73a-8a4823e71fc6 devid 1 transid 4 /dev/sdc1
Feb 8 11:48:22 (MLD) user.info kernel: btrfs: disk space caching is enabled
Feb 8 11:48:22 (MLD) user.info kernel: btrfs: creating UUID tree
Feb 8 12:48:25 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 11:48:28 (MLD) user.info kernel: btrfs: setting 2 feature flag
Feb 8 12:48:36 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 11:48:38 (MLD) user.notice kernel: XFS (sdc2): Mounting Filesystem
Feb 8 11:48:45 (MLD) user.info kernel: XFS (sdc2): Ending clean mount
Feb 8 12:48:47 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:48:58 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:49:09 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 11:49:16 (MLD) user.info kernel: usb 1-5: reset high-speed USB device number 5 using ehci-pci
Feb 8 12:49:20 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
Feb 8 12:49:31 (MLD) user.err vdr: [9136] streamdev-client: Unexpected reply to 'PROV 0 C-41985-1101-28475' from 10.132.128.103:2004: 550 Undefined channel "C-41985-1101-28475"
--- End code ---
Danach habe ich versucht auf dem Stick zu installieren. Hier bleibt er bei "install system on sdc1" stehen und wird nicht fertig.
Gleiches Vorgehen hatte ich mit einem ISO gleicher Zusammenstellung vom 2. Februar erfolgreich (Installation dauert keine 2 Minuten) durchgeführt. Bei einem ISO wo ich zusätzlich noch den Avahi-Linker drin hatte, wurde die Installation auch damals nicht fertig (ca. 30 Minuten gewartet). Habe jetzt gerade noch einmal die Installation mit dem ISO vom 2.2. durchgeführt => klappt wie erwartet.
Das System vom 2.2. hatte ich mir allerdings durch Updates zerschossen und konnte es auch nicht über die angelegten Snapshots wieder herstellen. In den Snapshots vom Bootmenü wurden keine angezeigt.
Viele Grüße skippy
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version