Screen Blacking out Reliably After 15 Seconds Inactivity
by Tim Evans
F23: Linux harrier 4.4.7-300.fc23.x86_64 running on a Lenovo T530 with
Intel graphics:
lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
processor Graphics Controller (rev 09)
xorg-x11-server-Xwayland-1.18.3-1.fc23.x86_64
Screen is blacking out reliably after 15 second of inactivity. Touching
the mousepad lights it back up, but often with a different app on screen.
Does not occur in Windows 10, so would not seem to be hardware-related.
Presumably, this is an X thing.
Anyone else seeing anything like this?
--
Tim Evans |5 Chestnut Court
443-394-3864 |Owings Mills, MD 21117
8 years, 1 month
F23 dracut can't find disk
by CLOSE Dave
I have five machines which were fresh-installed with F23 back in
February and all have been booted successfully a few times since. Today,
booting of all of them fails in exactly the same way: dracut says it
can't find the disk filesystems. The kernel boots as it should, and of
course that comes from the disk, but then dracut comes along and says it
can't find any of the filesystems. Not the root or home filesystems
which are on LVM or the boot filesystem on a primary disk partition.
Everything on the disk is ok. I've checked by booting Anaconda from a
thumb drive and mounting manually. Anaconda troubleshooting mode says it
can't find the filesystems either ("you have no Linux partitions"), but
running vgchange -ay and a few mounts gets a proper chroot image.
There must be something that is causing both dracut and Anaconda to fail
to find the filesystems. I've tried following the instructions on
<https://fedoraproject.org/wiki/How_to_debug_Dracut_problems>, but that
isn't helping:
dracut:/# parted /dev/sda -s p
sh: parted: command not found
dracut:/# lvm vgscan
File descriptor 98 (/dev/console) leaked on lvm invocation. Parent PID
2679: sh
File descriptor 99 (/dev/console) leaked on lvm invocation. Parent PID
2679: sh
Reading all physical volumes. This may take a while...
dracut:/# lvm vgchange -ay
File descriptor 98 (/dev/console) leaked on lvm invocation. Parent PID
2679: sh
File descriptor 99 (/dev/console) leaked on lvm invocation. Parent PID
2679: sh
dracut:/# blkid
dracut:/#
Note that when booted from the thumb drive, vgchange finds the LVM
volumes just fine.
--
Dave Close
8 years, 1 month
Kickstart Help
by Alex Thomas
Looking for help in building a .ks file for my laptop. I have looked at the
anaconda-ks.cfg file you are given when installing Fedora 23 Workstation,
and it seams like all of the disk partitioning information is missing. Is
this file a condensed version with some shortcuts? Is there another file I
should be looking at as I teach myself about kickstart?
Specifically I want to build a ks file that for partitioning I can set up
so it does full disk encryption with / = ext4 and /home = xfs .
Thank you,
Alex Thomas
8 years, 1 month
Has anyone configured Fedora to use a joystick as a mouse, or know
of a tutorial?
by stan
The subject says it. I find instructions on the web, but they seem
to be more about dual use with gaming, and for more modern hardware. I
just want to use an old joystick as an ergonomic mouse replacement,
kind of like a weird trackball. And if I have to, I'll muck about and
muddle through to try to get it working. But if someone can point to a
tutorial that specifically targets Fedora, that would be great.
I've found xboxdrv, antimicro, and qjoydrv so far, though the last
seems to be obsolete.
If you know that this doesn't work in the latest Fedoras, that would be
useful to know also.
https://steamcommunity.com/app/221410/discussions/0/558748653738497361/#p2
http://askubuntu.com/questions/114895/how-can-a-gamepad-control-the-mouse
8 years, 1 month
filesystem error
by Jeffrey Ross
I have the following error reported in my logs, I've had it for quite
some time and through several reboots
EXT4-fs (md2): error count: 1
EXT4-fs (md2): initial error at 1452554514: ext4_lookup:1343: inode 1308162
EXT4-fs (md2): last error at 1452554514: ext4_lookup:1343: inode 1308162
md2 is my root partition, I ran "find / -mount -inum 1308162" find
didn't return any value.
How can I track down this error, identify what file it refers to and
clear the error out? if it matters, its an older Fedora system (16 to
be exact)
Thanks, Jeff
8 years, 1 month
Cant read superblocks
by Weiner, Michael
I have a Dell PowerEdge R910 with a PERC 700 controller that has a virtual drive configured as a RAID 5 with 15 disks in it. We're running CentOS 5.10 at the moment, and I created a 15Tb ext3 filesystem on that RAID group (set this up a few years back) that has been running fine up until yesterday. I had the opportunity to add another PERC H810 controller along with a PowerVault MD1200 to add more space (44Tb as XFS), but when we went to turn the server back on, we noticed one of the disks in the RAID group had apparently failed. I didn't think much of it at the time, as it was a RAID 5, but when the server came up and I tried to mount it, I received the following error:
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
I tried to get a listing of backup superblocks by doing the following:
[root@raos_apps01 ~]# mke2fs -b 8192 -n /dev/sdb1
Warning: blocksize 8192 not usable on most systems.
mke2fs 1.39 (29-May-2006)
mke2fs: 8192-byte blocks too big for system (max 4096)
Proceed anyway? (y,n) y
Warning: 8192-byte blocks too big for system (max 4096), forced to continue
Filesystem label=
OS type: Linux
Block size=8192 (log=3)
Fragment size=8192 (log=3)
1828894848 inodes, 1830420355 blocks
91521017 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4311218176
27934 block groups
65528 blocks per group, 65528 fragments per group
65472 inodes per group
Superblock backups stored on blocks:
65528, 196584, 327640, 458696, 589752, 1638200, 1769256, 3210872,
5307768, 8191000, 15923304, 22476104, 40955000, 47769912, 143309736,
157332728, 204775000, 429929208, 1023875000, 1101329096, 1289787624
But I am unable to actually use any of these, as they all end up giving the same error:
[root@raos_apps01 ~]# e2fsck -b 65528 /dev/sdb1
e2fsck 1.39 (29-May-2006)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
any idea how I can get the FS back? I ordered another drive to replace the failed on thinking that *might* be part of the problem, so I will have to wait and see on that, but I SHOULD be able to mount it, but I am not able to.
Thanks in advance
Michael
===================================
Please consider the environment before printing this e-mail
Cleveland Clinic is ranked as one of the top hospitals in America by U.S.News & World Report (2015).
Visit us online at http://www.clevelandclinic.org for a complete listing of our services, staff and locations.
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy.
Thank you.
8 years, 1 month
mate autologin
by Pasha R
Hi all,
I'm using Fedora 23 with mate and trying to setup autologin. I edited a
file /etc/lightdm/lightdm.conf and uncommented lines
autologin-user=pasha
autologin-user-timeout=0
but after boot, I still get a login window.
I also tried to uncomment
pam-autologin-service=lightdm-autologin
then after boot, I got login window with message "Unable to authenticate"
over it.
Any ideas where else to look?
Thanks.
8 years, 1 month
Bitmap font resizer (or: good classic-style terminal font)?
by Chris Adams
I guess I've been using xterm forever, and I'm really used to the
classic X "fixed" font (aka "6x13"). However, as display DPI has gone
up, it has gotten a little harder to see. I got a new notebook today
with a 14" 2560x1440 display (210 DPI), and "fixed" isn't going to work
any more.
Is there an easy tool that could take the old bitmap font and double the
size? That would probably be about right on this new display. In a
perfect world, somebody would create a TrueType vector font with the
same outline, but that's beyond my ability.
Alternately: is there a good vector/scalable font that has a similar
look?
--
Chris Adams <linux(a)cmadams.net>
8 years, 1 month
dnf - deprecated update cmd
by Jon LaBadie
On F22, the manpage for dnf says the update and update-to
commands are deprecated aliases for upgrade and upgrade-to.
That being the case, shouldn't the update-info and
check-update commands also be deprecated and have
corresponding upgrade versions?
jl
--
Jon H. LaBadie jonfu(a)jgcomp.com
8 years, 1 month
How to fix : GPG key retrivial failed
by Angelo Moreschini
Hi,
I cannot finish the installation of VLC 'because in my computer there' is
not the key GCG.
The *command*:* sudo install VLC* ends with the error message:
GPG key retrieval failed: [Errno 14] curl # 37 - "Could not open file / etc
/ pki / rpm-gpg / RPM-GPG-KEY-RPMFusion-free-fedora-21"
to my knowledge, it should be, in the / etc / pki / rpm-gpg, the file
/ RPM-GPG-KEY-RPMFusion-free-fedora-21 (which has the encryption key
required for installation).
I do not know the reason, but I didn't get this file, and currently the
installation can not 'be completed ...
May some one sais me *how I can find and import this file* (/
RPM-GPG-KEY-RPMFusion-free-fedora-21) on my computer??
Thank you
Angelo
8 years, 1 month
