accidental upgrade, what now?

Discussion:

Tom Fowle

2017-10-13 07:47:09 UTC

In attempting to upgrade a single package, elinks, I somehow upgraded the
whole system
I believe to 3.2.0-4-686-pae
that's the login version number, maybe not the upgraded version.

Without rebooting, it still works with doubletalk and brltty.

I assume after reboot with new system the doubletalk will no longer work.

Do I remember there is some way by selecting older kernel at grub boot time,
that the older kernel with doubletalk can still fly.

I have sighted help.
what do we look for when rebooting?

If that's wrong, do I have any other options to save the doubletalk system
beyond re-installing old version of wheezie from CD?

Also considering a new mini desktop like the mintbox mini from
Fit-PC. Any experience with this type of system?
This one has an RS232 port for my Alva. But then I'd have to put up with
espeak! Poor little blind one! <GRIN>
Thanks for any help, comments about luddites will not be taken amiss!
<GRIN>
Tom Fowle
P.S. I'm not turning this box off till forced, but we had power flicker a
while back, so things are tense! <GRIN>
sorry for babble.
Tom Fowle

Willem van der Walt

2017-10-13 08:22:49 UTC

Permalink

You are correct that you should be able to pick your currently running
kernel from the grub menu.
Somewhat generic instructions would be.
When the machine starts, move with the arrow down to stop the boot of the
default OS.
Then select the one you want to boot with the arrows and enter on the
desird one.
Since you are still on the machine, You can change the default so that it
will again boot with your currently running kernel next time.
how to do this might differ depending what flavor of Linux you are
running.
HTH, Willem

[The e-mail server of the sender could not be verified (SPF Record)]
In attempting to upgrade a single package, elinks, I somehow upgraded the
whole system
I believe to 3.2.0-4-686-pae
that's the login version number, maybe not the upgraded version.
Without rebooting, it still works with doubletalk and brltty.
I assume after reboot with new system the doubletalk will no longer work.
Do I remember there is some way by selecting older kernel at grub boot time,
that the older kernel with doubletalk can still fly.
I have sighted help.
what do we look for when rebooting?
If that's wrong, do I have any other options to save the doubletalk system
beyond re-installing old version of wheezie from CD?
Also considering a new mini desktop like the mintbox mini from
Fit-PC. Any experience with this type of system?
This one has an RS232 port for my Alva. But then I'd have to put up with
espeak! Poor little blind one! <GRIN>
Thanks for any help, comments about luddites will not be taken amiss!
<GRIN>
Tom Fowle
P.S. I'm not turning this box off till forced, but we had power flicker a
while back, so things are tense! <GRIN>
sorry for babble.
Tom Fowle
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Tom Fowle

2017-10-13 08:43:12 UTC

Permalink

Willem,
Thanks, relieves my panic. Running Debian wheezy
Tom Fowle

Post by Willem van der Walt
You are correct that you should be able to pick your currently
running kernel from the grub menu.
Somewhat generic instructions would be.
When the machine starts, move with the arrow down to stop the boot
of the default OS.
Then select the one you want to boot with the arrows and enter on
the desird one.
Since you are still on the machine, You can change the default so
that it will again boot with your currently running kernel next
time.
how to do this might differ depending what flavor of Linux you are
running.
HTH, Willem

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Tom Fowle

2017-10-14 02:43:48 UTC

Permalink

Did it upgrade or did it not?
Some programs act differently, but it still boots in same version with
doubletalk.

the original reason for upgrade was to solve problems with elinks which
didn't get solved.

I won't bother this list with elinks difficulties.

Thanks Willem, greg etc.
Tom Fowle

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Chime Hart

2017-10-13 22:40:07 UTC

Permalink

Tom, I figure all the work that several folks have done over the last year or so
would let you run your synth with newer kernels. I think there are dot deb files
you can run to enable speech after upgrading?
Chime

Gregory Nowak

2017-10-13 23:32:43 UTC

Permalink

Nope.
<https://www.github.com/bytefire/speakup/issues/5>

If Tom wants to keep using his doubletalk pc, then his best bet for
now is to stay with the kernel from debian wheezy.

Greg

--
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-***@EU.org

Tom Fowle

2017-10-14 02:46:23 UTC

Permalink

Chime
As Greg says, nope Doubletalk is probably a lost cause but will hang on and
look at Greg's git issues list entry occasionally. I'd comment there
but have nothing but "please" to say.

Tom Fowle

Post by Chime Hart
Tom, I figure all the work that several folks have done over the
last year or so would let you run your synth with newer kernels. I
think there are dot deb files you can run to enable speech after
upgrading?
Chime
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup