Wifi and sound broken after kernel upgrade 5.3.16 -> 5.4.7
by Benjamin Lowry
Hey everyone, I'm on Fedora 31 and recently upgraded my kernel from
5.3.16 to 5.4.7, and now my sound (via snd_hda_intel) and wifi doesn't
work; the wifi options in GNOME are missing, and my only sound device
is the default PulseAudio "Dummy Output". Everything works fine if I
manually select the old kernel in GRUB. Is this a known issue, and
should I file a bug about this?
# dmidecode -s system-version
ThinkPad X1 Carbon 7th
Here's the relevant log sections:
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: warning: No matching ASoC machine driver found
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: use msi interrupt mode
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2
Jan 08 16:42:46 newton kernel: sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Collecting data: trigger 15 fired.
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Status: 0x00000000, count: 1540278722
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Loaded firmware version: 48.4fa0041f.0
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xEDF689F1 | ADVANCED_SYSASSERT
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x64CB54DD | trm_hw_status0
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xF8687609 | trm_hw_status1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x308D2DCD | branchlink2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x6ADDA111 | interruptlink1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x1543DD43 | interruptlink2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x64802E76 | data1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x1DD12EFE | data2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x7716D38D | data3
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xDBC00F86 | beacon time
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xADE83137 | tsf low
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x33E55AED | tsf hi
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x8AC5F930 | time gp1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x71C94C4C | time gp2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xFEDB56F5 | uCode revision type
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xB1AC2681 | uCode version major
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xAF3B9842 | uCode version minor
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xFDAE5B60 | hw version
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x871997F8 | board version
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x4B1BD676 | hcmd
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x0E6EC2AE | isr0
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x88516878 | isr1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x1995D970 | isr2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xE6F00ADB | isr3
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xEADDC224 | isr4
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x6C9914F9 | last cmd Id
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x9A278D81 | wait_event
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x351FD4F6 | l2p_control
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x46D8FCD1 | l2p_duration
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x5DEA2927 | l2p_mhvalid
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x7DC7B996 | l2p_addr_match
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xD0C0BC2F | lmpm_pmg_sel
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x8B9718C9 | timestamp
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xBF827979 | flow_handler
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Status: 0x00000000, count: 7
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x201013F1 | ADVANCED_SYSASSERT
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xC008CF5C | umac branchlink2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000003 | umac data1
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x20000302 | umac data2
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x01300202 | umac data3
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000030 | umac major
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x4FA0041F | umac minor
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00005D11 | frame pointer
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xC0887F58 | stack pointer
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | last host cmd
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Fseq Registers:
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_ERROR_CODE
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x00000000 | FSEQ_TOP_INIT_VERSION
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x2E66E477 | FSEQ_CNVIO_INIT_VERSION
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x11C5D9CE | FSEQ_TOP_CONTENT_VERSION
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xE02CC5D2 | FSEQ_ALIVE_TOKEN
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xDD1880B9 | FSEQ_CNVI_ID
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x5562D073 | FSEQ_CNVR_ID
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x20000302 | CNVI_AUX_MISC_CHIP
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x5c84, CPU2 Status: 0x3
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Failed to start RT ucode: -110
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Firmware not running - cannot dump error
Jan 08 16:42:47 newton kernel: iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110
4 years, 5 months
Access to cbs.com failing with error 2002 or 2004??
by Michael D. Setzer II
Using Firefox was able to use it the other day with no problem, but then
yesterday started getting the 2002 or 2004 error message. Mentioned turning
off the new firefox tracker, but made no difference.
Rebooted the same machine to the old Windows 7 partition, and got the
same error with latest Firefox, but with windows, turning off the new tracking
made it go thru with no error. Contacted CBS, but no response yet..
Anyone else seen this, or have a solution..
Thanks.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned: 19,471
Processing time: 32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)
BOINC@HOME CREDITS
ROSETTA 66311323.990119 | ABC 16613838.513356
SETI 109804121.703177 | EINSTEIN 141859222.999240
4 years, 5 months
Current state of AMD/Radeon support
by Richard Shaw
With the AMD graphics card drivers being open sourced I'm considering
moving away from NVidia on my next graphics card purchase but I'm concerned
because of all the driver issues I've heard about on Windows.
Are the linux drivers experiencing the same problems or are they pretty
stable?
As much as I don't like depending on the NVidia binary drivers, I have had
VERY few issues.
Thanks,
Richard
4 years, 5 months
rkhunter warning: real or false alarm?
by home user
This morning, I got the following warning from rkhunter:
-----
---------------------- Start Rootkit Hunter Scan ----------------------
Warning: Network TCP port 60922 is being used by
/usr/lib64/firefox/firefox. Possible rootkit: zaRwT.KiT
Use the 'lsof -i' or 'netstat -an' command to check this.
----------------------- End Rootkit Hunter Scan -----------------------
-----
The output of lsof -i is here:
-----
bash.1[~]: lsof -i
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 31u IPv4 2530 0t0 TCP *:sunrpc (LISTEN)
systemd 1 root 32u IPv4 2536 0t0 UDP *:sunrpc
systemd 1 root 33u IPv6 2543 0t0 TCP *:sunrpc (LISTEN)
systemd 1 root 35u IPv6 2550 0t0 UDP *:sunrpc
rpcbind 857 rpc 4u IPv4 2530 0t0 TCP *:sunrpc (LISTEN)
rpcbind 857 rpc 5u IPv4 2536 0t0 UDP *:sunrpc
rpcbind 857 rpc 6u IPv6 2543 0t0 TCP *:sunrpc (LISTEN)
rpcbind 857 rpc 7u IPv6 2550 0t0 UDP *:sunrpc
rpcbind 857 rpc 11u IPv6 22909 0t0 UDP *:50041
avahi-dae 890 avahi 12u IPv4 24285 0t0 UDP *:mdns
avahi-dae 890 avahi 13u IPv6 24286 0t0 UDP *:mdns
avahi-dae 890 avahi 14u IPv4 24287 0t0 UDP *:57958
avahi-dae 890 avahi 15u IPv6 24288 0t0 UDP *:39302
chronyd 917 chrony 5u IPv4 27077 0t0 UDP localhost:323
chronyd 917 chrony 6u IPv6 27078 0t0 UDP localhost:323
dhclient 1091 root 6u IPv4 31071 0t0 UDP *:bootpc
cupsd 1110 root 7u IPv4 32911 0t0 TCP *:ipp (LISTEN)
cupsd 1110 root 8u IPv6 32912 0t0 TCP *:ipp (LISTEN)
dhclient 1168 root 5u IPv6 29353 0t0 UDP
coyote:dhcpv6-client
dnsmasq 1285 dnsmasq 3u IPv4 36958 0t0 UDP *:bootps
dnsmasq 1285 dnsmasq 5u IPv4 36961 0t0 UDP coyote:domain
dnsmasq 1285 dnsmasq 6u IPv4 36962 0t0 TCP coyote:domain
(LISTEN)
sendmail 2061 root 4u IPv4 40777 0t0 TCP localhost:smtp
(LISTEN)
bash.2[~]:
-----
The output from "netstat -an" is too long to put here. I don't know
what to look for in all that.
1. What specifically should I be looking for?
2. Is rkhunter's warning a false alarm or a real problem?
thanks,
Bill.
4 years, 5 months
Transfer my current Linux install to a new dual boot drive with
Windows ?
by linux guy
Hi people.
I'm about to purchase a new workstation computer because my current
workstation is too slow. The new computer comes with Windows 10 installed
on it. I rarely use Windows, but occasionally it comes in handy to
troubleshoot something, so I'd like to leave it on the hard drive.
Question: how do I transfer my current workstation installation to the
new hard drive and retain Windows ? I don't want to start over building
my workstation installation from a fresh install.
Thanks
LG
4 years, 5 months
Authentification error in kdm, gdm after rsync cloning an OS...
console fine.
by linux guy
Hello wonderful Fedora people. ;)
I cloned an operating system using rsync using the following, basically:
sudo rsync -aHxv --numeric-ids --progress root@brix:/* /mnt/drive
--exclude=/dev --exclude=/proc --exclude=/sys --exclude=/tmp --exclude=/boot
It worked fantastically well. I'll post the nity gritty details in another
thread once I confirm a few things.
Everything works perfectly, except that I can't log into a session with kdm
or gdm because of an authentication error. I can log into a console
session without any issues.
I have never been able to log into a session using gdm. The session
displays the user names, it allows me to input a password and then the
screen flashes and it returns me to the gdm screen.
I am able to log into a kdm session. When I first do I received several
SELinux errors and I am asked for the root password anytime I tried to do
anything. Other than that everything worked well.
The message is "Authentification is required to access the PC/SC daemon"
One of the SELinux erros was something about unix_chkpwd map
/etc/ld.so.cache and it gave me an option to fix it. I ran that command
and the SELinux errors seemed to have stopped.
Furthermore when I run passwd <username> and try to reset a password, I
get: Authentication Token Manipulation error.
What is going wrong and how do I fix it ?
Thanks
4 years, 5 months
i915 bug in kernel 5.4.x, GUI complete freezes up
by Chris Murphy
Affects Skylake and Kabylake so far, I'm not sure how extensive it is
within each series, but as F31 has rebased to 5.4 I thought I'd give a
heads up. It's actually somewhat rare, I have an npm+electron chat app
that seems to hit this way more often than say Firefox (and I'm not
chatting near as much as I'm webbing).
[drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out
https://bugzilla.redhat.com/show_bug.cgi?id=1780800
If you hit it, revert to 5.3.18 and if you want cc to the bug report
with CPU model. Another idea is to use a current 5.5.0rc, it's fixed
there but the backport is giving upstream devs some grief so I'm not
sure when it's going to get fixed in 5.4. I think part of the delay is
also the two holidays falling on Wednesdays :D
--
Chris Murphy
4 years, 5 months
Dual Monitor - second monitor not working
by Simon Colston
Fedora 31
When installing, I had a Dell monitor attached to an nvidia graphics card via HDMI and that was working fine. I
installed the nvidia drivers for this.
I now want to use an old ViewSonic monitor as a second monitor so I plugged it into the on-board VGA port and booted.
The ViewSonic monitor is now the only monitor working. I adjusted the settings to make the display useable (Settings ->
Devices -> Displays) but only the ViewSonic monitor is listed here.
Google has led me to try this:
simon@hedgehog ~]$ lspci | grep -i VGA
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop 9 Series) (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1)
[simon@hedgehog ~]$ xrandr -q
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 16384 x 16384
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1600x1200+0+0 (normal left inverted right x axis y axis) 432mm x 324mm
1600x1200 60.00*+
1400x1050 74.87 59.98
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
640x480 75.00 72.81 66.67 59.94
720x400 70.08
** Note that there is an HDMI connector on the motherboard as well so I am not sure if HDMI-1 here refers to that.
I tried this:
[simon@hedgehog ~]$ xrandr --output HDMI-1 --auto --right-of DP-1
[simon@hedgehog ~]$
... but there was no output and nothing changed.
I would like to end up with a separate desktop on each monitor.
Any help gratefully received.
Simon
4 years, 5 months
