Re: rdma-core-32.0-1.fc33.i686 has inferior architecture

2021-02-17 Thread Tim Jackson
On 06/02/2021 00:51, Matthew Miller wrote: Hmmm, yeah, this seems like something that could be untangled. Could you file this as a bug against the "distribution" component, for lack of anywhere better occurring to me right now? OK: https://bugzilla.redhat.com/show_bug.cgi?id=1930004 Tim

Re: New kernel errors after last update, Fedora 33

2021-02-17 Thread Ed Greshko
On 18/02/2021 03:07, Jerome Lille wrote: 192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora desktop that produces these error messages has some shares from it mounted. No errors on the NFS server and the nfs shares seems to work fine. Are you using NFSv3 or NFSv4 to mount the s

Re: can't find wireless

2021-02-17 Thread Roger Heflin
You need to run "ifconfig -a" to show all interfaces including "down" network hardware, otherwise it defaults to only show up interfaces. On Wed, Feb 17, 2021 at 4:54 PM Paolo Galtieri wrote: > > I have a Dell XPS 15 9500 laptop. I've already listed other issues with > this laptop running Fedora

Re: can't find wireless

2021-02-17 Thread Samuel Sieb
On 2/17/21 2:54 PM, Paolo Galtieri wrote: I have a Dell XPS 15 9500 laptop.  I've already listed other issues with this laptop running Fedora 33. Here's a new one :( lspic -k shows the following: 0:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi     Subsystem: Rivet Networ

can't find wireless

2021-02-17 Thread Paolo Galtieri
I have a Dell XPS 15 9500 laptop.  I've already listed other issues with this laptop running Fedora 33. Here's a new one :( lspic -k shows the following: 0:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi     Subsystem: Rivet Networks Device 1651     Kernel modules: iwlwifi

Re: New kernel errors after last update, Fedora 33

2021-02-17 Thread Jerry James
On Wed, Feb 17, 2021 at 12:08 PM Jerome Lille wrote: > Thanks for the suggestion. I did get more logging > > RPC: 5d78dc3a connect status 107 connected 0 sock state 7 > xs_tcp_setup_socket: connect returned unhandled error -107 > RPC: xs_tcp_state_change client 5d78dc3a

Re: New kernel errors after last update, Fedora 33

2021-02-17 Thread Jerome Lille
On Wed, 2021-02-17 at 11:43 -0700, Jerry James wrote: > On Wed, Feb 17, 2021 at 10:33 AM Jerome Lille > wrote: > > After the latest update there are some errors in the log that I > > haven't > > seen before. > > > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > > > There

Re: New kernel errors after last update, Fedora 33

2021-02-17 Thread Jerry James
On Wed, Feb 17, 2021 at 10:33 AM Jerome Lille wrote: > After the latest update there are some errors in the log that I haven't > seen before. > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > There are two of those per minute continuously. I haven't noticed any > other pro

Re: New kernel errors after last update, Fedora 33

2021-02-17 Thread Tom Horsley
On Wed, 17 Feb 2021 10:10:23 -0800 Clifford Snow wrote: > I'm running 5.10.15-200.fc33.x86_64 and have not seen those errors. Same here. Sounds like some application is running that causes that error and I'm not running that app. ___ users mailing list

Re: New kernel errors after last update, Fedora 33

2021-02-17 Thread Clifford Snow
I'm running 5.10.15-200.fc33.x86_64 and have not seen those errors. On Wed, Feb 17, 2021 at 9:34 AM Jerome Lille wrote: > After the latest update there are some errors in the log that I haven't > seen before. > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > There are tw

New kernel errors after last update, Fedora 33

2021-02-17 Thread Jerome Lille
After the latest update there are some errors in the log that I haven't seen before. kernel: xs_tcp_setup_socket: connect returned unhandled error -107 There are two of those per minute continuously. I haven't noticed any other problems with the system, but wondering about those messages are abou