Also affects 201202-10508 Dell Inspiron 5420 - E7=73 03 50, EC=73 02 02
** Tags added: 201202-10508
--
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/1190867
Title:
Touchpad was incorrectl
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) =>
Parameswaran Sivatharman (psivaa)
--
You received this bug notification becaus
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) =>
Parameswaran Sivatharman (psivaa)
--
You received this bug notification becaus
Hi Mr Cristopher,
I can not tell you certainly if i did or didnot uptade the BIOS in windows,i
hope not but i am not sure
I do remember that i went to the page
"http://support.ts.fujitsu.com/Download/ShowFiles.asp",after on right top of
this page in the "search" i put BIOS 1.90 and came out the
** Also affects: lubuntu-default-settings (Ubuntu)
Importance: Undecided
Status: New
--
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/1202320
Title:
[Acer AO722] suspend/resume f
Joseph, I get the same error with the "generic" kernel (using ubuntu-
gnome-13.04-desktop-i386.iso):
$ cat /proc/version_signature
Ubuntu 3.8.0-19.29-generic 3.8.8
$ lsb_release -d
Description: Ubuntu 13.04
$ gcc seccomp-filter.c
$ ./a.out
execve(): Operation not permitted
status = -1
--
You r
Also affects:
201202-10511 Dell Inspiron 5420 - E7=73 03 50, EC=73 02 02
201203-10655 Dell Inspiron 5323 - E7=73 03 50, EC=73 02 02
201203-10656 Dell Inspiron 5323 - E7=73 03 50, EC=73 02 02
201203-10656 Dell Inspiron 7420 - E7=73 03 50, EC=73 02 02
** Tags added: 201202-10511 201203-10655 201203
The workaround from @Batuhan works for me too (Dell Sputnik,
3.8.0-26-generic, BIOS A08)
--
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/1169376
Title:
XPS13 backlight stopped working aft
Thanks for your prompt advices, Christopher.
Sorry about the attachment spam. My attachments from Dell Optiplex 960 are not
valid for this Zenbook issue so I hid them (though I updated Dell's BIOS as you
suggested).
I tried to reproduce bug #989443 with Ubuntu 13.04 (and succeeded partly), and
No regressions seen:
http://reports.qa.ubuntu.com/sru/lucid/
** Tags added: qa-testing-passed
** Changed in: kernel-sru-workflow/regression-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
I'll do this ASAP. It might be a while before I get a chance but I'll
give it a go. I switched to a wired mouse some months ago because of
this problem.
Thanks in advance.
On 18/07/13 04:00, Christopher M. Penalver wrote:
> James Brierley, could you please test for this in Saucy and report the
Looks good
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
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/1199494
Title:
linux: 2.6.32-50.
Forgot to mention:
Could someone with the problem try reproducing it with Windows? Or (if you're
not converted all of your friends to linux) ask from a friend who's running
Windows in her/his Zenbook UX31E.
--
You received this bug notification because you are a member of Kernel
Packages, which
** Description changed:
This bug is for tracking the 2.6.32-50.112 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-
I don't think this is a software related problem but hardware one. I've
been running Windows on my ZenBook lately, and this problem occurs with
Windows too. Usually I see it when the laptop is running hot and I try
to plug or unplug the power adapter, but I can see it sometimes too when
I've just r
** Description changed:
This bug is for tracking the 2.6.32-50.112 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-
Screenshot added
** Attachment added: "20130717_223153_resized.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1202405/+attachment/3741191/+files/20130717_223153_resized.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Screenshots added
** Attachment added: "ctrl-alt-F1 to avoid splash screen"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1202405/+attachment/3741189/+files/20130717_222929_resized.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Screenshot added
** Attachment added: "3.2.0-49 Recovery kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1202405/+attachment/3741192/+files/20130717_223226_resized.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
babis x, could you please boot into Windows, find the file:
BIOS Windows Flash () - Winflash_AMILO Li1718
1.90
12.11.2007
Update to this, and advise if it changes anything?
If not, could you please both specify what happened, and provide the output of
the following terminal command:
sudo dmideco
** Summary changed:
- HDMI out doesn't work with ASUS Zenbook UX31E
+ [ASUS Zenbook UX31E] HDMI out doesn't work
--
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/989226
Title:
[ASUS Zenbo
Chris, I think Shahar's idea is to submit the patch and hopefully gets
merged so that regular users don't have to remove anything to get
everything working.
But yeah, why not, submit a patch and see what happens. I am curious.
--
You received this bug notification because you are a member of Ker
I can confirm that https://bugzilla.kernel.org/attachment.cgi?id=97751
fixes the issue on the FHD version (also works after suspend and blank
screen). I've attached the patch rebased on top of 3.8.0-26.38 in case
somebody is eager to try it too.
** Patch added: "The patch for the FHD version from
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) =>
Parameswaran Sivatharman (psivaa)
--
You received this bug notification becaus
No regressions seen
** Tags added: qa-testing-passed
** Changed in: kernel-sru-workflow/regression-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Marking this Fix Released for Saucy. Per my notes from a call with
Intel, the remaining patches needed for Saucy should have already landed
in the v3.9 kernel.
** Changed in: linux (Ubuntu Saucy)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a m
** Tags removed: blocks-hwcert blocks-hwcert-enablement
--
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/964231
Title:
System Stutter When HDMI/Displayport Monitor Is Connected
Status in
I probably didn't explain clearly enough:
So, what's actually happening is, the function key behaviour works
without pressing the function key - for instance you just press the
brightness button F2/F3 and the brightness changes, without using FN
and the F1-F12 keys require pressing the FN key to
I've just discovered that all the keys do work - longer explanation
required:
The issue seems to be that the behaviour on windows is different
(IIRC... this would be why i'm confused using the keyboard in linux).
On windows, F1-F12 are the default actions for pressing these keys, with
the functio
So in essence it works but needs to be re-mapped.
--
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/1201665
Title:
HP DV6-4008TX Function Keys do not work - brightness, sound, wireless
Sta
Had this exact problem running Xubuntu 13.04 with kernel version
3.8.0-26 on an HP tc4400 laptop. petr-daneck's script fixed it for me.
Thanks, Petr.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
A bisection reveals that the following patch solves the issue:
8093315a91340bca52549044975d8c7f673b28a1 veth: extend device features
However it relies on:
2681128f0ced8aa4e66f221197e183cc16d244fe veth: reduce stat overhead
For a clean cherry-pick.
And after building and testing the following bug
Gave Natty a try (also had to use the "nomodeset" option to boot).
Still no battery status - actually worse, there was no indicator at all.
I went to Power Management Preferences and noticed that there was not
"On Battery" tab and enabling "Always Display Icon" only showed the AC
Power icon. Basic
** 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/1201671
Title:
HP DV6-4008TX Wireless key light constantly flashing wh
** Description changed:
+ SRU Justification:
+
+ Impact:
+ Users of the 3.5/3.8 kernel will have poor network throughput when using
OpenStack Neutron depending on their setup.
+
+ Fix:
+ These patches are all in Ubuntu-3.9.0-7.15 / v3.9-rc1:
+ 2681128f0ced8aa4e66f221197e183cc16d244fe
+ 8093315a
** Description changed:
This bug is for tracking the 3.2.0-50.76 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Pr
I've just verified on saucy daily images that this seems to be work-aroundable
by launching with user-data containing a boothook that will run ethtool -K eth0
gso off.
example cloud-config:
#cloud-config
apt_update: true
apt_upgrade: true
packages: [ pastebinit ]
output: {all: '| tee -a /var/log
It happens also with the new 3.11 kernel. I noticed that I can force
this behavior by opening and closing the lid until it suspends. Also I
noticed that it always wakes up when removing/attaching the power cable,
that sometimes it wakes up automatically after about 2-3 minutes and
that sometimes, a
Is it possible to assign this bug as affecting linux-lts-raring too? It
is correctly marked as fixed for linux-lts-quantal, but in a month from
now 12.04.3 will be out with a buggy kernel... Or am I wrong?
--
You received this bug notification because you are a member of Kernel
Packages, which is
I contacted Dell as suggested, asked them what the recommended method
for updating the BIOS when running Ubuntu and got a response today:
…
"The easiest way to update the firmware on your server is to use the “platform
update” from the lifecycle controller. You can see a short video here on how t
Public bug reported:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East' location). I get a
300 second timeout before / is mounted RW.
See attached dmesg for full dmesg. snippet here.
[6.974
That is correct. The default raring kernel will be very disappointing
for people that are experiencing the problems outlined in this thread.
It seems that only >3.9.7 has a usable kernel for affected Sandybridge
users (I am using a Lenovo X220). Even then, the bug remains at some
level but it mo
nchpad.net/bugs/1202700
Title:
saucy kernel 300 second hang before root mounted rw on azure
Status in “linux” package in Ubuntu:
New
Bug description:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US Eas
apport information
** Tags added: apport-collected saucy uec-images
** Description changed:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East' location). I get a
300 second timeout before / is
gs/1202700
Title:
saucy kernel 300 second hang before root mounted rw on azure
Status in “linux” package in Ubuntu:
New
Bug description:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East' loca
nchpad.net/bugs/1202700
Title:
saucy kernel 300 second hang before root mounted rw on azure
Status in “linux” package in Ubuntu:
New
Bug description:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US Eas
ntu.
https://bugs.launchpad.net/bugs/1202700
Title:
saucy kernel 300 second hang before root mounted rw on azure
Status in “linux” package in Ubuntu:
New
Bug description:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB i
d.net/bugs/1202700
Title:
saucy kernel 300 second hang before root mounted rw on azure
Status in “linux” package in Ubuntu:
New
Bug description:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East'
d.net/bugs/1202700
Title:
saucy kernel 300 second hang before root mounted rw on azure
Status in “linux” package in Ubuntu:
New
Bug description:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East' loca
nchpad.net/bugs/1202700
Title:
saucy kernel 300 second hang before root mounted rw on azure
Status in “linux” package in Ubuntu:
New
Bug description:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US Eas
ang before root mounted rw on azure
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East' location). I get a
300 second timeout before
Created attachment 82347
possible fix
Does the attached patch help?
--
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/1034002
Title:
Lenovo E525 screen black on resume
Status in Direct Re
These problems seem similar to the bug I reported:
https://bugs.freedesktop.org/show_bug.cgi?id=42162 . One common thread
is that many of the affected machines are HP laptops. Maybe the HP ACPI
implementation does something funny?
--
You received this bug notification because you are a member of
(In reply to comment #26)
> Created attachment 82347 [details] [review]
> possible fix
>
> Does the attached patch help?
Have just tested, and it dont change anything.
I still also don't know what it have to do with backlight? The screen is
completely turned off, if I use a flash light I can see
** Bug watch added: freedesktop.org Bugzilla #42162
https://bugs.freedesktop.org/show_bug.cgi?id=42162
--
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/1034002
Title:
Lenovo E525 screen
*** Bug 61470 has been marked as a duplicate of this bug. ***
--
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/1034002
Title:
Lenovo E525 screen black on resume
Status in Direct Rendering
** Changed in: linux (Ubuntu Saucy)
Status: In Progress => Fix Released
--
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/1173423
Title:
Kernel fails to update EFI vars, rendering sy
I have the same problem with Lubuntu 13.10 from the desktop panel in
"Shut Down" I click on the "Suspend" everything is going well and the pc
is suspended, when I try to reactivate the screen remains black, no
imput and I must proceed to the forced shutdown of the machine by
holding down the power
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Are you able to reproduce this bug? If so, would it be possible for you
to test the latest upstream kernel? Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstr
3
[ 15.593280] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts:
(null)
--
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/1202700
Title:
saucy kernel 300 second hang before root mo
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
ges
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East' location). I get a
300 second timeout before / is mounted RW.
See attached dmesg for full dmesg. snippet here.
[6.974849] scsi3 : storvsc_host_t
[6.977249] scsi 3:0:1:0: Direct-Ac
** Bug watch added: Gentoo Bugzilla #474432
https://bugs.gentoo.org/show_bug.cgi?id=474432
** Changed in: gentoo
Importance: Undecided => Unknown
** Changed in: gentoo
Status: New => Unknown
** Changed in: gentoo
Remote watch: None => Gentoo Bugzilla #474432
--
You received this
ackage in Saucy:
Confirmed
Bug description:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East' location). I get a
300 second timeout before / is mounted RW.
See attached dmesg for full dmesg. snippet
LaMont,
There have been a number of updates since this bug was initially found.
Can you update to the latest raring kernel and verify that the bug still
exists?
If it does still exist please change the status of the bug back to
"Confirmed".
** Changed in: linux (Ubuntu)
Status: Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1202723
Title:
package linux-image-3.2.0-50-g
in “linux” package in Ubuntu:
Confirmed
Status in “linux” source package in Saucy:
Confirmed
Bug description:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East' location). I get a
300 second
It looks like the suspend resume problem has been fixed as I have tried
suspending ad resumeing about 5 times and everything seems normal. I am not
sure which update over the past day or so fixed the problem but so far so good.
I am using the 3.11 rc1 kernel still and the Graphics driver is Galli
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
** Tags added: patch
--
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/1169376
Title:
XPS13 backlight stopped working after update 3.8.0-18.28
Status in Dell Sputnik:
Confirmed
Status in
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
(In reply to comment #115)
> Yes, it works.
Thanks, it narrows it down. I looked through the Intel HW IOMMU code and
haven't found anything obvious that could explain this.
OTOH, looking again at the dmesg with the crash
(dmesg-3.10.0-rc6-00406-g73bc88c) I can't see the HW IOMMU being
enabled. I'
After your comment i did some more tests -- just in case.
Enabled VT-d and removed intel_iommu=igfx_off line. Result is really
interesting:
I get oops only on second boot without igfx_off. First boot without igfx_off is
ok, both displays are working, but after power off and new start with same
c
Launchpad has imported 4 comments from the remote bug at
https://bugs.gentoo.org/show_bug.cgi?id=474432.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.lau
(In reply to comment #111)
> yes, intel_iommu=igfx_off helps too. Thanks!
Ok, that's proof that something _really_ fishy is going on here. Big WTF
moment ... Imre do you have any ideas what this could be? Seen anything
like this when you've done the sg conversion?
--
You received this bug notifi
Created attachment 82344
disable sg compaction
> (In reply to comment #111)
> > yes, intel_iommu=igfx_off helps too. Thanks!
>
> Ok, that's proof that something _really_ fishy is going on here. Big WTF
> moment ... Imre do you have any ideas what this could be? Seen anything like
> this when you'
Ugh. I downloaded and tested the ISOs for Maverick and Lucid (10.04.4
version) and was met with the same results I had with Natty (also had to
use nomodeset to boot). Neither recognized the battery (including a
boot to Lucid on battery only). I know for certain when I had Lucid,
the battery was
Yes, it works.
--
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/946311
Title:
only external screen is working with asus zenbook ux31e [eDP1]
Status in X.org xf86-video-intel:
Incomplete
(In reply to comment #107)
> So, i tasted with latest git 3.10.0-rc7-00854-gf19c9d3 - same result.
>
> (gdb) l *intel_crtc_set_config+0x216
> 0x2bab0 is in intel_crtc_set_config
> (/home/lex/tmp/linux/drivers/gpu/drm/i915/intel_display.c:8678).
> 8673int num_connectors)
> 8
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
** Also affects: linux (Ubuntu Saucy)
Importance: High
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
--
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/1200243
Tit
yes, intel_iommu=igfx_off helps too. Thanks!
--
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/946311
Title:
only external screen is working with asus zenbook ux31e [eDP1]
Status in X.org
** Changed in: linux (Ubuntu Raring)
Status: New => Invalid
--
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/1189605
Title:
linux: 3.8.0-25.37 -proposed tracker
Status in Kernel SR
I don't have any further suspend/resume issues (running Saucy), so I
consider this fixed.
On Thu, Jul 18, 2013 at 9:38 AM, Brad Figg wrote:
> There have been a number of kernel updates since the one you reported this
> bug against. Please test again with the newer kernel and indicate in the
> b
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
Thanks for testing. I wonder if this issue exists in Raring, but may
have been fixed in Saucy.
Would it be possible for you to test the latest Saucy kernel? You can
find the .debs under the "Builds" section for your particular arch.
Thanks in advance.
[0] https://launchpad.net/ubuntu/+source/l
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
Will I need to do anything to get the Dahdi-dkms working ? I did try a
mainline kernel (3.2.0-49 I think) but phone card did not pick up or
make any calls, I assume it wasn't recognised or driver was missing.
--
You received this bug notification because you are a member of Kernel
Packages, which
-server-20130718-en-us-30GB in 'US East' location). I get a
300 second timeout before / is mounted RW.
See attached dmesg for full dmesg. snippet here.
[6.974849] scsi3 : storvsc_host_t
[6.977249] scsi 3:0:1:0: Direct-Access Msft Virtual Disk 1.0
PQ:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
1 - 100 of 200 matches
Mail list logo
