Slackware "freezes" (when BOOTING with LILO) ; Dual-Boot WinXP/Linux
Hi all,
I just installed Slackware 10.2. Now I try to boot Slackware with LILO, but it doesn't work... And I can't write my lilo.conf b/c when I boot with the Slackware CD1 (boot: bare.i root=/dev/hda3 noinitrd ro), the X Window System doesn't boot (its a black screen)(console))... Windows XP boots PERFECTLY but Slackware doesn't... And LILO is in MBR When I try to boot Linux with LILO, it says : Code:
Boot: Linux I waited like 2-3 mins, and there was nothing after "Booting Linux.........." And sometimes, it says: Code:
Boot: Linux So whats does I do? Heres my config: ---------[ Config ]---------- Pentium III Coppermine 870MHz overclocked to 1GHz ASUS CUSL2-C Dual-Boot LILO --> Windows XP Pro SP2/Linux Slackware 10.2 512Mb (SDRAM PCI133) ATI Radeon X700 256MbAGP 4X Sound Blaster PCI128 Two IDE hard disks of 80Gb including 35Gb disponible for Linux) ------------------------------ Kernel 2.4 (the default one on Slackware 10.2 CDs) FluxBox (just FluxBox, NO KDE or other Desktop Env.) LILO Partition ./ on "/dev/hda3" (partition ./ of 7.5 Go) 1 Gb of SWAP I checked my liloconfig (when booting with "bare.i root=/dev/hda3 noinitrd ro" (without the Windows config): Code:
# liloconfig ==== Thanx a LOT! Blue.- |
Great information btw... thanks.
Boot from the CD again to the console seeing that your system doesn't boot from LILO yet. Sounds to me like something is up with your lilo config, so lets take a look. When you run lilo from the console what does it say? also please run the following and post results.... Code:
ls -l /boot |
If you need to do anything with your system and you can't boot it, boot from the Slackware installation disk and chroot into your existing (installed) system. That way you're inside your installed system, and you can run lilo, do fdisk -l or anything else you need to do to see what went wrong.
What do you mean by "partition ./" This is not a valid definition. If you typed that in somewhere, it is probably part of the problem. Root is just "/" with nothing before or after. If that was just a typo (twice) then don't worry about it. Also it may help to see a real copy of your lilo.conf and fdisk -l because people often don't type stuff like it actually is. If you can, copy and paste it in to the entry so we can see what's going on. I don't know what the boot=/dev/hda is doing but it doesn't look normal. Here's a sample lilo.conf for a dual boot with Winblows in /dev/hda1 and Slackware in /dev/hda3. This is a complete lilo.conf which is sufficient: Code:
# Sample LILO configuration for dual boot |
I just want to post one thing so the OP doesn't get concerned, but "boot = /dev/hda" is normal. This might not be the only time that is entered, but when you choose the expert option for installing LiLO and pick the MBR, it asks you for this location.
This is not to be argumentative with Randux at all. |
I would say boot with Slack cd 1 and do a chroot like Randux suggested and then check your boot directory to make sure /boot/vmlinuz exists as a kernel or is a sym link to /boot/vmlinuz-ide-2.4.31 which is the usual kernel name for Slack 10.2 in 2.4.31 kernel. While your there do:
fdisk -l to get a list of available partitions and make sure that hda3 is your Slack partition. |
OK I want to copy my "fdisk -l", my "lilo.conf" and my "ls -l /boot", but I have a problem...
Hmmm, I think you will think im a dumb... lol Heres the problem: I use the "xterm" terminal... When I type, for example, "fdisk -l" in xterm, I see the informations, but I CAN'T copy the informations of "fdisk -l" from xterm to a plain text file... How to copy text in xterm? And does "vmlinuz" and "vmlinuz-ide-2.4.31" is the same? Because I think "vmlinuz" is a better kernel, no? I think its a guy that told me that... Thanx... P.S. for ScottReed : When I type lilo in the console, it says ONLY: Code:
Added Windows* |
vmlinuz is most likely a symlink to the vmlinuz-ide-2.4.31 file. No issue there.
The fact that lilo doesnt return any errors means that your lilo.conf is OK. Try to get the output from fdisk -l |
Quote:
First, for lilo issue: Code:
mingdao@silas:~$ cat /etc/lilo.conf > lilo.conf.txt Second, for the listing of your /boot directory issue: Code:
mingdao@silas:~$ ls -lh /boot > boot.txt (I added the -h switch to make the output 'human readable' -- you seem like the human type.) Third, for the output of your file partitions, (as root) issue: Code:
root@silas:~# fdisk -l > /home/blue/fdisk.txt (where I put blue, you put your username) If you can get online in Slackware, then you can copy and paste them from xterm into here. Start with your web browser open, and with a window here ready to reply to this thread. In xterm you can now issue: Code:
mingdao@silas:~$ cat fdisk.txt You also need to format that text in here where we other humans can read it easily. The way to do that is to use the code tag. You type [_code_] without the underscores _ before your text, and [_/code_] without the underscores _ after your text. So BlueSpirit, you start by getting a reply window here, then all you need to do is type [_code_] without those underscores and then got to xterm and issue "cat fdisk.txt" and then drag the mouse over the output and then come paste it here after [_code_] without those underscores by clicking on the middle mouse button. You should have something like this: Code:
mingdao@silas:~$ cat fdisk.txt Now, the way Slackware sets this thing up, you'll have an entry in your /boot directory like this: Code:
lrwxrwxrwx 1 root root 18 2006-06-18 01:43 vmlinuz -> vmlinuz-ide-2.4.32 You asked how to: Quote:
Code:
root@silas:~# fdisk -l Also, might I comment on your output: Quote:
Code:
# Windows bootable partition config begins Code:
# LILO configuration file This seems to be your problem from your first message where you said: Quote:
|
OK I got my config files...
And Chinaman, I tried your suggested lilo.conf, but it didn't work... :( Now, heres my config files: =============================================== =============================================== FDISK -L Code:
Disk /dev/hda: 80.0 GB, 80026361856 bytes =============================================== LS -L /BOOT Code:
total 1928 =============================================== LILO.CONF Code:
# LILO configuration file =============================================== Thanx for your HELP Blue |
Few things.
You didn't remove "change-rules reset" And your console is set to "vga=790" and not "vga = normal" but probably doesn't matter. Can you post the output of "df -h" for us? What you got on that hdb1 Windows partition? And why is it bootable also? |
It's ok if his NTFS partition on hdb is bootable; he needs it to be able to boot Win from that drive.
We need to see what LILO command he's issuing. In this example, he should use Code:
lilo -v -t -b /dev/hda # this is a test to see what msgs you get Code:
lilo -v -b /dev/hda # no errors from test, do it for real Don't rely on running lilo from the Slackware installation script. There are dozens of problem entries here- sometimes LILO complains and the error doesn't get percolated properly. Run the commands as shown and check the output. |
Quote:
Quote:
Code:
mingdao@silas:~$ man lilo.conf Quote:
All that needs to be input with a proper /etc/lilo.conf is "lilo" as root. BlueSpirit, If you tried my "/etc/lilo.conf" what was the error output when you ran "lilo" as root afterwards? If you tried Randux's "/etc/lilo.conf" what was the error output when you ran "lilo" as root afterwards? Why do you insist upon the "change-rules reset" line? Have you made any changes to your BIOS? Please give the output of "df -h" here. The output of "fdisk -l" tells your partition table and file systems, but not the mount points of the filesystems. |
Try setting 'vga=normal' in your lilo and reboot. I've often run into the BSOD (black screen of doom) when I'm trying to run a video reslotion that's not supported by the kernel's detected video device. Switching to normal will always work.
In the fiture, you might want to do what I do and have a "safe" lilo boot config option where it has vga=normal defined just in case you compiled in the wrong frame buffer. Cheers |
Quote:
Anyway, since the can is now open: Quote:
Quote:
At any rate, I said that mine was a "minimal configuration." I probably did make a mistake by suggesting the framebuffer console as katayamma pointed out. But I'll bet the problem is boot sector not going in MBR. Quote:
Quote:
|
At any rate, let's leave our differences in opinion aside and get him booting.
BlueSpirit, the next thing after your line which says "Linux loading ......" or whatever you label it (you chose the default suggested Linux) is alway "BIOS data check successful" or something worded similarly. Which is why I wonder if you have some problem in your BIOS. Randux is correct in suggesting those two lines for loading LiLO from CLI. If you'll do that it will tell you what your error is. If it returns the output you posted earlier "for ScottReed" in post #6, then LiLO loaded with your configuration, and the problem is somewhere else. Notice, fellers, he hasn't yet reported a LiLO error... |
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 ===================================================== DF -H Code:
Filesystem Size Used Avail Use% Mounted on ===================================================== ThanX Blue! |
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. |
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... ;) |
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. :scratch: :study: 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:
|
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? |
Quote:
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. |
Quote:
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. :cool: |
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
|
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:
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... 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:
|
Quote:
Quote:
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:
Quote:
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:
Quote:
Quote:
Remember to install Lilo in the MBR! |
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... |
Quote:
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. |
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 ;) |
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.
|
I will now leave this in your capable hands, woh de pung-yo :p (sorry for bad transliteration!)
|
OK but...
Before posting all these outputs, I would like (what you think) to know : Do you think its "LILO" or the "kernel"? ThanX |
I think you got too many SCSI bitmaps in that system...
|
OK here we go...
I posted two DMESG outputs... I took 1 with my overclock settings (booted with "bare.i") and 1 with my standard settings (booted SUCESSFULLY with LILO)... And I posted my .config file located in /boot (the kernel "vmlinuz")... ======================================== ++++++++++++++++++++++++++++++++++++++++ ======================================== dmesg (tooken with my overclock setting) Code:
6 Sun Jun 5 19:04:47 PDT 2005 |
========================================
++++++++++++++++++++++++++++++++++++++++ ======================================== dmesg (tooken with my standard CPU settings) Code:
tree) (gcc version 3.3.5) #6 Sun Jun 5 19:04:47 PDT 2005 |
And my .config file
Code:
# |
Code:
# |
SRY, but it was too long for the forums...
I had to separate it... lol Thanx for your help |
help! me! plZ!
If I install the new kernel (2.6), can it maybe solve the problem? Does anyone can tell me what to do... ThanX Sry, its rly a problem lawl > I can<t boot! |
You are running a generic Slackware kernel, which means it should work on almost any CPU. But when you overclock your old P3, you are outside that kernel's parameters. I do not know for sure if this is the problem, but I would at least recommend that you compile a custom kernel, if you are going to overclock. (Note that the Slackware generic kernel has CONFIG_M486=y but you're not running a 486 series processor; you're running a P3 so you might get better results with CONFIG_MPENTIUMIII=y instead; as well as other settings that come with it.)
Now, that means that you will have to learn your hardware -- intimately. If you are willing to do that, then read Kwan Lowe's Kernel Rebuild Guide and start learning about kernel building. And you should also read Linus Torvalds' instructions in the README file of the top level directory of the kernel source after you untar the file. If you're not ready and/or willing to do this, there are two alternatives IMNSHO: 1 - stop overclocking that old P3 2 - try the generic 2.6.16.22 kernel in Slackware -current (which you might still need to recompile, also). If you want to start by trying that 2.6.16.22 generic kernel, you MUST read the Slackware current release notes. This is the most relative part for you: Quote:
Ball's in your court. Randux, it's "wode pengyou". |
OK thax...
Im gonna compile the next stable kernel... If LILO is getting fucked again, ill use SysLinux to boot with LILO... And I just started to watch some things about kernel compiling, and it says I should use (for processor feature), the "PENTIUM4" option, b/c I have optimized my CPU,a dn it says PIII optimized should use the "PENTIUM4" options for "BEST PERFORMANCE-STABILITY AND COMPATIBLE-OVERCLOCK ENVIRONMENT"... Thax Chinaman... Gonna compile my kernel soon I kinda know how... |
All times are GMT -5. The time now is 06:04 PM. |