[00:06] <mykhyggz> so I want to install this next to my windoze and ubuntu lts. I have free partition sda8. mounted is /dev/sda1 on /boot/efi -- so when I get the option to do "something else" do I just accept boot on /dev/sda and select sda8, then? Overwriting my work install won't be okay... ;-)
[00:25] <mykhyggz> Well, no one to hold my hand. Fair enough, I take my chances, then. Cheers!
[00:44] <mykhyggz> well, I totally chickened out -- I can't see what I'm to do to be sure I'm installing on a free partition and not b0rking my work installations. I have an ext4 ready, /boot exists, swap exists. I shouldn't need to format or partition... :(
[01:07] <mykhyggz> It seems there must be a way to just ensure install writes to a particular partition, so I can boot to studio without touching other OSs.
[01:08] <Eickmeyer> mykhyggz: Using the "something else" is exactly how to ensure it writes to a particular partition.
[01:09] <Eickmeyer> If you need to do partitioning ahead of time, try using gparted.
[01:09]  * Eickmeyer doesn't like ubiquity's built-in partitioner
[01:10] <mykhyggz> That's what it looks like. So highlight that partition -- and go? It is already ready. Yeah, I guess that's what is unnerving me -- I already prepped with gparted.
[01:10] <mykhyggz> But just highlight the partition I want, and click install should work? It will pick up the swap and /boot from what is already there?
[01:10] <Eickmeyer> No, make sure that it is going to use the partition (edit, click Use As), and make sure it assigns root (/) to that partition.
[01:11] <Eickmeyer> No, you'll have to manually assign /boot to that partition if you wish to use the same /boot.
[01:11]  * Eickmeyer recommends against that unless it's /boot/efi
[01:11] <mykhyggz> it is efi, yes.
[01:12] <Eickmeyer> Then yes. Really, it should automatically use the existing /boot/efi and swap partitions. Everything else must be manually assigned from that screen.
[01:12] <mykhyggz> so select three, and assign three partitions for / /boot and swap? Never seen this interface before.
[01:12]  * mykhyggz sez Thanks!
[01:12] <Eickmeyer> You're welcome. Good luck.
[01:13] <mykhyggz> I'll need it. Cheers!
[01:14] <Eickmeyer> mykhyggz: This isn't unique to Ubuntu Studio, so if you don't get a response here in the future, try #ubuntu.
[01:14] <mykhyggz> Thanks, will do.
[02:08] <mykhyggz> Eickmeyer: thanks again, I have new grub entries and still able to boot into my work. Now to go play with my realtime kernel!
[02:10] <Eickmeyer> mykhyggz: Have fun! Just understand that we don't have a realtime kernel, but a lowlatency one with the PREEMPT_RT patch in place.
[02:10] <mykhyggz> Ah, right. It is still an improvement though, from what I saw when testing.
[02:11] <studiobot> Austin Erlandson was added by: Austin Erlandson
[02:12] <Eickmeyer> mykhyggz: Yes. An actual realtime kernel does no good on hardware that doesn't support it, which is very, very limited to OEM application, such as consoles and what-not. Even if a kernel claims to be rt, it's likely only lowlantency and simply has the PREEMPT_RT flag set.
[02:15]  * mykhyggz sees the fog of distant memories clearing a bit. Been a while since patching kernels or the like.
[02:15] <mykhyggz> Thanks again, gonna go play now. ;-)
[02:24] <studiobot> <Austin Erlandson> Hey again, so I'm trying to run the "try Ubuntu Studio from us stick" option in grub but I'm pretty sure it's not setup to work with a 4k panel maybe? I'm seeing some errors in the dbus(?) output when I select that option... … I'm trying to install on an X1 Extreme. Any tips?
[02:25] <studiobot> <Eickmeyer> @Austin Erlandson [Hey again, so I'm trying to run the "try Ubuntu Studio from us stick" option in …], Yeah, that stumped me in one fell swoop.
[02:26] <studiobot> <Eickmeyer> I'd say get on IRC and check the #xubuntu or #ubuntu channels.
[02:27] <studiobot> <Austin Erlandson> Okay no worries! Thanks for the forward 😊 … I'm a guitarist turn dev so I never know what language to speak when :)
[02:27] <studiobot> <Eickmeyer> Yeah. Ubuntu Studio _is_ Ubuntu, so those channels are helpful. Xubuntu when dealing with the UI, and Ubuntu when dealing with the underlying system.
[02:28] <studiobot> <Austin Erlandson> Perfect 👌
[03:08] <mykhyggz> Well, so far, I was running the software update and my screen went blank. Had to power off. I notice there are two boot options, ubuntu "low latency" and plain ubuntu. No doubt the preemption disallowed the screen to wake up? So, better to do maintenance in the "plain" option?
[03:08] <mykhyggz> Anyway, turned of the screen blanking for when I'm on AC power.
[03:09] <mykhyggz> And finishing the updates with no "low-latency" option. Does this make some sense, I wonder? ;-)
[03:10] <mykhyggz> Oh, well, just making a public note then. I'll figure it out eventually.
[03:26] <Eickmeyer> Left before I could respond.
[03:26] <Eickmeyer> (it's the exact same kernel)
[12:06] <studiobot> <Chris> Using 16.04. Duel boot with Windows 7 ( on sepRE physical disk).I am in recovery mode and whatever it has done it hasn't fixed the problem. I have an (initrams) prompt. And it is suggesting I do a manual FSCK. I am not clued up about commands. Any suggestions apart from hard reboot?
[12:07] <studiobot> <Chris> Had similar problem yesterday and recovery appeared to fix booting.
[12:09] <studiobot> <Chris> I had to do a hard reboot earlier yesterday and that seemed to cause the boot to fail after I chose Ubuntu on the Grub menu.
[12:20] <studiobot> <Chris> Just searching online and now using a US DVD disk to check errors.
[13:51] <studiobot> <Chris> I am back into Ubuntu Studio. I used the Live DVD and terminal to do a manual fsck after reading up online using my phone.  … sudo fsck /dev/sdb1 … That appears to have sorted it.  … I will replace 16 04 with 18.10 soon.
[15:52] <studiobot> <Duke> Erich, removing calf-ladspa did not help. Thanks for the suggestion though.
[16:01] <studiobot> <Eickmeyer> @Duke [Erich, removing calf-ladspa did not help. Thanks for the suggestion though.], Hey, it was worth a shot. That's the most common problem the Ardour devs tell me about.
[17:35] <studiobot> <Duke> I really think that it is a problem running linux on a Mac.  I had the same problem with Ardour in Manjaro linux. I'm going to test Fedora from a USB flash drive, to see if Ardour in Fedora does the same thing.