new drivers

[YipMan]

I've installed them without problems.
FYI I'm at work and I've done the update via SSH connection, after reboot the box it's come back online immediately.
I can only suggest to connect to your box via telnet/ssh and send the following command:

dmesg

and report here the output.

Hi!
I can not connect via ssh refuses all IP addresses, my receiver is set on the logo BLACKHOLE

 

[angelofsky1980]

Hi!
I can not connect via ssh refuses all IP addresses, my receiver is set on the logo BLACKHOLE

If you have in "Starting" phase your box should have already taken an IP address from DHCP or use the static IP you have setted up.
If both of these possibilities are gone the only thing it's a corrupted image but ATM it's impossible to determine in which manner because there is no debug/log infos about the possible problem.
Try also with telnet ....

 

[YipMan]

ok I'll try again

 

[YipMan]

Ok here is the content of dmesg :


NET: Registered protocol family 16
USB0: power enable is active high; overcurrent is active low
USB1: power enable is active high; overcurrent is active low
bio: create slab <bio-0> at 0
SCSI subsystem initialized
libata version 3.00 loaded.
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.
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource wktmr
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 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.
Registering unionfs 2.5.11 (for 3.3.0-rc3)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NTFS driver 2.1.30 [Flags: R/W].
msgmni has been set to 1116
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x10406900 (irq = 65) is a 16550A
console [ttyS0] enabled, bootconsole disabled
serial8250.0: ttyS1 at MMIO 0x10406940 (irq = 66) is a 16550A
serial8250.0: ttyS2 at MMIO 0x10406980 (irq = 67) is a 16550A
loop: module loaded
__clk_enable: sata [1]
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 mod e
ahci strict-ahci.0: flags: ncq sntf stag clo slum part
scsi0 : ahci_platform
scsi1 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x100 irq 41
ata2: SATA max UDMA/133 mmio [mem 0x10181000-0x10190fff] port 0x180 irq 41
brcmstb_nand: NAND controller driver is loaded
__clk_enable: network [1]
__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]
__clk_enable: network [1]
__clk_enable: moca_genet [1]
bcm40nm_pm_genet1_enable 00
__clk_enable: moca [1]
bcm40nm_pm_moca_enable 00
ata1: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
No PHY detected, not registering interface:1
__clk_disable: moca [0]
bcm40nm_pm_moca_disable 00
__clk_disable: moca_genet [0]
bcm40nm_pm_genet1_disable 00
__clk_disable: network [0]
bcmgenet: probe of bcmgenet.1 failed with error -5
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
__clk_enable: usb [1]
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 69, 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 70, 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 74, 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 75, 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 71, io mem 0x10480400
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 72, 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 76, 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 77, io mem 0x10490600
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
WARNING: You are using an experimental version of the media stack.
As the driver is backported to an older kernel, it doesn't offer
enough quality for its usage in production.
Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
3151d14aa6e983aa36d51a80d0477859f9ba12af [media] media: remove __dev* an notations
978ae2247fac3b330ecd1095823001d2c08c7efd [media] extract_xc3028.pl: fix permissions
73ec66c000e9816806c7380ca3420f4e0638c40e [media] stv0900: Multistream su pport
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
Success! Registering the characther device success with 0
blackhole initialised
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) 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: 0xda (Samsung NAND 256MiB 3,3V 8-bi t)
brcmnand brcmnand.0: 256MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, Ha mming ECC
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: bad block at 0x000000900000
nand_read_bbt: bad block at 0x000003300000
nand_read_bbt: bad block at 0x000008060000
nand_read_bbt: bad block at 0x0000090c0000
nand_read_bbt: bad block at 0x000009fa0000
nand_read_bbt: bad block at 0x00000e5c0000
Creating 4 MTD partitions on "brcmnand.0":
0x000001f00000-0x000010000000 : "rootfs"
0x000001f00000-0x000010000000 : "rootfs(redundant)"
0x000000200000-0x000000900000 : "kernel"
0x000000900000-0x000000a00000 : "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
UBI: max. sequence number: 3778
UBI: attached mtd0 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 225 MiB
UBI: number of good PEBs: 1791
UBI: number of bad PEBs: 9
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: 1791
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 17/11
UBI: image sequence number: 2020381919
UBI: background thread "ubi_bgt0d" started, PID 44
UBIFS: parse sync
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 223350784 bytes (218116 KiB, 213 MiB, 1759 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: 184k freed
NET: Registered protocol family 10
procmk_init
udevd (100): /proc/100/oom_adj is deprecated, please use /proc/100/oom_score_adj instead.
__clk_enable: network [1]
__clk_enable: enet [1]
bcm40nm_pm_genet_enable 00
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: Link up, 100 Mbps Full Duplex
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
svc: failed to register lockdv1 RPC service (errno 124).
eth0: no IPv6 routers present
out of order segment: rcv_next B6E9A3A9 seq B6E9A3AD - B6E9A94D
ofo requeuing : rcv_next B6E9A3AD seq B6E9A3AD - B6E9A94D
root@vusolo2:~#

 

[YipMan]

I have found that there is a problem with the file dvb-bcm7356.ko (size 12,117 Ko) but I do not know which

 

[Javi5555]

I have found that there is a problem with the file dvb-bcm7356.ko (size 12,117 Ko) but I do not know which

Same problem for me.
Is the first time that I´ve problem updating drivers with a Vu+ box.

Regards from Spain!

 

[Yannis_d]

these drivers decodes wma ?

 

[angelofsky1980]

these drivers decodes wma ?

Into che Changelog it's not reported and I'm pretty sure the answer is NO.
Write to Vu+ (www.vuplus.com) to support WM media formats.

 

[Yannis_d]

thank you i will do that

 

[Pedro C]

try using VUCC to upgrade your new drivers. Been doing that for a long time and never had any issues.

 

[YipMan]

Hi!
I restored my old drivers and restart my receiver is normally

 

[rassi]

Hi!
I restored my old drivers and restart my receiver is normally

Using USB DVB sticks? There is a driver issue at least with OpenViX images when using Sundtek DVB-T/C sticks.
Solo2 do not boot till end with newest drivers. 02.08 are the latest which does work with two Sundtek's.
19.08 drivers does recognize only one stick. So im staying with 02.08 drivers.

 

[YipMan]

Using USB DVB sticks? There is a driver issue at least with OpenViX images when using Sundtek DVB-T/C sticks.
Solo2 do not boot till end with newest drivers. 02.08 are the latest which does work with two Sundtek's.
19.08 drivers does recognize only one stick. So im staying with 02.08 drivers.

Excuse me, I did not understand your answer

 

[rassi]

Excuse me, I did not understand your answer

I meant to ask if you use external USB tuners as i do and did have same issue, box didn´t boot till end with newest drivers.