1748 replies to this topic

[Taykun345]

Almost every time I visit commit history i get 500 error. What are they thinking? Very unprofessional and they will certainly lose users with this attitude.

[Persian Prince]

Almost every time I visit commit history i get 500 error. What are they thinking? Very unprofessional and they will certainly lose users with this attitude.

 

they already did , just take a look at github users

[Persian Prince]

sourceforge just doesn't work! Trying to view the proposed commits of persian prince or latest commits in OpenPLI and I usually get 500 errors. They screwed it completely!

 

you can take a look at them here : https://github.com/O.../commits/master

[Persian Prince]

another fix for https://sourceforge....nwebif.bbappend

 

i did add "dm7020hd.jpg" and "xp1000.jpg" here : https://github.com/E...ic/images/boxes

 

so you can change "unknown.jpg" for them

[Persian Prince]

@MiLo

 

check your solo2 build my friend , it's not ok

 

mine is ok with 3.3.8 and new drivers

[MiLo]

Yours is mine. So what do you mean?

[Persian Prince]

i mean solo2 with new kernel and drivers is ok in my OE but it seems it's not ok in your OE

 

check the logs maybe we missed something

[MiLo]

What logs?

[Persian Prince]

image logs like log.do_rootfs there must be some logs so we can read them and see what's wrong

[MiLo]

Nothing wrong there. Other suggestions?

[Persian Prince]

hhmm maybe we should clean the kernel first

 

try "bitbake -c cleansstate virtual/kernel" then build (on the server)

 

i did remove my build-vusolo2 folder and rebuilded

[MiLo]

Just to be clear: You are claiming that you built an OpenPLi 3 image for the vusolo2 from the current sources, and that it has no problems with (keyboard) input? Is that correct?

I have two build environments (for OpenPli 3 and 4), both delivered an image with buggy input, and the buildserver did the same.

[MiLo]

hhmm maybe we should clean the kernel first
try "bitbake -c cleansstate virtual/kernel" then build (on the server)

That has already happened when the package changed its version number. So it's not going to make a difference (just to humor you, I'll try it anyway some day).

[Persian Prince]

no i have my own OE and i did commit solo2 changes for your OE so you can build kernel 3.3.8 too (contribution)

 

there are some input problems with solo2 and ultimo and you can see them in other vuplus images too like BH , i think Vu+ should do something about it not us

 

and about bump PR i know but sometimes it's good to clean the kernel to be sure

[Persian Prince]

a new merge request : https://sourceforge....ge-requests/28/

 

add missing openwebif box pictures

 

i did add these pictures here : https://github.com/E...ic/images/boxes

[MiLo]

there are some input problems with solo2 and ultimo and you can see them in other vuplus images too like BH , i think Vu+ should do something about it not us

Now I'm confused. What problem were you referring to then?

[Persian Prince]

there are some input problems with solo2 and ultimo and you can see them in other vuplus images too like BH , i think Vu+ should do something about it not us

Now I'm confused. What problem were you referring to then?

 

for example entering numbers in USALS

[MiLo]

That would be the "input problems" that other teams are also seeing right? Or is that an OpenPLi exclusive?

[Persian Prince]

as far as i know it's global , for example we have our own OE but we're using your enigma2 and we have input problems , we did change ultimo remote and still the same

 

and take a look at http://openpli.org/f...ndpost&p=353701 otherwise your tonight build won't be ok

 

and another simple merge request : https://sourceforge....ge-requests/28/

[Rob van der Does]

as far as i know it's global , ....

I tried Open-ViX and Open-ATV but in both there is no problem in this area (using the 3.3.8 kernel and the 8/5 drivers).