Re: XFree86-4.2 on older TiBook -- experience
Stew Benedict wrote: >On Tue, 26 Mar 2002, isaac wrote: > >That XFree is known to be broken on r128. The next one will be OK. > Thanks. Not to put on any pressure because you're busy enough ... but do you have a guess about when the fixed one will be available? Also, is there some place to grab the old final set of the 4.1 XFree's? The ones I had to downgrade to are from an old backup.:(
XFree86-4.2 on older TiBook -- experience
hi, I just had the following fun experience trying to get the latest XFree packages working on my TiBook (an older one with Rage 128 Mobility). This was originally an 8.0 install, which is now almost in sync with cooker. first, went to runlevel 1 and REMOVED all the XF-4.1.x packages (rpm -e --nodeps ...) next installed all the 4.2's minus some of the unnecessary fonts. it wouldn't work (tried telinit 5, startx, Xtart), here are the errors... Symbol xf86int10Addr from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol xf86InitInt10 from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol xf86FreeInt10 from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol xf86FreeInt10 from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol drmFreeBufs from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol drmR128TextureBlit from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol drmFreeBufs from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! (I have the whole XFree86.0.log file if anybody thinks that info can help) I guessed about several other packages needing to be updated, but this didn't help either (glibc for one). I'm curious about how the kernel-headers package # doesn't match the latest kernel available. Does this matter at all? Also, I corrected for the typo in /etc/X11 with hsync/vsync ... and tried using a backup of my XF86Config-4 that works under 4.1.x ... to no avail. Finally, I downgraded back to 4.1 and everything is mostly fine again. Anyway, thought I'd share the experience and see if anyone has a tip to get it working. -i
Re: XFree86-4.2 on older TiBook -- experience
On Tue, 26 Mar 2002, isaac wrote: > hi, > > I just had the following fun experience trying to get the latest XFree > packages working on my TiBook (an older one with Rage 128 Mobility). > This was originally an 8.0 install, which is now almost in sync with cooker. > > first, went to runlevel 1 and REMOVED all the XF-4.1.x packages (rpm -e > --nodeps ...) > > next installed all the 4.2's minus some of the unnecessary fonts. > > it wouldn't work (tried telinit 5, startx, Xtart), here are the errors... > > Symbol xf86int10Addr from module > /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! > Symbol xf86InitInt10 from module > /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! > Symbol xf86FreeInt10 from module > /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! > Symbol xf86FreeInt10 from module > /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! > Symbol drmFreeBufs from module /usr/X11R6/lib/modules/drivers/r128_drv.o > is unresolved! > Symbol drmR128TextureBlit from module > /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! > Symbol drmFreeBufs from module /usr/X11R6/lib/modules/drivers/r128_drv.o > is unresolved! > > (I have the whole XFree86.0.log file if anybody thinks that info can help) > That XFree is known to be broken on r128. The next one will be OK. > I guessed about several other packages needing to be updated, but this > didn't help either (glibc for one). I'm curious about how the > kernel-headers package # doesn't match the latest kernel available. Does > this matter at all? > kernel headers tracks glibc > Also, I corrected for the typo in /etc/X11 with hsync/vsync ... and > tried using a backup of my XF86Config-4 that works under 4.1.x ... to no > avail. > > Finally, I downgraded back to 4.1 and everything is mostly fine again. > Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
Re: XFree86-4.2 on older TiBook -- experience
On Tue, Mar 26, 2002 at 03:26:41PM +, isaac wrote: > first, went to runlevel 1 and REMOVED all the XF-4.1.x packages (rpm -e > --nodeps ...) > > next installed all the 4.2's minus some of the unnecessary fonts. > > it wouldn't work (tried telinit 5, startx, Xtart), here are the errors... Which XFree86 package? (i.e. rpm -q XFree86) -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org What difference does it make to the dead, the orphans, and the homeless, whether the mad destruction is wrought under the name of totalitarianism or the holy name of liberty and democracy? - Ghandi
XFree86-4.2 on older TiBook -- experience
[apologies if you get this twice. it's been a few hours since i first posted it, and it hasn't shown up yet] hi, I just had the following fun experience trying to get the latest XFree packages working on my TiBook (an older one with Rage 128 Mobility). This was originally an 8.0 install, which is now almost in sync with cooker. first, went to runlevel 1 and REMOVED all the XF-4.1.x packages (rpm -e --nodeps ...) next installed all the 4.2's minus some of the unnecessary fonts. it wouldn't work (tried telinit 5, startx, Xtart), here are the errors... Symbol xf86int10Addr from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol xf86InitInt10 from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol xf86FreeInt10 from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol xf86FreeInt10 from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol drmFreeBufs from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol drmR128TextureBlit from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! Symbol drmFreeBufs from module /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! (I have the whole XFree86.0.log file if anybody thinks that info can help) I guessed about several other packages needing to be updated, but this didn't help either (glibc for one). I'm curious about how the kernel-headers package # doesn't match the latest kernel available. Does this matter at all? Also, I corrected for the typo in /etc/X11 with hsync/vsync ... and tried using a backup of my XF86Config-4 that works under 4.1.x ... to no avail. Finally, I downgraded back to 4.1 and everything is mostly fine again. Anyway, thought I'd share the experience and see if anyone has a tip to get it working. -i
