I'm not aware this bug was filed against the kernel. It indeed is in the
install area. What would be the package, since I get 144 hits when I
search for "install"?
NB: There is no need for extra logs, the (reproducible) issue here is
that swap is not enabled after install.
** Changed in: linux (U
Public bug reported:
I have installed Kubuntu 24.04.1 on two different machines. During
installation I choose Manual configuration, I select a partition for /
and I select a (swap) partition for use as swap.
During the use of Kubuntu, especially with multiple users that use multiple
tabs in Chro
Unmounting all shares resolves the issue (ofc until you mount again)
--
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/2076576
Title:
5.15.0-118: NFS causes suspend to fail
Status in linux
Same issue here (mint though)
[Wed Aug 14 17:27:06 2024] OOM killer disabled.
[Wed Aug 14 17:27:06 2024] Freezing remaining freezable tasks ...
[Wed Aug 14 17:27:26 2024] Freezing of tasks failed after 20.002 seconds (1
tasks refusing to freeze, wq_busy=0):
[Wed Aug 14 17:27:26 2024] task:NFSv4
My computer booted just fine with that file in /lib/firmware/amdgpu. I
downloaded it again after booting, just to make sure that it was the
right file version.
% ls -l /lib/firmware/amdgpu/gc_11_0_0_imu.bin
-rw-r--r-- 1 root root 132352 Oct 7 09:36
/lib/firmware/amdgpu/gc_11_0_0_imu.bin
% sha1
I believe this is the right journal. It has a couple of amdgpu call
stacks.
I had a lot of restarts trying to get stuff working.
I'll try out that specific file later today.
** Attachment added: "6db523c73ff64c62a3703c38cd11bad9.journal"
https://bugs.launchpad.net/ubuntu/+source/linux-firmwa
I upgraded to linux-firmware_20220329.git681281e4-0ubuntu3.19 last night
and I couldn't start my computer without going into recovery mode this
morning. There were a few warnings about missing firmware in the apt
logs, but when I googled them, the usual response is "that's normal".
I played around
Confirmed, 5.15.0-56.62 boots as normal.
--
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/1996740
Title:
5.15.0-53-generic no longer boots
Status in linux package in Ubuntu:
Invalid
Sta
5.15.0-53 fails for me too, also with a Radeon graphics card with
monitor connected via DisplayPort. Is that a common theme?
2d:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1)
(prog-if 00 [VGA controller])
Same as
That workaround fixed it (after a while?)
--
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/1859592
Title:
Bluetooth unavailable after updates - Reading Intel version
information failed (
0)
I tried the workaround above:
rmmod btusb
rmmod btintel
modprobe btinel
modprobe btusb
Error message:
modprobe: FATAL: Module btinel not found in directory
/lib/modules/5.15.0-48-generic
uname -a
Linux jeroen-G14 5.15.0-48-generic #54-Ubuntu SMP Fri Aug 26 13:26:29 UTC 2022
x86_64 x86_64 x
What exact version of the mainland kernel would you recommend?
--
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/1926809
Title:
WD19 dock stops working in Ubuntu 21.04
Status in linux pack
Public bug reported:
Hi,
Focal Fossa currently carries LLVM 12.0.0, which has a bug in its C API
that renders it unusable as a backend for some compilers.
The upstream commit that fixes the bug is https://github.com/llvm/llvm-
project/commit/07234c7d6bc246925710b88a1f9552f678587165 and was inclu
IMHO kernel version 5.4.0-40 should be deleted with the highest prejudice.
Never before have I experienced 3 kernel panics in one day and a few after that.
This thing should have never left Canonical quality control for an LTS system.
And I have been running Ubuntu since the first release.
Jul 15
.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-05-
bly fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:
.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-05-
ion: 2.20.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed
.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-05-
ion: 2.20.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: I
.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on
pe: Bug
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
Installatio
ion: 2.20.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed
ion: 2.20.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: I
.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-05-
.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on
ion: 2.20.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jeroen 2488 F pulseaudio
/dev/snd/controlC0: jeroen 2488 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed
ionic Beaver" - Release amd64
(20190210)
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.12
+ Architecture: amd64
+ AudioDevicesInUse:
+ USER PID ACCESS COMMAND
+ /dev/snd/control
Public bug reported:
When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook
UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest
BIOS (UX450FDX.313), the laptop keeps getting events to change the
display mode (FN+F8), when having an external monitor connected this
makes the lapt
Yes it does
--
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/1851833
Title:
[Sager Clevo notebook model PB50_70RF,RD,RC] Unable to adjust
brightness of backlight
Status in linux package
@thorstenr-42: Also have a nfc model so still facing the same dead touchpad
issues.
I've never built a custom kernel before, just loaded a kernel module for a wifi
nic that didn't have drivers in the kernel. How do you go about building and
running this?
Also I'm wondering what would be necessa
I have started the process of adding dis_ucode_ldr to grub recovery mode
in Ubuntu. https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
In Kubuntu 18.04 the middle mouse button of my Logitech M310 didn't work
anymore.
After I tried the workaround as described in #91 and #95 it started working
again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
bios screenshots
--
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/1794318
Title:
unable to boot after installing vagrant
Status in vagrant:
New
Status in linux package in Ubuntu:
Inco
** Attachment added: "bios screenshots.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193579/+files/bios%20screenshots.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
sudo dmidecode
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
76 structures occupying 2828 bytes.
Table at 0xCBD62018.
Handle 0x, DMI type 11, 5 bytes
OEM Strings
String 1:
String 2: $BIOSE121
String 3:
String 4:
sudo mdadm --examine /dev/sd[a-z]
/dev/sda:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.2.06
Orig Family : b64dd376
Family : b64de296
Generation : 0806
Attributes : All supported
UUID : fe813c51:b5e27074:8e458e63:fd55063a
Checksum : d3a
sudo mdadm --assemble --scan
returns nothing
--
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/1794318
Title:
unable to boot after installing vagrant
Status in vagrant:
New
Status in lin
sudo mdadm --detail-platform
[sudo] password for jeroen:
Platform : Intel(R) Rapid Storage Technology
Version : 12.9.0.2006
RAID Levels : raid0
Chunk Sizes : 4k 8k 16k 32k 64k 128k
2TB volumes : supported
2TB disks : supported
Max Disks : 6
Max
find /etc/initramfs-tools/ -ls
14417979 4 drwxr-xr-x 5 root root 4096 sep 26 08:25
/etc/initramfs-tools/
14419131 4 -rw-r--r-- 1 root root 378 jan 5 2018
/etc/initramfs-tools/update-initramfs.conf
14419128 4 drwxr-xr-x 12 root root 409
sudo cat /proc/mounts
[sudo] password for jeroen:
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=8140992k,nr_inodes=2035248,mode=755
0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5
after a purge remove vagrant I get raid problems.
** Attachment added: "cannot activate member md127.jpg"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193074/+files/cannot%20activate%20member%20md127.jpg
** Changed in: mdadm (Ubuntu)
Status: Invalid => Inco
initramfs
** Attachment added: "initramfs.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193066/+files/initramfs.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
After installing vagrant it did a update-initramfs, which I presume,
broke booting from kernel 4.15.0-34-generic when I switched back, using
the grub menu, to a previous kernel 4.15.0-29-generic I could still
boot without problems
--
You received this bug notification because you are a member of
** Description changed:
- My system won't boot after a kernel upgrade. When I switch back to the
previous kernel version it works fine.
- I've got 3 ssd's and 1 hdd.
- Currently I'm using 2 ssd's for intel fake raid 1(mirror) for kubuntu 18.04
- The last ssd has windows 10 installed.
+ Reproducti
I've added my logs after a failed boot (using a usb live disk).
** Attachment added: "log.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1794318/+attachment/5193049/+files/log.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
** Summary changed:
- unable to boot
+ unable to boot after installing vagrant?
--
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/1794318
Title:
unable to boot after installing vagrant?
S
I reinstalled my system again and did a fool update and a reboot. It
looks like something else is causing the problem.
** Description changed:
My system won't boot after a kernel upgrade. When I switch back to the
previous kernel version it works fine.
I've got 3 ssd's and 1 hdd.
Currently
full*
** Summary changed:
- kernel update breaks boot on intel fake raid 1
+ unable to boot
--
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/1794318
Title:
unable to boot
Status in linu
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+question/674023
--
You received this bug notification because you are a member of Kernel
Packages, which is su
What to do next, I cannot update my desktop.
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: apport (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-g
can confirm after updating ubuntu Xenial and removing nomodeset from
boot options, everything seems to work again :)
--
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/1764194
Title:
Dell La
What about Xenial?!!
--
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/1764194
Title:
Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot
Status in linux package in Ubunt
i really don't understand why they allow anyone to update the status in
launchpad, it only creates confusion, especially when you can't revert
accidental changes :(
maybe @joseph salisbury can reopen this
--
You received this bug notification because you are a member of Kernel
Packages, which i
i'm also on the 4.13 kernel on xenial
thanks for fixing the issue!
it's really important for me cause i really need my external monitor to be more
productive at work
can't wait for the xenial kernel update to drop
--
You received this bug notification because you are a member of Kernel
Packages,
will this also be fixed in xenial?
--
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/1764194
Title:
Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot
Status in linux pa
any way to fix it for regular users (without compiling a kernel)
nomodeset works, but i can't use my external display if i use it
--
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/1764194
Tit
The patch I sent was ultimately accepted upstream. 'Liyama' should now
be spelled as 'Iiyama' on system's using this database.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to hwdata in Ubuntu.
https://bugs.launchpad.net/bugs/572628
Title:
I also tried upstream kernel 4.5.2-040502-generic, which solves the
problem except that it cannot wake up from hibernate. So I'm sticking
with 4.2.0-35-generic for now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
I have similar experiences since I upgraded from Ubuntu 15.10 to 16.04.
I can no longer suspend or hibernate, the screen goes black but the PC
stays on, heating up and triggering the fan after a while.
When I run Ubuntu 16.04 with kernel 4.2.0-35-generic (which was still
installed) instead of kern
@adam lee; dkms_1.1_all.deb works fine at kubuntu 15.04
uname -a
Linux GS70-2QE 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
lspci
Network controller: Qualcomm Atheros Device 003e (rev 20)
Subsystem: Bigfoot Networks, Inc. Device 1525
Hello? Any corrections for that revisions range you wanted me to
bisect?
--
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/1300557
Title:
Screen resolution no longer works
Status in linux
This is still happening on a fresh 15.04 install and then updating it
completely with apt/aptitude. Kernel version 3.19.0-26.
--
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/1374759
Title:
This last weird effect was transient; it went away after a reboot.
--
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/1300557
Title:
Screen resolution no longer works
Status in linux packag
It just got a bit weirder.
I've got my custom xrandr-defined 2560×1440 resolution going. But for
purposes like window placement, resizing windows, and maximising
windows, the UI seems to think it's 1920×1080 or thereabouts.
So if I open a whole bunch of editor windows from the shell, they all
ap
This is getting awkward. The upper-bound version you wanted me to
bisect is also missing from the Ubuntu/upstream version mapping. So
even if I want to bisect upstream versions I still have the same
problem. Are you sure you gave me the correct versions for bisection?
Maybe you meant 3.13.0-20.4
Thanks. Could you also update that section? It says that it applies in
two situations, but it never actually lists those two situations. I
*think* (but without already knowing of course I can't be sure) that
it's meant to refer to a list of three headings, “BISECTING: A MERGE
BASE MUST BE TESTED
Thanks for following up. I read most of that document, but it's
difficult in places. My understanding is that what you're asking me to
do is what's described under “Commit bisecting Ubuntu kernel versions,”
correct? That's the only part of the main page (excluding the FAQ
below) that seems to ap
If you don't have time to read what I wrote, or if something I wrote is
not clear, just say so and I will understand. Let's not get caught in
the endless Confirmed/Incomplete circle.
I'll summarise what I said before, to make it easier to digest:
You asked me to bisect between 3.13.0.18.38 and 3
Read back and it will become clear.
** 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/1300557
Title:
Screen resolution
Once again: with the given instructions I can't bisect kernel commits
any further. Is there another way to obtain the kernel source versions
we need?
Marking as Confirmed again until then, to avoid this bug timing out.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You
Oh, one other thing: with the older kernels I can play AssaultCube
again! I couldn't really do that with the current Vivid kernels because
the frame rate was too low. Reported frame rate would be around 60 fps,
but it looks more like 10 fps. With these old kernels it plays
smoothly.
--
You rec
Nope, the Utopic kernel branch only has 3.13.0-19.40 and 3.13.0-20.41,
nothing inbetween.
So, all I know is up to and including 3.13.0-19.40 it still works OK.
The problem must have been introduced later than that.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You rece
The Precise kernel repository finished downloading, but it doesn't have
3.13.0-20.24. It has 3.13.0-19.39 and 3.13.0-20.41, nothing inbetween.
Pinning my hopes on the Utopic branch...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
3.13.0-19.40 also works OK! So it broke sometime after that.
I'm now trying to find 3.13.0-20.24 in one of the kernel branches from
before Vivid. It's not in the Trusty branch. I can't get the Quantal,
Raring, or Saucy ones, presumably because those releases are no longer
supported. Downloadin
Using the ubuntu-vivid kernel branch, 3.13.0-18.38 works OK.
That branch has no tag Ubuntu-3.13.0.20.24 or Ubuntu-3.13.0-20.24. The
closest tags I see are Ubuntu-3.13.0-19.40 and Ubuntu-3.13.0-20.41.
I'll try 3.13.0-19.40 next.
--
You received this bug notification because you are a member of K
Tried 4.1-rc8 as well for good measure. Still no improvement. Highest
resolution offered in the System Settings is 1920×1200.
--
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/1300557
Title
No Tried 4.1-rc7. No change.
** 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/1300557
Title:
Screen resolution no lon
Marking this bug as "Confirmed" to avoid timeout. It was marked
Incomplete pending testing against Saucy, but as of a few months ago the
results are shown above.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member o
After another reboot this effect seems to have gone away. So I still
don't have my native resolution available by default, but at least I can
get it back by defining it with xrandr.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hurray, the problem just got a little worse!
After the upgrade to kernel 3.19.0-14.14, when I define my monitor's
native resolution using xrandr, I get the right *resolution* but still
not the right number of *pixels*. So I'm getting (as far as I can see)
one logical pixel per physical pixel on t
Correction: that last upgrade was *from* 3.19.0-14.14, not *to* it. It
was the upgrade to 3.19.0-15.15.
--
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/1300557
Title:
Screen resolution n
> Janne, good point. There's another possible workaround in certain
circumstances. You can also clear the auditd rules which should allow
you to continue working on a running system. This would be done by
issuing an "auditctl -D", after which you should be able to use the
running system, albeit wit
I found a driver on debian: https://wiki.debian.org/alx#Installation
--
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/1383184
Title:
Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] n
Well, I did some bisecting but the results are disappointing. Actually
I ended up trisecting. On Saucy, kernel...
3.11.0-12 was OK. Recognised my full native resolution and enabled it
by default. Wonderful.
3.11.0-13 to 3.11.0.24 inclusive were completely messed up. They booted
in some ultra
I could temporarily swap out the hard drive and install Saucy on the
spare. More after the weekend.
--
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/1300557
Title:
Screen resolution no lo
Okay, I got a seemingly successful install of the last Saucy kernel.
But it's not working very well: I get a super-low-res login screen, and
the system doesn't respond to keyboard or mouse. (It does notice the
power button, so it's not frozen). This happens both with the default
boot on that kern
Trying 13.11.0-17. There was a problem while installing linux-headers
though... "fwts-efi-runtime-dkmis 15.03.00-0ubuntu1: fwts-efi-runtime-
dkms kernel module failed to build." Somewhere along the way it said:
run-parts: executing /etc/kernel/postinst.d/dkms 3.11.0-17-generic
/boot/vmlinuz-3.
The latest upstream version I found there was v4.0-rc4-vivid. It boots,
but it doesn't fix the problem.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.0-rc4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
I'm still having this problem after updating to 14.10.
This issue exclusively arises if I suspend my laptop when connected to
the power cord, then unplug it during suspend and wake it up on battery.
It does not happen every time, maybe once in seven times.
The scaling_governor keeps all cores at
Running 3.13.0-40-generic triggering this as well:
kernel: [ 11.095358] nvidia: module license 'NVIDIA' taints kernel.
kernel: [ 11.095361] Disabling lock debugging due to kernel taint
kernel: [ 11.100122] nvidia: module verification failed: signature and/or
required key missing - tainting
Just a note, I'm not 100% certain that it was completely broken before
the bios update. It could very well be that it had the same 60 second
delay. Then again, that long a delay means broken in my eyes anyway. No
user is going to wait that long to log back in every time his system
suspends.
--
Yo
Yes, it takes roughly 60 seconds before networking is started.
Hibernation would not be an option for us, the hardware is capable of
resuming, and the subsequent attempts show that it should be able to do
so quickly.
Attached is a log again of login, suspend, and resume cycles.
16:02:27 the machi
The first time it takes 60 seconds to log in, and it seems that
networking is broken during that time.
Subsequent logins take only three seconds, and also see almost no
downtime in networking.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
We have upgraded the BIOS of the machine:
# sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A18
04/30/2014
We now find that after a reboot, the first suspend and resume cycle
takes long: after pressing enter in the password screen it takes about
60 seconds to either log that
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1352379
Title:
Network broken after resume
Status in “linux” package in Ubu
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1352379/+attachment/4169661/+files/UdevDb.txt
--
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/1352379
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1352379/+attachment/4169654/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1352379/+attachment/4169655/+files/Lspci.txt
--
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/1352379
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1352379/+attachment/4169658/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
1 - 100 of 114 matches
Mail list logo
