I’ve had some troubles getting my home system use highresolution consoles, virtual-terminals, framebuffers or whatever the official name is… \ud83d\ude42<\/p>\n
It started out as installation troubles. I went out and bought SuSE 8.2 Professional<\/a>, but when I started the installation (which defaults to graphical) my screen went black. I thought that it was that I had a too new graphics card – GeForce4 Ti 4800 SE, but it’s not it’s the amount of memory in the system that screws this up.<\/p>\n And I have now finally found the solution. After a text-based installation and then forcing the system to use the framebuffer by adding “vga=0x31B video=vesafb”<\/i> at the bootprompt, the symptoms are black screen at boot until the xdm\/kdm\/gdm starts, then the system is usable through X but if you switch to one of the virtual terminals with Ctrl Alt F1-6<\/b> the screen goes black.<\/p>\n You will also get something like this message in \/var\/log\/messages and if you look through dmesg:<\/p>\n vesafb: abort, cannot ioremap video memory 0x8000000 @ 0xf0000000\n<\/p><\/blockquote>\n \nThe solution is to apply this patch, that I found in this message<\/a>, to \/usr\/src\/linux\/drivers\/video\/vesafb.c:<\/p>\n *** vesafb.c 2003-05-01 11:59:23.000000000 +0200 \nThen rebuild your kernel, install it and reboot.<\/p>\n","protected":false},"excerpt":{"rendered":" I’ve had some troubles getting my home system use highresolution consoles, virtual-terminals, framebuffers or whatever the official name is… \ud83d\ude42 It started out as installation troubles. I went out and bought SuSE 8.2 Professional, but when I started the installation (which defaults to graphical) my screen went black. I thought that it was that I … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-49","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/bygden.nu\/jonas\/index.php\/wp-json\/wp\/v2\/posts\/49","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bygden.nu\/jonas\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bygden.nu\/jonas\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bygden.nu\/jonas\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/bygden.nu\/jonas\/index.php\/wp-json\/wp\/v2\/comments?post=49"}],"version-history":[{"count":0,"href":"https:\/\/bygden.nu\/jonas\/index.php\/wp-json\/wp\/v2\/posts\/49\/revisions"}],"wp:attachment":[{"href":"https:\/\/bygden.nu\/jonas\/index.php\/wp-json\/wp\/v2\/media?parent=49"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bygden.nu\/jonas\/index.php\/wp-json\/wp\/v2\/categories?post=49"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bygden.nu\/jonas\/index.php\/wp-json\/wp\/v2\/tags?post=49"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n
\nThe problem is that the sourcecode for the vesa framebuffer within the kernel-source can’t handle the memory if it’s equal to or more than 1GB (I have 1GB in my home system).<\/p>\n
\n— vesafb.c.orig 2003-05-01 11:47:52.000000000 +0200
\n***************
\n*** 521,525 ****
\n video_height = screen_info.lfb_height;
\n video_linelength = screen_info.lfb_linelength;
\n! video_size = screen_info.lfb_width * screen_info.lfb_height * video_bpp;
\n video_visual = (video_bpp == 8) ?
\n FB_VISUAL_PSEUDOCOLOR : FB_VISUAL_TRUECOLOR;
\n— 521,525 —-
\n video_height = screen_info.lfb_height;
\n video_linelength = screen_info.lfb_linelength;
\n! video_size = screen_info.lfb_size * 65536;
\n video_visual = (video_bpp == 8) ?
\n FB_VISUAL_PSEUDOCOLOR : FB_VISUAL_TRUECOLOR;\n<\/p><\/blockquote>\n