• Content Count

  • Joined

  • Last visited

About perfstr

  • Rank
    Advanced Member

Recent Profile Visitors

550 profile views
  1. perfstr

    Hdmi 1280 x 800 display

    The new patch is attached to this message. I am not sure what should be its correct name, so kept it as created by Armbian build script. I would be glad to get a confirmation about it. kernel-sun8i-default.patch
  2. perfstr

    Hdmi 1280 x 800 display

    Hello, the pll change didn't cause any difference. But when I set DVI mode, this did the trick - the background has changed to black. BTW, in order to set the RGB565 mode using h3disp command, the fb_mode should be set to 10. Hope this will help also to somebody else.
  3. perfstr

    Hdmi 1280 x 800 display

    Hello, after I edited the sources manually, now it works, but shows purple background. Is this the only pll value to play with, or I need to change something else? I would like get correct results before publishing the patch. Thank you,
  4. perfstr

    Hdmi 1280 x 800 display

    Thank you for tip, Igor! Will do that.
  5. perfstr

    Hdmi 1280 x 800 display

    Hello, I've just tried to apply the z-0004-add_1280x800.patch file from the above link and was able to see in the new compilation [warn] z-0004-add_1280x800.patch [failed] I've compared the files in an older compilation and indeed, the patch was not fully applied. What is a good way to solve this problem (I assume that editing the source files is not a good way). Thanks,
  6. perfstr

    Hdmi 1280 x 800 display

    Hello, I also have the 1280x800 monitor. The patch z-004-add-addonal-2048x1536.txt didn't work for me. The monitor works well with Armbian based on mainline kernel, but I need to continue with 3.4.113 kernel. I was unable to download the u-boot-h3-video-helper.bin file - the site can't be reached. Where can I find the file? Thanks,
  7. Hello, I think, my problem is similar. After I downloaded and installed last Armbian version with mainline kernel in Orange Pi PC Plus board, in attempt to shut down both desktop and console systems, the last message in the console screen is "system halted". The console doesn't turn off. Any idea of how to avoid the problem?
  8. Hello Everyone, I would like to share my experience about how to boot Orange Pi almost silently in console mode (eliminate a lot of kernel messages on startup) without desktop and remove cursor blinking that can cause black rectangle appearing over white background, when painting to framebuffer. Many options that proposed as being able to reduce kernel messages on boot didn't work for me. So based on Armbian documentation I started to experience with armbianEnv.txt file in the /boot folder. The extraargs setting was not part of the default armbianEnv.txt file, but appeared in BOOT.CMD file. The setting extraargs=vt.global_cursor_default=0 quiet solved both above problems. Hope this will be helpful for somebody else.
  9. Hello, we have a working Armbian system that runs the user mode USB device and Windows application that uses LIBUSB to connect to device. Once we used another hardware platform for the device firmware. Now, when we switched to Orange Pi PC, I had to change the Windows part in order to adapt it for the USB OTG driver limitation. We used USB sniffer program in order to get USB traces of old and new devices. This way we were able to solve some startup problems. Please explain what .config file you mean - kernel configuration?
  10. Correction of path in Kernel configuration: Device Drivers -> Graphics support -> Console display driver support -> Framebuffer Console Rotation.
  11. In order for echo number to fbcon -> rotate or -> rotate_all to work, the kernel should be configured to support rotation in frame buffer, see kernel configuration tool: Device Drivers -> Graphics Support -> Support for framebuffer devices -> Framebuffer Console Support. Currently this requires custom build. I would consider to always enable frame buffer rotation support in default configuration.
  12. Hello, I would like to share my experience about development and debugging inside Armbian. On the beginning I tried to use Code::Blocks. But it crashed too many times, mostly during simple file editing. Then I found better IDE - CodeLite. When I wanted to debug a program, I found I have to install GDB. After installing and configuring it, the debugging looked to be possible, but every attempt finished with segmentation fault somewhere outside of my program, even before the first statement in main function was reached. After several attempts, I uninstalled and re-installed GDB and this time found recommended additional component - libc6-dbg. Installing this component fixed the fault problem. It looks a bit strange for me that the libc6-dbg is recommended and not required component. And another point - how would it be possible to detect during debugging that this component is missing? I hope this topic will help somebody else, who meets the problem.
  13. perfstr

    Autologin to Armbian console

    I found the solution - it should be similar to the change described in the link: change /lib/systemd/system/getty@.service file, ExecStart string to contain ExecStart=-/usr/bin/agetty --autologin username ... After the change is applied, the console screen still shows some text, which needs to be disabled. Any idea?
  14. Hello, I run my program system as a service in console mode, so no login is needed. The Linux system starts up almost quietly after changes in boot.scr. The only "small" thing that needs a solution is the login prompt. How can I prevent login prompt from appearing? I've tried some autologin options I found for different Linux systems, but they didn't work for me. Any suggestion?
  15. perfstr

    How to set framebuffer 16bpp in 1080p DVI

    The problem with colors exists in startup console screen, but desktop colors are fine, including terminal windows. If somebody has an idea of how the startup colors can be changed (adapted to RGB565 mode), please let me know.