On Mon, May 21, 2007 at 07:44:14PM -0500, Owen Heisler wrote:
Anyway, I tried some other video= lines and nothing makes any
difference. I tried vesafb, rivafb, and nvidiafb for the driver and
both 1024x768 (vga=791 works fine) and 1280x960 for the resolution (all
combinations for rivafb and
On Tue, 2007-05-22 at 09:33 +0300, Andrei Popescu wrote:
On Mon, May 21, 2007 at 07:44:14PM -0500, Owen Heisler wrote:
Anyway, I tried some other video= lines and nothing makes any
difference. I tried vesafb, rivafb, and nvidiafb for the driver and
both 1024x768 (vga=791 works fine) and
On Tue, May 22, 2007 at 07:24:40AM -0500, Owen Heisler wrote:
There doesn't seem to be a correct vga= parameter for 1280x960.
I was suggesting 791 as it is still better then the default and you can
see something happening (I just hate it when I mess with options and I
see no change :))
On Tue, 2007-05-22 at 18:56 +0300, Andrei Popescu wrote:
On Tue, May 22, 2007 at 07:24:40AM -0500, Owen Heisler wrote:
There doesn't seem to be a correct vga= parameter for 1280x960.
I was suggesting 791 as it is still better then the default and you can
see something happening (I just
On Tue, May 22, 2007 at 06:28:50PM -0500, Owen Heisler wrote:
So I add nvidiafb to /etc/initramfs-tools/modules, run
update-initramfs -u (this is fun) and now nvidia is also listed.
Now I reboot and try video=nvidiafb:1280x960 and
video=nvidiafb:1024x768 and get something slightly worse
On Sun, May 20, 2007 at 11:06:39PM -0400, cga2000 wrote:
I tried:
video=rivafb:1280x960
video=vesafb:1280x960
but neither worked.
You do realize that you may need to compile a custom kernel to enable
support for a given video card..?
Not necessarily. It should work if you
On Mon, May 21, 2007 at 02:44:29AM EDT, Andrei Popescu wrote:
On Sun, May 20, 2007 at 11:06:39PM -0400, cga2000 wrote:
I tried:
video=rivafb:1280x960
video=vesafb:1280x960
but neither worked.
You do realize that you may need to compile a custom kernel to enable
support
On Mon, May 21, 2007 at 08:18:37AM -0400, cga2000 wrote:
On Mon, May 21, 2007 at 02:44:29AM EDT, Andrei Popescu wrote:
On Sun, May 20, 2007 at 11:06:39PM -0400, cga2000 wrote:
I tried:
video=rivafb:1280x960
video=vesafb:1280x960
but neither worked.
You do realize
On Mon, May 21, 2007 at 12:35:57PM EDT, Andrei Popescu wrote:
On Mon, May 21, 2007 at 08:18:37AM -0400, cga2000 wrote:
On Mon, May 21, 2007 at 02:44:29AM EDT, Andrei Popescu wrote:
On Sun, May 20, 2007 at 11:06:39PM -0400, cga2000 wrote:
I tried:
video=rivafb:1280x960
On Mon, 2007-05-21 at 19:27 -0400, cga2000 wrote:
_Owen_,
What do you get .. a kernel oops .. a black screen of death .. a vga
console with oversized fonts ..?
With any video= parameter, I get the default resolution (640x480/80x25,
I suppose), just like there was no vga= or video=
On Sun, 2007-05-20 at 01:10 -0400, cga2000 wrote:
On Sat, May 19, 2007 at 07:33:51PM EDT, Owen Heisler wrote:
On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote:
On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote:
On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote:
On Thu,
On Sun, May 20, 2007 at 12:01:18PM EDT, Greg Folkert wrote:
[..}
Mind if I add snippets of you two posts to Owen to that Vesa Mode Page?
Not in principle naturally.
Just that I'd be a little concerned about the contents of my posts
possibly misleading others .. A clear case of I don't
On Sun, 2007-05-20 at 17:25 -0400, cga2000 wrote:
On Sun, May 20, 2007 at 12:01:18PM EDT, Greg Folkert wrote:
Mind if I add snippets of you two posts to Owen to that Vesa Mode Page?
Not in principle naturally.
[snip]
Oh, if you do decide to add something to your web page, please let me
On Sun, 2007-05-20 at 01:10 -0400, cga2000 wrote:
On Sat, May 19, 2007 at 07:33:51PM EDT, Owen Heisler wrote:
On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote:
On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote:
On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote:
On Thu,
On Sun, May 20, 2007 at 07:25:41PM EDT, Owen Heisler wrote:
[..]
A list of the available video drivers here (?):
http://linux-fbdev.sourceforge.net/driverlist.php
I tried:
video=rivafb:1280x960
video=vesafb:1280x960
but neither worked.
You do realize that you may need to compile a
On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote:
On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote:
On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote:
http://www.gregfolkert.net/info/vesa-display-codes.html
Very helpful! Although no 1280x960 (grr) unfortunately. Is there
On Sat, 2007-05-19 at 17:09 -0500, Owen Heisler wrote:
On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote:
On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote:
On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote:
http://www.gregfolkert.net/info/vesa-display-codes.html
Very
On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote:
On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote:
On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote:
On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote:
http://www.gregfolkert.net/info/vesa-display-codes.html
Very
On Sat, 2007-05-19 at 18:33 -0500, Owen Heisler wrote:
video=:xres:,yres:,depth:,left:,right:,hslen:,upper:,lower:,vslen:
It looks like I need something like this:
Modeline 1280x1024 DCF HR SH1 SH2 HFL VR SV1 SV2 VFL
Is there some way to get that from xorg?
And what do I use for the
On Sat, May 19, 2007 at 07:33:51PM EDT, Owen Heisler wrote:
On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote:
On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote:
On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote:
On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote:
On Sat, May 19, 2007 at 07:33:51PM EDT, Owen Heisler wrote:
On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote:
On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote:
On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote:
On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote:
On Sun, May 13, 2007 at 07:51:18AM -0400, Douglas Allan Tutty wrote:
Over time, xorg takes up more and more memory. On my i386, I only have
64 MB of ram so I can only run X for about 45 minutes before the system
thrashes. Eventually, Xorg dies but doesn't release the screen. If I
let the
Package: xserver-xorg-core
Running up-to-date Etch.
Over time, xorg takes up more and more memory.
I have two computers:
rocky: PII-233 with 64 MB ram running i386
titan: Athlon64 with 1 GB ram running amd64
On my i386, I only have 64 MB of ram so I can only run X for about 45
On Fri, May 18, 2007 at 09:18:01PM -0400, Douglas Allan Tutty wrote:
Package: xserver-xorg-core
Sorry for the noise. I thought I'd turn my question into a bug report
but sent it here instead of bugs by accident.
Doug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On Fri, May 18, 2007 at 09:24:37PM -0400, Douglas Allan Tutty wrote:
On Fri, May 18, 2007 at 09:18:01PM -0400, Douglas Allan Tutty wrote:
Package: xserver-xorg-core
Sorry for the noise. I thought I'd turn my question into a bug report
but sent it here instead of bugs by accident.
Don't
On Sun, May 13, 2007 at 02:43:15PM +0200, Hervé Piedvache wrote:
Le dimanche 13 mai 2007, Douglas Allan Tutty a écrit :
I'm having trouble with Xorg under Etch i386 and similar annoyance under
amd64.
Over time, xorg takes up more and more memory. On my i386, I only have
I had the same
On Sun, May 13, 2007 at 10:22:00AM -0500, Mumia W.. wrote:
On 05/13/2007 06:51 AM, Douglas Allan Tutty wrote:
I'm having trouble with Xorg under Etch i386 and similar annoyance under
amd64.
Over time, xorg takes up more and more memory. [...]
I also installed Etch on a computer that has
On Thu, May 17, 2007 at 12:17:34PM -0400, Douglas Allan Tutty wrote:
On Sun, May 13, 2007 at 10:22:00AM -0500, Mumia W.. wrote:
On 05/13/2007 06:51 AM, Douglas Allan Tutty wrote:
Try out the VESA driver and see if the problem recurs.
Would if I could. On the i386, dpkg-reconfigure
On Thu, May 17, 2007 at 05:31:09PM +0100, Tom Furie wrote:
On Thu, May 17, 2007 at 12:17:34PM -0400, Douglas Allan Tutty wrote:
On Sun, May 13, 2007 at 10:22:00AM -0500, Mumia W.. wrote:
On 05/13/2007 06:51 AM, Douglas Allan Tutty wrote:
Try out the VESA driver and see if the problem
On Thu, 2007-05-17 at 12:58 -0400, Douglas Allan Tutty wrote:
On Thu, May 17, 2007 at 05:31:09PM +0100, Tom Furie wrote:
On Thu, May 17, 2007 at 12:17:34PM -0400, Douglas Allan Tutty wrote:
On Sun, May 13, 2007 at 10:22:00AM -0500, Mumia W.. wrote:
On 05/13/2007 06:51 AM, Douglas Allan
On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote:
http://www.gregfolkert.net/info/vesa-display-codes.html
Very helpful! Although no 1280x960 (grr) unfortunately. Is there any
way to get that?
signature.asc
Description: This is a digitally signed message part
On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote:
On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote:
http://www.gregfolkert.net/info/vesa-display-codes.html
Very helpful! Although no 1280x960 (grr) unfortunately. Is there any
way to get that?
vbetool is supposed to do it.
Or
I'm having trouble with Xorg under Etch i386 and similar annoyance under
amd64.
Over time, xorg takes up more and more memory. On my i386, I only have
64 MB of ram so I can only run X for about 45 minutes before the system
thrashes. Eventually, Xorg dies but doesn't release the screen. If I
I had the same trouble was my video driver which made that ...
Switch to last version of nvidia solved the trouble for me !
regards,
Le dimanche 13 mai 2007, Douglas Allan Tutty a écrit :
I'm having trouble with Xorg under Etch i386 and similar annoyance under
amd64.
Over time, xorg takes up
On 05/13/2007 06:51 AM, Douglas Allan Tutty wrote:
I'm having trouble with Xorg under Etch i386 and similar annoyance under
amd64.
Over time, xorg takes up more and more memory. [...]
I also installed Etch on a computer that has only 64MB of RAM, and I
haven't noticed this problem. As Hervé
On Sun, Feb 25, 2007 at 08:26:03PM -0500, Kamaraju S Kusumanchi wrote:
Bill Moseley wrote:
Every once in a while my desktop machine becomes unresponsive and top
shows that Xorg is using all my memory.
Are there any errors in the log files such as /var/log/Xorg.0.log ?
What is your
On Sun, Feb 25, 2007 at 10:23:09PM -0500, Roberto C. Sanchez wrote:
Firefox? I haven't seen it in a while, but I used to occasionally see
my machine get *really* slow and when I would do a top, X was chewing
everything up. However, if I closed Firefox (or killed it), things
would return to
This is just a probe to see if anyone else is having problems with
Xorg eating memory.
Every once in a while my desktop machine becomes unresponsive and top shows
that Xorg is using all my memory.
I was out of town and ssh'ing into my machine every day or so and it
was fine, except today I was
Bill Moseley wrote:
Every once in a while my desktop machine becomes unresponsive and top
shows that Xorg is using all my memory.
Are there any errors in the log files such as /var/log/Xorg.0.log ?
What is your video card, what driver are you using?
Are you tracking etch or sid?
raju
--
On Sun, Feb 25, 2007 at 05:05:31PM -0800, Bill Moseley wrote:
This is just a probe to see if anyone else is having problems with
Xorg eating memory.
Every once in a while my desktop machine becomes unresponsive and top shows
that Xorg is using all my memory.
Firefox? I haven't seen it in
Top reports Xorg using 90% of RAM and processes get killed. All swap
is being used, but vmstat isn't showing that much so and si paging.
Load average every once in a while will shoot up to 25 or so.
I can find a few posts about memory leaks, but not may responses. And
one memory leak bug report
Pardon me for a second. Shit, shit shit!
Ok, Now after a fresh dist-upgrade and a reboot only one of my
monitors is running.
This really sucks. For one thing when I upgraded to Xorg it decided
to make my main monitor (the screen that comes up in text mode
before running the xserver) the
Whew. Panic time is over.
The drivers from the Matrox site fixed everything. Yea Matrox!
Xorg put my monitors back in the right order and both monitors are
working.
--
Bill Moseley
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
43 matches
Mail list logo
