Re: Display Problems




"imotgm" <imotgm_REM@xxxxxxxxxxxxxxxxx> wrote in message
news:pan.2005.12.07.07.58.48.726565@xxxxxxxxxxxxxxxxxxxx
> On Wed, 07 Dec 2005 05:44:58 +0000, Ash wrote:
>
>
>>
>> yes i have (after much frustration).
>> now im having trouble with the configuration utilities. the 2 that have
>> been
>> recommended to me dont seem to be working.
>
> At the prompt:
>
> # xorgconfig <Enter>
>
> should give the following;
>
> ========================================================
>
> This program will create a basic xorg.conf file, based on menu selections
> you
> make.
>
> The xorg.conf file usually resides in /usr/X11R6/etc/X11 or /etc/X11. A
> sample
> xorg.conf file is supplied with Xorg; it is configured for a standard
> VGA card and monitor with 640x480 resolution. This program will ask for a
> pathname when it is ready to write the file.
>
> You can either take the sample xorg.conf as a base and edit it for your
> configuration, or let this program produce a base xorg.conf file for your
> configuration and fine-tune it.
>
> Before continuing with this program, make sure you know what video card
> you have, and preferably also the chipset it uses and the amount of video
> memory on your video card. SuperProbe may be able to help with this.
>
> Press enter to continue, or ctrl-c to abort.
>
> ======================================================
>
> If you get that, press enter and follow the instructions. If you don't get
> that, there's a problem with the program.
>
> I have an nVidia GEforce 6600 also, and so far the nVidia drivers have not
> worked. YMMV, but to get you something usable for now, If the above does
> not work, open /etc/X11/xorg.conf in an editor, go to the Section "Device"
> which should look something like this:
>
> Section "Device"
> Identifier "device1"
> VendorName "Nvidia"
> BoardName "GEforce 6600"
> Driver "vesa"
> Option "DPMS"
> EndSection
>
> and change whatever entry you have for Driver to "vesa", as above. This
> works for me on SUSE, Mandrake, and Slackware. It will not give you 3D
> acceleration, but should give you a decent 2D screen. From that point, you
> should be able to set-up and use your internet connection to get the
> latest nVidia driver, from
>
> http://www.nvidia.com/object/unix.html
>
> to try. If it doesn't work, reset the "vesa" driver, and wait for the next
> nVidea driver release.
>
> --
> imotgm
> "Lost? Lost? I've never been lost... Been a tad confused for a
> month or two, but never lost."
>
>

thanks for the reply. with this post and others i should be able to get up
and running. ill get those new drivers too.
ive run out of energy for today so ill have a stab at it tomorrow!
thanks again.


.



Relevant Pages

  • Re: Display Problems
    ... > now im having trouble with the configuration utilities. ... I have an nVidia GEforce 6600 also, and so far the nVidia drivers have not ... and change whatever entry you have for Driver to "vesa", ... "Lost? ...
    (alt.os.linux.suse)
  • Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64
    ... If the system fails in ACPI mode, but works in non-ACPI mode, ... Using ACPI for SMP configuration information ... Using IOAPIC for interrupt routing ... Non-volatile memory driver v1.2 ...
    (Linux-Kernel)
  • Re: Problem with 8250_pnp Module and using ttyS0 as console
    ... PCI: Using configuration type 1 ... 15 nodes reported by PnP BIOS; 15 recorded by driver ... registered new interface driver hub ... USB Universal Host Controller Interface driver v3.0 ...
    (Linux-Kernel)
  • Re: Second SATA disk is not recognized in kernel 2.6.x
    ... same configuration in 2.6.9. ... number of MP IRQ sources: ... Serial driver version 5.05c with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ... usb.c: new USB bus registered, ...
    (Linux-Kernel)
  • Re: 2.6.21-rc4-mm1 and rc5-mm2 - problem with cpuidle routine
    ... No output about not being able to attach, just the driver string and then nothing. ... configuration file and part of /var/log/boot.msg for my working system. ... ACPI: Processor ... cpuidle: driver acpi_idle failed to attach to cpu 0 ...
    (Linux-Kernel)