Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
07-03-2006, 02:49 PM
|
#16
|
Member
Registered: Jun 2006
Distribution: Slackware
Posts: 144
Original Poster
Rep:
|
SRY guys for the delay...
I had a chirurgical operation yesterday
But now im OK
HERE WE GO!
Lets find those errors...
I commented the "change-rules" and "reset" things and did the "vga=normal"...
But it always do the same freeze thing...
=====================================================
=====================================================
LILO -V -T -B /dev/hda3
Code:
LILO version 22.5.9 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 08-Apr-2004 and compiled at 00:18:50 on May 21 2004.
Ignoring entry 'boot'
Warning: LBA32 addressing assumed
Warning: COMPACT may conflict with LBA32 on some systems
Reading boot sector from /dev/hda3
Warning: Partition 3 on /dev/hda is not marked Active.
Using MENU secondary loader
Calling map_insert_data
Mapping message file /boot/boot_message.txt
Calling map_insert_file
Boot other: /dev/hda1, on /dev/hda, loader CHAIN
Added Windows *
Boot image: /boot/vmlinuz -> vmlinuz-ide-2.4.31
Added Linux
The boot sector and the map file have *NOT* been altered.
=====================================================
=====================================================
DF -H
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/hda3 7.0G 95M 6.5G 2% /
/dev/hda5 8.4G 1.7G 6.3G 21% /usr
/dev/hda6 13G 52M 12G 1% /home
/dev/hda1 45G 6.3G 39G 15% /hda1_win32
/dev/hdb1 75G 47G 29G 63% /hdb1_win32
/dev/fd0 1.4M 0 1.4M 0% /mnt/floppy
=====================================================
=====================================================
ThanX
Blue!
Last edited by BlueSpirit; 07-03-2006 at 02:51 PM.
|
|
|
07-03-2006, 03:48 PM
|
#17
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
|
The lilo test invocation looks fine except that you are using capital -V -T -B which is not a good idea. You MUST use small letters as small and uppercase letters are DIFFERENT options. But from the output you showed I think you must have typed it right for the command and just changed it when you showed it in your post. You realize with the -t flag that nothing is updated, right?
The problem will be that if you are not installing lilo in the MBR (and installing lilo in the MBR is normally the best way) then you understand that you need some other boot loader in the MBR to boot anything from superblock, right?
Also, 95M used does not give me a good feeling about your Slackware installation. For sure lilo found the kernel but I think nothing else is there. I think you need to double check your Slackware installation and make sure you understand what you put where. And make sure you know why you are choosing to put lilo in the superblock of hda3- usually this means you have changed ntloader in Winbloze to boot your other systems.
I think you should forget about installing lilo in the superblock of hda3 and just do lilo -v -b /dev/hda and this will solve all your problems.
Last edited by Randux; 07-03-2006 at 03:59 PM.
|
|
|
07-03-2006, 04:16 PM
|
#18
|
Member
Registered: Jun 2006
Distribution: Slackware
Posts: 144
Original Poster
Rep:
|
OK well...
I installed LILO first (i said first) when IN the superblock it was when I installed Slackware on the CDs...
So the first time, I installed it in the superblock...
But then, I saw that it wasnt booting, so I booted Slack with the CD1 and then, I typed "liloconfig" and installed it in the MBR...
Maybe I should re-install it...
But do you think my Computer (a Pentium III Coppermine 870MHz overclocked to 1GHz) is NOT compatible with LILO?
...I dont think so but...
And I **ALWAYS** type my cmds in lowercase...
I just typed it in uppercase to SHOW it in the forums...
ThanX
For ur future answers...
|
|
|
07-03-2006, 08:12 PM
|
#19
|
HCL Maintainer
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Arch, Gentoo
Posts: 6,941
Rep:
|
BlueSpirit,
You have /etc/lilo.conf and your entire Slackware OS messed up.
You can't return proper information when you type improper commands. In *nix commands are case sensitive, and what Randux is trying to tell you is that in the command "lilo" the "v" switch means increase verbosity, and the "V" switch means print version number.
You would be better off to sit down and read Chapter 5. Installing Slackware Linux and then just start over with a fresh, proper Slackware installation. There is no way on God's green earth that you can have a good Slackware install with 95M in / and 1.7 G in /var. Not at your present Slackware knowledge level.
That's just my opinion. I'll be happy as a pig in poop if no one shares it, or the entire world shares it. This forum is a post of just that, opinions. As Jeremy points out in the rules: - We would like to stress that you should fully understand what a recommended change may do to your system. You should not give anyone you do not know login information to your system. LinuxQuestions.org cannot be held liable for for anything you do as a result of information obtained at this site.
|
|
|
07-04-2006, 03:01 AM
|
#20
|
LQ Newbie
Registered: Jul 2006
Location: In a house
Distribution: You mean there's MORE than one? I better let Mr. Gates know
Posts: 4
Rep:
|
Has anyone noticed how all the linux partitions are WELL past cylinder 1024 and I can't see any 'LBA' in the lilo.conf...
(And the Wind-Blows partition is at the START of the disk thus it's PROBABLY booting from data before cyl=1024)
Perhaps the old BIOS issue where cyl > 1024 has reared its ugly head once more?
|
|
|
07-04-2006, 03:24 AM
|
#21
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
|
Quote:
Originally Posted by trev_vb
Has anyone noticed how all the linux partitions are WELL past cylinder 1024 and I can't see any 'LBA' in the lilo.conf...
(And the Wind-Blows partition is at the START of the disk thus it's PROBABLY booting from data before cyl=1024)
Perhaps the old BIOS issue where cyl > 1024 has reared its ugly head once more?
|
This is a very old limitation and Lilo defaults to LBA (as you see from the output, it says "LBA32 assumed".) It could be BIOS related but because there are so many other obvious problems here, I don't think this is the issue. The issue seems to be related to the fact that the installation wasn't done properly (95M root is not going to work without other mountpoints that he doesn't have), and the fact that he's installing lilo all over the place without knowing why. (If lilo is installed in the superblock and MBR then the lilo entry for that Linux has to be a chainloader entry like for Winbloze, not like for a normal Linux booted from MBR. This is not what was done.) Once everything else is done properly everything should work. This is not complicated except because of all the disorganized guessing that occurred. If it doesn't work after following the normal procedure, then it would be time to look into BIOS incompatibility.
From what I've seen in terms of documentation and OP confusion I agree with the Chinaman that it's time to take a break, do a little reading and planning, and then start from the beginning.
A good idea would be to state your plans here and get some people to look them over before your next installation. That way you can proceed with confidence.
|
|
|
07-04-2006, 03:27 AM
|
#22
|
HCL Maintainer
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Arch, Gentoo
Posts: 6,941
Rep:
|
Quote:
Originally Posted by Randux
A good idea would be to state your plans here and get some people to look them over before your next installation. That way you can proceed with confidence.
|
Now that is a great idea!
And before you trash anything, also let us help you backup your data. No sense in losing the best picture you ever shot of your wife because of this.
|
|
|
07-04-2006, 04:01 AM
|
#23
|
LQ Newbie
Registered: Jul 2006
Location: In a house
Distribution: You mean there's MORE than one? I better let Mr. Gates know
Posts: 4
Rep:
|
Last time I was about to take a shot of my wife I think I got confused between the camera and the shotgun... She _WAS_ a good woman till then
|
|
|
07-04-2006, 02:52 PM
|
#24
|
Member
Registered: Jun 2006
Distribution: Slackware
Posts: 144
Original Poster
Rep:
|
WoW guys...
You seem rly ready to help me... Thanx a lot...
But plz HELP ME!
I wanna use Slack b/c its a real LIGHT distribution, I don't say my comp is old and slow (Nah, Its OK I run like Half-Life 2 or F.E.A.R. with everything at MEDIUM and HIGH and theres no laggs), but I want to use Slackware with FluxBox ONLY to have a VERY LIGHT and FAST side in my computer...
My comp ISNT the best, but its not a SLOW pile of shit, so don't think I have a prehistorical computer and that my comp is incompatible with a lot of things...
Now I would like you to help me to tell me whats wrong in my Slack Installation...
You are PROS, Im a newbie in Slackware...
I was running Fedora before, but it was too simple for me, I HATE things that are too simple... So I hate WIN, but its kinda essential... lol
And I have an ASUS "Award Medallion BIOS Revision 1009", that I modified (I know what I do in my BIOS), and its NOT a beta...
Don't worry, everything is OK in my BIOS, im sure...
-------------Heres my Questions---------------
1)
Quote:
Originally Posted by Randux
95M root is not going to work without other mountpoints that he doesn't have
|
What's the problem with the 95M in root?
The total space for root is 7.5Gb
Don't forget I only use FluxBox... And NO KDE or GNOME...
And (lol im such a noob), how can I do mountpoints?
2) Does I have to use separate partition for "/usr" and "/home"? Is it better?
3) If 2) = Yes
Does the following partitions configuration can be OK:
Code:
32Gb for Slackware...
SWAP = 1024Gb of 32Gb
/ = 7.5Gb of 32Gb
/usr = 9Gb of 32Gb [logical]
/home = 14.5Gb of 32Gb [logical]
4) Does my / partition needs the bootable flag?
5) Does ext2 is faster than ext3?
If I have other questions, ill post them...
-----------------------------------------------
If you have any recommendations, plz tell it to me!
Thanx
Blue
P.S.:
Quote:
Originally Posted by Chinaman
And before you trash anything, also let us help you backup your data. No sense in losing the best picture you ever shot of your wife because of this.
|
If I erease all our photos... Ill be at the hospital
Last edited by BlueSpirit; 07-04-2006 at 03:10 PM.
|
|
|
07-05-2006, 02:06 AM
|
#25
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
|
Quote:
Originally Posted by BlueSpirit
What's the problem with the 95M in root?
The total space for root is 7.5Gb
Don't forget I only use FluxBox... And NO KDE or GNOME...
|
If you want to make your life easy, and you are making a desktop machine (not a server) than consider just having two mountpoints- root and home.
Quote:
Originally Posted by BlueSpirit
And (lol im such a noob), how can I do mountpoints?
|
If you create the partitions with fdisk or during the installation, the Slackware installation dialog will ask where you want to mount the various mountpoints. You can do it from there.
If you change your mind later, it's easy to update /etc/fstab to change mountpoints. And you can issue commands while the system is running to mount and unmount filesystems.
Quote:
Originally Posted by BlueSpirit
2) Does I have to use separate partition for "/usr" and "/home"? Is it better?
|
A separate /usr is never necessary, I think. For desktop, separate /usr/local is not necessary. /home is a good idea so that when you mess up your installation you don't have to keep creating your userids and lose all their files each time
Quote:
Originally Posted by BlueSpirit
3) If 2) = Yes
Does the following partitions configuration can be OK:
Code:
32Gb for Slackware...
SWAP = 1024Gb of 32Gb
/ = 7.5Gb of 32Gb
/usr = 9Gb of 32Gb [logical]
/home = 14.5Gb of 32Gb [logical]
|
How much RAM do you have? 1G of swap is a waste of disk space. 256M or 512M at the most sounds a lot better. If you have 512M or more RAM then go with 256M.
7.5G of root is more than you will ever need unless you install thousands of apps or need a lot of temp space.
/usr mounted separately is a bad idea, don't do it
/home 14.5G is huge /home for desktop machine unless you will save many MP3 and docs on it
Quote:
Originally Posted by BlueSpirit
4) Does my / partition needs the bootable flag?
|
No.
Quote:
Originally Posted by BlueSpirit
5) Does ext2 is faster than ext3?
|
Yes. But it's faster for a reason. If you ever shut down hard on ext2 you may lose data. If you don't have a good reason, then use the default fs which is reiserfs. Pat (Slackware owner) didn't choose his defaults without thinking!
Quote:
Originally Posted by BlueSpirit
If I have other questions, ill post them...
|
All of your questions have already been answered in other threads. Please do some research.
Remember to install Lilo in the MBR!
Last edited by Randux; 07-05-2006 at 09:47 AM.
|
|
|
07-05-2006, 11:55 AM
|
#26
|
Member
Registered: Jun 2006
Distribution: Slackware
Posts: 144
Original Poster
Rep:
|
OK I found the error...
My CPU is a Pentium III Coppermine 866MHz overclocked to 1001MHz...
I took a lil time to check my BIOS...
I restored the CPU defaults in the BIOS, so I changed the 1001MHz to 866MHz...
And now LILO is booting perfectly...
To resume, when my CPU is set at 1001MHz, LILO freezes when booting Slackware 10.2 and when my CPU is set to 866MHz (the default frequency), LILO boots perfectly...
And Windows XP ALWAYS boot with LILO...
And note that when I boot Slackware from the CD1 (with "bare.i root=/dev/hda3 noinitrd ro) with the overclock, it works...
My overclock is very safe and stable, the MAX CPU temperature is like 46.5 °C...
What I do to make LILO compatible with my Overclock?
Thanx for ANSWERs...
Last edited by BlueSpirit; 07-05-2006 at 11:59 AM.
|
|
|
07-05-2006, 12:13 PM
|
#27
|
HCL Maintainer
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Arch, Gentoo
Posts: 6,941
Rep:
|
Quote:
Originally Posted by Chinaman
Have you made any changes to your BIOS?
|
Could have saved some time if you'd answered ...
I've overclocked an Asus A7V600-X with no boot problems. I suspect you don't realize what you did, but in restoring "the CPU defaults in the BIOS" you've fixed something else that was messed up.
You should now try to overclock again, and check the results. Perhaps if you just change CPU Speed and see if it will boot.
To test, I just changed that same board from 1350MHz to 1800MHz and it booted fine.
|
|
|
07-05-2006, 12:23 PM
|
#28
|
Member
Registered: Jun 2006
Distribution: Slackware
Posts: 144
Original Poster
Rep:
|
Yep, thats what I did...
I re-overclocked and re-booted and... FREEZE!
Then I re-set the CPU frequency to 866MHz and... BOOTING WAS OK!
Hmmm...
Any ideas?
P.S.: Don't worry, Im kinda noob in Linux, but I rly know what I do in my BIOS
Last edited by BlueSpirit; 07-05-2006 at 12:30 PM.
|
|
|
07-05-2006, 12:44 PM
|
#29
|
HCL Maintainer
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Arch, Gentoo
Posts: 6,941
Rep:
|
Could be all manner of stuff in your kernel that keeps it from working. Why don't you just post the entire .config file of the kernel that hangs somewhere on the internet, and the exact error message you get on the screen when it hangs -- actually, post the entire "dmesg" output.
|
|
|
07-05-2006, 01:53 PM
|
#30
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
|
I will now leave this in your capable hands, woh de pung-yo (sorry for bad transliteration!)
|
|
|
All times are GMT -5. The time now is 08:22 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|