xdebconfigurator
Diederik de Haas wrote:
>Where do you have a resolution problem?
Thanks for your interest.
I have it on all my HP Proliant servers, even the later ones still use
Ati Rage XL (graphics not being a priority on a server).
But I have confused myself (again) , within debian-live the
kinfocenter does not show any driver at all. I am limited to 800x600
only.
Under knoppix, driver atyfb is listed by kinfocenter and I can select
1024x768
Also, I have an IBM 8194 P4 desktop with a Geforce4 MX 440, this too
is restricted to 800x600 in debian-live and the driver is listed as
nvideafb, Under knoppix I can again slect 1024x768 and the drivers are
listed as rivafb, nvideafb
Finally, my laptop has an Intel Mobile 945, uses driver intelfb and is
fine at 1024x768 in debian-live and knoppix
I have posted similar in repect of Proliant DL380 previously but this
is a bit different, perhaps; here is a section of my Xorg.0.log:
===================================
(II) Matched mach64 from file name mach64.ids in autoconfig
(==) Matched mach64 for the autoconfigured driver
(==) Assigned the driver to the xf86ConfigLayout
(II) LoadModule: "mach64"
(II) Loading /usr/lib/xorg/modules/drivers//mach64_drv.so
(II) Module mach64: vendor="X.Org Foundation"
compiled for 1.4.0.90, module version = 6.8.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 2.0
(==) MACH64(0): Write-combining range (0xfc000000,0x800000)
(II) MACH64(0): [drm] SAREA 2200+1208: 3408
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "mach64"
(EE) [drm] drmOpen failed.
(EE) MACH64(0): [dri] DRIScreenInit Failed
(II) MACH64(0): Largest offscreen areas (with overlaps):
(II) MACH64(0): 800 x 2021 rectangle at 0,600
(II) MACH64(0): 96 x 2022 rectangle at 0,600
(II) MACH64(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Setting up tile and stipple cache:
32 128x128 slots
14 256x256 slots
(==) MACH64(0): Backing store disabled
(==) MACH64(0): Silken mouse enabled
(II) MACH64(0): DPMS enabled
(II) MACH64(0): Direct rendering disabled
=================================
I can see a fail to load error - "[drm] failed to load kernel module
"mach64"".
So without trying to repeat what's gone on before, the GForce is due
to XOrg , but this may be different?
Regards,
----Original Message----
From: stephen_b_allen@tiscali.co.uk
Date: 25/09/2009 16:16
To: <debian-live@lists.debian.org>
Subj: Re: Fwd: xdebconfigurator
I have been following this thread, this is what the FAQ page has on
it:
=========================================================================
Q: The X configuration does not seems to work, the resolution is too
low. What can I do?
A: Use xdebconfigurator
$ lh_config --bootappend xdebconf
$ lh_config --packages xdebconfigurator
=========================================================================
I tried but as now stated this is possibly irrelevent?
Trying xdebconfigurator it returns a "No known X server system
detected!"
Would it be best to remove these from my builld (including the --
bootappend xdebconf)?
Regards
Internet Security tips and offers from Tiscali - http://www.tiscali.
co.uk/security
_______________________________________________________________________
Internet Security tips and offers from Tiscali - http://www.tiscali.co.uk/security
_______________________________________________________________________
Reply to: