[Dri-devel] Re: Strange lockups with DRI on Radeon 8500LE
Hi Michel! Monday 22, at 09:39:50 PM you wrote: skip Hmm, I suspect this could be related to the new card memory layout introduced with the radeon DRM 1.10.0. Can you try either the DRM or the 2D driver from before November 4th? Hmm where I can found this source/binaries? /snapshots on dri.sf.net contains only mach64 binaries :( There would probably no longer be any snapshots from November anyway; you could try the 2D driver from XFree86 CVS (which shouldn't have the change in question yet), e.g. from http://www.xfree86.org/~alanh/ . bad luck :( those drivers dated 03 december. I know, but they still shouldn't have the change in question. It went into DRI CVS on November 4th, which was after DRI CVS was fully merged into XFree86 CVS last time. No can't do that. If simply use only radeon_drv.o I get many unresolved symbols and x server crashes with sig11. But I can't use XFree86 from this link cause I have glibc-2.2 system. So I try to change kernel... some logs related to unresolved symbols: skip (==) RADEON(0): Write-combining range (0xd000,0x800) (II) RADEON(0): Wrote: rd=12, fd=107, pd=1 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: Searching for BusID PCI:1:0:0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 5, (OK) drmOpenByBusid: drmOpenMinor returns 5 drmOpenByBusid: drmGetBusid reports pci::01:00.0 (II) RADEON(0): [drm] loaded kernel module for radeon driver (II) RADEON(0): [drm] DRM interface version 1.2 (II) RADEON(0): [drm] created radeon driver at busid PCI:1:0:0 (II) RADEON(0): [drm] added 8192 byte SAREA at 0xd0a9d000 (II) RADEON(0): [drm] mapped SAREA 0xd0a9d000 to 0x40012000 (II) RADEON(0): [drm] framebuffer handle = 0xd000 (II) RADEON(0): [drm] added 1 reserved context for kernel (II) RADEON(0): [agp] Mode 0x1f000201 [AGP 0x8086/0x2530; Card 0x1002/0x514c] (II) RADEON(0): [agp] 8192 kB allocated with handle 0x0001 (II) RADEON(0): [agp] ring handle = 0xe000 (II) RADEON(0): [agp] Ring mapped at 0x4824a000 (II) RADEON(0): [agp] ring read ptr handle = 0xe0101000 (II) RADEON(0): [agp] Ring read ptr mapped at 0x40014000 (II) RADEON(0): [agp] vertex/indirect buffers handle = 0xe0102000 (II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x4834b000 (II) RADEON(0): [agp] GART texture map handle = 0xe0302000 (II) RADEON(0): [agp] GART Texture map mapped at 0x4854b000 (II) RADEON(0): [drm] register handle = 0xe500 (II) RADEON(0): [dri] Visual configs initialized (II) RADEON(0): CP in BM mode (II) RADEON(0): Using 8 MB GART aperture (II) RADEON(0): Using 1 MB for the ring buffer (II) RADEON(0): Using 2 MB for vertex/indirect buffers (II) RADEON(0): Using 5 MB for GART textures (II) RADEON(0): Memory manager initialized to (0,0) (1152,8191) (II) RADEON(0): Reserved area from (0,864) to (1152,866) (II) RADEON(0): Largest offscreen area available: 1152 x 7325 (II) RADEON(0): Will use back buffer at offset 0x1068000 (II) RADEON(0): Will use depth buffer at offset 0x1434000 (II) RADEON(0): Will use 106496 kb for textures at offset 0x180 (II) RADEON(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Lines Scanline Image Writes Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 32 256x256 slots 16 512x512 slots (II) RADEON(0): Acceleration enabled (==) RADEON(0): Backing store disabled (==) RADEON(0): Silken mouse enabled (II) RADEON(0): Using hardware cursor (scanline 866) (II) RADEON(0): Largest offscreen area available: 1152 x 7321 (**) Option dpms (**) RADEON(0): DPMS enabled Symbol currentRegionScreen from module /usr/X11R6-DRI/lib/modules/drivers/radeon_drv.o is unresolved! Symbol currentRegionScreen from module /usr/X11R6-DRI/lib/modules/drivers/radeon_drv.o is unresolved! Symbol currentRegionScreen from module /usr/X11R6-DRI/lib/modules/drivers/radeon_drv.o is unresolved! Symbol currentRegionScreen from module /usr/X11R6-DRI/lib/modules/drivers/radeon_drv.o is unresolved! Symbol currentRegionScreen from module /usr/X11R6-DRI/lib/modules/drivers/radeon_drv.o is unresolved! Symbol currentRegionScreen from module /usr/X11R6-DRI/lib/modules/drivers/radeon_drv.o is unresolved! *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting When reporting a problem related to a server crash, please send the full server
[Dri-devel] Re: Strange lockups with DRI on Radeon 8500LE
Hi Michel! Monday 22, at 12:18:11 AM you wrote: On Sun, 2003-12-21 at 20:14, Konstantin Lepikhov wrote: Here is logs from dmesg: skip Linux agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 203M agpgart: Detected Intel i850 chipset agpgart: AGP aperture is 64M @ 0xe000 radeonfb: ref_clk=2700, ref_div=12, xclk=2 from BIOS Console: switching to colour frame buffer device 80x25 radeonfb: ATI Radeon 8500 QL DDR SGRAM 128 MB radeonfb: DVI port no monitor connected radeonfb: CRT port CRT monitor connected Does not loading radeonfb make a difference? (It shouldn't, but...) no it doesn't make sense. Got the same problem. [drm] Initialized radeon 1.10.0 20020828 on minor 0: ATI Radeon QL R200 8500 LE [drm] Loading R200 Microcode Hmm, I suspect this could be related to the new card memory layout introduced with the radeon DRM 1.10.0. Can you try either the DRM or the 2D driver from before November 4th? Hmm where I can found this source/binaries? /snapshots on dri.sf.net contains only mach64 binaries :( -- WBR, Konstantin chat with ==ICQ: 109916175 Lepikhov,speak to ==JID: [EMAIL PROTECTED] aka L.A. Kostis write to ==mailto:[EMAIL PROTECTED] ...The information is like the bank...(c) EC8OR --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Strange lockups with DRI on Radeon 8500LE
On Mon, 2003-12-22 at 08:26, Konstantin Lepikhov wrote: Monday 22, at 12:18:11 AM you wrote: On Sun, 2003-12-21 at 20:14, Konstantin Lepikhov wrote: [drm] Initialized radeon 1.10.0 20020828 on minor 0: ATI Radeon QL R200 8500 LE [drm] Loading R200 Microcode Hmm, I suspect this could be related to the new card memory layout introduced with the radeon DRM 1.10.0. Can you try either the DRM or the 2D driver from before November 4th? Hmm where I can found this source/binaries? /snapshots on dri.sf.net contains only mach64 binaries :( There would probably no longer be any snapshots from November anyway; you could try the 2D driver from XFree86 CVS (which shouldn't have the change in question yet), e.g. from http://www.xfree86.org/~alanh/ . -- Earthling Michel Dnzer | Debian (powerpc), X and DRI developer Software libre enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: Strange lockups with DRI on Radeon 8500LE
Hi Michel! Monday 22, at 01:05:37 PM you wrote: On Mon, 2003-12-22 at 08:26, Konstantin Lepikhov wrote: Monday 22, at 12:18:11 AM you wrote: On Sun, 2003-12-21 at 20:14, Konstantin Lepikhov wrote: [drm] Initialized radeon 1.10.0 20020828 on minor 0: ATI Radeon QL R200 8500 LE [drm] Loading R200 Microcode Hmm, I suspect this could be related to the new card memory layout introduced with the radeon DRM 1.10.0. Can you try either the DRM or the 2D driver from before November 4th? Hmm where I can found this source/binaries? /snapshots on dri.sf.net contains only mach64 binaries :( There would probably no longer be any snapshots from November anyway; you could try the 2D driver from XFree86 CVS (which shouldn't have the change in question yet), e.g. from http://www.xfree86.org/~alanh/ . bad luck :( those drivers dated 03 december. Now I try to play with different kernel versions and report about results. -- WBR, Konstantin chat with ==ICQ: 109916175 Lepikhov,speak to ==JID: [EMAIL PROTECTED] aka L.A. Kostis write to ==mailto:[EMAIL PROTECTED] ...The information is like the bank...(c) EC8OR --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Strange lockups with DRI on Radeon 8500LE
On Mon, 2003-12-22 at 18:58, Konstantin Lepikhov wrote: Monday 22, at 01:05:37 PM you wrote: On Mon, 2003-12-22 at 08:26, Konstantin Lepikhov wrote: Monday 22, at 12:18:11 AM you wrote: On Sun, 2003-12-21 at 20:14, Konstantin Lepikhov wrote: [drm] Initialized radeon 1.10.0 20020828 on minor 0: ATI Radeon QL R200 8500 LE [drm] Loading R200 Microcode Hmm, I suspect this could be related to the new card memory layout introduced with the radeon DRM 1.10.0. Can you try either the DRM or the 2D driver from before November 4th? Hmm where I can found this source/binaries? /snapshots on dri.sf.net contains only mach64 binaries :( There would probably no longer be any snapshots from November anyway; you could try the 2D driver from XFree86 CVS (which shouldn't have the change in question yet), e.g. from http://www.xfree86.org/~alanh/ . bad luck :( those drivers dated 03 december. I know, but they still shouldn't have the change in question. It went into DRI CVS on November 4th, which was after DRI CVS was fully merged into XFree86 CVS last time. -- Earthling Michel Dnzer | Debian (powerpc), X and DRI developer Software libre enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: Strange lockups with DRI on Radeon 8500LE
Hi Michel! Sunday 21, at 03:20:33 PM you wrote: On Sun, 2003-12-21 at 14:55, Konstantin Lepikhov wrote: After upgrading my box to latest trunk DRI, I got strange problem - XServer did not start correctly, e.g. it hangs after init dri stuff. But I can ssh to this box, and SysRq keys are working and I can sync/umount/reboot. If I comment Load dri/remove radeon.o module - all works fine except DRI =) So what it can be? Problems with build/my hands or is a problem with videocard? FYI, fglrx drivers works fine. Have you tried not enabling AGP fast writes? I'm a bit confused by the log and config files you attached: the config says AGP 4x, the log 1x; the config contains Option UseFBDev, but the log shows no trace of the fbdevhw module; and last but not least, the log seems to show a complete and successful startup with DRI enabled? Please clarify. I send different logs/configs sorry about that. In previous XFree86.log.0, I'm use AGPMode 1 and commented UseFBDev 1 and yes, this XFree86.log.0 of hanged XFree86 server, it doesn't init keyboard/mouse and my screen is blank. Now I show XFree86.log.0 and related XF86Config-4 with disabled fast writes. In this case I have the same xserver hangs :( -- WBR, Konstantin chat with ==ICQ: 109916175 Lepikhov,speak to ==JID: [EMAIL PROTECTED] aka L.A. Kostis write to ==mailto:[EMAIL PROTECTED] ...The information is like the bank...(c) EC8OR This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs). XFree86 Version 4.3.99.12 (DRI trunk) Release Date: 10 September 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.22-std-up-alt8 i686 [ELF] Current Operating System: Linux lks.home 2.4.22-std-up-alt8 #1 Mon Nov 10 00:15:21 MSK 2003 i686 Build Date: 18 December 2003 Changelog Date: 10 September 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Sun Dec 21 18:02:17 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Server Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device ATI Radeon (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option AutoRepeat 250 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us,ru (**) XKB: layout: us,ru (**) Option XkbOptions ,grp:caps_toggle,grp_led:scroll (**) XKB: options: ,grp:caps_toggle,grp_led:scroll (==) Keyboard: CustomKeycode disabled (**) FontPath set to tcp/localhost:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6-DRI/lib/modules (**) Option AllowNonLocalXvidtune (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.2 XFree86 Video Driver: 0.7 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6-DRI/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.3.99.12, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6-DRI/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.3.99.12, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000f940, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2530 card 147b,0507 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2532 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1e:0: chip 8086,244e card , rev 04 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2440 card , rev 04 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,244b card 147b,0507 rev 04 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2442 card 147b,0507 rev 04 class 0c,03,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,2443 card 147b,0507 rev 04 class 0c,05,00 hdr 00 (II) PCI: 00:1f:4: chip 8086,2444 card 147b,0507 rev 04 class 0c,03,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2445 card 147b,0507 rev 04 class 04,01,00 hdr 00 (II)
Re: [Dri-devel] Re: Strange lockups with DRI on Radeon 8500LE
On Sun, 2003-12-21 at 16:10, Konstantin Lepikhov wrote: I send different logs/configs sorry about that. In previous XFree86.log.0, I'm use AGPMode 1 and commented UseFBDev 1 and yes, this XFree86.log.0 of hanged XFree86 server, it doesn't init keyboard/mouse and my screen is blank. I assume the monitor can handle [EMAIL PROTECTED] Can you log in remotely and see whether the X server hogs the CPU, and if so, whether killing it helps? Anything interesting in the kernel output? Now I show XFree86.log.0 and related XF86Config-4 with disabled fast writes. In this case I have the same xserver hangs :( Have you tried AGP 1x with fast writes disabled? -- Earthling Michel Dnzer | Debian (powerpc), X and DRI developer Software libre enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: Strange lockups with DRI on Radeon 8500LE
Hi Michel! Sunday 21, at 06:26:27 PM you wrote: On Sun, 2003-12-21 at 16:10, Konstantin Lepikhov wrote: I send different logs/configs sorry about that. In previous XFree86.log.0, I'm use AGPMode 1 and commented UseFBDev 1 and yes, this XFree86.log.0 of hanged XFree86 server, it doesn't init keyboard/mouse and my screen is blank. I assume the monitor can handle [EMAIL PROTECTED] Can you log in remotely and see whether the X server hogs the CPU, and if so, whether killing it helps? Anything interesting in the kernel output? Yes, my monitor can handle this resolution and refresh OK here is logs: # ps -waux | grep X xfs 1736 0.0 1.5 6052 3860 ?S19:14 0:00 /usr/X11R6/bin/xfs -port 7100 -daemon -user xfs lakostis 9026 0.0 0.4 1960 1032 tty3 S21:47 0:00 /bin/sh /usr/X11R6/bin/startx lakostis 9038 0.0 0.2 2116 572 tty3 S21:47 0:00 xinit /home/lakostis/.xinitrc -- /etc/X11/xinit/xserverrc :0 root 9039 98.8 2.9 150916 7556 ? R21:47 18:26 /usr/X11R6/bin/X -nolisten tcp :0 skip # kill -9 `pidof X` ps -waux | grep X xfs 1736 0.0 1.5 6052 3860 ?S19:14 0:00 /usr/X11R6/bin/xfs -port 7100 -daemon -user xfs lakostis 9026 0.0 0.4 1960 1032 tty3 S21:47 0:00 /bin/sh /usr/X11R6/bin/startx lakostis 9038 0.0 0.2 2116 572 tty3 S21:47 0:00 xinit /home/lakostis/.xinitrc -- /etc/X11/xinit/xserverrc :0 root 9039 98.9 2.9 150916 7556 ? R21:47 21:04 /usr/X11R6/bin/X -nolisten tcp :0 skip # kill -15 `pidof X` ps -waux | grep X xfs 1736 0.0 1.5 6052 3860 ?S19:14 0:00 /usr/X11R6/bin/xfs -port 7100 -daemon -user xfs root 9039 99.0 0.0 00 ?RW 21:47 21:46 [X] Yes X server hogs the CPU and don't killed anymore :( # cat /proc/modules radeon114112 1 ip_nat_ftp 3024 0 (unused) ip_nat_irc 2448 0 (unused) ip_conntrack_ftp3856 1 ip_conntrack_irc3152 1 ipt_MASQUERADE 1432 0 (autoclean) iptable_nat17208 2 (autoclean) [ip_nat_ftp ip_nat_irc ipt_MASQUERADE] ipt_REJECT 3352 0 (autoclean) ipt_LOG 3544 0 (autoclean) ipt_limit984 0 (autoclean) ipt_state696 0 (autoclean) iptable_filter 1732 0 (autoclean) ip_conntrack 18216 4 [ip_nat_ftp ip_nat_irc ip_conntrack_ftp ip_conntrack_irc ipt_MASQUERADE iptable_nat ipt_state] ip_tables 12120 9 [ipt_MASQUERADE iptable_nat ipt_REJECT ipt_LOG ipt_limit ipt_state iptable_filter] ppp_deflate 3192 0 (autoclean) zlib_inflate 19748 0 (autoclean) [ppp_deflate] zlib_deflate 18744 0 (autoclean) [ppp_deflate] bsd_comp4504 0 (autoclean) ppp_async 6816 0 (autoclean) vmnet 18664 4 vmmon 23092 0 (unused) af_packet 12424 2 (autoclean) nfsd 69136 8 (autoclean) lockd 48144 1 (autoclean) [nfsd] sunrpc 64220 1 (autoclean) [nfsd lockd] parport_pc 25320 1 (autoclean) lp 6496 0 (autoclean) parport23040 1 (autoclean) [parport_pc lp] autofs4 8212 1 (autoclean) snd-intel8x0 17256 0 (unused) snd-mpu401-uart 2912 0 [snd-intel8x0] snd-pcm-oss37092 0 (unused) snd-mixer-oss 10928 0 [snd-pcm-oss] snd-cs46xx 65700 0 snd-pcm56576 0 [snd-intel8x0 snd-pcm-oss snd-cs46xx] snd-timer 13380 0 [snd-pcm] snd-ac97-codec 36344 0 [snd-intel8x0 snd-cs46xx] gameport1628 0 [snd-intel8x0 snd-cs46xx] snd-rawmidi12352 0 [snd-mpu401-uart snd-cs46xx] snd-seq-device 3744 0 [snd-rawmidi] snd30436 0 [snd-intel8x0 snd-mpu401-uart snd-pcm-oss snd-mixer-oss snd-cs46xx snd-pcm snd-timer snd-ac97-codec snd-rawmidi snd-seq-device] soundcore 3652 9 [snd] snd-page-alloc 5836 0 [snd-intel8x0 snd-cs46xx snd-pcm] w83627hf 12912 0 (unused) eeprom 3368 0 (unused) i2c-proc5780 0 [w83627hf eeprom] i2c-isa 748 0 (unused) i2c-i8014436 0 (unused) i2c-core 14564 0 [w83627hf eeprom i2c-proc i2c-isa i2c-i801] ppp_generic20636 1 (autoclean) [ppp_deflate bsd_comp ppp_async] slhc4960 0 (autoclean) [ppp_generic] 8139too14824 1 (autoclean) mii 2544 0 (autoclean) [8139too] crc32 2880 0 (autoclean) [8139too] sg 30588 0 (autoclean) floppy 48540 0 (autoclean) sd_mod 12044 0 usb-storage72640 0 ehci-hcd 16168 0 (unused) usb-uhci 21676 0
Re: [Dri-devel] Re: Strange lockups with DRI on Radeon 8500LE
On Sun, 2003-12-21 at 20:14, Konstantin Lepikhov wrote: Here is logs from dmesg: skip Linux agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 203M agpgart: Detected Intel i850 chipset agpgart: AGP aperture is 64M @ 0xe000 radeonfb: ref_clk=2700, ref_div=12, xclk=2 from BIOS Console: switching to colour frame buffer device 80x25 radeonfb: ATI Radeon 8500 QL DDR SGRAM 128 MB radeonfb: DVI port no monitor connected radeonfb: CRT port CRT monitor connected Does not loading radeonfb make a difference? (It shouldn't, but...) [drm] Initialized radeon 1.10.0 20020828 on minor 0: ATI Radeon QL R200 8500 LE [drm] Loading R200 Microcode Hmm, I suspect this could be related to the new card memory layout introduced with the radeon DRM 1.10.0. Can you try either the DRM or the 2D driver from before November 4th? -- Earthling Michel Dnzer | Debian (powerpc), X and DRI developer Software libre enthusiast| http://svcs.affero.net/rm.php?r=daenzer --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
