date:20231029


On 30/10/2023 01:21, Jeffrey Walton wrote:
Also see 
,

where the systemd folks said to modify the hostname by hand because
hostnamectl butchered the fully qualified hostname.


Debian bookworm is not affected by this decade-old bug.

I am however unsure concerning reasons behind the following suggestion 
in respect to /etc/hostname


hostname(5) from systemd

It is recommended that this name contains only a single label, i.e.
without any dots.

Re: Domain name to use on home networks


On 30/10/2023 00:08, Pocket wrote:

On 10/29/23 12:24, gene heskett wrote:
I have also made a very painfull attempt to 
change my domainname from coyote.den to home.arpa, and finally 
reverted that,


Gene, have you posted what exactly you did to switch from coyote.den to 
home.arpa? You have been told that setting NIS domainname was a wrong 
direction since you do not manage your hosts through NIS.


NetworkManager keeps updating the /etc/resolv.conf file in my opinion 
because it is querying the DHCP server.

[ ... ]> cat /etc/NetworkManager/system-connections/GREMLIN.nmconnection

[ipv4]
method=auto


Gene has no DHCP server, so it should be method=manual. Frankly 
speaking, I see almost no advantages of NetworkManager over ifupdown in 
a purely static network. E.g. cable plug/unplug events should not matter 
since there is no need to update configuration in response.

Re: A replacement for gkrellm


On 10/29/23 14:27, Dominique Dumont wrote:

On Saturday, 28 October 2023 13:18:13 CET gene heskett wrote:

It seems Bill Wilsons site for gkrellm stuff has expired.


This site is still active: http://gkrellm.srcbox.net/

New site, the docs don't mention it, thanks for the link. bookmarked.


All the best




.


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

Re: Domain name to use on home networks

2023-10-29 Thread John Hasler

Gene writes:
> possibly, its a Buffalo Netfinity with a now elderly dd-wrt reflash,
> and whose pw I've long since forgot, and its 30 chars of random
> gibberish IIRC.

Write the password on the router.  Write all your passwords down.
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA

Re: A replacement for gkrellm

2023-10-29 Thread Dominique Dumont

On Saturday, 28 October 2023 13:18:13 CET gene heskett wrote:
> It seems Bill Wilsons site for gkrellm stuff has expired. 

This site is still active: http://gkrellm.srcbox.net/

All the best

Re: Domain name to use on home networks

2023-10-29 Thread Jeffrey Walton

On Fri, Oct 27, 2023 at 3:14 PM Andrew M.A. Cater  wrote:
>
> On Fri, Oct 27, 2023 at 09:30:09AM -0400, Pocket wrote:
> >
> > > On Oct 27, 2023, at 9:05 AM, Greg Wooledge  wrote:
> > >
> > > On Fri, Oct 27, 2023 at 07:59:00AM -0400, Pocket wrote:
> > >>> On 10/27/23 07:50, Greg Wooledge wrote:
> > >>> On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote:
> >  /etc/hosts
> > >>> If you're using short-form hostnames like this:
> > >>>
> > >>> unicorn:~$ hostname
> > >>> unicorn
> > >>>
> > >>> then yeah, that's all you need.  If you're using long-form hostnames
> > >>> (with dots in them), then you also need to configure /etc/hostname.
>
> hostnamectl set-hostname is the command to do it - and will survive a reboot.

Also see 
,
where the systemd folks said to modify the hostname by hand because
hostnamectl butchered the fully qualified hostname.

I'm not sure if it still applies. I avoid hostnamectl. I don't care
about mDNS. DNS is the source of truth on my networks.

Jeff

Re: Domain name to use on home networks


On 10/29/23 13:09, Pocket wrote:


On 10/29/23 12:24, gene heskett wrote:

On 10/29/23 10:23, David Wright wrote:

On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote:


You saw my hosts entry in the last post, but again
192.168.71.3    coyote.home.arpa    coyote
but after a reboot, domainname returns none, and the /etc/domainname
file has been deleted. As in not visible to an ls of /etc. hostname
works as it should. My hosts file is all long form, dotted names with
a trailing alias.
So I just sudo edited /etc/domainname, and entered "home.arpa\return"
and wrote the flle.
results:

You are quite right David, /etc/domainname was composed by me in nano 
after that was posted, I have also made a very painfull attempt to 
change my domainname from coyote.den to home.arpa, and finally 
reverted that, amoung an attack by network mangler, finally solved by 
editing resolv.conf to put the nameserver address into it, followed by 
a chattr +i resolv.conf. I have no d clue where mangler gets the 
"search coyote.den" it keeps putting in resolv.conf every 45 seconds 
as it times out and sets it offline for 5 seconds. Maybe its not 
right, but it fixes it.  All of the -alphabet options to hostname now 
work once I edited out the domainname part of /etc/hostname. IMO, 
giving network mangler the ability to change resolv.conf has been the 
single glaringly biggest headache for hosts file users in the last 
decade. After 3 days of screwing around with an armbian jammy on a 
bananapi-m5, one of many on this home network, its finally working. I 
had to revert to an earlier xfce desktop image to get the video to 
work. Then with everything looking correct, I had a net connection for 
45 seconds, followed by a 5 second reset. So chattr +i to the rescue 
after making sure the nameserver address was in resolv.conf.



NetworkManager keeps updating the /etc/resolv.conf file in my opinion 
because it is querying the DHCP server.


After much trouble this is my current setup for what will become my new 
DNS, NFS and web server


which BTW is running on a raspberry pi 4, with debian bookworm.

Be mindful of the following NetworkManager uses this if the 
configuration file is not in 
/etc/NetworkManager/system-connections/


ls  /run/NetworkManager/system-connections/
'Wired connection 1.nmconnection'   lo.nmconnection

My setup:

cat /etc/hostname

gremlin

cat /etc/hosts
127.0.0.1    localhost
::1        localhost ip6-localhost ip6-loopback
ff02::1        ip6-allnodes
ff02::2        ip6-allrouters
127.0.1.1    gremlin.home.arpa gremlin

cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

[device]
wifi.scan-rand-mac-address=no

[global-dns]
options=edns0 trust-ad

This is for my Wireless connection, Wired has the same settings:

cat /etc/NetworkManager/system-connections/GREMLIN.nmconnection
[connection]
id=GREMLIN
uuid=49743fda-4a97-4ff4-b46a-a12a7b1383fb
type=wifi
interface-name=wlan0

[wifi]
mode=infrastructure
ssid=GREMLIN

[ipv4]
method=auto
dns-search=home.arpa;

[ipv6]
addr-gen-mode=stable-privacy
method=auto
dns-search=home.arpa;
dns=
ignore-auto-dns=true

  cat /etc/resolv.conf
# Generated by NetworkManager
search home.arpa
nameserver 192.168.1.1
nameserver 
options edns0 trust-ad

That is all it took to get it setup on my Network.

NetworkManager will populate /etc/resolv.conf using both wired and wifi 
connections/setup, maybe that is some of your troubles as well?


I make them with the same settings


Finally some info worth checking out and putting on dead tree.


Also maybe your router needs some TLC


possibly, its a Buffalo Netfinity with a now elderly dd-wrt reflash, and 
whose pw I've long since forgot, and its 30 chars of random gibberish 
IIRC. So I'll have to start with the long reset to factory, which was 
easy because the old asus mobo had two net plugs, but this one only has 
one. I have a spare router whose mac has been cloned that can be used in 
a pinch, but will need to get a usb to net dongle first. With a ups and 
auto stand by here, its not even been rebooted in years.  What can I 
say?  As a guard dog its sharp teeth have been 100% effective so I 
haven't had an excuse to log into it since I turned off the radio about 
5 years ago to keep a neighbors phone from using 80GB a month to watch 
porn. I could probably turn the radio back on, he spent some time in 
jail for mail nondelivery, and his woman thru him out when he got out, 
so he and his hacked phone are no longer neighbors. Found a dongle. 
Bought it.  Be here Tuesday.  And this time around, I'll set a pw and 
write it down. ;o)>



I have 4 more bananapi-m5's coming, so I may be back but last post on 
this thread unless someone can tell me how to housebreak network 
mangler. I'm plumb tuckered out from mopping up its messes.


Take care & stay well, all.

Cheers, Gene Heskett.




Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury,

Re: [Bookworm] collecting sensors data

2023-10-29 Thread Darac Marjal

On 29/10/2023 12:00, mick.crane wrote:

On 2023-10-28 18:31, Roy J. Tellason, Sr. wrote:

On Saturday 28 October 2023 07:25:39 am gene heskett wrote:

On 10/28/23 00:14, Max Nikulin wrote:
> On 28/10/2023 01:39, Greg wrote:
>> I just noticed that there is no rrdcollect in Bookworm. What is the
>> "proper" way of collecting sensors readings?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029995 :
>> please consider removing rrdcollect. Its a tool/daemon to collect
>> metrics from the local system into RRD files. There are quite a 
number

>> of alternatives in Debian to do the same, better (munin, et al).
>
I just looked at munin in synaptic, But while there lots of parts to 
it,

there is not a single word that indicates what it does? Absolutely
nothing that tells me it can monitor the system fans or measure the
systems voltages.  What does it actually DO?

I've seen that fairly often,  particularly with software packages.
It's a real aggravation at times.

I've sometimes thought it would be useful if at the top of man pages 
there was.

"Why would I use this" with explanation.

I suppose that's what the "summary" line is for:

 * ls - list directory contents
 * munin-node - A daemon to gather information in cooperation with the
   main Munin program
 * sensors - print sensors information
 * synaptic - graphical management of software packages

OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Domain name to use on home networks

2023-10-29 Thread Pocket




On 10/29/23 12:24, gene heskett wrote:

On 10/29/23 10:23, David Wright wrote:

On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote:


You saw my hosts entry in the last post, but again
192.168.71.3    coyote.home.arpa    coyote
but after a reboot, domainname returns none, and the /etc/domainname
file has been deleted. As in not visible to an ls of /etc. hostname
works as it should. My hosts file is all long form, dotted names with
a trailing alias.
So I just sudo edited /etc/domainname, and entered "home.arpa\return"
and wrote the flle.
results:

You are quite right David, /etc/domainname was composed by me in nano 
after that was posted, I have also made a very painfull attempt to 
change my domainname from coyote.den to home.arpa, and finally 
reverted that, amoung an attack by network mangler, finally solved by 
editing resolv.conf to put the nameserver address into it, followed by 
a chattr +i resolv.conf. I have no d clue where mangler gets the 
"search coyote.den" it keeps putting in resolv.conf every 45 seconds 
as it times out and sets it offline for 5 seconds. Maybe its not 
right, but it fixes it.  All of the -alphabet options to hostname now 
work once I edited out the domainname part of /etc/hostname. IMO, 
giving network mangler the ability to change resolv.conf has been the 
single glaringly biggest headache for hosts file users in the last 
decade. After 3 days of screwing around with an armbian jammy on a 
bananapi-m5, one of many on this home network, its finally working. I 
had to revert to an earlier xfce desktop image to get the video to 
work. Then with everything looking correct, I had a net connection for 
45 seconds, followed by a 5 second reset. So chattr +i to the rescue 
after making sure the nameserver address was in resolv.conf.



NetworkManager keeps updating the /etc/resolv.conf file in my opinion 
because it is querying the DHCP server.


After much trouble this is my current setup for what will become my new 
DNS, NFS and web server


which BTW is running on a raspberry pi 4, with debian bookworm.

Be mindful of the following NetworkManager uses this if the 
configuration file is not in 
/etc/NetworkManager/system-connections/


ls  /run/NetworkManager/system-connections/
'Wired connection 1.nmconnection'   lo.nmconnection

My setup:

cat /etc/hostname

gremlin

cat /etc/hosts
127.0.0.1    localhost
::1        localhost ip6-localhost ip6-loopback
ff02::1        ip6-allnodes
ff02::2        ip6-allrouters
127.0.1.1    gremlin.home.arpa gremlin

cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

[device]
wifi.scan-rand-mac-address=no

[global-dns]
options=edns0 trust-ad

This is for my Wireless connection, Wired has the same settings:

cat /etc/NetworkManager/system-connections/GREMLIN.nmconnection
[connection]
id=GREMLIN
uuid=49743fda-4a97-4ff4-b46a-a12a7b1383fb
type=wifi
interface-name=wlan0

[wifi]
mode=infrastructure
ssid=GREMLIN

[ipv4]
method=auto
dns-search=home.arpa;

[ipv6]
addr-gen-mode=stable-privacy
method=auto
dns-search=home.arpa;
dns=
ignore-auto-dns=true

 cat /etc/resolv.conf
# Generated by NetworkManager
search home.arpa
nameserver 192.168.1.1
nameserver 
options edns0 trust-ad

That is all it took to get it setup on my Network.

NetworkManager will populate /etc/resolv.conf using both wired and wifi 
connections/setup, maybe that is some of your troubles as well?


I make them with the same settings

Also maybe your router needs some TLC


I have 4 more bananapi-m5's coming, so I may be back but last post on 
this thread unless someone can tell me how to housebreak network 
mangler. I'm plumb tuckered out from mopping up its messes.


Take care & stay well, all.

Cheers, Gene Heskett.


--
It's not easy to be me

Re: Changing host name and domain name on Debian; was: Domain nametouse on home networks


On 10/29/23 12:10, Max Nikulin wrote:

On 27/10/2023 23:03, gene heskett wrote:


I suggest you file a bug against this command to among other things, 
clean up the language to refer to FQDN's or aliases which we are 
familiar with, "static, transient or pretty" as so called choices. If 
using new words for old, either define them so we do understand or 
remove them in favor of names we are familiar with.


If you see a bug then why somebody else should report it?


begin rant:

Somebody who /can/ report it. I changed ISP's over a decade back, so I 
am not me to bugzilla, and because I am known also by name, I can't 
re-register. I can't even get a pw reset cuz it (I'm guessing here) is 
sending it to my earlier ISP's, could be iolinc.net or frontier.com I 
was using when I first installed redhat5.0 in 1998.  Messages to the 
maintainer to wipe me out of the system so I can re-register have never 
been replied to.


People DO CHANGE ISP's for good reasons, like no telephone for several 
months because frontier refuses to lay new buried copper that is now 70 
years old, paper insulated and full of water. I repeatedly filed with 
the states P.U.C. and all that got me was a letter cussing me out for 
filing with the WV PUC.  Screw it.


I'd heard rumors the local cable people could do phone service so I 
switched it all. We had a 112 mph direcho come thru in 2010, all the 
system battery's eventually went down. Did $18,000 damage to this house 
and the 35 foot pin oak in the front yard was the only tree that 
survived in a path about 100 foot wide and 10 miles long. Those 2 days 
while putting the neighborhood utilities back together 13 years ago has 
been my only phone or net failure since.


So don't give me any more static about filing my own bugs, I can't and 
you've just been told why. If you want /ME/ to file bugs, fix it so I 
can AND TELL ME when its been fixed.


/end rant


It is not clear for me why hostnamectl(1) should discuss FQDN. The scope 
of hostnamectl is host name as it is stored in kernel structures: 
gethostname(2), sethostname(2), uts_namespaces(7); and persistence 
across reboots (/etc/hostname). Another part is representation of the 
host in GUI and in responses to multicast service discovery ("pretty"). 
FQDN as described in hostname(1) is related to name resolver (hosts 
entry in /etc/nsswitch.conf). So hostname(1) deals with more features 
than hostnamectl. nss-myhostname(8) affects "hostname --all-fqdns", but 
I am unsure if it does it in the way expected by hostname(1).


.


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

Re: Domain name to use on home networks


On 10/29/23 10:23, David Wright wrote:

On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote:


You saw my hosts entry in the last post, but again
192.168.71.3coyote.home.arpacoyote
but after a reboot, domainname returns none, and the /etc/domainname
file has been deleted. As in not visible to an ls of /etc. hostname
works as it should. My hosts file is all long form, dotted names with
a trailing alias.
So I just sudo edited /etc/domainname, and entered "home.arpa\return"
and wrote the flle.
results:

gene@coyote:/etc$ sudo nano domainnane
[sudo] password for gene:
gene@coyote:/etc$ domainname
(none)
gene@coyote:/etc$ cat domainname
cat: domainname: No such file or directory
now I see the typu. sudo mv to fx the files name. but even with a
corrected filename visible to an ls:
gene@coyote:/etc$ domainname
(none)
gene@coyote:/etc$ cat domainname
home.arpa

I'd reboot again, but that, by the time I get everything remounted and
my system fully operational, takes me entering my pw about 20 times.
when done I am logged into 6 other machines via an ssh -X login to
each, and I've a sshfs file transfer link setup to each so mc can copy
work output around.  Then I can go to work.

Why was the domainname I set and could see with a cat, deleted by a
reboot?  Seems to be the question for the day... I sure didn't delete
it. But it was gone after a reboot.  Seems to me there ought to be a
PERMANENT way to do this. Now, even if the file exists, its ignored.


I'm just wondering where this file /etc/domainname came from in the
first place. I can't find it with apt-file (killing two birds):

   $ apt-file find etc/domain
   $

Neither can I find it/them in the install/remove scripts for the packages
on my systems:

   $ grep etc/domain /var/lib/dpkg/info/*
   $

I don't recall ever seeing either /etc/domainname or /etc/domain
in the past either, as I would have my copy backed up.

/etc/domainname might be anodyne on your system, but it raises
suspicions when this is meant to be a recent bookworm netinst
where "I'm not doing anything the installer didn't ask me to do"
(posted last week).

Cheers,
David.



You are quite right David, /etc/domainname was composed by me in nano 
after that was posted, I have also made a very painfull attempt to 
change my domainname from coyote.den to home.arpa, and finally reverted 
that, amoung an attack by network mangler, finally solved by editing 
resolv.conf to put the nameserver address into it, followed by a chattr 
+i resolv.conf. I have no d clue where mangler gets the "search 
coyote.den" it keeps putting in resolv.conf every 45 seconds as it times 
out and sets it offline for 5 seconds. Maybe its not right, but it fixes 
it.  All of the -alphabet options to hostname now work once I edited out 
the domainname part of /etc/hostname. IMO, giving network mangler the 
ability to change resolv.conf has been the single glaringly biggest 
headache for hosts file users in the last decade. After 3 days of 
screwing around with an armbian jammy on a bananapi-m5, one of many on 
this home network, its finally working. I had to revert to an earlier 
xfce desktop image to get the video to work.  Then with everything 
looking correct, I had a net connection for 45 seconds, followed by a 5 
second reset. So chattr +i to the rescue after making sure the 
nameserver address was in resolv.conf.


And the chrome browser is still broken, it cannot look at localhost:80, 
hostname:80 or alias:80. It blanks that out of the address line and 
refills it with 250+ chars of a failure message from google %$#^@!& dns 
server. I had to fix my net before I could install the snap of firefox, 
which DOES follow the lookup rules chrome refuses to use. google. spit.


I have 4 more bananapi-m5's coming, so I may be back but last post on 
this thread unless someone can tell me how to housebreak network 
mangler. I'm plumb tuckered out from mopping up its messes.


Take care & stay well, all.

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

Re: Domain name to use on home networks


On 27/10/2023 21:19, Greg Wooledge wrote:
More importantly, why on earth would this be recommended over editing 
the /etc/hostname file, which is *much* simpler, and which appears to be 
independent of the init system that's in use?


hostnamectl tries to prevent split brain /etc/hostname vs. kernel 
structures in RAM. "hostnamectl hostname --transient NAME" does not work 
if /etc/hostname is present. Notice diverged static and transient names 
in Gene's message



   Static hostname: coyote.home.arpa
Transient hostname: coyote


"hostnamectl hostname NAME" besides changing /etc/hosts calls 
sethostname(2) (or what libc provided instead of it), so it is less 
chance that a user will get inconsistent settings by forgetting another 
command.


I think, original intention was to provide D-Bus API for GUI and 
hostnamectl is just a CLI tool for that API.

Re: Changing host name and domain name on Debian; was: Domain nameto use on home networks


On 27/10/2023 23:03, gene heskett wrote:


I suggest you file a bug against this command to among other things, 
clean up the language to refer to FQDN's or aliases which we are 
familiar with, "static, transient or pretty" as so called choices. If 
using new words for old, either define them so we do understand or 
remove them in favor of names we are familiar with.


If you see a bug then why somebody else should report it?

It is not clear for me why hostnamectl(1) should discuss FQDN. The scope 
of hostnamectl is host name as it is stored in kernel structures: 
gethostname(2), sethostname(2), uts_namespaces(7); and persistence 
across reboots (/etc/hostname). Another part is representation of the 
host in GUI and in responses to multicast service discovery ("pretty"). 
FQDN as described in hostname(1) is related to name resolver (hosts 
entry in /etc/nsswitch.conf). So hostname(1) deals with more features 
than hostnamectl. nss-myhostname(8) affects "hostname --all-fqdns", but 
I am unsure if it does it in the way expected by hostname(1).

Re: Domain name to use on home networks

2023-10-29 Thread John Hasler

David Wright writes:
> I'm just wondering where this file /etc/domainname came from in the
> first place. I can't find it with apt-file (killing two birds):

Gene created it, having been confused by the hostname man page.
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA

Re: [Bookworm] collecting sensors data


On 10/29/23 08:01, mick.crane wrote:

On 2023-10-28 18:31, Roy J. Tellason, Sr. wrote:

On Saturday 28 October 2023 07:25:39 am gene heskett wrote:

On 10/28/23 00:14, Max Nikulin wrote:
> On 28/10/2023 01:39, Greg wrote:
>> I just noticed that there is no rrdcollect in Bookworm. What is the
>> "proper" way of collecting sensors readings?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029995 :
>> please consider removing rrdcollect. Its a tool/daemon to collect
>> metrics from the local system into RRD files. There are quite a 
number

>> of alternatives in Debian to do the same, better (munin, et al).
>
I just looked at munin in synaptic, But while there lots of parts to it,
there is not a single word that indicates what it does? Absolutely
nothing that tells me it can monitor the system fans or measure the
systems voltages.  What does it actually DO?


I've seen that fairly often,  particularly with software packages.
It's a real aggravation at times.


I've sometimes thought it would be useful if at the top of man pages 
there was.

"Why would I use this" with explanation.


Something along those lines would sure generate the huzzahs here.

mick

.


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

Re: Domain name to use on home networks

2023-10-29 Thread Greg Wooledge

On Sun, Oct 29, 2023 at 09:22:38AM -0500, David Wright wrote:
> I'm just wondering where this file /etc/domainname came from in the
> first place. I can't find it with apt-file (killing two birds):
> 
>   $ apt-file find etc/domain
>   $ 

I'm assuming either Gene created it himself, because he thought he needed
to, or his non-Debian installer created it, for reasons only the maintainer
of said installer would know.

Having that file on a non-NIS system doesn't actually hurt anything.
I advised Gene to remove his in order to avoid confusion.  We can all
do with less of that.

Re: Fallo

2023-10-29 Thread Francisco Cid

El dom., 29 oct. 2023 12:19, Fran  escribió:

> Ha fallado la descarga del paquete:E:
> http://ftp.cica.es/mirrors/Linux/MX-Packages/mx/repo bookworm/main amd64
> mx-installer amd64 23.10.03mx23 is not (yet) available (404 Not Found
> [IP: 150.214.5.134 80])
> 
>

Repositorios

>
>

¿GRUB? SOLUCIONADO.

2023-10-29 Thread casadellabrador

Hola.
Para recuperar el grub seguí las instrucciones que hallé en:
https://slimbook.es/tutoriales/linux/164-3-maneras-de-como-reinstalar-o-reparar-grub-boot-repair-archlinux-o-antergos.
Descarguë una iso de Boot-Repair y la puse en un USB mediante la utilidad que a 
tales fines incluye Linux-Mint (grabador de USB).
Arranqué el ordenador con la USB pinchada y seguí las indicaciones del programa 
para solucionar los problemas de arranque del GRUB, que en mi caso, tras un 
primer intento fallido, incluyó crear con Gparted una partición de 1 Mb para 
alojar el arranque, ¿por qué hube de hacer esta operación?: lo ignoro; el caso 
es que después pude reiniciar normalmente.
Por otro lado, incluyo en el asunto de este email el término SOLUCIONADO, pero 
no sé si es así como debía hacerlo, pues en el enlace que me indican:
https://lists.debian.org/debian-user-spanish/2023/09/threads.html
no he encontrado cómo hacerlo.
Aprovecho pues para preguntar si existe y conocen un tutorial sobre cómo 
utilizar correctamente esta lista de correo.
De nuevo un saludo y mi agradecimiento.
Gerardo
-- 
 Enviado con Tutanota, disfruta del correo seguro y sin publicidad. 



29 oct 2023, 15:20 por javier.debian.bb...@gmail.com:

>
>
> El 29/10/23 a las 05:27, casadellabra...@tutanota.com escribió:
>
>> Buenos días.
>>
>> Lo primero es que os alegréis conmigo porque gracias a vuestra ayuda y al 
>> Boot-Repair he podido recuperar el GRUB y, de momento, todo parece volver a 
>> funcionar.
>>
>> Lo segundo es deciros que sí, que algo más hice cuando traté de instalar 
>> Ungoogled-Chromium.Appimage, pues, como no arrancaba tras el mero cambio en 
>> sus propiedades para que el archivo se ejecutara como un programa, ejecuté 
>> los comandos que recomendaban en una web que, desgraciadamente, no tuve la 
>> precaución de anotar y que no he vuelto a localizar.
>>
>> Como a partir de ahora sé a dónde dirigirme para conseguir ayuda en mi 
>> trajín con Debian, me prometo a mi mismo no volver a usar recomendaciones 
>> que a lo peor no entiendo bien (no tengo conocimientos de informática, soy 
>> un mero usuario algo atrevido que, eso sí, quiere confiar, usar y apoyar el 
>> software libre y alternativo a los microsoftes, googles y otras hierbas).
>>
>> Me pongo a vuestra disposición en lo que pueda ayudar.
>>
>> Un cordial saludo.
>>
>> /_Gerardo_/
>>
>> -- 
>> Enviado con Tutanota, disfruta del correo seguro y sin publicidad.
>>
>>
>>
>> 28 oct 2023, 20:13 por n4ch0...@gmail.com:
>>
>>  On 23/10/28 08:03AM, casadellabra...@tutanota.com wrote:
>>
>>  Buenos días.
>>  Soy novato en el uso de Debian GNU/Linux 11 bullseye (x86-64),
>>  Cinnamon 4.8.6; núcleo Linux: 5.10.0-26-amd64; procesador:
>>  Intel© Core™2 CPU T5600 @ 1.83GHz × 2, RAM 2,9 GiB; tarjeta
>>  gráfica: Advanced Micro Devices, Inc. [AMD/ATI] RV515/M52
>>  [Mobility Radeon X1300] (prog-if 00 [VGA controller]).
>>
>>  Después de intentar instalar un nuevo navegador de internet,
>>  concretamente Ungoogled-Chromium, no puedo arrancar el sistema
>>  normalmente, pues la pantalla se queda en negro con la leyenda
>>  "GRUB" junto al cursor intermitente.
>>  He intentado recuperar Grub con Supergrub2, y he arrancado el
>>  sistema pero al ejecutar el comando "sudo grub-install
>>  /dev/sda", como paso previo para recuperar Grub, la consola me
>>  devuelve el siguiente mensaje:
>>
>>  Instalando para plataforma i386-pc.
>>  grub-install: aviso: esta etiqueta de partición GPT no contiene
>>  ninguna Partición de Arranque BIOS; el embebido no será posible.
>>  grub-install: aviso. El embebido no es posible. GRUB podrá ser
>>  instalado con esta configuración únicamente usando listas de
>>  bloques. No obstante, las listas de bloques son INSEGURAS y su
>>  uso está desaconsejado.
>>  grub-install: error: no se procederá con las listas de bloques.
>>
>>  Y cuando posteriormente intento arrancar normalmente el sistema,
>>  éste se bloquea con la pantalla en negro y la leyenda "GRUB" que
>>  antes comenté.
>>
>>  Supongo que podrá reinstalar todo el sistema con un live-usb,
>>  pero antes me he decidido a consultarles:
>>  ¿qué podría hacer un profano informático como yo para recuperar
>>  el GRUB o para arrancar el sistema normalmente?
>>
>>  Un cordial saludo.
>>  Gerardo
>>
>>
>>  -- Enviado con Tutanota, disfruta del correo seguro y sin 
>> publicidad.
>>
>>
>>  Primero decirte que hayas instalado un browser nada tiene que ver
>>  con lo que te ocurrió.
>>
>>  algo más has hecho que no nos han contado
>>
>>  Y si te conviene, ir con un live cd pero primero debes montar
>>  ciertas carpetas para poder instalarlo, chequea este enlace:
>>
>>  
>> https://slimbook.es/tutoriales/linux/164-3-maneras-de-como-reinstalar-o-reparar-grub-boot-repair-archlinux-o-antergos
>>
>>  Slds
>>
>
>
> Enhorabuena.
>
> Ahora bien.
> Es costumbre en la lista dos cosas:
>
> 1 - Detallar qué hiciste para solucionarlo, y en el futuro sirva de 
> referencia a otra persona.
>
> 2 - Cuando se soluciona algo,

Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

The instructions on the webpage:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md,
the portion of the note:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md#notes-about-combined-wifibluetooth-devices
may please be perused

The firmware was already in the directory: /lib/firmware/brcm, but
still error messages were read on the terminal. Solved the issue.

There was a simple trick involved:
I had to make the file read-only for all. Then restart the computer.

Now:
# dmesg | grep -i bluetooth # Shows all Bluetooth driver info

Output:
[   29.102165] Bluetooth: Core ver 2.22
[   29.102210] Bluetooth: HCI device and connection manager initialized
[   29.102219] Bluetooth: HCI socket layer initialized
[   29.102224] Bluetooth: L2CAP socket layer initialized
[   29.102230] Bluetooth: SCO socket layer initialized
[  105.688413] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  105.688419] Bluetooth: BNEP filters: protocol multicast
[  105.688426] Bluetooth: BNEP socket layer initialized

# dmesg | grep -i bluetooth | grep -i firmware # Shows Bluetooth firmware issues

Output: None

However, I am still receiving the same error messages for the other
commands as listed  on the post:
https://lists.debian.org/debian-user/2023/10/msg00871.html

I now would need your support to install specific packages and
reconfigure the settings so that I no longer receive the error
messages.

Best wishes

Re: Domain name to use on home networks

2023-10-29 Thread David Wright

On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote:

> You saw my hosts entry in the last post, but again
> 192.168.71.3coyote.home.arpacoyote
> but after a reboot, domainname returns none, and the /etc/domainname
> file has been deleted. As in not visible to an ls of /etc. hostname
> works as it should. My hosts file is all long form, dotted names with
> a trailing alias.
> So I just sudo edited /etc/domainname, and entered "home.arpa\return"
> and wrote the flle.
> results:
> 
> gene@coyote:/etc$ sudo nano domainnane
> [sudo] password for gene:
> gene@coyote:/etc$ domainname
> (none)
> gene@coyote:/etc$ cat domainname
> cat: domainname: No such file or directory
> now I see the typu. sudo mv to fx the files name. but even with a
> corrected filename visible to an ls:
> gene@coyote:/etc$ domainname
> (none)
> gene@coyote:/etc$ cat domainname
> home.arpa
> 
> I'd reboot again, but that, by the time I get everything remounted and
> my system fully operational, takes me entering my pw about 20 times.
> when done I am logged into 6 other machines via an ssh -X login to
> each, and I've a sshfs file transfer link setup to each so mc can copy
> work output around.  Then I can go to work.
> 
> Why was the domainname I set and could see with a cat, deleted by a
> reboot?  Seems to be the question for the day... I sure didn't delete
> it. But it was gone after a reboot.  Seems to me there ought to be a
> PERMANENT way to do this. Now, even if the file exists, its ignored.

I'm just wondering where this file /etc/domainname came from in the
first place. I can't find it with apt-file (killing two birds):

  $ apt-file find etc/domain
  $ 

Neither can I find it/them in the install/remove scripts for the packages
on my systems:

  $ grep etc/domain /var/lib/dpkg/info/*
  $ 

I don't recall ever seeing either /etc/domainname or /etc/domain
in the past either, as I would have my copy backed up.

/etc/domainname might be anodyne on your system, but it raises
suspicions when this is meant to be a recent bookworm netinst
where "I'm not doing anything the installer didn't ask me to do"
(posted last week).

Cheers,
David.

Re: ¿GRUB?

2023-10-29 Thread JavierDebian

El 29/10/23 a las 05:27, casadellabra...@tutanota.com escribió:

Buenos días.

Lo primero es que os alegréis conmigo porque gracias a vuestra ayuda y
al Boot-Repair he podido recuperar el GRUB y, de momento, todo parece
volver a funcionar.

Lo segundo es deciros que sí, que algo más hice cuando traté de instalar
Ungoogled-Chromium.Appimage, pues, como no arrancaba tras el mero cambio
en sus propiedades para que el archivo se ejecutara como un programa,
ejecuté los comandos que recomendaban en una web que, desgraciadamente,
no tuve la precaución de anotar y que no he vuelto a localizar.

Como a partir de ahora sé a dónde dirigirme para conseguir ayuda en mi
trajín con Debian, me prometo a mi mismo no volver a usar
recomendaciones que a lo peor no entiendo bien (no tengo conocimientos
de informática, soy un mero usuario algo atrevido que, eso sí, quiere
confiar, usar y apoyar el software libre y alternativo a los
microsoftes, googles y otras hierbas).

Me pongo a vuestra disposición en lo que pueda ayudar.

Un cordial saludo.

/_Gerardo_/

--
Enviado con Tutanota, disfruta del correo seguro y sin publicidad.

28 oct 2023, 20:13 por n4ch0...@gmail.com:

On 23/10/28 08:03AM, casadellabra...@tutanota.com wrote:

Buenos días.
Soy novato en el uso de Debian GNU/Linux 11 bullseye (x86-64),
Cinnamon 4.8.6; núcleo Linux: 5.10.0-26-amd64; procesador:
Intel© Core™2 CPU T5600 @ 1.83GHz × 2, RAM 2,9 GiB; tarjeta
gráfica: Advanced Micro Devices, Inc. [AMD/ATI] RV515/M52
[Mobility Radeon X1300] (prog-if 00 [VGA controller]).

Después de intentar instalar un nuevo navegador de internet,
concretamente Ungoogled-Chromium, no puedo arrancar el sistema
normalmente, pues la pantalla se queda en negro con la leyenda
"GRUB" junto al cursor intermitente.
He intentado recuperar Grub con Supergrub2, y he arrancado el
sistema pero al ejecutar el comando "sudo grub-install
/dev/sda", como paso previo para recuperar Grub, la consola me
devuelve el siguiente mensaje:

Instalando para plataforma i386-pc.
grub-install: aviso: esta etiqueta de partición GPT no contiene
ninguna Partición de Arranque BIOS; el embebido no será posible.
grub-install: aviso. El embebido no es posible. GRUB podrá ser
instalado con esta configuración únicamente usando listas de
bloques. No obstante, las listas de bloques son INSEGURAS y su
uso está desaconsejado.
grub-install: error: no se procederá con las listas de bloques.

Y cuando posteriormente intento arrancar normalmente el sistema,
éste se bloquea con la pantalla en negro y la leyenda "GRUB" que
antes comenté.

Supongo que podrá reinstalar todo el sistema con un live-usb,
pero antes me he decidido a consultarles:
¿qué podría hacer un profano informático como yo para recuperar
el GRUB o para arrancar el sistema normalmente?

Un cordial saludo.
Gerardo

--
Enviado con Tutanota, disfruta del correo seguro y sin publicidad.

Primero decirte que hayas instalado un browser nada tiene que ver
con lo que te ocurrió.

algo más has hecho que no nos han contado

Y si te conviene, ir con un live cd pero primero debes montar
ciertas carpetas para poder instalarlo, chequea este enlace:

https://slimbook.es/tutoriales/linux/164-3-maneras-de-como-reinstalar-o-reparar-grub-boot-repair-archlinux-o-antergos

Slds

Enhorabuena.

Ahora bien.
Es costumbre en la lista dos cosas:

1 - Detallar qué hiciste para solucionarlo, y en el futuro sirva de
referencia a otra persona.

2 - Cuando se soluciona algo, al final del "Asunto" del correo se agrega
[SOLUCIONADO] para saber que el hilo se cerró, como podés ver acá:

https://lists.debian.org/debian-user-spanish/2023/09/threads.html

Saludos.

JAP

Re: PATH revisited: one PATH to "rule the [Debian] World"

2023-10-29 Thread David Wright

On Sat 28 Oct 2023 at 06:29:19 (+0200), to...@tuxteam.de wrote:
> On Fri, Oct 27, 2023 at 02:46:55PM -0400, Stefan Monnier wrote:
> > >> > https://wiki.debian.org/EnvironmentVariables
> > >> It needs some TLC:
> > >> [quote]
> > >> 1. At the end of booting, the mother of all processes -- init -- is 
> > >> started.
> > >> 2. init runs services as described above.
> > >> [/quote]
> > >> 
> > >> Isn't this rather obsolete as long as systemd has been with us?
> > >
> > > Systemd is just an init by another name. It's process 1 and still
> > > is the mother of all processes.
> > 
> > I don't think there's a need to defend the status quo: the above page
> > may not be fully incorrect, but it is misleading (especially since the
> > `init` is given a monospace font,
> 
> This is misleading indeed. A bit of more detail won't hurt, i.e. that
> you can tell your kernel to use another init in the command line (that's
> how systemd gets started: "init=/lib/systemd", AFAIK)

I think more detail /does/ hurt, as does the edit of 2023-10-27 23:03:36
(though I'm not trying to criticise your best of intentions).

The focus of the page should be
. what environment variables are and how they're set/used,
. the ones that are set by the system and/or are expected
  by any linux user,
. where they can be, and are, set under different login regimes,
. the su change.

I think this wiki page should attempt (even if it can't necessarily
succeed) to answer the FAQ expressed in the Subject line above,
and not get filled with extraneous information.

The Quick Start and Notes and Exceptions are reasonable, except for
the latest addition, "SysV, Systemd and init". There's a "BootProcess"
wiki page where this would be a better fit, and this page needs
a lot of updating for modern times.

Then there's an "Init" wiki page for describing the two flavours,
systemd and sysv, and comparing and contrasting them. This should
stick to inits that bring up a Debian system, about which there's
plenty to say. After all, "Init's /job/ is to start other programs
that are essential to the operation of your system." But telling
the kernel to start an arbitrary process doesn't give it that /job/,
so that option should be treated under either a boot or a system
recovery (the typical use) page.

> >   to suggest it's an actual program name
> > rather than just the name used to refer to the concept of the initial
> > process).
> 
> Agreed.
> 
> > Even saying that "At the end of boot the mother of all processes init is
> > started" is quite confusing, IMO: while it might be true that it happens
> > when the *kernel* finishes the boot, I personally tend to consider this
> > to be rather closer the beginning than the end of the overall
> > boot process.
> 
> The one person's boots are another person's socks, true. The range of
> "boot" goes from the boot loader loading the kernel up to some desktop
> environment up and ready.

Yes, and there's a sequence of wiki pages (some a bit rusty) available
for each step.

Cheers,
David.

Fallo

2023-10-29 Thread Fran

Ha fallado la descarga del paquete:E: 
http://ftp.cica.es/mirrors/Linux/MX-Packages/mx/repo bookworm/main amd64 
mx-installer amd64 23.10.03mx23 is not (yet) available (404 Not Found 
[IP: 150.214.5.134 80])

Re: Which Network Controller Card handling Wi-Fi, Bluetooth, etc., connectivities, is GNU/Linux Approved/certified, and would be (1) compatible with my HP laptop's motherboard, and (2) could replace t

2023-10-29 Thread Andy Smith

Hello,

On Sun, Oct 29, 2023 at 07:04:35PM +0530, Susmita/Rajib wrote:
> Dear Mr. Cater, Thank you for your post, re-forming the subject-line
> and your query.

Why are you reforming Andrew's subject line? It seemed like a very
sensible subject line.

> I request you not to rename the subject of the thread, as the
> continuity of the thread shall be lost and I might not be able to
> trace the thread in future.

But your subject lines are too long. Can you find even one person
besides yourself who thinks that your practice of putting an entire
paragraph into a subject line is a sensible email practice compared
to the subject that Andrew Cater used, and you rejected?

I request that you stop using such lengthy subject lines as they
make it hard to quickly determine what any of your emails are
actually about - the primary purpose of the subject header.

Additionally, I would suggest that if your email software can't cope
with the proper threading of emails when their subject line is
changed, that you should pick better software for the purpose of
reading email. There is no shortage of options that can accomplish
the basic task of presenting threads of conversation.

Thanks,
Andy

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

Re: Which Network Controller Card handling Wi-Fi, Bluetooth, etc., connectivities, is GNU/Linux Approved/certified, and would be (1) compatible with my HP laptop's motherboard, and (2) could replace t

Dear Mr. Cater, Thank you for your post, re-forming the subject-line
and your query.

Since this part is over, please let this subject thread remain closed.
I won't post any further messages ion it. It would be a different
matter if someone posts on the thread and I am obliged to reply to
that query.

Please note that the reply your query on the post with the renamed subject:
Broadcom WiFi/Bluetooth BCM43142 issues

Will be posted on the subject thread:
Please help configure to activate Bluetooth networking for "Network
controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev
01)" card

In fact, I posted my last message without reading yours. Good
coincidence, I have partly replied to your query on output on that
last message.

I request you not to rename the subject of the thread, as the
continuity of the thread shall be lost and I might not be able to
trace the thread in future.

Best wishes,
Rajib
Etc.

No 6.5.8 RT kernel image?

2023-10-29 Thread Scott Denlinger

I'm running trixie/sid, and I don't see a 6.5.8 RT kernel image available.
I'm currently using a 6.5.3 RT kernel, but I don't see an upgrade option.
Did I miss some kind of notification about 6.5 series RT images?

Scott Denlinger

AW: Panic again

2023-10-29 Thread Schwibinger Michael

Hello
Here is Sophie
Im so sorry.

I dont understand this email.

Stupid question.
Update
Crash.
No relationship?

Regards
Sophie

Thank You

Von: to...@tuxteam.de
Gesendet: Freitag, 27. Oktober 2023 04:26
Bis: Cindy Sue Causey
Cc: Debian Users
Betreff: Re: Panic again

On Thu, Oct 26, 2023 at 05:22:37PM -0400, Cindy Sue Causey wrote:

[...]

> An afterthought up top here: Is there a program that will snag and
> retain boot messages specifically geared toward systems that never
> fully boot? [...]

That depends on what you consider "boot messages". Surely you can
only start retaining stuff once you have managed to mount a writable
medium for the first time, which is pretty late in the boot process
(you miss all that interesting early kernel and initramfs action).

There are ways to dump all that via an interface (serial, net),
but then you need to set up things (including another computer
ready and willing to catch and store all that output).

> Has chroot been suggested and/or attempted? I'm imagining that it was
> possibly yes, suggested.

What has been tried is either taking file system snapshots (either
through LVM or with a snapshot capable file system) or installing
in an overlayfs, yes.

I think it hasn't stuck because of the added complexity. I know
I wouldn't use that for esactly that reason. Debian upgrades have
proven to be so rock solid that I just don't see it as a compelling
choice.

Cheers
--
t

Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card

Again, I post the following output for the command:
# sudo pkexec dmesg | grep -i "BCM"

Output:
[3.731659] usb 1-4: Product: BCM43142A0
[   17.507884] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless
Controller 6.30.223.271 (r587334)
[   18.939316] Bluetooth: hci0: BCM: chip id 70
[   18.940314] Bluetooth: hci0: BCM: features 0x06
[   18.956242] Bluetooth: hci0: BCM43142A
[   18.956249] Bluetooth: hci0: BCM43142A0 (001.001.011) build 
[   19.175963] bluetooth hci0: firmware: direct-loading firmware
brcm/BCM43142A0-0a5c-216d.hcd
[   19.175977] Bluetooth: hci0: BCM43142A0 'brcm/BCM43142A0-0a5c-216d.hcd' Patch
[   29.429513] Bluetooth: hci0: BCM: Patch command 227b failed (-110)
[   29.431433] Bluetooth: hci0: BCM: Patch failed (-110)
[   39.669304] Bluetooth: hci0: BCM: Reset failed (-110)

On the webpage:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md,
the portion of the note:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md#notes-about-combined-wifibluetooth-devices
 may please be perused:

Some Bluetooth controller (for example, BCM4354 and BCM4356) are
integrated to WiFi chipset (this can be BCM43XX 802.11ac Wireless
Network Adapter or just simple generic Broadcom PCIE Wireless). These
devices requires two kinds of firmware - first for WiFi, and second
for Bluetooth. Without WiFi firmware Bluetooth will not initialize and
will not work properly. Firmware for WiFi already included to kernel,
but you may need to do additional work to place correct NVRAM.

Resolution needed for the above note.

I used the instructions on the Debian page to install the packages:

https://wiki.debian.org/BluetoothUser

I have installed the packages bluetooth, blueman and the rest.
Have the following installed:
blueman
bluetooth
bluez
bluez-obexd
libbluetooth3
connman

I typed on the terminal:
# blue
then used tab. The following applications are installed.
blueman-adapters   blueman-assistant  blueman-report
blueman-services   bluemoon
blueman-applet blueman-managerblueman-sendto blueman-tray
 bluetoothctl

>From the Start Menu/Preferences/Bluetooth Manager, but the tray icon
isn't visible.

Used:
# sudo blueman-services
blueman-services version 2.1.4 starting
root@debianHPRajib:/home/rajib# sudo service bluetooth status
● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled;
vendor preset: enabled)
 Active: active (running) since Sun 2023-10-29 06:41:39 IST; 9h ago
   Docs: man:bluetoothd(8)
   Main PID: 815 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4566)
 Memory: 1.4M
CPU: 49ms
 CGroup: /system.slice/bluetooth.service
 └─815 /usr/libexec/bluetooth/bluetoothd

Oct 29 06:41:34 debianHPRajib systemd[1]: Starting Bluetooth service...
Oct 29 06:41:35 debianHPRajib bluetoothd[815]: Bluetooth daemon 5.55
Oct 29 06:41:39 debianHPRajib systemd[1]: Started Bluetooth service.
Oct 29 06:41:39 debianHPRajib bluetoothd[815]: Starting SDP server
Oct 29 06:41:40 debianHPRajib bluetoothd[815]: Bluetooth management
interface 1.18 initialized

This is consistently reported as Running.

Then tried: # sudo blueman-assistant
A pop-up says no assistant found

Then:
# sudo blueman-manager
blueman-manager version 2.1.4 starting
blueman-manager 16.17.02 ERRORManager:118 on_dbus_name_appeared:
Default adapter not found, trying first available.
blueman-manager 16.17.02 ERRORManager:122 on_dbus_name_appeared:
No adapter(s) found, exiting

Then tried:
# sudo blueman-adapters
blueman-adapters version 2.1.4 starting
blueman-adapters 16.18.13 ERRORAdapter:53 __init__  : No adapter(s) found

Then tried:
# sudo blueman-applet
blueman-applet version 2.1.4 starting
There is an instance already running

Then tried:
# sudo blueman-tray
blueman-tray version 2.1.4 starting
There is an instance already running

Then tried:
# sudo blueman-services
blueman-services version 2.1.4 starting
A window opens with title: local services and presents options.

Then tried:
# sudo blueman-report
Terminating blueman-applet
Describe your next action (keep empty if done):
Traceback (most recent call last):
  File "/usr/bin/blueman-report", line 57, in 
response = urllib2.urlopen('https://api.github.com/gists',
data.encode('UTF-8')).read()
  File "/usr/lib/python3.9/urllib/request.py", line 214, in urlopen
return opener.open(url, data, timeout)
  File "/usr/lib/python3.9/urllib/request.py", line 523, in open
response = meth(req, response)
  File "/usr/lib/python3.9/urllib/request.py", line 632, in http_response
response = self.parent.error(
  File "/usr/lib/python3.9/urllib/request.py", line 561, in error
return self._call_chain(*args)
  File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
  File "/usr/lib/python3.9/urllib/request.py", line 641, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)

Broadcom WiFi/Bluetooth BCM43142 issues

2023-10-29 Thread Andrew M.A. Cater

On Sun, Oct 29, 2023 at 03:24:00PM +0530, Susmita/Rajib wrote:

Rajib,

Please note the change of subject.

> I have had a conversation with the Team ThinkPenguin for the wireless
> N model model. Their USB WiFi dongle is only for WiFi connectivity.
> Not for Bluetooth.
> 
> The team has been very transparent with sharing information, and I
> thank you for letting me know about such an empowering team surviving
> within the proprietary universe.
> 

The WiFi and Bluetooth connectivity for your laptop is almost certainly
all provided by the Broadcom chipset and the firmware it requires.

If not, it may be provided by the main laptop chipset - so maybe Intel?

You have been given (off list) a method for configuring kernel modules and
using DKMS to provide support when each kernel is updated.

You may need to download a firmware "blob" and place that in /lib/firmware

The method you've been given is by using module-assistant to automate
the process of building the kernel modules

> Since the wl module already has configured and restored the WiFi
> connectivity for my laptop, I wouldn't require the said dongle.
> 
> Shortly, I will post for configuring the Bluetooth connectivity for my
> HP laptop.
> 

So - you already have some of that in place: https://wiki.debian.org/wl

As root, you can run the command dmesg to see what the kernel finds at boot.
It produces a lot of output, so you can use grep to filter that.

What does the output of: 

dmesg | grep Bluetooth | less

produce for you - some of that should give you a clue as to what firmware
is found or is missing.

> So your support is all the more expected.
> 
> Best wishes,
> Rajib
>

With best wishes, as always

Andy Cater

[amaca...@debian.org]

Re: [Bookworm] collecting sensors data

2023-10-29 Thread mick.crane

On 2023-10-28 18:31, Roy J. Tellason, Sr. wrote:

On Saturday 28 October 2023 07:25:39 am gene heskett wrote:

On 10/28/23 00:14, Max Nikulin wrote:
> On 28/10/2023 01:39, Greg wrote:
>> I just noticed that there is no rrdcollect in Bookworm. What is the
>> "proper" way of collecting sensors readings?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029995 :
>> please consider removing rrdcollect. Its a tool/daemon to collect
>> metrics from the local system into RRD files. There are quite a number
>> of alternatives in Debian to do the same, better (munin, et al).
>
I just looked at munin in synaptic, But while there lots of parts to 
it,

there is not a single word that indicates what it does? Absolutely
nothing that tells me it can monitor the system fans or measure the
systems voltages.  What does it actually DO?

I've seen that fairly often,  particularly with software packages.
It's a real aggravation at times.

I've sometimes thought it would be useful if at the top of man pages 
there was.

"Why would I use this" with explanation.

mick

Summary of understanding the bootin problem [WAS Re: AW: Panic again]

2023-10-29 Thread Andrew M.A. Cater

On Sat, Oct 28, 2023 at 02:02:29PM +, Schwibinger Michael wrote:
> 

SUMMARY

After a lot of questions backwards and forwards:

Sophie has: 

A desktop machine with one user and regular backups.
It was originally running Debian 9 and has been updated to Debian 11.
It has booting problems: it doesn't boot from the latest kernel and hangs.
It does run if started from "recovery"

>From reading the replies: it sounds like a kernel panic with a screenful of
text. We don't know exactly what. The machine is an older machine if it
has been running since Debian 9. 

This could be from a number of causes: a misconfigured/failed update to
Debian 11, Grub not being installed properly, maybe even a boot partition
being full so that the kernel was not installed.

Suggestions made here:

* Boot from an external medium, run recovery from there and reinstall Grub.

For Sophie: chroot is a way of moving to and working from the filesystem
on disk once you have booted from an external medium like a USB stick.
If you use something else to boot from - the installer, for example, then
changes you run are in memory until you write them. The recovery mode of
the installer runs entirely in memory.

At one point you "change root" and pivot to the other filesystem.
If the filesystem you want to use is mounted at /target

cd /target
chroot .

Now you are running from /target filesystem 

* Run a complete install using the Debian 12 Bookworm installer 

This might be the easiest way forward but will need someone to work out
* how to write the install medium - netinst.iso from the Debian website -
* how to persuade the desktop machine to boot from something other
than the hard disk
> 

With every good wish, as ever,
> 
> I did only understand
> chroot.
> 
> Is this another kind of booting?
> 
> Does this repair
> DEBIAN?.
> 
> If yes
> what do I have to do?
> 
> 
> https://en.wikipedia.org/wiki/Chroot
> I did find this.
> 
> Good idea?
> 
> 
> Regards Sophie
> 
> 
> 

Andy
[amaca...@debian.org]
> 
> 
> 
> Von: Cindy Sue Causey 
> Gesendet: Donnerstag, 26. Oktober 2023 21:22
> An: Debian Users 
> Betreff: Re: Panic again
> 
> On 10/26/23, Schwibinger Michael  wrote:
> >
> > Good afternoon
> > Thank You for help.
> >
> > I ll answer into Your email
> > with
> > +++
> >
> >
> > Von: Andrew M.A. Cater 
> > Gesendet: Mittwoch, 25. Oktober 2023 12:04
> > An: Schwibinger Michael 
> > Betreff: Re: AW: AW: Panic again any idea IV
> >
> > On Wed, Oct 25, 2023 at 10:59:09AM +, Schwibinger Michael wrote:
> >> Good morning
> >>
> >> Thank You.
> >>
> >> I do booting.
> >> Crash.
> >> Bug report I did send.
> >>
> >
> > Hi Sophie,
> >
> > Thank you. You didn't really send a bug report
> >
> >
> > +++
> > I know.
> > But how can I produce a bug report
> > when the PC is frozen?
> 
> 
> An afterthought up top here: Is there a program that will snag and
> retain boot messages specifically geared toward systems that never
> fully boot? It seems like I've seen that topic come up and be answered
> one single time in the last ~25 years. I actually tried to find some
> form of that type of program the other day when I saw an earlier
> portion of this thread then. I was thinking, hoping maybe such a
> program could possibly be installed via chroot if it does exist.
> 
> Now my original thought..
> 
> Has chroot been suggested and/or attempted? I'm imagining that it was
> possibly yes, suggested.
> 
> If not, what about attempting a chroot to then next attempt apt or
> apt-get update then upgrade?
> 
> As a user who has occasionally battled issues, I know that, ideally,
> it would be nice, i.e. satisfying, to find the cause of bigger issues
> like this. At some point, I also know firsthand that outing the cause
> becomes less important when weighed against moving on in Life. :)
> 
> Apt/apt-get upgrade via chroot would potentially help preserve a
> particular setup rather than going with a new install if that is why
> this continues to be a topic.
> 
> If anyone can think of a reason why running apt/apt-get in chroot
> would only stand to cause data harm in this particular situation, that
> would be great to know.
> 
> My firsthand experience has been that tinkering via chroot has
> eventually gotten me back up and running maybe 99% of the time,
> including against multiple kernel panic-ish fails a few years ago.
> 
> Biggest reason my chroot repair attempts ever failed was due to not
> properly mounting maybe 4 or 5 basic necessities that apt/apt-get use
> to properly install programs. /dev and /proc come first to mind as
> examples there. That knowledge came from working through the manual
> steps necessary during debootstrap installs, in case that ever helps
> anyone else.
> 
> Cindy :)
> --
> Talking Rock, Pickens County, Georgia, USA
> * runs with a retirement state of mind *
>

Re: Which Network Controller Card handling Wi-Fi, Bluetooth, etc., connectivities, is GNU/Linux Approved/certified, and would be (1) compatible with my HP laptop's motherboard, and (2) could replace t