MX17 will not allow bios boot install

[theber]

Unfortunately I don't have much control over boot options in my machine's BIOS settings. I might try updating the BIOS when I feel adventurous again.
But during the last attempt to install MX17, the live USB did in fact boot in BIOS mode, so something else is going on. As I've said, I can install practically any OS in BIOS mode, just not MX17. (MX16 installed OK, but there's no way to upgrade to MX17 from MX16.)

[fehlix]

Please show us the system info from within the installed MX17 by pasting the output of the following command

Code: Select all

inxi -Fxz

between the code-tags [code] here [/code]
( press </> above editor box and paste)
Thanks

[theber]

Once I've installed MX17 I can't boot to it, not even after running update-grub from another Linux installation. So I'm giving up the ship, until I update the BIOS or MX18 gets released.

[fehlix]

Unfortunately I don't have much control over boot options in my machine's BIOS settings. I might try updating the BIOS when I feel adventurous again.
But during the last attempt to install MX17, the live USB did in fact boot in BIOS mode, so something else is going on. As I've said, I can install practically any OS in BIOS mode, just not MX17. (MX16 installed OK, but there's no way to upgrade to MX17 from MX16.)

An inxi out put from another Linux might also be helpfull. ( or from running MX Linux Live)
Do you have GPT or MBR partition layouts on your drives?
If you install into GPT drive you need to have an extra "grub-bios" partition,
otherwise bios will not boot from GPT, partition.

[dolphin_oracle]

**wrong thread**

[theber]

Here is the output from inxi while running MX17 live, from a stick with all the EFI folders and files removed:

Code: Select all

$ inxi -Fxz
System:    Host: mx1 Kernel: 4.15.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 tk: Gtk 2.24.31 Distro: MX-17.1_x64 Horizon March 14, 2018 
Machine:   Type: Laptop System: FUJITSU product: LIFEBOOK E782 v: 10601581569 serial: <filter> 
           Mobo: FUJITSU model: FJNB253 v: L3 serial: <filter> UEFI [Legacy]: FUJITSU // Phoenix 
           v: Version 2.04 date: 10/16/2012 
Battery:   ID-1: CMB1 charge: 54.8 Wh condition: 54.8/72.4 Wh (76%) model: Fujitsu CP669832-01 
           status: Full 
CPU:       Topology: Dual Core model: Intel Core i5-3210M bits: 64 type: MT MCP arch: Ivy Bridge 
           rev: 9 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19955 
           Speed: 1197 MHz min/max: 1200/3100 MHz Core speeds (MHz): 1: 1197 2: 1197 3: 1197 
           4: 1197 
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1600x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 3.3 Mesa 13.0.6 
           direct render: Yes 
Audio:     Card-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel 
           v: kernel bus ID: 00:1b.0 
           Sound Server: ALSA v: k4.15.0-1-amd64 
Network:   Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e v: 3.2.6-k port: 4080 
           bus ID: 00:19.0 
           IF: eth0 state: down mac: <filter> 
           Card-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel 
           bus ID: 0a:00.0 
           IF: wlan0 state: up mac: <filter> 
Drives:    HDD Total Size: 473.31 GiB used: 47.8 MiB (0.0%) 
           ID-1: /dev/sda vendor: Toshiba model: MK5061GSYN size: 465.76 GiB 
           ID-2: /dev/sdb type: USB model: LaCie iamaKey size: 7.55 GiB 
Partition: ID-1: / size: 2.92 GiB used: 47.8 MiB (1.6%) fs: overlay dev: ERR-102 
           ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda8 
Sensors:   System Temperatures: cpu: 58.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 206 Uptime: 4m Memory: 3.70 GiB used: 839.9 MiB (22.1%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.10 

While running MX17 live I also verified that the system was using BIOS boot. I am writing this mail while using Mint 19, which also booted in BIOS mode.

[dolphin_oracle]

you might want to check your partitions to see if a boot flag needs enabled. if the device uses a gpt table, the boot flag is not set on the gpt partition you want to boot from.

[theber]

I think that I am using MBR partitions:

Code: Select all

$ sudo parted -l
[sudo] password for theber: 
Model: ATA TOSHIBA MK5061GS (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

[dolphin_oracle]

yep.

I wonder if the boot flag didn't get set for some reason.

[fehlix]

What is actually your current boot loader?
As you wrote above you recovered Win-MBR?
How do you boot into grub-menu or into the other Linux (Linux Mint) ?
You wrote you did run update-grub from within another linux?
Was a new MX17 menu entry generated? What did you mean with cannot boot into MX17? No menu-entry ? error mesg?