mouse pointer moves in opposite direction
Pages: 1 2
John Rickman (71) 629 posts |
When the RISC OS desktop appears on my RPi3 the mouse pointer moves up when the mouse is moved down, and left when the mouse is moved right. |
John Williams (567) 768 posts |
You haven’t got the monitor upside-down and the screen rotated 180 degrees? Just a joke! |
John Rickman (71) 629 posts |
No, it reminds me of trying to ride one of those trick bicycles where the steering has been reversed. |
Andrew McCarthy (460) 126 posts |
Mouse behaviour thread … question is. How come? Does it go away if you were to use a vanilla RC15 build? |
John Rickman (71) 629 posts |
That thread describes a different problem of a “wandering” mouse. My mouse has no inclination to wander it just goes in the diametrical opposite direction to what it is told. If you turn your mouse horizontally through 180 degrees and use it you will get the same effect. |
mikko (3145) 120 posts |
No help to the OP but in light of what Andrew asks it’s worth noting I occasionally experience wandering mouse behaviour on a RPi3 with RC15. |
Jeffrey Lee (213) 6046 posts |
It sounds like (a) the CMOS settings are a bit funny (negative mouse step value), and (b) changes to the CMOS settings aren’t being saved. Are you still experiencing the problem described here where the machine is crashing on boot? (Or that lots of modules are showing as unplugged/dormant) Now that you’ve updated the ROM image (instead of using the RC15 ROM which would be incompatible with the latest firmware), you could try deleting the CMOS file, rebooting, and then re-saving it again in order to reset it. Or try holding down the delete key while you power on the system, which should have the same effect (the boot-time keyboard scan for CMOS reset, shift-boot, etc. is one of the new features in the latest Pi development ROM when compared to RC15) |
Andrew McCarthy (460) 126 posts |
Go with the last post above and try my suggestion of using the RC15 SD card image if you don’t succeed, as it contains everything you’ll need that includes the relevant firmware. If you try my suggestion first, back-up what you have so that you can return to it. ;-) |
Steve Pampling (1551) 7932 posts |
Since the latest Pi firmware as used on the Pi3 has what Jeffrey referred to as “a breaking change” then John wouldn’t succeed with the plain RC15 image and would actually require the use of one of the recent daily beta ROM images to start the machine. If, as hinted by Jeffrey above, there are currently modules not starting or some other error that is the avenue to follow. I’d suggest that Rick Murrays Harinezumi startup/logging utility would be handy at this point. |
Jeffrey Lee (213) 6046 posts |
Andrew’s suggesting using the full RC15 SD card image (i.e. ROM + firmware + filing system), not just the ROM image.
To me it sounded like the modules were unplugged or there’s a crash during ROM init (as John mentions in his original thread), so Harinezumi isn’t likely to help much. CMOS settings not being saved correctly will either be due to SDCMOS not working (module unplugged, module didn’t start due to crash during ROM init, or module refused to start due to not finding the CMOS file), or a broken Loader partition. |
John Rickman (71) 629 posts |
Thanks to everyone who has taken trouble to reply. There are three odditites. As the problems are relatively minor I will keep using it. |
Rob Andrews (112) 161 posts |
If you have a spare SDXC card write a new rc15 Image to it boot it to see if your problems go away. |
Jeffrey Lee (213) 6046 posts |
Double-check that (a) you have framebuffer_swap=0 in there (it sounds like your display is red/blue swapped, the framebuffer_swap option should fix that), and (b) the ‘x’ in ramfsaddr=0×508000 actually is a letter ‘x’ and not some other character (I think the forum has a habit of replacing it with a multiply symbol?). If in doubt, you can double-check most/all of the settings once the machine has booted via Get the values of all non-default (?) settings: *vcgencmd get_config int *vcgencmd get_config str Get the value of an individual setting: *vcgencmd get_config framebuffer_swap FWIW, the latest firmware + ROM appear to work correctly on my Pi 3.
Yes. I don’t think they’ve released any new hardware models in the last few months. |
Martin Avison (27) 1418 posts |
I don’t suppose you have a folder called !Territory in the root directory of your boot drive? If you have and it does not contain the right stuff that can be the effect you see. |
Andrew McCarthy (460) 126 posts |
You’ll need a Linux, RISC OS, Mac or Windows computer with an SD card reader ;-) and an SD card. Check here for further instructions. Video instructions for Windows here → How to install RISC OS on a Pi . Linux – Ubuntu (debian) has an iso image writer installed as default. Alternatively, you can get a standard SD card with RISC OS on it or an Epic SD card from the ROOL store. BTW when you copied !Boot to the SD card did you use the merge facility? |
Jeffrey Lee (213) 6046 posts |
Although, if you’re thinking of trying SDCreate then apparently there are a couple of issues which cause problems with using it to write SD card images for the Pi (1, 2). I should probably look into those at some point! |
John Rickman (71) 629 posts |
I don’t suppose you have a folder called !Territory in the root directory of your boot drive? No !Territory folder anywhere |
John Rickman (71) 629 posts |
Double-check that (a) you have framebuffer_swap=0 in there (it sounds like your display is red/blue swapped, the framebuffer_swap option should fix that), Thanks – that problem is now fixed (although I quite liked the purple Rasberry PI) |
John Rickman (71) 629 posts |
If in doubt, you can double-check most/all of the settings once the machine has booted via *vcgencmd get_config: *vcgencmd get_config int *vcgencmd get_config str |
John Williams (567) 768 posts |
The giant floppy icon is definitely a Territory problem. The territory setting is not being read from CMOS – it should be 1 for the UK – so the OS throws up the old “Insert a floppy disc with a Territory setting in it” icon from times long forgotten. This, with your mouse speed problems and other configuration issues, suggests that the problem is with the CMOS file reading or saving. Did you check the presence of the module SDCMOS as Jeffrey suggested earlier? |
John Rickman (71) 629 posts |
Did you check the presence of the module SDCMOS as Jeffrey suggested earlier? Yes SDCMOS is ROM 91 and Active |
David Pitt (3386) 1248 posts |
Wrong x, as Jeffrey suggested further up.
|
John Rickman (71) 629 posts |
You’ll need a Linux, RISC OS, Mac or Windows computer with an SD card reader ;-) and an SD card. No Mac, but otherwise yes, and will probably go with Linux as I have another Pi with Raspbian installed. |
John Williams (567) 768 posts |
So all this has been caused by a Textile misinterpretation of an x between two numbers being changed to a multiplication sign and copied from there? Could this have been avoided by using code tags, I wonder?
It appears so! A lesson for us all! Well-predicted Jeffrey, well-spotted David! PS And it even makes it correct in the RSS feed! |
John Rickman (71) 629 posts |
Wrong x, as Jeffrey suggested further up. Sorry – the difference between the Xs was too too subtle |
Pages: 1 2