LinuxQuestions.org
Review your favorite Linux distribution.
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 10-09-2014, 06:44 AM   #1
zetrotrack000
Member
 
Registered: Dec 2011
Posts: 368

Rep: Reputation: Disabled
Boot Error End Trace


Hi
I have recently installed (first time) slackware 14.1 (64bit) with kernel 'huge'. During installaion, i selected 'full' option to install everything. However, right after installation, now slackware is giving "End Trace" error and laptop freezes. I know that this is not RAM problem as 3 other OSes (linux and win7) are installed and working perfectly and I have also checked the RAM with memtest86. Some posts suggest to check for video driver. Here is the output of lspci:
Code:
lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] (rev ff)
I have also tried to boot into single user mode by entering 'single' and 'init=1' and '1' and 'ro single' etc. in grub entry but no use.
As this is my first time with slackware and also system freezes at boot, i dont know how to confirm the error or how to fix this error on freezed system. Kindly help me to fix this error.
 
Old 10-09-2014, 07:43 AM   #2
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,013

Rep: Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684
That error doesn't give us much to work on. When you say "right after installation," does this mean right after the installer exits or upon you rebooting the first time? If it is when you're rebooting, how far along does the boot process get? A visual would help, which can be done by taking a picture with your cellphone or digital camera and uploading it to an image sharing site like http://imgur.com. I'd also bet that the error message you state is the last error, but there's probably at least one more mentioned before it (like showing where the trace started from).

EDIT: Didn't notice the title had "boot" in the name, which implies this is on the reboot.

Last edited by bassmadrigal; 10-09-2014 at 07:44 AM.
 
Old 10-09-2014, 08:42 AM   #3
zetrotrack000
Member
 
Registered: Dec 2011
Posts: 368

Original Poster
Rep: Reputation: Disabled
Yup, the error appears on every boot. Here is the image.
http://s27.postimg.org/bjwhafqrn/boot_error.jpg
 
Old 10-09-2014, 10:28 AM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,013

Rep: Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684
That site is blocked at my work, so someone else will have to take a look.
 
Old 10-09-2014, 11:01 AM   #5
zetrotrack000
Member
 
Registered: Dec 2011
Posts: 368

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bassmadrigal View Post
That site is blocked at my work, so someone else will have to take a look.
No Problem. Here is another link:
http://imgur.com/roXUZuf
 
Old 10-09-2014, 11:27 AM   #6
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,307
Blog Entries: 4

Rep: Reputation: Disabled
That's the end of a kernel panic trace. It looks like it's the classic unable to mount root FS (see mount_root, then mount_block_root, and then panic, reading up from the bottom). So your grub config is almost certainly the problem. If you post details, someone else will be able to help you.
 
Old 10-09-2014, 12:49 PM   #7
zetrotrack000
Member
 
Registered: Dec 2011
Posts: 368

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by 55020 View Post
So your grub config is almost certainly the problem. If you post details, someone else will be able to help you.
During installaion, I did not install grub (b/c arch is my primary os and i dont want to mess up its grub), rather I have updated my arch's grub and it detected slackware.The arch linux puts grub.cfg at /boot/grub and here is the relevant entry:
Code:
menuentry 'Slackware Linux (Slackware 14.1) (on /dev/sda8)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-846954c8-231f-484f-8bc8-62be6df15820' {
	insmod part_msdos 
	insmod ext2
	set root='hd0,msdos8'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8  846954c8-231f-484f-8bc8-62be6df15820
	else
	  search --no-floppy --fs-uuid --set=root 846954c8-231f-484f-8bc8-62be6df15820
	fi
	linux /boot/vmlinuz-generic-3.10.17 root=/dev/sda8
}
 
Old 10-09-2014, 12:51 PM   #8
zetrotrack000
Member
 
Registered: Dec 2011
Posts: 368

Original Poster
Rep: Reputation: Disabled
This is my 100th post. First time ever crossed 100 on any forum. Congratulations to myself
 
Old 10-09-2014, 12:54 PM   #9
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,013

Rep: Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684
It's been a long time since I dual booted between multiple linux distros, so I may be off on this and I haven't used grub in over 10 years, so take any advice with a grain of salt and lots of Google searching.

With lilo, you need to have both kernels available to the command before running it. So, you can either copy the Slackware kernel to the /boot folder of your main OS (whatever is set to your boot drive), or mount the Slackware drive somewhere (maybe /mnt/slackware) and provide that image location to lilo (/mnt/slackware/boot/vmlinuz), and then have the proper root devices for each distro, running lilo will then work properly. Keep in mind, you should only do this from one distro.

As for grub, I'd assume it's similar, but as I said before, it's been a LONG time since I've run it, and I wasn't very knowledgeable back then (my "knowledge" is still questionable).

If you boot off the disk, you're able to use it as a rescue disc to see if it is an actual kernel problem (doubtful, since there's not really any brand spanking new hard drive controllers that wouldn't have at least some form of support in the default kernel) or if it is from not loading the right kernel. When you boot off the disc, instead of hitting Enter when the ISOLINUX screen comes up you can type the following, replacing /dev/sda1 with the root drive of the slackware install.

Code:
huge.s root=/dev/sda1 rdinit= ro
This should get you into a fully running Slackware system.

Last edited by bassmadrigal; 10-09-2014 at 12:59 PM.
 
Old 10-09-2014, 01:01 PM   #10
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,013

Rep: Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684Reputation: 3684
I originally had this as an edit, but I wanted to make sure you read it in case you already viewed my response.

After looking at your follow-up post, it seems that Arch found the generic kernel for Slackware which has most hardware support built as modules and not into the kernel. This is quite different from the huge kernel, since that has almost everything built in. If you wanted to keep the generic kernel, you'd need to build an initrd from within Slackware and add that to your grub (no clue how and I'm too lazy to research). Or you could copy the vmlinuz-huge-3.10.17 kernel from Slackware's /boot to Arch's /boot and change the entry in grub to that, followed by running whatever you need to run in grub to update the boot.
 
Old 10-09-2014, 04:18 PM   #11
zetrotrack000
Member
 
Registered: Dec 2011
Posts: 368

Original Poster
Rep: Reputation: Disabled
Problem solved
in /boot/grub/grub.cfg
I have noticed that the vmlinuz is vmlinuz-generic-3.10.7. I changed it to vmlinuz-huge-3.10.7. Now system is booting fine. Thanks everyone
 
Old 02-17-2015, 01:28 PM   #12
Rita G.
Member
 
Registered: Jan 2008
Posts: 135

Rep: Reputation: 15
Quote:
Originally Posted by zetrotrack000 View Post
I have noticed that the vmlinuz is vmlinuz-generic-3.10.7. I changed it to vmlinuz-huge-3.10.7.
wow! thanks for this! it just fixed a new install for me; was about to start all over!
 
Old 05-10-2017, 08:20 PM   #13
brainout
LQ Newbie
 
Registered: Aug 2012
Location: near Houston
Distribution: Not sure yet, am overwhelmed
Posts: 19

Rep: Reputation: Disabled
Update on 'End Trace' error causes

I just had the same error the guy above describes, but with respect to an old fullmonty PCLinuxOS distro I was experimenting on. Since I have 15 Windows machines and I never install Linux to hard drives but instead tell the installer to install to an external hard drive or stick, I got the End Trace cuz I plugged a stick I'd installed using one older laptop into a much newer one.

Kernel panic thus avoided, by plugging the stick back into an older (not the same) machine.

Difference was nVidia and other things (the newer machine was Dell Lat 6530, the older ones are D630, 6510, 6410, etc).

So don't panic, just try a different machine for your distro...
 
  


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
insllation of gives trace/cmu-trace.cc:1531:9: error: stray \342 in program error rakeshpanchiwala Linux - Newbie 17 04-26-2013 01:28 AM
Sir, While installing ns2.34 on fedora 16 got the error : trace/cmu-trace.cc 1327:22 jeevanpinto Linux - Newbie 2 06-28-2012 03:35 AM
end trace error mistertylersmith Linux - Newbie 1 02-12-2009 09:55 AM
How to trace and disable the HTTP TRACE method in Apache 1.3.33 with FreeBSD? SomnathG Linux - Security 1 11-11-2008 09:41 AM
Sata Harddisk gives warnings on boot witch end up with error (it works but it's slow) tunez Linux - Hardware 4 02-16-2008 09:05 AM

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

All times are GMT -5. The time now is 02:44 PM.

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