Re: RES: State of XOrg in testing/unstable
On Fri October 13 2006 05:50, [EMAIL PROTECTED] wrote: To clarify X hasn't worked since the move from 6.9 but it does run. I get an impressionist image and moveable square which represents the mouse, as I can move it about. My suspicion is some change to the PCI code/memory map as I imagine hardly anyone in i386 land has a PCI graphics card. Does the UP1100 have an AGP socket, some of the UP series did, didn't they? I'm running an ATI 3D Rage Pro 215GP PCI card on a i386. Works fine on kernel 2.6.16 and Xorg 7.1.1. It's not the same card as yours, so guess it doesn't really help with anything, but here are the relevant Xorg lines: X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 snip (--) PCI:*(0:14:0) ATI Technologies Inc 3D Rage Pro 215GP rev 92, Mem @ 0xfe 00/24, 0xffbef000/12, I/O @ 0xfc00/8 I also have the same in my PWS500au. Its running fine under kernel 2.6.16 and Xorg 7.0.0. Here are the relevant lines for it: X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 snip (--) PCI:*(1:10:0) ATI Technologies Inc 3D Rage Pro 215GP rev 92, Mem @ 0x09 00/24, 0x0a803000/12, I/O @ 0x8400/8, BIOS @ 0x8000/17 Good luck! -T -- Tyson Whitehead (-twhitehe at uwo.ca -- MC-) Computer Engineer Dept. of Applied Mathematics, Graduate Student- Applied Mathematics University of Western Ontario, GnuPG Key ID# 0xF7666BFF London, Ontario, Canada pgpn5TxMjNqSI.pgp Description: PGP signature
Re: RES: State of XOrg in testing/unstable
Strange. I have UP1100 motherboard with ATI Technologies Inc RV280 [Radeon 9200 PRO] controller and total lock up still after unstable was going for Xorg instead of XFree86. Kernel is self compiled 2.16.18 for nautilus. The hardware setup is almost the same and you have no problems.. ? Anyway the machine has been unusable with X almost 5 moths now.. :( Joni Simon Brown wrote: On Wed, 2006-10-04 at 01:36 -0400, Ivan Jager wrote: Heh, I was somehow expecting it to drop me back into a firmware prompt. After a reboot the bits seemed to still be around, so I attached the output of ser pim. This was with the G200, xorg 7.1.0-1, on the c3700. Nothing from Xorg.0.log survived. :( On my XP1000 alpha Xorg 7.0 or 7.1 has never locked the system up so I have Xorg log. I've attached it in case it's of any use. Simon X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: UNKNOWN Current Operating System: Linux bruce 2.6.18-1-alpha-generic #1 Fri Sep 29 15:40:05 UTC 2006 alpha Build Date: 07 July 2006 Before reporting problems, check http://wiki.x.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/Xorg.0.log, Time: Thu Oct 12 21:08:36 2006 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device ATI Technologies, Inc. RV280 [Radeon 9200 PRO] (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi/ does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/X11/Type1. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/X11/Type1). (WW) The directory /usr/X11R6/lib/X11/fonts/Type1 does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi does not exist. Entry deleted from font path. (**) FontPath set to: unix/:7100, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (**) Ignoring ABI Version (II) No APM support in BIOS or kernel (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.0 X.Org XInput driver : 0.6 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor=X.Org Foundation compiled for 7.1.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:07:0: chip 1080,c693 card , rev 00 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1080,c693 card , rev 00 class 01,01,80 hdr 80 (II) PCI: 00:07:2: chip 1080,c693 card , rev 00 class 01,01,00 hdr 80 (II) PCI: 00:07:3: chip 1080,c693 card , rev 00 class 0c,03,10 hdr 80 (II) PCI: 00:0c:0: chip 1002,5960 card 174b,0250 rev 01 class 03,00,00 hdr 80 (II) PCI: 00:0c:1: chip 1002,5940 card 174b,0251 rev 01 class 03,80,00 hdr 00 (II) PCI: 100:03:0: chip 1011,0019 card , rev 41 class 02,00,00 hdr 00 (II) PCI: 100:06:0: chip 1077,1020 card , rev 06 class 01,00,00 hdr 00 (WW) pciGenFindNext: primary bus mismatch on PCI bridge 0x01004000 (0x100, 0x101) (II) PCI: 100:08:0: chip 1011,0024 card , rev 03 class
Re: RES: State of XOrg in testing/unstable
[EMAIL PROTECTED] wrote: Strange. I have UP1100 motherboard with ATI Technologies Inc RV280 [Radeon 9200 PRO] controller and total lock up still after unstable was going for Xorg instead of XFree86. Kernel is self compiled 2.16.18 for nautilus. The hardware setup is almost the same and you have no problems.. ? Anyway the machine has been unusable with X almost 5 moths now.. :( To clarify X hasn't worked since the move from 6.9 but it does run. I get an impressionist image and moveable square which represents the mouse, as I can move it about. My suspicion is some change to the PCI code/memory map as I imagine hardly anyone in i386 land has a PCI graphics card. Does the UP1100 have an AGP socket, some of the UP series did, didn't they? Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RES: State of XOrg in testing/unstable
On Wed, 2006-10-04 at 01:36 -0400, Ivan Jager wrote: Heh, I was somehow expecting it to drop me back into a firmware prompt. After a reboot the bits seemed to still be around, so I attached the output of ser pim. This was with the G200, xorg 7.1.0-1, on the c3700. Nothing from Xorg.0.log survived. :( On my XP1000 alpha Xorg 7.0 or 7.1 has never locked the system up so I have Xorg log. I've attached it in case it's of any use. Simon X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: UNKNOWN Current Operating System: Linux bruce 2.6.18-1-alpha-generic #1 Fri Sep 29 15:40:05 UTC 2006 alpha Build Date: 07 July 2006 Before reporting problems, check http://wiki.x.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/Xorg.0.log, Time: Thu Oct 12 21:08:36 2006 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device ATI Technologies, Inc. RV280 [Radeon 9200 PRO] (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi/ does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/X11/Type1. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/X11/Type1). (WW) The directory /usr/X11R6/lib/X11/fonts/Type1 does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi does not exist. Entry deleted from font path. (**) FontPath set to: unix/:7100, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi (==) RgbPath set to /etc/X11/rgb (==) ModulePath set to /usr/lib/xorg/modules (**) Ignoring ABI Version (II) No APM support in BIOS or kernel (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.0 X.Org XInput driver : 0.6 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor=X.Org Foundation compiled for 7.1.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:07:0: chip 1080,c693 card , rev 00 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1080,c693 card , rev 00 class 01,01,80 hdr 80 (II) PCI: 00:07:2: chip 1080,c693 card , rev 00 class 01,01,00 hdr 80 (II) PCI: 00:07:3: chip 1080,c693 card , rev 00 class 0c,03,10 hdr 80 (II) PCI: 00:0c:0: chip 1002,5960 card 174b,0250 rev 01 class 03,00,00 hdr 80 (II) PCI: 00:0c:1: chip 1002,5940 card 174b,0251 rev 01 class 03,80,00 hdr 00 (II) PCI: 100:03:0: chip 1011,0019 card , rev 41 class 02,00,00 hdr 00 (II) PCI: 100:06:0: chip 1077,1020 card , rev 06 class 01,00,00 hdr 00 (WW) pciGenFindNext: primary bus mismatch on PCI bridge 0x01004000 (0x100, 0x101) (II) PCI: 100:08:0: chip 1011,0024 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 101:0a:0: chip 1102,0002 card 1102,8026 rev 07 class 04,01,00 hdr 80 (II) PCI: 101:0a:1: chip 1102,7002 card 1102,0020 rev 07 class 09,80,00 hdr 80 (II) PCI: End of PCI scan (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) PCI-to-PCI bridge: (II) Bus [EMAIL PROTECTED]: bridge is at ([EMAIL PROTECTED]:8:0), ([EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]), BCTRL: 0x0007 (VGA_EN is cleared) (II) Bus [EMAIL
Re: RES: State of XOrg in testing/unstable
On Tue, 3 Oct 2006, Ivan Jager wrote: On Mon, 2 Oct 2006, Grant Grundler wrote: On Sun, Oct 01, 2006 at 02:15:42AM -0400, Ivan Jager wrote: ... Then it will start cycling between: FLT 500B SYS BD bus timeout FLT CB74 SYS BD bad os HPMC cksm FLT CBFC SYS BD OS HPMC br err FLT CBF0 SYS BD HPMC initiated To paraphrase, the chassis codes mean: o Someone accessed an address that didn't respond. o CPU timed out the transaction. o HPMC == High Priority machince Check. Try ser pim at the firmware prompt to see which address it tried to reference. Ok, I'll try that sometime soon. Heh, I was somehow expecting it to drop me back into a firmware prompt. After a reboot the bits seemed to still be around, so I attached the output of ser pim. This was with the G200, xorg 7.1.0-1, on the c3700. Nothing from Xorg.0.log survived. :( I don't actually know what most of these bits mean. Is MEM_ADDR = 0x01ff3fff the physical address it tried to access? This may be relevant: $ cat /proc/ioports -1fff : PCI00 Ports 0020-003e : pic1 00a0-00be : pic2 03c0-03df : matrox 07e0-07fe : acpi 0800-08ff : sym53c8xx 0900-09ff : sym53c8xx 0a00-0a07 : ide0 0a08-0a0f : ide1 0e02-0e02 : ide0 0f00-0f07 : ide0 1000-107f : tulip 00012000-00013fff : PCI01 Ports 00028000-00029fff : PCI02 Ports 0003c000-0003dfff : PCI03 Ports [EMAIL PROTECTED]:~$ cat /proc/iomem -bfff : System RAM -09ff : PDC data (Page Zero) 0010-004c1fff : Kernel code 004c2000-006cefff : Kernel data fff0f05d-fff0f05d : lcd_data fff0f05d0008-fff0f05d0008 : lcd_cmd f400-f47f : PCI00 LMMIO f400-f4001fff : sym53c8xx f4002000-f4003fff : sym53c8xx f4004000-f40043ff : sym53c8xx f4005000-f40053ff : sym53c8xx f4007000-f4007fff : ohci_hcd f4008000-f40083ff : tulip f4009000-f400900f : AD1889 f400a000-f400a00f : AD1889 f400b000-f400b00f : AD1889 f400c000-f400c1ff : AD1889 f480-f4ff : PCI01 LMMIO f600-f67f : PCI02 LMMIO f700-f77f : PCI03 LMMIO f800-f8ff : PCI01 ELMMIO f800-f8ff : matroxfb FB f900-f9003fff : matroxfb MMIO fa00-fbff : PCI03 ELMMIO fed0-fed00fff : 10 fed3-fed30fff : 10:0 fed32000-fed32fff : 10:1 fed38000-fed38fff : 10:4 fed3c000-fed3cfff : 10:6 fef0-feff : Astro Intr Ack fff8-fffa : Central Bus fffa-fffa0fff : 32 fffb-fffd : Local Broadcast fffe- : Global Broadcast IvanMain Menu: Enter command ser pim PROCESSOR PIM INFORMATION - Processor 0 HPMC Information -- Timestamp = Wed Oct 4 02:31:42 GMT 2006(20:06:10:04:02:31:42) HPMC Chassis Codes = 2cbf0 2500b 2cbf4 2cbfc General Registers 0 - 31 00-03 40ac37c0 40ac373b 40017ff0 04-07 001c98b8 c0650760 c0650760 0040 08-11 0007 0019a0f4 f901 12-15 0001 0004 c0650760 16-19 0001 0055 00aa 40b939bc 20-23 40ac36bc 0007 0001 24-27 0010 40017ff0 c065075c 001c98b8 28-31 40ac3844 0151 c06509c0 Press any key to continue (q to quit) Control Registers 0 - 31 00-03 04-07 08-11 102c 00c0 0008 12-15 00103000 ff00 16-19 001a63539900 0040b000 40ac384f 0f201094 20-23 002403ff 4000ffc17ff0 00ff000eff0f 8000 24-27 005c8000 bd33a000 28-31 ff7e ff7e cd24c000 1062 Space Registers 0 - 7 00-03 0040b000 0040b000 0040b000 04-07 0040b000 0040b000 0040b000 0040b000 Press any key to continue (q to quit) IIA Space= 0x0040b000 IIA Offset = 0x40ac37f7 Check Type = 0x2000
Re: RES: State of XOrg in testing/unstable
On Mon, 2 Oct 2006, Grant Grundler wrote: On Sun, Oct 01, 2006 at 02:15:42AM -0400, Ivan Jager wrote: ... Then it will start cycling between: FLT 500B SYS BD bus timeout FLT CB74 SYS BD bad os HPMC cksm FLT CBFC SYS BD OS HPMC br err FLT CBF0 SYS BD HPMC initiated To paraphrase, the chassis codes mean: o Someone accessed an address that didn't respond. o CPU timed out the transaction. o HPMC == High Priority machince Check. Try ser pim at the firmware prompt to see which address it tried to reference. Ok, I'll try that sometime soon. Pressing the (soft) power button causes a clean shutdown after which it powers down, so it's not completely dead. An HPMC means the box is dead from an OS point of view. We can't access the IO subsystem after an HPMC and the OS gets control but only attempts dump a tombstone to the console (which might fail too). Can you clarify what you mean by clean shutdown? Oops, I was looking at the wrong part of /var/log/messages. :( No clean shutdown. It just takes about half a minute before turning off. ... I'm currently using the fbdev driver with the G200. I can't vouch for it's stability, but it seems to be working. wow! coool! Yes. Um, for people on debian-alpha: I guess I should have explicitly said I was crossposting to avoid confusion. The fbdev driver with G200 is working on hppa now. (I only tried fbdev with the radeon on alpha, and that didn't work.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RES: State of XOrg in testing/unstable
Ivan Jager wrote: Yes. Um, for people on debian-alpha: I guess I should have explicitly said I was crossposting to avoid confusion. The fbdev driver with G200 is working on hppa now. (I only tried fbdev with the radeon on alpha, and that didn't work.) For the one or two of us reading this on debian-alpha :-), I knew you were writing about the hppa case... Nevertheless, it remains encouraging that fbdev is working for someone running a less popular architecture (than x86). Might have to dig up a Matrox somewhere and give that a try. (Still not giving up on the radeon, though...) -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RES: State of XOrg in testing/unstable
On Sun, Oct 01, 2006 at 02:15:42AM -0400, Ivan Jager wrote: ... Then it will start cycling between: FLT 500B SYS BD bus timeout FLT CB74 SYS BD bad os HPMC cksm FLT CBFC SYS BD OS HPMC br err FLT CBF0 SYS BD HPMC initiated To paraphrase, the chassis codes mean: o Someone accessed an address that didn't respond. o CPU timed out the transaction. o HPMC == High Priority machince Check. Try ser pim at the firmware prompt to see which address it tried to reference. Pressing the (soft) power button causes a clean shutdown after which it powers down, so it's not completely dead. An HPMC means the box is dead from an OS point of view. We can't access the IO subsystem after an HPMC and the OS gets control but only attempts dump a tombstone to the console (which might fail too). Can you clarify what you mean by clean shutdown? ... I'm currently using the fbdev driver with the G200. I can't vouch for it's stability, but it seems to be working. wow! coool! grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RES: State of XOrg in testing/unstable
On Mon, 25 Sep 2006, Bob Tracy wrote: Bob Tracy wrote: Tomorrow I'll try yanking the ATI card and putting the old TGA2 back in, just to see if Xorg 7.1 will work with the hardware that worked back in the 6.8 days. The good (I think) news is that the TGA2 works fine with the latest Xorg 7.1 and dependent packages from the unstable tree, i.e., I think the reported ATI and MGA problems are probably driver issues. It seems the same or similar problems happen on both hppa and alpha. I just tested a Radeon 9250, a Matrox G200, and a Millenium II on an HP c3700. With the radeon and mga drivers, the screen will go black, and the box will stop responding to pings or keyboard. (On alpha I could sometimes ssh in.) I noticed shortly after the screen went black, the LCD would print FLT CBF0 (followed by 6.17-pa6 which was already there before) Then it will start cycling between: FLT 500B SYS BD bus timeout FLT CB74 SYS BD bad os HPMC cksm FLT CBFC SYS BD OS HPMC br err FLT CBF0 SYS BD HPMC initiated Pressing the (soft) power button causes a clean shutdown after which it powers down, so it's not completely dead. This is with xorg 7.1.0-1, but on alpha the same happens with 7.0. (I haven't tested 7.0 on hppa.) Can anyone else with an mga or radeon check whether it is in fact broken on hppa? I'm currently using the fbdev driver with the G200. I can't vouch for it's stability, but it seems to be working. Ivan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: RES: State of XOrg in testing/unstable
http://www.parisc-linux.org/faq/graphics-howto.html Look for Which non-HP PCI graphics cards work with PA-RISC Linux? On 10/1/06, Ivan Jager [EMAIL PROTECTED] wrote: On Mon, 25 Sep 2006, Bob Tracy wrote: Bob Tracy wrote: Tomorrow I'll try yanking the ATI card and putting the old TGA2 back in, just to see if Xorg 7.1 will work with the hardware that worked back in the 6.8 days. The good (I think) news is that the TGA2 works fine with the latest Xorg 7.1 and dependent packages from the unstable tree, i.e., I think the reported ATI and MGA problems are probably driver issues. It seems the same or similar problems happen on both hppa and alpha. I just tested a Radeon 9250, a Matrox G200, and a Millenium II on an HP c3700. With the radeon and mga drivers, the screen will go black, and the box will stop responding to pings or keyboard. (On alpha I could sometimes ssh in.) I noticed shortly after the screen went black, the LCD would print FLT CBF0 (followed by 6.17-pa6 which was already there before) Then it will start cycling between: FLT 500B SYS BD bus timeout FLT CB74 SYS BD bad os HPMC cksm FLT CBFC SYS BD OS HPMC br err FLT CBF0 SYS BD HPMC initiated Pressing the (soft) power button causes a clean shutdown after which it powers down, so it's not completely dead. This is with xorg 7.1.0-1, but on alpha the same happens with 7.0. (I haven't tested 7.0 on hppa.) Can anyone else with an mga or radeon check whether it is in fact broken on hppa? I'm currently using the fbdev driver with the G200. I can't vouch for it's stability, but it seems to be working. Ivan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Thibaut VARENE http://www.parisc-linux.org/~varenet/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RES: State of XOrg in testing/unstable
Ivan Jager wrote: Can anyone else with an mga or radeon check whether it is in fact broken on hppa? I'm currently using the fbdev driver with the G200. I can't vouch for it's stability, but it seems to be working. This is encouraging. Haven't tried fbdev on Alpha with 7.1, but it was definitely broken with an ATI card and 7.0. Usually (but not always) it was broken *less* than for the ati driver case in that I could at least switch back to a virtual console tty and stop X11 without locking up the machine. Somewhere near 7.0.23 with a 2.6.18-rcX kernel, fbdev would lock the machine solid. -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
