[Solved...sort of]Changing grub and console resolution during boot

I recently purchased a new monitor that runs at 1920x1080, my older monitor was at 1920x1200, and when I boot now I end up with a boxed output, black borders on each side. This influences how my grub looks and how my terminal looks at startup. I've changed the settings so my WM looks and works properly, but I am not sure how to change, or update, the resolution for my boot-up process. I could use some assistance. Thanks!
EDIT:
Well I found out that I can only change my resolution in grub based on what is shown in vbeinfo when booting with grub. The strange thing is that the resolution being used is 1920x1080x32, which is the recommendedd, and max resolution of my monitor. I also noticed my BIOS splash screen is also being shown with black borders on all sides.
EDIT:
Well it looks like this is problem with OCD on my monitor, and my NVIDIA card. Looks like it's pretty wide spread without any real solution. I'll mark this as solved since this has nothing to do with grub or linux settings.
Last edited by barefly (2015-05-10 02:50:01)

jasonwryan wrote:Did you regenerate your grub config?
I just tried this by running grub-mkconfig without changing any settings in /etc/default/grub, and it didn't work. So I went ahead and modified /etc/default/grub on my next boot to another valid resolution and restarted. That had no effect either. The last thing I tried was manually adding the preferred resolution instead of leaving it at auto. None of the changes made any difference. It only changed the way my text was outputted, making it more or less scrunched really. I think the issue could be stemming from the monitor and bios are interacting, since my bios splash screen starts with the black border, and then grub inherits the screen properties, and then in turn linux inherits these settings before my video card finally kicks in after tty and x starts.
Last edited by barefly (2015-05-10 02:46:25)

Similar Messages

I am getting frequent lock-ups and blue screens during boot up. The lock ups occur during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button. Ideas?

I am getting frequent lock-ups and blue screens during boot up on my Mac Pro. The lock- ups occur sometimes during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button.
I had the Mac Defender malware and I have used apple jack but still having issues.

I am getting frequent lock-ups and blue screens during boot up on my Mac Pro. The lock- ups occur sometimes during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button.
I had the Mac Defender malware and I have used apple jack but still having issues.

[SOLVED]Unable to install grub "couldn't find /mnt/boot/grub/menu.lst"

Ok so I was trying to install windows after I had arch installed, used an ubuntu cd to use gparted to create a partition, tried to go to the windows installation but it would endlessly send me back to restart the installation even after succesfully writting all files...
So now I decided to not install it, went back into ubuntu/gparted, deleted the partition and rejoined the space with my main arch partition and then selected the "boot" flag to boot...
Cannot boot, grub its still on /boot/ but the MBR its obviously tempered with by windows ( which coincidentally couldn't even find itself after writing mbr to its liking....*sigh* ).
So I try to use my arch install cd to reinstall grub but i get this:
"couldn't find /mnt/boot/grub/menu.lst is grub installed?"
I tried to use the select packages thing to make sure the cd is mounted and mounts fine but it keeps getting me that error message. I managed to boot to my system just fine with arch root=/dev/sda1 but obviosly the kernell does not has my nvidia module which means I can't get into x which means i am using links and since my grub is not loaded i can't even get framebuffer so this is rather inconvenient.
Im sure im missing a very simple and stupid thing but im so annoyed my brain must be saying "ok im done somebody else figure it out". I still have a backup copy of my grub menu.lst I made before. Do I just delete /bood/grub/ and try again? Am I missing something on the install procedure to be able to rewrite grub? Can I just do it from the command line or with pacman? Any help appreciate it thanks.
Last edited by Misanthrope (2008-06-01 17:22:32)

If you can get into your arch and cli then you should just be able to reinstall grub with
install-grub /dev/sda
or reinstall grub with
pacman -S grub
if the package is messed up or missing.

Change Seconds Waiting for Device during boot

During boot at the section: "Waiting 10 Seconds for Device", I am often dropped to a shell. I think it may be because I need to increase the wait time. How can I do this? I've looked in several places but I'm not sure what to look for.

I've ran into exactly same problem lately, but finally solved it.
Setup: Intel Fake RAID, mirror, partitioned as:
/dev/mapper/isw_dfjeffgfaj_rootvol1 /boot
/dev/mapper/isw_dfjeffgfaj_rootvol2 /
/dev/mapper/isw_dfjeffgfaj_rootvol3 /home (dm-crypted)
In /etc/fstab i had following mountpoints:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
/dev/mapper/isw_dfjeffgfaj_rootvolp1 /boot ext4 rw,relatime,data=ordered 0 2
and boot hung on waiting for /dev/mapper/isw_dfjeffgfaj_rootvolp1. Solution involves changing dev path to UUID:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
UUID=44809529-11d9-4f53-9652-7b97ed077225 /boot ext4 rw,relatime,data=ordered 0 2
For some reason symlinks /dev/mapper/isw* are not present during systemd mount.

[SOLVED] How to get NetworkManager start on background during boot?

NetworkManager has always taken relatively long time to start during boot, presumably waiting for wlan to connect.
$ systemd-analyze blame
7.682s NetworkManager.service
Previously I was able to get it to start on background by removing /etc/systemd/system/multi-user.target.wants/NetworkManager.service
This prevented multi-user.target from waiting for NM to start and it would continue to connect on background while my boot finishes.
However, after upgrade to networkmanager-0.9.10.0-2 that doesn't seem work any more.
If I remove the .service file from multi-user.target.wants/, NetworkManager doesn't start during boot at all.
enabling NetworkManager.service creates these symlinks:
# systemctl enable NetworkManager
Created symlink from /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service to /usr/lib/systemd/system/NetworkManager.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/NetworkManager.service to /usr/lib/systemd/system/NetworkManager.service.
Created symlink from /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service to /usr/lib/systemd/system/NetworkManager-dispatcher.service.
looks like enabling any other basic systemd unit links the .service file to multi-user.target.wants/ as well..
How can I enable NetworkManager.service during boot without multi-user.target.wants/, and get it to start on background again?
any ideas appreciated :)
Last edited by ooo (2014-08-03 12:13:28)

Okay, looks like this can be resolved by simply changing the NetworkManager.service type from dbus to forking.
$ systemd-analyze blame
173ms NetworkManager.service
Here's the modified service file if anyone's interested:
place it in /etc/systemd/system/NetworkManager.service
[Unit]
Description=Network Manager
Wants=network.target
Before=network.target
[Service]
Type=forking
PIDFile=/var/run/NetworkManager.pid
BusName=org.freedesktop.NetworkManager
ExecStart=/usr/bin/NetworkManager --pid-file=/var/run/NetworkManager.pid
# NM doesn't want systemd to kill its children for it
KillMode=process
[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.NetworkManager.service
Also=NetworkManager-dispatcher.service
You need to disable NetworkManager.service before creating the file and enable it after so that systemd links the file from /etc/systemd instead of /usr/lib/systemd,
there may be simpler way but I can't be bothered to go through systemd manuals any more.
Note that this will probably break any systemd .service that actually requires network, although that was the case with my previous workaround as well.
I won't guarantee this will work for you and won't set your machine on fire. If you have issues, simply remove the file and re-enable to go back to default

How can I get the arch logo in console/terminal during boot?

Hello
I just installed arch as my first linux, and I would like to get the arch logo in the top left corner during boot, like on the following screenshot:
http://i4.photobucket.com/albums/y132/s … h_boot.png
uname -a:
Linux 3.6.6.1-ARCH #1
syslinux bootloader
How can I do that?
Thanks a lot and greetings

I'm not sure what's the situation now, but you may not get the logo - neither the penguin nor Arch logo:
* https://bbs.archlinux.org/viewtopic.php?id=120516
* https://bbs.archlinux.org/viewtopic.php?id=122778
* https://bbs.archlinux.org/viewtopic.php?id=124730

[SOLVED]Xorg: cannot change keymap and add multiple langs

~/.xinitrc
setxkbmap -layout gb,dk,lt -option grp:alt_shift_toggle
I've followed wiki and this didn't change anything. My keymap is currently us and alt+shift change doesn't react.
Last edited by decas (2014-02-23 18:54:02)

slithery wrote:Everything following the exec line in a .xinitrc is ignored. Move the exec line to the bottom of the file.
This.
decas, read the note https://wiki.archlinux.org/index.php/Xinitrc

TA43884 My imac beeps between 7 and 9 times during boot up.

When I power up my imac it beeps berween 7 and 9 times and will not boot up.

Intel-based Mac Power On Self Test RAM error beeps
Power On Self-Test Beep Definition - Part 2

[Solved] The framebuffer, Grub, and graphics card driver

I'm running Arch on a 15.1" laptop, and the natural resolution for my LCD is 1366x768.
X has no problem of adjusting itself to the right resolution. The console can do this too, but only when I have the open-source graphics card driver (xf86-video-ati). If I try catalyst in the AUR, the console falls back to 800x600, characters being wide and blur. Grub seems to suffer from a similar problem. It always present me with a 800x600 menu, and the early userspace booting is in this resolution too.
I followed the instructions in https://wiki.archlinux.org/index.php/Gr … resolution and the following is what I found out.
I couldn't find the package lrmi in the repo. (I doubt the wiki page is outdated.) I did find vbetool, but it doesn't provide vbetest. Taking the next approach, running sudo hwinfo --framebuffer gives:
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.459]
Unique ID: rdCR.A3Y7SCr7Y49
Hardware Class: framebuffer
Model: "(C) 1988-2005, ATI M92"
Vendor: "(C) 1988-2005, ATI Technologies Inc."
Device: "M92"
SubVendor: "ATI ATOMBIOS"
SubDevice:
Revision: "01.00"
Memory Size: 16 MB
Memory Range: 0xd0000000-0xd0ffffff (rw)
Mode 0x0300: 640x400 (+640), 8 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+832), 8 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0310: 640x480 (+1280), 15 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x0313: 800x600 (+1600), 15 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0316: 1024x768 (+2048), 15 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x030d: 320x200 (+640), 15 bits
Mode 0x030e: 320x200 (+640), 16 bits
Mode 0x0320: 320x200 (+1280), 24 bits
Mode 0x0393: 320x240 (+320), 8 bits
Mode 0x0395: 320x240 (+640), 16 bits
Mode 0x0396: 320x240 (+1280), 24 bits
Mode 0x03b3: 512x384 (+512), 8 bits
Mode 0x03b5: 512x384 (+1024), 16 bits
Mode 0x03b6: 512x384 (+2048), 24 bits
Mode 0x03c3: 640x350 (+640), 8 bits
Mode 0x03c5: 640x350 (+1280), 16 bits
Mode 0x03c6: 640x350 (+2560), 24 bits
Mode 0x0333: 720x400 (+768), 8 bits
Mode 0x0335: 720x400 (+1472), 16 bits
Mode 0x0336: 720x400 (+2944), 24 bits
Mode 0x0360: 848x480 (+896), 8 bits
Mode 0x0361: 848x480 (+1728), 16 bits
Mode 0x0362: 848x480 (+3456), 24 bits
Mode 0x0321: 640x480 (+2560), 24 bits
Mode 0x0322: 800x600 (+3200), 24 bits
Mode 0x0323: 1024x768 (+4096), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown
No 1366x768. Taking the last approach, I added "vga=ask" to the Grub entry. Again no 1366x768. How can I get the resolution set to 1366x768 during Grub and/or early userspace booting? Or is it simply impossible?
Last edited by xiaq (2011-03-07 09:23:10)

Mr.Elendig wrote:The only way to really do it is to use kms and the free driver for X.
So... I should follow https://wiki.archlinux.org/index.php/AT … _KMS_start, since I have an ATI card and I've decided to stick with the free driver(at least for now).
Still one question: to use KMS early(this is what I want), I need to regenerate the initial image(mkinitcpio). What's the worst result if it fails? Will mkinitcpio make no complaints but give me an unusable image? I'm asking the questions both in general and in my specific case(trying to enable KMS during early start).

S10 on SF v20z - video out and console redirection

Hi,
Is there a way to have both video out redirection and be able to do 'platform console' command in ALOM at the same time?
by default, settings in eeprom are:
output-device=screen
input-device=keyboard
obviously, console redirection doesn't work. (Well, actually it works fine while it boots, bios output gets sent on both places, the video out and console, until solaris boots ...)
if I set
output-device=ttya
input-device=ttya
I lose the video/keyboard switch functionality, but alom console redirection works fine.
What am I missing? Is it possible to have both inputs and outputs active at the same time?
Thanks for your time,
Honza

After installing, I needed to get into single user mode then run the Xfree86 configuration utility to properly detect and use the video card. I can't remember the exact command line, but it's something like /usr/X11/bin/xfconfig or something similar. After that, the video worked fine.

[SOLVED] Forced reboot, now GRUB reset and cannot find Arch

2 nights ago, my area had a fairly large storm. When I woke up, my Arch box had rebooted itself, and was stuck on a GRUB error screen. I had not updated, nor had I recently touched anything in /boot.
The major complaints from GRUB were "file not found" when trying to load the kernel, and complaints about invalid UUIDs when trying to mount the root filesystem. It's also worth noting that GRUB's menu resolution had changed back to the default lowest setting, and was colorless. This, I think, indicates a problem with the configuration. I could still see all my files and systems through grub's prompt. Everything was still there and the HDD seemed fine.
Yesterday, I was able to boot into Arch successfully by simply doing:
grub> set root=(hd0,msdos1)
grub> linux /boot/vmlinuz-linux
grub> initrd /boot/initramfs-linux.img
grub> boot
Once I got in I updated the system, ran pacdiffviewer, ran grub-mkconfig as per the wiki (to hopefully fix the config issue), and rebooted. Now I cannot get into Arch at all. Using the Arch GRUB menu item, I just get "file not found" and booted back to the menu. Using the above commands gets me the following errors, and a recovery shell:
ERROR: device '' not found. Skipping fsck.
ERROR: Unable to find root device ''.
One last thing: I have an old Ubuntu 10.10 partition on the same drive. I can get to that partition through GRUB's menu just fine. This is strictly an issue with Arch. Perhaps the hard reboot caused something to change related to UUIDs? What should I do?
Last edited by MeisBarry (2013-08-13 22:16:51)

Well this is embarrassing.
While getting grub.cfg, I noticed that when I had done grub-mkconfig, ...I saved it as grub.conf by accident. I fixed it and my system works again!
So I'll mark it Solved. Any idea why a reboot would corrupt grub's configuration?

Console resolution and X on dual screen

I'm using a laptop with an external display.
The laptop max resolution is 1024x600 and the external's is 1680x1050.
I've got xorg running this script on login:
# If an external monitor is connected, place it with xrandr
# External output may be "VGA" or "VGA-0" or "DVI-0" or "TMDS-1"
EXTERNAL_OUTPUT="VGA"
INTERNAL_OUTPUT="LVDS"
xrandr |grep $EXTERNAL_OUTPUT | grep " connected "
if [ $? -eq 0 ]; then
xrandr --output $INTERNAL_OUTPUT --off --output $EXTERNAL_OUTPUT --auto
else
xrandr --output $INTERNAL_OUTPUT --auto --output $EXTERNAL_OUTPUT --off
fi
Then when I close my window manager, this script runs:
#/bin/sh
xrandr --output VGA --off --output LVDS --auto
fluxbox-remote "Exit"
The only time the console resolution is correct is after i've closed my window manager and this script has run.
I'm using hal and don't have an xorg.conf. Is this the issue? I also have VGA=790 in my grub config. I guess my question is, what am I missing, and would there be a better way to do this?
Edit: if it helps, im using an intel gma945 in an msi wind
Last edited by keegan (2009-05-22 00:43:39)

Okay, I got the console to work from bootup using vga=normal. Now the only time my console is unusable is after leaving xorg when I had been using the external screen and didn't run my script at logout. So when i reboot/shutdown, kill x, crash x or switch to a vt (ctrl-alt-Fx) the screen is jacked up. If I never startx, or make sure to use my script to close x, everything is okay.

I changed everything and i signed out then i sign in again but still my. apple id is disabled plz solve this problem!!!!!????

I changed everything and i signed out then i sign in again but
still my. apple id is disabled plz solve this problem!!!!!????

Hello jek28,
Thanks for using Apple Support Communities.
If you're getting the message that your Apple ID has been disabled for security reasons, then please follow the directions in the article below to resolve the issue.
If your Apple ID has been locked - Apple Support
Have a good one,
Alex H.

Change fps and resolution in a Thorlabs DCC1645C camera

Hello,
Im working with a DCC1645C camera with Labview. I need to programatically change the fps and the resolution, but if I try to do that with a property node: FrameRate, Width and heigh are only Readable attributes. Also, the video modes of the camera that are displayed in MAX are only a few modes and all of them has 1280x1024 and 10 fps.
When using the manufacturer software of the camera I am able to change both, resolution and fps. Also, Thorlabs gives some VIs to work with the camera, where the fps can be set, but I dont know how to use this VI in my program, where Im using IMAQdx to acquire the images.
Thank you.

Hello,
There is a function called IMAQ Resample where you can set the resolution of your image, there is no function to change the FPS settings, but you can set both attributes (FPS and resolution) using the property nodes that you found, they are read attributes but you can change them to write, just right click the property node and click on the "change to write" option on the drop down menu.
Hope to help you.
Thiago Matos
Engenharia de Aplicações
National Instruments Brasil

Programmatically change screen orientation and/or resolution?

We don't have VB.NET available and I was wondering if it is possible to create VBA code that would change:
1) screen orientation (and maybe resolution)
2) on a specific monitor (in a multiple monitor setup; we have two)
The idea would be to put it into an Excel workbook and have the macro autorun then exit.
I see examples for C#.Net but can't find any for VBA. Maybe it's not possible. Your comments are appreciated. Thanks.
Edit: ANY MS Office application can be used as long as it can be used via a shortcut on the desktop and run automatically. "One click and done" is the idea.

Hello Doug,
I believe you can use Windows API functions to get the job done.
Anyway, the current forum is for Office Apps. I'd recommend asking VBA questions on the
General Office Development forum instead.

[Solved...sort of]Changing grub and console resolution during boot

Similar Messages

Maybe you are looking for