Subject: Re: vmode for the Ruff-Pack 8.0 3.3.6 RPMS
From: Evan Read (eread@netaccess.co.nz)
Date: Sat Feb 26 2000 - 14:16:22 MST
Not quite what I was looking for ;)
Seems that any vmodes apart from 16 and 17 make my monitor sleep (well, the
sample I tried) when booting Linux.
I think I will take this from a different angle. Can anyone tell me where
Xconfigurator sends it's errors? It is telling me "There is a problem with
you X configuration", but I have no clue as to what is broken! Surely this
tool would like to give me more info than that.
BTW, I tried re-symlinking /etc/X11/X to /usr/X11R6/bin/Xpmac (which I
assume means I am using the Xpmac server) but to no avail. Last time I
tried the 3.3.5 upgrade, I remember having to switch something there.
BTW, I am on a 2.2.6 kernal. Not sure if this is a problem ;) I am too
lazy and am gonn re-upgrade with CS 1.2 ;)
THanks (after looking over some mail list archives, looks like I should be
using FBDev)
Ev.
----------
>From: Jim Cole <greyleaf@yggdrasill.net>
>To: yellowdog-general@lists.yellowdoglinux.com
>Subject: Re: vmode for the Ruff-Pack 8.0 3.3.6 RPMS
>Date: Sat, 26 Feb 2000 5:57 PM
>
>Hi - I use the following line with the 3.3.6 stuff on a PowerBook...
>
>video:atyfb:vmode:14,cmode:32,mclk=70
>
>It has been there so long, I don't even remember what it all means ;) If
>it ain't broken.. and all that. In XF86Config, I set my depth to 24.
>
>Jim
>
>Evan Read's bits of Sat, 26 Feb 2000 translated to:
>
>>Hey there,
>>
>>Just ran the RPMs for 3.3.6. Had Xconfigurator shit itself on me ;).
>>
>>Upgraded Xconfigurator from the Ruff-Pack (satisfying all the library
>>requirements for all the updated libraries it needed bar some stuff about
>>"/etc/services" have a dependency on something older and something else.
>>
>>I run it and in some modes, it runs the gray screen but the mouse isn't
>>working and sometimes it just jumps to the "Problem with configuration"
>>screen. Yes, I updated mouseconfig and ran it first. Either way, it always
>>fails.
>>
>>I think last time this happened, one had to enter in a mode for the command
>>"vmode". What is it? I tried "16" to no avail (and the screen seems to
>>shift). I tried "15" and the monitor tried to sleep.
>>
>>Haven't tried 32 or 24 yet because I know there are some issues so perhaps
>>someone could point me in the right direction.
>>
>>Thanks to all
>>
>>Ev.
>>
>
>
This archive was generated by hypermail 2a24 : Wed Mar 01 2000 - 00:07:12 MST