Re: [suse-ppc] How to get Graphical GUI / Xwindows @ PM4400/ Suse 7.1PPC ?
On Mon, Jul 16, Olaf replied to request from Carolus: Original request:
I finally got Suse PPC 7.1 installed at my OldWorld PowerMac4400 with: etc. entering "startx" gives just the following error messages from the server-log:
(**)FBDev(0): claimed PCI slot 0:17:0 ( I I ) FBDev (0): using default device (WW)****INVALID IO ALLOCATION**** b: 0x400 e: 0x4ff correcting (EE) FBdev(0): xf86RegisterResources found resource conflicts. (EE) Screen(s) found, but none have a usable configuration.
Fatal server error : no screens found.
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
Then I again just get my root-prompt back ...
Olaf replied: Can you have a look at `cat /proc/fb`, is OFfb active? If yes, dont boot with "No video driver". The Ati chip in the 4400 is a bit tricky, can you boot with "video=atyfb:vmode:13:cmode:8"? I tried those different video settings, with and without the checkbox "no video driver", but in the end the original problem reamins the same: no Xserver, and I keep getting the same error messages in the log. Note: the system-info of Suse recognizes the chip as a ATI mach 64, so that looks ok. Olaf replied: I guess the 2.4 kernel should work better, but try the above first. That's ok : I'm allready using Kernel version 2.4.2 Thanks so far; any other options left ;-) Carolus
I finally got Suse PPC 7.1 installed at my OldWorld PowerMac4400 with: etc. entering "startx" gives just the following error messages from the server-log:
(**)FBDev(0): claimed PCI slot 0:17:0 ( I I ) FBDev (0): using default device (WW)****INVALID IO ALLOCATION**** b: 0x400 e: 0x4ff correcting (EE) FBdev(0): xf86RegisterResources found resource conflicts. (EE) Screen(s) found, but none have a usable configuration.
Fatal server error : no screens found.
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining.
Then I again just get my root-prompt back ...
Olaf replied:
I guess the 2.4 kernel should work better, but try the above first.
That's ok : I'm allready using Kernel version 2.4.2
Thanks so far; any other options left ;-)
I had exactly the same problem on my PowerBase 200 (same chipset as far as I know) with SuSE 7.1: X just refused to startup with the above resource conflicts. The only workaround I found was to revert back to Kernel 2.2.x: Although there is still a similar warning about a resource conflict, X starts up ok with 8 or 15 (!) bit color depth. I have no clue whatsoever what change in the kernel framebuffer actually triggers this error and whether the 2.4 kernel or XFree is actually to blame... Cheers, Markus ---------------------------------------------------------------------- email: mlischka@physik.tu-muenchen.de Markus Lischka www : http://www.ph.tum.de/~mlischka Physics Department T30 phone: (0 89) 2 89-1 43 30 James-Franck-Str. 1 fax : (0 89) 2 89-1 22 96 D-85747 Garching ----------------------------------------------------------------------
participants (2)
-
Carolus -
Markus Lischka