Thank you all for the advice regarding the Xserver problems. I am still not
sure what happened here but following your advice and with some other ideas
Disable nouveau when booting press e add nouveau.modeset=0 press F10. This
boots and allows me to log in.
ps -A | grep shows that startx, xinit and Xorg are not running so clearly a
step in the right direction.
startx fails with no screens found and that it is using /etc/X11/xorg.conf.
Renaming /etc/X11/xorg.conf to /etc/X11/xorg.conf.bak and trying again also
fails with no screens found but now reports that it is using
A quick look in there shows a file 20-nouveau.conf which identifies the
video card as Nvidia and uses the nouveau driver. Renaming that to
20-nouveau.conf.bak and restarting the system brings everything up normally.
I have no idea what happened, what was wrong with these files or why
renaming them worked. In fact not even sure what video drivers I am running
right now. Much still to investigate.
Thanks for the suggestions.
On Fri, 26 Apr 2019 at 01:41, Timothy Rice <timothy.rice(a)unimelb.edu.au>
> Hi Stripes,
> On Thu, Apr 25, 2019 at 08:49:48AM +0100, 'stripes theotoky' via mlug-au
> > Following the latest update on my Devuan box I have lost the Xserver.
> > <snip>
> If you haven't checked /var/log/Xorg.0.log yet, you might want to check it
> What is your usual method of starting X? Eg do you rely on a login manager
> such as slim, or do you set up an ~/.xinitrc and run startx? What's your
> If you've been relying on a login manager and/or a fullblown desktop
> environment, you might find it easier to troubleshoot if you switch to the
> startx method and launch a simple WM like openbox. How to do that is
> covered at https://wiki.archlinux.org/index.php/Xinit
> ~ Tim
> You received this message because you are subscribed to the Google Groups
> "mlug-au" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mlug-au+unsubscribe(a)googlegroups.com.
> To post to this group, send email to mlug-au(a)googlegroups.com.
> Visit this group at https://groups.google.com/group/mlug-au.
> For more options, visit https://groups.google.com/d/optout.
Following the latest update on my Devuan box I have lost the Xserver.
The box boots normally then instead of a log in screen it is just black.
Pressing Alt Ctrl F1 gets me to a terminal where i can log in.
ps -A | grep shows that slim and Xorg are running. Xorg on tty7.
Pressing alt ctrl F7 turn the cursor off in tty1 but does nothing else.
I am using the nouveau drivers.
dmesg seems to show them loaded.
I have run apt purge nvidia* just to be sure they are not installed.
nothing is blacklisted in /etc/modprobe.d/
xorg.conf refers to nouveau
modprobe shows the nouveau drivers loaded.
Any ideas on where to go from here?
Some time ago, Andrew Pam expressed a need for floppy drives for a
particular project he was considering.
My collection of at least 12 drives, mostly of the " no facia "
version , would be immediately available, should the need remain.
After the posts last week about android I thought I would try
android-x86 on my Samsung Slate currently running Debian Buster. At
first I tried the rpm version using alien. The scripts configure android
with qemu and also adds a grub entry for dual booting. The qemu version
works well. When I tried to boot neither android nor Debian would boot.
Android would just return to the grub screen and Debian would stuck at '
Loading Linux 4.19.0-4-amd64' . So more fool me for trying the alien rpm
So boot with rescue usb, chroot, and alien -e android-x86 to remove
android. Update-grub and reboot. All OK boots into Debian. So make
Android-x86 boot usb and reboot into installation mode. Install Android
into /dev/sda1 without formatting as per
http://www.android-x86.org/documents/installhowto. Do not install grub.
Installation finishes. Option to run android with out rebooting, works fine.
Reboot and can't get passed grub. Same symptoms as before. Booting with
rescue usb, chroot, and update-grub appears to work but after reboot
won't get passed grub.
Then at grub screen click on c and get grub shell. set root(hd0,1) and
get the grub prompt again, using ls I can see all of the required files
with tab to autocomplete so,
linux /boot/vmlinuz-4.19.0-4-amd64 root=/dev/sda1
sticks. Doesn't return to grub prompt. No timeout.
Get supergrub usb. Boot, sees the partition and can boot Debian.
What am I missing here? I getting close to nuking everything and
reinstalling. Any ideas?
I'm looking for both wearable hardware and software for heart rate monitoring
on linux. On wrist or chest strap is fine.
Heart rate monitoring is essential. Oxygen saturation and ECG functionality
would be nice too.
I've got a better idea of what I **DON'T** want than what I do. I don't want
anything that requires sync to a corporate server, I want to BUY a product,
not BE one (optional syncing is fine, I can choose not to use it). I just
want something that gathers data and either transmits it in real time to my
bluetooth-paired desktop machine and/or android device, or logs the data
for later download.
I'll also need software to display and/or analyse the data.
I've seen lots of cheap devices on ebay for $10-$20 but have no idea if they
can be made to work with linux or if they use their own proprietary protocols
and only work with their spyware app.
I'd prefer to avoid brand name equipment, because I see no good reason to pay
$300 or $400 for hardware not significantly better than the stuff that sells
for under $20 - especially when I explicitly do not want any "value added"
cloud services they provide, services that get promoted as features but I see
as spying malware.
in short what i'm after is:
* open source data acquisition, visualisation, & analysis
* open data formats
* no mandatory spyware service
Any clues or pointers to relevant hardware or software would be appreciated.
 i've found https://github.com/Freeyourgadget/Gadgetbridge (which is
availabled on the F-Droid app store) so something compatible with that would
craig sanders <cas(a)taz.net.au>
Is anyone seeing this problem and if they are do they know a solution?
About 2 twice a week when waking the box from suspend wicd fails to connect
to the wifi with a bad password error. The solution usually is to suspend
the box again and on wake the second time the wifi is connected and working.
Occasionally on wake the suspend dialogue is still on the screen and
everything except movement of the mouse is frozen. In this case a hard
reset is the only solution.
I am using the latest Devuan with LXDE but have
ca-certificates, elogind, libelogind0, libpam-elogind, openssl
held back to earlier because the city supplied wifi here uses SSL3
upgrading these disables my ability to connect. I don't see how this would
cause the above problems but included for completeness.