F35 no USB after today's updates
by Sergio Pascual
Hi, I upgraded my workstation to F35 last Friday, and today I 'dnf updated'
and rebooted. After the reboot, all my USBs are disabled. No mouse, no
keyword.
I know my hardware works because the keyboard works in grub, and the light
of my optical mouse in on until some errors appear in the kernel during
boot.
I have tried:
kernel-5.14.15-200.fc34.x86_64
kernel-5.14.15-300.fc35.x86_64
kernel-5.14.16-301.fc35.x86_64
without success.
I'm getting messages like these:
[ 23.722355] usb 3-10: new high-speed USB device number 7 using xhci_hcd
[ 23.857746] usb 3-10: New USB device found, idVendor=0bda,
idProduct=0184, bcdDevice=84.13
[ 23.857755] usb 3-10: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 23.857759] usb 3-10: Product: USB2.0-CRW
[ 23.857762] usb 3-10: Manufacturer: Generic
[ 23.857764] usb 3-10: SerialNumber: 20100818841300000
[ 24.016363] usb 3-7.1: new high-speed USB device number 8 using xhci_hcd
[ 29.648377] usb 3-7.1: device descriptor read/64, error -110
[ 45.520400] usb 3-7.1: device descriptor read/64, error -110
[ 45.624451] usb 3-7-port1: attempt power cycle
[ 45.738358] usb 3-13: new high-speed USB device number 9 using xhci_hcd
[ 45.865929] usb 3-13: New USB device found, idVendor=05e3,
idProduct=0608, bcdDevice=32.98
[ 45.865939] usb 3-13: New USB device strings: Mfr=0, Product=1,
SerialNumber=0
[ 45.865942] usb 3-13: Product: USB2.0 Hub
[ 45.866653] hub 3-13:1.0: USB hub found
[ 45.866992] hub 3-13:1.0: 4 ports detected
[ 46.304365] usb 3-7.1: new high-speed USB device number 10 using xhci_hcd
[ 56.160384] xhci_hcd 0000:00:14.0: Abort failed to stop command ring:
-110
[ 56.160384] xhci_hcd 0000:00:14.0: xHCI host controller not responding,
assume dead
[ 56.160384] xhci_hcd 0000:00:14.0: HC died; cleaning up
[ 56.488455] xhci_hcd 0000:00:14.0: Timeout while waiting for setup
device command
[ 56.488480] usb 4-2: USB disconnect, device number 2
[ 56.904366] usb 3-7.1: device not accepting address 10, error -108
[ 56.904412] usb 3-7-port1: couldn't allocate usb_device
[ 56.904464] usb usb3-port2: couldn't allocate usb_device
[ 56.904502] usb 3-13-port1: couldn't allocate usb_device
[ 56.904603] usb 3-3: USB disconnect, device number 2
[ 56.927819] usb 3-6: USB disconnect, device number 3
2 years, 6 months
Fedora 35 - gedit
by Michael J. Baars
Hi All,
I've been working with Fedora for years now, and I just installed the newest Fedora Workstation 35 on one of my computers.
Since I use gedit a lot for editing source codes, gedit was one of the first programs I tried to launch. Now, there I get into trouble. After opening a few
source files and trying to start off where I left, I noticed that the mouse pointer (and the line number) often does not end up where I clicked the mouse when
trying to position the cursor (for cutting and pasting for example). This is the very first time that I experience this problem.
Help would be appreciated,
Best regards,
Mischa Baars.
2 years, 6 months
During the first update after installation: Failed to connect to bus:
Invalid argument
by Peter Boy
While updating right after installation of Fedora Server 35 today I get:
> [...]# sudo dnf update
> ...
> Cleanup : glibc-langpack-de-2.34-7.fc35.x86_64 303/306
> Cleanup : glibc-gconv-extra-2.34-7.fc35.x86_64 304/306
> Running Scriptlet: glibc-gconv-extra-2.34-7.fc35.x86_64 304/306
> Cleanup : glibc-common-2.34-7.fc35.x86_64 305/306
> Cleanup : tzdata-2021b-1.fc35.noarch 306/306
> Running Scriptlet: grub2-common-1:2.06-8.fc35.noarch 306/306
> Running Scriptlet: selinux-policy-targeted-35.5-1.fc35.noarch 306/306
> Running Scriptlet: clevis-18-4.fc35.x86_64 306/306
> Running Scriptlet: libwbclient-2:4.15.1-0.fc35.x86_64 306/306
> Running Scriptlet: kernel-core-5.14.16-301.fc35.x86_64 306/306
> Running Scriptlet: sssd-common-2.6.0-2.fc35.x86_64 306/306
> Running Scriptlet: tzdata-2021b-1.fc35.noarch 306/306
> Failed to connect to bus: Invalid argument
>
> Failed to connect to bus: Invalid argument
>
> Failed to connect to bus: Invalid argument
> Failed to connect to bus: Invalid argument
>
> Verifying : clevis-pin-tpm2-0.3.0-2.fc35.x86_64 1/306
> Verifying : freetype-2.11.0-1.fc35.x86_64 2/306
I first suspected there was an error during installation and repeated it, watching for error / warning messages (none). The error messages during the update occurred again.
I can’t remember these messages some days ago after another installation using an activated root account.
I didn’t found any issues yet.
Anyone else got these messages?
Best
Peter
2 years, 6 months
Introduction: nedia, a Silverblue fan
by Aiden Langley
Kia ora koutou,
I'm nedia, I live in NZ & I've been knocking about the matrix/irc for a few days now. I'll be 28 on the 30th, I've been using Fedora for about a year, Linux for about 3-4 (Ubuntu & Antergos), & have been doing software dev for about 5-6 years.
I started my career w/ Java, then spent some time w/ PHP on some legacy spaghetti, wrote a cool CLI that interfaced w/ AWS EC2 instances to run data conversions and had a lot of fun with it, and I've dabbled in some Rust, C#, Python and more JavaScript than I'd like to admit. Keen to write something in Go one day.
https://wowhub.co.nz is what keeps me occupied at the moment, I contract / volunteer at a not for profit, charge enough to pay my bills but my work is mostly kōha (a gift \ given free of charge.) I could potentially spend a lot of time on Fedora related projects, my weekends are v open & I give the Whakaoranga Whanau about 24 hours a week. I have tourettes so sometimes I need days to myself to recoup mentally.
I'm currently using Silverblue, I'm enamored by the ideas - immutability is huge to me now. I get anxiety whenever I use another distro, knowing one false step might lead to a re-install. I'm a tinkerer so it happens a fair bit.
I'm also running Rawhide, since Silverblue affords me an extra layer of security, it seemed like it was the perfect fit for running some potentially unstable software.
An area that seems like it could use some work from what I've observed is `rpm-ostree`, being able to upgrade packages for testing e.g. `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-992e409289` & group installs are missing at the moment. I wanted to be able to run a 2nd DE in case of bugs, but would have to install each package individually as it stands so I settle for just rebasing when the time comes. Is `rpm-ostree module` intended to be the new `group`?
Anyway, v interested in Silverblue and putting myself in a position to test & contribute to the above, so if anybody would like to sponsor / point me in the right direction, that would be much appreciated.
Cheers,
*nedia*
2 years, 6 months
Notice: openQA test failures today - expected
by Adam Williamson
Hey folks! Just a heads up about test failures in openQA overnight and
today. The server_cockpit_updates test was failing overnight; this was
because I switched from virtio to qxl graphics to work around a bug in
Rawhide. Unfortunately there seems to be a bug in qxl with a specific
thing that test does (snapshot the machine, run X from a console,
restore the snapshot, run X from a console again).
I've switched that test back to virtio graphics and re-triggered all
the failed runs, but since then the planned Koji outage has started.
All update tests that run during the Koji outage will fail because the
test process relies on downloading the update packages from Koji. So
some of the re-runs for the other bug failed. We will not be able to
get successful runs until the Koji outage is over.
Basically, if you're seeing an openQA failure on your update, hang
tight for the end of the Koji outage.
There are two updates with other issues (a Pango update that changes
font rendering and so will need a lot of openQA screenshots to be re-
taken, and a Python update that seems to break `systemctl stop
ipa.service` for some reason), but again I can't really work on those
with Koji down, so will wait for it to be back.
Thanks folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
2 years, 6 months
Re: deltarpm usefulness?
by Sumit Bhardwaj
It is not always about speed. There are still plenty of places in the world
where people are on limited data plans and to them using delta rpms makes a
lot of sense. They can work with slow speeds but not with high data
expenses. So i feel turning it on by default and having a setting to turn
it off is still a sane choice. Just my 2 cents.
Regards,
Sumit Bhardwaj
On Sun, Nov 7, 2021, 9:33 AM <devel-request(a)lists.fedoraproject.org> wrote:
> Send devel mailing list submissions to
> devel(a)lists.fedoraproject.org
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
> devel-request(a)lists.fedoraproject.org
>
> You can reach the person managing the list at
> devel-owner(a)lists.fedoraproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devel digest..."Today's Topics:
>
> 1. Re: deltarpm usefulness? (Gary Buhrmaster)
>
>
>
> ---------- Forwarded message ----------
> From: Gary Buhrmaster <gary.buhrmaster(a)gmail.com>
> To: Development discussions related to Fedora <
> devel(a)lists.fedoraproject.org>
> Cc:
> Bcc:
> Date: Sun, 7 Nov 2021 02:30:30 +0000
> Subject: Re: deltarpm usefulness?
> On Sun, Nov 7, 2021 at 2:22 AM Demi Marie Obenour <demiobenour(a)gmail.com>
> wrote:
>
> > I have almost always seen it *increase* download times,
>
> In my experience, while the download times may
> be (slightly) reduced, on a number of my (slower)
> systems, the rebuild of the rpm itself took longer
> then it would have taken to download the full rpm.
>
> As with all else, your mileage WILL
> vary._______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
2 years, 6 months
