driver nvidia f24
by François Patte
Bonjour,
I try to install nvidia proprietary drivers on a fresh f24 install.
I tried this: http://rpmfusion.org/Howto/nVidia
failed
this:
http://doc.fedora-fr.org/wiki/Carte_graphique_NVIDIA_:_installation_des_p...
failed
All these seem to be incomplete....
Where can I find a correct guide for this installation?
Thank you.
PS. I had to boot on rescue disk after each attempt in order to remove
all akmod and xorg packages installed.
2 remarks: 1- the rescue mode from grub does not work
2- the rescue mode from install disck works but the
keyboard remains qwerty, and my luks passphrase was typed
initialy with an azerty keyboard..... This is not too much friendly for
non qwerty users!
--
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
7 years, 7 months
Asus RT-N66U/Tomato-Shibby -
by Bob Goodwin
I have an Asus RT-N66U running Tomato USB Shibby which has been working
without any trouble but after some ISP problems recently I have managed
to screw up the time offset. It should be -400 but has become +200 which
makes it difficult for me to deal with Access Restrictions and reading
logs. Other than that, time and the offset is correct in this computer.
This is a major component of my Fedora system so I am asking here if
anyone knows how to correct this.
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10VM FEDORA-25a/64bit LINUX XFCE POP3
7 years, 7 months
Graphics issue in modeset
by Patrick Dupre
Hello,
With my card
product: GM107M [GeForce GTX 960M]
vendor: NVIDIA Corporation
description: VGA compatible controller
product: HD Graphics 530
vendor: Intel Corporation
Using the modules:
nouveau 1519616 0
i915 1302528 0
mxm_wmi 16384 1 nouveau
ttm 90112 1 nouveau
crc32c_intel 24576 6
i2c_algo_bit 16384 2 i915,nouveau
drm_kms_helper 143360 2 i915,nouveau
serio_raw 16384 0
drm 344064 4 ttm,i915,drm_kms_helper,nouveau
alx 36864 0
mdio 16384 1 alx
wmi 16384 3 msi_wmi,mxm_wmi,nouveau
video 40960 3 i915,msi_wmi,nouveau
In modeset, the graphics mode is stuck:
Sep 10 21:23:32 Sappho kernel: NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [Xorg.wrap:1145]
Sep 10 21:23:32 Sappho kernel: Modules linked in: cmac bnep dm_crypt rtsx_usb_ms memstick arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm snd_hda_codec_hdmi irqbypass crct10dif_pclmul snd_hda_codec_realtek crc32_pclmul iwlmvm snd_hda_codec_generic ghash_clmulni_intel intel_cstate intel_uncore intel_rapl_perf mac80211 snd_hda_intel snd_hda_codec iTCO_wdt snd_hda_core iTCO_vendor_support snd_hwdep snd_seq msi_wmi sparse_keymap snd_seq_device snd_pcm iwlwifi hci_uart btusb btrtl joydev btqca btbcm btintel cfg80211 snd_timer bluetooth snd i2c_i801 soundcore mei_me shpchp mei rfkill intel_lpss_acpi intel_lpss pinctrl_sunrisepoint pinctrl_intel acpi_als kfifo_buf industrialio tpm_tis acpi_pad binfmt_misc rtsx_usb_sdmmc mmc_core rtsx_usb nouveau i915 mxm_wmi ttm crc32c_intel i2c_algo_bit drm_kms_helper
Sep 10 21:23:32 Sappho kernel: serio_raw drm alx mdio wmi video i2c_hid fjes ecryptfs encrypted_keys trusted tpm
Sep 10 21:23:32 Sappho kernel: CPU: 3 PID: 1145 Comm: Xorg.wrap Tainted: G L 4.7.2-201.fc24.x86_64 #1
Sep 10 21:23:32 Sappho kernel: Hardware name: Micro-Star International Co., Ltd. GE62 6QD/MS-16J5, BIOS E16J5IMS.10F 01/21/2016
Sep 10 21:23:32 Sappho kernel: task: ffff880276b08000 ti: ffff880277e74000 task.ti: ffff880277e74000
Sep 10 21:23:32 Sappho kernel: RIP: 0010:[<ffffffff813f3b40>] [<ffffffff813f3b40>] ioread32+0x30/0x40
Sep 10 21:23:32 Sappho kernel: RSP: 0018:ffff880277e777e8 EFLAGS: 00000292
Sep 10 21:23:32 Sappho kernel: RAX: 00000000ffffffff RBX: ffff880276051400 RCX: 0000000000000018
Sep 10 21:23:32 Sappho kernel: RDX: 00000da3a628615e RSI: ffffc9000410a014 RDI: ffffc90004009400
Sep 10 21:23:32 Sappho kernel: RBP: ffff880277e77808 R08: ffffea0009df6020 R09: 0000000000184000
Sep 10 21:23:32 Sappho kernel: R10: 0000000000284000 R11: 000000000000004d R12: 00000000ffffffff
Sep 10 21:23:32 Sappho kernel: R13: ffff88027566c788 R14: ffff880279ed9e00 R15: ffffffffffffffff
Sep 10 21:23:32 Sappho kernel: FS: 00007f92c6007740(0000) GS:ffff880283cc0000(0000) knlGS:0000000000000000
Sep 10 21:23:32 Sappho kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 10 21:23:32 Sappho kernel: CR2: 00007f81e4f9e050 CR3: 000000027732b000 CR4: 00000000003406e0
Sep 10 21:23:32 Sappho kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 10 21:23:32 Sappho kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 10 21:23:32 Sappho kernel: Stack:
Sep 10 21:23:32 Sappho kernel: ffffffffc032a4cb ffff880276051400 0000000000000000 ffff88027566c788
Sep 10 21:23:32 Sappho kernel: ffff880277e77818 ffffffffc032a04f ffff880277e77850 ffffffffc03229a0
Sep 10 21:23:32 Sappho kernel: ffff88027566c788 ffff880276051400 0000004afddac7fc 0000004afbbd1e3c
Sep 10 21:23:32 Sappho kernel: Call Trace:
Sep 10 21:23:32 Sappho kernel: Call Trace:
Sep 10 21:23:32 Sappho kernel: [<ffffffffc032a4cb>] ? nv04_timer_read+0x3b/0x70 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc032a04f>] nvkm_timer_read+0xf/0x20 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc03229a0>] nvkm_pmu_init+0x50/0x450 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc02dc9d5>] nvkm_subdev_init+0x95/0x200 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc032e598>] nvkm_device_init+0x178/0x280 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc0331f98>] nvkm_udevice_init+0x48/0x60 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc02db360>] nvkm_object_init+0x40/0x190 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc02db3d4>] nvkm_object_init+0xb4/0x190 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc02d856e>] nvkm_client_init+0xe/0x10 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc0375e8e>] nvkm_client_resume+0xe/0x10 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc02d7797>] nvif_client_resume+0x17/0x20 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc037354b>] nouveau_do_resume+0x4b/0x120 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc037394f>] nouveau_pmops_runtime_resume+0x7f/0x120 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffff8142b00b>] pci_pm_runtime_resume+0x7b/0xa0
Sep 10 21:23:32 Sappho kernel: [<ffffffff8152bdf7>] __rpm_callback+0x27/0x70
Sep 10 21:23:32 Sappho kernel: [<ffffffff8152be64>] rpm_callback+0x24/0x80
Sep 10 21:23:32 Sappho kernel: [<ffffffff8142af90>] ? pci_restore_standard_config+0x40/0x40
Sep 10 21:23:32 Sappho kernel: [<ffffffff8152c7eb>] rpm_resume+0x49b/0x6a0
Sep 10 21:23:32 Sappho kernel: [<ffffffff8135f992>] ? cred_has_capability+0x72/0x120
Sep 10 21:23:32 Sappho kernel: [<ffffffff8121fcf1>] ? __slab_free+0xa1/0x2a0
Sep 10 21:23:32 Sappho kernel: [<ffffffff8152d83e>] __pm_runtime_resume+0x4e/0x70
Sep 10 21:23:32 Sappho kernel: [<ffffffffc0373e7b>] nouveau_drm_open+0x3b/0x1a0 [nouveau]
Sep 10 21:23:32 Sappho kernel: [<ffffffff8135faa0>] ? selinux_capable+0x20/0x30
Sep 10 21:23:32 Sappho kernel: [<ffffffff81355fb8>] ? security_capable+0x48/0x60
Sep 10 21:23:32 Sappho kernel: [<ffffffffc0081be5>] drm_open+0x1f5/0x430 [drm]
Sep 10 21:23:32 Sappho kernel: [<ffffffffc0087f30>] drm_stub_open+0xb0/0x110 [drm]
Sep 10 21:23:32 Sappho kernel: [<ffffffff8124ad60>] chrdev_open+0xb0/0x180
Sep 10 21:23:32 Sappho kernel: [<ffffffff812434a5>] do_dentry_open+0x205/0x2e0
Sep 10 21:23:32 Sappho kernel: [<ffffffff8124acb0>] ? cdev_put+0x30/0x30
Sep 10 21:23:32 Sappho kernel: [<ffffffff81244894>] vfs_open+0x54/0x80
Sep 10 21:23:32 Sappho kernel: [<ffffffff81251c0c>] ? may_open+0x8c/0x100
Sep 10 21:23:32 Sappho kernel: [<ffffffff81254ebd>] path_openat+0x68d/0x14b0
Sep 10 21:23:32 Sappho kernel: [<ffffffff817e940b>] ? __mutex_unlock_slowpath+0x6b/0x90
Sep 10 21:23:32 Sappho kernel: [<ffffffff81256fb1>] do_filp_open+0x91/0x100
Sep 10 21:23:32 Sappho kernel: [<ffffffff8125e599>] ? dput+0xd9/0x260
Sep 10 21:23:32 Sappho kernel: [<ffffffff8126505f>] ? __alloc_fd+0x3f/0x170
Sep 10 21:23:32 Sappho kernel: [<ffffffff81244c50>] do_sys_open+0x130/0x220
Sep 10 21:23:32 Sappho kernel: [<ffffffff81244d5e>] SyS_open+0x1e/0x20
Sep 10 21:23:32 Sappho kernel: [<ffffffff81003d52>] do_syscall_64+0x62/0x110
Sep 10 21:23:32 Sappho kernel: [<ffffffff817eb921>] entry_SYSCALL64_slow_path+0x25/0x25
Sep 10 21:23:32 Sappho kernel: Code: 03 00 77 25 48 81 ff 00 00 01 00 76 05 0f b7 d7 ed c3 55 48 c7 c6 85 bc a6 81 48 89 e5 e8 19 ff ff ff b8 ff ff ff ff 5d c3 8b 07 <c3> 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 81 fe ff ff
Does this help to fix the glitch ?
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
===========================================================================
7 years, 7 months
Fedora 24: sound fails at random times
by Timothy Murphy
In the last couple of weeks I've had a curious problem
on my Fedora-24/KDE Thinkpad T510 laptop.
Sound (on YouTube for example) starts up fine on Firefox,
but then suddenly stops working after 5 to 30 minutes.
It's exactly the same with Google Chrome.
I see nothing at all odd in journalctl -b0 ;
alsa and pulseaudio seem to start fine,
and then are no longer mentioned.
The only cure I have found is to re-boot.
I've looked at
<https://fedoraproject.org/wiki/How_to_debug_sound_problems>
and
<https://fedoraproject.org/wiki/How_to_troubleshoot_sound_problems>
and followed some of the suggestions there,
but to no avail.
There does not seem to have been any recent update
to alsa or pulse-audio.
I wonder if anyone else has had a similar experience?
Or if anyone can suggest any possible alternative to re-booting?
Incidentally, I can boot into Windows 10 on this laptop,
and sound seems to work perfectly there.
So it seems there is nothing wrong with the hardware.
--
Timothy Murphy
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin
7 years, 7 months
problem with dnf
by Reynold DeMarco Jr
When I run an install with dnf the program downloads the packages runs
through transaction checks and begins the installation. When it is done
with the installation it just freezes. In the past it would run through
a verification and clean up and then return to command prompt. Any ideas
on correcting this situation would be appreciated.
Reynold
7 years, 7 months
brightness
by Patrick Dupre
Hello,
How can I manage the brightness of my laptop ?
xbacklight -get (or -set)
does not work.
A gui interface would be helpful.
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
===========================================================================
7 years, 7 months
F23: Seems sshd service not accepting connections
by Ron Leach
Running F23/XFCE, with firewalld, and having commanded:
# systemctl start sshd.service
/var/log/secure
shows that sshd is opening port 22, and listening on 0.0.0.0 .
There is no entry suggesting a login attempt is received.
In the XFCE GUI for firewalld, everything is running in zone labelled
'public'.
- The network interface is bound to the zone 'public'
- SSH service is enabled in zone 'public'
- I've added port 22/tcp to the list of active ports in zone 'public'
- 'Lockdown', and 'panic mode' are disabled
These settings are the same in mode 'permanent' and in mode 'runtime'
sshd config is set to listen on 0.0.0.0 (and ::).
Our LAN uses ipv4, in the range 192.168.0/24 .
This machine is connected to the network, but I cannot log in to sshd
from any machine on the LAN. The client times-out after a few
seconds. Clients do not report a 'rejection'.
If any list readers have any ideas about what else might need to be
set up, or might be going wrong, I'd be very grateful to hear,
Ron
7 years, 7 months
Cleaning up after an aborted upgrade
by CLOSE Dave
I have a machine where I tried to do a system-upgrade from F23 to F24.
The download portion worked fine but after the reboot, the upgrade
process aborted. I'd like to know why, but first I need to clean up the
mess so I can try it again. Right now I have 4782 total packages
installed including 1490 fc24 packages. I haven't checked all of them
but it appears that all are paired with the same fc23 package.
Trying to repeat the download step, I get this result.
# dnf --allowerasing -y system-upgrade download --releasever 24
Last metadata expiration check: 0:23:15 ago on Tue Sep 6 15:53:47 2016.
Dependencies resolved.
Error: The operation would result in removing the following protected
packages: systemd.
Evidently, there are two systemd packages installed:
# rpm -q systemd
systemd-222-14.fc23.x86_64
systemd-229-13.fc24.x86_64
No new kernel was installed and the machine is running fine as F23. But
I'd like to get it upgraded...
I tried using "dnf history rollback" but that didn't work, reporting "A
transaction cannot be undone". Since dnf won't erase the extra stuff, I
can probably do it with something like, "rpm erase --force $(rpm
-qa|grep fc24)" but that seems iffy. Better suggestions are very welcome.
--
Dave Close
7 years, 7 months
*Still* having grief trying to stick a samsung SSD into ASUS laptop
running fedora 23
by Robert P. J. Day
(this is almost certainly a kernel issue but here's hoping someone
can give me some guidance.)
once upon a time, i whined pathetically about problems sticking a
samsung 950 PRO M.2 SSD into my ASUS G752VL-DH71 gaming laptop
currently running fedora:
http://osdir.com/ml/fedora-users/2016-07/msg00410.html
eventually, i tripped over this ASUS forum page:
https://rog.asus.com/forum/archive/index.php/t-79590.html
where one gets the distinct impression that that particular samsung
SSD is not compatible with my laptop, but one is assured that what
does work is the samsung SM951, which i picked up, with still no luck,
still getting early error message:
ata1.00: failed to enable AA (error_mask=0x4)
... etc etc ...
this is the SSD:
https://www.amazon.com/Samsung-SM951-512GB-NVMe-MZVPV512HDGL-00000/dp/B01...
and i'm running out of ideas; do i need to roll my own kernel to add
support for this thing? i would have thought that if i don't have
support, the SSD would just be ignored, and not choke the system.
i'm about to do more testing this weekend, but i sure would like
some advice.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
7 years, 7 months