On Mon, Apr 19, 2021 at 10:00:59AM +0530, Susmita/Rajib wrote:
> On Mon, 19 Apr 2021 00:12:29 -0400, Felix Miata wrote:
> Ref: https://lists.debian.org/debian-user/2021/04/msg00530.html
>
> "...
> Unless and until all traces of NVidia's driver installation and associated
> configuration changes h
On Mon, Apr 19, 2021 at 09:40:54AM +0530, Susmita/Rajib wrote:
> Would the setps as described in the following link be necessary?
> http://www.linuxfromscratch.org/blfs/view/svn/x/xorg-server.html
>
> ---
> Installation of Xorg Se
as iso by
> > loopback loop, or with iso extracted and am presently using knoppix
> > for the HCL Me laptop.
I'm assuming that the HCL Me laptop is the one you want to install on - and
was the one the screenshots relate to. To make it easier, I'm assuming that
you are prepared
Susmita/Rajib composed on 2021-04-19 10:30 (UTC+0530):
> Okay, in any case I am to reinstall fresh and latest stable Debian, as
> advised by Dr./Mr. Cater.
> So in nutshell, may please the steps be described? The idea involved?
Susmita/Rajib composed on 2021-04-19 8:35 (UTC+05300):
> On Sun, 18 Apr 2021 21:52:25 -0400, Felix Miata wrote:
> [...]
> As above indicated, it works with Debian 10, using the FOSS default X driver
> (Modesetting DIX), along with the Nouveau kernel driver it depends on. No
> proprietary NVidia or
On Mon, 19 Apr 2021 00:12:29 -0400, Felix Miata wrote:
Ref: https://lists.debian.org/debian-user/2021/04/msg00530.html
"...
Unless and until all traces of NVidia's driver installation and associated
configuration changes have been purged from your machine, I can be no
help except
WRT eradicating
Would the setps as described in the following link be necessary?
http://www.linuxfromscratch.org/blfs/view/svn/x/xorg-server.html
---
Installation of Xorg Server
Install the server by running the following commands:
./configure
On Sun, 18 Apr 2021 21:52:25 -0400, Felix Miata wrote:
[...]
As above indicated, it works with Debian 10, using the FOSS default X driver
(Modesetting DIX), along with the Nouveau kernel driver it depends on. No
proprietary NVidia or other non-Debian software is required for competent Xorg
operati
un knoppix, either as iso by
> loopback loop, or with iso extracted and am presently using knoppix
> for the HCL Me laptop.
>
> Please tell me if there is a possibility of using Debian to use vesa
> (or fbdev) from grub, although fbdev is deprecated, vesa runs fine.
> But a little stressful
esently, Debian Live isn't
> able to run on it even in Vesa. GUI installation is possible, but not
> using vesa post-installation.
>
I followed through the screenshots you provided.
> Earlier when computers and drivers were 32bit, drivers from nvidia
> downloaded directl
my asking for suggestion on
which Debian-authorised laptop to buy this time to avoid undue
complexity with the ones that I have already.
This one relates to my HCL-Me laptop. Presently, Debian Live isn't
able to run on it even in Vesa. GUI installation is possible, but not
using vesa
On 2018-02-22 15:57 +0100, Dominique Dumont wrote:
> On Tuesday, 20 February 2018 11:40:49 CET terryc wrote:
>> i've just finshed trying amdgp, radeon 7 ati drivers under wheezy and
>> stretch and it is a total wipeout. All ii can get working is a copied
>> default singl
On Tuesday, 20 February 2018 11:40:49 CET terryc wrote:
> i've just finshed trying amdgp, radeon 7 ati drivers under wheezy and
> stretch and it is a total wipeout. All ii can get working is a copied
> default single screen under vesa driver.
Can you make sure that radeon kernel mo
How?
As per subject I am trying to get something other than a basic single
screen screen running on this dual port GPU.
i've just finshed trying amdgp, radeon 7 ati drivers under wheezy and
stretch and it is a total wipeout. All ii can get working is a copied
default single screen under
Am Mittwoch, 9. April 2014, 02:20:16 schrieb Scott Ferguson:
> On 09/04/14 01:33, Andrei POPESCU wrote:
> > On Ma, 08 apr 14, 16:20:22, Hans wrote:
> >> Is it possible (and if yes, how), to compute the code from the wanted
> >> solution? For example, if I want to have 1440x900, can I compute the
>
On 09/04/14 01:33, Andrei POPESCU wrote:
> On Ma, 08 apr 14, 16:20:22, Hans wrote:
>>
>> Is it possible (and if yes, how), to compute the code from the wanted
>> solution? For example, if I want to have 1440x900, can I compute the
>> vga=whatever code? Or must I always look into a table?
See:-
On Ma, 08 apr 14, 17:48:17, Hans wrote:
>
> No, I could not find an answer, if the number from the "vga=" can be computed
> out of the wanted resolution. So, for example, 800x600x32 = 789h(ex) or
> whatever.
...
> Maybe my English is too bad, so my question is misunderstood.
You question was w
Hi Andrei,
> GRUB_GFXPAYLOAD_LINUX=1440x900
>
I know this variable. It is from grub2, I know. Besides I am still using grub-
legacy, my problem is not to find the correct vga= for my resolution. I know
this one.
No, I could not find an answer, if the number from the "vga=" can be computed
On Ma, 08 apr 14, 16:20:22, Hans wrote:
>
> Is it possible (and if yes, how), to compute the code from the wanted
> solution? For example, if I want to have 1440x900, can I compute the
> vga=whatever code? Or must I always look into a table?
Not what you're asking for, but maybe what you need:
> The video mode number of the Linux kernel is the VESA mode number plus
> 0x200
>
>
No no, what I mean is the following: Guess, I want to have a special
resolution at boot, for example 800x600x32.
Now I need the vga=whatever. To get it, I can look into a list and see, yes,
i
ode number of the Linux kernel is the VESA mode number plus
0x200
>
> Is it possible (and if yes, how), to compute the code from the wanted
> solution? For example, if I want to have 1440x900, can I compute the
> vga=whatever code? Or must I always look into a table?
>
&
's 317h".
And 317h is defined by VESA 2.0 as 1024x768x16.
> Is it possible (and if yes, how), to compute the code from the wanted
> solution? For example, if I want to have 1440x900, can I compute the
> vga=whatever code? Or must I always look into a table?
Sure, there'
Hi there,
I am asking myself now for many years, if there is a relationship between the
solution and the vesacode at the grub commandline.
Of course, there is a table everywhere, where I can see, which resolution is
at the givenm mode (i.e. vga=791 is 1024x768).
But what does 791 mean? I guess
On Fri, 18 Oct 2013 22:26:52 -0400 (EDT)
Stephen Powell wrote:
> I tried that. But the previous version of the driver has a dependency on
> xserver-xorg-video-abi-12, which is a virtual package not currently provided
> by any current package. The last package to provide it was the old version
>
On Thu, 17 Oct 2013 13:20:03 -0400 (EDT), Marko Randjelovic wrote:
> On Thu, 17 Oct 2013 07:47:01 -0400 (EDT), Stephen Powell wrote:
>>
>> Due to a bug in the MACH64 driver (see Debian bug report 726585 for details),
>> I am temporarily using the VESA X driver in Debian je
for monitors. My German monitor might be
> equal to another, international one, but IIRC I couldn't get info by the
> web, just Suse supported it. On Arch Linux with a nearly equal config, I
> get 81.9kHz/90.0Hz with the above config. IIRC the frequency thing does
> work with the vesa dr
On Thu, 17 Oct 2013 07:47:01 -0400 (EDT)
Stephen Powell wrote:
>
> Due to a bug in the MACH64 driver (see Debian bug report 726585 for details),
> I am temporarily using the VESA X driver in Debian jessie to get graphical
> support to work on my machine. I am experiencing three p
On Thu, 2013-10-17 at 14:54 +0200, Ralf Mardorf wrote:
> On Arch Linux with a nearly equal config, I
> get 81.9kHz/90.0Hz with the above config.
*chuckle*
Regarding to the frequency section the configs are equal ;). I type
faster, than I think ;).
--
To UNSUBSCRIBE, email to debian-user-requ.
On Thu, 2013-10-17 at 07:47 -0400, Stephen Powell wrote:
>Section "Device"
>Identifier "Default Device"
>Driver "vesa"
>EndSection
>Section "Screen"
>Identifier "Configured Screen"
Due to a bug in the MACH64 driver (see Debian bug report 726585 for details),
I am temporarily using the VESA X driver in Debian jessie to get graphical
support to work on my machine. I am experiencing three problems with it.
First of all, I can only get 1024x768 resolution to work at a 60 Hz
nces, right and
down to Monitor Settings and LM. Strike
to open the resolution menu. Use
to reach resolution 1024 x 768. Strike .
to OK. Strike . At this resolution
the mouse and display coordinates are aligned
... and the VESA driver isn't used; good!
The new setting isn't pr
CamaleA3n,
> http://wiki.debian.org/Xorg
>
> You can follow the steps provided in *"What if I do not have an xorg
> config file?"* and let xorg to generate its own "xorg.conf" file. Then
> just change the "Driver" line and replace it with "vesa
On Mon, 21 Dec 2009 16:28:31 -0800, peasthope wrote:
> Date: Mon, 21 Dec 2009 22:50:09 + (UTC), Camaleon wrote,
>> Section "Device"
>> Identifier "Configured Video Device"
>> Driver "vesa"
>> EndSecti
Date: Mon, 21 Dec 2009 22:50:09 + (UTC), Camaleon wrote,
> Section "Device"
> Identifier "Configured Video Device"
> Driver "vesa"
> EndSection
>
> And restart X.
Yields a black screen.
> Review the xorg log to
On Mon, 21 Dec 2009 14:45:51 -0800, peasthope wrote:
> The problem with X and the Intel 82815 Chipset Graphics Controller is
> expanding. A mouse pointer is no longer visible.
>
> Can anyone offer an xorg.conf which will ensure that the vesa driver is
> used rather than the
Folk,
The problem with X and the Intel 82815 Chipset Graphics
Controller is expanding. A mouse pointer is no longer visible.
Can anyone offer an xorg.conf which will ensure that the
vesa driver is used rather than the current default driver.
Thanks, ... Peter E.
--
Google
Robert Latest wrote:
Hello folks,
recently I accidentally hosed my old kernel image (it was something
that ended on -k7). The only reason I'd kept it was because I couldn't
get anything but the ugly boxy 80-by-something text mode console fonts
to work with the 2.6.26-x-686 line of Debian prepack
Hello Frank,
> Assuming you are running a Debian kernel,
Correct, 2.26-2-686 out of the box
>> Use vga=ask for menu.
doesn't work. All I get is the list of standard VGA modes. When I type
"scan", the screen goes blang for about a minute but the system
doesn't find any ad
On Sun, 2009-07-05 at 21:59 +0200, Robert Latest wrote:
>
> Long story short, when I put "vga=ask" in grub's menu.lst, I can't
> enter anything but the 80-by-something modes. I've searched the Net up
> and down, have tried the 0x30... modes in hex, in decimal , with the
> '0x' and without ... noth
On Sun,05.Jul.09, 21:59:17, Robert Latest wrote:
>
> What can I do? I like working in the console a lot, but I need more
> and better-looking characters on screen.
Try using modes shown by 'hwinfo --framebuffer' (in package hwinfo).
Regards,
Andrei
--
If you can't explain it simply, you don't u
On Sun, Jul 05, 2009 at 09:59:17PM +0200, Robert Latest wrote:
> Long story short, when I put "vga=ask" in grub's menu.lst, I can't
> enter anything but the 80-by-something modes.
Have you enabled video mode selection support? That used to be a
kernel option.
--
To UNSUBSCRIBE, email to debian-
Hello folks,
recently I accidentally hosed my old kernel image (it was something
that ended on -k7). The only reason I'd kept it was because I couldn't
get anything but the ugly boxy 80-by-something text mode console fonts
to work with the 2.6.26-x-686 line of Debian prepackaged kernels.
Anyway,
On 02 May 2009, Stefan Bellon wrote:
> Kelly Clowers wrote:
> > Just for fun, you might try purging and reinstalling
> > the drivers, then see what kind of results you get
> > with this setup.
>
> Yes, you are right. Because of the fact that not even the vesa driver
&g
Kelly Clowers wrote:
> Just for fun, you might try purging and reinstalling
> the drivers, then see what kind of results you get
> with this setup.
Yes, you are right. Because of the fact that not even the vesa driver
worked, I went that way and uninstalled all the fglrx related pac
Anthony Campbell wrote:
> I have the same card and it is working well on Sid, with 3d
> acceleration, using radeonhd. Make sure have firmware-linux (see bug
> 523724).
Would you mind posting or sending me by private email your xorg.conf
configuration file?
Greetings,
Stefan
--
Stefan Bellon
n is too new for you, you can install an
> > older fglrx (9.3) or stick with the free driver.
>
> But nevertheless, even if my X1400 was legacy and not supported in
> fglrx anymore (which is not the case), then the main problem is that
> neither radeonhd, nor radeon, nor pla
In <49fad646.40...@googlemail.com>, thveillon.debian wrote:
>I don't know if I am the only one, but the attachment you sent in the
>first message has been messed up, to the point that it's impossible to
>understand anything:
>
>begin 644 xorg.conf
>M"B,@>&]R9RYC;VYF("A8;W)G(%@@5VEN9&]W(%-Y[...]
>
>
On Fri, May 1, 2009 at 04:18, Stefan Bellon wrote:
> thveillon.debian wrote:
>> I don't know if I am the only one, but the attachment you sent in the
>> first message has been messed up, to the point that it's impossible to
>> understand anything:
>
> Ah, didn't know that. I'll put the files inlin
(size
= 0x4000)
(II) RADEONHD(0): FB: Allocated Cursor Image at offset 0x4000 (size
= 0x4000)
(II) RADEONHD(0): Connector[0] {RHD_CONNECTOR_VGA, "VGA CRT1",
RHD_DDC_0, RHD_HPD_NONE, { RHD_OUTPUT_DACA, RHD_OUTPUT_NONE } }
(II) RADEONHD(0): Connector[1] {RHD_CONNECTOR_PANEL,
rietary libGL maybe ?
>
> Unlikely. In the past I have switched between fglrx, radeon and vesa
> quite some times if one or the other did have some issue. And switching
> to another one always worked without having to change more than the
> driver line in the xorg.conf file.
>
tched between fglrx, radeon and vesa
quite some times if one or the other did have some issue. And switching
to another one always worked without having to change more than the
driver line in the xorg.conf file.
It looks like the new Xorg has some very fundamental change which I am
not aware of.
So,
less, even if my X1400 was legacy and not supported in
> fglrx anymore (which is not the case), then the main problem is that
> neither radeonhd, nor radeon, nor plain vesa seem to work right now.
> THIS is my problem.
So maybe you have another problem on top of that, some leftovers fro
river.
But nevertheless, even if my X1400 was legacy and not supported in
fglrx anymore (which is not the case), then the main problem is that
neither radeonhd, nor radeon, nor plain vesa seem to work right now.
THIS is my problem.
Still being very grateful for hints.
Greetings,
Stefan
--
Stefa
ect is, that for fglrx there seems to be some ABI
> incompatibility such that X does not start (ABI 2.0 of fglrx vs. ABI
> 5.0 of Xorg) and when falling back to other drivers like radeon,
> radeonhd or even vesa, then the display goes black as soon as X starts
> and nothing happens anym
ABI 2.0 of fglrx vs. ABI
5.0 of Xorg) and when falling back to other drivers like radeon,
radeonhd or even vesa, then the display goes black as soon as X starts
and nothing happens anymore, switching back to the console is not
possible, and the machine can only be operated via remote login.
The inst
Hi,
it seems I have solved the following problem, or at least I have found
a workaround.
> I use Debian for a few years now (since Sarge was Testing), the
> Testing distribution, regularly dist-upgrading it. I have an ATI
> Radeon X1300 graphics card, hence "vesa" driver
Ólafur Jens Sigurðsson ha scritto:
Have you tried the radeonhd driver?
I'll try it this evening, thanks for the hint.
But, in any case, isn't it strange that just running a kernel newer than
2.6.18 makes *vesa* stop working?
Bye,
Salvo
--
--
To UNSUBSCRIBE, email to [EMAIL
Il Friday 18 July 2008 15:30:04 Salvo Isaja ha scritto:
> Ólafur Jens Sigurðsson ha scritto:
> > Have you tried the radeonhd driver?
>
> I'll try it this evening, thanks for the hint.
I've just tried the radeonhd driver, and I experience a problem
similar to the ves
Ólafur Jens Sigurðsson ha scritto:
Have you tried the radeonhd driver?
I'll try it this evening, thanks for the hint.
But, in any case, isn't it strange that just running a kernel newer than
2.6.18 makes vesa (that I used to believe the safest) stop working?
Bye,
Salvo
On Thu, Jul 17, 2008 at 03:20:50PM +0200, Salvo Isaja wrote:
> Hi there,
> I use Debian for a few years now (since Sarge was Testing), the Testing
> distribution, regularly dist-upgrading it. I have an ATI Radeon X1300
> graphics card, hence "vesa" driver in Xorg (&q
ard, hence "vesa" driver in Xorg ("ati" and "radeon" don't
seem to work, will look into the proprietary ATI driver in the near
future). FWIW, I have an AMD Sempron PC, 512 MiB RAM, 1152x864x24bpp
screen mode.
All worked just fine on this box until a kernel upd
On Thu, Apr 17, 2008 at 08:17:32AM +0200, Joey Schulze wrote:
> Luis Ariel Lecca wrote:
> >On 04/16/08 11:15, Joey Schulze wrote:
> >> I'm seeking information on modern graphic cards (PCI, PCIe) that
> >> support VESA BIOS mode 0x010C, a s
Luis Ariel Lecca wrote:
>On 04/16/08 11:15, Joey Schulze wrote:
>> I'm seeking information on modern graphic cards (PCI, PCIe) that
> > support VESA BIOS mode 0x010C, a special text mode that works with
>> 132x60 characters. Linux supports this mo
Ron Johnson wrote:
> > I'm seeking information on modern graphic cards (PCI, PCIe) that
> > support VESA BIOS mode 0x010C, a special text mode that works with
> > 132x60 characters. Linux supports this mode when the graphics board
> > provides this particular mode
On 04/16/08 11:15, Joey Schulze wrote:
> I'm seeking information on modern graphic cards (PCI, PCIe) that
> support VESA BIOS mode 0x010C, a special text mode that works with
> 132x60 characters. Linux supports this mode when the graphics board
> provides this particular mode.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/16/08 11:15, Joey Schulze wrote:
> Hi,
>
> I'm seeking information on modern graphic cards (PCI, PCIe) that
> support VESA BIOS mode 0x010C, a special text mode that works with
> 132x60 characters. Linux supports this mo
Hi,
I'm seeking information on modern graphic cards (PCI, PCIe) that
support VESA BIOS mode 0x010C, a special text mode that works with
132x60 characters. Linux supports this mode when the graphics board
provides this particular mode.
Unfortunately, not many of current video cards support
; On Fri, Jan 11, 2008 at 10:21:56AM +0100, Kum Gabor wrote:
> > > > > Can somebody help me how to set up 1280x800 on Etch with vesa driver?
> > > > > For me only 1280x720 is working. (video is SiS672)
> > > >
> > > > That may not be possible
somebody help me how to set up 1280x800 on Etch with vesa driver?
> > > > For me only 1280x720 is working. (video is SiS672)
> > >
> > > That may not be possible for the vesa driver (see the vesa(4) man page)
> > > as it only accesses the basic vesa-compli
On Sat, Jan 12, 2008 at 10:50:01AM +0100, Kum Gabor wrote:
> On Saturday 12 January 2008 00:59, Douglas A. Tutty wrote:
> > On Fri, Jan 11, 2008 at 10:21:56AM +0100, Kum Gabor wrote:
> > > Can somebody help me how to set up 1280x800 on Etch with vesa driver?
> > > For
On Saturday 12 January 2008 00:59, Douglas A. Tutty wrote:
> On Fri, Jan 11, 2008 at 10:21:56AM +0100, Kum Gabor wrote:
> > Can somebody help me how to set up 1280x800 on Etch with vesa driver?
> > For me only 1280x720 is working. (video is SiS672)
>
> That may not be possibl
On Fri, Jan 11, 2008 at 10:21:56AM +0100, Kum Gabor wrote:
> Can somebody help me how to set up 1280x800 on Etch with vesa driver?
> For me only 1280x720 is working. (video is SiS672)
>
That may not be possible for the vesa driver (see the vesa(4) man page)
as it only accesses the b
Hello!
Can somebody help me how to set up 1280x800 on Etch with vesa driver?
For me only 1280x720 is working. (video is SiS672)
regards,
--
Kum Gabor
www.kumgabor.hu
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, 24 Aug 2007 00:33:46 +0200, Nigel Henry wrote:
> xset -dpms
>
> This appears to work ok, and my monitor stays on all the time.
Thanks for the respond, Nigel. But unfortunately what I want is how to get
dpms working, not to disable it.
--
Tong (remove underscore(s) to reply)
http://x
roblem is that none of the dpms setting is working:
>
> xset dpms force standby
> xset dpms force suspend
> xset dpms force off
>
> None of the above command has any effect. I'm using the vesa driver. Is
> this a known issue?
>
> thanks
Hi Tong. I used to find that
module,
>
> "extmod"# some commonly used server extensions (e.g. shape extension)
>
> I'm able to use 'xset dpms force off' again.
But the problem is that none of the dpms setting is working:
xset dpms force standby
xset dpms force suspend
xset dpms
vga=791, 792, and 793 worked on the CRT but
> no 1280x1024 modes work on the LCD.
>
It seems that xorg VESA driver can't do it here.
from the /var/log/Xorg.0.log
(II) VESA(0): Total Memory: 64 64KB banks (4096kB)
(II) VESA(0): Samsung 204BW: Using hsync range of 30.00-81.00 k
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 sli
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 (
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 :))
> I'
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)
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
t; kernel & atyfb/mach64.
...
> I suspect that debian kernels are compiled w/o native driver support
> because the sum total of all the specific drivers ends up support only a
> subset of the hundreds or video cards & chipsets available .. and since
> once they're present they wou
r built-in or as a module.
>
> Sorry, I thought you were telling him he needs to recompile the kernel.
> I missed the "may".
I suspect that debian kernels are compiled w/o native driver support
because the sum total of all the specific drivers ends up support only a
subset of
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 worke
t I was saying is that support for his card may have been included in
whatever kernel he's using .. either built-in or as a module.
The other aspect is that initrd or not .. I have never managed to get
the frame buffer console to start when using atyfb instead of the
generic vesa when compilin
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 i
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 compil
8: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) unfortun
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 we
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
8: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) unfortun
6: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
6: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
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?
>
>
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.ne
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.ne
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 n
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
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
1 - 100 of 146 matches
Mail list logo
