VDR Italia

lukkino ha scritto: capito... quello che hai postato è l'epg che trasmette la Rai, mentre quello che scarica LoadEPG è l'epg prodotto da Sky, che ovviamente fa una conversione... forse alcuni decoder Sky non supportano gli accenti...

Ciao

L'avevo intuito ma adesso ne sono certo
Grazie

lukkino ha scritto:
papernik ha scritto:Per lukk, loadepg mi da sempre errore nel caricamento dei dati, sia qui che su yavdr....si può fare qualcosa ?
Sai dirmi l'errore che compare?

Oppure nel syslog dai un occhio a cosa dice...

Ciao

Per lukkino :

I canali marcopolo e alice sono ok :

Codice: Seleziona tutto

Alice:11880:vC34:S13.0E:27500:2560=2:2561=ita@3:2562:919,93B,9CD:3630:64511:5800:0
Marcopolo:11880:vC34:S13.0E:27500:2569=2:2570=ita@3:2571:919,93B,9CD:3633:64511:5800:0

Prima mi compare : attendi il caricamento dei dati , poi dopo un po' , 'errore di caricamento'
Appena unix mi risponderà ti darò i dettagli dei log.

L'unica cosa che vedo è :

Codice: Seleziona tutto

LoadEPG: Start task
set  8 00:29:26.922 [core.pids] 1/0: now tuned to source 5300ff7e(S13.0E) transponder 33ba9
set  8 00:29:31.346 [core.pids] 1/0: now tuned to source 5300ff7e(S13.0E) transponder 33830
set  8 00:29:31.535 [core.pids] 1/0: now tuned to source 5300ff7e(S13.0E) transponder 33ba9
set  8 00:29:35.763 [core.pids] 1/0: now tuned to source 5300ff7e(S13.0E) transponder 33830
set  8 00:29:35.763 [core.pids] 0/0: now tuned to source 5300ff7e(S13.0E) transponder 33ba9
LoadEPG: End task
set  8 00:29:45.409 [core.pids] 1/0: tune to same source/transponder

Per unix :
dove vanno a finire i log di vdr e il syslog nella sif ?

/var/log tutti i log del sistema
/tmp i log di vdr-sxfe.

in /var/log ho solo Xorg0.log e vdr-sc log , mi mancano i soliti message. Da qualche parte trovo la inf che mi ha chiesto lukk , visto che lanciando manualmente ./runvdr vedo solo quello che ho già scritto sopra ?

Grazie

modifica così il file rsyslog.service e poi riavvia

Codice: Seleziona tutto

[Unit]
Description=System Logging Service

[Service]
ExecStart=/usr/sbin/rsyslogd -n -c5
Sockets=syslog.socket
StandardOutput=null

[Install]
WantedBy=multi-user.target
Alias=syslog.service

lukkino ha scritto:
papernik ha scritto:Per lukk, loadepg mi da sempre errore nel caricamento dei dati, sia qui che su yavdr....si può fare qualcosa ?
Sai dirmi l'errore che compare?

Oppure nel syslog dai un occhio a cosa dice...

Ciao

Ecco qui , rimossi messaggi relativi alla 3c :

Codice: Seleziona tutto

Sep  8 14:57:22 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:22 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:22 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:23 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:23 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:23 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:24 localhost vdr: [1180] LoadEPG: tuned transponder with adapter number=0
Sep  8 14:57:24 localhost vdr: [1180] LoadEPG: Local Time Offset=[UTC]+2
Sep  8 14:57:24 localhost vdr: [495] warning: LoadEPG - Attendi il caricamento dei dati
Sep  8 14:57:24 localhost vdr: [1222] Text2Skin: message display update thread started (pid=495, tid=1222)
Sep  8 14:57:24 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:24 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:24 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:25 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:25 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:25 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:26 localhost vdr: [1180] LoadEPG: Error, timeout polling filter
Sep  8 14:57:26 localhost vdr: [1180] switching to channel 102
Sep  8 14:57:26 localhost vdr: [1180] changing transponder data of channel 102 from 10992:VC23M2O0S0:S13.0E:27500 to 11881:VM2:S13.0E:27500
Sep  8 14:57:26 localhost vdr: [1180] changing id of channel 102 from 318-12400-8512-0 to 4096-4095-4094-0
Sep  8 14:57:26 localhost vdr: [1180] changing caids of channel 102 from 100,183D to 0
Sep  8 14:57:26 localhost vdr: [865] ERROR (dvbdevice.c,671): Operation not supported
Sep  8 14:57:26 localhost vdr: [865] ERROR (dvbdevice.c,685): Operation not supported
Sep  8 14:57:26 localhost vdr: [865] ERROR (dvbdevice.c,687): Operation not supported
Sep  8 14:57:26 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:26 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:26 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:27 localhost vdr: [865] ERROR (dvbdevice.c,691): Operation not supported
Sep  8 14:57:27 localhost vdr: [865] ERROR (dvbdevice.c,689): Operation not supported
Sep  8 14:57:27 localhost vdr: [865] ERROR (dvbdevice.c,686): Operation not supported
Sep  8 14:57:27 localhost vdr: [865] ERROR: frontend 0/0: Invalid argument
Sep  8 14:57:27 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:27 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:27 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:28 localhost vdr: [1180] LoadEPG: End task
Sep  8 14:57:28 localhost vdr: [1180] cTaskLoadepg thread ended (pid=495, tid=1180)
Sep  8 14:57:28 localhost runvdr[381]: set  8 14:57:22LoadEPG: End task
Sep  8 14:57:28 localhost vdr: [1222] Text2Skin: message display update thread ended (pid=495, tid=1222)
Sep  8 14:57:28 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:28 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:28 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:29 localhost vdr: [495] ERROR: LoadEPG - Errore di caricamento
Sep  8 14:57:29 localhost vdr: [1223] Text2Skin: message display update thread started (pid=495, tid=1223)
Sep  8 14:57:29 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:29 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:29 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:30 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:30 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:30 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:31 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:31 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:31 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:32 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:32 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:32 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:33 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:33 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:33 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:34 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:34 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:34 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:35 localhost vdr: [1223] Text2Skin: message display update thread ended (pid=495, tid=1223)
Sep  8 14:57:35 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:35 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:35 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:36 localhost vdr: [495] switching to channel 102
Sep  8 14:57:36 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:36 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:36 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:37 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:37 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:37 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:38 localhost vdr: [1211] [xine..put] Detected video size 720x576
Sep  8 14:57:38 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:38 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:38 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:39 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:39 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:39 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:40 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:40 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:40 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:41 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:41 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:41 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:42 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:42 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:42 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:43 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:43 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:43 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:44 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:44 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:44 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:45 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:45 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:45 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:46 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:46 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:46 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:47 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:47 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:47 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:48 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:48 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:48 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:49 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:49 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:49 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:50 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:50 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:50 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:51 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:51 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:51 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:52 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:52 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:52 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:53 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:53 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:53 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:54 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:54 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:54 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:55 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:55 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:55 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:56 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:56 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:56 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:57 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:57 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:57 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:58 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:58 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:58 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:57:59 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:57:59 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:57:59 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:58:00 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:58:00 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:58:00 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:58:01 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:58:01 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:58:01 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:58:02 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:58:02 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:58:02 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:58:03 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:58:03 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:58:03 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:58:04 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:58:04 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:58:04 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:58:05 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:58:05 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:58:05 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:58:06 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:58:06 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:58:06 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:58:07 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:58:07 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:58:07 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr
Sep  8 14:58:08 localhost vdr: [1016] dbus2vdr: try to connect to system bus
Sep  8 14:58:08 localhost vdr: [1016] dbus2vdr: name error: Connection ":1.4" is not allowed to own the service "de.tvdr.vdr" due to security policies in the configuration file
Sep  8 14:58:08 localhost vdr: [1016] dbus2vdr: not primary owner for bus de.tvdr.vdr

unixer ha scritto:Adesso lancio un appello

c'è qualcuno che conosce i processori ARM ???

ho compilato la sif box per il raspberry e per il cubox ma non so come si creai la partizione fat o meglio non so cosa andarci a mettere

Grazie

bhe detto in due parole, per il raspberry devi metterci :
start.elf, loader.bin, bootcode.bin, kernel.img ...vedi anche QUI
al limite puoi provare a scaricare un immagine gia' pronta tipo raspbian o altro e sostituire la rootfs con quella tua, facendo attenzione ai moduli (kernel) ecc.
il cubox non lo conosco visto che non ce lo.
ogni Soc ha le sue caratteristiche, dunque la forma di avviare da SD varia.
se mi passi la rootfs per raspberry posso provare, visto che e li che prende polvere e non fa nulla

per caso hai anche una rootfs per armv7a hf ?(allwinner a10)

bye

von fritz ha scritto:se mi passi la rootfs per raspberry posso provare, visto che e li che prende polvere e non fa nulla
per caso hai anche una rootfs per armv7a hf ?(allwinner a10)

bye

eccolo
http://dl.dropbox.com/u/23897246/sifbox ... pi.tar.bz2

grazie unixer per il lavoro,
ho scaricato l' immagine, domani la provo,
ma e' per il mele come ti chiedeva von, o e' per il raspberry come dice il nome?
hai un frontend grafico funzionanet?

davidea ha scritto:grazie unixer per il lavoro,
ho scaricato l' immagine, domani la provo,
ma e' per il mele come ti chiedeva von, o e' per il raspberry come dice il nome?
hai un frontend grafico funzionanet?

è per il rasp
se mi date i dati del mele vediamo se riesco a ricavarne qualche cosa

Preimpostate ho queste conf

Codice: Seleziona tutto

drwxr-xr-x  4 root root 4096 set  1 14:47 armada5xx/
drwxr-xr-x  4 root root 4096 ago 29 16:10 bcm2708/
drwxr-xr-x  3 root root 4096 ago 29 16:10 bcmring/
drwxr-xr-x  4 root root 4096 ago 29 16:10 imx5x/
drwxr-xr-x  4 root root 4096 ago 29 16:10 imx6/
drwxr-xr-x  3 root root 4096 ago 29 16:10 kirkwood/
-rw-r--r--  1 root root  659 ago 31 22:01 meta
drwxr-xr-x  4 root root 4096 ago 29 16:10 omap3/
drwxr-xr-x  4 root root 4096 ago 29 16:10 omap4/
drwxr-xr-x  3 root root 4096 ago 29 16:10 s3c24xx/
drwxr-xr-x  4 root root 4096 ago 29 16:10 tegra2/
drwxr-xr-x  4 root root 4096 ago 29 16:10 ux500/
drwxr-xr-x  3 root root 4096 ago 29 16:10 versatilepb/
root@HTPCServer:~/openbricks/config/platforms/arm#

ma suppongo che se ne possano aggiungere altre

davidea ha scritto: hai un frontend grafico funzionanet?

In che senso ???

Hello

@unixer, provato con il raspberry ieri.
mi da un bel :
Kernel panic - not syncing: Attempted to kill init!

unixer ha scritto:se mi date i dati del mele vediamo se riesco a ricavarne qualche cosa

per provare va bene anche omap3, il resto ce lo metto io.
il debug per il raspb lo lascio a @davidea

bye

von fritz ha scritto:Hello

@unixer, provato con il raspberry ieri.
mi da un bel :
Kernel panic - not syncing: Attempted to kill init!

unixer ha scritto:se mi date i dati del mele vediamo se riesco a ricavarne qualche cosa
per provare va bene anche omap3, il resto ce lo metto io.
il debug per il raspb lo lascio a @davidea

bye

queste opzioni ti soddisfano ???

Codice: Seleziona tutto

        Target architecture (ARM)  --->                              │ │
  │ │        Target sub-architecture (armv7)  --->                        │ │
  │ │        Target platform (OMAP3)  --->                                │ │
  │ │        Target machine (ISEE IGEPv2)  --->                           │ │
  │ │        Target CPU (cortex-a8)  --->                                 │ │
  │ │        FPU optimizations (NEON)  --->

Scusate ma senza "calcio nel sedere" (accelerazione) alla fine sarebbe solo un'esercizio accademico. O no?

Vdr dovrebbe compilarsi senza problemi sotto debian arm...

Smanettate, smanettate

ragno ha scritto:Scusate ma senza "calcio nel sedere" (accelerazione) alla fine sarebbe solo un'esercizio accademico. O no?

Vdr dovrebbe compilarsi senza problemi sotto debian arm...

Smanettate, smanettate

Scusa
ma mi vuoi lasciare senza far nulla ???
il bello di Linux è proprio questo

Poi sinceramente ho provato una registrazione di un Canale SD sul rasp tramite xbmc e sinceramente non l'ho visto così male

VDR già compilato sotto arm solo che mi so inchiodato nella fase di creazione della SD

VDR Italia

SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana

Re: SifBox una distro VDR Tutta Italiana