Hi Alex, just to make sure that I reinstalled one of the kernels that was
supposed to be good (perhaps by accident I reinstalled a bad one), could
you direct me to a good kernel on your ftp site? best, Jim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Alex,
unfortunately that bug has come back. It just took longer to manifest
itself after booting. It also affects recognition of the power state and
the brightness buttons, which I hadn't noticed before. --Jim
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Alex,
I see that I am currently running 5.4.0-48-generic, which I think is the
same version that you originally sent me. But livepatch alters the
running kernel without changing its version number, doesn't it?
That's what makes me still wonder if it is the culprit.
thanks--Jim
On Tue, 3 Nov
Hi Alex,
my problem came back. Is it possible that livepatch has replaced my
working kernel with the broken one again? --Jim
On Thu, 24 Sep 2020, Alex Hung wrote:
> A test kernel with target patches ready for SRU is available @
> https://people.canonical.com/~alexhung/LP1896482/fixes/
>
> The
last one you sent with the commit? It is working.
On Fri, 25 Sep 2020, Alex Hung wrote:
> @jcline-physics,
>
> can you give kernel in #24 a try?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
> Title:
> a
thanks a lot Alex
On Thu, 24 Sep 2020, Alex Hung wrote:
> A test kernel with target patches ready for SRU is available @
> https://people.canonical.com/~alexhung/LP1896482/fixes/
>
> The patch in #23 requires three precedent patches. See SRU.log file for
> more details.
>
> Note it is rebased Ub
that one seems to be fine.
On Thu, 24 Sep 2020, Alex Hung wrote:
> Next one:
> https://people.canonical.com/~alexhung/LP1896482/937d1d5d752513b8/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
> Title:
> a
that one also seems to be good.
On Wed, 23 Sep 2020, Alex Hung wrote:
> Next one is @
> https://people.canonical.com/~alexhung/LP1896482/c271d18b523bb58e/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
> Ti
this one seems to be good
On Wed, 23 Sep 2020, Alex Hung wrote:
> @jcline-physics,
>
> Thanks for testing. The next is available @
> https://people.canonical.com/~alexhung/LP1896482/31be3e3551d09f20/
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => In Progress
>
> ** Changed in: li
okay, so that kernel has the problem again.
On Wed, 23 Sep 2020, Alex Hung wrote:
> Thanks mfo for helping out how to disable secure boot and install kernel
>
> I uploaded a test kernel @
> https://people.canonical.com/~alexhung/LP1896482/0a8c35897f60b202/
>
> There are 17 patches so it requires
ok, that's not such a big problem. I'll keep all the versions' deb
packages in separate directories so I can easily switch back to one of
them if needed.
On Wed, 23 Sep 2020, Mauricio Faria de Oliveira wrote:
> Hi Jim,
>
> You can install on top of the previous ones without removing them firs
Hi, if I install this on top of the previous one using dpkg -i * will that
be sufficient? Or do I have to remove the previous packages first?
It seems like my grub configuration is somehow set to keeping only two
kernels in the boot list. It would be nice if it would keep them all so I
don't
ok, I can do that
On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote:
> Hey Jim,
>
> That's very good news!
>
> I believe Alex should send you more test kernels,
> with different sets of patches included/removed,
> so to bisect/identify which specific patch(es)
> resolve the problem.
>
> If y
Looks like it is working! At any rate the old kernel started having the
problem much sooner while this one is still fine. Thanks very much for
your help with this!
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/18964
thanks, I fixed that and will start testing
On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote:
> It looks like you have secure boot enabled.
> Unfortunately test kernels are unsigned and thus require it to be disabled in
> your BIOS/EFI menu.
>
> --
> You received this bug notification bec
Hi Maricio, I did as you suggested, but cannot boot,
error:/boot/vmlinuz-5.4.0-47-generic has invalid signature
loading initial ramdisk
error: you need to load the kernel first
--Jim
On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote:
> Hi Jim,
>
> This is a conflict between the (un)signed
Hi Alex, thanks for that. I got this error message while installing,
dpkg: regarding
linux-image-unsigned-5.4.0-47-generic_5.4.0-47.51_amd64.deb contntaining
linux-image-unsigned-5.4.0-47-generic:
linux-image-unsigned-5.4.0-47-generic conflicts with
linux-image-5.4.0-47-genereric
linux-ima
17 matches
Mail list logo
