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, 4 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, 4 months
Monitor / graphics card recommendation
by Mark
One of my new year's resolutions is to upgrade the monitor on my Fedora
23 Desktop.
I've been looking at a 34" curved 3440 x 1440 monitor. But first I want
to make sure it actually makes sense to get such a large monitor for
Linux and that there's a graphics card on the market that works well
with Fedora and that can drive such a large monitor. I would prefer an
open source driver, but I'm prepared to install a blob if I have to.
I'm not interested in gaming so that's not an issue, it's the real
estate I'm after.
Any thoughts/recommendations?
8 years, 4 months
Mate-bluetooth SRPM?
by Fred Smith
Hi!
I'm looking for a SRPM for mate-bluetooth. I'm told Fedora packages
it, but so far I've not been able to find it despite my mythical
google-fu :).
Can anyone point me to a location of it?
thanks!
--
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
The eyes of the Lord are everywhere,
keeping watch on the wicked and the good.
----------------------------- Proverbs 15:3 (niv) -----------------------------
8 years, 4 months
Fedora 23: IPv6 not working with Dell DW1525 (ath9k)
by Laurențiu Păncescu
Hi there,
I upgraded a Dell Vostro 260 desktop PC (with a Dell DW1525 wireless
card for network connectivity, using an Atheros AR9280 chip) from
Fedora 22 to 23. IPv4 continued to work, but IPv6 packets seem to go
into a black hole, even ping6 or ssh. I added ipv6.disable=1 to the
grub configuration as a workaround, but I'd like to understand what's
going on.
I booted both the PC and a netbook (having an AR9281 wireless card,
which also uses the ath9k kernel driver, connected to the same
wireless router) from the same Fedora 23 Workstation live image: IPv6
works perfectly on the netbook, but not on the PC. Fedora 22 and 21
worked fine, too. I also tried to boot F23 on the PC with the 4.2.6
and 4.2.8 kernels from F22, but IPv6 doesn't work in this
configuration, either.
Any idea what might be wrong? I could attach the full output of lspci
-vvnn if it's useful:
03:00.0 Network controller [0280]: Qualcomm Atheros AR928X Wireless
Network Adapter (PCI-Express) [168c:002a] (rev 01)
Subsystem: Qualcomm Atheros DW1525 802.11abgn WLAN PCIe Card [AR9280]
[168c:0203]
Thanks,
Laurentiu
8 years, 4 months
Re: Fedora 22 continuously rebooting (Solved)
by Armelius Cameron
Hello,
Well, I finally figured out the cause, thanks to Richard's first
suggestion in looking at journalctl output.
I was playing around with udev rules to try to automatically mount an
external drive (it didn't really work yet). Apparently having this
extra rule in /etc/udev/rules.d causes the system to continually
reboot, something to do with watchdog and udev I guess. These lines
were in the log:
Jan 19 13:19:12 daedalus kernel: watchdog watchdog1: watchdog did not stop!
Jan 19 13:19:12 daedalus kernel: watchdog watchdog1: watchdog did not stop!
Jan 19 13:19:12 daedalus systemd-udevd[512]: Error calling
EVIOCSKEYCODE on device node '/dev/input/event16' (scan code 0x150,
key code 190): Invalid argument
Somehow I missed the udev error before, but simply removing the extra
rule fix the infinite reboot issue.
It is still surprising to me that such an innocent mistake causes that
kind of catastrophic results.
Thanks again for all the response. They prompted me to look into this
direction which solved the issue eventually.
Best,
AC
8 years, 4 months
Fedora 23 will not boot if laptop lid closed
by Mike Wohlgemuth
I have an old laptop that I use as a home server, so it sits in the
corner closed most of the time. Something changed with the last set of
updates I applied so now if I reboot, it suspends in the middle of the
boot process, and will not continue until I open the laptop, at which
point it will continue. Is anyone else seeing this? Is there a new
setting somewhere that I can change to get it to boot with the lid
closed?
Thanks
Mike
8 years, 4 months
F23 PXE strange failure
by CLOSE Dave
I'm working with a new PXE configuration file which may certainly
contain some errors. Usually, it terminates with a "pane dead". But
after the latest modification, it terminated by going to the Dracut
emergency shell. In itself, that might help me, even though thus far I
haven't found my error in the logs. But I did find something that seems
quite strange to me and would like any available feedback.
Inside the Dracut shell, I ran the journalctl command. As this was a
server in a remote data center, I couldn't easily attach a thumb drive
and save the result. But here are the last few lines output.
Jan 19 20:35:52 localhost dracut-initqueue[812]: Starting dhcp for
interface eth0
Jan 19 20:35:52 localhost dracut-initqueue[812]: dhcp: PREINIT eth0 up
Jan 19 20:35:52 localhost dhclient[1041]: Created duid
\000\001\000\001\03612\250\260\203\376\341\211.
Jan 19 20:35:52 localhost dhclient[1041]: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8 (xid=0x45a50c20)
Jan 19 20:36:00 localhost dhclient[1041]: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 18 (xid=0x45a50c20)
Jan 19 20:36:18 localhost dhclient[1041]: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 8 (xid=0x45a50c20)
Jan 19 20:36:26 localhost dhclient[1041]: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 15 (xid=0x45a50c20)
Jan 19 20:36:41 localhost dhclient[1041]: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 12 (xid=0x45a50c20)
Jan 19 20:36:53 localhost dhclient[1041]: No DHCPOFFERS received.
Jan 19 20:36:53 localhost cracut-initqueue[812]: dhcp failed
Jan 19 20:36:59 localhost kernel: random: nonblocking pool is initialized
Jan 19 20:40:01 localhost dracut-initqueue[812]: Warning: Could not boot.
Jan 19 20:40:01 localhost systemd[1]: Received SIGRTMIN+20 from PID 823
(plymouthd).
Jan 19 20:40:01 localhost dracut-initqueue[812]: Warning: /dev/root does
not exi
st
Jan 19 20:40:01 localhost systemd[1]: Starting Dracut Emergency Shell...
Ok, so the PXE startup doesn't think it was able to get an IP address.
But when I look at the DHCP server, it did get an address! The times
from journalctl are UTC and those from the DHCP log are local PST
(-0800) but the times otherwise match up quite well. Here's what the
DHCP log shows.
Jan 19 12:34:52 us02linuxdhcp01p dhcpd[8500]: DHCPDISCOVER from
b0:83:fe:e1:cc:89 via 10.76.148.1
Jan 19 12:34:53 us02linuxdhcp01p dhcpd[8500]: DHCPOFFER on 10.76.148.243
to b0:83:fe:e1:cc:89 via 10.76.148.1
Jan 19 12:34:57 us02linuxdhcp01p dhcpd[8500]: DHCPREQUEST for
10.76.148.243 (10.76.140.72) from b0:83:fe:e1:cc:89 via 10.76.148.1
Jan 19 12:34:57 us02linuxdhcp01p dhcpd[8500]: DHCPACK on 10.76.148.243
to b0:83:fe:e1:cc:89 via 10.76.148.1
Jan 19 12:36:01 us02linuxdhcp01p dhcpd[8500]: DHCPDISCOVER from
b0:83:fe:e1:cc:89 via 10.76.148.1: network 10.76.148.0/23: no free leases
Jan 19 12:36:18 us02linuxdhcp01p dhcpd[8500]: DHCPDISCOVER from
b0:83:fe:e1:cc:89 via 10.76.148.1: network 10.76.148.0/23: no free leases
Jan 19 12:36:26 us02linuxdhcp01p dhcpd[8500]: DHCPDISCOVER from
b0:83:fe:e1:cc:89 via 10.76.148.1: network 10.76.148.0/23: no free leases
Jan 19 12:36:42 us02linuxdhcp01p dhcpd[8500]: DHCPDISCOVER from
b0:83:fe:e1:cc:89 via 10.76.148.1: network 10.76.148.0/23: no free leases
Not only was an OFFER sent in response to the first REQUEST, it appears
that the OFFER was accepted by the client. Still the client sent four
additional REQUESTs and didn't record the result of the acceptance. How
can this be?
--
Dave Close
8 years, 4 months
Issues with install F23 MATE desktop
by Chris Adams
I have a brand-new Dell Precision workstation, on which I'm trying to
install Fedora 23 (with my preferred desktop environment, MATE), which
is turning into the most frustrating Linux install I've experienced in a
long time (and I've been using Linux since before Red Hat existed).
I started with Fedora-Workstation-netinst-x86_64-23 on a thumb drive. I
booted, selected automatic partitioning and MATE, and it started
downloading RPMs. When it finished downloading, it rebooted.
Apparently, there's a conflict between release and updates on who owns
/etc/xdg/menus/mate-preferences-categoris.menu, and anaconda just
crashes and reboots (not even a traceback) on an install transaction
failure.
After a few passes through that before I figured out anaconda was not
going to install MATE (with frustrating waits for downloads each time),
I gave up and did a minimal install. Then I did a dnf groupinstall
MATE, and that downloaded all the RPMs, then gave me the error about the
file conflict. I tried to exclude one of the choices, use --best, etc.,
and nothing would solve it.
Also, when "dnf groupinstall foo" is run, even if it fails, dnf then
thinks the group is installed (and so a repeated groupinstall does
nothing). I had to do a groupremove first.
I just manually installed the RPMs from the dnf cache to get around the
MATE brokenness, and then got systemd to do a graphical boot.
Now, when I get to the graphical login, my USB is dead. I can boot
single-user mode and the keyboard works fine; as soon as the graphical
login loads, USB appears dead (keyabord is like it is powered off, no
Numlock, Capslock, etc.). Tried unplugging keyboard, moving it to
different USB ports (directly on the computer instead of hub), etc. with
no result. The fact that the keyboard works in single-user mode shows
there's no hardware problem, Linux USB issue, etc.
At this point, I guess I'll roll back and try Fedora 22. If I ever get
a working desktop, I'll try to file some bugs I guess. I found a BZ
about anaconda that appears to match my problem (1287841). That doesn't
explain the MATE conflicts in the repos, dnf groupinstall fail, or
disappearing USB though.
--
Chris Adams <linux(a)cmadams.net>
8 years, 4 months
f23 mate policykit libvirt problem
by Nate Pearlstein
I’ve been trying to get policykit to automatically authorize virt-manager.
This was working fine with fedora 21, but with fedora 23 it doesn’t seem to work. For both I’ve been using the mate desktop.
With f21 I had the following in /etc/polkit-1/localauthority/50-local.d/caprica.libvirt.pkla
[Allow user libvirt management permissions]
Identity=unix-user:user
Action=org.libvirt.unix.manage
ResultAny=yes
ResultInactive=yes
ResultActive=yes
I tried the above with f23 and no luck. I’ve since tried
/etc/polkit-1/rules.d/80-libvirt.rules
polkit.addRule(function(action, subject) {
if (action.id == "org.libvirt.unix.manage" && subject.local && subject.active && subject.isInGroup("wheel")) {
return polkit.Result.YES;
}
});
and a few variations with no luck.
Anyone seen this work with f23?
I have the following rpms installed:
mate-polkit-1.12.0-1.fc23.x86_64
polkit-0.113-4.fc23.x86_64
polkit-devel-0.113-4.fc23.x86_64
polkit-docs-0.113-4.fc23.noarch
polkit-gnome-0.105-9.fc23.x86_64
polkit-libs-0.113-4.fc23.x86_64
polkit-pkla-compat-0.1-6.fc23.x86_64
polkit-qt-0.112.0-5.fc23.x86_64
polkit-qt5-1-0.112.0-5.fc23.x86_64
8 years, 4 months
