Public bug reported:
I have installed Ubuntu Server on My VisionFive v2, the Kernel version is
6.5.0-14-generic, I notice the new Kernel linux-image-starfive(= 6.5.0.1005.7)
was released and I upgrade it, and then VisionFive v2 crashes while it boots.
the initramfs message:
ALERT!
** Tags removed: verification-needed-jammy-linux-oem-6.1
verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.1
verification-done-jammy-linux-oem-6.5
** Changed in: hwe-next
Status: In Progress => Fix Committed
--
You received this bug notification
** Tags removed: verification-needed-jammy-linux-oem-6.1
verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.1
verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
>From the log in pstore the issue was caused by iwlwifi.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046217
Title:
Some machines can't pass the pm-graph test
Status in
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046315
Title:
oem-6.5: disable psr2 for some panels
** Description changed:
- tracking
+ BugLink: https://bugs.launchpad.net/bugs/2046681
+
+ [Impact]
+ The customer Dell provide the edid for one more panel, this panel also needs
to disable the psr2, otherwise the display will not work correctly
+
+ [Fix]
+ There is no real fix so far, ODM
ODM verify passed on Orchid Bay MLK2 FHD panel.
So verification done forlinux-oem-6.5
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Jammy)
Public bug reported:
tracking
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux-oem-6.5 (Ubuntu)
Importance: High
Assignee: Hui Wang (hui.wang)
Status: Invalid
** Affects: linux-oem-6.5 (Ubuntu Jammy)
Importance: High
Assignee:
6.5.13 > "Test amd64/build failed (rc=2, on=amd64, time=0:07:36,
log=amd64/log)".
@superm1
In 6.6.6 this issue seems fixed FYI.
--
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/2039570
Unfortunately, I think the issue is still not resolved. The touchpad
still disconnects for me on a fully updated Fedora 39 with Gnome 45.2.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I tested it. The trackpad worked for more than an hour without the same
disconnections every 10 minutes that we had before. But an hour later it
disconnected and could not restore the connection. Only restarting
bluetooth helped. This happened several times. The problem has not yet
been resolved.
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
On Fri, Dec 15, 2023 at 3:55 PM Sam Tannous <2043...@bugs.launchpad.net> wrote:
>
> You're correct. It can fail for other reasons. I don't think we could check
> the errno, could we? It would be 1, "Operation not permitted".
The exit code is not documented in the manpage, and it appears to
Public bug reported:
SRU Justification:
[Impact]
The msdhci-of-dwcmshc driver in the Jammy repo
consists of some SAUCE patches. These need to be replaced.
[Fix]
The fix is to revert the four SAUCE patches, replacing them with
upstream commits for the same functionality.
[Test Case]
* Boot BF3
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Hi,
I contacted manufacturer and they have told me that most likely wifi
module is broken. They sent me a replacement and it works out of the box
now. So I think this bug can be closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
16 matches
Mail list logo
