Re: something seriously wrong with my bookworm install

[Michel Verdier]

On 2023-07-26, gene heskett wrote:

>> §5.1.7 indicates syslog (rsyslog) is not installed and is replaced by
>> journald (from systemd). You still can install rsyslog and
>> configure rsyslog/journald to get what you want where you want
>> 
> All the files in /var/log/journal/big hash subdir/* are digital trash, mostly
> $00
> and worthless for any human troubleshooting.  What is the big secret all
> about?

the secret is called journalctl -h

> A link to that file you are fond of quoting from sure would be nice...

a simple search obviously comes to this page, but as you seems to don't
know how to do a search here it is:
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#changes-to-system-logging

Re: something seriously wrong with my bookworm install

[tomas]

On Wed, Jul 26, 2023 at 06:03:02PM -0400, gene heskett wrote:
> On 7/26/23 16:42, Michel Verdier wrote:
> > On 2023-07-26, gene heskett wrote:
> > 
> > > > > So where are syslog and dmesg?
> > > > I take it you didn't bother to read §5.1.7 of the bookworm Release 
> > > > Notes.
> > > 
> > > Not yet David. [...]
> > 
> > §5.1.7 indicates syslog (rsyslog) is not installed and is replaced by
> > journald (from systemd). You still can install rsyslog and
> > configure rsyslog/journald to get what you want where you want
> > 
> All the files in /var/log/journal/big hash subdir/* are digital trash,
> mostly $00
> and worthless for any human troubleshooting.  What is the big secret all
> about?

Gene, this makes me furious. Really. Either you're lazy, don't read
docs and go with the default install -- and take what you get, or
you tinker, understand a bit of what you are doing and beat the system
into the shape you need/want/like it.

Defaults are bound to change from time to time, due to available
free programs, user base, maintainer community, yadda, yadda.

C'm on, you are a technician, you should know about such tradeoffs.

So going the lazy route /and/ publically ranting isn't helpful.

I dislike the whole systemd environment myself. Know what? My init
is SysV, my logs are clear text, all of that. With Debian Bullseye.
But it ain't the default, so it takes some reading, tinkering and
asking around.

I thank Debian and the maintainers every day for making that
possible!.

There are no secrets. Just engineering.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: How could a standalone python binary executable be made from a python script, to be run on other computers that don't have python installed?

[Susmita/Rajib]

From: Greg Wooledge 
Date: Wed, 26 Jul 2023 22:14:01 -0400
Message-id: <[🔎] zmhs6ajl2jzoi...@wooledge.org>
Mail-followup-to: debian-user@lists.debian.org
In-reply-to: <[🔎]
CAEG4cZXBJ3CbFUN1LuRQsKR=xjkzuw92lxlnrxwkxae-ery...@mail.gmail.com>
References: <[🔎]
CAEG4cZXe=BUQ5VE_z0rcLqHGGERdANnZ=vjiznjbk439jif...@mail.gmail.com>
and others

> On Thu, Jul 27, 2023 at 07:08:35AM +0530, Susmita/Rajib wrote:
>> I have considered myself as the 1st party. Debian universe as the 2nd
>> party and the rest as the 3rd party. So by my consideration, anything
>> 'Python' outside of the Debian Universe is 3rd party. I have rarely
>> install software outside of the Debian Universe.
>
> For Python development questions such as yours, you've got things
> upside down.

[   ...   ]

> Users on this mailing list are a wildcard.  Most people do not possess
> the detailed Python knowledge that you're requesting.  But if someone
> here happens to know Python development extremely well, they might have
> an answer for you.  This includes any pages on the Debian wiki, WHICH
> IS WRITTEN BY END USERS, not by the Debian project.

I totally am in full agreement with what you say, Mr. Wooledge.

But I am unsure whether will my poor system be able to cope with virtualisation.

Is there something called a bare minimum virtualisation, where only
the python environment could be in a 'cage', isolated from the rest
system, so that irrespective of the virtual environment resides or is
removed the system remains in its pristine state?

I have considered creating a new 'user' and installing various python
packages there. But that doesn't happen. There are components that
install with 'root-level' privileges. They can't be removed by just
removing the 'user'.

I have HDD space for a new installation. But a fresh installation takes time.

Two decades back, in 2003, I had bought a software called Acronis OS
selector. It was Version 6, probably. It could duplicate an
installation in just minutes and I could boot from that duplicate OS
with a separate boot menu it also created. Or keep the copied system
as a snapshot/backup. From the feel I could clearly make out that it
was based on Unix(or Linux)-type OS.

Whole partitions could be moved, resized, manipulated, ..., almost
anything one could imagine!

I am unsure if Debian has something like that. Would have solved these problems.

Re: How could a standalone python binary executable be made from a python script, to be run on other computers that don't have python installed?

[David Wright]

On Thu 27 Jul 2023 at 07:08:35 (+0530), Susmita/Rajib wrote:
> From: David Wright 
> Date: Wed, 26 Jul 2023 12:22:04 -0500
> > On Mon 24 Jul 2023 at 15:52:38 (+0530), Susmita/Rajib wrote:
> >> Thank you for writing back with the link leading to the Python
> >> Discourse thread. [ … ]
> >> Can't accept a third party website info on face value.
> >
> > PEPs are official Python documents; the one I referred to
> > is an Accepted (as of June last year) Standards Track.
> >
> >> I would have preferred a similar post assuring us
> >> from the Debian Side. A 3rd party software installer from within the
> >> native Debian
> >> system for which there isn't an explicit assurance from Debian is
> >> unsettling.
> >
> > I'm not sure who you think the first and second parties are.
> [   ...   ]
> 
> I have considered myself as the 1st party. Debian universe as the 2nd
> party and the rest as the 3rd party. So by my consideration, anything
> 'Python' outside of the Debian Universe is 3rd party. I have rarely
> install software outside of the Debian Universe.

As one of the two parties, what is it that you're offering? And from
where in the "Debian Universe" are you expecting something in return?
(A universe can hardly be said to be a party to anything.)

Cheers,
David.

Re: something seriously wrong with my bookworm install

[Felix Miata]

gene heskett composed on 2023-07-26 18:03 (UTC-0400):

> All the files in /var/log/journal/big hash subdir/* are digital trash, 
> mostly $00
> and worthless for any human troubleshooting.  What is the big secret all 
> about?

That big hash is there for at least one good reason: good tools are built into
journalctl for accessing those binaries, so there's no good reason to dive
directly into their content. e.g., journalctl -b opens the complete log for the
current boot, in a modern pager equivalent to less. If MH doesn't like less, it
only takes a second or so extra to redirect whatever of its content pleases MH 
to
>whateverfilenamepleasesMH so MH can open it in whatever text/log file peruser 
>he
likes better. Meanwhile you might peruse the journalctl man page to see all the
neat ways to extract subsets of its contents. I don't have to guess which log(S)
to look in when I need something any more since systemd brought us journalctl. I
like that digital blob setup, and I'm only about 2^4 years younger than you.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: How could a standalone python binary executable be made from a python script, to be run on other computers that don't have python installed?

[Greg Wooledge]

On Thu, Jul 27, 2023 at 07:08:35AM +0530, Susmita/Rajib wrote:
> I have considered myself as the 1st party. Debian universe as the 2nd
> party and the rest as the 3rd party. So by my consideration, anything
> 'Python' outside of the Debian Universe is 3rd party. I have rarely
> install software outside of the Debian Universe.

For Python development questions such as yours, you've got things
upside down.

The upstream Python developers are the primary source of knowledge.
This includes most web sites in the python.org domain.  If what you
want to achieve is documented by the Python developers on python.org
then you're all set.

The Python community, including Python mailing lists, IRC channels, web
forums and so on, would be your secondary source.  Other Python users
might have done what you're trying to do.  Those people would most likely
be found in the Python community, rather than here.

The Debian Python maintainer(s) might be a tertiary source at best.
This includes official Debian publications such as Release Notes.
However, your question is so incredibly specific and esoteric that it's
not likely to be covered by any such documents.  It never comes up during
a Debian installation or upgrade, because it's a product developer's
question, not a system administrator's question.

Users on this mailing list are a wildcard.  Most people do not possess
the detailed Python knowledge that you're requesting.  But if someone
here happens to know Python development extremely well, they might have
an answer for you.  This includes any pages on the Debian wiki, WHICH
IS WRITTEN BY END USERS, not by the Debian project.

Re: How could a standalone python binary executable be made from a python script, to be run on other computers that don't have python installed?

[Susmita/Rajib]

From: David Wright 
Date: Wed, 26 Jul 2023 12:22:04 -0500
Message-id: <[🔎] zmfwpfrxuvr5g...@axis.corp>
Reply-to: debian-user@lists.debian.org
In-reply-to: <[🔎]
CAEG4cZXy=0lra4adonsaueeoafdyapoqf5cze3s1zerrjfs...@mail.gmail.com>
References: <[🔎]
CAEG4cZXe=BUQ5VE_z0rcLqHGGERdANnZ=vjiznjbk439jif...@mail.gmail.com>


<[🔎] CAEG4cZXy=0lra4adonsaueeoafdyapoqf5cze3s1zerrjfs...@mail.gmail.com>

> On Mon 24 Jul 2023 at 15:52:38 (+0530), Susmita/Rajib wrote:
>> From: David Wright 
>> Date: Thu, 20 Jul 2023 10:06:43 -0500
>>
>> Thank you for writing back with the link leading to the Python
>> Discourse thread. [ … ]
>> Can't accept a third party website info on face value.
>
> PEPs are official Python documents; the one I referred to
> is an Accepted (as of June last year) Standards Track.
>
>> I would have preferred a similar post assuring us
>> from the Debian Side. A 3rd party software installer from within the
>> native Debian
>> system for which there isn't an explicit assurance from Debian is
>> unsettling.
>
> I'm not sure who you think the first and second parties are.
[   ...   ]

I have considered myself as the 1st party. Debian universe as the 2nd
party and the rest as the 3rd party. So by my consideration, anything
'Python' outside of the Debian Universe is 3rd party. I have rarely
install software outside of the Debian Universe.

[   ...   ]
> Debian is a distribution, not a software company. The best
> you can expect from Debian is what I gave you: the Release
> Notes for bookworm.¹ Debian offers no guarantees, and you're
> reminded of this every time you login:
>
>  "Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY,
>   to the extent permitted by applicable law."
[   ...   ]

Yes, I have acknowledged and thanked you for your post. But we are not
travelling in that direction presently.

[   ...   ]
>> I could have risked if a Debian system snapshot could be
>> saved and in case of any trouble, could be reverted back to.
>>
>> Yes, a virtual environment (i.e., virtualisation) however is an idea
>> that could theoretically be looked into, but that would mean extra
>> system resources to be spent for it.
>
> AIUI a standalone binary is bound to use more resources anyway,
> because it duplicates some already supplied as part of the OS.
[   ...   ]

A virtualisation environment is huge in terms of memory, RAM, HDD or
CPU usages. But let us not discuss on this aspect presently. I want to
build a standalone binaries and give it to a kid who runs Doze. He
doesn't have 'python' environment installed. I am trying to assist
him.

[   ...   ]
>
> ¹ As you later wrote: "something published as the Debian Wiki, Release
>   Notes, Debian GNU/Linux FAQ or other informative posts or webpages
>   that could help disseminate information about issues that matter."
[   ...   ]

Re: something seriously wrong with my bookworm install

[gene heskett]

On 7/26/23 18:13, David Wright wrote:

On Wed 26 Jul 2023 at 15:03:55 (-0400), gene heskett wrote:

On 7/26/23 10:32, David Wright wrote:

On Wed 26 Jul 2023 at 10:07:34 (-0400), gene heskett wrote:

And since bookworm has shut down, or moved, all the logs that might
keep track of this, I'm lost. What can I do to trace or fix the reason
for this denial of service? I know zip about your new ACL stuff if
thats even involved. IDK.  Is there a special version of chown for
raid arrays?
And where the heck are the logs, they should be in the /var directory
of the drive its booted from which s/b /dev/sda, but df thinks its:
now /dev/sda, last boot it was /dev/sdb, so much for UUID's. I have
not moved any cables. One is a 500G samsung 860 SSD, the other a 1t
Samsung 870 SSD.
An ls of /var/log:
gene@coyote:~$ ls /var/log
alternatives.logapache2  boot.logboot.log.2  boot.log.4  btmp
cups  dpkg.log.1  faillog gdm3   journal  private
runit  sddm.log   wtmp
alternatives.log.1  apt  boot.log.1  boot.log.3  boot.log.5
btmp.1 dpkg.log  exim4   fontconfig.log  installer  lastlog
README   samba
speech-dispatcher

So where are syslog and dmesg?


I take it you didn't bother to read §5.1.7 of the bookworm Release Notes.


Not yet David. I was forced to install bookworm after an update wiped
out the validity of my pw. So I went to another machine on my net and
downloaded and  wrote a dvd with the bookworm netinstall. so at no
time was I presented with an opportunity to read the release notes.


It's a long time since the dog ate my homework. Anyway, dmesg
hasn't gone anywhere as it's in util-linux, a Required package.
Typing journalctl will give you the journal in full AIUI, but
you can add -b to limit it to this boot. man journalctl has more
options; the Release Notes prefer -e for showing the last 1000 lines.


This to me, is not a toy,   And that's not the first time my pw has
been invalidated by an update. No root pw has ever been set since
wheezy, so I had no choice but to install either bookworm or wheezy as
I seem to have misslaid the diskj for the in betweens.


I don't know why you don't use a root password. It's never seemed
a sensible choice to me, so I always say yes during installation.


Wheezy thru buster has been good to me, bullseye was troublesome but
fixable, now bookworm is a disaster. The applications I use daily act
like they don't have write perms to storage I own lock stock and
barrel.  The logs I might use to troubleshoot this myself are gone,
and you want to know if I read the release notes?  So I come here
asking for help with all the changes and catch it for not reading the
notes i never had the chance to read.


You're an experienced user. I think you've been running bookworm
(or trying to) for about three weeks? It takes four clicks from
the Debian home page to read them (or download them as a PDF).
And however wheezy was, once it settled down, installing it led
to long threads here through 2015, about how broken it was.


I ask how to do an fsck on it which might fix whatever changes
bookworm has done to ext4. One possibility is to comment that line
that mounts it out of fstab and reboot. But alluding to that before
has been ignored.


It's still as it was in:

   https://lists.debian.org/debian-user/2017/10/msg00399.html

ie forcefsck on the kernel line when you boot, though I'm lazy,
and understand that forcefsck's Sunday name is fsck.mode=force.

Cheers,
David.

Thanks David, although I fail to connect Sunday to that. ;o)>  I'll do 
that on the next reboot, which since its bookworm will likely be well 
before Sunday. There are other problems, like an unused konsole losing 
its bash, so I have to close the window and run a new one.

.


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: How to create /home BTRFS subvolume on a second disk during installation?

[Erick Delgado]

> El jul. 26, 2023, a la(s) 17:07, debian-u...@howorth.org.uk escribió:
> 
> On Wed, 26 Jul 2023 16:27:54 -0400
> Erick Delgado  wrote:
> 
>> Unfortunately I am unable to provide the output by text since I am
>> only able to login via tty2. I can take a photo of it and send it.
>> Will that be okay?
> 
> Please keep the conversation on list.
> And please don't top post.
> 
> I'd assumed you knew pretty much what you were doing, since you're
> trying a somewhat unusual installation for Debian. You can post a photo
> somewhere if you need to and post a link to the mailing list.
> 
>>> El jul. 26, 2023, a la(s) 16:04, debian-u...@howorth.org.uk escribió:
>>> 
>>> Erick Delgado  wrote:  
 Dear Debian users and developers,
 I would like to know if it’s possible to create the /home BTRFS
 subvolume on a second disk (nvme, etc.) during expert installation?
 If so, how? The reason I ask is because I was following this YouTube
 video (https://youtu.be/MoWApyUb5w8) and I have tried to do the
 partition table first (/ on first disk and the /home on the second
 disk, both BTRFS), then Ctrl + Alt + F2 to the Debian installer
 shell to create some BTRFS subvolumes on the first disk similar as
 in the video. The subvolumes for the first disk that I created were
 @ (for /root), @cache, @log, and @tmp.  
>>> 
>>> Err I haven't looked at the video but I think the @ subvolume should
>>> be for / (i.e. the root directory) rather than for /root (i.e.
>>> root's home directory). The latter is just a normal directory in the
>>> former. 
 After I finish, I proceed to do
 a minimal installation of Debian. Once I reboot after the complete
 installation and login through terminal I get a message that HOME is
 not found and sets HOME=/ (which is very odd since the partition was
 done). I tried to install the minimal KDE Plasma and tried to login
 to see what occurs. But can’t login to the desktop because it takes
 me right back to the login screen. Can someone please help me on
 this?
 
 Thank you for your time and help.  
>>> 
>>> Maybe after you boot you could run e.g. df -hT and post the output
>>> here. 
> 
My sincere apologies. I did not notice that the conversation was not on the 
list.
Here is a photo link of my df -hT as requested > 
https://drive.google.com/file/d/1xaJ8kyPGMYY32H2cG_pipuwYjXYQQxhn/view?usp=drivesdk

Thank you for your time and help.

Re: General Questions

[David Wright]

On Tue 25 Jul 2023 at 08:18:21 (-0400), Greg Wooledge wrote:
> On Tue, Jul 25, 2023 at 07:53:52AM -0400, Dan Ritter wrote:
> > Source Code wrote: 
> > > 3. Is it possible to reduce RAM consumption? And minimize it? Let's say up
> > > to 100-200 mb?
> > 
> > That depends on what you choose to run, and how. I would not
> > recommend trying to do anything interesting on a machine with
> > less than 256MB of RAM. That will not be enough for many common
> > uses.
> 
> According to 
> 256 MB is the absolute minimum amount of RAM for installing bookworm
> on an AMD64 machine, using the text installer and no GUI packages.

The numbers on that page look rather suspect (as unchanged since
bullseye) and inconsistent ("With swap enabled, it is possible to
install Debian with as little as 350MB").

But that said, I have installed bookworm (standard system utilities
& SSH server) on a 512MB i386 laptop with no swap. (I add the 1GB
encrypted swap later.) I gave up trying to run Firefox since buster,
but that's more to do with FF versions rather than Debian, I think.

Cheers,
David.

Re: something seriously wrong with my bookworm install

[David Wright]

On Wed 26 Jul 2023 at 15:03:55 (-0400), gene heskett wrote:
> On 7/26/23 10:32, David Wright wrote:
> > On Wed 26 Jul 2023 at 10:07:34 (-0400), gene heskett wrote:
> > > And since bookworm has shut down, or moved, all the logs that might
> > > keep track of this, I'm lost. What can I do to trace or fix the reason
> > > for this denial of service? I know zip about your new ACL stuff if
> > > thats even involved. IDK.  Is there a special version of chown for
> > > raid arrays?
> > > And where the heck are the logs, they should be in the /var directory
> > > of the drive its booted from which s/b /dev/sda, but df thinks its:
> > > now /dev/sda, last boot it was /dev/sdb, so much for UUID's. I have
> > > not moved any cables. One is a 500G samsung 860 SSD, the other a 1t
> > > Samsung 870 SSD.
> > > An ls of /var/log:
> > > gene@coyote:~$ ls /var/log
> > > alternatives.logapache2  boot.logboot.log.2  boot.log.4  btmp
> > > cups  dpkg.log.1  faillog gdm3   journal  private
> > > runit  sddm.log   wtmp
> > > alternatives.log.1  apt  boot.log.1  boot.log.3  boot.log.5
> > > btmp.1 dpkg.log  exim4   fontconfig.log  installer  lastlog
> > > README   samba
> > > speech-dispatcher
> > > 
> > > So where are syslog and dmesg?
> > 
> > I take it you didn't bother to read §5.1.7 of the bookworm Release Notes.
> 
> Not yet David. I was forced to install bookworm after an update wiped
> out the validity of my pw. So I went to another machine on my net and
> downloaded and  wrote a dvd with the bookworm netinstall. so at no
> time was I presented with an opportunity to read the release notes.

It's a long time since the dog ate my homework. Anyway, dmesg
hasn't gone anywhere as it's in util-linux, a Required package.
Typing journalctl will give you the journal in full AIUI, but
you can add -b to limit it to this boot. man journalctl has more
options; the Release Notes prefer -e for showing the last 1000 lines.

> This to me, is not a toy,   And that's not the first time my pw has
> been invalidated by an update. No root pw has ever been set since
> wheezy, so I had no choice but to install either bookworm or wheezy as
> I seem to have misslaid the diskj for the in betweens.

I don't know why you don't use a root password. It's never seemed
a sensible choice to me, so I always say yes during installation.

> Wheezy thru buster has been good to me, bullseye was troublesome but
> fixable, now bookworm is a disaster. The applications I use daily act
> like they don't have write perms to storage I own lock stock and
> barrel.  The logs I might use to troubleshoot this myself are gone,
> and you want to know if I read the release notes?  So I come here
> asking for help with all the changes and catch it for not reading the
> notes i never had the chance to read.

You're an experienced user. I think you've been running bookworm
(or trying to) for about three weeks? It takes four clicks from
the Debian home page to read them (or download them as a PDF).
And however wheezy was, once it settled down, installing it led
to long threads here through 2015, about how broken it was.

> I ask how to do an fsck on it which might fix whatever changes
> bookworm has done to ext4. One possibility is to comment that line
> that mounts it out of fstab and reboot. But alluding to that before
> has been ignored.

It's still as it was in:

  https://lists.debian.org/debian-user/2017/10/msg00399.html

ie forcefsck on the kernel line when you boot, though I'm lazy,
and understand that forcefsck's Sunday name is fsck.mode=force.

Cheers,
David.

Re: something seriously wrong with my bookworm install

[gene heskett]

On 7/26/23 16:42, Michel Verdier wrote:

On 2023-07-26, gene heskett wrote:


So where are syslog and dmesg?

I take it you didn't bother to read §5.1.7 of the bookworm Release Notes.


Not yet David. [...]


§5.1.7 indicates syslog (rsyslog) is not installed and is replaced by
journald (from systemd). You still can install rsyslog and
configure rsyslog/journald to get what you want where you want

All the files in /var/log/journal/big hash subdir/* are digital trash, 
mostly $00
and worthless for any human troubleshooting.  What is the big secret all 
about?


A link to that file you are fond of quoting from sure would be nice...

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: Are there Nvidia drivers on Trixie repositories right now ?

[Greg Wooledge]

On Wed, Jul 26, 2023 at 11:15:13PM +0200, rudu wrote:
> Thank you David, but I thought that non-free-firmware should be enough for
> the new testing repositories.
> Should I had "non-free" to "main contrib non-free-firmware" ?
> Sounds weird to me ... ??

The non-free-firmware section only contains firmware.  Not drivers.

If you need to build non-free drivers (e.g. nvidia) you'll need both
sections.

Re: Are there Nvidia drivers on Trixie repositories right now ?

[rudu]

Le 26/07/2023 à 17:12, David Wright a écrit :

# cat /etc/apt/sources.list
# deb cdrom:[Debian GNU/Linux testing_Bookworm_  - Official Snapshot
amd64 NETINST 20221031-03:18]/ bookworm main

#deb cdrom:[Debian GNU/Linux testing_Bookworm_  - Official Snapshot
amd64 NETINST 20221031-03:18]/ bookworm main

debhttp://ftp.fr.debian.org/debian  trixie main contrib non-free-firmware
deb-srchttp://ftp.fr.debian.org/debian  trixie main contrib
non-free-firmware

debhttp://ftp.fr.debian.org/debian-security/  trixie-security main
contrib non-free-firmware
deb-srchttp://ftp.fr.debian.org/debian-security/  trixie-security main
contrib non-free-firmware

debhttp://ftp.fr.debian.org/debian  trixie-updates main contrib
non-free-firmware
deb-srchttp://ftp.fr.debian.org/debian  trixie-updates main contrib
non-free-firmware

You appear to be lacking non-free in your sources.list.

Cheers,
David.
Thank you David, but I thought that non-free-firmware should be enough 
for the new testing repositories.

Should I had "non-free" to "main contrib non-free-firmware" ?
Sounds weird to me ... ??

Rudu

Re: How to create /home BTRFS subvolume on a second disk during installation?

[debian-user]

On Wed, 26 Jul 2023 16:27:54 -0400
Erick Delgado  wrote:

>Unfortunately I am unable to provide the output by text since I am
>only able to login via tty2. I can take a photo of it and send it.
>Will that be okay?

Please keep the conversation on list.
And please don't top post.

I'd assumed you knew pretty much what you were doing, since you're
trying a somewhat unusual installation for Debian. You can post a photo
somewhere if you need to and post a link to the mailing list.

>> El jul. 26, 2023, a la(s) 16:04, debian-u...@howorth.org.uk escribió:
>> 
>> Erick Delgado  wrote:  
>>> Dear Debian users and developers,
>>> I would like to know if it’s possible to create the /home BTRFS
>>> subvolume on a second disk (nvme, etc.) during expert installation?
>>> If so, how? The reason I ask is because I was following this YouTube
>>> video (https://youtu.be/MoWApyUb5w8) and I have tried to do the
>>> partition table first (/ on first disk and the /home on the second
>>> disk, both BTRFS), then Ctrl + Alt + F2 to the Debian installer
>>> shell to create some BTRFS subvolumes on the first disk similar as
>>> in the video. The subvolumes for the first disk that I created were
>>> @ (for /root), @cache, @log, and @tmp.  
>> 
>> Err I haven't looked at the video but I think the @ subvolume should
>> be for / (i.e. the root directory) rather than for /root (i.e.
>> root's home directory). The latter is just a normal directory in the
>> former. 
>>> After I finish, I proceed to do
>>> a minimal installation of Debian. Once I reboot after the complete
>>> installation and login through terminal I get a message that HOME is
>>> not found and sets HOME=/ (which is very odd since the partition was
>>> done). I tried to install the minimal KDE Plasma and tried to login
>>> to see what occurs. But can’t login to the desktop because it takes
>>> me right back to the login screen. Can someone please help me on
>>> this?
>>> 
>>> Thank you for your time and help.  
>> 
>> Maybe after you boot you could run e.g. df -hT and post the output
>> here. 

Re: something seriously wrong with my bookworm install

[Michel Verdier]

On 2023-07-26, gene heskett wrote:

>>> So where are syslog and dmesg?
>> I take it you didn't bother to read §5.1.7 of the bookworm Release Notes.
>
> Not yet David. [...]

§5.1.7 indicates syslog (rsyslog) is not installed and is replaced by
journald (from systemd). You still can install rsyslog and
configure rsyslog/journald to get what you want where you want

Re: How to create /home BTRFS subvolume on a second disk during installation?

[debian-user]

Erick Delgado  wrote:
> Dear Debian users and developers,
> I would like to know if it’s possible to create the /home BTRFS
> subvolume on a second disk (nvme, etc.) during expert installation?
> If so, how? The reason I ask is because I was following this YouTube
> video (https://youtu.be/MoWApyUb5w8) and I have tried to do the
> partition table first (/ on first disk and the /home on the second
> disk, both BTRFS), then Ctrl + Alt + F2 to the Debian installer shell
> to create some BTRFS subvolumes on the first disk similar as in the
> video. The subvolumes for the first disk that I created were @
> (for /root), @cache, @log, and @tmp.

Err I haven't looked at the video but I think the @ subvolume should be
for / (i.e. the root directory) rather than for /root (i.e. root's home
directory). The latter is just a normal directory in the former.

> After I finish, I proceed to do
> a minimal installation of Debian. Once I reboot after the complete
> installation and login through terminal I get a message that HOME is
> not found and sets HOME=/ (which is very odd since the partition was
> done). I tried to install the minimal KDE Plasma and tried to login
> to see what occurs. But can’t login to the desktop because it takes
> me right back to the login screen. Can someone please help me on this?
> 
> Thank you for your time and help.

Maybe after you boot you could run e.g. df -hT and post the output here.

How to create /home BTRFS subvolume on a second disk during installation?

[Erick Delgado]

Dear Debian users and developers,
I would like to know if it’s possible to create the /home BTRFS subvolume on a 
second disk (nvme, etc.) during expert installation? If so, how?
The reason I ask is because I was following this YouTube video 
(https://youtu.be/MoWApyUb5w8) and I have tried to do the partition table first 
(/ on first disk and the /home on the second disk, both BTRFS), then Ctrl + Alt 
+ F2 to the Debian installer shell to create some BTRFS subvolumes on the first 
disk similar as in the video. 
The subvolumes for the first disk that I created were @ (for /root), @cache, 
@log, and @tmp.
After I finish, I proceed to do a minimal installation of Debian. Once I reboot 
after the complete installation and login through terminal I get a message that 
HOME is not found and sets HOME=/ (which is very odd since the partition was 
done). I tried to install the minimal KDE Plasma and tried to login to see what 
occurs. But can’t login to the desktop because it takes me right back to the 
login screen.
Can someone please help me on this?

Thank you for your time and help.

Re: something seriously wrong with my bookworm install

[gene heskett]

On 7/26/23 10:32, David Wright wrote:

On Wed 26 Jul 2023 at 10:07:34 (-0400), gene heskett wrote:

And since bookworm has shut down, or moved, all the logs that might
keep track of this, I'm lost. What can I do to trace or fix the reason
for this denial of service? I know zip about your new ACL stuff if
thats even involved. IDK.  Is there a special version of chown for
raid arrays?
And where the heck are the logs, they should be in the /var directory
of the drive its booted from which s/b /dev/sda, but df thinks its:
now /dev/sda, last boot it was /dev/sdb, so much for UUID's. I have
not moved any cables. One is a 500G samsung 860 SSD, the other a 1t
Samsung 870 SSD.
An ls of /var/log:
gene@coyote:~$ ls /var/log
alternatives.logapache2  boot.logboot.log.2  boot.log.4  btmp
cups  dpkg.log.1  faillog gdm3   journal  private
runit  sddm.log   wtmp
alternatives.log.1  apt  boot.log.1  boot.log.3  boot.log.5
btmp.1 dpkg.log  exim4   fontconfig.log  installer  lastlog
README   samba
speech-dispatcher

So where are syslog and dmesg?


I take it you didn't bother to read §5.1.7 of the bookworm Release Notes.

Cheers,
David.


Not yet David. I was forced to install bookworm after an update wiped 
out the validity of my pw. So I went to another machine on my net and 
downloaded and  wrote a dvd with the bookworm netinstall. so at no time 
was I presented with an opportunity to read the release notes. This to 
me, is not a toy,   And that's not the first time my pw has been 
invalidated by an update. No root pw has ever been set since wheezy, so 
I had no choice but to install either bookworm or wheezy as I seem to 
have misslaid the diskj for the in betweens. I got the bookworm 
net-installer by taking my portable dvd writer to the buster machine and 
writing it there, then bring it back to install on this machine after I 
had crawled under the table and unplugged al the drives but the one I 
wanted to install to.  They've since been plugged back in and the /home 
partition on that raid10 is mounted on top of the almost empty /home on 
the boot drive.  Its all SSD's since the last 2 2t seacrates I bought 
for buster, one for working room on /home, and one for amanda only ran a 
few weeks, both just disappearing off the end of the cables with no 
warning in the same d## week.  Since my main working sw on this 
machine is much newer AppImages, they all live in /home/me/AppIages on 
that raid. So when the raid10 was created, I had only  3 or 4 files for 
backup, so I have about half of a 25 year collection of pix I was able 
to recover from the amandatapes disk before it puked 3 days after the 
new buster boot disk failed. At that point I didn't ever consider 
warratying an obviously sold 6 months before the bugs were fixed for 
shingled drives, so the next time it was powered up it had an 8 inch 
stack of Samsung SSD's and no spinning rust.  Every SSD including the 
first 40 gig adak I ever bought is still working just fine in one of the 
7 machines here.


Wheezy thru buster has been good to me, bullseye was troublesome but 
fixable, now bookworm is a disaster. The applications I use daily act 
like they don't have write perms to storage I own lock stock and barrel. 
 The logs I might use to troubleshoot this myself are gone, and you 
want to know if I read the release notes?  So I come here asking for 
help with all the changes and catch it for not reading the notes i never 
had the chance to read.


I don't have a place, nor the slot left for another controller, nor the 
spare disks to save that raids data to while its being reformatted for 
bookworm.


I ask how to do an fsck on it which might fix whatever changes bookworm 
has done to ext4. One possibility is to comment that line that mounts it 
out of fstab and reboot. But alluding to that before has been ignored.


Or if a 2T SSD is affordable, I do have a spare sata-iii socket left on 
the mobo. And 2 empty sockets on the controller serving the raid10.


I see they've come down a ways for off brand stuff, so 3 2T's will be 
here friday. I think I have, between the 2 controllers, each with 6 
ports, enough empty sockets to setup a volume managed something, maybe 
even another 2nd raid10.


So I should have a place to put the raids contents if a reformatting is 
indicated.




.


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: How could a standalone python binary executable be made from a python script, to be run on other computers that don't have python installed?

[David Wright]

On Mon 24 Jul 2023 at 15:52:38 (+0530), Susmita/Rajib wrote:
> From: David Wright 
> Date: Thu, 20 Jul 2023 10:06:43 -0500
> 
> Thank you for writing back with the link leading to the Python
> Discourse thread. [ … ]
> Can't accept a third party website info on face value.

PEPs are official Python documents; the one I referred to
is an Accepted (as of June last year) Standards Track.

> I would have preferred a similar post assuring us
> from the Debian Side. A 3rd party software installer from within the native 
> Debian
> system for which there isn't an explicit assurance from Debian is
> unsettling.

I'm not sure who you think the first and second parties are.
Debian is a distribution, not a software company. The best
you can expect from Debian is what I gave you: the Release
Notes for bookworm.¹ Debian offers no guarantees, and you're
reminded of this every time you login:

 "Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY,
  to the extent permitted by applicable law."

> I could have risked if a Debian system snapshot could be
> saved and in case of any trouble, could be reverted back to.
> 
> Yes, a virtual environment (i.e., virtualisation) however is an idea
> that could theoretically be looked into, but that would mean extra
> system resources to be spent for it.

AIUI a standalone binary is bound to use more resources anyway,
because it duplicates some already supplied as part of the OS.

¹ As you later wrote: "something published as the Debian Wiki, Release
  Notes, Debian GNU/Linux FAQ or other informative posts or webpages
  that could help disseminate information about issues that matter."

Cheers,
David.

Re: Error: no such device

[Michael Kjörling]

On 26 Jul 2023 07:43 -0400, from s.mol...@sbcglobal.net:
> I just tried to boot
> into the new OS and it booted!!! After bumbling luck on my part, but I'll
> take it.

In that case, you may want to run `sudo update-grub` from within the
system that boots. Doing so will rewrite the GRUB configuration files.

-- 
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: Are there Nvidia drivers on Trixie repositories right now ?

[David Wright]

On Wed 26 Jul 2023 at 15:39:49 (+0200), rudu wrote:
> Switching from the nouveau driver to some nvidia-driver does not seam
> to be possible on my laptop running Debian Testing/Trixie.
> Now, it can be found right here apparently :
> https://packages.debian.org/trixie/nvidia-driver
> Am I missing something ?

> # cat /etc/apt/sources.list
> # deb cdrom:[Debian GNU/Linux testing _Bookworm_ - Official Snapshot
> amd64 NETINST 20221031-03:18]/ bookworm main
> 
> #deb cdrom:[Debian GNU/Linux testing _Bookworm_ - Official Snapshot
> amd64 NETINST 20221031-03:18]/ bookworm main
> 
> deb http://ftp.fr.debian.org/debian trixie main contrib non-free-firmware
> deb-src http://ftp.fr.debian.org/debian trixie main contrib
> non-free-firmware
> 
> deb http://ftp.fr.debian.org/debian-security/ trixie-security main
> contrib non-free-firmware
> deb-src http://ftp.fr.debian.org/debian-security/ trixie-security main
> contrib non-free-firmware
> 
> deb http://ftp.fr.debian.org/debian trixie-updates main contrib
> non-free-firmware
> deb-src http://ftp.fr.debian.org/debian trixie-updates main contrib
> non-free-firmware

You appear to be lacking non-free in your sources.list.

Cheers,
David.

Re: something seriously wrong with my bookworm install

[David Wright]

On Wed 26 Jul 2023 at 10:07:34 (-0400), gene heskett wrote:
> And since bookworm has shut down, or moved, all the logs that might
> keep track of this, I'm lost. What can I do to trace or fix the reason
> for this denial of service? I know zip about your new ACL stuff if
> thats even involved. IDK.  Is there a special version of chown for
> raid arrays?
> And where the heck are the logs, they should be in the /var directory
> of the drive its booted from which s/b /dev/sda, but df thinks its:
> now /dev/sda, last boot it was /dev/sdb, so much for UUID's. I have
> not moved any cables. One is a 500G samsung 860 SSD, the other a 1t
> Samsung 870 SSD.
> An ls of /var/log:
> gene@coyote:~$ ls /var/log
> alternatives.logapache2  boot.logboot.log.2  boot.log.4  btmp
> cups  dpkg.log.1  faillog gdm3   journal  private
> runit  sddm.log   wtmp
> alternatives.log.1  apt  boot.log.1  boot.log.3  boot.log.5
> btmp.1 dpkg.log  exim4   fontconfig.log  installer  lastlog
> README   samba
> speech-dispatcher
> 
> So where are syslog and dmesg?

I take it you didn't bother to read §5.1.7 of the bookworm Release Notes.

Cheers,
David.

something seriously wrong with my bookworm install

[gene heskett]

1. about half the time, opening a file requestor from a AppImage program 
which includes DigiKam 8.2.0 from the July 24th build, Ultimaker-cura 
5.4.0, OpenSCAD, latest AppImage often takes a minute or more after I've 
clicked the mouse.


2. digiKam cannot access to write, stuff it can see in the camera, and 
no errors are reported other than the popup attached. Which comes up 
instantly, no time lag involved.
3. OpenSCAD and Cura may save 10 times, or may not the next time, be 
subjected to this 1 minute or more lag.


This on a system with 32 gigs of dram that is currently 0/107 gigs of 
swap according to htop.  With 1.99/31.2 of used memory.


/home is a nearly 2t raid10 that was formatted ext4, last under buster. 
mouunted in fstab:
UUID=bc6135de-0578-4e3b-b2c0-5c4687abd9bd /home ext4 errors=remount-ro 
0   1


I've tried to induce an fsck (the final 1 above) without visible success 
while booting, And I've gone into the Pictures and Photo subdirs and exec'd:

sudo chown -R me:me both directories w/o changing anything I can see.

And since bookworm has shut down, or moved, all the logs that might keep 
track of this, I'm lost. What can I do to trace or fix the reason for 
this denial of service? I know zip about your new ACL stuff if thats 
even involved. IDK.  Is there a special version of chown for raid arrays?
And where the heck are the logs, they should be in the /var directory of 
the drive its booted from which s/b /dev/sda, but df thinks its: now 
/dev/sda, last boot it was /dev/sdb, so much for UUID's. I have not 
moved any cables. One is a 500G samsung 860 SSD, the other a 1t Samsung 
870 SSD.

An ls of /var/log:
gene@coyote:~$ ls /var/log
alternatives.logapache2  boot.logboot.log.2  boot.log.4  btmp 
cups  dpkg.log.1  faillog gdm3   journal  private  runit 
 sddm.log   wtmp
alternatives.log.1  apt  boot.log.1  boot.log.3  boot.log.5  btmp.1 
dpkg.log  exim4   fontconfig.log  installer  lastlog  README   samba

speech-dispatcher

So where are syslog and dmesg?

Thanks.

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: qemu-guest-agent doesn't get restarted after update

[Shawn Weeks]

About the time I post this someone on the Proxmox forums posted the link to the 
Debian merge request. See 
https://salsa.debian.org/qemu-team/qemu/-/merge_requests/37

Thanks
Shawn

On Jul 26, 2023, at 8:39 AM, Shawn Weeks  wrote:

I’ve been tracking down an issue where my Debian 12 instances on Proxmox keep 
stopping their qemu-guest-agents and I’ve finally determined that it’s because 
unattended-upgrade doesn’t restart the agent after it updates it. I was 
wondering if this sounds like a bug or if someone has seen an existing bug 
report for it.

Thanks
Shawn

Are there Nvidia drivers on Trixie repositories right now ?

[rudu]

Hi there,

Switching from the nouveau driver to some nvidia-driver does not seam to 
be possible on my laptop running Debian Testing/Trixie.

Now, it can be found right here apparently :
https://packages.debian.org/trixie/nvidia-driver
Am I missing something ?
Some information about my system is following, just ask for more if needed.

Thanks

Rudu

$ LANG=C inxi -G
Graphics:
  Device-1: Intel HD Graphics 530 driver: i915 v: kernel
  Device-2: NVIDIA GM204GLM [Quadro M3000M] driver: nouveau v: kernel
  Device-3: Bison ThinkPad P50 Integrated Camera driver: uvcvideo type: USB
  Display: server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: 
X: loaded: modesetting
    unloaded: fbdev,vesa dri: iris,nouveau gpu: i915 tty: 158x38 
resolution: 1920x1080

  API: OpenGL Message: GL data unavailable in console. Try -G --display

$ LANG=C nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204GLM 
[Quadro M3000M] [10de:13fa] (rev a1)


Checking card:  NVIDIA Corporation GM204GLM [Quadro M3000M] (rev a1)
Uh oh. Failed to identify your Debian suite.

# LANG=C apt policy nvidia-driver
nvidia-driver:
  Installed: (none)
  Candidate: (none)
  Version table:

# cat /etc/apt/sources.list
# deb cdrom:[Debian GNU/Linux testing _Bookworm_ - Official Snapshot 
amd64 NETINST 20221031-03:18]/ bookworm main


#deb cdrom:[Debian GNU/Linux testing _Bookworm_ - Official Snapshot 
amd64 NETINST 20221031-03:18]/ bookworm main


deb http://ftp.fr.debian.org/debian trixie main contrib non-free-firmware
deb-src http://ftp.fr.debian.org/debian trixie main contrib 
non-free-firmware


deb http://ftp.fr.debian.org/debian-security/ trixie-security main 
contrib non-free-firmware
deb-src http://ftp.fr.debian.org/debian-security/ trixie-security main 
contrib non-free-firmware


deb http://ftp.fr.debian.org/debian trixie-updates main contrib 
non-free-firmware
deb-src http://ftp.fr.debian.org/debian trixie-updates main contrib 
non-free-firmware


# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

qemu-guest-agent doesn't get restarted after update

[Shawn Weeks]

I’ve been tracking down an issue where my Debian 12 instances on Proxmox keep 
stopping their qemu-guest-agents and I’ve finally determined that it’s because 
unattended-upgrade doesn’t restart the agent after it updates it. I was 
wondering if this sounds like a bug or if someone has seen an existing bug 
report for it.

Thanks
Shawn

RE: Error: no such device

[s.molnar]

-Original Message-
From: Greg Wooledge  
Sent: Wednesday, July 26, 2023 7:15 AM
To: debian-user@lists.debian.org
Subject: Re: Error: no such device

On Wed, Jul 26, 2023 at 06:46:31AM -0400, s.mol...@sbcglobal.net wrote:
> I installed Debian 12.0.0 on my Linux platform form the net install 
> iso

> The computer has been in service since the last time I upgraded the 
> system

..???

Did you *reinstall* Debian, or did you *upgrade* it?  Those are two
dramatically different things.

> Welcome to GRUB! 
> Error: no such device:  1d937ccf-2b57-4dcd-97d9-83522d7504f1.

If GRUB can't locate your root or /boot file system by UUID, then we would
need to know how you partitioned everything.  Did you try to do LVM, RAID,
or any combination of them?  Is the root or /boot file system inside one of
those, or is it on a native partition?  What file system type did you use to
create it?  Is this an EFI system or Legacy boot?


Thank you for your reply. I'm sorry for the brevity, but I wasn't sure what
I should report.

As usual, I sent the follow-up note a tad too sone. I just tried to boot
into the new OS and it booted!!! After bumbling luck on my part, but I'll
take it.

Once again, many thanks!!

Re: not a debian problem

[Michel Verdier]

On 2023-07-26, Tim Woodall wrote:

> Anyone seen anything like this and what was the issue?

I don't have such a difference between 2 machines. But I had one which
freeze and I played with reboot kernel parameter succeeding with:

reboot=pcie

reboot accept different values. I set it in /etc/default/grub so you can
prepare some kernel stances and try them quickly.

Re: NIS and systemd-udevd

[Greg Wooledge]

On Wed, Jul 26, 2023 at 10:31:09AM +0200, Christoph Pleger wrote:
> I found out that, though this works for users listed in /etc/passwd, it
> does not for users who have a remote NIS account.
> 
> That problem already occurred a longer time ago, but in the meanwhile,
> I had solved (by following suggestions from the internet) it by
> installing unscd and creating a file /etc/systemd/system/systemd-
> udevd.service.d/override.conf with the following content:
> 
> [Service]
> IPAddressAllow=localhost
> 
> But now, the problem occurs again: After booting the computer,
> I have to restart systemd-udevd to make 99-local.rules work as desired.
> 
> Does anyone have an idea how to solve the problem?

First thing I'll note is that this reminds me quite a bit of this
change which occurred in buster:

The security settings for some components of systemd have
been tightened. People using nis with systemd may encounter
bug 878625 which breaks a variety of things related to login
sessions. Workarounds include installing the nscd package,
or reconfiguring systemd-logind.service to allow it to use
the network.



But I suppose you're past that, and you're asking why you have to
restart a service after booting.  I don't have a direct answer for
that, but I'm wondering whether installing nscd would help.

FW: Error: no such device

[s.molnar]

 

 

From: s.mol...@sbcglobal.net  
Sent: Wednesday, July 26, 2023 6:47 AM
To: 'debian-user@lists.debian.org' 
Subject: Error: no such device

 

I installed Debian 12.0.0 on my Linux platform form the net install iso
without any warning or error messages. The initial boot of the system booted
the system came to a halt father quickly with the message:

 

GRUB loading

Welcome to GRUB! 

 

Error: no such device:  1d937ccf-2b57-4dcd-97d9-83522d7504f1.

Error: unknown file system.

grub rescue>

 

The computer has been in service since the last time I upgraded the system
and has not had this problem. I have been using Linux since the early days
with Slackware.

 

At this point I have downloaded the Debian-live-12.0.1-amd64-xfce.iso and
burned it to a USB flash drive which boots. I intend trying to installing
the system via this route, but wanted to send this hopping to get guidance.

 

Thanks in advance.

 

 

Stephen P. Molnar, Ph.D.

https:insilicochemistry.net

Cell:  (614)312-7528

Skype:  smolnar1

 

Booted into the live system, ran the installer, but got the same error when
attempted booting.

 

Now I really need help.

Re: Error: no such device

[Michael Kjörling]

On 26 Jul 2023 06:46 -0400, from s.mol...@sbcglobal.net:
> I installed Debian 12.0.0 on my Linux platform form the net install iso
> without any warning or error messages. The initial boot of the system booted
> the system came to a halt father quickly with the message:
> 
>  
> 
> GRUB loading
> 
> Welcome to GRUB! 
> 
>  
> 
> Error: no such device:  1d937ccf-2b57-4dcd-97d9-83522d7504f1.
> 
> Error: unknown file system.
> 
> grub rescue>

How exactly did you "install" Debian? In particular, when you did, did
you by any chance repartition or reformat anything? What's your file
system layout; do you have a separate /boot?

"No such device" from GRUB with a UUID suggests a mismatch between
partition/file system UUIDs and GRUB's configuration.

Something like `grep -i -C 5 --color 1d937ccf /boot/grub/grub.cfg`
pointing to the /boot/grub of the broken GRUB installation might point
you to where it's getting that UUID from and thus what needs to be
done to fix it. `lsblk -o +PARTUUID` might also be helpful.

I seriously doubt that you'll need to reinstall Debian to fix this.
It's more likely that your GRUB configuration just needs a little
tweak.

-- 
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: Error: no such device

[Greg Wooledge]

On Wed, Jul 26, 2023 at 06:46:31AM -0400, s.mol...@sbcglobal.net wrote:
> I installed Debian 12.0.0 on my Linux platform form the net install iso

> The computer has been in service since the last time I upgraded the system

...???

Did you *reinstall* Debian, or did you *upgrade* it?  Those are two
dramatically different things.

> Welcome to GRUB! 
> Error: no such device:  1d937ccf-2b57-4dcd-97d9-83522d7504f1.

If GRUB can't locate your root or /boot file system by UUID, then we
would need to know how you partitioned everything.  Did you try to do LVM,
RAID, or any combination of them?  Is the root or /boot file system inside
one of those, or is it on a native partition?  What file system type
did you use to create it?  Is this an EFI system or Legacy boot?

Error: no such device

[s.molnar]

I installed Debian 12.0.0 on my Linux platform form the net install iso
without any warning or error messages. The initial boot of the system booted
the system came to a halt father quickly with the message:

 

GRUB loading

Welcome to GRUB! 

 

Error: no such device:  1d937ccf-2b57-4dcd-97d9-83522d7504f1.

Error: unknown file system.

grub rescue>

 

The computer has been in service since the last time I upgraded the system
and has not had this problem. I have been using Linux since the early days
with Slackware.

 

At this point I have downloaded the Debian-live-12.0.1-amd64-xfce.iso and
burned it to a USB flash drive which boots. I intend trying to installing
the system via this route, but wanted to send this hopping to get guidance.

 

Thanks in advance.

 

 

Stephen P. Molnar, Ph.D.

https:insilicochemistry.net

Cell:  (614)312-7528

Skype:  smolnar1

 

Re: not a debian problem

[Dan Ritter]

Tim Woodall wrote: 
> This is not a debian problem but I'm hoping the collective wisdom might
> have some ideas.
> 
> One can be soft rebooted with no issues, the other hangs in the bios.
> 
> Anyone seen anything like this and what was the issue?
> 
> Both machines are running bullseye if there are things I can check while
> booted.

It is most likely either a motherboard BIOS change or a BIOS
setting that differs; it is less likely to be a BMC firmware
difference, but that's possible.

Can you diff the output of dmidecode from each system?

-dsr-

Re: General Questions

[Tim Woodall]

On Tue, 25 Jul 2023, Greg Wooledge wrote:


On Tue, Jul 25, 2023 at 07:53:52AM -0400, Dan Ritter wrote:

Source Code wrote:

3. Is it possible to reduce RAM consumption? And minimize it? Let's say up
to 100-200 mb?


That depends on what you choose to run, and how. I would not
recommend trying to do anything interesting on a machine with
less than 256MB of RAM. That will not be enough for many common
uses.


According to 
256 MB is the absolute minimum amount of RAM for installing bookworm
on an AMD64 machine, using the text installer and no GUI packages.

However, if one is trying to set up a low-memory server of some kind,
especially in a virtual machine or similar environment, that's an
entirely different line of questioning.

I'm guessing that's NOT the goal here, because the OP mentioned WiFi.
This leaves me somewhat perplexed.




FWIW, i don't think a minimal bullseye install will boot under xen with
128MB of ram configured. IIRC Buster will.

not a debian problem

[Tim Woodall]

This is not a debian problem but I'm hoping the collective wisdom might
have some ideas.

I have two, nominally identical, systems. Only difference should be the
make and model of the ssd disks.

One can be soft rebooted with no issues, the other hangs in the bios.

They have ipmi, and a power cycle via that will allow a successful
reboot. It doesn't require a power drain.

I'm 95% sure I've tried swapping the disks between the machines - but
I'll reconfirm when I've got a few hours spare. The problem is the
motherboard (or case?)

The motherboard is J1900D2Y

It's not a huge issue, I rarely reboot and can do it remotely if
required, but it's an annoyance I'd like to fix.

Anyone seen anything like this and what was the issue?

For various reasons I cannot reboot the good one at will, so I'm hoping
to gather a set of things to try and check all in one go.

Both machines are running bullseye if there are things I can check while
booted.

Tim

NIS and systemd-udevd

[Christoph Pleger]

Hello,

I have the following udev rule in /lib/udev/rules.d/99-local.rules:

ACTION=="add", SUBSYSTEM=="block", ATTRS{removable}=="1",
PROGRAM="/lib/udev/foreground-user", RESULT!="root", MODE="0600",
OWNER="$result"

This is to ensure that, if someone is logged in on the graphical
console at the time when a USB is inserted, this person becomes the
owner of the devive file belonging to the stick, /dev/sd[a-z].

I found out that, though this works for users listed in /etc/passwd, it
does not for users who have a remote NIS account.

That problem already occurred a longer time ago, but in the meanwhile,
I had solved (by following suggestions from the internet) it by
installing unscd and creating a file /etc/systemd/system/systemd-
udevd.service.d/override.conf with the following content:

[Service]
IPAddressAllow=localhost

But now, the problem occurs again: After booting the computer,
I have to restart systemd-udevd to make 99-local.rules work as desired.

Does anyone have an idea how to solve the problem?

Regards
   Christoph


signature.asc
Description: This is a digitally signed message part

Re: no sound on Debian 12

[Michel Verdier]

On 2023-07-25, Bruce Byfield wrote:

> Last week, I installed Debian 12. Since then I've had no sound. I've 
> consulted 
> various pages on the Debian wiki, and found no solution, either with 
> pulseaudio or pipewire. Built-in speakers,  and external features (including 
> bluetooth ones, which are definitely connected) don't work. Any suggestions?

pulseaudio is provided by pipewire-pulse if you use pipewire. And you
should have wireplumber for your user. Check packages and systemd
services.