Re: XFree86 just broke on PB3400 (Fri 5/28/99 AM (US))
On Thu, Jun 03, 1999 at 11:15:40AM -0500, Mike James wrote:
> Hi, Sven--
>
> On Jun 3 1999 at 3:08 AM -0500 you wrote:
>
> > On Wed, Jun 02, 1999 at 03:23:00PM -0500, Mike James wrote: <snip>
> > >
> > > X is now working again on my PB3400.
> > >
> > > The primary thing I did was to downgrade to Hartmut's x* files version
> > > 3.3.3.1-0.3 (2[345]-Feb-99) available at
> > > <http://powerpc.debian.org/~koptein/xfree/>
> >
> > That are the old X servers i made in January. They also contain Geert's
> > fbdev patch. (X --probeonly should give you the same output as above).
> > Please try the following server :
> >
> > http://dpt-info.u-strasbg.fr/~luther/xfree/XF68_FBDev_pm2_4.gz
> >
> > its just the the XF68_FBDev, that you must copy in place of the old one.
> > Best would be to change the name of the server to point to it in
> > /etc/X11/Xserver.
>
> This XF68_FBDev_pm2_4 server works. Thank you.
>
> Of course, it's working in the context of the version 3.3.3.1-03 x* (Feb)
> pkgs noted above. Because the current x* pkgs are not working on a PB3400 ,
> I think my present functionality implies something is wrong with the
> current x* pkgs, not in the xserver pkg(s), but in the xfont* pkgs.
Did you upgrade properly ? the font and othe X packages ?
Could you please try the XF68_FBDev_pm2_4 server in conjunction with the new X
packages ?
> > > MacOS display is /bandit/chips65550
> > > Using unsupported 800x600 chips65550 at 81800200, depth=16, pitch=1664
> > > Console: switching to colour frame buffer device 100x37
> >
> > Does that mean that you have a Chips&Technology 65550 chip ? and not an
> > ATI mach64 derivative one ? if yes, then it must be some other debian
> > patch, and nothing to do with mine.
>
> Yes. I think you're right.
>
> > What does fbset -i say about your framebuffer device
>
> Hmm, I can't find a binary called fbset.
ftp.debian.org/debian/dists/potato/main/binary-powerpc/admin/fbset_2.0.1-1.deb
very nice package, will let you change the resolution and depth of the framebuffer
device, and provide you info on said framebuffer device.
Friendly,
Sven LUTHER
Reply to: