Hi !
> Fixed. kgicon.o compiles and gets inserted. Ah, graphical console at
> 640x480 !!
Ah - good.
> 3) Why do I always get the message
> "mtrr: base(0xe6000000) is not aligned on a size(0xfe0000) boundary"
> when switching consoles ?????
Strange - looks like a kernel bug to me. To my knowledge this message does
not come from within kgicon. You might want to try the kgicon_mtrr=0
parameter - though I have no idea what it does ... could someone explain ?
> Next I generated my /etc/ggi/kgicon.mon (for MiroPTLA150) and touched
> /etc/fb.modes. Setmon works. No more messages when switching consoles
> !!!!!!
Oh - interesting.
> 4) Why does fbset (e.g. fbset -xres 1024 -yres 768) always return
> "ioctl: FBIOPUT_VSCREENINFO: Invalid argument" ??????????
Hmm - try also giving -xvres and -yvres. I've seen problems when you don't.
> 5) Is there a way to remove the kgicon-module ????
No. Unfortunately not.
> 6) This time trying "modprobe kgicon kgicon_width=1024 kgicon_height=768
> kgicon_bpp=24". Excerpt from my /var/log/messages-file:
> kernel: nVidia Riva Card detected.
> kernel: Control mem=0xE4000000
> kernel: Framebuffer mem=0xE6000000
> kernel: 16256KByte of RAM detected
> kernel: KGI monitor driver rev $Revision: 1.12 $
> kernel: RAMDAC_init.
> kernel: nVidia Riva Integrated Clock driver rev 0.1
> kernel: Crystal = 13500KHz
> kernel: Manufacturer Model driver loaded.
> kernel: error: kgifb_set_var: Unsupported bpp '1'.
> kernel: error: kgifb_set_var: Unsupported bpp '1'.
> kernel: mtrr: base(0xe6000000) is not aligned on a size(0xfe0000)
> boundary
> kernel: kgifb_init: xres 640 yres 480 bpp 8 vaddr 0xc884c000 paddr
> 0xe6000000 size 16646144
This is due to the following probing sequence:
{ 0, 0, 0 }, /* first try command-line parameters */
{ 0, 0, 1 },
{ 0, 0, 8 },
{ 0, 0, 16 },
{ 0, 0, 24 },
{ 0, 0, 32 },
{ 640, 480, 0 },
{ 640, 480, 1 },
{ 640, 480, 8 },
A 0 here means "use commandline values".
Thus it probes 1024x768x24,1024x768x1 (1st warning),1024x768x8,x16,x24,x32,
640x480x1 (2nd warning), 6480x480x8 (success).
Your mode is rejected, because the standard generic/generic monitor driver
is set up for VGA-only when it comes up and has not yet talked to setmon
for security reasons.
You need to insert at 640x480, setmon and then use fbset.
> However I moved on and built and installed libgii. Next configure
> libggi:
> 7) I can't set the include-path of libgii. The configure-script seems to
> insist on the include-files to reside in /usr/include/ggi but libgii
> copies them to
> /usr/local/include/ggi.
This is strange - it works for me. However you can use
./configure --with-gii=DIR to force it to /usr/local/.
> Any ideas how I can run ggi at higher resolutions ?
Your first idea was right - contact me if the problem persists - we'll need
some tracing, then. Also try, if the demos can switch to higher resolutions.
CU, ANdy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
