From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: Slint: No Sound, Screen not in text mode
Date: Mon, 6 Jan 2020 21:54:04 -0500 [thread overview]
Message-ID: <alpine.NEB.2.21.2001062149520.22387@panix1.panix.com> (raw)
In-Reply-To: <20200107.021828.169.22@[0.0.0.0]>
Could it be e2fsck needs to be run as root on that hard disk?
I think for us screen reader users it would be helpful to have a chron
job run that would repair the hard drive while the system was able to
use the screen reader and let the user know the disk repair job is
starting and to leave the system alone until maybe some sound signal or
message comes up telling them the job is done and here's what got fixed.
I just had to run e2fsck a few minutes ago.
On Mon, 6 Jan 2020, Linux for blind general discussion wrote:
> Date: Mon, 6 Jan 2020 21:18:28
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: blinux-list@redhat.com
> Subject: Slint: No Sound, Screen not in text mode
>
> I have installed the latest slint onto a hard drive, choosing
> "start in graphical mode"
> . Speech was available during install. However, I rebooted with my braille display attached, saw that ubiquitous
> screen not in text mode
> message, and there is no sound.
> I attempted to get a console with ctrl+alt+f1-2-3. No console prompt appeared. Obviously it has started up, because the
> screen not in text mode
> would not be there otherwise.
> During install, I chose the mate desktop, but I forget which window manager I chose.
> Any tips for rescuing this situation would be appreciated.
> Rob
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
--
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.NEB.2.21.2001062149520.22387@panix1.panix.com \
--to=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).