You are not logged in.
- Topics: Active | Unanswered
#101 Re: Installation » mini HowTo install ascii on a RaspBerry pi 3 B+ » 2018-07-20 17:32:16
I think this is missing a part.
While parted does show the new size:
(parted) print
Model: SD SC16G (sd/mmc)
Disk /dev/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 135MB 134MB primary fat16 lba
2 135MB 15.9GB 15.8GB primary ext4
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 14.9G 0 disk
|-mmcblk0p1 179:1 0 128M 0 part /boot
`-mmcblk0p2 179:2 0 14.7G 0 part /however ... the filesystem doesn't seem quite right:
# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 1743136 777240 859300 48% /
devtmpfs 438328 0 438328 0% /dev
tmpfs 88764 1200 87564 2% /run
tmpfs 5120 4 5116 1% /run/lock
tmpfs 177520 0 177520 0% /run/shm
/dev/mmcblk0p1 130798 35754 95044 28% /boot/dev/root size should be much larger, it is only reporting 1,743,136 KB (~1.7 GB).
#102 Re: Other Issues » Devuan Ascii - Suspend change? » 2018-07-02 03:05:22
To reply to my self (or is it preferred to edit the original post):
Apparently this didn't begin with the Ascii upgrade (which I did 2 weeks ago) -- /var/log/pm-suspend.log has a date of Fri Jun 29 (morning wakeup time). There's no record of Fri Jun 29 (night sleep time) or Sat Jun 30, Sun Jul 1 in /var/log/pm-suspend.log at all. This is likely when the suspend/resume hooks stopped running. This seems strange to me. I have rebooted in the meantime, which did not correct the issue. On Jun 29 I did remove mono and a bunch of things along with it... I'll see if any of that is related. So at this point it seems less likely a bug and more likely something I've done to my own system.
[Mon Jul 2 AM edit]
So last night I directly ran /usr/sbin/pm-suspend instead of /usr/bin/xfce4-session-logout --suspend
The result was the hooks were called on suspend/resume, /var/log/pm-suspend.log was updated, screen was not locked on resume (of course).
I suppose I could change my suspend routine to call /usr/bin/xflock4 then run /usr/sbin/pm-suspend, after granting my user account the ability to run /usr/sbin/pm-suspend . Still unclear as to what changed with xfce4-session-logout .
#103 Other Issues » Devuan Ascii - Suspend change? » 2018-07-01 19:44:57
- rbit
- Replies: 1
In Jessie this worked:
/usr/bin/xfce4-session-logout --suspend
before suspending, the system would call
/etc/pm.d/sleep/50_unmount
which I have unmount certain things...
Now in Ascii, the /etc/pm.d/sleep/50_unmount is no longer called when suspending.
In fact, none of the files in /etc/pm.d/sleep are called when resuming from suspend, either.
Is this a bug or intentional change, or do I have something else misconfigured?
I can work around this, but just wondering what has changed or if /etc/pm.d/sleep/* has been abandoned for some other way of calling scripts on suspend/hibernate/thaw/resume.
#104 Installation » my jessie -> ascii dist-upgrade experience » 2018-06-12 01:12:34
- rbit
- Replies: 1
First ran on a (backed-up) virtual machine. The only "major" problem was with wicd, a missing file /etc/dbus-1/system.conf -- I copied from my host system and resumed the upgrade... it finished, rebooted, all seems to be okay.
Then backed up my "baremetal" system. Some other errors (depencencies?) partway through, had to run a "apt-get --fix-broken install" then resume the dist-upgrade. Same issue with wicd, copied system.conf from most recent backup and resumed upgrade. Rebooted, no gui. Reinstalled nvidia driver, rebooted, all seems okay. Remmina was uninstalled. Opened synaptic to some error, had to run "dpkg --configure -a", now synaptic works. Had to force specific remmina version (something about backports?), now it is okay. Had to redo some other minor tweaks, but overall a rather painless experience. Just kind of curious about that wicd thing, it seems the system.conf is deleted too early in the upgrade process?
I know this is supposed to work, in theory, but is it recommended to try debian 8 -> devuan ascii upgrade on a remote (ssh) machine? Will I lose ssh connectivity during the upgrade process, what other things should I be aware of before attempting it?
Again, thanks to the developers for their work in this project, and the people who provide forum support / other chat.
Board footer
