LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
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-04-2010, 04:23 AM   #16
JokerBoy
Member
 
Registered: Sep 2009
Posts: 140

Rep: Reputation: 24

# ls /boot -l
# cat /etc/lilo.conf
# ls /var/log/packages | grep kernel

and copy/paste the output here

Code:
End of the output from the Linux kernel build system.
Installation successful
from http://pastebin.com/m4fe4b3cb

Last edited by JokerBoy; 01-04-2010 at 04:24 AM.
 
Old 01-04-2010, 04:54 AM   #17
wubai
Member
 
Registered: Dec 2009
Posts: 103

Original Poster
Rep: Reputation: 20
Hi,

root@sl:~# ls /boot -l
总计 10816
-rw-r--r-- 1 root root 512 2009-12-18 04:30 boot.0812
-rw-r--r-- 1 root root 512 2009-12-19 00:11 boot.0820
-rw-r--r-- 1 root root 281 2009-12-18 04:34 boot_message.txt
lrwxrwxrwx 1 root root 20 2009-12-18 04:18 config -> config-huge-2.6.29.6
-rw-r--r-- 1 root root 90657 2009-08-17 15:48 config-generic-2.6.29.6
-rw-r--r-- 1 root root 90685 2009-08-18 00:59 config-huge-2.6.29.6
-rw-r--r-- 1 root root 5040 2009-02-27 19:49 diag1.img
-rw-r--r-- 1 root root 17932 2009-02-27 19:49 diag2.img
-rw------- 1 root root 15872 2009-12-20 01:18 map
lrwxrwxrwx 1 root root 37 2009-12-18 04:18 README.initrd -> /usr/doc/mkinitrd-1.3.4/README.initrd
-rw-r--r-- 1 root root 17318 2008-12-09 08:56 slack.bmp
lrwxrwxrwx 1 root root 24 2009-12-18 04:18 System.map -> System.map-huge-2.6.29.6
-rw-r--r-- 1 root root 1292554 2009-08-17 15:48 System.map-generic-2.6.29.6
-rw-r--r-- 1 root root 1878226 2009-08-18 00:59 System.map-huge-2.6.29.6
lrwxrwxrwx 1 root root 21 2009-12-18 04:18 vmlinuz -> vmlinuz-huge-2.6.29.6
-rw-r--r-- 1 root root 2629312 2009-08-17 15:48 vmlinuz-generic-2.6.29.6
-rw-r--r-- 1 root root 5004096 2009-08-18 00:59 vmlinuz-huge-2.6.29.6
root@sl:~#


root@sl:~# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/root
compact # faster, but won't work on all systems.
# Standard menu.
message = /boot/boot_message.txt

# Append any additional kernel parameters:
append=" vt.default_utf8=0"
#prompt
#timeout = 5
# 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
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sdb2
label = Slackware
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

root@sl:~# ls /var/log/packages | grep kernel
kernel-firmware-2.6.29.6-noarch-2
kernel-generic-2.6.29.6-x86_64-2
kernel-headers-2.6.29.6-x86-2
kernel-huge-2.6.29.6-x86_64-2
kernel-modules-2.6.29.6-x86_64-2
kernel-source-2.6.29.6-noarch-2
root@sl:~#

 
Old 01-04-2010, 05:04 AM   #18
JokerBoy
Member
 
Registered: Sep 2009
Posts: 140

Rep: Reputation: 24
you are using "vmlinuz-huge-2.6.29.6"

btw,

Code:
Tue Dec 8 20:44:44 UTC 2009
a/kernel-firmware-2.6.29.6-noarch-3.txz: Rebuilt.
a/kernel-generic-2.6.29.6-x86_64-3.txz: Rebuilt.
       Patched a bug (CVE-2009-1298) where oversized IP packets cause a
       NULL pointer dereference and immediate hang.
       For more information, see:
       http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1298
       http://lkml.org/lkml/2009/11/25/104
       (* Security fix *)
a/kernel-huge-2.6.29.6-x86_64-3.txz: Rebuilt.
       Patched CVE-2009-1298.
       (* Security fix *)
a/kernel-modules-2.6.29.6-x86_64-3.txz: Rebuilt.
d/kernel-headers-2.6.29.6-x86-3.txz: Rebuilt.
k/kernel-source-2.6.29.6-noarch-3.txz: Rebuilt.
       Patched CVE-2009-1298, and included the diff in /usr/src/linux-2.6.29.6.
       (* Security fix *)
but this doesn't matter, in any case try to update your kernel and then try again, maybe you did something to the current kernel source ..

did you did a full install or a custom install of slackware?

from what i see, there's nothing wrong
 
Old 01-04-2010, 05:43 AM   #19
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
Use the generic kernel. Then recompile vbox.
 
Old 01-04-2010, 05:51 AM   #20
wubai
Member
 
Registered: Dec 2009
Posts: 103

Original Poster
Rep: Reputation: 20
Quote:
Originally Posted by ~sHyLoCk~ View Post
Use the generic kernel. Then recompile vbox.
Is it enough to change the link of vmlinuz to generic kernel for using the generic kernel and reboot? or i need do something more ?
 
Old 01-04-2010, 05:54 AM   #21
JokerBoy
Member
 
Registered: Sep 2009
Posts: 140

Rep: Reputation: 24
# rm /boot/vmlinuz
# rm /boot/System.map
# ln -s /boot/vmlinuz-generic-2.6.29.6 /boot/vmlinuz
# ln -s /boot/System.map-generic-2.6.29.6 /boot/System.map
# lilo


Last edited by JokerBoy; 01-04-2010 at 06:09 AM.
 
Old 01-04-2010, 06:04 AM   #22
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
Quote:
Originally Posted by wubai View Post
Is it enough to change the link of vmlinuz to generic kernel for using the generic kernel and reboot? or i need do something more ?
You don't even need to change the vmlinuz link. If you want to keep the links as it is just create another entry or edit the existing lilo entry [since you may want to comeback to this kernel.], pointing the kernel to /boot/vmlinuz-generic-2.6.29.6
Quote:
Originally Posted by Jokerboy
# rm /boot/vmlinuz
# rm /boot/System.map
# ln -s /boot/vmlinuz /boot/vmlinuz-generic-2.6.29.6
# ln -s /boot/System.map /boot/System.map-generic-2.6.29.6
# lilo
Won't he need an initrd? :\
 
Old 01-04-2010, 06:08 AM   #23
wubai
Member
 
Registered: Dec 2009
Posts: 103

Original Poster
Rep: Reputation: 20
@JokerBoy

are you sure about what you taught me ?

coz for what i leaned i think it should be like this to chnage the link ,

# ln -s /boot/vmlinuz-generic-2.6.29.6 /boot/vmlinuz

or i am wrong ?
 
Old 01-04-2010, 06:08 AM   #24
JokerBoy
Member
 
Registered: Sep 2009
Posts: 140

Rep: Reputation: 24
this i don't know, i only use kernel-huge for the first boot, then i build a custom kernel

yes, my bad. i edited my post

Last edited by JokerBoy; 01-04-2010 at 06:10 AM.
 
Old 01-04-2010, 06:17 AM   #25
wubai
Member
 
Registered: Dec 2009
Posts: 103

Original Poster
Rep: Reputation: 20
@ ~sHyLoCk~
Quote:
You don't even need to change the vmlinuz link. If you want to keep the links as it is just create another entry or edit the existing lilo entry [since you may want to comeback to this kernel.], pointing the kernel to /boot/vmlinuz-generic-2.6.29.6
Quote:
Originally Posted by Jokerboy
# rm /boot/vmlinuz
# rm /boot/System.map
# ln -s /boot/vmlinuz /boot/vmlinuz-generic-2.6.29.6
# ln -s /boot/System.map /boot/System.map-generic-2.6.29.6
# lilo
Won't he need an initrd? :\\
I think you might be right, i remembered when I tried to installed slackware64 on LVM , i read some info that generic seems need a initrd

and i change the link back, in the /boot dir, ln -s vmlinuz-huge-2.6.29.6 vmlinuz, then i run lilo got a fatal msgs:
# lilo
Warning: LBA32 addressing assumed
Fatal: read /boot/vmlinuz: No such file or directory

seems a serious problem, i guess i can't boot my system before i fix it, how's this come?

Last edited by wubai; 01-04-2010 at 06:30 AM.
 
Old 01-04-2010, 07:10 AM   #26
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
wubai

First of all read /boot/README.initrd file to find out how you can build an initrd image.
Next., just add this entry to your lilo.conf, don't modify/delete anything anywhere, keep everything intact.

Quote:
image = /boot/vmlinuz-generic-2.6.29.6
initrd = /boot/initrd.gz
root= /dev/hdaN
label = Generic
read-only
Then re-run lilo. Also you can add lba32 and compact to your lilo.conf to skip BIOS check at boot.
 
Old 01-04-2010, 07:12 AM   #27
~sHyLoCk~
Senior Member
 
Registered: Jul 2008
Location: /dev/null
Posts: 1,173
Blog Entries: 12

Rep: Reputation: 129Reputation: 129
Also, if you don't want an initrd you have to recompile kernel and build-in the root partition file system in kernel and not as modules.
 
Old 01-04-2010, 07:51 AM   #28
JokerBoy
Member
 
Registered: Sep 2009
Posts: 140

Rep: Reputation: 24
Exclamation

Quote:
Originally Posted by JokerBoy View Post
# rm /boot/vmlinuz
# rm /boot/System.map
# ln -s /boot/vmlinuz-generic-2.6.29.6 /boot/vmlinuz
# ln -s /boot/System.map-generic-2.6.29.6 /boot/System.map
# lilo
i modified my post! did you make new symlinks?
 
Old 01-04-2010, 08:21 AM   #29
voyciz
Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 425

Rep: Reputation: 40
Just use the slackbuilds ( http://slackbuilds.org/result/?searc...ualbox&sv=13.0 )
You'll need virtualbox-ose and virtualbox-kernel. Then
$ chmod +x /etc/rc.d/rc.vboxdrv
$ /etc/rc.d/rc.vboxdrv start

And also add the entry mentioned in post #3 to rc.local. Then you should be set.
 
Old 01-04-2010, 08:31 AM   #30
wubai
Member
 
Registered: Dec 2009
Posts: 103

Original Poster
Rep: Reputation: 20
Hi, guys!

@ JokerBoy,
i change it back , actually , i delete the huge kernel by mistake,because i created a hard link before (missed the '-s' option), then when i delete the link i deleted the real huge kernel, that's why that fatal error came, i guess !
it's my mistake
I copied a huge kernel from dvd and it's fine now

And i created an initrd, use the generic kernel to test if the vbox works with the generic kernel, it's working well now ! it's real unexpected , fun, and weird , isn't it? working fine with generic kernel but huge kernel. and don't need to recompile the virtualbox,just run "/etc/rc.d/rc.vboxdrv setup" as root

@~sHyLoCk~ , how did you know it works with generic kernel, and why ?

Last edited by wubai; 01-05-2010 at 06:59 AM.
 
  


Reply



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
Problem installing vpn client on Ubuntu: Failed to make module "cisco_ipsec.ko" challysand Linux - Newbie 1 08-29-2009 02:12 PM
Failed to Load Kernel Module "i915" alkos333 Slackware 3 01-13-2007 09:08 PM
Install ati-drivers fails with "Failed to compile kernel module" erpe Debian 2 06-13-2006 05:09 AM
mkinitrd failed with message "no module raid0 found for kernel 2.6.9" ythevenot Red Hat 3 12-07-2004 09:15 PM
"Failed to load module "i915"" Kane635 Linux - Software 0 11-22-2004 08:17 PM

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

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