Debian Hardware :: USB Joystick Only Works When Reconnected It
Feb 8, 2010
USB joystick with Linux only works when I disconnected and reconnected its. I have a problem that it can easy, but I didn't find a solution yet. When I turn on my computer using a Debian or Ubuntu and tried to use the joystick the commands of joystick doesn't pass to SO. Once I disconnect and reconnect the joystick on USB port it pass to work.
Environment: SO: Debian 5.0 lsusb - executed this command before disconnect and reconnected the joystick result is equal:
1 I have XP installed on HDD1 (SATA 200 Gb master). Now I installed Cetos 5.5 (use 4.1 Gb DVD1) on the second drive, HDD2 (Seagate STA 40 Gb slave.) I didnt fund the option for selecting boot location during installation, just selected second drive. I think this is my first mistaking. The Centos can�t boot up after initial installation. I disconnected the HDD1 (XP drive.) Then finished Centos install. � Second mistaking.
2 After that Sentos installed, I reconnected HDD1 but XP is disappeared. The grub.cfg shows about XP as: Title other Rootnoverity (hd1,0) Chainloader +1
3 For finding XP I disconnected HDD2 (Sentos), but XP can�t be started. This message is shown up:
Just wait 5 seconds for normal startup! Boot: could not find kernel image:vmlinuz
4 I think that stuff was written by grub. I decided to get rid of them then reinstall all. I tried to deleted and create new partition, format c:, fixmbr, and fixboot, then install XP on c:. But above message still shows up when boot machine. I have to use XP install cd to start Windows XP.
I'm a network services rookie and I am seeing this error, but it doesn't seem to be effecting functionality. Nov 22 12:12:16 r01 nscd: nss_ldap: reconnected to LDAP server ldap://10.5.1.4 after 1 attempt This error is scattered through out my logs. We are authenticating this Red Hat server to another OpenLdap server. Everything seems to work just fine and we are not even using Kerberos as this is a render server. We set-up ldap right in the GUI, nothing fancy.
RHEL 5.4, Basic install, again, nothing fancy. LDAP does seem to be working fine and allows the right people to login to the machine. We have two of these machines running and both are configured exactly the same and getting the same errors.
I have the Joystick driver installed and it works in the FlightGear app. I need to calibrate it if possible. I found jsattach and jscal. I know it works like a Logitech Warrier. I don't know the device nomenclature. I connects to a USB port so I suspect it is a /dev/usbmon X with X = o thru 7. I don't know how to identify it.
I am running open suse 11.3 64 bit and am trying hard how to install the above mentioned joystick on my system. I am using a medion akoya laptop. 4 gig ram.
I just recently did a clean install of 10.10. My controller works fine for games no issues there. I haven't done any sort of configuring in order to make my Logitech cordless rubmble pad 2 controller work as a mouse yet it is. It just started this morning when I booted up. I have found many threads on how to make your controller/joystick work as a mouse. But I have yet to find one on how to get it to quit doing so. Or at least how to toggle it on and off which would be better in my case as Ive found in the past 30 min that I like scrolling with the analog stick much better than pgup/dn or the mouse wheel. The main issue is that I have a 4/yo here that plays games all the time and he keeps opening random things when he plays. I also am looking into how to get virtual box to let windows xp detect my controller but I will post that later after I have done more research if I can't figure it out.
I am using ubuntu 10.04 and have a problem it seems no matter what joystick I plug into ubuntu it wants to treat it like a mouse. I have no idea as to why this is but it is quite annoying. I searched the menu and have yet to find the ability to disable using the joystick as a mouse function.
I have an old Logitech Wingman analog joystick connected to a game port on a Creative sound card. At this point I've got the system to see the joystck and was able to run jscal. I was also able to run jstest. I was able to see positive & negative numbers moving the joystick in four directions. However, when I try 2 different MAME games or Open Arena there is no right direction. Pushing the joystick right only stops it from going left.. Up and down movement seems to be OK.
I'm using a "HuiJia USB Gamepad" to connect a standard N64 controller to my computer over USB. I'm doing this so that I can play games using mupen64plus, which uses the SDL to get input. My problem has to do with the way the adapter deals with C button events. Apparently, the u/d and l/r C buttons are treated by the adapter as joystick axes, so joystick events are generated by using them. But, for some reason, these events aren't recognized by SDL.
It gets stranger - if I cat the output of /dev/input/event5, the event gets printed when a C button is pressed. Furthermore, when I configure SDL to use the /dev/input/event* devices rather than /dev/input/js0, the C buttons are recognized! (Though, this leads to a situation where the joystick can't be calibrated... go figure). So, I can either have a correctly calibrated joystick with no C buttons or a miscalibrated joystick with working C buttons. Does anyone have any idea what I can do about this situation? The best outcome would be to force the C button joystick events to appear when using /dev/input/js0. Device as it appears in the output of lsusb:
Currently I have 5 HID's I would like to use on the system at any given time. However, I have the problem of them using different device paths depending on what order I plug them in... Which wreaks havoc on qjoypad and also my music software which looks for a specific device number, which may or may not be the same as it was last time.
For example, I have 2 rock band drum controllers which I use to send MIDI signals. I need them always assigned to the same device path, so that I don't have to change the settings in my music software every time I run it, to make sure it's looking at the right controller
Or if I am going to play games with a gamepad, but I also have the drums hooked up, the gamepad may be assigned to /dev/input/js2, so I create my qjoypad profile.... Let's say the next day I reboot with the drums not plugged in, the gamepad is now /dev/input/js0, and the qjoypad profile won't work because it is looking for that gamepad at /dev/input/js2... So I would either have to create a new profile, or hook the drums back up in the same order ... Or something
It's just a mess...
Is there any way to tell Ubuntu to say "/dev/input/js0 is always Playstation gamepad", "/dev/input/js1 is always drum pad 1", etc.?
Or some way to do away with /dev/input scheme altogether and somehow link directly to the name of the device?
I'm looking for a way to use my PS3 remote as a configurable tool (mouse andor joystick) for my computer. This site doesn't work at all: https://help.ubuntu.com/community/Sixaxis
I was looking at the Canon CanoScan 8800F and the SANE website says that it works. Does anybody here have this scanner and does it work as it should?I would be using it to scan photos, slides and negatives. Perhaps somebody can recommend a different one?
We have a GPS receiver connected to COM2/ttyAM1. It works on 2.26.21, but not on 2.6.29. It's settings are 4800 8N1, and stty gives 'the same' flags. Appears to work ok with minicom, but we cannot write to the GPS receiver on 2.6.29, and we get "ttyAM1: input overrun" during prolonged use reading NMEA strings from it. It's fine on 2.6.21. What is telling is this:
Start reading NMEA strings via minicom, no overruns. Start a user space process then that writes a little to SD, pdflush becomes more active, then blam, overruns /dev/ttyAM1 @ 4800 baud, and no overruns on /dev/ttyAM0 @ 115200 baud. How can that be?! Is pdflush using IRQ5 or competing with us for some other resource?
I have a Clear 4G+ Mobile USB modem. It is a Sierra Wireless Air Card 250u. I was able to get a brief 3G connection out of the box, with Squeeze 6.0. I would be happy to at least get connection manager working, as it does in Windows XP.
Subsequent edit. I did a clean install of 6.0 Squeeze, and Clear USB modum worked right out of the box. All I had to do was, right click on Network Manager icon on upper right corner of screen, checked enable mobile broadband. clicked on edit connection info. There I manually entered Clear as my provider, checked on connect auto, and left other fields blank or default settings. I still only get 3G, but I have multiple barriers to a microwave signal in my location. But I still will continue and may need help as I configure Clears Connection Manager, and or firmware.
url
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 005: ID 198f:0220 Beceem Communications Inc. Bus 001 Device 004: ID 1199:0301 Sierra Wireless, Inc. Bus 001 Device 002: ID 0424:2512 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 roo
I am guessing I would have to locate firmware to make this device work in linux.
I just setup a debian OS(in emulator) and trying to use apt-get update. When I log in as root and do:
export http_proxy=http://proxy.com:9090 apt-get update works
If I use another user and ssh to this debian, sudo apt-get update will fail to work because it don't use the proxy. I try to do the export http_proxy stuff again but still not working. echo $http_proxy showing it already set correctly...
p/s: I have a workaround by adding this lines in the apt.conf ACQUIRE { http::proxy "http://proxy.com:9090" }
but I really don't want this solutions because I want to easily disable the http_proxy in command prompt (by unset it).
Code: Select all      require "fileinto";   if header :contains "subject" ["beispiel"] {    fileinto "beispielordner";   } else {    # The rest goes into INBOX    # default is "implicit keep", we do it explicitly here    keep;   }    I can see no errors in dovecot.log, -info.log, -debug.log but also no sieve messages
Code:
Select all  #/etc/dovecot/conf.d/15-lda.conf   protocol lda {       postmaster_address = julius@localhost       mail_plugins = $mail_plugins sieve
After to install Debian Sid, i can't to connect to my network. When i launch lsmod, ath9k is present so the module is enabled.I don't use network-manager-gnome, wicd and other, i modify myself /etc/network/interface. But even with this configuration, the wifi does not works.
I'm using the stock nouveau driver that ships with Jessie, and loads by default. I installed this card during my botched attempt to upgrade from Wheezy. This is a fresh install, and DPMS isn't working right.
I can run "xset dpms force off", and the screens will blank. I even see the "HDMI signal lost" screen of both (identical) monitors. However, before the power LEDs of either monitor go orange (instead of blue) the screens come back on as if I had made mouse or keyboard input. If I've locked the screen with xscreensaver, the screens are blank (I use only the blank hack). I've forgone the use of xscreensaver for now, believing it to be contributing to the problem. If I run "xset dpms force off" now, the screens blank, but the "HDMI signal lost" screen doesn't show, and the screens immediately unblank.
Here's the output of "xset q":
Code: Select allxset q                                                                                              Keyboard Control:  auto repeat: on  key click percent: 0  LED mask: 00000000  XKB indicators:   00: Caps Lock:  off  01: Num Lock:  off  02: Scroll Lock: off   03: Compose:   off  04: Kana:    off  05: Sleep:    off
[Code] ...
It's like something is preventing the screen from going blank, but I don't know what it could be.
I installed the proprietary nvidia driver. Sadly, it does the same thing, so that's one thing I can cross off as the likely culprit.
Ran this command:
Code: Select allxset dpms 0 0 0
So when "xset dpms force off" is called, it powers down the monitor immediately. I will be reverting back to nouveau, and will report whether the problem resurfaces.
I recently got my USB microphone working with Audacity under: Debian 3.16.7-ckt20-1+deb8u1 (2015-12-14) i686 GNU/Linux.What I'd like to do is use that same microphone at the following Google/Chrome link in order to convert speech to text (mostly for the purposes of automating my note-taking process.): url...But the the microphone is never recognized, so nothing happens.(And, BTW, the same microphone works fine on that same link/site when I'm using my Windoze box instead of the Linux machine.)
Here's further information: My mic (from lsusb) - Bus 005 Device 003: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio Controller
