It should be no problem. I use Debian on Pentium 120 computers dating from around 1992, and I have used a serial mouse in the past.You will probably have to set it up manually though, so you will need to do some googling.Incidentally, you might like to try Puppy linux. It is extremely compact, but you will still need to figure out how to get that mouse working.Is the kernel serial mouse driver module loaded?modprobe mouse_serial Mark.-- Mark Hobley,393 Quinton Road West,Quinton, BIRMINGHAM.B32 1QE.
DSL is then like an Atom Ant(remember the atom ant???). It works with my damn old computer at a very reasonable speed (Much faster than Windows 95 was !!!). The number of applications and extensions you can add to a fresh install is more than enough to enjoy working in your old computer. So we should all thank so much to everyone who did an effort to develop DSL!!!
damn small linux mouse not working
Due to infighting among the project's originators and main developers, DSL development seemed to be at a standstill for a long time, and the future of the project was uncertain, much to the dismay of many of the users.[1] On July 8, 2012, John Andrews (the original developer) announced that a new release was being developed. The DSL website, including the forums which were once inaccessible, were back, as well.[6] The first RC of the new 4.11 was released on August 3, 2012,[7] followed by a second one on September 26. The damnsmalllinux.org site was inaccessible again sometime in 2015 to February 2016. As of March 27, 2016, it was again accessible for some time,[8] but as of February 10, 2019 was inaccessible yet again. As of 2021 it was accessible.
I setup dsl linux which is only 50mb to boot of the fog pxe menu. Here is the link where I got the instructions =17156. This distro has Firefox and it boots pretty fast from pxe. DSL is based on knoppix linux. So, this could be used as a work around to access the fog console to send images if you do not have a working computer near by. This might be useful until there is a way to image through the pxe menu. Actually you might not need this feature now with this work around. Here is how I did it.
It might be interesting to try to get Damn Small Linux - Not! (DSL-N) working from a PXE boot as well, because it includes more hardware support and a 2.6 kernel. I will try to get this working when I have some time at work... please add notes here if you get this working! One of the biggest problems I have with DSL PXE boot is that the USB drivers for the systems I've tried DSL with aren't recognized, so I can't type or use the mouse Ericgearhart 13:04, 16 July 2009 (MST)
I downloaded dsl 2.1 and it worked fine on my old computer where everything is connected by PS2, by when I boot the OS on my new computer, which has everything connected by USB the linux doesn't work, and when going in to the Linux, the mouse and the keyboard isn't reponsive, and the only thing i can do it restart computer, i thought DSL 2.1 comes with USB support in defaulthelpMax,
(In reply to comment #20)>> "Due to this problem, none of my friends are using ubuntu. And my 10 cd set of> ubuntulinux has gone waste.They say that if a system cant detect even a mouse,> we wont use it."
I had this problem with Breezy (5.10) and it's still not fixed with Dapper RC (6.06).How is a novice user supposed to know what to do when their serial mouse doesn't work? Even if there is no working autodetect, at the very least there should be some way to manually configure a serial mouse during LiveCD startup. Other distributions have had this right for many years.
> Even if there is no working autodetect, at the very least there should> be some way to manually configure a serial mouse during LiveCD> startup. Other distributions have had this right for many years.
Well as I see it's quite an old bug, so I just want to say that today I wanted to try out my brand new, cool looking (sent from Canonical) Ubuntu 6.06 LTS CD ... I put it in, boot the system - I see the desktop and that's it - since my old Logitech serial mouse is NOT working, I'm not able to use the system. Ok. I'm quite advanced Linux user - I know that I can edit xorg.conf, or use some other console tools to configure the mouse. It's not so difficult - and I did it many times in old Slackwares;) But hey ... my Windows XP made no problems with that mouse - it just worked.
I think such small elements make the big picture of the whole system. Why "Joe User" doesn't like Linux? Mayby becouse he still (after so many years of development) needs to grab the console and cast some magic spells to make his mouse just work.
to follow up, I eventually got this working by runningmdetect -vI discovered that if mdetect finds nothing it defaults to intellimouse on psaux (on my mobo ymmv)replacing the mouse then gave me the output/dev/ttyS0microsoftwhich can be used to edit (copy old version first I ended up with no x at all once)/etc/X11/xorg.confhopefully this will help someone elsePS mdetect is now in dapper 6.06
I still bump into this bug regularly - there are a lot of old serial mice still in good working order, especially where I operate - NGO's and small businesses on the tip of Africa, where new hardware is a luxury.
Going on five years on this serial mouse bug, apparently little progress... today I was testing a PCChips M748LMRT mainboard, with AT keyboard, serial mouse, no PS/2 or USB. 384MB. Puppy Linux booted fine, with simple manual choice of serial mouse. The latest Ubuntu 9.04 was useless. Booted into destop GUI, mouse cursor, but no mouse response. No useful boot parameter help from LiveCD. Googling for Ubuntu serial mouse boot parameters also no help, just repeated obscure references to "mouse/device=/dev/ttyS1". No mention of the fact that this geekness actually refers to the second COM port, not the first. How can something so basic and simple be so complicated? Tried Knoppix 5.1.1 CD. Auto detected and configured the standard Microsoft Serial Mouse 2.0A just fine. Delving into the dmesg there revealed the proper /dev/ttyS0 reference. Of course, by then, I didn't need to know, since 2007 Knoppix Just Worked. Ubuntu is mostly great, but if Puppy starts converting to Ubuntu base and loses the special advantages, it will be a big loss for the linux LiveCD ecosystem. The more I experiment, the more I get the feeling Ubuntu does not really believe in LiveCD mode, just views it as a demo toy. For years, most of my Linux experience has been from LiveCD, from scratch, over and over. If it doesn't work well enough, I move on to another distro. Puppy is the only distro I have ever found that always properly supports my new 1360x768 Toshiba LCD TV -- another victory for simple manual selection. Ubuntu auto-supports the TV less than half the time, randomly -- mostly I get a mysterious no-video mode; and after months of struggle I have not yet found any secret cheatcode to make it always work. One gets tired of trying to use something that may need to be rebooted ten times before it starts properly. It would be a vast improvement if Ubuntu LiveCD offered an alternative Puppy-like simple manual start mode, just asking about mouse, keyboard, and video modes.
After this change, it's needed to restart HAL and Xorg.Maybe someone can do better and produce a new file... but at least my serial mouseit's working now! (sorry i posted the whole file before the solution :-P)
Yes, HAL is dropped in Lucid so the fdi file technique is not relevant anymore. Instead, we have incorporated an xorg.conf.d snippets system, whereby you will configure things like this by dropping a file with the serial mouse snippet (like the ones in comments #12 or #49) into your /etc/X11/xorg.conf.d/ directory. We figure that the fdi file syntax (and the udev syntax that replaced it in earlier versions of lucid) only served to make configuration more obtuse - while editing config files is not a pleasant way to get things working, at least the xorg.conf syntax is reasonably well known and documented pretty heavily on the internet.
Isn't this all the kernel issue, not Xorg one? IMHO the kernel should support the serial mice as it supports PS/2 mice.I tested my COM mouse on Windows, and when i press "search for new hardware" button, it just autodetects it. I don't even have to move the mouse. And, as i experimented with my mouse on linux, it gives some 55 bytes of (supposedly) identification data on power-on (or minicom 'initialize modem'). I looked into leaked WindNT sources and found that windows uses these (or similar) data to identify mouse.
And when installing Ubuntu we do not get a chance to configure it, unlike what some other distributions (Mandriva, PCLinuxOS etc) do: if they do not detect a PS2 or USB mouse, they go into mouse configuration, asking for port and interrupt, and then on to a mouse-testing page where you can move cursor, click right and left, before going back to the mouse config or exit once you have it working.
Hi,I am using ubuntu 12.04, my mouse is Ligitech wireless, it had been working fine suddenly the MMB no. 3 stoped working though scrolling works fine, it has three button right , left and middle with scrol , after checking few forums and the command " xev grep -i button " i figured out that if i tilt the scrol button to the right a bit and press then button no. 3 (MMB) works, any idea ? thanks.
On 16/12/13 15:11, Shams wrote:> I am using ubuntu 12.04, my mouse is Ligitech wireless, it had been working fine suddenly the MMB no. 3 stoped working though scrolling works fine, it has three button right , left and middle with scrol , after checking few forums and the command " xev grep -i button " i figured out that if i tilt the scrol button to the right a bit and press then button no. 3 (MMB) works, any idea ? thanks.
I checked Microsoft's App-V but it just virtualised the app not setting up a new standalone environment. I need a new environment with their own mouse pointer but needing very small RAM preferably just for running the bot and the app. 2ff7e9595c
Comments