Starting wayland from multi-user using startx, how do I know it's wayland?
by stan
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.
8 years, 3 months
how to create rescue disk fedora 23
by Jack Craig
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...
8 years, 3 months
KDE mailing list?
by John Horne
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
8 years, 3 months
ssh confusion
by Tom Horsley
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 :-).
8 years, 3 months
screen/remote apps
by bruce
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..
8 years, 3 months
4.3.3-300 DMAR: DMAR:[DMA Write] Request device [8a:06.1] fault addr fc26e000
by Nate Pearlstein
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.
8 years, 3 months
What kernel has a built-in support for this wlan card?
by M. Gelle
Hello,
If there's no current kernel that supports this card, then what's the eta
for Fedora 23 with:
Network controller: Qualcomm Atheros Device 0042 (rev 30). It's the QCA9377
model I believe.
The reason I ask is because this Lenovo Laptop has the weird ideapad_laptop
module.
I even tried disabling the Secure Boot to no avail - rfkill couldn't enable
wlan. Otherwise drivers will not load due to the "required key kissing"
error.
dmidecode | grep 'System Information' -A8
System Information
Manufacturer: LENOVO
Product Name: 80QD
Version: Lenovo YOGA 700-14ISK
Serial Number: PF0EKTY1
UUID: 4F9FAF54-8C06-11E5-8FC7-507B9D6D7E08
Wake-up Type: Other
SKU Number: LENOVO_MT_80QD_BU_idea_FM_Lenovo YOGA 700-14ISK
Family: IDEAPAD
regards,
Mo
8 years, 3 months
driver install but not loaded
by thibaut noah
Hello guys, got this weird error trying to install my raid driver :
Start to install the driver rr272x_1x.ko of rr272x_1x.
Finish installing the kernel module rr272x_1x.ko.
Loading rr272x_1x driver module rr272x_1x
modprobe: FATAL: Module rr272x_1x not found.
Checked with lsmod driver does not appear tough the installation is
finished (checked the sh file, modprobe is running at the end).
After a little read of the sh file i can confirm that the driver is in
/etc/rc.modules (it appears to be with sd_mod and that's all).
chmod on rc.modules in the sh file is successfull (chmod 755).
The failing part seems to be this :
elif [ "${MODULE}" = "rr272x_1x" -o "${MODULE}" = "rr274x_3x" -o
"${MODULE}" = "rr276x" -o "${MODULE}" = "rr278x" ] ; then
( cd /lib/modules/
for dir in [23].*; do
[ -d $dir/kernel/fs ] || continue
if [ -f /boot/initrd-$dir.img ]; then
mv /boot/initrd-$dir.img /boot/initrd-$dir.img.bak
# do not include mvsas in initrd, as the udev and so will load the driver
mkinitrd --builtin=mvsas /boot/initrd-$dir.img $dir
elif [ -f /boot/initramfs-$dir.img ]; then
mv /boot/initramfs-$dir.img /boot/initramfs-$dir.img.bak
# do not include mvsas in initramfs, as the udev and so will load the driver
dracut /boot/initramfs-$dir.img $dir
fi
done
Can someone give me a hint on how to do what needs to be done? I'm not
familiar with drivers on unix systems so i'm a bit lost, full sh file is
attached if needed, thanks.
8 years, 3 months