Kernel boot video mode

Just did pacman -Syu for the first time in a long time.
Using lilo.
Lilo boots fine and starts unpacking the kernel in the "normal" video mode.
However, as soon as the kernel takes over, the video mode switches to a large mode (don't know which one) where most of the text is actually off the bottom of the screen. Almost like the kernel thinks it's in the "normal" mode, but the video card jumped into a different mode. I'm not sure about that theory, though.
I'm still able to login and startx. But the console mode is nearly useless.
I tried adding vga=ask to my lilo.conf
It asks and I reply but the kernel (or hardware) still jumps into a useless mode.
I tried typing vga=normal at the lilo command line... same deal.
Any thoughts? theories?
Just for reference is there a way to revert back to my old kernel or did pacman -Syu change too much to bother with that?
thanks for helping an old newbie
TheGipp

ack! another clue
/sbin/lilo reports this:
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
I hadn't noticed that before.
That's probably another problem that I need to work.
any help?

Similar Messages

Video Mode on Boot - Oracle Linux Server r6u2

Having an issue. See posts on forums but they are very old and with no clues. When our servers boot up, our rack monitor says the video mode is not supported. We do not see anything past POST - no red line across the bottom. Nothing except for the message from our monitor saying the video mode is not supported. We connect another monitor and it also says the same. We boot with that monitor and it comes up OK. We reconnect our rack monitor and we see Linux. Any idea on how to configure the video mode on start up? Or any other suggestions other than replacing my rack monitor?

You can try to change the screen resolution using specific kernel boot parameters
Check the following if it helps:
linux installation
I recommend to check all the vga cables to make sure there aren't any bend pins, even the ones that are connected to other machines can cause trouble.

PXE boot and video mode

Hello all,
I posted about this problem a while ago but now I have more information.
6.5 SP2 IR1.
The problem: Booting from CD results in a video mode with far more lines and
column than booting PXE. PXE is always 80x25, on many different hardware
types. I want it to be like the CD.
Theoretically, the video mode is controlled by the vga= parameter on the
kernel's command line. For PXE, the kernel command line comes from <imaging
server>\sys\tftp\cmds, various files therein. Here are the contents of a
typical file:
KERNEL boot/linux
APPEND initrd=boot/initrd vga=0x314 install=tftp://$TFTPIP/boot
rootimage=/root PROXYADDR=$PROXYADDR TFTPIP=$TFTPIP splash=silent
PXEBOOT=YES mode=5
Notice the vga= parameter.
I can modify this vga parameter any way I like, without effect. I have
tried:
- removing the parameter entirely
- setting it to ask
- setting it to vga_ask
- setting it to single-digit numbers e.g. 1, 2
- setting it to other 0x3nnn options
- setting it to extended
It should be possible for anybody to replicate this simply by changing the
vga parameter in one of your CMD files and booting that particular PXE
option. I suggest using "ask" as it is the one that would give the most
visibly obvious evidence of working or not working.
The boot loader for PXE appears to be linld.com. So, I took my PXE
materials and Novell's linld (to ensure same version) and ran them from DOS.
When I run them from DOS, the vga= parameter DOES have an effect; it behaves
exactly as it should.
So, the situation appears to be that linld launched via PXE ignores the vga
parameter while linld launched manually from DOS does not, on the same
hardware.
Working with linld under DOS yielded some interesting information. The text
files specifying the kernel command line parameters for PXE are not actually
in anything remotely like the format linld requires. Having KERNEL and
APPEND keywords is more characteristic of other boot loaders. If you run
linld without parameters under DOS, it gives you very terse command line
information, which is as follows:
LINLD v0.97
Syntax:
LINLD [image=<file>] [initrd=<file>] [vga=vgamode] [cl=<kernel cmdline>]
vgamode: ask,extended,normal or dec/oct/hex number
Use quotes: "cl=..." if you need spaces in cmdline
Use cl=@filename to take cmdline from file
So compared to the CMD file provided for PXE, what linld would really want
is this:
linld image=boot/linux initrd=boot/initrd vga=0x314 [email protected]
where params.txt would contain:
install=tftp://$TFTPIP/boot
rootimage=/root
PROXYADDR=$PROXYADDR
TFTPIP=$TFTPIP
splash=silent
PXEBOOT=YES
mode=5
(It's worth noting that things are actually even slightly more complicated,
because the variables used in the CMD file (e.g. $PROXYADDR) don't actually
work; I have not found any way to use variables on the command line.)
All this tells me that before Novell launches linld, it is internally
processing the contents of these CMD files and spitting out a command line
that linld can really work with. My experience indicates that the vga
parameter is being incorrectly handled in this process.
I cannot figure out where the DOS environment that must exist during the PXE
boot process is coming from. (There must be a DOS environment, because
linld is a DOS Linux launcher.) It was easy to tell with the old preworx
materials, because you could see the .bin files which were nothing but
images of DOS boot floppies; it was even possible to open them in
third-party PXE utilities. I see no comparable files in the current boot
materials. The only other interesting file is loadlin.dnx, but I suspect it
is not involved because the old preworx process had DNX files as well and
they served a different purpose. Consequently I can't look at what is
happening when linld is launched, so I can't get any further in trying to
figure out the problem.
I would be very interested to know whether anybody out there can get their
PXE materials to respond sensibly to vga=ask.
If you can, I'd be interested to know the dates and times of all the backend
NLMs, in case my problem is due to incorrect updating/version mismatch.
If anybody can shed light on the innards of what happens when linld is
launched during PXE boot, I would love to know.
Thanks,
Lisa.

Lisa,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Monitor says VIDEO MODE NOT SUPPORTED after changing display settings

HELP! I am about to have a nervous breakdown with my mac mini! I hooked up the mac to my Philips LCD via DVI. No problem at all. But because the screen is only 15" I wanted to play around with the display settings a bit. So I changed the resolution from it's original 1204x768 to the one higher (not sure of numbers) and to my HORROR, I now can't get any picture at all - it says "VIDEO MODE NOT SUPPORTED". I have tried everything I can think of. I have rest the P-RAM, I have unplugged all cables, plugged the back in again, I bought the mac into work and hooked it up to my monitor and changed the resolution back to 1024x768 which is what it was on originally and that STILL didn't work. I can see the Apple logo and then it goes black and comes up with the error message. HELP! What am I doing wrong - I can't believe one click of a mouse button has rendered my display useless!!!

Welcome to Apple Discussions!
Try booting the mini without the display connected, and then, once the system is running, connect the display. This will often force the system to default to a low resolution, and then correctly detect the display when it is connected.
If that doesn't help, with the display connected, boot into safe mode (hold the shift key down when starting up) and once the system is running, change the resolution to 1024x768, and ensure the correct refresh rate is selected. Rebooting normally ought then to give you a good display.
If all else fails, boot into safe mode with the display connected, and then in the Finder's file menu, use the 'find' option to search for 'windowserver' (no quotes). You should get 2 or 3 results, including one with a string of alphanumeric characters. Move all of them to the trash and restart normally.

Digital Input Cannot Display this Video Mode Optimum Resolution 1280 x 1024 60hz.

HP Pavilion h8-1360t, Windows7 home premium 64-bit, AMD Radeon HD 7570 graphics card.
error message: Digital Input Cannot Display this Video Mode Optimum Resolution 1280 x 1024 60hz.
I get the error message as soon as Windows opens and the desktop displays. Then it goes black with that message. I've been using the computer for awhile and I had it so that when I maximized a window it would go across both screens. I have two monitors on the graphics card. Somehow I changed the settings so that a program would maximize to one monitor or the other. That is how I want it to work. Maybe I activated HydraVision. Now I have the problem when I start.
Also now when I boot to Safe Mode I get the message that there is no AMD graphics driver installed, or it is not functioning properly. I have tried to update it and the computer tells me I have the most recent version installed. I would like to uninstall it and reinstall it, but I'm a little worried I won't get it installed and be without video. Something like that happened to me once before years ago.
Could someone tell me what I should do please?
Thanks,
Jim Allen

HP support is here:
http://www8.hp.com/us/en/contact-hp/contact.html
In safe mode you should uninstall the driver, then try to boot normal again.
Then check if driver was installed by win7.
If not go go AMD website and download latest driver for your card.
V.
*** Say 'Thanks' with Kudos ***

New Arch Logo - Kernel Boot

Well I made a Arch Kernel Boot Logo using the new logo (in knoppix as netpbm is broken in arch)
It is kinda fuzzy on the edges, I'll try to see if its possible to fix up hopefully this weekend.
Get it here: http://mezoko.net/stuff/arch/logo_arch_clut224.ppm
How to install:
Just download this package (i686), I used the pkgbuild from aur, I just replaced logo_linux_clut224.ppm with mine: http://mezoko.net/stuff/arch/kernel26-2 … pkg.tar.gz
From source:
-Way 1-
1) Run abs
2) cd /var/abs/base/kernel26
3) Replace logo_linux_clut224.ppm with logo_arch_clut224.ppm
4) Run makepkg
-Way 2-
1) cd /usr/src/linux/drivers/video/logo/
2) Replace logo_linux_clut224.ppm with logo_arch_clut224.ppm
3) Compile kernel as normal
-Way 3-
1) More official if you have your own kernel source (adds logo to kernel tree)
2) Read: http://gentoo-wiki.com/HOWTO_Linux_Logo … o_it_Right
P.S. if someone could fix the netpbm package, as it lacks
[mezoko@pyther ~]$ pnmtoplainpnm
/usr/bin/pnmtoplainpnm: line 3: pnmtopnm: command not found
Last edited by mezoko (2008-01-17 00:49:45)

mezoko wrote:
Well I made a Arch Kernel Boot Logo using the new logo (in knoppix as netpbm is broken in arch)
It is kinda fuzzy on the edges, I'll try to see if its possible to fix up hopefully this weekend.
Get it here: http://mezoko.net/stuff/arch/logo_arch_clut224.ppm
How to install:
Just download this package (i686), I used the pkgbuild from aur, I just replaced logo_linux_clut224.ppm with mine: http://mezoko.net/stuff/arch/kernel26-2 … pkg.tar.gz
From source:
-Way 1-
1) Run abs
2) cd /var/abs/base/kernel26
3) Replace logo_linux_clut224.ppm with logo_arch_clut224.ppm
4) Run makepkg
-Way 2-
1) cd /usr/src/linux/drivers/video/logo/
2) Replace logo_linux_clut224.ppm with logo_arch_clut224.ppm
3) Compile kernel as normal
-Way 3-
1) More official if you have your own kernel source (adds logo to kernel tree)
2) Read: http://gentoo-wiki.com/HOWTO_Linux_Logo … o_it_Right
P.S. if someone could fix the netpbm package, as it lacks
[mezoko@pyther ~]$ pnmtoplainpnm
/usr/bin/pnmtoplainpnm: line 3: pnmtopnm: command not found
lool when i first posted the ppm problm on a multimedia topic it was for this purpose

Changing virtual console video mode timings

I’ve been trying to figure out how to tweak the video timing for virtual consoles (Ctrl-Alt-F1 to F6). I’m pretty sure KMS (kernel mode-setting) is running; the VCs are at 1280 × 1024 resolution and the Nouveau kernel module is running.
My motivation is that I have an LCD where the default timings (that apparently come from EDID information from the monitor itself!) aren’t handled perfectly by the monitor. In X, I am reducing the “front porch” by 8 dots using xrandr and this gives a correct image, at least while I am using X:
O=DVI-I-1
# Horiz. values from EDID: 1280 1328 1440 1688
xrandr --newmode metho 108 1280 1320 1432 1680 1024 1025 1028 1066
xrandr --addmode "$O" metho
xrandr --output "$O" --mode metho
I am looking for a way to do the equivalent to the other virtual text consoles. I’ve read about a video kernel parameter for setting the resolution, but I haven’t tried it because I haven’t seen any indication you can set the timing with it. I have tried playing with the “fbset” command which mentions some timing settings, but they don’t seem to have any effect.
I’ve also tried making a simple C program to call some libdrm routines like below, but I’m really just stabbing in the dark. This program kind of did what I wanted, but when I switch to another virtual console, the video mode is reverted; even when I switch back to the original console my changes remain undone until I rerun my program.
#include <xf86drmMode.h>
drmModeCrtcPtr crtc = drmModeGetCrtc(drm, crtc_id);
drmModeModeInfo mode = crtc->mode;
mode.hsync_start -= 8;
mode.hsync_end -= 8;
mode.htotal -= 8;
int ret = drmModeSetCrtc(drm, crtc->crtc_id, crtc->buffer_id,
crtc->x, crtc->y, &conn_id, 1, &mode);
drmModeFreeCrtc(crtc);
I fear I am stepping into rather specialised territory, but any clues might be helpful. Even a way to hack or fake the EDID information might make me happy.

grey wrote:Are you using a login manager?
Yea i was using gdm, i don't know what i did, but it seems to work just fine now.

[Solved] How to Suppress Kernel Boot Error Messages?

In
/var/log/errors.log
I get this output while booting:
May 26 00:28:30 localhost kernel: [ 6.943801] sd 6:0:0:0: [sdb] No Caching mode page present
May 26 00:28:30 localhost kernel: [ 6.943802] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 26 00:28:30 localhost kernel: [ 6.945795] sd 6:0:0:0: [sdb] No Caching mode page present
May 26 00:28:30 localhost kernel: [ 6.945797] sd 6:0:0:0: [sdb] Assuming drive cache: write through
May 26 00:28:30 localhost kernel: [ 6.950164] sd 6:0:0:0: [sdb] No Caching mode page present
May 26 00:28:30 localhost kernel: [ 6.950166] sd 6:0:0:0: [sdb] Assuming drive cache: write through
sdb is an external USB 2.0 2TB harddrive formatted as NTFS. My /etc/fstab line for it is:
/dev/sdb1 /media/Win_USB ntfs-3g uid=1000,gid=users,fmask=113,dmask=0022 0 0
My
/etc/udev/rules.d/
directory is empty.
The drive works correctly both under Arch and under Windows 7 in this machine's dual-boot. Googling so far has shown that the above errors are nothing out of the ordinary.
I would like to suppress just those error messages on boot and also do not write them to errors.log.
I do not even have a clue for what I should be searching for to do that. Perhaps someone can helpfully point me to the correct page in the Wiki?
Edit, and "fdisk -l" returns:
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6bf2b3a4
Device Boot Start End Blocks Id System
/dev/sdb1 63 3907024064 1953512001 7 HPFS/NTFS/exFAT
For sdb.
Last edited by headkase (2012-05-30 17:54:29)

erikw wrote:I have this problem too but loglevel=4 does not hide them for me.
You misread.
headkase wrote:
From Here led to Here I set "loglevel=3" in my kernel boot line.
From /boot/grub/menu.lst, my new kernel line looks like this:
kernel /vmlinuz-linux root=/dev/sda4 ro loglevel=3
At loglevel=4 the messages reappear.
See above; you need loglevel=3.

I was trying to fix my screen resolution and now it's stuck on auto detect cannot display this video mode. I tried another monitor and it still won't show anything. I'm locked out

I was trying to fix my screen resolution and now it's stuck on auto detect cannot display this video mode. I tried another monitor and it still won't show anything. I'm locked out

Reset the SMC and PRAM
Intel-based Macs: Resetting the System Management Controller (SMC)
About NVRAM and PRAM
Next try Safe Mode boot and and then normal boot
OS X: What is Safe Boot, Safe Mode?

Slipped into strange video mode - how to reset?

My mac slipped into a strange video mode. It looks like some kind of reverse-video. I was playing around with configuring the icon view, and with a script that automatically positioned my windows, when this happened.
The video mode - when I boot I see the normal white-screen with apple, then the normal blue background for a second, and then it switches into "reverse-video". Menu bar is dark, lettering on menu bar is white. The usual "shadow" effect appears like a highlighted halo; the pop-up menu on the desktop appears black; the letters on that popup appear white. etc.
If I re-boot in safe mode the video appears normal.
Any suggestion what sequence of things I might try to get this reset?
Thanks!

Thank you!!
I had used that key combination as a shortcut for my window scripts, never even occurred to me that it might have triggered something like this.
Thanks again.

My classic video ipod won't switch back to regular video mode after using it on an elliptical. The port still allows me to charge and works on the elliptical and treadmill but it will no longer change modes to allow me to watch my shows on the ipod screen

My classic video ipod won't switch back to regular video mode after using it on an elliptical. The port still allows me to charge and works on the elliptical and treadmill but it will no longer change modes to allow me to watch my shows on the ipod screen

From the iPod's Main Menu choose Videos -> Settings and make sure TV Out is set to Off.
Otherwise, try a hard reset as well. To do this, press and hold both the Select (Center) and Menu buttons together long enough for the Apple logo to appear.
B-rock

[SOLVED] Black screen after kernel boot after pacman -Syu

Hi, after full system upgrade with pacman -Syu, I get after the kernel boot black screen and everything is freezing. Then need to manually shut down the power button!
Normally when my system starts up after the kernel boot I get straight to the command line terminal login.
Can anybody help me how to fix this? Any clues? Any advice is welcome!
The problem is solved by downgrading to kernel 3.6.11.-1
Many thanks for the help from the people on #archlinux !
Last edited by OpenEye (2013-01-29 05:14:04)

jasonwryan wrote:
Please stop bumping your thread: use the edit button
https://wiki.archlinux.org/index.php/Fo … te#Bumping
What have you done about the errors being printed to your logs? You could start by fixing the network error and the broken udev rule...
Are you still using intiscripts? They are no longer supported: https://www.archlinux.org/news/end-of-i … s-support/
# edit: not a pacman issue, moving to Newbie Corner
I have searched for many hours and days for solutions on the internet and forums, tried some things, but with no results! I don't know how to fix the errors! Do you know how to fix that? I'm a total n00b! I'm doing my best as I can! Need help, thanks!

I Can No Longer Switch My Camera to Video Mode

After my ipad had a new update recently, I can no longer switch my camera from camera to video mode. I lost all of my pictures and videoes as well. How can I get them back and have my camera working like before? It does switch from back to front, but the video button does not work.

Try sliding the words "Video" "Photo" "Square" instead of tapping them. Weird, I know, but it works.

Can't zoom in or out in video mode - 4th gen ipad, ios 7.0.2

Today I discovered that I should be able to zoom in and out while in Video Mode in the Camera app. There is no slider at the bottom of the screen, and I've tried pinching my fingers. I'm stumped. Is there anything I need to do in settings? Any suggestions would be very much appreciated! Thanks!

Alison, I sympathise with your situation. After 30+ years in the classroom myself I know well the pain that follows the 'upgrade' to the IT system that then won't run your tried and trusted computer program!
Try this on your iPad - it works on mine.
Try going to Settings - General - Accessibility - Zoom and switch it on (it seems to me it's 'off' by default).
Zooming is now controlled by 'three-finger' actions! (although the original two-finger pinch still operates as well, on actual photos though not videos, I find)
Double-tap with three fingers together and slide up the screen to zoom in.
Double-tap and slide down to zoom out.
Simple double-tap three fingers to return to normal size.
This works with videos. In fact it works even 'now', as I'm typing this here in Safari! It works on the 'home screen' itself! - it works in 'Notes'. It seems to work everywhere in iOS 7.1
So, get your video on screen - use three-finger-slide zoom to achieve required zoom level - play.
Hope this helps with your lesson plans!

Video exposure not working in all 3 video modes new iphone 6 Plus ios 8.1

Bug 1. In video mode, exposure does not automatically brighten in darkly lit areas - then when you touch the screen to focus and try and use the sun slider for upping or lowering the exposure, you have to swipe it many, many times to go a short distance, then IT ONLY WORKS TO DARKEN THE EXPOSURE, IT DOES NOT LIGHTEN IT IN ALL 3 VIDEO MODES. It works fine in Photo mode. Go to this video at :54 to see it working properly: https://www.youtube.com/watch?v=tehcNa3ecs4#t=75
Bug 2: Slo-Motion videos will play back on computers in slow motion ONLY if the base frame rate is set to 60 fps and the Slo-mo speed is set to 240fps. With any other settings the computer (both win and mac) play the video back at full speed.
Especially with bug 1, can any of you check your phone to see if sliding your finger up will brighten the image while in any of the 3 video modes?

Hi,
I'm having also having game sound issues the game music and sounds just go completely quiet in iOS 8.1. Sometimes it'll just be completely quiet and others I'll have game music and sounds and partway through the game I'll lose audio. It's not the side lock/mute button either which I checked.
It's happening in two different games: Shadowgun:Deadzone and Modern Combat 5.
I have that side button above the volume set to toggle mute and I tried changing it to lock rotation instead to see if that made a difference which it did not. I have to kill the game and relaunch it to get the game audio working again.

Kernel boot video mode

Similar Messages

Maybe you are looking for