an issue related to dual boot on seperate drive

[SsamirR]

hello everybody

im not really new to salix. i have already tried V12. i have an issue now. i have to choose manualy Salix drive from bios so as to log to it. otherwise it will log in windows 10 automaticly. heres some outputs maybe it can help.

Code: Select all

inxi -v 2
System:
  Host: darkstar.example.net Kernel: 5.15.63 x86_64 bits: 64
    Desktop: Xfce 4.16.0 Distro: Salix 15.0
Machine:
  Type: Desktop System: Hewlett-Packard product: HP ProDesk 600 G1 SFF v: N/A
    serial: <superuser required>
  Mobo: Hewlett-Packard model: 18E7 serial: <superuser required>
    BIOS: Hewlett-Packard v: L01 v02.65 date: 07/13/2015
CPU:
  Info: dual core Intel Pentium G3420 [MCP] speed (MHz): avg: 950
    min/max: 800/3200
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    driver: i915 v: kernel
  Display: x11 server: X.Org 1.20.14 driver: loaded: modesetting
    unloaded: vesa resolution: 1680x1050~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics (HSW GT1) v: 4.5 Mesa 21.3.5
Network:
  Device-1: Intel Ethernet I217-LM driver: e1000e
  Device-2: TP-Link TL-WN722N v2/v3 [Realtek RTL8188EUS] type: USB
    driver: r8188eu
Drives:
  Local Storage: total: 698.65 GiB used: 44.23 GiB (6.3%)
Info:
  Processes: 185 Uptime: 2h 23m Memory: 3.72 GiB used: 1.31 GiB (35.1%)
  Shell: Bash inxi: 3.3.12

Code: Select all

udo fdisk -l
Password: 
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500DM002-1BD14
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 8A84AD6D-A53D-4DCB-9C72-5D80DE2A530A

Device         Start       End   Sectors  Size Type
/dev/sda1       2048 209717247 209715200  100G Linux filesystem
/dev/sda2  209717248 964691967 754974720  360G Linux filesystem
/dev/sda3  964691968 976773134  12081167  5.8G Linux swap


Disk /dev/sdb: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: ST3250310AS     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 048FC690-12D4-43BC-BF04-7B3FA5045DB5

Device       Start       End   Sectors   Size Type
/dev/sdb1     2048    923647    921600   450M Windows recovery environment
/dev/sdb2   923648   1128447    204800   100M EFI System
/dev/sdb3  1128448   1161215     32768    16M Microsoft reserved
/dev/sdb4  1161216 488396799 487235584 232.3G Microsoft basic data

Code: Select all

cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append="quiet  vt.default_utf8=1"

boot = /dev/sda
# This option loads the kernel and initrd much faster:
compact

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/salix.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 12,0,10,0,9,9
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 5,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 70,6,14,0

# Standard menu.
# Or, you can comment out the bitmap menu above and 
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda1
  label = Salix
  read-only
# Linux bootable partition config ends

# Chainload other system

other = /dev/sdb2
label = Windows

i added a chainload section on liloconfig. maybe its wrong. i want to be able to see both salix and windows on lilo boot menu so as to choose between them.

[galmei]

hello everybody

im not really new to salix. i have already tried V12. i have an issue now. i have to choose manualy Salix drive from bios so as to log to it. otherwise it will log in windows 10 automaticly. heres some outputs maybe it can help.

Cut listings .................................
End of cut

Code: Select all

# Chainload other system

other = /dev/sdb2
label = Windows

i added a chainload section on liloconfig. maybe its wrong. i want to be able to see both salix and windows on lilo boot menu so as to choose between them.

Is wrong. For a chainloader usage you need more.

Looks like spam to me. We have reached version 5.0. V12 will still take a while. You are probably the Swiss member of the Anti Sociel Club on a war footing. Then go away! Nevertheless a try:
You could have selected the second drive as boot drive in the BIOS or put the MBR on the second drive or lilo was not executed without errors.

[SsamirR]

spam !? what are you talking about !!!

here is my old membership here. name: zazlox
viewtopic.php?f=14&t=3940&start=60

[SsamirR]

i dont understand what do you mean by spam.

[galmei]

spam !? what are you talking about !!!

here is my old membership here. name: zazlox
viewtopic.php?f=14&t=3940&start=60

If you claim to have added a chainload section with this, it makes me suspect it could be spam:

Code: Select all

# Chainload other system

other = /dev/sdb2
label = Windows

If you want to find out more about LILO:
man lilo
and
man lilo.conf
will help you a lot.

I hereby formally apologize for suspecting you of spamming zazlox/SsamirR, Sir.

For me, that settles the issue.

[galmei]

Was the disk /dev/sdb with disk identifier: 048FC690-12D4-43BC-BF04-7B3FA5045DB5 the only and first disk in the computer before?
In other words, did the disk with disk identifier: 8A84AD6D-A53D-4DCB-9C72-5D80DE2A530A come later? Did you upgrade the computer?
Both disks are marked with disklabel type: gpt (GUID Partition Table). This works together with Lilo.
When using Lilo the MasterBootRecord MBR must be stored somewhere. Where is that on your system?

The "chainload section" must not be called so. No chainloading is possible this way.

Correct could be:

Code: Select all

other = /dev/sdb4   # maybe your Windows partition
  table = /dev/sda
  label = Windows

How, on what occasion, was Lilo installed? What did you do to anchor Lilo?

After boot = /dev/sda add lba32 (before the line with the compact statment).
To edit /etc/lilo.conf you need root rights.

When everything is ready, use the call

Code: Select all

sudo lilo -v -t

If no errors were displayed, then again

Code: Select all

sudo lilo -v

Call sudo lilo -v after every change to /etc/lilo.conf and after every kernel refresh.

I don't know what I've forgotten, since I don't have all the information about your system and your actions; but also because I've lost track of this mess.
Just now I see you are using an EFI system on the disk with identifier 048FC690-12D4-43BC-BF04-7B3FA5045DB5. What's with the lilo effort?
/dev/sdb2 923648 1128447 204800 100M EFI System

Now, do you want to use Lilo or EFI? You must know that. You have to figure out for yourself what you want!
Lilo is sufficient for such small hard disks. EFI is therefore probably superfluous. EFI is probably caused by the Windows installer.
If EFI is still active, therefore started Windows, although lilo is in the MBR. I do not know this.
Possibly for the use of Windows the Winows-loader can be started from EFI, perhaps as follows with:

other = /dev/sdb2
label = Windows

As you had already suggested! But this does not result in an explicit chainloading.
Maybe only the call sudo lilo -v and the lba32 extension and the change of table = /dev/sda is missing.

[SsamirR]

its ok. problem solved by installing arcolinux next to windows. now i have all three on grub boot loader.

Code: Select all

Disk /dev/sda: 465,76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500DM002-1BD14
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 8A84AD6D-A53D-4DCB-9C72-5D80DE2A530A

Device         Start       End   Sectors  Size Type
/dev/sda1       2048 209717247 209715200  100G Linux filesystem
/dev/sda2  209717248 964691967 754974720  360G Linux filesystem
/dev/sda3  964691968 976773134  12081167  5,8G Linux swap


Disk /dev/sdb: 232,89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: ST3250310AS     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 048FC690-12D4-43BC-BF04-7B3FA5045DB5

Device         Start       End   Sectors   Size Type
/dev/sdb1       2048    923647    921600   450M Windows recovery environment
/dev/sdb2     923648   1128447    204800   100M EFI System
/dev/sdb3    1128448   1161215     32768    16M Microsoft reserved
/dev/sdb4    1161216 282923279 281762064 134,4G Microsoft basic data
/dev/sdb5  282923281 488396799 205473519    98G Linux filesystem


Disk /dev/loop0: 718,73 MiB, 753645568 bytes, 1471964 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes