More init 3

[ggg]

OK, looks like I have Mylo's problem. I rarely get myself out of X so who knows how long the problem. All screens  perfect: desktop, grub, bootup, shutdown. Only when I manually drop out of X do the screen fonts become unreadabley huge. Inputs seem to respond OK. How is it possible for even non-X screens to be OK? Is there a run level display setting somwhere?

3.8-3.towo-siduction-686 with proprietary "tainted" nVidia drivers.

[michaa7]

first of all: How does it help to open a new thread?

[dieres]

perhaps your Framebuffer mode doesn't work
try following in /etc/default/grub and do a update-grub

GRUB_TERMINAL=console  (delete the starting #)
comment  GFXMode and GFXPayload

[ggg]

Second of all, how is your response user friendly to a new forum member. Perhaps you were influenced by the folks over at aptosid. They seem to have mellowed in recent years though. Should I have left the name Mylo out so you are not confused? My question is presented from a different standpoint. If you have something useful to present regarding any of the points of my question, feel free to do so. I'm sure the powers that be on this forum can blend my question in with Mylo's thread if you are still confused.

[ggg]

Thank you dieres! I'll try your helpful response and see how it goes.

[michaa7]

OK, looks like I have Mylo's problem. ...

Wasn't meant to be unfriendly but clear:
I think it is best practice to keep problem, facts and solution together instead of discussing each aspect in a different thread.
And I don't see your problem much different from mylo's. Given what you told us so far I think even you do no see much of a difference.

[piper]

I don't think it has anything to do with user friendly or aptosid, what michaa7 was saying is clear

OK, looks like I have Mylo's problem.

Why not keep it in the same thread as Mylo's if it is the same problem ? Why open a new thread ?

Why blame aptosid ?

EDIT: sorry michaa7, your post wasn't there when I was replying

[michaa7]

@ piper

no, no, thanks for your post!

[mylo]

Hi all,

lets cool down. The proposal to consolidate in one thread is more then senseful. I was disappointed to not finding any response in my thread. But I was lucky and found one proposed here.

Sometimes it is indecisive to decide at the start of a thread, whether symptom and root cause are congruent. Just in this case one solution can help solving several peoples problem.

I'll found the proposed solution here, will try it and report later...

EDIT: for me this problem remains, so it not the solution for my machine. Hope to hear other proposals. Thanks!

[dibl]

I recently had to re-learn how to control the tty console fonts on one of my systems.  I'll put the steps here before I forget (again) -- they might help fix this issue. Make sure you have installed the package hwinfo, which wants to be run as root.

1. In a terminal window, find out what resolutions your graphics card can support:

Code Select Expand

hwinfo --framebuffer

2. Find the resolution that you want, among the possibilities.  In my case, it was 1600x1200.

3.  In /etc/default/grub, at the end of the "graphical terminal] stanza set two lines like this:

Code Select Expand

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
# GRUB_GFXMODE=
GRUB_GFXPAYLOAD_LINUX=1600x1200
GRUB_GFXPAYLOAD_LINUX="keep"

4.  Run

Code Select Expand

update-grub

5. Reboot to test it.

[mylo]

Hi dibl,

thanks for your help, however I tried it without success. I just added the "keep" line as the payload was there in grub file.

Is it possible that a hardware defect is driving this?

[dibl]

Hi mylo,

OK, it is more complicated than I thought!  Today, I have been googling and doing experiments.  Here is what I found about my hardware.

On three different computers, with three different nVidia cards, I have to make three different grub configurations to get a higher resolution console.

1.  On this computer:

Code Select Expand

System:    Host: imerabox Kernel: 3.8-4.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2)
          Desktop: KDE 4.9.5 (Qt 4.8.2) Distro: aptosid 2011-02 Ἡμέρα - kde-lite - (201107131633)
Machine:   Mobo: ASUSTeK model: P6X58D-E version: Rev 1.xx Bios: American Megatrends version: 0602 date: 03/24/2011
CPU:       Quad core Intel Core i7 CPU 950 (-HT-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 33735.7
          Clock Speeds: 1: 4216.964 MHz 2: 4216.964 MHz 3: 4216.964 MHz 4: 4216.964 MHz 5: 4216.964 MHz 6: 4216.964 MHz 7: 4216.964 MHz 8: 4216.964 MHz
Graphics:  Card: NVIDIA GF100 [GeForce GTX 480] bus-ID: 05:00.0 X.Org: 1.12.4 driver: nvidia Resolution: 1920x1200@59.9hz
          GLX Renderer: GeForce GTX 480/PCIe/SSE2 GLX Version: 4.3.0 NVIDIA 313.26 Direct Rendering: Yes

I can get a 1600x1200 console with this adjustment in /etc/default/grub, and I leave /etc/grub.d/00_header as default:

Code Select Expand


.
.
.
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
# GRUB_GFXMODE=
GRUB_GFXPAYLOAD_LINUX=1600x1200
GRUB_GFXPAYLOAD_LINUX="keep"


2. On this computer:

Code Select Expand

System:  Host: delle6500 Kernel: 3.8-3.towo.1-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2)
          Desktop: Enlightenment 0.17.1 Distro: siduction 12.1-RC1 Desperado - kde - (201205152133)
Machine:   System: Dell product: Latitude E6500
          Mobo: Dell model: 0PP476 Bios: Dell version: A14 date: 07/31/2009
CPU:       Dual core Intel Core2 Duo CPU P8600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 9576.28
          Clock Speeds: 1: 2401.00 MHz 2: 2401.00 MHz
Graphics:  Card: NVIDIA G98M [Quadro NVS 160M] bus-ID: 01:00.0
          X.Org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1920x1200@60.0hz
GLX Renderer: Gallium 0.4 on NV98 GLX Version: 2.1 Mesa 8.0.5 Direct Rendering: Yes

I do not touch /etc/default/grub or /etc/grub.d/00_header, and I have a nice high-res console (I'm not sure of the resolution, maybe 1600x1200).


3.  On this computer:

Code Select Expand

System:    Host: latitude-D620 Kernel: 3.8-4.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2)
          Desktop: KDE 4.8.4 (Qt 4.8.2) Distro: siduction 12.1.1 Desperado Reloaded - kde - (201206241901)
Machine:   System: Dell product: Latitude D620
          Mobo: Dell model: 0KX350 Bios: Dell version: A10 date: 05/16/2008
CPU:       Dual core Intel Core2 CPU T7200 (-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 7988.84
          Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz
Graphics:  Card: NVIDIA G72M [Quadro NVS 110M/GeForce Go 7300] bus-ID: 01:00.0
          X.Org: 1.12.4 driver: nvidia Resolution: 1440x900@60.0hz
          GLX Renderer: GeForce Go 7300/PCIe/SSE2 GLX Version: 2.1.2 NVIDIA 304.84 Direct Rendering: Yes

I cannot get a high-resolution console with adjustments in /etc/default/grub only -- it is necessary to add a line to /etc/grub.d/00_header, as shown here:

Code Select Expand


.
.
.
if loadfont \$font ; then
EOF
           else
   cat << EOF
if loadfont unicode ; then
EOF
           fi
       fi

   cat << EOF
 set gfxmode=${GRUB_GFXMODE}
 set gfxpayload=keep            <------ ADDED
 load_video
 insmod gfxterm
EOF
.
.
.

then I can get a 1024x768 console by adjusting /etc/default/grub as follows:

Code Select Expand


.
.
.
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=1024x768
GRUB_GFXPAYLOAD=keep

So, it seems different cards require different configurations.

[mylo]

Is it correct, that you configured

on compi 1 with

Code Select Expand

GRUB_GFXPAYLOAD_LINUX="keep"
on compi 3 with

Code Select Expand

GRUB_GFXPAYLOAD=keep ?

[dibl]

YES, that is exactly what I have.

But, I think the "" marks are not important -- I did not notice those.  I will delete them and post back if anything changes.

EDIT:  The quote marks are not needed -- it works correctly without them.

[mylo]

Problem solved! It grew out by d-u, the driver was updated. I assume that is the reason.
Thank you!