On 2004.03.08 15:40, Nicolas CASSART wrote:
> >How do you shutdown kdm or kde?
> I shutdown my laptop from kde with the K menu ;
> When i do this i can't see my shutdown splashscreen because the
> resolution seems to be 40x30 and without interlacing, but it is not
> important :)
> I've tried the via_drv.o-unichrome_r10-debian_sarge_xfree86-4.3.0-2
> the files section with the new xfree86-4.3.0-5 from sid but it
> work (it worked with 4.3.0-2)
Can you give more information about the first _and_ the second.
What is the shutdown splashscreen?
What happens when you try to load the binary for -2 in -5? What is in
the log, how does X fail, etc.
On 2004.03.08 17:08, Nicolas CASSART wrote:
> This is the log with the
> It worked when i had the experimental debian xfree-4.3.0 builds
> on my sarge (because sid's were 4.2.1) .
> My splash screen is a picture that is displayed on boot in
> mode (bootsplash kernel patch and splashutils)
> I tried without splash and the result is the same .
> The via_drv.o i use is from the today's unichrome-cvs built against
> original xfree-4.3.0 tarball contained in debian-src package
> (II) LoadModule: "via"
> (II) Loading /usr/X11R6/lib/modules/drivers/via_drv.o
> (EE) LoadModule: Module via does not have a viaModuleData data
> (II) UnloadModule: "via"
> (II) Unloading /usr/X11R6/lib/modules/drivers/via_drv.o
Aha. It seems that this is the vga register restoration problem!
This has been reported on netBSD, where the console implementation
doesnt do its own restoration too (on top of what xfree86 already tries
to do). Normal linux console does this itself np, effectively masking
the problem with the via driver.
Now, i have never used directfb, never even been near it. But someone
on undernet was willing to answer some questions about it. The splash
screen apparently runs on top of directFB, directFB uses the hardware
directly. And then you run xfree86 which, in this case, also uses the
hardware directly. Apparently this isnt much of a problem, with a
recent enough X and with a suited driver. (this amazes me though, as i
would expect both to contend for the same resources)
Anyway, this might be where the VT restoration issues comes back at us
again. This is imho great news, as this means that we can test this
without installing netBSD :)
About the driver issue, hrm, apparently nothing has changed (in this
respect) between -2 and -5.
On 2004.03.08 18:20, Luc Verhaegen wrote:
> About the driver issue, hrm, apparently nothing has changed (in this
> respect) between -2 and -5.
Lol, i am a clueless idiot. I plainly (and completely) stripped the
strip --strip-debug --remove-section=.note --remove-section=.comment
shouldve been used. Fixing that. Please try the new version i have put