ace lo inet loopback
The wireless interface doesn't require any parameters. Otherwise I'm
glad that the fix worked for you as well.
/Dennis
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
32) though, so you might
need to make a new one for your version [168c:041]. You should also
check out some other Atheros bug reports for the card, but since your PC
relatively new, it might be a new issue.
/Dennis
--
You received this bug notification because you are a member of Kernel
Packa
as hardware
acceleration support for this PC is currently only supported there.
The same problem exists in this version too and I'm able to reproduce the
issue.
Hoping to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
as hardware
acceleration support for this PC is currently only supported there.
The same problem exists in this version too and I'm able to reproduce the
issue.
Hoping to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
ect me if I'm wrong. As
I'm not yet familiar with this bug reporting system, could someone
advice me further?
PS. I'm glad you figured it out Oliver, sorry for the extra hassle.
/Dennis
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
be marked with "patch released" or something similar and possibly the
fix merged upstream? I'm not sure how to do this (or what to do next) so
could someone give an advice?
/Dennis
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
lude
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.2-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USERPID
laptops seem to include the
same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
+ ---
+ ApportVersion: 2.19.2-0ubuntu6
+ Architecture: amd64
ing to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.2-0ubuntu6
Ar
ing to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.2-0ubuntu6
Ar
Hoping to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.
ing to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.
ing to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.
ing to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.2-0ubuntu6
Ar
Hoping to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.
Hoping to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.
Hoping to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.
roblem exists in this version too and I'm able to reproduce the
issue.
Hoping to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (devel
the
issue.
Hoping to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.
nch of Ubuntu 16.04 as hardware
acceleration support for this PC is currently only supported there.
The same problem exists in this version too and I'm able to reproduce the
issue.
Hoping to get this fixed, as many other new laptops seem to include
the same wireless card.
/Den
this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.2-0ubuntu6
Architect
Hoping to get this fixed, as many other new laptops seem to include
the same wireless card.
/Dennis
Current system information:
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
---
ApportVersion: 2.19.
Still same message with 4.3-rc5:
Oct 14 09:42:43 DK-ThinkPad kernel: [1.009399] tpm_tis 00:05: A TPM error
(6) occurred attempting to read a pcr value
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
I haven't noticed it.
** 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/1449079
Title:
TPM error (6) occurred
Still occurs after BIOS update.
--
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/1449079
Title:
TPM error (6) occurred attempting to read a pcr value
Status in linux package in Ubuntu:
G6ETB1WW (2.71 )
04/23/2015
** 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/1449079
Title:
TPM error (6) occurred
Sad news: I had the same crash with the 3.19.8 kernel a couple of times now.
The obvious symptom is that the screen turns off and searches for a new signal
source (HDMI/VGA/etc.).
This time it happened when zooming in Firefox (CTRL+Mousewheel) while a Youtube
video was loading in a background
Testing with ppa kernel 3.19.8-031908ckt6-generic seems to resolve the issue.
At least no more crashes/freezes have occurred since then.
I have added the 'kernel-fixed-upstream" tag as requested.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete =>
Public bug reported:
Full freeze, screen turns off, happened when Youtube video running in
background tab in Firefox.
Hard reset necessary.
Multiple crashes/freezes have occurred updating linux kernel/image from
3.19.0-28 to 3.19.0-29.
All of them have happened when Firefox was running playing
** Tags added: kernel-fixed-upstream
** Changed in: linux-lts-utopic (Ubuntu)
Status: Incomplete = Opinion
** Changed in: linux-lts-utopic (Ubuntu)
Status: Opinion = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
Regression from at least:
linux-image-3.16.0-45-generic=3.16.0-45.60~14.04.1
to:
linux-image-3.16.0-47-generic=3.16.0-47.63~14.04.1
On an Intel Xeon Workstation with an Intel IGB Gigabit Ethernet Adapter,
the network connection is never stable, as the Adapter regularly
** Tags added: kernel linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1488024
Title:
[Regression] From 3.16.0-45 to -47: Intel IGB Tx Unit Hang network
adapter reset
Thanks. Problem has not gone away but it is a lot better now. Still
have to power down and reboot sometimes to wake up computer, but
downloads finish.
From: Ilari 1380...@bugs.launchpad.net
To: dennis.dugga...@yahoo.com
Sent: Wednesday, June 3, 2015 3:58 AM
Subject: [Bug 1380221] Re:
** 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/1453565
Title:
package linux-image-3.19.0-17-generic 3.19.0-17.17
Bug also exists in upstream kernel. Error message was also there before
Ubuntu 15.04 upgrade. See also bug #1427860.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of
Public bug reported:
Issue was already reported in #1427860 but penalvch asked for a new bug.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
Alright new bug entered #1449079
--
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/1427860
Title:
tpm error
Status in linux package in Ubuntu:
Incomplete
Bug description:
I see this
Installed latest upstream kernel 4.0.0-04.201504121935. Same problem
there.
BIOS: G6ETB0WW (2.70 ) 02/05/2015
** Tags removed: bios-outdated-1.20
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.0
latest-bios-2.70
** Changed in: linux (Ubuntu)
Status:
That commit seems to be the cause of the error message. However I just
noticed that bluetooth is still working. I was confused because the
indicator icon was gone after 15.04. release upgrade but I was able to
start it manually and connection works although the error message is
present.
--
You
There was no firmware conversion necessary with Ubuntu 14.10 and 3.16
kernel.
--
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/1447790
Title:
bluetooth not working after upgrading to
Not working with 4.0 kernel: /dev/mem: No such file or directory
--
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/1447790
Title:
bluetooth not working after upgrading to 15.04
Status in
I also updated BIOS to 2.70 without effect.
--
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/1447790
Title:
bluetooth not working after upgrading to 15.04
Status in linux package in
Output with 3.19 kernel:
G6ETB0WW (2.70 )
02/05/2015
--
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/1447790
Title:
bluetooth not working after upgrading to 15.04
Status in linux
with 3.19 kernel:
G6ETB0WW (2.70 )
02/05/2015
--
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/1447790
Title:
bluetooth not working after upgrading to 15.04
Status in linux package in
with 3.19 kernel:
G6ETB0WW (2.70 )
02/05/2015
** 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/1447790
Title:
with 3.19 kernel:
G6ETB0WW (2.70 )
02/05/2015
--
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/1447790
Title:
bluetooth not working after upgrading to 15.04
Status in linux package in
Installed latest upstream kernel 4.0.0-04.201504121935. Same problem here:
kernel: [0.00] Linux version 4.0.0-04-generic (kernel@gomeisa) (gcc
version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201504121935 SMP Sun Apr 12
23:36:33 UTC 2015
kernel: [8.997867] bluetooth hci0:
Public bug reported:
Similar issue was already reported as #1406014
After upgrading to 15.04 bluetooth is not working anymore:
kernel: [9.421402] bluetooth hci0: Direct firmware load for
brcm/BCM20702A0-0a5c-21e6.hcd failed with error -2
kernel: [9.421404] Bluetooth: hci0: BCM: patch
Hmm...I've updated to 3.19.2 and the Touchpad seems does it work. But
after a few seconds the left button doesn't work anymore...only after
clicking the right button and then it works for a few time. So on and so
on.
--
You received this bug notification because you are a member of Kernel
@Vincent Jaubert
Where can I read the patch about to enable the touchpad? Thanks in advanced...
--
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/1402393
Title:
Touchpad elantech on
*** This bug is a duplicate of bug 1252121 ***
https://bugs.launchpad.net/bugs/1252121
Can confirm with 14.04/14.10/15.04, Thinkpad X121e, Intel WiFi 7260 N.
Network is avaible after suspend but often fails to associate and to
therefore to connect. This problem does _NOT_ exist with
*** This bug is a duplicate of bug 1252121 ***
https://bugs.launchpad.net/bugs/1252121
Can confirm using pm-suspend works ALWAYS, while Suspend from Unity
menu is broken.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in
I tracked down the issue where WiFi would fail after suspend in that it
doesn't associate anymore (tries to connect but fails), and it's a bug
in wpa-supplicant that was fixed in the current version (Ubuntu uses
2.1, newest is 2.3). Replacing Ubuntu's wpa-supplicant 2.1 with Debian's
*** This bug is a duplicate of bug 1252121 ***
https://bugs.launchpad.net/bugs/1252121
I tracked down the issue where WiFi would fail after suspend in that it
doesn't associate anymore (tries to connect but fails), and it's a bug
in wpa-supplicant that was fixed in the current version (Ubuntu
I've the same Laptop, an Fujitsu E554 and the same Problem(s).
I'm on Ubuntu 12.04 AMD64. Till Kernel 3.8.0* the Tochpad works, but without
the right Mousebutton.
This Site helps me:
http://superuser.com/questions/619582/right-elantech-touchpad-button-not-working-in-linux
Now I'm on Kernel
Ack, sorry everyone, I changed the status to Fix Released by accident
and now I can't change it back to Triaged. Can someone change it back?
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages,
By the way...
I wanted to apologize for the curt, arrogant and condescending part of
my post in #16 on this bug. I know those guys on the development lists
are busy and responding to many inquiries.
Still, I very much appreciate the cordial response from Bernie.
And, if anyone knows of a
pomidorabelis...@gmail.com offered this link:
https://lkml.org/lkml/2013/7/23/121
--
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/1376771
Title:
DisplayLink Attached Display Adapter and
response from linux-fbdev:
Hi Dennis,
Only drivers for DisplayLink's USB 2.0 generation chips (DL-1x5) are
available and in kernel. That Dell dock is using the newer DL-3x00
chips. There's no way to get the graphics portion working for Linux on
that.
Part of the reason is even for USB 2.0
I very much appreciate the cordial response from Bernie. Bernie Thompson
is a gentleman.
Much of the response in regards to seeking help from those who are
indeed the experts upstream was short, curt, arrogant and
condescending.
Getting help with bugs upstream is hard.
I would like to update
to get to market.
Thank you so much,
Dennis
--
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/1376771
Title:
DisplayLink Attached Display Adapter and Monitor Not Recognized
Status
linux-...@vger.kernel.org asked for outpu from lsusb -v:
Bus 002 Device 003: ID 04f2:b34c Chicony Electronics Co., Ltd
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass
Alan Stern's Response:
By the way, Alan. Thank you for looking at that. I'd really like to
get this working. --drg
Well, I'm not so much looking at this as trying to collect information
that will help the people who do know what to look for. The standard
information requested by the
information. Please let me know If I should post
to a different list or if this is OK to file in the bug system.
Thanks,
Dennis
[1.] One line summary of the problem:
Displaylink Attached Display Adapater and Monitor Not Recognized
[2.] Full description of the problem/report:
DisplayLink Plug and Play
but not until after asking first on the
mailling lists. My issue touches many parts usb/graphics/etc so I tried to
choose the most general list.
Below is my collected information. Please let me know If I should post
to a different list or if this is OK to file in the bug system.
Thanks,
Dennis
A participant on the list wanted my Xorg logs. i submitted:
On this device
DisplayLink Plug and Play Universal docking Station
DELL
Model: D3000
MFG: ACP075US
SN: 1309017059
I did have an hp keyboard and mouse also plugged in...
X.Org X Server 1.16.0
Release Date: 2014-07-16
[ 9.901] X
should post to a different list or if this is OK
to file in the bug system. Or, if since this chip set might be
considered newer, if should file a feature/enhancement request in the
bug system.
Thanks,
Dennis
[1.] One line summary of the problem:
Displaylink Attached Display Adapater and Monitor
Public bug reported:
DisplayLink Plug and Play Universal docking Station
DELL
Model: D3000
MFG: ACP075US
SN: 1309017059
All ports on the device are recocognized and function correctly except
the display adapter.
Description:Ubuntu Utopic Unicorn (development branch)
Release:14.10
Just downloaded and installed:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc7-utopic/linux-
image-3.17.0-031700rc7-generic_3.17.0-031700rc7.201409281835_amd64.deb
Same behavior. Displaylink Attached Display Adapater and Monitor Not
Recognized
** Tags added: kernel-bug-exists-upstream
I changed status to confirmed. I think this was a mistake for me to do
that as I am the reporter. Apologies if I did not follow correct
procedure.
But, it did not work with latest v3.17 kernel
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc7-utopic/linux-
Hi Joseph:
I will do that. But, need a hint. There seem to be MANY lists on kernel.org.
Which one is the right one?
--drg
On Thu, Oct 2, 2014 at 1:01 PM, Joseph Salisbury
joseph.salisb...@canonical.com wrote:
This issue appears to be an upstream bug, since you tested the latest
upstream
Version 3.16.1-031601.201408140014 of linux-image-3.16.1-031601-generic
does not show the 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.
The message appears (with the Ubuntu kernel) everytime the computer
returns from standby.
--
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/1356076
Title:
firmware: fw-04ca_2007.hcd will
Public bug reported:
Upon wakeup from standby, I see: firmware: fw-04ca_2007.hcd will not be
loaded, followed by Bluetooth: can't load firmware, may not work
correctly.
Reading several bugreports, it seems that I need to get that firmware
file from somewhere, but I do not know how. Thus I would
Hi,
this happens still in Trusty with all updates (todate: 13.07.2014, 20:00) and
kvm is unusable with this. We wanted to use kvm instead of virtualbox/vmware
but with this, you can forget that.
Why on Earth is it a wontfix?
--
You received this bug notification because you are a member of
Hi,
this problem happens (not very fast, but too) with QXL and Spice, just fyi
--
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/1080674
Title:
[QEMU] Corrupted desktop screen for raring
= QUIRK_MIDI_YAMAHA
},
{
.ifnum = 4,
.type = QUIRK_IGNORE_INTERFACE
},
{
.ifnum = -1
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional
Same for me. Sony vaio SVF1521KSNB with ubuntu 13.10 as well as 14.04.
ANy fix is appreciated .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1264311
Title:
BCM43142 bluetooth adapter
= QUIRK_MIDI_YAMAHA
},
{
.ifnum = 4,
.type = QUIRK_IGNORE_INTERFACE
},
{
.ifnum = -1
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass
,
.type = QUIRK_IGNORE_INTERFACE
},
{
.ifnum = -1
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID
and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass
}
}
}
},
Thanks and best regards,
Dennis
P.S. Here are some additional device informations:
$ lsusb -v -d 0499:1509
Bus 001 Device 002: ID 0499:1509 Yamaha Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
Public bug reported:
This a re-occurrence of bug 1304591.
J. Salisbury asked me to test kernel v3.14 but when I went to
wiki.ubuntu.com/KernelMaillineBuilds it was not at all obvious to me
what I should do to build and test. I am not a Unix/Linux/Ubuntu expert.
I need obvious.
I have been
Public bug reported:
Opened lid to un-suspend and found, what would be called in the windows
world, THE BLUE SCREEN OF DEATH. Had to force power-off. On re-boot
screen was at minimum brightness.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-23-generic
On 11/8/2013 12:39 PM, Julian Wiedmann wrote:
Fernando Miguel,
could you please test the latest kernel in -updates (3.11.0-13.20) and
confirm that this bug is fixed? Thanks.
** Changed in: linux (Ubuntu)
Status: In Progress = Incomplete
Yes, this update fixed the error message
I updated to 13.10 today and installed jsalisbury's packages from
comment #72. Neither his 3.11 kernel, nor the 3.8 kernel from 13.04
work for me. They both show the Ubuntu splash screen for a second or
two and then drop me into the console. Ctrl + Alt + F7 just shows a
blinking cursor.
--
201 - 300 of 308 matches
Mail list logo
