Here's dmesg with #33~lp1783906DEBUGv2: https://paste.ubuntu.com/p/jK6zjKjtqc/
I expected this to have the bug and only print additional debug info, but it
seems this fix the bug. The second drive (WDC) came up and I could mount it's
partitions and read info from them.
Just to make sure, I did a
Here's dmesg with 4.15.0-30-generic #33~lp1783906DEBUG running for 10 mins:
https://paste.ubuntu.com/p/Qc9Kpb62ch/
--
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/1783906
Title:
Linux 4.1
Your test kernel with commit 2dc0b46b5ea3 does indeed fix the issue with
the WD HDD. Here's the dmesg with your test kernel:
https://paste.ubuntu.com/p/745NscYFJh/
As you can see at the top i was using: "[0.00] Linux version
4.15.0-29-generic (root@kathleen) (gcc version 7.3.0 (Ubuntu
7.3.
I went ahead and test this bug from linux 4.15rc1 and up to linux 4.15rc5.
What i found is that linux 4.15rc3 is the last RC version where this bug
doesn't occur, and linux 4.15rc4 is the first RC version where this bug occur.
Here's the dmesg with linux 4.15rc3 and the WD HDD working:
https://p
I first experienced this issue while testing the second beta of ubuntu
18.04, as i explained in the original bug report this issue doesn't
happen if i use linux 4.14
I've installed linux 4.18rc6 as explained in the wiki, but the WD HDD still
won't come up.
Here's the dmesg with this kernel: https
I forgot to mention the Western Digital hard drive has always been slow
to actually show up, and I’ve always gotten those "COMRESET failed, link
is slow to respond" messages since I bought it.
And two details I forgot to mention about the hard drives:
1 The Toshiba hard drive that works is formatt
Public bug reported:
I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200 the
second backup hard drive is a Western Digital WD5003AZEX. I installed
lubuntu 18.04.1 on the Toshiba HDD and it boots just fine, the issue is
with the second hard drive, when installing the WD HDD wouldn't
Hi Christopher,
Don't have access to the computer in question just now, but I could try to get
to it soon. It would be great to know if there's a chance that this issue will
be fixed before I take more time on it however.
--
You received this bug notification because you are a member of Kernel
updated to 513 and still same problem.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1372143
Title:
[Asus X551MA] B
Can anyone provide some simple steps on how to identify the information
I need to map these properly? I've poked around with google, and found
for example a wiki page on evtest here:
https://wiki.ubuntu.com/DebuggingTouchpadDetection/evtest
I installed and ran evtest, but the wiki entry makes no
same problems with latest upstream kernel, 3.17-rc6.
While running acpi_listen, I can see that the following fn hotkeys show
no response:
fn+F2 wifi
fn+F5 decrease brightness
fn+F6 increase brightness
fn+F8 screen output
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.17-
Just discovered that I can manually change brightness by changing the
integer value in:
/sys/class/backlight/intel_backlight/brightness
--
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/13721
Public bug reported:
Just installed Ubuntu 14.04.1, have run the latest updates and the
brightness and wifi fn hotkeys don't work.
Here's a complete list of working/non working fn hotkeys:
fn + f1 (suspend) yes
fn + f2 (wifi) no
fn + f5 (decrease brightness) no
fn + f6 (increase brightness) no
f
13 matches
Mail list logo
