You are not logged in.
- Topics: Active | Unanswered
#226 Re: Hardware & System Configuration » Non-specific error message at boot from nVidia drivers » 2019-07-13 21:38:08
Hmm, some people just don't turn their computer off at night? 
The only difference I can see is that mine has an extra "remove" line. What matters, of course, is how these lines are invoked during the boot process. Following that process is a very technical feat that I'm not sure I can figure out. I hate to the Windows-style "uninstall and reinstall" routine, but that may be my only recourse. Or just ignore the error since the drivers seem to be working fine.
#227 Re: Hardware & System Configuration » [Solved] Grub "savedefault" not working » 2019-07-13 21:25:57
"grub-editenv list" produced no output at all. Even when run in a root terminal. From what I can see about grub-editenv in the man pages, that is where the default should be saved. But it's clearly not getting saved. This was a re-install over the previous Linux (Mint 17.3) -- could differences between the different versions of grub have caused a problem?
#228 Re: Hardware & System Configuration » CPU microcode blacklisted by nvidia drivers » 2019-07-13 21:22:47
As I said, it's got one active line. And a comment that says it's not safe to allow microcode. Here is the full content:
# The microcode module attempts to apply a microcode update when
# it autoloads. This is not always safe, so we block it by default.
blacklist microcode#229 Re: Hardware & System Configuration » Non-specific error message at boot from nVidia drivers » 2019-07-13 01:07:59
Well, that's an interesting thought. If the modprobe.conf commands are in fact not working at all, maybe I can just comment them out and let this user-space fail-safe do the loading? What confuses me is that the message "udevd[*number*]" is always so different. Isn't that number supposed to tell you something useful about where in the boot process the error occurred? Is it really failing at wildly different points every time? Where in the boot process would this other load system be invoked? I am not familiar with the Linux boot process at such a low-level of detail.
#230 Hardware & System Configuration » CPU microcode blacklisted by nvidia drivers » 2019-07-13 01:02:21
- Micronaut
- Replies: 8
While researching the mysterious nvidia non-specific boot error message, I found something else annoying. The nvidia drivers install a blacklist that prevents microcode from being loaded for Intel CPUs! The file is named "intel-microcode-blacklist.conf" and it has a line that simply says "blacklist microcode" -- meaning it will block ALL microcode, I guess. Why? This is now very important with the meltdown/spectre issues. Granted, most cloud servers aren't going to be using nvidia video cards, so it's not an issue for them, but I am concerned that this might cause problems on a desktop with up-to-date kernels. Are there checks for the state of the CPU before the new security fixes are used? Or do they just assume that your Intel CPU is using the microcode that changes threading behavior?
#231 Hardware & System Configuration » [Solved] Grub "savedefault" not working » 2019-07-13 00:56:40
- Micronaut
- Replies: 8
It was great fun to discover Grub could be configured to save the last manual choice as the default for future boots. I used it with my Linux Mint Rosa (17.3) install and it worked fine. But now it won't work with Devuan Ascii. I can't figure out what is different. Just put:
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
in the /etc/default/grub config file and run update-grub. It worked with Mint. What is different about grub in Devuan?
#232 Hardware & System Configuration » Non-specific error message at boot from nVidia drivers » 2019-07-07 23:38:45
- Micronaut
- Replies: 4
Every time my Devuan Ascii system with recently installed nvidia proprietary drivers boots, I get the frankly useless "Error running install command for nvidia" message as the very first thing on the screen. Yet the driver seems to work perfectly. There are two threads I have found about this problem already. There may be more. I thought it a good idea to start a new thread because this is (hopefully) a different approach.
https://dev1galaxy.org/viewtopic.php?id=2311
https://dev1galaxy.org/viewtopic.php?pid=10922
As I said in the first thread, this looks to me like something that should have been removed being left behind by an installer.
The second thread, in the Hardware & System Configuration forums like this post, contains a suggestion to comment out a line of a config file in modprobe.d, but those files have been replaced by the install of the nvidia drivers on my system. The file with the module init commands is now named glx--nvidia-modprobe.conf and it's in the /alternatives directory instead of /etc/modprobe.d Since the original poster did not return and report his results, I can only guess if it worked. Here is the content of that file on my system.
install nvidia modprobe -i nvidia-current $CMDLINE_OPTS
install nvidia-modeset modprobe nvidia ; modprobe -i nvidia-current-modeset $CMDLINE_OPTS
install nvidia-drm modprobe nvidia-modeset ; modprobe -i nvidia-current-drm $CMDLINE_OPTS
install nvidia-uvm modprobe nvidia ; modprobe -i nvidia-current-uvm $CMDLINE_OPTS
remove nvidia modprobe -r -i nvidia-drm nvidia-modeset nvidia-uvm nvidia
remove nvidia-modeset modprobe -r -i nvidia-drm nvidia-modeset
# These aliases are defined in *all* nvidia modules.
# Duplicating them here sets higher precedence and ensures the selected
# module gets loaded instead of a random first match if more than one
# version is installed. See #798207.
alias pci:v000010DEd00000E00sv*sd*bc04sc80i00* nvidia
alias pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00* nvidia
alias pci:v000010DEd*sv*sd*bc03sc02i00* nvidia
alias pci:v000010DEd*sv*sd*bc03sc00i00* nvidiaDo any of those lines appear redundant to an expert who knows how this part of the boot process works? As I said, the generic "error running install command" message looks to me like an installer not completely removed. But I can't distinguish what all of these lines do. If not, is there anywhere else I could look for driver config commands that might be superfluous once the driver is installed?
#233 Re: Installation » Odd message on booting a new install » 2019-07-07 01:25:48
Well, it seemed to be the TDE widget, but when I removed network-manager-gnome it went away. Now I have re-installed network-manager-gnome and the little systray widget is in place. I'll not fuss about it anymore. That leaves the nvidia-driver spurious error message problem.
#234 Re: Hardware & System Configuration » Gkrellm and GkrellWeather » 2019-07-07 01:22:46
Well, it was not a permissions problem. It was a derp problem. The package maintainer did not keep the program config and the installation in sync. Once discovered, it was easily fixed with a manual edit. The GrabWeather script is installed to /usr/share/gkrellm/GrabWeather but the config file tells the program to run it from /usr/local/share/gkrellm/GrabWeather -- resulting in a fail. Despite the bug being reported more than a year ago, it still has not been fixed in the repository. See: https://bugs.debian.org/cgi-bin/bugrepo … bug=895851
#235 Re: Installation » Odd message on booting a new install » 2019-07-06 22:53:06
In the real world, unfortunately, "should be" and "is" are rarely the same thing. When I installed network-manager-gnome, I got the panel app in the menu, but no systray widget. Even after rebooting. But, as already described, when I rebooted into XFCE from testing KDE Trinity, the Trinity widget popped up in my systray. Still fussing with Trinity. It's interesting precisely because it is so blatantly "old school". Sort of like Windows XP for Linux.
#236 Re: Hardware & System Configuration » PulseAudio? Seriously!? » 2019-07-06 22:49:36
Ron wrote:Why would these apps depend on libpulse0 especially since a lot of people on Linux don't use Pulseaudio?
The only people who don't use Pulseaudio these days are hair-shirt minimalists, all the desktop environments have PA as a dependency because it provides a convenient high-level interface for controlling how multiple sources are connected to sinks.
For example, almost all new laptops have HDMI outputs and if pure ALSA is used then it is necessary to configure it to make the inbuilt speakers work, most non-technical users don't know how to do that and so need PA to do it for them.
I would have thought, with all the resentment there was for it even before the same author embarked on the systemd dumpster fire crusade, that it would have been avoided with the same loathing. That's why my initial post. Why would that be in a distro specifically created to get around mini-Bill and his work? Has it really become stable and reliable? It never was in the past. Did some other authors take over and essentially rewrite it?
#237 Re: Installation » Odd message on booting a new install » 2019-07-06 14:14:13
Installing the network-manager-gnome package gives me a panel app in the system menu, but not a systray app. But... I went ahead and installed Trinity Desktop and tried it out. That deserves its own thread. When I restarted into XFCE again, the Trinity systray nm app popped up. So now I have a triple-hybrid monstrosity desktop. Maybe I could remove network-manager-gnome and the Trinity panel app would appear?
#238 Re: Installation » Odd message on booting a new install » 2019-07-05 23:28:47
Well, I was using Mint 17.3 (Rosa) also, but it was the XFCE edition, and that is the default in Devuan anyway. I like XFCE, it's been my default Linux desktop for some time. I do have to admit that I was often borrowing things from Gnome to finish out my XFCE environment, at least until Gnome began to require systemd. Even used Nautilus as a file manager when Thunnar was too raw and undeveloped. I guess I should have tried Mate and Cinnamon. Maybe the accessories like the network manager widget are more complete in those.
After installing the network-manager package I have not found any graphical network management utilities of any sort. Not in the menus, and not in the list of available objects when adding things to the XFCE toolbar. Where would I look?
#239 Re: Installation » Odd message on booting a new install » 2019-07-05 20:49:15
Well, both. I want to find a widget for the systray like I have had on both Windows and every other Debian distro I've ever used. And I want to find the settings, either the text files (if necessary) or a more comprehensive graphical interface. If the widget can be clicked, that's fine. If it's on a menu, that's fine also.
I thought wicd was for Wifi only, but I've also been struggling with a laptop and when I set wicd up, it does watch both the cable connection and the wifi. And it puts a widget on the task bar! At last resort, I may just use wicd even on my desktop systems. I don't plan to put wifi on them, but oh well... it manages direct cable connections, too.
#240 Re: Installation » Odd message on booting a new install » 2019-07-05 16:35:04
There is an entry for networkmanager in the man pages, but it's about NetworkManager, the command line program. What happened to the graphical front-end that is still available in Debian? It's very tedious to have to hunt down a bunch of text files to make minor adjustments to your network.
#241 Re: Installation » Odd message on booting a new install » 2019-07-05 02:29:02
Not sure what happened, but after fiddling with /etc/network/interfaces a couple times I got network access and used it to install NetworkManager. Then commented out the unnecessary fields in interfaces. Now, I seem to have working dependable network access and no strange delays on boot. Yay!
Question -- where do you find the controls/config for NetworkManager? It doesn't have any entries in the System or Settings menus.
#242 Re: Hardware & System Configuration » Gkrellm and GkrellWeather » 2019-07-05 02:26:09
It works for you, but I don't see it working for me. Which is strange. It does work when I manually run the script. But GKrellM doesn't seem to be able to run it. Apparently that indicates a permissions problem? I wonder what I would check for?
#243 Re: Installation » Odd message on booting a new install » 2019-07-05 01:20:21
In the thread cited above: https://dev1galaxy.org/viewtopic.php?id=1688 it suggests change "allow-hotplug" to "auto" in etc/network/interfaces to get rid of the delay on boot.
That's what I did, and it sits there trying DHCP instead of on the init. And when I try to use the network, it doesn't work. So I changed it back. It still sits there waiting, but when the system finally comes up, the network does NOT work. Something else broke by simply changing the IF config to "auto". WTF?
#244 Re: Installation » Odd message on booting a new install » 2019-07-05 00:44:26
Not only did it not help, it broke my network setup somehow. I cannot get a connection anymore. Meaning I can't even install a network manager to try to fix it. What would changing one single line do to the rest of the network config that it would be completely broken?
#245 Re: Desktop and Multimedia » [SOLVED] Nvidia error at boot » 2019-07-05 00:38:33
One more case of the same thing. Same error message, but also no symptoms during uptime. Video seems to be flawless. It sounds like something in the install process was not properly removed and is now retrying at each boot.
#246 Re: Installation » Odd message on booting a new install » 2019-07-05 00:07:28
Unfortunately, now that I have the chance to tinker with the system, I see the same thing described in that other thread. It just waits in another place. This is a completely unacceptable boot problem. It sits there for minutes either way. Why? Other Linux distros have not done this. There must be a config option that doesn't try to setup networking while booting.
#247 Re: Desktop and Multimedia » [SOLVED] Installing VirtualBox in Devuan ASCII » 2019-07-04 21:28:53
Wow, that's nice. I knew that some of the other VM systems can convert other files, but hadn't seen anything about KVM in their lists of compatible formats. At least the Linux world can handle the other system's file formats. I guess I ought to learn about KVM rather than struggle with VirtualBox anymore.
Can you get KVM to run Android? I've seen instructions for installing Android into VirtualBox and it says use the Linux mode. I guess it would be the same with KVM?
#248 Re: Hardware & System Configuration » PulseAudio? Seriously!? » 2019-07-04 21:17:10
Well, I do like XFCE. The two original old standby desktops have gone nuts. KDE is an insane widget zoo that requires cutting edge hardware just to run and is very annoying when it does run. Supposedly all the fancy useless graphical hand-waving can be disabled but I don't even want to try to wade through the settings and find where to do that. Gnome is not quite as flashy but has gone down a similar route, trying to out-do Windows for bloat and restrictions meant to "help" the user do things The Right Way [tm]. But as the saying goes, make something foolproof and only a fool will use it.
The only competition I am aware of for XFCE right now is LXDE, but as the new kid on the block it's missing a lot of those "mature" features that take time to complete. If XFCE needs PulseAudio, I guess it will have to stay.
Edit: But I do need to try the "Trinity" Desktop one of these days... it's based on KDE 3, which was still sane.
#249 Re: Desktop and Multimedia » [SOLVED] Installing VirtualBox in Devuan ASCII » 2019-07-04 17:09:58
KVM seems to be the native Linux virtualization solution, but can you migrate a KVM machine to any other virtualization system? What if I want to run something from a KVM on Linux in a Windows environment?
#250 Re: Hardware & System Configuration » PulseAudio? Seriously!? » 2019-07-04 17:00:16
Argh... I'd hate to remove it and then find out that Firefox requires it. FF is becoming the only viable alternative to Chrome. Guess I'll just install alsa-mixer and leave PulseAudio alone for now.
Board footer
