mourip Posted April 13, 2019 Share Posted April 13, 2019 On 4/12/2019 at 10:55 AM, lmitche said: Piero, @hifi25nl Everything sounds more relaxed, thanks for the enhancements! Larry Question. To get the new kernel with NUMA disabled can you just use the AL menu choice to update the kernel? "Don't Believe Everything You Think" System Link to comment
lmitche Posted April 13, 2019 Author Share Posted April 13, 2019 Yes, just do a kernel update from the menu. Once done reboot. Pareto Audio aka nuckleheadaudio Link to comment
mourip Posted April 13, 2019 Share Posted April 13, 2019 Thanks! Seems to have worked however now when I try to re-enable ramroot now I get the error “Unable to determine root UUID”. Any ideas? "Don't Believe Everything You Think" System Link to comment
LTG2010 Posted April 13, 2019 Share Posted April 13, 2019 1 hour ago, mourip said: Any ideas? Try manually in console, the command: ramroot remove reboot then: ramroot -F enable Link to comment
mourip Posted April 13, 2019 Share Posted April 13, 2019 35 minutes ago, LTG2010 said: Try manually in console, the command: ramroot remove reboot then: ramroot -F enable Same error from the commandline. I now have an email in to Piero. Thanks! "Don't Believe Everything You Think" System Link to comment
rickca Posted April 13, 2019 Share Posted April 13, 2019 3 minutes ago, mourip said: I now have an email in to Piero. Please let us know if you get this resolved. Pareto Audio AMD 7700 Server --> Berkeley Alpha USB --> Jeff Rowland Aeris --> Jeff Rowland 625 S2 --> Focal Utopia 3 Diablos with 2 x Focal Electra SW 1000 BE subs i7-6700K/Windows 10 --> EVGA Nu Audio Card --> Focal CMS50's Link to comment
mourip Posted April 13, 2019 Share Posted April 13, 2019 19 minutes ago, rickca said: Please let us know if you get this resolved. I am not sure if I am more embarrassed or confused. I seem to be booting to ramroot and am also on the new kernel version. I am pretty sure that I followed the correct steps to disable ramroot, update the kernel files, and reboot at which time I got that error when I tried to re-enable ramroot. Thinking back on my early experimenting with AL I believe that the error I received is one that comes when you are already in ramroot. I guess that all is well that ends well? "Don't Believe Everything You Think" System Link to comment
rickca Posted April 13, 2019 Share Posted April 13, 2019 20 minutes ago, mourip said: I guess that all is well that ends well? So does the command ramroot status indicate that you are in fact already running in ramroot? Pareto Audio AMD 7700 Server --> Berkeley Alpha USB --> Jeff Rowland Aeris --> Jeff Rowland 625 S2 --> Focal Utopia 3 Diablos with 2 x Focal Electra SW 1000 BE subs i7-6700K/Windows 10 --> EVGA Nu Audio Card --> Focal CMS50's Link to comment
Dev Posted April 13, 2019 Share Posted April 13, 2019 20 minutes ago, mourip said: I am not sure if I am more embarrassed or confused. I seem to be booting to ramroot and am also on the new kernel version. I am pretty sure that I followed the correct steps to disable ramroot, update the kernel files, and reboot at which time I got that error when I tried to re-enable ramroot. Thinking back on my early experimenting with AL I believe that the error I received is one that comes when you are already in ramroot. I guess that all is well that ends well? I think with the updates, there is a bug somewhere. I also faced the same issue. This is how I resolved 1. ramroot disable 2. reboot 3. check status after reboot using 'ramroot status' and it should say :: ramroot status: disabled 4. enable ramroot from menu option Link to comment
rickca Posted April 13, 2019 Share Posted April 13, 2019 2 minutes ago, Dev said: ramroot disable I think Piero said not to use ramroot disable (and use ramroot remove instead) because it can give unpredictable results. Pareto Audio AMD 7700 Server --> Berkeley Alpha USB --> Jeff Rowland Aeris --> Jeff Rowland 625 S2 --> Focal Utopia 3 Diablos with 2 x Focal Electra SW 1000 BE subs i7-6700K/Windows 10 --> EVGA Nu Audio Card --> Focal CMS50's Link to comment
LTG2010 Posted April 14, 2019 Share Posted April 14, 2019 42 minutes ago, mourip said: I guess that all is well that ends well? I get the same message as you, I am also already in ramroot, however the message I was expecting was :'' ramroot already enabled'' I guess all is fine. Link to comment
Dev Posted April 14, 2019 Share Posted April 14, 2019 7 minutes ago, rickca said: I think Piero said not to use ramroot disable (and use ramroot remove instead) because it can give unpredictable results. Wasn't aware of it but those are the steps that solved my issue. I guess 'remove' should have been the better step. Link to comment
mourip Posted April 14, 2019 Share Posted April 14, 2019 2 hours ago, rickca said: So does the command ramroot status indicate that you are in fact already running in ramroot? Yes and USB drive pulled currently. Sounds great. "Don't Believe Everything You Think" System Link to comment
Dutch Posted April 14, 2019 Share Posted April 14, 2019 Related, I have also noticed I always have to disable ramroot twice in the menu with reboots in between. After the first reboot it is actually no longer booting to RAM but I have to do it again before it actually says it’s ‘disabled’. No biggie or a even a problem at all of course. System details Link to comment
Popular Post hifi25nl Posted April 14, 2019 Popular Post Share Posted April 14, 2019 New Menu 110 with WiFi script! WIFI CONFIGURATION This will work if the driver/firmware for your WiFi adapater is available in linux Consult the wiki athttps://wiki.archlinux.org/index.php/Wireless_network_configuration#Troubleshooting_drivers_and_firmware LTG2010, rickca, Monge and 1 other 4 AudioLinux --> https://www.audio-linux.com developer of AudioLinux realtime OS Link to comment
lmitche Posted April 14, 2019 Author Share Posted April 14, 2019 The ramroot setting state of the newly downloaded kernel supercedes the prior state of ramroot on a system as it overwrites the existing kernel. This setting can be set randomly to ramroot or not, although most often it seems set to ramroot. When set to ramroot, there is no reason to enable ramroot a second time. mourip 1 Pareto Audio aka nuckleheadaudio Link to comment
Popular Post BigAlMc Posted April 14, 2019 Popular Post Share Posted April 14, 2019 2 minutes ago, hifi25nl said: New Menu 110 with WiFi script! WIFI CONFIGURATION This will work if the driver/firmware for your WiFi adapater is available in linux Consult the wiki athttps://wiki.archlinux.org/index.php/Wireless_network_configuration#Troubleshooting_drivers_and_firmware No deal! Nope! Not doing it. My system is just sound soooooo damn good right now, I ain't tinkering with anything 😋 Cheers, Alan mourip, Boomboy, Dutch and 1 other 4 Synergistic Research Powercell UEF SE > Sonore OpticalModule (LPS-1.2 & DXP-1A5DSC) > EtherRegen (SR4T & DXP-1A5DSC) > (Sablon 2020 LAN) Innuos PhoenixNet > Muon Streaming System > Grimm Audio MU1 server > (Sablon AES) Mola Mola Tambaqui DAC > PS Audio M1200 monoblocks > Salk Sound Supercharged Songtowers Link to comment
mourip Posted April 14, 2019 Share Posted April 14, 2019 2 hours ago, lmitche said: The ramroot setting state of the newly downloaded kernel supercedes the prior state of ramroot on a system as it overwrites the existing kernel. This setting can be set randomly to ramroot or not, although most often it seems set to ramroot. When set to ramroot, there is no reason to enable ramroot a second time. That makes sense based upon what I experienced. I did get a reply from Piero. His emphasis... 1) Boot to normal mode answering N to ramroot boot prompt 2) type ramroot remove on command line or use the menu option to do this 3) Reboot 4) Reinstall kernel with the menu option 5) Reboot 6) typeramroot -F enable on command line or use the menu option to do this 7) Reboot Monge 1 "Don't Believe Everything You Think" System Link to comment
lpost Posted April 14, 2019 Share Posted April 14, 2019 Anyone else running the NUMA-off kernel notice sluggish response via SSH? I don't really mind as it sounds great just curious as I've not seen it mentioned. Link to comment
ray-dude Posted April 14, 2019 Share Posted April 14, 2019 On 4/4/2019 at 8:16 AM, hifi25nl said: 2) Euphony blacklist some modules in /etc/modprobe.d/blacklist.confblacklist snd_hda_intel blacklist snd-hda-intel blacklist iwlmvm blacklist iwldvm blacklist iwlwifi blacklist bnep blacklist btusb blacklist bluetooth blacklist joydev blacklist mousedev blacklist iTCO_vendor_support blacklist iTCO_wdt blacklist ip_tables blacklist mei_me blacklist intel_rapl blacklist intel_powerclamp Just getting back to AL tweaking, catching up on all the goodies from the last several weeks (thanks to all!) For those that have been experimenting with blacklist modules, is there a consensus on which make the most sense for AL on end points and server? I'm not seeing most of these with lsmod, but I'm seeing a lot of others that may be candidates to disable (NUC7i7DNKE for both end point and server, running Roon) ATT Fiber -> EdgeRouter X SFP -> Taiko Audio Extreme -> Vinnie Rossi L2i-SE w/ Level 2 DAC -> Voxativ 9.87 speakers w/ 4D drivers Link to comment
lpost Posted April 14, 2019 Share Posted April 14, 2019 57 minutes ago, lpost said: Anyone else running the NUMA-off kernel notice sluggish response via SSH? I don't really mind as it sounds great just curious as I've not seen it mentioned. After Roon finished its startup shenanigans, all is normal. Link to comment
lmitche Posted April 14, 2019 Author Share Posted April 14, 2019 54 minutes ago, ray-dude said: Just getting back to AL tweaking, catching up on all the goodies from the last several weeks (thanks to all!) For those that have been experimenting with blacklist modules, is there a consensus on which make the most sense for AL on end points and server? I'm not seeing most of these with lsmod, but I'm seeing a lot of others that may be candidates to disable (NUC7i7DNKE for both end point and server, running Roon) I see some kvm stuff in lsmod that may be a good candidate for removal. Pareto Audio aka nuckleheadaudio Link to comment
ray-dude Posted April 14, 2019 Share Posted April 14, 2019 16 minutes ago, lmitche said: I see some kvm stuff in lsmod that may be a good candidate for removal. I was also eyeing a bunch of the non-PCM stuff on the snd_usb_audio dependency tree I'm leary of trimming i915 and the rest of the video tree (make the system truly headless) since I sometimes have to hook up a monitor to debug these beasts. One take I'm thinking of is a script to rmmod a bunch of these things that I manually run after boot. ATT Fiber -> EdgeRouter X SFP -> Taiko Audio Extreme -> Vinnie Rossi L2i-SE w/ Level 2 DAC -> Voxativ 9.87 speakers w/ 4D drivers Link to comment
LTG2010 Posted April 14, 2019 Share Posted April 14, 2019 4 hours ago, ray-dude said: I'm leary of trimming i915 I have these 4 extra parameters on my server blacklist: blacklist snd_usb_audio blackilist drm_kms_helper blacklist drm blacklist i915 The monitor still works, but i915 & drm are no longer listed in lsmod. Monge 1 Link to comment
lpost Posted April 15, 2019 Share Posted April 15, 2019 Do you notice any SQ differences removing inactive modules from the kernel? Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now