• Content Count

  • Joined

  • Last visited

About vexation

  • Rank

Recent Profile Visitors

345 profile views
  1. Fine that you have searched. Sometimes the problem is to use the right searching terms. I have always looked for displayproblems | resolution | xfce and so on ;O) I have never looked for Motorola Lapdock. It would be nice, if you could add it to the documentation. But how I have written: With Armbian 4.2.3 Jessie everything works out of the box. BTW: Quitt this topic with "solved"? How can I do this
  2. Supplement: Installed armbian 4.2.3 jessie on another Micro SD Card. There were no problems with Display resolution. Funny, now I have two working boot systems;O)
  3. solved!!! After my last post I have thought a little bit of it ;O) /etc/rc.local is a file and not a directory, how I have written. nano /etc/rc.local fbset -xres 1366 -yres 768 exit 0 A reboot and it works!!! Many thanks for your kind support. Without "fbset" I would not get it ;O) One last question: How can I changed this post to "solved"?
  4. Sorry - I have just seen you have written to change resolution with fbset in /etc/rc.local. Do you mean I should create a fb.modes file in /etc/rc.local? Would this commands be the right one? Should I only set the one desired mode (1366*768) into the file? cp /etc/fb.modes /etc/rc.local/ mv /etc/fb.modes /etc/bak_fb.modes fbset -db /etc/rc.local/fb.modes regards
  5. Okay, fbset -i output: mode "1920x1080-60" I have checked the modes in /etc/fb.modes - there are several "modes". When I try: fbset 1152x864-60 output: ioctl FBIOPUT_VSCREENINFO: invalid argument fbset -fb /dev/fd0 1152x864-60 output: ioctl FBIOPUT_VSCREENINFO: invalid argument (also with dev/fd1 ;O) fbset --test 1152x864-60 output: ioctl FBIOPUT_VSCREENINFO: invalid argument ##################### What worked: fbset -xres 1152 -yres 864 ##################### But after that, my "Desktop" was not in the whole visible ;O) After that I used fbset -xres 1366 -yres 768 fbset -i >> /etc/fb.modes (deleted the not needed last lines) fbset 1366x768-111 # This time no (error)output fbset /dev/fb0 1366x768-111 export FRAMEBUFFER=/dev/fb0 (after a reboot also with /dev/fb1) reboot When I invoke fbset -i it is back to mode "1920x1080-60" ;O) In the beginning I have made a new bootable micro SD Card and changed the values for display in /boot/boot.cmd for , but without any effect. But when I changed it with the command it works: a10disp changehdmimodeforce 4 Maybe it was an option to add this command or fbset to a file while the system boot up? Thanks for your support ;O)
  6. Hallo, I have armbian 3.4.109 (Jessie) on a cubietruck. It is connected to a Motorola Lapdock. I have the problem, I could not change the resolution (xfce 4) from 1920x1080. Tried following steps: xrandr output: Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 60.00* error Message: Failed to get size of gamma for output default cvt 1280 800 output: # 1280x800 59.81 Hz (CVT 1.02MA) hsync: 49.70 kHz; pclk: 83.50 MHz Modeline "1280x800_60.00" 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync When I try to add new entry with xrandr, I always get error messages. Once the gamma value is missing. When I add a gamma value, it sais, the Display "Screen 0" is not known: root@cubietruck:~# xrandr --output "Screen 0" --gamma 1.0:1.0:1.0 xrandr: Failed to get size of gamma for output default warning: output Screen 0 not found; ignoring xrandr: Need crtc to set gamma on. OUTPUT from logfile: root@cubietruck:/var/log# cat Xorg.0.log | grep gamma [ 513.429] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) root@cubietruck:/var/log# cat Xorg.0.log | grep screen [ 513.401] Kernel command line: console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1 [ 513.404] (==) No screen section available. Using defaults. [ 513.405] (==) No monitor specified for screen "Default Screen Section". [ 513.496] (II) GLX: Initialized DRISWRAST GL provider for screen 0 In the logfile the screen is specificate as "Screen 0" and the gamma set to 1.0 1.0 1.0? I tried several options with xrandr (add a new entry or change one - but it never works... Is someone there with an advise? I have read different threads in other forums, but nothing helped. Or should I remove all desktop manager and install them again? Regards vexation
  7. Hallo, found your post yesterday. I had a similar problem with my Micro SD-Card. 1. Downloaded Armbian 3.xx 2. Used dd command, which works fine 3. Tryed to boot up my Cubietruck, but it could not finish to boot (can't remember the exact message). Then I tryed several times to make a bootable Micro SD Card (I have tested additional on the same card a Raspbian for my Banana Pi, which works!). Again: Tryed it with armbian (3.xx and 4.xx); tested the card (f3), but with each try it get worst. At last the card was not recognized by Debian system. After all I have pushed it into my Windows PC and checked the card for errors. This time there were no error messages!! Downloaded Armbian with Windows PC, used the installer, pushed the card into the Cubietruck and everything works well (except wlan - but this is another problem ;O) It seems my SD Card reader on my Debian Laptop was faulty . The strange thing, sometimes it works well, but in other cases it could not finish a process. I have also tryed another Micro SD Card (with the faulty reader) which works well years ago. But when I have checked it with f3 there were also error messages (f3 has interrupted writting on it). Hope you will solve your problem ;O) Regards vexation