vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I can't seem to get direct rendering working. Here is my system info: Linux 2.6.17.1 Debian 3.1r2. XFree86 4.3.0.1 Relevant PCI info: 0000:01:00.0 VGA compatible controller: VIA Technologies, Inc.: Unknown device 3108 (rev 01) (prog-if 00 [VGA]) Subsystem: Elitegroup Computer Systems: Unknown device 1828 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10 Memory at e8000000 (32-bit, prefetchable) [size=64M] Memory at ec000000 (32-bit, non-prefetchable) [size=16M] Expansion ROM at <unassigned> [disabled] [size=64K] Capabilities: <available only to root> The file pci.ids says that device 3108 is an S3 Unichrome Pro VGA Adapter. I think the 'via' module supports this. This is what I did to try to get DRM working on my system: ** modprobe via ** Edit /etc/X11/XF86Config-4 and change this: > Section "Device" > Identifier "Generic Video Card" > Driver "vesa" > EndSection to this: > Section "Device" > Identifier "Generic Video Card" > Driver "via" > EndSection When I did the "modprobe via," dmesg said this: > [drm] Initialized drm 1.0.1 20051102 > ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 > [drm] Initialized via 2.7.4 20051116 on minor 0 And lsmod shows that drm and via are loaded. But when I try to start X, it aborts with the message "(EE) no devices detected." How do I get my hardware to do DRI? |
| |||
| On Fri, 23 Jun 2006 04:26:49 GMT, Mumia W. wrote: >> Section "Device" >> Identifier "Generic Video Card" >> Driver "via" >> EndSection >> [drm] Initialized drm 1.0.1 20051102 >> ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 >> [drm] Initialized via 2.7.4 20051116 on minor 0 > > But when I try to start X, it aborts with the message "(EE) no devices > detected." > How do I get my hardware to do DRI? have you got Load "dri" in the Section "Module" of your xorg.conf/XF86whatever.conf? gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `- NP: Chris Rea: Red |
| |||
| gregor herrmann wrote: > On Fri, 23 Jun 2006 04:26:49 GMT, Mumia W. wrote: > >>> Section "Device" >>> Identifier "Generic Video Card" >>> Driver "via" >>> EndSection > >>> [drm] Initialized drm 1.0.1 20051102 >>> ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 >>> [drm] Initialized via 2.7.4 20051116 on minor 0 >> But when I try to start X, it aborts with the message "(EE) no devices >> detected." >> How do I get my hardware to do DRI? > > have you got > Load "dri" > in the Section "Module" of your xorg.conf/XF86whatever.conf? > > > gregor yes |
| |||
| Mumia W. skrev: > I can't seem to get direct rendering working. Here is my system info: > > Linux 2.6.17.1 > Debian 3.1r2. > XFree86 4.3.0.1 > Relevant PCI info: > 0000:01:00.0 VGA compatible controller: VIA Technologies, Inc.: Unknown > device 3108 (rev 01) (prog-if 00 [VGA]) > Subsystem: Elitegroup Computer Systems: Unknown device 1828 > Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10 > Memory at e8000000 (32-bit, prefetchable) [size=64M] > Memory at ec000000 (32-bit, non-prefetchable) [size=16M] > Expansion ROM at <unassigned> [disabled] [size=64K] > Capabilities: <available only to root> > > The file pci.ids says that device 3108 is an S3 Unichrome Pro VGA > Adapter. I think the 'via' module supports this. > > This is what I did to try to get DRM working on my system: > > ** modprobe via > ** Edit /etc/X11/XF86Config-4 and change this: > >> Section "Device" >> Identifier "Generic Video Card" >> Driver "vesa" >> EndSection > to this: >> Section "Device" >> Identifier "Generic Video Card" >> Driver "via" >> EndSection > > When I did the "modprobe via," dmesg said this: >> [drm] Initialized drm 1.0.1 20051102 >> ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 10 (level, >> low) -> IRQ 10 >> [drm] Initialized via 2.7.4 20051116 on minor 0 > > And lsmod shows that drm and via are loaded. > > But when I try to start X, it aborts with the message "(EE) no devices > detected." > > How do I get my hardware to do DRI? > I also have a VIA S3 Unichrome Pro VGA Adapter at my notebook, and I had a lot of problems configuring it some time ago. But then X.org 6.9.0 was released... And I have just been using the default via-driver since then. So my advise is to install a backported version of X.org 6.9.0, which should be available by adding the following lines to your sources.list: ----- deb http://www.debian-desktop.org/pub/li...org-6.8.99.15/ sarge main deb-src http://www.debian-desktop.org/pub/li...org-6.8.99.15/ sarge main ----- -- Best regards Jacob Tranholm <http://jtranholm.dk/> Favourite quote: "Observation statements and statements of experimental results are always interpretations of the facts observed." [Karl R. Popper] |
| |||
| Jacob Tranholm wrote: > Mumia W. skrev: >> I can't seem to get direct rendering working. >> [...] > > I also have a VIA S3 Unichrome Pro VGA Adapter at my notebook, and I had > a lot of problems configuring it some time ago. But then X.org 6.9.0 was > released... And I have just been using the default via-driver since > then. So my advise is to install a backported version of X.org 6.9.0, > which should be available by adding the following lines to your > sources.list: > > ----- > deb http://www.debian-desktop.org/pub/li...org-6.8.99.15/ sarge > main > deb-src http://www.debian-desktop.org/pub/li...org-6.8.99.15/ > sarge main > ----- > Thanks Jacob. Will xorg replace my entire xfree86? |
| |||
| Mumia W. skrev: > > Thanks Jacob. > > Will xorg replace my entire xfree86? I must admit, it has been quite a while since my last update from xfree86 to xorg. But as I remember you can add the sources to you 'sources.list', make an 'apt-get update' and an 'apt-get dist-upgrade', and then your xfree86 is replaced by xorg. -- Best regards Jacob Tranholm <http://jtranholm.dk/> Favourite quote: "Observation statements and statements of experimental results are always interpretations of the facts observed." [Karl R. Popper] |
| |||
| Jacob Tranholm wrote: > Mumia W. skrev: >> Thanks Jacob. >> >> Will xorg replace my entire xfree86? > > I must admit, it has been quite a while since my last update from > xfree86 to xorg. But as I remember you can add the sources to you > 'sources.list', make an 'apt-get update' and an 'apt-get dist-upgrade', > and then your xfree86 is replaced by xorg. > Thanks, I'll think about doing that. |
| |||
| Mumia W. wrote: > I can't seem to get direct rendering working. Here is my system info: > > Linux 2.6.17.1 > Debian 3.1r2. > XFree86 4.3.0.1 > Relevant PCI info: > 0000:01:00.0 VGA compatible controller: VIA Technologies, Inc.: Unknown > device 3108 (rev 01) (prog-if 00 [VGA]) > Subsystem: Elitegroup Computer Systems: Unknown device 1828 > Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10 > Memory at e8000000 (32-bit, prefetchable) [size=64M] > Memory at ec000000 (32-bit, non-prefetchable) [size=16M] > Expansion ROM at <unassigned> [disabled] [size=64K] > Capabilities: <available only to root> > > The file pci.ids says that device 3108 is an S3 Unichrome Pro VGA > Adapter. I think the 'via' module supports this. hmm..I'm using ~$ uname -a Linux sarge 2.6.8-2-386 #1 Tue Aug 16 12:46:35 UTC 2005 i686 GNU/Linux Debian 3.1r1 - and while you certainly have a newer kernel than I . I'm using 4.3.0.1 too; ~$ X -version XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-14sarge1 20050901212727 fjp@localhost.localdomain) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.8-16.0508-2 i686 [ELF] Build Date: 02 September 2005 [...] Funny this; in my /usr/share/misc/pci.ids ...and I use "Find" function, there's no mention of *3108* being there; This is what I have in that file; =========================================== [...] # S3 Graphics UniChrome 2D/3D Graphics with motion compensation 7205 VT8378 [S3 UniChrome] Integrated Video 1458 d000 GA-7VM400M Motherboard 8231 VT8231 [PCI-to-ISA Bridge] 8235 VT8235 ACPI 8305 VT8363/8365 [KT133/KM133 AGP] 8391 VT8371 [KX133 AGP] 8501 VT8501 [Apollo MVP4 AGP] 8596 VT82C596 [Apollo PRO AGP] 8597 VT82C597 [Apollo VP3 AGP] 8598 VT82C598/694x [Apollo MVP3/Pro133x AGP] 1019 0985 P6VXA Motherboard 8601 VT8601 [Apollo ProMedia AGP] 8605 VT8605 [PM133 AGP] 8691 VT82C691 [Apollo Pro] 8693 VT82C693 [Apollo Pro Plus] PCI Bridge b091 VT8633 [Apollo Pro266 AGP] b099 VT8366/A/7 [Apollo KT266/A/333 AGP] b101 VT8653 AGP Bridge b102 VT8362 AGP Bridge b103 VT8615 AGP Bridge b112 VT8361 [KLE133] AGP Bridge b168 VT8235 PCI Bridge b188 VT8237 PCI bridge [K8T800 South] b198 VT8237 PCI Bridge [...] ===================================== Also; Notice how your "lspci -v" output says "unknown device 1308" and there's not even any 1828 listing in my pci.ids file for anything - but perhaps my file is older ? and besides it shouldn't matter much for this discussion, but keep these things in mind. For ex; My 'sudo lspci -vv' yields a funky reading for my Nvidia AGP tnt2 card; 0000:01:00.0 VGA compatible controller: nVidia Corporation NV5 [RIVA TNT2/TNT2 Pro] (rev 11) (prog-if 00 [VGA]) Subsystem: Ensoniq: Unknown device 0003 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 (1250ns min, 250ns max) Interrupt: pin A routed to IRQ 11 Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at fc000000 (32-bit, prefetchable) [size=32M] Capabilities: [60] Power Management version 1 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [44] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none> Note the; Subsystem: Ensoniq: Unknown device 0003 Ensoniq is my Chipset onboard SoundBlaster -- go figure --anyways, supposedly nVidia's don't do/use DRI, or DRM (atleast the older one like I have)...I recall reading that in an article about configuring X, and /etc/X11/XF86Config-4 Here's some output of that file; ====================== [...] Section "Device" Identifier "NVIDIA Corporation NV5 [RIVA TNT2/TNT2 Pro]" Driver "nv" VideoRam 32000 EndSection Section "Monitor" Identifier "LCD1735NXM" HorizSync 31-81 VertRefresh 56-75 Option "DPMS" EndSection [...] ====================== I left the Monitor stuff in there, just in case you need to reconfigure....which brings me to; You should be able to run this; 'sudo dpkg-reconfigure -plow xserver-xfreee86' to completely reconfigure the setup (Video, Monitor, Mouse, Keyboard, etc - all XF86Config-4 entries) -- the '-plow' (Priority Low) option means to ask/present you with the smallest detailed questions possible -- just leave it off (exclude it), if you don't want it that intricate. But in ther you should be able to add/subtract 'dri' and 'drm' support if you desire it. > This is what I did to try to get DRM working on my system: > > ** modprobe via > ** Edit /etc/X11/XF86Config-4 and change this: > > > Section "Device" > > Identifier "Generic Video Card" > > Driver "vesa" > > EndSection > to this: > > Section "Device" > > Identifier "Generic Video Card" > > Driver "via" > > EndSection > > When I did the "modprobe via," dmesg said this: > > [drm] Initialized drm 1.0.1 20051102 > > ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 > > [drm] Initialized via 2.7.4 20051116 on minor 0 Is this an AGP card? -- or likely this is an Onboard Chipset? Do you have AGP support -- now mine is Intel's, but yours would be the VIA equivalent; ~$ lsmod | grep -i agp intel_agp 20512 1 agpgart 31784 1 intel_agp > And lsmod shows that drm and via are loaded. > > But when I try to start X, it aborts with the message "(EE) no devices > detected." > > How do I get my hardware to do DRI? We're trying ;-) Regards |
| |||
| Mumia W. wrote: > I can't seem to get direct rendering working. Here is my system info: > > Linux 2.6.17.1 > Debian 3.1r2. > XFree86 4.3.0.1 > Relevant PCI info: > 0000:01:00.0 VGA compatible controller: VIA Technologies, Inc.: Unknown > device 3108 (rev 01) (prog-if 00 [VGA]) > Subsystem: Elitegroup Computer Systems: Unknown device 1828 > Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10 > Memory at e8000000 (32-bit, prefetchable) [size=64M] > Memory at ec000000 (32-bit, non-prefetchable) [size=16M] > Expansion ROM at <unassigned> [disabled] [size=64K] > Capabilities: <available only to root> > > The file pci.ids says that device 3108 is an S3 Unichrome Pro VGA > Adapter. I think the 'via' module supports this. hmm..I'm using ~$ uname -a Linux sarge 2.6.8-2-386 #1 Tue Aug 16 12:46:35 UTC 2005 i686 GNU/Linux Debian 3.1r1 - and while you certainly have a newer kernel than I . I'm using 4.3.0.1 too; ~$ X -version XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-14sarge1 20050901212727 fjp@localhost.localdomain) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.8-16.0508-2 i686 [ELF] Build Date: 02 September 2005 [...] Funny this; in my /usr/share/misc/pci.ids ...and I use "Find" function, there's no mention of *3108* being there; This is what I have in that file; =========================================== [...] # S3 Graphics UniChrome 2D/3D Graphics with motion compensation 7205 VT8378 [S3 UniChrome] Integrated Video 1458 d000 GA-7VM400M Motherboard 8231 VT8231 [PCI-to-ISA Bridge] 8235 VT8235 ACPI 8305 VT8363/8365 [KT133/KM133 AGP] 8391 VT8371 [KX133 AGP] 8501 VT8501 [Apollo MVP4 AGP] 8596 VT82C596 [Apollo PRO AGP] 8597 VT82C597 [Apollo VP3 AGP] 8598 VT82C598/694x [Apollo MVP3/Pro133x AGP] 1019 0985 P6VXA Motherboard 8601 VT8601 [Apollo ProMedia AGP] 8605 VT8605 [PM133 AGP] 8691 VT82C691 [Apollo Pro] 8693 VT82C693 [Apollo Pro Plus] PCI Bridge b091 VT8633 [Apollo Pro266 AGP] b099 VT8366/A/7 [Apollo KT266/A/333 AGP] b101 VT8653 AGP Bridge b102 VT8362 AGP Bridge b103 VT8615 AGP Bridge b112 VT8361 [KLE133] AGP Bridge b168 VT8235 PCI Bridge b188 VT8237 PCI bridge [K8T800 South] b198 VT8237 PCI Bridge [...] ===================================== Also; Notice how your "lspci -v" output says "unknown device 1308" and there's not even any 1828 listing in my pci.ids file for anything - but perhaps my file is older ? and besides it shouldn't matter much for this discussion, but keep these things in mind. For ex; My 'sudo lspci -vv' yields a funky reading for my Nvidia AGP tnt2 card; 0000:01:00.0 VGA compatible controller: nVidia Corporation NV5 [RIVA TNT2/TNT2 Pro] (rev 11) (prog-if 00 [VGA]) Subsystem: Ensoniq: Unknown device 0003 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 (1250ns min, 250ns max) Interrupt: pin A routed to IRQ 11 Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at fc000000 (32-bit, prefetchable) [size=32M] Capabilities: [60] Power Management version 1 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [44] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none> Note the; Subsystem: Ensoniq: Unknown device 0003 Ensoniq is my Chipset onboard SoundBlaster -- go figure --anyways, supposedly nVidia's don't do/use DRI, or DRM (atleast the older one like I have)...I recall reading that in an article about configuring X, and /etc/X11/XF86Config-4 Here's some output of that file; ====================== [...] Section "Device" Identifier "NVIDIA Corporation NV5 [RIVA TNT2/TNT2 Pro]" Driver "nv" VideoRam 32000 EndSection Section "Monitor" Identifier "LCD1735NXM" HorizSync 31-81 VertRefresh 56-75 Option "DPMS" EndSection [...] ====================== I left the Monitor stuff in there, just in case you need to reconfigure....which brings me to; You should be able to run this; 'sudo dpkg-reconfigure -plow xserver-xfreee86' to completely reconfigure the setup (Video, Monitor, Mouse, Keyboard, etc - all XF86Config-4 entries) -- the '-plow' (Priority Low) option means to ask/present you with the smallest detailed questions possible -- just leave it off (exclude it), if you don't want it that intricate. But in ther you should be able to add/subtract 'dri' and 'drm' support if you desire it. > This is what I did to try to get DRM working on my system: > > ** modprobe via > ** Edit /etc/X11/XF86Config-4 and change this: > > > Section "Device" > > Identifier "Generic Video Card" > > Driver "vesa" > > EndSection > to this: > > Section "Device" > > Identifier "Generic Video Card" > > Driver "via" > > EndSection > > When I did the "modprobe via," dmesg said this: > > [drm] Initialized drm 1.0.1 20051102 > > ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 > > [drm] Initialized via 2.7.4 20051116 on minor 0 Is this an AGP card? -- or likely this is an Onboard Chipset? Do you have AGP support -- now mine is Intel's, but yours would be the VIA equivalent; ~$ lsmod | grep -i agp intel_agp 20512 1 agpgart 31784 1 intel_agp > And lsmod shows that drm and via are loaded. > > But when I try to start X, it aborts with the message "(EE) no devices > detected." > > How do I get my hardware to do DRI? We're trying ;-) Regards |
| ||||
| Mumia W. wrote: > Jacob Tranholm wrote: > > Mumia W. skrev: > >> Thanks Jacob. > >> > >> Will xorg replace my entire xfree86? > > > > I must admit, it has been quite a while since my last update from > > xfree86 to xorg. But as I remember you can add the sources to you > > 'sources.list', make an 'apt-get update' and an 'apt-get dist-upgrade', > > and then your xfree86 is replaced by xorg. > > > > Thanks, I'll think about doing that. If you do actually do that you'll be doing a complete dist-upgrade to "Testing" (...or even the lesser "upgrade" posted by Jacob Tranholm earlier, will likely upgrade 'X' only, and it's components, but may break a few things too) -- Either way, see this; <http://wiki.debian.org/Xorg69To7> Regards |