On Thu, 2002-05-16 at 00:04, Koos van den Hout wrote: > > I installed woody on a powerbook/G3 laptop (now booting ;) and the next > thing I'd really like to have working is X. > > The funny thing is that X starts and xterms run, but I don't see anything. > Switching back to a text console and then to vc7 (where X lives) gives the > funny effect that the cursor gets disabled but I keep seeing the text from > the vc I thought I left. > > I'm using > ii xserver-xfree8 4.1.0-16 the XFree86 X server > > configured is the FBdev device hopefully talking to the FBdev driver in the > kernel. > > What I keep seeing on the console (does not show up in dmesg or the X log > though) is: > > ioctl FBIOPUTCMAP: Function not implemented > > Which I see as a slight hint.. but what to do ?
Try atyfb instead of OFfb. > (logfile and configfile available, but I didn't want to flood those right > away) Can you put them up somewhere? > lspci gives: > 00:11.0 VGA compatible controller: ATI Technologies Inc 3D Rage LT-G 215LG > (rev 80) (prog-if 00 [VGA]) > Flags: bus master, stepping, medium devsel, latency 32, IRQ 24 > Memory at 82000000 (32-bit, non-prefetchable) > I/O ports at 0400 [disabled] > Memory at 82fff000 (32-bit, non-prefetchable) > > Changing to the ati driver with usefbdev true gives less result.. > > (II) ATI: ATI driver (version 6.3.6) for chipsets: ati > (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 RE (PCI), > ATI Rage 128 RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 RK > (PCI), > ATI Rage 128 RL (AGP), ATI Rage 128 Pro PD (PCI), > ATI Rage 128 Pro PF (AGP), ATI Rage 128 Pro PP (PCI), > ATI Rage 128 Pro PR (PCI), ATI Rage 128 Mobility LE (PCI), > ATI Rage 128 Mobility LF (AGP), ATI Rage 128 Mobility MF (AGP), > ATI Rage 128 Mobility ML (AGP) > (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP), > ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP), > ATI Radeon VE (AGP) > (II) ATI: Candidate "Device" section "ATI 3d rage". > (WW) ATI: PCI/AGP Mach64 in slot 0:17:0 could not be detected! > (EE) No devices detected. Seems it doesn't recognize your particular chip, maybe using the ChipID directive to override detection could help. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
