>> echo "PKGNAME hold" | sudo dpkg --set-selections
> is that the same as apt-mark hold PKGNAME
Reminds me that I wish we could add a comment describing why it's on
hold (or alternatively, provide a config file where we can write which
package should be held, using a format that allows comments).
Thanks
On Thu, 29 May 2025, Felix Miata wrote:
Date: Thu, 29 May 2025 14:41:08 -0400
From: Felix Miata
To: debian-user@lists.debian.org
Subject: Re: Disable upgrades on grub
Resent-Date: Thu, 29 May 2025 18:41:29 + (UTC)
Resent-From: debian-user@lists.debian.org
Greg Wooledge composed on
On Thu, May 29, 2025 at 18:38:31 +, fxkl4...@protonmail.com wrote:
> On Thu, 29 May 2025, Greg Wooledge wrote:
>
> > On Thu, May 29, 2025 at 17:54:00 +, xuser wrote:
> >> How to configure apt to not install upgrades for grub?
> >
> > echo "PKGN
Greg Wooledge composed on 2025-05-29 14:27 (UTC-0400):
> On Thu, May 29, 2025 at 17:54:00 +, xuser wrote:
>> How to configure apt to not install upgrades for grub?
> echo "PKGNAME hold" | sudo dpkg --set-selections
> Do that for each package you want to put on hold
On Thu, 29 May 2025, Greg Wooledge wrote:
> On Thu, May 29, 2025 at 17:54:00 +, xuser wrote:
>> How to configure apt to not install upgrades for grub?
>
> echo "PKGNAME hold" | sudo dpkg --set-selections
>
> Do that for each package you want to put on hold.
On Thu, May 29, 2025 at 17:54:00 +, xuser wrote:
> How to configure apt to not install upgrades for grub?
echo "PKGNAME hold" | sudo dpkg --set-selections
Do that for each package you want to put on hold.
How to configure apt to not install upgrades for grub?
xu...@sdf.org
SDF Public Access UNIX System - http://sdf.org
Hi,
i wrote:
> > Would it be ok to install "grub-pc-bin" and "grub-efi-ia32-bin" ?
Steve McIntyre wrote:
> Yes. That's exactly the design of the packaging here: the -bin
> packages contain the binary grub code that you're looking for, and
> grub-pc a
Thomas wrote:
>
>i am trying to reproduce a problem of grub-mkrescue. For that i need
>the directories
> /usr/lib/grub/i386-pc
> /usr/lib/grub/i386-efi
>alongside the already installed
> /usr/lib/grub/x86_64-efi
>in order to get an ISO for legacy BIOS and EFI to
Hi,
Dan Ritter wrote:
> Would downloading the deb packages, then un-ar'ing them in a tmp dir
> get you most of what you want?
Maybe. But i was looking for a way to create BIOS+EFI grub-mkrescue
ISOs by regular Debian means.
To answer my own question:
https://tracker.debian.org/med
Thomas Schmitt wrote:
> Hi,
>
> i am trying to reproduce a problem of grub-mkrescue. For that i need
> the directories
> /usr/lib/grub/i386-pc
> /usr/lib/grub/i386-efi
> alongside the already installed
> /usr/lib/grub/x86_64-efi
> in order to get an ISO for l
Hi,
i am trying to reproduce a problem of grub-mkrescue. For that i need
the directories
/usr/lib/grub/i386-pc
/usr/lib/grub/i386-efi
alongside the already installed
/usr/lib/grub/x86_64-efi
in order to get an ISO for legacy BIOS and EFI together.
Gentoo and Arch obviously can have this
On Tue, May 20, 2025 at 05:53:31AM +, Kean Hai2 Ren | 任 海 wrote:
> Hi Tomas,
>
> Thanks for your updates.
Hi, Kean (is this the correct way to address you?)
Thanks for your detailed description. Myself, I am not a grub
expert, but with that description I'm sure someone around
On Mon, May 19, 2025 at 05:49:34AM +, Kean Hai2 Ren | 任 海 wrote:
> renh...@lenovo.com would like to recall the message, "Grub struct the OS
> reboot".
Hi,
I read your first message, and couldn't make much sense of
it. Quite possibly, others are in the same situation a
renh...@lenovo.com would like to recall the message, "Grub struct the OS
reboot".
d then it is stuck without seeing the grub info, and the
> mouse and keyboard no response.
>
> What did I do?
> I removed the SSD from the machine and put it on another device for use. The
> other devices could boot up normally, so I executed "sudo apt-get install
> g
Package: grub
Version: 2.06
When I installed Debian 12.10 on my device :
CPU: 13th GenIntel Core i5-13500x20
Graphic:Mesa intel UHD Graphics 770(ADL-S GT1)
Memery: 16G
During the installation, it works well, but after finishing the installation,
it will reboot, and then it is stuck without
nd).
Yes, the harddisk is prepared and now you can
start the installation almost from scratch.
> Question: It would be better if I would have made /boot too?
This is a question of personal preference. I like to have a separated
partition or softraid device for /boot even while not required b
Thanks!
Debian 12 only.
So... mdadm!
CPA
Da: Dan Ritter
Inviato: Giovedì, 24 Aprile, 2025 16:29
A: Pier Antonio Corradini
Cc: Debian Users
Oggetto: Re: R: R: R: Grub problem
Pier Antonio Corradini wrote:
> You are right!
> LSI Software RAID Configu
apt update
apt install --reinstall grub-pc
exit
umount /target/sys /target/proc /target/dev
umount /target
Anything wrong?
Thanks.
CPA
Da: Frank Guthausen
Inviato: Giovedì, 24 Aprile, 2025 18:36
A: debian-user@lists.debian.org
Oggetto: Re: R: R: R: Grub problem
elped me
manage the configuration of LSI for Linux.
The AI recommended me a very long manual configuration procedure in which
Grub was installed after I had installed /boot on each of the two hard drives
and had partitioned each disk identically. However, when I restarted the
computer I ha
use of dmraid?
If you don't need the hardware RAID (e.g. for dual boot Windows) you
might try deactivate it and use Debian softraid with mdadm only. This
should work in any case, because once the Linux kernel is started it
takes control and does usually a very good job.
You should install grub
Pier Antonio Corradini wrote:
> You are right!
> LSI Software RAID Configuration Uitility Ver A.63, 2010; BIOS Versione
> A.09.04151432R.
> Chipset Intel 3200 + ICH9R (
> https://www.fujitsu.com/cl/Images/ds-py-tx100-s1.pdf: Intel 3200 server
> chipset, ECC memory and RAID 0/1).
> This RAID is
to: Giovedì, 24 Aprile, 2025 14:14
A: Pier Antonio Corradini
Cc: Titus Newswanger; debian-user@lists.debian.org
Oggetto: Re: R: R: Grub problem
Pier Antonio Corradini wrote:
> You can find everything about the LSI system I described at this link:
> https://www.fujitsu.com/global/imagesgig5/b7
manage the configuration of LSI for Linux.
>
> The AI recommended me a very long manual configuration procedure in which
> Grub was installed after I had installed /boot on each of the two hard drives
> and had partitioned each disk identically.
> I don't understand if I&
Debian 12 to do the partitioning does not create
/boot and therefore the Grub installation fails. If you create /boot
(and all the other partitions) manually, Grub is installed but the
operating system does not load and when you turn it back on, the RAID
no longer exists in the loading console
create /boot and
therefore the Grub installation fails. If you create /boot (and all the other
partitions) manually, Grub is installed but the operating system does not load
and when you turn it back on, the RAID no longer exists in the loading console.
Moreover, if you create, in the
n that
case, I think GRUB mostly installs to the /efi filesystem, and
possibly also /boot filesystem (or / if there's no /boot filesystem),
similar to the above. As for /efi, that can't be under md raid1,
however one can have it on two drives and install it to both for
redundancy.
If the
(i.e.
with RAID 0). Then, one day, after compiling the source code the OS went to
crash and any attempt to install it always gave problems. Even a careful manual
partitioning allowed the installation of Grub but not the loading of the
operating system.
PA
_
Hello everyone,
Debian 12 does not install GRUB on a RAID 1 array of my computer: I don't know
if this problem is caused by a hardware failure or by my inexperience so I ask
if there is a reference guide for this case. Thanks.
C.P.A.
Thank Wright!
with more than 20 years of experience in installing and using debian, do
i have to read installation guide?
it is said that installing debian is as easy as pressing Enter
it is dumb to report fatal error after all configuration and copying
after 30 years of development, install
On Wed, Mar 26, 2025 at 07:48:16AM -0500, Richard Owlett wrote:
> On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > [SNIP]
> >
> > I normally use "sudo -s", which is the closest sudo approximation to
> > the traditional behvior of "su" (before it was broken in buster).
> >
>
> I don't understand the
On Tue, Apr 01, 2025 at 04:09:31AM +0800, hlyg wrote:
>
> On 3/31/25 10:50, David Wright wrote:
> > Presumably that error message was from the screen. Have you looked
> > at /var/log/installer/syslog for more expansive error messages?
> >
> > Cheers,
> > David.
> >
> Thank Wright! i have solved
Greg (HE12025-03-27):
> I'm certain sudo has its use cases, but all I do personally is su to
> root and update and upgrade my stable Bookworm using apt, so I feel no
> need to complexify the issue with sudo.
The fallacy in here being assuming, without stating it and without
justifying it that sudo
>
> "sudo -i" is meant to approximate the behavior of "su -". Before buster,
> nobody would have used that on a Debian system. It's horrible. The
> fact that people are now embracing it as a norm is even worse.
>
Why horrible?
On Sun 30 Mar 2025 at 11:50:52 (+0800), hlyg wrote:
> i install with debian-12.10.0-amd64-netinst.iso
>
> during final stage of installation, it fails to install grub
>
> "Executing 'grub-install dummy' failed."
> "This is a fatal error."
>
&g
David Wright writes:
> host!auser 09:57:47 /somewhere/that/is/obnoxiously/long/program-1.2.3$
> /bin/su --login
> Password:
> bullseye on /dev/sda5 toto05
> host 09:57:59 ~# cd /somewhere/that/is/obnoxiously/long/program-1.2.3
> host 09:58:08 /somewhere/that/is/obnoxiously/long/progra
On 4/1/25 05:20, Andrew M.A. Cater wrote:
Make it simple for yourself. If you are at all unsure when you install,
just take guided partitioning.
That should set up a 512M partition for boot, a 1G partition for swap
and the rest of the disk for /
Unless you *really have* to partition things you
On Wed, Mar 26, 2025 at 02:55:11PM -, Greg wrote:
> On 2025-03-26, Richard Owlett wrote:
>
> >> If he hasn't noticed yet, I doubt it.
> >
> > I agree.
> > If I understand what people want to accomplish by using command-line
> > options, I would likely have gone to System->Log Out ... and the
On 21/03/2025 20:38, J wrote:
But i must mention that *this passage from Debian Wiki seems incorrect*
Bind mount various virtual filesystems:
# for i in /dev /dev/pts /proc /sys /sys/firmware/efi/efivars /run;
do mount -B $i /mnt/$i; done
https://wiki.debian.org/GrubEFIReinstall#
On 20/03/2025 03:22, J wrote:
But before this oopsie deletion I have saved as a back-up at least
something from /boot folder, or maybe even everything.
Copy files from backup to /boot and to the EFI system partition
EFI/debian/BOOTX64.CSV
EFI/debian/fbx64.efi
EFI/debian/grub.cfg
EFI/debian/g
Thank Nikulin! i read wiki page you mention, it is too technical, as end
user, i am not expected to worry such details
it seems to me that efi isn't very mature
at present it doesn't offer any benefits to me though it is superior to mbr
ne of my PCs doesn't support gpt
I'm surprised. I BIOS-boot my 20-yr old laptop into linux running on a
GPT disk, and I scrapped a similar but older desktop too. Grub is
installed in the protective MBR of the GPT disk, so the BIOS boots
the MBR in the same way as if the disk was MBR-p
On 01/04/2025 03:09, hlyg wrote:
in the end i use mbr, as one of my PCs doesn't support gpt
It depends on firmware, but I expect that UEFI spec describes
requirements for ESP in the case of MBR partitions.
btw what is recommended size of efi partition?
default size is 512M
sgdisk(8)
On 3/31/25 10:50, David Wright wrote:
Presumably that error message was from the screen. Have you looked
at /var/log/installer/syslog for more expansive error messages?
Cheers,
David.
Thank Wright! i have solved it on my own
i am new user of gpt, fatal error is caused by my failure to creat
i install with debian-12.10.0-amd64-netinst.iso
during final stage of installation, it fails to install grub
"Executing 'grub-install dummy' failed."
"This is a fatal error."
how to solve it?
i bet it is caused by other bootloader in installation target disk
Greg Wooledge wrote:
...
> Maybe. If you haven't created an /etc/default/su file, then something
> like this:
>
> $ su
> # adduser richard
>
> may fail. You could work around it in various ways (e.g. explicitly
> typing out /usr/sbin/adduser richard).
>
> My recommendation is to create a
Max Nikulin (HE12025-03-28):
> Approximately a decade ago I
> noticed that new entries were not added to some history file, I do not
> remember if it was .bash_history or for some other tool, but the owner of
> the file was root. It was the reason why I
On 26/03/2025 18:55, Greg Wooledge wrote:
"sudo -i" is meant to approximate the behavior of "su -". Before buster,
nobody would have used that on a Debian system. It's horrible. The
fact that people are now embracing it as a norm is even worse.
It seems I have to clarify why I suggested name
number of minor problems.
Though I also found out that *Timeshift* keeps not only /root but also
/boot folder (even if it is physically on the other disk)! Thanks Universe
So I just copied files from the timeshift /boot backup to the new *ESP*
folder and *GRUB *showed the OS correctly.
There were also
On 2025-03-28, David Wright wrote:
>
> As end-users are the people that computers are built and run
> for, I don't know why you'd find people's use of the term
> "slightly pejorative". (I assume you aren't calling out me
> in particular.)
I was calling myself out, not you. You have always been he
On Wed, Mar 26, 2025 at 15:46:15 +0100, Nicolas George wrote:
> $ su
> # make install
>
> Whoopsie! The Makefile just pwned you.
That's a COMPLETELY separate discussion. Obviously I was referring to
software from reputable sources.
> $ make DESTDIR=/tmp/i install
> $ sud
On Thu 27 Mar 2025 at 22:14:03 (-0400), Michael Stone wrote:
> On Thu, Mar 27, 2025 at 08:29:50PM -0500, David Wright wrote:
> > Excellent, that solves the problem for those on old terminals or
> > lacking copy/paste. As for me, I'll continue to use /bin/su --login,
> > as I have for nigh on three
On Thu, Mar 27, 2025 at 08:29:50PM -0500, David Wright wrote:
Excellent, that solves the problem for those on old terminals or
lacking copy/paste. As for me, I'll continue to use /bin/su --login,
as I have for nigh on three decades, so that I land in my preferred,
consistent cwd, /root.
su -
do
On Thu 27 Mar 2025 at 17:05:56 (-), Greg wrote:
> On 2025-03-26, David Wright wrote:
> >
> > As posted earlier today, a file in sudoers.d/ makes trivial admin
> > tasks like monitoring and logging easier, particularly where the
> > programs concerned can cause damage if the wrong options are us
On Thu 27 Mar 2025 at 13:58:10 (-0400), Greg Wooledge wrote:
> On Thu, Mar 27, 2025 at 12:48:35 -0500, David Wright wrote:
> > It could be argued that it would be simple enough to communicate
> > the user's cwd to root, as a workaround, so that it didn't have to
> > be retyped.
>
> You know what d
On 2025-03-26, David Wright wrote:
>
> As posted earlier today, a file in sudoers.d/ makes trivial admin
> tasks like monitoring and logging easier, particularly where the
> programs concerned can cause damage if the wrong options are used.
I'm certain sudo has its use cases, but all I do persona
On Thu, Mar 27, 2025 at 12:48:35 -0500, David Wright wrote:
> It could be argued that it would be simple enough to communicate
> the user's cwd to root, as a workaround, so that it didn't have to
> be retyped.
You know what does that for you? sudo -s. Or su if you've configured
it with a one-lin
On Thu 27 Mar 2025 at 12:23:26 (+0200), Anssi Saari wrote:
> David Wright writes:
>
> > host!auser 09:57:47 /somewhere/that/is/obnoxiously/long/program-1.2.3$
> > /bin/su --login
> > Password:
> > bullseye on /dev/sda5 toto05
> > host 09:57:59 ~# cd /somewhere/that/is/obnoxiously/long/p
Anssi Saari wrote:
> David Wright writes:
>
> > host!auser 09:57:47 /somewhere/that/is/obnoxiously/long/program-1.2.3$
> > /bin/su --login
> > Password:
> > bullseye on /dev/sda5 toto05
> > host 09:57:59 ~# cd /somewhere/that/is/obnoxiously/long/program-1.2.3
> > host 09:58:08 /somew
On 3/26/25 6:55 AM, Greg Wooledge wrote:
[SNIP]
I normally use "sudo -s", which is the closest sudo approximation to
the traditional behvior of "su" (before it was broken in buster).
I don't understand the reference to some "brokenness" of "su".
I've not closely followed this thread so I may
On Wed 26 Mar 2025 at 16:37:41 (-), Greg wrote:
> On 2025-03-26, Richard Owlett wrote:
> >
> > I assumed it was effectively the same as power down and then logging in
> > as root on power-up.
>
> It is. But it's unnecessary and dangerous to run your entire DE as root.
> Or maybe you log in t
Greg Wooledge (HE12025-03-26):
> This caused ALL KINDS of problems. People would do things like:
>
> $ su
> # apt update
> # apt install somepkg
>
> And the postinstall script for somepkg would fail because it couldn't
> find commands that are in /sbin or /usr/sbin, because those dir
So, in most cases* sudo -s* is better? Any downsides?
ср, 26 мар. 2025 г. в 16:10, Greg Wooledge :
> On Wed, Mar 26, 2025 at 07:48:16 -0500, Richard Owlett wrote:
> > On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > > I normally use "sudo -s", which is the closest sudo approximation to
> > > the trad
On Wed, Mar 26, 2025 at 07:55:33AM -0400, Greg Wooledge wrote:
[...]
> I normally use "sudo -s", which is the closest sudo approximation to
> the traditional behvior of "su" (before it was broken in buster).
>
> "sudo -i" is meant to approximate the behavior of "su -". Before buster,
> nobody w
On 2025-03-26, Richard Owlett wrote:
>
> I assumed it was effectively the same as power down and then logging in
> as root on power-up.
It is. But it's unnecessary and dangerous to run your entire DE as root.
Or maybe you log in to the console and use startx to run Mate?
At any rate, I do follo
On 2025-03-26, Greg Wooledge wrote:
>>
>> Does this "brokenness" of "su" have any potential effect on my usage?
>
> Maybe. If you haven't created an /etc/default/su file, then something
> like this:
If he hasn't noticed yet, I doubt it.
I noticed when I finally erased Stretch and installed Boo
On 2025-03-26, Richard Owlett wrote:
>> If he hasn't noticed yet, I doubt it.
>
> I agree.
> If I understand what people want to accomplish by using command-line
> options, I would likely have gone to System->Log Out ... and then logged
> in as root.
Not recommended.
On Wed 26 Mar 2025 at 10:03:59 (-0500), Richard Owlett wrote:
> On 3/26/25 9:55 AM, Greg wrote:
> > On 2025-03-26, Richard Owlett wrote:
> >
> > > > If he hasn't noticed yet, I doubt it.
> > >
> > > I agree.
> > > If I understand what people want to accomplish by using command-line
> > > options
On Wed 26 Mar 2025 at 16:24:21 (+0300), J wrote:
> ср, 26 мар. 2025 г. в 16:10, Greg Wooledge :
> > On Wed, Mar 26, 2025 at 07:48:16 -0500, Richard Owlett wrote:
> > > On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > > > I normally use "sudo -s", which is the closest sudo approximation to
> > > > the t
On 3/26/25 9:55 AM, Greg wrote:
On 2025-03-26, Richard Owlett wrote:
If he hasn't noticed yet, I doubt it.
I agree.
If I understand what people want to accomplish by using command-line
options, I would likely have gone to System->Log Out ... and then logged
in as root.
Not recommended.
On 3/26/25 9:04 AM, Greg wrote:
On 2025-03-26, Greg Wooledge wrote:
Does this "brokenness" of "su" have any potential effect on my usage?
Maybe. If you haven't created an /etc/default/su file, then something
like this:
If he hasn't noticed yet, I doubt it.
I agree.
If I understand what
On Wed, Mar 26, 2025 at 04:19:37PM +0300, J wrote:
> >
> > > work with* root?* I will try to test.
> >
> > I fully expect it to, yes.
> >
>
> Oh, yes, it works. I just had to use *sudo su* and not not
I think you never need "sudo su". "sudo -i" and "sudo -s" will do your
bidding, depending on you
>
> > work with* root?* I will try to test.
>
> I fully expect it to, yes.
>
Oh, yes, it works. I just had to use *sudo su* and not not
*su - *
Also it's bad that Wiki doesn't clarify* how to* 'boot the rescue system
including the kernel option "efi=runtime" and mount the EFI variables
before pro
On Wed, Mar 26, 2025 at 07:48:16 -0500, Richard Owlett wrote:
> On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > I normally use "sudo -s", which is the closest sudo approximation to
> > the traditional behvior of "su" (before it was broken in buster).
>
> I don't understand the reference to some "brok
On Wed, Mar 26, 2025 at 12:23:38 +0100, to...@tuxteam.de wrote:
> On Wed, Mar 26, 2025 at 02:15:03PM +0300, J wrote:
> > And i thought *sudo -i*, you speaking about, is something like
> > *--interactive*, which is not, how i see now...
>
> The long form is "--login", not interactive. But the "-i"
On Wed, Mar 26, 2025 at 02:15:03PM +0300, J wrote:
> > In my opinion, "sudo -i" might be added to the wiki articles. I would
> > prefer to see a warning concerning compound shell commands in *sudo* docs.
> >
> > J, my impressions is that you read some docs strongly suggesting to
> > prefix every co
> In my opinion, "sudo -i" might be added to the wiki articles. I would
> prefer to see a warning concerning compound shell commands in *sudo* docs.
>
> J, my impressions is that you read some docs strongly suggesting to
> prefix every command instead of just becoming root.
Actually it is easier
There were also some minor problems which I solved with *apt update/upgrade*
> while being in *chroot*.
>
In particular, there was for some reason no internet connection after I
booted to the restored system. Something wrong was with firmware and/or
initramfs i guess.
On 25/03/2025 19:47, J wrote:
Notice that the page suggests "# for i in /dev /dev/pts /proc "
so it is assumed that users should run
$ sudo -i
sudo *SH -c '...' -* as mentioned above. But it is not written in WIki.
In my opinion, "sudo -i" might be added to the wiki articles. I wo
On Wed, Mar 26, 2025 at 09:25:01AM +0700, Max Nikulin wrote:
> On 25/03/2025 19:47, J wrote:
> > Notice that the page suggests "# for i in /dev /dev/pts /proc "
> > so it is assumed that users should run
> >
> > $ sudo -i
> >
> > sudo *SH -c '...' -* as mentioned above. But it is not
>
> Notice that the page suggests "# for i in /dev /dev/pts /proc "
> so it is assumed that users should run
>
> $ sudo -i
>
sudo *SH -c '...' - *as mentioned above. But it is not written in WIki.
I am thinking about if i should propose the Wiki update.
> The error suggests that you forgot to m
debian.org/GrubEFIReinstall#Using_the_rEFInd_rescue_media
In the context of bind-mounts the link is confusing. In some cases
rEFInd should be able to boot *installed* Linux in the case of troubles
system firmware, e.g. missed boot entry. No chroot is required for grub
reinstall. However you wrot
> sudo sh -c '...'
>
Didn't know such a thing. Wasn't mention in the wiki.
Have you considered doing something crazy like creating the mount points?
>
Can't say so. I have fixed my problem a few days ago (see above about
mounting), now i am discussing with Max if Wiki is correct.
https://wiki.d
I have rechecked.
It doesn't work with sudo also.
Not in a one line, not when i tried to make line breaks with \, not in a
bash script.
user@debian:~$ sudo for i in /dev /dev/pts /proc /sys
/sys/firmware/efi/efivars /run; do mount -B $i /mnt/$i; done
bash: syntax error near unexpected token `do'
first installation.
But before this oopsie deletion I have saved as a back-up at least
something from /boot folder, or maybe even everything. There is a Microsoft
folder, /grub folder with bootx64.efi and bootx64.efi.grb (though EMPTY!)
and /Debian folder with shimx64.efi etc…
I have tried to fix the
do a full powercycle.
I just happened to have a cheap USB3 that fails on attempt to boot when
it is plugged into the USB2 port of my old laptop.
A variation is: not the same hub as keyboard and mouse.
grub> echo $cmdpath
(hd2,gpt1)/EFI/debian
grub> echo $fw_path
### no
g the stick into another USB port (e.g. USB2 instead of
USB3 or vice versa)? Try full power cycle, not just reboot.
All the 10 USB ports on my T5820 are specified as USB 3.1 Gen 1. I always do a
full powercycle.
To figure out what happens in your case you may try the following commands:
gru
On Tue, Dec 17, 2024 at 03:32:03PM +0100, Thomas Schmitt wrote:
Roger Price wrote:
To check for bad USB stick, I downloaded debian-12.8.0-amd64-DVD-1.iso and
built a new 12.8 USB installation stick using command
dd if=debian-12.8.0-and64-DVD-1.iso of=/dev/sdj1 bs=4M && sync
The "1" in "/dev/s
small to take a DVD ISO.
Is this the same USB stick as the one with Debian 12.7.0 netinst ?
If so, did you run a partition editor to create a new partition 1 ?
> I tried booting this and got to a GRUB command line. This time ls -l
> reports that (hd0) has "no known filesystem detected&q
On 16/12/2024 15:45, Roger Price wrote:
So I re-inserted the USB installation stick to redo the installation.
This took me to the GRUB command line.
Am I right that you have internal SSD (SATA? NVME?) and a USB stick?
Have you tried to plug the stick into another USB port (e.g. USB2
instead
On Tue, 17 Dec 2024, Thomas Schmitt wrote:
Roger Price wrote:
I got the message error: file '/install.amd/vmlinux' not found
So perhaps:
grub> set root=(hd0)
grub> linux/install.amd/vmlinuz vga=788 --- quiet
grub> initrd /install.amd/gtk/initrd.gz
grub> boot
Hi,
i proposed for booting from the now reluctant USB stick:
> > grub> linux/install.amd/vmlinuz vga=788 --- quiet
> > grub> initrd /install.amd/gtk/initrd.gz
> > grub> boot
Roger Price wrote:
> I got the message error: file '/install.amd/vmlinux'
On Mon, 16 Dec 2024, Thomas Schmitt wrote:
Does the USB stick yield the proper checksum when inspected on a running
GNU/Linux system ?
Will check.
grub> cat (hd0,msdos2)/efi/debian/grub.cfg
set prefix-($root)/boot/grub
I see "=" instead of "-" in this file when t
On Mon, 16 Dec 2024 09:45:59 +0100 (CET)
Roger Price wrote:
> But I did create a
> small FAT32 partition to be mounted on /boot/efi if one day I needed
> it.
Which option in the installer's partitioner did you use, one of the FAT
options, or the EFI one? The latter will create a partition with
On Mon, 16 Dec 2024 18:50:02 +
Joe wrote:
> So I gave up, and just installed bookworm clean. No bootable OS found.
> I'll cut it short: it wouldn't boot because a /boot/efi/EFI directory
> did not contain a Microsoft directory containing bootmgfw.efi.
> Previously, it had been happy to boot f
On 12/16/24 10:50, Joe wrote:
I would add that many modern computers are almost hardwired for
Windows. ...
So I gave up, and just installed bookworm clean. No bootable OS found.
I'll cut it short: it wouldn't boot because a /boot/efi/EFI directory
did not contain a Microsoft directory containing
On Mon, 16 Dec 2024 09:39:22 -0800
David Christensen wrote:
> On 12/16/24 00:45, Roger Price wrote:
> > I have a Dell T5820 workstation. I had already installed Debian 12
> > in a spare partition on a Transcend SSD dating from 2017 using a
> > USB memory stick. I left in place the existing Wind
On 12/16/24 00:45, Roger Price wrote:
I have a Dell T5820 workstation. I had already installed Debian 12 in a
spare partition on a Transcend SSD dating from 2017 using a USB memory
stick. I left in place the existing Windows SSD that came with the
workstation. All went well - a very smooth i
l test command does not
yield "IT MATCHES", then some change has happened to the ISO on the USB
stick. (You may check file debian-12.7.0-amd64-netinst.iso the same way
as /dev/sdc to check whether already the ISO image was altered.)
> grub> cat (hd0,msdos2)/efi/debian/grub.cfg
1 - 100 of 1661 matches
Mail list logo
