Re: boot fails very early with a systemd-service message about failing to load kernel variables

On 2025-02-01 12:39, Andrew M.A. Cater wrote: On Sat, Feb 01, 2025 at 10:07:49AM -0700, g...@extremeground.com wrote: On 2025-02-01 09:29, g...@extremeground.com wrote: BTW: the same happens with the previous kernel. Also, this is a Debian/Buster server running on AMD64 hardware. I've fsck'd th

Re: boot fails very early with a systemd-service message about failing to load kernel variables

On Sat, Feb 01, 2025 at 10:07:49AM -0700, g...@extremeground.com wrote: > On 2025-02-01 09:29, g...@extremeground.com wrote: > > BTW: the same happens with the previous kernel. Also, this is a > Debian/Buster server running on AMD64 hardware. I've fsck'd the partition > and it's fine. > > I reboo

Re: boot fails very early with a systemd-service message about failing to load kernel variables [RESOLVED]

On 2025-02-01 11:29, g...@extremeground.com wrote: I get the message right after the boot sequence declares the / drive clean. The subject message repeats 3 times then the system boot stops. It still responds to the keyboard but there is no system to log into. When I go into the system in a ch

Re: boot fails very early with a systemd-service message about failing to load kernel variables

On 2025-02-01 09:29, g...@extremeground.com wrote: I get the message right after the boot sequence declares the / drive clean. The subject message repeats 3 times then the system boot stops. It still responds to the keyboard but there is no system to log into. When I go into the system in a ch

Re: Boot from USB?

> Ahem, well, it is of course no SSD, just a harddrive with SATA port. > And I got this one from a heritage. Oohhh. big disappointment! Stefan

Re: Boot from USB?

Ahem, well, it is of course no SSD, just a harddrive with SATA port. And I got this one from a heritage. Hans Am Montag, 16. Dezember 2024, 16:10:02 CET schrieb Stefan Monnier: > > No problem for me, as I still only have one single 3,5" SSD. > > Really? A 3½" SSD? Where did you find such a bea

Re: Boot from USB?

> No problem for me, as I still only have one single 3,5" SSD. Really? A 3½" SSD? Where did you find such a beast? I'm curious to know the make/model. Also curious what made you choose to buy such a thing instead of the more common 2½" SSDs. Stefan

Re: Boot from USB?

Yes, same I cable I own. However, my only computer with this port is died. So at the moment I am looking for a new (better say: used) one. The cable worked well with 2,5" SSD, but 3,5" SSD need too much current, the port does not deliver. No problem for me, as I still only have one single 3,5"

Re: Boot from USB?

On 12/15/24 07:30, Hans wrote: I had this one until about 14 days ago, when my Lenovo T520 dies, which was the only one with eSATA connector. That sounds like a "USB/eSATA combo" port. My Dell Latitude E6520 has one. I use this cable to connect a 2.5" SATA drive: https://www.ebay.com/itm/

Re: Boot from USB?

On 12/14/24 12:02, Hans wrote: Hi folks, I was unaware, that a native installed linux is capable from booting at the USB-port! I put a harddrive with linux with a native installed linux (native means, the harddrive was built-in) in an usb-case and could boot from it. This was nice! Thus some qu

Re: Boot from USB?

Hi, Hans wrote: > I put a harddrive with linux with a native installed linux (native means, > the harddrive was built-in) in an usb-case and could boot from it. > [...] > 1. Is this is normal standard behaviour and can this be confirmed? This depends on the settings of your computers firmware (Le

Re: Boot from USB?

On 12/14/24 15:02, Hans wrote: > Hi folks, > > I was unaware, that a native installed linux is capable from booting at > the USB-port! > > I put a harddrive with linux with a native installed linux (native > means, the harddrive was built-in) in an usb-case and could boot from > it. This was nice!

Re: Boot from USB?

On Sat, Dec 14, 2024 at 09:02:45PM +0100, Hans wrote: I put a harddrive with linux with a native installed linux (native means, the harddrive was built-in) in an usb-case and could boot from it. This was nice! Thus some questions appeared: 1. Is this is normal standard behaviour and can this be

Re: boot Debian Gnome, Debian KDE, and Mate, XFCE

On 28/09/2024 22:04, George at Clug wrote: To get the earlier installations to discover the later installed installations, I ran grub-mkconfig I have never tried it, but my impression is that in the case of UEFI boot, rEFInd may detect installed OSes dynamically without explicit configurati

Re: boot Debian Gnome, Debian KDE, and Mate, XFCE

Hi, Thanks for your report! Le 29/09/2024, George at Clug a écrit: > # grub-mkconfig -o /boot/grub/grub.cfg > https://averagelinuxuser.com/dual-boot-arch-linux-with-linux/ Alternatively, you could have used a simple 'update-grub' because: $ cat $(which update-grub) #!/bin/sh set -e exec grub-

Re: boot Debian Gnome, Debian KDE, and Mate, XFCE

Hi, I decided I should again test setting up 'multi boot linux installations' on a single PC with multiple disk drives, to verify my previous failures at doing this. The result of this test? It seems that Grub does a great job of booting from multiple linux installations. For testing I creat

Re: boot Debian Gnome, Debian KDE, and Mate, XFCE

On 27/09/2024 18:53, George at Clug wrote: 3) I am not confident that constant switching between display manager, e.g. LightDM, SLiM, XDM, GDM, SDDM, KDM, Ly will not cause issues. Besides the frustration of changing the configuration each time you want to jump into another DE. Is it really n

Re: boot Debian Gnome, Debian KDE, and Mate, XFCE

On Friday, 27-09-2024 at 12:40 David Wright wrote: > On Thu 26 Sep 2024 at 09:52:18 (+0100), Joe wrote: > > On Thu, 26 Sep 2024 07:19:26 +1000 George at Clug wrote: > > > On Wednesday, 25-09-2024 at 12:37 Max Nikulin wrote: > > > > On 25/09/2024 04:52, George at Clug wrote: > > > > > An other

Re: boot Debian Gnome, Debian KDE, and Mate, XFCE

On Thu 26 Sep 2024 at 09:52:18 (+0100), Joe wrote: > On Thu, 26 Sep 2024 07:19:26 +1000 George at Clug wrote: > > On Wednesday, 25-09-2024 at 12:37 Max Nikulin wrote: > > > On 25/09/2024 04:52, George at Clug wrote: > > > > An other example would be to boot Debian Gnome, Debian KDE, and > > > > D

Re: boot Debian Gnome, Debian KDE, and Mate, XFCE

On Thu, 26 Sep 2024 07:19:26 +1000 George at Clug wrote: > My experiences - George. > > On Wednesday, 25-09-2024 at 12:37 Max Nikulin wrote: > > On 25/09/2024 04:52, George at Clug wrote: > > > An other example would be to boot Debian Gnome, Debian KDE, and > > > Debian Mate, Debian XFCE. >

Re: boot Debian Gnome, Debian KDE, and Mate, XFCE

On 26/09/2024 04:19, George at Clug wrote: Grub did not find other existing Linux distributions. Found Windows, but not other linux distributions. The following has been discussed on debian-user:

Re: /boot/grub/grub.cfg hex number reference

On Wed 13 Mar 2024 at 18:59:30 (+), Gareth Evans wrote: > On Wed 13/03/2024 at 12:50, Michel Verdier wrote: > > On 2024-03-13, Gareth Evans wrote: > > > >> That suggests perhaps something to do with an FS UUID, but it doesn't seem > >> to appear in the output of any of > >> > >> # blkid > > >

Re: /boot/grub/grub.cfg hex number reference

> On 13 Mar 2024, at 19:00, Gareth Evans wrote: > > Hi Michael, I'm sorry - Michel

Re: /boot/grub/grub.cfg hex number reference

On Wed 13/03/2024 at 12:50, Michel Verdier wrote: > On 2024-03-13, Gareth Evans wrote: > >> That suggests perhaps something to do with an FS UUID, but it doesn't seem >> to appear in the output of any of >> >> # blkid > > Here I have them shown as UUID by blkid > > # grep root /boot/grub/grub.cfg

Re: /boot/grub/grub.cfg hex number reference

On 2024-03-13, Gareth Evans wrote: > That suggests perhaps something to do with an FS UUID, but it doesn't seem to > appear in the output of any of > > # blkid Here I have them shown as UUID by blkid # grep root /boot/grub/grub.cfg ... search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gp

Re: Boot Problem

Stephen P. Molnar composed on 2023-12-05 13:33 (UTC-0500): > I decided to try something. I logged in to the rescue  mode as root and > entered startx at the prompt. This generated the error: I believe if xserver-xorg-legacy is not installed that startx failure is expected. I keep it installed o

Re: Boot Problem

Please forgive me if I somehow messed up the quote attribution. There was a lot of stuff I was able to cull. :) On 12/5/23, David Christensen wrote: > On 12/5/23 10:33, Stephen P. Molnar wrote: > > I decided to try something. I logged in to the rescue mode as root and > > entered startx at the

Re: Boot Problem

On 5 Dec 2023 11:05 -0500, from s.mol...@sbcglobal.net (Stephen P. Molnar): > I have Bookworm installed on a 1TB SSD. When I attempted logging this > morning I failed! Rather than opening my XFCE desktop I was sent back tot he > login screen, over and over and . I got the same resul

Re: Boot Problem

On 12/5/23 08:05, Stephen P. Molnar wrote: I have Bookworm installed on a 1TB SSD. When I attempted logging this morning I failed! Rather than opening my XFCE desktop I was sent back tot he login screen, over and over and . I got the same result attempting to login as root. I ha

Re: Boot Problem

My Os is up to date and running the version XFCE4 I've attached the log files that i could find. I hope that it will help. On 12/05/2023 02:26 PM, Alexander V. Makartsev wrote: On 05.12.2023 23:33, Stephen P. Molnar wrote: I decided to try something. I logged in to the rescue  mode as root an

Re: Boot Problem

Am Dienstag, 5. Dezember 2023, 18:56:48 CET schrieb Stephen P. Molnar: Not good! You have to start startx from the shell. However, when you see the login screen (gdm, lightdm, kdm, whatever), that means, the X-server is running and ok. So you have a problem with XFCE. Look at ~/.config/xfce4 an

Re: Boot Problem

On 05.12.2023 23:33, Stephen P. Molnar wrote: I decided to try something. I logged in to the rescue  mode as root and entered startx at the prompt. This generated the error: Unable to contact settings server failed to execute child process "dbus-launch" (No such file or directory) I vaguely re

Re: Boot Problem

I decided to try something. I logged in to the rescue  mode as root and entered startx at the prompt. This generated the error: Unable to contact settings server failed to execute child process "dbus-launch" (No such file or directory) On 12/05/2023 01:03 PM, Tom Furie wrote: "Stephen P. Moln

Re: Boot Problem

"Stephen P. Molnar" writes: > On 12/05/2023 12:47 PM, Tom Furie wrote: >> "Stephen P. Molnar" writes: >> >>> I have Bookworm installed on a 1TB SSD. When I attempted logging this >>> morning I failed! Rather than opening my XFCE desktop I was sent back >>> tot he login screen, over and over and

Re: Boot Problem

I've attached the log. I hope that someone can tell me what the problem is. Thanks inn advance. On 12/05/2023 11:59 AM, Joe wrote: On Tue, 5 Dec 2023 11:05:15 -0500 "Stephen P. Molnar" wrote: I have Bookworm installed on a 1TB SSD. When I attempted logging this morning I failed! Rather than

Re: Boot Problem

Xfce4 graphical login screen On 12/05/2023 12:47 PM, Tom Furie wrote: "Stephen P. Molnar" writes: I have Bookworm installed on a 1TB SSD. When I attempted logging this morning I failed! Rather than opening my XFCE desktop I was sent back tot he login screen, over and over and ...

Re: Boot Problem

"Stephen P. Molnar" writes: > I have Bookworm installed on a 1TB SSD. When I attempted logging this > morning I failed! Rather than opening my XFCE desktop I was sent back > tot he login screen, over and over and . I got the When you say "back to the login screen", do you mean ba

Re: Boot Problem

On Tue, 5 Dec 2023 11:05:15 -0500 "Stephen P. Molnar" wrote: > I have Bookworm installed on a 1TB SSD. When I attempted logging this > morning I failed! Rather than opening my XFCE desktop I was sent back > tot he login screen, over and over and . I got the > same result attempt

Re: Boot Problem

Am Dienstag, 5. Dezember 2023, 17:05:15 CET schrieb Stephen P. Molnar: To get closer to the cause, I suggest to remove temporaryly any loginmamanger out of the way Either /usr/bin/xdm, /usr/bin/kdm, /usr/bin/gdm or /usr/bin/ xdm, whatever. Copy it somewhere, i.e. to /root Then reboot and from th

Re: Boot fails to load network or USB, piix4_smbus - SMBus Host Controller, after update to dbus (1.14.10-3) unstable SOLVED

I'm pretty sure you can bind mount /proc, /sys, /dev, /run, chroot and then update-initramfs to regen. Thanks Tim. You make it sound so simple. I searched for "chroot to mounted disk to update initramfs" and found several detailed descriptions of the process. https://forums.debian.net/viewtop

Re: Boot fails to load network or USB, piix4_smbus - SMBus Host Controller, after update to dbus (1.14.10-3) unstable

I'm pretty sure you can bind mount /proc, /sys, /dev, /run, chroot and then update-initramfs to regen. Thanks Tim. You make it sound so simple. I searched for "chroot to mounted disk to update initramfs" and found several detailed descriptions of the process. https://forums.debian.net/viewto

Re: Boot fails to load network or USB, piix4_smbus - SMBus Host Controller, after update to dbus (1.14.10-3) unstable

On Thu, 23 Nov 2023, Andy Dorman wrote: I have not yet figured out how to fix our two broken servers since we can't boot them to update them. Since we have several identical running servers and can mount and manipulate the file system of the dead servers, is it possible to just copy a good in

Re: Boot fails to load network or USB, piix4_smbus - SMBus Host Controller, after update to dbus (1.14.10-3) unstable

On Thu, Nov 23, 2023 at 4:09 PM Andy Dorman wrote: > > I have continued to research this and I think I found the problem. > > I also think the dbus update timing mentioned in the subject is entirely > coincidental. I hope I haven't caused any unnecessary excitement or work > for anyone in the dbus

Re: Boot fails to load network or USB, piix4_smbus - SMBus Host Controller, after update to dbus (1.14.10-3) unstable

I have continued to research this and I think I found the problem. I also think the dbus update timing mentioned in the subject is entirely coincidental. I hope I haven't caused any unnecessary excitement or work for anyone in the dbus package team. My apologies if I did. A few months back we

Re: Boot issue

On Sun, Aug 27, 2023 at 22:51 David Wright wrote: > On Sun 27 Aug 2023 at 14:27:09 (-0500), Tom Browder wrote: > > On Sun, Aug 27, 2023 at 13:27 Greg Wooledge wrote: > > > > > On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote: > > > > When I boot the system, then the drives are not mounted as

Re: Boot issue

On Sun 27 Aug 2023 at 14:27:09 (-0500), Tom Browder wrote: > On Sun, Aug 27, 2023 at 13:27 Greg Wooledge wrote: > > > On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote: > > > When I boot the system, then the drives are not mounted as set in > > /etc/fstab. > > > For example, the SDD should mou

Re: Boot issue

On Sun, Aug 27, 2023 at 13:27 Greg Wooledge wrote: > On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote: > > When I boot the system, then the drives are not mounted as set in > /etc/fstab. > > For example, the SDD should mounted to /space, and the unencrypted HDD ... > Use UUIDs or Labels ins

[SOLVED] Re: Boot issue

I am answering myself. It must be the opened UUID. Looks like this problem is solved. Thank you all for the fast response! I hope, my question was not too annoying. But I am very very happy, to get this little issue so easily solved - and learned something, too. Thank you all, you made a man

Re: Boot issue

So, now I added all UUIDs. But I am not quite sure for the enrcypted /home partition. The UUID changes when the device is luks-opened. Which one must be in the fstab? The one from "lsblk -f /dev/sda4" or "lsblk -f /dev/mapper/home"? Am Sonntag, 27. August 2023, 20:26:46 CEST schrieb Greg W

Re: Boot issue

Here it is: # /etc/fstab: static file system information. # # proc/proc procdefaults0 0 # /dev/sda3 / ext4defaults,errors=remount-ro 0 1 UUID=819bf8ae-a727-4b5e-97f8-007f58e98f74 /

Re: Boot issue on system with four SATA devices

On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote: > Dear list, > > there is a little issue, which I try to solve. On my desptop computer I have > 4 > harddrives: > > SATA 0: HDD 300 GB with Debian + GRUB on MBR (parted in /boot, /, /home > (luks), /var (luks) and /usr (luks) > SATA 1: HDD

Re: Boot issue

Hans composed on 2023-08-27 20:19 (UTC+0200): > When I boot the system, then the drives are not mounted as set in /etc/fstab. > For example, the SDD should mounted to /space, and the unencrypted HDD shall > be mounted to /daten. > But it seems, sometimes the mountpoints are not correct, so the

Re: Boot issue

On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote: > Dear list, > > there is a little issue, which I try to solve. On my desptop computer I have > 4 > harddrives: > > SATA 0: HDD 300 GB with Debian + GRUB on MBR (parted in /boot, /, /home > (luks), /var (luks) and /usr (luks) > SATA 1: HDD

Re: Boot issue

On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote: > When I boot the system, then the drives are not mounted as set in /etc/fstab. > For example, the SDD should mounted to /space, and the unencrypted HDD shall > be mounted to /daten. > > But it seems, sometimes the mountpoints are not correct

Re: Boot issue

> When I boot the system, then the drives are not mounted as set in /etc/fstab. I suspect that showing us your `/etc/fstab` would help, Stefan

Re: Boot an EFI system with QEMU

On Tue, Apr 25, 2023 at 07:00:21PM +0200, Valentin Caracalla wrote: >Hello Steve, > >thanks a lot for the tip! However, I'm a complete novice when it comes to >running custom firmware in QEMU. I just tried the following: > >1.: Download the latest EDK2 release from Github: > >https://github.com/ti

Re: Boot an EFI system with QEMU

Valentin Caracalla (12023-04-25): > thanks a lot for the tip! However, I'm a complete novice when it comes to > running custom firmware in QEMU. I just tried the following: > > 1.: Download the latest EDK2 release from Github: I could boot a VM with a UEFI bootloader using only files packaged by

Re: Boot Errors

When you get the "invalid argument" error do you see something in the output of "dmesg"? Can you try to mount it from another distro live-USB or from the Debian installer rescue mode? Enviado desde Outlook Mobile From: Michael Lee Sent: T

Re: /boot/grub/grub.cfg menu entries

Intense Red composed on 2022-12-08 16:42 (UTC-0600): >That seems to be the problem -- os-prober only shows that /dev/sdf1 has an > OS on it, it seems to ignore the linux install on /dev/sdg1. Did you install one in legacy mode and the other in UEFI mode? Is GRUB_DISTRIBUTOR= in /etc/default

Re: /boot/grub/grub.cfg menu entries

> You can also try os-prober as root and see if it detects the other > partitions. That seems to be the problem -- os-prober only shows that /dev/sdf1 has an OS on it, it seems to ignore the linux install on /dev/sdg1. IMO the next question becomes how do I convince os-prober to see /dev/s

Re: /boot/grub/grub.cfg menu entries

On Wed 07 Dec 2022 at 00:14:48 (-0600), Intense Red wrote: > > To re-enable this, set GRUB_DISABLE_OS_PROBER=false in /etc/default/grub. > >Thanks! But I did that, ran update-grub which reported: > > > Warning: os-prober will be executed to detect other bootable partitions. > > Its output wil

Re: /boot/grub/grub.cfg menu entries

> > To re-enable this, set GRUB_DISABLE_OS_PROBER=false in /etc/default/grub. > >Thanks! But I did that, ran update-grub which reported: > > > Warning: os-prober will be executed to detect other bootable partitions. > > Its output will be used to detect bootable binaries on them and create >

Re: /boot/grub/grub.cfg menu entries

> To re-enable this, set GRUB_DISABLE_OS_PROBER=false in /etc/default/grub. Thanks! But I did that, ran update-grub which reported: > Warning: os-prober will be executed to detect other bootable partitions. > Its output will be used to detect bootable binaries on them and create new boot entr

Re: /boot/grub/grub.cfg menu entries

Michel Verdier: > Intense Red: > > > Looking at /boot/grub/grub.cfg it uses a function format that I > > don't recognize and cannot make easy sense of -- I just want a simple > > text entry to give me the option of booting off sdf1 or sdg1 in the > > grub menu. > > > > Can anyone whack me with

Re: /boot/grub/grub.cfg menu entries

Le 6 décembre 2022 Intense Red a écrit : > Looking at /boot/grub/grub.cfg it uses a function format that I don't > recognize and cannot make easy sense of -- I just want a simple text entry to > give me the option of booting off sdf1 or sdg1 in the grub menu. > >Can anyone whack me with a

Re: /boot/grub/grub.cfg menu entries

06/12/2022 19:49, Intense Red wrote: On my machine I have 2 bootable Linux installs, one each on /dev/sdf1 and / dev/sdg1. Grub *used to* detect the various partitions and creat entries for each one, but in this install it didn't do that. Looking at /boot/grub/grub.cfg it uses a function

Re: /boot size and kernel updates

> I used the MODULES=dep setting and got a reduction from 70mb to 20mb > for each initramfs. Wow, that's still about twice as large as what I get on my amd64/armhf/686 systems (I typically get about 40MB for MODULES=most and 10-12MB for MODULES=dep). The compression algorithm in use makes some di

Re: /boot size and kernel updates

> On 13 Nov 2022, at 23:06, Mike Kupfer wrote: > > Hi Stefan! > > Stefan Monnier wrote: > >> I use `MODULES=dep` and my kernel+initrd uses less than 20MB still so my >> 250MB /boot partition is currently 21% full with 2 kernels installed. > > Ah, thanks for the tip. I'll give that a try,

Re: /boot size and kernel updates

Hi Stefan! Stefan Monnier wrote: > I use `MODULES=dep` and my kernel+initrd uses less than 20MB still so my > 250MB /boot partition is currently 21% full with 2 kernels installed. Ah, thanks for the tip. I'll give that a try, as well as trying more aggressive compression (thanks, Peter!). > Th

Re: /boot size and kernel updates

Hi Mike, > I've had the problem with /boot being too small on 2 systems. I tried > reinstalling one of them so that I could get a larger /boot. And the > installer did make /boot larger, but not as much as I wanted. IIRC, it > went from 250M to 500M, whereas I wanted to give it at least 1 GB.

Initramfs compression algorithm - was Re: /boot size and kernel updates

To reduce size of initramfs I change the compression setting in /etc/initramfs/initramfs.conf and set it to “xz” After that one needs to rebuild initramfs. Sent from my phone. Please forgive misspellings and weird “corrections” > On 13 Nov 2022, at 16:35, David Christensen wrote: > > On 1

Re: /boot size and kernel updates

On Sun, 13 Nov 2022 14:45:15 + "Andrew M.A. Cater" wrote: > Ideally, you shouldn't need more than the current kernel and, > perhaps, the previous version. One nitpick: I believe that installing a new kernel means installing the new kernel, and only if that is successful removing an old one.

Re: /boot size and kernel updates

On 11/13/22 01:41, Peter von Kaehne wrote: I mostly let the installer do what it likes to do when installing Debian and this has worked out fine until the last couple installs on UEFI rather than legacy boot. It now appears that the automatic installer does not get size of /boot right - even

Re: /boot size and kernel updates

Peter von Kaehne wrote: > It now appears that the automatic installer does not get size of /boot > right - even with only one new kernel update wanting to install itself > it often fails with lack of space. I have had this problem, too, so thank you for bringing it up on the list. > One solutio

Re: /boot size and kernel updates

Andrew M.A. Cater wrote: > Ideally, you shouldn't need more than the current kernel and, perhaps, the > previous version. If the current kernel works on the reboot, then you should > be able to remove all previous variants with the same major version number. It used to be that I could leave the o

Re: /boot size and kernel updates

On Sun, Nov 13, 2022 at 09:41:43AM +, Peter von Kaehne wrote: > I mostly let the installer do what it likes to do when installing Debian and > this has worked out fine until the last couple installs on UEFI rather than > legacy boot. > > It now appears that the automatic installer does not

Re: Boot usb

Hi, maybe the USB stick mounts automagically if you just plug it out after copying the ISO and then plug it in again. (I personally dislike this automount feature.) Gunnar Gervin wrote: > I have burned iso image to usb but it is unmounted. Do you mean that it cannot be mounted ? It must not be

Re: Boot usb

Hm. Tried press option key But usb does not show in screen And when in grub wrote boot=/dev/sdb a ? mark came on screen, which only came up black with blinker up in left corner... & nothing else. Nope Youtube did not solve it.. Debian live again, soon, or else how reset back to start... Gunnar PS G

Re: Boot usb

On Wed, Jul 14, 2021 at 11:37:47AM +1000, Keith Bainbridge wrote: > The boot command requires a mount point, ... huh? This makes no sense. There is no "boot command", and there is no need to mount a USB device to which you have written a Debian installer ISO image. In fact, mounting at any poin

Re: Boot usb

Good Morning Gunnar The boot command requires a mount point, but I'm never sure how to do this well outside of file manager In any case, if you're confident that the USB was correctly written, just try booting to it All the best Keith Bainbridge keithrbaugro...@gmail.com On 7/14/21 11

Re: Boot usb

On Wed, 14 Jul 2021 04:14:41 +0300 Gunnar Gervin wrote: > Hi. > I have burned iso image to usb but it is unmounted. > Thus can probably not be booted(?) No - whether or not it is currently mounted (or mountable at all, in /etc/fstab, etc.) makes no difference as to whether it will successfully b

Re: Boot Repair. Still Going Round and Round.

I placed the ailing drive back on a good Linux system and mounted it as /dev/sdd1 /mnt and ran the following commands on it: #!/bin/sh #mount the drive being repaired. Uncomment lines as needed. sudo mount /dev/sdd1 /mnt cd /mnt/boot #installing to the mounted disk sudo grub-install \ --boot-

Re: Boot Repair

Martin McCormick wrote: > This is actually a systemic problem these days when > dealing with sick machines. Nobody is selling new desktops > with RS-232 native serial ports and that is fine as long as > there is an alternative way such as a bluetooth interface or ssh > network connection.

Re: Boot Repair

Weaver writes: > Well, let us know how it goes, because I've noted a few visually > disadvantaged users on the list, and they would find the reference > useful. I have found out that grub is very accessible if one has defined a serial console and there is a working serial port on the targ

Re: Boot Repair

On 03-06-2021 13:02, Martin McCormick wrote: > Weaver writes: >> https://www.supergrubdisk.org/ > > The site recommends downloading the hybrid version of > grub2disk so that is what I did because all the Linux boxes I > have are x86 hardware and have CD technology built in. > > This

Re: Boot Repair

Weaver writes: > https://www.supergrubdisk.org/ The site recommends downloading the hybrid version of grub2disk so that is what I did because all the Linux boxes I have are x86 hardware and have CD technology built in. This is quite an interesting creation. The ISO image is a we

Re: Boot Repair

On 03-06-2021 05:59, Martin McCormick wrote: > Weaver writes: >> On 03-06-2021 03:59, Martin McCormick wrote: >> > Is there any free utility that can run in Linux which helps one >> > rebuild a corrupted boot configuration? >> >> https://www.supergrubdisk.org/ > > Thank you very much as you

Re: Boot Repair

Weaver writes: > On 03-06-2021 03:59, Martin McCormick wrote: > > Is there any free utility that can run in Linux which helps one > > rebuild a corrupted boot configuration? > > https://www.supergrubdisk.org/ Thank you very much as you did answer my question perfectly but I did not stop

Re: Boot Repair

On 03-06-2021 03:59, Martin McCormick wrote: > Is there any free utility that can run in Linux which helps one > rebuild a corrupted boot configuration? https://www.supergrubdisk.org/ Cheers! Harry. -- ‘The issues are too important to be left for the voters’. ― Henry Kissinger

Re: boot screen not shown properly

i've solved on my own, it's easyopen grub.cfg in /boot/grubreplace "insmod all_video" with "insmod vga" some user just ask me to provide more detailsafter i do so, they say nothing, they don't look like experti've said grub screen isn't ok but screen is ok after  debian boots doesn't such info

Re: boot screen not shown properly

Hi ! On 2021-05-27 4:48 p.m., Long Wind wrote: > grub screen isn't ok, i can't see grub menu, i can't see any text, i > just see some dots > after some time, i can see debian boots > i think both grub and debian use text mode though some users will > eventually boot into graphics mode > > it's th

Re: boot screen not shown properly

On 2021-05-27 4:48 p.m., Long Wind wrote: > grub screen isn't ok, i can't see grub menu, i can't see any text, i > just see some dots > after some time, i can see debian boots > i think both grub and debian use text mode though some users will > eventually boot into graphics mode > > it's thin c

Re: boot screen not shown properly

You still haven't described properly... What does "screen isn't ok" supposed to mean ? What isn't okay with the screeen ? What is the configuration inside this laptop ? The more you save people work, the more chance you may get helped. So let us understand what's inside you laptop as hardware inst

Re: Boot better have mounted on root or /boot ?

On Sun, Apr 11, 2021 at 02:33:22PM -0400, Felix Miata wrote: On Thu 08 Apr 2021 at 14:37:59 (+0200), Marco Ippolito wrote: What would you consider in your future planning regarding sizing /boot? root@asa88:/boot#

Re: Boot better have mounted on root or /boot ?

David Wright composed on 2021-04-13 09:52 (UTC-0500): > On Sun 11 Apr 2021 at 14:33:22 (-0400), Felix Miata wrote: >>> On Thu 08 Apr 2021 at 14:37:59 (+0200), Marco Ippolito wrote: What would you consider in your future planning regarding sizing /boot? >> root@asa88:/boot# du -sh . >> 769M

Re: Boot better have mounted on root or /boot ?

On Sun 11 Apr 2021 at 14:33:22 (-0400), Felix Miata wrote: > > On Thu 08 Apr 2021 at 14:37:59 (+0200), Marco Ippolito wrote: > > >> What would you consider in your future planning regarding sizing /boot? > > root@asa88:/boot# du -sh . > 769M. > root@asa88:/boot# dpkg -l | grep linux-image-4 |

Re: Boot better have mounted on root or /boot ?

> On Thu 08 Apr 2021 at 14:37:59 (+0200), Marco Ippolito wrote: >> What would you consider in your future planning regarding sizing /boot? root@asa88:/boot# du -sh . 769M. root@asa88:/boot# dpkg -l | grep linux-im

Re: Boot better have mounted on root or /boot ?

On Fri 09 Apr 2021 at 21:10:20 (+0300), Andrei POPESCU wrote: > On Vi, 09 apr 21, 09:14:31, to...@tuxteam.de wrote: > > On Fri, Apr 09, 2021 at 09:07:04AM +0300, Andrei POPESCU wrote: > > > On Jo, 08 apr 21, 07:21:04, Eike Lantzsch ZP6CGE wrote: > > > > On Donnerstag, 8. April 2021 02:15:00 -04 And

Re: Boot better have mounted on root or /boot ?

On Thu 08 Apr 2021 at 14:37:59 (+0200), Marco Ippolito wrote: > > Eventually it all boils down to one's ability to predict the future or > > at least a subset thereof. > > What would you consider in your future planning regarding sizing /boot? I create ~500MB ESP and /boot partitions on each syst

Re: Boot better have mounted on root or /boot ?

On Fri, Apr 09, 2021 at 02:37:22PM -0400, Dan Ritter wrote: > Andrei POPESCU wrote: > > > > apt show grml-rescueboot > > Thanks muchly! Seconded :) -- t signature.asc Description: Digital signature

  1   2   3   4   5   6   7   8   9   10   >