Booting from USBs on old laptops, was Re: laptop installs

[David Wright]

On Tue 27 Aug 2024 at 21:42:22 (-0400), Roy J. Tellason, Sr. wrote:
> In the case of two of the three laptops I have here to play with,  it's 
> simply a matter of telling it to boot off the DVD drive and then inserting 
> the appropriate disc and going on from there.  In the case of this other one, 
>  things get a little weird.
> 
> On powerup I see messages referring to PXE,  which if I remember correctly 
> involves booting off a network connection?  There's "Media test failure, 
> check cable" followed by "Exiting PXE ROM" and then I get "No bootable device 
> -- insert boot disk and press any key.
> 
> The thing is,  this machine doesn't have a DVD drive.  What it does have is a 
> couple of USB ports (two different color connectors so I assume different 
> speeds?).  I am also assuming that simply putting an iso file on to a USB 
> stick won't quite do it.  No idea about how to implement anything to do with 
> PXE,  though I can probably safely assume that I have what I need on the LAN 
> here.
> 
> Any thoughts on how best to deal with this?

I assume your DVD drives are internal, so they're always present when
you boot up, and they're always selectable in the BIOS menus.

I have a laptop that only shows a USB stick as available in the menu
/if/ it's already plugged in before you turn on the power. If you
don't plug it in that early, you might be unaware that it could boot
from a USB stick at all: there's no mention of that in the specs, and
no hint in the extensive PhoenixBIOS documentation that you have to
expand the /Hard Drive/ item in the Boot menu to reveal the USB stick
under the actual hard drive. (You then have to promote the USB above
the hard drive in the two-item list.)

Cheers,
David.

Windows Update and dual booting linux

[George at Clug]

Hi,


I noticed the below issue today.


I think it only affects certain configuration of dual booting so not
too many people should be affected.

Does anyone know of people who have been affected?



https://www.theverge.com/2024/8/21/24225108/microsoft-security-update-windows-linux-dual-boot-errors

 Distributions including Ubuntu, Debian, Linux Mint, Zorin OS, and
Puppy Linux have all been affected by Microsoft’s patch.


Microsoft has been using Secure Boot in Windows for years, and made it
a key requirement for Windows 11 [1] to use the technology to secure
against BIOS rootkits. Researchers have found plenty of
vulnerabilities in Secure Boot over the years, and recently it was
discovered that Secure Boot is completely broken on many PCs [2].




George.



Links:
--
[1]
https://www.theverge.com/2021/6/29/22555371/microsoft-windows-11-cpu-support-hardware-requirements-tpm-response
[2]
https://www.theverge.com/2024/7/26/24206711/secure-boot-is-completely-broken-on-many-pcs

Re: [SOLVED] Re: Virtual machine - booting from USB?

[didier gaumet]

Le 21/08/2024 à 18:30, Hans a écrit :
[...]

Well, now as I know, that qemu is working, I will check if I can use also the
commandline with qemu. Should be possible!

[...]

That, too, is explained in the link I indicated previously,
("3. Boot From the Command Line"):
https://www.baeldung.com/linux/qemu-boot-physical-drive#boot-from-the-command-line

[SOLVED] Re: Virtual machine - booting from USB?

[Hans]

> yes
> https://www.baeldung.com/linux/qemu-boot-physical-drive
> (minimal answer ;-) )

Hi Didier,

thanks for the quick response! This is working perfectly.

However, fanca thing is: virtual-manager is working great, but Aqumu got not 
this option. Obviously both are based on qemu.

Well, now as I know, that qemu is working, I will check if I can use also the 
commandline with qemu. Should be possible! 

As virtual-manager is not always available or installed (i.e. Windows or 
MacOS), a batch file on an USB-stick starting qemu will do it.

For now I can say: Problem solved and thank you very much for the link.

Best

Hans

Re: Virtual machine - booting from USB?

[didier gaumet]

Le 21/08/2024 à 13:27, Hans a écrit :
[...]

does one know, if it is possible to boot from an USB-stick within a virtual
machine?

[...]

Short answer like "yes, it wqill wor with"  or "no, this is not
possible..." will be fine for me.

[...]

yes
https://www.baeldung.com/linux/qemu-boot-physical-drive
(minimal answer ;-) )

Virtual machine - booting from USB?

[Hans]

Hi folks,

does one know, if it is possible to boot from an USB-stick within a virtual 
machine?

I want to boot a multiboot usb stick with YUMI within a virtual machine.

Tried Virtualbox (here you can only make a *.vdk from the USB-stick and boot 
it), as well as virtual-manager (seem also only be capable to boot images) and 
quemu (with aqemu gui). Last also images, no devices.

However, I don't now if this is possible at all, so I allowed me to as here, 
if one knows, if this is possible with some virtual machine - just before I am 
trying and searching until my death.

Hint
YES - I could create an ISO-image from the USB stick and copy this to another 
USB-stick, then mount it and thenn boot it. This will work!

But NO, I do NOT want to create an ISO from the USB-stick, I just want to 
leave it as it is for some reasons.

Short answer like "yes, it wqill wor with"  or "no, this is not 
possible..." will be fine for me.

Thanks for reading.

Best regards

Hans

Re: Booting BananaPi from sd [WAS Re: can this iso be put on a micro-sd]

[gene heskett]

On 8/4/24 06:55, Andrew M.A. Cater wrote:

On Sun, Aug 04, 2024 at 02:01:24AM -0400, gene heskett wrote:

On 8/4/24 01:17, David Wright wrote:

On Sat 03 Aug 2024 at 20:04:08 (-0400), gene heskett wrote:

On 8/3/24 19:39, gene heskett wrote:

[ISO]    debian-12.6.0-arm64-DVD-1.iso



This will work on an arm64 board potentially that is in a desktop/server.
It will also work on a Raspbberry Pi 4 that's booting from a port of
Tianocore. (EDK - the UEFI basis) [For the Pi 4, Pete Batard has done
a port].


Links?

Yes, no response, written to /dev/sdl or to .dev/sdl1. The armbian .img's
for noble and bookworm written to /dev/sdl, booted to a cli in 30 or 40
seconds.



RIGHT - see previous note about Armbian and how they take the vendor
core support and make it boot. You've got a .img file - kernel, initrd
and (probably) u-boot in one file. You put it in and it boots.
The 30-40s is probably u-boot kicking in, initialising hardware
including any dtb and then booting up.
It does seem to be a 2 stage thing. But it does by at a fraction of C 
speed, to fast to capture.


If you _know_ how to build u-boot for yourself, you can possibly
get it to boot anything arbitrary but at that point it gets complicated:
see, for example 
https://www.earth.li/~noodles/blog/2023/10/debian-on-bpi-m2-zero.html

I've built an rt-preempt 4.19-something, but at the time I wasn't fam 
enough with u-boot or bootp in some circles so my middle 1940's 11x54 
Sheldon lathe I run with linuxcnc was analized and I made a 27 megabyte 
tarball that when unpacked to the sd card, installed enough of two 
directory's that it booted to the realtime version for the next 7 years. 
Folks said I couldn't run it with a pi, so I did it anyway.  Its worked 
so well that if I could still get the interface cards, I'd convert my 
other cnc'd machines to it. intel stuff works well too but is a huge 
power pig. 10x or more than the pi & monitor which totals about 25 watts.



or did you mystify yourself by trying to mount the partitions and
then abandon the process in favour of:


Now writing it to /dev/sdl1.


that didn't work either. The 2 armbian .img files worked fine, the
debian.iso failed 100%.  This thing should work for amanda, it has
recognized all 4 of the 4t SP SSD's. And in past linux installs from stretch
to buster, rpi-os just worked I had built earlier versions of amanda with
little problems as long as I skipped the docs. Thats always a problem for
intel stuff, dependency hell, for both amanda and linuxcnc.  I believe
that's my problem as the linuxcnc buildbot is doing them ok recently.


which is an odd thing to do.


Well, I'm tired of trying to make debian-arm work so you guys aren't
hassling me for bringing armbian questions here, while armbian Just Works
for everything once the network is configured. Getting the network
configured on armbian is a pita though.  Never have made it work on
debian-arm since wheezy.



One topic at a time, please, Gene :)


Cheers,
David.


Thanks David, take care & stay well.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis



.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Booting BananaPi from sd [WAS Re: can this iso be put on a micro-sd]

[Andrew M.A. Cater]

On Sun, Aug 04, 2024 at 02:01:24AM -0400, gene heskett wrote:
> On 8/4/24 01:17, David Wright wrote:
> > On Sat 03 Aug 2024 at 20:04:08 (-0400), gene heskett wrote:
> > > On 8/3/24 19:39, gene heskett wrote:
> > > > [ISO]    debian-12.6.0-arm64-DVD-1.iso
> > > > 

This will work on an arm64 board potentially that is in a desktop/server.
It will also work on a Raspbberry Pi 4 that's booting from a port of 
Tianocore. (EDK - the UEFI basis) [For the Pi 4, Pete Batard has done
a port].

> Yes, no response, written to /dev/sdl or to .dev/sdl1. The armbian .img's
> for noble and bookworm written to /dev/sdl, booted to a cli in 30 or 40
> seconds.
> 

RIGHT - see previous note about Armbian and how they take the vendor
core support and make it boot. You've got a .img file - kernel, initrd
and (probably) u-boot in one file. You put it in and it boots.
The 30-40s is probably u-boot kicking in, initialising hardware
including any dtb and then booting up.

If you _know_ how to build u-boot for yourself, you can possibly
get it to boot anything arbitrary but at that point it gets complicated:
see, for example 
https://www.earth.li/~noodles/blog/2023/10/debian-on-bpi-m2-zero.html

> > or did you mystify yourself by trying to mount the partitions and
> > then abandon the process in favour of:
> > 
> > > Now writing it to /dev/sdl1.
> 
> that didn't work either. The 2 armbian .img files worked fine, the
> debian.iso failed 100%.  This thing should work for amanda, it has
> recognized all 4 of the 4t SP SSD's. And in past linux installs from stretch
> to buster, rpi-os just worked I had built earlier versions of amanda with
> little problems as long as I skipped the docs. Thats always a problem for
> intel stuff, dependency hell, for both amanda and linuxcnc.  I believe
> that's my problem as the linuxcnc buildbot is doing them ok recently.
> 
> > which is an odd thing to do.
> 
> Well, I'm tired of trying to make debian-arm work so you guys aren't
> hassling me for bringing armbian questions here, while armbian Just Works
> for everything once the network is configured. Getting the network
> configured on armbian is a pita though.  Never have made it work on
> debian-arm since wheezy.
> 

One topic at a time, please, Gene :)

> > Cheers,
> > David.
> 
> Thanks David, take care & stay well.
> 
> Cheers, Gene Heskett, CET.
> -- 
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author, 1940)
> If we desire respect for the law, we must first make the law respectable.
>  - Louis D. Brandeis
> 

Re: problem with live usb booting

[Eddie]

On 4/11/24 10:14, Greg Wooledge wrote:

On Thu, Apr 11, 2024 at 01:30:46PM +, sarath wrote:

dear debian

I have created live usb with debian-live-12.5.0-amd64-standard.iso using tool 
Ventoy-1.0.95. When tried to booting it is ended with command line options. 
please help me to the next step


It's not clear to me what you mean.  Was there an *error* message?  If so,
what does it say?

If you simply mean "I expected a graphical interface, and instead I got
a text console login prompt", that's because you used the -standard image
which has a minimalist set of packages, equivalent to what you would get
if you installed Debian normally, and un-selected the desktop environment
option, and only left "Standard" selected.

If you want a graphical interface, you'll need a different image.



I agree with Greg - I use Ventoy/debian-live-12.2.0-amd64-xfce.iso and 
it works just fine in the xfce graphical interface. Use the desktop you 
prefer as part of the debian live iso for a graphical install.

Re: problem with live usb booting

[Greg Wooledge]

On Thu, Apr 11, 2024 at 01:30:46PM +, sarath wrote:
> dear debian
> 
> I have created live usb with debian-live-12.5.0-amd64-standard.iso using tool 
> Ventoy-1.0.95. When tried to booting it is ended with command line options. 
> please help me to the next step

It's not clear to me what you mean.  Was there an *error* message?  If so,
what does it say?

If you simply mean "I expected a graphical interface, and instead I got
a text console login prompt", that's because you used the -standard image
which has a minimalist set of packages, equivalent to what you would get
if you installed Debian normally, and un-selected the desktop environment
option, and only left "Standard" selected.

If you want a graphical interface, you'll need a different image.

problem with live usb booting

[sarath]

dear debian

I have created live usb with debian-live-12.5.0-amd64-standard.iso using tool 
Ventoy-1.0.95. When tried to booting it is ended with command line options. 
please help me to the next step

thanks regards
Sarathdc

Sent with [Proton Mail](https://proton.me/) secure email.

Problem booting the Debian machine [WAS Re: AW: su su- sudo dont work]

[Andrew M.A. Cater]

On Sat, Jan 20, 2024 at 02:30:43PM +, Schwibinger Michael wrote:
> Good afternoon
> I destroyed DEBIAN
> now 2 years agon.
> I asked here for help
> no solution.
> So every morning
> I interrupt booting
> change to rescue mode.
> 
> "Normal" booting does create panic.
> 
> Regards
> Sophie
> 
> PC
> accident happened after update to DEBIAN 11.
> 

Hi Sophie,

We are asking you questions because we can't see you, we can't see 
what you type, we need clear information.

It's like playing chess by post: every time we ask for details
on what you have - what has happened, how the pieces are laid
out - we get an "I have a chess problem" message.

In your reply, please try and answer each of the questions
written below *under* the question so it is clear. If you only have
a phone to reply, that's OK, but please reply to one question
at a time in that case.

Please try and keep to the subject of the message. I have changed
that to "Problem booting the machine" I expect your reply to be
something like AW: Problem booting the machine

First - and most important question - is this your only computer?

If so, I would not want to break it further but in order to fix it,
we will need more information.

Second question - is this the computer that you mail us from to this list
or are you using some other device to mail us?

Your reply above has given more information: this happened after
you upgraded from Debian 10 to Debian 11. 

Third question - Even if it's now more than two years ago: can you
remember whether the upgrade completed successfully?

Fourth question -Is it that when the computer starts - and you get a
(blue or green??) first screen with white writing, it lists 
several kernels to choose from?
 
Fifth question - If you have only one kernel listed, then under that may be
a "rescue" option - is that what you use to boot the machine every
day?

If so, then *what do you type* to get into the system: what commands?

Sixth question - One line may list the Debian 11 kernel version -
with 5.10 - or may list the Debian 10 kernel version - with 4.19
Which do you select  / which one works?

Thank you in advance for your replies

Andy
(amaca...@debian.org)
> 

> 

Re: Bug#1056998: cdrom: Installation media changes after booting it

[Nicholas Geovanis]

On Mon, Dec 4, 2023, 3:30 AM Thomas Schmitt  wrote:

> .
> This seems to indicate that the firmware has a stake in the problem ...
>
> > Both the Thinkpad E14 Gen 5s had the same specifications and type number,
> > differing only in that the one with corruption of the installer has 24GB
> of
> > memory (16GB installed in the slot, 8GB soldered) and the other only has
> 8GB
> > soldered. They both have the same BIOS version, R2AET32W(1.07).
>
> ... but the trigger would have to be very subtle.
>
> > This seems to be really interesting because the corruption only happened
> on
> > certain computers, and it would stay that way on repeated attempts.
>


FWIW check the BIOS L[123] cache settings and consider changing them to
more conservative "slower" values if possible. And you have different RAM
models and configurations, could there be one DIMM in the mix that is
running overclocked?

Have a nice day :)
>
> Thomas
>

Grüß Gott :-)

Re: /etc/resolv.conf changes every booting time

[songbird]

gene heskett wrote:
...
> I load up a file I want to 3d print in cura, slice it into gcode, click 
> on save to disk. kde gets in the way so it opens a tab on the toolbar at 
> the bottom of the screen and to continue I have to click on that tab. 
> 20% of the time the where do you want to save it requester pops up 
> instantly but 80% of the time the whole workspace freezes for 2 minutes. 
> Eventually the save requester pops up and life goes on at normal speeds 
> I have the thought that both occurrences are different exhibits of the 
> same access problem. But thats just a WAG. The commonality is both apps 
> are AppImages, and my /home is a raid.  Is there a connection? w/o logs, 
> how can I tell.  There are no "user" logs.

  as i may have said before.  whatever you have going on
with file saving and file system access may be getting
stomped all over by whatever settings you have in the KDE
desktop or the particular application.  so one thing i
would do for sure is make sure that the KDE desktop file
extension associations that may be turned on to do anything
automatically are turned off (until you resolve where the
issue actually resides).

  once you have the KDE desktop stuff turned off then you
can at least know it isn't that which is mucking you up.

  from there is it some other thing?  well, if it now 
works then you've solved it, and if it hasn't been solved
then you've at least eliminated one variable.

  from there if it still does not work then you are up 
against any automatic automounter crap (which i find a
PITA so i remove it or find ways to turn it off which
then gets through another layer of possible variables).

  after that you should be down to the applcation and
what settings it has for dealing with file and accesses
and again i turn off all automatic stuff i can there to
make sure exactly what i'm trying to do can get done with
minimal interference.

  since you have network stuff going on which i hardly
ever do and i also don't do bluethooth, samba, ssh, rpc 
(or plenty of other things) well then you're going to
have to wade through those things and see what each may 
let you do to narrow down where the issue is at.

  when you have a complicated system it may be well 
worth it to set up a blank slate new machine and put in
each layer and test it before adding the next to see
which step is going kerblooey.  if i'm running a 
production system this is a natural and common 
procedure for any upgrade and debugging.  gotta have a
way to do tests that doesn't shut down production.


  songbird

Re: /etc/resolv.conf changes every booting time

[songbird]

Eduardo M KALINOWSKI wrote:
...
> He just told you to not hijack threads, and there you go and your 
> immediate reply is to start talking about something completely unrelated 
> to the rest of the discussion.

  oops, sorry, i just replied again.


  songbird

Re: /etc/resolv.conf changes every booting time

[Eduardo M KALINOWSKI]

On 07/08/2023 23:45, gene heskett wrote:

On 8/7/23 21:47, Greg Wooledge wrote:

Start a new thread, and treat the problem seriously.  Show us the
commands you're running and their output.  Show us the relevant
parts of your configuration.

That particular problem has been solved, Greg, and 60 days later there's 
no way I can recreate all that.


There is at my age some considerable truth in the remark that I can't 
remember what I had for breakfast or if I even had any.  It might be 
funny to the younger folks here, until they can't recall it either...



Don't just tack it onto a different thread and make vague statements.
That won't solve anything.


Go back and look at me vs digikam. 

> [snip]

He just told you to not hijack threads, and there you go and your 
immediate reply is to start talking about something completely unrelated 
to the rest of the discussion.


--
If little else, the brain is an educational toy.
-- Tom Robbins

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: /etc/resolv.conf changes every booting time

[gene heskett]

On 8/7/23 21:47, Greg Wooledge wrote:

On Mon, Aug 07, 2023 at 09:03:47PM -0400, gene heskett wrote:

And I'm back
to hunting for the reason I can ping yahoo.com but not other machines on my
local net, that are fully identified in my hosts file or vice versa


Start a new thread, and treat the problem seriously.  Show us the
commands you're running and their output.  Show us the relevant
parts of your configuration.

That particular problem has been solved, Greg, and 60 days later there's 
no way I can recreate all that.


There is at my age some considerable truth in the remark that I can't 
remember what I had for breakfast or if I even had any.  It might be 
funny to the younger folks here, until they can't recall it either...



Don't just tack it onto a different thread and make vague statements.
That won't solve anything.


Go back and look at me vs digikam. No help here, no help there. All the 
clues and they are scant at best, the database can make its index files 
just fine which are on my raid, Digikam  can see every pix I've ever 
stored there, it can see every pix on the card in the camera, but when I 
ask it to download a pix from the camera, a jpg file, it winds up saying 
at the end without logging an error anyplace I've found, but claims the 
target directory selected to save the pix to, does not exist, when I can 
see it and its contents just fine in the other digikam window.


I load up a file I want to 3d print in cura, slice it into gcode, click 
on save to disk. kde gets in the way so it opens a tab on the toolbar at 
the bottom of the screen and to continue I have to click on that tab. 
20% of the time the where do you want to save it requester pops up 
instantly but 80% of the time the whole workspace freezes for 2 minutes. 
Eventually the save requester pops up and life goes on at normal speeds 
I have the thought that both occurrences are different exhibits of the 
same access problem. But thats just a WAG. The commonality is both apps 
are AppImages, and my /home is a raid.  Is there a connection? w/o logs, 
how can I tell.  There are no "user" logs.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: /etc/resolv.conf changes every booting time

[Greg Wooledge]

On Mon, Aug 07, 2023 at 09:03:47PM -0400, gene heskett wrote:
> And I'm back
> to hunting for the reason I can ping yahoo.com but not other machines on my
> local net, that are fully identified in my hosts file or vice versa

Start a new thread, and treat the problem seriously.  Show us the
commands you're running and their output.  Show us the relevant
parts of your configuration.

Don't just tack it onto a different thread and make vague statements.
That won't solve anything.

Re: /etc/resolv.conf changes every booting time

[gene heskett]

On 8/7/23 18:43, Brian wrote:

On Mon 07 Aug 2023 at 17:53:41 -0400, gene heskett wrote:


On 8/7/23 14:57, Brian wrote:

On Sun 06 Aug 2023 at 20:50:26 -0400, gene heskett wrote:

[...]


Sorry you are so offended by a hosts file user Andy, but when the guys


Did someone mention a hosts file? Is this an attempt to move discussion on
to a different toic? I thought 'chattr -i' and the wisdom of using it was
under discussion.


Its all related to networking.


A pathetic response.
  

My experience is that 'chattr -i' cripples the ability of my laptop to roam
on other networks.


I do not own a lappy.  The last one I had, an hp I paid about $1500 for, was
so poorly supported that when I went out someplace as a consulting engineer,
had to borrow a modem from the motel just to talk to their wifi about 50% of
the time. The rest of the time the wifi needed a reboot. Even windows xp
could not make the broadcom radio in it work. Its battery was as problematic
as the windows it came with, and when it died I tossed it. My expertise as a
broadcast consultant went out of date when the US went digital in mid-2008.
Now I just keep our local Ma and Pa daytimer on the air. I also don't have a
hell phone.


Even more pathetic. Taking one word (laptop) and making it central is typical
of your style of response. All me, me, me.

I don't recall being the 1st user of the word "laptop", what I am trying 
to prove is that linux is not windows, its far more versatile if you'll 
let it be, and that different people have different environments, I've 
been made to understand that resolv.conf is now not the place to put 
search order, that has now been moved to nssconfig.


There was once a stanza at the end of dhcpd.conf where one could setup 
his network by filling in the blanks and removing the # comments. If all 
else failed, that worked, But that was too easy so it was removed. And 
I'm back to hunting for the reason I can ping yahoo.com but not other 
machines on my local net, that are fully identified in my hosts file or 
vice versa. I've had it both ways in the last 3 major releases.


Consistency Brian, is what works best over the long haul for those to 
whom a computer is a tool to get a job done, not a plaything, and there 
does not seem to be any consistency.


Take care & stay well Brian.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: /etc/resolv.conf changes every booting time

[Brian]

On Mon 07 Aug 2023 at 17:53:41 -0400, gene heskett wrote:

> On 8/7/23 14:57, Brian wrote:
> > On Sun 06 Aug 2023 at 20:50:26 -0400, gene heskett wrote:
> > 
> > [...]
> > 
> > > Sorry you are so offended by a hosts file user Andy, but when the guys
> > 
> > Did someone mention a hosts file? Is this an attempt to move discussion on
> > to a different toic? I thought 'chattr -i' and the wisdom of using it was
> > under discussion.
> > 
> Its all related to networking.

A pathetic response.
 
> > My experience is that 'chattr -i' cripples the ability of my laptop to roam
> > on other networks.
> > 
> I do not own a lappy.  The last one I had, an hp I paid about $1500 for, was
> so poorly supported that when I went out someplace as a consulting engineer,
> had to borrow a modem from the motel just to talk to their wifi about 50% of
> the time. The rest of the time the wifi needed a reboot. Even windows xp
> could not make the broadcom radio in it work. Its battery was as problematic
> as the windows it came with, and when it died I tossed it. My expertise as a
> broadcast consultant went out of date when the US went digital in mid-2008.
> Now I just keep our local Ma and Pa daytimer on the air. I also don't have a
> hell phone.

Even more pathetic. Taking one word (laptop) and making it central is typical
of your style of response. All me, me, me.

-- 
Brian.

Re: /etc/resolv.conf changes every booting time

[gene heskett]

On 8/7/23 14:57, Brian wrote:

On Sun 06 Aug 2023 at 20:50:26 -0400, gene heskett wrote:

[...]


Sorry you are so offended by a hosts file user Andy, but when the guys


Did someone mention a hosts file? Is this an attempt to move discussion on
to a different toic? I thought 'chattr -i' and the wisdom of using it was
under discussion.


Its all related to networking.


My experience is that 'chattr -i' cripples the ability of my laptop to roam
on other networks.

I do not own a lappy.  The last one I had, an hp I paid about $1500 for, 
was so poorly supported that when I went out someplace as a consulting 
engineer, had to borrow a modem from the motel just to talk to their 
wifi about 50% of the time. The rest of the time the wifi needed a 
reboot. Even windows xp could not make the broadcom radio in it work. 
Its battery was as problematic as the windows it came with, and when it 
died I tossed it. My expertise as a broadcast consultant went out of 
date when the US went digital in mid-2008.   Now I just keep our local 
Ma and Pa daytimer on the air. I also don't have a hell phone.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: /etc/resolv.conf changes every booting time

[Andy Smith]

Hi Brian,

On Mon, Aug 07, 2023 at 07:57:07PM +0100, Brian wrote:
> On Sun 06 Aug 2023 at 20:50:26 -0400, gene heskett wrote:
> > Sorry you are so offended by a hosts file user Andy, but when the guys
> 
> Did someone mention a hosts file?

If I understand correctly, Gene identifies himself as "a hosts file
user" and one of his major delusions is that there is some
conspiracy within the Debian-like world to make the life of people
who make use of /etc/hosts very hard. One of the ways, in this
delusion, that it is made hard is by "forcing everyone to use a DHCP
server", which also leads to Gene's resolv.conf being modified,
which Gene does not like and uses the immutable file approach to
prevent.

I think since I have criticised the immutable resolv.conf "solution",
Gene has decided I must be part of this wide-ranging conspiracy and
so I must be offended that he *also* uses hosts files. That is, he's
saying I am offended by "a hosts file user", i.e. him and by
extension what he does, not offended by "a hosts file". It did take
me some effort to parse.

That is my best guess at how this particular one of Gene's bizarre
rants even tangentially connects with reality as I know it, anyway.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: /etc/resolv.conf changes every booting time

[Brian]

On Sun 06 Aug 2023 at 20:50:26 -0400, gene heskett wrote:

[...]

> Sorry you are so offended by a hosts file user Andy, but when the guys

Did someone mention a hosts file? Is this an attempt to move discussion on
to a different toic? I thought 'chattr -i' and the wisdom of using it was
under discussion.

My experience is that 'chattr -i' cripples the ability of my laptop to roam
on other networks.

-- 
Brian.

Re: /etc/resolv.conf changes every booting time

[tomas]

On Sun, Aug 06, 2023 at 08:50:26PM -0400, gene heskett wrote:

> Sorry you are so offended by a hosts file user Andy [...]

Now this is stuff for Quote of the Day ;-)

Thank you, Gene.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: /etc/resolv.conf changes every booting time

[gene heskett]

On 8/6/23 12:09, Andy Smith wrote:

Hello,

On Sun, Aug 06, 2023 at 07:37:35PM +0800, Jon Smart wrote:

Timothy M Butterworth wrote:
The file /etc.resolv.conf is just a soft link.

You need to:

1: Delete /etc/resolv.conf - rm /etc/resolv.conf
2: Create a new /etc/resolv.conf file: touch /etc/resolv.conf
3: Configure you nameservers
4: Make the file immutable: chattr +i /etc/resolv.conf


These 4 steps do work great!
Thanks a lot.


And so another one fails to spend the time to work out how their
operating system works for trivial minutiae like "how my network
gets set up", leaving a nice rake in the grass for some point in the
future when they are trying to debug something else. 🙁

And we wonder why this list ends up dealing with the aftermath of
the Gene school of "don't understand it? Hit it with chattr +i / rm
/ apt-get purge!" so often.

Regards,
Andy

Sorry you are so offended by a hosts file user Andy, but when the guys 
decide to do networking differently, usually in the badly mistaken idea 
that everybody runs a dhcpd server even for their isolated local 
network, and don't check that their brainless changes don't screw up a 
host file based local network, or worse, don't care if it does, then you 
should expect that we WILL do what WE KNOW JUST WORKS.  Blaming me in 
that case is just plain poor form.  If there indeed IS a better way to 
deal with this in a hosts file system, then teach us /how/ WITHOUT 
ASSUMING we'll just run a dhcpd server with all the configuration sand 
maintenance bs that entails. Tain't gonna happen.


We hide our local stuff behind something like dd-wrt and its ilk for a 
reason.  As a guard dog, its an 800 lb pit bull with a very bad attitude.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: /etc/resolv.conf changes every booting time

[Jon Smart]

> On Sun, Aug 06, 2023 at 05:17:23PM +0800, Jon Smart wrote:
>> It's a VPS provided by a local ISP. The VPS has a static IPv4.
>> Do you know how to know if /etc/resolv.conf is modified by dhcp?
>
> The first thing you could do is check whether a DHCP client daemon
> is running.  That's usually a sign.
>
> Failing that, find out what your primary network interface's name is,
> and then find out how that network interface is brought up.  In a server
> configuration, it's *usually* brought up by a stanza in the
> /etc/network/interfaces file.  If that stanza consists of a line
> ending with "dhcp", then voila.
>
> If the primary network interface is not configured in /e/n/i then the
> second most likely configuration is NetworkManager.  Usually if NM
> is in the picture, /etc/resolv.conf will be a symlink, and you will
> see evidence of NM both in the symlink's target, and in the contents
> of the file.  Thus,
>
> ls -ld /etc/resolv.conf
> cat /etc/resolv.conf
>
> Both of these should give you hints, if NM is involved.
>
>

Yes my system is exactly using NM for networking. so resolv.conf is just a
symlink. I delete that symlink and create a real file, put content into it
(no chattr needed), and reboot the OS everything works fine now.

regards.

Re: /etc/resolv.conf changes every booting time

[tomas]

On Sun, Aug 06, 2023 at 04:09:14PM +, Andy Smith wrote:

[...]

> And we wonder why this list ends up dealing with the aftermath of
> the Gene school of "don't understand it? Hit it with chattr +i / rm
> / apt-get purge!" so often.

I must admit that I was one of those proposing chattr +i in this
context (it feels like half to one decade ago). To my defense, I
said then (and repeat now) that I don't recommend it as a permanent
fix, rather as a debugging tool. The next step would be to go to
the logs and see which software is complaining. Then you know which
man pages to hit :-)

Leaving "chattr +i" behind in /etc at random spots will come back
to shoot you painfully in the foot (e.g. at the next system upgrade,
when you'll have forgotten about it).

If the sysadmin is me, I'll just leave it for as long as the single
debugging session lasts.

Then you'll [1] come here, whining ;-)

Cheers

[1] No, not you, Andy. This was more the generic "you" :-)

-- 
tomás


signature.asc
Description: PGP signature

Re: /etc/resolv.conf changes every booting time

[Andy Smith]

Hi Greg,

On Sun, Aug 06, 2023 at 08:48:25AM -0400, Greg Wooledge wrote:
> On Sun, Aug 06, 2023 at 07:37:35PM +0800, Jon Smart wrote:
> > These 4 steps do work great!
> > Thanks a lot.
> 
> These same steps are also on the wiki page that's been discussed many
> times in this thread.  You might want to read what the wiki has to
> say about it, especially about /etc filling up with temporary files.
> 
> They're also the same steps that someone else in this thread has
> criticized.  Again.  As you can see, some people simply *despise* this,
> despite how simple and effective it is.

So you honestly do not see a problem with how this has played out,
despite your tone in the preceding paragraph where you seem
exasperated that Jon has not taken the time to understand the
problem or read any of the documentation or basically do anything
that involves effort on their part?

I'm surprised I need to clarify this, but I'm not disappointed
because Jon chose to make a file immutable, I'm disappointed because
Jon leapt at the option that involved pasting some commands in
without understanding them or what is actually going on with their
machine. And not purely because I think Jon ought to understand
these things as some pure ideal state of being, but objectively
because when Jon hits any sort of networking problem in future, Jon
will STILL have no idea how their network is actually set up. Which
is astonishing for someone wanting to run a server. And this
attitude will be applied to other parts of the system. And this list
will see Jon or someone like them again very soon and be asked to
unpick this behaviour.

Here I think chattr +i is a useful tool that should be used to reach
a state of understanding if necessary, not an actual fix. I agree
that it belongs at the bottom of documentation and couched with
caveats, not handed out as a "just do this". That's very sad to see.
And even sadder to see promoted as the "solution".

Cheers,
Andy
> 

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: /etc/resolv.conf changes every booting time

[Andy Smith]

Hello,

On Sun, Aug 06, 2023 at 07:37:35PM +0800, Jon Smart wrote:
> > Timothy M Butterworth wrote:
> > The file /etc.resolv.conf is just a soft link.
> >
> > You need to:
> >
> > 1: Delete /etc/resolv.conf - rm /etc/resolv.conf
> > 2: Create a new /etc/resolv.conf file: touch /etc/resolv.conf
> > 3: Configure you nameservers
> > 4: Make the file immutable: chattr +i /etc/resolv.conf
> 
> These 4 steps do work great!
> Thanks a lot.

And so another one fails to spend the time to work out how their
operating system works for trivial minutiae like "how my network
gets set up", leaving a nice rake in the grass for some point in the
future when they are trying to debug something else. 🙁

And we wonder why this list ends up dealing with the aftermath of
the Gene school of "don't understand it? Hit it with chattr +i / rm
/ apt-get purge!" so often.

Regards,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: /etc/resolv.conf changes every booting time

[tomas]

On Sun, Aug 06, 2023 at 07:06:01AM -0400, Timothy M Butterworth wrote:
> On Sun, Aug 6, 2023 at 6:13 AM Jon Smart  wrote:
> 
> > It's a VPS provided by a local ISP. The VPS has a static IPv4.
> > Do you know how to know if /etc/resolv.conf is modified by dhcp?
> >
> > Thanks.
> >
> >
> > >
> > > Hi Jon,
> > >
> > >> I have removed the default systemd-resolved local dns service following
> > >> the link below,
> > >>
> > >>
> > https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
> > >>
> > >> And I have unbound installed and enabled as local DNS server.
> > >>
> > >> But every time I reboot the server, the configuration file
> > >> /etc/resolv.conf changes to a default one. So every time I have to
> > >> update
> > >> its content to:
> > >>
> > >> nameserver 127.0.0.1
> >
> The file /etc.resolv.conf is just a soft link.

Not always, so please make sure it is /before/ you follow the
steps below.

> You need to:
> 
> 1: Delete /etc/resolv.conf - rm /etc/resolv.conf
> 2: Create a new /etc/resolv.conf file: touch /etc/resolv.conf
> 3: Configure you nameservers
> 4: Make the file immutable: chattr +i /etc/resolv.conf

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: /etc/resolv.conf changes every booting time

[Greg Wooledge]

On Sun, Aug 06, 2023 at 05:17:23PM +0800, Jon Smart wrote:
> It's a VPS provided by a local ISP. The VPS has a static IPv4.
> Do you know how to know if /etc/resolv.conf is modified by dhcp?

The first thing you could do is check whether a DHCP client daemon
is running.  That's usually a sign.

Failing that, find out what your primary network interface's name is,
and then find out how that network interface is brought up.  In a server
configuration, it's *usually* brought up by a stanza in the
/etc/network/interfaces file.  If that stanza consists of a line
ending with "dhcp", then voila.

If the primary network interface is not configured in /e/n/i then the
second most likely configuration is NetworkManager.  Usually if NM
is in the picture, /etc/resolv.conf will be a symlink, and you will
see evidence of NM both in the symlink's target, and in the contents
of the file.  Thus,

ls -ld /etc/resolv.conf
cat /etc/resolv.conf

Both of these should give you hints, if NM is involved.

Re: /etc/resolv.conf changes every booting time

[Greg Wooledge]

On Sun, Aug 06, 2023 at 07:37:35PM +0800, Jon Smart wrote:
> Unattributed:
> > The file /etc.resolv.conf is just a soft link.

Not always.

> > You need to:
> >
> > 1: Delete /etc/resolv.conf - rm /etc/resolv.conf
> > 2: Create a new /etc/resolv.conf file: touch /etc/resolv.conf
> > 3: Configure you nameservers
> > 4: Make the file immutable: chattr +i /etc/resolv.conf
> >
> 
> These 4 steps do work great!
> Thanks a lot.

These same steps are also on the wiki page that's been discussed many
times in this thread.  You might want to read what the wiki has to
say about it, especially about /etc filling up with temporary files.

They're also the same steps that someone else in this thread has
criticized.  Again.  As you can see, some people simply *despise* this,
despite how simple and effective it is.

Re: /etc/resolv.conf changes every booting time

[Eduardo M KALINOWSKI]

On 06/08/2023 00:26, Greg Wooledge wrote:

I'm also forced to relegate the chattr solution to the end of the page,
and couch it in caveats, because some people think that it's wrong.
They can't say WHY it's wrong, of course.  Maybe because it's too simple
and effective.  I dunno.


How about the fact that it just solves the symptom but not the real problem?

/etc/resolv.conf does not change by itself, some tool must be making the 
(possibly undesired) changes, so in most cases, I'd say it's better to 
configure that tool to stop changing resolv.conf, or to add the 
nameservers you want instead of whatever the tool auto discovers. Or 
perhaps you don't even need that tool (in a server with static IP, for 
example).


I'm not saying that chattr +i should never be used, but it should be the 
last resort, and the user should know what they're doing and possible 
consequences.



--
The idle man does not know what it is to enjoy rest.

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: /etc/resolv.conf changes every booting time

[Jon Smart]

> On Sun, Aug 6, 2023 at 6:13 AM Jon Smart  wrote:
>
>> It's a VPS provided by a local ISP. The VPS has a static IPv4.
>> Do you know how to know if /etc/resolv.conf is modified by dhcp?
>>
>> Thanks.
>>
>>
>> >
>> > Hi Jon,
>> >
>> >> I have removed the default systemd-resolved local dns service
>> following
>> >> the link below,
>> >>
>> >>
>> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
>> >>
>> >> And I have unbound installed and enabled as local DNS server.
>> >>
>> >> But every time I reboot the server, the configuration file
>> >> /etc/resolv.conf changes to a default one. So every time I have to
>> >> update
>> >> its content to:
>> >>
>> >> nameserver 127.0.0.1
>>
> The file /etc.resolv.conf is just a soft link.
>
> You need to:
>
> 1: Delete /etc/resolv.conf - rm /etc/resolv.conf
> 2: Create a new /etc/resolv.conf file: touch /etc/resolv.conf
> 3: Configure you nameservers
> 4: Make the file immutable: chattr +i /etc/resolv.conf
>

These 4 steps do work great!
Thanks a lot.

regards.

Re: /etc/resolv.conf changes every booting time

[Timothy M Butterworth]

On Sun, Aug 6, 2023 at 6:13 AM Jon Smart  wrote:

> It's a VPS provided by a local ISP. The VPS has a static IPv4.
> Do you know how to know if /etc/resolv.conf is modified by dhcp?
>
> Thanks.
>
>
> >
> > Hi Jon,
> >
> >> I have removed the default systemd-resolved local dns service following
> >> the link below,
> >>
> >>
> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
> >>
> >> And I have unbound installed and enabled as local DNS server.
> >>
> >> But every time I reboot the server, the configuration file
> >> /etc/resolv.conf changes to a default one. So every time I have to
> >> update
> >> its content to:
> >>
> >> nameserver 127.0.0.1
>
The file /etc.resolv.conf is just a soft link.

You need to:

1: Delete /etc/resolv.conf - rm /etc/resolv.conf
2: Create a new /etc/resolv.conf file: touch /etc/resolv.conf
3: Configure you nameservers
4: Make the file immutable: chattr +i /etc/resolv.conf


> >>
> >> (points to unbound)
> >>
> >> How to stop the auto-changes to /etc/resolv.conf after rebooting?
> >
> > In case you get the configuration overwritten by DHCP you can avoid that
> > by the following lines in /etc/dhcp/dhclient.conf.
> >
> > interface "bond0" {
> > supersede domain-name-servers 127.0.0.1;
> > }
> >
> > Just replace the interface name with yours.
> >
> > Kind regards,
> > Christoph
> > --
> > Ist die Katze gesund
> > schmeckt sie dem Hund.
> >
>
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀c

Re: /etc/resolv.conf changes every booting time

[Christoph Brinkhaus]

Am Sun, Aug 06, 2023 at 05:17:23PM +0800 schrieb Jon Smart:
Hi Jon,
> It's a VPS provided by a local ISP. The VPS has a static IPv4.
> Do you know how to know if /etc/resolv.conf is modified by dhcp?
> 
I am not sure about the details. But with DHCP a bunch of network
configuration items can be send from the server to the client. The
nameserver configuration is one of the items.

Kind regards,
Christoph
> 
> >
> > Hi Jon,
> >
> >> I have removed the default systemd-resolved local dns service following
> >> the link below,
> >>
> >> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
> >>
> >> And I have unbound installed and enabled as local DNS server.
> >>
> >> But every time I reboot the server, the configuration file
> >> /etc/resolv.conf changes to a default one. So every time I have to
> >> update
> >> its content to:
> >>
> >> nameserver 127.0.0.1
> >>
> >> (points to unbound)
> >>
> >> How to stop the auto-changes to /etc/resolv.conf after rebooting?
> >
> > In case you get the configuration overwritten by DHCP you can avoid that
> > by the following lines in /etc/dhcp/dhclient.conf.
> >
> > interface "bond0" {
> > supersede domain-name-servers 127.0.0.1;
> > }
> >
> > Just replace the interface name with yours.
> >
> > Kind regards,
> > Christoph
> > --
> > Ist die Katze gesund
> > schmeckt sie dem Hund.
> >
> 
> 

-- 
Ist die Katze gesund
schmeckt sie dem Hund.


signature.asc
Description: PGP signature

Re: /etc/resolv.conf changes every booting time

[Jon Smart]

It's a VPS provided by a local ISP. The VPS has a static IPv4.
Do you know how to know if /etc/resolv.conf is modified by dhcp?

Thanks.


>
> Hi Jon,
>
>> I have removed the default systemd-resolved local dns service following
>> the link below,
>>
>> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
>>
>> And I have unbound installed and enabled as local DNS server.
>>
>> But every time I reboot the server, the configuration file
>> /etc/resolv.conf changes to a default one. So every time I have to
>> update
>> its content to:
>>
>> nameserver 127.0.0.1
>>
>> (points to unbound)
>>
>> How to stop the auto-changes to /etc/resolv.conf after rebooting?
>
> In case you get the configuration overwritten by DHCP you can avoid that
> by the following lines in /etc/dhcp/dhclient.conf.
>
> interface "bond0" {
> supersede domain-name-servers 127.0.0.1;
> }
>
> Just replace the interface name with yours.
>
> Kind regards,
> Christoph
> --
> Ist die Katze gesund
> schmeckt sie dem Hund.
>

Re: /etc/resolv.conf changes every booting time

[Christoph Brinkhaus]

Am Sun, Aug 06, 2023 at 09:28:55AM +0800 schrieb Jon Smart:

Hi Jon,

> I have removed the default systemd-resolved local dns service following
> the link below,
> 
> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
> 
> And I have unbound installed and enabled as local DNS server.
> 
> But every time I reboot the server, the configuration file
> /etc/resolv.conf changes to a default one. So every time I have to update
> its content to:
> 
> nameserver 127.0.0.1
> 
> (points to unbound)
> 
> How to stop the auto-changes to /etc/resolv.conf after rebooting?

In case you get the configuration overwritten by DHCP you can avoid that
by the following lines in /etc/dhcp/dhclient.conf.

interface "bond0" {
supersede domain-name-servers 127.0.0.1;
}

Just replace the interface name with yours.

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.


signature.asc
Description: PGP signature

Re: /etc/resolv.conf changes every booting time

[Greg Wooledge]

On Sat, Aug 05, 2023 at 10:52:35PM -0500, Nicholas Geovanis wrote:
> On Sat, Aug 5, 2023, 10:27 PM Greg Wooledge  wrote:
> 
> > On Sat, Aug 05, 2023 at 10:05:31PM -0500, Nicholas Geovanis wrote:
> > > On Sat, Aug 5, 2023, 9:13 PM Greg Wooledge  wrote:
> > >
> > > > On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> > > > > How to stop the auto-changes to /etc/resolv.conf after rebooting?
> > > >
> > > > https://wiki.debian.org/resolv.conf
> > > >
> > >
> > > Contrary to what that page states, auto changes to resolv.conf are never
> > > appropriate in the server environment. The statement there that it works
> > > fine in a "properly configured server" is the boilerplate escape hatch
> > for
> > > that inconvenient fact :-)
> >
> > Those words do not appear on that page.  I don't know which sentence(s)
> > you're actually referring to.
> 
> 
> I'm referring to these exact words:
> "It also works well for many desktop and server systems, so long as the
> network infrastructure is perfect."
> 
> Its a red herring because the DNS infrastructure in a data center is static
> at the IP address and host name level. And I feel certain that any network
> infrastructure constructed by humans is imperfect to some degree.
> There's their escape hatch.

Not all Debian systems are in a "data center".  Sometimes they're on a
home network, or a workplace network.  In both of those environments,
the DHCP server may be questionable -- either because it's being provided
by a cheap router (home), or because it's being managed by a different
department (workplace).

Some workplaces require the use of DHCP to configure network interfaces,
even when the DHCP server behaves in a way you do not wish.  For example,
it may offer DNS nameservers that are not the ones you want to use.  So,
many of us are running Debian systems where the IP address has to come
from DHCP, for political reasons, but the DNS servers that would come
from DHCP are *undesired*.

Therefore, we want to edit /etc/resolv.conf ourselves, and not let the
DHCP client daemon, or any other program, change it.

Therefore, this wiki page.

Do you have a specific wording change you'd like to see?

Is there any part of the page that is actually *incorrect*?

Are there any alternative solutions that are *missing*?

Re: /etc/resolv.conf changes every booting time

[Nicholas Geovanis]

On Sat, Aug 5, 2023, 10:27 PM Greg Wooledge  wrote:

> On Sat, Aug 05, 2023 at 10:05:31PM -0500, Nicholas Geovanis wrote:
> > On Sat, Aug 5, 2023, 9:13 PM Greg Wooledge  wrote:
> >
> > > On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> > > > How to stop the auto-changes to /etc/resolv.conf after rebooting?
> > >
> > > https://wiki.debian.org/resolv.conf
> > >
> >
> > Contrary to what that page states, auto changes to resolv.conf are never
> > appropriate in the server environment. The statement there that it works
> > fine in a "properly configured server" is the boilerplate escape hatch
> for
> > that inconvenient fact :-)
>
> Those words do not appear on that page.  I don't know which sentence(s)
> you're actually referring to.


I'm referring to these exact words:
"It also works well for many desktop and server systems, so long as the
network infrastructure is perfect."

Its a red herring because the DNS infrastructure in a data center is static
at the IP address and host name level. And I feel certain that any network
infrastructure constructed by humans is imperfect to some degree.
There's their escape hatch.

The closest thing I see there is "so
> long as the network infrastructure is perfect", which refers to the DHCP
> server, not the Debian system.
>
> A lot of us run Debian systems on networks where we DO NOT CONTROL the
> DHCP server, and have to work around it.  That's what the introduction
> of the page is talking about.
>
> In any case, appeasing EVERY reader is impossible.  I have to use vague
> wording to try to make sure nobody is offended that their personal
> preference configuration is not snubbed.  No matter how utterly batshit
> insane such a configuration may be from my point of view.
>
> I'm also forced to relegate the chattr solution to the end of the page,
> and couch it in caveats, because some people think that it's wrong.
> They can't say WHY it's wrong, of course.  Maybe because it's too simple
> and effective.  I dunno.
>
> People are horrible sometimes.
>
> With all that in mind, and considering that this is a WIKI and you may
> edit it your damned SELF if you disagree with the content, what is your
> actual disagreement?
>
>

Re: /etc/resolv.conf changes every booting time

[Greg Wooledge]

On Sat, Aug 05, 2023 at 10:05:31PM -0500, Nicholas Geovanis wrote:
> On Sat, Aug 5, 2023, 9:13 PM Greg Wooledge  wrote:
> 
> > On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> > > How to stop the auto-changes to /etc/resolv.conf after rebooting?
> >
> > https://wiki.debian.org/resolv.conf
> >
> 
> Contrary to what that page states, auto changes to resolv.conf are never
> appropriate in the server environment. The statement there that it works
> fine in a "properly configured server" is the boilerplate escape hatch for
> that inconvenient fact :-)

Those words do not appear on that page.  I don't know which sentence(s)
you're actually referring to.  The closest thing I see there is "so
long as the network infrastructure is perfect", which refers to the DHCP
server, not the Debian system.

A lot of us run Debian systems on networks where we DO NOT CONTROL the
DHCP server, and have to work around it.  That's what the introduction
of the page is talking about.

In any case, appeasing EVERY reader is impossible.  I have to use vague
wording to try to make sure nobody is offended that their personal
preference configuration is not snubbed.  No matter how utterly batshit
insane such a configuration may be from my point of view.

I'm also forced to relegate the chattr solution to the end of the page,
and couch it in caveats, because some people think that it's wrong.
They can't say WHY it's wrong, of course.  Maybe because it's too simple
and effective.  I dunno.

People are horrible sometimes.

With all that in mind, and considering that this is a WIKI and you may
edit it your damned SELF if you disagree with the content, what is your
actual disagreement?

Re: /etc/resolv.conf changes every booting time

[Nicholas Geovanis]

On Sat, Aug 5, 2023, 9:13 PM Greg Wooledge  wrote:

> On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> > How to stop the auto-changes to /etc/resolv.conf after rebooting?
>
> https://wiki.debian.org/resolv.conf
>

Contrary to what that page states, auto changes to resolv.conf are never
appropriate in the server environment. The statement there that it works
fine in a "properly configured server" is the boilerplate escape hatch for
that inconvenient fact :-)

Re: /etc/resolv.conf changes every booting time

[Greg Wooledge]

On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> How to stop the auto-changes to /etc/resolv.conf after rebooting?

https://wiki.debian.org/resolv.conf

Re: /etc/resolv.conf changes every booting time

[jeremy ardley]

On 6/8/23 09:28, Jon Smart wrote:

Hello

I have removed the default systemd-resolved local dns service following
the link below,

https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu

And I have unbound installed and enabled as local DNS server.

But every time I reboot the server, the configuration file
/etc/resolv.conf changes to a default one. So every time I have to update
its content to:

nameserver 127.0.0.1

(points to unbound)

How to stop the auto-changes to /etc/resolv.conf after rebooting?

Thanks.



What is the new contents of /etc/resolv.conf?

If it mentions NetworkManager then that is the cause of your problems 
and you will have to follow web instructions to change NetworkManager 
behaviour.

/etc/resolv.conf changes every booting time

[Jon Smart]

Hello

I have removed the default systemd-resolved local dns service following
the link below,

https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu

And I have unbound installed and enabled as local DNS server.

But every time I reboot the server, the configuration file
/etc/resolv.conf changes to a default one. So every time I have to update
its content to:

nameserver 127.0.0.1

(points to unbound)

How to stop the auto-changes to /etc/resolv.conf after rebooting?

Thanks.

Re: Please help with not booting from USB so to install Debian

[Bret Busby]

On 10/6/23 00:22, Bret Busby wrote:

On 10/6/23 00:05, Bret Busby wrote:

On 9/6/23 23:34, Bret Busby wrote:

On 9/6/23 18:43, Rodolfo Medina wrote:

Rodolfo Medina  writes:

I want to install Debian on a new machine but don't manage to boot 
from USB
stick.  (I can do so regularly with another machine, so the USB 
stick is ok
and so is the Debian netinst I burned onto it.)  At the boot I 
press F9 and a
menu appears where I can choose to boot from USB stick; but then it 
doesn't

so at all booting instead into Windows 11.  In BIOS I enabled the CSM
protocol but nothing.  Please help as I don't know what to do: thanks.



Now I tried with a CDROM instead of a USB stick but the problem 
remains.


Rodolfo



I asked before, and have not seen an answer.

Have you gone into the UEFI/BIOS, and turned off secure booting?

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..


You might want to read this;

https://lists.ubuntu.com/archives/ubuntu-users/2023-June/310491.html

and, of course, after that procedure, in the system UEFI/BIOS, change 
the boot order to


USB drive
Optical (eg, DVD) drive (if the computer has one)
HDD

so that the computer should attempt to boot from the respective 
drives, in that order.




It occurred to me, after posting the above message, that I should have 
worded that last part, slightly differently, for clarification; the

"and, of course, after that procedure, in the system UEFI/BIOS, change
  the boot order to"

should have been

"and, of course, in that procedure, while still in the system UEFI/BIOS, 
between steps 2 and 3, change the boot order to".


I hope that all of this, is helpful, and, credit for success, should go 
to Liam.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

In this, since I last posted, I remembered that, on one of my computers, 
on which I installed Linux Mint, whilst the BIOS was set to boot first 
from the USB input, it would not, so, I simply wrote a copy of the iso 
file to a DVD, and, booted from the DVD drive, and, installed from the 
DVD drive, without any problem.


If the original poster has not yet been able to boot into a Linux iso 
file from the USB input, perhaps, providing the computer does have a DVD 
drive, the original poster could try the DVD method, and, tell us how 
successful that is.



..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: Please help with not booting from USB so to install Debian

[Hans]

Am Freitag, 9. Juni 2023, 18:37:14 CEST schrieb Stefan Monnier:
Hi Stefan,

this might e a problem of your BIOS. However, if your BIOS does not support 
booting from USB, 
here is a trick:

You can download a bootable CD-Rom from this site:

https://www.plop.at[1]

Look for the Bootmgr. It is a live-cd., which is booting, then you can chose 
further boot from 
another media like USB.

It helps, whenever your BIOS does not have the capability (i.e. it is too old), 
to boot from USB.

Hope this helps.

Good luck!

Best 

Hans


> > I want to install Debian on a new machine but don't manage to boot
> > from USB stick.  (I can do so regularly with another machine, so the
> > USB stick is ok and so is the Debian netinst I burned onto it.)  At
> > the boot I press F9 and a menu appears where I can choose to boot from
> > USB stick; but then it doesn't so at all booting instead into Windows
> > 11.  In BIOS I enabled the CSM protocol but nothing.  Please help as
> > I don't know what to do: thanks.
> 
> I don't have experience with your specific problem and after reading the
> rest of the thread, I'm not sure what might be the problem or how to fix
> it, but faced with this, I think I'd try to open the machine up and
> remove the "disk" to which it boots (i.e. the one with Window-11 on it).
> 
> Not sure it would fix the problem, but if not I'd hope it might give
> further hints.
> 
> 
> Stefan




[1] https://www.plop.at

Re: Please help with not booting from USB so to install Debian

[Peter Ehlert]

On 6/8/23 11:36, Rodolfo Medina wrote:

I want to install Debian on a new machine but don't manage to boot from USB
stick.  (I can do so regularly with another machine, so the USB stick is ok and
so is the Debian netinst I burned onto it.)  At the boot I press F9 and a menu
appears where I can choose to boot from USB stick; but then it doesn't so at all
booting instead into Windows 11.  In BIOS I enabled the CSM protocol but
nothing.  Please help as I don't know what to do: thanks.

Rodolfo


(after reading the other comments)

I recently had a similar issue with a HP 840G3 laptop

after editing the BIOS to disable secure boot and setting the boot order 
no joy.


I discovered that holding down F9 and then pressing the power button it 
goes directly into BIOS boot menu.

THEN selecting the USB drive from the list it works.


maybe your laptop has some such direct boot path option
best of luck

Re: Please help with not booting from USB so to install Debian

[Stefan Monnier]

> I want to install Debian on a new machine but don't manage to boot
> from USB stick.  (I can do so regularly with another machine, so the
> USB stick is ok and so is the Debian netinst I burned onto it.)  At
> the boot I press F9 and a menu appears where I can choose to boot from
> USB stick; but then it doesn't so at all booting instead into Windows
> 11.  In BIOS I enabled the CSM protocol but nothing.  Please help as
> I don't know what to do: thanks.

I don't have experience with your specific problem and after reading the
rest of the thread, I'm not sure what might be the problem or how to fix
it, but faced with this, I think I'd try to open the machine up and
remove the "disk" to which it boots (i.e. the one with Window-11 on it).

Not sure it would fix the problem, but if not I'd hope it might give
further hints.


Stefan

Re: Please help with not booting from USB so to install Debian

[Bret Busby]

On 9/6/23 23:34, Bret Busby wrote:

On 9/6/23 18:43, Rodolfo Medina wrote:

Rodolfo Medina  writes:

I want to install Debian on a new machine but don't manage to boot 
from USB
stick.  (I can do so regularly with another machine, so the USB stick 
is ok
and so is the Debian netinst I burned onto it.)  At the boot I press 
F9 and a
menu appears where I can choose to boot from USB stick; but then it 
doesn't

so at all booting instead into Windows 11.  In BIOS I enabled the CSM
protocol but nothing.  Please help as I don't know what to do: thanks.



Now I tried with a CDROM instead of a USB stick but the problem remains.

Rodolfo



I asked before, and have not seen an answer.

Have you gone into the UEFI/BIOS, and turned off secure booting?

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..


You might want to read this;

https://lists.ubuntu.com/archives/ubuntu-users/2023-June/310491.html

and, of course, after that procedure, in the system UEFI/BIOS, change 
the boot order to


USB drive
Optical (eg, DVD) drive (if the computer has one)
HDD

so that the computer should attempt to boot from the respective drives, 
in that order.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: Please help with not booting from USB so to install Debian

[Bret Busby]

On 10/6/23 00:05, Bret Busby wrote:

On 9/6/23 23:34, Bret Busby wrote:

On 9/6/23 18:43, Rodolfo Medina wrote:

Rodolfo Medina  writes:

I want to install Debian on a new machine but don't manage to boot 
from USB
stick.  (I can do so regularly with another machine, so the USB 
stick is ok
and so is the Debian netinst I burned onto it.)  At the boot I press 
F9 and a
menu appears where I can choose to boot from USB stick; but then it 
doesn't

so at all booting instead into Windows 11.  In BIOS I enabled the CSM
protocol but nothing.  Please help as I don't know what to do: thanks.



Now I tried with a CDROM instead of a USB stick but the problem remains.

Rodolfo



I asked before, and have not seen an answer.

Have you gone into the UEFI/BIOS, and turned off secure booting?

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..


You might want to read this;

https://lists.ubuntu.com/archives/ubuntu-users/2023-June/310491.html

and, of course, after that procedure, in the system UEFI/BIOS, change 
the boot order to


USB drive
Optical (eg, DVD) drive (if the computer has one)
HDD

so that the computer should attempt to boot from the respective drives, 
in that order.




It occurred to me, after posting the above message, that I should have 
worded that last part, slightly differently, for clarification; the

"and, of course, after that procedure, in the system UEFI/BIOS, change
 the boot order to"

should have been

"and, of course, in that procedure, while still in the system UEFI/BIOS, 
between steps 2 and 3, change the boot order to".


I hope that all of this, is helpful, and, credit for success, should go 
to Liam.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: Please help with not booting from USB so to install Debian

[Bret Busby]

On 9/6/23 18:43, Rodolfo Medina wrote:

Rodolfo Medina  writes:


I want to install Debian on a new machine but don't manage to boot from USB
stick.  (I can do so regularly with another machine, so the USB stick is ok
and so is the Debian netinst I burned onto it.)  At the boot I press F9 and a
menu appears where I can choose to boot from USB stick; but then it doesn't
so at all booting instead into Windows 11.  In BIOS I enabled the CSM
protocol but nothing.  Please help as I don't know what to do: thanks.



Now I tried with a CDROM instead of a USB stick but the problem remains.

Rodolfo



I asked before, and have not seen an answer.

Have you gone into the UEFI/BIOS, and turned off secure booting?

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: Please help with not booting from USB so to install Debian

[Max Nikulin]

On 09/06/2023 17:54, Rodolfo Medina wrote:

...And now I tried even with an MS Windows 10 installation CDROM but the
problem remains!


Check what devices are enabled in boot settings in system setup (BIOS or 
firmware setting).


When you switching off a computer with windows, perhaps actually it 
performs suspend do disk (hibernate), not shutdown. Alternative boot 
options may be disabled when system is resumed from hibernation. Ensure 
that you namely *shutdown* windows. The following page suggests that it 
may be configured in "System and Security". Perhaps some modifier (Alt 
or Shift) may unveil additional options related to the power item of the 
start menu.


https://support.microsoft.com/en-us/windows/shut-down-sleep-or-hibernate-your-pc-2941d165-7d0a-a5e8-c5ad-8c972e8e6eff

Re: Please help with not booting from USB so to install Debian

[fjd]

On Fri, 9 Jun 2023, Rodolfo Medina wrote:


Rodolfo Medina  writes:


Rodolfo Medina  writes:


I want to install Debian on a new machine but don't manage to boot from USB
stick.  (I can do so regularly with another machine, so the USB stick is ok
and so is the Debian netinst I burned onto it.)  At the boot I press F9 and
a menu appears where I can choose to boot from USB stick; but then it
doesn't so at all booting instead into Windows 11.  In BIOS I enabled the
CSM protocol but nothing.  Please help as I don't know what to do: thanks.



Now I tried with a CDROM instead of a USB stick but the problem remains.



...And now I tried even with an MS Windows 10 installation CDROM but the
problem remains!


I may have missed it: have you tried going into Windows 10 and into 
setup, looking for 'boot' in the search bar and select 'change 
advanced startup options'? then you go to "Advanced startup" and 
hit "Restart now"?


When the machine reboots go into the BIOS/UEFI system and select your 
usb.


Sorry if this has been proposed already and I missed it. Also sorry if 
it doesn't work. I have to do it if I want to boot from usb on my Acer 
laptop.


fjd

--

Verbum sat sapienti.

Re: Please help with not booting from USB so to install Debian

[Rodolfo Medina]

Rodolfo Medina  writes:

> Rodolfo Medina  writes:
>
>> I want to install Debian on a new machine but don't manage to boot from USB
>> stick.  (I can do so regularly with another machine, so the USB stick is ok
>> and so is the Debian netinst I burned onto it.)  At the boot I press F9 and
>> a menu appears where I can choose to boot from USB stick; but then it
>> doesn't so at all booting instead into Windows 11.  In BIOS I enabled the
>> CSM protocol but nothing.  Please help as I don't know what to do: thanks.
>
>
> Now I tried with a CDROM instead of a USB stick but the problem remains.


...And now I tried even with an MS Windows 10 installation CDROM but the
problem remains!

Rodolfo

Re: Please help with not booting from USB so to install Debian

[Rodolfo Medina]

Rodolfo Medina  writes:

> I want to install Debian on a new machine but don't manage to boot from USB
> stick.  (I can do so regularly with another machine, so the USB stick is ok
> and so is the Debian netinst I burned onto it.)  At the boot I press F9 and a
> menu appears where I can choose to boot from USB stick; but then it doesn't
> so at all booting instead into Windows 11.  In BIOS I enabled the CSM
> protocol but nothing.  Please help as I don't know what to do: thanks.


Now I tried with a CDROM instead of a USB stick but the problem remains.

Rodolfo

Re: Please help with not booting from USB so to install Debian

[DdB]

Am 08.06.2023 um 20:36 schrieb Rodolfo Medina:
> I want to install Debian on a new machine but don't manage to boot from USB
> stick.  (I can do so regularly with another machine, so the USB stick is ok 
> and
> so is the Debian netinst I burned onto it.)  At the boot I press F9 and a menu
> appears where I can choose to boot from USB stick; but then it doesn't so at 
> all
> booting instead into Windows 11.  In BIOS I enabled the CSM protocol but
> nothing.  Please help as I don't know what to do: thanks.
> 
> Rodolfo
> 
> 
Sorry, i have no experience with this concrete issue. Last time, i
experienced USB boot issues, it did help to just use another USB-port
instead. ;-)

But honestly, i see many hints and advices are coming, but still the
cause of the problem has not yet been identified, which would be my
first attempt in any case.

Since you confirm, that booting from the stick is possible on another
machine, it cannot be, that the stick itself doesnt work. But does that
other machine also have the same processor architecture (celeron ...)?

IIRC it is possible to boot a 32-bit OS on a 64 bit machine (not
recommended, but possible), whereas the other way round would just fail.

Sure, in here Windooze is regarded as a nuisance, but even windows can
inspect its boot config and determine, how the machine is coming up, if
the disk has GPT or MBR (probably the first), and you might be able to
find out, if your setup allows ANY booting from USB (like non flash
storage).

Even without aspiring for completeness, i was suggesting different areas
being possibly of concern, like
- hardware (usb, processor)
- bios (setup)
- version mismatch (partition tables, OS-architecture)
- there may be more (like secret holes leading to hidden switches)

Once the cause will be identified, it is going to be much easier (or
just plain impossible) to remedy the problem. And please report back,
what you found.

Re: Please help with not booting from USB so to install Debian

[David Christensen]

On 6/9/23 00:59, Rodolfo Medina wrote:

David Christensen writes:

On 6/8/23 11:36, Rodolfo Medina wrote:

I want to install Debian on a new machine but don't manage to boot from USB
stick.  (I can do so regularly with another machine, so the USB stick is ok
and
so is the Debian netinst I burned onto it.)  At the boot I press F9 and a menu
appears where I can choose to boot from USB stick; but then it doesn't so at
all
booting instead into Windows 11.  In BIOS I enabled the CSM protocol but
nothing.  Please help as I don't know what to do: thanks.


On 6/8/23 13:01, Rodolfo Medina wrote:

   
https://www.amazon.it/KUU-Notebook-Prozessor-Bluetooth-portatile/dp/B0C4TGXKBC/ref=sr_1_2_sspa?crid=3PK1MW55MAOA


Do you want Windows/Debian dual-boot, or Debian only?


At least one of the two.  What I don't want is MS Windows only...  ;-)



Okay.  I avoid dual-boot, so I will allow others more familiar with 
dual-boot help.



David

Re: Please help with not booting from USB so to install Debian

[Rodolfo Medina]

Bret Busby  writes:

> If you go to
>
> https://lists.ubuntu.com/archives/ubuntu-users/2022-July/thread.html
>
> and scroll down to the thread starting with the subject "Questions about
> Linux Mint and this list", read that message, and, work your way through the
> responses, especially, the ones from Liam Proven, you should be able to get
> the answer that you seek.


Thanks, but it is of no help, I'm afraid...

Rodolfo

Re: Please help with not booting from USB so to install Debian

[Rodolfo Medina]

"Thomas Schmitt"  writes:

> I understand from the link that it has a 64 bit Celeron J4105 CPU.
> So its EFI would want an "amd64" ISO.
>
> [...]
>
> You could try with
>   
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.7.0-amd64-netinst.iso
> and CSM disabled.

Unfortunately, it won't boot either...

Rodolfo

Re: Please help with not booting from USB so to install Debian

[Rodolfo Medina]

David Christensen  writes:

> On 6/8/23 11:36, Rodolfo Medina wrote:
>> I want to install Debian on a new machine but don't manage to boot from USB
>> stick.  (I can do so regularly with another machine, so the USB stick is ok
>> and
>> so is the Debian netinst I burned onto it.)  At the boot I press F9 and a 
>> menu
>> appears where I can choose to boot from USB stick; but then it doesn't so at
>> all
>> booting instead into Windows 11.  In BIOS I enabled the CSM protocol but
>> nothing.  Please help as I don't know what to do: thanks.
>
> On 6/8/23 13:01, Rodolfo Medina wrote:
>>
>   
> https://www.amazon.it/KUU-Notebook-Prozessor-Bluetooth-portatile/dp/B0C4TGXKBC/ref=sr_1_2_sspa?crid=3PK1MW55MAOA
>
>
> Do you want Windows/Debian dual-boot, or Debian only?


At least one of the two.  What I don't want is MS Windows only...  ;-)

Rodolfo

Re: Please help with not booting from USB so to install Debian

[Thomas Schmitt]

Hi,

i wrote:
> > I understand from the link that it has a 64 bit Celeron J4105 CPU.
> > So its EFI would want an "amd64" ISO.

Charles Curley wrote:
> A Celeron should be able to run i386 Debian. But the amd64 might be a
> better use of its capabilities.

Other than with legacy BIOS, EFI looks for different boot programs in the
EFI System Partition's FAT filesystem:
i386:  \EFI\BOOT\BOOTIA32.EFI
amd64: \EFI\BOOT\BOOTX64.EFI

debian-11.7.0-i386-netinst.iso only offers BOOTIA32.EFI :
  mount debian-11.7.0-i386-netinst.iso /mnt/iso
  mount /mnt/iso/boot/grub/efi.img /mnt/fat
  find /mnt/fat
So a normal amd64 EFI will not consider booting it.

The MBR code for legacy BIOS should be usable for 64-bit and 32-bit
alike. But Rodolfo Medina's machine seems not to like the USB stick in
CSM mode.


Have a nice day :)

Thomas

Re: Please help with not booting from USB so to install Debian

[Joseph Loo]

You might want to read the manual with the computer. My Lenovo would boot
automatically to Windows. In the manual, it had a hold on the side, trusty
paperwork clip press the hole, boots into bios. Install Linux

On Thu, Jun 8, 2023, 2:51 PM Bret Busby  wrote:

> On 9/6/23 05:18, Bret Busby wrote:
> > On 9/6/23 05:02, Bret Busby wrote:
> >> On 9/6/23 04:52, Rodolfo Medina wrote:
> >>> Bret Busby  writes:
> >>>
> >>>> My understanding is that Windows 11 computers have malware that is
> >>>> designed
> >>>> to prevent booting into anything other than the malicious Windows 11.
> >>>>
> >>>> A procedure to get around the Windows 11 malware, and to be able to
> >>>> boot into
> >>>> Linux, has, I believe, been described on the Ubuntu Users mailing
> list.
> >>>
> >>>
> >>> Can you perhaps point out a link to read that procedure?  Thanks!
> >>>
> >>> Rodolfo
> >>>
> >> I have posted a query to the Ubuntu list, asking the person who I
> >> believe, provided the procedure on that list, and, who has published
> >> equivalent information for Windows 10.
> >>
> >> I seek his response.
> >>
> >> ..
> >> Bret Busby
> >> Armadale
> >> West Australia
> >> (UTC+0800)
> >> ..
> > Have you disabled "secure boot" on your Windows 11 PC?
> >
> > ..
> > Bret Busby
> > Armadale
> > West Australia
> > (UTC+0800)
> > ..
>
> If you go to
>
> https://lists.ubuntu.com/archives/ubuntu-users/2022-July/thread.html
>
> and scroll down to the thread starting with the subject "Questions about
> Linux Mint and this list", read that message, and, work your way through
> the responses, especially, the ones from Liam Proven, you should be able
> to get the answer that you seek.
>
> ..
> Bret Busby
> Armadale
> West Australia
> (UTC+0800)
> ..
>
>

Re: Please help with not booting from USB so to install Debian

[David Christensen]

On 6/8/23 11:36, Rodolfo Medina wrote:

I want to install Debian on a new machine but don't manage to boot from USB
stick.  (I can do so regularly with another machine, so the USB stick is ok and
so is the Debian netinst I burned onto it.)  At the boot I press F9 and a menu
appears where I can choose to boot from USB stick; but then it doesn't so at all
booting instead into Windows 11.  In BIOS I enabled the CSM protocol but
nothing.  Please help as I don't know what to do: thanks.


On 6/8/23 13:01, Rodolfo Medina wrote:
> 
https://www.amazon.it/KUU-Notebook-Prozessor-Bluetooth-portatile/dp/B0C4TGXKBC/ref=sr_1_2_sspa?crid=3PK1MW55MAOA



Do you want Windows/Debian dual-boot, or Debian only?


David

Re: Please help with not booting from USB so to install Debian

[David Wright]

On Thu 08 Jun 2023 at 15:36:27 (-0600), Charles Curley wrote:
> On Thu, 08 Jun 2023 23:15:36 +0200 "Thomas Schmitt" wrote:
> 
> > I understand from the link that it has a 64 bit Celeron J4105 CPU.
> > So its EFI would want an "amd64" ISO.
> 
> A Celeron should be able to run i386 Debian. But the amd64 might be a
> better use of its capabilities.

Perhaps we have to distinguish between "CPU can run 32-bits too"
and "a particular UEFI can boot into a 32-bit OS".

Cheers,
David.

Re: Please help with not booting from USB so to install Debian

[Bret Busby]

On 9/6/23 05:18, Bret Busby wrote:

On 9/6/23 05:02, Bret Busby wrote:

On 9/6/23 04:52, Rodolfo Medina wrote:

Bret Busby  writes:

My understanding is that Windows 11 computers have malware that is 
designed

to prevent booting into anything other than the malicious Windows 11.

A procedure to get around the Windows 11 malware, and to be able to 
boot into

Linux, has, I believe, been described on the Ubuntu Users mailing list.



Can you perhaps point out a link to read that procedure?  Thanks!

Rodolfo

I have posted a query to the Ubuntu list, asking the person who I 
believe, provided the procedure on that list, and, who has published 
equivalent information for Windows 10.


I seek his response.

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Have you disabled "secure boot" on your Windows 11 PC?

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..


If you go to

https://lists.ubuntu.com/archives/ubuntu-users/2022-July/thread.html

and scroll down to the thread starting with the subject "Questions about 
Linux Mint and this list", read that message, and, work your way through 
the responses, especially, the ones from Liam Proven, you should be able 
to get the answer that you seek.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: Please help with not booting from USB so to install Debian

[Bret Busby]

On 9/6/23 05:26, Bret Busby wrote:

On 9/6/23 05:18, Bret Busby wrote:

On 9/6/23 05:02, Bret Busby wrote:

On 9/6/23 04:52, Rodolfo Medina wrote:

Bret Busby  writes:

My understanding is that Windows 11 computers have malware that is 
designed

to prevent booting into anything other than the malicious Windows 11.

A procedure to get around the Windows 11 malware, and to be able to 
boot into
Linux, has, I believe, been described on the Ubuntu Users mailing 
list.



Can you perhaps point out a link to read that procedure?  Thanks!

Rodolfo

I have posted a query to the Ubuntu list, asking the person who I 
believe, provided the procedure on that list, and, who has published 
equivalent information for Windows 10.


I seek his response.

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Have you disabled "secure boot" on your Windows 11 PC?

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..


If you go to

https://lists.ubuntu.com/archives/ubuntu-users/2022-July/thread.html

and scroll down to the thread starting with the subject "Questions about 
Linux Mint and this list", read that message, and, work your way through 
the responses, especially, the ones from Liam Proven, you should be able 
to get the answer that you seek.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..
I should have included, in my previous posts about this, that the 
imperative first step, before either using a newly purchased computer, 
or, trying to add an extra booting operating system to any computer, new 
or otherwise, is to ensure that you have the latest available UEFI/BIOS 
installed on the computer.


The computer manufacturer's web site should have the applicable 
procedures involved,  for both checking the installed and latest 
UEFI/BIOS versions for the computer, and, for upgrading it as needed.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: Please help with not booting from USB so to install Debian

[Charles Curley]

On Thu, 08 Jun 2023 23:15:36 +0200
"Thomas Schmitt"  wrote:

> I understand from the link that it has a 64 bit Celeron J4105 CPU.
> So its EFI would want an "amd64" ISO.

A Celeron should be able to run i386 Debian. But the amd64 might be a
better use of its capabilities.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Please help with not booting from USB so to install Debian

[Charles Curley]

On Thu, 08 Jun 2023 20:01:20 +
Rodolfo Medina  wrote:

> Here it is:
> 
>  
> https://www.amazon.it/KUU-Notebook-Prozessor-Bluetooth-portatile/dp/B0C4TGXKBC/ref=sr_1_2_sspa?crid=3PK1MW55MAOA

Hmm, never heard of that vendor. You might do better with one of the
Debian Italian language lists.
https://lists.debian.org/completeindex.html

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Please help with not booting from USB so to install Debian

[Bret Busby]

On 9/6/23 05:02, Bret Busby wrote:

On 9/6/23 04:52, Rodolfo Medina wrote:

Bret Busby  writes:

My understanding is that Windows 11 computers have malware that is 
designed

to prevent booting into anything other than the malicious Windows 11.

A procedure to get around the Windows 11 malware, and to be able to 
boot into

Linux, has, I believe, been described on the Ubuntu Users mailing list.



Can you perhaps point out a link to read that procedure?  Thanks!

Rodolfo

I have posted a query to the Ubuntu list, asking the person who I 
believe, provided the procedure on that list, and, who has published 
equivalent information for Windows 10.


I seek his response.

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Have you disabled "secure boot" on your Windows 11 PC?

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: Please help with not booting from USB so to install Debian

[Thomas Schmitt]

Hi,

Rodolfo Medina wrote:
> https://www.amazon.it/KUU-Notebook-Prozessor-Bluetooth-portatile/dp/B0C4TGX
KBC/ref=sr_1_2_sspa?crid=3PK1MW55MAOA
>  $ dd if=debian-11.7.0-i386-netinst.iso of=/dev/sdd bs=4M; sync

I understand from the link that it has a 64 bit Celeron J4105 CPU.
So its EFI would want an "amd64" ISO.


> > In BIOS I enabled the CSM protocol
> No message: it simply boots into Windows instead of the USB drive that I
> chose in the menu.

You could try with
  
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.7.0-amd64-netinst.iso
and CSM disabled.
(Maybe it even begins to work with CSM if the firmware is brain damaged
enough.)


Have a nice day :)

Thomas

Re: Please help with not booting from USB so to install Debian

[Bret Busby]

On 9/6/23 04:52, Rodolfo Medina wrote:

Bret Busby  writes:


My understanding is that Windows 11 computers have malware that is designed
to prevent booting into anything other than the malicious Windows 11.

A procedure to get around the Windows 11 malware, and to be able to boot into
Linux, has, I believe, been described on the Ubuntu Users mailing list.



Can you perhaps point out a link to read that procedure?  Thanks!

Rodolfo

I have posted a query to the Ubuntu list, asking the person who I 
believe, provided the procedure on that list, and, who has published 
equivalent information for Windows 10.


I seek his response.

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: Please help with not booting from USB so to install Debian

[Rodolfo Medina]

Bret Busby  writes:

> My understanding is that Windows 11 computers have malware that is designed
> to prevent booting into anything other than the malicious Windows 11.
>
> A procedure to get around the Windows 11 malware, and to be able to boot into
> Linux, has, I believe, been described on the Ubuntu Users mailing list.


Can you perhaps point out a link to read that procedure?  Thanks!

Rodolfo

Re: Please help with not booting from USB so to install Debian

[Bret Busby]

On 9/6/23 02:36, Rodolfo Medina wrote:

I want to install Debian on a new machine but don't manage to boot from USB
stick.  (I can do so regularly with another machine, so the USB stick is ok and
so is the Debian netinst I burned onto it.)  At the boot I press F9 and a menu
appears where I can choose to boot from USB stick; but then it doesn't so at all
booting instead into Windows 11.  In BIOS I enabled the CSM protocol but
nothing.  Please help as I don't know what to do: thanks.

Rodolfo

My understanding is that Windows 11 computers have malware that is 
designed to prevent booting into anything other than the malicious 
Windows 11.


A procedure to get around the Windows 11 malware, and to be able to boot 
into Linux, has, I believe, been described on the Ubuntu Users mailing list.


My understanding is that, to boot into Linux or any other non-MS 
operating system, Windows 11 should be avoided like the plague that it 
is, and, that a computer with the Windows 10 OS should be obtained, 
rather than the malware that is Windows 11.


Windows 11 also, in the malware that it is, proscribes software that 
runs on Windows 10 and earlier versions of Windows.


The best use for a Windows 11 computer, is to use it as a projectile. 
Such computers are not even substantial enough to use as boat anchors.


..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: Please help with not booting from USB so to install Debian

[Rodolfo Medina]

Thank you Andrew and Charles.

"Andrew M.A. Cater"  writes:

> What model of machine is this - and how new?

Here it is:

 
https://www.amazon.it/KUU-Notebook-Prozessor-Bluetooth-portatile/dp/B0C4TGXKBC/ref=sr_1_2_sspa?crid=3PK1MW55MAOA


> How did you write the image to the USB stick?

This way:

 $ dd if=debian-11.7.0-i386-netinst.iso of=/dev/sdd bs=4M; sync

As I said, another machine of mine boots regularly into it, so it must be ok.

> CSM is probably not needed. USB boot *should* work but there is a
> way of forcing boot only to Windows 11 in some machines. (I had this
> on a relatively new T490).
>
> Does it show any messages?

No message: it simply boots into Windows instead of the USB drive that I chose
in the menu.

Thanks,

Rodolfo

Re: Please help with not booting from USB so to install Debian

[Charles Curley]

On Thu, 8 Jun 2023 18:36:27 +
Rodolfo Medina  wrote:

> I want to install Debian on a new machine but don't manage to boot
> from USB stick.

It might help if you identified the new machine.

You might also check web sites related to Linux on that manufacturer's
products. E.g. thinkwiki (https://www.thinkwiki.org/wiki/ThinkWiki) for
Lenovo/IBM machines. Or https://linux-hardware.org.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Please help with not booting from USB so to install Debian

[Andrew M.A. Cater]

On Thu, Jun 08, 2023 at 06:36:27PM +, Rodolfo Medina wrote:
> I want to install Debian on a new machine but don't manage to boot from USB
> stick.  (I can do so regularly with another machine, so the USB stick is ok 
> and
> so is the Debian netinst I burned onto it.)  At the boot I press F9 and a menu
> appears where I can choose to boot from USB stick; but then it doesn't so at 
> all
> booting instead into Windows 11.  In BIOS I enabled the CSM protocol but
> nothing.  Please help as I don't know what to do: thanks.
> 

Hi Rodolfo,

What model of machine is this - and how new?

How did you write the image to the USB stick?

CSM is probably not needed. USB boot *should* work but there is a
way of forcing boot only to Windows 11 in some machines. (I had this
on a relatively new T490).

Does it show any messages?


> Rodolfo
>

All the very best, as ever,

Andy Cater 

Please help with not booting from USB so to install Debian

[Rodolfo Medina]

I want to install Debian on a new machine but don't manage to boot from USB
stick.  (I can do so regularly with another machine, so the USB stick is ok and
so is the Debian netinst I burned onto it.)  At the boot I press F9 and a menu
appears where I can choose to boot from USB stick; but then it doesn't so at all
booting instead into Windows 11.  In BIOS I enabled the CSM protocol but
nothing.  Please help as I don't know what to do: thanks.

Rodolfo

PANIC Debian 11 LXDE After update no booting is possible

[Schwibinger Michael]

Good morning
Dear Gene

Sorry I could no find Your anwswer

Thank You
Regards
Sophie




Von: gene heskett 
Gesendet: Samstag, 20. Mai 2023 11:51
An: debian-user@lists.debian.org 
Betreff: Re: AW: PANIC Debian 11 LXDE After update no booting is possible

On 5/20/23 07:32, Schwibinger Michael wrote:
>
> AW: PANIC Debian 11 LXDE After update no booting is possible
>
> Good afternoon
> Thank You for email.
> I think
> in Linux
> I shall post here a file
> where the other users of the group can see the mistake I did.
>
> Which file shall I read out and mail here to the group?
>
> Regards
> Sophie
>
> The computer is using
> Browsers
> Thunderbird
> Gedit<<<<<<<<< VLC
> GIMP
> and nothing else
>
>
>
>
>
>
> 
> Von: Cindy Sue Causey 
> Gesendet: Freitag, 19. Mai 2023 15:47
> An: Debian Users 
> Betreff: Re: PANIC Debian 11 LXDE After update no booting is possible
>
> On 5/19/23, Schwibinger Michael  wrote:
>> Good afternoon
>>
>> I did the update and
>> when doing new start:
>> Crash
>
>
> Hi, Sophie.. While you're waiting for others to respond, am typing to
> say I just went through this a couple days ago. Our situations are all
> so different so this is a recap of what happened for me.
>
> In *my* case, something unknown changed a BUNCH of (but not all) top
> level root directory permissions. I found out by accident while trying
> to mitigate the first errors I encountered.
>
> At some point, systemd was referenced and was freaking out that it had
> lost permissions. That's when I ran "ls -ld /*" and received e.g.:
>
> lrwxrwxrwx   1 root  root  7 Feb 11 14:26 /bin -> usr/bin
> drwxr-xr-x   4 1001 1001  4096 May 17 05:47 /boot
> drwxr-xr-x  11 root  root  36864 Feb 12 14:17 /dev
> drwxr-xr-x 125 1001 1001 12288 May 16 22:12 /etc
> drwxr-xr-x   5 1001 1001  4096 Apr 14 02:39 /home
> lrwxrwxrwx   1 root  root  7 Feb 11 14:26 /lib -> usr/lib
> lrwxrwxrwx   1 root  root  9 Feb 11 14:26 /lib32 -> usr/lib32
> lrwxrwxrwx   1 root  root  9 Feb 11 14:26 /lib64 -> usr/lib64
> lrwxrwxrwx   1 root  root 10 Feb 11 14:26 /libx32 -> usr/libx32
> drwx--   2 1001 1001 16384 Feb  9 20:57 /lost+found
> drwxr-xr-x   4 1001 1001  4096 Apr 21 20:52 /media
> drwxr-xr-x  10 1001 1001  4096 May 16 16:27 /mnt
> drwxr-xr-x   3 1001 1001  4096 Feb 26 16:44 /opt
> drwxr-xr-x   2 root  root   4096 Oct  3  2022 /proc
> drwx--   8 root  1001  4096 May 16 22:19 /root
>
> 1001 is the username I was on when the incident occurred. That /root
> change is odd because it only changed one of them. Even odder is how
> whatever did this made only partial permission changes instead of
> altering all child directories under the top level parent "/"
> directory.
>
> First sign something was wrong was that I suddenly couldn't log onto
> the Internet. Prior to that, everything else worked as expected.
>
> Then I rebooted and landed at an "sh" prompt. A second or third reboot
> landed at that dreaded kernel panic screen that only shuts down for me
> by punching the hardware ON/OFF button.
>
> I had also done an update/upgrade a few hours before. Newest program
> added was Einstein after a different Debian-User thread reminded me it
> exists.
>
> In case it helps narrow down a culprit, the last four apt-get actions
> I performed between 2023.05.15 and 2023.05.16 are:
>
>
>  START SNIPPETS FROM /var/log/apt/history.log 
>
> Upgrade: libgsl27:amd64 (2.7.1+dfsg-3+b1, 2.7.1+dfsg-4),
> libgslcblas0:amd64 (2.7.1+dfsg-3+b1, 2.7.1+dfsg-4)
>
> Install: libsdl-mixer1.2:amd64 (1.2.12-17+b3, automatic),
> libsdl-ttf2.0-0:amd64 (2.0.11-6, automatic), einstein:amd64
> (2.0.dfsg.2-10+b1), libmikmod3:amd64 (3.3.11.1-7, automatic)
>
> Upgrade: libcap2-bin:amd64 (1:2.66-3, 1:2.66-4), grub-pc-bin:amd64
> (2.06-12, 2.06-13), libcap2:amd64 (1:2.66-3, 1:2.66-4),
> grub-efi-amd64-bin:amd64 (2.06-12, 2.06-13), grub2-common:amd64
> (2.06-12, 2.06-13), grub-common:amd64 (2.06-12, 2.06-13),
> grub-pc:amd64 (2.06-12, 2.06-13)
>
> Upgrade: google-chrome-stable:amd64 (113.0.5672.92-1,
> 113.0.5672.126-1), libtbbbind-2-5:amd64 (2021.8.0-1, 2021.8.0-2),
> libtbbmalloc2:amd64 (2021.8.0-1, 2021.8.0-2), libtbb12:amd64
> (2021.8.0-1, 2021.8.0-2)
>
>  END SNIPPETS FROM /var/log/apt/history.log 
>
> The affected partition is still here, but I didn't have time for
> fighting with it. I debootstrap'ed onto another partition, installed a
> ton of favorite programs (not Einstein), ran &

Re: AW: PANIC Debian 11 LXDE After update no booting is possible

[gene heskett]

On 5/20/23 07:32, Schwibinger Michael wrote:


AW: PANIC Debian 11 LXDE After update no booting is possible

Good afternoon
Thank You for email.
I think
in Linux
I shall post here a file
where the other users of the group can see the mistake I did.

Which file shall I read out and mail here to the group?

Regards
Sophie

The computer is using
Browsers
Thunderbird
Gedit<<<<<<<<<
Gesendet: Freitag, 19. Mai 2023 15:47
An: Debian Users 
Betreff: Re: PANIC Debian 11 LXDE After update no booting is possible

On 5/19/23, Schwibinger Michael  wrote:

Good afternoon

I did the update and
when doing new start:
Crash



Hi, Sophie.. While you're waiting for others to respond, am typing to
say I just went through this a couple days ago. Our situations are all
so different so this is a recap of what happened for me.

In *my* case, something unknown changed a BUNCH of (but not all) top
level root directory permissions. I found out by accident while trying
to mitigate the first errors I encountered.

At some point, systemd was referenced and was freaking out that it had
lost permissions. That's when I ran "ls -ld /*" and received e.g.:

lrwxrwxrwx   1 root  root  7 Feb 11 14:26 /bin -> usr/bin
drwxr-xr-x   4 1001 1001  4096 May 17 05:47 /boot
drwxr-xr-x  11 root  root  36864 Feb 12 14:17 /dev
drwxr-xr-x 125 1001 1001 12288 May 16 22:12 /etc
drwxr-xr-x   5 1001 1001  4096 Apr 14 02:39 /home
lrwxrwxrwx   1 root  root  7 Feb 11 14:26 /lib -> usr/lib
lrwxrwxrwx   1 root  root  9 Feb 11 14:26 /lib32 -> usr/lib32
lrwxrwxrwx   1 root  root  9 Feb 11 14:26 /lib64 -> usr/lib64
lrwxrwxrwx   1 root  root 10 Feb 11 14:26 /libx32 -> usr/libx32
drwx--   2 1001 1001 16384 Feb  9 20:57 /lost+found
drwxr-xr-x   4 1001 1001  4096 Apr 21 20:52 /media
drwxr-xr-x  10 1001 1001  4096 May 16 16:27 /mnt
drwxr-xr-x   3 1001 1001  4096 Feb 26 16:44 /opt
drwxr-xr-x   2 root  root   4096 Oct  3  2022 /proc
drwx--   8 root  1001  4096 May 16 22:19 /root

1001 is the username I was on when the incident occurred. That /root
change is odd because it only changed one of them. Even odder is how
whatever did this made only partial permission changes instead of
altering all child directories under the top level parent "/"
directory.

First sign something was wrong was that I suddenly couldn't log onto
the Internet. Prior to that, everything else worked as expected.

Then I rebooted and landed at an "sh" prompt. A second or third reboot
landed at that dreaded kernel panic screen that only shuts down for me
by punching the hardware ON/OFF button.

I had also done an update/upgrade a few hours before. Newest program
added was Einstein after a different Debian-User thread reminded me it
exists.

In case it helps narrow down a culprit, the last four apt-get actions
I performed between 2023.05.15 and 2023.05.16 are:


 START SNIPPETS FROM /var/log/apt/history.log 

Upgrade: libgsl27:amd64 (2.7.1+dfsg-3+b1, 2.7.1+dfsg-4),
libgslcblas0:amd64 (2.7.1+dfsg-3+b1, 2.7.1+dfsg-4)

Install: libsdl-mixer1.2:amd64 (1.2.12-17+b3, automatic),
libsdl-ttf2.0-0:amd64 (2.0.11-6, automatic), einstein:amd64
(2.0.dfsg.2-10+b1), libmikmod3:amd64 (3.3.11.1-7, automatic)

Upgrade: libcap2-bin:amd64 (1:2.66-3, 1:2.66-4), grub-pc-bin:amd64
(2.06-12, 2.06-13), libcap2:amd64 (1:2.66-3, 1:2.66-4),
grub-efi-amd64-bin:amd64 (2.06-12, 2.06-13), grub2-common:amd64
(2.06-12, 2.06-13), grub-common:amd64 (2.06-12, 2.06-13),
grub-pc:amd64 (2.06-12, 2.06-13)

Upgrade: google-chrome-stable:amd64 (113.0.5672.92-1,
113.0.5672.126-1), libtbbbind-2-5:amd64 (2021.8.0-1, 2021.8.0-2),
libtbbmalloc2:amd64 (2021.8.0-1, 2021.8.0-2), libtbb12:amd64
(2021.8.0-1, 2021.8.0-2)

 END SNIPPETS FROM /var/log/apt/history.log 

The affected partition is still here, but I didn't have time for
fighting with it. I debootstrap'ed onto another partition, installed a
ton of favorite programs (not Einstein), ran "ls -ld /*" on the new
partition, and all has been well...

So far.

PS I reported this exact kind of thing to Debian Security a number of
years ago. I was "blown off", shown the cyber door. The PRIVATE email
I sent them had explained the situation two different ways to help
expedite their receiving end's grasp of the repeatedly reproducible
direness of what happened.

In last year or so, someone else got credit for reporting a part of
the same thing I reported years ago. I don't remember what was left
out, but whatever it was, someone else has possibly figured it out...
so that it's not just Adobe perping it this time.

And they're perping it in a different way. Adobe had gone straight
down the line and changed everything directly under "/" to a third
party username. No root, no 1001 for that one back then.

Cindy :)
--
Talking Rock, Pickens County, Georgia, USA
* run

AW: PANIC Debian 11 LXDE After update no booting is possible

[Schwibinger Michael]

AW: PANIC Debian 11 LXDE After update no booting is possible

Good afternoon
Thank You for email.
I think
in Linux
I shall post here a file
where the other users of the group can see the mistake I did.

Which file shall I read out and mail here to the group?

Regards
Sophie

The computer is using
Browsers
Thunderbird
Gedit
VLC
GIMP
and nothing else







Von: Cindy Sue Causey 
Gesendet: Freitag, 19. Mai 2023 15:47
An: Debian Users 
Betreff: Re: PANIC Debian 11 LXDE After update no booting is possible

On 5/19/23, Schwibinger Michael  wrote:
> Good afternoon
>
> I did the update and
> when doing new start:
> Crash


Hi, Sophie.. While you're waiting for others to respond, am typing to
say I just went through this a couple days ago. Our situations are all
so different so this is a recap of what happened for me.

In *my* case, something unknown changed a BUNCH of (but not all) top
level root directory permissions. I found out by accident while trying
to mitigate the first errors I encountered.

At some point, systemd was referenced and was freaking out that it had
lost permissions. That's when I ran "ls -ld /*" and received e.g.:

lrwxrwxrwx   1 root  root  7 Feb 11 14:26 /bin -> usr/bin
drwxr-xr-x   4 1001 1001  4096 May 17 05:47 /boot
drwxr-xr-x  11 root  root  36864 Feb 12 14:17 /dev
drwxr-xr-x 125 1001 1001 12288 May 16 22:12 /etc
drwxr-xr-x   5 1001 1001  4096 Apr 14 02:39 /home
lrwxrwxrwx   1 root  root  7 Feb 11 14:26 /lib -> usr/lib
lrwxrwxrwx   1 root  root  9 Feb 11 14:26 /lib32 -> usr/lib32
lrwxrwxrwx   1 root  root  9 Feb 11 14:26 /lib64 -> usr/lib64
lrwxrwxrwx   1 root  root 10 Feb 11 14:26 /libx32 -> usr/libx32
drwx--   2 1001 1001 16384 Feb  9 20:57 /lost+found
drwxr-xr-x   4 1001 1001  4096 Apr 21 20:52 /media
drwxr-xr-x  10 1001 1001  4096 May 16 16:27 /mnt
drwxr-xr-x   3 1001 1001  4096 Feb 26 16:44 /opt
drwxr-xr-x   2 root  root   4096 Oct  3  2022 /proc
drwx--   8 root  1001  4096 May 16 22:19 /root

1001 is the username I was on when the incident occurred. That /root
change is odd because it only changed one of them. Even odder is how
whatever did this made only partial permission changes instead of
altering all child directories under the top level parent "/"
directory.

First sign something was wrong was that I suddenly couldn't log onto
the Internet. Prior to that, everything else worked as expected.

Then I rebooted and landed at an "sh" prompt. A second or third reboot
landed at that dreaded kernel panic screen that only shuts down for me
by punching the hardware ON/OFF button.

I had also done an update/upgrade a few hours before. Newest program
added was Einstein after a different Debian-User thread reminded me it
exists.

In case it helps narrow down a culprit, the last four apt-get actions
I performed between 2023.05.15 and 2023.05.16 are:


 START SNIPPETS FROM /var/log/apt/history.log 

Upgrade: libgsl27:amd64 (2.7.1+dfsg-3+b1, 2.7.1+dfsg-4),
libgslcblas0:amd64 (2.7.1+dfsg-3+b1, 2.7.1+dfsg-4)

Install: libsdl-mixer1.2:amd64 (1.2.12-17+b3, automatic),
libsdl-ttf2.0-0:amd64 (2.0.11-6, automatic), einstein:amd64
(2.0.dfsg.2-10+b1), libmikmod3:amd64 (3.3.11.1-7, automatic)

Upgrade: libcap2-bin:amd64 (1:2.66-3, 1:2.66-4), grub-pc-bin:amd64
(2.06-12, 2.06-13), libcap2:amd64 (1:2.66-3, 1:2.66-4),
grub-efi-amd64-bin:amd64 (2.06-12, 2.06-13), grub2-common:amd64
(2.06-12, 2.06-13), grub-common:amd64 (2.06-12, 2.06-13),
grub-pc:amd64 (2.06-12, 2.06-13)

Upgrade: google-chrome-stable:amd64 (113.0.5672.92-1,
113.0.5672.126-1), libtbbbind-2-5:amd64 (2021.8.0-1, 2021.8.0-2),
libtbbmalloc2:amd64 (2021.8.0-1, 2021.8.0-2), libtbb12:amd64
(2021.8.0-1, 2021.8.0-2)

 END SNIPPETS FROM /var/log/apt/history.log 

The affected partition is still here, but I didn't have time for
fighting with it. I debootstrap'ed onto another partition, installed a
ton of favorite programs (not Einstein), ran "ls -ld /*" on the new
partition, and all has been well...

So far.

PS I reported this exact kind of thing to Debian Security a number of
years ago. I was "blown off", shown the cyber door. The PRIVATE email
I sent them had explained the situation two different ways to help
expedite their receiving end's grasp of the repeatedly reproducible
direness of what happened.

In last year or so, someone else got credit for reporting a part of
the same thing I reported years ago. I don't remember what was left
out, but whatever it was, someone else has possibly figured it out...
so that it's not just Adobe perping it this time.

And they're perping it in a different way. Adobe had gone straight
down the line and changed everything directly under "/" to a third
party username. No root, no 1001 for that one back then.

Cindy :)
--
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: PANIC Debian 11 LXDE After update no booting is possible

[Cindy Sue Causey]

On 5/19/23, Cindy Sue Causey  wrote:
> On 5/19/23, Schwibinger Michael  wrote:
>> Good afternoon
>>
>> I did the update and
>> when doing new start:
>> Crash
>
< snipped for relevance >
>
>
> And they're perping it in a different way. Adobe had gone straight
> down the line and changed everything directly under "/" to a third
> party username. No root, no 1001 for that one back then.


After thinking about it again, I take that back. I THINK Adobe
affected only the directories it touched, not all "/" directories,
which would partially match how whatever changed mine didn't change
all the child directories.

It still doesn't explain how e.g. /root became "root 1001" instead of
"root root" permissions. My impression as someone who reported this
years ago is that someone has figured out how to take the damage to a
new level.

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: PANIC Debian 11 LXDE After update no booting is possible

[Cindy Sue Causey]

On 5/19/23, Schwibinger Michael  wrote:
> Good afternoon
>
> I did the update and
> when doing new start:
> Crash


Hi, Sophie.. While you're waiting for others to respond, am typing to
say I just went through this a couple days ago. Our situations are all
so different so this is a recap of what happened for me.

In *my* case, something unknown changed a BUNCH of (but not all) top
level root directory permissions. I found out by accident while trying
to mitigate the first errors I encountered.

At some point, systemd was referenced and was freaking out that it had
lost permissions. That's when I ran "ls -ld /*" and received e.g.:

lrwxrwxrwx   1 root  root  7 Feb 11 14:26 /bin -> usr/bin
drwxr-xr-x   4 1001 1001  4096 May 17 05:47 /boot
drwxr-xr-x  11 root  root  36864 Feb 12 14:17 /dev
drwxr-xr-x 125 1001 1001 12288 May 16 22:12 /etc
drwxr-xr-x   5 1001 1001  4096 Apr 14 02:39 /home
lrwxrwxrwx   1 root  root  7 Feb 11 14:26 /lib -> usr/lib
lrwxrwxrwx   1 root  root  9 Feb 11 14:26 /lib32 -> usr/lib32
lrwxrwxrwx   1 root  root  9 Feb 11 14:26 /lib64 -> usr/lib64
lrwxrwxrwx   1 root  root 10 Feb 11 14:26 /libx32 -> usr/libx32
drwx--   2 1001 1001 16384 Feb  9 20:57 /lost+found
drwxr-xr-x   4 1001 1001  4096 Apr 21 20:52 /media
drwxr-xr-x  10 1001 1001  4096 May 16 16:27 /mnt
drwxr-xr-x   3 1001 1001  4096 Feb 26 16:44 /opt
drwxr-xr-x   2 root  root   4096 Oct  3  2022 /proc
drwx--   8 root  1001  4096 May 16 22:19 /root

1001 is the username I was on when the incident occurred. That /root
change is odd because it only changed one of them. Even odder is how
whatever did this made only partial permission changes instead of
altering all child directories under the top level parent "/"
directory.

First sign something was wrong was that I suddenly couldn't log onto
the Internet. Prior to that, everything else worked as expected.

Then I rebooted and landed at an "sh" prompt. A second or third reboot
landed at that dreaded kernel panic screen that only shuts down for me
by punching the hardware ON/OFF button.

I had also done an update/upgrade a few hours before. Newest program
added was Einstein after a different Debian-User thread reminded me it
exists.

In case it helps narrow down a culprit, the last four apt-get actions
I performed between 2023.05.15 and 2023.05.16 are:


 START SNIPPETS FROM /var/log/apt/history.log 

Upgrade: libgsl27:amd64 (2.7.1+dfsg-3+b1, 2.7.1+dfsg-4),
libgslcblas0:amd64 (2.7.1+dfsg-3+b1, 2.7.1+dfsg-4)

Install: libsdl-mixer1.2:amd64 (1.2.12-17+b3, automatic),
libsdl-ttf2.0-0:amd64 (2.0.11-6, automatic), einstein:amd64
(2.0.dfsg.2-10+b1), libmikmod3:amd64 (3.3.11.1-7, automatic)

Upgrade: libcap2-bin:amd64 (1:2.66-3, 1:2.66-4), grub-pc-bin:amd64
(2.06-12, 2.06-13), libcap2:amd64 (1:2.66-3, 1:2.66-4),
grub-efi-amd64-bin:amd64 (2.06-12, 2.06-13), grub2-common:amd64
(2.06-12, 2.06-13), grub-common:amd64 (2.06-12, 2.06-13),
grub-pc:amd64 (2.06-12, 2.06-13)

Upgrade: google-chrome-stable:amd64 (113.0.5672.92-1,
113.0.5672.126-1), libtbbbind-2-5:amd64 (2021.8.0-1, 2021.8.0-2),
libtbbmalloc2:amd64 (2021.8.0-1, 2021.8.0-2), libtbb12:amd64
(2021.8.0-1, 2021.8.0-2)

 END SNIPPETS FROM /var/log/apt/history.log 

The affected partition is still here, but I didn't have time for
fighting with it. I debootstrap'ed onto another partition, installed a
ton of favorite programs (not Einstein), ran "ls -ld /*" on the new
partition, and all has been well...

So far.

PS I reported this exact kind of thing to Debian Security a number of
years ago. I was "blown off", shown the cyber door. The PRIVATE email
I sent them had explained the situation two different ways to help
expedite their receiving end's grasp of the repeatedly reproducible
direness of what happened.

In last year or so, someone else got credit for reporting a part of
the same thing I reported years ago. I don't remember what was left
out, but whatever it was, someone else has possibly figured it out...
so that it's not just Adobe perping it this time.

And they're perping it in a different way. Adobe had gone straight
down the line and changed everything directly under "/" to a third
party username. No root, no 1001 for that one back then.

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

PANIC Debian 11 LXDE After update no booting is possible

[Schwibinger Michael]

Good afternoon

I did the update and
when doing new start:
Crash
Regards
Sophie



Von: CL 
Gesendet: Donnerstag, 18. Mai 2023 08:34
An: Schwibinger Michael ; Andrew M.A. Cater 
; debian-user@lists.debian.org 

Betreff: Re: NEW problem PANIC AW: SOLUTION AW: EPSON ...

Hello,

first I have to apologies for being a little bit rude within the next
sentences.

BUT STOP this stupid conversation.

It is quite clear that this is one of following things

1. Stupid freaking AI
2. Psycho test
3. Troll

So

@Sophie or Michal Schwibinger or what ever your name is
please stop this

It is far away from being funny or helpful

It is boring, stupid and annoying

One reason of this community is to help each other. But what you make is
questioning our all intelligence and also competences. And this freaks
me out a little bit.

Again please stop this

Thank you in advance




--
mit freundlichen Grüßen / Best Regards

**Christian Lorenz**

mailto:cl.debian.mail...@t-online.de
--

Am 18.05.23 um 09:48 schrieb Schwibinger Michael:
> Good morning
> Thank You.
>
> Sorry for bad asking.
>
> I wanted to say:
> Shall I delete in my mailbox the unanswered EPSON emails?
> I think YES.
>
> The new problem.
> Debian 11 LXDE is not booting.
>
> ,,panic,,
>
> What did I do ?
> I did the update to Debian 11.
>
> How to repair?
> What did I do wrong?
>
> Regards Sophie
>
> 
> *Von:* Andrew M.A. Cater 
> *Gesendet:* Mittwoch, 17. Mai 2023 19:47
> *An:* debian-user@lists.debian.org 
> *Betreff:* Re: SOLUTION AW: EPSON ET M 1120 new printer: If You can read
> this, you are using the wrong driver
> On Wed, May 17, 2023 at 06:27:55PM +, Schwibinger Michael wrote:
>> Good evening
>>
>> This did work.
>>
>> Thank You
>>
>> Thank You
>>
>> Thank You
>>
>>
>> Thank You
>>
>> Thank You
>>
>>
> Hi Sophie,
>
> I'm really very pleased that it all worked for you eventually.
>
> There were some false starts and some misunderstandings but the main
> thing is that IT WORKS :)
>
> We don't normally delete emails from the mailing lists - they are there
> to explain how things happened and how solutions were found.
>
> These emails also led to people explaining various facts about
> how to use the mailing list - maybe these will help other people.
>
> Herzlichen Gluckwuenshen
>
> Andy
>>
>>
>>
>> Regards Sope
>>
>> I ll send 2nd email with topoic   Delete Printer Emails.
>>
>>
>>
>> 
>> Von: Jeremy Ardley 
>> Gesendet: Montag, 8. Mai 2023 00:47
>> An: debian-user@lists.debian.org 
>> Betreff: Re: EPSON ET M 1120 new printer: If You can read this, you are 
>> using the wrong driver
>>
>>
>> On 8/5/23 08:12, Will Mengarini wrote:
>> > * Brian  [23-05/08=Mo 00:27 +0100]:
>> >>
>> >> https://download3.ebz.epson.net/dsc/f/03/00/14/48/15/1d37501ad39bd2b5753
> <https://download3.ebz.epson.net/dsc/f/03/00/14/48/15/1d37501ad39bd2b5753> \
>> >> cce3b2715b3e2fef557/epson-inkjet-printer-escpr_1.7.26-1lsb3.2_amd64.deb
>> > That includes a literal space in the middle of that hash
>> > (because the space before the backslash is taken literally).
>> >
>> > However, when I removed that space by hand, I still got "not found":
>>
>> The driver is already included in the standard debian distribution
>>
>> sudo apt-get install printer-driver-escpr
>>
>> Then the usual cups administration to attach driver to printer using lpadmin 
>> or  http://localhost:631 <http://localhost:631>
>>
>>
>> --
>> Jeremy
>> (Lists)
>>
>

Booting Debian from NFS (using EFI PXE GRUB)

[tuxifan]

Hey!

As kind of a network-wide fallback system (and for some diskless computers in 
our network) I'd like to set up EFI PXE boot for a simple Debian system. 
However, I have only been able to find very sparse and possibly outdated 
information on how to actually tell the kernel/initramfs to mount a NFS 
filesystem as filesystem root. I even asked Chatgpt, and it replied with its 
usual hallucinations, unable to provide real links to source of information.

This is what my TFTP root currently looks like:

├── grub
│   └── grub.cfg
├── grubnetx64.efi
├── initrd.img (Generic Debian Testing initrd.img)
└── vmlinuz (Generic Debian Testing vmlinuz)
(1 directory, 4 files)

And my NFS root currently isn't much more than the result of a Debian Stable 
debootstrap.

Do you have any tips and ideas on how to get Linux to mount that NFS root as 
the filesystem root?

Thanks in advance
Tuxifan

Re: Booting problem

[David Wright]

On Sun 13 Nov 2022 at 08:24:11 (+0530), Emilia Maher wrote:
> Hello,
> I have installed NetBeans through snapd process, as explained here:
> 
> https://wiki.debian.org/Netbeans
> 
> But after installation completed, I have faced booting problem.
> Then I have removed the snapd through terminal command as well I followed
> the instructions given here:
> https://wiki.debian.org/ReduceDebian#Remove_unnecessary_kernel_modules
> 
> To clear the unwanted packages but still I am facing the same booting
> problem.
> Please let me know what I can do to fix booting problem.

It might be an idea to explain what the nature of your booting problem is.

Cheers,
David.

Booting problem

[Emilia Maher]

Hello,
I have installed NetBeans through snapd process, as explained here:

https://wiki.debian.org/Netbeans

But after installation completed, I have faced booting problem.
Then I have removed the snapd through terminal command as well I followed
the instructions given here:
https://wiki.debian.org/ReduceDebian#Remove_unnecessary_kernel_modules

To clear the unwanted packages but still I am facing the same booting
problem.
Please let me know what I can do to fix booting problem.

Thanks and Regards

Re: PXE booting EFI client

[john doe]

On 9/7/2022 1:46 PM, Sven Hoexter wrote:

On Tue, Sep 06, 2022 at 07:21:59PM +0200, john doe wrote:

Debians,

I'm trying to pxe boot a client with UEFI BIOS to no avail.

Everything works with legacy BIOS but if I use those two lines in my
dnsmasq.conf:

"dhcp-boot=bootnetx64.efi
pxe-service=X86-64_EFI, "Boot UEFI PXE-64", bootnetx64.efi"


Maybe you've a host which sents as architecture "7" instead of
"9" via DHCP and this pxe-service is not matched at all. You
can figure that out if you look with wireshark at the DHCP traffic.
According to my notes the protocol option field is 93 you've to look at.
I ran into such an issue a few years back with HPE DL360G10 vs DL120G9.

Config setting to try out would be:
pxe-service=BC_EFI, "Boot UEFI PXE-64", bootnetx64.efi"



Thanks to the help of "Sven Hoexter ' I got it
working by doing:
/etc/dnsmasq.conf:
pxe-service=BC_EFI, "Boot UEFI PXE-64",
/debian-installer/amd64/bootnetx64.efi

I emulate the 'dhcp-boot' option in a option file:
option:bootfile-name,/debian-installer/amd64/bootnetx64.efi

I also had to put the below file in the tftp root directory:
grubx64.efi

Sven's blog [1] has more info on all of this.


[1] https://sven.stormbind.net/blog/posts/deb_stretch_hpe_dl360/

--
John Doe

Re: PXE booting EFI client

[Sven Hoexter]

On Tue, Sep 06, 2022 at 07:21:59PM +0200, john doe wrote:
> Debians,
> 
> I'm trying to pxe boot a client with UEFI BIOS to no avail.
> 
> Everything works with legacy BIOS but if I use those two lines in my
> dnsmasq.conf:
> 
> "dhcp-boot=bootnetx64.efi
> pxe-service=X86-64_EFI, "Boot UEFI PXE-64", bootnetx64.efi"

Maybe you've a host which sents as architecture "7" instead of
"9" via DHCP and this pxe-service is not matched at all. You
can figure that out if you look with wireshark at the DHCP traffic.
According to my notes the protocol option field is 93 you've to look at.
I ran into such an issue a few years back with HPE DL360G10 vs DL120G9.

Config setting to try out would be:
pxe-service=BC_EFI, "Boot UEFI PXE-64", bootnetx64.efi"

Sven

PXE booting EFI client

[john doe]

Debians,

I'm trying to pxe boot a client with UEFI BIOS to no avail.

Everything works with legacy BIOS but if I use those two lines in my
dnsmasq.conf:

"dhcp-boot=bootnetx64.efi
pxe-service=X86-64_EFI, "Boot UEFI PXE-64", bootnetx64.efi"


the client gets an IP but no file are sent.

I'm at a lost on what to do to PXE boot a EFI client.

Does PXE booting of EFI clients require other ports than 69 UDP and 4011
UDP?

Any pointers is appreciated.

--
John Doe

Re: booting 5.10 686-pae kernel on domU

[Tim Woodall]

On Mon, 5 Sep 2022, Andy Smith wrote:


Hello,

On Sun, Sep 04, 2022 at 01:54:16PM +0100, Tim Woodall wrote:

and remove pvshim=1


I think this was your issue. pvshim is PV-inside-PVH. So the
hypervisor that starts your guest kernel is in PV mode, which as
mentioned is not supported for 32-bit in newer Linux kernels.

Modern Linux kernels should either be run in PVH or HVM mode under
Xen. pvshim is strictly for older guests.



Yes, thanks. I understand now. I was actually running the 64 bit kernels
this way too - a bit of googling and I worked out that I should be using
the grub-i386-xen_pvh.bin kernel for 64 bit too.

The old pv grub kernel had to be different for i386 and amd64 but the
pvh grub kernel can be used for both - which simplifies things.

Thanks for your help - I was completely stuck and duckduckgo wasn't
giving me any clues but as soon as you said pv had been removed my
'enhanced' searching and experimenting put me on the right track.

Tim.

Re: booting 5.10 686-pae kernel on domU

[Andy Smith]

Hello,

On Sun, Sep 04, 2022 at 01:54:16PM +0100, Tim Woodall wrote:
> and remove pvshim=1

I think this was your issue. pvshim is PV-inside-PVH. So the
hypervisor that starts your guest kernel is in PV mode, which as
mentioned is not supported for 32-bit in newer Linux kernels.

Modern Linux kernels should either be run in PVH or HVM mode under
Xen. pvshim is strictly for older guests.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: booting 5.10 686-pae kernel on domU

[Tim Woodall]

On Sun, 4 Sep 2022, Andy Smith wrote:


Hello,

On Sun, Sep 04, 2022 at 11:07:35AM +0100, Tim Woodall wrote:

Should I be able to boot a 686-pae i686 kernel on a xen domU (bullseye -
but bookworm fails too)


The Linux kernel removed PV mode 32-bit Xen domU support at version
5.9. What type of virtualisation are you using? (show us your domain
config file from /etc/xen)

type=pvh should work. type=pv is not expected to work. I don't know
about type=hvm.


kernel="/usr/lib/grub-xen/grub-i386-xen.bin"
memory=256
name="test17"
type="pvh"
pvshim=1
disk=[ 
'script=block-iscsi,vdev=xvda,target=portal=xen17:3260,iqn=iqn.xen17:test17,w',
]
vif=[ 'bridge=xenbr0,mac=00:16:3e:e0:70:50',
]

But you've given me the clue I needed to fix it:
kernel="/usr/lib/grub-xen/grub-i386-xen_pvh.bin"

and remove pvshim=1


Thanks!


Making the domU multiarch and booting it with an amd64 kernel while
retaining the i686 userland should work.


Good idea.

Tim.

Re: booting 5.10 686-pae kernel on domU

[Andy Smith]

Hello,

On Sun, Sep 04, 2022 at 11:07:35AM +0100, Tim Woodall wrote:
> Should I be able to boot a 686-pae i686 kernel on a xen domU (bullseye -
> but bookworm fails too)

The Linux kernel removed PV mode 32-bit Xen domU support at version
5.9. What type of virtualisation are you using? (show us your domain
config file from /etc/xen)

type=pvh should work. type=pv is not expected to work. I don't know
about type=hvm.

Making the domU multiarch and booting it with an amd64 kernel while
retaining the i686 userland should work.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

booting 5.10 686-pae kernel on domU

[Tim Woodall]

Hi,

Should I be able to boot a 686-pae i686 kernel on a xen domU (bullseye -
but bookworm fails too)

(XEN) d46v0 Unhandled page fault fault/trap [#14, ec=0010]
(XEN) Pagetable walk from 0100:
(XEN)  L4[0x000] = 09790027 1f90
(XEN)  L3[0x000] = 097a4027 1fa4
(XEN)  L2[0x008] =  
(XEN) domain_crash_sync called from entry.S: fault at 82d040271ed8 
x86_64/compat/entry.S#compat_create_bounce_frame+0xd9/0xf6
(XEN) Domain 46 (vcpu#0) crashed on cpu#0:
(XEN) [ Xen-4.14.5  x86_64  debug=n   Not tainted ]
(XEN) CPU:0
(XEN) RIP:e019:[<0100>]
(XEN) RFLAGS: 0246   EM: 1   CONTEXT: pv guest (d46v0)
(XEN) rax: 0100   rbx:    rcx: 
(XEN) rdx:    rsi: c1f8d000   rdi: 0001
(XEN) rbp:    rsp: c20a5ff0   r8:  
(XEN) r9:     r10:    r11: 
(XEN) r12:    r13:    r14: 
(XEN) r15:    cr0: 8005003b   cr4: 001006e4
(XEN) cr3: 0f25b000   cr2: 0100
(XEN) fsb:    gsb:    gss: 
(XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
(XEN) Guest stack trace from esp=c20a5ff0:
(XEN)   0010 0100 0001e019 00010046    
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          
(XEN)          

This is a minimal install - I've now tried both as a fresh install and
upgrading from buster but I always get this same failure. The 4.19
buster kernel boots bullseye fine. Dom0 is bullseye.


I cannot find anybody else reporting this so either I'm doing something
wrong, doing something that is no longer supposed to work, or nobody is
using xen any more...


Assuming there isn't a simple solution, what do people think is the best
way forwards:

1. Convert to using KVM instead - this seems to be more popular now -
when I started using xen I don't think it even existed.

2. Convert my few remaining i686-pae images into amd64 images.

Will KVM boot a 686-pae kernel? If not then it seems I need to do 2
first anyway.


My processor says it supports VT-x although I don't see that in flags -
perhaps because I'm looking in a dom0? So changing to KVM might need new
hardware...


Tim.

Re: "Failed to start Create System Users" when booting Debian 10 rootfs from NFS mount.

[mj]

Hi,

A suggestion: we've had issues in the past, where on NFS root the issue 
was that setting "Linux Capabilities" (setcap) fails, because NFS does 
not support the extended attributes to store them.


Perhaps that is your issue as well?

MJ

Op 16-08-2022 om 21:58 schreef Lie Rock:

Hi,

I'm trying to bring up the Debian 10 root file system on an ARM SoC 
board. When the rootfs was in an SD card the board worked well. When I 
put the rootfs on an NFS server and tried to boot the board through NFS 
mount, it reported error through serial port:


|[FAILED] Failed to start Create System Users. See 'systemctl status 
systemd-sysusers.service' for details. |


And this is the only error message printed out. The board went all the 
way to login inputI, but I could not login with any of 
the preset accounts including root (because no users have been created 
as it suggested?), and I didn't see any way to run commands to check 
system status for details.


So how is the process "create system users" performed when Linux/Debian 
starts? What can be contributing to this error?


Any suggestions would be greatly appreciated.

Rock

Re: "Failed to start Create System Users" when booting Debian 10 rootfs from NFS mount.

[tomas]

On Tue, Aug 16, 2022 at 04:20:36PM -0400, Greg Wooledge wrote:
> On Tue, Aug 16, 2022 at 03:58:30PM -0400, Lie Rock wrote:
> > So how is the process "create system users" performed when Linux/Debian
> > starts? What can be contributing to this error?
> 
> unicorn:~$ grep -ri 'create system users' /lib/systemd
> /lib/systemd/system/systemd-sysusers.service:Description=Create System Users

[...]

Good research, and "thank you" from a systemd-abstainer, that's
my way to learn, after all :)

I'd contribute my hunch: perhaps systemd is trying to get sysusers
up "too early", before the root file system is pivoted-in?

Feeding my search engine with "NFS root" and +systemd turns up a
bunch of interesting suggestions (e.g. network has to be up before
NFS has to be mounted, etc:).

Good luck... and tell us what it was ;-)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: "Failed to start Create System Users" when booting Debian 10 rootfs from NFS mount.

[Greg Wooledge]

On Tue, Aug 16, 2022 at 03:58:30PM -0400, Lie Rock wrote:
> So how is the process "create system users" performed when Linux/Debian
> starts? What can be contributing to this error?

unicorn:~$ grep -ri 'create system users' /lib/systemd
/lib/systemd/system/systemd-sysusers.service:Description=Create System Users

unicorn:~$ systemctl cat systemd-sysusers.service
[...]
Documentation=man:sysusers.d(5) man:systemd-sysusers.service(8)
[...]
ExecStart=systemd-sysusers

unicorn:~$ man systemd-sysusers
[...]
   systemd-sysusers creates system users and groups, based on the file
   format and location specified in sysusers.d(5).

That's enough to get you started down the rabbit hole(s).  You should
also definitely check the logs on your system (e.g.
 journaltctl -u systemd-sysusers) to see what *exactly* went wrong.

"Failed to start Create System Users" when booting Debian 10 rootfs from NFS mount.

[Lie Rock]

Hi,

I'm trying to bring up the Debian 10 root file system on an ARM SoC board.
When the rootfs was in an SD card the board worked well. When I put the
rootfs on an NFS server and tried to boot the board through NFS mount, it
reported error through serial port:

[FAILED] Failed to start Create System Users.
See 'systemctl status systemd-sysusers.service' for details.

And this is the only error message printed out. The board went all the way
to login inputI, but I could not login with any of the preset accounts
including root (because no users have been created as it suggested?), and I
didn't see any way to run commands to check system status for details.

So how is the process "create system users" performed when Linux/Debian
starts? What can be contributing to this error?

Any suggestions would be greatly appreciated.

Rock

Re: booting from install usb

[Paul Scott]

On 5/9/22 14:19, Felix Miata wrote:

Paul Scott composed on 2022-05-09 12:25 (UTC-0700):


I let my laptop update its UEFI BIOS which of course zapped GRUB.

Not in the way you think...


/dev.sda2 which is "ef EFI (FAT-12/16/32)"

This should be the key, suggesting strongly that your Linux installation is
installed in UEFI mode.

That is correct.  I did install in UEFI mode.

If this is the case, you should be able to fix the problem
via BIOS setup, to select the (presumably Debian) entry that is probably there 
to
select as top priority.
After the BIOS update I mentioned the only boot choice was Windows which 
is why I figured some part of the GRUB stuff had been broken or deleted.

Alternatively, having executed mount -a after chrooting,
running efibootmgr should allow reorganizing the priority list to put your 
choice
at the top, or to add a new one if the one you need to be first is missing.

man efibootmgr


That didn't seem to work but as I was trying to figure out why I 
discovered I must have missed where rescue mode was telling me to mount 
the partition that must have had the EFI stuff I needed.  I can't give 
precise information but I was able to reinstall GRUB from Rescue mode 
and now all is well!


Thank you very much for your help,

Paul