[02:04] <OvenWerks> I wonder if that is grub out of our package...
[02:20] <wonko> Hmmm. Live iso doesn't work so good for me
[02:20] <wonko> Going to try safe graphics
[02:21] <wonko> Oh wait
[02:21] <wonko> Shit, I know
[02:21] <wonko> Grumble onboard crappy video
[02:26] <wonko> Can I force the live iso to use the GTX instead of the onboard crap?
[02:27] <wonko> I wonder if I blacklist the onboard garage if it'll use the GTX then
[02:33] <wonko> Nope, that didn't work. Boo.
[02:35] <wonko> Dammit, off to sitting in the garage I go
[02:38] <Eickmeyer> OvenWerks: The grub out of our package is only after it's installed. The one in the live ISO is not.
[02:38] <wonko> There we go, blacklist ast boot in safe gfx mode
[02:38] <Eickmeyer> wonko: That's odd. The iso should include the proprietary Nvidia drivers.
[02:39] <Eickmeyer> It probably does, but your system is... weird, can I say?
[02:40] <wonko> It is
[02:40] <wonko> It's not your typical sudden
[02:40] <wonko> System
[02:41] <wonko> Asus Z10PE-D16 if you're interested in details
[02:41] <wonko> Ok, booted into live cd, chrooted into my install, dpkg --configure -a is running now
[02:42] <wonko> Not sure if this will make it bootable or not. It's not happy about dev
[02:42] <wonko> I mean /dev
[02:45] <wonko> Well, let's reboot and see what happens. 😁
[02:55] <wonko> Ugh I need to remember to remove quiet so I can see what's going on
[03:13] <wonko> Oh, it is.
[03:13] <wonko> This thing is so messed up now. Need to figure out how to fix it. Really don't want to do a fresh install again.
[03:24] <wonko> Ok, chroot with bind mounts of dev, proc and sys this time
[03:26] <wonko> And hangs at Setting up grub-pc like before
[03:31] <wonko> https://paste.ubuntu.com/p/Rb3mxhP74q/
[06:28] <ramboldo> hi all
[13:44] <drmacro> Upgraded to 19.10 yestereve.  blacklisted the alsa modules for firewire. noted: jack does not start at session start. No firewire audio device shows in UBS Controls.
[14:13] <OvenWerks> drmacro: Can you set up you FW device from qjackctl instead? ie does the FW device show up there?
[14:18] <OvenWerks> drmacro: because I don't have a FW device to play with (yet :) I have assumed that with only one FW device it should show up as hw:0,0,0 when using ffado. The documents on this are thin.
[14:34] <drmacro> OvenWerks: Since I posted I poked around with lshw, ffado-test, ffado-mixer. Didin't fix, but confirmed it was there. Then I discovered the the Jack Backend in UBS Controls. selected FW there and it seems to work (haven't rebooted, don't know if things are sticky yet) Noted: with firewire selected can no longer see on board audio HW, but onboard digital audio still shows. Also, on ports to use, in UBSC'trol, it only goes to 10, wit
[14:34] <drmacro> h the AF12, well there are 12. But, can select from really badly names ports in Carla though i.e. first port is _out, second is _0, etc.
[14:38] <OvenWerks> drmacro: I didn't think it was possible to set ports number for FW devices
[14:38] <drmacro> And channel 11, 12 on the AF12 shows as 9, 10 in carla. I think this is what wonko was referring to yesterday? and I know there was something in QJAckCTL, prety names or something, that made it less confusing...
[14:38] <OvenWerks> I know alsa suggests it should be possible but when I tried it, I got nothing
[14:40] <OvenWerks> pretty names in in jackd2 is not yet released... what qjackctl uses is internal to qjackctl with jackd2 (so far as I can tell)
[14:41] <OvenWerks> the pretty names wonko was taking about are different. With the pulse bridges we do set the jack client names... he doesn't like pulse_in pulse_in_1 etc. :)
[14:42] <OvenWerks> I am guessing next it will be the USB bridges :P
[14:43] <OvenWerks> drmacro: So I can set port names in qjackctl, but when I open patchage or Carla patchbay, I don't see those names
[14:52] <drmacro> OvenWerks: yes, I think (it's been a while...)  I used the pretty names in scripts, run by QJACKCTL, on start and stop to setup my tri-amp system and connect up zitalrx, etc. Just rebooted the other PC, jack didn't start automagically. so not sticky...?
[14:52] <OvenWerks> sounds like bug
[14:53] <OvenWerks> I still have to try a 19.10 install so I can test.
[14:54] <drmacro> It did start by itself when I started Carla, but only the AF12 ports showed, no pulse or onboard.
[14:55] <OvenWerks> There may need to be some more delay with the FW backend
[14:57] <drmacro> So, what does the Start Engine selection in Carla actually do? Sometimes it seems to just refresh Carla's connection tab
[14:58] <OvenWerks> drmacro: can you paste ~/.log/autojack.log
[15:02] <OvenWerks> drmacro: engine start/stop I am not sure about.
[15:02] <OvenWerks> I know carla less well than other things :)
[15:03] <drmacro> https://pastebin.com/hSfz24Cv
[15:04] <OvenWerks> That looks pretty normal
[15:05] <OvenWerks> The first three "no process found" messages are from controls doing a killall of those processes just in case they are running when they should not be
[15:07] <drmacro> what does the Warning about 2 channels mea?
[15:08] <OvenWerks> Except if it just stops there.
[15:08] <OvenWerks> drmacro: zita-ajbridge wants to know how many channels to use but has no option to use all available channels. So I select 100 channels
[15:09] <OvenWerks>  zita-ajbridge gives a warning but then uses whatever channels it can
[15:11] <drmacro> hmm...just rebooted again new log: https://pastebin.com/LKn9fw5G
[15:14] <drmacro> But, hit start button in controls and it got pulse, 12 chans, onboard digital...
[15:14] <OvenWerks> Hmm, a delay may help with that. jack_control was able to use dbus to set jack up but it did not start
[15:16] <OvenWerks> can you paste ./log/jack/jackdbus.log
[15:16] <OvenWerks> It may be that it takes time for the FW unit/modules to be ready
[15:18] <OvenWerks> If you reboot again, but when it gets to the login screen, wait for 60 seconds or so before logging in does that make a difference (wait till the fans quiet down)
[15:18] <drmacro> But, when I tried to play audio mouse went unresponsive, had to exit Xterm to command line and reboot. :-( the jack log is cumulative, right, I'll get it when it reboots.
[15:19] <OvenWerks> ok
[15:26] <drmacro> Got the tail of the last few: https://pastebin.com/85mAbfuP
[15:28] <OvenWerks> The fails all look like device access failures
[15:30] <drmacro> meaning?
[15:32] <OvenWerks> I am thinking that it just takes more time for the device to be ready to stream that autojack allows
[15:34] <OvenWerks> drmacro: did delaying login after boot help at all?
[15:44] <drmacro> OvenWerks: not sure, at this point  hitting Start Restart Jack does and show AF12, pulse audio in Carla, but any attempt to send audio after, no audip, and unresponsive mouse. Even if I go to terminal and kill audio source...
[15:46] <OvenWerks> drmacro: so this is worse than using the alsa FW drivers. Or does that not work either?
[15:47] <drmacro> Hmm... to go back and un-blacklist them ...haven't tried...but, can
[15:48] <OvenWerks> This seems like a fw trouble. If you tell controls to stop jack and try running jack using qjackctl can you get jcak to work that way?
[15:59] <drmacro> So, started with QJAck, same ports sow up, same unresponsive. went to command line tried ffado-test Discover. it found the device but reports protocol errors...
[15:59] <drmacro> this while in the unresponsive state.
[16:01] <OvenWerks> OK, so timing may be an issue in controls, but the unreposive part is ffado... somewhere
[16:06] <drmacro> sorry the protocol errors were logitech errors that popped at the end of the ffado-test output. but, I'm still not convinced the ffado drivers are happy at this point. gonna un-blacklist the alsa modules and start this over
[16:07] <OvenWerks> Ok, you may have to reblacklist the ffado modules.
[16:10] <drmacro> yeah, about that. what should show in a lsmod output for the ffado modules?
[16:11] <OvenWerks> they do not have ffado in all the names
[16:12] <drmacro> it only shows firewire_ohci and firewire_core
[16:12] <drmacro> no ffado at all
[16:14] <OvenWerks> look for 1394?
[16:15] <OvenWerks> in /etc/modprobve.d/ there is a file called blacklist-firewire.conf
[16:15] <OvenWerks> I know raw1394 has to load for any of the ffado modules to work.
[16:20] <drmacro> hmm...may have found a smoking gun.:-/ when I looked in the modprobe.d directory to find the blacklist for the alsa stuff I found a bl file that was black listing the new FW stack in favor of the old... and raw1394 is in there.
[16:21] <drmacro> Have no idea when I did that. :P
[16:22] <OvenWerks> you didn't
[16:22] <OvenWerks> That is stock
[16:22] <OvenWerks> I think you have to blacklist the alsa stuff and unblacklist those ones
[16:23] <OvenWerks> Thats my guess... but I don't know. maybe the ffado home page has better instructions
[16:24] <drmacro> trying that now...
[16:26] <OvenWerks> My hope is to have -controls load/unload the right modules depending on which jack backend is chosen
[16:27] <OvenWerks> But to do that I have to be able to test and get to learn about FW
[16:27] <OvenWerks> FW is dead except that it's not.
[16:28] <OvenWerks> You can't buy new ones but people with them want to keep using them because the "new" USB ones are not as good.
[16:30] <drmacro> So, I commented out the blacklist of the raw1394, rebooted. but lsmod shows no 1394. Do I need to do something else?
[16:30] <OvenWerks> I don't know
[16:30] <OvenWerks> Anything I can say is a guess at best
[16:37] <OvenWerks> I wonder if there are any udev rules for this.
[16:42] <OvenWerks> you may have to manually load raw1394
[16:42] <OvenWerks> sudo modprobe raw1394
[16:43] <OvenWerks> drmacro: ^^
[17:02] <uefi-user> Hello :)
[17:03] <uefi-user> I am trying to install ubuntu-studio to an external usb disk. The problem is that the installer mounts the windows (internal disk) EFI partition (/dev/sdd2) at /target/boot/efi instead of the external disks EFI /dev/sde2
[17:04] <uefi-user> I was sure to select /dev/sde to install bootmanager on. Tried twice, so it seems like a bug. Is there any way to repair this - to force efi to be installed on correct disk after installation
[17:05] <OvenWerks> That would be a bios setting. On my system hitting F8 during boot screen gives me a device list to boot from
[17:05] <uefi-user> yes
[17:06] <uefi-user> But the installer doesnt install to sde2 which is the EFI partition on the external disk, but installs it on sdd2 which is the windows boot partition
[17:06] <uefi-user> I booted from a usb key
[17:07] <uefi-user> so, doing F8 during boot finds "ubuntu" on the windows disk, and an empty grub on the external disk
[17:07] <drmacro> OvenWerks: modprobe says raw1394 isn't on the system. =-O
[17:08] <uefi-user> hm. I manually mounted the external efi partition and moved the files over. going to reboot and see :D
[17:08] <OvenWerks> drmacro: so why blacklist then? that sounds weird
[17:13] <uefi-user> It worked to copy the files from sdd2 to sde2 efi partion
[17:14] <uefi-user> Must be a bug in the installer =(
[17:14] <OvenWerks> could be, The installer is the same for all flavours of ubuntu
[17:15] <OvenWerks> So that would not be unique to Studio.
[17:15] <uefi-user> Probably true
[17:16] <uefi-user> Even I could boot it mounts the windows efi partition in /boot/efi
[17:16] <uefi-user> something not right there.  =(
[17:16] <uefi-user> is it not possible to do a normal MBR+grub setup any more?
[17:16] <OvenWerks> It depends on the bios
[17:17] <uefi-user> I can do both
[17:17] <uefi-user> but the installer doesn't exactly ask
[17:18] <OvenWerks> I think once one os uses efi all are exoected to. I don't have windows here and when I use F8 it showed the USB drive as both efi and not. I chose the not and it installed bios mode
[17:18] <OvenWerks> (with standard grub)
[17:19] <OvenWerks> But yes, being able to decide this during install would make a lot more sense
[17:19] <uefi-user> Yes, the boot F8 thing works both ways here and correctly. That wasn't the issue but that the installer installes on the Windows EFI partition even though I selected to install on the external disks EFI
[17:20] <OvenWerks> That does sound like a bug to me.
[17:20] <uefi-user> root and boot ended up correctly on the external disk, just not the EFI
[17:23] <uefi-user> going to reboot again. updated fstab with correct UUID for the efi partition
[17:23] <OvenWerks> I think from an efi POV that makes sense... but I don't know because I don't use it. You might ask in #ubuntu because there are a lot more people there
[17:24] <uefi-user> perhaps the point is to install ubuntu to the same boot manager as windows one. but still, annoying
[17:29] <drmacro> OvenWerks: I'm stumped. Not sure what to try next...
[17:31] <OvenWerks> drmacro: did the alsa FW modules work if re-enabled?
[17:33] <drmacro> Just rebooted from commenting out the alsa blacklist. After login...totally unresponsive mouse. WTF. :'(
[17:36] <OvenWerks> I am wondering if the newer kernels just don't come with the right modules
[17:37] <OvenWerks> searching through the modules I have not found any 1394 files.
[17:37] <OvenWerks> or ffado
[17:38] <OvenWerks> They are all firewire-somthing
[17:42] <OvenWerks> drmacro: it looks to me like the ffado modules are not installed
[17:42] <OvenWerks> more research needed
[17:44] <OvenWerks> I do not know if dkms would be of help for adding the ffado modules without rebuilding the whole kernel
[17:46] <uefi-user> So I found some other posts online saying the same thing, that the installer will always install to the internal disks efi =(. and to make a portable usb installation requires the manual edit I did (by moving the EFI files)
[17:46] <drmacro> OvenWerks: removed FW card, reboot, start controls, choose alsa, now onboard working fine. (but, obviously, no FW).
[17:48] <OvenWerks> more work required for sure.
[17:48] <drmacro> Reference you comment about FW, If I could find a 6-8 output usb device for reasonable price, I'd have no problem chucking FW (though, there is nothing comparable to the AF12 at this point...even for it's original price point)
[17:49] <OvenWerks> drmacro: I am still using a PCI card (delta 66) for the same reason. USB doesn't do good audio
[17:49] <drmacro> note: XLR out and up to 192khz. ;-)
[17:50] <OvenWerks> XLR out is good, I would never use 192k though (even 96k) unless I was researching bats.
[17:51] <OvenWerks> latency and stability are my biggest concern
[17:52] <OvenWerks> USB really doesn't deliver.
[17:53] <drmacro> agreed about good audio and comments about 96+khz, and latency. BUT, I have access to both A&H ZEDi8 and (at least 3) Behringer X32, in those cases, plug and play. Every time I plug in the usb connector, even in combo with on board HW. I've had no stability issues.
[17:57] <OvenWerks> A lot of pro users have switched to AOiP (Dante, aes67, AVB) or PCIe.
[18:16] <drmacro> OvenWerks: Well, once again I thank you for your help and coaching. :) a pleasure. I need to move on to other projects of the day... and then off to snore through Hamlet again. Probably won't tinker with this until Monday now.