Slack 13.0 and X.org
in [Slackware]
|
Prev: Acer Nplify
Next: Slackware 12.2 audio
From: Douglas Mayne on 31 Mar 2010 09:31 On Tue, 30 Mar 2010 21:41:58 -0500, Longfellow wrote: > 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 > Did you upgrade or perform a clean install? For whatever reason, this version works better "out of the box" as a clean install. The biggest problems that people have reported (AFAICT) is with X. X no longer requires and x.org configuration file (except in certain cases). I have an old monitor which falls under that exception, and still requires a x.org to manually enter the refresh rates. I documented what I did here: http://groups.google.com/group/alt.os.linux.slackware/msg/50d91397325b7833 Also, if you performed a clean install and you have a fairly new monitor, and X doesn't start when using an Intel graphics chipset, then I agree that another Intel driver may be the best next step. I see that several are located in "extra," but I have never needed them personally. YMMV. -- Douglas Mayne
From: Mike Jones on 31 Mar 2010 10:31 Responding to Henrik Carlqvist: > 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 As 12 had some X glitches that appear to have been sorted by 12.2, I'd go for 12.2 as the default choice, and wait for 13.2. ;) -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: tapp on 2 Apr 2010 15:27 Longfellow <not(a)this.address> [Tue, 30 Mar 2010 23:32:32 -0500] > > Oh dear... I was afraid it was something like that. It runs fine on > 12.0, so there's nothing broken in the hardware. Answering probably too late, but I had X crash after my first 13.0 installation until I found out it needs hald running. Make sure it's activated in /etc/rc.d, along with udev and messagebus. And first try without a xorg.conf in /etc/X11. Just my $0.02...
From: danube on 3 Apr 2010 04:45 On Fri, 02 Apr 2010 21:27:53 +0200, tapp wrote: > Longfellow <not(a)this.address> [Tue, 30 Mar 2010 23:32:32 -0500] >> >> Oh dear... I was afraid it was something like that. It runs fine on >> 12.0, so there's nothing broken in the hardware. > > Answering probably too late, but I had X crash after my first 13.0 > installation until I found out it needs hald running. Make sure it's > activated in /etc/rc.d, along with udev and messagebus. And first try > without a xorg.conf in /etc/X11. Just my $0.02... I found that the mouse driver is the one that needs udev and messagebus. Find your correct protocol (in my case IMPS/2) and device (in my case / dev/input/mice) and you don't need this automated overhead.
From: Henrik Carlqvist on 4 Apr 2010 03:01
Longfellow <not(a)this.address> wrote: > Could not load /lib/modules/2.6.21.5-smp/modules.dep > Found /lib/modules/2.6.29.6-smp/modules.dep; why is it looking > for the 2.6.21.5-smp file? How did you install Slackware 13.0? Did you add any precompiled packages to your installation? If so, where did you get those packages? Slackware 12.0 uses kernel 2.6.21.5, to me it seems as if you have mixed up packages from different Slackware versions. Maybe you have failed in your attempt to upgrade from 12.0 to 13.0? Mixing libraries and drivers from different versions could also explain your problems to start X. 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 |