On 26 Jul 2023 07:43 -0400, from s.mol...@sbcglobal.net:
> I just tried to boot
> into the new OS and it booted!!! After bumbling luck on my part, but I'll
> take it.
In that case, you may want to run `sudo update-grub` from within the
system that boots. Doing so will rewrite the GRUB configuratio
-Original Message-
From: Greg Wooledge
Sent: Wednesday, July 26, 2023 7:15 AM
To: debian-user@lists.debian.org
Subject: Re: Error: no such device
On Wed, Jul 26, 2023 at 06:46:31AM -0400, s.mol...@sbcglobal.net wrote:
> I installed Debian 12.0.0 on my Linux platform form the
From: s.mol...@sbcglobal.net
Sent: Wednesday, July 26, 2023 6:47 AM
To: 'debian-user@lists.debian.org'
Subject: Error: no such device
I installed Debian 12.0.0 on my Linux platform form the net install iso
without any warning or error messages. The initial boot of the sys
t;
> GRUB loading
>
> Welcome to GRUB!
>
>
>
> Error: no such device: 1d937ccf-2b57-4dcd-97d9-83522d7504f1.
>
> Error: unknown file system.
>
> grub rescue>
How exactly did you "install" Debian? In particular, when you did, did
you by any chance
se are two
dramatically different things.
> Welcome to GRUB!
> Error: no such device: 1d937ccf-2b57-4dcd-97d9-83522d7504f1.
If GRUB can't locate your root or /boot file system by UUID, then we
would need to know how you partitioned everything. Did you try to do LVM,
RAID, or any co
I installed Debian 12.0.0 on my Linux platform form the net install iso
without any warning or error messages. The initial boot of the system booted
the system came to a halt father quickly with the message:
GRUB loading
Welcome to GRUB!
Error: no such device: 1d937ccf-2b57-4dcd-97d9
On Fri, 12 Jul 2019 16:07:23 -0500
David Wright wrote:
> On Fri 12 Jul 2019 at 12:36:33 (-0700), Patrick Bartek wrote:
> > On Fri, 12 Jul 2019 06:22:16 - (UTC)
> > Bert Riding wrote:
> >
> > > Yes, I'm sorry I didn't mention that my device name was merely an
> >
> > Didn't have to. I
On Fri 12 Jul 2019 at 12:36:33 (-0700), Patrick Bartek wrote:
> On Fri, 12 Jul 2019 06:22:16 - (UTC)
> Bert Riding wrote:
>
> > Yes, I'm sorry I didn't mention that my device name was merely an
>
> Didn't have to. I understood. It's just wlan0 USED to be the default
> 1st wireless device,
On Fri, 12 Jul 2019 09:54:14 +0300
Andrei POPESCU wrote:
> On Jo, 11 iul 19, 19:26:45, Patrick Bartek wrote:
> > On Thu, 11 Jul 2019 21:02:44 - (UTC)
> > Bert Riding wrote:
> >
> > > You could try using the actual device for the -i option
> > > (interface)...like
> > > wlan0 or, in the
On Fri, 12 Jul 2019 06:22:16 - (UTC)
Bert Riding wrote:
> Yes, I'm sorry I didn't mention that my device name was merely an
Didn't have to. I understood. It's just wlan0 USED to be the default
1st wireless device, the last time I had to do this with another system
about 15 years ago, and I
On Jo, 11 iul 19, 19:26:45, Patrick Bartek wrote:
> On Thu, 11 Jul 2019 21:02:44 - (UTC)
> Bert Riding wrote:
>
> > You could try using the actual device for the -i option (interface)...like
> > wlan0 or, in the new notation wlp3s0, and use nl80122 as the -D
> > option (driver).
>
> iw dev
Yes, I'm sorry I didn't mention that my device name was merely an
example. I wonder if "ip link show" or "ls -l /sys/class/net" or the
obsolete "ifconfig a" give the same device name. Udevadm might
help, too. "udevadm info -e | grep .wl" for instance. The name you are
using is the name using
On Thu, 11 Jul 2019 21:02:44 - (UTC)
Bert Riding wrote:
> You could try using the actual device for the -i option (interface)...like
> wlan0 or, in the new notation wlp3s0, and use nl80122 as the -D
> option (driver).
iw dev or ip a report the device name to be wlx00e04c2a23c4. This
desig
You could try using the actual device for the -i option (interface)...like
wlan0 or, in the new notation wlp3s0, and use nl80122 as the -D
option (driver).
On Thu, 11 Jul 2019 02:10:02 +0200, Patrick Bartek wrote:
> A problem when trying to associate with a wireless router
> (WPA2). Get the fol
A problem when trying to associate with a wireless router
(WPA2). Get the following error when manually executing:
wpa_supplicant -i wlx
-c /etc/wpa_supplicant/wpa_supplicant.conf
Could not read interface wlx flags: No such device
nl80211: Driver does not support authentication/association or con
has been fixed since then.
Now I have in grub-emu:
error: no such device: dff08b74-3e1a-46b2-aef7-d1c77b14d098.
Loading Linux 4.19.0-2-amd64 ...
error: can't find command `linux'.
Loading initial ramdisk ...
error: can't find command `initrd'.
Press any key to continu
n issue? Why it doesn't see my device?
Maybe I have missed something - any warnings in Debian mailing lists, etc.
that I must read before doing an upgrade?
Now I have in grub-emu:
error: no such device: dff08b74-3e1a-46b2-aef7-d1c77b14d098.
Loading Linux 4.19.0-2-amd64 ...
error: can't find
17 matches
Mail list logo
