The officially official Devuan Forum!

You are not logged in.

#2 Re: Other Issues » [SOLVED] No extensions available in iptables after upgrading do ascii » 2018-05-13 12:28:43

If you don't know, then you probably haven't set any pin preferences.

You do know that the last image was 116 Mb, I suppose. Please use the text copied into the posts, rather. You can pipe output to file, or use script to get a typescript file.

Anyhow, I'm guesing your iptables (v1.6.1) is from ascii-backports; where's your kernel from?
Do you have the /lib/modules/$(uname -r) sub tree with kernel modules?
Specifically do you have /lib/modules/$(uname -r)/kernel/net/ipv4/netfilter/ipt_MASQUERADE.ko, which is the module concerned?

#3 Re: Other Issues » [SOLVED] No extensions available in iptables after upgrading do ascii » 2018-05-13 11:24:30

Seems odd; something must have gone wrong with your upgrade.

a) what's your sources.list (and sources.list.d/*) ?

b) what's your pin preferences

c) what does "apt-get -s dist-upgrade" say (the "-s" means "simulate", i.e., "just analyze what would be done, but don't do it")

#4 Re: Hardware & System Configuration » FIPS ssh? » 2018-05-11 00:27:30

Isn't that just a matter of choosing which encryption algorithm(s) your server accepts? I.e., it's your choice, and a property of your running server; not a property of the software as such. And based on a rather superficial web search, I believe that the answer is "Yes": there is a sufficient number of algorithms to use to make your ssh service compliant.

#5 Re: Desktop and Multimedia » when X is killed, lightdm restarts it [SOLVED] » 2018-05-02 13:19:31

It might not work well given that the C-A-Del handler command processing is terminated together with lightdm. You will almost certainly need to spawn a separate script for the actions, and perhaps that it also needs to escape the user cgroups, as it might otherwise be killed together with lightdm anyhow. Apart from that, it's easy smile

Though, the return to X might then also need attention; or does X start happily on tty7 while it's in use by a running getty?

I'd rather suggest that utilizing runlevels (and init) is the "simple" approach.

EDIT: or, it might be possible to shift to, say, tty1 instead, and then not start getty for tty7 at all. The "simpler" line would then be:

sudo chvt 1 ; sudo lightdm stop

I.e., first shift to tty1, then kill lightdm (and the C-A-Del handling). The return to X would be the command

$ sudo lightdm start

If that works, I would call it simpler smile

#6 Re: Desktop and Multimedia » when X is killed, lightdm restarts it [SOLVED] » 2018-05-02 12:05:25

I suppose you'll then need to arrange for running /sbin/getty 38400 tty7 in runlevel 3. For example, you add a line for this to /etc/inittab, to let init manage it:. E.g., the following as a line after the tty6 line might do the job:

7:3:respawn:/sbin/getty 38400 tty7

#7 Re: Hardware & System Configuration » wireless problem on qemu » 2018-04-30 10:55:45

As the dongle behaves in your Debian and mis-behaves in your Devuan, there must be some difference in the code involved, obviously. The start point for tracking that down would be in the versions: of the kernels, of the ath modules and firmwares, of the hotplug handlers, etc. Perhaps you can make a table. Then it would be possible to experiment by aligning versions where possible, and by inspecting the differences more exactly otherwise.

btw, there is also the iw tool (from wireless-tools) for

# iw dev wlan0 scan

Rumours has it that sometimes that works where iwlist fails.

#8 Re: Hardware & System Configuration » wireless problem on qemu » 2018-04-30 01:53:18

Have you tried with rfkill (tool for enabling and disabling wireless devices)? As in a "googled" example:

# modprobe -rf ath9k ath9k_htc
# rfkill unblock all
# modprobe ath9k ath9k_htc

I'm not sure what's the difference from Debian though. It would depend on versions, since the code for bringing up interfaces has had some development recently (last few years). Not long ago, it had a bug where the script could query the interface state too early after power-on. The patch against that problem was to add a sleep into the script between starting the interface and checking its state.

You could also try to use the "auto" method rather than "allow-hotplug", to let the networking init script raise the interface instead of (e)udev.

#9 Re: Hardware & System Configuration » how to completely disable laptop lid detection? [SOLVED] » 2018-04-28 23:53:20

Right, the kernel uses the ec and button drivers for dealing with the lid switch. In my lsmod I have a button module, used by nouveau and i915. I don't have an  ec module, so that's probably built-in, and maybe so is the button module for you(?)
(my kernel is linux-image-4.9.0-5-amd64 version 4.9.65-3+deb9u2 from ascii-security)

If button is built-in, blacklisting is not an option, and according to modinfo button there are only the two parameters lid_report_interval and lid_init_state, which don't appear to be useful here.

But, maybe you have a thinkpad_acpi module, or some other module, that registers as button driver? A quick glance at
modinfo $(lsmod | sed 's/\s.*//') might lead to something...

The other end of the chain is at X, and perhaps installing that xserver-xorg-input-evdev would lead to something...

#10 Re: Hardware & System Configuration » how to completely disable laptop lid detection? [SOLVED] » 2018-04-28 12:36:05

Well, I'm no expert on this, but I think it's the lines following that log line that should tell whether the input is actually added or ignored. On the other hand, it's apparently eudev that presents the lid switch to X in the first place, presumably during its traversal of /sys. Perhaps it traces back to /lib/udev/rules.d/80-libinput-device-groups.rules  or 90-libinput-model-quirks.rules, or some other rule(s), and perhaps there's a suitable knuckle-rap to make eudev ignore the lid switch instead.

Thus I'm thinking that whatever it is that results in the /dev/input/eventX device node should be patched to not do that for the lid switch, and then it won't be presented to X. I tried this by removing /dev/input/eventX manually, and restarting X (not rebooting), which resulted in a log without a "Lid Switch" discovery line. Maybe you could try that as an experiment to see if it makes any difference for your graphics problem. Otherwise it's probably no use in digging deeper.

#11 Re: Hardware & System Configuration » how to completely disable laptop lid detection? [SOLVED] » 2018-04-28 06:18:58

Maybe you have xserver-xorg-input-evdev installed, and it grabs the lid switch as input device for X?
Check /var/log/Xorg.0.log where it says Lid Switch.

#12 Re: Off-topic » surf and surf2 browsers » 2018-04-27 21:28:41

actually it's the  opposite for in/out .... it's page zoom and not text zoom, but ctrl-+ works now.

#13 Re: Off-topic » surf and surf2 browsers » 2018-04-27 21:24:51

On my keyboard, ctrl-- (control minus) zooms in and ctrl-+ (control plus) zooms out. This is surf2=2.0-9 from (current) ascii.

#14 Re: Desktop and Multimedia » Booting direct to the desktop. » 2018-04-27 05:33:07

Right. I suppose you'll need a sibling or replace of /usr/share/xsessions/xfce.desktop to make that happen. Perhaps by replacing all "xfce" with "mate"; and maybe add some particular hand-crafting to the "Exec=..." line at the bottom. Or, just hang around until someone who knows something swings by smile

#15 Re: Desktop and Multimedia » Booting direct to the desktop. » 2018-04-27 04:10:34

If it's slim you could possibly achieve auto-login by editing /etc/slim.conf, and then only change #default_user devuan to be default_user caluser (i.e., remove the # and choose user name wisely), as well as changing #auto_login no to be auto_login yes (i.e., remove the # and change to  yes).

#16 Re: Hardware & System Configuration » nomodeset causes suspend to work only once per boot [SOLVED] » 2018-04-14 12:06:42

Great. You might even want to lodge a bug report on pm-utils to add the appropriate vendor quirk combination into the database for T400.

#17 Re: Hardware & System Configuration » nomodeset causes suspend to work only once per boot [SOLVED] » 2018-04-14 04:19:22

To explore deeper, you might want to try

# PM_DEBUG=true pm-suspend >& LOG 

Reviewing that LOG file might tell you something about why suspending fails.

#18 Re: Hardware & System Configuration » trying to understand basics of SysVinit scripts [SOLVED] » 2018-04-03 04:07:24

You'll probably do need to understand insserv, which is the one using the LSB headers, and manipulating the files /etc/init.d/.depend.{boot,start,stop}, which are the "make files" for the init process. I'm not totally sure where/when/how init uses those files, but as I remember it, those files tell which scripts to run when. The insserv man page points at startpar as the actual driver process, so I guess, all together it's init, insserv and startpar to peruse.

#19 Re: Hardware & System Configuration » occasional boot hang on ascii [SOLVED] » 2018-03-30 21:06:17

From the log snippets, it looks to me to be an X issue, that after launch, X says it's ready (signals) before it's actually waiting for connections. So sometimes it fails when the connection attempt is made. This causes lightdm to try another launch, but the second launch fails before giving any signal. So now lightdm is awaiting the signal from X, while the first X is sitting there waiting for connections.

If you would have a side entrance (eg ssh) ot the system you could check up if it might be this situation.

But I don't really know what to do about it. If any part of this is scripted, eg lightdm, it might be possible to insert a delay between receiving the ready signal and attempting a connection. Or something.

#20 Re: DIY » Warn on exit script for Openbox, JWM etc. » 2018-03-29 21:23:15

Well, since process ids may have anything between one and five digits, you could as well let the interpreter do the tokenization, making it be like the following:

wmctrl -l -p | while read a b c d ; do echo $c ; done

#21 Re: DIY » Warn on exit script for Openbox, JWM etc. » 2018-03-28 12:18:24

It looks like it takes every space character as a delimiter, whereas awk sees space sequences as delimiting units.

#23 Re: Desktop and Multimedia » [Solved] RXVT config ignored when started via x-terminal-emulator » 2018-03-17 23:59:11

By my theory, the desired resources are tagged with urxvt (rather than URxvt), and they are therefore not applicable to a window lacking that tag. The supporting patch would thus be to replace all urxvt with URxvt in the resource definition file(s), and then it all will magically work.

#24 Re: Desktop and Multimedia » [Solved] RXVT config ignored when started via x-terminal-emulator » 2018-03-17 22:46:14

Presumably it's because the WM_CLASS property is different between the two cases, and that the resources for urxvt refers to the differing class tag.

Use xprop | grep WM_CLASS to check.

#25 Re: Hardware & System Configuration » Need to resize partitions before upgrade » 2018-03-17 22:10:30

You'll have Murpy's ghost chuckling at your side, I'm sure smile

1. You should probably not change file system type at the same time as repartitioning. I know that sound engineering tells you to change at least two things every time, but sometimes it's safer to take it in steps.

2. rsync transfer of a root partition is not something I've had success with. Perhaps resizing and dd transfer is an option. (Somewhere someone said ext3 be converted to ext4 without reformatting).

3. Be ready to manually update the UUIDs in grub.cfg and fstab. I'm not sure whether UUIDs will change or not, but I would expect them to.

Board footer

Forum Software