Re: Getting a new printer/scanner
On Tue, 2022-06-21 at 17:30 +0100, Patrick O'Callaghan wrote: > On Tue, 2022-06-21 at 06:54 -0700, Doug Herr wrote: > > > I installed and configured the driver as a dnssd service (using > > > the > > > KDE > > > system settings panel), but I'm getting an error: "Unable to > > > locate > > > printer". > > > > > > The dnssd daemon is running, as is systemd-resolved and avahi- > > > daemon. > > > I've logged out and in again to no effect. > > > > > > Journalctl shows nothing relevant (using "-g dnssd" or "-g dns- > > > sd"). > > > > Is Cups running? > > If so, does it see the printer? > > Yes and yes. The CUPS admin page page shows the printer, but the test > page in the queue has "Unable to locate printer". > > To be clear, the printer does physically work with the Brother > driver. > On installing the brlaser driver I created a new printer and marked > it > as default, but didn't uninstall the Brother software. It's possible > that this is causing some kind of interference, so I'll uninstall it > and try again. I removed the old driver and it made no difference. Since this is getting off-topic wrt the original thread subject, I'm going to re-post as a new topic. poc ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Configuring a printer with DNS-SD
(See ... for context) I have a Brother All-in-one wireless laser printer/scanner which has worked for years using the manufacturer's driver blob. I now want to configure it using the printer-driver-brlaser package from the Fedora repo. I've uninstalled the original Brother driver and deleted the printer config using the CUPS interface. I then added a new printer using the KDE System Settings widget, and attempted to print a test page. This appears to go through, but then the queue status shows "Unable to locate printer". I deleted that configuration and tried again using the CUPS web interface. This shows up as: dnssd://Brother%20DCP-7055W._ipp._tcp.local/ Printing a test page again shows "Unable to locate printer". This happens both using the generic IPP driver and the specific model driver from the RPM package. The CUPS systemd service and AVAHI daemon are both running, as is systemd-resolved, which handles DNS-SD (I reloaded the latter just in case.) I'm out of ideas. To repeat: both printing and scanning work correctly with the manufacturer's driver, so it's not a hardware or connection problem. Any thoughts before I give up and revert to the binary blob? poc ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
Dear friends, I have a fully updated F36 Dell XPS 13 that has been updated nightly (and upgraded when appropriate) using dnf on a cron job for the past few years. Sadly, after last Thursday's updates, the machine goes down fine (with the usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had any suggestions as to how I may diagnose and fix this problem. Many thanks and best wishes, Ranjan ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: CPU Access in the Kernel
On Tue, Jun 14, 2022 at 05:44:27PM -0600, Jerry James wrote: > > Just a quick question. To determine how many cpu's/cores/channels > > the kernel is configured to support, do I need to look at the kernel > > source to determine if all of the cores I have are capable of being > > used, or is there something else available to tell me without going to > > the source? > > The values the kernel was configured with are in > /boot/config-. If I understand your question correctly, you > are looking for CONFIG_NR_CPUS, which is 8192 on my machine. You can also look at /proc/cpuinfo for what's actually detected — or run `lscpu` for a more human-readable view (especially when there are a lot of identical cores!) Or, `cpu-x` for a GUI view with a lot of detail. -- Matthew Miller Fedora Project Leader ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Configuring a printer with DNS-SD
On Wed, Jun 22, 2022 at 8:32 AM Patrick O'Callaghan wrote: > (See ... for context) > > I have a Brother All-in-one wireless laser printer/scanner which has > worked for years using the manufacturer's driver blob. I now want to > configure it using the printer-driver-brlaser package from the Fedora > repo. > > I've uninstalled the original Brother driver and deleted the printer > config using the CUPS interface. > > I then added a new printer using the KDE System Settings widget, and > attempted to print a test page. This appears to go through, but then > the queue status shows "Unable to locate printer". > > I deleted that configuration and tried again using the CUPS web > interface. This shows up as: > > dnssd://Brother%20DCP-7055W._ipp._tcp.local/ > I suspect this detection doesn't adequately check the details of the IPP support. Given the age of the printer, IPP may not be implemented "properly" by current standards. > Printing a test page again shows "Unable to locate printer". This > happens both using the generic IPP driver and the specific model driver > from the RPM package. > I looked at the Brother DCP-7055W Advanced User's Guide, which is dated 2012. I can't see any mention of IPP or AirPrint. https://discussions.apple.com/thread/7199902 says this model was not on Apple's list of supported printers for AirPort in 2015. https://wiki.gentoo.org/wiki/Brother_networked_printer says the printer works, but gives no configuration details https://www.pwg.org/ipp/ippguide.html tells you to "Consult your Printer documentation or the Printer's Bonjour (DNS-SD) registration information to determine the proper hostname, port number, and path to use for your Printer." It would be interesting to know why IPP is failing, but I suspect you are stuck with Brother's rpm. > The CUPS systemd service and AVAHI daemon are both running, as is > systemd-resolved, which handles DNS-SD (I reloaded the latter just in > case.) > > I'm out of ideas. To repeat: both printing and scanning work correctly > with the manufacturer's driver, so it's not a hardware or connection > problem. > > Any thoughts before I give up and revert to the binary blob? > > poc > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On Wed, Jun 22, 2022 at 8:43 AM Ranjan Maitra wrote: > Dear friends, > > I have a fully updated F36 Dell XPS 13 that has been updated nightly (and > upgraded when appropriate) using dnf on a cron job for the past few years. > Sadly, after last Thursday's updates, the machine goes down fine (with the > usual systemctl hibernate), but does not come back up. I am a little > confused what changed last Thursday, but I was wondering if anyone had any > suggestions as to how I may diagnose and fix this problem. > Is this a dual boot with Windows? Did you recently get firmware updates from Dell? Have you looked at messages using journalctl? -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On Wed Jun22'22 11:40:10AM, George N. White III wrote: > From: "George N. White III" > Date: Wed, 22 Jun 2022 11:40:10 -0300 > To: Community support for Fedora users > Reply-To: Community support for Fedora users > Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from > hibernate (post Thursday updates) > > On Wed, Jun 22, 2022 at 8:43 AM Ranjan Maitra wrote: > > > Dear friends, > > > > I have a fully updated F36 Dell XPS 13 that has been updated nightly (and > > upgraded when appropriate) using dnf on a cron job for the past few years. > > Sadly, after last Thursday's updates, the machine goes down fine (with the > > usual systemctl hibernate), but does not come back up. I am a little > > confused what changed last Thursday, but I was wondering if anyone had any > > suggestions as to how I may diagnose and fix this problem. > > > > Is this a dual boot with Windows? Did you recently get firmware updates > from Dell? Have you > looked at messages using journalctl? My apologies for overlooking such obvious necessary information. To answer your questions: > Is this a dual boot with Windows? No, only runs Fedora since I bought it. I believe I wiped out all partitions when it came and put up Fedora (in 2018). > Did you recently get firmware updates from Dell? No, sorry. I did not even check. > Have you looked at messages using journalctl? So, I don't really know what to look for, but I tried: journalctl | grep hibernate and got: Jun 22 06:06:49 localhost.localdomain systemd[1]: Created slice system-systemd\x2dhibernate\x2dresume.slice - Slice /system/systemd-hibernate-resume. Jun 22 06:06:50 localhost.localdomain systemd[1]: Starting systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service - Resume from hibernation using device /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605... Jun 22 06:06:50 localhost.localdomain systemd-hibernate-resume[390]: Could not resume from '/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605' (259:4). Jun 22 06:06:50 localhost.localdomain systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service: Deactivated successfully. Jun 22 06:06:50 localhost.localdomain systemd[1]: Finished systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service - Resume from hibernation using device /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605. Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Note however, that this is after the machine was asked to reboot since the system never came back from hibernate so I am not completely sure it has the information from not coming back. Let me know what else I should look for. Many thanks again and best wishes, Ranjan ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Configuring a printer with DNS-SD
On Wed, Jun 22, 2022, at 4:32 AM, Patrick O'Callaghan wrote: > (See ... for context) > > I have a Brother All-in-one wireless laser printer/scanner which has > worked for years using the manufacturer's driver blob. I now want to > configure it using the printer-driver-brlaser package from the Fedora > repo. > > I've uninstalled the original Brother driver and deleted the printer > config using the CUPS interface. > > I then added a new printer using the KDE System Settings widget, and > attempted to print a test page. This appears to go through, but then > the queue status shows "Unable to locate printer". > > I deleted that configuration and tried again using the CUPS web > interface. This shows up as: > > dnssd://Brother%20DCP-7055W._ipp._tcp.local/ > > Printing a test page again shows "Unable to locate printer". This > happens both using the generic IPP driver and the specific model driver > from the RPM package. > > The CUPS systemd service and AVAHI daemon are both running, as is > systemd-resolved, which handles DNS-SD (I reloaded the latter just in > case.) > > I'm out of ideas. To repeat: both printing and scanning work correctly > with the manufacturer's driver, so it's not a hardware or connection > problem. > > Any thoughts before I give up and revert to the binary blob? George might have the final answer, maybe your model will only work via a USP connection if using the brlaser option. But, I checked my virtual machine to see how it is connecting to the printer... Brother_DCP-L2550DW_series Brother_DCP-L2550DW_series (Idle, Accepting Jobs, Not Shared) Description:Brother DCP-L2550DW series Location: Driver: Brother DCP-L2550DW series, using brlaser v6 (grayscale, 2-sided printing) Connection: dnssd://Brother%20DCP-L2550DW%20series._pdl-datastream._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4d12445 Defaults: job-sheets=none, none media=na_letter_8.5x11in sides=two-sided-long-edge So it does seem to be using dnssd. This is a pretty generic F36 XFCE install so I did not do much to get that working, mostly just needed to start cups. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Configuring a printer with DNS-SD
On Wed, Jun 22, 2022, at 8:01 AM, Doug Herr wrote:
> But, I checked my virtual machine to see how it is connecting to the
> printer...
>
> Brother_DCP-L2550DW_series
I just thought to check the web interface that the printer provides and I see
that connection protocols can be turned off.
This is at http://{printer IP}/net/net/protocol.html
Protocol
Web Based Management (Web Server) HTTP Server Settings
SNMPAdvanced Settings
LPD Advanced Settings
Raw Port
IPP HTTP Server Settings
AirPrintAdvanced Settings HTTP Server Settings
Mopria
Web ServicesAdvanced Settings HTTP Server Settings
Mobile printing for Windows
Proxy Advanced Settings
Network Scan
SMTPAdvanced Settings
FTP Server
FTP Client
TFTP
mDNSAdvanced Settings
LLMNR
The only two that are unchecked for the above list are "FTP Server" and "Proxy".
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Configuring a printer with DNS-SD
On Wed, Jun 22, 2022 at 12:43 PM Doug Herr
wrote:
> On Wed, Jun 22, 2022, at 8:01 AM, Doug Herr wrote:
> > But, I checked my virtual machine to see how it is connecting to the
> printer...
> >
> > Brother_DCP-L2550DW_series
>
This seems to be a much newer printer and does have Apple AirPrint.
AirPrint was
introduced in 2011 to support iPads.
https://openprinting.github.io/driverless/01-standards-and-their-pdls/
summarizes the differences in the various Driverless Printing
implementations. PDF is supported
across the board, but there are several raster formats and also PDFm which
is viewable with PDF viewers,
but tailored for the capabilities of specific printer models. AirPrint and
IPP use different raster formats,
and Apple could change the details in the future, but currently it doesn't
appear to be a big deal as most
printers support both and conversion from IPP to Apple raster formats just
requires simplifying the header,
so probably easy to implement in the printer to gain IPP support.
> I just thought to check the web interface that the printer provides and I
> see that connection protocols can be turned off.
>
> This is at http://{printer IP}/net/net/protocol.html
>
>
> Protocol
> Web Based Management (Web Server) HTTP Server Settings
> SNMPAdvanced Settings
> LPD Advanced Settings
> Raw Port
> IPP HTTP Server Settings <<< CUPS driverless printing
> AirPrintAdvanced Settings HTTP Server Settings
> Mopria << also a "driverless printing" protocol
> Web ServicesAdvanced Settings HTTP Server Settings
> Mobile printing for Windows
> Proxy Advanced Settings
> Network Scan
> SMTPAdvanced Settings
> FTP Server
> FTP Client
> TFTP
> mDNSAdvanced Settings
> LLMNR
>
> The only two that are unchecked for the above list are "FTP Server" and
> "Proxy".
>
--
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On Wed, Jun 22, 2022 at 12:00 PM Ranjan Maitra wrote: > On Wed Jun22'22 11:40:10AM, George N. White III wrote: > > From: "George N. White III" > > Date: Wed, 22 Jun 2022 11:40:10 -0300 > > To: Community support for Fedora users > > Reply-To: Community support for Fedora users < > users@lists.fedoraproject.org> > > Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from > > hibernate (post Thursday updates) > > > > On Wed, Jun 22, 2022 at 8:43 AM Ranjan Maitra wrote: > > > > > Dear friends, > > > > > > I have a fully updated F36 Dell XPS 13 that has been updated nightly > (and > > > upgraded when appropriate) using dnf on a cron job for the past few > years. > > > Sadly, after last Thursday's updates, the machine goes down fine (with > the > > > usual systemctl hibernate), but does not come back up. I am a little > > > confused what changed last Thursday, but I was wondering if anyone had > any > > > suggestions as to how I may diagnose and fix this problem. > > > > > > > Is this a dual boot with Windows? Did you recently get firmware updates > > from Dell? Have you > > looked at messages using journalctl? > > My apologies for overlooking such obvious necessary information. To answer > your questions: > > > Is this a dual boot with Windows? > > No, only runs Fedora since I bought it. I believe I wiped out all > partitions when it came and put up Fedora (in 2018). > > > Did you recently get firmware updates from Dell? > > No, sorry. I did not even check. > > > Have you looked at messages using journalctl? > > So, I don't really know what to look for, but I tried: > > journalctl | grep hibernate > > and got: > > Jun 22 06:06:49 localhost.localdomain systemd[1]: Created slice > system-systemd\x2dhibernate\x2dresume.slice - Slice > /system/systemd-hibernate-resume. > Jun 22 06:06:50 localhost.localdomain systemd[1]: Starting > systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service > - Resume from hibernation using device > /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605... > Jun 22 06:06:50 localhost.localdomain systemd-hibernate-resume[390]: > Could not resume from > '/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605' (259:4). > Next chance, make Searching for "systemd-hibernate-resume Could not resume from 'dev/disk/by-uuid" in the past year may give you some ideas. Interesting hit was https://www.suse.com/support/kb/doc/?id=20264, which says: Specifying to attempt resuming from a hibernation image should not normally result in a failure to boot. SUSE Support has observed cases in which it does. These include: Security hardened systems Systems in which the swap device, root filesystem or /boot partition was not specified by UUID Otherwise improperly configured GRUB, such as duplicate resume= parameters Cases where the swap device was unreachable. > Jun 22 06:06:50 localhost.localdomain systemd[1]: > systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service: > Deactivated successfully. > Why is ASCII "minus/dash" (-) is shown as hex "\x2d"? I see similar entries on my Fedora 35 system. -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
Thanks! > > > > Dear friends, > > > > > > > > I have a fully updated F36 Dell XPS 13 that has been updated nightly > > (and > > > > upgraded when appropriate) using dnf on a cron job for the past few > > years. > > > > Sadly, after last Thursday's updates, the machine goes down fine (with > > the > > > > usual systemctl hibernate), but does not come back up. I am a little > > > > confused what changed last Thursday, but I was wondering if anyone had > > any > > > > suggestions as to how I may diagnose and fix this problem. > > > > > > > > > > Is this a dual boot with Windows? Did you recently get firmware updates > > > from Dell? Have you > > > looked at messages using journalctl? > > > > My apologies for overlooking such obvious necessary information. To answer > > your questions: > > > > > Is this a dual boot with Windows? > > > > No, only runs Fedora since I bought it. I believe I wiped out all > > partitions when it came and put up Fedora (in 2018). > > > > > Did you recently get firmware updates from Dell? > > > > No, sorry. I did not even check. > > > > > Have you looked at messages using journalctl? > > > > So, I don't really know what to look for, but I tried: > > > > journalctl | grep hibernate > > > > and got: > > > > Jun 22 06:06:49 localhost.localdomain systemd[1]: Created slice > > system-systemd\x2dhibernate\x2dresume.slice - Slice > > /system/systemd-hibernate-resume. > > Jun 22 06:06:50 localhost.localdomain systemd[1]: Starting > > systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service > > - Resume from hibernation using device > > /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605... > > Jun 22 06:06:50 localhost.localdomain systemd-hibernate-resume[390]: > > Could not resume from > > '/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605' (259:4). > > > > Next chance, make > > Searching for "systemd-hibernate-resume Could not resume from > 'dev/disk/by-uuid" in the past year may give you some ideas. > Interesting hit was https://www.suse.com/support/kb/doc/?id=20264, > which says: > > Specifying to attempt resuming from a hibernation image should not normally > result in a failure to boot. I don't know what this means, but I do boot in, but not to the hibernated state, but a new one. > SUSE Support has observed cases in which it > does. These include: > > Security hardened systems > Systems in which the swap device, root filesystem or /boot partition > was not specified by UUID > Otherwise improperly configured GRUB, such as duplicate resume= > parameters > Cases where the swap device was unreachable. > I have changed nothing for months, if not years. In any case, I am pretty certain the first three points are not true for me, and I have no idea as to how to see if the swap device is reachable or not. Btw, I have noticed something, that the grub menu now has an entry for the kernel with debug as well as the kernel itself (which is what it boots into, and does not resume). Before last week (at least), there were not two entries: one for the kernel with debug and the other for the kernel only. I am not sure if this is relevant. My /etc/default/grub is as follows: GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="resume=UUID=a83ac239-cc10-43a6-be54-de4ce7050605 rhgb quiet" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true It was last updated on May 5, 2019. > > > Jun 22 06:06:50 localhost.localdomain systemd[1]: > > systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service: > > Deactivated successfully. > > > > Why is ASCII "minus/dash" (-) is shown as hex "\x2d"? I see similar > entries on my Fedora 35 system. > Don't know, sorry. Thanks again for your help and your suggestions, Ranjan ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Configuring a printer with DNS-SD
On Wed, 2022-06-22 at 11:35 -0300, George N. White III wrote: > > I deleted that configuration and tried again using the CUPS web > > interface. This shows up as: > > > > dnssd://Brother%20DCP-7055W._ipp._tcp.local/ > > > > I suspect this detection doesn't adequately check the details of the > IPP support. Given the age of the printer, IPP may not be > implemented > "properly" by current standards. > > > > Printing a test page again shows "Unable to locate printer". This > > happens both using the generic IPP driver and the specific model > > driver > > from the RPM package. > > > > I looked at the Brother DCP-7055W Advanced User's Guide, which is > dated > 2012. I can't see any mention of IPP or AirPrint. The User's Guide and Networking Guide are both pretty basic and mostly talk about using the manufacturer's admin utility for setup under Windows. However I was motivated to try the RPM package because it explicitly lists the DCP-7055W as one of the supported models. poc ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Configuring a printer with DNS-SD
On Wed, 2022-06-22 at 08:01 -0700, Doug Herr wrote: > George might have the final answer, maybe your model will only work > via a USP connection if using the brlaser option. > > But, I checked my virtual machine to see how it is connecting to the > printer... > > Brother_DCP-L2550DW_series > Brother_DCP-L2550DW_series (Idle, Accepting Jobs, Not Shared) > Description:Brother DCP-L2550DW series > Location: > Driver: Brother DCP-L2550DW series, using brlaser v6 (grayscale, 2- > sided printing) > Connection: dnssd://Brother%20DCP-L2550DW%20series._pdl- > datastream._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4d12445 > Defaults: job-sheets=none, none media=na_letter_8.5x11in > sides=two-sided-long-edge > > So it does seem to be using dnssd. This is a pretty generic F36 XFCE > install so I did not do much to get that working, mostly just needed > to start cups. That looks like a different model, and a later one than mine I think. poc ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Configuring a printer with DNS-SD
On Wed, 2022-06-22 at 14:01 -0300, George N. White III wrote: > On Wed, Jun 22, 2022 at 12:43 PM Doug Herr > > wrote: > > > On Wed, Jun 22, 2022, at 8:01 AM, Doug Herr wrote: > > > But, I checked my virtual machine to see how it is connecting to > > > the > > printer... > > > > > > Brother_DCP-L2550DW_series > > > > This seems to be a much newer printer and does have Apple AirPrint. Mine doesn't show Airprint but does show IPP (as well as FTP, LPD etc.) poc ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Configuring a printer with DNS-SD
On Wed, 2022-06-22 at 14:01 -0300, George N. White III wrote: > AirPrint was introduced in 2011 to support iPads. > https://openprinting.github.io/driverless/01-standards-and-their-pdls/ > summarizes the differences in the various Driverless Printing > implementations. PDF is supported across the board, but there are > several raster formats and also PDFm which is viewable with PDF > viewers, but tailored for the capabilities of specific printer > models. I have a HP printer in that boat. It proudly proclaims direct PDF printing (send it a PDF file, or plug a USB into the front with a PDF on it). But after a lot of digging around you find that it only supports a special PDF created by their driver program, no other PDF files are supported. -- uname -rsvp Linux 3.10.0-1160.66.1.el7.x86_64 #1 SMP Wed May 18 16:02:34 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates)
On 6/22/22 07:59, Ranjan Maitra wrote: On Wed Jun22'22 11:40:10AM, George N. White III wrote: From: "George N. White III" Date: Wed, 22 Jun 2022 11:40:10 -0300 To: Community support for Fedora users Reply-To: Community support for Fedora users Subject: Re: fully updated F36 Dell XPS 13 no longer comes back from hibernate (post Thursday updates) On Wed, Jun 22, 2022 at 8:43 AM Ranjan Maitra wrote: Dear friends, I have a fully updated F36 Dell XPS 13 that has been updated nightly (and upgraded when appropriate) using dnf on a cron job for the past few years. Sadly, after last Thursday's updates, the machine goes down fine (with the usual systemctl hibernate), but does not come back up. I am a little confused what changed last Thursday, but I was wondering if anyone had any suggestions as to how I may diagnose and fix this problem. Have you looked at messages using journalctl? So, I don't really know what to look for, but I tried: journalctl | grep hibernate and got: Jun 22 06:06:49 localhost.localdomain systemd[1]: Created slice system-systemd\x2dhibernate\x2dresume.slice - Slice /system/systemd-hibernate-resume. Jun 22 06:06:50 localhost.localdomain systemd[1]: Starting systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service - Resume from hibernation using device /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605... Jun 22 06:06:50 localhost.localdomain systemd-hibernate-resume[390]: Could not resume from '/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605' (259:4). Jun 22 06:06:50 localhost.localdomain systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service: Deactivated successfully. Jun 22 06:06:50 localhost.localdomain systemd[1]: Finished systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service - Resume from hibernation using device /dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605. Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Note however, that this is after the machine was asked to reboot since the system never came back from hibernate so I am not completely sure it has the information from not coming back. What do you mean "doesn't come back up"? Usually the problem is that you get a normal boot instead of a resume. That would correspond to the logs that you're showing there. The other thing to check is the last bit of the logs from the previous boot. I also suggest looking at some lines in that area that might not have been caught by the grep. Maybe there is a reason listed for why the resume failed. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
