LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 07-07-2012, 03:27 PM   #1
unclejed613
Member
 
Registered: Mar 2009
Posts: 322

Rep: Reputation: 26
armedslack in qemu has no mouse


i'm running armedslack 13.37 in qemu. host os is slack 13.37, and qemu is 1.0,1 installed by sbopkg. installed armedslack per the instructions on armedslack.org, and chose the usb mouse in the installer, after my first install attempt failed with the same problem, no mouse, with the ps2 mouse selected during install. if i add -usbdevice mouse to the start script (disk_launch) qemu can't read the disk image (???). anybody run across this before????
 
Old 07-08-2012, 03:45 AM   #2
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 153

Rep: Reputation: 122Reputation: 122
Quote:
Originally Posted by unclejed613 View Post
i'm running armedslack 13.37 in qemu. host os is slack 13.37, and qemu is 1.0,1 installed by sbopkg. installed armedslack per the instructions on armedslack.org, and chose the usb mouse in the installer, after my first install attempt failed with the same problem, no mouse, with the ps2 mouse selected during install.
There was a time when the USB mouse didn't work in QEMU with the Versatile platform. However, I've just looked at the setup.mouse script and I have noticed that whether you set a USB or PS2 mouse, the mouse is configured as "PS2". I don't recall whether that's a deliberate choice or a bug - probably deliberate as I recall there being fluctuation around mouse device names when I was patching that script-- however it works fine in -current and it does mean you chose the right mouse which ever option you chose ;-)

Where doesn't the mouse work? on the console? Did you select gpm to start upon boot? Try sh /etc/rc.d/rc.gpm restart

If it's inside of X11 then I'm not sure - The xorg conf for Versatile just uses /dev/mouse - so if that's setup correctly then it ought to work.

Quote:
Originally Posted by unclejed613 View Post
if i add -usbdevice mouse to the start script (disk_launch) qemu can't read the disk image (???). anybody run across this before????
You shouldn't need to do that, but you've most likely mangled the command line for qemu. Try removing that line and see if restarting gpm works.
 
Old 07-08-2012, 09:10 AM   #3
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 153

Rep: Reputation: 122Reputation: 122
Quote:
Originally Posted by drmozes View Post

You shouldn't need to do that, but you've most likely mangled the command line for qemu. Try removing that line and see if restarting gpm works.
I did a test install of 13.37 and the mouse at the console (using gpm) and inside X works fine.

My guess is that you did not start gpm. You can always reconfigure the mouse setting and make gpm start upon boot by running /var/log/setup/setup.mouse
 
Old 07-08-2012, 04:51 PM   #4
unclejed613
Member
 
Registered: Mar 2009
Posts: 322

Original Poster
Rep: Reputation: 26
tnx, but trying both of the above didn't work. i did however, do some more digging and found out what the problem was. there were errors in messages saying that the 3.4.4-versatile kernel modules could not be found. i was using the kernel images from here: http://armed.slackware.com/fixes/versatile/ but had not installed the fixed kernel modules. so i did this after booting the qemu image:
Code:
wget http://armed.slackware.com/fixes/versatile/slackware/a/kernel-modules-versatile-3.4.4_versatile-arm-1.tgz
installpkg kernel-modules-versatile-3.4.4_versatile-arm-1.tgz
and rebooted the image. after this gpm works (i didn't have a text mode cursor before, but i do now), as well as having a working mouse in X.
 
Old 07-09-2012, 02:33 AM   #5
drmozes
Slackware Contributor
 
Registered: Apr 2008
Location: Surrey, England
Distribution: Slackware
Posts: 153

Rep: Reputation: 122Reputation: 122
Quote:
Originally Posted by unclejed613 View Post
problem was. there were errors in messages saying that the 3.4.4-versatile kernel modules could not be found. i was using the kernel images from here: http://armed.slackware.com/fixes/versatile/ but had not installed the fixed kernel modules. so i did this after booting the qemu image:
Code:
wget http://armed.slackware.com/fixes/versatile/slackware/a/kernel-modules-versatile-3.4.4_versatile-arm-1.tgz
installpkg kernel-modules-versatile-3.4.4_versatile-arm-1.tgz
These kernels and modules are for -current, not 13.37. If you download and install 13.37 from the armedslack-13.37 tree, it works perfectly.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ARMedSlack and Raspberry Pi? blue_k Slackware 240 06-02-2013 07:32 PM
LXer: Set up qemu-kvm-1.0+noroms as spice enabled qemu server vs qemu-kvm-spice on Ubuntu Precise LXer Syndicated Linux News 0 05-26-2012 07:41 AM
armedslack 13.37 tmfizzle Slackware 3 05-17-2011 09:56 AM
Photoshop in qemu-kvm mouse problem Linux.tar.gz Linux - Virtualization and Cloud 5 10-25-2010 04:58 AM
Qemu, vnc, mouse position problem AzeriTillDeath Linux - Virtualization and Cloud 3 11-27-2009 09:30 AM


All times are GMT -5. The time now is 03:23 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration