now winXP is messed up! + turning off + useFBdev

[fossatig]

I was trying to solve a problem with the linux
boot with framebuffer and the console "shifted down"
(I posted this problem a couple of days ago),
and after a few different attempts, with still some
problems, not X works.

However, now when I boot winXP during boot the
screen just goes dark, as if it was turned off, and
never comes back again.
The boot seem to end fine (though invisibly).
If I "suspend" and then "restart", then I get the winXP session back to visible.

Any clue?
I never toucher a thing in the winXP installation....

This behavior started to happen after I tried to switch in linux between different display resolutions, with
the Ctrl-Alt-+- ....
This is the only detail that I seem to be able to correlate with the screw up of winXP.

Also, linux does not seem to be able to turn off the computer at shutdown.

I've read here and there that nvidia drivers may have a problem with power management, but I could not really follow the details.
Does anybody have a few simple guidelines to share with me?
Thanks.

Final question: I am still fighting with the framebuffer.
I don't seem to be able to get around it... it seems that its "start" is "hardwired" in the kernel.
Is there a way to disable it?
The fact that the kernel supports it should not mean necessarily that it has to use it, isn't it?

Among other things, I have tried to set UseFBdev option to false in the XF86Config file.
But according to XFree....log it is ignoring it.
Is this in fact a valid option?

Thank you very much!

System:
DELL i8100
Geforce 2 Go (32Mb)
Debian woody, 3.0r1

[Kiamu]

your changes in linux should have no sideeffects on windoze...

the only thing i can imagine is, that you played with the config of your bootmanager (usually lilo) ?

i had the same powerdown problem:
i simply switch from apm to acpi in the kernel and load the modules at boot. shutdown is smooth since and i have info about cpu temp and few other thingies ;)

yepp, you can change the 'hardwired' kernel things if that is the problem: change the kernel config and recompile it. (sounds difficult, but it is not as hard as it seems... )

[fossatig]

Well, I did not change anything substantial in my lilo.conf, it is a very lean one.
I have played around a little with the vga option trying to work around the framebuffer problem.

I eventually installed a different kernel, 2.4.18 non bf24 (which is the one I had installed originally), and this one does not use framebuffer, apparently.
There is no penguin at boot.
[note: of course I then recompiled the nvidia modules]
[note-2: I have tried the hack in the nv.c code, changing the return=1 to return=0]

However, once X starts, still I get the consoles shifted down a bit, and the prompt disappears below the horizon...

I also have the "black screen" problem that many people have complained about (and not real solutions have been posted).
If get X "console" back if I play a little with the Ctrl-Alt-F# keys... quite randomly.
I am really annoyed.

But the worst thing of all is still the black screen when I boot winXP.


switch from apm to acpi in the kernel and load the modules at boot.

does this need kernel recompile?
btw, at boot, in dmesg, there are messages saying:


Local APIC disabled by Bios -- reenabling
Found and enabled local APIC
...
Using local APIC timer settings
calibrating APIC timer.


The bios is AO7, on i8100.
The nvidia I am trying is 4191 (tried 3123, but not really much improvement].

I have the NVreg_softEDIDs=0 and NVreg_Mobile=1 (dell).
NvAGP=3 in XF86Config, but in the last couple of days I have gone through 0 and 1 as well.

Bottom line: by far my main worry is about the problem with winXP boot... it does not make sense! Please somebody come up with some good clue!

Thanks!

[bwkaz]

Heh, APIC != ACPI. ;)

APIC is a way to route IRQ's, and ACPI is a power management function.

Disabling ACPI shouldn't require a kernel recompile, unless ACPI support isn't built as a module.

[fossatig]

Yes, apic != acpi.
However, I have often found the 'disableapic' option among recommendations for people encountering this kind of troubles.

Any idea as to why they do it?

Thanks a lot.
-G

[bwkaz]

No, not really... huh.