Updating Lilo

[happydog500]

In Mint, I had a "Linux" HD and a "Windows" HD. I unhook my Windows and install linux on the only drive. After, I plug in the Windows HD. After I boot, I run, sudo apt get update-grub The next time I boot, I get grub and windows to chose from.

I did the same thing with Salix. I plugged in my windows HD, went to "Lilo setup." It doesn't list any OS other then Salix. When I try to open the other drives, I'm "unable to mount" the drive.

What do I need to do to access the other drives, and, have windows choice on boot up?

Thank you,
Chris.

[mimosa]

Regarding mounting windows partitions, this is a Windows problem and easy to fix:

viewtopic.php?f=30&t=7091

Are you booting Linux with legacy or UEFI? Presumably, this is the 64 bit Salix?

If so, you should be able to boot everything with UEFI, using refind. However, some users have experienced problems with the latest version so it may be better to try the previous one. If you search the forums for refind, you should find a thread with all relevant information.

On the other hand, if you turn off windows fast boot as described above, perhaps lilosetup will work for you booting in legacy. But UEFI/refind is probably the best way to go if you can. I'm not even sure if Lilosetup still works with UEFI machines.

[happydog500]

I'll go check, default is "auto" for UEFI. Salix64 bit. No, just a real quick note while I work on the other salix problems. Other distros don't have a problem. Salix does. That makes it a Salix problem. I have fast boot turned off already. If you have Linux installed, try out several distros and they work, then Salix doesn't, doesn't sound like a Windows problem to me.

I am so glad I did more research on Salix 14. I thought I was just stupid. One that was very positive about it said,

Lilo setup:
The "Lilo Setup" application is unfortunately flawed by design. After a bit it went on and added, "The Lilo Setup application is to be frank, just horrible and deviates from the design and logic of the other applications.

Didn't realize how bad it was until I installed it.

Thanks for the reply,
Chris.

[mimosa]

If you're booting with UEFI, you shouldn't be using Lilosetup. Use refind (but please search the forum for a link to download the earlier version, rather than installing it from the repositories - there was a bug in a recent upgrade, fixed now, but may take a little while to filter through).

As for accessing windows partitions, even Ubuntu is affected. Perhaps you are having difficulty for another reason than fast boot, and if you post about the problem in detail, someone may be able to help.

[laprjns]

What version of Salix are you using? The research you did found a four year old review of Salix 14.0. Are you using 14.0 or 14.2? Is you system uefi or bios? Can you please open a terminal, type in the following command:

Code: Select all

ls /sys/firmware/efi/

and post the output here.

Can't help you until you tells us this information

[happydog500]

If you're booting with UEFI, you shouldn't be using Lilosetup. Use refind (but please search the forum for a link to download the earlier version, rather than installing it from the repositories - there was a bug in a recent upgrade, fixed now, but may take a little while to filter through).

As for accessing windows partitions, even Ubuntu is affected. Perhaps you are having difficulty for another reason than fast boot, and if you post about the problem in detail, someone may be able to help.

I had been using the "auto" (Default) but switched to EFI during this thread.

EFI is enabled, this is what I got when I ran the command.

Code: Select all

[~]$ ls /sys/firmware/efi/
ls: cannot access '/sys/firmware/efi/': No such file or directory
[~]$

Thank you for helping me,
Chris.

[mimosa]

Which version of Salix are you using?

Code: Select all

 cat /etc/slackware-version

[laprjns]

EFI is enabled, this is what I got when I ran the command.

Code: Select all

[~]$ ls /sys/firmware/efi/
ls: cannot access '/sys/firmware/efi/': No such file or directory
[~]$

Assuming that you ran that command from your Salix install then it indicates that Salix is running in legacy (bios mode), not efi. So if you really do have EFI enabled then you must have it running CMS mode where it can boot bios boat loaders.