rpm-ostree has no "progress bar" you just have to trust it does its thing if it fails it will error

C

char•5/5/24, 6:19 PM

gotcha

C

char•5/5/24, 6:20 PM

how long does it take on average?

A

antheas•5/5/24, 6:20 PM

k bazzite installed successfully

A

antheas•5/5/24, 6:20 PM

13 minutes

Cchar how long does it take on average?

T

tryhardsoccermomswag•5/5/24, 6:25 PM

depends on the drive and your internet speed

C

char•5/5/24, 6:28 PM

it finished relatively quick

C

char•5/5/24, 6:29 PM

thanks for the help btw :)

Aantheas by the way plymouth got a bit greedy whats going on with that spinner

F

fiftydinar•5/5/24, 6:38 PM

that spinner is huge lol

HHikariKnight rpm-ostree has no "progress bar" you just have to trust it does its thing if it ...

W

wolfyreload•5/5/24, 6:48 PM

Btw I just found a progress log for the rpm-ostree daemon

journalctl -u rpm-ostreed -f

journalctl -u rpm-ostreed -f

journalctl -u rpm-ostreed -f

journalctl -u rpm-ostreed -f in this complaining thread https://github.com/ostreedev/ostree/issues/3118 Can actually see as the layers get downloaded

GitHub

No download progress when rebasing to a container image · Issue #31...

When rebasing to a container image, the inital download of the image layers before the rebase opration takes some time, and there is no indication of something happenning in the terminal . I first ...

Ttryhardsoccermomswag That was actually due to the linux ports of the games. Some of them like Team Fo...

X

xX_dongmaster_Xx•5/5/24, 6:52 PM

Don’t worry source games work good on Bazzite

X

xX_dongmaster_Xx•5/5/24, 6:53 PM

To this moment i’ve tried CSS, HL2 and L4D2

Wwolfyreload Btw I just found a progress log for the rpm-ostree daemon `journalctl -u rpm-ost...

W

wolfyreload•5/5/24, 7:10 PM

@nickname would it be worth making a note of this under section https://universal-blue.discourse.group/docs?topic=36#terminal-command-to-update-manually-7 in the documentation?

Universal Blue

Updates, Rollback, and Rebasing on Bazzite

Yes it is true for all of them, however I mostly focus on documentation on the Bazzite image which is why it’s here. Desktop images of Bazzite follow the same automatic update style that the main images follow. However, there’s also the -deck images that do not follow this which is why I wanted to differentiate between them. As for pinning, w...

C

char•5/5/24, 7:14 PM

if i wanted to dualboot this + tiny11 on the ROG Ally, would grub work / have touch support?

A

antheas•5/5/24, 7:16 PM

Use the bios to boot

A

antheas•5/5/24, 7:16 PM

Or refind

C

char•5/5/24, 7:17 PM

that could work

L

Leaf•5/5/24, 7:17 PM

hi yall! my friend got a steam deck and is having issues with the screen dimming while he is watching videos, and energy saving settings under the Power Management tab in system settings not sticking after making changes. even just clicking defaults and then apply doesn't save, and is reverted after reopening settings. Is this a thing the bazzite-deck image is known to fix?

L

Leaf•5/5/24, 7:19 PM

he is also having issues with his bluetooth headphones cutting in and out, which I am hoping is also fixable just by getting him onto something more stable like bazzite, and away from arch. both are issues I have never run into in my time on linux, so I am not sure about any of this

LLeaf he is also having issues with his bluetooth headphones cutting in and out, which...

C

char•5/5/24, 7:22 PM

the arch on the steam deck is stable

C

char•5/5/24, 7:22 PM

SteamOS despite being based on Arch is not a rolling distro, its more akin to how ChromeOS is based on Gentoo

L

Leaf•5/5/24, 7:25 PM

I mean it might not be rolling, but I won't believe it is stable if my friend's first experience with steamOS wasn't more buggy than anything I have ever experienced before on linux. for some dumb reason it isn't even running kde 6 yet, so there is no good reason he should have this many issues

C

char•5/5/24, 7:35 PM

bazzite from my limited experience (granted i installed it on a ROG ally because the alternative is windows 11) has been somewhat unstable compared to stock SteamOS

C

char•5/5/24, 7:35 PM

nothing major though and i have no ill will towards the developers

A

Aru•5/5/24, 7:38 PM

useless

$ cat /sys/devices/virtual/dmi/id/chassis_vendor
Default string

$ cat /sys/devices/virtual/dmi/id/chassis_vendor
Default string

$ cat /sys/devices/virtual/dmi/id/chassis_vendor
Default string

$ cat /sys/devices/virtual/dmi/id/chassis_vendor
Default string

AAru 😒 useless ``` $ cat /sys/devices/virtual/dmi/id/chassis_vendor Default string ...

K

Kyle Gospo•5/5/24, 7:53 PM

Does DMI have any identifying information?

KKyle Gospo Does DMI have any identifying information?

A

Aru•5/5/24, 7:55 PM

dmi is

V3

V3

V3

V3

A

Aru•5/5/24, 7:55 PM

so i was just going to work with that for now

AAru dmi is `V3`

K

Kyle Gospo•5/5/24, 7:55 PM

Not bad

K

Kyle Gospo•5/5/24, 7:55 PM

And then I think what we can do is just clone valve's steamdeck-dsp services

K

Kyle Gospo•5/5/24, 7:55 PM

Since ours would only apply to hardware theirs doesn't apply to

K

Kyle Gospo•5/5/24, 7:55 PM

Make it a separate package

KKyle Gospo And then I think what we can do is just clone valve's steamdeck-dsp services

A

Aru•5/5/24, 7:56 PM

hrm, it's just a single conf file. i was thinking of adding it to the

bazzite-hardware-setup

bazzite-hardware-setup

bazzite-hardware-setup

bazzite-hardware-setup file

K

Kyle Gospo•5/5/24, 7:56 PM

And then I can make that a separate package like bazzite-dsp so others can benefit like Nobara

A

Aru•5/5/24, 7:56 PM

~/.config/wireplumber/wireplumber.conf.d/alsa-soft-mixer.conf

monitor.alsa.rules = [
  {
    matches = [
      {
        # This matches all cards.
        device.name = "~alsa_card.*"
      }
    ]
    actions = {
      update-props = {
        # Apply properties on the matched object.

        # Do not use the hardware mixer for volume control. It
        # will only use software volume. The mixer is still used
        # to mute unused paths based on the selected port.
        api.alsa.soft-mixer = true
      }
    }
  }
]

~/.config/wireplumber/wireplumber.conf.d/alsa-soft-mixer.conf

monitor.alsa.rules = [
  {
    matches = [
      {
        # This matches all cards.
        device.name = "~alsa_card.*"
      }
    ]
    actions = {
      update-props = {
        # Apply properties on the matched object.

        # Do not use the hardware mixer for volume control. It
        # will only use software volume. The mixer is still used
        # to mute unused paths based on the selected port.
        api.alsa.soft-mixer = true
      }
    }
  }
]

~/.config/wireplumber/wireplumber.conf.d/alsa-soft-mixer.conf

monitor.alsa.rules = [
  {
    matches = [
      {
        # This matches all cards.
        device.name = "~alsa_card.*"
      }
    ]
    actions = {
      update-props = {
        # Apply properties on the matched object.

        # Do not use the hardware mixer for volume control. It
        # will only use software volume. The mixer is still used
        # to mute unused paths based on the selected port.
        api.alsa.soft-mixer = true
      }
    }
  }
]

~/.config/wireplumber/wireplumber.conf.d/alsa-soft-mixer.conf

monitor.alsa.rules = [
  {
    matches = [
      {
        # This matches all cards.
        device.name = "~alsa_card.*"
      }
    ]
    actions = {
      update-props = {
        # Apply properties on the matched object.

        # Do not use the hardware mixer for volume control. It
        # will only use software volume. The mixer is still used
        # to mute unused paths based on the selected port.
        api.alsa.soft-mixer = true
      }
    }
  }
]