# Screen resolution problem during installation **URL:** \ **Category:** Installation\ **Created:** [July 1, 2026, 10:10pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404 "2026-07-01T22:10:31Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Bosquet](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/e95f7d/32.png) [@Bosquet](https://forum.endeavouros.com/u/Bosquet)\ **Post date:** [July 1, 2026, 10:10pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/1 "2026-07-01T22:10:32Z")
I am trying to install endeavouros on my raspberry Pi 4b to replace the currently un-maintained Manjaro, but I am having great difficulty in tracking progress, since a large slice of the left-hand side of the display is off-screen and I cannot read the start of the lines of the output. My monitor is an Acer P195HQL with a screen resolution of 1366x768 (according to the on-line manual) although the Systems Setting utility on Manjaro tells me it’s 1280x720. It’s a SVGA monitor, fed from the Pi via an HDMI/VGA adaptor. I don’t know how much of each line is invisible, and can’t tell whether I should be typing responses to on-screen prompts to move the install process on. I would be glad to know how I can get around this problem. ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [July 1, 2026, 10:13pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/2 "2026-07-01T22:13:27Z")
welcome, just moved the post to the correct location :enos: ---
**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\ **Post date:** [July 1, 2026, 10:16pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/3 "2026-07-01T22:16:40Z")
i have also issues when using non 1920x1080 displays, thats set in the boot.ini file .. at least for the odroid images, not sure about Pi ones.. but now as this is in the ARM subforum @pudge or @sradjoker will get informed ---
**Author:** ![Pudge](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pudge/32/17155_2.png) [@Pudge](https://forum.endeavouros.com/u/Pudge)\ **Post date:** [July 2, 2026, 12:50am UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/4 "2026-07-02T00:50:30Z")
@Bosquet Welcome to the EndeavourOS forum. 🤝 I hope you enjoy your time here. I assume you are installing with [this image.](https://github.com/endeavouros-arm/images/releases/tag/rpi-4b-image) If so, this should be the default `/boot/config.txt` file > **Click to view** > > ```auto > # For more options and information see > # http://rptl.io/configtxt > # Some settings may impact device functionality. See link above for details > > initramfs initramfs-linux.img followkernel > > # Uncomment some or all of these to enable the optional hardware interfaces > # dtparam=i2c_arm=on > # dtparam=i2s=on > # dtparam=spi=on > > # Enable audio (loads snd_bcm2835) > dtparam=audio=on > > # Additional overlays and parameters are documented > # /boot/firmware/overlays/README > > # Automatically load overlays for detected cameras > camera_auto_detect=0 > > # Automatically load overlays for detected DSI displays > display_auto_detect=1 > > # Enable DRM VC4 V3D driver > dtoverlay=vc4-kms-v3d > max_framebuffers=2 > > # Don't have the firmware create an initial video= setting in cmdline.txt. > # Use the kernel's default instead. > disable_fw_kms_setup=1 > > # Run in 64-bit mode > arm_64bit=1 > > # Disable compensation for displays with overscan > disable_overscan=1 > > # Uncomment if hdmi display is not detected and composite is being output > #hdmi_force_hotplug=1 > > # Uncomment if you want to disable wifi or bluetooth respectively > # dtoverlay=disable-wifi > dtoverlay=disable-bt > > # Uncomment this to enable infrared communication. > # dtoverlay=gpio-ir,gpio_pin=17 > # dtoverlay=gpio-ir-tx,gpio_pin=18 > > # Run as fast as firmware / board allows > arm_boost=1 > > [cm4] > # Enable host mode on the 2711 built-in XHCI USB controller. > # This line should be removed if the legacy DWC2 controller is required > # (e.g. for USB device mode) or if USB support is not required. > otg_mode=1 > > [cm5] > dtoverlay=dwc2,dr_mode=host > > [all] > > ``` Line 35 and 36 does affect the left part of the screen being blank. Be sure this is set to ```auto # Disable compensation for displays with overscan disable_overscan=1 ``` next, check lines 21 & 22 it should be ```auto # Automatically load overlays for detected DSI displays display_auto_detect=1 ``` That is the most common errors made in the `/boot/config.txt` file. If that doesn’t fix it. try temporally hooking your RPi 4b up to a 1920x1080 monitor or TV. EDIT: I just re-read your original post > [@Bosquet](#): > > It’s a SVGA monitor, fed from the Pi via an HDMI/VGA adaptor. I am not sure if this will work or not. Again for trouble shooting purposes, I would recommend hooking up to a 1920x1080 Monitor or TV where you can get a HDMI to HDMI hook up. Pudge ---
**Author:** ![Bosquet](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/e95f7d/32.png) [@Bosquet](https://forum.endeavouros.com/u/Bosquet)\ **Post date:** [July 5, 2026, 10:28am UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/5 "2026-07-05T10:28:14Z")
Thanks for your advice, Pudge. I hooked the Pi up to our tv via a borrowed HDMI cable and completed the installation, but when I tried to use it, all I got was a full-screen console-type window containing only a request to log in to localhost, This didn’t respond either to my username/password or superuser/password, and KDE Plasma, which I chose from the list during the installation process, seems to be nowhere to be seen. Where do I go from here? (I’m not exactly a newbie, but I’m not really a systems person) ---
**Author:** ![Pudge](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pudge/32/17155_2.png) [@Pudge](https://forum.endeavouros.com/u/Pudge)\ **Post date:** [July 5, 2026, 4:20pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/6 "2026-07-05T16:20:00Z")
First off, Thank you for the feedback. > [@Bosquet](#): > > completed the installation, but when I tried to use it, all I got was a full-screen console-type window containing only a request to log in to localhost, Just to clarify, when you "tried to use it’ and “all I got was a full-screen console-type window containing only a request to log in to localhost” was this still on the TV or with the SVGA monitor. If it works with the TV, but not with the SVGA monitor, I am at a loss. I don’t even know where to point you for information on this. Pudge ---
**Author:** ![Bosquet](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/e95f7d/32.png) [@Bosquet](https://forum.endeavouros.com/u/Bosquet)\ **Post date:** [July 5, 2026, 9:37pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/7 "2026-07-05T21:37:42Z")
In answer to your question, the behaviour was identical, both when I expected a normal boot to a Plasma desktop at the conclusion of the installation process using the HDMI/tv option, and when I tried to boot up the Pi using the SVGA monitor. To clarify a point in my last post, the screen didn’t show a console type window, but just appeared to be a teletype screen. The single line at the top of this screen began with something like “localhost login” followed by the following string (possbly missing some initial characters): cmgcnet fd500000.ethernet cnd0: Link is Up - 1Gbps/Full- flow control rx/tx I couldn’t get past this stage (even Ctrl-Alt-Printscreen REISUB didn’t work). Does this info enable you to pinpoint where the boot crashed? ---
**Author:** ![Bosquet](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/e95f7d/32.png) [@Bosquet](https://forum.endeavouros.com/u/Bosquet)\ **Post date:** [July 5, 2026, 9:40pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/8 "2026-07-05T21:40:35Z")
Thanks for the location change! ---
**Author:** ![Bosquet](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/e95f7d/32.png) [@Bosquet](https://forum.endeavouros.com/u/Bosquet)\ **Post date:** [August 7, 2026, 10:17pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/9 "2026-08-07T22:17:57Z")
Long time no see! Domestic life has been over-complicated recently, but I have finally got KDE installed on my Raspberry Pi 4B. BUT the screen size problem is still stopping me using it. The system doesn’t recognize my Acer 1280X720 monitor and the screen edges are way out of sight beyond the edges of the monitor, so once I open a settings window, I can’t see the X symbol at its top right hand corner to close it – which means that I can’t even shut down the Pi properly! At boot time, I can’t see a panel anywhere. There are a few symbols at the top right-hand of the screen, but they don’t seem to be in a panel, because I can’t right-click to edit panel settings., nor discover any way to change the screen resolution. Is there any possibility of editing a configuration file (using the working OS I have at present) on the KDE MicroSD card to get round this problem? Or do you have any other suggestions? I’ve tried using HDMI via the TV set, but it has the same problem. ---
**Author:** ![marteng69](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/m/8edcca/32.png) [@marteng69](https://forum.endeavouros.com/u/marteng69)\ **Post date:** [August 8, 2026, 4:52pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/10 "2026-08-08T16:52:37Z")
> [@Bosquet](#): > > Is there any possibility of editing a configuration file (using the working OS I have at present) on the KDE MicroSD card to get round this problem? Or do you have any other suggestions? I’ve tried using HDMI via the TV set, but it has the same problem. Please look in the following thread: [https://forum.endeavouros.com/t/hdmi-problems-on-initial-boot-with-rpi4b/80044](https://forum.endeavouros.com/t/hdmi-problems-on-initial-boot-with-rpi4b/80044) Your problem seems to be similar to my one in this thread. I was able to create my own edid.dat via the website which is mentioned in the thread. Hope it helps! ---
**Author:** ![Bosquet](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/e95f7d/32.png) [@Bosquet](https://forum.endeavouros.com/u/Bosquet)\ **Post date:** [August 9, 2026, 1:51pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/11 "2026-08-09T13:51:26Z")
Thanks for your prompt reply marteng69. I always concede that I’m not a systems person, so need a little clarification in cases like this. So, first, does the downloaded edid.dat file simply have to be copied as is into the directory /usr/lib/firmware ? Second, where do I find cmdline.txt in fhe filesystem? In either case I have to do these operations with the Endeavouros MicroSD card mounted on a different Linux OS, as the oversized Plasma desktop gives me no access even to a terminal window! I await your reply with interest. ---
**Author:** ![rsher](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/848f3c/32.png) [@rsher](https://forum.endeavouros.com/u/rsher)\ **Post date:** [August 9, 2026, 2:14pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/12 "2026-08-09T14:14:31Z")
> [@Bosquet](#): > > So, first, does the downloaded edid.dat file simply have to be copied as is into the directory /usr/lib/firmware ? Yes > [@Bosquet](#): > > Second, where do I find cmdline.txt in fhe filesystem? /boot/cmdline.txt or if mounted on different OS it will be mounted under the BOOT\_ENOS partition. ---
**Author:** ![marteng69](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/m/8edcca/32.png) [@marteng69](https://forum.endeavouros.com/u/marteng69)\ **Post date:** [August 9, 2026, 5:21pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/13 "2026-08-09T17:21:44Z")
> [@Bosquet](#): > > I always concede that I’m not a systems person, so need a little clarification in cases like this. @rsher already pointed you to the right direction. Steps I would do: 1. Download the `edit.dat` in the mentioned thread. 2. Insert your microSD-card from your Raspi 4B in a card reader connected to your PC or laptop. 3. Open the drive named ROOT\_ENOS and copy the edid.dat to the folder `/usr/lib/firmware`. 4. Open the drive named BOOT\_ENOS open the file cmdline.txt and append ` drm.edid_firmware=HDMI-A-1:edid.dat video=HDMI-A-1:D` at the and of the line. 5. Connect your micro HDMI to the left micro HDMI port of the RPi4B. Unmount your microSD-card and start your RPi4B. I hope this will work for you. ---
**Author:** ![Bosquet](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/e95f7d/32.png) [@Bosquet](https://forum.endeavouros.com/u/Bosquet)\ **Post date:** [August 12, 2026, 2:22pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/14 "2026-08-12T14:22:52Z")
Thanks for your reply. I followed your suggestions to the letter, and on booting from the edited MicroSD card I got a successful boot, but the desktop was still clearly larger than the screen. I can’t send you a screenshot via the forum, but the features of the displayed area were as follows: Screen top left: Large font of time, only showing ‘9 PM’ with date down below, smaller typeface, with the name of the day “offstage” L Screen top right: Row of 7 small icons, Search at left, Power at right 2/3rd down screen at left hand edge: about half of large clickable icon showing; visible text ‘OS Quick…’ Bottom of screen: Tops of 6 clickable icons, the edge-most ones partly off-stage. The arrow keys enabled different ones of all the large clickable icons to be selected, for example I was able to access the ‘System settings’ page. Under ‘Display’ however, it was showing a 1920 × 1080 resolution, and on opening the drop-down there was no item for the 1366x768 resolution of my monitor. The scale was set at 150%. The ‘Apply’ button at the bottom right-hand corner of the screen didn’t seem to be working reliably, but eventually as a fall-back solution I managed to get things set to 1280x720 with scaling as 100%. The window had no top bar, so I had to close it using Alt+F4. When re-booting with these settings, more of the desktop was visible, but it still clearly extended beyond the margins of the screen, and windows still didn’t have the top or bottom bars showing. Nor was there any sign of what I expected to see as a KDE panel. Neither left- nor right-clicking near the top right row of icons gave access to a ‘panel edit’ function, so I presume that bit of the display isn’t a panel. In fact the display, with the large clickable icons, didn’t look at all like what I have experienced for years as a typical KDE Plasma desktop. So, where do I go from here? ---
**Author:** ![rsher](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/848f3c/32.png) [@rsher](https://forum.endeavouros.com/u/rsher)\ **Post date:** [August 12, 2026, 3:58pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/15 "2026-08-12T15:58:56Z")
Some monitors/tv’s let you tweak the screen edges to align with the video resizing in the monitor’s settings. ---
**Author:** ![rsher](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/848f3c/32.png) [@rsher](https://forum.endeavouros.com/u/rsher)\ **Post date:** [August 12, 2026, 4:55pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/16 "2026-08-12T16:55:34Z")
Put edid.bin and put it in your /usr/lib/firmware and specify the name in /boot/cmdline.txt: Try this first: `drm.edid_firmware=HDMI-A-1:edid.bin` Then this second if first causes issues: `drm.edid_firmware=HDMI-A-1:edid.bin video=HDMI-A-1:1366x768@59.78` ---
**Author:** ![Bosquet](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/e95f7d/32.png) [@Bosquet](https://forum.endeavouros.com/u/Bosquet)\ **Post date:** [August 13, 2026, 4:49pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/17 "2026-08-13T16:49:24Z")
Sorry to be a difficult dinosaur, rsher, but as I don’t use a smartphone I can’t access Google Drive using the QR code verification step. (Their help page provides a link to get round that immediate problem, but you can only use the link if you are already logged in to your account, which I can’t because I’m trying to set up the account!) As the edid.bin flle is quite small, could you embed its content in a reply to this post, or is there some other way you could make it accessible? ---
**Author:** ![rsher](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/848f3c/32.png) [@rsher](https://forum.endeavouros.com/u/rsher)\ **Post date:** [August 13, 2026, 5:51pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/18 "2026-08-13T17:51:38Z")
> [@Bosquet](#): > > could you embed its content in a reply Copy the following to a file named edid.hex: edid-decode (hex): 00 ff ff ff ff ff ff 00 04 72 41 01 53 3e 30 03 21 14 01 03 6c 29 17 78 ea 23 05 a2 58 53 9c 26 11 50 54 bf ef 80 71 4f 81 c0 81 00 81 40 81 80 81 8f 01 01 01 01 66 21 56 aa 51 00 1e 30 46 8f 33 00 9a e6 10 00 00 1e 00 00 00 fd 00 38 4b 1f 53 0e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 41 63 65 72 20 50 31 39 35 48 51 4c 0a 00 00 00 ff 00 4c 4c 39 30 57 30 31 31 34 33 32 30 0a 00 fa Then run this command to convert to a binary named edid.bin: ```auto edid-decode edid.hex edid.bin ``` You also need to make sure this is enabled in /boot/config.txt so the firmware does not overwrite your custom `video=` arguments in cmdline.txt: `disable_fw_kms_setup=1` ---
**Author:** ![Bosquet](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/b/e95f7d/32.png) [@Bosquet](https://forum.endeavouros.com/u/Bosquet)\ **Post date:** [August 14, 2026, 10:08pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/19 "2026-08-14T22:08:08Z")
Finally, success! I found the edid.dat file on my Manjaro installation (of blessed memory!) and copied it into /usr/lib/firmware, and then edited /boot/cmdline.txt, changing the reference to edid.dat. I now have endeavouros running with a full-screen display at 1366x768. So the major issue is now solved. Many thanks for pointing me to the appropriate area. However, I would still like advice on how to get a conventional Plasma desktop with an editable panel, instead of the mass of large clickable icons. Any advice welcome! ---
**Author:** ![system](https://forum.endeavouros.com/uploads/default/original/2X/9/9ea52f9fd5ef8e609e593c362d61a36295f48be8.png) [@system](https://forum.endeavouros.com/u/system)\ **Post date:** [August 16, 2026, 10:08pm UTC](https://forum.endeavouros.com/t/screen-resolution-problem-during-installation/80404/20 "2026-08-16T22:08:41Z")
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.