-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

One more thing about aurora:
could the start ship possibly check if VESA FB is really running? Some new motherboards
(Asus A7V-266E) + nVidia Cards  seem to have a problem with at least the latest 
kernels (tested
this on 3 different machines with all this mobo but different nvidia cards): When in 
Vesa FB the
virtual terminals do not show up. After X is started you can switch back to the 
virtual terminals and
they appear normally but before going to X the screen is almost black (bit lighter, so 
something is happening). 
I think it's a kernel bug but as a work-around I disabled VESA fb, Riva FB works fun 
but has known instability problems
in conjuction with the nvidia drivers. So I enabled 16 color VGA in the kernel. When I 
now enable Aurora the system hangs
with a message like (IIRC):
unable to initialize framebuffer object.

possibly aurora really wants at least VESA, so can the script check for this?


Danny

On Friday 04 January 2002 02:12, you wrote:
> Peter Berg Larsen wrote:
> >On Thu, 3 Jan 2002, Guy Zelck wrote:
> >>>>>I guess this is a old thing, I get this with 8.1 also.
> >>>>>Whenever i boot mandrake with any of the Aurora rpms installed
> >>>>>it complains that it can't run kudzu cause it can't open the console.
> >>>>
> >>>>Yes, I noticed the aurora variable used in the concerning startup
> >>>> script stays empty so the if statements fail.
> >>>>Where this aurora variable is supposed to be defined I don't know but
> >>>>would like to.
> >>>
> >>>It (aurora variable) is defined in /etc/rc.d/rc, but it is never
> >>> exported.
> >>
> >>That's true, but, the next line in /etc/rc :
> >>"[ -f /lib/aurora/functions -a -f /etc/aurora/Monitor ] &&
> >>/etc/aurora/Monitor startable && aurora=1"
> >>will never yield aurora=1 since /etc/aurora/Monitor is of size 0 and on
> >>my system even absent.
> >
> >/etc/aurora/Monitor is a softlink to the gui (script) you want
> >aurora to use (e.q. gtk+, newstyle) in /lib/aurora/Monitors/.
> >
> >>Or is this script called Monitor created when you enable aurora in the
> >>Mandrake control center. Anyway, sth. is wrong as I had the same pb.
> >>as the "HeadTechnician".
> >
> >If I understand it correct then yes. (and removes the softlink if aurora
> >is not used).
> >
> >
> >Peter
>
> I've done the test. I didn't think about the symlink because I saw a
> plain file in the package but this is what they do in the postinstall
> phase of the aurora package :
> # rpm -q --scripts Aurora
> postinstall scriptlet (through /bin/sh):
> rm -f /etc/aurora/Monitor
> preuninstall scriptlet (through /bin/sh):
> touch /etc/aurora/Monitor
> [root@gz:/tmp]
>
> Then after enabling aurora we get :
> # ll /etc/aurora/Monitor
> lrwxr-xr-x    1 root     root           38 jan  4 02:02
> /etc/aurora/Monitor -> /lib/aurora/Monitors/Traditional-WsLib*
>
> Nevertheless, the cmd "/etc/aurora/Monitor startable" in /etc/rc must
> under some circomstances yield a false so aurora=1 is not set or is  it
> just "export aurora" that's missing from the file? Anyway, knowing all
> this we can test and solve further.
>
> One other thing on aurora, I chose the Traditional style but never see
> the mouse pointer on startup. I've seen it only once but do not know
> under which conditions. It can't be needing gpm that early in the
> bootprocess can it?
>
> See ya,
> Guy.

- -- 
"I don't know, " said the voice on the PA, "apathetic 
bloody planet, I've no sympathy at all. "
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8NjkeaeiN+EU2vEIRAvOtAJ95c870LfUzpX7xykGY9OQbUuEfAACdEc/H
8wzp312l/N29SGJKUxL82kU=
=c+3x
-----END PGP SIGNATURE-----

Reply via email to