Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I'm trying to configure my Ipega PG-9025 with Retropie with no succeed. I made some progress following this link (https://askubuntu.com/questions/608386/using-ipega-bluetooth-gamepad-with-steam-linux) but it only works at Emulation Station menu...
The gamepad stops working in every emulation system and also gives me some problems pairing and reconnecting my device.
Has someone any other advice? Any other try?
Thank you very much
Finally I found a solution: I installed the last Retropie 3.0 BETA version. It has the bluetooth manager integrated and you will need only some few steps to configure your Ipega PG-9025:
1) First time you'll need to pair your Ipega with Raspberry (once is done, no need to do this anymore).
Check if your dongle is correctly connected:
$ hcitool dev
Get your adapter number (e.g. hci0)
$ hciconfig
Scan your bluetooth Ipega device:
$ hcitool scan
Pair your device using the MAC number scanned previously:
$ sudo bluez-simple-agent hci# xx:xx:xx:xx:xx:xx
After pairing connect your controller:
$ sudo bluez-test-input connect xx:xx:xx:xx:xx:xx
You will need to trust this device to allow auto-connection after a reboot:
$ sudo bluez-test-device trusted xx:xx:xx:xx:xx:xx yes
2) Check if your controller is in the input devices and responds correctly:
Verify there is an input file in e.g. /dev/input/js0
$ ls /dev/input
You can also try your device using the following command:
$ jstest /dev/input/js0
3) Now you can configure it running the retropie_setup.sh script:
cd RetroPie-Setup/
sudo ./retropie_setup.sh
In the menu, select these options and follow the instructions:
SETUP (only if you already have run one of the installations above)
317 Register RetroArch controller
And that's all, if you need to use Neo Geo system you will need an extra configuration explained here: https://github.com/petrockblog/RetroPie-Setup/wiki/Neo-Geo#controls
It's just test your device (jstest /dev/input/js0) and set the button numbers in the correct config file.
Here my Ipega PG-9025 and Nintendo64 demo running in Retropie 3.0 BETA: https://www.youtube.com/watch?v=DmvQi0w0Tec
Great tutorial helped a lot.
I had to start bluetoothd deamon for all this to work
sudo bluetoothd
Some ppl had problems if thay had sixad service runing and paired with ps3 controler
sudo service sixad stop
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I am a newbie at Linux, in fact this is the first time i'm using linux.
Having installed Kali Linux i keep getting the text mode display, a youtube tutorial shows that i need a display manager and how to set it up, but i can't run
sudo apt-get update
or
sudo apt-get install
gdm3 because i am not connected to the net ( a step i skipped while setting up due to ignorance).
Please how do i set up a WIFI connection or install a usb modem in text mode?
Thanks. I'm stuck at black n white
Try to enable the WiFi by running:
nmcli r wifi on
Just edit /etc/network/interfaces and write:
auto wlan0
iface wlan0 inet dhcp
wpa-ssid {ssid}
wpa-psk {password}
After that write and close file and use command:
sudo dhclient wlan0
Replace {ssid} and {password} with your respective WiFi SSID and password.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have been using ubuntu 20.04 recently and have a HP pavillion laptop with B&O speakers. However i am not able to hear any sound. though, Bluetooth is working fine.
I have tried many solutions such as :
*sudo apt purge timidity-daemon
*sudo alsa force-reload
*sudo apt install pavucontrol and running pavucontrol.
None of the solutions have worked for me yet.
EDIT:
Later I assumed it to be a kernel bug and say a solution using the following commands:
sudo add-apt-repository ppa:kaihengfeng/fix-lp1869819
sudo apt-get update
after that i have tried reinstalling pulseaudio. And now bluetooth devices just after getting connected are automatically disconnected, do not play any sound either.
The Temporary fix I found(Worked for me and all my friends).
Suspend your system then start again. Now the sound will work.
What worked for me immediately after all was
pulseaudio --start
sudo apt-get install pavucontrol
from https://www.maketecheasier.com/fix-no-sound-issue-ubuntu/
with no changes to the files in /etc/modprobe.d/
This is silly but After days of searching, upgrading from 18.04 to 20.04 then installing fresh 20.04 it still not solved,
which finally got solved by just
go to BIOS -> disable Internal Speakers -> apply changes -> Enable again -> Apply changes -> Exit.
Voila Problem is solved :) :) (Dell Latitude 3510)
Finally, after surfing a lot through the net and reading about options of alsa for NVIDIA aound controller I got the following solution
2 files are to be changed
/etc/modprobe.d/alsa-base.conf
/etc/modprobe.d/blacklist.conf
Changes in File 1.
open the file using root
add the following line to the bottom of the file options snd-hda-intel dmic_detect=0
save and exit the file
Changes in File 2.
open the file using root
add the following to the bottom of the line blacklist snd_soc_skl
save and exit the file.
Reboot and Enjoy with the restored sound!
I had the same issues. I would get no audio output, except for when I plugged an HDMI in which case I could redirect the sound to the HDMI device. I've tried all the previous answer and it didn't work for my case I have a Dell inspiron 9510 and had ubuntu 20.04 freshly installed.
I made all the different changes in the files
/etc/modprobe.d/blacklist.conf
/etc/modprobe.d/alsa-base.conf
this never worked for me. I've tried a lot of things, disable internal speakers in BIOS and such, still nothing. I've spent hours trying to fix this.
Finally I found this:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422
and this:
https://www.reddit.com/r/Dell/comments/husu3r/how_to_get_fully_working_audio_in_ubuntu_2004_on/
Basically what you got to do is to allow focal-proposed updates first:
Software & Updates > "Developer options" tab > check "pre-released updates" box.
From here you can already do a
sudo apt update && apt upgrade
Then you can install the linux-oem-20.04
sudo apt install linux-oem-20.04
This will install a new kernel (5.6.0-1036-oem) where sound as proper support apparently. Now just reboot you system and you should be good to go.
You can find more info on this on the links provided. Also the second link has additional steps but for me only the first one worked like a charm !
I hope this can help anyone here who is running into the same issue. If anyone has found another way I'd be also glad to hear it since using a linux-oem is not a completely satisfying method.
SOLVED!, following RolandBBerlin at:
https://forum.ubuntu-fr.org/viewtopic.php?id=2055691
I just installed an Acer Swift 3 (SF314-57) and encountered the same problem. This solved the Audio problems:
**Edit the file /etc/modprobe.d/alsa-base.conf** and add the following lines:
**options snd-hda-intel dmic_detect=0
options snd-hda-intel model=laptop-amic enable=yes**
The first line is to enable the speaker, the second for the internal microphone.
Works after rebooting
In case if you don't have any output and input devices on sound settings
just type on terminal the following command pulseaudio --start and try to turn on video or audio, but when you reboot your system you need to retype the command.
In my case it was the temporary solution.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Yesterday I tried to upgrade from ubuntu 16.04 to 17.10.
When I upgraded to 17.04 it went all good, no problem.
But when I installed 17.10 I deleted the obsolete packages when it asked me to, and it changed my standard gnome loader to some new one.
And now when I am at the window to select the user, I can't move my mouse or input anything from my keyboard, just my poweroff works.
I tried to unplug the adapter and plug it in to see if it just freezes, but it does not, it recognizes when I plug/unplug the charger, everything seems fine, but the keyboard and mouse.
I tried to run a different kernel, or run in recovery mode but when I boot it freezes in the process.
I'll assume that you're using a laptop because you mentioned charger.
There might be an option in the BIOS for Legacy USB support try enabling that.
I only suggested that because I had the same problem and when I removed all of the packages, my keyboard and mouse drivers got removed as well, so I had to switch that option so it worked. After you boot and login, you can download drivers again and than you can disable this option.
Alternatively you can try plugging in external USB keyboard and trying if it works.
P.S.: When I booted my PC to linux for the first time, none of my USB peripherals worked, so I had to use PS2 keyboard and mouse to navigate, but when I enabled that option in BIOS, I was able to use it normally.
Can you explain in more detail, how it "freezes" when you boot into recovery(I expect you calling CLI recovery)
EDIT:
you can try following these steps:
use alt+f2 and login into a separate terminal session
remove gnome with
sudo apt-get autoremove gnome-core gnome-shell gnome-session
update broken packages
sudo apt-get -f install
run it twice!
reinstall it
sudo apt-get install gnome-core gnome-shell gnome-session
reboot
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I have a raspberry pi laptop with a raspberry pi 3 running Jasmine, and was wondering if I could connect to it through SSH no matter what WiFi network the Raspberry pi was connected to.
Example: I leave my Pi Laptop at McDonald's, connected to their free WiFi, I then go home, and on my chromebook I SSH into my Pi Laptop.
And I need to do this without port forwarding since I don't have access to McDonalds WiFi settings or most other network's settings, so I can't port forward my Pi Laptop.
I was in your same shoes 4 years ago. I finally decided to use a VPN solution. The best and most reliable for me was Hamachi (now owned by logmein). It might still be free.
https://secure.logmein.com/labs/#HamachiforLinux
I haven't added any new system in a while but here were the commands I typed.
sudo wget https://secure.logmein.com/labs/logmein-hamachi_2.1.0.86-1_armel.deb
sudo apt-get update
sudo apt-get install --fix-missing lsb lsb-core
sudo dpkg --force-architecture --force-depends -i logmein-hamachi_2.1.0.86-1_armel.deb
sudo hamachi login
sudo hamachi join xxx-xxx-xxx yourkey
sudo hamachi go-online xxx-xxx-xxx
Also install and add hamachi on your computer.
Now if as long as your Pi and your computer have internet access you will be able to reach it.
I realize this post is old, but thought I might have some useful info.
To connect to multiple pis on different networks without port forwarding I use the service: https://www.remot3.it/web/index.html
You can make a free account on their website. Then, in the terminal of the pis, you can run the commands:
sudo apt-get update
sudo apt-get install connectd
sudo connectd
Then follow the steps in the installer and you can view and control all your devices (as long as they have a route to the internet, or even cellular). You can also follow this video once you have an account/the installer: https://www.youtube.com/watch?v=rfr5Ox17S6U
Full disclosure: I'm actually an intern at remote.it this summer, but I thought it might be useful for you.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have set up a Linux VM on Azure - Ubuntu Server 14.04 LTS.
My goal is to be able to do remote desktop connection from my Windows 10.
I'm a complete newbie with Linux and that's why I've been following this tutorial. Everything seems to work fine until the point where I need to create an "Standalone Endpoint". The interface has changed in Azure's portal. What I've done is create an Endpoint as the pic below, but when I try to click "Connect" the option is still disabled.
The 3389 port should be set in “Inbound security rules” which you could refer to Where is the EndPoint setting for VM in new Azure portal for details.
After setting the 3389 port you could follow commands below to install desktop and enable RDP connection in your linux VM.
Update your system and install desktop, I choose xfce4 instead.
sudo apt-get update
sudo apt-get install xfce4
Install xrdp and start it
sudo apt-get install xrdp
sudo /etc/init.d/xrdp start
Next add a user that you want to be able to use the Remote Desktop with, the “primech” bit is the username. You get prompted for some other user-type data.
sudo adduser primech
sudo adduser primech sudo
Open Remote Desktop Connection tool in your Windows 10, you could start it by typing command mstsc, and then input your ubuntu's public ip address and then click 'connect' button.
Then you could get the same dialog in your tutorial, just input the username primech and password. And then you are able to see the remote desktop now.
This is correct. RDP (port 3389) is a windows-specific capability. SSH is the default and only supported means of remotely connecting into a Linux VM on azure.
You might be able to configure VNC to run on the Linux box and create an endpoint (VNC uses port 59xx, with xx being the display number, e.g. 00 for :0) but I haven't tried this and not sure it's supported.
RDP (remote desktop) i believe is a Windows only feature. Linux VM doesn`t support this feature.
From my knowledge instead of RDP, you have the options of SSH into a linux VM with command line or use VNC for RDP like experience.