users January 2016

users@lists.fedoraproject.org

141 participants
138 discussions

Kernel 4.3.3-301
by jarmo 24 Jan '16

24 Jan '16

Last updated kernel brings me these... WARNING: Kernel Errors Present ata1.00: cmd 61/38:50:00:40:7d/07:00:06:00:00/40 tag 10 ncq 946176 out#012 res 40/00:58:38:47:7d/00:00:06:00:00/40 Emask 0x60 (host bus error) ...: 1 Time(s) ata1.00: cmd 61/70:b8:a8:16:7d/01:00:06:00:00/40 tag 23 ncq 188416 out#012 res 40/00:b8:a8:16:7d/00:00:06:00:00/40 Emask 0x60 (host bus error) ...: 1 Time(s) ata1.00: cmd 61/a8:b0:00:10:7d/06:00:06:00:00/40 tag 22 ncq 872448 out#012 res 40/00:b8:a8:16:7d/00:00:06:00:00/40 Emask 0x60 (host bus error) ...: 1 Time(s) ata1.00: cmd 61/e0:58:38:47:7d/00:00:06:00:00/40 tag 11 ncq 114688 out#012 res 40/00:58:38:47:7d/00:00:06:00:00/40 Emask 0x60 (host bus error) ...: 1 Time(s) ata1.00: irq_stat 0x20000000, host bus error ...: 2 Time(s) ata1: SError: { HostInt } ...: 2 Time(s) Jarmo -- конец

1 0

F23 and Ctrl D
by Stephen Davies 23 Jan '16

23 Jan '16

I have just updated my Compaq 610 from F22 to F23 (using dnf) and find that I can no longer use Ctrl D to exit a session nor Ctrl C to stop a process. Instead of the traditional response, I just get the keystrokes echoed in the terminal window. How can I restore the traditional responses?

1 0

Starting wayland from multi-user using startx, how do I know it's wayland?
by stan 23 Jan '16

23 Jan '16

I usually boot to multi-user, and then start the X server and client from a terminal using startx. It works great for X, but I would like to do the same for wayland. After reading the man for startx, I came up with putting #!/bin/bash exec startlxde -- /usr/bin/Xwayland into my ~/.Xclients file and then running startx. It seems to work, as I get a graphical interface running lxde. But am I really running wayland instead of X? Because it looks so much like X, I couldn't see that it wasn't X, and I wondered if startx just ignored the server request and used its default, X. How would I tell? There was no process Xwayland when I checked. If this isn't the way to start wayland from the command line, how would I do that? Thanks.

2 2

how to create rescue disk fedora 23
by Jack Craig 23 Jan '16

23 Jan '16

hi all, after a recent, unfortunate upgrade to F23, i resolve to have a rescue disk ready for next time i end in grub. however, i am not finding any how to create bookable recovery disk doc? ptrs anyone? tia, jackc...

6 8

KDE mailing list?
by John Horne 23 Jan '16

23 Jan '16

Hello, Does anyone know what is happening with the Fedora KDE mailing list? I joined the list a few weeks ago now, and sent a message to it. I have not received any messages from the list, and according to the archives it seems to have just stopped last November. I tried emailing the list maintainer, but again got no response at all. John. -- ---------------------------------------------------- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK

3 3

ssh confusion
by Tom Horsley 23 Jan '16

23 Jan '16

If I try to login to a fedora 23 virtual machine as root, I get rejected because of "too many authentication failures" (or something like that, I don't remember the precise wording). I'm running an agent, but none of the keys in the agent would allow a root login so I expect it to fallback to a password prompt, but I get the failure instead. When I then try with this: ssh -o PreferredAuthentications=keyboard-interactive,password I do indeed get a password prompt and can login. I suspect I'm suffering from the effects of the changes in f23 to remove various crypto algorithms and ssh1 support, etc. But I can't figure out what the heck is going on. Any ideas? I'd love to not have to dig up the silly long option every time I want to login as root :-).

5 6

Mounting /proc with additional options
by Todor Petkov 23 Jan '16

23 Jan '16

Hello, I am trying to remount /proc on Fedora 22, kernel 4.0.4-301, following this guide http://www.cyberciti.biz/faq/linux-hide-processes-from-other-users/ It works on RHEL/CentOS, but not on this setup. Have someone tried it on Fedora with newer kernel? Also, can someone tell or guide me to a manual how and which systemd file to be changed, so the mount of /proc accepts this parameter? Of I can use /etc/fstab? Regards,

1 1

Mounting /proc with additional options
by Todor Petkov 23 Jan '16

23 Jan '16

1 0

screen/remote apps
by bruce 22 Jan '16

22 Jan '16

Hi. I can locally run screen, and then run an app. If I wanted to have a process where I remotely start/run an app on a remote box (ssh) via screen, How is this accomplished? Can it be done? Ie, I want the app on the remote instance/box to be running in a screen process within a term. This would allow someone to login, fire up the screen process for the screen id, and see the process in action... Thanks for any pointers..

5 9

4.3.3-300 DMAR: DMAR:[DMA Write] Request device [8a:06.1] fault addr fc26e000
by Nate Pearlstein 22 Jan '16

22 Jan '16

Seeing errors after upgrading from 4.2.8-300 to 4.3.3-300, I also see the same errors on newer kernels for f23 from koji and 4.5.0-0.rc0.git6.1.vanilla.knurd.1 dmesg | egrep -i ‘mlx|dmar' [ 17.816756] mlx4_core 0000:82:00.0: Mapped 1 chunks/256 KB at 120040000 for ICM [ 17.825330] mlx4_core 0000:8a:00.0: SRIOV, disabling HA mode for intf proto 0 [ 17.825541] <mlx4_ib> mlx4_ib_add: counter index 0 for port 1 allocated 0 [ 17.833869] <mlx4_ib> mlx4_ib_add: counter index 1 for port 2 allocated 0 [ 17.906397] mlx4_core 0000:8a:00.0: Mapped 1 chunks/256 KB at 120040000 for ICM [ 17.911403] mlx4_core 0000:8a:00.0: mlx4_ib: multi-function enabled [ 17.925065] mlx4_core 0000:8a:00.0: mlx4_ib: initializing demux service for 128 qp1 clients [ 17.937459] mlx4_core 0000:8a:00.0: Mapped 1 chunks/256 KB at 128040000 for ICM [ 17.938766] mlx4_core 0000:8a:00.0: Mapped 1 chunks/256 KB at 1200c0000 for ICM [ 29.527780] mlx4_core 0000:8a:00.0: Mapped 1 chunks/256 KB at 128080000 for ICM [ 29.529083] mlx4_core 0000:8a:00.0: Mapped 1 chunks/256 KB at 120140000 for ICM [ 31.330799] DMAR: DRHD: handling fault status reg 2 [ 31.330803] DMAR: DMAR:[DMA Write] Request device [8a:06.1] fault addr fc26e000 DMAR:[fault reason 02] Present bit in context entry is clear [ 31.330865] DMAR: DRHD: handling fault status reg 102 [ 31.330868] DMAR: DMAR:[DMA Read] Request device [8a:06.1] fault addr fc632000 DMAR:[fault reason 02] Present bit in context entry is clear [ 31.530006] DMAR: DRHD: handling fault status reg 202 . . . All previous f22 and f23 releases I’ve used were fine. I have two IB cards: all Firmware version: 2.9.1000 82:00.0 InfiniBand: Mellanox Technologies MT26428 [ConnectX VPI PCIe 2.0 5GT/s - IB QDR / 10GigE] (rev b0) 8a:00.0 InfiniBand: Mellanox Technologies MT26428 [ConnectX VPI PCIe 2.0 5GT/s - IB QDR / 10GigE] (rev b0) The first one has sriov off the second has sriov on.

2 2

← Newer
1
2
3
4
5
6
7
8
9
...
14
Older →

Jump to page: