On 4/16/09, Manish Jain <invalid.poin...@gmail.com> wrote:
> I am not sure what the norms are in this forum w.r.t. top-posting. My
> reply is at the bottom.
>
>
> Paul B. Mahol wrote:
>> On 4/14/09, Manish Jain <invalid.poin...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I am running xorg-server 1.4.2 on FreeBSD 7.1 (Release) on a Celeron
>>> Coppermine 800 MHz + Intel 810 chipset-based system. The xorg
>>> documentation states that enabling DRI on this chipset just requires the
>>> colour depth to be set to either 8 or 16 bpp. My xorg.conf uses just one
>>> screen with the depth set to 16. I am loading the agp module at
>>> boot-time via loader.conf. But xorg still disables DRI.
>>>
>>> Following are some relevant lines from xorg's log :
>>>
>>>> X.Org X Server 1.4.2
>>>> Release Date: 11 June 2008
>>>> (**) intel(0): page flipping disabled
>>>> (II) intel(0): XvMC is Disabled: use XvMCSurfaces config option to
>>>> enable.
>>>> drmOpenDevice: node name is /dev/dri/card0
>>>> drmOpenDevice: open result is -1, (No such file or directory)
>>>> drmOpenDevice: open result is -1, (No such file or directory)
>>>> drmOpenDevice: Open failed
>>>> drmOpenDevice: node name is /dev/dri/card0
>>>> drmOpenDevice: open result is -1, (No such file or directory)
>>>> drmOpenDevice: open result is -1, (No such file or directory)
>>>> drmOpenDevice: Open failed
>>>> [drm] failed to load kernel module "i810"
>>>>
>>
>> is i915.ko loaded?
>>
>>
>>>> (EE) [drm] drmOpen failed.
>>>> (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
>>>> (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x00000000 (pgoffset 0)
>>>> (WW) intel(0): xf86AllocateGARTMemory: allocation of 1024 pages failed
>>>> (Cannot allocate memory)
>>>>
>>> Please note there is no directory named /dev/dri on my devfs-enabled
>>> system.
>>>
>>> Here is my /etc/X11/xorg.conf :
>>>
>>>> Section "Module"
>>>> Load "dri"
>>>> Load "glx"
>>>> Load "extmod"
>>>> Load "dbe"
>>>> Load "freetype"
>>>>
>>>> SubSection "extmod"
>>>> Option "omit xfree86-dga"
>>>> EndSubSection
>>>> EndSection
>>>>
>>>> Section "Files"
>>>> RgbPath "/usr/local/lib/X11/rgb"
>>>>
>>>> FontPath "/usr/local/lib/X11/fonts/misc/"
>>>> FontPath "/usr/local/lib/X11/fonts/TTF/"
>>>> FontPath "/usr/local/lib/X11/fonts/OTF"
>>>> FontPath "/usr/local/lib/X11/fonts/Type1/"
>>>> FontPath "/usr/local/lib/X11/fonts/100dpi/"
>>>> FontPath "/usr/local/lib/X11/fonts/75dpi/"
>>>> FontPath "/usr/local/lib/X11/fonts/bitstream-vera/"
>>>> FontPath "/usr/local/lib/X11/fonts/cyrillic/"
>>>> FontPath "/usr/local/lib/X11/fonts/util/"
>>>> FontPath "/usr/local/share/fonts/cmpsfont/type1"
>>>>
>>>> ModulePath "/usr/local/lib/xorg/modules"
>>>> EndSection
>>>>
>>>> Section "ServerFlags"
>>>> Option "AllowEmptyInput" "off"
>>>> EndSection
>>>>
>>>> Section "InputDevice"
>>>> Identifier "Keyboard_US_ISO_105"
>>>> Driver "kbd"
>>>> Option "AutoRepeat" "500 30"
>>>> Option "XkbRules" "xorg"
>>>> Option "XkbModel" "pc105"
>>>> Option "XkbLayout" "us"
>>>> EndSection
>>>>
>>>> Section "InputDevice"
>>>> Identifier "Mouse_Logitech_USB_Optical"
>>>> Driver "mouse"
>>>> Option "Protocol" "Auto"
>>>> Option "Device" "/dev/sysmouse"
>>>> Option "ZAxisMapping" "4 5 6 7"
>>>> EndSection
>>>>
>>>> Section "Monitor"
>>>> Identifier "Philips105St"
>>>> HorizSync 31.5 - 48.5
>>>> VertRefresh 50-90
>>>> EndSection
>>>>
>>>> Section "Device"
>>>> Identifier "i810_Tomato"
>>>> Driver "i810"
>>>> VideoRam 4096
>>>> EndSection
>>>>
>>>> Section "Screen"
>>>> Identifier "Screen_Only"
>>>> Device "i810_Tomato"
>>>> Monitor "Philips105St"
>>>> DefaultDepth 16
>>>>
>>>> Subsection "Display"
>>>> Depth 16
>>>> Modes "1024x768"
>>>> ViewPort 0 0
>>>> EndSubsection
>>>> EndSection
>>>>
>>>> Section "ServerLayout"
>>>> Identifier "Layout_Xorg732"
>>>> Screen "Screen_Only"
>>>> InputDevice "Mouse_Logitech_USB_Optical" "CorePointer"
>>>> InputDevice "Keyboard_US_ISO_105" "CoreKeyboard"
>>>> EndSection
>>>>
>>>> Section "DRI"
>>>> Mode 0666
>>>> EndSection
>>>>
>>> And here is my /boot/loader.conf :
>>>
>>>> agp_load="YES"
>>>> drm_load="YES"
>>>> snd_ich_load="YES"
>>>> linux_load="YES"
>>>> linprocfs_load="YES"
>>>> hint.acpi.0.disabled=0
>>>> hw.acpi.verbose=1
>>>>
>>> Can somebody tell me what the problem is and how do I get to enable DRI
>>> on my system ? Any help would be greatly appreciated.
>>>
>>> --
>>> Thank you and Regards
>>> Manish Jain
>>> invalid.poin...@gmail.com
>>> +91-99830-62246
>>>
>>> NB : Laast year I kudn't spell Software Engineer. Now I are won.
>>>
>>> _______________________________________________
>>> xorg mailing list
>>> xorg@lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/xorg
>>>
>>>
>>
>>
>>
>
>
> Hello Paul,
>
> Thank you for your reply. I was on the verge of giving up hope.
>
>> is i915.ko loaded?
>>
>
> I had tried loading i915.ko at boot-time (successfully). It makes no
> difference - DRI remains disabled even with i915.ko loaded. This
> behaviour is exactly what the developer has programmed for (despite the
> documentation).
You mean that /dev/dri doesnt appear?
> /usr/src/sys/dev/drm/i915_drv.c says :
>> static drm_pci_id_list_t i915_pciidlist[] = {
>> i915_PCI_IDS
>> };
>
> /usr/src/sys/dev/drm/drm_pciids.h in turn says :
>> #define i915_PCI_IDS \
>> {0x8086, 0x3577, 0, "Intel i830M GMCH"}, \
>> {0x8086, 0x2562, 0, "Intel i845G GMCH"}, \
>> {0x8086, 0x3582, 0, "Intel i852GM/i855GM GMCH"}, \
>> {0x8086, 0x2572, 0, "Intel i865G GMCH"}, \
>> {0x8086, 0x2582, 0, "Intel i915G"}, \
>> {0x8086, 0x2592, 0, "Intel i915GM"}, \
>> {0x8086, 0x2772, 0, "Intel i945G"}, \
>> {0x8086, 0x27A2, 0, "Intel i945GM"}, \
>> {0x8086, 0x2972, 0, "Intel i946GZ"}, \
>> {0x8086, 0x2982, 0, "Intel i965G"}, \
>> {0x8086, 0x2992, 0, "Intel i965Q"}, \
>> {0x8086, 0x29A2, 0, "Intel i965G"}, \
>> {0x8086, 0x2A02, 0, "Intel i965GM"}, \
>> {0x8086, 0x2A12, 0, "Intel i965GME"}, \
>> {0, 0, 0, NULL}
>>
>
> So what is known as the i810 driver leaves out the i810 chipset itself
> and begins DRI support with the i830 chipset instead. The reason I write
> to this forum is that the i810 chipset sold like wildfire and performed
> like one too. I, probably like many others, am now left staring at the
> prospect of giving up on a superb system, apart from more than a month's
> income and countless hours installing and configuring the system, to go
> in for an overhaul when all this would have been unnecessary had the
> i810 chipset DRI support not been taken away from the i810 driver.
>
> I still hope against hope that xorg considers reviving i810 DRI support
> soon enough.
And related lspci, pciconf output for your card is?
--
Paul
_______________________________________________
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
