users December 2016

users@lists.fedoraproject.org

163 participants
146 discussions

closing lid of laptop
by Paolo Galtieri 01 Jan '17

01 Jan '17

I have a question regarding what is supposed to happen when I close the lid of a laptop. I always assumed that closing the lid would cause the system to go into suspend mode and wake up when the lid was opened. What I mean by suspend is that the system should be doing very little so as to not consume battery. However, what I have observed with my laptop when I upgraded to F25 is that the system is still active. I have an ssh session into the laptop from another system and this session is still active after I close the lid. So the question is what is supposed to happen when I close my laptop's lid? Any help is appreciated. Thanks, Paolo

5 9

DVD
by Patrick Dupre 01 Jan '17

01 Jan '17

Hello, I cannot rad DVD on my laptop;* Here are the sort of mesages that get: Gnome MPlayer Error: couldn't open DVD device: /dev/dvd (No suchfile or directory) DVD subpicture decoder, DVD subpicture decoder are required to play the file, but are not installed FAILED - Could not access dvdcdrom: /dev/dvd gxine: Either create a symbolic link /dev/dvd pointing to your cdrom device or set cdrom device in the preferences dialog If you are using the ise-cd module ensure that you have the following entry in /etc/modules: options ide-cd dma=1 Reload ide-cd module. Otherwise run hdparm -d 1 on your dvd-device /dev/sr0 on /run/media/pdupre/ROUBLEV type udf (ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2) The only thing that I can do is to view the file: /run/media/pdupre/ROUBLEV/VIDEO_TS/VIDEO_TS.VOB WHich shouldme access to the rest of the DVD, but then I get an error message: cannot find ....... Any idea? 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 ===========================================================================

3 4

Can F25 install Btrfs on top of LVM?
by Mayavimmer 31 Dec '16

31 Dec '16

I am trying to install F25 on a legacy box that already has a working Ext4 over LVM over Md raid 1 of 2x2TB disks, and only a single empty non raid partition on the second disk. The plan is to nondestructively upgrade the old OS to F25 by keeping both for a while, giving the user the option to boot the old OS if they want, without any further down time. Meanwhile I would slowly move the old data over to new dynamic Btrfs raid1, to take advantage of its gorgeous scrub and autorepair mechanism. All the work must be done remotely. The installer is confusing to me. Logic would suggest that you choose LVM device, then select a Btrfs volume instead of ext4, but there is no such option! Another sweaty palmed option would be to accept the ext4 over LVM install, then remotely online convert to btrfs, yikes! Then add magical incantations to fstab and/or grub and pray that the next remote reboot does not turn into a tragedy!

2 3

nouveau powermanagement causes system freeze after login
by Rob Mokkink 31 Dec '16

31 Dec '16

Hi, Did a fresh installation of fedora 25 on my new laptop, which has a nvidia geforce gtx960m. My plan was to use opensource drivers only, and make use of PRIME afterwards, to save battery life. I had to enable nomodeset during the installation, otherwise the system would freeze. After the installation i removed the nomodesetoption, which causes the system to freeze after logging in to gnome. When i set nouveau.modeset=0 in grub, i was able to login and work with the system. But then switcheroo-control service wouldn't work, and my battery life is really bad. I thought maybe it could be related to the power management options in the nouveau driver, booting with the nouveau.runpm=0, enables me to login, and switcheroo-control service works. However battery life is not that great, there is still a huge battery drain on my system. Do more people have this problem and is it this a nouveau problem? Thanks. Kind regards, Rob

1 0

Google Chrome generates many audit type 1326 messages
by Patrick O'Callaghan 31 Dec '16

31 Dec '16

I have hundreds of these per day in the journal. I even have a "audit_printk_skb: 45 callbacks suppressed". Does anyone know if this a) means anything, or b) can be turned off? Dec 27 12:47:36 bree kernel: audit: type=1326 audit(1482842856.033:8766): auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=18810 comm="chrome" exe="/opt/google/chrome/chrome" sig=0 arch=c00 Chrome version is: google-chrome-stable-55.0.2883.87-1.x86_64 poc

4 14

GPU lockup on Fedora 25 Mobility Radeon HD 5650/5750
by John O'Dwyer 31 Dec '16

31 Dec '16

I have been getting random GPU lockups on Fedora 25. I have the following GPU: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] I use the opensource driver on Wayland. I'm think the beginning of the random lockups coincided with upgrade from Mesa 12 to 13 on Fedora 25. I never experienced any lock up on Fedora 24 with Wayland. Is anyone having the same issue?

2 3

EFI F25 LVM install does not need separate /boot partition
by Mayavimmer 30 Dec '16

30 Dec '16

It seems that on EFI hardware Fedora 25 can be installed without the suggested separate /boot partition. I just selected auto partitioning on a LVM device, then deleted the given new /boot partition. It seems to work ok. Is it safe? If so, why does the Fedora installer propose a separate /boot in this EFI hardware case with GPT partitioning? Are there advantages/disadvantages? Skipping the creation of a separate /boot seems very convenient since a new install under LVM would only require one new physical partition, and reduce clutter (though I am a little suspicious about having swap under LVM too - is it shared by other OS' too?). On the other hand note that the Btrfs volume install does not allow you to delete the /boot partition.

3 3

GUI won't start - vdsmd.service ???
by Jeffrey Ross 30 Dec '16

30 Dec '16

I'm running Fedora 24 kernel 4.7.9-200 (x86_64). the system is on a Lenovo T440P. the machine boots and is accessable from the network but the system itself never presents a login prompt after starting a blank gray screen. Below are some the information that I think is useful, I'm not sure where to go from here. I was never successful with any of the 4.8.x kernels which is why I set acpi=off in grub, this allowed the 4.8 kernels to boot but they wouldn't start the gui either. I had just tried 4.8.15-200 with the same result so I removed it with the following command " sudo dnf remove kernel-core-4.8.15 kernel-modules-4.8.15 kernel-4.8.15 kernel-core-4.8.15 kernel-modules-4.8.15 kernel-4.8.15" to go back to 4.7.9, now I no longer get a login screen with 4.7.9. I am using the Lenovo "Ultradock" docking station (40A20170WW) with 2 external monitors connected via Displayport video interfaces. I'm looking for any help to get the display working again plus I'd like to get the 4.8 kernels working and upgrade to Fedora 25. Thanks in advance, Jeff â vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: disabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 14:26:07 EST; 1min 8s ago Process: 1952 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=1/FAILURE) Dec 30 14:26:07 laptop systemd[1]: vdsmd.service: Unit entered failed state. Dec 30 14:26:07 laptop systemd[1]: vdsmd.service: Failed with result 'exit-code'. Dec 30 14:26:07 laptop systemd[1]: vdsmd.service: Service hold-off time over, scheduling restart. Dec 30 14:26:07 laptop systemd[1]: Stopped Virtual Desktop Server Manager. Dec 30 14:26:07 laptop systemd[1]: vdsmd.service: Start request repeated too quickly. Dec 30 14:26:07 laptop systemd[1]: Failed to start Virtual Desktop Server Manager. $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:16.3 Serial controller: Intel Corporation 8 Series/C220 Series Chipset Family KT Controller (rev 04) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d4) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM87 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) 02:00.0 VGA compatible controller: NVIDIA Corporation GK208M [GeForce GT 730M] (rev a1) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) 04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83) grub kernel line - " rd.lvm.lv=fedora_laptop/root rd.luks.uuid=luks-533e7156-775d-48f6-abbd-90f14f31303d rd.lvm.lv=fedora_laptop/s wap rhgb quiet i915.enable_rc6=7 i915.enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 acpi=off" Xorg.0.log (last 40 lines or so) [ 118.031] (II) intel(0): EDID vendor "AUO", prod id 9022 [ 118.031] (II) intel(0): Printing DDC gathered Modelines: [ 118.031] (II) intel(0): Modeline "1600x900"x0.0 112.60 1600 1664 1706 1954 900 903 906 960 -hsync -vsync (57.6 kHz eP) [ 119.431] (II) intel(0): switch to mode 1920x1200(a)60.0 on DP2-1 using pipe 0, position (1920, 0), rotation normal, reflection none [ 119.431] (II) intel(0): switch to mode 1920x1200(a)60.0 on DP2-2 using pipe 1, position (0, 0), rotation normal, reflection none [1009690.260] (**) Option "fd" "17" [1009690.260] (**) Option "fd" "20" [1009690.260] (**) Option "fd" "21" [1009690.260] (**) Option "fd" "22" [1009690.260] (**) Option "fd" "23" [1009690.260] (**) Option "fd" "24" [1009690.260] (**) Option "fd" "25" [1009690.260] (**) Option "fd" "26" [1009690.260] (**) Option "fd" "27" [1009690.260] (**) Option "fd" "28" [1009690.260] (**) Option "fd" "29" [1009690.260] (**) Option "fd" "30" [1009690.260] (**) Option "fd" "25" [1009690.261] (II) UnloadModule: "libinput" [1009690.261] (II) systemd-logind: not releasing fd for 13:70, still in use [1009690.261] (II) UnloadModule: "libinput" [1009690.261] (II) systemd-logind: releasing fd for 13:75 [1009690.459] (II) UnloadModule: "libinput" [1009690.459] (II) systemd-logind: releasing fd for 13:71 [1009690.550] (II) UnloadModule: "libinput" [1009690.550] (II) systemd-logind: releasing fd for 13:68 [1009690.573] (II) UnloadModule: "libinput" [1009690.573] (II) systemd-logind: releasing fd for 13:67 [1009690.593] (II) UnloadModule: "libinput" [1009690.593] (II) systemd-logind: releasing fd for 13:74 [1009690.611] (II) UnloadModule: "libinput" [1009690.611] (II) systemd-logind: releasing fd for 13:70 [1009690.632] (II) UnloadModule: "libinput" [1009690.632] (II) systemd-logind: releasing fd for 13:69 [1009690.660] (II) UnloadModule: "libinput" [1009690.660] (II) systemd-logind: releasing fd for 13:83 [1009690.687] (II) UnloadModule: "libinput" [1009690.687] (II) systemd-logind: releasing fd for 13:65 [1009690.705] (II) UnloadModule: "libinput" [1009690.705] (II) systemd-logind: releasing fd for 13:73 [1009690.714] (II) UnloadModule: "libinput" [1009690.714] (II) systemd-logind: releasing fd for 13:72 [1009690.726] (II) UnloadModule: "libinput" [1009690.726] (II) systemd-logind: releasing fd for 13:66 [1009690.744] (II) NOUVEAU(G0): NVLeaveVT is called. [1009690.825] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error [1009691.303] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error [1009691.303] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error [1009691.706] (II) Server terminated successfully (0). Closing log file.

1 1

F24 Grub chainload for Win7 fails (long)
by Ron Leach 30 Dec '16

30 Dec '16

List, good evening, Our F24 installation in dual boot mode with Windows 7 has stopped W7 from booting from the Windows menu choice in Grub's screen. F24, nevertheless, boots and operates fine. Here are the installation details. We have a new laptop with Windows 7 pre-installed, which we'd configured for use, and backed up. The BIOS is set for UEFI with legacy settings. Since W7 had occupied the whole SSD we've upgraded the SSD (cloning the W7 SSD onto the new SSD using dd) and then rechecked, and tested, W7 running on the lower 228GB of the new SSD; all was fine. We installed F24/Xfce/64 from its 'live' spin onto the the remaining (approx 250 GB) segment of the SSD, allowing it to auto-partition. Installation proceeded without error; gparted showed that F24 had created 2 more partitions above the W7 partitions. On reboot, Grub starts fine, the F24 selection boots perfectly into F24, but selecting Windows just causes the machine to 'hang', showing a constant cursor in the top left corner of the screen. Checks done so far: 1. Bios boot order now shows an additional item 'Fedora'. Switching this 'Fedora' entry (in the Bios boot list) to below the HDD boot item (in the Bios boot order) has no different effect. 2. Using the Grub CLI to set the root, the chainloader location, and give a 'boot' command, has exactly the same effect as choosing the Windows entry in the Grub menu - 'hang' with the constant cursor in the top left corner. Grub CLI shows that the Windows boot partition, and files, all seem to be in place (sda2, /EFI/Microsoft/boot/bootmgfw.efi). 3. Because some of our work activities require use of Windows, it was essential to make sure we could get back to Windows, so we ran the W7 Windows System repair CD. This identified a problem in the UEFI firmware and wanted to reset the 'fwbootmgr' item in the UEFI system (NVRAM, apparently). We let it do this - aware that it might have repercussions on the F24 installation that was working well but, since it is relatively easy to re-install Fedora, we proceeded to let Windows recover. But this had two effects: (i) Windows rebooted quite happily, without a murmur. But it rebooted only itself; Fedora's Grub menu never appeared. (ii) Though the Fedora Grub menu had gone, checking the boot order in the Bios we found that there was, now, a new entry: 'Windows Boot Loader'. This was above another entry, 'Fedora' which was never executing now because 'Windows Boot Loader' had higher priority order. Switching the boot order in the Bios - to place 'Fedora' at the top, and 'Windows Boot Loader' second - Fedora's Grub menu then appears on booting up; F24 will boot and run perfectly, but selecting the Windows choice in Grub's menus again 'hangs' (with a cursor in the the top left corner). Setting the HDD to be at the top of the boot order gave the same result as setting 'Fedora' at the top - F24 would load, but Windows would not. Conclusions: (i) UEFI seems to contain an 'order of booting'. (ii) Fedora (presumably) makes a new entry in UEFI to point to its Grub system on bootup - that aspect seems to succeed. (iii) The chainloader sequence that Fedora employs executes a Windows bootmgfw.efi (on this machine) which might be 'hanging'. (iv) Might it be possible that the F24 installer has selected a file other than that which Windows 7 itself *actually* uses when it boots? Well, apologies for the length - I'd done quite a few checks and thought it best to add those results to the post in case they help narrow things down a bit. If anyone who managed this far has any suggestions for some things to try or to check, I'd be very grateful. In particular, I'd like to check which files W7 is using in its initial boot - ie, that I could try to emulate with the Grub CLI. If I could emulate a successful W7 boot, I could edit the F24 Grub configuration and make the change permanent. Has anyone here tried something similar themselves? regards, Ron

2 2

Most system update requires system reboot or session restart
by Sudhir Khanger 30 Dec '16

30 Dec '16

Hi, I update my Fedora Plasma desktop on a weekly basis. I have dnf tracer plugin installed. On my weekly update I notice that I am almost always required to either restart the session or reboot the system. Both of these options are unacceptable because they require closing 10-15 apps and restarting them. That's unnecessary hassle and loss in productivity. Fedora's all or none update system also doesn't make it easy. If I don't update system then I leave it vulnerable. I am setting up a work machine and I have to decide if Fedora is appropriate for me or not. Is the tracer plugin faulty or Fedora updates do require restarting session or system very frequently? https://dnf-plugins-extras.readthedocs.io/en/latest/tracer.html Regards, Sudhir Khanger, sudhirkhanger.com.

15 28

Jump to page: