[02:23] <jamesg27> Hello good evening, I have just installed Ubuntu Studio Disco Dingo 19.04 on a Toshiba Satellite C55
[02:24] <jamesg27> It did not recognize the built in laptop keyboard or trackpad, I am trying solutions to make them work, working with a usb at the moment, kybrd and mouse, one of the solutions I found was to update the kernel, I currently have 5.0.0-29-lowlatency, and the possible solution advised to update to kernel to 5.1.16 through PPA
[02:25] <jamesg27> Since I am new I do not know exactly how to update only the kernel, using ubuntu studios low latency, which is the point I installed Ubuntu Studio, could someone please advice me?
[02:29] <jamesg27> Having a rough install, does not detect internal keyboard, trackpad, external bluetooth keyboard, and has wifi intermittengly
[02:30] <jamesg27> I installed from scratch on laptop
[02:35] <jamesg27> I am really excited to try ubutustudio, used linux many years ago, trying to come back to it
[03:23] <tomreyn> jamesg27: hmm, that's unfortunate, it's actually quite rare that an internal laptop keyboard isnt detected. sure, you can try a different kernel version, though 19.04 only supports a single kernel version. you could also take a look at your logs and try to understand what's causing these issues, and how to handle them with the kernel version you already have.
[03:25] <tomreyn> "journalctl -b"  shows your system and application logs since the latest reboot. to share it here, use     journalctl -b | nc termbin.com 9999   (you can also try getting help in #ubuntu, since this should be an ubuntu 19.04-wide issue with your hardware).
[03:29] <jamesg27> Thank you let me try to print the log
[03:35] <jamesg27> thank you for your help, here is the link for the log   <pre>https://termbin.com/2kth</pre>
[03:37] <jamesg27> I have npo problem with a single kernel, what I do not know is hopw to update it to the 5.1.16 throu8gh ppa like a person said it worked for them, without loosing the low latency kernel which is the reason I installed ubuntustudio for multimedia applications
[03:40] <tomreyn> jamesg27: i suspect you added those extra kernel parameters in an attempt to fix the issue?
[03:42] <jamesg27> no no I currently have the 5.0.0-29-lowlatency that came with the install, I learned that the updating to the 5.1.16 through ppa helped another user with this same problem, So I thought I should try it, but I dont know how
[03:42] <jamesg27> yes that is correct
[03:42] <tomreyn> about the newer kernel version: i believe i would do you a disfavor by suggesting ways to install different but unsupported kernel versions. what i can suggest is to install 18.04 LTS instead, which will offer at least two, maybe three, kernel versions to choose from.
[03:43] <jamesg27> qahhh I c... and how do you choose those kernel versions, do they come up as options in the menu while you are installing
[03:44] <jamesg27> I am also going to try and update the bios of the laptop, since it has the 1st version...
[03:44] <jamesg27> i think i will try that before installing 18.04 lts
[03:45] <jamesg27> did you happen to see something important in the logs?
[03:45] <tomreyn> i generally recommend bios updates, too
[03:45] <tomreyn> i'm still reading those logs
[03:45] <tomreyn>  TOSHIBA Satellite C55-A/Portable PC, BIOS 1.10 12/03/2013
[03:45] <jamesg27> ok ok ty
[03:46] <tomreyn> but i think you should remove those extra kernel parameters, do the bios upgrade and test that way first of all.
[03:46] <tomreyn> and share another log based on it, too.
[03:47] <jamesg27> ty what extra kernel parameters? how do i do that?
[03:47] <tomreyn> i8042.nomux=1 i8042.reset acpi=noirq
[03:47] <tomreyn> those three, did you not add those to /etc/default/grub ?
[03:47] <jamesg27> ahh that was somebody elses solution i tried that i found online, did not work
[03:47] <jamesg27> yes
[03:47] <jamesg27> i did
[03:48] <tomreyn> you can copy line that's in the file and comment it out (place a # in front), then remove those options off the non commented line.
[03:48] <tomreyn> so you keep it for later
[03:48] <jamesg27> ok i will remove those, and try the bios update , if it does not work, i will install 18.04 LTS
[03:48] <tomreyn> then run     sudo update-grub
[03:48] <jamesg27> yes thank you
[03:49] <jamesg27> will do that right now, and will make a bootable usb with the bios update,
[03:52] <tomreyn> good luck. if you'll return here and want to address me later, be sure to mention my nickname, tomreyn (or i may not notice). but i may also no longer be at the computer then (just logged in).
[03:54] <jamesg27> thank you tom I appreciate your help, do i mention your nick with the @ infront?
[03:58] <jamesg27> Tom I found some instructions on how to update the bios on linux, they recommend a prog called 'unetbootin' but I do not find it on the software center, can you recommend something else I can use?
[03:59] <jamesg27> I have the updated bios, but it is an exe, and inside there is an iso image..
[03:59] <jamesg27> that was the only update avaliable on the laptops page on the toshiba website
[04:05] <tomreyn> no need for the @ here on irc. if yu ever want a better chaqt client, you can install hexchat (on several operating systems including ubuntu linux).
[04:06] <tomreyn> jamesg27: << this should make your browser tab flash, and similarily it'd try to ge tmy attention here.
[04:08] <tomreyn> you can use    usb-creator-gtk    (probably already installed) to write the iso to a USB stick - but be aware that the entire stick gets overwritten that way - backup your data first.
[12:37] <Uhfgood> I don't have experience with any version of linux.  I'm running windows 7, and most likely will want to dual-boot.  Where should I start?
[12:41] <jazzslag> Uhfgood I'd make a bootable USB of the latest version (19.04) and take it for a spin
[12:44] <Uhfgood> ok, i'll probably have to burn an iso and use a dvd.  I don't have any extra usb drives (I guess I'm still stuck in the last century ;-))
[12:49] <Uhfgood> jazzslag - thanks
[12:56] <tomreyn> dvd should work, too (but yes, i'd prefer usb)
[14:12] <wonko> OvenWerks: Well, the good news is jackd appears to be more stable now. Hasn't restarted at all over the weekend. The bad news is I do still get 4-5 xruns per minute, but we also haven't figured out the irq thing so there is hope. :)
[15:27] <jazzslag> wonko which version are you using? I just upgraded to 19.04 and is super stable
[15:28] <wonko> 19.04
[15:37] <wonko> I've tried shortening the USB extension cable to the audio device and I got a proper mic so I'm no longer doing zita-a2j for the shitty webcam mic. One of those things may have solved the issue. :)
[15:50] <wonko> Or neither did and it's a coincidence. :)
[16:02] <Eickmeyer> jazzslag: wonko has some IRQ conflict problems, from what I understand. Fairly unique to his hardware.
[16:05] <jazzslag> Eickmeter ah ok sorry to trivialise
[16:06] <jazzslag> simply installing 19.04 and playing with the Carla settings fixed a very specific problem I had, so I assumed 19.04 was the magic cure-all :D
[16:06] <wonko> Well, the IRQ thing is still an issue. I'm not sure if that's related to the jackd stability or not. A lot of unknowns here. :)
[16:07] <Eickmeyer> wonko: It absolutely is. If the IRQ thing is conflicting, you bet jackd is going to have a problem.
[16:07] <wonko> oh, getting the audio device onto a different controller than the mouse/keyboard may also have played a part to stability. Hard to say.
[16:07] <wonko> I'm not sure it's conflicting though or not
[16:07] <wonko> those are just guesses Oven and I had. :)
[16:08] <Eickmeyer> Well, they're decent guesses.
[16:09] <wonko> still need to figure out a way to determine which is the correct irq handler for chrt though.
[16:09] <Eickmeyer> Yeah. That stuff is over my head, unfortunately.
[16:14] <wonko> Yeah, I don't quite understand things at this depth either
[16:17] <wonko> The thing I don't understand is if I follow the path all the way to the pci usb controller its IRQ is 24, but there is no process for that, only for 35 which is the root hub it's connected to
[16:20]  * Eickmeyer whoosh
[16:25] <wonko> EXACTLY
[16:25] <wonko> I'm asking some people smarter than me to see what they say. :)
 pcie interrupts are message signaled; the controller puts a message in a ring buffer and then (maybe) flags a physical interrupt line to say the queue needs processing
 so the thread in this case is the kthread that's processing that ring buffer
[16:52] <wonko> So that technically answers the question
[16:52] <wonko> I just don't know how that applies to what I'm doing. :)
[16:53] <OvenWerks> wonko: it means that the computer doesn't bother with the physical IRQ... the one listed by lspci
[16:53] <OvenWerks>  it uses a virtual or messages irq.
[16:53] <wonko> is that the one we're getting from /sys?
[16:53] <OvenWerks> *messaged
[16:54]  * OvenWerks has forgotten where we were with that
[16:55] <wonko> Lost in the woods I think
[16:55] <OvenWerks> if the one from sys matches the one shown in /proc/interrupts then that is the correct one
[16:55] <OvenWerks> /proc/interrupts shows what is actually being seen by the cpu
[16:56] <wonko> so looking at the irq for the PCIe USB card, they do not match
[16:56] <wonko> for the root hub I think they do
[16:56] <wonko> but there is no process for the USB card anyway so I'm not sure what magic that is
[16:57] <wonko> PCIe PME, aerdrv is what shows up on 35 from /proc/interrupts
[16:57] <OvenWerks> wonko: when I was playing with it on my system... I was finding that the irq listed in lspci -v was the right one... not sure what changed... oh maybe I was looking at my ethernet card
[16:58] <wonko> https://paste.ubuntu.com/p/Nbh5H3WsHm/
[16:58] <wonko> ugh, lspci -v on this system is painful. :)
[16:58] <wonko> wonko@deepthought:~/bin$ lspci -v | wc -l
[16:58] <wonko> 868
[17:02] <wonko> so lspci output matches expectations
[17:02] <wonko> https://paste.ubuntu.com/p/2yR588xVhs/
[17:03] <wonko> using /sys to fine the irq matches that anyway
[17:03] <wonko> s/fine/find/
[17:41] <OvenWerks> wonko: first thing is that /sys/devices/ does not show me everything
[17:41] <OvenWerks> ... /sys/devices has a sub directory pci0000:00
[17:42] <OvenWerks> but lspci seems to show pci0000:02 - 05
[17:50] <OvenWerks> wonko: I think you are looking for /sys/bus/pci/devices/<device>/msi_irqs/
[17:50] <OvenWerks> the MSI is the key
[18:04] <OvenWerks> wonko: this is for my ethernet because it has the same problem.
[18:05] <OvenWerks> $ cat pci/devices/0000\:03\:00.0/irq -> 17
[18:05] <OvenWerks> ls pci/devices/0000\:03\:00.0/msi_irqs/ -> 26  27  28  29  30
[18:06] <wonko> yeah, looking at the msi IRQs they match nothing else I've collected before. :)
[18:06] <OvenWerks> Ya 5 of them this is an Intel i210
[18:06] <wonko> wonko@deepthought:~/bin$ ls /sys/devices/pci0000:80/0000:80:02.0/0000:81:00.0/msi_irqs
[18:06] <wonko> 38  39  40  41  42  43  44  45
[18:06] <wonko> 81:00.0 is the PCIe USB controller
[18:08] <OvenWerks> except I bet you find the same list for your internal USB pci "card"
[18:10] <OvenWerks> I did try blacklisting the xhci module with no success
[18:10] <OvenWerks> there is supposed to be a bit that can be turned off in the usb controller that changes that too.
[18:13] <OvenWerks> https://www.systutorials.com/241533/how-to-force-a-usb-3-0-port-to-work-in-usb-2-0-mode-in-linux/
[18:14] <OvenWerks> wonko: I found a number of pages about turning off xhci and why that are not related to audio but usb device count:
[18:14] <OvenWerks> https://acroname.com/blog/why-cant-i-connect-more-usb-30-devices-my-system
[18:15] <OvenWerks> http://marc.merlins.org/perso/linux/post_2018-12-20_Getting-Around-USB3-xhci-32-Device-Limit-_Max-number-of-devices-this-xHCI-host-supports-is-32_.html
[18:15] <OvenWerks> wonko: however it is obvious to me that because of the horrible way xhci does things, you may have little choice
[18:17] <wonko> ugh
[18:18] <wonko> smart guy can't figure out how we need to do this because he's pretty sure this interrupt is handled as a kthread so there is no way to alter the priority
[18:18] <OvenWerks> you do need thge right irq one way or the other
[18:18] <wonko> that he's figured out so far anyway
[18:20] <OvenWerks> what does your jack log look like when there is an xrun?
[18:20] <OvenWerks> Is there one particular port that is listed every time?
[18:21] <OvenWerks> I am guessing you have both pulse and usb bridging turned off?
[18:22] <wonko> https://paste.ubuntu.com/p/mNTy5NZsw6/
[18:22] <wonko> no, those bridges are both on I believe
[18:23] <OvenWerks> pulse in was not fiished seems to be pretty common.
[18:23] <OvenWerks> a2j needs to be on, I meant usb bridging and pulse bridge size is greater than 0
[18:25] <OvenWerks> wonko: also pavucontrol in the Confiuration tab should say "No cards available for configuration"
[18:27] <OvenWerks> It is almost like pulse is picking up another sync source
[18:27] <wonko> indeed it does say that, yes
[18:31] <OvenWerks> Hmm, normally pulse doesn't give problems like that unless it can see another device.
[18:32] <OvenWerks> but pulse is causing xruns in an almost clock like way.
[18:38] <OvenWerks> not quite
[18:38] <OvenWerks> two or three in a row then nothing for a bit
[18:43] <wonko> So I'm reading a bit and they mentioned rtirq
[18:44] <wonko> so I wanted to see what it was doing
[18:44] <wonko> https://paste.ubuntu.com/p/BdnGjJ3fmx/
[18:44] <wonko> Looks like it just takes the IRQs handling USB devices and blindly assigns decending prioroty
[18:45] <wonko> priority
[18:45] <wonko> with HDA-Intel at the top
[18:45] <wonko> and wtf even is that?
[18:45] <wonko> I have no intel audio
[18:47] <wonko> and yes, it's not handling stuff like usb5 like you want it to it doesn't look like
[18:47] <wonko> Well
[18:47] <wonko> actually I think it would if it found it in the output of /etc/interrupts
[18:48] <wonko> but at least in my case usb5 doesn't show up there
[18:49] <wonko> the only ones that show up are usb1, usb2 and usb3
[18:55] <OvenWerks> yup...
[18:56] <OvenWerks>  That has been my experience too.
[18:57] <OvenWerks> it has found something that looks like an HDA controller
[18:58] <OvenWerks> it could very well be your display has an hdmi line and some MB handle that using hda
[18:58] <OvenWerks> (or you graphics card)
[19:02] <wonko> ah, yes, that is the case
[19:02] <wonko> I don't use it, but the nvidia card has audio
[19:03] <OvenWerks> I have seen hdmi two ways, as a part of hda or PCU or the may be a batch of [hdmi]
[19:03] <OvenWerks> it seems the new way is to separate out hdmi which often requires a large latency to even work.
[19:04] <wonko> so if I put usb before snd in /etc/defaults/rtirq it at least puts the USB before that, but honestly it's not even used so I doubt that'll have much impact
[19:05] <OvenWerks> if you know the irq you want you can use like 38-xhci in rtirq
[19:05] <wonko> that's the problem, I don't. :)
[19:05] <wonko> I still haven't worked that part out yet
[19:06] <wonko> I mean unless I prioritize the pci hub, but I don't think that's what we want?
[19:06] <OvenWerks> so if cat /proc/interrupts has one of the with :usb5 that would be the one or if the same output shows one og the irqs with a lot of activity on only one cpu
[19:07] <wonko> there is no usb5 unfortunately
[19:07] <wonko> only usb1/2/3
[19:07] <wonko> no 4/5/6
[19:08] <OvenWerks> well looking at  cat /proc/interropts my usb audio device shows as:  20:    2774412          0         30          0   IO-APIC  20-fasteoi   ehci_hcd:usb1
[19:09] <OvenWerks> note the first number after the irq is quite high while the next three nujmbers are low or none.
[19:09] <OvenWerks>  this is compared to: 23:          0      38027     331623         63   IO-APIC  23-fasteoi   ehci_hcd:usb2
[19:09] <OvenWerks> which is my mouse
[19:10] <OvenWerks> the numbers are lower eventhough I just plugged the audio in while the mouse has been there since boot
[19:11] <OvenWerks> So you should be able to guess which of the eh/xhci are handling your USB audio by looking for such a pattern
[19:13] <wonko> 116:          0     359301          0          0          0       9035          0     202119    2862447       1995          0          0          0      12727          0          0          0          0          0          0          0          0          0          0          0          0          0          0        909          0          0      67105          0          0          0          0          0   32437585          0          0
[19:13] <wonko> 5524745    5286763          0          0          0          0          0          0          0          0          0          0          0          0          0          0  IR-PCI-MSI 512000-edge      ahci[0000:00:1f.2]
[19:13] <wonko> oh wait
[19:13] <wonko> that's all the CPUs, isn't it?
[19:13] <wonko> so I'll need to look at every other one?
[19:14] <wonko> GRRR
[19:14] <OvenWerks> so maybe show me what cat /proc/interrputs |grep hcd
[19:14] <wonko> http://paste.ubuntu.com/p/5y5t6VmVjB/
[19:14] <wonko> 38 looks like a winner
[19:15] <OvenWerks> ya that would be my guess
[19:15] <wonko> so how would I tell rtirq to set that one highest?
[19:16] <OvenWerks> so for rtirq use 38-xhci
[19:17] <OvenWerks> I would do "38-xhci snd usb"
[19:17] <OvenWerks> but you should be able to not include usb or snd try it both ways :)
[19:18] <wonko> wonko@deepthought:~/.log/jack$ sudo /etc/init.d/rtirq restart
[19:18] <wonko> Setting IRQ priorities: start [HDA-Intel] irq=184 pid=1498 prio=85: OK.
[19:18] <wonko> Setting IRQ priorities: start [ehci_hcd] irq=18 pid=557 prio=80: OK.
[19:18] <wonko> Setting IRQ priorities: start [ehci_hcd] irq=19 pid=556 prio=79: OK.
[19:18] <wonko> Setting IRQ priorities: start [xhci_hcd] irq=38 pid=559 prio=80: OK.
[19:18] <OvenWerks> 38 and 18 are conected then
[19:19] <OvenWerks> also rtirq does not reset stuff it did last time very well may have to reboot to see the real effect
[19:20] <wonko> it's still putting hda ahead of it though
[19:20] <wonko> which is a tad confusing
[19:20] <OvenWerks> yes, but it may be left from last boot
[19:20] <wonko> hmm, ok
[19:20] <OvenWerks> rtirq does not lower old irq settings
[19:20] <wonko> ah, ok
[19:21] <wonko> I can try a reboot
[19:21] <OvenWerks> at least that was what the docs used to say... thogh I haven't read them lately
[19:21] <OvenWerks> but even still with what you had, your audio card should be a higher priority than yur mouse
[19:23] <OvenWerks> wonko: are you running hyperthreading?
[19:24] <OvenWerks> ie, is you cpu x cores/(x*2)threads?
[19:30] <wonko> yes, hyperthreading
[19:30] <wonko> after reboot:
[19:30] <wonko> wonko@deepthought:~$ /etc/init.d/rtirq status
[19:30] <wonko>   PID CLS RTPRIO  NI PRI %CPU STAT COMMAND	
[19:30] <wonko>  1444 FF      85   - 125  0.0 S    irq/184-snd_hda	
[19:30] <wonko>   555 FF      80   - 120  0.0 S    irq/18-ehci_hcd	
[19:30] <wonko>   557 FF      80   - 120  0.7 S    irq/38-xhci_hcd	
[19:30] <wonko>   554 FF      79   - 119  0.0 S    irq/19-ehci_hcd	
[19:30] <wonko>   558 FF      79   - 119  0.0 S    irq/39-xhci_hcd	
[19:30] <wonko> so snd is still top, but 38/18 is at least second highest
[19:33] <OvenWerks> in testing I did some time ago (think P4) I found that with hyperthreading enabled the lowest quite stable low xrun latency I could go on my PCI audio was about 62/2. with hyperthreading disabled I was able to have 16/2 with no xruns
[19:34] <wonko> Hmmm
[19:34] <wonko> I probably don't *need* hyperthreading
[19:34] <wonko> 28 cores should be more than enough. :)
[19:35] <OvenWerks> with latencies above 64/2 there seemed to be little difference
[19:35] <wonko> well, i'm at 128/2
[19:35] <OvenWerks>  I have also found that having "Boost" turned off helps
[19:36] <wonko> although shouldn't I have 3? Is that still the recommended number of periods for usb?
[19:36] <OvenWerks> by the time you get to 128 it should not matter.
[19:37] <wonko> ok, well let's watch it and see what happens
[19:37] <wonko> so far no xruns
[19:37] <OvenWerks> USB is 1 ms cycles (maybe 1.25ms I have heard other places)
[19:37] <wonko> starting qsynth caused an xrun
[19:38] <OvenWerks> so 16/3 at 48k is 1ms
[19:38] <OvenWerks> So long as you don't get them while using qsynth that is ok
[19:38] <wonko> yeah, played some stuff an no xruns while playing
[19:39] <OvenWerks> so the minimum a USB device can run is 32/3 ish
[19:43] <wonko> The annoying part about debugging this is now there's nothing really to do except wait and see what happens
[19:44] <OvenWerks> I purposely chose the i5 over the i7 (there was no i9 at the time and xeon was too pricey) because I felt that paying for hyperthreading I wasn't going to use anyway :)
[19:44] <wonko> I didn't pay for these CPUs/RAM so I wasn't complaining. :)
[19:44] <OvenWerks>  :)
[19:44] <OvenWerks> best way.
[19:45] <wonko> I probably should have sold them and gotten something else with the money but at the time they made sense
[19:45] <wonko> to keep that is
[19:46] <OvenWerks> I likely would have done the same
[19:46] <wonko> We were possibly moving out of the country and dragging a rack full of server gear wasn't feasable so this became my everything box. It is *really* good at that. :)
[19:47] <wonko> Also, it's very good at building UnrealEngine4 for linux. :)
[19:47] <OvenWerks> Ya, I build enough stuff I would like it for that
[19:48] <wonko> 11 minutes. Last I tried building it was on an i7 laptop and it took like 2 hours and didn't even finish. :)
[19:48] <wonko> their build process scales nicely across CPUs
[19:48] <wonko> and ran the thing up to 4% idle
[19:49] <OvenWerks> I build Ardour quite a bit. my laptop takes an hour at least, this is 14 min and someone with a server similar to your's reports less than 1 min
[19:49] <OvenWerks> Ardour pins all of my cpus to 100
[19:50] <OvenWerks>  I use that to monitor my temperature if it gets too high it is time to clean dust out
[19:50] <wonko> nice. :)
[19:50] <wonko> I haven't run into too many dust issues yet
[19:51] <wonko> although the radiator for the 1080 will clog up eventually
 😔
 @miftahulAlvinRizki [😔], Do you have a support issue?
[19:56] <wonko> OvenWerks: as things stand now my CPUs are running at 49C and 54C
[19:56] <OvenWerks> while working hard or at idle?
[19:56] <wonko> mostly idle
[19:56] <wonko> it's hard to make this thing work hard
[19:56] <wonko> I should build UE4 again
[19:57] <wonko> so far still no xruns except for that one starting qsynth
[19:57] <OvenWerks> mine idles at around 25C and gets to about 70C at 100% times 4
[19:57] <wonko> Xeons run a lot hotter in my experience
 No, i just confused about bot. Did you know something?
[19:58] <OvenWerks> I think my do not excede is 90C
[19:59] <OvenWerks> So 20 min with no x runs. that is not a bad place to start
 @miftahulAlvinRizki [No, i just confused about bot. Did you know something?], The bot is a bridge to our IRC channel.
[20:00] <OvenWerks> It remains to be seen if your IF will use the same IRQ every boot. But time will tell. If you boot some time and the xruns go up that would be something to check
[20:02] <wonko> boo, just got come
[20:02] <wonko> some
[20:02] <OvenWerks> Did cron just run something in the background? (apt update for example)
[20:02] <wonko> I started doing a sizable apt install
[20:03] <OvenWerks>  That would do it, some network operations are more atomic than I like
[20:03] <wonko> ok, that's good to know
[20:03] <OvenWerks> If you had to do an apt anything to get xruns you are doing well
[20:04] <OvenWerks> wonko: next test: set sample buffer to 64/3
[20:04] <OvenWerks> or 64/2 or 32/3
[20:04] <OvenWerks>   :)
[20:04] <wonko> That was my plan. :)
 @Eickmeyer [The bot is a bridge to our IRC channel.], Okay, thank you
[20:48] <wonko> OvenWerks: building UE4 (takes idle to 0.2%) and the CPUs topped out at 59C and 68C