LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-04-2019, 08:44 AM   #1
karabot
LQ Newbie
 
Registered: Jan 2014
Posts: 10

Rep: Reputation: Disabled
Booting from Slack DVD hangs at /sbin/udevadm trigger --action=add


Hey guys,

I have an issue that recently started showing up. I hang from the while booting from the DVD also.
I keep hanging on
Code:
Triggering udev events: /sbin/udevadm trigger --action=add
I was able to get past it once this morning and was able to partition, format, and do the slow check with no errors. But when I was installing the packages it failed on a package.

My guess is I have a hardware issue. Do you guys have any ideas?

Cheers,
George
 
Old 01-04-2019, 12:12 PM   #2
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware, Devuan, Xubuntu
Posts: 1,295
Blog Entries: 3

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Requested for thread to be moved to Slackware board.
 
Old 01-05-2019, 08:49 AM   #3
karabot
LQ Newbie
 
Registered: Jan 2014
Posts: 10

Original Poster
Rep: Reputation: Disabled
Just an update, I am pretty sure it is hardware; I have installed archlinux and xubuntu and I see similar behavior. Mind you I can boot a lot more often as compare to Slack.
I guess I am due for a new (used) laptop

Cheers,
George
 
Old 01-05-2019, 08:58 AM   #4
Fred-1.2.13
Member
 
Registered: Jan 2006
Location: Midwest USA
Distribution: Started with Slackware - 3.0 1995 Kernel 1.2.13 - Now Slackware Current. Also some FreeBSD.
Posts: 124

Rep: Reputation: 59
I agree with your assessment of a hardware issue. Years ago (1997ish) I had a computer that I was setting up to use as a web server. It ran with no issues on Windows but would kernel panic when I tried to install Slackware.

I started checking and it turned out that a jumper on the motherboard was on the wrong set of pins, I can't remember the exact thing the jumper did now, but once I got it on the correct pins Slackware installed without error. (For the younger crowd... old school hardware had jumpers to select options where as now that is done in the BIOS)

You may want to check out your memory, if you have more than one memory card, try pulling one out, if you still have problems swap them in one at a time and see if you can nail it down.

Good luck!!

Last edited by Fred-1.2.13; 01-05-2019 at 09:10 AM.
 
1 members found this post helpful.
Old 01-05-2019, 10:30 AM   #5
karabot
LQ Newbie
 
Registered: Jan 2014
Posts: 10

Original Poster
Rep: Reputation: Disabled
hehe Fred, I remember these days too--I remember when buying a used PC I would install Linux and start recompiling the kernel to test RAM etc .

I just switched memory cards, as you suggested and I got the same behavior. I think its something on the MB that failed. I will try to find me an older compatible laptop to the one I have and I 'll cannibalize the old one .

Cheers,
George
 
Old 01-05-2019, 12:58 PM   #6
brodo
Member
 
Registered: Jan 2004
Location: Poland, Poznan
Distribution: Slackware current 32
Posts: 319

Rep: Reputation: 24
I used to have similar behavior on my Thinkpad T460 but now it's gone. I use current Slackware 32 bit.
It didn't always happen - maybe one third of booting processes were affected.
Several months ago the problem disappeared (newer kernel from curent?).

Last edited by brodo; 01-05-2019 at 12:59 PM.
 
Old 02-14-2019, 07:39 AM   #7
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,723
Blog Entries: 6

Rep: Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386
This just happened to me. I've been using 14.2 for several weeks without any problems, but today I couldn't get it to boot. It just hung on
Code:
 Triggering udev events /sbin/udevadm trigger --action=change
The keyboard was live but there were no consoles available other than the system console so I was stuck. ctrl-alt-del started a shutdown but it hung a long time on "Stopping udevd" and then stopped altogether on "Reboot" instead of actually rebooting. So I switched off manually.

Switched on again, booted LFS without any problems and then rebooted into Slackware. This time everything appeared to be normal and I couldn't find anything suspicious in the logs.

Can anyone explain this glitch?
 
Old 02-14-2019, 08:11 AM   #8
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware, Devuan, Xubuntu
Posts: 1,295
Blog Entries: 3

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
A hang on boot is very rare - and for me it is unheard of on any of my machines. OP suggested a hardware issue. Also this thread says similarly.

Do you use a generic kernel - have you tried huge as well?

Last edited by Lysander666; 02-14-2019 at 08:12 AM.
 
Old 02-14-2019, 09:48 AM   #9
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,723
Blog Entries: 6

Rep: Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386
Quote:
Originally Posted by Lysander666 View Post
A hang on boot is very rare - and for me it is unheard of on any of my machines. OP suggested a hardware issue. Also this thread says similarly.
That's using UnRAID, which I gather is some kind of container system. And the poster had altered the bios just before the problem manifested itself. That suggests a different kind of problem altogether.
Quote:
Do you use a generic kernel - have you tried huge as well?
Yes, I use generic and so far it has served me perfectly well. Right from my first Slackware boot, it loaded all the drivers I needed. This is the first time I have ever had a glitch at boot like this, though I have twice had a freeze in X.

I don't see any advantage in using the huge kernel other than the fact that you don't need an initrd. I was well past the initrd stage when this happened.

The last kernel message before the freeze, if it's relevant, was "Checking generic (a0000000 300000) vs hw (a0000000 10000000)". But I got exactly the same message in the current successful boot.
 
Old 02-14-2019, 11:53 AM   #10
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,723
Blog Entries: 6

Rep: Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386
Bah! I got another freeze while in X. I'm posting this out of LFS. I fscked the Slackware partition (nothing obviously wrong there), then mounted it and checked the logs. Nothing reported in any of them.
 
Old 02-15-2019, 02:09 PM   #11
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,213

Rep: Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575
Normally memory, power supply, or motherboard capacitor problems. The power supply has capacitors as well, and they can fail over time.
 
Old 02-15-2019, 02:22 PM   #12
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,723
Blog Entries: 6

Rep: Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386
I thought memory too. I'm going to be running LFS mostly over the next couple of weeks as there is a new release candidate to test out. If I see the same sort of thing there, it's hardware. If not, it's Slackware!
 
Old 02-15-2019, 10:32 PM   #13
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,213

Rep: Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575
The slackware installer comes with memtest; you can run that as well.
 
2 members found this post helpful.
Old 02-16-2019, 09:35 AM   #14
hazel
Senior Member
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 2,723
Blog Entries: 6

Rep: Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386Reputation: 1386
Using memtest is an excellent idea. However the memtest on the installation disk only works for mbr boots and I don't really want to switch my boot method back and forth. If you do that, especially at my age, sooner or later you are going to forget to switch back and you'll wreck something. There is an alternative version of memtest which does work with uefi and I have found a howto on installing it permanently. It isn't free software but there's a version of it that you can use free of charge. I can add it permanently to elilo.conf. In another thread, enorbet also recommended lmsensors so I will install that in Slack. Then I can check if anything's overheating.

But building the new LFS out of the existing one takes priority. Some of the builds are quite demanding so it will be a good test environment for the hardware too.
 
Old 02-16-2019, 06:10 PM   #15
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,213

Rep: Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575Reputation: 1575
Quote:
Originally Posted by hazel View Post
If you do that, especially at my age, sooner or later you are going to forget to switch back and you'll wreck something.
pfft. Like that's age related.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Updating hardware index /sbin/udevadm hwdb staus Slackware 1 07-22-2016 12:52 PM
Slackware 14.0 install hangs at udevadm jtdippold Slackware - Installation 2 03-30-2013 05:00 PM
Trigger jenkins build with URL trigger when using git? jonizen Linux - Server 1 10-14-2011 01:07 PM
[SOLVED] udevadm trigger is not permitted while udev is unconfigured bortbortresson Linux - Server 1 08-31-2011 03:09 PM
udev/udevadm trigger led to disks being unable to spin down for more than a second exscape Linux - Kernel 0 01-03-2010 09:23 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:21 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration