I have a Lenovo Thinkpad x250 that I just installed slackware 14.1 on. I did the full install and everything booted up fine.

I logged in as the root user and created an account for myself. I then logged into the account then proceeded to use the "startx" command. However, upon doing this the system froze. All I saw was a black screen. No mouse, nothing. I tried ctrl+alt+f1 and ctrl+alt+del, but nothing short of powering off worked.

I tried fluxbox and it worked just fine, so I figured it must be something with XFCE. It should be noted that when I log in as root I can start up XFCE, however upon logging out, the system freezes again.

I have installed Slackware on multiple systems in the past and have never come across this problem before. I am at a loss and any help would be appreciated

Can you start a different window manager (TWM, WindowMaker, Fluxbox) as normal user? Run 'xwmconfig' (as your normal user) and give it a try.

Isn't the real problem here that a Thinkpad x250 comes with a graphics card that is too new for Slackware 14.1 as it has a Intel HD Graphics 5500?

btw) related topic: http://www.linuxquestions.org/questi...-a-4175559431/

So it seems that my laptop is too new and I should try to upgrade to Slackware -current. However, I have never done this and am not sure how to go about doing this. There is a page on the slackdocs site that says how to do this through slackpkg, is this correct?

If you have never done this, it's maybe a good idea to wait a little bit until Slackware 14.2 is released. Won't be too long now, I guess.

1 members found this post helpful.

Hi,

You could use Alien_Bob's mirror-slackware-current.sh to create a local tree and ISO of choice. You can create the mirror-slackware-current.conf by entering 'mirror-slackware-current.sh -w' which will create the 'mirror-slackware-current.conf' file in the same directory as 'mirror-slackware-current.sh'. You can then edit/configure within the 'mirror-slackware-current.conf' file to suit your needs. That configure file is well documented.

Once you have created the ISO then you just need to burn the image to DVD for the install. I do not need the source so I use the no source option within the configure file.

Hope this helps.
Have fun & enjoy!

@onebuck

the link of yours has a character problem

Hi,

Thanks! Corrected link.

This was an issue with 14.1 a while back. I remember Pat saying something about it and was fixed with updates.
I did the same thing to test it and reproduced it. But if I logged into kde and set it up it worked.
I been working on a distro upgrade script for my fellow users. And ran accross the same thing as is spoken here. doing the adduser from root command line did not do the job. Then if you look into the way back machine of LQ some where you will find this issue and Pat addressed it. or it was in the change log. But Old as I am I remembered when it failed. vim to the group group- and shadow shadow- and they did not match.

Go to http://taper.alienbase.nl/mirrors/slackware/ and download your daily ISO of choice. It is the fastest way. You can then upgrade incrementally with the current change log.

1 members found this post helpful.

Thanks for the help everyone. I downloaded alien's script and used it to make a local copy of Slackware-current. I then burned it onto a USB, installed it, and everything is working fine.

I agree, if your not comfortable with current, then use fluxbox until 14.2 comes out.

After your initial install did you download all the patches (including the kernel patches for 64-bit) and install them? There are 69 patches plus the kernel patches, might make a difference.

Every so often my laptop, Dell Inspiron 1750, Slackware 64-bit 14.1 stable, either refuses to start Xfce or takes some minutes to do so. The other machines never do. Every machine has Intel graphics, so no graphics card weirdness.

I finally just gave up trying to figure out what the heck causes this and just put it down to laptop weirdness. Laptops have a tendency to do weird stuff; computers don't, as a rule, work sometimes and not work other times (if you leave them to their own devices). Laptops, every one I've ever had, do strange and wonderful things all by themselves. And nobody knows why, you can't really fix something that only breaks when the phase of the moon is wrong or you swore at the blasted thing.

Glad to know that current doesn't exhibit whatever the problem may be. I'll wait for the next stable release and see.

1 members found this post helpful.