https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209674
--- Comment #4 from bourne.ident...@hotmail.com
---
It so happened that I recently had to purchase a new keyboard (Cooler Master
CMStorm) for a feature I needed - LED backlights. The new keyboard is fairly
expensive, and unfortunately, the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209674
Anthony Jenkins changed:
What|Removed |Added
CC||scoobi_...@yahoo.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200938
Kubilay Kocak changed:
What|Removed |Added
Assignee|freebsd-usb@FreeBSD.org |gleb...@freebsd.org
F
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200938
Kubilay Kocak changed:
What|Removed |Added
Flags|mfc-stable11? |
--- Comment #21 from Kubilay Koca
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209674
--- Comment #6 from bourne.ident...@hotmail.com
---
The output (generated by { usbdump -i usbus2 -f 4 -s 65536 -vvv; } >>
usbdump.txt) below has an anomaly event that happened around 20:58:25 by my
local time. Please let me know by email i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209674
--- Comment #7 from Hans Petter Selasky ---
Hi,
The ERR=STALLED indicates a USB error. We expect 8-bytes, while the device only
send 6, and in addition STALLED. Is the device connected directly to the USB
port or through some kind of USB H
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209674
--- Comment #8 from Hans Petter Selasky ---
Created attachment 172246
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172246&action=edit
Possible fix
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
Bug ID: 211205
Summary: USB_ERR_TIMEOUT errors after upgrade from 10.2
Product: Base System
Version: 10.3-RELEASE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
--- Comment #2 from Doug ---
Not sure I want to just blindly copy the entire 10.2 USB subsystem inside a
10.3 tree. Even if it works, it doesn't tell me much other than someone hosed
the 10.3 USB subsystemwhich is pretty much what I kn
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
Kubilay Kocak changed:
What|Removed |Added
Product|Community |Base System
Assignee|i..
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208791
--- Comment #2 from a...@inferiorhumanorgans.com ---
With this kernel:
FreeBSD bloaty 10.3-RELEASE-p4 FreeBSD 10.3-RELEASE-p4 #0: Sat May 28 12:23:44
UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64
And h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208791
--- Comment #3 from Hans Petter Selasky ---
Hi,
Do you have a link where such a device can be bought? Used or new?
There has been updates in the USB audio driver which might have broken your
device, but fixed others.
--HPS
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
Mark Linimon changed:
What|Removed |Added
CC|freebsd-am...@freebsd.org |
Keywords|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
Mark Linimon changed:
What|Removed |Added
CC|freebsd-am...@freebsd.org, |
|freebsd-usb@Fre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209674
Mark Linimon changed:
What|Removed |Added
Keywords||patch
CC|freebsd-am
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208959
--- Comment #4 from Jamie Ivanov ---
Bueller?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
--- Comment #2 from Carlos Martinez ---
Created attachment 173483
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173483&action=edit
Devinfo
hope this helps
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
--- Comment #3 from Carlos Martinez ---
Created attachment 173484
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173484&action=edit
pciconf
here's pciconf
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
--- Comment #4 from Carlos Martinez ---
Created attachment 173485
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173485&action=edit
dmesg.boot
Thank you!
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
--- Comment #5 from Carlos Martinez ---
I have a creative X-fi pci card which is not working either... but my main
concern is the tascam. thank you.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211716
Bug ID: 211716
Summary: [PATCH] USB Driver didn't get the right size
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Keyword
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211716
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: sephe
Date: Thu Aug 11 03:12:57 UTC 2016
New revision: 303944
URL: https://svnweb.freebsd.org/changeset/base/303944
Log:
cam/da: Add quirk for I-O Data
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
--- Comment #7 from Carlos Martinez ---
Created attachment 173706
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173706&action=edit
usbconfig
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
--- Comment #8 from Carlos Martinez ---
Created attachment 173707
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173707&action=edit
usbconfigdump
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
--- Comment #9 from Carlos Martinez ---
Ok, there they are
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211247
--- Comment #10 from Hans Petter Selasky ---
Your device is not attaching because it is using vendor specific interface
class values (0xff).
Does this help:
usbconfig -d ugen4.2 add_quirk UQ_AU_VENDOR_CLASS
Then re-plug the device.
--HP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
Mark Linimon changed:
What|Removed |Added
Keywords||regression
Component|kern
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #1 from Aleksander Alekseev ---
For the record - bug doesn't reproduce if you disconnect Logitech adapter
before suspend and connect it back after resume.
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
Bug ID: 211967
Summary: USB Keyboard is detected as USB mouse when USB mouse
is plugged in at boot
Product: Base System
Version: 10.3-STABLE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
Anthony Jenkins changed:
What|Removed |Added
CC||scoobi_...@yahoo.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
k...@denninger.net changed:
What|Removed |Added
CC||k...@denninger.net
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #3 from nc ---
Created attachment 173828
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173828&action=edit
login prompt when unplugging/plugging in keyboard when mouse is plugged in at
boot
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #4 from nc ---
(In reply to Anthony Jenkins from comment #1)
Wow, thanks for jumping on this so fast :)
* The keyboard is a WhiteFox Mechanical Keyboard and the mouse is a SteelSeries
Kinzu v2.
* The problem still exists with o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #6 from nc ---
(In reply to Hans Petter Selasky from comment #5)
OK, I'll try that. Should I run those commands for the keyboard or for the
mouse?
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #7 from Hans Petter Selasky ---
For wrongly detected mouse you add:
usbconfig -d X.Y add_quirk UQ_UMS_IGNORE
For wrongly detected keyboard you add:
usbconfig -d X.Y add_quirk UQ_KBD_IGNORE
Given that keyboard and mouse is not
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #9 from k...@denninger.net ---
See the bug I linked; I reverted that change and the problem with IPKVM
keyboards disappeared.
You might want to try reverting this change on your system.
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #8 from nc ---
(In reply to Hans Petter Selasky from comment #7)
Hmm... it doesn't seem to work.
I also realized that this issues is affecting any USB keyboard I plug in
(including other brands/models). Maybe it has something t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #10 from nc ---
(In reply to karl from comment #9)
Thanks, I'll try that. Is there a "proper" way of building the kernel from a
specific commit, or is it just an svn checkout to a random directory, then
build it from there? (I c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #11 from k...@denninger.net ---
(In reply to nc from comment #10)
>From /usr/src...
svn log -v -r xxx (will tell you which file(s) got changed, in this case
just one file in the USB driver set)
Then, after figuring out whe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #12 from k...@denninger.net ---
(In reply to nc from comment #10)
BTW if your machine is multi-core (and most are these days) you may want "make
-jx buildkernel" instead of just "make buildkernel"; the "-jx" (replace "x"
with th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #13 from nc ---
Awesome, I think that solved it. Should I leave this bug open or close it then?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
--- Comment #14 from k...@denninger.net ---
(In reply to nc from comment #13)
Probably ought to merge it with my other report
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
Bug ID: 212021
Summary: xhci(4) broken on big-endian systems
Product: Base System
Version: CURRENT
Hardware: ppc
OS: Any
Status: New
Severity: Affec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208791
--- Comment #4 from a...@inferiorhumanorgans.com ---
I believe I purchased mine from Amazon, although the version I have (1.2, IIRC)
has since been discontinued.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
--- Comment #2 from Nathan Whitehorn ---
(In reply to Hans Petter Selasky from comment #1)
You misunderstand, I think. This is a bog-standard PCI-E XHCI card with
little-endian registers. The driver just doesn't work when the CPU is
big-en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
--- Comment #3 from Hans Petter Selasky ---
Got it. OK, Look at this error:
xhci: output context at 831a000
xhci: invalid input context control 0003
13236@1471749323.871077:usb_xhci_queue_event v 0, idx 8, ER_COMMAND_COMPLETE,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
--- Comment #4 from Nathan Whitehorn ---
(In reply to Hans Petter Selasky from comment #3)
That is probably true, but I think that can't be the problem in this case, for
two reasons:
1. The host CPU for my QEMU is little-endian, so that ch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
--- Comment #5 from Hans Petter Selasky ---
The qemu prints the values x=0 and y=3 in hex. And the check is (x != 0 || y !=
3) which I find very odd.
I'll check if we are writing a 32-bit field with 64-bit ops.
--HPS
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
--- Comment #6 from Nathan Whitehorn ---
(In reply to Hans Petter Selasky from comment #5)
The QEMU code that is printing the error is this in xhci_configure_slot():
if ((ictl_ctx[0] & 0x3) != 0x0 || (ictl_ctx[1] & 0x3) != 0x1) {
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
--- Comment #7 from Hans Petter Selasky ---
Created attachment 173916
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=173916&action=edit
Fix XHCI compatibility with QEMU
Hi,
Can you test the attached patch. Looks like a XHCI com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
Hans Petter Selasky changed:
What|Removed |Added
Summary|xhci(4) broken on |xhci(4) broken with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
--- Comment #8 from Nathan Whitehorn ---
(In reply to Hans Petter Selasky from comment #7)
That doesn't seem to help. The ppc64 QEMU behavior seems identical.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
--- Comment #9 from Hans Petter Selasky ---
Hi,
I looked into this yesterday and there are some missing pieces in the QEMU
control endpoint handling code. FreeBSD sends the SETUP, DATA and STATUS stage
as separate events, while QEMU expect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
--- Comment #10 from commit-h...@freebsd.org ---
A commit references this bug:
Author: hselasky
Date: Mon Aug 22 10:21:25 UTC 2016
New revision: 304597
URL: https://svnweb.freebsd.org/changeset/base/304597
Log:
Fix for invalid use of bit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212043
Mark Linimon changed:
What|Removed |Added
CC|freebsd-am...@freebsd.org |
Assignee|freebsd-b...@fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212043
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212043
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #2 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
--- Comment #11 from commit-h...@freebsd.org ---
A commit references this bug:
Author: hselasky
Date: Mon Aug 22 19:32:50 UTC 2016
New revision: 304629
URL: https://svnweb.freebsd.org/changeset/base/304629
Log:
Don't separate the status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212021
Hans Petter Selasky changed:
What|Removed |Added
Attachment #173916|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
--- Comment #3 from Hans Petter Selasky ---
Hi,
You might find the following two patches useful candidates for testing:
https://svnweb.freebsd.org/changeset/base/304597
https://svnweb.freebsd.org/changeset/base/304629
--HPS
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212043
Andriy Gapon changed:
What|Removed |Added
CC||tr...@freebsd.org
Assigne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211967
Kubilay Kocak changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #2 from Aleksander Alekseev ---
I've found very easy way to reproduce this issue. You need a laptop with
working suspend/resume and Logitech K360 keyboard.
1. Reboot the system
2. Login as root
3. Suspend: acpiconf -s 3
4. Turn
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
Aleksander Alekseev changed:
What|Removed |Added
Summary|11.0-RC1: Exception:|Logitech K360 keyboard:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170358
Tobias Kortkamp changed:
What|Removed |Added
CC||t...@tobik.me
--- Comment #6 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170358
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212256
Bug ID: 212256
Summary: xhci controllers cannot be used with ppt
Product: Base System
Version: 10.3-STABLE
Hardware: Any
OS: Any
Status: New
Severit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212256
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #4 from Aleksander Alekseev ---
I'm sorry but I'm having some problems getting a backtrace.
There are:
```
dumpdev="AUTO"
ddb_enable="YES"
```
... lines in /etc/rc.conf
I can't enter debugger using sysctl:
```
$ sudo sysctl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #5 from Hans Petter Selasky ---
Bruce Evans has recently fixed some issues using the USB keyboard from the
debugger. Are you running the latest 12-current?
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
k...@denninger.net changed:
What|Removed |Added
CC||k...@denninger.net
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #7 from Aleksander Alekseev ---
hselasky@,
> Are you running the latest 12-current?
No, I'm running 11.0-RC2
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #8 from Hans Petter Selasky ---
Can you test a 12-current kernel and see if this problem is fixed?
--HPS
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156000
Andriy Voskoboinyk changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #9 from Aleksander Alekseev ---
Here is some additional debug information, just for the record (still on
11.0-RC2).
dmesg right after resume:
http://afiskon.ru/s/c1/e5cf238331_usb1.jpg
dmesg after reconnecting USB adapter:
h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212256
--- Comment #2 from commit-h...@freebsd.org ---
A commit references this bug:
Author: hselasky
Date: Thu Sep 8 09:50:04 UTC 2016
New revision: 305589
URL: https://svnweb.freebsd.org/changeset/base/305589
Log:
MFC r281499:
Modify the r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212256
Hans Petter Selasky changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170358
Hans Petter Selasky changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170358
--- Comment #8 from commit-h...@freebsd.org ---
A commit references this bug:
Author: hselasky
Date: Thu Sep 8 10:10:05 UTC 2016
New revision: 305590
URL: https://svnweb.freebsd.org/changeset/base/305590
Log:
Correctly map the USB mouse
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
--- Comment #4 from Hans Petter Selasky ---
Ping - were you able to test the above mentioned patches?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
--- Comment #5 from Doug ---
(In reply to Hans Petter Selasky from comment #4)
No. Unfortunately my work schedule has simply not permitted evaluating them.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
--- Comment #6 from Hans Petter Selasky ---
Hi,
These patches have now been MFC'ed to 10-stable.
--HPS
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
--- Comment #7 from Doug ---
While playing with this again today I noticed something I didn't report earlier
-- when the machine initially boots into the bootloader and the bootloader is
counting down, my keyboard works and I can press retu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
--- Comment #8 from Hans Petter Selasky ---
The bootloader is using the BIOS USB code. Try disabling USB legacy support in
the BIOS.
BTW: The patches are in 10-stable not the release branches.
--HPS
--
You are receiving this mail becaus
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211205
--- Comment #9 from Doug ---
(In reply to Hans Petter Selasky from comment #8)
> Try disabling USB legacy support in the BIOS.
What will that do in this context? Not opposed to trying it. I just want to
know what your aim is in suggestin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #10 from Aleksander Alekseev ---
Ok, here are a few updates on this issue.
1. I solved all issues regarding entering KDB and writing kernel core dumps.
Now I can provide really any debug information you might need. In case anyo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
Aleksander Alekseev changed:
What|Removed |Added
Summary|Logitech K360 keyboard: |[11.0-RC2, 12.0] Logitech
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
Aleksander Alekseev changed:
What|Removed |Added
Summary|[11.0-RC2, 12.0] Logitech |[11.0-RC2, 12.0]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #11 from Hans Petter Selasky ---
Hi,
Are there any settings in the BIOS for USB, like Legacy support. Can you turn
them off? Does it make any difference?
Maybe you could just "diff -ur" the RC1 and 11-0-BETA4 sources and look
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #12 from Hans Petter Selasky ---
Just guessing, that some PCI hotplug support was merged to 11.0:
https://svnweb.freebsd.org/changeset/base/304434
Can it be the cause?
--HPS
--
You are receiving this mail because:
You are t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
--- Comment #13 from Aleksander Alekseev ---
hselasky@,
There is indeed "Legacy USB support" option. Currently I disabled this options,
however it doesn't make any difference.
Just in case I took pictures of all BIOS settings.
Info:
htt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211895
Aleksander Alekseev changed:
What|Removed |Added
Summary|[11.0-RC2, 12.0]|[11.0-RC2, 12.0]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170358
--- Comment #10 from commit-h...@freebsd.org ---
A commit references this bug:
Author: hselasky
Date: Thu Sep 15 08:34:17 UTC 2016
New revision: 305828
URL: https://svnweb.freebsd.org/changeset/base/305828
Log:
MFC r305590:
Correctly m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170358
--- Comment #11 from commit-h...@freebsd.org ---
A commit references this bug:
Author: hselasky
Date: Thu Sep 15 08:35:46 UTC 2016
New revision: 305829
URL: https://svnweb.freebsd.org/changeset/base/305829
Log:
MFC r305590:
Correctly m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=170358
--- Comment #12 from commit-h...@freebsd.org ---
A commit references this bug:
Author: hselasky
Date: Thu Sep 15 08:37:20 UTC 2016
New revision: 305830
URL: https://svnweb.freebsd.org/changeset/base/305830
Log:
MFC r305590:
Correctly m
601 - 700 of 2842 matches
Mail list logo
