Open/install a .txz package on Slackware 12.2?
in [Slackware]
|
From: Tuxedo on 3 Jan 2010 15:46 I wrote: [...] > I just did a fresh installation of Slackware 13.0. For me X -configure and > thereafter X -config /root/xorg.conf.new returns a screenful of errors in > the console. Actually, something must have gone wrong with my first base installation. I redid the intallation but this time after doing 'X -configure' the 'X -config /root/xorg.conf.new' command produces just a black screen. startx works however but after logging out of X there's an error that the system failed to load module "i180" and "fbdev" because they don't exist. So I ran 'xorgsetup' and now using an generated xorg.conf the above error did not occur. Instead, some other errors are returned to console after logging out of an X session. Loading KDE4 works but without direct rendering, or with DRI, but if so very slowly and with various display errors while moving windows around. I also did a complete reboot in case that makes a difference, which it didn't. I guess the wrong default Intel driver must be in use. I will test with the alternate Intel drivers in the extra directory to see if any of those might work better in Slackware 13.0.
From: Mike Jones on 3 Jan 2010 16:42 Responding to Tuxedo: > I wrote: > > [...] > >> I just did a fresh installation of Slackware 13.0. For me X -configure >> and thereafter X -config /root/xorg.conf.new returns a screenful of >> errors in the console. > > Actually, something must have gone wrong with my first base > installation. I redid the intallation but this time after doing 'X > -configure' the 'X -config /root/xorg.conf.new' command produces just a > black screen. > > startx works however but after logging out of X there's an error that > the system failed to load module "i180" and "fbdev" because they don't > exist. > > So I ran 'xorgsetup' and now using an generated xorg.conf the above > error did not occur. Instead, some other errors are returned to console > after logging out of an X session. Loading KDE4 works but without direct > rendering, or with DRI, but if so very slowly and with various display > errors while moving windows around. I also did a complete reboot in case > that makes a difference, which it didn't. I guess the wrong default > Intel driver must be in use. I will test with the alternate Intel > drivers in the extra directory to see if any of those might work better > in Slackware 13.0. Have you tried 'xorgsetup' at all? Its more like the old way of doing things. Don't forget to check through your new xorg.conf and add back bits you might need, like maybe prefered gamma settings, etc. I managed to get a fully working X setup doing things this way, that still worked after installing NVIAIA drivers, and with a working UK keyboard layout too! -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Tuxedo on 3 Jan 2010 16:41 I wrote: [...] > driver must be in use. I will test with the alternate Intel drivers in the > extra directory to see if any of those might work better in Slackware > 13.0. After testing all four Intel drivers shipped in the extra directory and doing 'upgradepkg --install-new' for each and auto-reconfiguring X by 'xorgsetup' with full reboots between, none of the drivers work at all on this hardware, except for 'xf86-video-intel-2.8.1-i486-1.txz', which runs X with the exact same symptons as right after the system was originally installed, which was a full DVD install. I guess that is probably the same driver that's in use on the 13.0 system default installation. What about XFree86? It surely can't work as badly as xorg does with new drivers and somewhat old hardware. Is it even possible to install on Slackware?
From: Tuxedo on 3 Jan 2010 16:53 Mike Jones wrote: [...] > Have you tried 'xorgsetup' at all? Its more like the old way of doing > things. Don't forget to check through your new xorg.conf and add back > bits you might need, like maybe prefered gamma settings, etc. Sure I did, however, it failed in making DRI work with any of the drivers, and the hard part is knowing what is necessary to add manually to xorg.conf, as well as finding the values relating to the hardware. This information isn't exactly written anywhere on Intel's or Samsung's websites. So far it is only DRI that isn't working and this is obviously because the drivers are broken to begin with. I'm pretty sure it would work on a much older Linux system. I've searched countless forums and found many people having similar problems but could not find a clear solution anywhere. Tuxedo
From: Henrik Carlqvist on 4 Jan 2010 02:18
Tuxedo <tuxedo(a)mailinator.com> wrote: > After testing all four Intel drivers shipped in the extra directory and > doing 'upgradepkg --install-new' for each and auto-reconfiguring X by > 'xorgsetup' with full reboots between, none of the drivers work at all on > this hardware, except for 'xf86-video-intel-2.8.1-i486-1.txz', which runs X > with the exact same symptons as right after the system was originally > installed, which was a full DVD install. If so, I have no better idea than to stick to Slackware 12.2 and hope that the intel issues will be resolved in future versions of the kernel and X included in upcoming versions of Slackware. > What about XFree86? It surely can't work as badly as xorg does with new > drivers and somewhat old hardware. Is it even possible to install on > Slackware? The last release of XFree86 is version 4.8.0 from December 2008, Slackware 12.2 is newer than so. Version 4.9.0 was expected the summer or maybe winter of 2009, but that did obviously not happen. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost |