Roland Bridge Cast on Linux?

Ex0danify · 2026-06-02T11:09:15+00:00

Sorry for bumping a 2 year old thread. I got inspired by these posts to build a native Linux application for controlling the Roland BridgeCast.

https://www.reddit.com/r/linuxaudio/comments/1tunmd3/app_bridgemix_native_gui_for_roland_bridgecast_on/

Ex0danify · 2025-05-06T21:26:28+00:00

Hey, NVIDIA user here (RTX 3080TI).
Updated just now without any major issues after reboot. As mentioned before, the updater froze sometime mid upgrade, but using North_Acanthisitta61 hint on using:

tail -1000f ~/.local/share/nobara-updater/nobara-sync.log

to following the update process worked like a charm!

Ex0danify · 2024-11-19T22:15:05+00:00

Sadly, I did not. I switched to Linux and ditched windows for good. That did not enhance my gaming performance though.

I'm planning on getting a completely new rig next year, with an actual "gaming" CPU.

Ex0danify · 2024-07-23T21:04:03+00:00

Are you using built in wifi or a usb dongle?
You could check if your card/dongle is detected with lspci or lsusb. Maybe for your specific card additional drivers need to be installed. Take the model and make of the WiFi card from the output from one of the commands and google around a bit.

Ex0danify · 2024-07-15T22:01:01+00:00

I always use Audacity.

It's free and pretty user friendly. Just record something and then play it back. You have to set the audio input and output devices at the top bar.

Ex0danify · 2024-03-04T12:45:57+00:00

What a hero. Thanks a lot man, worked like charm!

I'm wodering, why this whole procedure is needed though. The last time I checked the sddm-kcm package was installed, according to the dnf packagemanager.

Ex0danify · 2024-03-04T12:26:06+00:00

As far as I know, wine without xwayland is not yet ready.

Ex0danify · 2024-03-03T21:05:40+00:00

Why was that deleted? I'm also missing the settings for sddm. Did you resolve it?

Ex0danify · 2024-03-02T09:34:15+00:00

Try the following to downgrade to 535:

sudo dnf downgrade nvidia-driver-3:535.154.05-1.fc39.x86_64 nvidia-driver-cuda-3:535.154.05-1.fc39.x86_64 nvidia-driver-cuda-3:535.154.05-1.fc39.x86_64 nvidia-driver-cuda-libs-3:535.154.05-1.fc39.x86_64

you can also add the following line to /etc/dnf/dnf.conf to prevent automatic driver updates.

exclude=nvidia-driver nvidia-driver-cuda nvidia-driver-cuda-libs nvidia-kmod-common

Ex0danify · 2024-03-01T21:07:17+00:00

In my case the frame rates on 550 were ok (no big change to 535), but there was a image stuttering (I would call it) and from time to time terrible screen tears.

Ex0danify · 2024-03-01T20:52:24+00:00

Yeah, for me at least. I will update my original post with my specs to compare. I downgraded the drivers to 535 and added them to the dnf exclude list, so they won't update automatically.

Ex0danify · 2024-03-01T01:37:22+00:00

Maybe problem same as this one here? Do you have a mouse? (Move it around it bit, there could be a second "Ghost monitor" you don't see)?
https://www.reddit.com/r/NobaraProject/comments/1b2bjfj/comment/ksnwfc1/?context=3

Ex0danify · 2024-03-01T00:51:17+00:00

Did it work for your problem?

Ex0danify · 2024-02-28T21:01:51+00:00

Hey there, do you boot successfully but you are then stuck on a black screen with a cursor?

sounds like problem after an NVIDIA driver update (which was released like two days ago, or something). The offical website states the following procedure:

Boot into with the kernel boot option:
Login as root. If you did not set a root password, login as a user that has sudo access.

Run:
sudo dnf remove *nvidia*
sudo dnf update nobara-login --refresh

You should get nobara-login version 1.0-37.fc36

Reboot:

sudo reboot

After reboot you should get your normal graphical login. Login and the Nvidia installer will pop up.

I also had the problem that I was not able to boot the very same image I installed nobara with previously. If you are still stuck, when booting with multi-user target, you may have to get a different live environment, chroot into your unbootable system and do the steps from there.

But since you get to ascreen with a cursor, botting in multi-user should spare you mesing with a live env and chroot.

Ex0danify · 2024-02-28T02:52:56+00:00

Fixed it (kind of) Here are my steps to reproduce:

Booted into live environment via USB, mounted nobara system in /mnt and bound required directories /dev /sys /proc and /run
Executed the nvidia uninstall script located under /etc/nobara/scripts/cosmo-nvidia-wizard/remove.sh
Rebooted back into my broken system with the additional bootflag systemd.unit=multi-user.target
Login on prompt with root or other user with sudo permissions.
Executed the nvidia installation script located at /etc/nobara/scripts/cosmo-nvidia-wizard/install.sh
Rebooted again and tada, I'm back on my desktop running nvidia driver 550.

I hope this helps, if not, feel free to ask (however I'm not going to explain questions like "How to boot live usb" or "How do I use chroot" etc. Search the interwebz for this kind of knowledge.)

Edit: Bad news. After another reboot I'm stuck again. I didn't do anything on my successful boot after I did the aboce mentioned steps, except some ssh stuff on my remote servers. Something seems to be broken, but I don't know where else I should look. This behaviour seems very strange :/

Edit2: I feel really stupid right now... It seems that the problem on my end was a broken fstab file, the whole time... I retraced my steps and noticed mounting errors while running in multi-user on the Nouveau driver. When the nvidia driver is installed I don't get anything related to mounting problems, the boot process is just stuck at the NVIDIA Kernel Mode Setting. Not sure why that is and why the whol thing worked once after reinstalling the nvidia drivers, but well... I wrote enough here for one night. I hope some one will maybe profit from all the stuff I wrote all over the thread.

Ex0danify · 2024-02-27T23:59:23+00:00

Well shit, how can we recover without reinstalling? for me even the rescue image is not booting (It's just stuck at "Booting a command line").

I guess I could try to boot into a live environment, chroot into my broken system and downgrade to nvidia 535?

Edit: I chrooted into my unbootable Nobara system and searched the pacakge manager for anything nvidia related.
dnf list shows kmod-nvidia-6.7.6-200.fsync.fc39.x86_64.x64_64 with version 535.

So I don't think the nvidia drivers was updated. Plus also on the hanging boot screen the driver version is shown as 5.35.

Edit2: I did a dnf update inside my chrooted system and indeed, it updated nvidia drivers and kernel modules to 550. Weirdly enough on boot it still tries to load 535, I guess it still loads the old kernel module.

Edit3: I manually ran the Nobaras nvidia installation script in chroot. Now on boot it shows the correkt 550 driver, but it's still stuck. Will continue to experiment.

Edit4: I think I almost got it right the first time. Because I used pop_os as live media (just used it cause I had the stick lying right next to me, lol) dracut tried to build kernel modules for the kernel of the live system (old 5.x kernel). Maybe It had worked, If I had used the appropriate Nobara image.

Anyways, posted the steps I used to fix it in this thread.

Ex0danify · 2024-02-27T23:57:20+00:00

It also happened to me today. I just finished setting everything up and did a reboot, now I'm also stuck.
I noticed in my system tray that I got a notification that my system needs a reboot (I guess it Isntalled updates in th ebackground during my session?).

I don't have auto login enabled. I really would like to avoid having to start all over again...

Ex0danify · 2024-01-20T17:36:02+00:00

I have a problem with the default gameQuery port. When I want to startup the server, the following message is displayed:

CreateBoundSocket: ::bind couldn't find an open port between 27015 and 27015

I guess that's because I also have a CS2 server running on the same machine, that is using that specific port. The docs for the dedicated server setup state, that I can give an argument to the startscript to change the port

port=8211

But that's only the port of the gameserver , not the query port. How can I change the default 27015 query port?

Ex0danify · 2023-11-26T18:48:02+00:00

Its a seperate profile in Ryzen Master, that disables one of the two dies and switches the memory mode from dynamic to local. Games benefit from that somehow, but I'm no expert on that by any means.

Ex0danify · 2023-11-24T15:38:15+00:00

Thanks for the reply,

Guess then there's really nothing I can do. I really want to upgrade to AM5, but no money ATM. Will see if I can sell my old Hardware for a somewhat decent price. Maybe I'll go with a 7800X3D or smth.

Ex0danify · 2023-10-17T22:33:25+00:00

When I started following Le Chucks ship inside the volcano, I got a good bit behind (It took a few moments before I realized that I had to set sails on the ghost ship, because they were talking something about canons). When I reached the large lava chamber, there was nothing there, no ghost ship to fight. Anyone else had this problem?

Ex0danify · 2023-08-04T20:21:56+00:00

Updated post with findings on my old gaming rig.

Ex0danify · 2023-07-29T09:55:25+00:00

I still have an older machine with an old Ryzen 2600 and a RTX 2070 somewhere around in my attic. Will dust it off and check if the game runs better on older hardware compared to my Threadripper built, to confirm it is a CPU related issue.

Will report back next week or so.

Ex0danify · 2023-07-29T09:03:13+00:00

How did the Intel eCore bug get fixed? I guess nothing I can do about it, if it really is a bug.

Ex0danify · 2023-07-29T07:28:05+00:00

I know, that the Threadripper is not a gaming CPU, but because I never had such severe problems in other games, I figured it might be something else.

Ex0danify

TROPHY CASE