Re: Problems with Xorg video
Florian,
I made some progress, but I am beginnning to believe that I have put myself in
a world of hurt.
I got past not finding the i810 card by inserting the correct bus address (see
below). But now it complains that I am missing module i915. So, I think I
made a big mistake installing xorg! I should have gone to the dentist for a
root canal (without novacaine) instead of mucking with my computer! ;-)
My version of sarge probably does not support xorg, so I should be using
xfree86. How do I remove all the X stuff and start over again and install
xfree86. I am using kernel 2.6.8-2-386. THanks!
Here is the ouput you requested:
hammerhead:/home/mark# egrep '^\((EE|WW)\)' /var/log/Xorg.0.log
(WW) The directory "/usr/share/fonts/X11/misc" does not exist.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
(WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic" does not exist.
(WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
(WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
(WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
(WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
(WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
(WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not
exist.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Extended BIOS function 0x5f11 not supported.
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): config file hsync range 28-64kHz not within DDC hsync range
31-50kHz
(WW) I810(0): config file vrefresh range 43-70Hz not within DDC vrefresh range
60-70Hz
(WW) (1024x768,Generic Monitor) mode clock 78.8MHz exceeds DDC maximum 70MHz
(WW) (1024x768,Generic Monitor) mode clock 94.5MHz exceeds DDC maximum 70MHz
(WW) (1280x1024,Generic Monitor) mode clock 135MHz exceeds DDC maximum 70MHz
(WW) (1280x1024,Generic Monitor) mode clock 157.5MHz exceeds DDC maximum 70MHz
(WW) (1280x1024,Generic Monitor) mode clock 132.751MHz exceeds DDC maximum
70MHz
(WW) (1280x1024,Generic Monitor) mode clock 128.943MHz exceeds DDC maximum
70MHz
(WW) (1280x1024,Generic Monitor) mode clock 128.943MHz exceeds DDC maximum
70MHz
(WW) (1280x1024,Generic Monitor) mode clock 108.78MHz exceeds DDC maximum
70MHz
(WW) (1280x1024,Generic Monitor) mode clock 108.78MHz exceeds DDC maximum
70MHz
(WW) (1280x1024,Generic Monitor) mode clock 108.78MHz exceeds DDC maximum
70MHz
(WW) (1280x1024,Generic Monitor) mode clock 108.78MHz exceeds DDC maximum
70MHz
(WW) (1280x1024,Generic Monitor) mode clock 108.78MHz exceeds DDC maximum
70MHz
(WW) (1280x1024,Generic Monitor) mode clock 108.78MHz exceeds DDC maximum
70MHz
(WW) (1280x1024,Generic Monitor) mode clock 108.78MHz exceeds DDC maximum
70MHz
(WW) (1280x1024,Generic Monitor) mode clock 108.78MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 175.5MHz exceeds DDC maximum 70MHz
(WW) (1600x1200,Generic Monitor) mode clock 189MHz exceeds DDC maximum 70MHz
(WW) (1600x1200,Generic Monitor) mode clock 202.5MHz exceeds DDC maximum 70MHz
(WW) (1600x1200,Generic Monitor) mode clock 229.5MHz exceeds DDC maximum 70MHz
(WW) (1600x1200,Generic Monitor) mode clock 195.84MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 190.247MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 190.247MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 160.833MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 160.833MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 160.833MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 160.833MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 160.833MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 160.833MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 160.833MHz exceeds DDC maximum
70MHz
(WW) (1600x1200,Generic Monitor) mode clock 160.833MHz exceeds DDC maximum
70MHz
(WW) I810(0): Bad V_BIOS checksum
(EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI.
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(EE) AIGLX: Screen 0 is not DRI capable
(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
(WW) I810(0): Extended BIOS function 0x5f05 failed.
(WW) I810(0): Successfully set original devices (2)
hammerhead:/home/mark#
awk '/Section "Device"/,/EndSection/' /etc/X11/xorg.conf
Section "Device"
Identifier "Generic Video Card"
Driver "i810"
BusID "PCI:0:2:0"
EndSection
hammerhead:/home/mark#
On Monday 07 May 2007 13:29, Florian Kulzer wrote:
> On Mon, May 07, 2007 at 12:29:41 -0700, Mark Phillips wrote:
> > I seem to have lost my video after moving from xfree86 to xorg.
> >
> > The error reported in my xorg log (after many pages of no errors) -
> >
> > (II) I810: Driver for Intel Integrated Graphics Chipsets: i810,
> > i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221
> > (i915), 915GM, 945G, 945GM, 965G, 965G, 965Q, 946GZ
> > (II) Primary Device is: PCI 00:02:0
> > (WW) I810: No matching Device section for instance (BusID PCI:0:2:0)
> > found (EE) No devices detected.
> >
> > Fatal server error:
> > no screens found
> >
> > lspci reports:
>
> [...]
>
> > 0000:00:02.0 VGA compatible controller: Intel Corp.
> > 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
>
> [...]
>
> > So, the graphics card is there.
> >
> > Any suggestions? Could the graphics card be half-dead? It works in text
> > mode when I boot up, but X cannot start. If it works in text mode must it
> > also work in graphics mode? Should I get another graphics card? Any
> > suggestions on a good linux compatible card?
> >
> > I am running debian sarge with kernel 2.6.8-2-386
>
> Is this a backported version of Xorg? Sarge still had XFree86, right?
>
> Also, please post the output of these two commands:
>
> egrep '^\((EE|WW)\)' /var/log/Xorg.0.log
>
> awk '/Section "Device"/,/EndSection/' /etc/X11/xorg.conf
>
> (The first one is just to make sure that you did not miss an error or a
> warning message when you read the log yourself.)
Reply to: