LinuxQuestions.org
Help answer threads with 0 replies.
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-20-2010, 06:54 PM   #1
dc_eros
Member
 
Registered: Nov 2006
Distribution: Slackware
Posts: 294

Rep: Reputation: 39
Upgrade to Current - Crashes After Reboot


First:

I upgraded my slackware 13.0 last night (Philippine time) to -current. I just download the while current tree (except for source) and copied to my home dir, then do the slackpkg commands.

#1 Added a mirror to my home directory pointing the slackware-current tree.
#2 slackpkg update
#3 slackpkg install-new
#4 slackpkg upgrade-all
#5 slackpkg clean-system
#6 lilo was configured
#7 reboot

It successfully upgraded. Although I'm aware that I have installed openchrome driver and drm kernel module when it was slackware 13.0.

After a reboot, it crashes in between the boot time, if I was not mistaken, I read ACPI something on the bottom of the console, then the screen flickers and goes blank. It locks up there.

By the way, it is a laptop with VIA chipset on it.

(Using the Slackware 13.0 DVD, I booted using hugesmp.s root=/dev/sda3 rdinit= ro for the rescue.)

Trying to fix it by myself (no internet at home) I tried to look at /var/log/messages and cannot find what is the cause (newbie mode). I also tried to disable some services such as hald, httpd, mysqld, bluetooth, wicd, wireless, the old kernel and some others at /etc/rc.d/ by removing the execute bit.

After a restart, still the problem exists.

Now, I finally backup the whole home dir, moved to home-bak and decided to install the fresh slackware-current instead.

Second:

I used the 13.0 installer, then setup slackware using the pre-mounted directory containing the slackware-current tree. I only deleted the files except for home-bak and not reformat the drive.

It actually installs, but after the reboot (using the new 2.6.32.3 kernel), still the problem persists.

Or maybe I missed some steps. I searched the forum and it talks about an initrd.gz but I'm not sure. Any guide please?

Thanks in advance

EDIT: By the way, I'm just in a hurry that I immediately posted this. I'm currently searching and found similar threads. (I also read about the FAQ creation thread ).

Hope this would not bother you guys.

Last edited by dc_eros; 01-20-2010 at 07:47 PM.
 
Old 01-20-2010, 07:49 PM   #2
Andersen
Member
 
Registered: Dec 2008
Distribution: Slackware
Posts: 176

Rep: Reputation: 72
Not sure, but appending "acpi=off noapic" to /etc/lilo.conf maybe can solve the problem.
 
Old 01-20-2010, 08:22 PM   #3
r4lly
LQ Newbie
 
Registered: Oct 2009
Location: under the bridge
Distribution: linuxmint xfce
Posts: 20

Rep: Reputation: 8
Maybe the problems in your hardware compatibility , there's a lot changes regarding new kernels, i don't know for sure but you can check that first.
Hope that will help and sorry for bad english
 
Old 01-20-2010, 08:32 PM   #4
dc_eros
Member
 
Registered: Nov 2006
Distribution: Slackware
Posts: 294

Original Poster
Rep: Reputation: 39
It could be that I have /dev/dh* stuff on my fstab, but hey, I'm using /dev/sda as hard disk and DVD-ROM is auto mounted and is commented out at fstab. The kernel is pointing still to the vmlinuz and its initrd.gz. I don't remember that I've changed the link to 2.6.32.3 smp.

Maybe that is the problem.

But, I have the same system install in the office, on VMWare and the same steps I did was the same. Seeing the upgrade went flawlessly on that system, I upgraded mine at home. Hmmm... And I don't even bother changing /dev/hd* to /dev/sd* in my test machine because it just work out of the box, even lilo works!

Maybe, I will just try as much information I'll find in this forum as possible and try it at home.

Thanks for the reply.
 
Old 01-21-2010, 06:37 PM   #5
dc_eros
Member
 
Registered: Nov 2006
Distribution: Slackware
Posts: 294

Original Poster
Rep: Reputation: 39
I tried to fix it at home, but still no luck. But here are some information that may suggest what the problem is as I'm trying to troubleshoot it myself (no internet, no other PC, no manuals except for a Slackware 13.0 DVD and the slackware-current tree on a backup directory.)

1. When I booted normally, I closely looked at the console and it crashed right after it is saying about "Freeing init ???????".

2. I tried to look at /var/log by using the Slackware DVD booting by "hugesmp.s root=/dev/sda3 rdinit= ro" and examined /var/log/messages, dmesg, debug, etc. I found out that there is nothing reflected about the normal kernel, the time indicates that the log was created / modified when I tried to rescue the installed slackware using the kernel from the Slackware DVD. Nothing is reflected when I booted using the normal kernel 2.6.32.3-smp. It suggests that when I boot using the normal kernel, it does not have a chance to log anything (maybe I guess).

3. I checked for any instances of /dev/hd* on lilo.conf and fstab and there's nothing because my laptop uses /dev/sda from the start and the CDROM is just automounted.

4. The default kernel I'm using is vmlinuz-huge-smp-2.6.32.3-smp. When I tried to use the other kernel (after saving changes to lilo) like the non-smp huge kernel, still the problem occurs. I tried to use the generic kernel and created and initrd, using the exact steps stated on the README, still the same problem.

5. The installation is a full installation and ext4 is the filesystem. I did a fresh install of the slackware-current, not upgrade (because my last upgrade did not work [same problem as above], so I decided it to be a fresh install). When I install it, I used the 13.0 installer and just point the source to the slackware-current directory.

6. Last, I downloaded the slackware-current tree using wget. While it was downloading, I waited to the point when it is downloading the source directory (slackware-current/source/*) thinking the it will still work without it and then canceled the download. I bring the whole tree (unfinished download but all packages in slackware-current/slackware/* are there) and use it for the installation.

Now, I'm currently downloading the slackware-current (re-download actually) using rsync. Hope it will fix it. If you guys can spot the problem, please let me know, I'm just a newbie

TIA
 
Old 01-21-2010, 07:30 PM   #6
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 53
I haven't installed 13 yet, neither -current, but did you try disable framebuffer during boot to see if the screen doesn't go blank?
You've to pass vga=normal parameter in lilo's prompt.
 
Old 01-21-2010, 07:53 PM   #7
dc_eros
Member
 
Registered: Nov 2006
Distribution: Slackware
Posts: 294

Original Poster
Rep: Reputation: 39
Okay I'll try that at home. The screen actually loads with small fonts (vga above normal - don't know the code 733 or something) and tries to boot, maybe after it scrolls for three page screen of text, then it goes blank.

Have to try that. I have to compress the slackware-current directory since my flash drive can only fit 3.7GB but the whole directory size is 3.79GB.
 
Old 01-21-2010, 10:19 PM   #8
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 53
Then it's actually loading framebuffer correctly, don't think my suggestion will help.
 
Old 01-24-2010, 06:43 PM   #9
dc_eros
Member
 
Registered: Nov 2006
Distribution: Slackware
Posts: 294

Original Poster
Rep: Reputation: 39
I think 2.6.32.3 kernel does not work for my hardware, that's why I used the old and unpatched 2.6.29.6 kernel. But the rest are in -current. However, there was an update last Jan 24, so I think I'm going to break my system once again.

 
Old 01-31-2010, 11:41 PM   #10
r4lly
LQ Newbie
 
Registered: Oct 2009
Location: under the bridge
Distribution: linuxmint xfce
Posts: 20

Rep: Reputation: 8
Smile

Glad you can trough that and hope your experiment successful , but in my opinion upgrade being made if only you actually needed , maybe for security issue or you have a really a new hardware and didn't work properly

Hope will help

Regards

R4
 
  


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
mplayerplug-in crashes in current Petri Kaukasoina Slackware 1 06-03-2009 04:19 PM
DISCUSSION: Upgrade to Slackware -current without a -current CD truthfatal LinuxAnswers Discussion 0 09-19-2006 01:42 PM
What first upgrade kernel or upgrade slack 10.0 to current Kelean Slackware 7 01-16-2005 06:54 PM
Slackware-current Xorg 6.8.1 crashes SirJohnWackness Slackware 20 11-26-2004 09:09 AM
shutdown and reboot x crashes goneaway Linux - Newbie 2 01-29-2002 11:49 AM

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

All times are GMT -5. The time now is 05:03 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
Open Source Consulting | Domain Registration