RE: [Xpert]PowerBook III locks up using the HEAD ati driver(previous HEAD builds were okay)

2002-10-03 Thread Miles Lane 

Whoops. The XFree86.log information I included was from a session 
using the fbdev driver.  It shows a few problems of its own,
but not the ones I asked about.


The following info from the kernel log may be helpful: 

radeonfb: ref_clk=2700, ref_div=12, xclk=36675 from OF 
radeonfb: detected DFP panel size from EDID: 1280x854 
Console: switching to colour frame buffer device 160x53 
Registered "ati" backlight controller, level: 15/15 
radeonfb: pm reg @50, clk_pwrmgt: f17500, pll_pwrmgt: a027e01f,
mdll_cko: 980098radeonfb: ATI Radeon M7 LW  DDR SGRAM 32 MB 
radeonfb: DVI port LCD monitor connected 
radeonfb: CRT port no monitor connected 
no framebuffer address found for
/pci@f000/ATY,CrownParent@10/ATY,Crown_B 

agpgart: Maximum main memory to use for agp memory: 440M 
agpgart: Detected Apple UniNorth 1.5 chipset 
agp: configuring for size idx: 4 
agpgart: AGP aperture is 16M @ 0x0 
[drm] AGP 0.99 on Unknown @ 0x 16MB 
[drm] Initialized radeon 1.1.1 20010405 on minor 0 


And here is a log from the ati driver session:

XFree86 Version 4.2.99.1 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 26 September 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.20-pre7-ben0 ppc [ELF] 
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: Thu Oct  3 22:07:59 2002
(==) Using config file: "/etc/X11/XF86Config"
(==) ServerLayout "XFree86 Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "macintosh_old"
(**) XKB: model: "macintosh_old"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(--) Keyboard: CustomKeycode enabled
(**) FontPath set to
"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/tmp/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(**) ModulePath set to "/usr/X11R6/lib/modules"
(--) using VT number 7

(II) Open APM successful
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.6
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
compiled for 4.2.99.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
compiled for 4.2.99.1, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.6
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:0b:0: chip 106b,002d card , rev 00 class 06,00,00
hdr 00
(II) PCI: 00:10:0: chip 1002,4c57 card 1002,4c57 rev 00 class 03,00,00
hdr 00
(II) PCI: 10:0b:0: chip 106b,002e card , rev 00 class 06,00,00
hdr 00
(II) PCI: 10:17:0: chip 106b,0022 card , rev 03 class ff,00,00
hdr 00
(II) PCI: 10:18:0: chip 106b,0019 card , rev 00 class 0c,03,10
hdr 00
(II) PCI: 10:19:0: chip 106b,0019 card , rev 00 class 0c,03,10
hdr 00
(II) PCI: 10:1a:0: chip 104c,ac50 card 1000, rev 02 class 06,07,00
hdr 02
(II) PCI: 24:0b:0: chip 106b,002f card , rev 00 class 06,00,00
hdr 00
(II) PCI: 24:0e:0: chip 11c1,5811 card 11c1,5811 rev 00 class 0c,00,10
hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:11:0), (0,0,36), BCTRL: 0x0008 (VGA_EN is
set)
(II) Bus 0 I/O range:
[0] -1  0   0x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) Host-to-PCI bridge:
(II) Bus 16: bridge is at (16:11:0), (16,16,36), BCTRL: 0x0008 (VGA_EN
is set)
(II) Bus 16 I/O range:
[0] -1  0   0x - 0x (0x1) IX[B]
(II) Bus 16 non-prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) Bus 16 prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) PCI-to-CardBus bridge:
(II) Bus 17: bridge

Re: [Xpert]PowerBook III locks up using the HEAD ati driver(previous HEAD builds were okay)

2002-10-04 Thread Michel Dänzer 

On Fre, 2002-10-04 at 06:41, Miles Lane wrote:
> 
> I am running XFree86 HEAD on a Titanium PowerBook III/800
> with a 2.4.20-pre7-ben0 kernel built from Benjamin Herrenschmidt's
> rsync tree.  For the last couple of days, when I build from cvs HEAD,
> starting X has locked up my display (I cannot switch away from
> the locked tty7).  My kernel is still running, because the CAPSLOCK
> light still toggles.  

So it did when my machine didn't power on and I had to send it in for
repair... I usually try to ping it to determine if the kernel is up.


> Anyhow, I have had only minor problems with the ati driver for the
> last couple of months.  I am running radeonfb in the kernel and
> have the following settings in XF86Config:
> 
> Section "Module"
> Load"GLcore"
> Load"bitmap"
> Load"dbe"
> Load"ddc"
> #   Load"dri"
> Load"extmod"
> Load"freetype"
> Load"glx"
> Load"int10"
> Load"pex5"
> Load"record"
> Load"speedo"
> Load"type1"
> Load"vbe"
> Load"xie"
> EndSection

That's a bit excessive, have you tried removing at least int10 and vbe?


> The problem I have had with the ati driver prior to hitting this
> display lockup problem was that sometimes when I would switch
> between a VT window and the X display (or vice versa), the display 
> would show a sequence of three scanlines all starting at 
> different points.  So, line 1, 4, 7, 10, ... would start at the 
> right edge of the screen, lines 2, 5, 8, 11, ... would be indented 
> about 1/8 of the screen and lines 3, 6, 12, 13, ... would be 
> indented 1/4 of the screen.  Switching back and forth between a VT 
> and the X display would usually clean up the problem.  
> Very occaisionally the machine would lock up and need a cold boot.
> There was also a scrolling effect, where unsynced lines would seem
> to be scrolliny up slowly up.

[...]

> It is worth noting that the fbdev driver is working pretty well,
> though it exhibits the same problem that the ati driver used to
> have.  That is, sometimes when switching between a VT and the
> X display (or vice versa), the display is munged with unsynced
> scanlines.

That's a radeonfb glitch. The one to find and fix it gets the prize. :)


> (EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument

That's also a radeonfb bug, I sent a fix to Ben and Ani and Ben is
merging it into his tree right now.


The second log you posted was still from the fbdev driver BTW.


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert