Search Results for 'ppa'

[Member stevesr0]

Hi Moddit,

Thanks for response.

I agree that the easiest (and smartest?) way to get a working desktop would be to start with something not minimal.

However, my situation is (a) I have a working minimalist Sid install running Pipewire (with elogind), that I wish to use as a reference comparator for a version of Pipewire (without elogind).

I am walking back and forth between the two to check the differences on the working and nonworking (so far) install.

General update:

I have found a number of additional pieces that are needed for X to work. At this point, I think I may have all the necessary packages and I am trying to figure out a fatal error that causes the Xserver not to connect.

In the /var/log/Xorg.0.log file, I am getting an error “unw_get_proc_info failed: no unwind info found [-10].
Unfortunately, this is not a specific pointer to a unique problem apparently.

It is associated ultimately with a “signal 6 Server aborting” message in my case and some other reports. Other reports associate it with a segmentation fault.

Finished for today.

I may read up on persistence before doing a reboot.

I deliberately did NOT do a “full-upgrade” when I launched the live usb, in order to avoid accidental loading of elogind (although I don’t think that was supposed to happen with the “bare” netinstall provided). So I still have about 140 upgradable packages that come in the netinstall that I haven’t upgraded.
So, I will look thru that list (before rebooting) to see if any of those might be obviously needed to get X going.

It is an interesting (re)educational experience for me.

stevesr0

Hi to readers,

first, if you want an overview of my computer, check my first post:
https://www.antixforum.com/forums/topic/403-forbidden-for-system-updates/

sound was working before in seamonkey but not since the last two versions (12 and 13).
i had to remove the last version first (11), cause it wouldn’t install the new otherwise. then via synaptic, I updated,looked for seamonkey and
instaled the last version (12).
but no more sound via seamonkey.
and with the version 13 neither.
I checked alsamixer, nothing is mute, i disabled the automute. no change.
I had to enable it back cause it brought sound from the computer above the sound of the speakers in vlc.
via F6, I selected my speakers; but still nothing.
see the pictures of my alsamixer attached.

via the terminal, I tried to remove pulseaudio but it is not instaled; and I checked synaptic, apulse is instaled.

as suggested here (https://oldforum.puppylinux.com/viewtopic.php?p=1057904): trying apulse seamonkey from the terminal, it opens seamonkey but still no sound.

then, from https://www.antixforum.com/forums/topic/have-sound-in-firefox-no-sound-in-seamonkey/: I tried to modify the desktop file in /usr/share/applications to read:
Exec=apulse /opt/seamonkey/seamonkey %u
but it refused to modify the file saying “Unable to open the file for writing”.
though I connected as root via the terminal before doing that.

then I tried apulse /opt/seamonkey/seamonkey %u from the terminal, but still nothing.

I want to keep apulse as my computer is an old one.

there is also this in post #12 in https://forums.debian.net/viewtopic.php?t=150955 but i’m not sure, it seems quite technical.

this page : http://kb.mozillazine.org/Mozilla_Suite_:_Issues_:_Sound
it tells me i’m missing some plugins.
if this is the solution, do you know which plugins is the lightest fo an old computer?
I looked at them quickly and java seems the best; but when I looked for it, I only found a debugger add-on
which i’m not sure is useful.

it also says it may be linked to me installing vlc, that could enter in conflict with whatever is already instaled on seamonkey as a sound device. apparently, I have “no installed plugins found” when I look for them.

Can anyone bring any light in any of these directions?

Thanks in advance

• This topic was modified 7 months, 4 weeks ago by Brian Masinick.

Attachments:

1. 

   alsamixer.jpg
   

Looks like Nvidia recently open sourced their drivers (sorta): https://github.com/NVIDIA/open-gpu-kernel-modules

It says they did some processing on the code base (to remove dependency on proprietary tools?).

It apparently has Vulkan support — does this mean it will be easier to integrate Nvidia drivers with Vulkan into antiX?

• This topic was modified 8 months, 2 weeks ago by PenguinGuy.
• This topic was modified 8 months, 2 weeks ago by PenguinGuy.
• This topic was modified 8 months, 2 weeks ago by PenguinGuy.

[Member stevesr0]

(UPDATE: See following post)

Hi Brian and olsztyn,

Thanks for you kind comments. I am very aware of my limited skills and great ignorance, so any assistance is gratefully received and tried out.

Yesterday in the thread on “types of dependencies”, I posted an error message

I see an error message about a missing file (module-rt.c in libwireplumber-module-logind.so) and an error in m-lua-scripting in ../modules/modules-rt.c.

So, I will have to look to see if anyone on the internet has dealt with this.

Today, I saw a post from someone running Void Linux (https://gitlab.freedesktop.org/pipewire/wireplumber/~/issues/236), which was solved by

"running as a dbus-session by creating a simple runit service: 

#/bin/sh
sv check pipewire > /dev/null || /dev/null || exit 1
exec env HOME=/var/run/pipewire chpst -u _pipewire:_pipewire:audio:video dbus-run-session wireplumber

The poster was lacking a /usr/lib/x86_64-gnu-linux/wireplumber/libwireplumber-module-logind.so. On my working install, there is such a file. On the live usb,that file doesn’t exist.

So in the absence of an install which generates a wirplumber-module-logind.so file, apparently a dbus session has to be started by other means.

Since the live usb is using runit as an init (my first time trying it), I guess I could use the same script?

My challenge is to make this work without a reboot, unless I can add persistence or logout and log back in without changing the system. I haven’t seen this listed as an option. If someone knows the answer, please advise.

I will provide update with substantial progress (or problems) or next Monday, which will give others a chance to help me <g>.

All suggestions welcome!

stevesr0

• This reply was modified 8 months, 2 weeks ago by stevesr0.
• This reply was modified 8 months, 2 weeks ago by stevesr0.

[Member DaveW]

anticapitalista,
Thanks for taking time to consider my issue. It looks like the problem was caused by me, and is now corrected.

Before shutdown last night, I edited /etc/X11/xorg.conf.d/synaptics.conf
to change touchpad parameters. However, I mis-typed “Option” on one line. This was discovered by reading /var/log/Xorg.0.log

Apparently, this error was enough to prevent loading a screen.

I apologize for the false alarm. Please mark as Solved. Thanks!

• This reply was modified 8 months, 2 weeks ago by DaveW. Reason: problem solved

[Member olsztyn]

madibi wrote:

(*) issue B: no = (*); means that if I make the install using zzz-IceWM, the issue doesn’t appear, also if at that point I change to fluxbox

Yes. Similar behavior I also experienced in the past when I had these issues. At that time IceWM also had the same issue as Fluxbox but apparently has been fixed since IceWM no longer exhibits drop-down menu issues at this time.
I particular my experience was:
– When initially booted with with IceWM (This is fixed now) or Fluxbox: Experienced drop down issues.
– When after the above switched to JWM (Other Desktops —> JWM): No drop down menu issues – this was normal
– Now switched back to IceWM or Fluxbox (Other Desktops —> Fluxbox): Drop down menu issues were gone – all worked fine

The above appears to match your experience for Fluxbox, as IceWM no longer exhibits drop down menu issues in the first place…

However what I experienced at that time was also:
– Booted initially with Fluxbox (as installed with Fluxbox default desktop): Drop-down menu issue, as you experience currently
– After boot with default Fluxbox desktop switch briefly to JWM (other Desktops): No issues as expected.
– Switch back to Fluxbox: Drop-down issues gone. All works fine.

So if it still works now the same way, then you do not need to install with IceWM if your favorite desktop is Fluxbox and after boot switch to Fluxbox. You can install with Fluxbox as default desktop, the briefly switch to IceWM and back to Fluxbox for drop-down issues to be gone.

Having related my experience in the above, similar to yours, I think I remember one downside of such workaround though:
– After switching back to Fluxbox and so making drop-down menus work on Fluxbox: It worked for some time, even after restarting Chrome/Chromium browser but unfortunately after some time the drop-down menu issues came back (during the same session), and required me to again switch to working desktop (JWM) and back to restore working drop-down menus on Fluxbox. I would be curious if the same still happens…

At some point I just permanently moved on to JWM and never had such issues since…

P.S.:
This workaround to resolve drop-down menu issue by switching desktop to working one and back can be done only with antiX, thanks to antiX having multiple desktops to switch to. The system I like is also MX-Fluxbox, which also has the same drop-down menu issue in my experience. Unfortunately with MX-Fluxbox I cannot use the same workaround as with antiX as in MX there are no alternate desktops to switch to and back…

• This reply was modified 8 months, 3 weeks ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

dear all,
I noticed a strange issue with chromium.

When I install the program, both from the antiX native app «installa programmi» or using synaptic, and after the install is completed I start the program from the menu, always it appears a great white square (see photo below). The with ALT F4 or «app killer» I close it.
When restarted, the program opens apparently normal.

BUT

If I go to the antiX forum home page, and I choose the drop down menu, for example: Forum -> recent posts ==> the output is that I don’t go to the desired page. Instead I am redirected to the “Register” page
(https://www.antixforum.com/register/).

The same applies on other sites that I usually surf.

The first time I encountered the above mentioned issue, I thought that something was wrong in my installation, so I did a new fresh install, unfortunately with no avail.
Than I started to make some tries using the live:
– install from synaptic,
– install from the chromium download page.

The sequence of problems persists.

I have to point out that I choose chromium on this pc after a long search, because it is complete and light.
With it all my needs should be perfectly satisfied (in this specific case for me it is better than FFox.

On the same computer, using Q4OS the same version of chromium simply works with no issues.

Any ideas?

Many thx in advance for your help
m

Please find enclosed my detailed info:

Chromium: Versione 104.0.5112.79 (Build ufficiale) built on Debian 11.4, running on Debian 11.4 (a 32 bit)

$ inxi -Fzx
System:
Kernel: 4.9.0-279-antix.1-486-smp arch: i686 bits: 32 compiler: gcc
v: 10.2.1 Desktop: Fluxbox v: 1.3.7
Distro: antiX-21_386-base Grup Yorum 31 October 2021
base: Debian GNU/Linux 11 (bullseye)
Machine:
Type: Laptop System: TOSHIBA product: Satellite A110 v: PSAB0E-007002IT
serial: <superuser required>
Mobo: TOSHIBA model: HTW20 v: Null serial: <superuser required>
BIOS: TOSHIBA v: 1.30 date: 07/20/2006
Battery:
ID-1: BAT1 charge: 0% condition: 44.4/44.4 Wh (100.0%) volts: 11.1
min: 11.1 model: TOSHIBA PA3465U status: N/A
CPU:
Info: dual core model: Intel T2250 bits: 32 type: MCP arch: M Yonah rev: 8
cache: L1: 128 KiB L2: 2 MiB
Speed (MHz): avg: 1200 high: 1333 min/max: 800/1733 cores: 1: 1067
2: 1333 bogomips: 6915
Flags: ht pae sse sse2 sse3
Graphics:
Device-1: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics
vendor: Toshiba driver: i915 v: kernel arch: Gen3.5 bus-ID: 00:02.0
Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: intel
unloaded: fbdev,modesetting,vesa gpu: i915 resolution: 1280×800~60Hz
OpenGL: renderer: Mesa DRI Intel 945GM x86/MMX/SSE2 v: 1.4 Mesa 20.3.5
direct render: Yes
Audio:
Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Toshiba
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
Sound Server-1: ALSA v: k4.9.0-279-antix.1-486-smp running: yes
Sound Server-2: PulseAudio v: 14.2 running: no
Network:
Device-1: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945
v: in-tree:s bus-ID: 04:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Toshiba
driver: r8169 v: 2.3LK-NAPI port: 4000 bus-ID: 05:00.0
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 96.85 GiB used: 43.91 GiB (45.3%)
ID-1: /dev/sda vendor: Hitachi model: HTS541010G9SA00 size: 93.16 GiB
ID-2: /dev/sdb type: USB model: Mass Storage Device size: 3.69 GiB
Partition:
ID-1: / size: 74.75 GiB used: 43.9 GiB (58.7%) fs: ext4 dev: /dev/sda1
Swap:
ID-1: swap-1 type: partition size: 1.5 GiB used: 0 KiB (0.0%)
dev: /dev/sda2
Sensors:
System Temperatures: cpu: 32.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 157 Uptime: 40m Memory: 2.95 GiB used: 651.3 MiB (21.6%)
Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Packages: 1344
Shell: Bash v: 5.1.4 inxi: 3.3.19

• This topic was modified 8 months, 4 weeks ago by madibi.
• This topic was modified 8 months, 4 weeks ago by madibi.
• This topic was modified 8 months, 4 weeks ago by madibi.

Attachments:

1. 

   screenshot-1.jpg
   

[Member stevesr0]

Hi mikey777,

I have experienced the reverse problem where an antiX kernel worked and a similar version of a debian kernel lacked functionality.

Apparently, kernels are complicated enough that incompatibilities crop up not infrequently.

The kernel developers have produced a tool – kdump – which enables a user to collect crash dumps, which might enable you or one of the more knowledgeable members (not me) to identify what the problem is.

The page describing the tool and how to use it is located at: https://www.kernel.org/doc/html/latest/admin-guide/kdump/kdump.html

Even if you don’t use this, I figure others might try it out.

stevesr0

[Member andyprough]

wb8tyw wrote:

With the higher swapiness, most of the hangs until a web browswer or visual studio code grow too big, are gone. I still have to restart those two applications every few days, because both apps will grow apparently until either the system crashes them or they hang/crash the system.

This is one thing I like about Pale Moon. Run it for several days without a restart, and it’s still sitting there using about the same amount of memory. Firefox and Chromium-based browsers go pretty insane with the memory usage over time. And it doesn’t take several days for it to be noticeable.

Thanks for the lengthy post otherwise. That’s some pretty interesting info you’ve accumulated.

[Member wb8tyw]

Random freezing of a system with limited memory can be caused by the vm.swappiness setting.
For various definitions of what is “linited”.

By default anti-x 19 sets the vm.swappiness value to 10 in /etc/sysctl.conf.

It would be much better if anti-x put their custom values in something like /etc/sysctl.d/20-anti-x-settings.conf.

The lower the value of swappiness, the less Linux does a cleanup of moving memory into the swap file.

If you have plenty of memory, a low value may give you some faster response.

However the problem with a low value is that if you need to so any swapping at all, Linux does not have enough free memory available for the process that needs more memory, which is likely the program you most interested in at the moment, so it has to freeze that program while it goes around to all the other programs and swaps out some memory, repeating that process until it finally gets enough for the program you are using. This will show up as high CPU and high disk rate, if the monitoring programs are not victimized by this.

The default value of vm.swappiness for linux is documented to be 60.

On my laptop with a mere 4Gb, I had these freezes routinely until I commented out the value in /etc/sysctl.conf and added /etc/sysctl.d/95_local_swappiness.conf file with one line: vm.swappiness = 80.

Settings in the “xxx.d” directories is the preferred way to make customizations to packages that support them. This eliminates
the upgrade messages about someone has changed a file provided by this package.

With the higher swapiness, most of the hangs until a web browswer or visual studio code grow too big, are gone. I still have to restart those two applications every few days, because both apps will grow apparently until either the system crashes them or they hang/crash the system.

With a higher swappiness rate, most users will not see any issue, because most programs follow an “80/20 rule”. 80 % of programs use mostly 20% of the code / data.

So while your system is not busy, Linux starts copying parts of memory into the swapfile in the background, usually this is not noticed at all. Executable binaries (not scripts) are also effectively “readonly” swap files for this purpose.

The contents of the memory are not changed by this, and so if a program references the memory that was swapped out before it was reused, a soft page fault occurs and the memory is given back. Soft page faults are very fast because no disk I/O is involved.

But when a program needs memory, there is free memory to expand, and expanding to free memory is also a soft fault operation.

So what you need to know, to more precisely tune the swappiness value is how much memory is allocated for each memory expansion request by the kernel and multiply that by how many processes are CPU bound at one moment. I have not bothered to do that
calculation and just try addjusting swappiness upward until I still have a responsive system, and have minimized the hangs.

There is a formula to determine how much hard faults a system can tolerate with out impacting users, but you need to know some metrics and I do not remember all of them for Linux. Unfortunately for modern system that number is usually pretty low and
not worth calculating.

But back in the early days, knowing this calculation made a big difference on what you could actually get done with your systsem.

You need to know the number of processes that the CPU can run simultaneously with out visible load.
On a VAX/11-750, that number is 4.

You need to know the speed at which the CPU is reading instructions from memory. VAX/11-750 is .75 Mips.

You need to know the DMA transfer rate of the devices that the swap files are on. VAX/11-750 is 4 MB/second for the good disks.

As long as CPU speed in MIPS * number of active compute bound processes is less than the total MB/Second to for the swap file, users will pretty much not notice any swapping.

For most things that Linux is running on, the CPU / Memory speed makes it impossible for most swapfiles reads to be transparent, so there will be some impact to swapping.

Good luck.

[Member stevesr0]

Hi marcelocripe,

Thanks for response.

Xecure’s thread (and his responses to my questions in that thread) were very helpful to my getting Pipewire running.

I never heard of Kega-Fusion. I just looked and found a thread (https://aur.archlinux.org/packages/kega-fusion) which indicated that it works with Pipewire if you add some libraries (lib32-pipewire and pipewire-alsa). You probably already tried that.

Yes, Pipewire is still basically provided by debian in a usable form (apparently) in Sid and testing, not in Bullseye-backports.

I am working on this figuring that in the next year of so, Pipewire may become mainstream and then the main barrier to running it will be the adjustments needed to run it without systemd.

Since I am able to use it (in my simple fashion), I thought it might be useful to try to make it work with antiX in order to allow other antiXers to use it when the time is right.

stevesr0

—————————–
Oi marcelocripe,

Obrigado pela resposta. O fio de Xecure (e suas respostas às minhas perguntas nesse segmento) foram muito úteis para a minha corrida pipewire.

Nunca ouvi falar de Kega-Fusion. Eu só olhei e encontrei um fio (https://aur.archlinux.org/packages/kega-fusion) que indicava que ele funciona com Pipewire se você adicionar algumas bibliotecas (lib32-pipewire e pipewire-alsa). Você provavelmente já tentou isso.

Sim, Pipewire ainda é basicamente fornecido por debian em uma forma utilizável (aparentemente) em Sid e testando, não em bullseye-backports. Estou trabalhando nisso, descobrindo que no próximo ano, a Pipewire pode se tornar mainstream e, em seguida, a principal barreira para executá-lo serão os ajustes necessários para executá-lo sem sistema.

Como eu sou capaz de usá-lo (da minha maneira simples), eu pensei que poderia ser útil para tentar fazê-lo funcionar com antiX, a fim de permitir que outros antiXers usá-lo quando for a hora certa.

stevesr0

• This reply was modified 9 months, 1 week ago by stevesr0.
• This reply was modified 9 months, 1 week ago by stevesr0.

[Member marcelocripe]

Hello stevesr0.

I appreciate you starting this topic.

I started implementing PipeWire in my antiX installations about 3 months ago, I always refer to the tutorial Pipewire to manage audio in antiX 21Pipewire to manage audio in antiX 21 that Xecure created.

PipeWire without PulseAudio can output sound on ZSNES, but cannot output Kega-Fusion sound, apparently PulseAudio is required for Kega-Fusion to work with sound. Some sound cards were only able to work properly after installing and configuring PipeWire. But this process of installing and configuring PipeWire is not so simple for everyone to do, even with Xecure’s excellent explanation.

Debian’s repository is full of the crap called “SystemD”, unfortunately this is the way to input “SystemD” in antiX. As much as the Debian repository has an immense amount of extremely useful application programs, “SystemD” will always be a pest that will enter at some point in an installation or update of some program.

I had already written something about this in another topic, I think that sooner or later the GNU/Linux distributions that don’t want “SystemD” in their operating system at all, need to get closer to each other and maybe share their repositories free from “SystemD” with each other. Bearing in mind that porting the entire Debian repository with “SystemD” to another repository without “SystemD” is a huge job and we would have to have many people working on this process. I hope I can learn to do this in order to help, but for this to be possible, we volunteers need to be trained and the development team will no longer be small and will be able to increase gradually, because if it doesn’t increase, one day, inevitably it won’t have no more developers because life will end for everyone one day since death is the only thing that human beings cannot escape. However, operating systems and programs can continue to exist and continue to live through other people.

PulseAudio slows down antiX, so I turn it on or off when needed. As you have the trial version of antiX, you can access the latest version of PipeWire, unfortunately I don’t have the necessary technical knowledge to be an eternal tester, because I don’t have so much free time to study and learn to fix the system operational with each update.

I’m also happy to test different things on a LiveUSB without persistence to make PipeWire work without libelogind0 or elogind or libpam-elogind or anything that has “SystemD”.

Libera.Chat’s #antiX-translators channel on HexChat with the machine translation program that Robin developed, is still the easiest way for me to be able to communicate and help test together with others from any program, I hope to be able to talk to you through this medium at some point.

– – – – –

Olá stevesr0.

Eu agradeço por você iniciar este tópico.

Eu comecei a implementar o PipeWire nas instalações que eu faço do antiX há cerca de 3 meses, eu sempre utilizo como referência o tutorial Pipewire to manage audio in antiX 21 que o Xecure criou.

O PipeWire, sem o PulseAudio consegue emitir o som no ZSNES, mas não consegue emitir o som do Kega-Fusion, ao que parece o PulseAudio é necessário para o Kega-Fusion funcionar com o som. Algumas placas de som só conseguiram funcionar corretamente após a instalação e a configuração do PipeWire. Mas este processo de instalação e configuração do PipeWire não é tão simples de ser feito por todas as pessoas, mesmo com a excelente explicação do Xecure.

O respositório do Debian está cheio da porcaria chamada “SystemD”, infelizmente é este o meio de entrada do “SystemD” no antiX. Por mais que o respositório do Debian possua uma quantidade imensa de programas aplicativos extremamente úteis, o “SystemD” sempre será um praga que entrará em algum momento em uma instalação ou na atualização de algum programa.

Eu já havia escrito algo sobre isso em outro tópico, eu penso que cedo ou tarde as distribuições GNU/Linux que não querem de forma alguma o “SystemD” em seu sistema operacional, precisam se aproximarem uma das outras e quem sabe compartilharem os seus repositórios livres do “SystemD” umas com as outras. Haja vista que portar todo o respositório do Debian com o “SystemD” para um outro o respositório sem o “SystemD” é um trabalho gigantesco e teríamos que ter muitas pessoas trabalhando neste processo. Eu espero poder aprender a fazer isso para poder ajudar, mas para que isso seja possível, nós voluntários precisamos ser treinados e a equipe de desenvovimento deixará de ser pequena e poderá aumentar de forma gradual, porque se não aumentar, um dia, inevitavelmente não terá mais nenhum desenvolvedor porque a vida acabará para todos um dia já que a morte é única coisa que o ser humano não tem como escapar. Contudo, os sistemas operacionais e os programas podem continuar existindo e continuar vivos por meio de outras pessoas.

O PulseAudio causa lentidão no antiX, por isso eu ativo ou desativo quando é necessário. Como você possui a versão de teste do antiX, você consegue ter acesso a versão mais recente do PipeWire, infelizmente eu não tenho conhecimentos técnicos necessários para ser um testador eterno, pois eu não tenho tanto tempo livre para ficar estudando e aprendendo a consertar o sistema operacional a cada atualização.

Eu também fico contente em testar coisas diferentes em um LiveUSB sem persistência para fazer o PipeWire funcionar sem libelogind0 ou elogind ou libpam-elogind ou qualquer coisa que tenha o “SystemD”.

O canal #antiX-translators do Libera.Chat no HexChat com o programa de tradução automática que o Robin desenvolveu, ainda é o meio mais fácil para eu poder me comunicar e ajudar a fazer testes em conjunto com outras pessoas de qualquer programa, eu espero poder conversar com você por este meio em algum momento.

For a long time now I have been using the /etc/fstab file to mount shared folders on my NAS when booting. In combination with a few symbolic links in my home folder, I find this a very convenient and flexible way to organize my filesystem tree. Yesterday however I experienced some problems with my Synology NAS, and in the course of solving them, an upgrade of the NAS OS from DSM6 to DSM7 was made. The result was that my shared folders on the NAS were no longer mounted. The error messages I saw were not very informative, and even downright confusing. It took some googling to find out how to remedy this problem, so I decided to put it on the forum, in case someone is interested.

To mount a share //<NAS>/<SHARE> at (e.g.) /mnt/<MNT-point> every time I boot up the system, I include the following line in my /etc/fstab file.

//<NAS>/<SHARE> /mnt/<MNT-point> cifs user=<NAME>,password=<PASSWD>,vers=2.0,iocharset=utf8,sec=ntlmsspi 0 0

In the line above, <NAS> is the host name of the server, <SHARE> the name of a shared folder on that server, <NAME> is a user-account on that server (who – of course – must have sufficient rights on that shared folder) and <PASSWD> the password (on the server) associated with the account <NAME>. The parameter ‘vers=’ specifies the version of the SMB-protocol used for the communication between client and server machine, while ‘sec=’ specifies the security method that is being used. Before the upgrade to DSM7, I used the parameter ‘sec=ntlm’, which no longer works. Apparently, security has been tightened on the new version of Synology’s OS.

For this to work the package cifs-utils must be installed.

Keep in mind that /etc/fstab is readable, so if security is a concern, you should replace the ‘user=’ and ‘password=’ parameters with ‘credentials=<PATH-TO-TXT-file>’, and write the ‘user=’ and ‘password=’ parameters on separate lines in that text-file, that only you can read. (I didn’t try this however).

There’s another useful trick to mount a share ‘on the fly’. Open the file manager and type the following in the address bar:

//<NAME>:<PASSWD>@<NAS>/<SHARE>

The share is then mounted in a subfolder of /media/, automatically created by the system. This folder is also automatically removed when unmounting the folder (right-click on it in the menu >Devices and choose [Unmount] in the context menu). If you omit the part :<PASSWD> from the address bar, you are prompted for the password of <NAME> on the server. This works on SpaceFM, but should work on zzzFM as well.

• This topic was modified 9 months, 1 week ago by dirkd.
• This topic was modified 9 months, 1 week ago by dirkd.

[Member Peter Linu]

BobC,
I’m a little confused. I tried putting those 2 lines into the terminal, also with sudo but neither worked. Will you please give me ‘baby’ instructions like;
1. do this
2. do that
3. etc
BTW zzzfm no longer exists in the Desktop manager. I now apparently have zzzIceWM (looks the same to me).

Live-USB = zzz-IceWM-antiX21-runit-64-base: static persistence
VirtualBox= zzz-IceWM-antiX21-runit-64-base

[Member stevesr0]

Hi male,

Thanks for checking that it (apparently) is not obviously linked to systemd in antiX-21 stable!

Then the questions in my mind are:

1. Is this a useful tool to use in antiX?
2. Do its functions overlap with other antiX tools?
3. Does it offer anything that other antiX tools don’t?

ALL COMMENTS APPRECIATED.

Beyond that, my focus was in the possible use of this to enable Pipewire’s use in antiX without elogind or libelogind0. But that question really deserves its own thread – or raising in the thread originated in May 2021 by Xecure [https://www.antixforum.com/forums/topic/pipewire-to-manage-audio-in-antix-21/], which I will do when I have composed a list of the approaches I have seen for running Pipewire without systemd.

stevesr0