Re: Wrong screen resolution (1024x768) after upgrade

[Stephen Morris]

On 1/11/22 09:37, Joe Zeff wrote:

On 10/31/2022 03:51 PM, Barry Scott wrote:
I found that to wipe the nvidia driver and then reinstall it takes a 
number of steps.


Removing them all can be done in one step:

sudo dnf remove *nvidia*
I've also found that sudo dnf remove akmod-nvidia kmod-nvidia also 
removes all the nvidia files and all the associated dependencies.


regards,
Steve



HTH, HAND.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Wrong screen resolution (1024x768) after upgrade

[John Pilkington]

On 01/11/2022 07:23, Stephen Morris wrote:

On 1/11/22 09:37, Joe Zeff wrote:

On 10/31/2022 03:51 PM, Barry Scott wrote:
I found that to wipe the nvidia driver and then reinstall it takes a 
number of steps.


Removing them all can be done in one step:

sudo dnf remove *nvidia*
I've also found that sudo dnf remove akmod-nvidia kmod-nvidia also 
removes all the nvidia files and all the associated dependencies.


regards,
Steve



HTH, HAND.


I haven't wanted to use nouveau recently, although IIRC it will now be 
activated as a fallback.  But in the past I had the impression that only 
the last-installed driver would behave properly. If you want nouveau, 
try reinstalling it.


John P
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Nouveau Blacklisting not in /etc/default/grub

[greg]

On Tue, Nov 1, 2022 at 4:15 AM Stephen Morris  wrote:
> I've just managed to get the 6.0.5 kernel to load the nvidia driver.
> There is potentially a defect in the akmod-nvidia (or relevant package)
> scripts in that it seems that they no longer add the blacklisting
> statements for nouveau into the kernel parameters in /etc/default/grub,
> I had to put those statements in there manually before the nvidia driver
> was loaded instead of the nouveau driver.

/etc/default/grub - contains default kernel options
/boot/grub2/grubenv - has the line
saved_entry=
which refers to
/boot/loader/entries/.conf
which contains kernel options for the entry (which are actually used)
which get modified when editing kernel options via grub menu (thus becom
ing persistent)

/etc/default/grub - contains the line
GRUB_ENABLE_BLSCFG=true
which is documented at
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault

greg
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: How do I rebuild Grub/Boot/initramfs from a Live USB?

[George N. White III]

On Fri, Oct 28, 2022 at 5:01 PM Chris Murphy 
wrote:

>
>
> On Fri, Oct 28, 2022, at 2:31 PM, Jake D wrote:
> > Hello all.
> >
> > I need some help.
>
>
> My opinion: This is probably easier in a live discussion on IRC or Matrix.
> There's just too much back and forth required.
>
> But the absolute easiest thing to do is mount the encrypted btrfs, make a
> backup of the home directory, and then clean install followed by restoring
> the home directory files from the backup.
>

Sound advice.

>
> Otherwise you and at just one other person have to have a fairly intense
> conversation about very low level esoterics. Boot is very distro specific.
> There's maybe two or three dozen steps to repair this setup. They all have
> to be exactly correct or it won't work. Much of this logic is in the
> installer.
>

and differs over time as well as distro, so is hard to deal with for those
of use who have to work with multiple distros and versions.

 has a summary
of the current linux
boot process, then discusses a proposal for a Unified Kernel Image (UKI)
that is intended to
improve security and simplify the user side of the configuration process.

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fwd: [Undeliverable: Re: Mailing lists and Discourse]

[Wolfgang Pfeiffer]

On Mon, Oct 31, 2022 at 04:42:14PM -0700, Kevin Fenzi wrote:

On Tue, Nov 01, 2022 at 12:18:43AM +0100, Wolfgang Pfeiffer wrote:

Kevin,
Thanks for your quick response!
[ ... ]



I have already tried this, so I guess let me know when/if you get the
bounce. ;) (ie, I have unsubscribed the user who I think is forwarding
to outlook.com).


Good. Thanks! - After my last message to this list ("Nov 01, 2022 at
12:18:43AM +0100") I got no "Undeliverable" messages coming in to my
Inbox again. So far .. ;) .. I'll write back to you (not to the list)
if problems reappear ..




> The list has mitigation for a similar case (DMARC).
> It applies this to messages From: a domain publishing a DMARC policy of 
reject or quarantine
> So, if you could add such a policy/support to gmx.com it could use this
> workaround (basically it replaces your sender address with the list
> address).

Again: Please see my tl;dr from above: is this what your suggesting in
this last part? If yes: as I said above: I'm fine with the address
replacement for this list and for my r...@gmx.net address ...


I can't force the list to do this. Your domain would need to enable
DMARC and set reject or quarantine for the list software to decide to
set this for you. ;(


As Stephen already wrote a few hours ago: gmx.net - I say: sadly -
isn't mine .. ;) .. it's a - I think German - email and I don't know
what else provider offering free and, I think, paid email services.


This needs a DNS entry added to your domain.  See
https://dmarc.org/overview/


Thanks for this link - seems interesting: nice side-effect of this
"Undeliverable" messages problem is now that I might set up my own
email domain: I'm getting curious about this whole thing ... :) but on
the other hand: as long as gmx.net works here: why care .. :)

Thanks for your efforts, Kevin - goes out also to everyone else in
this thread.

Regards,
Wolfgang



kevin

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Can I see an iMac drive with a Live USB?

[George N. White III]

On Mon, Oct 31, 2022 at 11:17 PM George N. White III 
wrote:

>
>
> On Sun, Oct 30, 2022 at 8:51 PM ToddAndMargo via users <
> users@lists.fedoraproject.org> wrote:
>
>> Hi All,
>>
>> I have an upcoming appointment with a customer
>> who wants a number of his old computers
>> (mostly iMacs) removed from service.
>>
>> [...]
>>
>>  # dd if=/dev/zero of=/dev/sd[x]
>
>
> An old iMac has been running this (x=a) for over 12 hours here using
> thr “rescue” option from an old linux installer CD.   I’ve done this with
> newer Macs, but just left it running overnight, so not sure how long it
> took.
>

My dd process ran out of space 24 hours after I started it, on a 250G drive.

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Can I see an iMac drive with a Live USB?

[Roger Heflin]

I usually add a bs=4k or bs=16k or a bs=256k when using dd so the
blocksize is larger.  That usually makes it quite a bit  faster.

And if you background the dd you can use "vmstat 1" and the bi/bo
columns tell you the actual disk io rates, and you can use that to
reliably estimate.

Default is 512 and does not align with most (all?) underlying physical
devices block sizes and may cause various layers extra work and take
much longer.

On Tue, Nov 1, 2022 at 9:26 AM George N. White III  wrote:
>
> On Mon, Oct 31, 2022 at 11:17 PM George N. White III  wrote:
>>
>>
>>
>> On Sun, Oct 30, 2022 at 8:51 PM ToddAndMargo via users 
>>  wrote:
>>>
>>> Hi All,
>>>
>>> I have an upcoming appointment with a customer
>>> who wants a number of his old computers
>>> (mostly iMacs) removed from service.
>>>
>>> [...]
>>>
>>>  # dd if=/dev/zero of=/dev/sd[x]
>>
>>
>> An old iMac has been running this (x=a) for over 12 hours here using
>> thr “rescue” option from an old linux installer CD.   I’ve done this with
>> newer Macs, but just left it running overnight, so not sure how long it took.
>
>
> My dd process ran out of space 24 hours after I started it, on a 250G drive.
>
> --
> George N. White III
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Lost highlight

[Patrick Dupre]

Hello,

In a terminal (gnome-terminal), I used to use the mouse right button,
to copy paste highlighted text.
Sometimes I lost this option: the highlight odes not work.
It seems to be due to xmgrace.
Do you know how to recover this way of going without closing all
the xmgrace terminals?

Thank.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988| | Room# D114A
===
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Lost highlight

[stan via users]

On Tue, 1 Nov 2022 20:13:54 +0100
Patrick Dupre  wrote:

> Hello,
> 
> In a terminal (gnome-terminal), I used to use the mouse right button,
> to copy paste highlighted text.
> Sometimes I lost this option: the highlight odes not work.
> It seems to be due to xmgrace.
> Do you know how to recover this way of going without closing all
> the xmgrace terminals?

I have a similar experience, except that I used to be able to double
click with the left button to select, and paste at the text cursor with
the center button, or left button drag to select and paste at the
text cursor with the center button in programs like claws-mail and gvim.
That hasn't worked for some time.  I assumed that it was because of the
decreased support for X because of wayland or that the mouse driver was
rewritten or there was a security issue.  The workarounds are clumsy.
The technique still works in the virtual consoles (F1-F6), so something
in the gui handling of mouse clicks has changed.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Lost highlight

[Samuel Sieb]

On 11/1/22 12:55, stan via users wrote:

I have a similar experience, except that I used to be able to double
click with the left button to select, and paste at the text cursor with
the center button, or left button drag to select and paste at the
text cursor with the center button in programs like claws-mail and gvim.
That hasn't worked for some time.  I assumed that it was because of the
decreased support for X because of wayland or that the mouse driver was
rewritten or there was a security issue.  The workarounds are clumsy.
The technique still works in the virtual consoles (F1-F6), so something
in the gui handling of mouse clicks has changed.


Are you using Wayland or X for the desktop?  In Wayland, I just tested 
drag and middle-click in gvim and it worked fine.


If you have mouse support in the virtual consoles, I assume you're 
running gpm, which is completely different than mouse support in the 
graphical desktop.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Nouveau Blacklisting not in /etc/default/grub

[Barry Scott]

> On 1 Nov 2022, at 11:53, greg  wrote:
> 
> On Tue, Nov 1, 2022 at 4:15 AM Stephen Morris  
> wrote:
>> I've just managed to get the 6.0.5 kernel to load the nvidia driver.
>> There is potentially a defect in the akmod-nvidia (or relevant package)
>> scripts in that it seems that they no longer add the blacklisting
>> statements for nouveau into the kernel parameters in /etc/default/grub,
>> I had to put those statements in there manually before the nvidia driver
>> was loaded instead of the nouveau driver.
> 

I think it is because it is no longer needed. My memory on this prompted by 
reply in another thread.
If nvidia fails to be available, not install or did not build, then nouveau is 
used.

Barry

> /etc/default/grub - contains default kernel options
> /boot/grub2/grubenv - has the line
> saved_entry=
>which refers to
> /boot/loader/entries/.conf
>which contains kernel options for the entry (which are actually used)
>which get modified when editing kernel options via grub menu (thus 
> becom
> ing persistent)
> 
> /etc/default/grub - contains the line
> GRUB_ENABLE_BLSCFG=true
>which is documented at
> https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
> 
> greg
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fwd: [Undeliverable: Re: Mailing lists and Discourse]

[Kevin Fenzi]

On Tue, Nov 01, 2022 at 03:50:07PM +0900, Stephen J. Turnbull wrote:
> Kevin Fenzi writes:
> 
>  > I can't force the list to do this. Your domain would need to enable
>  > DMARC and set reject or quarantine
> 
> Pretty sure it's not "his" domain.  I believe GMX is a major internet
> provider (and email provider) in Germany, which already has an
> explicit DMARC policy of 'none' on gmx.net, and 'quarantine' on
> subdomains.  I suspect they've thought out their DMARC configuration
> pretty carefully.

Perhaps so.
 
> Does Fedora participate in the ARC protocol?  I didn't see any ARC
> fields for Fedora in the headers.  Both of the sites he's reported
> DSNs from (outlook and Google) do understand ARC, so that might help
> (especially at Google, which is invoking From alignment even though
> GMX publishes 'p=none').  No promises, of course, as both those
> domains are well-known for thinking they know better than everyone
> else.

We don't currently have any ARC setup. 

When / if we can get the list processor upgraded, I think newer versions
of mailman3 have native ARC support, and we could look at enabling that. 

For now, no, there's no ARC support.

kevin


signature.asc
Description: PGP signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: grub2 Question

[Robert McBroom via users]

On 10/31/22 17:26, Felix Miata wrote:

Robert McBroom via users composed on 2022-10-31 17:17 (UTC-0400):


Running Fedora 35 and trying to fix installed boot files on a third drive.
~]# grub2-install /dev/sdc
grub2-install: error: this utility cannot be used for EFI platforms
because it does not support UEFI Secure Boot.
Secure Boot is turned off in the bios. The boot is from UEFI.

MBR is not a component of UEFI booting. The UEFI BIOS looks to the \EFI 
directory
on the ESP partition. Instead of grub2-install, do:

dnf reinstall grub2-efi grub2-efi-modules shim

after appropriately following the directions on



No mention of MBR as the drive is GPT. Totally UEFI system, four drives 
three OS. I was suspecting a problem with the boot sector, but on 
removal of all drives but the one, it boots. Adding the drives one by 
one to see the point of digression.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: grub2 Question

[Samuel Sieb]

On 11/1/22 14:37, Robert McBroom via users wrote:
No mention of MBR as the drive is GPT. Totally UEFI system, four drives 
three OS. I was suspecting a problem with the boot sector, but on 
removal of all drives but the one, it boots. Adding the drives one by 
one to see the point of digression.


UEFI doesn't use a boot sector.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Nouveau Blacklisting not in /etc/default/grub

[Robert McBroom via users]

On 11/1/22 16:46, Barry Scott wrote:



On 1 Nov 2022, at 11:53, greg  wrote:

On Tue, Nov 1, 2022 at 4:15 AM Stephen Morris  wrote:

I've just managed to get the 6.0.5 kernel to load the nvidia driver.
There is potentially a defect in the akmod-nvidia (or relevant package)
scripts in that it seems that they no longer add the blacklisting
statements for nouveau into the kernel parameters in /etc/default/grub,
I had to put those statements in there manually before the nvidia driver
was loaded instead of the nouveau driver.

I think it is because it is no longer needed. My memory on this prompted by 
reply in another thread.
If nvidia fails to be available, not install or did not build, then nouveau is 
used.

Barry


/etc/default/grub - contains default kernel options
/boot/grub2/grubenv - has the line
saved_entry=
which refers to
/boot/loader/entries/.conf
which contains kernel options for the entry (which are actually used)
which get modified when editing kernel options via grub menu (thus becom
ing persistent)

/etc/default/grub - contains the line
GRUB_ENABLE_BLSCFG=true
which is documented at
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault


Things seem to be in quite a mess. The grub.cfg file is almost 
irrelevant with only the Windows chainloader stanza having any meaning. 
It doesn't get updated with new kernals. Only 
/boot/loader/entries/*.conf. With the appropriate entries in /boot and 
/boot/loader/entries/*.conf multiple fedora invocations and centOS8 show 
in the menu and are boot-able. Not sure where blscfg comes in to the 
process. Dynamic change is far out stripping documentation.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Nouveau Blacklisting not in /etc/default/grub

[Stephen Morris]

On 1/11/22 22:53, greg wrote:

On Tue, Nov 1, 2022 at 4:15 AM Stephen Morris  wrote:

I've just managed to get the 6.0.5 kernel to load the nvidia driver.
There is potentially a defect in the akmod-nvidia (or relevant package)
scripts in that it seems that they no longer add the blacklisting
statements for nouveau into the kernel parameters in /etc/default/grub,
I had to put those statements in there manually before the nvidia driver
was loaded instead of the nouveau driver.

/etc/default/grub - contains default kernel options
/boot/grub2/grubenv - has the line
saved_entry=
 which refers to
/boot/loader/entries/.conf
 which contains kernel options for the entry (which are actually used)
 which get modified when editing kernel options via grub menu (thus 
becom
ing persistent)

/etc/default/grub - contains the line
GRUB_ENABLE_BLSCFG=true
 which is documented at
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
I have GRUB_ENABLE_BLSCFG=false in /etc/default/grub because I hate that 
functionality.
My concern was with the GRUB_CMDLINE_LINUX statement which was not 
supplying the parameters to blacklist the nouveau driver and load the 
nvidia driver that is supplied in other situations (maybe secureboot is 
impacting that functionality, the parameters were supplied before I got 
the signing keys into secureboot).


regards,
Steve

greg
___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Nouveau Blacklisting not in /etc/default/grub

[Samuel Sieb]

On 11/1/22 14:50, Robert McBroom via users wrote:

On 11/1/22 16:46, Barry Scott wrote:



On 1 Nov 2022, at 11:53, greg  wrote:
/etc/default/grub - contains the line
GRUB_ENABLE_BLSCFG=true
    which is documented at
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault


Things seem to be in quite a mess. The grub.cfg file is almost 
irrelevant with only the Windows chainloader stanza having any meaning. 
It doesn't get updated with new kernals. Only 
/boot/loader/entries/*.conf. With the appropriate entries in /boot and 
/boot/loader/entries/*.conf multiple fedora invocations and centOS8 show 
in the menu and are boot-able. Not sure where blscfg comes in to the 
process. Dynamic change is far out stripping documentation.


blscfg is documented at the link given there.  It refers to the files in 
/boot/loader/entries.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora 36: suspend failed with "PM: Some devices failed to suspend, or early wake event detected"

[Dario Lesca]

I have resolve this problem follow this Arch Linux howto:
https://wiki.archlinux.org/title/Power_management#Hybrid-sleep_on_suspend_or_hibernation_request

I have add these lines at the end of /etc/systemd/sleep.conf file
SuspendMode=suspend
SuspendState=disk
HibernateMode=suspend
HibernateState=disk

Now suspend work fine every time

Thanks
Dario
 
Il giorno mer, 14/09/2022 alle 09.25 +0200, Dario Lesca ha scritto:
> When I try suspend with "systemctl suspend" my notebook Fedora 36
> sometime do not suspend with "PM: Some devices failed to suspend, or
> early wake event detected" error.
> 
> Someone can help me to resolve this issue?
> 
> Many thanks
> Dario
> 
> #
> set 14 00:41:26 dodo.home.solinos.it kernel: PM: suspend entry
> (s2idle)
> set 14 00:41:26 dodo.home.solinos.it kernel: Filesystems sync: 0.006
> seconds
> set 14 00:41:28 dodo.home.solinos.it kernel: Freezing user space
> processes ... (elapsed 0.005 seconds) done.
> set 14 00:41:28 dodo.home.solinos.it kernel: OOM killer disabled.
> set 14 00:41:28 dodo.home.solinos.it kernel: Freezing remaining
> freezable tasks ... (elapsed 0.002 seconds) done.
> set 14 00:41:28 dodo.home.solinos.it kernel: printk: Suspending
> console(s) (use no_console_suspend to debug)
> set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd :00:14.0:
> PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
> set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd :00:14.0:
> PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
> set 14 00:41:28 dodo.home.solinos.it kernel: xhci_hcd :00:14.0:
> PM: failed to suspend async: error -16
> set 14 00:41:28 dodo.home.solinos.it kernel: PM: Some devices failed
> to suspend, or early wake event detected
> set 14 00:41:28 dodo.home.solinos.it kernel: nouveau :01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:28 dodo.home.solinos.it kernel: nouveau :01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:28 dodo.home.solinos.it kernel: nouveau :01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:28 dodo.home.solinos.it kernel: nouveau :01:00.0:
> fb: VPR locked, but no scrubber binary!
> set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3: reset high-
> speed USB device number 4 using xhci_hcd
> set 14 00:41:28 dodo.home.solinos.it kernel: ata1: SATA link down
> (SStatus 4 SControl 300)
> set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3.1: reset low-
> speed USB device number 6 using xhci_hcd
> set 14 00:41:28 dodo.home.solinos.it kernel: usb 1-3.2: reset high-
> speed USB device number 8 using xhci_hcd
> set 14 00:41:28 dodo.home.solinos.it kernel: PM: resume devices took
> 1.418 seconds
> set 14 00:41:28 dodo.home.solinos.it kernel: OOM killer enabled.
> set 14 00:41:28 dodo.home.solinos.it kernel: Restarting tasks ...
> done.
> set 14 00:41:28 dodo.home.solinos.it gvfsd[219783]: PTP: reading
> event an error 0x05 occurred
> set 14 00:41:28 dodo.home.solinos.it kernel: thermal thermal_zone9:
> failed to read out thermal zone (-61)
> set 14 00:41:29 dodo.home.solinos.it bluetoothd[1739]: Controller
> resume with wake event 0x0
> set 14 00:41:29 dodo.home.solinos.it kernel: PM: suspend exit
> set 14 00:41:29 dodo.home.solinos.it kernel: PM: suspend entry
> (s2idle)
> set 14 00:41:29 dodo.home.solinos.it kernel: Filesystems sync: 0.002
> seconds
> set 14 00:41:31 dodo.home.solinos.it kernel: Freezing user space
> processes ... (elapsed 0.002 seconds) done.
> set 14 00:41:31 dodo.home.solinos.it kernel: OOM killer disabled.
> set 14 00:41:31 dodo.home.solinos.it kernel: Freezing remaining
> freezable tasks ... (elapsed 0.003 seconds) done.
> set 14 00:41:31 dodo.home.solinos.it kernel: printk: Suspending
> console(s) (use no_console_suspend to debug)
> set 14 00:41:31 dodo.home.solinos.it kernel: mei_hdcp :00:16.0-
> b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops
> i915_hdcp_component_ops [i915])
> set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd :00:14.0:
> PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
> set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd :00:14.0:
> PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
> set 14 00:41:31 dodo.home.solinos.it kernel: xhci_hcd :00:14.0:
> PM: failed to suspend async: error -16
> set 14 00:41:31 dodo.home.solinos.it kernel: PM: Some devices failed
> to suspend, or early wake event detected
> set 14 00:41:31 dodo.home.solinos.it kernel: nouveau :01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:31 dodo.home.solinos.it kernel: nouveau :01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:31 dodo.home.solinos.it kernel: nouveau :01:00.0:
> Refused to change power state from D3hot to D0
> set 14 00:41:31 dodo.home.solinos.it kernel: nouveau :01:00.0:
> fb: VPR locked, but no scrubber binary!
> set 14 00:41:31 dodo.home.solinos.it kernel: usb 1

Re: grub2 Question

[Felix Miata]

Robert McBroom via users composed on 2022-11-01 17:37 (UTC-0400):

>> Robert McBroom via users composed on 2022-10-31 17:17 (UTC-0400):

>>> ~]# grub2-install /dev/sdc
>>> grub2-install: error: this utility cannot be used for EFI platforms
...
> No mention of MBR as the drive is GPT. 

MBR is implicit in

grub2-install /dev/sdc

A GPT MBR is normally kept unused except for a portion of its last 66 bytes, the
partition table's starting location:

-0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00010-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00020-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00030-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00040-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00050-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00060-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00070-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00080-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00090-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-000A0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-000B0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-000C0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-000D0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-000E0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-000F0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00100-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00110-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00120-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00130-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00140-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00150-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00160-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00170-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00180-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-00190-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-001A0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-001B0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-001C0-  02 00 ee ff ff ff 01 00  00 00 af 6d 70 74 00 00 [...mpt..]
-001D0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-001E0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 []
-001F0-  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa [..U.]
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Nouveau Blacklisting not in /etc/default/grub

[Stephen Morris]

On 2/11/22 07:46, Barry Scott wrote:



On 1 Nov 2022, at 11:53, greg  wrote:

On Tue, Nov 1, 2022 at 4:15 AM Stephen Morris  wrote:

I've just managed to get the 6.0.5 kernel to load the nvidia driver.
There is potentially a defect in the akmod-nvidia (or relevant package)
scripts in that it seems that they no longer add the blacklisting
statements for nouveau into the kernel parameters in /etc/default/grub,
I had to put those statements in there manually before the nvidia driver
was loaded instead of the nouveau driver.

I think it is because it is no longer needed. My memory on this prompted by 
reply in another thread.
If nvidia fails to be available, not install or did not build, then nouveau is 
used.
The nouveau blacklisting parameters were added to /etc/default/grub 
before I embarked on adding the signing keys for the nvidia driver into 
secureboot. Those parameters are still required as even though 
akmod/kmod is providing the driver for the booted kernel without those 
parameters in /etc/default/grub and propagated into grub.cfg via 
grub2-mkconfig the nouveau driver is used instead. What seems to be the 
functionality now is, if the nvidia driver can't be loaded for whatever 
reason the system does a fail over to nouveau, and produces a message to 
that effect, even if the blacklisting parameters are specified. I was in 
that situation when I changed the secureboot mode and lack of signing 
was preventing the nvidia driver from being loaded by the kernel (in 
full secure boot mode the kernel won't allow non-signed drivers to be 
loaded). What I found was that after activating full secureboot the 
install of akmod-nvidia, kmod-nvidia and all the associated packages no 
longer added the parameters into /etc/default/grub.


regards,
Steve


Barry


/etc/default/grub - contains default kernel options
/boot/grub2/grubenv - has the line
saved_entry=
which refers to
/boot/loader/entries/.conf
which contains kernel options for the entry (which are actually used)
which get modified when editing kernel options via grub menu (thus becom
ing persistent)

/etc/default/grub - contains the line
GRUB_ENABLE_BLSCFG=true
which is documented at
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault

greg
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Nouveau Blacklisting not in /etc/default/grub

[Stephen Morris]

On 2/11/22 08:57, Samuel Sieb wrote:

On 11/1/22 14:50, Robert McBroom via users wrote:

On 11/1/22 16:46, Barry Scott wrote:



On 1 Nov 2022, at 11:53, greg  wrote:
/etc/default/grub - contains the line
GRUB_ENABLE_BLSCFG=true
    which is documented at
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault


Things seem to be in quite a mess. The grub.cfg file is almost 
irrelevant with only the Windows chainloader stanza having any 
meaning. It doesn't get updated with new kernals. Only 
/boot/loader/entries/*.conf. With the appropriate entries in /boot 
and /boot/loader/entries/*.conf multiple fedora invocations and 
centOS8 show in the menu and are boot-able. Not sure where blscfg 
comes in to the process. Dynamic change is far out stripping 
documentation.


blscfg is documented at the link given there.  It refers to the files 
in /boot/loader/entries.

I have blscfg disabled in /etc/default/grub because I hate it functionality.
/etc/default/grub is still significant if using grub2-mkconfig, it may 
be supplemented from the other locations, but what is in there is still 
honoured.
What seems to be the problem now, which may be the rpmfusion environment 
or may be Fedora, is that they don't play properly with full secureboot. 
What I'm experiencing is that in full secureboot mode is the install of 
the nvidia packages from either rpmfusion-nonfree or from 
rpmfusion-nonfree-nvidia, which ever one dnf is using, does not add the 
nouveau blacklisting parameters and the nvidia modeset parameter into 
the kernel parameters in /etc/default/grub that are added in non-full 
secureboot mode.
The grub menu is extremely relevant, at least for me, when booting 
between Fedora, Windows and Ubuntu, albeit ignoring the os-prober 
functionality that is wrong (it boots Ubuntu from the wrong partition 
for UEFI, but even though it is wrong Ubuntu still boots anyway, and 
ignoring the fact that Ubuntu ignores certain configuration 
specifications at install time, at least if in UEFI mode.


regards,
Steve


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Lost highlight

[stan via users]

On Tue, 1 Nov 2022 13:18:52 -0700
Samuel Sieb  wrote:

> On 11/1/22 12:55, stan via users wrote:
> > I have a similar experience, except that I used to be able to double
> > click with the left button to select, and paste at the text cursor
> > with the center button, or left button drag to select and paste at
> > the text cursor with the center button in programs like claws-mail
> > and gvim. That hasn't worked for some time.  I assumed that it was
> > because of the decreased support for X because of wayland or that
> > the mouse driver was rewritten or there was a security issue.  The
> > workarounds are clumsy. The technique still works in the virtual
> > consoles (F1-F6), so something in the gui handling of mouse clicks
> > has changed.  
> 
> Are you using Wayland or X for the desktop?  In Wayland, I just
> tested drag and middle-click in gvim and it worked fine.

X, and with LXDE.  I've been meaning to check if wayland now allows
custom keymappings.  Maybe time to try gnome or kde again.  In X, when
I use gvim it pastes the selected text at the mouse cursor.  So, if I'm
editing something and want to grab some phrase from the text above, and
paste it at the text cursor where I am typing, it makes a mess by
pasting it where the mouse cursor is.  Same in Claws mail. 

> If you have mouse support in the virtual consoles, I assume you're 
> running gpm, which is completely different than mouse support in the 
> graphical desktop.

Yes, running gpm.  If I select something in vim, and click the middle
button, it puts the text at the text cursor where I am typing, not at
the mouse cursor.  X used to behave like this for me.  I find it
convenient, saves me from moving around in the file with the text
position.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Lost highlight

[Samuel Sieb]

On 11/1/22 15:36, stan via users wrote:

On Tue, 1 Nov 2022 13:18:52 -0700
Samuel Sieb  wrote:


On 11/1/22 12:55, stan via users wrote:

I have a similar experience, except that I used to be able to double
click with the left button to select, and paste at the text cursor
with the center button, or left button drag to select and paste at
the text cursor with the center button in programs like claws-mail
and gvim. That hasn't worked for some time.  I assumed that it was
because of the decreased support for X because of wayland or that
the mouse driver was rewritten or there was a security issue.  The
workarounds are clumsy. The technique still works in the virtual
consoles (F1-F6), so something in the gui handling of mouse clicks
has changed.


Are you using Wayland or X for the desktop?  In Wayland, I just
tested drag and middle-click in gvim and it worked fine.


X, and with LXDE.  I've been meaning to check if wayland now allows
custom keymappings.  Maybe time to try gnome or kde again.  In X, when
I use gvim it pastes the selected text at the mouse cursor.  So, if I'm
editing something and want to grab some phrase from the text above, and
paste it at the text cursor where I am typing, it makes a mess by
pasting it where the mouse cursor is.  Same in Claws mail.


That's the normal behaviour for graphical programs for as long as I can 
remember.  gvim might have been a special case, but I don't use it.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Can I see an iMac drive with a Live USB?

[George N. White III]

On Tue, Nov 1, 2022 at 3:14 PM Roger Heflin  wrote:

> I usually add a bs=4k or bs=16k or a bs=256k when using dd so the
> blocksize is larger.  That usually makes it quite a bit  faster.


fdisk shows block size

>
>
> And if you background the dd you can use "vmstat 1" and the bi/bo
> columns tell you the actual disk io rates, and you can use that to
> reliably estimate.


Elderly rescue CD’s have busybox, which provides nmeter.Fdisk gives
values for logical and physical block size, but those may be fictional.

 % doas fdisk -l /dev/sdb1

Disk /dev/sdb1: 1.91 TiB, 2100425654272 bytes, 4102393856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

On the elderly iMac, logical and physical were both 512.



>
> Default is 512 and does not align with most (all?) underlying physical
> devices block sizes and may cause various layers extra work and take
> much longer.
>

I have done experiments preparatory to using dd to clone a box of disks.
Modern storage devices are more complicated and network speed means
sneakernet is no longer needed.

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Can I see an iMac drive with a Live USB?

[Samuel Sieb]

On 11/1/22 11:13, Roger Heflin wrote:

I usually add a bs=4k or bs=16k or a bs=256k when using dd so the
blocksize is larger.  That usually makes it quite a bit  faster.


I usually use at least bs=1M.


And if you background the dd you can use "vmstat 1" and the bi/bo
columns tell you the actual disk io rates, and you can use that to
reliably estimate.


A much more friendly disk speed option is "iostat 5" (the 5 is how many 
seconds between updates).


You can also use "status=progress" as a dd option.

Why would you background dd versus using a second terminal tab?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Can I see an iMac drive with a Live USB?

[Roger Heflin]

For people that don't want to use a 2nd terminal, and/or are working
in single user mode.

I usually do the =1M also, and the default for dd has always sucked
going back 30+ years.

On Tue, Nov 1, 2022 at 6:56 PM Samuel Sieb  wrote:
>
> On 11/1/22 11:13, Roger Heflin wrote:
> > I usually add a bs=4k or bs=16k or a bs=256k when using dd so the
> > blocksize is larger.  That usually makes it quite a bit  faster.
>
> I usually use at least bs=1M.
>
> > And if you background the dd you can use "vmstat 1" and the bi/bo
> > columns tell you the actual disk io rates, and you can use that to
> > reliably estimate.
>
> A much more friendly disk speed option is "iostat 5" (the 5 is how many
> seconds between updates).
>
> You can also use "status=progress" as a dd option.
>
> Why would you background dd versus using a second terminal tab?
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Can I see an iMac drive with a Live USB?

[Go Canes]

When using dd for copying or erasing disks, I typically use bs=1M.

For erasing disks I prefer to use the shred utility - multiple passes
with various patterns and it displays progress.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Can I see an iMac drive with a Live USB?

[Mauricio Tavares]

I second shred. Only issue is that if drive is ssd chances are you
will not overwrite every sector.

Todd, I do not know how old those iMacs are, but some (lampshade) had
the drives on the base while others have it behind the motherboard
behind the monitor. And some also had the drive soldered to the
motherboard.

On Tue, Nov 1, 2022 at 9:04 PM Go Canes  wrote:
>
> When using dd for copying or erasing disks, I typically use bs=1M.
>
> For erasing disks I prefer to use the shred utility - multiple passes
> with various patterns and it displays progress.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fwd: [Undeliverable: Re: Mailing lists and Discourse]

[Slade Watkins via users]

On 11/1/22 5:30 PM, Kevin Fenzi wrote:
> We don't currently have any ARC setup. 
> 
> When / if we can get the list processor upgraded, I think newer versions
> of mailman3 have native ARC support, and we could look at enabling that. 
> 

I think so, yeah. 100% worth looking at when/if upgraded.

-srw

--
I use plain text email and bottom post: https://useplaintext.email
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Can I see an iMac drive with a Live USB?

[Slade Watkins via users]

On 11/1/22 11:54 PM, Mauricio Tavares wrote:
> I second shred. Only issue is that if drive is ssd chances are you
> will not overwrite every sector.

Ditto, as well.

> 
> Todd, I do not know how old those iMacs are, but some (lampshade) had
> the drives on the base while others have it behind the motherboard
> behind the monitor. And some also had the drive soldered to the
> motherboard.
> 

I didn't even think about that. Apple sticks to the same design for
basically everything for so long I hadn't considered that when I
originally replied to Todd.

-srw

--
I use plain text email and bottom post: https://useplaintext.email
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue