New computer, Windows 7 won't show in Linux GRUB menu

[Goatmilk]

Hey everybody

I really have a hard time finding a title for this one...

I had to ditch that awful Dell I got last December and get a new 'new' computer, and I foolishly decided to install my MX Linux 25 KDE from scratch, rather than trying to copy the old one. Reasons: Being the eternal newbie, I've done so many trial and error operations on the old one that I felt a new clean reinstall was in order. Old Windows habits die hard, I guess. Besides, I wanted a system where I know what's what, not my usual, "No idea how I got here, but it somehow works..."

And of course, I had to drag my ancient Windows 7 x86 along, which is why the new computer has two hard drives and two operation systems. Right now, the computer runs up to MX Linux and arrives at its welcome screen, offering the following choices to pick from:

MX Linux 25.1 Infinity
Advanced options for MX Linux 25.1 Infinity
Memory Test (64-bit UEFI)
System setup


When I want Win7, I'll have to press F12 along the way. It works, but BEFORE, on the old computer, it simply offered Windows 7 as an option on the welcome screen (of course I don't know how I did that). As far as I recall, Linux did it by itself, because Windows was already there. That's why I had Windows installed first again, hoping that Linux would figure it out. Obviously it didn't. It does find the Windows drives inside Linux's Disk Manager, I can mount and open them alright.

Any way how I could get the Windows 7 option into the welcome menu? I must admit I didn't dare pressing the 'system setup', being scared it might mess with the Linux installation.


Talking about the Linux installation - it does work fine as far as I can see for now, but it won't accept chrome-based browsers. I tried Brave and Vivaldi, both install with no apparent glitch but then appear merely as greyed out screens that won't react to anything. You have to kill the processes in order to close them. Internet advice like "Do 'vivaldi --disable-gpu'" achieved nothing.

Firefox and Librewolf, however, work splendidly.

I've included the system info below. The 'new' computer is, of course, not entirely new, due to lack of funds and my unholy obsession with Windows 7 (32bit, to boot), but as far as I can tell by now, it's a nice enough machine.

Any help regarding those two problems is highly appreciated. I don't know if I should have put them in different posts, when they're different problems, but since both popped up with the new computer, they might be related.

Thanks and cheers!

System:
  Kernel: 6.12.73+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0 clocksource: tsc
    avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.73+deb13-amd64 root=UUID=<filter>
    ro quiet splash
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.13.0 wm: kwin_wayland vt: 1
    dm: SDDM Distro: MX-25.1_KDE_x64 Infinity Nov 9 2025 base: Debian GNU/Linux 13 (trixie)
Machine:
  Type: Desktop System: Wortmann_AG product: TERRA_PC v: N/A serial: <superuser required> Chassis:
    type: 6 serial: <superuser required>
  Mobo: FUJITSU model: D3236-S1 v: S26361-D3236-S1 serial: <superuser required>
    part-nu: S26361-Kxxx-Vyyy uuid: <superuser required> UEFI: FUJITSU // American Megatrends
    v: 4.6.5.4 R1.34.0 for D3236-S1x date: 02/20/2020
CPU:
  Info: model: Intel Core i7-4790 bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
    note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x28
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 800 min/max: 800/3600 scaling: driver: intel_cpufreq governor: schedutil
    cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 57461
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GK110 [GeForce GTX 780] vendor: Palit Microsystems driver: nouveau v: kernel
    non-free: series: 470.xx+ status: legacy-active (EOL~2024-09-xx) arch: Kepler-2 code: GKxxx
    process: TSMC 28nm built: 2012-2018 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s ports: active: DVI-I-1 empty: DP-1,DVI-D-1,HDMI-A-1 bus-ID: 01:00.0
    chip-ID: 10de:1004 class-ID: 0300 temp: 27.0 C
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6 compositor: kwin_wayland
    driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: 0
  Monitor-1: DVI-I-1 model: EIZO NANAO S2411W serial: <filter> built: 2007 res: mode: 1680x1050
    hz: 60 scale: 100% (1) dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 616mm (24.2")
    ratio: 16:10 modes: max: 1920x1200 min: 720x400
  API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau device: 1 drv: swrast
    gbm: drv: nouveau surfaceless: drv: nouveau wayland: drv: nouveau x11: drv: nouveau
  API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 25.3.3-1~mx25ahs glx-v: 1.4 direct-render: yes
    renderer: NVF1 device-ID: 10de:1004 memory: 2.92 GiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.309 layers: 5 device: 0 type: discrete-gpu name: GeForce GTX 780 (NVK
    GK110B) driver: mesa nvk v: 25.3.3-1~mx25ahs device-ID: 10de:1004 surfaces: xcb,xlib,wayland
    device: 1 type: cpu name: llvmpipe (LLVM 19.1.7 256 bits) driver: mesa llvmpipe
    v: 25.3.3-1~mx25ahs (LLVM 19.1.7) device-ID: 10005:0000 surfaces: xcb,xlib,wayland
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Fujitsu Solutions
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
  Device-2: NVIDIA GK110 High Definition Audio vendor: Palit Microsystems driver: snd_hda_intel
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
    chip-ID: 10de:0e1a class-ID: 0403
  API: ALSA v: k6.12.73+deb13-amd64 status: kernel-api tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.5 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I217-LM vendor: Fujitsu Solutions driver: e1000e v: kernel port: f040
    bus-ID: 00:19.0 chip-ID: 8086:153a class-ID: 0200
  IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel I210 Gigabit Network vendor: Fujitsu Solutions driver: igb v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 04:00.0 chip-ID: 8086:1533 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Info: services: NetworkManager, nfsd, smbd, systemd-networkd, wpa_supplicant
Drives:
  Local Storage: total: 894.26 GiB used: 151.29 GiB (16.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SEDC500M480G size: 447.13 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: J2.7
    scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Patriot model: Burst size: 447.13 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 61.3
    scheme: MBR
Partition:
  ID-1: / raw-size: 83.01 GiB size: 81.15 GiB (97.76%) used: 9.86 GiB (12.2%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 800 MiB size: 798.4 MiB (99.80%) used: 8.8 MiB (1.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 355.53 GiB size: 348.88 GiB (98.13%) used: 88.62 GiB (25.4%) fs: ext4
    dev: /dev/sda4 maj-min: 8:4
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3
    maj-min: 8:3
Sensors:
  System Temperatures: cpu: 35.0 C pch: 34.5 C mobo: N/A gpu: nouveau temp: 27.0 C
  Fan Speeds (rpm): N/A gpu: nouveau fan: 780
Repos:
  Packages: pm: dpkg pkgs: 2755 libs: 1555 tools: apt, apt-get, aptitude, nala, synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/vivaldi-archive.list
  Active apt repos in: /etc/apt/sources.list.d/debian.sources
    1: deb http://deb.debian.org/debian/ trixie main  contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ trixie-security main  contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian/ trixie-updates  main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
    1: deb [arch=amd64] https://repo.librewolf.net librewolf main
  Active apt repos in: /etc/apt/sources.list.d/mx.sources
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ trixie main  non-free
    2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ trixie ahs
Info:
  Memory: total: 32 GiB available: 31.27 GiB used: 1.87 GiB (6.0%)
  Processes: 296 Power: uptime: 28m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 12.45 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 257
    default: graphical tool: systemctl
  Compilers: gcc: 14.2.0 Client: shell wrapper v: 5.2.37-release inxi: 3.3.38
Boot Mode: UEFI

 

[Brickwizard]

Your windows was probably not connected when you installed MX so grub didn't see it. Open MX, open terminal and run
sudo update-grub

 

[Goatmilk]

Thanks, but it didn't change anything.

Found this website where some poor sod pressed the "System setup" and ran into trouble.
https://askubuntu.com/questions/1199066/dual-boot-grub-loader-system-setup-option-broke-everything

From the answer, I got this:

Quote: "I'm not sure if you're talking about UEFI Boot Order or simply grub boot order. It is because Grub does not include a system setup entry but UEFI Boot Order does"

Never knew there is a difference, but okay. I'm not sure at all if I should try what he suggested as I cannot make head or tails about my own stuff, but did run "efibootmgr" to see what's all in my own whatchamacallit.

Result:

root@Sam:/home/owl# efibootmgr
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0006,0008,0009,0000,0004,0005,0007
Boot0000* Diagnostic Program MemoryMapped(11,0xcd0b9004,0xcd9db003)/FvFile(6f1cf8df-2398-4b3b-aaa6-35d97d4a76e9)
Boot0001* MX Linux HD(1,MBR,0xf2d8bc08,0x800,0x190000)/File(\EFI\MX\shimx64.efi)
Boot0004 IBA GE Slot 00C8 v1550 BBS(Network,,0x0)0000424f
Boot0005 IBA GE Slot 0400 v1550 BBS(Network,,0x0)0000424f
Boot0006* Patriot Burst BBS(HD,,0x0)0000424f
Boot0007 HL-DT-ST DVDRAM GH24NSD1 BBS(CDROM,,0x0)0000424f
Boot0008* KINGSTON SEDC500M480G BBS(HD,,0x0)0000424f
Boot0009* WD Elements 25A2 1019 BBS(HD,,0x0)0000424f
root@Sam:/home/owl#


Sooo... I know Linux is on the Kingston sdd and Windows is on the Patriot Burst ssd.

WD Elements is my external backup hdd.

Why is the Kingston aka Linux listed twice... or is it?

How does that even correspond to:
MX Linux 25.1 Infinity
Advanced options for MX Linux 25.1 Infinity
Memory Test (64-bit UEFI)
System setup
?

 

[Goatmilk]

Installed "Grub Customizer" and saw at least that the last entry (System setup) is marked as "menu entry/script: uefi firmware"

As it seems, Windows 7 is not even present, even though I can get there via F12

By the way, not even the F12 choices say anything about Windows, the choices are those:

MX Linux
P0: Patriot Burst
P4: Kingston SEDC500M480G
Diagnostic Program
Enter Setup

Windows sits on the Patriot Burst and runs quite fine.

Could I safely try the "Diagnostic Program" or might I end up like the poor lad from the website (who ended up removing his drive)?

 

[Condobloke]

It isn't broken...?

(you know the rejoinder here, I am certain).....

 

[KGIII]

Installed "Grub Customizer" and saw at least that the last entry (System setup) is marked as "menu entry/script: uefi firmware"

Some folks here have issues with Grub Customizer.

I've never personally had issues with it, but others have reported problems. So, I'm urging you to exercise caution and ensure that you have backups that are viable for your recovery process.

 

[osprey]

Installed "Grub Customizer" and saw at least that the last entry (System setup) is marked as "menu entry/script: uefi firmware"

As it seems, Windows 7 is not even present, even though I can get there via F12

By the way, not even the F12 choices say anything about Windows, the choices are those:

MX Linux
P0: Patriot Burst
P4: Kingston SEDC500M480G
Diagnostic Program
Enter Setup

Windows sits on the Patriot Burst and runs quite fine.

Could I safely try the "Diagnostic Program" or might I end up like the poor lad from the website (who ended up removing his drive)?

The usual way to get grub to see all the installed distributions is to have the configuration: GRUB_DISABLE_OS_PROBER= set so that it appears in the file /etc/default/grub like this:

GRUB_DISABLE_OS_PROBER=false

Grub should then do its probing to check all installed operating systems. After ensuring that the option appears in /etc/default/grub, (writing it in if necessary) one needs to update grub. On rebooting, grub then usually presents the installed systems in the menu, if the menu is configured to appear. Then the user can select what they wish to boot from the menu.

 

[Goatmilk]

Thanks for the warning, KGIII - I'm a scaredy cat when it comes to pressing buttons; I haven't even dared to run the "diagnostic program" in the F12 menu (almost as ominous as 'enter setup'...)

@osprey , I've checked it with "sudo nano /etc/default/grub" and it seems fine. No # in front of it or anything.

Condobloke, I hear you.....

 

[Goatmilk]

If it helps any:

owl@Sam:~
$ sudo fdisk -l
[sudo] password for owl:
Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: Patriot Burst
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: dos
Disk identifier: 0x16db3a67

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1  *         2048    206847    204800  100M  7 HPFS/NTFS/exFAT
/dev/sda2          206848 105084927 104878080   50G  7 HPFS/NTFS/exFAT
/dev/sda3       105084928 937699327 832614400  397G  7 HPFS/NTFS/exFAT


Disk /dev/sdb: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: KINGSTON SEDC500
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: dos
Disk identifier: 0xf2d8bc08

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1            2048   1640447   1638400   800M ef EFI (FAT-12/16/32)
/dev/sdb2  *      1640448 175720447 174080000    83G 83 Linux
/dev/sdb3       175720448 192104447  16384000   7.8G 83 Linux
/dev/sdb4       192104448 937699327 745594880 355.5G 83 Linux
owl@Sam:~
$ ^C
owl@Sam:~
$

 

[wizardfromoz]

Sam, I have a few avenues ahead that you might like to consider, but first, I would reiterate what my bestie, Brian @Condobloke has commented above.

If it isn't broken...?

...don't fix it?

Given you can get Windows up through F12, that might be as good as or better than, running risks of losing your XP.

That being said, we cannot advocate the continued use of XP, as its shelf life expired January 14 2020, over 6 years ago.

WIZARD'S OBSERVATIONS

1. Both the Kingston (for MX) and the Patriot (for XP) are listed in your inxi output with a scheme of MBR, not GPT. That suggests that you might be better served running the computer under Legacy Mode. I will detail more below.

2. Installed "Grub Customizer" and saw at least that the last entry (System setup) is marked as "menu entry/script: uefi firmware"

   My feelings on GC are fairly well known, and that is that I advise against using it, without taking a Timeshift snapshot first. Now that you have used it, see how hard it is to remove it and revert the changes to your boot system files.
3. You are using American Megatrends 4.6.5.4 for your BIOS

With that BIOS, a little bit of AI (Google assisted) search suggests that you can change the boot method to Legacy using the following steps:

AI Overview



To enable or configure
Legacy Mode in an American Megatrends (AMI) BIOS (often identified by Core Version 4.6.5.4), you typically need to adjust the Compatibility Support Module (CSM) settings, which allows modern UEFI systems to boot older operating systems or drives formatted with MBR.

Steps to Enable Legacy Mode in AMI BIOS

1. Enter BIOS: Restart your computer and immediately press F2, Delete, or Esc (depending on your manufacturer) repeatedly to enter the BIOS Setup utility.
2. Navigate to Boot Menu: Use the arrow keys to navigate to the Boot tab.
3. Locate CSM/Legacy Settings: Look for a menu labeled CSM (Compatibility Support Module) or Boot Mode.
4. Configure Settings:
   • Set Launch CSM to Enabled or Always.
   • Change Boot Device Control to Legacy Only or UEFI and Legacy.
   • Set Boot from Storage Devices to Legacy Only.
5. Disable Secure Boot: Legacy mode often requires Secure Boot to be disabled. Go to the Security or Boot tab, select Secure Boot, and set it to Disabled.
6. Save and Exit: Press F10 to save your changes and exit

Once the computer reboots, if you have access to MX, I would enter it and try

sudo update-grub

and reboot.

It wouldn't hurt, too to show us the content from

cat /etc/default/grub

in code tags.

The above is at your discretion, of course.

HTH

Chris

 

[Goatmilk]

Hi @wizardfromoz thanks for the reply. I did install Grub Customizer, but up to now have just looked around in it and not actually done anything else. I've learned the hard way to be careful here (and seeing how it offers to put glitter and tinsel in your boot menu, I can imagine what a poisonous booby trap it might be).

Right now, I'm trying to learn what exactly goes on inside the new machine. It's the same Windows 7 Pro NTLite/WSUS-Offline installation I've used for years. The same MX Linux 25.1 Infinity KDE installation I used last time. That exact same combination produced a beautiful boot menu with both options on the last machine, without me doing anything.

But I've got a new computer now, so you might be right that I'd have to look at the BIOS.

Here is the cat /etc/default/grub:

owl@Sam:~
$ cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(unset PRETTY_NAME; (. /etc/lsb-release; echo ${PRETTY_NAME:?}) 2>/dev/null || echo Debian)"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=1024x768

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

GRUB_DISABLE_OS_PROBER=false

GRUB_THEME="/boot/grub/themes/mx_linux/theme.txt"

owl@Sam:~
$

By the way, Windows 7 is purely for offline use, I wouldn't go online with it and I don't have to. I also keep CondoBloke's words in mind.

But then again: you don't learn if you don't try.


edit for p.s.
Went to BIOS and looked at the CSM:
Launch CSM is enabled
Boot option filter = UEFI and Legacy
Launch PXE OpRom policy = Legacy only
Launch Storage OpRom policy = Legacy only
Launch video OpRom policy = Legacy only

 

[wizardfromoz]

Thanks for that.

If it were me, I would try the following

1. In BIOS, flip the switch on

2. Boot option filter = UEFI and Legacy

   to Legacy only, and save changes and reboot to see what results.
3. If it doesn't work, back into BIOS and reset it.
4. With your Grub, I would change the line

5. GRUB_DISABLE_RECOVERY="true"

   to change true to false, save changes and exit then run sudo update-gruband reboot. This will give you an extra capability for troubleshooting which we can explain more at another time and place.

Your choice whether to try these of course.

HTH

Wizard

 

[f33dm3bits]

It's not safe to use Windows 7 online anymore because of it being End of Life and not getting security updates, unless you disconnect the network connection when using it.

 

[Goatmilk]

@wizardfromoz - Thanks so much for sticking to it. Unfortunately, neither suggestion did much.

Changing the boot option filter to "Legacy only" resulted in the computer starting up into Windows only. Somehow, it had changed the boot option order, but bringing Linux back up to spot 1 only had the computer starting into Linux.

I reversed it again, back to "UEFI and Legacy", and with Linux on top of the list.

Setting "GRUB_DISABLE_RECOVERY="true"" to "false" didn't change a thing, it only felt like the system started a bit slower. Put it back again. By the way, in the grub file it also said I could have simply blotted it out by putting a # in front of the line, but I didn't try that.

Do you happen to have an opinion to "MX Boot Repair"? It's included in MX Linux's "MX Tools" and offers 3 options:

1. Reinstall GRUB bootloader on ESP, MBR or PBR (root)
2. Repair GRUB configuration file
3. Regenerate initramfs images
(two more, actually but they're for Legacy boot only)

No. 2 looks particularly tempting right now...


@f33dm3bits - As said, Win7 doesn't go online anymore. That's what Linux is for...

 

[f33dm3bits]

@f33dm3bits - As said, Win7 doesn't go online anymore. That's what Linux is for...

Good to know, I missed that

 

[Goatmilk]

I just ran

sudo os-prober

It returned nothing, which according to the webs means that no other operating systems are found.

But it should find Windows, right? Even on another hard drive?

 

[osprey]

I just ran

sudo os-prober

It returned nothing, which according to the webs means that no other operating systems are found.

But it should find Windows, right? Even on another hard drive?

A couple of points come to mind. You may have attended to them, but I mention them just in case.

Both operating systems, linux and MS need to have been installed in the same mode, i.e. BIOS or UEFI.
Secondly, for the external disk to be seen, it has to be mounted into the linux system before updating grub, or grub won't see it subsequently.

 

[rtoledo2002]

I'm having fun reading this thread , I'm a Old dog since the first days of GRUB and other(my apologies my memory is going bye bye , need new memory chips and prevegen barely helps) . I just registered here just to post.

Reason for enjoyment is being retired and recovering from cancer ,(keeping busy is good). I started compiling kernel 7.0 rc1 and ended up with 3 versions in grub so I had to search how to go in and remove the compilations and entries in grub completely . that was no problem , BUT in the old days you could see lines about windows and linux kernels in grub and I remember editing to my likes.

I have tried several settings compiling 7.0rc1 , but no matter what , it compiles but does not load and when I try the recovery 7.0 it say " kernel needs to load ". this is why I removed it all from GRUB .

now that one line " baffles me " >> GRUB_DISTRIBUTOR="$(unset PRETTY_NAME; (. /etc/lsb-release; echo ${PRETTY_NAME:?}) 2>/dev/null || echo Debian)"

I want to remove ANY mention about Windows as that resides in nvem0 and is set as a secureboot uefi partition and grub can not handle it, long story , that I had Debian already installed on a second nvme externally attached to my Asus Zenbook s16 lid , then after having disabled recall when the laptop arrived (registry hacks from youtube videos ) I ended up damaging it enough that even with a fresh "repair" it never worked , so I bought a new 4TB nvme, opened up the laptop and replaced the original ssd.

So I turned on secure boot back on in the bios and did a full fresh install with secure boot on , and finally got 25h2 76200.7800 to get recall working (my memory is forcing me to test RECALL and see what the hype is all about .

so Grub can't handle that windows partition as it was installed WHEN the bios was set to non-secure boot .

so to get to the point FINALLY , I want to play around in grub and see if I can replace that grub distributor line with a less auto option where I can just have it show Linux only options and forget Windows. I use the ESC key at bootup to choose between Debian nvme and Windows 11 nvme.

Finally I hope this is not stealing this thread and would love any relevant links, If the administrator wants to please move it to a new thread and let me know so I can follow it ( rtoledo2002 yahoo OR rtoledo2 gmail )
Best Regards
Roman Toledo Casabona

 

[Goatmilk]

A couple of points come to mind. You may have attended to them, but I mention them just in case.

Both operating systems, linux and MS need to have been installed in the same mode, i.e. BIOS or UEFI.
Secondly, for the external disk to be seen, it has to be mounted into the linux system before updating grub, or grub won't see it subsequently.

Well, Linux can see the other drives:

$ lsblk -o NAME,FSTYPE,LABEL,UUID,SIZE,TYPE
NAME   FSTYPE LABEL           UUID                                   SIZE TYPE
sda                                                                447.1G disk
├─sda1 vfat   EFI-SYSTEM      E990-032C                              800M part
├─sda2 ext4   rootMX25        a0eb7f07-3015-474a-ae3c-c675cd6cd823    83G part
├─sda3 swap   swapMX          8245743c-e23c-4ad8-9ded-ca59d5ed453c   7.8G part
└─sda4 ext4   homeMX          788be469-9775-4398-8b6a-5c82d8d10a64 355.5G part
sdb                                                                447.1G disk
├─sdb1 ntfs   System Reserved 7098F43298F3F506                       100M part
├─sdb2 ntfs   WinCellar       D2A023A2A0238BD3                        50G part
└─sdb3 ntfs   WinSeven        90AEF058AEF03874                       397G part
sdc                                                                  1.8T disk
└─sdc1 ntfs   Elements        8AC48D6DC48D5BF7                       1.8T part
sdd                                                                    0B disk
sde                                                                    0B disk
sdf                                                                    0B disk
sdg                                                                    0B disk
sr0                                                                 1024M rom

I must admit I don't know if Windows 7 was installed in BIOS or EFI. As said, it's the same old Windows NTLite version I've used last time - and last time the grub worked just fine.

By the way, I can mount and open the Windows drives in Linux.

 

[rtoledo2002]

Well, Linux can see the other drives:

$ lsblk -o NAME,FSTYPE,LABEL,UUID,SIZE,TYPE
NAME   FSTYPE LABEL           UUID                                   SIZE TYPE
sda                                                                447.1G disk
├─sda1 vfat   EFI-SYSTEM      E990-032C                              800M part
├─sda2 ext4   rootMX25        a0eb7f07-3015-474a-ae3c-c675cd6cd823    83G part
├─sda3 swap   swapMX          8245743c-e23c-4ad8-9ded-ca59d5ed453c   7.8G part
└─sda4 ext4   homeMX          788be469-9775-4398-8b6a-5c82d8d10a64 355.5G part
sdb                                                                447.1G disk
├─sdb1 ntfs   System Reserved 7098F43298F3F506                       100M part
├─sdb2 ntfs   WinCellar       D2A023A2A0238BD3                        50G part
└─sdb3 ntfs   WinSeven        90AEF058AEF03874                       397G part
sdc                                                                  1.8T disk
└─sdc1 ntfs   Elements        8AC48D6DC48D5BF7                       1.8T part
sdd                                                                    0B disk
sde                                                                    0B disk
sdf                                                                    0B disk
sdg                                                                    0B disk
sr0                                                                 1024M rom

I must admit I don't know if Windows 7 was installed in BIOS or EFI. As said, it's the same old Windows NTLite version I've used last time - and last time the grub worked just fine.

By the way, I can mount and open the Windows drives in Linux.

Since I have time to kill , I went ahead and re-installed debian 13.2 this time with BIOs set to secure , but grub tries and I get the beloved bitlocker screen , so I just modified grub to not probe OS .

moving on did distro upgrade to sid , but when i try to compile 7.0 i get error 2 . Funny I was not getting that error when it was on the older 13.2 setup.

oh well just have to wait , MR. no patience does not like that LOL