Thin pink LHS border
by Joe Feely
I noticed a thin pink border, left hand side edge of display about half a
millimeter wide.
It's there when using latest kernel, Kernel Linux 4.0.5-300.fc22.x86_64
x86_64, but not with prior kernel versions.
Doesn't show on screenshots (even of the whole screen).
Also shows if I Ctrl Alt F6 (or any other) virtual screen.
My setup is; AMD A4-5300 APU with Radeon(tm) HD Graphics × 2 and a Samsung
SyncMaster S22B300 monitor (connected with a HDMI cable).
This isn't a problem for me, but would seem to indicate something isn't
quite as intended.
I'm not sure who would be best to inform of this, this list or elsewhere. I
expect it will disappear with the next kernel update.
Joe
8 years, 10 months
[OT] HP Officejet Pro 8620
by g
greetings.
anyone on this list using an HP Officejet Pro 8620?
question regarding this exact model.
tia.
--
peace out.
-+-
If Bill Gates got a dime for every time Windows crashes...
...oh, wait. He does. THAT explains it!
-+-
in a world with out fences, who needs gates.
-+-
CentOS GNU/Linux 6.6
tc,hago.
g
.
8 years, 10 months
Fedora 22 - syslog rotating but new old files being updated!
by Philip Rhoades
People,
After I move from F21 to F22 (fresh install) and changing the frequency
of logrotates to "daily", I notice that the new syslog logs (ie those
without the date appended) are not being changed and the files from the
date of the last reboot are the ones that continue to be updated! eg:
eg:
-rw-r--r-- 1 root root 0 Jun 26 03:33 /var/log/cron
-rw-r--r--. 1 root root 35220 May 16 18:01 /var/log/cron-20150514
-rw-r--r--. 1 root root 6006 Jun 17 18:10 /var/log/cron-20150617
-rw-r--r-- 1 root root 275974 Jun 21 03:47 /var/log/cron-20150621
-rw-r--r-- 1 root root 725768 Jun 26 15:31 /var/log/cron-20150624
-rw-r--r-- 1 root root 0 Jun 24 03:15 /var/log/cron-20150625
-rw-r--r-- 1 root root 0 Jun 25 03:27 /var/log/cron-20150626
-rw------- 1 root root 0 Jun 26 03:33 /var/log/maillog
-rw-------. 1 root root 0 Apr 16 09:15 /var/log/maillog-20150514
-rw-------. 1 root root 0 May 14 14:45 /var/log/maillog-20150617
-rw------- 1 root root 605403 Jun 21 03:34 /var/log/maillog-20150621
-rw------- 1 root root 1844346 Jun 26 15:31 /var/log/maillog-20150624
-rw------- 1 root root 0 Jun 24 03:15 /var/log/maillog-20150625
-rw------- 1 root root 0 Jun 25 03:27 /var/log/maillog-20150626
-rw------- 1 root root 553261 Jun 21 01:31 /var/log/maillog.t
-rw------- 1 root root 0 Jun 26 03:33 /var/log/messages
-rw-------. 1 root root 2060072 May 16 18:02 /var/log/messages-20150514
-rw-------. 1 root root 1830620 Jun 17 18:13 /var/log/messages-20150617
-rw------- 1 root root 4738203 Jun 21 03:47 /var/log/messages-20150621
-rw------- 1 root root 3275905 Jun 26 15:30 /var/log/messages-20150624
-rw------- 1 root root 0 Jun 24 03:15 /var/log/messages-20150625
-rw------- 1 root root 0 Jun 25 03:27 /var/log/messages-20150626
-rw------- 1 root root 0 Jun 26 03:33 /var/log/secure
-rw-------. 1 root root 16180 May 16 18:01 /var/log/secure-20150514
-rw-------. 1 root root 8410 Jun 17 18:13 /var/log/secure-20150617
-rw------- 1 root root 127116 Jun 21 03:47 /var/log/secure-20150621
-rw------- 1 root root 118816 Jun 26 00:14 /var/log/secure-20150624
-rw------- 1 root root 0 Jun 24 03:15 /var/log/secure-20150625
-rw------- 1 root root 0 Jun 25 03:27 /var/log/secure-20150626
-rw------- 1 root root 0 Jun 26 03:33 /var/log/spooler
-rw-------. 1 root root 0 Apr 16 09:15 /var/log/spooler-20150514
-rw-------. 1 root root 0 May 14 14:45 /var/log/spooler-20150617
-rw------- 1 root root 0 Jun 17 18:10 /var/log/spooler-20150621
-rw------- 1 root root 0 Jun 21 03:44 /var/log/spooler-20150624
-rw------- 1 root root 0 Jun 24 03:15 /var/log/spooler-20150625
-rw------- 1 root root 0 Jun 25 03:27 /var/log/spooler-20150626
Any suggestions about why this is happening?
Thanks,
Phil.
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au
8 years, 10 months
F22 rsyslogd writes to a dated file name...
by dcw
The following is a current list of the messages file in /var/log:
-rw-------. 1 root root 104339300 Jun 20 10:27 messages-20150614
-rw------- 1 root root 0 Jun 22 03:30 messages
-rw------- 1 root root 36077670 Jun 25 20:25 messages-20150622
The other log files are treated similarly.
-rw-------. 1 root root 9446999 Jun 20 10:27 secure-20150614
-rw------- 1 root root 0 Jun 22 03:30 secure
-rw------- 1 root root 1493733 Jun 25 20:38 secure-20150622
I have bot been able to find out why the messages file is zero length or
why the messages file that is being written to is a date identified
file, in this case messages-20150622.
Is there a config setting to change this?
David
8 years, 10 months
secure erase drive errors
by JD
during secure erase, I am seeing these continuous rolling errors
in /var/log/messages
Jun 23 16:00:37 localhost kernel: ata6.00: error: { ABRT }
Jun 23 16:00:37 localhost kernel: ata6.00: configured for UDMA/100
Jun 23 16:00:37 localhost kernel: ata6: EH complete
Jun 23 16:00:37 localhost kernel: ata6.00: exception Emask 0x0 SAct 0x0
SErr 0x0 action 0x0
Jun 23 16:00:37 localhost kernel: ata6.00: irq_stat 0x00060002, device
error via D2H FIS
Jun 23 16:00:37 localhost kernel: ata6.00: failed command: WRITE DMA EXT
Jun 23 16:00:37 localhost kernel: ata6.00: cmd
35/00:00:b0:b5:47/00:04:02:00:00/e0 tag 0 dma 524288 out
res 51/04:00:b0:b5:47/00:04:02:00:00/e0 Emask 0x1 (device error)
Jun 23 16:00:37 localhost kernel: ata6.00: status: { DRDY ERR }
Jun 23 16:00:37 localhost kernel: ata6.00: error: { ABRT }
Jun 23 16:00:37 localhost kernel: ata6.00: configured for UDMA/100
Jun 23 16:00:37 localhost kernel: sd 6:0:0:0: [sdc]
Jun 23 16:00:37 localhost kernel: Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Jun 23 16:00:37 localhost kernel: sd 6:0:0:0: [sdc]
Jun 23 16:00:37 localhost kernel: Sense Key : Aborted Command [current]
[descriptor]
Jun 23 16:00:37 localhost kernel: Descriptor sense data with sense
descriptors (in hex):
Jun 23 16:00:37 localhost kernel: 72 0b 00 00 00 00 00 0c 00 0a
80 00 00 00 00 00
Jun 23 16:00:37 localhost kernel: 02 47 b5 b0
Jun 23 16:00:37 localhost kernel: sd 6:0:0:0: [sdc]
Jun 23 16:00:37 localhost kernel: Add. Sense: No additional sense
information
Jun 23 16:00:37 localhost kernel: sd 6:0:0:0: [sdc] CDB:
Jun 23 16:00:37 localhost kernel: Write(10): 2a 00 02 47 b5 b0 00 04 00 00
Jun 23 16:00:37 localhost kernel: end_request: I/O error, dev sdc,
sector 38254000
Jun 23 16:00:37 localhost kernel: ata6: EH complete
Jun 23 16:00:37 localhost kernel: ata6.00: exception Emask 0x0 SAct 0x0
SErr 0x0 action 0x0
Jun 23 16:00:37 localhost kernel: ata6.00: irq_stat 0x00060002, device
error via D2H FIS
Jun 23 16:00:37 localhost kernel: ata6.00: failed command: WRITE DMA EXT
Jun 23 16:00:37 localhost kernel: ata6.00: cmd
35/00:00:b0:b9:47/00:04:02:00:00/e0 tag 0 dma 524288 out
res 51/04:00:b0:b9:47/00:04:02:00:00/e0 Emask 0x1 (device error)
Jun 23 16:00:37 localhost kernel: ata6.00: status: { DRDY ERR }
Jun 23 16:00:37 localhost kernel: ata6.00: error: { ABRT }
So, then, the drive is DeD dead ????
8 years, 10 months
install f22 into btrfs subvolume won't boot
by Neal Becker
I tried it. It was not easy to figure out how to use anaconda gui to setup
install into a subvolume - but I got it done. I now have 3 subvolumes:
sudo btrfs subvolume list /
[sudo] password for nbecker:
ID 256 gen 1818627 top level 5 path home
ID 259 gen 1818478 top level 5 path root
ID 487 gen 1818625 top level 5 path root00
But if I try to boot with 1st grub entry, I get:
dracut-initqueue warning could not boot
starting dracut emergency shell
If I try to boot off the grub entry labeled 'rescue', it boots OK.
dracut says something about fixing initramfs.
--
Those who fail to understand recursion are doomed to repeat it
8 years, 10 months
f22 fedup with btrfs snapshot?
by Neal Becker
I have f21 installed on btrfs. I wonder what's a good procedure to use
fedup along with btrfs snapshot, so that I can backout to f21 if I don't
like it?
Right now I have:
sudo btrfs sub list /
ID 257 gen 67442 top level 5 path root
ID 318 gen 67442 top level 5 path home
-- /etc/fstab
UUID=93c586fa-6d86-4148-a528-e61e644db0c8 / btrfs
subvol=root 0 0
UUID=93c586fa-6d86-4148-a528-e61e644db0c8 /home btrfs
subvol=home 0 0
UUID=e907e423-4282-4ca9-a873-b544d17d34b9 /boot ext4
defaults 1 2
UUID=b0cde31d-3694-4b98-ad90-e28c7d35a869 swap swap
defaults 0 0
--
Those who fail to understand recursion are doomed to repeat it
8 years, 10 months
BTRFS Question
by Javier Perez
Hi
I am just learning about btrfs on my home system.
How do I know what kind of options where used to create a BTRFS filesystem?
I installed F21 from scratch and I created a BTRFS filesystem on a HDD.
I think I created it with the "single" option.
Now I read that that is dangerous, I should have created it as one of the
raids if I want to have data redundancy and protection vs bit rot (which is
what I was looking forward to).
How can I verify it? Also, If I want to change it, can I do it IN-PLACE or
do I have to reformat/recreate the filesystem?
Thanks for whatever help/illumination you might provide. I am catching up
on btrfs, but I am not there yet.
JP
--
------------------------------
/\_/\
|O O| pepebuho(a)gmail.com
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
8 years, 10 months
RFC: Multiboot Guide
by Pete Travis
Hi All,
There's regularly questions here, and around the internet (ie ask.fp.o)
about dual booting Fedora with Windows systems, or other Linux systems,
or OSX. To address the more common questions, the Fedora Docs team has
written a Multiboot Guide[1].
The guide is intended to help set up a multiboot system in a functional
way, or to help get to a more functional state if needed. For the most
part, we've tried not to make it intimidatingly complex, and I hope that
it will aid you in most multibooting situations.
As with all of Fedora's documentation, feedback from readers is crucial
to ensuring the quality of the work. Please use the guide, and if you
find questions unanswered or answers unclear, reply here or use the
'multiboot-guide' component of the Fedora Documentation product on
https://bugzilla.redhat.com .
[1]
http://docs.fedoraproject.org/en-US/Fedora/22/html/Multiboot_Guide/index....
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
8 years, 10 months
No IP 4 address setup no loopback interface
by Bruno Wolff III
I am still investigating this, but I have an f22 laptop that is only
getting an IP6 address set up on the loopback interface. I noticed this
because I run a local resolver on 127.0.0.1 and connections to it stopped
working over night (after a reboot). The was a NetworkManager update before
the reboot where things stopped working, so that seems to be the mostly
change that triggered the problem. I'll be able to reboot another f22
machine tomorrow and also should have time to try downgrading
NetworkManager to confirm whether or not that update is really causing the
problem. (And file a bug and give negative karma if appropriate.)
8 years, 10 months
