On 2020-11-01 14:13, Samuel Sieb wrote:
On 10/31/20 11:53 PM, ToddAndMargo via users wrote:
# modprobe -r lp
# modprobe -r parport_pc
# modprobe parport_pc
# modprobe lp
# echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
But still no lp0 showing in CUPS or Printer Admin (notice
I used t
On Sun, Nov 1, 2020 at 7:00 PM Chris Murphy wrote:
> ddrescue by default reads the whole file (via the mounted file system,
> not pointing it to raw sectors), but with truncated bad 4KiB blocks.
> The bad blocks are simply missing, there is no gap filled with zeros
> or some other pattern unless
On Sun, Nov 1, 2020 at 6:51 AM John Mellor wrote:
>
> On 2020-10-31 10:46 p.m., Tim via users wrote:
> > On Sat, 2020-10-31 at 16:11 +, lancelasset...@gmail.com wrote:
> >> Will NFS tell you data has been corrupted during the transfer and
> >> write process?
> > Does any filing system? In gen
On 2020-11-01 15:41, ToddAndMargo via users wrote:
On 2020-11-01 14:18, Samuel Sieb wrote:
That doesn't explain why there's no 32->33 in
the list, but it worked anyway.
> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
Or why the date and time were for the failed upgrade
An
On 2020-11-01 14:18, Samuel Sieb wrote:
That doesn't explain why there's no 32->33 in
the list, but it worked anyway.
> 8 / bad1ef89617e45658d9cede422f8f944: 2020-11-01 12:07:52 31→32
Or why the date and time were for the failed upgrade
___
users mai
On 02/11/2020 06:18, Samuel Sieb wrote:
On 11/1/20 1:49 PM, Ed Greshko wrote:
On 02/11/2020 05:44, ToddAndMargo via users wrote:
On 2020-11-01 13:41, Ed Greshko wrote:
On 02/11/2020 04:19, ToddAndMargo via users wrote:
# dnf system-upgrade log
The following boots appear to contain upgrade log
On 11/1/20 1:49 PM, Ed Greshko wrote:
On 02/11/2020 05:44, ToddAndMargo via users wrote:
On 2020-11-01 13:41, Ed Greshko wrote:
On 02/11/2020 04:19, ToddAndMargo via users wrote:
# dnf system-upgrade log
The following boots appear to contain upgrade logs:
1 / 1426e9395eb4423ab17c92394d5a9cac:
On 10/31/20 11:53 PM, ToddAndMargo via users wrote:
# modprobe -r lp
# modprobe -r parport_pc
# modprobe parport_pc
# modprobe lp
# echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
But still no lp0 showing in CUPS or Printer Admin (notice
I used the Linux term for it!)
After running th
On 2020-11-01 13:49, Ed Greshko wrote:
On 02/11/2020 05:44, ToddAndMargo via users wrote:
On 2020-11-01 13:41, Ed Greshko wrote:
On 02/11/2020 04:19, ToddAndMargo via users wrote:
# dnf system-upgrade log
The following boots appear to contain upgrade logs:
1 / 1426e9395eb4423ab17c92394d5a9cac:
On 02/11/2020 05:44, ToddAndMargo via users wrote:
On 2020-11-01 13:41, Ed Greshko wrote:
On 02/11/2020 04:19, ToddAndMargo via users wrote:
# dnf system-upgrade log
The following boots appear to contain upgrade logs:
1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
2 / a7b5ab0d7
On 2020-11-01 13:41, Ed Greshko wrote:
On 02/11/2020 04:19, ToddAndMargo via users wrote:
# dnf system-upgrade log
The following boots appear to contain upgrade logs:
1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
3
On Sun, Nov 1, 2020 at 3:43 PM ToddAndMargo via users <
users@lists.fedoraproject.org> wrote:
> On 2020-11-01 12:39, Doug McGarrett wrote:
> >>> I don't think it's originally a windows term. It's actually "LPT
> >>> #1", similar to the following "Serial Port #1". "LPT" stands for
> >>> "line pri
On 02/11/2020 04:19, ToddAndMargo via users wrote:
# dnf system-upgrade log
The following boots appear to contain upgrade logs:
1 / 1426e9395eb4423ab17c92394d5a9cac: 2018-04-06 22:41:13 27→28
2 / a7b5ab0d772d49f5bc4bece971e3e34f: 2018-09-28 11:26:59 28→29
3 / af5f137e166b43f29a0b569932d59c5b: 201
On 2020-11-01 13:39, Samuel Sieb wrote:
On 11/1/20 1:34 PM, ToddAndMargo via users wrote:
Solved:
I did a
# dnf system-upgrade clean
# dnf --refresh upgrade
and started over.
It does ask if you fully updated before starting. :-)
I generally update at least all of dnf and system
On 11/1/20 1:34 PM, ToddAndMargo via users wrote:
Solved:
I did a
# dnf system-upgrade clean
# dnf --refresh upgrade
and started over.
It does ask if you fully updated before starting. :-)
I generally update at least all of dnf and systemd before doing a
system-upgrade and I ha
On 2020-11-01 12:19, ToddAndMargo via users wrote:
On 2020-10-31 04:24, Ed Greshko wrote:
dnf system-upgrade log
# df -kPT
Filesystem Type 1024-blocks Used Available Capacity Mounted on
devtmpfs devtmpfs 995088 0 995088 0% /dev
tmpfs tmpfs
On 2020-11-01 12:39, Doug McGarrett wrote:
I don't think it's originally a windows term. It's actually "LPT
#1", similar to the following "Serial Port #1". "LPT" stands for
"line printer" for those of us old enough to remember when printers
could only do lines of text.
I wonder what it was
On 11/1/20 2:45 PM, ToddAndMargo via users wrote:
On 2020-11-01 00:08, Samuel Sieb wrote:
On 10/31/20 11:50 PM, ToddAndMargo via users wrote:
On 2020-10-31 23:36, Samuel Sieb wrote:
If I do the modprobe will above, lpt1 (lp0) shows up in
both printer admin and CUPS. Otherwise not.
Why do
On 2020-10-31 04:24, Ed Greshko wrote:
dnf system-upgrade log
# df -kPT
Filesystem Type 1024-blocksUsed Available Capacity Mounted on
devtmpfs devtmpfs 995088 0995088 0% /dev
tmpfs tmpfs1013564 0 1013564 0% /dev/shm
tmpfs
On 2020-11-01 00:08, Samuel Sieb wrote:
On 10/31/20 11:53 PM, ToddAndMargo via users wrote:
On 2020-10-31 23:36, Samuel Sieb wrote:
# echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
bash: /sys/bus/pci/drivers/parport_pc/new_id: No such file or directory
Was the "parport_pc" driver loa
On 2020-11-01 00:08, Samuel Sieb wrote:
On 10/31/20 11:50 PM, ToddAndMargo via users wrote:
On 2020-10-31 23:36, Samuel Sieb wrote:
If I do the modprobe will above, lpt1 (lp0) shows up in
both printer admin and CUPS. Otherwise not.
Why do you say "lpt1"? I have 4 lp[0-3] devices in /dev, bu
On Sun, 1 Nov 2020 at 02:54, ToddAndMargo via users <
users@lists.fedoraproject.org> wrote:
> On 2020-10-31 23:36, Samuel Sieb wrote:
> >> # echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
> >> bash: /sys/bus/pci/drivers/parport_pc/new_id: No such file or directory
> >
> > Was the "parport
That worked! Thanks!
___
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
On 2020-10-31 10:46 p.m., Tim via users wrote:
On Sat, 2020-10-31 at 16:11 +, lancelasset...@gmail.com wrote:
Will NFS tell you data has been corrupted during the transfer and
write process?
Does any filing system? In general, writes to storage are assumed to
have worked unless something t
On 10/31/20 11:50 PM, ToddAndMargo via users wrote:
On 2020-10-31 23:36, Samuel Sieb wrote:
If I do the modprobe will above, lpt1 (lp0) shows up in
both printer admin and CUPS. Otherwise not.
Why do you say "lpt1"? I have 4 lp[0-3] devices in /dev, but I have
no actual parallel port hardwar
On 10/31/20 11:53 PM, ToddAndMargo via users wrote:
On 2020-10-31 23:36, Samuel Sieb wrote:
# echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
bash: /sys/bus/pci/drivers/parport_pc/new_id: No such file or directory
Was the "parport_pc" driver loaded when you tried that? Try loading
th
26 matches
Mail list logo
