Ubuntu :: Unsupported Console Resolution After Initrd?
Aug 7, 2010
I debootstrapped an install into an existing lvm and booted into it and everything is working great except that after initrd hands off to boot the real root, the text font changes and the resolution is unsupported by my old monitor. The box is up and running because I can ssh in. This is more of an annoyance than anything as I only use the console when something is broken, but it does need to be resolved.
I used dpkg-reconfigure console-setup as described in the debootstrap config guide but I don't see an option for changing the "vga" statement before it regenerates the initrd.
View 2 Replies
ADVERTISEMENT
May 8, 2011
I just installed Opensuse 11.4 (gnome) in a new desktop but the screen resolution is 1360x768 60hz and this is not listed in monitor settings, so the monitor keeps displaying "not optimized mode" message. In order to use the correct resolution, I used these two commands:xrandr --newmode "1360x768_60.00" 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsyncxrandr --addmode VGA1 "1360x768_60.00"it worked, but every time the computer is restarted, I must run this command again. So I think "I just have to create a script in the initialization!". It works, every time the computer is started, there is no need to run the commands again. But when program enters in full screen, the resolution is "lost" and the monitor message is displayed again.
View 7 Replies
View Related
Jul 2, 2010
I use a desktop with an unsupported VIA graphic card which lucid cannot find resolution higher than 800x600so I have to use generic video driver to get resolution higher then 800x600. My question is, which generic driver is better, vesa or fbdev or any other generic driver.
View 1 Replies
View Related
Jul 16, 2009
So, I had fun with this one the past week. I had an FC11 system running just fine. Then one day it would not boot - it was hung somewhere inside the init script of the initrd image. CTRL-ALT-DEL would reboot the system. Using grub editor, I could temporarily delete the initrd line and boot into the system OK. But what was going on?
mkinitrd was of no help to me. I even did a yum update, which got a new kernel, which also generated a new initrd - no joy. I extracted the initrd file system and edited the init script. I eventually hit on this tidbit: If I commented out this line:
daemonize --ignore-missing /bin/plymouthd and rebuild the initrd image - the system would finally at least tell me what the problem was: mount failed for selinuxfs on /selinux. No such file or directory.
So, I examine the root (the real root, not the initrd temporary root) - and sure enough, no /selinux. I make one and reboot. The system goes into a "targeted policy relabel" operation, reboots, and I am back in business - even with my original, unmodified, initrd.
I have no idea what happened to my /selinux directory, but I think the initrd "init" script needs to check for this directory's existance, and make it if necessary. Or at least report that it isn't there. In FC11 right now the system just HANGS without this directory being present, without any clue as to what the problem is!
View 1 Replies
View Related
May 18, 2010
When I compile a custom kernel with this command: make-kpkg --initrd kernel_image kernel_headers and then install the .deb, there's no initrd in /boot and I have to create it manually. I've thought that the --initrd option should take care about this, but somehow it doesn't.
It behaves like this for about two years at least (since I've compiled my first kernel). Of course, it's no big deal to create it manually, I was just wondering whether do I do anything wrong or whether should I fill a bug report..
View 1 Replies
View Related
Jul 4, 2010
I got my hands recently on openSUSE 10.2 (ppc) to put on my b&w powermac g3. i can boot from the cd and it gives me a text prompt and the choices install, rescue, and something to do with the network (which is whatever), and a not-very-helpful help option. so i type install, and my monitor says "input not supported." i figure, "ok, that's cool, i'll just plug in one of my old crt monitors 'cause it must be trying to use a resolution lower than my fancy-schmancy one supports." plug in the old one, restart, type "install," same thing. i'm not new to linux, but i don't really have any options with this prompt that any manner of googling or thread-hunting can uncover which allows me to specify the resolution at which the yast installer starts (or refresh rate, maybe that's it...) or lets me keep it in text mode through the installation. I tried typing "install textmode=1" which seems to do nothing special (same result as just "install") and just "textmode=1" (which is a fundamentally retarded approach, but what else am i supposed to do?). Once the operating system is installed and i can boot into a terminal, i figure can edit the xorg.config to use the resolution i want, but i can't very well install the system without seeing what i'm doing! It's just confusing 'cause it doesn't seem to like any display i give it.
View 3 Replies
View Related
Jul 20, 2010
I have been running Ubuntu 10.04 on my laptop just about since it came out.Prior to that I was running 9.10 on the same laptop. I was so happy with 9.10 I thought I could only be happier with 10.04.I was wrong.There are some things about 9.10 that I have *lost* in the transition to 10.04.These bother me quite a bit so much so that I have repeatedly considered going back to 9.10.Please keep in mind this all worked fine under 9.10 on exactly the same hardware.
1) When I connect the external VGA port on my laptop to my 32 Samsung TV it comes up as a 40 Samsung TV and it is impossible to set the correct resolution.This makes watching TV over the Internet via my notebook impossible (I used to use URL... and others).
2) I cannot change the resolution on the console (the TTY's 1 to 6). It used to come up as standard old fashioned VGA (80 columns by 25 rows of text) but now it is much smaller font and much larger console.The VGA= in GRUB does nothing. And this is the only suggestion I seem to be able to find. From my reading most people seem to like the large console w/ small font.I dislike it for the reason I will get into next
3) DOSEMU locks up my computer with a blank screen when running in super mode on the console.Pressing Ctrl+Alt+F# accomplishes nothing and either does Ctrl+Alt+Del.I have to press and hold the power button forcing a hard shutdown (at least this is the only solution I have found).
View 3 Replies
View Related
Mar 4, 2010
Let's start with some context: About a week ago, I saw in the university computer that the text mode consoles(ctrl+alt+f[n]) worked with a great resolution on a 19" wide screen (I think it is 1440x900) running fedora 11. So I wondered if I could make the text consoles at home to work with a good resolution also.So I started to search for that and found the kernel parameter vga= . The problem: it doesn't support 1440x900 or any other 16:10 resolution for my graphic card. Then I thought that maybe fedora uses some module that allows that, because the livecd allows a good resolution (by default) on my desktop computer.
What I thought so far is that fedora is not using vesa for the virtual console (which i think is the driver that ubuntu uses) and I want to know what driver it is and how to use it in ubuntu (either compiling the kernel or simply installing something).I don't even know if my guesses are right or not. But I've gathered some info so far:From /var/log/messages (fedora 12 livecd) I got this part, which I think is the really interesting one.Quote:
Mar 2 22:37:18 localhost kernel: [drm] Initialized drm 1.1.0 20060810
Mar 2 22:37:18 localhost kernel: [drm] radeon defaulting to kernel modesetting.
Mar 2 22:37:18 localhost kernel: [drm] radeon kernel modesetting enabled.
[code]...
View 2 Replies
View Related
Jan 21, 2010
I'm trying to track down a screen resolution issue (Karmic on an Acer SK20 [Intel 945 graphics] with Acer AL1511 flat panel via VGA) and mechanism for setting the framebuffer screen resolution after GRUB2 has loaded the kernel but before X starts.
Before I forced it to behave itself by adding an xorg.conf with a lone "Modes" entry for 1024x768, X was setting the panel to 640x350 by default. It appears from looking at get-edid | parse-edid that this is because 640x350 is the only resolution this idiot panel's EDID says it knows about, even though its native resolution is in fact 1024x768.
So the GUI works fine now, but all the text consoles (Ctrl-Alt-F1 through F6) are still operating at 640x350 and look terrible; also, because usplash doesn't know what to do with 640x350, I don't get my nice white Ubuntu logo before GDM starts.
In previous releases, I would have dealt with something like this by adding vga=791 to the kernel boot options. That doesn't work for the Karmic kernel, and GRUB2 whines about it being deprecated and tells me to use "set gfxpayload=1024x768x16,1024x768" on a line before the "linux" command instead.
Things I have already tried, with no success:
1. Adding "set gfxpayload=1024x768x16,1024x768" into the boot sequence, right before the "linux" line, by using GRUB2's inbuilt boot sequence editor (Ctrl-E): no change.
2. Changing the GRUB_GFXMODE= line in /etc/default/grub and running update-grub: changes the resolution used for GRUB's own menu, but as soon as the kernel boots it's back to 640x350 on text consoles.
3. Same as (2) but also adding a "set gfxpayload=keep" line in /etc/grub.d/00_header, right after the "set gfxmode=${GRUB_GFXMODE}" line: same effect as (2).
4. Removing the "splash" option from the "linux" line. No change (I guess this is because usplash didn't work anyway at 640x350). By the way, usplash.conf is set up for 1024x768 and yes, I did remember to dpkg-reconfigure -phigh usplash to rebuild the initramfs after checking this.
where exactly does Karmic set the screen resolution for its text consoles, and how can I force it to ignore this LCD panel's bogus EDID?
View 3 Replies
View Related
Feb 1, 2011
I am using Ubuntu 10.10 on a Dell Optiplex GX270, with the Intel video chip. I have a problem with my virtual consoles/terminals (<ctrl-alt>F1-F6). The default screen resolution was set to 1600x1200 at installation, which results in a nearly microscopic, unreadable font. I posted the problem on this thread on ubuntuforums.org, where they suggested adding GRUB_GFXMODE=640x480 and GRUB_GFXPAYLOAD_LINUX=640x480 to /etc/default/grub and /etc/grub.d/00_header. Still no joy--the console screen resolution still was 1600x1200.
I have noticed that the screen resolution changes three times during boot; it starts at standard VGA, 640x480, then switches to 1600x1200, then finally to 1024x768, which is my preferred resolution in X. But, if I switch to a virtual console, the resolution shoots up to 1600x1200 again. There are times when I like to use virtual terminals, and I would like to avoid eyestrain.
View 10 Replies
View Related
Jun 10, 2015
In vm workstation console resolution default is 640x480 ,and i want to change it to 1024x768.
In Debian7 , it can changed use vga=792 in /boot/grub/grub.cfg.
But in Debian8 use changed use vga=792 in /boot/grub/grub.cfg , screen will all black.
Although screen can't see anything , but it can connect through ssh normal.
I also tried GRUB_GFXMODE=1024x768,GRUBGFXPAYLOAD_LINUX=1024x768 in /etc/default/grub , it get same Result.
I don't know the problem is at VM workstation or Debian 8.
View 3 Replies
View Related
Jun 16, 2010
playing with debian I find that I have no answer when I try to resize my console if I wish to use it without a GUI. Are there something that could resize the screen ? In this moment it seems to be 640x480 and it could be better if the resolution could be 800x600. I have tryed to modified /etc/grub/00_header
if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=800x600 ; fi
View 7 Replies
View Related
Jan 3, 2010
I am have upgraded from 9.04 to 9.10 in my laptop. After performing the reboot, the shell/console resolution went very high and the font size went too small. How to regain the old console shell resolution as in 9.04. I require this urgently as my laptop suffers the white screen problem. Switching between Ctrl+Alt+F6 and Ctrl+Alt+F7 I could get back the screen as the change in the resolution switches off and on the screen, so that I can negotiate with the white screen problem.
View 10 Replies
View Related
Sep 16, 2010
I am running Lenny of a Dell Mini 10, using only the console. I want to get the resolution smaller that 80 on the horizontal axis, but I can't find the right setting for vga in /boot/grub/menu.lst.
Inserting various values makes the dell give me list of possible video modes at boot, but none of these are higher than 80xSomething. It offers VESA modes that are choosing these results in unreadably tiny text, and anyway I wouldn't know how to edit in order to make these mode take effect automatically.
Can anyone tell give me a value that works for vga on Dell Mini 10 that produces a smaller resolution that 80xSomething? If not, can someone suggests a different way to obtain the same result?
View 9 Replies
View Related
May 6, 2011
The resolution is OK in grub menu but after something is setting to higher value. How can i set it back to 640x480?
View 1 Replies
View Related
Aug 8, 2010
I have install Fedora 13 on my machine (Intel 815 Chipset with graphic card of nVidia GeForce 256), but the default resolution of text console wound have be about 1024x768. I intend this machine as a simple samba server (without X Window), so just a low-resolution monitor will work with it. However, this monitor can't work with the resolution higher than 800x600, I have to change the resolution lower. I have searched the solutions for this problem on Google. Most of them thought I should fix /boot/grub/grub.conf, append "vga=769", "vga=771" or even "vga=ask" to the end of the line start with the word "kernel". I have tried but all of them doesn't work. Just like Fedora 13 use the value from the other configure file overwrite the one list in grub.conf. As everyone knows, if I installed and launched X Window on my machine, I could query and change the resolution with command "xrandr". Are there some similar ones that can work on text console?
View 3 Replies
View Related
Nov 2, 2010
I've been scouring the internet for an answer to this problem. I am using Squeeze and have properly configured Grub2 to set my console screen resolution to 1024x768x32 (as per updating /etc/default/grub to contain 'GRUB_GFXMODE=1024x768x32' and updating /etc/grub.d/00_header to contain 'set gfxpayload=keep') and everything works wonderfully. My resolution is set as it should be. However upon installing Xorg (aptitude install xorg ratpoison), my console resolution gets changed to what appears to be 1280x1024.
I thought that this was due to xrandr, however when I issue:
# xrandr -s 1024x768
only the X resolution is changed. When I then CTRL-ALT-F1 back to the console, the resolution is still at 1280x1024 (I am aware that xrandr only affects X, but I assumed that because my console resolution was correct before installing X there might have been some correlation).
I would like for my console resolution to stay at 1024x768 as per Grub2's configuration and for X's resolution to be at 1280x1024.
PS I also noticed that prior to installing Xorg, my CPU boots up without any screen blanking (only for a second or so). However, after installing Xorg, during the boot process the screen does blank briefly. It is at that time that the resolution gets changed to the 1280x1024 setting.
View 5 Replies
View Related
Mar 25, 2009
I'm using Fedora 10 x86_64 with an ATI Radeon Mobility x1400 video card. Before installing fglrx & compiz, the text console (while booting up) was shown at 1280x800 resolution (laptop widescreen). After installing fglrx & compiz the console would only show up as 640x480 resolution. My resolution in X starts as 1280x800 without any problem. I realize that you can use vga=xxx as a kernel argument but this only works with NON-widescreen resolutions. I require that it be set to a widescreen resolution like it was before the fglrx & compiz installation.
View 9 Replies
View Related
Dec 20, 2009
virtual console (run level 3,5) screen resolution. After installing fed12 the resolution is higher(which is good) then in previous versions. After upgrading from 11 -> 12 the resolution of the virtual consoles stays the same, to large. I already compared grub.conf,i18n which are the same. Where is the resolution configuration for fed 11,12?
View 2 Replies
View Related
Jul 29, 2010
After install of FC13, my command prompt console and tty virtual consoles are a small box in the upper left corner of the screen. It contains tiny 80 characters by 25 rows. I want to fill the screen the old way. I assume the problem is high value screen resolution set automatically to match my display; with fonts based on the smaller pixels. This is NOT X-Windows. I can set that resolution but it has no effect on tty consoles.
It is NOT grub, which I can set with kernel parameter vga=0 to do exactly what I want. Messages from grub are big letters but change to tiny ones at init ("press 'I' for interactive startup" and the beginning of the boot log). This is not an issue with the same display using FC10 and no vga= parameter. Is there a reason that the kernel parameter failed after grub? Can I specify console resolution?
View 5 Replies
View Related
Dec 17, 2010
I have using fedora 14, when i want boot into system the console resolution goes to 1600x1200. i want change the resolution to 1024x768-85.
View 1 Replies
View Related
Mar 8, 2010
I have tried this with many different configurations, however, I believe that the scroll bar that shows the progress of the boot is preventing it from changing successfully. I don't know how to switch it off. X is not installed. No gui, only tui.
View 5 Replies
View Related
Mar 3, 2010
I use CentOS and i need to set resolution or font size so that i can see more lines of logs at a time on the main console of my CentOS box.
View 3 Replies
View Related
May 6, 2010
I have a Asus EEE PC 1005P which I installed a Command-line system on using the Alternate Installer CD of Ubuntu Lucid Lynx. I do not have (or want) the X Window System installed.
I want to change my console screen resolution (not inside X) to 1024x600. But it isn't reported when I use vbeinfo inside grub2:
Code:
grub> vbeinfo
VBE info: version: 3.0 OEM software rev: 1.0
total memory: 8128 KiB
List of compatible video modes:
[code]....
View 5 Replies
View Related
May 6, 2010
I have a Asus EEE PC 1005P which I installed a Command-line system on using the Alternate Installer CD of Ubuntu Lucid Lynx. Altough I think this is a general linux and grub2 question. I do not have (or want) the X Window System installed. I want to change my console screen resolution (not inside X) to 1024x600. But it isn't reported when I use vbeinfo inside grub:
grub> vbeinfo
VBE info: version: 3.0 OEM software rev: 1.0
total memory: 8128 KiB
List of compatible video modes:
Legend: P=Packed pixel, D=Direct color, mask/pos=R/G/B/reserved
0x112: 640 x 480 x 32 Direct, mask: 8/8/8/8 pos: 16/8/0/24
[Code]...
Does it mean I have the driver? how to set it to 1024 x 600 in grub2?
View 1 Replies
View Related
Feb 21, 2010
Basically, About 50% of the time, the system boots and sets the console resolution to something strange, and the console renders in a small box in the top-left hand corner of my screen. This causes problems not only with the display of the console, but with the display of X as well.
I have an Intel GL40 chipset on this laptop, with an integrated GMA4500 GPU. I am using the latest stable Intel video drivers (2.10.0-1), and have tried using the git drivers. In addition, the problem has been occuring since December, when I install Arch linux on this machine, I have just now had the time to address it. So basically, the issue has persisted with all driver versions since mid-December to the latest releases.
In addition, I have tried using several kernels, including:
But the problem persists with each.
I wish I could give you relevant diagnostic information for this issue, but if I had any idea where to start...
I will gladly post any information necessary. I was going to post a copy of everything.log for a successful and unsuccesful boot, but unfortunately they put me over the posing limit by about 100,000 characters each.
I guess, on second thought, that my Intel video driver really wouldn't have anything to do with my console, now would they?
View 9 Replies
View Related
Sep 8, 2010
How can I start a program from tty1 console text mode to be executed in tty2 console text mode? Actualy I would like to start a program (chat client cli program) in tty8 automaticaly when linux PC boots.
View 6 Replies
View Related
Oct 21, 2010
I recently received an automatic update to my 10.04 system which included some kernel stuff. I am using vanilla repositories, I haven't added, removed, or altered any of the default repositories. I downloaded and installed the updates using the graphical Update Manager found in System->Administration
I'm running Ubuntu 10.04, and my kernel is listed as 2.6.32-25-generic. I haven't installed any new hardware whatsoever; my hard disk drive is the same as it has always been. When I go through System->Administration->Disk Utility, then view my hard drive, the line: SMART Status: reads with a grey circle and then "Not Supported" I am able to run the Benchmark application from Disk Utility and it completes without problem. This happened to me where I was unable to view SMART data after automatic updates involving the kernel when I was using Ubuntu 9.10.
View 1 Replies
View Related
Dec 26, 2010
I have installed Ubuntu 10.10 in my desktop, and network doesn't work, are nForce 7 network cards unsupported in Ubuntu?
View 1 Replies
View Related
Jun 14, 2010
I'm helping a friend set up his new pc and we're having a lot of trouble getting his second monitor to work.He has a GeForce GTS250 video card which has a HDMI output port as well as VGA. His main monitor is connected via the VGA and works fine. The second monitor is a Soniq QV320H TV which he wants to connect via HDMI. The nvidia settings configuration shows both monitors (set up as separate x-screens) but the only output on the Soniq is a black screen which flashes "unsupported" about every 2 seconds. Currently the resolution is set to auto (1280x1024) but we've also tried lower resolutions (down to 800x600) with no success.
View 3 Replies
View Related
