F33 just pretends to print
by Michael Hennebry
I have a Brother HL-L2360DL that I'd thought I'd finally managed to install.
I had to go to the Brother website to get a script to run.
The instructions for the script had the wrong name for it.
None of the default options for Brother printers came close.
The CUPS adminstration "web" pages say the right things:
Idle, accepting jobs, two completed jobs.
Nothing actually prints. Not even a test page.
The printer never comes out of deep sleep.
How do I fix this?
It worked with Centos 7, but I do not know what I did.
In my experience, there is no such thing as a small problem when it comes to
installing a printer on Linux:
Either it just works or it requires a mighty effort.
I am getting mighty tired of mighty efforts.
BTW how do I change the default from single- to double-sided?
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
-- someeecards
1 month, 1 week
cisco ise
by david richyad
cisco ise helps safeguard your business. It lets you control access throughout your network, see the user and device details, and stop/contain any threats. You can also use it to enforce security policies throughout your network. As a result, it helps prevent any technical issues and strengthens your cybersecurity measures. In short, you can manage your network security with more ease. Everything can be handled in one place, as opposed to needing multiple different applications open at once.
https://www.fieldengineer.com/blogs/cisco-ise-deployment-guide
3 months, 1 week
Improper shutdown, now Kernel panic.
by murph nj
Hi all:
I've got an odd problem that I was hoping for some help on.
The laptop was previously working fine, I am running F30, updated regularly.
I've got an Acer laptop that has been shutting down suddenly. (I
suspect a bad battery, working on that.)
After a sudden shutdown last night, I now get a kernel panic on boot
right after "Starting Switch Root..."
I was able to boot from a USB stick, and was able to read the journal,
but I didn't see anything obvious to help.
I was able to get all of my data off of the (encrypted) disks, so
that's not a problem, but I don't want to just give up, and wash and
reload too quickly.
Any suggestions?
Thanks,
--murph
3 months, 4 weeks
Fedora 34 does not install on laptop, screen freezes
by Javier Perez
Hi
I have a very old Acer 3050 laptop
The graphics card is Advanced Micro Devices [AMD/ATI] RS482M [Mobility
Radeon Xpress 200]
Initially it starts well , but after a few minutes the screen freezes hard
with a white wash
Installation does not complete.
How can I finish installation and troubleshoot this?
Is there a way to install command line?
--
------------------------------
/\_/\
|O O| pepebuho(a)gmail.com
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
7 months, 4 weeks
Monitor shuts off randomly - possibly sync problem?
by Alex
Hi,
I have fedora34 installed on my desktop with three monitors; two of
them are older 27" Samsungs, and the third is a new 34" Samsung
S34J55x. Occasionally, the 34" seems to shut off for a second, then
comes back on and continues to work normally.
Has anyone seen this type of behavior before? The other two monitors
have never done this. However, when it happens, the other two seem to
follow with shutting off for a second. It always seems to be driven by
the new 34" monitor.
The problem is that, when this happens, all of the windows on the 34"
monitor move to the 27" monitor on the right once the monitors turn on
again.
This is not a power problem, as the entire computer is connected to
the same power strip, backed by a 2200W UPS.
My video card is also new - it's a Radeon RX570. All three monitors
are connected via displayport.
I do see lines in my Xorg.0.log file periodically along the lines off
the following:
[992023.990] (EE) event3 - Logitech Gaming Mouse G900: client bug:
event processing lagging behind by 16ms, your system is too slow
[994674.766] (EE) event6 - Logitech Gaming Keyboard G910: client bug:
event processing lagging behind by 29ms, your system is too slow
But are they related? Is this also an issue? The system itself is a
12-core with 64GB of RAM, so certainly not slow.
Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Please let me know what more I can do to troubleshoot this before
contacting Samsung directly.
8 months
NFS mount
by Dave Close
I'm trying to setup an NFS mount to an older NAS device. The client
is Fedora 34, the NAS is a Buffalo Linkstation. I have access to the
NAS via SSH and I can successfully mount it using CIFS and SSHFS. Of
course, CIFS loses some file attributes and SSHFS seems slow and
doesn't see the filesystem usage properly. So I'd prefer NFS but it
keeps failing. I've even tried with my firewall disabled but no luck.
The NAS only works with NFS v2. It's NFS is a client-side application
as there is no NFS built into its kernel. But it is nothing new; the
app has been running successfully for many folks for years.
All the necessary ports seem to be open.
# nmap -sU -p2049,111 nas1
PORT STATE SERVICE
111/udp open rpcbind
2049/udp open nfs
# nmap -sT -p2049,111 nas1
PORT STATE SERVICE
111/tcp open rpcbind
2049/tcp open nfs
I can access the NAS with rpcinfo and showmount.
# showmount -e nas1
Export list for nas1:
/mnt/array1/share client.compata.com
# rpcinfo -p nas1
program vers proto port service
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
100005 1 udp 726 mountd
100005 2 udp 726 mountd
100005 1 tcp 729 mountd
100005 2 tcp 729 mountd
But mount fails.
# mount -v -o vers=2 -t nfs nas1:/mnt/array1/share /nas1
mount.nfs: timeout set for Sat Aug 28 17:52:01 2021
mount.nfs: trying text-based options 'vers=2,addr=192.168.44.20'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: trying 192.168.44.20 prog 100003 vers 2 prot TCP port 2049
mount.nfs: prog 100005, trying vers=1, prot=17
mount.nfs: trying 192.168.44.20 prog 100005 vers 1 prot UDP port 726
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
# mount -v -o udp -o vers=2 -t nfs nas1:/mnt/array1/share /nas1
mount.nfs: timeout set for Sat Aug 28 17:53:43 2021
mount.nfs: trying text-based options 'udp,vers=2,addr=192.168.44.20'
mount.nfs: prog 100003, trying vers=2, prot=17
mount.nfs: trying 192.168.44.20 prog 100003 vers 2 prot UDP port 2049
mount.nfs: prog 100005, trying vers=1, prot=17
mount.nfs: trying 192.168.44.20 prog 100005 vers 1 prot UDP port 726
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
I have tcpdump captures from both ends and I don't see anything obviously
wrong. (But then I'm not sure just what I ought to see there.) I do see
the portmap calls and the results seem ok. Each is followed by a null
call and a null reply, again nothing obviously wrong. I don't understand
why the mount proceeds to use V1 for prog 100005 (mount) without any
indication of a problem with the V2 attempt for NFS. But forcing V2 for
both doesn't help.
# mount -v -o nfsvers=2 -o mountvers=2 -o mountproto=tcp -t nfs
nas1:/mnt/array1/share /nas1
mount.nfs: timeout set for Sat Aug 28 18:28:37 2021
mount.nfs: trying text-based options 'nfsvers=2,mountvers=2,
mountproto=tcp,addr=192.168.44.20,mountaddr=192.168.44.20'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: trying 192.168.44.20 prog 100003 vers 2 prot TCP port 2049
mount.nfs: prog 100005, trying vers=2, prot=6
mount.nfs: trying 192.168.44.20 prog 100005 vers 2 prot TCP port 729
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
I can't find anything relevant in any system log. The final message,
"Protocol not supported", doesn't clearly indicate which protocol --
I presume mount(2) -- nor give any clue to a remedy. But if I force
v3 for mount, I get a version mismatch.
--
Dave Close, Compata, Irvine CA +1 714 434 7359
dave(a)compata.com dhclose(a)alumni.caltech.edu
"Computers are useless. They can only give you answers."
-- Pablo Picasso
8 months, 2 weeks
rkhunter warning
by François Patte
Bonjour,
Since I upgraded to f34, rkhunter is warning me with this file:
Warning: Hidden file found: /usr/share/man/fr/man1/..1.gz: symbolic link
to builtins.1.gz
Asking rpm -qf /usr/share/man/fr/man1/..1.gz, it returns that this file
belongs to the man-pages-fr package.
rkhunter --propupd does not change anything, every day rkhunter sends me
a warning mail...
Which of these two must be believed: rkhunter or rpm -qf?
Thank you.
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
8 months, 2 weeks
Weird keyboard problem
by Frederic Muller
Hi!
I'm using a Logitech G512 (wired) keyboard. Usually works perfectly in
the morning and little by little I get stuck with 'some' keys. I say
some because it's not regular. I press them and they don't seem to
work.. then work "if I press harder" ... or later?
When using the native laptop keyboard, or another BT Logitech K480
keyboard the problem is not there.
I am really hesitating to bring it back as I've noticed when in the
browser or some applications highlighting the blinking character cursor,
that it actually stops blinking at times, and then suddenly either gets
3 keys typed in a row, or just a 'huge' time delay between the moment I
typed that key and the moment it appears.
Are there any reliable ways to troubleshoot and pinpoint where the issue
could be coming from?
Thank you.
Fred
8 months, 3 weeks
