OpenVZ Forum


Home » General » Support » Kernel used with slackware?
Kernel used with slackware? [message #32877] Sun, 07 September 2008 00:11 Go to next message
penguin_2007 is currently offline  penguin_2007
Messages: 5
Registered: September 2008
Location: Japan
Junior Member
Hi all,
Please teach kernel used with slackware12.0 which to be used.
↓ It doesn't understand well though it traces and it looks for the
link from following URL.
http://wiki.openvz.org/Download/kernel
Re: Kernel used with slackware? [message #32883 is a reply to message #32877] Sun, 07 September 2008 08:50 Go to previous messageGo to next message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member

Hi,

on http://www.slackware.com/announce/12.1.php shows:

[...]
Here are some of the advanced features of Slackware 12.1:

- Runs the 2.6.24.5 version of the Linux kernel from ftp.kernel.org.
Also included is a kernel patched with Speakup to support speech
synthesizers providing access to Linux for the visually impaired
community. The 2.6.x kernel series has matured into a stable
kernel, and provides reliable performance for your desktop or
your production server.
[...]

So you can try the 2.6.24er (devel) OpenVZ patch and built a own OpenVZ Kernel (-> http://wiki.openvz.org/Download/kernel/2.6.24/2.6.24-ovz005. 1)



Re: Kernel used with slackware? [message #32895 is a reply to message #32883] Mon, 08 September 2008 01:02 Go to previous messageGo to next message
penguin_2007 is currently offline  penguin_2007
Messages: 5
Registered: September 2008
Location: Japan
Junior Member
Dir curx
Thank you for the reply.
The domination of version 12.1 has been understood well.
The patch taught to the kernel source code is restructured, and it
applies, and the system is restructured for openvz.
Re: Kernel used with slackware? [message #32980 is a reply to message #32895] Sun, 14 September 2008 03:33 Go to previous messageGo to next message
penguin_2007 is currently offline  penguin_2007
Messages: 5
Registered: September 2008
Location: Japan
Junior Member
Referring to given information
Though it installed as follows
Please teach the method of settlement where the problem occurs
variously.

※ error messages
VFS: Cannot open root device "803" or unknown-block(8,3)
Please append a correct "root=" boot option; here are the available partitions;
Kernel panic - non syncing: VFS: Unable to mount root fs on unknown-block(8,3)

# lilo -v
Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/slack.bmp
Calling map_insert_file

Boot image: /boot/vmlinuz-huge-smp-2.6.24.5-smp
Added Linux *

Boot image: /boot/vmlinuz-2.6.24.8-union
Added Linux-union

Boot image: /boot/vmlinuz-2.6.24-ovz
Added Linux-ovz

Writing boot sector.
/boot/boot.0800 exists - no boot sector backup copy made.
One warning was issued.

※ Procedure of installation
# tar vjxf linux-2.6.24.tar.bz2
# cd linux-2.6.24
# gzip -dc patch-ovz005.1-combined.gz | patch -p1
# cp kernel-2.6.24-i686.config.ovz .config
# make oldconfig
# ln -sf linux-2.6.24 linux
# cd /usr/src/linux
# make
# make bzImage
# make modules
# make modules_install
# cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.6.24-ovz
# cp /usr/src/linux/System.map /boot/System.map-2.6.24-ovz
# ln -sf /boot/System.map-2.6.24-ovz /boot/System.map
# cp /usr/src/linux/.config /boot/config-2.6.24-ovz
# ln -sf /boot/config-2.6.24-ovz /boot/config
Edit of lilo
# lilo -L
# shutdown -r now

※ Spec of system
CPU : AMD Athlon(tm)64 Processor 35000+
Memory : DDR 1GHz
HDD : SATA 200G
OS : Slackware 12.1
.config : kernel-2.6.24-i686.config.ovz
patch : patch-ovz005.1-combined.gz
LILO : version 22.8
Re: Kernel used with slackware? [message #32981 is a reply to message #32980] Sun, 14 September 2008 09:36 Go to previous messageGo to next message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member

Have you built a initrd as well ?

Plz show your /etc/lilo.conf.

Re: Kernel used with slackware? [message #32982 is a reply to message #32895] Sun, 14 September 2008 10:05 Go to previous messageGo to next message
penguin_2007 is currently offline  penguin_2007
Messages: 5
Registered: September 2008
Location: Japan
Junior Member
Thank you for the reply ..curx.. again.
No, initrd is not Bilded.
It did not know even the thing that initrd had to be Bilded.......
Lilo.conf and the relation file are posted.
It asks suitably.

# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-huge-smp-2.6.24.5-smp
root = /dev/sda3
label = Linux
read-only
image = /boot/vmlinuz-2.6.24.8-union
root = /dev/sda3
label = Linux-union
read-only
image = /boot/vmlinuz-2.6.24-ovz
root = /dev/sda3
label = Linux-ovz
read-only
# Linux bootable partition config ends

# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 9614148 2898764 6227008 32% /
/dev/sda1 474440 32933 417010 8% /boot
tmpfs 645268 0 645268 0% /dev/shm
/dev/sdb1 511696 281768 229928 56% /mnt/usb

# cat /etc/fstab
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext3 defaults 1 1
/dev/sda1 /boot ext2 defaults 1 2
/dev/cdrom /mnt/cdrom auto noauto,owner,ro,users 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,users 0 0
/dev/sdb1 /mnt/usb auto noauto,owner,users 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
Re: Kernel used with slackware? [message #32983 is a reply to message #32982] Sun, 14 September 2008 13:21 Go to previous message
penguin_2007 is currently offline  penguin_2007
Messages: 5
Registered: September 2008
Location: Japan
Junior Member
Hi curx and All
It reactivates, and was it thought the situation to be an improvement, and did the problem occur here, is not sda3 still recognized, and is it good the examination of mkinitrd, and making like this, and when solving it very?
# cd /root
# mkinitrd -c -m scsi_mod:sg:sd_mod:libata:sata_nv -r /dev/sda3 -k 2.6.24 -o /boot/initrd-2.6.24.img

※ Excerpt lilo.conf
image = /boot/vmlinuz-2.6.24-ovz
initrd=/boot/initrd-2.6.24.img
root = /dev/sda3
label = Linux-ovz
read-only
# Linux bootable partition config ends

※ Problem
mount : mounting /dev/sda3 on rootdev(or not mounted)
Trouble ahead
You can try to fix it. Type 'exit' when things are done.

※ Input exit
/ bin/sh : can't access tty; job control turned off
/ $ exit
initrd-2.6.24.img : exiting
switch -root:bad newroot /mnt
kernel panic -not syncing : Attempted to kill init!
Previous Topic: KEEPALIVE: Socket operation error
Next Topic: Supported OS's
Goto Forum:
  


Current Time: Thu Oct 17 16:46:01 GMT 2024

Total time taken to generate the page: 0.05468 seconds