| Summary: | aTI-USB ports are detected, but don't work | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | salim salim <almusalimalmusalimah> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | djmarian4u, marja11, tmb |
| Version: | 1 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
salim salim
2011-12-23 19:32:15 CET
@ salim Sorry for replying so late. Nice picture, I guess it was too big to upload here. Please give the output of lsusb (If the command doesn't work, try again after installing usbutils) which device(s) did not work when being plugged in? printer? wireless modem? did you try with a simple usb stick? Keywords:
(none) =>
NEEDINFO Marja van Waes i am sorry that i cant help you now to know a lot more info .... take a look here https://forums.mageia.org/en/viewtopic.php?f=7&t=1583&p=11775&hilit=ati+usb#p11775
Marja Van Waes
2012-02-14 12:10:25 CET
CC:
doktor5000 =>
(none) (In reply to comment #2) > Marja van Waes > > i am sorry that i cant help you now > > to know a lot more info .... > > take a look here > > https://forums.mageia.org/en/viewtopic.php?f=7&t=1583&p=11775&hilit=ati+usb#p11775 Sorry, that doesn't contain enough information. Please get your friend to reply to the questions in comment 1, or we'll have to close this report as old two weeks from now
Dan Joita
2012-03-07 11:15:21 CET
CC:
(none) =>
djmarian4u will i am sorry to say this but he remove the distro and install another one rather than mageia (In reply to comment #4) > will i am sorry to say this > > but he remove the distro and install another one rather than mageia Thanks for the feedback, Salim. We don't have enough information to further investigate this bug. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Status:
NEW =>
RESOLVED |