SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hello there, first sorry for my bad english, its not my mother tongue..
Well, i've installed slackware 11.0 few days ago and i've noticed that if I want to use my RTL8139 and Marvell net adapters I have to upgrad to kernel 2.6, well, i looked up this site and found out an excellent guide for doing this ( http://www.linuxquestions.org/linux/...Slackware_10_1 )
I followed it step by step and everything went just fine except one little thing is when finally I typed 'lilo' to initialize it , it showed my an msg that goes something like that: "warning: master boot and system map are not on the same disk", well, I kind of ignored that just for its being a simple warning and typed finally 'reboot' and then lilo popped up, I chose my new kernel from the menu and unfortunately I had nothing on my screen, a totally blank screen but I heard my hard-drive is working so I realized that the booting process is happening but it doesn't show me nothing, while it was a black screen , I waited it to boot completely (just by hearing my hard-drive) and tried to log-in as root (while I see nothing on my screen).. well, I heard my hard-drive works again so I realized that it DOES work but it just shows me nothing.. well, I typed on my console (again, while I see a blank screen) a 'startx' and for my surprise it opened up my kde (from the new kernel, and it even made a cool sounds at the beginning so all the kernel compiling at the beginning was quite successful) so I realized that maybe there is some problem with my kernel modules so in the kde KConsole i typed 'xconfig' while im in /usr/src/linux-188.8.131.52 and I chose all the modules that I thought that might help me figure it out (for example frame-buffer stuff and this kind of things), after closing the 'xconfig' i typed:
2) make modules
3) make modules_install
well, it made all this compiling process and then I tried to reboot.. and unfortunately while im still trying to boot it from the new kernel I still see a blank screen and hear that my hard-drive is booting it out :\
please help me because im kind of desperate already :\
I think im missing some part while im trying to update the kernel (I mean im missing some step from the steps i wrote above, after doing changed in the xconfig I mean).
I did include the frame buffer support but my question is: after im including this, and after exiting the menuconfig, what command should I type? only these 3 ones that I mentioned? or maybere there is something more?
my lilo.conf looks like this:
# Slack NEW begins
image = /boot/vmlinuz-2.6.10
root = /dev/hdb1
label = Slack_2.6.10
# Slack NEW ends
# Slack OLD begins
image = /boot/vmlinuz-old
root = /dev/hdb1
label = Slack_OLD
# Slack OLD
mmmm and I actually didn't really understand what should I put in the lilo.conf file? (the dirty way u talked about). It would be great if you'll show me an example of your file or something like that..
mmm well, it quite worked but still only when the vga (in the lilo.confg) is set to normal even though I chose all the frame buffer options in the kernel config but when I type 'make intall' or 'lilo' I get this strange warning that I can't figure out:
root@darkstar:/usr/src/linux-184.108.40.206# make install
sh /usr/src/linux-220.127.116.11/arch/i386/boot/install.sh 18.104.22.168 arch/i386/boot/bzImage System.map "/boot"
Warning: The boot sector and map file are on different disks.
Added New_Linux *
dude.. I'm sooo sorry. I didnt catch this before, I was kind of assuming you were following a guide:
$make oldconfig # just restores your previous .config
$make bzImage # makes the kernel image
$make modules # makes the modules
#make modules_install # installs the modules
#cp arch/i386/boot/bzImage /boot/bzImage-2.X.Y.Z # copies your newly created image to /boot
#cp System.map /boot/System.map-2.X.Y.Z # same w/System.map .. X.Y.Z is kernel version number (really your choice)
#ln -s /boot/System.map-2.X.Y.Z /boot/System.map # link new system.map to old one
#vi lilo.conf # edit lilo.conf
#/sbin/lilo # run lilo (hopefully no errors)
i use these commands _every_ time I build a new kernel. For a more in-depth look at kernel compiling check the link in my sig.
again, I am sorry I didn't catch that lilo error before.
btw- the X.Y.Z thing is purely optional, I always do kernel version number and because it sometimes takes a few tries to get it right some alpha suffix to keep them ordered in my head. (this is reflected in my lilo.conf where 22.214.171.124f )
hope this helps!
-ack- I keep thinking of other things to ask: how are your partitions & HDs set up?
is the MBR where lilo is installed on the same disk as your /boot directory?
if you have a separate partition for /boot do you fully specify the path in lilo.conf?
I followed these steps man and I loaded the new kernel but unfortunately only when vga=normal, and I still dunno why :\
my partitions goes something like that:
/dev/hda1 - an NTFS (40GB)
/dev/hda2 - FAT32 (40GB)
/dev/hdb1 - ex2fs (12GB)
and another swap partitions that is about 1.5GB
well, I haven't really chose where to install lilo besides of choosing 'MBR' at the slackware installation but I guess its not on the same disk as the /boot directory.
How can I fully specify the path in lilo.conf?
mmm I got another problem popped out.. afer compiling this kernel and loading it up I can't reach the NTFS hard-drive, even though I chose the modules for the ntfs and compiled them but I can't see nothing in the /fat-c folder.. even when I try to do: mount /dev/hda1 /fat-c , it writes me something like that: ntfs: unknown filesystem.. plz help me ;\
in the same order as I wrote them.. after i leave the menuconfig do I have to do 'make oldconfig' too? I never did that.. I chose all the ntfs support (first I tried as a module and it didn't work and after that I just put an asterisk on it and it didn't work too) and then I hit 'exit' and clicked on yes to save the changes and after that I typed all the steps that I wrote above without any 'make oldconfig', do u think its necessary? if so, then why?
I dont get the same problem running /sbin/lilo (and that's quite weird), the same problem I got running /sbin/lilo is this warning about the system map that I already mentioned.. the lilo sees the /dev/hda1 perfectly withuot any problems but when I try to mount the /dev/hda1 to some folder it shows me that thing that the ntfs is an unknown filesystem.
and then I hit 'exit' and clicked on yes to save the changes and after that I typed all the steps that I wrote above without any 'make oldconfig', do u think its necessary? if so, then why?
i find that if I don't 'make oldconfig' before runnning make xconfig all my previous settings are lost. ergo if I want to change just a few options then I run make oldconfig to read in what I last did, then run 'make xconfig' to adjust.
I know nothing of 'make install' I suspect it just copies the bzImage and system.map and creates the link for you. either way i think the error from lilo is gone because of the make install command.
so, before skipping prblem #1 - is that fb working now?
I did some more reading, you can try this:
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
timeout = 400
# Override dangerous defaults that rewrite the partition table:
# End LILO global section
# Linux bootable partition config begins
image = /boot/bzImage-2.6.20
root = /dev/hda4
label = Current2.6.20
vga = 791 # note vga option is now for each kernel
image = /boot/bzImage-126.96.36.199f
root = /dev/hda4
vga=extended # note vga option is now for each kernel
label = Test188.8.131.52f
image = /boot/vmlinuz
root = /dev/hda4
label = Slack-Huge26
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda2
label = Windows
table = /dev/hda
# Windows bootable partition config ends
that helped me, turns out you can not 'append="vga=<anything>"' - but each image can have its own vga= argument.
can you show your fstab and or mount command using for ntfs?