Slack 13.0 and X.org
in [Slackware]
|
Prev: Acer Nplify
Next: Slackware 12.2 audio
From: Longfellow on 30 Mar 2010 22:41 After a very long time during which Slack 12.0 ran flawlessly, even though there's a spaghetti of soft links that sometimes even confuses the boot routine (gotta love Slackware!!), I've finally had to upgrade one of the boxen. The new Gimp (I am told) sports a GEGL 16 bit capability, and Gimp is sooooo much superior to Photoshop..... So I got 13.0 d/l'd and burnt to CD, which installed flawlessly (of course), but THEN.... I couldn't start X!! So here I am with a console trying to remember what that was like when I didn't know any better (before X and SLANG, etc), and decided I didn't want to go there any more! The error messages abound with stuff it can't find, with dire hints about having to load a (one or more) module(s) that I don't have, and do(es)n't show up in the kernel configuration file. And there's more, of course, which I could include in a post here, but.... So I came here, and sho 'nuff, I'm all alone. Apparently, no one has encountered anything like this. I'm old now, and I'd rather chase flowers with a camera during springtime, than I would spending lotsa hours feeling stupid while I chase this all down. Now.... does anyone have one of those "stupid UNIX tricks" (the kind you can only do with Slackware) that will fix this? Alternatively, would one of you young feller's give this old fart a hand? Off list, of course. I'd certainly appreciate any help, and thanks for reading. Longfellow
From: Stephen Bloom on 30 Mar 2010 23:19 Longfellow <not(a)this.address> wrote: [snipping for brevity..] > So I got 13.0 d/l'd and burnt to CD, which installed flawlessly (of > course), but THEN.... I couldn't start X!! So here I am with a console > trying to remember what that was like when I didn't know any better > (before X and SLANG, etc), and decided I didn't want to go there any > more! > The error messages abound with stuff it can't find, with dire hints > about having to load a (one or more) module(s) that I don't have, and > do(es)n't show up in the kernel configuration file. And there's more, > of course, which I could include in a post here, but.... > Longfellow X can be a nuisance at times. Folks around here are going to need more particulars about your system if they are to give you any real help. Most specifically, what graphics hardware does your box have? For example, I know from (painful) experience that the newer X drivers for the integrated Intel graphics (I810 vintage) have problems. Steve
From: Longfellow on 31 Mar 2010 00:32 On 2010-03-31, Stephen Bloom <sbloom(a)beauty.toad.net> wrote: > Longfellow <not(a)this.address> wrote: > [snipping for brevity..] >> So I got 13.0 d/l'd and burnt to CD, which installed flawlessly (of >> course), but THEN.... I couldn't start X!! So here I am with a console >> trying to remember what that was like when I didn't know any better >> (before X and SLANG, etc), and decided I didn't want to go there any >> more! > >> The error messages abound with stuff it can't find, with dire hints >> about having to load a (one or more) module(s) that I don't have, and >> do(es)n't show up in the kernel configuration file. And there's more, >> of course, which I could include in a post here, but.... > > >> Longfellow > > X can be a nuisance at times. Folks around here are going to need > more particulars about your system if they are to give you any > real help. Most specifically, what graphics hardware does your > box have? For example, I know from (painful) experience that the > newer X drivers for the integrated Intel graphics (I810 vintage) have > problems. > > > Steve Oh dear... I was afraid it was something like that. It runs fine on 12.0, so there's nothing broken in the hardware. Okay. Awww, geez.... I was going to stay clear of all this, but I guess not. The video chip is an Intel Media Graphics Accelerator 3100, better known as Intel's GMA-31. Intel has an Intel Linux section that treats exactly this problem. It's a matter of drivers, modules, libraries, and such. It involves apgart and drm, apparently more commonly as a module than as compiled into the kernel itself. This is gonna take chasing down and compiling all this stuff, and then recompiling the kernel to accept it. I gotta wonder just WTH X.org had to do to screw this up so badly, but that's life as a geek, right? I'm wondering whether it's worth messing with... maybe it'd be easier to get the latest Gimp and compile it, although God knows what kind of dependencies it is carrying now. Arghh. Thing is, I'm redecorating (wife died last year) and moving the LAN along with the ADSL gateway and its wiring, so this is not a trivial affair. My thinking is that I'm probably better off hanging with the current setup and taking potshots at the new OS until it's up and running; I'm arguably better off with more recent software, etc. So it looks like I'm gonna have to get my hands dirty here. Maybe go shooting on even days and hacking at the system on odd days? Argh. Thanks for the decent response, Steve. I appreciate that. Longfellow
From: Henrik Carlqvist on 31 Mar 2010 01:56 Longfellow <not(a)this.address> wrote: > The video chip is an Intel Media Graphics Accelerator 3100 > This is gonna take chasing down and compiling all this stuff, and then > recompiling the kernel to accept it. Or you could try some of the precompiled and packaged alternative intel drivers from the extra directory of your Slackware disc and hope for the best. However with older intel graphics the easiest way is probably to stick to Slackware 12 and install the newer gimp from source. 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
From: Mikhail Zotov on 31 Mar 2010 04:18
On Tue, 30 Mar 2010 23:32:32 -0500 Longfellow <not(a)this.address> wrote: > On 2010-03-31, Stephen Bloom <sbloom(a)beauty.toad.net> wrote: > > Longfellow <not(a)this.address> wrote: > > [snipping for brevity..] > > X can be a nuisance at times. Folks around here are going to need > > more particulars about your system if they are to give you any > > real help. Most specifically, what graphics hardware does your > > box have? For example, I know from (painful) experience that the > > newer X drivers for the integrated Intel graphics (I810 vintage) > > have problems. > > [...] > Awww, geez.... I was going to stay clear of all this, but I guess > not. The video chip is an Intel Media Graphics Accelerator 3100, > better known as Intel's GMA-31. Intel has an Intel Linux section > that treats exactly this problem. It's a matter of drivers, modules, > libraries, and such. It involves apgart and drm, apparently more > commonly as a module than as compiled into the kernel itself. I second Henrik. Go try other intel drivers from the extra/xf86-video-intel-alternate directory. There are chances at least one of them works for you. If not, download xf86-video-intel-2.9.1.tar.gz and compile it. -- Mikhail |