from:"Mario"

[Bug 2081199] [NEW] On high resolution modes, after screen resume from power saving, the display configuration gets lost, and sometimes Gnome crashes

2024-09-19 Thread Mario Emmenlauer

Public bug reported:

This is a follow-up issue from
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/2075525, and some of the information from the earlier issue
may apply here.

I have configured the host screen with two monitors extending the desktop.
They are both configured at 3840x2160 @ 60Hz, scale 200%, fractional scaling:
no.

I'm using a HDMI 2.1 cable on the one monitor, and a DisplayPort cable
on the other monitor. My graphics card lacks a second display port
connector, so I can not try if the problem would persist with two
DisplayPort cables.

After a period of inactivity, the screens get blanked as configured.
When I move the mouse and the screens unblank, the display configuration is
changed. I have observed different behavior of the changed display
configuration:
- most commonly, the displays change into mirror mode instead of joined mode.
- sometimes, a third, small display appears on one of the sides.
- sometimes, the second monitor stays blank
- sometimes, Gnome crashes

I confirm that I have ubuntu-drivers-common:amd64/noble-updates
1:0.9.7.6ubuntu3.1, so this should have the issue fixed?

Attached is an excerpt from syslog, from around the time then I unlocked
the display coming back from suspend, until the Gnome crash.

System information:
No LSB modules are available.
Description:Ubuntu 24.04.1 LTS
Release:24.04

** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New

** Tags: multimonitor noble nvidia

** Attachment added: "Excerpt from syslog"
https://bugs.launchpad.net/bugs/2081199/+attachment/5819393/+files/log.txt.gz

** Tags added: multimonitor noble

** Tags added: nvidia

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081199

Title:
On high resolution modes, after screen resume from power saving, the
display configuration gets lost, and sometimes Gnome crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2081199/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-09-19 Thread Mario Emmenlauer

For anyone coming here, the follow-up issue is in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/2081199

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075525

Title:
  After screen blank, the displays configuration gets lost

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2075525/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080823] Re: 6.8.0-44 breaks amdgpu-dkms 6.8.5

2024-09-18 Thread Mario Limonciello

> I don't know why i use dkms

When you installed the packaged version of ROCm you can use arguments to
decide whether or not to build the DKMS package.  I don't expect you
really need it with this kernel version.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080823

Title:
  6.8.0-44 breaks amdgpu-dkms 6.8.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080823/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-09-18 Thread Mario Emmenlauer

I'm sorry for coming back to this, but the new display cable does *not*
help.

I have just had actually my worst Gnome crash so far, and it happened
immediately on the first try, after upgrading my HDMI cable to a
supposedly decent 2.1 standards cable, and switching again to 4K
resolution at 60 Hz (no fractional scaling). When the monitors woke up
from display power save, only one monitor became active. I've waited for
about one minute with no avail. When later opening the Gnome display
settings, Gnome crashed, and I could only log out.

Attached is an excerpt from syslog, from around the time then I unlocked
the display coming back from suspend, until the Gnome crash.

I confirm that I have ubuntu-drivers-common:amd64/noble-updates
1:0.9.7.6ubuntu3.1, so this should have the issue fixed?

** Attachment added: "Excerpt from syslog"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2075525/+attachment/5818944/+files/log.txt.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075525

Title:
  After screen blank, the displays configuration gets lost

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2075525/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080823] Re: 6.8.0-44 breaks amdgpu-dkms 6.8.5

2024-09-17 Thread Mario Limonciello

I am tending to agree with Juerg, this is not Ubuntu's bug.  They picked
up a stable update that fixed a problem, but it just so happens this
DKMS doesn't compile anymore.

I think the DKMS package will need to be re-spun due to this change.
I suggest reporting it here: https://gitlab.freedesktop.org/drm/amd/-/issues

---


But that being said - why not use the amdgpu driver distributed in Ubuntu?

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080823

Title:
  6.8.0-44 breaks amdgpu-dkms 6.8.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080823/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-09-12 Thread Mario Emmenlauer

Ok, so, for what its worth, here is my current summary:
 - I already have `ubuntu-drivers-common` `1:0.9.7.6ubuntu3.1` installed since 
a few days, and it did not help resolve the problem.
 - I have reduced the monitor resolution, and this reliably circumvents the 
problem (no more issues since 24h)

I will try with a more modern HDMI cable next, to see if that helps!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075525

Title:
  After screen blank, the displays configuration gets lost

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2075525/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080294] Re: linux 6.8.0-44 + amdgpu 6.2.60200-2009582.24.04

2024-09-11 Thread Mario Limonciello

This definitely isn't an Ubuntu kernel bug, I will reject it as such.
You can file an issue here:
https://gitlab.freedesktop.org/drm/amd/-/issues if you have problems
stemming from that script.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080294

Title:
  linux 6.8.0-44 + amdgpu 6.2.60200-2009582.24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080294/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080294] Re: linux 6.8.0-44 + amdgpu 6.2.60200-2009582.24.04

2024-09-11 Thread Mario Limonciello

> That's an unsupported DKMS, not a kernel problem. Is there any reason
why you don't use the kernel's amdgpu driver?

The DKMS driver takes an upstream snapshot of amdgpu for use with older
kernel versions.  As I notice that in the above error log the DKMS
driver is from "6.8.5-2009582.24.04" you can probably remove it and just
use the amdgpu driver provided with the Ubuntu 6.8 kernel series.

> I don't know if mixing Ubuntu amdgpu with ROCm libraries from amdgpu-
install script will work. Is there another way?

The ROCm install script offers support for with or without DKMS package.
You can just install without DKMS package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080294

Title:
  linux 6.8.0-44 + amdgpu 6.2.60200-2009582.24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080294/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-09-11 Thread Mario Emmenlauer

Also, the issue goes away when I turn down the resolution to 1920x1080
again. So it is certainly tied to the high resolution.

The problem may have something to do with the HDMI cable on one of the
two monitors. Only one monitor uses HDMI, the second monitor uses
DisplayPort. Before I switched to HDMI 2.0, the refresh rate was limited
to 30 Hz at 3840x2160 resolution, and the problem was also not present.

So possibly the problem is related to the high resolution and refresh
rate, as it was not present with lower refresh rate, and disappears with
lower resolution.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075525

Title:
  After screen blank, the displays configuration gets lost

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2075525/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-09-11 Thread Mario Emmenlauer

Dear @vanvugt and all,
I am so happy to find this issue, because I suffer from the same problem.
However I am very surprised to see this issue closed as fixed, when @raffaeler
was saying that the proposed fix does *not* solve the main problem (and it does
not solve it for me either)!

So the original, main problem reported here in this issue is (quoting from OP):

After a period of inactivity, the screens get blanked as configured.
When I move the mouse and the screens unblank, sometimes (not always) the
configuration is changed by mirroring the same content on the two displays.
Anyway, the display are still configured as extended in the applet.
Trying to change some settings to restore the desired configuration never work.

I have exactly this problem, and it is driving me crazy. The problem appeared
for me with Ubuntu 22.04, after I changed:
- Second monitor was set from older HDMI standard to HDMI 1.4
- Screen resolution was increased from 1920x1080 to 3840x2160 @60 Hz

Prior to that, I never had problems with the displays or their configuration.
After that change, the problem persists. Here is what I tried:
- Update from Ubuntu 22.04 to 24.04
- Change NVIDIA driver from 535 to 550
- Change NVIDIA driver to nouveau
- Unplug and re-plug all cables

Nothing helped. I'm using X11 instead of wayland, because currently
VSCode does not support wayland (yet). Not sure if this is related.

Attached a snipped from syslog from when the issue comes.

** Attachment added: "syslog-x11-error.txt"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2075525/+attachment/5815624/+files/syslog-x11-error.txt

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075525

Title:
After screen blank, the displays configuration gets lost

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2075525/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078573] Re: I can no longer boot from my Thunderbolt disk

2024-09-09 Thread Mario Limonciello

Thanks for checking.  I believe what's going on is that it resets the
topology, but the policy to re-authorize it doesn't happen because bolt
is missing until the rootfs is loaded.  So initramfs needs a hook to
include bolt.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078573

Title:
  I can no longer boot from my Thunderbolt disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2078573/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2079892] Re: IOMMU or firmware protection issues

2024-09-07 Thread Mario Limonciello

Fwupd only reports the security of the firmware that it can measure.
It's not a fwupd bug if there is a problem.

** Changed in: fwupd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079892

Title:
  IOMMU or firmware protection issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2079892/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078573] Re: I can no longer boot from my Thunderbolt disk

2024-09-06 Thread Mario Limonciello

Thanks for confirming it.  You can also try to add thunderbolt to
/etc/initramfs-tools/modules to see if that's enough to fix the issue
instead of the kernel command line workaround.

I suspect it's not though, and that a hook will be needed to add:
* /lib/udev/rules/90-bolt.rules
* bolt.service
* boltd

In any case; I feel the bug is now in initramfs-tools.

** Changed in: linux (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078573

Title:
  I can no longer boot from my Thunderbolt disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2078573/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078573] Re: I can no longer boot from my Thunderbolt disk

2024-08-31 Thread Mario Limonciello

Try adding thunderbolt.host_reset=0 to your kernel command line.
Suspect it's the changes that came in
https://launchpad.net/ubuntu/+source/linux/6.8.0-38.38:

- thunderbolt: Introduce tb_port_reset()
- thunderbolt: Introduce tb_path_deactivate_hop()
- thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4
  routers
- thunderbolt: Reset topology created by the boot firmware

These changes were done to fix a number of other issues with re-using
boot firmware settings.  That kernel command line option will align it
with old behavior as a workaround.

I feel that a "correct" solution for your issue would be for
'thunderbolt.ko' and boltd to be included in the initramfs so that the
reset happens before the rootfs is mounted.

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078573

Title:
  I can no longer boot from my Thunderbolt disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2078573/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064595] Re: AMD Rembrandt & AMD Rembrandt-R: Suspend hangs system

2024-08-29 Thread Mario Limonciello

This appears to be a different problem even if it leads to same symptom.
Please open a separate issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595

Title:
  AMD Rembrandt & AMD Rembrandt-R: Suspend hangs system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064595/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077920] Re: [RTL8821CE] awful performance

2024-08-28 Thread Mario Limonciello

> But building a new kernel and switching to it without deeper
experience and a fallback would be too hard for me.

No need to build a new kernel.  There are binaries in the link that was
posted above. You can grab some of those to try.  Just note that you
need to turn off secure boot if you have it enabled because they're not
signed.

This is an important debugging step as it helps to identify if it's
already fixed in a newer kernel and it's a backport effort for a fix or
if it's still an upstream issue.  If it's still an upstream issue it
should be reported to the developers of the driver.

> pci bus timeout, check dma status

Maybe it's an issue with the DMA implementation of the wireless driver.
You can experiment with the IOMMMU disabled (amd_iommu=off) to see if
that changes anything.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077920

Title:
  [RTL8821CE] awful performance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077920/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077411] Re: [Ubuntu 24.04] Somtimes unable to exit 'fwupd' install excution via Redfish protocol

2024-08-26 Thread Mario Limonciello

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077411

Title:
  [Ubuntu 24.04] Somtimes unable to exit 'fwupd' install excution via
  Redfish protocol

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2077411/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077553] Re: ESP detection failures

2024-08-23 Thread Mario Limonciello

That regression isn't real.  Looks like an infra problem.

0s autopkgtest [15:16:00]: starting date and time: 2024-08-23 15:16:00+
  0s autopkgtest [15:16:00]: git checkout: fd3bed09 nova: allow more retries 
for quota issues
  0s autopkgtest [15:16:00]: host 
juju-7f2275-prod-proposed-migration-environment-9; command line: 
/home/ubuntu/autopkgtest/runner/autopkgtest --output-dir 
/tmp/autopkgtest-work.4sctwlte/out --timeout-copy=6000 --setup-commands 'ln -s 
/dev/null /etc/systemd/system/bluetooth.service; printf 
"http_proxy=http://squid.internal:3128\nhttps_proxy=http://squid.internal:3128\nno_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com\n";
 >> /etc/environment' --apt-pocket=proposed=src:fwupd --apt-upgrade update-motd 
--timeout-short=300 --timeout-copy=2 --timeout-build=2 
'--env=ADT_TEST_TRIGGERS=fwupd/1.9.24-1~24.04.1' -- lxd -r 
lxd-armhf-10.145.243.163 lxd-armhf-10.145.243.163:autopkgtest/ubuntu/noble/armhf
  0s : failure: ['lxc', 'launch', '--ephemeral', 
'lxd-armhf-10.145.243.163:autopkgtest/ubuntu/noble/armhf', 
'lxd-armhf-10.145.243.163:autopkgtest-lxd-ahyvel'] failed (exit status 1, 
stderr 'Error: The remote "lxd-armhf-10.145.243.163" doesn\'t exist\n')
  0s autopkgtest [15:16:00]: ERROR: testbed failure: unexpected eof from the 
testbed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077553

Title:
  ESP detection failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/2077553/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077553] Re: ESP detection failures

2024-08-23 Thread Mario Limonciello

Verified that ESP is still being identified properly on my test systems.

❯ sudo fwupdtool esp-list
Loading… [   ]15:24:50.821 
FuHistoryLoading… 
[** ]
Selected volume: /org/freedesktop/UDisks2/block_devices/nvme0n1p1
/boot/efi/EFI/ubuntu/grubx64.efi
/boot/efi/EFI/ubuntu/shimx64.efi
/boot/efi/EFI/ubuntu/mmx64.efi
/boot/efi/EFI/ubuntu/BOOTX64.CSV
/boot/efi/EFI/ubuntu/grub.cfg
/boot/efi/EFI/ubuntu/fwupdx64.efi
/boot/efi/EFI/BOOT/BOOTX64.EFI
/boot/efi/EFI/BOOT/fbx64.efi
/boot/efi/EFI/BOOT/mmx64.efi
/boot/efi/EFI/fwupd/fwupdx64.efi
❯ apt policy fwupd
fwupd:
  Installed: 1.9.24-1~24.04.1
  Candidate: 1.9.24-1~24.04.1
  Version table:
 *** 1.9.24-1~24.04.1 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1.9.16-1 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages

** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077553

Title:
  ESP detection failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/2077553/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2076151] Re: [SRU] Support new hardware system in mediatek_scalar plugin

2024-08-22 Thread Mario Limonciello

KC - Yes, I've already uploaded it to unapproved queue.  It's waiting
for SRU team member review (see comment #8).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076151

Title:
  [SRU] Support new hardware system in mediatek_scalar plugin

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2076151/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 2076191] Re: gpsmon crashes (segfault)

2024-08-22 Thread Mario Lorenz

Bryce,

I can report the following:

Am 14. Aug 2024, um 15:22:30 schrieb Bryce Harrington:
> Mario, can you provide a log showing the assertion failure?

It simply says:
gpsmon: assertion failure, probable I/O error

Or with gpsmon -D5 to provide some more details:

gpsmon:INFO: startup at 2024-08-22T21:44:50.000Z (1724363090)
gpsmon:PROG: CORE: gpsd_activate(tcp://localhost:2947, 1) fd -1
gpsmon:PROG: CORE: gpsd_open(tcp://localhost:2947) fd -1
gpsmon:PROG: CORE: opening TCP feed at localhost, port 2947.
gpsmon:PROG: CORE: TCP tcp://localhost:2947 IP  opened on fd 3
gpsmon:PROG: CORE: activate fd 3 done
gpsmon: assertion failure, probable I/O error

gpsd-3.25-dev (GIT download, built myself) does not suffer from this
problem. I havent bisected it though.

-git seems to mostly work, there is only the oddity remaining that after
I powercycle the GPS, gpsd does not seem to completely recognize it
again and switchin the unit to UBX mode as it does when gpsd is started.
With NMEA the output in particular of cgps flickers between n/a and
correct data. I have not yet checked if this is merely cosmetic or if
does influence time synchronization via chronyd.

I can further report that the problem does not seem to change with GPS
units, at least I have now sample size = 2 with a NEO-M8N unit. It
behaves identically (crash with distributed package, crash is fixed with
mitchdz updated package, assertion error still happens, until I switch
to -git.

Best regards,
Mario

-- 
Mario LorenzInternet:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076191

Title:
  gpsmon crashes (segfault)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/2076191/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077490] Re: Error: out of memory while booting after installing the linux-firmware in proposed

2024-08-22 Thread Mario Limonciello

Perhaps a dumb question - but why even bother to put any of the GPU
binaries in the initramfs?  There should be a good enough display from
the pre-boot framebuffer that none of them should be needed with
simpledrm.

Punt i915.ko, xe.ko, amdgpu.ko, nvidia.ko out of the initramfs and let
them get loaded later in boot.  It should solve this problem I would
expect.  Furthermore this gets you a lot "closer" to server built and
signed initrd images.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077490

Title:
  Error: out of memory while booting after installing the linux-firmware
  in proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2077490/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064023] Re: Installer should detect small ESP in a dual boot

2024-08-22 Thread Mario Limonciello

As this is really a development effort not a bug I've also filed it at
https://github.com/canonical/ubuntu-desktop-provision/issues/800.

** Bug watch added: github.com/canonical/ubuntu-desktop-provision/issues #800
   https://github.com/canonical/ubuntu-desktop-provision/issues/800

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064023

Title:
  Installer should detect small ESP in a dual boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2064023/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 10431 matches

Mail list logo