I installed mate over here and if you installed gnome or unity and the
desktop environment that may be why control-alt-f1 does not work.
Earlier I had an x11 system installed and had removed lightdm and for
gnome. If you can get to the internet settings and bring up a network
with mate and standard utilities installed without desktop environment
and then download and install x11 you'll have a system that stops at
speakup and you get to login and only when you want to do something in
the gui environment you run startX inside of speakup to bring the
graphical user environment up. Inside of that environment you'd want to
have or get orca running.
On Wed, 30 Nov 2016, Nick Gawronski wrote:
Date: Wed, 30 Nov 2016 13:55:43
From: Nick Gawronski <[email protected]>
To: Jude DaShiell <[email protected]>, [email protected]
Subject: Re: debian stretch testing findings
Resent-Date: Wed, 30 Nov 2016 19:24:58 +0000 (UTC)
Resent-From: [email protected]
Hi, I upgraded from Jessie and am not sure what happened as I do lose speakup
as packages are being upgraded. I let the hard drive stop making noise and
then powered off and back on the system and was able to kind of finish the
upgrade process. Now when the system boots up I hear all of the boot
messages but I am placed either into an accessible login screen with orca or
lose speech all together and control and alt and f1 does not bring me to the
console. I did a fresh installation of Jessie before doing the upgrade
process. Orca was working in Jessie but I do the upgrading using speakup.
Nick Gawronski
On 11/30/2016 11:13 AM, Jude DaShiell wrote:
I was able to install debian-stretch-testing using the 3.5MM jack standard
speaker set connected to my computer and speakup came up talking
post-install. I put mate on that installation too and failed to get a wifi
network setup working using command line instructions and wpa_passphrase to
add to wpa_supplicant.conf. I got a start job is running related to
bringing up the network after trying that. While inside mate, screen
reader only works for user accounts and I need talking root access to
configure the network using mate. Since debian does not save any detected
network configuration files so far as I can tell during installation one
almost has to do the network configuration post-install.
When I tried that install of mini.iso earlier I didn't change priority
notifications from medium to low so if a kernel was installed I didn't hear
any choices for it.
I'll try what I did in sonar with debian and see if I can get root access
that way.
If I remember properly I logged in as user; got a terminal, used su - in
terminal and entered root password. Then hit control-alt-tab and got the
top bar menu and went from there into internet and configured wifi network.
Now I'm going to clear the junk I created with the command line failure so
I start from a known state when I try this next procedure.
--
--
