> However, I don't see how we can argue that dropping FAN support is
> *not* a regression, even if the kernel we ship does not support it.
I understand.
I guess the situation is a bit particular here. If the official kernel
doesn't support it -- something Ubuntu-specific, not upstreamed -- it
> I don't think we can justify dropping FAN support in an SRU, so let's
add that port back in.
Even if it will not be used in Ubuntu 24.04, and dropping these patches
would stop the diversion with Debian?
> @matttbe - is there any documentation about upstream compatibility guarantees
> and
Hi Dann,
Thank you for doing that!
Is there something I can do to help?
Note that I published the modifications I did [1] in a dedicated PPA
[2]. This was a merge with Debian.
If it is no longer needed to support Ubuntu FAN -- see my comment in #3
-- all Ubuntu-specific patches can be removed,
Hello,
I was quickly checking if I could help preparing the upgrade of IPRoute2
packages for Noble (before the final freeze).
In short, IPRoute2 has Ubuntu specific modifications. The merge was not
difficult, the code is there:
** Summary changed:
- Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable
(main)
+ Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable
(main)
** Description changed:
A few versions have been released and Ubuntu Noble still has the 6.1
I hope that's OK if I put the 24.04's feature freeze as milestone.
** Changed in: iproute2 (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching
** Description changed:
A few versions have been released and Ubuntu Noble still has the 6.1
version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
import the latest version from Debian unstable fixing a bunch of issues
and supporting features from more recent kernels?
Public bug reported:
A few versions have been released and Ubuntu Noble still has the 6.1
version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
import the latest version from Debian unstable fixing a bunch of issues
and supporting features from more recent kernels?
Please note that
Public bug reported:
Hello,
First, thank you for maintaining this kernel package for RPi!
When looking at something else[1], Phil Elwell from Raspbian OS noticed
that in the Ubuntu Raspi Lunar image with a kernel v6.2,
CONFIG_MPTCP_IPV6 is not enabled.
I guess this is because CONFIG_IPV6 is
@Dimitry: Are we not safe on 20.04 because the "ondemand" systemd
service is still there and will switch to "ondemand" CPU freq governor
after boot?
This service has been removed in systemd 245.5-1. Are there plan to
backport this to 20.04.2?
--
You received this bug notification because you
Hello!
Regarding the comment #8, I didn't get the same positive experience on
my side. It was more closer to what is described in comment #9. See bug
1889479 for more details.
I would suggest switching back to powersave/ondemand either with a new
service or the kernel config. Having a dedicated
Hello Christopher,
I confirm that I still have this crash when using the lastest RC version of the
kernel (v3.13 RC3) on Ubuntu Trusty.
Note that this bug has also been reported to DRI DRM/Radeon devs:
https://bugs.freedesktop.org/show_bug.cgi?id=71930
** Bug watch added: freedesktop.org
Despite this, would it be possible to either free up some space on
your main drive, or do the bisect from your backup drive?
Unfortunately it's currently not possible... I've to find some free time
and to buy a new drive.
I know that it's maybe not the same but a few bisects have also be made
Hello Luis,
Unfortunately, I no longer have this wireless card.
As this bug is fixed, maybe there is another problem.
Feel free to open a new bug report and don't hesitate to indicate that
the problem looks the same as this one but with a newer kernel.
--
You received this bug notification
According to Wolfgang, this issue was only affected 64 bits users.
But your problem is certainly not exactly the same as this one.
--
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/659143
Annoying :-/
Then don't forget to link your new bug report with this one :-)
--
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/659143
Title:
64bit-only: regression: kernels =2.6.34:
Hello Christopher,
Sorry for the delay.
I'm currently not able to bisect this bug simply because I've not enough free
space on my hard disk...
Maybe I can test a patch or a specific version and used my ppa to compile that
but I don't know if it will help.
Note that it seems I'm not the only
PS: sorry to not have updated this status when the bug was fixed.
--
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/987298
Title:
Sound card takes time to be initialised
Status in The
@Christopher: This bug has been fixed in the kernel 3.5, so yes, it should be
fixed when using Ubuntu 12.04.3 with the kernel 3.8.
I guess I can change the status to 'Fix Released'
Note that with this new kernel, there is another bug: LP: #1170917
** Changed in: linux (Ubuntu)
Status:
@Christopher: sorry, there is no option to disable this card in BIOS of
my laptop.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Description changed:
With using Kernel 3.8 and newer sometimes I have a kernel OOPS at startup and
it seems it's because I switch off my
@Christopher
so the default Trusty kernel crashes immediately
Yes. According to the backtrace, it's due to the Radeon driver (there are some
lines with 'r600_pcie(...)').
I can take a picture but should I open a new bug report?
--
You received this bug notification because you are a member
@Christopher: I'm now using Ubuntu Trusty but I'm not able to start kernel
3.12, it crashes immediately.
The backtrace is not available in /var/log/kern.log, what can I do more? Do you
want a screenshot of this crash?
--
You received this bug notification because you are a member of Kernel
@Christopher: without the workaround given in comment #7 I had this
problem with the development version of Saucy.
Now, I'm using Trusty and I have kernel oops (due to the Radeon module)
when using the kernel 3.12 (I have to report a new bug...)
** Changed in: linux (Ubuntu)
Status:
@Christopher: I didn't have this bug with Precise and Raring (I've not
tested with Precise and the kernel 3.8 but I guess we still have this
bug)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sorry, I would said: 'I didn't have this bug with Precise and *Quantal*'
I've this bug when using Kernel 3.8 and newer. When using Precise
12.04.0 or Quantal 12.10, I didn't have this bug because the version of
the kernel is 3.8. But with Precise 12.04.3 (kernel 3.8), I guess this
bug is there
I forgot to say this: for those who have this bug, simply add this line
in a service which is launched before X' start (e.g. in
/etc/init/lightdm.conf, just after the line with 'script'):
echo OFF /sys/kernel/debug/vgaswitcheroo/switch
--
You received this bug notification because you are
I now have this crash all the time at startup (I'm using Ubuntu 13.10,
kernel 3.11)
--
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/1170917
Title:
Powering down inactive GPU while
27 matches
Mail list logo
