When I try to connect my ER9XPro USB device to my Fedora 21 server, it fails
to connect with:
[1024110.158374] usb 1-7: new full-speed USB device number 15 using xhci_hcd
[1024110.312216] usb 1-7: device descriptor read/64, error -71
[1024110.565928] usb 1-7: device descriptor read/64, error -71
[1024110.819660] usb 1-7: new full-speed USB device number 16 using xhci_hcd
[1024110.973497] usb 1-7: device descriptor read/64, error -71
[1024111.227212] usb 1-7: device descriptor read/64, error -71
[1024111.480928] usb 1-7: new full-speed USB device number 17 using xhci_hcd
[1024111.482576] usb 1-7: Device not responding to setup address.
[1024111.693836] usb 1-7: Device not responding to setup address.
[1024111.894473] usb 1-7: device not accepting address 17, error -71
[1024112.047316] usb 1-7: new full-speed USB device number 18 using xhci_hcd
[1024112.047415] usb 1-7: Device not responding to setup address.
[1024112.298755] usb 1-7: Device not responding to setup address.
[1024112.498815] usb 1-7: device not accepting address 18, error -71
[1024112.498836] usb usb1-port7: unable to enumerate USB device
It is a direct connection (no hub).
Cheers and thanks,
I was apparently missing something like the raid1 kernel
module in the initramfs in my fedora 21 partition, but
I disabled the mdmonitor service and removed the raid
filesystem from the /etc/fstab, yet the system still
could not boot. It spent several minutes trying to recognize
the raided disks then went into the dracut shell.
Should it really be utterly impossible to boot a system
that merely has raided disks connected to it which no
one is trying to reference? Should I make a kernel bug
I currently locally mirror Fedora release trees, as well as updates
and testing trees, and are all nfs mounted. I would like to do the 2
1 - What to issue at boot to include updates and testing trees? I
already use nfs parameter for the release tree.
2 - What do I do to use a newer anaconda package from the testing tree
instead of the one in the main tree? I guess I want to include a new
image to use from the newer anaconda? I already use the boot.iso from
the release tree and guess I need to create a new/custom image?
Thanks ahead of time,
"Best lil town on Earth!"
What is the best way in Fedora to handle the following situation?
- Package X depends on package Y
- Package Y is actually installed through custom compiling it (in $HOME/bin)
yum install X
will want to install Y
Specifically in my case X is kdenlive and Y is ffmpeg.
I compiled ffmpeg manually to have jack audio  support by following
the guide on the ffmpeg website . This means ffmpeg is in
~/bin/ffmpeg (also in my PATH). Before doing this I removed (with yum)
ffmpeg. Now if I try to:
yum install kdenlive
it will want to install ffmpeg.
Any suggestions, ideas, pointers are welcome.
 http://www.jackaudio.org/ (ffmpeg will add jack support if it finds
the jack development files)
Have a student with a Toshiba Satellite L305 and tried to install Fedora 20
and 21 by using both DVD and Flash. In both cases it would come up with
the grub screen, but both the regular install and the basic video would result
in strange graphics and no response??
I use a fail-safe option with my disk imaging project, so tried adding its
options to the boot line.
noapic noacpi pnpbios=off acpi=off pci=noacpi
Installation went thru just fine, and machine is working fine.
In checking the grub.cfg file on the system, it only included these two options.
Don't know how common this issue might be, but perhaps Fedora should add
a fail-safe option to the installations, so that if the regular ones don't work,
they could at least try this one.
Don't know why this caused the installation to fail, but it seems to be a simple
Not sure if the people that could change this are on the list, or where I could
Try to get students to check out Linux, and have an install fail for a reason
like this would probable stop a lot of users from continuing.
Michael D. Setzer II - Computer Science Instructor
Guam Community College Computer Center
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
Number of Seti Units Returned: 19,471
Processing time: 32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)
ROSETTA 27363592.026654 | SETI 47906557.533588
ABC 16613838.513356 | EINSTEIN 55609387.365699
On 26.03.2015 08:21, Lennart Poettering wrote:
> On Wed, 25.03.15 13:03, poma (pomidorabelisima(a)gmail.com) wrote:
>> On 23.03.2015 05:25, Lennart Poettering wrote:
>>> On Tue, 17.03.15 14:11, poma (pomidorabelisima(a)gmail.com) wrote:
>>>> On 17.03.2015 13:08, poma wrote:
>>>>> On 17.03.2015 11:56, Olav Vitters wrote:
>>>>>> On Tue, Mar 17, 2015 at 08:08:04AM +0100, Niels Weber wrote:
>>>>>>> Is there any way that I missed so far? Or is it simply not possible?
>>>>>> Please try:
>>>>>> $ loginctl list-sessions
>>>>>> $ loginctl lock-session $ID
>>>>>> $ loginctl unlock-session $ID
>>>>> Does it work for you?
>>>> Mister Lennart, can we expect in the near future to be feasible?
>>>> $ /usr/lib/systemd/systemd --version
>>>> systemd 219
>>> Sorry, but I miss the context. What are you asking for?
>> Exactly, content is missing, "loginctl un/lock-session $ID" is doing nothing, only placeholding, waiting for Baobab.
> Maybe your desktop environment does not listen to the logind signals
> for locking/unlocking? GNOME does, not sure about others.
This is a good idea to RFE.
Thanks for answering.
For my regular user I have to strike hard the keyboard for it to work.
My root user works as always.
Looks like one of my kids just touched something but I haven't find a value
for that property in the keyboard configuration UI
(systemTools/systemSettings/hardware/keyboard) Any other idea?
OK I'm going to display some total KDE ignorance here, hopefully a KDE
user can answer this.
On GNOME, gnome-software + packagekit + systemd work together to make
the user aware of software updates. This includes any installed
applications, as well as OS + kernel updates. The user clicks on
Restart & Install in gnome-software, or chooses that option in the
reboot/poweroff panel. The system reboots, a special systemd offline
updates target is triggered, and packagekit installs all the
previously downloaded rpms with a progress indicator, then reboots
So I'm wondering what the equivalent is on KDE, with about that much detail.
I just installed Fedora-21 and xfce. Install was from
the regular live x64 download, not the xfce spin.
I have an odd problem with checkboxes in gui dialogs:
they don't show any checkmarks. If I click on a
checkbox, a checkmark will appear for a fraction of
a second then disappear. From the program's behavior
I can tell that the setting got set but it is obviously
difficult if one can not see which boxes are checked
in a dialog and which aren't.
This problem seems to be limited to Gnome apps (the ones
with the new -- at least to someone coming from F15 --
and really unpleasant UI design). For example, brasero
exhibits the effect but k3b doesn't.
Does this problem ring a bell with anyone?