> > i dunno, are lombards supported under xfree4.0
>
> I guess they should be, please post the exact error output.
Depends on the kernel version; PCI resource fixup for the Mach64 is needed
if you happen to boot via BootX.
Michael
steven alyari wrote:
> i have downloaded xfree4 from the rsync tree listed at
>
> http://linuxppc.org/documentation/xf4/
>
> and i use the "fbdev" driver for Section "Device"
>
> but when i startx all i get is a frozen black screen that is
> unescapable.. ctrl+alt+backspace, ctrl-c, switching c
Michel Dänzer wrote:
> > I didn't have any video options set. I set video=aty128fb in yaboot.conf
> > but it doesn't make any difference.
> You also need Option "UseFBDev" in XF86Config.
I have the following:
Section "Device"
Identifier "Rage128"
Driver "r128"
Option "UseFBDev"
Brendan J Simon wrote:
> > As Jack Howarths page says, mouse type should be "IMPS/2" still.
>
> Yes. Setting the mouse option to "imps/2" works on my G4. I thought the
> docs for Xfree86 4.0 said that PS/2 is not supported for Linux (or was that
> Linux98 ?).
I use "PS/2" on my Athlon without
Tom Rini wrote:
> > I didn't have any video options set. I set video=aty128fb in yaboot.conf
> > but it
> > doesn't make any difference. I get the bright green screen. When I change
> > video
> > modes with ctrl-alt-+ I can see that the resolution changes but the
> > background
> > turns to
On Wed, May 10, 2000 at 08:06:44PM +1000, Brendan J Simon wrote:
> Tom Rini wrote:
>
> > > > Do I need a kernel parameter option ? ie. video= ?
> > > No, I assume you're already using aty128fb.
>
> I didn't have any video options set. I set video=aty128fb in yaboot.conf but
> it
> doesn't m
Tom Rini wrote:
> Nope. Right now in 2.3.99preX (and for a while before) all usb mice look the
> same. With the evdev stuff, usb stuff looks even more the same (no more
> keycode translations). BTW, type "auto" doesn't seem to be too happy anywhere
> (friend of mine on x86 warned me against usi
Sven LUTHER wrote:
> On Tue, May 09, 2000 at 10:52:12AM -0400, Adam C Powell IV wrote:
> > Sven LUTHER wrote:
> >
> > > but when i enter a bad login in gdm, the gdm requester shivers from right
> > > to
> > > left and vice versa, about 10-20 pixels, becoming less, before
> > > stabilizing.
> > >
On Tue, May 09, 2000 at 05:44:33PM +0200, Michel Dänzer wrote:
> Brendan J Simon wrote:
>
> > The X server does get further on the G4. It recognises the video
> > chip fine but it gets stuck with the pointer and keyboard devices.
> > I went to the XFree86 Australian mirror and read the online doc
Brendan J Simon wrote:
> The X server does get further on the G4. It recognises the video
> chip fine but it gets stuck with the pointer and keyboard devices.
> I went to the XFree86 Australian mirror and read the online documentation
> for 4.0. It says for USB mouse to use either "usb" or "auto
On Wed, May 10, 2000 at 09:51:56AM +1000, Brendan J Simon wrote:
> Michel Dänzer wrote:
>
> > > How recent a kernel do I need ? One from CVS ?
> > > I am using the one from Ben H's site (vmlinux-2.2.15pre14).
> >
> > For a mach64 chip, you might need a 2.3.x kernel - don't know exactly.
> >
> > B
On Tue, May 09, 2000 at 10:52:12AM -0400, Adam C Powell IV wrote:
> Sven LUTHER wrote:
>
> > but when i enter a bad login in gdm, the gdm requester shivers from right to
> > left and vice versa, about 10-20 pixels, becoming less, before stabilizing.
> > Did you already encounter such a problem ?
>
Sven LUTHER wrote:
> but when i enter a bad login in gdm, the gdm requester shivers from right to
> left and vice versa, about 10-20 pixels, becoming less, before stabilizing.
> Did you already encounter such a problem ?
To quote Microsoft, "That's not a bug, it's a feature." I think it's kind o
Michel Dänzer wrote:
> > How recent a kernel do I need ? One from CVS ?
> > I am using the one from Ben H's site (vmlinux-2.2.15pre14).
>
> For a mach64 chip, you might need a 2.3.x kernel - don't know exactly.
>
> But as you have a Rage128, it doesn't matter, you can use the fbdev driver
> (unti
Brendan J Simon wrote:
> > If it's in fact from the mach64 family, you'll have to use the fbdev
> > driver for now - you might need a recent kernel which corrects broken OF
> > PCI memory ranges from though.
>
> How recent a kernel do I need ? One from CVS ?
> I am using the one from Ben H's sit
Michel Dänzer wrote:
> > (--) PCI: (0:16:0) ATI unknown chipset (0x4c46) rev 2, Mem @
> > 0xa400/26, 0xa000/14, I/O @ 0x0400/8
>
> Are you sure the chip in those Notebooks is from the Rage128 family?
Yep. It is a Rage 128 Mobility chip.
> If it's in fact from the mach64 family, you
On Tue, May 09, 2000 at 01:39:11PM +0200, Michel Dänzer wrote:
> Sven LUTHER wrote:
> >
> > On Tue, May 09, 2000 at 11:22:56AM +0200, Michel Dänzer wrote:
> > > Brendan J Simon wrote:
> > > > (--) PCI: (0:16:0) ATI unknown chipset (0x4c46) rev 2, Mem @
>
Sven LUTHER wrote:
>
> On Tue, May 09, 2000 at 11:22:56AM +0200, Michel Dänzer wrote:
> > Brendan J Simon wrote:
> > > (--) PCI: (0:16:0) ATI unknown chipset (0x4c46) rev 2, Mem @
^^
> > > 0xa400/26, 0xa000/14, I/O @ 0x0400/8
> >
>
On Tue, May 09, 2000 at 11:22:56AM +0200, Michel Dänzer wrote:
> Brendan J Simon wrote:
>
> > > > (WW) r128: No matching Device section for instance (BusID PCI:0:16:0)
> > > > found
> > > > (EE) No devices detected.
> >
> > (--) PCI: (0:16:0) ATI unknown chipset (0x4c46) rev 2, Mem @
> > 0xa4
Brendan J Simon wrote:
> > > (WW) r128: No matching Device section for instance (BusID PCI:0:16:0)
> > > found
> > > (EE) No devices detected.
>
> (--) PCI: (0:16:0) ATI unknown chipset (0x4c46) rev 2, Mem @
> 0xa400/26, 0xa000/14, I/O @ 0x0400/8
Are you sure the chip in those Notebo
Does this work on the new Apple PowerBook (the one with FireWire) ?
I have installed the XFree86 4.0 server and get the following errors in the log
file.
It seems to be looking at "BusID PCI:0:16:0: even though the XF86Config
expicitly states
"BusID 0:1:0".
Can someone post a working XF86Config f
Nelson Abramson wrote:
> Brendan J Simon wrote:
>
> > Does this work on the new Apple PowerBook (the one with FireWire) ?
> > I have installed the XFree86 4.0 server and get the following errors in the
> > log file.
> > It seems to be looking at "BusID PCI:0:16:0: even though the XF86Config
> >
Brendan J Simon wrote:
> Does this work on the new Apple PowerBook (the one with FireWire) ?
> I have installed the XFree86 4.0 server and get the following errors in the
> log file.
> It seems to be looking at "BusID PCI:0:16:0: even though the XF86Config
> expicitly states
> "BusID 0:1:0".
>
> Changes since 3.9.18:
>
> - contains experimental support for the Xv extension, try
> http://n.ethz.ch/student/daenzerm/download/mpeg2play
> (don't forget the -b switch and maximizing the window :)
> Thanks to Michael Schimek for his code.
Unfortunately, I seem to have included an old
Alan Buxey wrote:
> > http://n.ethz.ch/student/daenzerm/download/XFree86/4.0/
>
> if I am to update my current server, what files do I need to download,
> should I just grab all of them?
According to the readmes, you don't really need -include- and -libs- ;)
> PS Is the glx version now working
hi,
> http://n.ethz.ch/student/daenzerm/download/XFree86/4.0/
if I am to update my current server, what files do I need to download,
should I just grab all of them?
PS Is the glx version now working i believe 3.9.18 didnt work?
alan
Logan Hall wrote:
> I see that XFree86 4.0 has been released. Does this release include accel
> for the Mach64 chips in the Biege G3's?
IIRC there has been rudimental accel support (screen to screen copies) for
Mach64 added recently, but I doubt the driver works on PPC, at least hardly
without t
27 matches
Mail list logo
