Jump to content


Photo

Vu+ Duo2 Openpli 4.0 issue


  • Please log in to reply
29 replies to this topic

Re: Vu+ Duo2 Openpli 4.0 issue #21 WanWizard

  • PLi® Core member
  • 70,528 posts

+1,811
Excellent

Posted 28 May 2014 - 18:30

We know the Duo2 becomes very slow when the box boots with a date < 1970, but as far as I know the Solo2 doesn't have that problem.

But both seem to have an issue with the setup wizard, and refusing to boot afterwards. It's also seen on an ET10K twice, but not reproducable.

 

So we're talking about two different issues.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Vu+ Duo2 Openpli 4.0 issue #22 Jedin

  • Member
  • 22 posts

0
Neutral

Posted 28 May 2014 - 18:52

I have tried different methods, but without result. But i send a list that i write "dmesg" with Telnet. Maybe you can see some is problem?

bcm40nm_pm_sata_enable 00
ahci: SSS flag set, parallel bus scan disabled
ahci strict-ahci.0: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl platform mo
e
ahci strict-ahci.0: flags: ncq sntf stag clo slum part
scsi0 : ahci_platform
scsi1 : ahci_platform
ata1: FORCE: PHY spd limit set to 1.5Gbps
ata1: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x100 irq 42
ata2: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x180 irq 42
brcmstb_nand: NAND controller driver is loaded
__clk_enable: network [1]
bcm7425_pm_network_enable 00
__clk_enable: enet [1]
bcm40nm_pm_genet_enable 00
Found PHY at Address 3
Config GPHY through MDIO
__clk_disable: enet [0]
bcm40nm_pm_genet_disable 00
__clk_disable: network [0]
bcm7425_pm_network_disable 00
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
__clk_enable: usb [1]
ata1: SATA link down (SStatus 0 SControl 310)
bcm40nm_pm_usb_enable 00
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 66, 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: 1 port 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 67, 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: 1 port detected
ehci-brcm ehci-brcm.2: Broadcom STB EHCI
ehci-brcm ehci-brcm.2: new USB bus registered, assigned bus number 3
ehci-brcm ehci-brcm.2: irq 71, io mem 0x10490300
ehci-brcm ehci-brcm.2: USB 0.0 started, EHCI 1.00
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 1 port detected
ehci-brcm ehci-brcm.3: Broadcom STB EHCI
ehci-brcm ehci-brcm.3: new USB bus registered, assigned bus number 4
ehci-brcm ehci-brcm.3: irq 72, io mem 0x10490500
ehci-brcm ehci-brcm.3: USB 0.0 started, EHCI 1.00
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 1 port 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 5
ohci-brcm ohci-brcm.0: irq 68, io mem 0x10480400
ata2: SATA link down (SStatus 0 SControl 300)
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 1 port detected
ohci-brcm ohci-brcm.1: Broadcom STB OHCI
ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 6
ohci-brcm ohci-brcm.1: irq 69, io mem 0x10480600
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 1 port detected
ohci-brcm ohci-brcm.2: Broadcom STB OHCI
ohci-brcm ohci-brcm.2: new USB bus registered, assigned bus number 7
ohci-brcm ohci-brcm.2: irq 73, io mem 0x10490400
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 1 port detected
ohci-brcm ohci-brcm.3: Broadcom STB OHCI
ohci-brcm ohci-brcm.3: new USB bus registered, assigned bus number 8
ohci-brcm ohci-brcm.3: irq 74, io mem 0x10490600
usb 4-1: new high-speed USB device number 2 using ehci-brcm
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 1 port 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
lirc_dev: IR Remote Control driver registered, major 254
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR SANYO protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR LIRC bridge handler initialized
Linux video capture interface: v2.00
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright© Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
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
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
PM: CP0 COUNT/COMPARE frequency does not depend on divisor
EBI CS0: setting up NAND flash (primary)
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit
brcmnand brcmnand.0: 1024MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit,
amming ECC
Bad block table found at page 524224, version 0x01
Bad block table found at page 524160, version 0x01
Creating 4 MTD partitions on "brcmnand.0":
0x000002700000-0x000040000000 : "rootfs"
0x000002700000-0x000040000000 : "rootfs(redundant)"
0x000000200000-0x000000900000 : "kernel"
0x000000900000-0x000000b00000 : "mac"
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 3-1: new high-speed USB device number 2 using ehci-brcm
scsi2 : usb-storage 3-1:1.0
scsi 2:0:0:0: Direct-Access     CHIPSBNK v3.3.8.1         5.00 PQ: 0 ANSI: 2
sd 2:0:0:0: Attached scsi generic sg0 type 0
sd 2:0:0:0: [sda] 4125472 512-byte logical blocks: (2.11 GB/1.96 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 0b 00 00 08
sd 2:0:0:0: [sda] No Caching mode page present
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] No Caching mode page present
sd 2:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 2:0:0:0: [sda] No Caching mode page present
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] Attached SCSI removable disk
UBI: max. sequence number:       0
gluebi (pid 1): gluebi_resized: got update notification for unknown UBI device
 volume 0
UBI: volume 0 ("rootfs") re-sized from 509 to 7794 LEBs
UBI: attached mtd0 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            985 MiB
UBI: number of good PEBs:        7876
UBI: number of bad PEBs:         4
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:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 7876
UBI: number of PEBs reserved for bad PEB handling: 78
UBI: max/mean erase counter: 300/48
UBI: image sequence number:  1040820366
UBI: background thread "ubi_bgt0d" started, PID 46
UBIFS: parse sync
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   518696960 bytes (506540 KiB, 494 MiB, 4085 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:14.
devtmpfs: mounted
Freeing unused kernel memory: 192k freed
fuse init (API version 7.18)
procmk_init
dvb_bcm7424: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
DVB: registering new adapter (vuduo2)
Booted !
Booted !
bcm7424: hotplug_callback():
Hotplug - status.connected 1:0
bcm7424: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
[GPIO]Default
[GP]:brcm_pwm_init

bcm7424: hotplug_callback():
Hotplug - status.connected 1:1
brcm_demux_init: $Id: bcm_demux.c,v 0.7 $
[MPVR]: >> misc_pvr_init
[VID]: <6>bcm7335_video_init
[AUD]: <6>bcm7335_audio_init
DVB: registering adapter 0 frontend 0 (Vuplus FE)...
DVB: registering adapter 0 frontend 0 (Vuplus FE)...
bcm7424: bcm7335_frontend_init(): vtuner1 : 3
BKNI_P_GetTrackAllocEntry_resize: resizing from 4096->8192
BKNI_Malloc(linuxkernel) top users:
    blocks,   bytes, filename:line
       635,  135868, ../BSEAV/lib/utils/balloc.c:35
       631,   42908, ../magnum/basemodules/mem/bmem_system.c:306
       409,   55624, magnum/commonutils/mrc/src/bmrc_monitor.c:972
  KSEG1 : 0x80000000
lcr 0x3
irq : 63 ret : 0
input: dreambox advanced remote control (native) as /devices/virtual/input/inpu
0
Resistor Div: 0x0
Duo2 LCD initialized 0
[LCD]: registered
[CI]: registered ci0 249
[CI]: registered ci1 248
[DFP]: registered dbox fp
[DFP]: Scart 9597 is found 0

[SC]: registered sci0
[SC]: registered sci1
system_time_set wakeup mode get
system_time_set wakeup mode get 0xc1
FP Update Driver Loaded
VFDController Update Driver Loaded
fpga update driver loaded
usb 4-1: reset high-speed USB device number 2 using ehci-brcm
phy0 -> rt2800_init_eeprom: Error - Invalid RT chipset detected.
phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
usbcore: registered new interface driver rt2800usb
rtusb init rt2870 --->


=== pAd = f809d000, size = 511144 ===

usbcore: registered new interface driver rt2870
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_SELECT_SOURCE 1
[VID]: VIDEO_PLAY 1  2 0
[VID]: VIDEO_CONTINUE 1  1
[VID]: VIDEO_CLEAR_BUFFER 1  1 0
[VID]: VIDEO_STOP 0  1
[VID]: VIDEO_SELECT_SOURCE 0
__clk_enable: network [1]
bcm7425_pm_network_enable 00
__clk_enable: enet [1]
bcm40nm_pm_genet_enable 00
eth0: Link up, 100 Mbps Full Duplex
NET: Registered protocol family 10
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_SELECT_SOURCE 1
[VID]: VIDEO_PLAY 1  2 0
[VID]: VIDEO_CONTINUE 1  1
[VID]: VIDEO_CLEAR_BUFFER 1  1 0
[VID]: VIDEO_STOP 0  1
[VID]: VIDEO_SELECT_SOURCE 0
eth0: no IPv6 routers present
[CI]: CI interface initialised

[AUD]: AUDIO_SET_MUTE 0
[AUD]: AUDIO_SET_MIXER -822993424
[AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
[AUD]: AUDIO_SET_MIXER : next left volume 0, right volume 0
[AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
[AUD]: AUDIO_SET_MIXER -822993424
[AUD]: AUDIO_SET_MIXER : amixl 32, amixr 32
[AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
[AUD]: AUDIO_SET_MIXER : next left volume -2355, right volume -2355
FE tune
FE tune
[AUD]: AUDIO_SELECT_SOURCE 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 6511456
[AUD]: AUDIO_PLAY 6511456 decoder start : 0
[AUD]: AUDIO_CONTINUE 6511456 1 aph=0xce8f5680
[AUD]: setting mute : 0
[VID]: VIDEO_SELECT_SOURCE 1
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_PLAY 0  2 0
[VID]: VIDEO_CONTINUE 0  1
[VID]: VIDEO_CLEAR_BUFFER 0  1 0
[AUD]: AUDIO_CHANNEL_SELECT 0
[VID]: VIDEO_STOP 0  1
[VID]: VIDEO_SELECT_SOURCE 0
[AUD]: AUDIO_STOP 6511456
[AUD]: AUDIO_CONTINUE 6511456 0 aph=0x0
[AUD]: AUDIO_CONTINUE aph=0 0 0
[AUD]: AUDIO_SELECT_SOURCE 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 6511456
[AUD]: AUDIO_PLAY 6511456 decoder start : 0
[VID]: VIDEO_SELECT_SOURCE 0
[VID]: VIDEO_GET_SIZE src w: 1280 h:720 display w:1280 h:720
[VID]: VIDEO_GET_SIZE aspect: 1 3
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_FREEZE 6511456  0
[VID]: VIDEO_PLAY 6511456  2 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 6511456  1
[AUD]: AUDIO_CONTINUE 6511456 1 aph=0xce8f5680
[AUD]: setting mute : 0
__clk_disable: enet [0]
bcm40nm_pm_genet_disable 00
__clk_disable: network [0]
bcm7425_pm_network_disable 00
__clk_enable: network [1]
bcm7425_pm_network_enable 00
__clk_enable: enet [1]
bcm40nm_pm_genet_enable 00
eth0: no IPv6 routers present
usb 3-1: USB disconnect, device number 2
root@vuduo2:~#



Re: Vu+ Duo2 Openpli 4.0 issue #23 WanWizard

  • PLi® Core member
  • 70,528 posts

+1,811
Excellent

Posted 28 May 2014 - 20:32

A USB tuner plugged in?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Vu+ Duo2 Openpli 4.0 issue #24 Jedin

  • Member
  • 22 posts

0
Neutral

Posted 28 May 2014 - 23:00

Yes, i forget take out USB-plug when i done test. But it is no matter when i tested with or without USB. I can only flash first time and do all to work fine and use only reboot Enigma. But if i want change mount to example HDD or network so it need do a real reboot so boot will be stuck direct and come never to Openpli beautiful summer-bootlogo. It is not problem with image OpenATV as i using now and all work really good. But i like best about Openpli because i have use this image in many years with Dreambox, but it is not fun with all issues with a advanced box Vu+ Duo2 as i paid for a lot money... :-/



Re: Vu+ Duo2 Openpli 4.0 issue #25 WanWizard

  • PLi® Core member
  • 70,528 posts

+1,811
Excellent

Posted 28 May 2014 - 23:50

Problem is we can't reproduce it. When I get back from my travels next week I will try it on my Duo2, maybe then we know more.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Vu+ Duo2 Openpli 4.0 issue #26 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 29 May 2014 - 07:54

My solo2 (which I have been using to try to reproduce the problem) doesn't have a harddisk. Maybe that is part of the problem.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Vu+ Duo2 Openpli 4.0 issue #27 vasilich07

  • Senior Member
  • 155 posts

+4
Neutral

Posted 29 May 2014 - 08:22

It appears that this problem has only Duo2...

By solo2 were no complaints


GI ET11000,Vu+DUO2 - 4W-90E Supral 120 (motor Stab  HH 120), 36Е- satellite antenna Nokia - 90

 xtrend ET9000 - Tests without a permanent connection


Re: Vu+ Duo2 Openpli 4.0 issue #28 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 29 May 2014 - 08:23

Wanwizard just explained that another users with two VU+ Solo2's had the same problem.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Vu+ Duo2 Openpli 4.0 issue #29 WanWizard

  • PLi® Core member
  • 70,528 posts

+1,811
Excellent

Posted 29 May 2014 - 09:38

Correct, this is the thread about it (http://openpli.org/f...e-keer-booten/, in Dutch), same problem.

 

And I have seen it once on an ET10K, and so did Frenske.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Vu+ Duo2 Openpli 4.0 issue #30 filou59

  • Member
  • 5 posts

0
Neutral

Posted 2 August 2014 - 08:39

Hello

 

To make some test with my new Duo2, I do some Flash of the box with Open PLI4 .

Don't remember the exact state of the box before Flash (Power OFF/Stanby) in all case.But on 3 try,  I had the problem 2 times.

 

The date was set in 1958.
Having set the date in the year 2000 in Telnet, and everything is ok.
 
date -s "2014-03-28 09:26"
 
 

Edited by filou59, 2 August 2014 - 08:39.

Vu+Duo² - Open PLI 4.0

Vu+Ultimo - Open PLI 4.0



5 user(s) are reading this topic

0 members, 5 guests, 0 anonymous users