Slackware 14.2: IT FREEZE, RANDOM, ALWAYS, I WANT A "BSOD" AT LEAST!

aldorgan · 07-31-2016, 02:29 PM

Ok i see, yeah i have noticed in changelogs before 14.2 was released that the intel driver got some updates here and there near the end, and getting a driver that works with all laptop is not easy. Thanks for the info on how i can get a driver and how to build it and will defintly try that out and see if that helps my laptop to stop acting up.

Quote:

Originally Posted by bassmadrigal

The Intel graphics were a major consideration during the development process. Intel drivers are so inconsistent on various hardware that it was a nightmare trying to find a good version that worked with everyone's hardware. Maybe yours didn't make the cut.

Pat does have a script in the source/ folder on 14.2 that will grab the latest git version and create a tarball. You can then use the x11.SlackBuild to create a new intel package and see if it fixes your problem.

Off the top of my head, you should be able to build the newest version with the following commands (I know running the SlackBuild and upgradepkg needs to be done as root, but the rest should be up to you).

Code:

wget -r -nH --no-parent --reject="index.html*" --cut-dirs=5 https://slackbuilds.org/mirror/slackware/slackware64-14.2/source/x/x11/
cd x11/src/drivers
sh ../get-xf86-video-intel.sh
cd ../../
sh x11.SlackBuild drivers xf86-video-intel
upgradepkg /tmp/xf86-video-intel*.txz

dugan · 07-31-2016, 02:31 PM

Quote:

Originally Posted by Darth Vader

BTW, the single common points of them are:

Radeon HD4450 -> 6450

The rest, one is GeForce 210 and one GeForce 6200 (AGP, on a P4)

Why are some people still talking about the Intel driver?

moesasji · 07-31-2016, 02:32 PM

Quote:

Originally Posted by dugan

Why are some people still talking about the Intel driver?

See the eigth post in this topic, i.e. the one here: http://www.linuxquestions.org/questi...0/#post5583786

linuxtinker · 07-31-2016, 02:42 PM

Please Look away and don't feed the TROLL!

hitest · 07-31-2016, 02:42 PM

I'm running 14.2 on three computers, and slackware64-current on two units. All is well here, no lock-ups.

Darth Vader · 07-31-2016, 02:42 PM

Okay guys, please understand that this thread is NOT a "Help me Obi-wan Kenobi! You are my only hope!", instead, it is just a warning that something sucks, in my computers case.

I know even the solution: the previous LTS Kernel tree, aka 4.1.x.

Darth Vader · 07-31-2016, 02:44 PM

Quote:

Originally Posted by linuxtinker

Please Look away and don't feed the TROLL!

So, today, if someone point his finger to a stinking shit in your garden, he's a TROLL?

In this case, I'm proud to be TROLL, thanks!

linuxtinker · 07-31-2016, 02:50 PM

Quote:

Originally Posted by Darth Vader

So, today, if someone point his finger to a stinking shit in your garden, he's a TROLL?

Actually I would grab a shovel and turn that ground over, shit is some good fertilizer!

kikinovak · 07-31-2016, 02:56 PM

Quote:

Originally Posted by Darth Vader

I never seen a Linux where you have to hard reset ten times the computer for a successfully boot, just to freeze on middle of writing an ordinary document on Kate (TXT of course) or browsing a News site.

Yet, this way behave Slackware 14.2 on my computers, ranged from P4 to Bulldozer x8.

WTF?

BTW, anyone, please do not reply to this thread! This way it will popup "random" in the eyes of the Slackware Team, just like my systems freeze.

Judging from your posts, here's how I imagine your /etc/mkinitrd.conf:

Code:

# mkinitrd.conf
#
SOURCE_TREE="/BOOT/INITRD.TREE"
CLEAR_TREE="YESMOTHERFUCKER"
OUTPUT_IMAGE="/BOOT/INITRD.GZ"
KERNEL_VERSION="FOUR!FOUR!FOURTEEN!"
KEYMAP="TRANSSYLVANIAN_TRANSVESTITE.UTF8"
MODULE_LIST="EE!EX!TEE!FOUR!"
ROOTDEV="/DEV/SDA3"
ROOTFS="EE!EX!TEE!FOUR!"
RESUMEDEV="/DEV/SDA2"
RAID="FUCKNO"
LVM="FUCKNO"
UDEV="FUCKYES"
MODCONF="FUCKNO"
WAIT="FUCKYES"

First things first. Check your Caps lock key.

Cheers,

Niki

Richard Cranium · 07-31-2016, 03:08 PM

Quote:

Originally Posted by Darth Vader

So, today, if someone point his finger to a stinking shit in your garden, he's a TROLL?

In this case, I'm proud to be TROLL, thanks!

Well, you are pointing out a stinking shit in your garden and demanding that somebody do something about it.

I haven't seen similar bowel movements in my garden. You appear to have a solution that works for you, which could have been the basis of a more reasonable post.

travis82 · 07-31-2016, 03:19 PM

Quote:

Originally Posted by Darth Vader

someone point his finger to a stinking shit in your garden

Seems that you liked our saying.

Drakeo · 07-31-2016, 03:55 PM

I use grub if you are not using it then read at the bottom.
The freeze random since I am not sure how you installed it and what boot loader you are using I can only tell you my experience since I have many Slackwares installed for different projects i make back up of them with squasfs. I notices I wanted to unsquasfs one on to another drive like I have done many times before. just adjust my fstab etc etc. you know if you do not then learn it.
I noticed it froze up all the time hey wtf I thought is going on. this is a back up of a devel install I have done many times.

Well Something about the new grub so I ran a new grub config and went and looked for that drive and guess what it never found that
O/S on sdb3. So tool a while to figure out seems I had a old grub on sdb1 and you may guess it it rewrote that wild huh.
but why not sdb3 looked in advance it was pretty screwed up. only thing I can think of was db3 was not bootable. Bootable is a word to me.
any way I went in an edited the grubfg with those uuid's and all is well. I am able to reproduce that problem of freezing then go good then freeze every time this way. So I thought hey I will just do a new install on that drive and not put a boot loader on it. Guess what same problem. If you do not use uuid as a drive for root and and chose top go /dev/sdbX=root still have the same problem.
do not ask my why it only happens since the latest grub update. I do not care. the fix is to run mkgrubcfg and learn grub.
As for a new default install and it freezes with KDE then that will happen till the search data base is built. since I have 3 drives and 14 partitions it will freezes on and off and I have.

dugan · 07-31-2016, 06:00 PM

Quote:

Originally Posted by Darth Vader

it is just a warning

The time for this justification is before you've been told that you're literally the only person in the world who is having this issue. Not after.

enorbet · 07-31-2016, 09:20 PM

I have to ask you, Darth Vader, if this is actually just a "warning" about a particular kernel then why would any sensible person write it up in Slackware and not General or some other more appropriate kernel thread and why in the Hell would you rave in all caps! Have you never heard that it is unwise and inconsiderate to bite the hand that has fed you for some time? You have somewhere around 1000 posts on LQN and therefore must be aware this is a helpful community and yet you don't realize that completely generalized rants with no specifics cannot get help.... or don't you want help to make it work and just prefer to spout off? To be bluntly honest I find your lack of gratitude and courtesy, let alone discretion, deplorable. Shame on you!

Paulo2 · 07-31-2016, 11:10 PM

Quote:

Originally Posted by gezley

Bulldozer FX-9590 8-core here. No freezes at all. Was on current for months before it went stable.

Excuse me, totally off-topic. My mother has an i5 (quad-core) notebook and booting Slackware
I see four Tux

. Do you see eight? Or there is a limit on how many Tux.