[VU+ Solo] Can't Set Resolution TO 1080i

[bbbuk]

@Sicilian,

As a hunch, I asked the OP to try BH 2.1.5 and he said he could select 1080i, no problem at all.

Do you still think this is a driver/kernel problem because it's fine in BH and I would have thought BH would be using same driver/kernel as what has been used in a Vix build like 150 as they were both released around same time and will have have had same drivers/kernel in them both (I assume)?

@Tkr001, could you try fresh usb flash to vix 150 (if you haven't already)?

Thanks

 

[rossi2000]

the kernels maybe the same but the contents are likely to be alot different.

i bet our defconfigs our different.

 

[bbbuk]

the kernels maybe the same but the contents are likely to be alot different.

i bet our defconfigs our different.

Sorry in english that means what?

 

[rossi2000]

the file that builds the kernel

https://github.com/oe-alliance/oe-a...pes-linux/linux-vuplus-3.9.6/vusolo/defconfig

 

[rossi2000]

and the last commit for this was [vusolo 1] no free mem revert 1080p support
2months ago.

 

[bbbuk]

the file that builds the kernel

https://github.com/oe-alliance/oe-a...pes-linux/linux-vuplus-3.9.6/vusolo/defconfig

Thanks.

That makes sense as to why BH may work but an OE-A core image wouldn't.

Got to admit, I assumed that kernel would be supplied by VU+ just like the drivers are but obviously it's just drivers.

 

[bbbuk]

and the last commit for this was [vusolo 1] no free mem revert 1080p support
2months ago.

I just noticed that.

Fits in with timescales as OP couldn't go that far back to check due to hacking of your ftp site.

 

[rossi2000]

the kernel is supplied by vu initially,
then other folks amend it, then it also doenst get updated with changed etc.

 

[Tkr001]

@Sicilian,

As a hunch, I asked the OP to try BH 2.1.5 and he said he could select 1080i, no problem at all.

Do you still think this is a driver/kernel problem because it's fine in BH and I would have thought BH would be using same driver/kernel as what has been used in a Vix build like 150 as they were both released around same time and will have have had same drivers/kernel in them both (I assume)?

@Tkr001, could you try fresh usb flash to vix 150 (if you haven't already)?

Thanks

flashed 150 and as expected 1080i failed.

 

[Sicilian]

This should be fixed in next build 164 +

https://github.com/oe-alliance/oe-alliance-core/commit/88c526c62ecfe580f26d3d02bd7b54df965933d8

 

[Sicilian]

This should be fixed in next build 164 +

https://github.com/oe-alliance/oe-alliance-core/commit/88c526c62ecfe580f26d3d02bd7b54df965933d8

I tested this fix in ATV, 1080i setting now fixed. Next ViX build will have the fix.

 

[Tkr001]

Still a problem for me on 164

 

[Sicilian]

Did you fresh flash and setup? RS232 log?

 

[Tkr001]

Can't fresh flash cos 164 not available for download yet. Updated from 163. Will fresh flash when I can download 164 and will attempt boot log. Need to get a gender bender for my usb to serial cable. Did flash ATV which worked fine with 1080i for me too.

 

[Sicilian]

Can't fresh flash cos 164 not available for download yet. Updated from 163. Will fresh flash when I can download 164 and will attempt boot log. Need to get a gender bender for my usb to serial cable. Did flash ATV which worked fine with 1080i for me too.

I've just released only the VU+ Solo images, please fresh flash and test.

Other images have been held back due to couple of issues I've found.

Just need to know if 1080i is fixed on Solo please.

 

[Tkr001]

Yes 1080i works with fresh flash but there are issues starting samba/nfs so I guess we need to wait for those to be resolved

 

[Sicilian]

Yes 1080i works with fresh flash but there are issues starting samba/nfs so I guess we need to wait for those to be resolved

Yes, thats why other images have been held back and feeds left unstable.

 

[Tkr001]

Flashed 165, no settings restore. All good now. Thanks.