This Bug doesnt Affect me any more. I can Install all available kernels
now on 12.04.3
--
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/876715
Title:
Message Unhandled kernel version 3.0
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.11.0-15
kernel-fixed-upstream-3.4.70
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looks like since the later updates the bug seems gone -- at least for vmwares
graphics drivers.
On an other system running on real hardware the bug seems gone too.
I'll check later today on my laptop -- hopefully it is history there
too!
--
You received this bug notification because you are a
With my laptop the problem is gone using my self compiled kernel or the latest
one from Ubuntu. It is there using some older kernels. I had to carefully
adjust vga=xxx to switch to the very same mode than gfxpayload set to
1280x800@32. Took some time and playing around until it worked as
Seems fixed now
--
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/1270656
Title:
Ubuntu 14.04 boots to blank console
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux”
** Attachment added: Console using plain vanilla kernel 3.13.0-rc8
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3952528/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_024.jpg
--
You received this bug notification because you are a member of Kernel
Packages,
apport-collect fails to login to launchpad after allowing to access on
my behalf see:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1270717
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
#12: yes this is true, but does not explain why this leads to blank
console using the ubuntu supplied kernel and not using one self
compiled from plain vanilla sources. I've tested since: 3.12.8,
3.13.0-rc8 and 3.13. All show the same result: working console at
expected 800x600.
The ubuntu
** Attachment added: blacklisted vmwgfx
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954400/+files/dmsg-201401221456.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: blacklist simple-framebuffer
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954401/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_036.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is
There are slightly differences in character display depending on which
driver is blacklisted.
With my own kernel I could recognize changes in character display while
booting.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Attachment added: blacklist simple-framebuffer -- own kernel
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954416/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_037.jpg
--
You received this bug notification because you are a member of Kernel
Packages,
** Attachment added: none blacklisted
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954404/+files/dmsg-201401221500.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: none blacklisted
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954403/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_037.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Attachment added: blacklisted vmwgfx
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954399/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_035.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: blacklist vmwgfx -- own kernel
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954415/+files/dmsg-201401221458.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: blacklist simple-framebuffer -- own kernel
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954417/+files/dmsg-201401221500.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Attachment added: blacklist simple-framebuffer
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954402/+files/dmsg-201401221458.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: none blacklisted -- own kernel
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954405/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_035.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: dmesg-log from Ubuntu-Kernel, no driver blacklisted
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954637/+files/dmsg-201401221500.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
With this kernel-option I'll get a console prompt, but various kernel
log lines are never prinited on screen.
Printing stops at about [ 54.811735] [drm] DMA map mode: Using
physical TTM page addresses. and then starts again after a screen size
change at about [ 57.317174] intel_rapl: domain
Since today a new version of open-vm-tools is available. I've tested
again with this new version. Some of the errors seen with the old
version are gone now.
** Attachment added: New version of open-vm-tools
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/1270656
Title:
Ubuntu 14.04 boots to blank console
Status in
** Changed in: linux (Ubuntu)
Status: Confirmed = 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/919961
Title:
Rescue mode not usable with latest kernel
Status in
I've added kernel-bug-exists-upstream since this bug is in the latest
upstream kernel, linux-image-4.8.0-17-generic, present.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags added: kernel-bug-exists-upstream
--
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/1630245
Title:
after starting ubuntu 16.10 -- no keyboard, no mouse
Status in linux package in
I've tested these now (quite difficult to push them into an image not
running self contained ...):
4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ --
seems to work: booting is ok, but no keyboard, no mouse. Unsure if
keyboard and mouse are available for short, but the cursor
The bug exists in v4.7 final as in v4.8-rc1 -- as long as I use the
Ubuntu kernels. compiling plain vanilla kernels seem to not have this
bug (taking configuration from Ubuntu).
I tried to add modeprobe.blacklist=intel_powerclamp" without any effect:
same as before -- no keyboard, no mouse.
--
Have a look at CentOS Mainline-kernels found at
"http://elrepo.org/linux/kernel/el7/; these work even with ubuntu!
--
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/1630245
Title:
after
And what a mess: after about 10 minutes you'll be unable to type
anything on consoles. All keyboard events are ignored, as are mouse
events!
The systems boot thrugh, start networking as expected, but then cancel
networking.
--
You received this bug notification because you are a member of
And it is not guarantied systems boot through -- about every fifth boot
fails. Last printed line on screen: "Reached target multi user system".
No keyboard, no mouse, no network. I have to reset VM as I have to reset
real Hardware!
--
You received this bug notification because you are a member
Should have written modprobe.blacklist=intel_powerclamp -- this works.
The systems now boot with kernel v4.7 final, v4.8-rc1 and the default
kernel installed.
But ssh does not get started as before. Upgrading will make you loose
connection to an headless server (tried on VMware, confirmed on real
I've tried now:
With Ubuntu 16.04.1 LTS:
- Plain vanilla kernels 4.1.x, 4.4.x, 4.7.10, 4.8.x
- Ubuntu-Kernels: 4.5-rc1, 4.5-final, 4.6-final
- fedora mainline kernels (only took kernel-config, compiled kernel myself)
Result: keyboard, mouse working as expected with all kernels, except
Next I've tried to install 16.10 without upgrading from 16.04.1 LTS.
Install went fine, but rebooting at the end gave the same result: short
time cursor blinking behind 'login:'. Within this time keyboard works.
As soon, as the cursor vanishes, keyboard is dead.
I've tried other kernel too, but
This kernel does not work either. Are you sure it is the kernel? I'd say
it is systemd not doing what is expected. ALL kernels you gave me to
test WILL work together with Ubuntu 16.04.1 LTS!!
ALL WORK. None of them works with Ubuntu 16.10!!
--
You received this bug notification because you are
Was to fast -- non of these kernels work! They'll boot to login, but
leaving the system alone for some time -> no keyboard, no mouse. Looks
like these are started by systemd, but then terminated again. Maybe it's
two different errors one being solved by changing kernels, one within
system startup
Public bug reported:
# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of
Public bug reported:
kernel 4.18.0-11 -> does not work with Thunnar
>From Thunnar the device is not mounted. Only error message: "An
operation is outstanding" oder "An operation is in progress". The device
will never mount.
kernel 4.4.0-xxx -> works with Thunnar
>From Thunnar the device is
With kernel 4.18.0 it takes very long (up to minutes) to mount the device from
commandline.
With kernel 4.4.0 it is done within a second.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
With kernel linux-image-4.15.0-36-generic the system continuously tries ti
initialize video. The screen backlight blinks all seconds once, but never
starts any display-manager or, if booting in text mode, show any text.
You cant do anything except press the power button to
Public bug reported:
linux-image-unsigned-5.4.0-46-generic wont initialize console as
expected. No monitor is used or found. No graphics, no text console.
Only a blank black screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-unsigned-5.4.0-46-generic 5.4.0-46.50
Public bug reported:
Kernel turns off USB-devices.
A mouse connected to an usb-port works until some time. Then this device is
turned off and never turned on again. I tried to turn off power saving for such
devices, but without success.
This started with kernels 5.4.0-49-generic and later. I
Public bug reported:
latest ubuntu-kernels stop responding to usb storage devices all using
xhci_hcd:
- Prolific Technology, Inc. PL2773 SATAII bridge controller
maybe others too. Symptom: devices are shown in thunar, nautilus. They show up
in /dev as /dev/sdXN, but clicking them in thunar or
Public bug reported:
usb devices connected via an usb 3.x-hub are not detected.
[53443.604120] usb 4-4.2: new SuperSpeed USB device number 6 using xhci_hcd
[53443.707572] usb 4-4.2: New USB device found, idVendor=2109, idProduct=0813,
bcdDevice=90.11
[53443.707583] usb 4-4.2: New USB device
Start-Date: 2022-02-21 01:16:18
Commandline: apt -y upgrade
Requested-By: tps (1000)
Upgrade: firefox-locale-en:amd64 (97.0+build2-0ubuntu1,
97.0.1+build1-0ubuntu1), dmeventd:amd64 (2:1.02.175-2.1ubuntu3,
2:1.02.175-2.1ubuntu4), udev:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1),
libctf-nobfd0:amd64
Public bug reported:
bluetooth connects with headset, then times out, deconnects.
Forcing it to connect again it does, then times out and deconnects again.
Seen this with:
- Cyber jack
- Phonak Hearing Aids
- Sennheiser Headset
Since it worked until Feb. 21st, 2022 latest fixes applied at
Public bug reported:
Paired Bluetooth devices are connected, then disconnected, connected
again, then finally disconected.
This is with
- Ubuntu, xUbuntu 21.10
- Ubuntu, xUbuntu 22.04(beta)
It works with
- kali (latest)
- debian 11.3 (latest)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Public bug reported:
linux-generic kernels are missing nbd modules.
Since these modules are not build and not found in linux-generic-extra
or other packages it is not possible to
- use nbd-devices
- it is not possible to mount *.qcow2 qemu virtual harddrives into your host
system
You can
Meanwhile even the distros working until yesterday stopped working today
(5. May 2022 around 22:00).
The bug seems related to pipewire and switching to this new infrastructure.
It breaks nearly everything related with sound and bluetooth.
Modules involved:
- pipewire-pulse
- wireplumber
--
You
These modules seem to collide with pipewire-media-session, but are
required by bluez-stack to connect bluetooth headsets (or other devices)
to pulseaudio.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
xubuntu and kubuntu, as lubuntu do use pipewire for audio.
kali switched last night to use it.
openSUSE did so too.
i did not test on a plain vanilla gnome based ubuntu until now. Will do
it later this day (if time permits).
--
You received this bug notification because you are a member of
Public bug reported:
Bluetooth devices do not connect. Or better: they connect, disconnect,
connect, then finally disconnect.
It is the same using graphical tools or cli.
It is the same for
- ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta)
- debian 11.3
- fedora 35
52 matches
Mail list logo
