date:20210828



On Sat, 28 Aug 2021 10:19:23 -0400 Jude Informed me about Re:
Network down incorrect

> As part of your reinstall process did you delete all partitions then
> run wipefs -af on the disk?  Failure to do so may have left old
> artifacts of the previous system on the drive which may be messing up
> your current installation.
> 
> 
> On Sat, 28 Aug 2021, Charlie wrote:
> 
> >
> > From my keyboard:
> >
> > Hello all,
> >
> > Since Bullseye went stable, updated on my 12 month old HP
> > laptop. When attempting to bring up the wireless interface
> > with ifup.
> >
> > The message on the screen tells me the "network is down", which is
> > incorrect. Because on another Bullseye machine it works perfectly.
> > as it did on this one before it went stable.
> >
> > It gives the message:
> >
> > RTNETLINK answers: Operation not possible due to RF-kill
> >
> > Then tries to connect for about 12 or so tries.
> >
> > I have not installed rfkill, and can't find it to uninstall it.
> >
> > On the web there is a reference to this "RTNETLINK answers:
> > Operation not possible due to RF-kill" on Archlinux where it was
> > solved by bringing the BIOS back to default. I tried that, but
> > temporarily locked myself out of the system. Then asking me to
> > install an operating system on the hard drive. I brought that back
> > buy returning the BIOS to when it booted the system.
> >
> > I can use the Ethernet port and cable to connect to the internet
> > with that machine, however, did connect wirelessly when Bullseye
> > was testing.
> >
> > Any pointers would be appreciated.
> >
> > TIA,
> > Charlie

No I didn't reinstall. I just let Bullseye move from testing to stable.

Thank you,
Charlie

-- 
Registered Linux User:- 329524

***

What do you want to get enlightened for? You may not like it.
-- Shunryu Suzuki

***
Debian GNU/Linux - Magic indeed.

-

Debian stable + backports + testing

2021-08-28 Thread Yoann LE BARS



Hello everybody out there!

First, I want to thank and congratulate Debian developers for Debian
11. I am about to upgrade to this version.

Usually, I am using Debian stable with backports, and I am quite happy
with it. However, it turns out I will probably have to test some early
versions of some software and libraries that are not in backports, such
as Ardour and SDL2.

Therefore, I am considering using a bit of testing into stable +
backports. I am wondering if anyone can give me some advice in doing so.
I guess I should set its priority like this:

Package: *
Pin: release o=Debian, a=testing
Pin-Priority: 50

Can anyone give me some piece of advice with this?

Best regards.

-- 
Yoann LE BARS
https://le-bars.net/yoann/
Diaspora* : yleb...@framasphere.org

Re: Network down incorrect........



On Sat, 28 Aug 2021 17:14:29 +0200 Marco Informed me about Re:
Network down incorrect

> On 28.08.21 15:38, Charlie wrote:
> > 
> > From my keyboard:
> > 
> > Hello all,
> > 
> > Since Bullseye went stable, updated on my 12 month old HP
> > laptop. When attempting to bring up the wireless interface
> > with ifup.
> > 
> > The message on the screen tells me the "network is down", which is
> > incorrect. Because on another Bullseye machine it works perfectly.
> > as it did on this one before it went stable.
> > 
> > It gives the message:
> > 
> > RTNETLINK answers: Operation not possible due to RF-kill
> > 
> > Then tries to connect for about 12 or so tries.
> > 
> > I have not installed rfkill, and can't find it to uninstall it.
> > 
> > On the web there is a reference to this "RTNETLINK answers:
> > Operation not possible due to RF-kill" on Archlinux where it was
> > solved by bringing the BIOS back to default. I tried that, but
> > temporarily locked myself out of the system. Then asking me to
> > install an operating system on the hard drive. I brought that back
> > buy returning the BIOS to when it booted the system.
> > 
> > I can use the Ethernet port and cable to connect to the internet
> > with that machine, however, did connect wirelessly when Bullseye
> > was testing.
> > 
> > Any pointers would be appreciated.
> > 
> > TIA,
> > Charlie
> > 
> > East Gippsland Wildlife Rehabilitators Inc..
> > http://www.egwildlife.com.au/
> >   
> 
> Temporary workaround:
> When I have had such problem in the past and also no rfkill
> installed, I simply installed rfkill (and for my use case created an
> alias for the CLI and shortcut for the GUI for reactivating WiFi and
> Bluetooth easily, if they would be blocked again).
> This does not explain where the problem comes from, but installing
> and using rfkill is not a big thing and quickly gets you out of
> trouble and up and working again.
> In my case, if I remember at least a little bit the case, it was the 
> graphical desktop environment which deactivated the wireless devices 
> upon shutdown, but then was not able to reactivate them at system
> start, letting the devices stay blocked, obviously having used some
> rfkill alike implementation in the GUI code itself. Since I installed
> the rfkill package and reactivated the devices manually at the CLI
> the problem disappeared somehow. I do not remember anymore if the
> problem disappeared instantely or after some few rounds of shutdown
> and reboot with manual rfkill intervention, or simply because maybe
> around that time also a GUI update arrived. I still assume that it
> was a bug in the GUI code, using maybe some internal rfkill alike
> code, but being buggy, having the feature to deactivate those devices
> working correctly but failing to reactivate them. As I quickly
> couldn't reproduce the problem no more, I could not provide a bug
> report. I did not even test what would happen if I now would remove
> the rfkill package again. Installation and usage of that package
> solved my problem first hand as a workaround, and then the problem
> anyway disappeared shortly after, and eventually I decided to simply
> keep rfkill installed.
> 
> ---
> Good Luck!
> Marco.

Thank you Marko.

That sounds like something I read, but seemed to be a strange thing to
do. However, I will take your advice since you have had experience with
it and found it works, by magic or any other way. Working is what would
be good, so whatever is required.

Thank you,
Charlie
-- 
Registered Linux User:- 329524

***

A society grows great when old men plant trees whose shade they
know they shall never sit in. Old Greek Proverb

***
Debian GNU/Linux - Magic indeed.

-

Re: Network down incorrect........



On Sat, 28 Aug 2021 10:43:07 -0400 Eike Informed me about Re:
Network down incorrect

> On Samstag, 28. August 2021 09:38:44 -04 Charlie wrote:
> > From my keyboard:
> >
> > Hello all,
> >
> > Since Bullseye went stable, updated on my 12 month old HP
> > laptop. When attempting to bring up the wireless interface
> > with ifup.
> >
> > The message on the screen tells me the "network is down", which is
> > incorrect. Because on another Bullseye machine it works perfectly.
> > as it did on this one before it went stable.
> >
> > It gives the message:
> >
> > RTNETLINK answers: Operation not possible due to RF-kill
> >
> > Then tries to connect for about 12 or so tries.
> >
> > I have not installed rfkill, and can't find it to uninstall it.
> >
> > On the web there is a reference to this "RTNETLINK answers:
> > Operation not possible due to RF-kill" on Archlinux where it was
> > solved by bringing the BIOS back to default. I tried that, but
> > temporarily locked myself out of the system. Then asking me to
> > install an operating system on the hard drive. I brought that back
> > buy returning the BIOS to when it booted the system.
> >
> > I can use the Ethernet port and cable to connect to the internet
> > with that machine, however, did connect wirelessly when Bullseye was
> > testing.
> >
> > Any pointers would be appreciated.
> >
> > TIA,
> > Charlie
> >
> > East Gippsland Wildlife Rehabilitators Inc..
> >http://www.egwildlife.com.au/  
> rfkill is a Linux device
> the program rfkill is not necessarily installed but it might help you
> to identify the underlying problem.
> A shot into the dark: This smells like a firmware problem.
> 
> 
> --
> Eike Lantzsch ZP6CGE
> 

Thank you. I tried to install the firmware package and it said it was
the latest version and wouldn't. I may have to purge it, then install
the firmware again.

Thank you,
Charlie

-- 
Registered Linux User:- 329524

***

Destiny is not a matter of chance, it is a matter of choice; it
is not a thing to be waited for, it is a thing to be achieved.
W J Bryan

***
Debian GNU/Linux - Magic indeed.

-

Re: Network down incorrect........



On Sat, 28 Aug 2021 11:39:13 -0500 David Informed me about Re:
Network down incorrect

> On Sat 28 Aug 2021 at 23:38:44 (+1000), Charlie wrote:
> > Since Bullseye went stable, updated on my 12 month old HP
> > laptop. When attempting to bring up the wireless interface
> > with ifup.
> > 
> > The message on the screen tells me the "network is down", which is
> > incorrect. Because on another Bullseye machine it works perfectly.
> > as it did on this one before it went stable.  
> 
> It's a matter of perspective: it means the network is down on this
> machine. That being so, it can't venture an opinion on the state of
> the external network.
> 
> > It gives the message:
> > 
> > RTNETLINK answers: Operation not possible due to RF-kill
> > 
> > Then tries to connect for about 12 or so tries.
> > 
> > I have not installed rfkill, and can't find it to uninstall it.  
> 
> The name of the command is somewhat deceptive. Just as the "kill"
> command doesn't just kill processes but sends them signals, so
> "rfkill" both disables and enables wireless networks. You want it
> (from the package of the same name).
> 
> > On the web there is a reference to this "RTNETLINK answers:
> > Operation not possible due to RF-kill" on Archlinux where it was
> > solved by bringing the BIOS back to default. I tried that, but
> > temporarily locked myself out of the system. Then asking me to
> > install an operating system on the hard drive. I brought that back
> > buy returning the BIOS to when it booted the system.
> > 
> > I can use the Ethernet port and cable to connect to the internet
> > with that machine, however, did connect wirelessly when Bullseye
> > was testing.
> > 
> > Any pointers would be appreciated.  
> 
> I think the days of providing a separate button for killing wireless
> have passed. (My old Acer has a badly placed button that's easy to
> accidently press with your trouser belt.)
> 
> Nowadays, it's usual to provide instead a function key to toggle
> wireless instead. By "function" key, I mean the locally modified
> functions, often call "hotkeys", usually selected by pressing some
> coloured Fn modifier. You might have a picture of an aeroplane¹
> engraved on the key, and typically there are other functions like
> screen-blank, sleep, volume, brightness, etc in close proximity.
> 
> Running rfkill with no arguments should show you the status of
> the WiFi, Bluetooth etc as Hard/Soft (un)blocked as appropriate.
> 
> An alternative to all this is that you have firmware installed on
> buster that you haven't yet installed for bullseye. One would hope
> that an upgrade would carry it over, but you need to check.
> 
> ¹ which tells you why this is easy to turn on/off: who wants to
>   be fiddling with the BIOS while sitting waiting for takeoff.
> 
> Cheers,
> David.
> 

Thanks David,

This is a bullseye system that went from testing to stable, so will
give the things you suggest a larrup and see how I go.

But later today. I have a kangaroo to transport to another wildlife
carer.

Thank you,
Charlie

-- 
Registered Linux User:- 329524

***

Life is an adventure in forgiveness. --- Norman Cousins

***
Debian GNU/Linux - Magic indeed.

-

Re: amdgpu broken on bookworm?


On 28/08/2021 17:33, Jeffrey Chimene wrote:



Thanks! That was it. I don't know why it never loaded amdgpu; which 
forced me to add nomodeset.


Glad I could help! :) So everything is working now, removing this 
nomodeset option solved it?


--

With kindest regards, piorunz.

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

Debian 11 and Win10 dual boot -- SOLVED

2021-08-28 Thread Intense Red

   The problem was that Win10 would constantly overwrite the MBR and blow away 
GRUB which forced the computer to boot straight into Windows.

   The solution is to go into Windows, open a command prompt/shell as the 
Windows administrator and run:

 "bcedit /set {bootmgr} path \EFI\debian\grubx64.efi"


-- 
"If you continue running Windows, your system may become unstable." -- Quote 
from the infamous Blue Screen of Death from Microsoft Windows95.(and they 
weren't lying!)

Re: CUPS permissions >Fixed

2021-08-28 Thread Brian

On Sat 28 Aug 2021 at 15:38:40 -0400, Greg Wooledge wrote:

> On Sat, Aug 28, 2021 at 08:31:56PM +0100, Brian wrote:
> > Nobody should be logging into the web interface as root.
> 
> As far as "nobody should...", I don't see the harm.  It's not like the
> password is going over a network cable (or wireless EM).  It's just
> loopback.
> 
> Also note the official instructions from the CUPS web site:
> 
> http://www.cups.org/doc/overview.html
> 
>   When you are asked for a username and password, enter your login
>   username and password or the "root" username and password. On macOS®,
>   the login username (or "short name") is typically your first and last
>   name in lowercase.
> 
> Conveniently, there are no useful instructions on this page that tell
> you how to arrange it so that your regular username and password will
> work.  That only leaves "root".
> 
> Then again, there are no useful instructions on this page about how
> to actually *get to* the web interface.  You have to find that on your
> own.
> 
> There's truly a lot to be desired about this documentation.

I suggest you submit a report to

 htps://github.com/OpenPrinting/cups/issues

Your points are pertinent.

-- 

Brian.

>

Re: CUPS permissions >Fixed

2021-08-28 Thread Greg Wooledge

On Sat, Aug 28, 2021 at 08:31:56PM +0100, Brian wrote:
> Nobody should be logging into the web interface as root.

As far as "nobody should...", I don't see the harm.  It's not like the
password is going over a network cable (or wireless EM).  It's just
loopback.

Also note the official instructions from the CUPS web site:

http://www.cups.org/doc/overview.html

  When you are asked for a username and password, enter your login
  username and password or the "root" username and password. On macOS®,
  the login username (or "short name") is typically your first and last
  name in lowercase.

Conveniently, there are no useful instructions on this page that tell
you how to arrange it so that your regular username and password will
work.  That only leaves "root".

Then again, there are no useful instructions on this page about how
to actually *get to* the web interface.  You have to find that on your
own.

There's truly a lot to be desired about this documentation.

Re: Specifying dedicated partions during install - pros/cons?

2021-08-28 Thread songbird

David Wright wrote:
> On Sat 28 Aug 2021 at 10:34:34 (-0500), Richard Owlett wrote:
>> During the partitioning phase of the install process, the user is
>> given the option of creating dedicated partitions. I chose to do it
>> for /home and swap {depending on machine I may also have a dedicated
>> project partition}.
>> 
>> That the partition phase presents a menu of ~10 choices indicates the
>> Debian team considers this an significant feature.
>> 
>> Where would I find a discussion of why the particular items rated
>> inclusion on the menu?
>
> Do you mean this?
>
>┌┤ [!!] Partition disks ├┐
>││
>│ Mount point for this partition:│
>││
>│  / - the root file system  │
>│  /boot - static files of the boot loader   │
>│  /home - user home directories │
>│  /tmp - temporary files│
>│  /usr - static data│
>│  /var - variable data  │
>│  /srv - data for services provided by this system  │
>│  /opt - add-on application software packages   │
>│  /usr/local - local hierarchy  │
>│  Enter manually│
>│  Do not mount it   │
>││
>│   │
>││
>└┘
>
> What's to discuss? They're all there, those that are sensible.
> Which would you consider for exclusion from this list?
> Or are you suggesting they've missed one? What?

  aren't these historically relevant possible choices for someone
doing an expert install?

  to find out where they come from you would have to go back 
into the early years of unix and then read forwards to see
if you can find where the newer one(s) were added (srv seems
to have been added after the web and web services came along).


> In case you're actually talking about:
>
>┌───┤ [!!] Partition disks ├───┐
>│  │
>│ How to use this partition:   │
>│  │
>│  Ext4 journaling file system │
>│  Ext3 journaling file system │
>│  Ext2 file system│
>│  btrfs journaling file system│
>│  JFS journaling file system  │
>│  XFS journaling file system  │
>│  FAT16 file system   │
>│  FAT32 file system   │
>│  swap area   │
>│  physical volume for encryption  │
>│  physical volume for RAID│
>│  physical volume for LVM │
>│  do not use the partition│
>│  │
>│ │
>│  │
>└──┘
>
> then repost (but you might as well give answers as above).

  songbird

Re: CUPS permissions >Fixed

2021-08-28 Thread Brian

On Sat 28 Aug 2021 at 07:11:55 -0700, Peter Ehlert wrote:

> 
> On 8/26/21 5:53 AM, Greg Wooledge wrote:

[...]

> > 2) Install cups.
> * cups was not installed by default. The Brother installer did flag that
> first off, easily corrected

A print queue was installed by Sun 22 Aug 2021 05:44:11 AM PDT. So cups
was present when you first posted.

> > 3) Visit http://localhost:631/ in a GUI web browser.  Make sure Javascript
> > is allowed.
> > 
> > 4) At some point, when you try to do stuff to the printers in the browser,
> > you will be prompted for a username and password, using HTTP basic
> > authentication.  When this occurs, you should login as root, using
> > root's password.
> 
> BINGO: I was not using root

That's not correct. Your user was not given root priviledges is the
correct conclusiom. You, root  and the user are not the same entities.
What does "I" refer to?

A responsible administrator does not hand out administrator priviledges
to anyone who comes along. Put the user into the lpadmin group.

Nobody should be logging into the web interface as root.

Glad you got it sorted, though.

(Incidentally, why you have any need for the Brother drivers is beyond
me).

-- 
Brian.

> 
> > 
> > 5) If you screwed up and logged in as yourself, restart the web browser
> > so that you can get the HTTP basic authentication dialog box again.  Go
> > to step 4.
> > 
> > 6) Once the printer is set up via the browser, you should be able to see
> > it and print to it from the command line.  "lpstat -t" to see all of
> > the printers and their status.  "lp" or "lpr" to print a text file.
> $ lpstat -t
> scheduler is running
> no system default destination
> device for MFCL3770CDW: 
> dnssd://Brother%20MFC-L3770CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-b4220033103b
> MFCL3770CDW accepting requests since Sun 22 Aug 2021 05:44:11 AM PDT
> printer MFCL3770CDW is idle.  enabled since Sun 22 Aug 2021 05:44:11 AM PDT
> > 
> > Any variants on this procedure will require knowledge that I don't
> > personally possess.  E.g. if for some reason you refuse to set a root
> > password, then you may have to set up a printer-admin account which
> > has the appropriate privileges, and a password, and then use that
> > instead of root.  I don't know what those privs would be.
> > 
> Summary:
> 
> I removed my browser cookie for "localhost"
> 
> restarted the browser
> 
> when CUPS requested a password I used "root"
> 
> I am now able to add printers and edit all options
> 
> Thanks to all for the assistance and Education
> 
>

Re: amdgpu broken on bookworm?

On Sat 28 Aug 2021 at 08:36:32 (-0400), songbird wrote:
> Jeffrey Chimene wrote:
> 
>   just to note that using "bookworm" in your subject line can
> give the implication that "bookworm" is actually released which
> it hasn't.  it is much better to use the keyword "testing" in
> the subject line instead.

I don't know where you got that from. A Release gets a *number*.
(The number that might be given to trixie will depend on how
superstitious the Debian release team is.) It's legitimate to talk
about, say, features that might be retained in bookworm, but dropped
by trixie. That's what the codenames are for.

> > Any debugging tips?
> 
>   it does not take that much space to set up a separate 
> partition for stable on a system to keep a working version
> available and for comparison.  this is what i do.

Ditto, except that typically mine are stable and oldstable.
Since a fortnight ago, they've become oldstable and oldoldstable.
See? Rather ambiguous. (They're buster and stretch.)

To interpret "testing" in an arbitrary post, I have to consult
my file listing the release dates of Debian suites.

0.01 1993-08
0.90 1993-12
0.91 1994-01
0.93R5   1995-03
0.93R6   1995-10-26
1.0  unreleased
buzz 1.1 1996-06-17
rex 1.2  1996-12-12
bo 1.3   1997-07-02/-06-05
hamm 2.0 1998-07-24
slink 2.11999-03-09
potato 2.2   2000-08-15
woody 3.02002-07-19
sarge 3.12005-06-06
etch 4.0 2007-04-08
lenny 5.02009-02-14
squeeze 6.0  2011-02-06
wheezy 7 2013-05-04
jessie 8 2015-04-25
stretch 92017-06-17
buster 102019-07-06
bullseye 11  2021-08-14
bookworm
trixie
sid (when woody started)

Cheers,
David.

Re: Debian 11 and Win10 dual boot

On Fri 27 Aug 2021 at 21:35:38 (-0500), Intense Red wrote:
>On a new HP Laptop pre-installed with Win10 Home edition installed on an 
> SSD. In the laptop's BIOS Secure Boot was turned off.
> 
>A fresh copy of Debian 11 was installed into the machine's 1TB HD. After 
> reboot, GRUB comes up normally and Linux works fine.
> 
>But once Windows is chosen from GRUB Windows overwrites the MBR and on 
> subsequent boots GRUB has been disappeared and the machine boots straight 
> into 
> Windows every time.
> 
>Question: How can Windows be lobotomized to stop it from overwriting the 
> MBR and doing this behavior?

>From your talk about "overwriting the MBR", it suggests that you
haven't read around the topic of UEFI booting or dual booting.
You might want to look through pages like:
https://wiki.archlinux.org/title/Dual_boot_with_Windows
https://unix.stackexchange.com/questions/524622/what-is-the-relation-between-uefi-and-grub
just to get an idea of the issues involved. Then, when you boot into
Windows and linux, you'll be aware of where to look for diagnostic
information on the problem.

If there are better starting points than those references, I'm sure
people will post them here.

Lastly, it might help to post how you booted the Debian installer,
and what choices you made when installing Grub during the installation.

Cheers,
David.

Re: Specifying dedicated partions during install - pros/cons?

On Sat 28 Aug 2021 at 10:34:34 (-0500), Richard Owlett wrote:
> During the partitioning phase of the install process, the user is
> given the option of creating dedicated partitions. I chose to do it
> for /home and swap {depending on machine I may also have a dedicated
> project partition}.
> 
> That the partition phase presents a menu of ~10 choices indicates the
> Debian team considers this an significant feature.
> 
> Where would I find a discussion of why the particular items rated
> inclusion on the menu?

Do you mean this?

   ┌┤ [!!] Partition disks ├┐
   ││
   │ Mount point for this partition:│
   ││
   │  / - the root file system  │
   │  /boot - static files of the boot loader   │
   │  /home - user home directories │
   │  /tmp - temporary files│
   │  /usr - static data│
   │  /var - variable data  │
   │  /srv - data for services provided by this system  │
   │  /opt - add-on application software packages   │
   │  /usr/local - local hierarchy  │
   │  Enter manually│
   │  Do not mount it   │
   ││
   │   │
   ││
   └┘

What's to discuss? They're all there, those that are sensible.
Which would you consider for exclusion from this list?
Or are you suggesting they've missed one? What?

In case you're actually talking about:

   ┌───┤ [!!] Partition disks ├───┐
   │  │
   │ How to use this partition:   │
   │  │
   │  Ext4 journaling file system │
   │  Ext3 journaling file system │
   │  Ext2 file system│
   │  btrfs journaling file system│
   │  JFS journaling file system  │
   │  XFS journaling file system  │
   │  FAT16 file system   │
   │  FAT32 file system   │
   │  swap area   │
   │  physical volume for encryption  │
   │  physical volume for RAID│
   │  physical volume for LVM │
   │  do not use the partition│
   │  │
   │ │
   │  │
   └──┘

then repost (but you might as well give answers as above).

Cheers,
David.

Re: Network down incorrect........

On Sat 28 Aug 2021 at 23:38:44 (+1000), Charlie wrote:
>   Since Bullseye went stable, updated on my 12 month old HP
>   laptop. When attempting to bring up the wireless interface with
>   ifup.
> 
> The message on the screen tells me the "network is down", which is
> incorrect. Because on another Bullseye machine it works perfectly. as
> it did on this one before it went stable.

It's a matter of perspective: it means the network is down on this
machine. That being so, it can't venture an opinion on the state of
the external network.

> It gives the message:
> 
> RTNETLINK answers: Operation not possible due to RF-kill
> 
> Then tries to connect for about 12 or so tries.
> 
> I have not installed rfkill, and can't find it to uninstall it.

The name of the command is somewhat deceptive. Just as the "kill"
command doesn't just kill processes but sends them signals, so
"rfkill" both disables and enables wireless networks. You want it
(from the package of the same name).

> On the web there is a reference to this "RTNETLINK answers: Operation
> not possible due to RF-kill" on Archlinux where it was solved by
> bringing the BIOS back to default. I tried that, but temporarily locked
> myself out of the system. Then asking me to install an operating system
> on the hard drive. I brought that back buy returning the BIOS to when
> it booted the system.
> 
> I can use the Ethernet port and cable to connect to the internet with
> that machine, however, did connect wirelessly when Bullseye was testing.
> 
> Any pointers would be appreciated.

I think the days of providing a separate button for killing wireless
have passed. (My old Acer has a badly placed button that's easy to
accidently press with your trouser belt.)

Nowadays, it's usual to provide instead a function key to toggle
wireless instead. By "function" key, I mean the locally modified
functions, often call "hotkeys", usually selected by pressing some
coloured Fn modifier. You might have a picture of an aeroplane¹
engraved on the key, and typically there are other functions like
screen-blank, sleep, volume, brightness, etc in close proximity.

Running rfkill with no arguments should show you the status of
the WiFi, Bluetooth etc as Hard/Soft (un)blocked as appropriate.

An alternative to all this is that you have firmware installed on
buster that you haven't yet installed for bullseye. One would hope
that an upgrade would carry it over, but you need to check.

¹ which tells you why this is easy to turn on/off: who wants to
  be fiddling with the BIOS while sitting waiting for takeoff.

Cheers,
David.

Re: amdgpu broken on bookworm?




On 8/28/21 08:56, piorunz wrote:

picasso*.bin files are part of firmware-amd-graphics package.

$ apt-file search picasso_asd.bin
firmware-amd-graphics: /lib/firmware/amdgpu/picasso_asd.bin

These files are present in your system when you package installed.
Their presence doesn't mean that they will get loaded.

I can see in your inxi:

$ inxi -G
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: N/A
   Display: server: X.Org 1.20.11 driver: loaded: ati,vesa
unloaded: fbdev,modesetting,radeon resolution: 1440x876~1Hz
   OpenGL: renderer: N/A v: N/A

You have no driver loaded, because you added nomodeset to boot
parameters. nomodeset instructs Linux kernel to not load video drivers.
You have installed non-free drivers (firmware-amd-graphics) and told
kernel not to load them.

Try without nomodeset and report back.
I may have missed your reply if you already did, please try to reply
with one post, not several consecutive posts, to keep discussion more
organized.

Thanks! That was it. I don't know why it never loaded amdgpu; which 
forced me to add nomodeset.

Re: amdgpu broken on bookworm?


picasso*.bin files are part of firmware-amd-graphics package.

$ apt-file search picasso_asd.bin
firmware-amd-graphics: /lib/firmware/amdgpu/picasso_asd.bin

These files are present in your system when you package installed.
Their presence doesn't mean that they will get loaded.

I can see in your inxi:

$ inxi -G
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: N/A
   Display: server: X.Org 1.20.11 driver: loaded: ati,vesa
unloaded: fbdev,modesetting,radeon resolution: 1440x876~1Hz
   OpenGL: renderer: N/A v: N/A

You have no driver loaded, because you added nomodeset to boot
parameters. nomodeset instructs Linux kernel to not load video drivers.
You have installed non-free drivers (firmware-amd-graphics) and told
kernel not to load them.

Try without nomodeset and report back.
I may have missed your reply if you already did, please try to reply
with one post, not several consecutive posts, to keep discussion more
organized.

I can see that you said "It enables display twitching during boot. When
XDM gains control, it will try to set the display mode."
You have to continue tests without nomodeset option, otherwise you have
no driver and that's it.

Specifying dedicated partions during install - pros/cons?

2021-08-28 Thread Richard Owlett

During the partitioning phase of the install process, the user is given 
the option of creating dedicated partitions. I chose to do it for /home 
and swap {depending on machine I may also have a dedicated project 
partition}.


That the partition phase presents a menu of ~10 choices indicates the 
Debian team considers this an significant feature.


Where would I find a discussion of why the particular items rated 
inclusion on the menu?


TIA

Re: amdgpu broken on bookworm?


On 8/28/21 07:07, Jeffrey Chimene wrote:

On 8/28/21 07:04, Jeffrey Chimene wrote:
No complaints about missing picasso firmware. I'll try removing the 
/lib/firmware to see what happens.


So this doesn't do what I thought it would. It's probably not even 
looking for the picasso firmware. 



It's finding the firmware

$# after removing /usr/lib/firmware
$ lsinitramfs /boot/initrd.img-5.10.0-8-amd64 > /tmp/before
$ grep -i pica /tmp/before
$ # revert /usr/lib/firmware
$ sudo update-initramfs -u
$ lsinitramfs /boot/initrd.img-5.10.0-8-amd64 > /tmp/after
$ grep -i pica /tmp/after
usr/lib/firmware/amdgpu/picasso_asd.bin
usr/lib/firmware/amdgpu/picasso_ce.bin
usr/lib/firmware/amdgpu/picasso_gpu_info.bin
usr/lib/firmware/amdgpu/picasso_me.bin
usr/lib/firmware/amdgpu/picasso_mec.bin
usr/lib/firmware/amdgpu/picasso_mec2.bin
usr/lib/firmware/amdgpu/picasso_pfp.bin
usr/lib/firmware/amdgpu/picasso_rlc.bin
usr/lib/firmware/amdgpu/picasso_rlc_am4.bin
usr/lib/firmware/amdgpu/picasso_sdma.bin
usr/lib/firmware/amdgpu/picasso_ta.bin
usr/lib/firmware/amdgpu/picasso_vcn.bin

Re: Network down incorrect........

2021-08-28 Thread Marco Möller


On 28.08.21 15:38, Charlie wrote:


From my keyboard:

Hello all,

Since Bullseye went stable, updated on my 12 month old HP
laptop. When attempting to bring up the wireless interface with
ifup.

The message on the screen tells me the "network is down", which is
incorrect. Because on another Bullseye machine it works perfectly. as
it did on this one before it went stable.

It gives the message:

RTNETLINK answers: Operation not possible due to RF-kill

Then tries to connect for about 12 or so tries.

I have not installed rfkill, and can't find it to uninstall it.

On the web there is a reference to this "RTNETLINK answers: Operation
not possible due to RF-kill" on Archlinux where it was solved by
bringing the BIOS back to default. I tried that, but temporarily locked
myself out of the system. Then asking me to install an operating system
on the hard drive. I brought that back buy returning the BIOS to when
it booted the system.

I can use the Ethernet port and cable to connect to the internet with
that machine, however, did connect wirelessly when Bullseye was testing.

Any pointers would be appreciated.

TIA,
Charlie

East Gippsland Wildlife Rehabilitators Inc..
http://www.egwildlife.com.au/



Temporary workaround:
When I have had such problem in the past and also no rfkill installed, I 
simply installed rfkill (and for my use case created an alias for the 
CLI and shortcut for the GUI for reactivating WiFi and Bluetooth easily, 
if they would be blocked again).
This does not explain where the problem comes from, but installing and 
using rfkill is not a big thing and quickly gets you out of trouble and 
up and working again.
In my case, if I remember at least a little bit the case, it was the 
graphical desktop environment which deactivated the wireless devices 
upon shutdown, but then was not able to reactivate them at system start, 
letting the devices stay blocked, obviously having used some rfkill 
alike implementation in the GUI code itself. Since I installed the 
rfkill package and reactivated the devices manually at the CLI the 
problem disappeared somehow. I do not remember anymore if the problem 
disappeared instantely or after some few rounds of shutdown and reboot 
with manual rfkill intervention, or simply because maybe around that 
time also a GUI update arrived. I still assume that it was a bug in the 
GUI code, using maybe some internal rfkill alike code, but being buggy, 
having the feature to deactivate those devices working correctly but 
failing to reactivate them. As I quickly couldn't reproduce the problem 
no more, I could not provide a bug report. I did not even test what 
would happen if I now would remove the rfkill package again. 
Installation and usage of that package solved my problem first hand as a 
workaround, and then the problem anyway disappeared shortly after, and 
eventually I decided to simply keep rfkill installed.


---
Good Luck!
Marco.

Re: Entreteniments variats després d'actualitzar a Bullseye

2021-08-28 Thread R. Sicart

Sembla més aviat el fitxer /etc/ufw/before.rules
que no pas el unit file. Els permisos són els mateixos ?
-- 

R. Sicart

28 août 2021 16:10:53 Lluís Gras :

> Així sembla ...
> 
> Però és que tant en el cas (D10) com en l'altre (D11) el fitxer 
> /lib/systemd/system/ufw.service és el mateix
> 
> root@gwbox:~# cat /lib/systemd/system/ufw.service
> [Unit]
> Description=Uncomplicated firewall
> Documentation=man:ufw(8)
> DefaultDependencies=no
> Before=network.target
> 
> [Service]
> Type=oneshot
> RemainAfterExit=yes
> ExecStart=/lib/ufw/ufw-init start quiet
> ExecStop=/lib/ufw/ufw-init stop
> 
> [Install]
> WantedBy=multi-user.target
> 
> 
> I el paquet ipset no te cap entrada a systemd.
> 
> 
> Missatge de R. Sicart  del dia ds., 28 d’ag. 2021 a 
> les 15:50:
>> Bones,
>> 
>> No he fet servir mai ufw, però pel missatge d'error "(nf_tables): Set 
>> Firehol_L1 doesn't exist
>> " sembla que, quan el servei systemd arranca, Firehol_L1 encara no existeix.
>> 
>> Sort !


signature.asc
Description: PGP signature

Re: Network down incorrect........

2021-08-28 Thread Eike Lantzsch ZP6CGE

On Samstag, 28. August 2021 09:38:44 -04 Charlie wrote:
>   From my keyboard:
>
>   Hello all,
>
>   Since Bullseye went stable, updated on my 12 month old HP
>   laptop. When attempting to bring up the wireless interface with
>   ifup.
>
> The message on the screen tells me the "network is down", which is
> incorrect. Because on another Bullseye machine it works perfectly. as
> it did on this one before it went stable.
>
> It gives the message:
>
> RTNETLINK answers: Operation not possible due to RF-kill
>
> Then tries to connect for about 12 or so tries.
>
> I have not installed rfkill, and can't find it to uninstall it.
>
> On the web there is a reference to this "RTNETLINK answers: Operation
> not possible due to RF-kill" on Archlinux where it was solved by
> bringing the BIOS back to default. I tried that, but temporarily
> locked myself out of the system. Then asking me to install an
> operating system on the hard drive. I brought that back buy returning
> the BIOS to when it booted the system.
>
> I can use the Ethernet port and cable to connect to the internet with
> that machine, however, did connect wirelessly when Bullseye was
> testing.
>
> Any pointers would be appreciated.
>
> TIA,
> Charlie
>
>   East Gippsland Wildlife Rehabilitators Inc..
>http://www.egwildlife.com.au/
rfkill is a Linux device
the program rfkill is not necessarily installed but it might help you to 
identify the
underlying problem.
A shot into the dark: This smells like a firmware problem.


--
Eike Lantzsch ZP6CGE

Re: CUPS permissions >Fixed

2021-08-28 Thread Peter Ehlert

On 8/26/21 5:53 AM, Greg Wooledge wrote:

On Thu, Aug 26, 2021 at 01:37:49PM +0100, Brian wrote:

On Thu 26 Aug 2021 at 13:23:58 +0100, mick crane wrote:

On 2021-08-26 12:59, Peter Ehlert wrote:

On 8/25/21 12:11 PM, Greg Wooledge wrote:

Some people report restarting the browser is enough. Some claim they
have to reboot. Who knows.

thanks. restarting firefox worked.
I got the login dialog box

after login as (user)
Add Printer gives> Unable to add printer: Forbidden

back to square one

I've got a print server working but I've forgotten how.
added a new printer a year or so ago.
Might have been lpadmin or something.
I do know always have to reboot after making changes.

Rebooting after adding a printer is *never* needed.

Agreed.

I suspect there's some *really* basic misunderstanding going on at some
level. Let's start from the beginning.

Thanks for this list of basics. I am now beginning to understand.

In order to administer a printer in CUPS, you do the following things:

1) Make sure the root account has a PASSWORD. Make sure you know it.
Access to sudo doesn't count.

I never use sudo, no users get sudo privileges on any of my machines.

2) Install cups.
* cups was not installed by default. The Brother installer did flag that
first off, easily corrected

3) Visit http://localhost:631/ in a GUI web browser. Make sure Javascript
is allowed.

4) At some point, when you try to do stuff to the printers in the browser,
you will be prompted for a username and password, using HTTP basic
authentication. When this occurs, you should login as root, using
root's password.

BINGO: I was not using root

5) If you screwed up and logged in as yourself, restart the web browser
so that you can get the HTTP basic authentication dialog box again. Go
to step 4.

6) Once the printer is set up via the browser, you should be able to see
it and print to it from the command line. "lpstat -t" to see all of
the printers and their status. "lp" or "lpr" to print a text file.

$ lpstat -t
scheduler is running
no system default destination
device for MFCL3770CDW:
dnssd://Brother%20MFC-L3770CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-b4220033103b

MFCL3770CDW accepting requests since Sun 22 Aug 2021 05:44:11 AM PDT
printer MFCL3770CDW is idle. enabled since Sun 22 Aug 2021 05:44:11 AM PDT

Any variants on this procedure will require knowledge that I don't
personally possess. E.g. if for some reason you refuse to set a root
password, then you may have to set up a printer-admin account which
has the appropriate privileges, and a password, and then use that
instead of root. I don't know what those privs would be.

Summary:

I removed my browser cookie for "localhost"

restarted the browser

when CUPS requested a password I used "root"

I am now able to add printers and edit all options

Thanks to all for the assistance and Education

Re: amdgpu broken on bookworm?


On 8/28/21 07:04, Jeffrey Chimene wrote:
No complaints about missing picasso firmware. I'll try removing the 
/lib/firmware to see what happens.


So this doesn't do what I thought it would. It's probably not even 
looking for the picasso firmware.


$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for 
module r8169

I: The initramfs will attempt to resume from /dev/dm-1
I: (/dev/mapper/epiktistes--vg-swap_1)
I: Set the RESUME variable to override this.

$ ll /lib/firmware
ls: cannot access '/lib/firmware': No such file or directory

Re: amdgpu broken on bookworm?

No complaints about missing picasso firmware. I'll try removing the 
/lib/firmware to see what happens.


$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64

W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for 
module r8169

I: The initramfs will attempt to resume from /dev/dm-1
I: (/dev/mapper/epiktistes--vg-swap_1)
I: Set the RESUME variable to override this.

Re: Network down incorrect........

2021-08-28 Thread Jude DaShiell

As part of your reinstall process did you delete all partitions then run
wipefs -af on the disk?  Failure to do so may have left old artifacts of
the previous system on the drive which may be messing up your current
installation.


On Sat, 28 Aug 2021, Charlie wrote:

>
>   From my keyboard:
>
>   Hello all,
>
>   Since Bullseye went stable, updated on my 12 month old HP
>   laptop. When attempting to bring up the wireless interface with
>   ifup.
>
> The message on the screen tells me the "network is down", which is
> incorrect. Because on another Bullseye machine it works perfectly. as
> it did on this one before it went stable.
>
> It gives the message:
>
> RTNETLINK answers: Operation not possible due to RF-kill
>
> Then tries to connect for about 12 or so tries.
>
> I have not installed rfkill, and can't find it to uninstall it.
>
> On the web there is a reference to this "RTNETLINK answers: Operation
> not possible due to RF-kill" on Archlinux where it was solved by
> bringing the BIOS back to default. I tried that, but temporarily locked
> myself out of the system. Then asking me to install an operating system
> on the hard drive. I brought that back buy returning the BIOS to when
> it booted the system.
>
> I can use the Ethernet port and cable to connect to the internet with
> that machine, however, did connect wirelessly when Bullseye was testing.
>
> Any pointers would be appreciated.
>
> TIA,
> Charlie
>
>   East Gippsland Wildlife Rehabilitators Inc..
>http://www.egwildlife.com.au/
>
>

Re: amdgpu broken on bookworm?




On 8/28/21 06:04, piorunz wrote:

On 28/08/2021 13:54, Jeffrey Chimene wrote:

Let me ask more questions, so we all can learn more about your situation
and start suggesting remedies.


Hi,

Thanks for the advice. The problem I'm trying to solve is why the AMD
firmware isn't getting incorporated in the kernel.


How you assumed that firmware isn't getting to kernel? Do you have any
errors in the log stating that?


I have to boot with
NOMODESET.


What happens if you don't? Please show error logs when you don't have
nomodeset.


The bookworm updates, while coincidental, are probably not
the cause. "Something else" happened, and I need help debugging. I can't
see amdgpu in lsmod. I can see the firmware in /var/lib/firmware.


Try this:

inxi -G
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX
6800/6800 XT / 6900 XT] driver: amdgpu v: kernel
   Display: x11 server: X.Org 1.20.11 driver: loaded:
amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution:
   1: 1920x1200~60Hz 2: 3840x2160
   OpenGL: renderer: AMD SIENNA_CICHLID (DRM 3.40.0
5.10.0-8-amd64 LLVM 12.0.1) v: 4.6 Mesa 21.1.4


$ inxi -G
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: N/A
   Display: server: X.Org 1.20.11 driver: loaded: ati,vesa 
unloaded: fbdev,modesetting,radeon resolution: 1440x876~1Hz

   OpenGL: renderer: N/A v: N/A

$ aptitude search "~i firmware"
i firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips
i firmware-iwlwifi - Binary firmware for Intel Wireless cards
i firmware-linux - Binary firmware for various drivers in the Linux 
kernel (metapackage)
i A firmware-linux-free - Binary firmware for various drivers in the 
Linux kernel
i firmware-linux-nonfree - Binary firmware for various drivers in the 
Linux kernel (metapackage)
i A firmware-misc-nonfree - Binary firmware for various drivers in the 
Linux kernel


$ ll /lib/firmware
total 40K
drwxr-xr-x 2 root root  20K Aug 27 05:50 amdgpu
drwxr-xr-x 2 root root 4.0K Aug 27 05:50 r128
drwxr-xr-x 2 root root  16K Aug 27 05:50 radeon

$ find /lib/firmware/ -iname \*pic\*

/lib/firmware/amdgpu/picasso_rlc_am4.bin
/lib/firmware/amdgpu/picasso_gpu_info.bin
/lib/firmware/amdgpu/picasso_ce.bin
/lib/firmware/amdgpu/picasso_ta.bin
/lib/firmware/amdgpu/picasso_me.bin
/lib/firmware/amdgpu/picasso_mec.bin
/lib/firmware/amdgpu/picasso_asd.bin
/lib/firmware/amdgpu/picasso_mec2.bin
/lib/firmware/amdgpu/picasso_sdma.bin
/lib/firmware/amdgpu/picasso_pfp.bin
/lib/firmware/amdgpu/picasso_vcn.bin
/lib/firmware/amdgpu/picasso_rlc.bin

Re: CUPS permissions

2021-08-28 Thread Peter Ehlert

On 8/26/21 5:53 AM, Greg Wooledge wrote:

On Thu, Aug 26, 2021 at 01:37:49PM +0100, Brian wrote:

On Thu 26 Aug 2021 at 13:23:58 +0100, mick crane wrote:

On 2021-08-26 12:59, Peter Ehlert wrote:

On 8/25/21 12:11 PM, Greg Wooledge wrote:

Some people report restarting the browser is enough. Some claim they
have to reboot. Who knows.

thanks. restarting firefox worked.
I got the login dialog box

after login as (user)
Add Printer gives> Unable to add printer: Forbidden

back to square one

I've got a print server working but I've forgotten how.
added a new printer a year or so ago.
Might have been lpadmin or something.
I do know always have to reboot after making changes.

Rebooting after adding a printer is *never* needed.

Agreed.

I suspect there's some *really* basic misunderstanding going on at some
level. Let's start from the beginning.

Thanks for this list of basics. I am now beginning to understand.

In order to administer a printer in CUPS, you do the following things:

1) Make sure the root account has a PASSWORD. Make sure you know it.
Access to sudo doesn't count.

I never use sudo, no users get sudo privileges on any of my machines.

2) Install cups.
* cups was not installed by default. The Brother installer did flag that
first off, easily corrected

3) Visit http://localhost:631/ in a GUI web browser. Make sure
Javascript

is allowed.

4) At some point, when you try to do stuff to the printers in the
browser,

you will be prompted for a username and password, using HTTP basic
authentication. When this occurs, you should login as root, using
root's password.

BINGO: I was not using root

5) If you screwed up and logged in as yourself, restart the web browser
so that you can get the HTTP basic authentication dialog box
again. Go

to step 4.

$ lpstat -t
scheduler is running
no system default destination
device for MFCL3770CDW:
dnssd://Brother%20MFC-L3770CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-b4220033103b

MFCL3770CDW accepting requests since Sun 22 Aug 2021 05:44:11 AM PDT
printer MFCL3770CDW is idle. enabled since Sun 22 Aug 2021 05:44:11 AM PDT

Summary:

I removed my browser cookie for "localhost"

restarted the browser

when CUPS requested a password I used "root"

I am now able to add printers and edit all options

Thanks to all for the assistance and Education

Re: Entreteniments variats després d'actualitzar a Bullseye

2021-08-28 Thread Lluís Gras

Així sembla ...

Però és que tant en el cas (D10) com en l'altre (D11) el
fitxer /lib/systemd/system/ufw.service és el mateix

root@gwbox:~# cat /lib/systemd/system/ufw.service
[Unit]
Description=Uncomplicated firewall
Documentation=man:ufw(8)
DefaultDependencies=no
Before=network.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/lib/ufw/ufw-init start quiet
ExecStop=/lib/ufw/ufw-init stop

[Install]
WantedBy=multi-user.target


I el paquet ipset no te cap entrada a systemd.


Missatge de R. Sicart  del dia ds., 28 d’ag. 2021 a
les 15:50:

> Bones,
>
> No he fet servir mai ufw, però pel missatge d'error "(nf_tables): Set
> Firehol_L1 doesn't exist
> " sembla que, quan el servei systemd arranca, Firehol_L1 encara no
> existeix.
>
> Sort !
>

Network down incorrect........



From my keyboard:

Hello all,

Since Bullseye went stable, updated on my 12 month old HP
laptop. When attempting to bring up the wireless interface with
ifup.

The message on the screen tells me the "network is down", which is
incorrect. Because on another Bullseye machine it works perfectly. as
it did on this one before it went stable.

It gives the message:

RTNETLINK answers: Operation not possible due to RF-kill

Then tries to connect for about 12 or so tries.

I have not installed rfkill, and can't find it to uninstall it.

On the web there is a reference to this "RTNETLINK answers: Operation
not possible due to RF-kill" on Archlinux where it was solved by
bringing the BIOS back to default. I tried that, but temporarily locked
myself out of the system. Then asking me to install an operating system
on the hard drive. I brought that back buy returning the BIOS to when
it booted the system.

I can use the Ethernet port and cable to connect to the internet with
that machine, however, did connect wirelessly when Bullseye was testing.

Any pointers would be appreciated.

TIA,
Charlie

East Gippsland Wildlife Rehabilitators Inc..
   http://www.egwildlife.com.au/

-- 
Registered Linux User:- 329524

***

The fool doth think he is wise, but the wise man knows himself
to be a fool. --William Shakespeare

***
Debian GNU/Linux - Magic indeed.

-

Re: amdgpu broken on bookworm?


Hi piorunz,

Thanks for your interest! I really appreciate your time. Background: 
I've been using Debian since Potato. This distro Just Works.


On 8/28/21 06:04, piorunz wrote:

On 28/08/2021 13:54, Jeffrey Chimene wrote:

Let me ask more questions, so we all can learn more about your situation
and start suggesting remedies.


Hi,

Thanks for the advice. The problem I'm trying to solve is why the AMD
firmware isn't getting incorporated in the kernel.


How you assumed that firmware isn't getting to kernel? Do you have any
errors in the log stating that?


There are no errors. Only warnings about an unsupported Wifi chip (r8169 
missing RTL8125b-2).


As an aside: I have not mentioned this before, and I think it is a red 
herring: The problems started when I connected the wifi antenna to the 
board. The firmware for this chip isn't supported in this kernel, yet. I 
think I can download the drivers from Intel. I'm not really interested 
in wifi for this machine, as a wired connection works for now. This is 
too coincidental and unrealistic, but I want to get past it so we can 
move to other things. As soon as the antenna connections (dual coax) to 
the board were made, the screen went black. I know. Bullshit. The board 
doesn't really need an external antenna to detect wifi, so the antenna 
connection only boosted the signal. If the OS wanted to load a 
non-existent driver (which it's already trying to do as that failing 
attempt appears in boot.log), it would've tried before then, external 
antenna or no. Then somehow botch already loaded amdgpu firmeare? I 
don't think so. It's as coincidental as the bookworm updates earlier 
that day. When I rebooted to clear the issue (Linux isn't windows! One 
doesn't reboot to fix issues), no display...


Anyway, on to your other questions...




I have to boot with
NOMODESET.


What happens if you don't? Please show error logs when you don't have
nomodeset.


There are no logs. nomodeset doesn't log anything. It enables display 
twitching during boot. When XDM gains control, it will try to set the 
display mode.






The bookworm updates, while coincidental, are probably not
the cause. "Something else" happened, and I need help debugging. I can't
see amdgpu in lsmod. I can see the firmware in /var/lib/firmware.


Try this:

inxi -G
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX
6800/6800 XT / 6900 XT] driver: amdgpu v: kernel
   Display: x11 server: X.Org 1.20.11 driver: loaded:
amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution:
   1: 1920x1200~60Hz 2: 3840x2160
   OpenGL: renderer: AMD SIENNA_CICHLID (DRM 3.40.0
5.10.0-8-amd64 LLVM 12.0.1) v: 4.6 Mesa 21.1.4


I don't have inxi installed. I will install it and post the results.






I've run update-initramfs -c after replacing /var/lib/firmware. Still
not getting positive results from lsmod | grep -i amdgpu


$ lsmod | grep -i amdgpu
amdgpu   6606848  90
gpu_sched  40960  1 amdgpu
i2c_algo_bit   16384  1 amdgpu
ttm   114688  1 amdgpu
drm_kms_helper    274432  1 amdgpu
drm   618496  39 gpu_sched,drm_kms_helper,amdgpu,ttm

For me it works.


For me, nada. One of my earliest tests. I swear, I did see positive 
results earlier!







Booting with

ro loglevel=7 nomodeset

isn't giving any useable clues in boot.log


What is your GPU (integrated or not) model? Please say exact model from
inxi for example.
I'm sure it's integrated. It's a Asus board model B550M-A By now, it has 
"reasonable" kernel support. About 18 months ago, it did not have such 
support. As I said earlier, I think wifi isn't well supported, but I 
don't care right now.




It feels like it's a kernel setting that got written and isn't reset
after down/up grades. This is testing. It's supposed to be "broken".


I don't know what you are trying to say here. What supposed to be broken
and why you think so?


It's based on intuition. If I had the resources to follow up that hunch, 
I would. I don't know where to start with such suppositions; which are 
based on instructions like "cat BLAH > /FOO/BLECH" to change OS behavior.


Cheers,
jec

Entreteniments variats després d'actualitzar a Bullseye

2021-08-28 Thread R. Sicart

Bones,

No he fet servir mai ufw, però pel missatge d'error "(nf_tables): Set 
Firehol_L1 doesn't exist
" sembla que, quan el servei systemd arranca, Firehol_L1 encara no existeix.

Sort !


signature.asc
Description: PGP signature

Re: [OT] Montar mi propio NAS casero

2021-08-28 Thread Camaleón

El 2021-08-27 a las 10:52 +0200, Roberto Leon Lopez escribió:

> > El 26 ago 2021, a las 18:03, Camaleón  escribió:

(...)

>  No sé si por precio interesa comprar alguna solución completa de un 
>  fabricante o montar mi propio NAS.
> >>> 
> >>> Este apartado sí que lo tengo claro: montar tu propio equipo (lo montas 
> >>> al gusto, lo amplías, lo mejoras y te dura años). El inicio es más 
> >>> duro pero a largo plazo compensa.
> >>> 
> >>> He tenido dos soluciones dedicadas: un NAS (bastardo) y un SAN (de alto 
> >>> abolengo). El primero me gustaba pero era de hardware limitado y se me 
> >>> quedó pequeño. Con el último terminé martillazos (literal). Era malo del 
> >>> copón.
> >> 
> >> ¿Y para el RAID apuestas por seguir el clásico mdadm y ext4 encima o tirar 
> >> a por brfs?
> > 
> > Para estas cosas, prefiero lo conocido (mdadm + ext4, o xfs, creo que le 
> > iría mejor) antes que la novedad. BTRFS aún no lo veo del todo claro 
> > para entornos de producción, tendría que probarlo antes en un equipo  
> > aíslado y controlado para ver cómo desempeña y qué problemas tiene con 
> > los componentes de hardware que tengo, es decir, disco convecionales 
> > :-).
> > 
> > Con el RAID tengo sentimientos encontrados, mi experiencia con 
> > controladoras de hardware y uso de niveles 1 y 5 no ha sido del todo 
> > buena y en los más de 15 años que las uso me han dado más problemas que
> > beneficios... no sé, quizá elegí mal o quizá esperaba más facilidades 
> > de lo que realmente daba de sí este sistema.
> > 
> >> Estoy viendo en Internet que se venden kits de diferente elementos según 
> >> la función de la RaspBerry Pi.
> > 
> > El problema que le veo a las soluciones SoC para almacenamiento masivo 
> > de datos es que al final tienes que alimentar varios discos duros, de 
> > teras, y eso requiere de alimentación y espacio extra suficiente (chasis, 
> > ventilación) por lo que al final acabas ocupando el mismo espacio que 
> > con una buena caja convencional y con las molestias añadidas de las 
> > Raspberry y similares (conectores especiales, tarjetas de ampliación, 
> > etc...).
> 
> 
> Efectivamente BTRFS o OpenZFS son sistema copy on write y hace más 
> escrituras. Además OpenZFS no deja de tener un requerimiento alto en memoria.
> 
> La flexibilidad de poder montar el RAID software, cuando se estropea el 
> hardware, en otro equipo es envidiable. Porque los años pasan y tras 7 años 
> busca una tarjeta igual y págala.
> 
> ¿Que té parece esas tarjetas PCIe con 4 puertos SATA con la finalidad de 
> meterle discos SSD y montar el RAID? ¿Dónde se puede comprar ese hardware y 
> la carcasa?

Hoy en día las placas base MicroATX llevan, como mínimo, 6 puertos 
SATA. Si añades que cada disco son de 4 TiB, pues tienes para 
almacenar datos hasta la eternidad :-)

Creo que ya va bien para un NAS casero o una empresa pequeña.

Tampoco descartaría una placa ATX convencional, por una cuestión de 
manejabilidad, compatibildiad, espacio adicional para futuras 
ampliaciones y buena ventilación, que también es importante.

Eso sí, para almacenamiento de datos nada de SSD, discos duros 
convencionales.
 
> He leído consumos de energía de 4w en reposo, al meterle la controladora PCIe 
> y los discos subirá y empieza a ser preocupante la calor.

Salvo que busques una capacidad de almacenamiento muy elevada o un 
acceso a los discos extremadamente alto, no creo necesario un apaptador
adicional.

Saludos,

-- 
Camaleón

Re: amdgpu broken on bookworm?



On 8/28/21 05:36, songbird wrote:

Jeffrey Chimene wrote:


   just to note that using "bookworm" in your subject line can
give the implication that "bookworm" is actually released which
it hasn't.  it is much better to use the keyword "testing" in
the subject line instead.


Agreed. However, a net search on testing would yield results that are 
too old to be useful. My goal is to watch for bookworm topics via search 
engine's "news alert" features.







Something happened to my amd firmware for a ryzen3 3200g. A few weeks
ago, this machine made an uneventful transition to bookworm. I'd
originally installed bullseye and the non-free firmware package to get
the firmware for this setup. Everything was fine until yesterday, after
some bookworm updates and a reboot. No more video driver for X.

I've tried downgrading to stable from testing. No joy.

I've wiped /lib/firmware and reinstalled firmware-amd-graphics. No joy.
I've checked

I just booted ubuntu live and graphics are high resolution.

It feels like there's some setting in /proc or /sys that got changed
accidentally.

Any debugging tips?


   it does not take that much space to set up a separate
partition for stable on a system to keep a working version
available and for comparison.  this is what i do.


Damn, that is such a good idea! I will add that to future 
re-partitioning. Right now, to get this box on the air, I did the two 
partition (/ and swap) setup and added lvm2 for backups and such. I 
think the resolution to this issue is to reinstall. I'll wait a few 
weeks for testing to ripen to 12, move /home to its own partition (and 
probably /var), create a /stable partition and reinstall.


As I understand it, this /stable is not bootable?

Re: amdgpu broken on bookworm?


On 28/08/2021 13:54, Jeffrey Chimene wrote:

Let me ask more questions, so we all can learn more about your situation
and start suggesting remedies.


Hi,

Thanks for the advice. The problem I'm trying to solve is why the AMD
firmware isn't getting incorporated in the kernel.


How you assumed that firmware isn't getting to kernel? Do you have any
errors in the log stating that?


I have to boot with
NOMODESET.


What happens if you don't? Please show error logs when you don't have
nomodeset.


The bookworm updates, while coincidental, are probably not
the cause. "Something else" happened, and I need help debugging. I can't
see amdgpu in lsmod. I can see the firmware in /var/lib/firmware.


Try this:

inxi -G
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX
6800/6800 XT / 6900 XT] driver: amdgpu v: kernel
   Display: x11 server: X.Org 1.20.11 driver: loaded:
amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution:
   1: 1920x1200~60Hz 2: 3840x2160
   OpenGL: renderer: AMD SIENNA_CICHLID (DRM 3.40.0
5.10.0-8-amd64 LLVM 12.0.1) v: 4.6 Mesa 21.1.4



I've run update-initramfs -c after replacing /var/lib/firmware. Still
not getting positive results from lsmod | grep -i amdgpu


$ lsmod | grep -i amdgpu
amdgpu   6606848  90
gpu_sched  40960  1 amdgpu
i2c_algo_bit   16384  1 amdgpu
ttm   114688  1 amdgpu
drm_kms_helper274432  1 amdgpu
drm   618496  39 gpu_sched,drm_kms_helper,amdgpu,ttm

For me it works.



Booting with

ro loglevel=7 nomodeset

isn't giving any useable clues in boot.log


What is your GPU (integrated or not) model? Please say exact model from
inxi for example.



It feels like it's a kernel setting that got written and isn't reset
after down/up grades. This is testing. It's supposed to be "broken".


I don't know what you are trying to say here. What supposed to be broken
and why you think so?

--

With kindest regards, piorunz.

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

Re: amdgpu broken on bookworm?




On 8/28/21 05:36, songbird wrote:

Jeffrey Chimene wrote:


   just to note that using "bookworm" in your subject line can
give the implication that "bookworm" is actually released which
it hasn't.  it is much better to use the keyword "testing" in
the subject line instead.


Agreed. However, a net search on testing would yield results that are 
too old to be useful. My goal is to watch for bookworm topics via search 
engine's "news alert" features.







Something happened to my amd firmware for a ryzen3 3200g. A few weeks
ago, this machine made an uneventful transition to bookworm. I'd
originally installed bullseye and the non-free firmware package to get
the firmware for this setup. Everything was fine until yesterday, after
some bookworm updates and a reboot. No more video driver for X.

I've tried downgrading to stable from testing. No joy.

I've wiped /lib/firmware and reinstalled firmware-amd-graphics. No joy.
I've checked

I just booted ubuntu live and graphics are high resolution.

It feels like there's some setting in /proc or /sys that got changed
accidentally.

Any debugging tips?


   it does not take that much space to set up a separate
partition for stable on a system to keep a working version
available and for comparison.  this is what i do.


Damn, that is such a good idea! I will add that to future 
re-partitioning. Right now, to get this box on the air, I did the two 
partition (/ and swap) setup and added lvm2 for backups and such. I 
think the resolution to this issue is to reinstall. I'll wait a few 
weeks for testing to ripen to 12, move /home to its own partition (and 
probably /var), create a /stable partition and reinstall.


As I understand it, this /stable is not bootable?

Re: amdgpu broken on bookworm?



On 8/28/21 04:28, piorunz wrote:

On 27/08/2021 19:20, Jeffrey Chimene wrote:

Something happened to my amd firmware for a ryzen3 3200g. A few weeks
ago, this machine made an uneventful transition to bookworm.


Great.


I'd
originally installed bullseye and the non-free firmware package to get
the firmware for this setup. Everything was fine until yesterday


Not bookworm upgrade fault then. You had upgraded the system and it was
working fine.


Everything was fine until yesterday, after
some bookworm updates and a reboot. No more video driver for X.


SOME bookworm updates? Please be more specific. That's the cause of your
problem. Please attach relevant logs from this "bookworm updates" event
so we can see what happened.



Hi,

Thanks for the advice. The problem I'm trying to solve is why the AMD 
firmware isn't getting incorporated in the kernel. I have to boot with 
NOMODESET. The bookworm updates, while coincidental, are probably not 
the cause. "Something else" happened, and I need help debugging. I can't 
see amdgpu in lsmod. I can see the firmware in /var/lib/firmware.


I've run update-initramfs -c after replacing /var/lib/firmware. Still 
not getting positive results from lsmod | grep -i amdgpu


Booting with

ro loglevel=7 nomodeset

isn't giving any useable clues in boot.log

It feels like it's a kernel setting that got written and isn't reset 
after down/up grades. This is testing. It's supposed to be "broken". 
When bullseye was broken after the downgrade, I knew something broke in 
my local configuration. I'm trying to fix it. I'd like help debugging. 
It's probably only reproducible if one follows a set of steps that 
aren't easily retraced.


It's been too many years since I used Debian from the console. I do not 
remember enough X to debug building the init image towards that goal.


I'm also chuffed that Ubuntu manages to pull off video in the live CD.

At this point, I think I'll reinstall from bookworm netinst in a few 
weeks or after the transition to 12 finishes. Running the box headless 
will be good enough for now.




--

With kindest regards, piorunz.

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

Re: amdgpu broken on bookworm?

2021-08-28 Thread songbird

Jeffrey Chimene wrote:

  just to note that using "bookworm" in your subject line can
give the implication that "bookworm" is actually released which
it hasn't.  it is much better to use the keyword "testing" in
the subject line instead.

> Something happened to my amd firmware for a ryzen3 3200g. A few weeks 
> ago, this machine made an uneventful transition to bookworm. I'd 
> originally installed bullseye and the non-free firmware package to get 
> the firmware for this setup. Everything was fine until yesterday, after 
> some bookworm updates and a reboot. No more video driver for X.
>
> I've tried downgrading to stable from testing. No joy.
>
> I've wiped /lib/firmware and reinstalled firmware-amd-graphics. No joy. 
> I've checked
>
> I just booted ubuntu live and graphics are high resolution.
>
> It feels like there's some setting in /proc or /sys that got changed 
> accidentally.
>
> Any debugging tips?

  it does not take that much space to set up a separate 
partition for stable on a system to keep a working version
available and for comparison.  this is what i do.

  songbird

Re: Debian 11 and Win10 dual boot

2021-08-28 Thread Kenneth Parker

On Sat, Aug 28, 2021, 6:06 AM Joe  wrote:

> On Sat, 28 Aug 2021 11:14:28 +0300
> ellanios82  wrote:
>
> > On 28/8/21 Intense Red:
> > > How can Windows be lobotomized
> >
> >
> >- maybe Install VirtualBox, & ONLY run windows inside Linux
> >
> >
>
> The Home version won't be licensed for use in a VM, and may be
> engineered not to work at all in one. The Pro version should, but costs
> a fair bit
>

I have Windows 10 PRO running in qemu-kvm under Stable Bullseye (though
installed when it was Testing Bullseye).

When I discussed my Windows 10 PRO purchase with them, the earlier part of
the conversation was, before I had selected PRO over Home and the person on
the phone did not bring up anything about Home on Virtual environments.

So my suspicion is that it will, at least technically run in a Virtual
environment.

Good luck!

Kenneth Parker

>

Re: amdgpu broken on bookworm?