The officially official Devuan Forum!

You are not logged in.

#1526 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-14 21:47:24

Hello:

I hate quoting myself ...

Altoid wrote:
~# cat /var/log/syslog
--- snip ---
Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411)
Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files.
Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411)
--- snip ---

As I wrote previously, the NVIDIA device files (/dev/nvidia*) do not exist.

Now, looking around the web I found this: https://forums.developer.nvidia.com/t/d … t/110139/4

forums.developer.nvidia wrote:

The content of your /etc/modprobe.d/nvidia.conf file is not correct. It should read options nvidia NVreg_DeviceFileMode=0660 You forgot ‘nvidia’ – and NVreg_ModifyDeviceFiles=0 means to not create /dev/nvidia* nodes at all.

Also this:

forums.developer.nvidia wrote:

You need to recreate your initrd to make the changes to /etc/modprobe.d/nvidia.conf effective.
Note that there is no proper rights management for the nvidia device files. They are expected to be rw for everyone, otherwise things don’t work. That’s why nvidia-modprobe exists. It’s suid root and will (among other things) fixup everything to be 0666. nvidia-smi calls it if necessary.

If I get (?) the idea behind these texts, /etc/modprobe.d/nvidia.conf (probably part of the drivers installation) could be incorrect and reading something other than nvidia NVreg_DeviceFileMode=0660 and have NVreg_ModifyDeviceFiles option set to =0.

If this is so (fail to understand how this could be) this, it would explain why the /dev/nvidia* files are missing.         

Any idea as to how to proceed and check the /etc/modprobe.d/nvidia.conf?
I don't have one in my Beowulf installation.

Thanks in advance,

A.

#1527 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-14 16:32:54

Hello:

HevyDevy wrote:

what does your ascii installation have to ...

Nothing.
I was comparing my working ascii installation with what nvidia drivers was installing in Beowulf.

HevyDevy wrote:

... using beowulf or ascii ?

Like I mention in my OP, my working installation is ascii and I'm installing Beowulf on a separate drive to see how it goes.

HevyDevy wrote:

Also, why not follow this guide ?
https://wiki.debian.org/NvidiaGraphicsDrivers

I installed the these nvidia-340XX legacy drivers in Beowulf in the very same way I have done it in Devaun ascii, Jesse, PCLinuxOS, Linux Mint and others. ie: ever since I retired my old rig with 'ancient' Matrox G550 PCI cards as there were no available drivers for Linux.

I'll have a look at the guide (*) but if these drivers installed with no issues on this box (exact same hardware) running ascii, I'd say there is a high probability that the problem lies with the Beowulf Nvidia-340xx package or something that has changed in Beowulf that creates some incompatibility.

There has been an important change in Beowulf wrt how su works, now we have to use su - instead.
Could this output from var/log/syslog be a clue?

~# cat /var/log/syslog
--- snip ---
Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411)
Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files.
Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411)
--- snip ---

Thanks for your input.

Cheers,

A.

(*)

Nvidia Graphics Drivers Wiki wrote:

--- snip ---
DKMS will build the nvidia module for your system, via the nvidia-legacy-340xx-kernel-dkms package.
--- snip ---

This is what (for whatever reason) is not happening.

#1528 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-14 15:16:49

Hello:

My ascii installation has both.

groucho@devuan:~$ apt list | grep libnvidia-legacy-340xx-cfg1
libnvidia-legacy-340xx-cfg1/oldstable,now 340.108-3~deb9u1 amd64 [installed,automatic]
groucho@devuan:~$ 
groucho@devuan:~$ apt list | grep nvidia-xconfig
nvidia-xconfig/oldstable 390.87-1~deb9u1 amd64
groucho@devuan:~$ 

nvidia-xconfig was there when I tried to install the driver (sorry for the lapse) but it would not work.

My sources list (from the Devuan GNU/Linux 3.0 (beowulf) amd64 - netinstall 20200526) are these:

deb http://pkgmaster.devuan.org/merged beowulf main non-free contrib
deb http://pkgmaster.devuan.org/merged beowulf-security main contrib non-free

# beowulf-updates, previously known as 'volatile'
deb http://pkgmaster.devuan.org/merged beowulf-updates main contrib non-free
deb http://pkgmaster.devuan.org/merged beowulf-backports main contrib non-free

I saw no reason to modify them as I understand that if a package is in the Debian repository it will then be in the Devuan repositories, save for the systemd stuff.

Thanks for your input.

Cheers,

A.

#1529 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-14 14:10:48

Hello:

HevyDevy wrote:

Maybe need to modprobe /dev/nvidia* ?

Yes.
But like I mentioned previously, the files are not there.

HevyDevy wrote:

... tried nvidia-xconfig ...

Not there either.

Before rebooting (and after) I tried apt purge nvidia-persistenced and then apt install nvidia-persistenced but it does not nstall.
The issue E: nvidia-persistenced: installed nvidia-persistenced package post-installation script subprocess returned error exit status 1 remains.

The only way out is apt purge *nvidia* to recover the desktop.

There seems to be a problem with the nvidia-persistenced package (seems to be a daemon) which will not start because the nvidia device files (/dev/nvidia*) are not where they should be.

Maybe a bug in the package?

Thanks for your input.

A.

#1530 Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-13 22:50:50

Altoid
Replies: 45

Hello:

I'm attempting to install the Nvidia legacy 340XX driver to be able to use my three monitor setup in Beowulf.

The two or three times I have done this with different Linux distributions, it was a matter of transplanting a previously working xorg.conf file and 'maybe' tweaking it a bit, never had serious issues.

The first transplant to a Devuan installation was from PCLinuxOS to the Devuan Jesse and from then onwards.

This is the second time I am attempting to install the proprietary driver in Beowulf and as I know what will happen, I have avoided a reboot so I can get the data.  ='7

Here's what synaptic had to say (previous driver installation was with apt but the printout was lost):

E: nvidia-persistenced: installed nvidia-persistenced package post-installation script subprocess returned error exit status 1

I then opened a terminal to see what was going on:

oot@devuan3:~# dkms status
nvidia-legacy-340xx, 340.108: added
root@devuan3:~# 

Seems the driver is installed (?)

So then I tried to see if anything was missing:

groucho@devuan3:~$ su -
Password: 
root@devuan3:~# apt install -f
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

1 not fully installed or removed.  <--- THIS seems to be the problem.

After this operation, 0 B of additional disk space will be used.
Setting up nvidia-persistenced (418.56-1) ...
Starting NVIDIA Persistence Daemon

nvidia-persistenced failed to initialize. Check syslog for more details.  <--- THIS seems to have caused the problem.

invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
 installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@devuan3:~# 

This confirmed what synaptic said.

~# cat /var/log/syslog
--- snip ---
Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411)
Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files.
Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411)
--- snip ---
root@devuan3:/# ls /dev/nvidia
ls: cannot access '/dev/nvidia': No such file or directory
root@devuan3:/# 

What's going on?

I will leave this here, reboot and see about cleaning up, otherwise I will not have X.

Any ideas welcome.

Thanks in advance,

A.

#1531 Re: Installation » openbox menu issue » 2020-09-13 22:12:08

Hello:

Altoid wrote:

Found it:  Command: pkexec pluma %f ...

... does not work.

According to the xfce page it should work:

Edit file as root

Name: Edit as root
Command: gksu put-your-favourite-text-editor-here %f
File pattern: *
Appears if selection contains: Text files

Note: You'll need to replace put-your-favourite-text-editor-here with your favourite text editor (e.g. mousepad or geany). Also, see previous note about gksu.   -> Note: Some distributions no longer include gksu. Use pkexec instead.

https://docs.xfce.org/xfce/thunar/custo … le_as_root

What am I missing?

Thanks in advance,

A.

#1532 Re: Installation » openbox menu issue » 2020-09-13 02:06:53

Hello:

Altoid wrote:

But the 'Custom actions' I hace set up in Thunar, such as "Edit as root" or "Open root Thunar here" use gksudo.

Command: gksu -l pluma %f and Command: gksu thunar %f in 'Edit' -> 'Configure custom actions ...'

How do I get them working with polkit?

Found it:  Command: pkexec -l pluma %f and Command: pkexec thunar %f in 'Edit' -> 'Configure custom actions ...'

A question remains:

Would it be better to run lxpolkit instead of gnome-polkit?

Thanks for your input.

Cheers,

A.

#1533 Re: Installation » openbox menu issue » 2020-09-12 23:48:10

Hello:

Head_on_a_Stick wrote:

So is the policykit-1 package installed?

Yes.
The gnome version.

Head_on_a_Stick wrote:

That OnlyShowIn bit indicates that the program will only be autostarted for the listed desktops ...
... policykit-1 package and a graphical authentication agent need to be running ...

Both gparted and synaptic are working now.

Would it be better to run lxpolkit instead of this one?

Head_on_a_Stick wrote:

Polkit is the modern way to run graphical applications ...
... minimises the security risks in comparison to su &sudo or gksu & gksudo.

Yes, I understand.

But the 'Custom actions' I hace set up in Thunar, such as "Edit as root" or "Open root Thunar here" use gksudo.

Command: gksu -l pluma %f and Command: gksu thunar %f in 'Edit' -> 'Configure custom actions ...'

How do I get them working with polkit?

Head_on_a_Stick wrote:

... gparted running with su but ...

Why would I want to do that?
It is stupid! 8-D!

Thanks for your input.

Cheers,

A.

#1534 Re: Installation » openbox menu issue » 2020-09-12 22:22:09

Hello:

Head_on_a_Stick wrote:

... any error messages if you run /usr/sbin/gparted directly in a terminal?

Yes.

groucho@devuan3:~$ /usr/sbin/gparted
localuser:root being added to access control list
Error executing command as another user: No authentication agent found.
localuser:root being removed from access control list
groucho@devuan3:~$ 
groucho@devuan3:~$ su
Password: 
root@devuan3:/home/groucho# /usr/sbin/gparted
sh: 1: dmidecode: not found
======================
libparted : 3.2
======================

In this last instance, via su (not su -), gparted ran. 

root@devuan3:/home/groucho# su -
root@devuan3:~# /usr/sbin/gparted

(gpartedbin:2414): Gtk-WARNING **: 21:52:42.365: cannot open display: 
root@devuan3:~# 
Head_on_a_Stick wrote:

Can we see

grep -A2 gparted ~/.config/openbox/menu.xml

Of course ...

groucho@devuan3:~$ grep -A2 gparted ~/.config/openbox/menu.xml
		<item label="gparted">
			<action name="Execute">
				<execute>/usr/sbin/gparted</execute>
			</action>
		</item>
groucho@devuan3:~$ 
Altoid wrote:

Looking around I found /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop and the the executable is there.

Head_on_a_Stick wrote:

But it's not being run:

/usr/lib/x86_64-linux-gnu/openbox-xdg-autostart --list pgrep -a polkit

Hmm ...

groucho@devuan3:~$ /usr/lib/x86_64-linux-gnu/openbox-xdg-autostart --list pgrep -a polkit

ERROR: openbox-xdg-autostart requires PyXDG to be installed

groucho@devuan3:~$ 

Interesting ...

But I previously ran apt-update, apt-upgrade and apt install -f and everything seemed to be right.

Seems the Openbox package needs to add this missing package to the depends list?

root@devuan3:~# apt update && apt upgrade && apt install -f
Hit:1 http://pkgmaster.devuan.org/merged beowulf InRelease
Hit:2 http://pkgmaster.devuan.org/merged beowulf-security InRelease
Hit:3 http://pkgmaster.devuan.org/merged beowulf-updates InRelease
Hit:4 http://pkgmaster.devuan.org/merged beowulf-backports InRelease
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@devuan3:~# 
groucho@devuan3:~$ su -
Password: 
root@devuan3:~# apt install python-xdg
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  python-xdg
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 35.9 kB of archives.
After this operation, 169 kB of additional disk space will be used.
Get:1 http://pkgmaster.devuan.org/merged beowulf/main amd64 python-xdg all 0.25-5 [35.9 kB]
Fetched 35.9 kB in 1s (35.7 kB/s)
Selecting previously unselected package python-xdg.
(Reading database ... 64424 files and directories currently installed.)
Preparing to unpack .../python-xdg_0.25-5_all.deb ...
Unpacking python-xdg (0.25-5) ...
Setting up python-xdg (0.25-5) ...
root@devuan3:~# 

Right, now that python-xdg is installed, we continue and get this:

groucho@devuan3:~$ /usr/lib/x86_64-linux-gnu/openbox-xdg-autostart --list pgrep -a polkit
[ ] 
	  File: /home/groucho/.config/autostart/xscreensaver.desktop
	* Excluded by: Missing Exec field

[*] 
	  File: /home/groucho/.config/autostart/xfce4-clipman-plugin-autostart.desktop
	  Executes: xfce4-clipman

[*] User folders update
	  File: /etc/xdg/autostart/xdg-user-dirs.desktop
	  Executes: xdg-user-dirs-update

[*] Wicd Network Manager Tray
	  File: /etc/xdg/autostart/wicd-tray.desktop
	  Executes: wicd-gtk --tray

[*] PulseAudio Sound System
	  File: /etc/xdg/autostart/pulseaudio.desktop
	  Executes: start-pulseaudio-x11

[ ] PolicyKit Authentication Agent
	  File: /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop
	  Executes: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
	* Excluded by: OnlyShowIn (XFCE, Unity, X-Cinnamon)

[*] AT-SPI D-Bus Bus
	  File: /etc/xdg/autostart/at-spi-dbus-bus.desktop
	  Executes: /usr/lib/at-spi2-core/at-spi-bus-launcher --launch-immediately

[ ] gnome-disk-utility notification plugin for GNOME Settings Daemon
	  File: /etc/xdg/autostart/org.gnome.SettingsDaemon.DiskUtilityNotify.desktop
	  Executes: /usr/lib/gnome-disk-utility/gsd-disk-utility-notify
	* Excluded by: OnlyShowIn (GNOME)

[ ] Xfsettingsd
	  File: /etc/xdg/autostart/xfsettingsd.desktop
	  Executes: xfsettingsd
	* Excluded by: OnlyShowIn (XFCE)

groucho@devuan3:~$ 

I removed XFCE to see if I could just use Openbox, which is probably the cause of what is happening.

Thanks for your input.

Cheers,

A.

#1535 Re: Installation » openbox menu issue » 2020-09-12 20:06:21

Hello:

Head_on_a_Stick wrote:

... run the wrapper script at /usr/sbin/gparted directly from the menu entry.

obmenu -> /usr/sbin/gparted in the 'Execute' box does not work.

Head_on_a_Stick wrote:

... install a graphical polkit authentication agent ...

Looking around I found /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop and the the executable is there.

groucho@devuan3:~$ locate gnome-authentication-agent
/etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
groucho@devuan3:~$ 

I also came upon lxpolkit on the web which in 2010 replaced gnome-polkit in LXDE.
Seems it is leaner and more suited to LXDE.

Head_on_a_Stick wrote:

*Do not* use su or sudo to launch graphical applications with elevated permissions, it is stupid and dangerous.

Good to know.
But it was the only way I got synaptic and gparted to run in my VM with Openbox.

I now have the same problem ...

Thanks for your input.

A.

#1536 Installation » openbox menu issue » 2020-09-12 16:26:51

Altoid
Replies: 11

Hello:

I'm (slowly) installing Devuan3 on a spare drive in my ascii box so I can eventually migrate without any headaches.
One of the things I want to do is use Openbox instead of Xfce of which I have grown rather tired.

I have it on a skeleton VM installation albeint on a single screen (vis-a-vis my 3-screen ascii)  and it works well enough form the time being.

I can start gparted there via lxterminal -e su - gparted but I would like to avoid using sudo.
Same with synaptic, which I keep to use as a GUI to look for applications as I am getting used to apt or apt-get.

So I try using lxterminal -e su - gparted but I only get a flicker on the screen.

My DM is SLiM and I wonder if this is not due to its starting X as root?

If I open the terminal and try to start gparted I get this:

~$ su -
Password: 
~# gparted

(gpartedbin:3660): Gtk-WARNING **: 16:23:29.432: cannot open display: 
~# 

Is there a way around this or do I have to install sudo and a set up sudoers?

Thanks in advance.

A.

#1537 Re: Installation » [Solved] Beowulf Netinstaller problem » 2020-09-07 00:29:01

Hello:

Altoid wrote:

Any idea as to what may be going on here?

Solved by burning the *.iso to the SD Card again.

Curious thing as it did not happen the first time I installed Beowulf.

The installer was skipping a step, the one where it loaded applications, among them probably the one needed to format the drive to ext 3/4.
Otherwise (up to that point) it seemed to work properly.

Maybe some part of the SD Card got corrupted?

Cheers,

CIV

#1538 Re: Installation » Upgrading from Ascii to Beowulf » 2020-09-06 23:15:29

Hello:

golinux wrote:

. . . perhaps you could adopt, adapt and maintain SLiM for devuan . . .

Thanks for the suggestion.
I was expecting it, it is not as if I have never heard it. 8^7

But I am not a coder or programmer, just an advanced (?) user with a few years of (more hardware than software) experience but who can't find his way around bash.

Actually, I'm an architect by trade who got into IT to make ends meet when recession and lack of work hit me broadside in 1995.
As you can imagine, I'd have no idea where to start and at 65+ I'm rather past the point of wanting to find out.

But IMO, the truth is that as SLiM is not news, shiny or desired, one wants to maintain it.

Like I said, a pity.

A.

#1539 Installation » [Solved] Beowulf Netinstaller problem » 2020-09-06 22:42:10

Altoid
Replies: 1

Hello:

I'm slowly approaching Beowulf and to start off I'm installing a parallel systen on an extra 73Gb SAS HDD I have in my box.

But I've come across a strange issue:

I boot up the devuan_beowulf_3.0.0_amd64-netinstall.iso which has been dd'd to a 2.0Gb SD Card but when I get to partitioning the drive, the installer only offers format a partition (or the whole disk for that matter) to ext2, FAT16, FAT32 or SWAP.

The HDD is in perfect health and I can partition and format it with GParted from my Devuan ASCII but the installer won't have anything to do with that. 

Same thing happens even if there is no partiton table on the drive. ie: it has been cleared.

Any idea as to what may be going on here?

TIA,

A.

#1540 Re: Installation » Upgrading from Ascii to Beowulf » 2020-09-06 20:36:44

Hello:

Head_on_a_Stick wrote:

... sorry about the file descriptor misinformation.

It's quite allright.
Happens.

Head_on_a_Stick wrote:

... best display manager is clearly no display manager ...

I would have to agree ...

But (if I recall correctly) not having a DM brought along quite a few (permission?) issues that surfaced while I was installing ASCII.
Cannot recall but installing SLiM solved everything right away and that was it.

So that's why I use SLiM.
I didn't even want the log-on process to execute startx.

I've set it up as simple as possible.
A dark screen with a cursor line: no 'USER', 'PASSWORD' or field to fill out, no 'Shutdown', 'Reboot' or 'Session'.

I wanted to also eliminate the cursor (I know there's a way in the SLiM config file) but never go around to it.

Head_on_a_Stick wrote:

SLiM runs X under the root user whereas a console login followed by startx[0] results in the X server being run under the normal user, which is clearly a major advantage

Indeed it is.

Being things as they are, for the moment I have no choice but to stay with SLiM.
And still think it is a real pity it has been abandoned.

Cheers,

A.

#1541 Re: Desktop and Multimedia » Choosing an email client » 2020-09-06 13:00:41

Hello:

Vernon wrote:

... Thunderbird apt-get install thunderbird for a graphical e-mail client.
... Alpine apt-get install alpine. as a text based e-mail client.

If I recall correctly, after trying out Eudora and some other whose name I cannot recall, I finally settled on Pegasus Mail as my email client.
This was way back then, as I went from W3.11 to W95.
Never looked back.

When I (finally) switched to Linux, it was because I was confident that I would be able to (via Wine) have PMail as my email client and this had the benefit of my being able to have my favourite photo tool (IrfanView) at hand without having to switch OSs.

I was sure that I could eventually manage to do without IrfanView but not without PMail.   

A couple of years ago, I thought that maybe there was an email client out there in Linux-land that could replace Pmail.
After searching through what was available I came across one which looked as it could do: Sylpheed-Claws.

All the boxes seemed to check: it was a similar front end and the Sylpheed-Claws FAQ indicated that it had what to me was a deal-breaker PMail feature: selective mail download.

So I installed Sylpheed-Claws to try it out but found none of that was there and there was no mention of it anywhere save that FAQ.

I asked at one list list but got no reply so I asked at another and got this:

Selective download was never in sylpheed, iirc, but it was in
Sylpheed-Claws many years ago, but was dropped by the time we
switched from gtk1 to gtk2, and has never reappeared (and is not
likely to).

The nearest thing to it would be to set a 'Receive size limit' on the
Receive page of the account preferences. Messages which have been
partially retrieved will show a button when opened, allowing you to
download the message in full.

How 'selective mail download' is in any way comparable (nearest thing) to 'receive size limit' is beyond me.

So ...
Pegasus Mail it will be, rightfully so as it has proven to be excellent and has served me very well for almost 25 years.
I have not been able to find anything to use as a suitable replacement in Linux.

I just hope to someday be able to settle my debt with David Harris.

Cheers,

A.

#1542 Re: Installation » Upgrading from Ascii to Beowulf » 2020-09-05 21:12:32

Hello:

Head_on_a_Stick wrote:

Maintenance for SLiM stopped in 2013 so any security issues will not be addressed.

Yes, I know ...

That's why I said:

Altoid wrote:

A real pity.
With so many capable developers out there, going after the newest shiniest whatever instead of supporting/maintaining good software.  :^ *

~$ echo foo >&3
bash: 3: Bad file descriptor
groucho@devuan:~$ tail -1 /var/log/slim.log
slim: waiting for X server to begin accepting connections.
~$ ls -l /var/log/slim.log
-rw-r--r-- 1 root root 403312 Sep  5 15:44 /var/log/slim.log
~$ whoami
groucho
~$ 

I really wanted to avoid using anything and just log in and startx from the command line.
But it proved problematic for a number of reasons related to other parts of the system, so I went with the simplest and (to me) less problematic DM.

Unsupported and all, I believe BSD had it as the default DM at least up to a couple of years ago.

I recall having seen an article on-line where it was voted the best DM out of 19. (found it!).

Cheers,

A.

#1543 Re: Installation » Upgrading from Ascii to Beowulf » 2020-09-05 16:37:48

Hello:

rdav wrote:

Hi fsmithred
... the ancient DM I use: "Slim".

After trying the two or three out there, I cannot but emphatically recommend SLiM to one and all.
It is not systemd compatible which is not an issue for us but probably the reason nobody is taking care of it these days.

A real pity.
With so many capable developers out there, going after the newest shiniest whatever instead of supporting/maintaining good software.  :^ *

Cheers,

A.

#1544 Re: Hardware & System Configuration » Startech firewire card » 2020-09-04 21:18:53

Hello:

viverna wrote:

... card with VIA VT6308P chipset. Works very well.

Glad to know you got the problem solved.  8^ )

It would be interesting (for future reference to others) if you would post whatever information you have (hardware, brand, source, etc.) as well as what is provided by dmesg, lspci, lsmod, etc.

Cheers,

A.

#1545 Re: Other Issues » sbin PATH problems on Beowulf [SOLVED] » 2020-09-04 19:40:25

Hello:

Head_on_a_Stick wrote:

Because su can be used for things other ...

I see.

Head_on_a_Stick wrote:

Read man su wink

Yes, my use of su is rather limited to the basics, so I really have quite a bit of reading to do.
That's what you get from arriving to Linuxland late in life.  8^7

Thanks for your input.

Cheers,

A.

#1546 Re: Other Issues » sbin PATH problems on Beowulf [SOLVED] » 2020-09-04 18:34:07

Hello:

Head_on_a_Stick wrote:

... seems to be an error ...
... should be added to /etc/login.defs.

I see.

Head_on_a_Stick wrote:

... call su correctly:

su -

^ The - is important.

Of course it is.
su won't work as intended expected without it.

Q:
Why not just get rid of the old su and let the output be command not found?

Now we have sudo, su and su - ...

Thanks for the link.

Head_on_a_Stick wrote:

... a PITA to add a - after the command?

Yes.
I forget to do it because I am very much used to su.
And I don't like sudo although it is convenient if properly used/configured.

Cheers,

A.

#1547 Re: Other Issues » sbin PATH problems on Beowulf [SOLVED] » 2020-09-04 15:26:21

Hello:

altoid wrote:

Would have been mine also ... 8⁷ |

I did not have /etc/default/su and generating the file and adding ALWAYS SET PATH  yes did not work.

What did work was ...

root@devuan2:/home/groucho# export PATH=$PATH:~/usr/local/sbin
root@devuan2:/home/groucho# $echo $PATH
bash: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/usr/local/sbin: No such file or directory
root@devuan2:/home/groucho# 

Got it from https://wiki.debian.org/EnvironmentVariables:

--- snip ---
... after doing su, your PATH may not contain directories like /sbin, and many system administration commands will fail. There are several workarounds:
...

Put the system administration directories (/sbin, /usr/sbin, /usr/local/sbin) in your regular account's PATH (see EnvironmentVariables for help with this).

--- snip ---

BTW: whatever the reason for the change in how su works, I hope it is a good/justified one and not another one of Poettering's wet dreams. It is a PITA.

A.

#1548 Re: Hardware & System Configuration » Startech firewire card » 2020-08-27 16:39:31

viverna wrote:

I read another link:
https://sgcdn.startech.com/005329/media … V2_QSG.pdf
and startech says to offer Linux Ubuntu.

The *.pdf also says this:

Requirements
For the latest requirements, please visit www.startech.com/PEX1394A2V2

That link is to yet another *.pdf that says this:

Software
OS Compatibility
Windows® 2000, XP, Vista, 7, 8, 8.1, 10
Windows Server® 2003

There is no mention of Linux in what seems to be the *.pdf with "latest requirements" for this card/chipset.

The card selling at the site recommended by GNUser is the same one I made reference to.
If it turns out to be expensive, just shop around for any other PCIe card that has the same chipset.

ie: Texas Instruments XIO2213B controller

Cheers,

A.

#1549 Re: Hardware & System Configuration » Startech firewire card » 2020-08-20 00:20:50

Hello:

viverna wrote:

Seller wrote me that Startech firewire card seems recognized in Windows.

Windows is not Linux.  8-⁷
The Startech webpage for this card does not mention Linux support.

That said ...

The card uses the Texas Instruments Texas Intruments -TSB82AA2 chipset and Startech's vendorID is 14b0.

Looking up TSB82AA2+14b0 on the linux-hardware.org website, we get this.

----

Results for 'Texas Instruments', 'TSB82AA2', id='14B0-*', type='firewire controller', bus='PCI' (0)
No data sad

----

Given that it is a card you can probably replace for less than US$25, I suggest that you get one that has Linux support.
   
See this one with a different TI chipset.

There are probably a few others, you'll have to shop around.

Cheers,

A.

#1550 Re: Other Issues » Uploading file to email server - size vs. outgoing total discrepancy. » 2020-08-19 13:26:11

Hello:

Excalibur wrote:

... as you say ...
... contain images of various sorts ...
... would affect the efficiency of the base64 encoding ...

Quite so, the document's physical surface is roughly 50% magazine quality colour photos.

Learnt something new this week.  =^)
Thanks a lot for your input.

Cheers,

A.

Board footer

Forum Software