LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices



Reply
 
Search this Thread
Old 06-23-2013, 08:58 AM   #1
textillis
Member
 
Registered: May 2013
Location: Northern Rivers, NSW, Australia
Distribution: Slackware64-current, Mint Nadya
Posts: 299

Rep: Reputation: 2
No boot after editing vmlinuz symbolic link to point to 3.3.45 generic


(subject should read: 3.2.45 generic")

Can't get slack14 64-bit to boot after I changed the symbolic link that had been pointing to "huge-3.2.45" so that it now points to "generic-3.2.45".

How do I get inside slackware to tinker? and what tinkering is to be done?
do I change link back to "huge"?

(I have a usb start-up but when i use it i can't find any of my files; it's like a fresh install)

Thanks
(still bogged down in the peat-moss bog flats surrounding mount slackware)

Last edited by textillis; 06-23-2013 at 09:27 AM.
 
Old 06-23-2013, 09:25 AM   #2
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 2,135

Rep: Reputation: Disabled
The "generic" kernel contains very little in terms of storage drivers, so you'll need an initrd.

Boot from the DVD and follow the instructions on the boot screen for booting your installed system. Basically, you tell the "huge.s" kernel not to use the installation initrd and mount a hard drive partition as a root FS instead.

Once your system is booted, log in and run /usr/share/mkinitrd/mkinitrd_command_generator.sh. It will tell you what parameters to use with the mkinird command to generate an initrd with the right kernel modules.

Last edited by Ser Olmy; 06-23-2013 at 09:27 AM.
 
1 members found this post helpful.
Old 06-23-2013, 09:26 AM   #3
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,524

Rep: Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876
For getting in see http://docs.slackware.com/howtos:sla...oot_from_media

It looks like you have been updating your Slackware 14.0 install to the latest kernel (should be 3.2.45 NOT the 3.3.45 in your post).
Did you create an initrd.gz using mkinitrd before trying to reboot to the generic kernel?
If so, did you add an entry to /etc/lilo.conf?
If so, did you run lilo?

It you have the huge kernel in /boot, it is probably best to change the symlink back to pointing to the huge kernel and run lilo (after doing the chroot) to recover your ability to boot.
 
1 members found this post helpful.
Old 06-23-2013, 10:36 AM   #4
textillis
Member
 
Registered: May 2013
Location: Northern Rivers, NSW, Australia
Distribution: Slackware64-current, Mint Nadya
Posts: 299

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by allend View Post
For getting in see http://docs.slackware.com/howtos:sla...oot_from_media

It looks like you have been updating your Slackware 14.0 install to the latest kernel (should be 3.2.45 NOT the 3.3.45 in your post).
Did you create an initrd.gz using mkinitrd before trying to reboot to the generic kernel?
If so, did you add an entry to /etc/lilo.conf?
If so, did you run lilo?

It you have the huge kernel in /boot, it is probably best to change the symlink back to pointing to the huge kernel and run lilo (after doing the chroot) to recover your ability to boot.
I didn't install lilo when i installed slackware (grub2 on MBR picks up slackware after upgrade-grub in mint) but i'm beginning to suspect that the problem you've been helping me with (patchy gui) could stem from having installed slack AFTER installing Mint, and that I might be advised to go for fresh install of both, but this time, starting first with slack, installing lilo in MBR and when i come to install mint, installing grub2 in mint's /boot partition.

What do you think?

Last edited by textillis; 06-23-2013 at 10:54 AM.
 
Old 06-23-2013, 05:23 PM   #5
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,653
Blog Entries: 2

Rep: Reputation: 4097Reputation: 4097Reputation: 4097Reputation: 4097Reputation: 4097Reputation: 4097Reputation: 4097Reputation: 4097Reputation: 4097Reputation: 4097Reputation: 4097
I don't think that this is a problem with Lilo or Grub, but since you give us no clue at all which errors you get when you try to boot Slackware this is just a shot in the dark. Have you created an initrd, which is mandatory when using the generic kernel?
Which error messages do you get?
 
  


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
vmlinuz-generic-2.6.30.5 boot problem bgeddy Slackware 3 02-12-2010 04:18 PM
[SOLVED] How to user vmlinuz-generic instead of vmlinuz-huge-smp? cola Slackware 12 09-15-2009 02:54 PM
Any reason to change symbolic links in /boot with generic kernel? gibson79 Slackware 2 09-04-2009 10:24 AM
what are initrd.img-2.6.28-11-generic and vmlinuz-2.6.28-11-generic? karuna-bdc Linux - Newbie 11 07-17-2009 06:00 AM
Editing a symbolic link twallstr Linux - General 1 11-09-2005 03:39 PM


All times are GMT -5. The time now is 01:19 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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration