Re: [suse-ppc] How to get Graphical GUI / Xwindows @ PM4400/ Suse 7.1PPC ?
To answer your question: I'm using allready Kernel version 2.4.2. NB: Olaf mentioned that the Mach64 chip at my PM4400 is very hard to use for SuSe linux. So I tried the following : I installed an extra PCI IMS TwinTurbo-128 card. I attached my monitor to the PCI card and rebooted. At first, sax refused to recognize this card. But with the command lspci the TwinTurbo showed up and it gave at least the correct PCI-position : 0:14:0 So I got brave and just changed the /etc/X11/XF86Config file with vi ; and changed the input for "Device" from "unknown" (for the still only detected ATI Mach built-in) to "IMS9129" and changed the busID from the old 0:17:0 (built-in Mach 64) to 0:14:0 ; I kept the "fbdev" as driver ; I kept the Device id [0] ; but changed the vendor name; And saved all changes. Then I just typed "startx" at my root prompt and >>> I GOT MY GRAPHICAL DESKTOP IMMEDIATE ! So, I think the built-in ATI Mach64 just doesn't work altogether... thanx so far, Carolus van Soest ===================previous text : ============================ 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.
participants (1)
-
Carolus