LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-28-2020, 12:56 PM   #16
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,001

Rep: Reputation: 689Reputation: 689Reputation: 689Reputation: 689Reputation: 689Reputation: 689

If it isn't a whole lot copy and past the text in a reply surrounded by code tags
 
1 members found this post helpful.
Old 03-28-2020, 03:44 PM   #17
jwc1936
LQ Newbie
 
Registered: Jul 2014
Posts: 16

Original Poster
Rep: Reputation: Disabled
/windows:
BOOTNXT
BOOTSECT.BAK
Boot
System Volume Information
bootmgr

/windows/Boot:
BCD
BCD.LOG
BCD.LOG1
BCD.LOG2
BOOTSTAT.DAT
Fonts
Resources
bg-BG
bootuwf.dll
bootvhd.dll
cs-CZ
da-DK
de-DE
el-GR
en-GB
en-US
es-ES
es-MX
et-EE
fi-FI
fr-CA
fr-FR
hr-HR
hu-HU
it-IT
ja-JP
ko-KR
lt-LT
lv-LV
memtest.exe
nb-NO
nl-NL
pl-PL
pt-BR
pt-PT
qps-ploc
qps-plocm
ro-RO
ru-RU
sk-SK
sl-SI
sr-Latn-RS
sv-SE
tr-TR
uk-UA
zh-CN
zh-TW

/windows/Boot/Fonts:
chs_boot.ttf
cht_boot.ttf
jpn_boot.ttf
kor_boot.ttf
malgun_boot.ttf
malgunn_boot.ttf
meiryo_boot.ttf
meiryon_boot.ttf
msjh_boot.ttf
msjhn_boot.ttf
msyh_boot.ttf
msyhn_boot.ttf
segmono_boot.ttf
segoe_slboot.ttf
segoen_slboot.ttf
wgl4_boot.ttf

/windows/Boot/Resources:
bootres.dll
en-US
es-ES
fr-FR

/windows/Boot/Resources/en-US:
bootres.dll.mui

/windows/Boot/Resources/es-ES:
bootres.dll.mui

/windows/Boot/Resources/fr-FR:
bootres.dll.mui

/windows/Boot/bg-BG:
bootmgr.exe.mui

/windows/Boot/cs-CZ:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/da-DK:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/de-DE:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/el-GR:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/en-GB:
bootmgr.exe.mui

/windows/Boot/en-US:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/es-ES:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/es-MX:
bootmgr.exe.mui

/windows/Boot/et-EE:
bootmgr.exe.mui

/windows/Boot/fi-FI:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/fr-CA:
bootmgr.exe.mui

/windows/Boot/fr-FR:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/hr-HR:
bootmgr.exe.mui

/windows/Boot/hu-HU:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/it-IT:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/ja-JP:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/ko-KR:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/lt-LT:
bootmgr.exe.mui

/windows/Boot/lv-LV:
bootmgr.exe.mui

/windows/Boot/nb-NO:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/nl-NL:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/pl-PL:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/pt-BR:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/pt-PT:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/qps-ploc:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/qps-plocm:
bootmgr.exe.mui

/windows/Boot/ro-RO:
bootmgr.exe.mui

/windows/Boot/ru-RU:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/sk-SK:
bootmgr.exe.mui

/windows/Boot/sl-SI:
bootmgr.exe.mui

/windows/Boot/sr-Latn-RS:
bootmgr.exe.mui

/windows/Boot/sv-SE:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/tr-TR:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/uk-UA:
bootmgr.exe.mui

/windows/Boot/zh-CN:
bootmgr.exe.mui
memtest.exe.mui

/windows/Boot/zh-TW:
bootmgr.exe.mui
memtest.exe.mui

/windows/System Volume Information:
tracking.log
 
Old 03-28-2020, 08:26 PM   #18
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,001

Rep: Reputation: 689Reputation: 689Reputation: 689Reputation: 689Reputation: 689Reputation: 689
That is all windows boot files on that partition. I suspect that windows 10 was installed in legacy/csm as there is no efi parition on sda and there is a windows boot partition. As root post the output of
Code:
parted -l
If this is the case you will need to re-enable legacy mode in the bios if you disabled it.

Last edited by colorpurple21859; 03-28-2020 at 08:44 PM.
 
Old 03-28-2020, 09:31 PM   #19
jwc1936
LQ Newbie
 
Registered: Jul 2014
Posts: 16

Original Poster
Rep: Reputation: Disabled
Yes,I agree with you there. My issue is how to go about that. There is a ~1M partition above the windows stuff, listed as free space and another free space partition about the same size farther down. Below the windows partitions is the linux stuff, which I can remove. The procedure with cfdisk is to create a uefi partition of 100M. Is it ok to just remove the linux partition and install the uefi partition below windows? I can then create a linux partition and reinstall if I want to but I don't really need linux on that disk because linux is on /dev/sdb. If I do the above will I get a bootable windows os?
 
Old 03-28-2020, 09:47 PM   #20
jwc1936
LQ Newbie
 
Registered: Jul 2014
Posts: 16

Original Poster
Rep: Reputation: Disabled
Parted -l /dev/sda gives the response error: can't have overlapping partitions.
Here is the output from gdisk /dev/sda:

GPT fdisk (gdisk) version 1.0.5

Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
typing 'q' if you don't want to convert your MBR partitions
to GPT format!
***************************************************************


Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
 
Old 03-28-2020, 10:26 PM   #21
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,001

Rep: Reputation: 689Reputation: 689Reputation: 689Reputation: 689Reputation: 689Reputation: 689
To boot windows in efi mode you will need to convert the windows. There are several how-to's to convert from within windows, not sure it is possible from linux. Is lilo installed to the mbr of sda1? With slackware installed in efi mode you will have to go into bios/firmware to select to boot windows. If lilo is still installed to the mbr of sda, you will need to do a windows boot repair. The other option would be to install slackware grub to the mbr of sda in legacy mode.
to do that run the following as root
Code:
grub-install --target=i386-pc /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg
then boot in legacy mode.
 
Old 03-29-2020, 02:53 AM   #22
Regnad Kcin
Member
 
Registered: Jan 2014
Location: Beijing
Distribution: Slackware 64 -current .
Posts: 262

Rep: Reputation: 169Reputation: 169
Strongly recommend refind.
Time spent studying with Rod's Books site will save you hours of consternation.
Refind frequently saves me serious headaches and disasters because I am frequently tweaking my system and experimenting with OSes. (Slackware Professional Linux 64-current is my daily driver)

It is good to have a rescue kit that consists of a slackware boot USB, a windows boot USB and a gparted USB if you are fiddling with your hardware or your OSes.

Note that once you have refind installed and you have the display of the different bootOSes it finds, you can use the F2 key to get a boot sub-menu where you may be able to find an option that saves your bacon.

Another thing you can try is the uefi boot menu in your "bios" UEFI system setup (press F2 or DEL or whatever while system is booting). You should become familiar with its options and what it can do for you. Sometimes the default page-thru in eliloconfig can reconfigure your EFI boot order if you don't read the fine print about what is going to be done if you press ENTER and continue.

once you get windows to boot, there is a complex repair option for fixing a scrozzled efi which Rod's Books (the refind site) details. I have had to use that on 3 different occasions with different machines due to various lack of foresight happenings.

Of course there is not always anything wrong with zeroing out everything and starting over and a clean system is a joy for awhile.

Backups are essential for saving essential stuff. Those USB to SATA dongles with the supplemental power supply are great to have around.

It's also good to learn the technique of booting Slackware from a USB, mounting the old slackware root partition, and chrooting into it to edit something that is scrozzled up by your lack of foresight, or a lost password, etc.

Finally I generally keep a second linux on the machine that I can start if the main one is down for some reason. That might be a second copy of Slackware (my recommendation actually) but any linux might work for you and I have used Ubuntu or Kali, etc. You can then edit your root (/) and /boot as a mounted drive to fix what went wrong or rescue valuable stuff preparatory to a total reformat. It is also interesting to see what the other Linuxes are doing and most of the time it makes me really really appreciate Slackware after I have played around with a different linux. Ubuntu will install grub, which grub is an experience in itself and can sometime help you find a lost OS but grub is nowhere near as effective as refind in my opinion, and grub has its peculiarities to learn.

Last edited by Regnad Kcin; 03-29-2020 at 03:06 AM. Reason: didnt like what i typed
 
Old 03-29-2020, 06:39 AM   #23
sxy
LQ Newbie
 
Registered: Aug 2019
Distribution: Slackware
Posts: 5

Rep: Reputation: Disabled
@jwc1936

I've made some observations about booting Windows 10. I hope my post will help you.

1) If Windows installer boots in UEFI mode, then it only supports GPT disks, similarly if boots in Legacy mode, only MBR disks can be used. Likely your Windows was installed in Legacy mode since you don't have an ESP (EFI System Partition).

2) Information about booting Windows, no matter which mode being used (UEFI/Legacy), is stored in a file called "BCD" (Boot Configuration Data). Without this BCD file, Windows cannot boot. The BCD file is in ESP/EFI/Microsoft/Boot/ if Windows is installed in UEFI mode. I'm not sure about the case of Legacy mode, however it can be easily located using the find command.

What I've tested is changing the original ESP used by both Windows and slackware to another partition. I just created a new FAT-formatted partition with boot and esp flags enabled (I also disabled those flags on the original ESP), copied relevant files into it, performed a grub-install, and then re-generated a /boot/grub/grub.cfg file (if you're using slackware-current, the os-prober should detect out Windows without problems).

Structure of my new ESP:
(yes Windows has some other efi binaries but the bootmgfw.efi alone is enough to make it boot)
Code:
/boot/efi
└── EFI
    ├── Microsoft
    │   └── Boot
    │       ├── BCD
    │       └── bootmgfw.efi
    └── slackware-14.2+
        └── grubx64.efi

4 directories, 3 files
and my new disk layout:
(/dev/sdb2 is the original ESP, and /dev/sda3 is the new one)
Code:
Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name       Flags
 1      1049kB  629MB  628MB               SLACKBOOT
 2      629MB   200GB  199GB               SLACKLUKS
 3      200GB   200GB  231MB  fat16        EFI_TEMP   boot, esp


Model: ATA TS240GMTS420S (scsi)
Disk /dev/sdb: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  556MB  555MB   ntfs         Basic data partition          hidden, diag
 2      556MB   660MB  104MB   fat32        EFI system partition
 3      660MB   676MB  16.8MB               Microsoft reserved partition  msftres
 4      676MB   240GB  239GB   ntfs         Basic data partition          msftdata
After changing the ESP, Windows booted perfectly through the grub menu, recognized it's new ESP, and marked the original ESP as drive D: (see attachment).

So now I suggest you to try the steps I've described above because I can expect that your BCD file contains information for both UEFI and Legacy boot mode, since the BCD file can be built that way and it indeed has been built that way through a UEFI installation. If succeed, you'll have a dual-UEFI-bootable Windows with slackware. (But if your BCD contains only information about Legacy mode, then my steps simply won't work.)

ref:
BCDBoot Command-Line Options
BIOS/MBR-based hard drive partitions
UEFI/GPT-based hard drive partitions

=================================================

@captain_sensible

In fact slackware does support secure boot provided that you have installed your own secure boot keys on your machine and signed your efi binaries with them! Very good resources are Sakaki's guide of Gentoo installation and Roderick's article about secure boot. The efitools and sbsigntools packages mentioned there can be easily built, or you can just use the pre-compiled binaries from other distros (these two packages on SBo are too much outdated).


regards,
sxy
Attached Thumbnails
Click image for larger version

Name:	Windows_Disk_Management.jpg
Views:	6
Size:	210.0 KB
ID:	32883  
 
1 members found this post helpful.
Old 03-29-2020, 08:59 PM   #24
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 4,001

Rep: Reputation: 689Reputation: 689Reputation: 689Reputation: 689Reputation: 689Reputation: 689
I've been playing around with your situation in a vm. Tried sxy suggestion that didn't work.

With a windows 10 iso you could do a repair of the the mbr of the windows drive, then use the bios boot to switch between slackware uefi and windows mbr.


or follow this guide to change windows to efi, https://www.windowscentral.com/how-c...efi-windows-10 you can use the windows iso to do this. Then for duel boot with slackware use slackware grub as the primary boot loader and chainload windows.

Convert slackware to mbr boot, then use easybsd in windows to boot slackware or change boot order in bios to use slackware bootloader to chainload windows.
 
1 members found this post helpful.
Old 03-29-2020, 09:07 PM   #25
jwc1936
LQ Newbie
 
Registered: Jul 2014
Posts: 16

Original Poster
Rep: Reputation: Disabled
I'm a little tied up right now but I downloaded a free windows10 a while back and it's in my office somewhere. If I can't recover from what I have done I will try to install windows10 as you suggest.
Best, jwc
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Ooooy. EFI boot mmx64.efi.efi not found bulgin Linux - Newbie 12 12-20-2018 11:03 AM
how to boot Slackware on the second disk if on the first is windows10 a4z Slackware 23 10-17-2017 11:25 AM
[SOLVED] Can't find /boot/efi/EFI/Slackware/vmlinuz kernel configuration ironQiu Slackware 4 02-09-2015 06:21 AM
EFI main GPT overwritten everytime (when windows 7 runs) - structure of EFI masuch Linux - Newbie 2 07-20-2012 02:49 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:39 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration