

Sujet : VU+ DUO reste sur "starting"
-
24-08-2012, 20:36 #1
- Inscrit
- Feb 2010
- Âge
- 36
- Messages
- 20
- Récepteur
- hatlas hd 200s
- TV
- samsung 55 pouces
VU+ DUO reste sur "starting"
Salam aleykoum et bonne fete de l'Ai¨d
Mon vu+ Duo reste sur "strarting"
Le boot doit être corrompu.
Donc plus de USB en Facade et plus de ETH0. La RS232 fonctionne. Mais comme pas de réseau, je peux rien faire avec vu+ util
J'ai essayé putty, mais rien à faire car je ne peux rien charger.
Quelqu'un a t'il une idée?
merci par avance
-
24-08-2012, 23:51 #2
- Inscrit
- Aug 2012
- Lieu
- BELGIQUE
- Âge
- 44
- Messages
- 27
- Récepteur
- VU+ DUO 2
- TV
- PANASONIC 55" 3D
En me baladant sur le net, j'ai trouver un forum plutot pas mal et qui pourrait t'aider. La Team Ferrari!!!
http://www.8a8f8.com/
Il faut savoir qu'il y a clone et clone... d'apres eux... et si tu as un clone cheap, toutes mes condoleances!
En espérant t'avoir aidé!
UrabusVu+ DUO2, VTI 9, WICARDD 1.18
Abo off Telesat Full, Carte TNT Sat
Antenne BIG BISAT, 5W 9E 13E 19.2E
DiseqC 17/8
-
25-08-2012, 01:29 #3
- Inscrit
- Feb 2010
- Âge
- 36
- Messages
- 20
- Récepteur
- hatlas hd 200s
- TV
- samsung 55 pouces
-
26-08-2012, 00:06 #4
- Inscrit
- Jul 2008
- Messages
- 341
- Récepteur
- vu+ duo
- TV
- samsung
-
26-08-2012, 09:37 #5
- Inscrit
- Feb 2010
- Âge
- 36
- Messages
- 20
- Récepteur
- hatlas hd 200s
- TV
- samsung 55 pouces
bonjour,
merci pour ton aide.
j'ai essayé dreamup mais rien.
c'est un vu+ duo of.
merci pour l'aide
-
26-08-2012, 10:21 #6
- Inscrit
- Nov 2007
- Âge
- 60
- Messages
- 530
- Récepteur
- duo2
- TV
- sony
-
26-08-2012, 10:45 #7
- Inscrit
- Feb 2010
- Âge
- 36
- Messages
- 20
- Récepteur
- hatlas hd 200s
- TV
- samsung 55 pouces
bonjour,
le duo ne boot plus sur la cle.
j'ai essayé avec plusieurs cles, il veut rien savoir.
merci pour tes conseils.
-
26-08-2012, 10:58 #8
- Inscrit
- Nov 2007
- Âge
- 60
- Messages
- 530
- Récepteur
- duo2
- TV
- sony
essaie sa
1) Arranque Putty y configurelo con estos datos (115200,8,n,1), conecte su cable Null Modem al puerto RS232 del ordenador y VU+, arranque su VU+
2) Lance este comando desde Putty.
Código:
boot -z -elf flash0.kernel: 'rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 bcmrac=3`
3)Ahora su VU debe arrancar desde la Flash
4) Vuelva a conectar con Putty y lance ahora este nuevo comando.
Código:
flash_eraseall /dev/mtd5
5) Reinicie su VU+
Terminado el proceso, ahora su VU+ debe arrancar sin problemas.
-
26-08-2012, 11:06 #9
- Inscrit
- Nov 2007
- Âge
- 60
- Messages
- 530
- Récepteur
- duo2
- TV
- sony
si sa marche pas j espere pour toi que elle ai sous garantie car beaucoup de chance que ce sois la plaquete en general on les repare pas on les remplace
-
26-08-2012, 11:27 #10
- Inscrit
- Feb 2010
- Âge
- 36
- Messages
- 20
- Récepteur
- hatlas hd 200s
- TV
- samsung 55 pouces
Bonjour,
J'ai essayé avec putty et ca donne ça:
CFE> boot -z -elf flash0.kernel: 'rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 bcmrac=3`
Loader:elf Filesys:raw Dev:flash0.kernel File: Options:rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 bcmrac=3`
Loading: 0x80001000/7078176 0x806c1120/122128 Entry address is 0x805594c0
TP1 Entry Address at 0x80000ffc = 805594c0
Starting program at 0x805594c0
Linux version 3.1.1 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP Sat Feb 4 21:29:53 CET 2012
Fetching vars from bootloader... found 11 vars.
Early serial console at MMIO32 0x10400b00 (options '115200n8')
bootconsole [uart0] enabled
Options: sata=1 enet=1 emac_1=1 no_mdio=0 docsis=0 pci=1 smp=1 moca=0 usb=1
Using 256 MB + 128 MB RAM (from CFE)
bootconsole [early0] enabled
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Determined physical RAM map:
memory: 10000000 @ 00000000 (usable)
bmem: adding 112 MB RESERVED region at 144 MB ([email protected])
Initrd not found or empty - disabling initrd
Zone PFN ranges:
Normal 0x00000000 -> 0x00010000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00010000
PERCPU: Embedded 7 pages/cpu @81203000 s4384 r8192 d16096 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: bmem=112M ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw rootflags=sync
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
Memory: 138096k/262144k available (5523k kernel code, 124048k reserved, 1145k data, 244k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Detected MIPS clock frequency: 405 MHz (202.500 MHz counter)
Calibrating delay loop... 403.45 BogoMIPS (lpj=201728)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
SMP: Booting CPU1...
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
SMP: CPU1 is running
Brought up 2 CPUs
NET: Registered protocol family 16
warning: USB IOC not initialized by bootloader, assuming active low
PCI2.3->SDRAM window: 512 MB
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
PCI: found device 14e4:8602 on SATA bus, slot 0 (irq 42)
pci 0000:01:00.0: BAR 5: assigned [mem 0x10510000-0x10510fff]
pci 0000:01:00.0: BAR 5: set to [mem 0x10510000-0x10510fff] (PCI address [0x10510000-0x10510fff])
pci 0000:01:00.0: BAR 6: assigned [mem 0x10511000-0x105117ff pref]
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource upg
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 128 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NTFS driver 2.1.30 [Flags: R/W].
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 269
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
loop: module loaded
brcm-pm: enabling sata clocks
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
scsi0 : sata_brcmstb
scsi1 : sata_brcmstb
ata1: SATA max UDMA7 mmio [email protected] port 0x10510000 irq 42
ata2: SATA max UDMA7 mmio [email protected] port 0x10510100 irq 42
Broadcom STB NAND controller (BrcmNand Controller)
bcmemac: Broadcom STB 10/100 EMAC driver v3.0
bcmemac: registered interface #0 at 0x10080000 as 'eth0' (00:1d:ec:02:81:68)
bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
usbcore: registered new interface driver zd1201
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
brcm-pm: enabling usb clocks
ehci-brcm ehci-brcm.0: Broadcom STB EHCI
ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci-brcm ehci-brcm.1: Broadcom STB EHCI
ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-brcm ohci-brcm.0: Broadcom STB OHCI
ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci-brcm ohci-brcm.1: Broadcom STB OHCI
ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
ata1: SATA link down (SStatus 4 SControl 300)
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Success! Registering the characther device success with 0
blackhole initialised
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
EBI CS0: setting up NAND flash (primary)
mtd->oobsize=0, mtd->eccOobSize=0
NAND_CS_NAND_XOR=00000001
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Block size=00020000, erase shift=17
NAND Config: Reg=55042200, chipSize=128 MB, blockSize=128K, erase_shift=11
busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB on CS0
Found NAND on CS0: ACC=d3000000, cfg=55042200, flashId=ecf10095, tim1=4232222d, tim2=00000d94
BrcmNAND version = 0x0201 128MB @00000000
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Found NAND flash on Chip Select 0, chipSize=128MB, usable size=128MB, base=0
brcmnand_scan: B4 nand_select = 40000101
brcmnand_scan: After nand_select = 40000101
page_shift=11, bbt_erase_shift=17, chip_shift=27, phys_erase_shift=17
Brcm NAND controller version = 2.1 NAND flash size 128MB @18000000
ECC layout=brcmnand_oob_bch4_4k
brcmnand_scan: mtd->oobsize=64
brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
-->brcmnand_default_bbt
brcmnand_default_bbt: bbt_td = bbt_main_descr
Creating 7 MTD partitions on "brcmnand.0":
0x000000000000-0x000007600000 : "rootfs"
0x000007600000-0x000007a00000 : "kernel"
0x000007a00000-0x000007c00000 : "boot"
0x000007c00000-0x000007d00000 : "cfe"
0x000007d00000-0x000007d80000 : "mac"
0x000007d80000-0x000007e00000 : "env"
0x000007e00000-0x000007f00000 : "nvm"
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
usb 2-1: new high speed USB device number 2 using ehci-brcm
scsi2 : usb-storage 2-1:1.0
ata2: SATA link down (SStatus 4 SControl 300)
UBI: max. sequence number: 2
UBI: attached mtd0 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 118 MiB
UBI: number of good PEBs: 942
UBI: number of bad PEBs: 2
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 929
UBI: total number of reserved PEBs: 13
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 2/1
UBI: image sequence number: -582639778
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(8,1)
UBI: background thread "ubi_bgt0d" started, PID 47
Please append a correct "root=" boot option; here are the available partitions:
1f00 120832 mtdblock0 (driver?)
1f01 4096 mtdblock1 (driver?)
1f02 2048 mtdblock2 (driver?)
1f03 1024 mtdblock3 (driver?)
1f04 512 mtdblock4 (driver?)
1f05 512 mtdblock5 (driver?)
1f06 1024 mtdblock6 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
Rebooting in 180 seconds..
-
26-08-2012, 11:31 #11
- Inscrit
- Feb 2010
- Âge
- 36
- Messages
- 20
- Récepteur
- hatlas hd 200s
- TV
- samsung 55 pouces
bonjour,
avec putty en faisant ctrl+u et ctrl + c , je suis sur le répertoire CFE.
je ne connais pas linux.
si quelqu'un peut me donner la ligne de commande pour lancer la cle usb avec le cfe sous CFE ?
merci pour vos réponses
-
26-08-2012, 13:08 #12
- Inscrit
- Mar 2008
- Lieu
- PT
- Âge
- 62
- Messages
- 74
- Récepteur
- vu+duo/vusolo2
- TV
- Sharp/shamsung
-
26-08-2012, 13:36 #13
- Inscrit
- Feb 2010
- Âge
- 36
- Messages
- 20
- Récepteur
- hatlas hd 200s
- TV
- samsung 55 pouces
bonjour,
J'ai essayé mais rien.
merci pour ton aide
je cherche, si je trouve je dirai comment
cordialement
-
27-08-2012, 01:50 #14
- Inscrit
- Jul 2008
- Messages
- 341
- Récepteur
- vu+ duo
- TV
- samsung
bizarre que ca marche pas avec dreamup tu me surprends
pourtant pas besoin de reseau tu remets une image off et ca repart
il faut le cable null modem sans ca ca marche pas
sinon ca ressemble a un pb materiel et la pas grand chose a faireVU+ DUO OpenAtv Oscam 11160
VU+ SOLO2 OpenAtv Oscam 11214
ATLAS HD 200
-
27-08-2012, 02:42 #15
une question as tu un disk dur interne dans ton demo si oui debranche le ca peux resoudre ton pb
VUPLUS ULTIMO BLACKHOLE 3.0.3 CCCAM 2.2.1
REDLINE 2500 HD PLUS IPTV
ICONE Z7 GOGOTV ET VOLKA TV PRO
ICONE VOGUE PRO MULTISTREAM GOGO TV
BBOX MIAMI VOLKA TV PRO
Sujets similaires
-
Comparatif "VU+ UNO", "DREAMBOX 800 SE", "TECHNOMATE 800 HD" et "Forever 9510 HD"
Par MooneeR dans le forum Discussions GénéralesRéponses: 16Dernier message: 15-08-2012, 12:06 -
Comparatif "VU+ UNO", "DREAMBOX 800 SE", "TECHNOMATE 800 HD" et "Forever 9510 HD"
Par MooneeR dans le forum Vu+Réponses: 1Dernier message: 13-12-2011, 13:14 -
"" prio special""ECRAN NOIR ""seca 3 + viaccess 4""
Par m.momo1000 dans le forum Entraide CCcamRéponses: 12Dernier message: 07-08-2011, 11:12