how can I change video resolution on lubuntu?

Johan

For some people this is obvious, for others it might be good to know that it's also a good practice to check and make sure the device after of=X, is really the device you want to write to!
Once started, some crucial data may already have been overwritten if you selected the wrong device.
I suggest checking the following with parted (or a similar program): parted /dev/sdX print

1. parted /dev/sda print
   
2. Model: ATA WDC WD1200JB-00D (scsi)
   
3. Disk /dev/sda: 120GB
   
4. Sector size (logical/physical): 512B/512B
   
5. Partition Table: msdos
   
6. Disk Flags:
   
7. 
   
8. Number  Start   End     Size    Type      File system  Flags
   
9. 1      32.3kB  12.6GB  12.6GB  primary   ntfs         boot
   
10. 2      12.6GB  120GB   107GB   extended               lba
    
11. 5      12.6GB  120GB   107GB   logical
    

Copy code

If you want to write to a uSD card of 8GB (or 16GB/32GB) and you see something like above, then you do not have the correct device.

(When partitions are already present, do know that /dev/sda1 is not the same as /dev/sda.)

fritz

@Johan
For me it's obvious, maybe for others no.
thanks for pointing this out.

@piento
OK
It works for me, I have no idea why for you it does not the work.
upload a new image with a modified uboot seems to me an overkill.
Sorry I can not help you.

It would be nice if someone 'else can confirm that it works.
Thanks

piento

ok.. i have retried and now works!


thx

zhao_steven

@fritz  Thank you very much.

moinejf

fritz replied at 2015-5-18 07:20
Try to write the attached "new" u-boot on SD-card.

Instructions:

Hi  Fritz,

I am trying to compile the u-boot on my Cubox with Debian armhf and gcc-4.9.2.
After fixing some problems (see http://moinejf.free.fr/opi2/u-boot.patch - the patch is relative to lichee/brandy/u-boot-2011.09/),
linking fails because BOOTADDRESS is not defined, giving ". = ;" in u-boot.lds.
Do you know why? Otherwise, is this value important? (i.e. may I set '.' to '0'?)

Otherwise, you built a u-boot with an other screen resolution. I searched the u-boot source without finding where this parameter is set.
Where must I act?

fritz

Thats an old crappy, shitty u-boot that only compiles with an old crappy, shitty old toolchain
why do you need to compile u-boot?
if you want to change resolution parameter you need to modify sys_config.fex

markwinger

Where is this file sys_config.fex file.  I dont file in in the image?

root@orangepi:/# find . | grep sys_config.fex
root@orangepi:/#

fritz

It's dumped from the android image

moinejf

fritz replied at 2015-5-27 03:08
Thats an old crappy, shitty u-boot that only compiles with an old crappy, shitty old toolchain
wh ...

I want to boot my OPI2 with the root file system on a USB hard disk as I did with the Cubox.

sys_config.fex is used in the boot0, and, indeed, there is no armhf tool for updating the boot0.. ?

Do you know why putting uEnv.txt or boot.scr with the uImage does nothing?

fritz

Allwinners u-boot present in the H3-SDK does not support this.
sunxi-u-boot does not support the H3
mainline-u-boot does not support the H3.
this is the reality