|
Can't boot into doze after Debian install...
My /etc/lilo.conf looked like a manual, but here is what seems to me to be the pertinent part. This may be the wrong information, but since I only have experience with grub (and very little at that), and all the lilo stuff was too confusing, please give me instructions if this isn't what you need.
# Boot up Linux by default. # default=Linux image=/vmlinuz label=Linux read-only # restricted # alias=1 image=/vmlinuz.old label=LinuxOLD read-only optional # restricted # alias=2 # If you have another OS on this machine to boot, you can uncomment the # following lines, changing the device name on the `other' line to # where your other OS' partition is. # # other=/dev/hda4 # label=HURD # restricted # alias=3 other=/dev/hdb1 label="Windows(hdb1)" It just hangs at: boot: Windows (hdb1) Loading Windows (hdb1) :scratch: Note: Before installing Debian I did a fdisk /mbr on the slave drive (hdb) which has Windoze XP, to remove any grub entries from the previous RH9 install on hda. Then when I installed Debian, it selected every partition on hdb. I have removed all but hdb1 and run lilo again, then rebooted. debian:/sbin# fdisk -l Disk /dev/hda: 16 heads, 63 sectors, 119150 cylinders Units = cylinders of 1008 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 194 97744+ 83 Linux /dev/hda2 195 4069 1953000 82 Linux swap /dev/hda3 4070 6007 976752 83 Linux /dev/hda4 6008 60260 27343512 5 Extended /dev/hda5 6008 35071 14648224+ 83 Linux /dev/hda6 35072 54447 9765472+ 83 Linux /dev/hda7 54448 56385 976720+ 83 Linux /dev/hda8 56386 60260 1952968+ 83 Linux Disk /dev/hdb: 255 heads, 63 sectors, 7476 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 1216 9767488+ c Win95 FAT32 (LBA) /dev/hdb2 1217 7476 50283450 f Win95 Ext'd (LBA) /dev/hdb5 1217 4864 29302528+ b Win95 FAT32 /dev/hdb6 4865 5229 2931831 b Win95 FAT32 /dev/hdb7 5230 5594 2931831 b Win95 FAT32 /dev/hdb8 5595 6810 9767488+ b Win95 FAT32 /dev/hdb9 6811 7476 5349613+ b Win95 FAT32 The slave drive (hdb) was formatted and partitioned in advance of install with Maxtor's MaxBlast 3. It has Windoze XP OS. No idea why it says Win95, as Win95 was FAT16, right? :scratch: The master drive (hda) has Debian as the only OS. It also had a low level format with MaxBlast before installing Debian. TIA :D |
:)
Looks like a case of "I wanna be first" typical of $omething in$talled on HDB ;) Your lilo entry for hdb should look something like this: [code]other = /dev/hdb1 label = Windoze table = /dev/hdb map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 Save, exit and run lilo: /sbin/lilo -v Cool |
Re: Can't boot into doze after Debian install...
Quote:
Cool |
That's more than 20 lines, but I'm not used to using nano, and didn't get pico, and don't know what to use in wmaker, so if that's not what you need, help me to know what to do and I'll post back. I'm gonna try your previous post fix now. Will let you know what happens.
:cool: # Boot up Linux by default. # default=Linux image=/vmlinuz # Boot up Linux by default. # default=Linux image=/vmlinuz label=Linux read-only # restricted # alias=1 image=/vmlinuz.old label=LinuxOLD read-only optional # restricted # alias=2 label=Linux read-only # restricted # alias=1 image=/vmlinuz.old label=LinuxOLD read-only optional # restricted # alias=2 |
Whoa, is there more above this then? I'm looking for things like:
boot=/dev/hda lba32 timeout=1000 Things like that. Is there entries like that anywhere in that file? If you want, feel free to post the entire thing, if it's a man page combined with the conf file, we should edit that out anyway ;) Cool |
Sorry there's so much here. And I had to Ctrl+Alt+Bksp and log in as root and use xedit because I dont' know how to get all of this file in nano - I can only get what's on the screen at one time.
:scratch: # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)', # --------------- `install-mbr(8)', `/usr/share/doc/lilo/', # and `/usr/share/doc/mbr/'. # +---------------------------------------------------------------+ # | !! Reminder !! | # | | # | Don't forget to run `lilo' after you make changes to this | # | conffile, `/boot/bootmess.txt', or install a new kernel. The | # | computer will most likely fail to boot if a kernel-image | # | post-install script or you don't remember to run `lilo'. | # | | # +---------------------------------------------------------------+ # Support LBA for large hard disks. # lba32 # Overrides the default mapping between harddisk names and the BIOS' # harddisk order. Use with caution. #disk=/dev/hde # bios=0x81 #disk=/dev/sda # bios=0x80 # Specifies the boot device. This is where Lilo installs its boot # block. It can be either a partition, or the raw device, in which # case it installs in the MBR, and will overwrite the current MBR. # boot=/dev/hda # Specifies the device that should be mounted as root. (`/') # root=/dev/hda3 # Enable map compaction: # Tries to merge read requests for adjacent sectors into a single # read request. This drastically reduces load time and keeps the # map smaller. Using `compact' is especially recommended when # booting from a floppy disk. It is disabled here by default # because it doesn't always work. # # compact # Installs the specified file as the new boot sector # You have the choice between: bmp, compat, menu and text # Look in /boot/ and in lilo.conf(5) manpage for details # install=/boot/boot-menu.b # Specifies the location of the map file # map=/boot/map # You can set a password here, and uncomment the `restricted' lines # in the image definitions below to make it so that a password must # be typed to boot anything but a default configuration. If a # command line is given, other than one specified by an `append' # statement in `lilo.conf', the password will be required, but a # standard default boot will not require one. # # This will, for instance, prevent anyone with access to the # console from booting with something like `Linux init=/bin/sh', # and thus becoming `root' without proper authorization. # # Note that if you really need this type of security, you will # likely also want to use `install-mbr' to reconfigure the MBR # program, as well as set up your BIOS to disallow booting from # removable disk or CD-ROM, then put a password on getting into the # BIOS configuration as well. Please RTFM `install-mbr(8)'. # # password=tatercounter2000 # Specifies the number of deciseconds (0.1 seconds) LILO should # wait before booting the first image. # delay=20 # You can put a customized boot message up if you like. If you use # `prompt', and this computer may need to reboot unattended, you # must specify a `timeout', or it will sit there forever waiting # for a keypress. `single-key' goes with the `alias' lines in the # `image' configurations below. eg: You can press `1' to boot # `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'. # # message=/boot/bootmess.txt prompt timeout=150 # prompt # single-key # delay=100 # timeout=100 # Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>) # # vga=ask # vga=9 # vga=normal # Kernel command line options that apply to all installed images go # here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in # the Linux kernel `Documentation' directory. # # append="" # Boot up Linux by default. # default=Linux image=/vmlinuz label=Linux read-only # restricted # alias=1 image=/vmlinuz.old label=LinuxOLD read-only optional # restricted # alias=2 # If you have another OS on this machine to boot, you can uncomment the # following lines, changing the device name on the `other' line to # where your other OS' partition is. # # other=/dev/hda4 # label=HURD # restricted # alias=3 other=/dev/hdb1 label="Windows(hdb1)" :eek: |
That's perfect, exactly what I was looking for. I couldn't figure out where your root entry was, nor which drive the boot loader was getting installed to ;)
Looks good, any luck with the above 'map' inclusions? Cool |
FYI, that root=/dev/hda3 entry will screw you up later on when you try to add another distro in there unless you specify a root entry for the new distro. Basically what I am saying is:
Right now your / partition for Debian is /dev/hda3 however when you install Slack your root partition ( / ) for it will be something different, maybe /dev/hda5 So you will need to specify that when you create your lilo entry for that new distro: image = /boot/imagename root = /dev/hda5 label = Slacky append = "" read-only Something like that, anyway, just an example for ya ;) Cool |
MasterC, you are way too cool :cool:
MasterC,
You are the best! It boots into Doze, with your prescribed changes. Maybe it just needed the proper name, i.e. Windoze :p Pity that OS is only days from getting a low level format :D As for the issue of root, I created some more partitions along the lines of Markus' securing Debian thread. Should I do something different with hda3, or just realize that when I add Slack I need to pay attention to location of it's / for lilo. And, if you would, if this isn't hijacking a thread... If so, at least it's my own thread I'm hijacking. Could you browse this thread http://www.linuxquestions.org/questi...867#post397867 and give your opinion? I've only been in here about a month, but I've come to respect what you have to say. :study: That's my new nick! TIA |
Thank you for the compliment :)
I'm glad it worked, and I'll take a look at the thread linked up there. As for changing things around, Markus is the man on Debian, I'd stick with his suggestions. Just note the root partition where you will be installing slackware to, it will need to be correct for the distro to boot. Cool |
Have you read Tinkster's review of Slackware 8.1? Until I read that, I would have installed Slack 9.0 from what others have written.
But since I will also install my own kernel (via the 2.4.21 one I will build tonight in Debian probably), would his recommendation of Slack 8.1 over Slack 9.0 be appropriate for me? When I installed Debian it was a toss-up between it and Gentoo. The Verbose walkthrough is what swung me to Debian. All I want is a lean, clean, fast computer. I got really good hardware inside here, and I'd like for it to run as well as it should. TTFN :D |
I've never attempted to move onto 9 as 8.1 has done it all for me no problem. The only problem I see is that most of your newer applications (if you get binaries) are going to be moving to gcc 3.x now that it's the "latest and greatest" and newer developments of applications will likely be migrating.
Similar with Gnome vs Gnome2. Latest and greatest versions of applications will be migrating to gtk2 apps. It's a toss up. You can easily stick with 8.1 for a while, and get TONS of speed out of some decent hardware. Or you could go up to 9 and be required to only use the latest of most applications but still get TONS of speed out of your hardware ;) I'd personally go with 8.1, then do a custom upgrade to GTK2 (as I did already ;) ) for those apps that require it. You retain GTk apps that way as well as welcome the new. You technically could use both versions of GCC as well, but I think that's a bit overboard. I've not had a single problem yet with my 2.9x series of GCC on any newer applications. The same goes both ways though, you could surely get the older GTk libs and install those 'custom' on a Slack 9 system as well and then have the best of both worlds without a need to upgrade to a GCC. It's a toss up, but Tink really knows a thing or 2, things are working just fine for me on Slack 8.1 (with still a lot of default setups) so, I guess, my official recommendation would be 8.1 ;) Cool |
Well presented. Soon as I get this kernel compiled, and my DVD burner recognized, I'll burn that Slack 8.1 iso and install it. Any *pre-install* hints would be appreciated. I will have the 2.4.21 kernel compiled from Debian available at that time - if that matters - and provided I can do it correctly.
Thanks. I appreciate your advice and opinion! |
Pre-install checklist would really not be a huge one. The thing to take most note of is your partition layout and what is installed where.
If you aren't using a seperate /boot that all your distros share, then whichever distro will be "servicing" or "providing" the boot loader (meaning which distro will /etc/lilo.conf live on) will need to have ALL distro's kernel's in it's /boot directory. Good Luck! Have fun :) And don't get too frustrated if things don't work out, someone will be happy to help out ;) Cool |
This is funner than picking peas!
How exactly would I use a separate boot that both Debian and Slack would share? What I have read, especially the lilo documentation, leaves me more confused after I finish than before I start. My /boot is /dev/hda1 and is 100MB.
I document almost everything in my little Linux notebook, since my first RH9 install on 2003/06/25. :rolleyes: :study: :confused: :study: :scratch: :study: :cool: |
| All times are GMT -5. The time now is 08:20 AM. |