46 replies to this topic

[chafpa]

hello,

 

I wanted to flash a new image for the updates.

The image of today or yesterday that will not install on my Vu + Solo2.

I thought these update problems were resolved. Is it me who have a problem ?

PS : Testing done several times with different USB sticks. 

 

[Erik Slagter]

You have give more details about what you're doing and what's the problem.

[chafpa]

Installation starts and quickly VU SOLO appears on the decoder and the host of autumn picture on TV and I get stuck.

Unable to do something and there is no color wheel that appears.

[40H3X]

Just out of thought, how long do you wait when you see the autumn picture and decide that it has stuck. It came take xx minutes before autoinstall completes, if you have installed lots of applications. In my case, I have only installed 1 application, it takes about 3 minutes before autoinstall finishes.

[chafpa]

So I'll start again and wait longer.

I will come to you if I fail.

[Stan]

chafpa, on 20 Dec 2014 - 16:11, said:

I will come to you if I fail.

[Teesi]

I also had the same (?) problem, and was forced to return to a week old image. My Ultimo could not see the internal hard drives content, and without that nothing worked. I tried file system check, but it newer finished (the drive stopped spinning).

 

I tried -vuultimo-20141220 and 20141219 images (bad), then returned to 20141213 which does work fine.  

 

Support for filesystem missing from the new kernel?

[pilnikov]

I also had the same (?) problem. HDD not worked property. External usb dvb t stick still not worked. I have a vu + uno/ image 12.19 & 12.20 is bad

Edited by pilnikov, 20 December 2014 - 16:46.

[Erik Slagter]

It's not missing, but it's optional now. To be precise, ext4 support and cifs support. We've had similar reports in the Dutch forum and I will try to replicate my explication here.

 

VU+ (which we now use the BSP layer from) have decided, for the receivers that have little memory (uno, solo, duo, ultimo), that some kernel features are not compiled into the kernel. But they can be installed afterwards (kernel module). The relevant modules are for cifs support and for ext4 support. Ext3 support is still available inside the kernel.

 

The quickest way to resolve it, is to use telnet or ssh, login into the receiver and type these commands, which will download and install the modules:

opkg update
opkg install kernel-module-cifs
opkg install kernel-module-ext4
init 6 # reboot

We're still looking into a way to fix this in a cleaner way.

[chafpa]

Just out of thought, how long do you wait when you see the autumn picture and decide that it has stuck. It came take xx minutes before autoinstall completes, if you have installed lots of applications. In my case, I have only installed 1 application, it takes about 3 minutes before autoinstall finishes.

Well done. I waited 10 minutes. The decoder was paused. He had not restarted automatically.

I started at the remote control and the image of December 20 was installed.

Thank you for helping hand.

[ovidijuslr]

Ok will try too after work and see how it goes

[pilnikov]

It's not missing, but it's optional now. To be precise, ext4 support and cifs support. We've had similar reports in the Dutch forum and I will try to replicate my explication here.

 

VU+ (which we now use the BSP layer from) have decided, for the receivers that have little memory (uno, solo, duo, ultimo), that some kernel features are not compiled into the kernel. But they can be installed afterwards (kernel module). The relevant modules are for cifs support and for ext4 support. Ext3 support is still available inside the kernel.

 

The quickest way to resolve it, is to use telnet or ssh, login into the receiver and type these commands, which will download and install the modules:

opkg update
opkg install kernel-module-cifs
opgk install kernel-module-ext4
init 6 # reboot

We're still looking into a way to fix this in a cleaner way.

Thank you for supporting us foolish. After installation of the modules hard disk appeared, however, my external usb stick dvb-t rtl2832 based not operate properly. The system does not see him, and when you try to switch on the broadcasting channel produces a crash:

 

Traceback (most recent call last):

  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 46, in action

  File "/usr/lib/enigma2/python/Screens/ChannelSelection.py", line 2105, in cancel

  File "/usr/lib/enigma2/python/Screens/ChannelSelection.py", line 2111, in zapBack

ValueError: invalid null reference in method 'eServiceReference___ne__', argument 2 of type 'eServiceReference const &'

(PyObject_CallObject(<bound method ActionMap.action of <Components.ActionMap.ActionMap instance at 0x16ccaa8>>,('OkCancelActions', 'cancel')) failed)

getResolvedKey config.plugins.crashlogautosubmit.sendAnonCrashlog failed !! (Typo??)

getResolvedKey config.plugins.crashlogautosubmit.addNetwork failed !! (Typo??)

getResolvedKey config.plugins.crashlogautosubmit.addWlan failed !! (Typo??)

[Erik Slagter]

This may be the bug we just fixed (but I am not 100% sure). Try again tomorrow.

[delavega]

It's not missing, but it's optional now. To be precise, ext4 support and cifs support. We've had similar reports in the Dutch forum and I will try to replicate my explication here.

 

VU+ (which we now use the BSP layer from) have decided, for the receivers that have little memory (uno, solo, duo, ultimo), that some kernel features are not compiled into the kernel. But they can be installed afterwards (kernel module). The relevant modules are for cifs support and for ext4 support. Ext3 support is still available inside the kernel.

 

The quickest way to resolve it, is to use telnet or ssh, login into the receiver and type these commands, which will download and install the modules:

opkg update
opkg install kernel-module-cifs
opgk install kernel-module-ext4
init 6 # reboot

We're still looking into a way to fix this in a cleaner way.

 opgk install kernel-module-ext4 its "opkg" you made a mistake there

 

despite installing those, cifs share doesnt work on solo.

[delavega]

what a stupid idea from vu+ to remove it from the solo box

Edited by taboune, 21 December 2014 - 16:53.

[40H3X]

Did you reactivate the share?

[delavega]

yes multiple times i even deleted and re created it

[Erik Slagter]

Restart?

[delavega]

yes rebooted at least 3 times

[40H3X]

Just to be on the safe side both installations reported fine?