Now I did another 'power cycle..and the devices are not there ?'
dave@withycombe:~$ ls -l /dev/ttyU*
ls: cannot access '/dev/ttyU*': No such file or directory
dave@withycombe:~$ ls -l /dev/ttyU*
ls: cannot access '/dev/ttyU*': No such file or directory
dave@withycombe:~$ lsusb
Bus 002 Device 001:
I have a Huawei usb dongle and after a power cycle reboot all appears
good:-
dave@withycombe:~$ uname -a
Linux withycombe 4.4.0-30-generic #49-Ubuntu SMP Thu Jun 30 20:51:32 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
dave@withycombe:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ub
dave@withycombe:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp.
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 12d1:1f01 Huawei Technologies Co., Ltd. E353/E3131 (Mass
storage mode)
Bus 00
An update: After some time, working, the usb mouse freezes from time to
time. I return to 3.13 :(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1435028
Title:
Kernel does not detect alr
I'm using 14.04.3 on Dell XPS 13. I just updated the kernal to 3.19 as
recommended on Dell's forum to try and solve my issue with the wifi not
turning on after suspend. I didn't have any boot issues with the
connected USBs (yet) but I did noticed an issue after returning from
suspend. Hope this hel
I cannot speak for the bug opener, but for me this bug has been resolved
(or it resolved itself otherwise, don't know). So you can safely ignore
my previous post from now. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
I freshly installed 15.04 about a week ago (my kernel is
19.0-22-generic) and am experiencing similiar behaviour, with some
additional symptoms to those described already:
- When the problem occurs for me, startup time spent on the loading screen
("colored dots") goes up from less than a sec
I happened again after rebooting the first time into the 3.19.0-14
kernel yesterday. So it is not solved yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1435028
Title:
Kernel does no
I am currently running on 3.19.3 upstream and the bug did not occur. But
I have to point out that the bug only occurred sometimes with the latest
Ubuntu vivid kernel. I do not know yet how to reliably trigger this bug,
it seems it needs some special conditions to happen.
--
You received this bug
Can you also test the latest 3.19 upstream stable kernel? This will tell
us if the fix in 4.0-rc5 was also sent for inclusion in the stable
releases. It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.3-vivid/
** Tags added: needs-bisect
--
You received this bug noti
The issue first happened after upgrading to vivid from utopic. The
utopic kernel did not show this behaviour.
I did a short test with the upstream kernel and the issue could not be
reproduced with it. Booting back into the Ubuntu kernel 3.19.0-9 on the
other hand exhibited this issue again.
** Ch
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1435028
Title:
Kernel does not detect already connected USB devices on boo
13 matches
Mail list logo