xt/graphics menu with Debian logo and all.
I really wonder what on your system can confuse GRUB, so that it does not
get to the file /boot/grub/grub.cfg of the ISO which contains the menu
items which i see with qemu.
Have a nice day :)
Thomas
Thomas Schmitt ha scritto il 17/08/22 alle 17:18
Whenever an ISO has to be investigated or tested, a tangible download URL
can be of great help ... (cough) ... :))
Of course you're right, sorry :)
This is the downloaded image:
Hi,
Massimo Maiurana wrote:
> Sorry, forgot to mention that my iso was not the netinst one, i.e. the CD
> image, but rather was the DVD image.
Whenever an ISO has to be investigated or tested, a tangible download URL
can be of great help ... (cough) ... :))
I confess that it also helps to test
Thomas Schmitt ha scritto il 17/08/22 alle 16:15:
Hi
I now tried in quemu
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-cd/firmware-testing-amd64-netinst.iso
which i downloaded ~8 hours after your post.
Sorry, forgot to mention that
/share/ovmf/OVMF.fd \
-hda firmware-testing-amd64-netinst.iso
Offering the ISO as -hda is supposed to trigger the same boot path as
a USB stick at a real machine.
This run gives me a text/graphical menu with Debian logo, mentioning of
"UEFI" and "GRUB" and som
Thomas Schmitt ha scritto il 16/08/22 alle 09:50:
Hi,
Massimo Maiurana wrote:
I've downloaded the latest iso with testing weekly build,
I understand that there are no weekly builds of Debian Live based on
Debian Testing. (I remember people asking for Debian 12 Live ISOs and
being told that
ell the exact URLs of the ISOs which you tested,
so that others can try to reproduce the problem ?
> From that command line i can boot the installer with the following commands
> [...]
> grub> linux (hd0,msdos1)/install.amd/gtk/vmlinuz root=/dev/sdb1
"root=/dev/sdb1" look
all i get is the
> grub comman line.
>
> From that command line i can boot the installer with the following commands
> but looks to me like it is a sort of bug, just don't know how to report it
> so i'm writing here:
> grub> linux (hd0,msdos1)/install.amd/gtk/vmlinuz root=/dev/s
I've downloaded the latest iso with testing weekly build, both with and
without firmwares, and wrote them on a usb stick (of course one at a
time) but at boot it doesn't start the installer. It boots but all i get
is the grub comman line.
From that command line i can boot the installer
installed
grub on /dev/sda1. At the end of the installation process I removed
the installationm media from the cdrom drive, rebooted the computer
and selected /dev/sda1. I got an error message that /dev/sda couldn't
be found. The good news is that if I hit the reset button on the
platform the old
and os-prober package installed, it could be as
simple as running update-grub in your old Bullseye. Which would create a
new grub config file with entries for the old and the new Bullseyes.
e copy of Bullseye on /dev/ssd1 and I installed
> grub on /dev/sda1. At the end of the installation process I removed
> the installationm media from the cdrom drive, rebooted the computer
> and selected /dev/sda1. I got an error message that /dev/sda couldn't
> be found. The good news is
On 25/06/2022 14:37, Stephen P. Molnar wrote:
The installer found the copy of Bullseye on /dev/ssd1 and I installed
grub on /dev/sda1.
You supposed to install GRUB in a disk, not in a partition. So,
/dev/sda, not /dev/sda1. You select /dev/sda during installation.
At the end
) blkid?
- did you look at all the grub.cfg files (in different systems)?
Anything particular?
- Are you able to use grub command line in case you would need it?
My first guess would be, that sticking to /dev/sd?? device names
confused yourself, the OS and maybe even grub. i recommend (mid-term
I have four hard drives ion my Bullseye platform; Three SSD's and one
HDD. My current copy of Bullseye is on /dev/sdd1. I have installed a
pristine copy of Bullsye on /dev/sda.
The installer found the copy of Bullseye on /dev/ssd1 and I installed
grub on /dev/sda1. At the end
>
>
>
> Von: Greg Wooledge
> Gesendet: Dienstag, 24. Mai 2022 19:16
> An: debian-user@lists.debian.org
> Betreff: Re: Firmware III grub
>
> On Tue, May 24, 2022 at 09:07:46PM +0200, Siard wrote:
> > I accomplished the same by crea
Good evening
Thank You
Is the most easy way for
update
and root managing
su
su -
sudo?
Tegards
Sophie
Von: Greg Wooledge
Gesendet: Dienstag, 24. Mai 2022 19:16
An: debian-user@lists.debian.org
Betreff: Re: Firmware III grub
On Tue, May 24, 2022 at 09:07
On Tue, May 24, 2022 at 03:16:46PM -0400, Greg Wooledge wrote:
> On Tue, May 24, 2022 at 09:07:46PM +0200, Siard wrote:
> > I accomplished the same by creating /usr/local/bin/su containing these
> > lines:
> >
> > #! /bin/sh
> > PATH=$PATH:/sbin:/usr/sbin
> > /bin/su
> >
> > and making it
On Tue, May 24, 2022 at 09:07:46PM +0200, Siard wrote:
> I accomplished the same by creating /usr/local/bin/su containing these lines:
>
> #! /bin/sh
> PATH=$PATH:/sbin:/usr/sbin
> /bin/su
>
> and making it executable.
Clever. But the final line should be:
exec /bin/su "$@"
I still prefer
Hans wrote:
> There is also "su -p", which stands for "preserve". You need this, if you
> want use graphical applications as a normal user, which need root rights
> (for example wireshark or editing config files with kwrite, with owner
> "root").
I accomplished the same by creating
There is also "su -p", which stands for "preserve". You need this, if you want
use graphical applications as a normal user, which need root rights (for
example wireshark or editing config files with kwrite, with owner "root").
I remember, there was "sux" in earlier times (dunno if it was a SuSE
t; > asked for your password, then the command is executed
> > as root. In your case:
> >
> > sudo update-grub
> > [asks for password]
> >
> > But root terminal is fine too.
>
> Isnt su- better?
"su-" doesn't exist. You have to put
Isnt su- better?
Regards
Von: to...@tuxteam.de
Gesendet: Sonntag, 01. Mai 2022 13:33
Bis: Schwibinger Michael
Cc: debian-user@lists.debian.org
Betreff: Re: Firmware III grub
On Sun, May 01, 2022 at 11:49:30AM +, Schwibinger Michael wrote:
>
>
Bonjour Cassis,
Merci pour ta réponse, la manipulation via le logiciel a marché.
Sylvain
Le 13/05/2022 à 19:00, k6dedi...@free.fr a écrit :
Bonjour,
J'ai remarqué que grub-customizer n'était pas au top des dernières versions de
GRUB.
Je ne l'utilise plus.
Il vaut mieux passer par la ligne
Bonjour,
J'ai remarqué que grub-customizer n'était pas au top des dernières versions de
GRUB.
Je ne l'utilise plus.
Il vaut mieux passer par la ligne de commande et modifier /etc/default/grub
background_image
Commande : background_image [[--mode ‘stretch’|‘normal’] file]
Charge l'image de fond
Bonjour et merci pour ta réponse.
Le 13/05/2022 à 13:10, NoSpam a écrit :
> L'utilisateur Sylvain n'est pas dans la liste des sudoers et ne peut
> faire de sudo . SOit rajouté l'utilisateur dans la liste
> soit se logguer sous root et executer les commandes.
J'ai lancé grub-customiz
Bonjour
Le 13/05/2022 à 12:28, Sylvain a écrit :
Bonjour,
J'ai utilisé grub-customizer pour mettre une image de fond à grub.
Lorsque j'ai fait ça je n'ai pas eu de problème d'authentification en
tant que root.
Mais brusquement je n'ai plus eu d'image de fond à grub et impossible
de lancer
Bonjour,
J'ai utilisé grub-customizer pour mettre une image de fond à grub.
Lorsque j'ai fait ça je n'ai pas eu de problème d'authentification en
tant que root.
Mais brusquement je n'ai plus eu d'image de fond à grub et impossible de
lancer grub-customizer, le mot de passe root est rejeté
re then
asked for your password, then the command is executed
as root. In your case:
sudo update-grub
[asks for password]
But root terminal is fine too.
Cheers
--
t
signature.asc
Description: PGP signature
:53:14AM +, Schwibinger Michael wrote:
> Good morning
> Thank You for help.
>
> Do we need this?
>
> We dont use WIFI
> we do connect the PC and the router with cable.
That depends on your hardware. Most Ethernet hardware
works without firmware.
> ***
>
> S
Jaroslav Fojtík writes:
> Syntax errors are detected in generated GRUB config file.
> Ensure that there are no errors in /etc/default/grub
> and /etc/grub.d/* files or please file a bug report with
> /boot/grub/grub.cfg.new file attached.
Interesting, it looks like os-prober g
Hi,
>Looks like your partition is full.
>Check if there are old and unneeded kernels installed. If so, uninstall
these
>and try again.
133GigaBytes free space on the partition should be sufficient enough.
>Please could you install pastebininit, maybe and put all the details into a
;
> http://78.108.103.11/~fojtik/debian11/DebianInstallFail.jpg
>
>
>
>
> Debian could be hacked to finish installation and then works.
>
>
>
>
>
> This does not look sane:
> http://78.108.103.11/~fojtik/debian11/update_grub.txt
>
gt;
>
>
>
> This does not look sane:
> http://78.108.103.11/~fojtik/debian11/update_grub.txt
> ***
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-5.15.0-3-amd64
> Found initrd image: /boot/
not look sane:
http://78.108.103.11/~fojtik/debian11/update_grub.txt
***
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.0-3-amd64
Found initrd image: /boot/initrd.img-5.15.0-3-amd64
Found linux image: /boot/vmlinuz-5.14.0-4
rtitioners, but only one set of useful names,
> those matched by * in /dev/disk/by-*. I let the Grub scripts play
> with the UUIDs, and switch over to LABELs when it's done.
>> > Grub itself, of course,
>> > supports their use, but not the scripts that generate grub.cfg.
>&g
hine set aside to test several configurations of Debian 11.
> > > >
> > > > Is there away to have the Grub Menu _automatically_ display the assigned
> > > > partition name rather than than /dev/sdaN ?
> > >
> > > I wonder whether thi
hine set aside to test several configurations of Debian 11.
> > > >
> > > > Is there away to have the Grub Menu _automatically_ display the assigned
> > > > partition name rather than than /dev/sdaN ?
> > >
> > > I wonder whether thi
hine set aside to test several configurations of Debian 11.
> > > >
> > > > Is there away to have the Grub Menu _automatically_ display the assigned
> > > > partition name rather than than /dev/sdaN ?
> > >
> > > I wonder whether thi
On 04/20/2022 05:44 PM, David Wright wrote:
On Wed 20 Apr 2022 at 20:09:54 (+), Andrew M.A. Cater wrote:
On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote:
I have a machine set aside to test several configurations of Debian 11.
Is there away to have the Grub Menu
On Wed 20 Apr 2022 at 20:09:54 (+), Andrew M.A. Cater wrote:
> On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote:
> > I have a machine set aside to test several configurations of Debian 11.
> >
> > Is there away to have the Grub Menu _automatically_
On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote:
> I have a machine set aside to test several configurations of Debian 11.
>
> Is there away to have the Grub Menu _automatically_ display the assigned
> partition name rather than than /dev/sdaN ?
>
I wonder wheth
I have a machine set aside to test several configurations of Debian 11.
Is there away to have the Grub Menu _automatically_ display the assigned
partition name rather than than /dev/sdaN ?
On Mon 14 Feb 2022 at 10:41:52 (-0500), Chuck Zmudzinski wrote:
> On 2/13/2022 11:23 AM, Andrei POPESCU wrote:
> > On Du, 13 feb 22, 02:40:27, Chuck Zmudzinski wrote:
> > > This is my understanding of how grub works.
> > >
> > > It looks you are using the old
On Mon 14 Feb 2022 at 10:54:21 (+0100), basti wrote:
> Hello,
>
> I try to use a USB Serial-Converter to output the grub menu on a
> Serial port.
>
> By the way the output is working at kernel boot time. (I See it on the
> remote host)
>
> How can I add usbserial_
Hello,
I try to use a USB Serial-Converter to output the grub menu on a Serial
port.
By the way the output is working at kernel boot time. (I See it on the
remote host)
How can I add usbserial_pl2303.mod to the GRUB core image?
The file is located in /boot/grub/i386-pc/ on the root
installé une Debian stable, comportant Grub.
Par la suite, j'ai installé d'autres distributions en parallèle et,
comme le dit Pierre, il est important de ne plus installer de Grub sur
ces distributions "secondaires" (ce n'est pas toujours évident, car
suivant le mode d'installation, c'e
)
Objet: Re: Remettre le fichier GRUB à neuf
Bonjour à tous,
j'ai plusieurs systèmes sur toutes mes machines et je n'ai pas eu
d'ennuis particuliers avec grub.
Il me semble important d'installer grub sur _un seul_ système, celui-ci
appelant les autres systèmes installés. Il suffit, lors d'une
Bonjour à tous,
j'ai plusieurs systèmes sur toutes mes machines et je n'ai pas eu
d'ennuis particuliers avec grub.
Il me semble important d'installer grub sur _un seul_ système, celui-ci
appelant les autres systèmes installés. Il suffit, lors d'une nouvelle
installation de refuser l'installation
u want to add after this comment. Be careful not to
change
# the 'exec tail' line above.
didier@hp-notebook14:~$ cat /etc/grub.d/41_custom
#!/bin/sh
cat <
> Merci pour ces configurations qui m'aident, je les fais.
> Mais je ne m'explique pas pourquoi grub créé des erreurs de UUID.
les UUID son
e 20_linux_xen 30_uefi-firmware 41_custom
Aah, enfin une aise positive... :-)
Est-ce que je peux ou dois effacer le contenu de "/etc/grub.d" ?
car faire le ménage dans les fichiers de /etc/grub.d/ = pas facile.
> a) dans /etc/default/grub utiliser l'option
> GRUB_DISABLE_
J'ai eu récemment un problème analogue. En fait update-grub refait le grub.cfg
du système, mais ce n'est pas ce grub.cfg qui est utilisé au démarrage, c'est
celui du dernier système qui a fait un grub-install. Et cela est important
quand tu as plusieurs systèmes debian, chaque grub-install
Le vendredi 04 février 2022 à 14:34 +0100, ajh-valmer a écrit :
>
> "Normarlement..." :-)
> mais in fine, le grub.cfg généré ne peut fonctionner (cf ci-dessus).
>
> Il doit utiliser des infos mémorisées (mais ou, dans quel fichier ?)
> que update-grub ajoute da
On Friday 04 February 2022 14:18:51 Marc Chantreux wrote:
> > Normalement on n'y trouve que ce qui est présent sur le système.
> ou alors tu te traines plein de vieux kernels parce que tu n'as jamais
> fais de apt autoremove ?
apt autoremove
0 mis à jour, 0 nouvellement installés, 0 à enlever et
rents dans plusieurs menuentruy d'une même
> > partition.
> > Comment recréer un nouveau fichier GRUB "grub.cfg",
> Le fichier `grub.cfg` est autogénéré par la commande `update-grub`. Elle
> est lancée à chaque installation/mise à jour du noyau.
> Normalement on n'y
> Normalement on n'y trouve que ce qui est présent sur le système.
ou alors tu te traines plein de vieux kernels parce que tu n'as jamais
fais de apt autoremove ?
cordialement,
marc
au fichier GRUB "grub.cfg",
Le fichier `grub.cfg` est autogénéré par la commande `update-grub`. Elle
est lancée
à chaque installation/mise à jour du noyau.
Normalement on n'y trouve que ce qui est présent sur le système.
Peut-être que tu as des choses pas standard dans le fichier
`/etc/
Bonjour,
Mon fichier "grub.cfg" fait des kilomètres de hauteur,
à cause de centaines de lignes redondantes et totalement inutiles,
sans compter des UUID différents dans plusieurs menuentruy d'une même partition.
Comment recréer un nouveau fichier GRUB "grub.cfg",
qui ne repre
ew installation. I've run buster from an external drive
> for a while, but have recently installed bullseye on its SSD.
>
> > When it reached the GRUB screen, I pressed Enter, and nothing happened
> > as far as I could see. I was initially worried that it had stopped
> &
cently installed bullseye on its SSD.
> When it reached the GRUB screen, I pressed Enter, and nothing happened
> as far as I could see. I was initially worried that it had stopped
> seeing my USB keyboard (a thing that I've experienced with GRUB and
> certain USB slots on certain ma
On Sun, 19 Dec 2021, Greg Wooledge wrote:
On Sun, Dec 19, 2021 at 07:19:40AM +, Tim Woodall wrote:
Check if the kernel log jumps from 1/1/70 to today as it boots. That
would point to the RTC being bad when the kernel first starts.
Not sure which log I'd need to look at for this
On 18/12/2021 16:08, Greg Wooledge wrote:
Today I rebooted my machine for the first time in quite a while, after
the kernel update that was released along with Debian 11.2.
When it reached the GRUB screen, I pressed Enter, and nothing happened
as far as I could see. I was initially worried
Looks like the fix is this:
# If you need to disable
# gfxpayload=keep on your system, just add this line (uncommented) to
# /etc/default/grub:
#
# GRUB_GFXPAYLOAD_LINUX=text
So, try just adding the above, then run "update-grub" to activate the change.
The problem seems to be some GPU
On Sun, Dec 19, 2021 at 02:17:17PM -, Curt wrote:
> Did we see /etc/default/grub? Could this resolution bug lead to a
> resolution via a new resolution for the New Year?
>
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/480159
>
> 11 years old, but still extan
On Sun, Dec 19, 2021 at 07:19:40AM +, Tim Woodall wrote:
> Check if the kernel log jumps from 1/1/70 to today as it boots. That
> would point to the RTC being bad when the kernel first starts.
Not sure which log I'd need to look at for this information. dmesg only
reports time in relative
> This will give you an idea where it is going slow.
>
> "quiet" is a kernel parameter. It's passed to the kernel. It does
> nothing until the kernel is executed, as far as I understand things.
>
> The symptoms I experienced were BEFORE the kernel was executed. During
>
On Sun, Dec 19, 2021 at 12:54:04PM +, James Dutton wrote:
> One question, does it boot faster if you just press enter at the grub
> menu, and don't wait for the counter?
On Sat, Dec 18, 2021 at 11:08:37AM -0500, Greg Wooledge wrote:
[...]
> When it reached the GRUB screen, I pres
On Sat, 18 Dec 2021 at 23:54, Greg Wooledge wrote:
> The symptoms I experienced were BEFORE the kernel was executed. During
> GRUB itself. While sitting at the GRUB menu.
>
> Once the kernel started running, everything was within normal expectations.
>
Sounds like a race condit
On Sat 18 Dec 2021 at 11:08:37 -0500, Greg Wooledge wrote:
> Today I rebooted my machine for the first time in quite a while, after
> the kernel update that was released along with Debian 11.2.
>
> When it reached the GRUB screen, I pressed Enter, and nothing happened
> as far as
-GRUB.
I upgraded three machines to that kernel, today. Two of them
went smoothly. One of them took a ridiculously long time to
boot.
I suspect it is some interesting interaction specific to machine
quirks and this release and/or kernel.
The problem, as described, is during the grub countdown
my experience with Grub(1) sloth:
https://www.linuxquestions.org/questions/linux-general-1/grub-legacy-delay-of-more-than-2-minutes-loading-initrd-from-ext4-filesystem-4175599620/
It could be Grub2 is capable of similar delays from a poor BIOS INT13*
implementation.
--
Evolution as taught in
uiet" is a kernel parameter. It's passed to the kernel. It does
nothing until the kernel is executed, as far as I understand things.
The symptoms I experienced were BEFORE the kernel was executed. During
GRUB itself. While sitting at the GRUB menu.
Once the kernel started runni
Disk looks OK to me.
Next, check no USB devices are connected while it boots.
Disable "quiet" boot mode, so you can see all the boot up messages.
This will give you an idea where it is going slow.
On Sat, 18 Dec 2021 at 22:39, Greg Wooledge wrote:
>
> On Sat, Dec 18, 2021 at 10:23:54PM +,
Greg Wooledge wrote:
> Today I rebooted my machine for the first time in quite a while, after
> the kernel update that was released along with Debian 11.2.
...
> Eventually, after a minute or two, the system booted. Everything is
> working normally now, post-GRUB.
I upgraded th
On Sat, Dec 18, 2021 at 10:23:54PM +, James Dutton wrote:
> Hi,
>
> This is most likely a failing disk.
> Please post the output of:
> smartctl -a /dev/sda
>
> or whatever your disk device name is, if not sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-10-amd64] (local build)
after
> the kernel update that was released along with Debian 11.2.
>
> When it reached the GRUB screen, I pressed Enter, and nothing happened
> as far as I could see. I was initially worried that it had stopped
> seeing my USB keyboard (a thing that I've experienced with GRUB and
> cert
Today I rebooted my machine for the first time in quite a while, after
the kernel update that was released along with Debian 11.2.
When it reached the GRUB screen, I pressed Enter, and nothing happened
as far as I could see. I was initially worried that it had stopped
seeing my USB keyboard
n designation in /dev/sdXY format.
> >
> > I give all partitions descriptive labels.
> > I want the Grub menu to display OS and the partition label.
> > I want it to update appropriately after using update-grub.
> >
> > Is there an appropriate tool?
> > TI
ignation in /dev/sdXY format.
> >
> > I give all partitions descriptive labels.
> > I want the Grub menu to display OS and the partition label.
> > I want it to update appropriately after using update-grub.
> >
> > Is there an appropriate tool?
> > TI
On Thu 09 Dec 2021 at 08:28:37 (-0800), Peter Ehlert wrote:
> the full error message at the end of update-grub:
>
> Warning: os-prober will not be executed to detect other bootable partitions.
> Systems on them will not be added to the GRUB boot configuration.
> Check GRUB_DI
the full error message at the end of update-grub:
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Question: why would this desirable?
it's totally new
On Wed 08 Dec 2021 at 12:16:49 (-0500), songbird wrote:
> Richard Owlett wrote:
> ...
> > I see no reference for Grub being able to read a partition's label only
> > its UUID.
>
> i don't use UUIDs (LABELS only) so i do this in /etc/default/grub:
>
> =
> #
On 12/08/2021 06:33 AM, Richard Owlett wrote:
I have a machine set aside for experimenting with different
configurations of Debian. The default Grub2 menu will display OS(with
version) and partition designation in /dev/sdXY format.
I give all partitions descriptive labels.
I want the Grub
Richard Owlett wrote:
...
> I see no reference for Grub being able to read a partition's label only
> its UUID.
i don't use UUIDs (LABELS only) so i do this in /etc/default/grub:
=
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
GRUB_DISABLE
give all partitions descriptive labels.
I want the Grub menu to display OS and the partition label.
I want it to update appropriately after using update-grub.
Is there an appropriate tool?
You want to read
https://www.gnu.org/software/grub/manual/grub/grub.html#Shell_002dlike-scripting
and make
Richard Owlett wrote:
> I have a machine set aside for experimenting with different configurations
> of Debian. The default Grub2 menu will display OS(with version) and
> partition designation in /dev/sdXY format.
>
> I give all partitions descriptive labels.
> I want the Grub
I have a machine set aside for experimenting with different
configurations of Debian. The default Grub2 menu will display OS(with
version) and partition designation in /dev/sdXY format.
I give all partitions descriptive labels.
I want the Grub menu to display OS and the partition label.
I want
Bonjour à tous,
Sous Debian Buster :
grub-install /dev/sda1
Réponse :
"Installation pour la plate-forme i386-pc.
grub-install : attention : Le système de fichiers «ntfs» ne prend pas en
charge l'embarquage.
grub-install : attention : L'embarquage est impossible.
GRUB ne peut être install
the
grub EFI into the EFI partition on the mobile disk but on the one in the
built-in disk. But that was easily fixed by by mounting the mobile EFI
partition, correcting /sys/fstab and re-installing grub and kernel.
Am 16.09.2021 06:44 schrieb Andrei POPESCU:
On Mi, 15 sep 21, 05:49:01, Musbur
On Mi, 15 sep 21, 05:49:01, Musbur wrote:
>
> Now I'm in my "full" Debian system. Next:
> # grub-install /dev/sda2
> # apt install [linux kernel]
> # update-grub
> Error: Cannot find GRUB drive for /dev/sda2
Unless you have a good reason to do otherwise grub is instal
/resolv.conf /mnt/etc/resolv.conf
4) # chroot /mnt
5) mount /dev/sda2 /boot
Now I'm in my "full" Debian system. Next:
# grub-install /dev/sda2
# apt install [linux kernel]
# update-grub
Error: Cannot find GRUB drive for /dev/sda2
I tried both the grub-pc as well as the grub-efi version
On 2021-08-16 6:44 a.m., Andrew M.A. Cater wrote:
> On Mon, Aug 16, 2021 at 06:19:47AM -0400, Polyna-Maude Racicot-Summerside
> wrote:
>> Hi,
>>
>> On 2021-08-16 2:30 a.m., to...@tuxteam.de wrote:
>>> On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside
>>> wrote:
> And one of the best way of learning is by trial and error
Dear Polly, but, you are so beautiful : not only Beautiful, but,
French-Canadienne-Beautiful
thank you : bless you
.
And one of the best way of learning is by trial and error
Dear Polly, but, you are so beautiful
.
regards
.
On Sun 15 Aug 2021 at 20:31:36 +, Andrew M.A. Cater wrote:
> On Sun, Aug 15, 2021 at 10:13:07PM +0300, Gunnar Gervin wrote:
[...]
> > Debian and Devuan obviously don't mix with Mint. And vice versa. Why not,
> > really? You can learn around Efi & Grub from each oth
On Mon, Aug 16, 2021 at 06:19:47AM -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi,
>
> On 2021-08-16 2:30 a.m., to...@tuxteam.de wrote:
> > On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside
> > wrote:
> >>
> >>
> >> On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote:
>
Hi,
On 2021-08-16 2:30 a.m., to...@tuxteam.de wrote:
> On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside
> wrote:
>>
>>
>> On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote:
>
> [...]
>
>>> Keep notes as you go. Try and raise single issues - it'll help.
>>>
>>> All the
On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside wrote:
>
>
> On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote:
[...]
> > Keep notes as you go. Try and raise single issues - it'll help.
> >
> > All the very best, as ever,
> I'd like to have as much patience you do ;-)
On 2021-08-15 3:34 p.m., Brian wrote:
> On Sun 15 Aug 2021 at 22:13:07 +0300, Gunnar Gervin wrote:
>
>> Hi.
>> After I put EFI in sda1 Refracta installer was not satisfied and told me to
>> put 'boot installer' in, and write some (unspecified) text in fstab, but
>> wasn't in ETC.
>
> [...]
>
b.
> Debian and Devuan obviously don't mix with Mint. And vice versa. Why
> not, really? You can learn around Efi & Grub from each other. Now you're
> both leaving it all up to Rod Smith.
> But to me it seems a bit too much for 1 man/team. Is Linux necessary to
> be such a mess ?
401 - 500 of 8889 matches
Mail list logo
