LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
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-25-2014, 01:41 PM   #16
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled

Markus why you dont put your Root lvm path on LILO root option

mine: root = dev/lvfelix/root

yours: root: dev/sda5

:s
 
Old 01-25-2014, 01:46 PM   #17
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Well, I don't use lvm

That's the reason why I can't help with lvm, I don't have any experience.

I posted the part of my lilo.conf to show you how I use the huge kernel in a case of kernel-panic with the generic kernel.

Markus
 
Old 01-25-2014, 01:52 PM   #18
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
i get it
 
Old 01-25-2014, 05:32 PM   #19
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
What is the output of
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh
?
 
Old 01-25-2014, 08:04 PM   #20
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
Code:
mkinitrd -c -k 3.2.29-smp -f ext4 -r /dev/lvfelix/root -m mbcache:jbd2:ext4 -L -u -o /boot/initrd.gz
Attached Images
File Type: png command generator.PNG (4.4 KB, 7 views)
 
Old 01-26-2014, 05:45 AM   #21
yenn
Member
 
Registered: Jan 2011
Location: Czech Republic
Distribution: Slackware, Gentoo
Posts: 153

Rep: Reputation: 21
Quote:
Originally Posted by fjur94 View Post
Markus why you dont put your Root lvm path on LILO root option

mine: root = dev/lvfelix/root
Correct. Mine working lilo.conf for LVM

Code:
image = /boot/vmlinuz
root = /dev/cryptvg/root
initrd = /boot/initrd.gz
label = Slackware
read-only
Quote:
Originally Posted by fjur94 View Post
Code:
mkinitrd -c -k 3.2.29-smp -f ext4 -r /dev/lvfelix/root -m mbcache:jbd2:ext4 -L -u -o /boot/initrd.gz
As far as I can see, mkinitrd command looks correct. Although question is, when did you execute this command. After installation? After reboot with install CD? Or within actual chroot?

If you execute this after installation, it will write initrd.gz to /boot of Slackware install CD (it will disappear after reboot). You want to execute it within your newly installed linux, so Lilo can pick it up.

I assume that you did full install or have at least on kernel in /boot. Just to make sure, could you mount your boot partition and see if kernel is actually there?

Look what is mounted right now (just to get clear picture what's going on).
Code:
$ mount
If real boot partition isn't already mounted, do it.
Code:
$ mount /dev/sda1 /mnt/boot
$ ls -l /mnt/boot
And if it doesn't list any files, then you have to install kernel package again. If there are files, then you can move to chrooting your system and re-run lilo.

I'll stop now and wait for output of commands above, then we can move further.
 
Old 01-26-2014, 09:26 AM   #22
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
i execute the mkinitrd command after installation without rebooting.

(/mnt/boot) didnt exist, so i created it.

Pictures shows (mount) and (ls -l /mnt/boot)

Note: i have not rebooted after i did the installation.
Attached Images
File Type: png mount.PNG (29.1 KB, 5 views)
File Type: png ls -l part 1.PNG (63.9 KB, 4 views)
File Type: png ls -l part 2.PNG (10.5 KB, 4 views)
 
Old 01-26-2014, 10:31 AM   #23
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Quote:
Originally Posted by fjur94 View Post
i execute the mkinitrd command after installation without rebooting.

(/mnt/boot) didnt exist, so i created it.

Pictures shows (mount) and (ls -l /mnt/boot)

Note: i have not rebooted after i did the installation.
Well, thanks to yenn for asking

Your approach seems quite odd. I'd strongly recommend that you put the huge kernel into your lilo.conf and boot with it (don't forget to rerun lilo). Then, when Slackware with the huge kernel is running, you may create the initrd, rerun lilo again and reboot then with the generic kernel.

Thanks to Richard Cranium for pointing me to this. I found this manual from Alien Bob, hope this helps.

Markus

Last edited by markush; 01-26-2014 at 10:57 AM.
 
Old 01-26-2014, 10:44 AM   #24
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
Quote:
Originally Posted by markush View Post
Well, thanks to yenn for asking

Your approach seems quite odd. I'd strongly recommend that you put the huge kernel into your lilo.conf and boot with it (don't forget to rerun lilo). Then, when Slackware with the huge kernel is running, you may create the initrd, rerun lilo again and reboot then with the generic kernel.

Markus
Not recommended. You must have an initrd in order to have your root partition on a logical volume.

I'm running a 14.0 install on a virtual machine right now to see what state the installer should be in when it finishes.

Last edited by Richard Cranium; 01-26-2014 at 10:46 AM.
 
Old 01-26-2014, 11:53 AM   #25
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by markush View Post
Thanks to Richard Cranium for pointing me to this. I found this manual from Alien Bob, hope this helps.
I did the same that the guide says and nothing.

Last edited by fjur94; 01-26-2014 at 11:55 AM.
 
Old 01-26-2014, 12:14 PM   #26
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
I recommend that you skip installing lilo as part of running setup. Then do the following immediately after setup exits:
Code:
mount -R /proc /mnt/proc
mount -R /sys /mnt/sys
mount -R /dev /mnt/dev
chroot /mnt
$(/usr/share/mkinitrd/mkinitrd_command_generator.sh -r )
liloconfig
While in liloconfig, select the Simple menu choice.
Select standard for "CONFIGURE LILO TO USE FRAME BUFFER CONSOLE?"
No optional parameters.
Select "No" for "Use UTF-8 TEXT CONSOLE?"
Select MBR for "SELECT LILO TARGET LOCATION"

You'll get a message indicating that lilo didn't install. Press enter.

Then run...
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh -l /boot/vmlinuz-generic-smp-3.2.29-smp >>/etc/lilo.conf
Then use your favorite editor to edit /etc/lilo.conf; vi, emacs, nano, or whatever you would use when logged into a console. Delete lines 62 to 67 inclusive. Save the file and exit.

Next, run...
Code:
lilo
...which will give a warning or two. Then run...
Code:
exit
to get out of the chroot followed by ctrl-alt-delete to reboot.
 
Old 01-26-2014, 04:32 PM   #27
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
62 to 67, even the 'image' option ?
Attached Images
File Type: png sure..PNG (43.4 KB, 8 views)
 
Old 01-26-2014, 05:13 PM   #28
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
Don't know why ours are that different, but from the screen shot you provided, it's lines 59-64.
 
Old 01-26-2014, 07:07 PM   #29
fjur94
LQ Newbie
 
Registered: Jan 2014
Posts: 29

Original Poster
Rep: Reputation: Disabled
I made a video because this is unexplainable

see link below
http://www.youtube.com/watch?v=qPFkQA4lkSc
Attached Images
File Type: png conio.PNG (23.1 KB, 7 views)

Last edited by fjur94; 01-26-2014 at 07:08 PM.
 
Old 01-26-2014, 07:15 PM   #30
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,494

Rep: Reputation: 437Reputation: 437Reputation: 437Reputation: 437Reputation: 437
I don't know if there is difference between selecting <Cancel> or actually using the Exit menu option to leave setup. I used the exit menu option.

Other than that, I'd have to run the installer under VM player. My tests were run in a VM running under libvirt.
 
  


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
Kernel panic - not syncing: VFS: unable to mount root fs on uknown-block(253,0) fjur94 Slackware 1 01-22-2014 06:05 PM
kernel panic - not syncing:vfs:unable to mount root fs on unknown-block (8.2) raleeha VectorLinux 6 04-21-2011 02:48 AM
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1) anjanesh Ubuntu 9 01-27-2011 12:00 PM
kernel panic - not syncing: VFS unable to mount root fs on unknown-block(8,3) AllShk Linux - Newbie 3 11-28-2009 12:56 AM
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block akaUr Linux - Kernel 10 06-18-2009 06:59 AM


All times are GMT -5. The time now is 03:36 PM.

Main Menu
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