Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

CABBA

Members
  • Joined

  • Last visited

  1. Here is another interesting thing I noticed, whenever the pi boots in the 1024x768 mode (which is random now) the TV shows DVI 1024x768, not hdmi 1024x768. Sound did not work with the HDMI cable and the TV obviously does not have dvi nor does the pi. Now I unplugged the HDMI cable from the TV when desktop loaded and plugged it back in. It changed to HDMI 1024x768 and sound worked again. Settings also showed 1024x768 max, no ghost screen and main screen under hdmi-1 with no info. So forced HDMI extraargs works, but I'm more than sure this TV is giving the sunxi kernel hell with drivers and mapping the proper pipeline.
  2. Hello everyone, back again for assistance! This is for the Orange PI PC Plus. I have since resolved the no signal issue mostly, though ran into a new one by a total accident that revealed that the display is not being mapped properly, nor is it sending the signal to the display properly, causing increased load on the pi, delay in graphical rendering seen in simple desktop use, emulation and videos. Here's how I got to that point. When I fixed the HDMI audio by adding extraargs=HDMI.audio=1 to armbianenv.txt and the changed HDMI.audio=EDID:0 to =1 on boot.cmd then recompiled it with mkimage, I rebooted the pi and a new resolution came to the display from boot to 1024x768, it went to login screen for the first time in forever, no no signal that I had to wait for autologin, and loaded the desktop. Everything worked MUCH better, no screen delays, emulation was smooth, videos smooth and xrandr only showed one screen HDMI-1. There was no longer a ghost screen under none-0 and the TV was no longer under hdmi-1-1. Things looked great as the pi ran cooler and better, until I completely shut it off and unplugged the power. Turning it back brought back the 1920x1080 forced resolution and the no signal during login, and screwed up the desktop to the point where I had to reset the settings to we the desktop normally. So how do I tell KMS to use the proper native support for this TV that it briefly did? I know for a fact its its true resolution because the manufacturer says 1024x768 in normal mode and 1366x768 in wide zoom mode. And also from the 60 fps emulation from the hdmi-1-1 is not as smooth as the hdmi-1 one. Video was a little harder to tell. Here's some extra info: - with hdmi-1-1 tv zoom mode says just scan, along with others like wide, normal, cinema. Resolution max went up to 1920x1080 - with hdmi-1 it TV zoom mode only had wide normal. Resolution max was 1024x768 - with hdmi-1-1 there's a name MS Telematica 52" - with hdmi-1 there was nothing. PS. Could PI be mapping the screen as an external rather then standard?
  3. Seems like the issue is fixed, although I believe this is more of a temporary solution. Here's what I did: - Upon a freshly flashed image, I created a sudo account without a password and let the pi boot to slick greeter screen. - When the screen went to no signal, I waited a few seconds to make sure login box is there and pressed enter on keyboard. - Once the NumLock light on keyboard came on, I unplugged the HDMI cable on the pi and plugged it back in. Screen came on displaying multi-display setup and the full desktop environment. - I ran xrandr | grep "connected" 1-None-1 1920x1080+0+0 0mm x 0mm 2-HDMI-1-1 1920x1080+0+0 708mm x 398mm I am now confused because the manufacturer says native is 1366x768, as does the sunxi kernel, yet the display allows rendering at 1920x1080. I set display 2 to default and set resolution to 1366x768 just in case. Also ID of screen 2, which is my TV says MS Telematica 52", which is also not the manufacturer OR right size. Now, is there a permanent fix to remove this ghost screen set on 1? Or is this a quirk of the pi?
  4. Thank you, Roberto, Did as you suggested with startx, here's what happened: - screen went to black then to no signal. - I brought tty back and try to start startx again, said xinit connection to x server lost. Then waiting for x server to shutdown, successfuly terminated, closing log file. - no EE Here's something I noticed: - On kernel command line, disp.screen0_output_mode=1366x768p60 and hdmi.audio=EDID:0 My guess is that the TV is the culprit and needs an auto resolution script for lightdm, or to force a resolution with lightdm that can handshake with this screen. Now I'm sort of a beginner with this, how can I go about telling lightdm to resolve the handshake with auto detect? Since sunxi kernel does it well and has no issues, can a script be made with xrandr for lightdm to force the program into auto detect?
  5. Hello, I have 2 orange pi PC plus units that upon booting go to no signal when lightdm service starts (the suppose to be slick greeter screen). This is with Ubuntu XFCE 22.11 trunk 59 image, and the same is with 22.11 trunk 1. Here are some details: - switching to tty works fine. Display returns. 1920x1080 - xrandr says no display - running bin files that use graphical says failed to open display - changing lightdm resolution in conf file to 1280x720 does nothing - this happens to both units - using HDMI 1.4 cable that works with a laptop outputting the same 1920x1080 resolution, so not a cable or TV issue. Questions: - is this an issue with Wayland and x11? If so, how to make the handshake work with the screen? - could the HDMI ports be somehow bad on both units? - could the TV be lying about the resolution then? Confusing the graphical rendering for the pi? - unfortunately there is no way for me to force an EDID handshake with a bin extraction method, no windows laptop with admin priveleges. Is there another way?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.