Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 40 |
Nodes: | 6 (0 / 6) |
Uptime: | 07:41:15 |
Calls: | 291 |
Files: | 910 |
Messages: | 76,393 |
Hi,
I plan to switch completely from Windows 11 to Debian on my laptop,
but as a first step I'd like to configure double-boot setup to give
it a try, look around and check if all hardware works fine under
Debian.
Current state:
Dell laptop (one NVMe disk only) with Windows 11 onboard.
Windows starts in UEFI mode (Secure Boot ON).
Already resized main partition to make space for Debian.
So currently there are the following partitions on disk:
100MB, FAT32, GPT (EFI System Partition)
16MB, Other, GPT (Reserved Partition)
300GB, NTFS, GPT (Data Partition) (Main C: disk visible under Win11)
168GB, free space, ready to have ~150GB for Debian and 16GB for swap
880MB, NTFS, GPT (Recovery Partition)
First try:
UEFI Boot (Secure Boot ON), Debian Trixie,
Expert mode installation During installation Debian does NOT see my
disk at all (pendrive with Debian Trixie is visible only)
Also during installation Debian says that "it seems there is another
system installed in Legacy Mode, am I sure to force UEFI mode?"
which is not correct - Win11 is installed in UEFI mode (when I try to
boot it in Legacy Mode I get Windows Blue Screen Of Death)
Second try:
Secure Boot set to OFF.
Nothing changed during Trixie installation, so no device to install
on.
Third try:
Boot in Legacy Mode (so Secure Boot is OFF).
Debian Trixie can see my laptop disk properly, so installation is successful, but...
It cannot see my Windows 11 installation when trying to install/configure/prepare GRUB.
At this step I decided to NOT install GRUB on my main disk to NOT
loose access to my Windows 11 system.
(but Trixie says that it's possible to restore access by manual configuration of GRUB later on - I'm not sure...)
Main goal:
To have both current Windows 11 and new Debian Trixie available in
GRUB and properly bootable.
How to achieve this? :-)
Hi,
I plan to switch completely from Windows 11 to Debian on my laptop,
but
as a first step I'd like to configure double-boot setup to give it a
try, look around and check if all hardware works fine under Debian.
Current state:
Dell laptop (one NVMe disk only) with Windows 11 onboard.
Windows starts in UEFI mode (Secure Boot ON).
Already resized main partition to make space for Debian.
So currently there are the following partitions on disk:
100MB, FAT32, GPT (EFI System Partition)
16MB, Other, GPT (Reserved Partition)
300GB, NTFS, GPT (Data Partition) (Main C: disk visible under Win11)
168GB, free space, ready to have ~150GB for Debian and 16GB for swap
880MB, NTFS, GPT (Recovery Partition)
First try:
UEFI Boot (Secure Boot ON), Debian Trixie, Expert mode installation
During installation Debian does NOT see my disk at all (pendrive with
Debian Trixie is visible only)
Settings-> System Configuration
Also during installation Debian says that "it seems there is another
system installed in Legacy Mode, am I sure to force UEFI mode?" which
is not correct - Win11 is installed in UEFI mode (when I try to boot it
in Legacy Mode I get Windows Blue Screen Of Death)
Second try:
Secure Boot set to OFF.
Nothing changed during Trixie installation, so no device to install on.
Third try:
Boot in Legacy Mode (so Secure Boot is OFF).
Debian Trixie can see my laptop disk properly, so installation is
successful, but...
It cannot see my Windows 11 installation when trying to install/ configure/prepare GRUB.
At this step I decided to NOT install GRUB on my main disk to NOT loose access to my Windows 11 system.
(but Trixie says that it's possible to restore access by manual
configuration of GRUB later on - I'm not sure...)
Main goal:
To have both current Windows 11 and new Debian Trixie available in GRUB
and properly bootable.
How to achieve this? :-)
Thank you,
Best Regards,
Rafal
Hi,
I plan to switch completely from Windows 11 to Debian on my laptop, but
as a first step I'd like to configure double-boot setup to give it a
try, look around and check if all hardware works fine under Debian.
Current state:
Dell laptop (one NVMe disk only) with Windows 11 onboard.
Windows starts in UEFI mode (Secure Boot ON).
Already resized main partition to make space for Debian.
So currently there are the following partitions on disk:
100MB, FAT32, GPT (EFI System Partition)
16MB, Other, GPT (Reserved Partition)
300GB, NTFS, GPT (Data Partition) (Main C: disk visible under Win11)
168GB, free space, ready to have ~150GB for Debian and 16GB for swap
880MB, NTFS, GPT (Recovery Partition)
First try:
UEFI Boot (Secure Boot ON), Debian Trixie, Expert mode installation
During installation Debian does NOT see my disk at all (pendrive with
Debian Trixie is visible only)
Also during installation Debian says that "it seems there is another
system installed in Legacy Mode, am I sure to force UEFI mode?" which
is not correct - Win11 is installed in UEFI mode (when I try to boot it
in Legacy Mode I get Windows Blue Screen Of Death)
Second try:
Secure Boot set to OFF.
Nothing changed during Trixie installation, so no device to install on.
Third try:
Boot in Legacy Mode (so Secure Boot is OFF).
Debian Trixie can see my laptop disk properly, so installation is successful, but...
It cannot see my Windows 11 installation when trying to install/configure/prepare GRUB.
At this step I decided to NOT install GRUB on my main disk to NOT loose access to my Windows 11 system.
(but Trixie says that it's possible to restore access by manual configuration of GRUB later on - I'm not sure...)
Main goal:
To have both current Windows 11 and new Debian Trixie available in GRUB
and properly bootable.
How to achieve this? :-)
Thank you,
Best Regards,
Rafal
Make? Dell, below. It is better to state this information at the top
of your message.
Model?Sorry, I should start my previous email from those details.
On my Dell machines with NVMe drives, I must change the Setup settings
for Debian to see NVMe drives:
Settings-> System Configuration
-> SATA Operation -> AHCI
It is best to take an image of the system drive before makingEven if Windows is finally lost, I accept that. No user data is lost (everything is already in the cloud), but at most some wasted time on configuration of Windows is lost ;-)
significant changes. I recommend that you do so now, before making
further changes.
It doesn't need to. Switch to UEFI mode, and the ESP will
boot into Windows.
Is there any reason for trixie? Both trixie and its installer (d-i) are evolving and may not give you useful results. I suggest you use the
current Stable, Debian 12.8, bookworm.
Even if Windows is finally lost, I accept that. No user data is lost (everything is already in the cloud), but at most some wasted time on configuration of Windows is lost ;-)
4) If you want to dual boot, then I do not see issues using Debian Bookworm to do this. I would boot into Debian (i.e. Grub), from where I select either Windows or Debian. If my primary use is Windows, then I edit grub to boot to Windows first. I havenot had issues with UEFI lately, I believe Debian handles this well.
5) I use Debian Bookworm as I like stability. Testing means things will break. Trixie is currently in testing. I rarely need the latest software. I sometimes use backports.Hmmm... in case of a whole desktop system (KDE Plasma) I guess it is not
https://backports.debian.org/Instructions/
As a matter of Backports policy, packages in the stable-backports suite are taken from Debian testing; however, in rare cases such as security updates, packages are taken from unstable.
6) What GUI have you decided to use? While I use XFCE, I recommend KDE to people, particularly when moving from Windows to Linux. In fact KDE is so nice now, maybe I will start using KDE too? (I want both, and I do use both, but on different computers)
I hope my comments helps you when trying Linux/Debian.
It can be recovered, it may take a little work.
First, does the laptop have a UEFI menu available on a hotkey during
startup? You may need to do a bit of Net searching to find it. If so,
there will be a Windows entry, try it.
The UEFI firmware, what we used to call the BIOS, may have options for enabling and disabling drives and setting the start priority. See if
any fiddling with these options will help.
Windows will not boot normally now, but it may be possible to boot it
into Safe Mode with a hotkey. If so, there ought to be a way of
restoring booting.
If Windows can be started, it will have a boot fixing option, again
search for details on the Net. Once you have Windows booting reliably,
it should be possible to get grub working again. In the worst case, you
can download the (huge) Windows installation image for your version, and
use its rescue facilities to fix booting.
I'd be more specific, but I haven't needed to deal with Windows fixing
for a while. and never on 11.
On 29.12.2024 07:21, George at Clug wrote:have not had issues with UEFI lately, I believe Debian handles this well.
4) If you want to dual boot, then I do not see issues using Debian Bookworm to do this. I would boot into Debian (i.e. Grub), from where I select either Windows or Debian. If my primary use is Windows, then I edit grub to boot to Windows first. I
Arghh... dual-boot, not double-boot - sorry for a wrong email subject ;-)
Now I've got a similar config: UEFI boot with GRUB with both entries:
Trixie and Windows, but Windows cannot boot (BSOD). Do you have any
ideas how to proceed and recover Windows system?
5) I use Debian Bookworm as I like stability. Testing means things will break. Trixie is currently in testing. I rarely need the latest software. I sometimes use backports.Hmmm... in case of a whole desktop system (KDE Plasma) I guess it is not
https://backports.debian.org/Instructions/
As a matter of Backports policy, packages in the stable-backports suite are taken from Debian testing; however, in rare cases such as security updates, packages are taken from unstable.
a matter of single package (or a few of them) from backports, but rather
a lot of them with inter-dependency. That's why I think it would be
better to start with Trixie if I want to have KDE Plasma 6, right?
computers)6) What GUI have you decided to use? While I use XFCE, I recommend KDE to people, particularly when moving from Windows to Linux. In fact KDE is so nice now, maybe I will start using KDE too? (I want both, and I do use both, but on different
Exactly. KDE Plasma 6 is awesome!
I hope my comments helps you when trying Linux/Debian.
Of course! Thank you for all comments and suggestions!
Regards,
Rafal
Try switching the SATA Operation mode back to what it was before you
switched it to AHCI mode, boot into Windows and do either [1] or [2].
Then switch the SATA Operation mode back to AHCI.
[1] https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-ide-to-ahci
[2] https://superuser.com/questions/1355060/how-to-switch-from-ide-to-ahci-after-installing-windows-vista
Hope that helps.
On 29.12.2024 04:07, David Christensen wrote:
Make? ... Model?Sorry, I should start my previous email from those details.
Dell XPS 13 (the old model, 9370), Intel UHD Graphics 620
On my Dell machines with NVMe drives, I must change the Setup settings
for Debian to see NVMe drives:
Settings-> System Configuration
-> SATA Operation -> AHCI
YEEES! That was the right solution in my case! Thank you very much!
That user support mailing list (debian-user) is amazing! I did not
expect so many answers on my question.
Each answer means someone gave me some of his time and attention for
free. Thank you ALL!
I will reply to all right now.
Back to the issue - so after that change, I boot in UEFI mode and successfully installed Trixie. My NVMe disk was properly recognized and
GRUB also found my Windows boot, so... now I have GRUB with Trixie and Windows 11 entries, BUT...
When I try to boot Windows 11 - after a while (Windows spinner at the
bottom) I have Blue Screen Of Death unfortunately.
Trixie boots normally, so I'm happy to see it on my laptop - fresh and running :-)
But anyway... do you have an idea how to recover access to Windows system?
Turning Secure Boot ON/OFF nothing changes.
Still in UEFI boot mode of course.
I had to switch back in SATA settings from "AHCI" to "Raid ON" again
to restore Windows boot.