Kernel 4.1.4 breaks external display
by CS DBA
Hi All;
I'm running Fedora 21 on a Dell M3800 laptop, been working great.
Updating to the latest kernel however breaks my external display
i.e. I plug the external monitor in and nothing happens, previous to the
update when I plug in the external monitor
the system would auto configure the second screen and I could use both
monitors.
I've googled the issue but not found anything.
Thoughts?
Thanks in advance
8 years, 7 months
rpm in background
by Patrick Dupre
Hello,
This task used to run very often on my machine and makes every slow.
How can I manage it?
rpm -q -a --queryformat %{NAME}\n%{VERSION}-%{RELEASE}\n%{EPOCH}\n%{GROUP}\n%{SUMMARY}\n\n
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
8 years, 7 months
multipathd rienstated message filling up log
by Shawn Bakhtiar
Good morning,
/var/log/messages is being filled with following message "multipathd: 104:0: reinstated". I though it might be a bad controller card, or something wrong with the hardware as suggested in IRC, but I have installed FC 22 64bit on two separate machines (same configuration) and I’m getting these same message.
The messages don’t seem to be effecting performance or have any effect on data, and short of being annoying, I want to make sure there is not some more serious/heinous issue going on that I need to be aware of.
Machine Specs:
Proliant DL160 Smart Array E200 controller running RAID 1 (250GB mirrored).
[root@postoffice ~]# blkid
/dev/block/253:4: LABEL="root" UUID="7e2a3fef-cab0-44a3-b5ec-cd9a50267ee0" TYPE="xfs"
/dev/block/253:2: UUID="dBG0Mg-6MaT-Jfm3-XuFH-5PeA-a881-D7VWfa" TYPE="LVM2_member" PARTUUID="449dbbad-02"
/dev/block/253:1: UUID="b8cfeac4-9d28-402d-9ba6-7f41f583508a" TYPE="ext4" PARTUUID="449dbbad-01"
/dev/block/253:3: UUID="362b77ca-8bf7-434a-96cf-6e30fd9c5a79" TYPE="swap"
/dev/cciss/c0d0: PTUUID="449dbbad" PTTYPE="dos"
/dev/sda1: UUID="6412b71f-3dfb-41c9-82af-5030dcad856d" TYPE="ext3"
/dev/mapper/mpatha: PTUUID="449dbbad" PTTYPE="dos"
[root@postoffice ~]# multipath -l
Aug 14 07:58:43 | cciss/c0d0: No fc_host device for 'host0'
Aug 14 07:58:43 | cciss/c0d0: No fc_host device for 'host0'
Aug 14 07:58:43 | cciss/c0d0: No fc_remote_port device for 'rport-0:0-0'
mpatha (3600508b10010503953574630334a0004) dm-0 HP ,LOGICAL VOLUME
size=233G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=0 status=active
`- 0:0:0:0 cciss/c0d0 104:0 active undef running
[root@postoffice ~]# more /etc/fstab
...
UUID=7e2a3fef-cab0-44a3-b5ec-cd9a50267ee0 / xfs defaults 0 0
UUID=b8cfeac4-9d28-402d-9ba6-7f41f583508a /boot ext4 defaults 1 2
UUID=362b77ca-8bf7-434a-96cf-6e30fd9c5a79 swap swap defaults 0 0
/dev/sda1 /media/USBBackup_001 auto defaults 0 0
[root@postoffice ~]# df -m
Filesystem 1M-blocks Used Available Use% Mounted on
devtmpfs 1966 0 1966 0% /dev
tmpfs 1976 0 1976 0% /dev/shm
tmpfs 1976 1 1976 1% /run
tmpfs 1976 0 1976 0% /sys/fs/cgroup
/dev/mapper/fedora_postoffice-root 233358 168507 64852 73% /
tmpfs 1976 0 1976 0% /tmp
/dev/mapper/mpatha1 843 148 636 19% /boot
/dev/sda1 1691174 329305 1275957 21% /media/USBBackup_001
tmpfs 396 0 396 0% /run/user/1000
Sample message logs:
Aug 14 07:24:21 postoffice multipathd: 104:0: reinstated
Aug 14 07:24:26 postoffice multipathd: 104:0: reinstated
Aug 14 07:24:31 postoffice multipathd: 104:0: reinstated
Aug 14 07:24:36 postoffice multipathd: 104:0: reinstated
Aug 14 07:24:41 postoffice multipathd: 104:0: reinstated
Aug 14 07:24:46 postoffice multipathd: 104:0: reinstated
Aug 14 07:24:51 postoffice multipathd: 104:0: reinstated
Aug 14 07:24:56 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:01 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:06 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:11 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:16 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:21 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:26 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:31 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:36 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:41 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:46 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:51 postoffice multipathd: 104:0: reinstated
Aug 14 07:25:56 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:01 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:06 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:11 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:16 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:21 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:26 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:31 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:36 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:41 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:46 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:51 postoffice multipathd: 104:0: reinstated
Aug 14 07:26:56 postoffice multipathd: 104:0: reinstated
Aug 14 07:27:01 postoffice multipathd: 104:0: reinstated
Aug 14 07:27:06 postoffice multipathd: 104:0: reinstated
8 years, 7 months
Moving Fedora 22 to RAID 0 - Trouble with initramfs
by Samuel Rakitničan
I have moved / partition to another partition formed in RAID 0
consisting of two SSDs. I have updated fstab with new partition UUID,
reinstalled GRUB2 and rebuild initramfs using dracut -f. Now computer
boots fine from RAID partition but hangs on when initramfs needs to
boot kernel from / partition found on RAID, because it can't find
partition with UUID that I've put in fstab.
Now from what I have understood when it drops me to dracut prompt in
initramfs boot process I indeed can't find the RAID assembled BUT I
can assemble it manually by using "mdadm -I /dev/sda" and "mdadm -I
/dev/sdb". If I boot from old hard drive the RAID is assembled
normally in kernel on boot time:
$ journalctl -b | grep "kernel: md"
Kol 30 01:20:53 computername kernel: md: bind<sdb>
Kol 30 01:20:53 computername kernel: md: bind<sda>
Kol 30 01:20:53 computername kernel: md: bind<sdb>
Kol 30 01:20:53 computername kernel: md: bind<sda>
Kol 30 01:20:53 computername kernel: md: raid0 personality registered
for level 0
Kol 30 01:20:53 computername kernel: md/raid0:md126: md_size is
500129792 sectors.
Kol 30 01:20:53 computername kernel: md: RAID0 configuration for md126 - 1 zone
Kol 30 01:20:53 computername kernel: md: zone0=[sda/sdb]
Kol 30 01:20:53 computername kernel: zone-offset= 0KB,
device-offset= 0KB,
Kol 30 01:20:53 computername kernel:
Kol 30 01:20:53 computername kernel: md126: detected capacity change
from 0 to 256066453504
Kol 30 01:20:53 computername kernel: md126: p1 p2 p3
Kol 30 01:20:53 computername kernel: md: export_rdev(sdb)
Kol 30 01:20:53 computername kernel: md: export_rdev(sda)
Kol 30 01:20:53 computername kernel: md: export_rdev(sdb)
Kol 30 01:20:53 computername kernel: md: export_rdev(sda)
The RAID is formed using onboard southbridge Intel controller. I have
managed to extract data from initramfs but I am not sure what to look
for, in particular what brings up RAID assembly.
/etc/udev/rules.d/65-md-incremental-imsm.rules seems like it's
responsible to assemble, but I am not sure.
Any thoughts why imsm RAID is not assembled in initramfs on boot?
8 years, 7 months
sometimes xfce turns crazy
by François Patte
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bonjour,
As I use to suspend for some time my computer every day without any
problems, today I am asked to get authenticated as root to perform
this action (as well as to shutdown the computer...)
I did not update my system, I did not change anything to my config, I
did not install any new software....
This kind of problem sucks!!!
Thank you for any clue!
- --
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)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlXkOLkACgkQdE6C2dhV2JXZIgCgr+lUJ1GH5ujLsjtzCBJFAGWf
UQ4An2BnrUnPzOjNm7PKVMQsubRBO1j3
=pPJy
-----END PGP SIGNATURE-----
8 years, 7 months
rsync checksum to compare directories
by Chris Murphy
# rsync -rvnc --delete /brick0 /brick1
I've confirmed that separate devices are mounted to /brick0 and
/brick1. What I'm seeing for ~ 20 minutes now is only the device
mounted at brick0 is being accessed, and yet I'm seeing piles of files
(verbose option) being listed.
I'd expect that there'd be some back and forth as the checksum
comparison happens almost simultaneously. Any ideas how this ought to
work? Is rsync caching the checksums for brick0, and then it'll go
compute checksums on brick1 and compare?
Maybe I should use diff -qr because this is just too much verbosity
anyway. I don't need every file listed. I only want to know if there
are any files that are different (deleted), but I don't know if I get
any delete notification from rsync without -v.
--
Chris Murphy
8 years, 7 months
grub2-install fails
by Paul Cartwright
I installed my new drive, and everything was fine. I added another OS,
and now I can't do the grub2-install anymore. What am I missing??
# grub2-install /dev/sda
grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist.
Please specify --target or --directory.
boot is mounted:
/dev/sda8 95M 9.5M 86M 11% /boot/efi
ls -l /boot/efi/EFI/fedora
total 5864
-rwx------ 1 root root 102 Feb 17 2015 BOOT.CSV
drwx------ 2 root root 2048 May 21 14:59 fonts
-rwx------ 1 root root 1064296 Apr 28 16:10 gcdx64.efi
-rwx------ 1 root root 7653 Aug 21 04:57 grub.cfg
-rwx------ 1 root root 1024 Aug 21 04:57 grubenv
-rwx------ 1 root root 1064296 Apr 28 16:10 grubx64.efi
-rwx------ 1 root root 1276224 Feb 17 2015 MokManager.efi
-rwx------ 1 root root 1293304 Feb 17 2015 shim.efi
-rwx------ 1 root root 1287032 Feb 17 2015 shim-fedora.efi
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
8 years, 7 months
efibootmgr help
by Paul Cartwright
ok, I am running fedora 22, along with ubuntu & Windows 10. a new kernel
got installed last night, and I rebooted, but grub doesn't show it, and
still defaults to the ubuntu OS. I am new to this efibootmgr, and google
is letting me down.. This is all new to me, and I am having a problem
understanding what I need to do now...
#df -h
/dev/sda10 46G 8.3G 36G 19% /
/dev/sdb6 154G 80G 67G 55% /home
/dev/sda8 95M 9.5M 86M 11% /boot/efi
grub2-mkconfig works, but grub2-install /dev/sda gives me an error
grub2-install /dev/sda
grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist.
Please specify --target or --directory.
this shows that the default is ubuntu. all I want is to update this & make the newest fedora kernel the default.
# efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,0003,0000,0001
Boot0000* P0: WDC WD10EZEX-75M2NA0 BBS(17,,0x0)
Boot0001* P4: TSSTcorp DVD+/-RW SH-216DB BBS(19,,0x0)
Boot0002* Fedora
HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\fedora\shim.efi)
Boot0003* Windows Boot Manager
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...9................
Boot0004* ubuntu
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)
Boot000C* UEFI OS
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0016* UEFI OS
HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\BOOT\BOOTX64.EFI)
Boot001A* ubuntu
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\Ubuntu\grubx64.efi)
#efibootmgr -o 0004,0003,0000,0001
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,0003,0000,0001
Boot0000* P0: WDC WD10EZEX-75M2NA0
Boot0001* P4: TSSTcorp DVD+/-RW SH-216DB
Boot0002* Fedora
Boot0003* Windows Boot Manager
Boot0004* ubuntu
Boot000C* UEFI OS
Boot0016* UEFI OS
Boot001A* ubuntu
is there a good manual somewhere for efibootmgr??
I thought when a new kernel was installed, grub would automagically add
it... not with efi?
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
8 years, 7 months
Install not working guacamole Fedora 22
by David Highley
Installation of guacamole is not working on Fedora 22. We have tried
native install and docker installation. We seem to get closer with the
native install. We are able to login to the guacamole web page and try
and connect VNC to hosts but they have blank screens. We can connect
using vinagre so the VNC seems to be working. We never see a connection
to guacd on port 4822. We did notice that the guacamole package and the
quacd package are different versions. We are using:
guacamole-0.9.3-2.fc22.noarch
guacd-0.9.5-3.fc22.x86_64
tomcat-7.0.59-4.fc22.noarch
libguac-client-vnc-0.9.5-3.fc22.x86_64
x11vnc-0.9.13-13.fc22.x86_64
Anyone have this working, if so what seems to be the magic? Thanks
8 years, 7 months
Fedora on Asus?
by Jonathan Allen
Dear Fedora Experts,
My daughter is looking at an Asus Zenbook UX305, which has a 128Gb
SSD but no hard-drive. It comes with Win 8.1, but is it likely to
work with Linux? Graphics are Intel HD5300.
Jonathan
8 years, 7 months
