Date
1 - 8 of 8
Virtual Linux and NVDA?
Damien Garwood <damien@...>
Hi,
When I tried to run a Linux-based VM, I got no speech, presumably because NVDA doesn't have access to the machine. So I'm wondering, other than through WSL, is it possible at all to run Linux and somehow get it to interact nicely with NVDA? Cheers. Damien. |
|
Oleksandr Gryshchenko
Hi Damien,
Usually I connect to a Linux machine via ssh and work with it via the command line. Greetings. Oleksandr |
|
Damien Garwood <damien@...>
Hi there,
toggle quoted message
Show quoted text
Yeah, that's what I've been doing up to now myself. But I'm cancelling my VPS subscription soon, so really I need a localised way, if there is one. Cheers, Damien. On 10/01/2021 06:39 pm, Oleksandr Gryshchenko wrote:
Hi Damien, |
|
Dan Miner
You have to understand that a VM provided by VirtualBox or VMWare is very much like having a whole different computer running. NVDA can't "reach in" and inspect the applications. So, you will have to get orca running within the VM itself for GUIs. Be sure you have sound enabled for the VM and the popular distributions can typically have orca turned on via pressing WIN+ALT+S once you believe you have the GUI running. If you don't plan to use a GUI, then you will need to get that Linux system to boot up with SpeakUp ,Fenrir, or some virtual console screen reader of your choice. With a command-line only method, I would just ssh into the box like your previous VPS set up.
toggle quoted message
Show quoted text
Dan -----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Damien Garwood Sent: Sunday, January 10, 2021 1:11 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Virtual Linux and NVDA? Hi there, Yeah, that's what I've been doing up to now myself. But I'm cancelling my VPS subscription soon, so really I need a localised way, if there is one. Cheers, Damien. On 10/01/2021 06:39 pm, Oleksandr Gryshchenko wrote: Hi Damien, |
|
Damien Garwood <damien@...>
Hi Dan,
toggle quoted message
Show quoted text
Yeah, I thought that when it booted and I got nothing. I was just getting absolutely no response - ended up having to do a hard shutdown. And then it clicked - same machine, but...Well. Different machine! I don't know how to set up an SSH server, which is why I ideally need it to work locally. But if it's not possible, it's not possible and I guess I'll have to learn some more advanced wizardry to be able to get stuff done. Including switching back to Windows. I must admit, this is my first time with VM's - whole new (and rather intimidating) area of computing for me. Cheers, Damien. On 10/01/2021 10:49 pm, Dan Miner via groups.io wrote:
You have to understand that a VM provided by VirtualBox or VMWare is very much like having a whole different computer running. NVDA can't "reach in" and inspect the applications. So, you will have to get orca running within the VM itself for GUIs. Be sure you have sound enabled for the VM and the popular distributions can typically have orca turned on via pressing WIN+ALT+S once you believe you have the GUI running. If you don't plan to use a GUI, then you will need to get that Linux system to boot up with SpeakUp ,Fenrir, or some virtual console screen reader of your choice. With a command-line only method, I would just ssh into the box like your previous VPS set up. |
|
Dan Miner
Setting up a basic ssh server is quite easy these days. I don't recall you mentioning a distro but it could be as easy as typing in a terminal :
toggle quoted message
Show quoted text
apt install openssh-server or yum install openssh-server Now, you need to be sure your VM application has fully "grabbed" the keyboard for that magic shortcut to work since you need it sent to Linux and not the host system. Often it is using the right control key to switch in and out like a toggle button. Now if you fill somewhat confident in your typing skills, it is possible to do a sequence of steps that will work on about 90% of the distros out there. You just need to know the default user for the distro and it have sudo rights if not an admin user. The idea is to take advantage of most distros put a virtual console on VC1, get yourself there, login, and install openssh.... all in the "dark". Using today's seeing apps can be a big help here too. Remember, you have a VM.. backup the initial disk image and you can destroy it to your heart's delight. *smile* Snapshots are very useful for this too. Now, I do feel this is off topic for this mailing list but if you feel a need to continue then I suggest moving it to NVDA chat at a minimum. Dan -----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Damien Garwood Sent: Sunday, January 10, 2021 4:13 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Virtual Linux and NVDA? Hi Dan, Yeah, I thought that when it booted and I got nothing. I was just getting absolutely no response - ended up having to do a hard shutdown. And then it clicked - same machine, but...Well. Different machine! I don't know how to set up an SSH server, which is why I ideally need it to work locally. But if it's not possible, it's not possible and I guess I'll have to learn some more advanced wizardry to be able to get stuff done. Including switching back to Windows. I must admit, this is my first time with VM's - whole new (and rather intimidating) area of computing for me. Cheers, Damien. On 10/01/2021 10:49 pm, Dan Miner via groups.io wrote: You have to understand that a VM provided by VirtualBox or VMWare is very much like having a whole different computer running. NVDA can't "reach in" and inspect the applications. So, you will have to get orca running within the VM itself for GUIs. Be sure you have sound enabled for the VM and the popular distributions can typically have orca turned on via pressing WIN+ALT+S once you believe you have the GUI running. If you don't plan to use a GUI, then you will need to get that Linux system to boot up with SpeakUp ,Fenrir, or some virtual console screen reader of your choice. With a command-line only method, I would just ssh into the box like your previous VPS set up. |
|
Jason White
On 1/10/21 12:43 PM, Damien Garwood wrote:
When I tried to run a Linux-based VM, I got no speech, presumably because NVDA doesn't have access to the machine. So I'm wondering, other than through WSL, is it possible at all to run Linux and somehow get it to interact nicely with NVDA?If the virtual machine has a network interface and runs sshd, you should be able to access it via ssh from the host system, with NVDA working as usual. Another option would be to run a screen reader on the Linux guest, and to interact with it directly once you've moved focus into the appropriate window. A third option would be to run Linux directly on hardware, with its own screen reader, instead of virtualizing it. That's what I do. In fact, I'm writing this message on Thunderbird 78.6 under Linux. |
|
bhanu computer <bhanuponguru@...>
that's quite easy t ssh in to your vm if you managed to install ubuntu or any distros, then, turn onn screen reader. or if you can't, just press alt+ctrl+t to open terminal in your vm. then, type in some commands sudo apt-get update sudo apt-get install openssh-server sudo ufw allow ssh when ever you wan't to know what's going on, if you turned on screen reader, then great. if you can't, then use OCR of nvda and check what's going on also, you need your IP address to connect by ssh type in the following in your linux terminal on vm ip route then, do nvda OCR. here i recommend OCR if you have a screen reader in linux because you can copy the IP address to clipboard you will find a text called src some where in thatresult. after that src, you will have some desimal number containing some numbers. copy that to your clipboard then, download putty from http://putty.org open the executable and paste in the IP address in your putty host name or IP address field. then leave every thing as default and click open. you w ill get a warning. simply click yes and enter your user name in login as and password in password field. then you will get a terminal. you can happyly use nvda here. hope this helps On Sun, Jan 10, 2021 at 11:13 PM Damien Garwood <damien@...> wrote: Hi, |
|