Hi
I use Nitpicker with dope applications. Sometimes, mouse cursor becomes mad: it goes from right to the left or up to the down. On serial console, I get the following message :
nitpicke| serio: i8042 AUX port at 0x60,0x64 irq 12 nitpicke| serio: i8042 KBD port at 0x60,0x64 irq 1 ... nitpicke| connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 nitpicke| connect "AT Raw Set 2 keyboard", isa0060/serio0/input0 nitpicke| connect "PC Speaker", isa0061/input0 nitpicke| connect "L4 input event injector", l4/sys ... nitpicke| psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronizati nitpicke: on, throwing 3 bytes away.
fiasco is started with -serial_esc option. I tried to modify ACPI parameters into bios, but nothing changed. On google, I've found that noacpi should be used but this option is not available into l4input. I also tried to change mouse. With a linux live cd configuration works perfectly.
Have you got any idea about this problem ? Driver should be updated (I use current svn version) ? Something else wrong into my configuration ?
Regards Marc
Hi Marc,
On Fri, Nov 02, 2007 at 07:50:29PM +0100, Marc CHALAND wrote:
I use Nitpicker with dope applications. Sometimes, mouse cursor becomes mad: it goes from right to the left or up to the down. On serial console, I get the following message :
[...]
nitpicke| psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronizati nitpicke: on, throwing 3 bytes away.
Did you start L4Linux too? I only got this kind of problems because of additional PS/2 port drivers in L4Linux. I think a complete Fiasco bootlog and L4Linux configuration file may help to expose the culprit.
BTW: Does our demo CD from http://demo.tudos.org/ suffer from the same problem?
Greets
2007/11/5, Christian Helmuth ch12@os.inf.tu-dresden.de:
Hi Marc,
Hi
Did you start L4Linux too?
I don't start L4Linux.
I think a complete Fiasco bootlog and L4Linux configuration file may help to expose the culprit.
I joined bootlog as attachment.
BTW: Does our demo CD from http://demo.tudos.org/ suffer from the same problem?
Yes, it happens less often but it happens. On demo CD, events is not used as I use it. I tried without events but same problems happens too.
On demo CD, I see: vbeset 0x117 323c46. What does mean second parameter ?
Regards Marc
Hey,
On Mon, Nov 05, 2007 at 01:02:54PM +0100, Marc CHALAND wrote:
BTW: Does our demo CD from http://demo.tudos.org/ suffer from the same problem?
Yes, it happens less often but it happens. On demo CD, events is not used as I use it. I tried without events but same problems happens too.
I think your recent super-duper mouse is not well supported by the used Linux 2.6.11 input drivers, sorry. I skimmed through a diff against 2.6.23 and there changed a lot. So, backporting the fixups is no option.
You could try to checkout and run l4/pkg/usbhid and plug your mouse into any USB port. Usbhid should also be on the demo CD.
On demo CD, I see: vbeset 0x117 323c46. What does mean second parameter ?
IIRC the second parameter is the initial framebuffer fill color to prevent flickering to black during boot ;)
Ciao
2007/11/6, Christian Helmuth ch12@os.inf.tu-dresden.de:
I think your recent super-duper mouse is not well supported by the used Linux 2.6.11 input drivers, sorry. I skimmed through a diff against 2.6.23 and there changed a lot. So, backporting the fixups is no option.
Yes, I've seen.
You could try to checkout and run l4/pkg/usbhid and plug your mouse into any USB port. Usbhid should also be on the demo CD.
I see it on demo CD, but not on svn. Is there something to do ?
Marc
2007/11/6, Christian Helmuth ch12@os.inf.tu-dresden.de:
I think your recent super-duper mouse is not well supported by the used Linux 2.6.11 input drivers, sorry. I skimmed through a diff against 2.6.23 and there changed a lot. So, backporting the fixups is no option.
Yes, I've seen.
You could try to checkout and run l4/pkg/usbhid and plug your mouse into any USB port. Usbhid should also be on the demo CD.
I see it on demo CD, but not on svn. Is there something to do ?
Marc
Hi,
sorry for the delay ;)
On Wed, Nov 07, 2007 at 10:02:12AM +0100, Marc CHALAND wrote:
You could try to checkout and run l4/pkg/usbhid and plug your mouse into any USB port. Usbhid should also be on the demo CD.
I see it on demo CD, but not on svn. Is there something to do ?
The package was missing from our remotely available SVN repository, but Adam added it today (will be available tomorrow). For a first test you could download http://os.inf.tu-dresden.de/~ch12/sub/usbhid-20071107.tar.gz, unpack it into your l4/pkg directory and build it.
Good luck
2007/11/7, Christian Helmuth ch12@os.inf.tu-dresden.de:
sorry for the delay ;)
No problem :). sometimes, I make mistakes with my mailbox :/. I've found a mouse which perfectly works ;).
The package was missing from our remotely available SVN repository, but Adam added it today (will be available tomorrow). For a first test you could download http://os.inf.tu-dresden.de/~ch12/sub/usbhid-20071107.tar.gz, unpack it into your l4/pkg directory and build it.
Thank you. I've built it and it works fine with a... PS/2 mouse. Is there an explanation ???
I've found a little typo into one log of l4io : Index: server/src/res.c =================================================================== --- server/src/res.c (revision 235) +++ server/src/res.c (working copy) @@ -410,7 +410,7 @@ if (err || !dw1) Panic("sigma0 request for I/O ports [%04x,%04x) failed (err=%d dw1=%ld)\n", regions[i].fpage.iofp.iopage, - regions[i].fpage.iofp.iopage + regions[i].fpage.iofp.iosize, + regions[i].fpage.iofp.iopage + (1 << regions[i].fpage.iofp.iosize) - 1, err, dw1); }
Cheers,
On Wed, Nov 07, 2007 at 03:09:24PM +0100, Marc CHALAND wrote:
I've found a mouse which perfectly works ;).
So, you use a working PS/2 mouse now?
The package was missing from our remotely available SVN repository, but Adam added it today (will be available tomorrow). For a first test you could download http://os.inf.tu-dresden.de/~ch12/sub/usbhid-20071107.tar.gz, unpack it into your l4/pkg directory and build it.
Thank you. I've built it and it works fine with a... PS/2 mouse. Is there an explanation ???
Ehm, for us here usbhid successfully drives at least OHCI and UHCI host controllers and connected USB HID devices, e.g., a USB mouse. Does this work for you too?
I've found a little typo into one log of l4io : Index: server/src/res.c =================================================================== --- server/src/res.c (revision 235) +++ server/src/res.c (working copy) @@ -410,7 +410,7 @@ if (err || !dw1) Panic("sigma0 request for I/O ports [%04x,%04x) failed (err=%d dw1=%ld)\n", regions[i].fpage.iofp.iopage,
regions[i].fpage.iofp.iopage + regions[i].fpage.iofp.iosize,
regions[i].fpage.iofp.iopage + (1 <<regions[i].fpage.iofp.iosize) - 1, err, dw1); }
Thanks
2007/11/7, Christian Helmuth ch12@os.inf.tu-dresden.de:
On Wed, Nov 07, 2007 at 03:09:24PM +0100, Marc CHALAND wrote:
I've found a mouse which perfectly works ;).
So, you use a working PS/2 mouse now?
Yes, I've got 3 mice : - one PS/2 which works - one PS/2 which looses sync without usbhid task, but works perfectly when usbhid task is started - one USB mouse which works (with usbhid of course).
Ehm, for us here usbhid successfully drives at least OHCI and UHCI host controllers and connected USB HID devices, e.g., a USB mouse. Does this work for you too?
Yes. The mystery is why PS/2 mouse works when usbhid is started ?
Regards Marc
Marc CHALAND l4@marc-chaland.net:
- one PS/2 which looses sync without usbhid task, but works perfectly
when usbhid task is started
Sorry, this info is not right. After some testing, sync is also lost but very less often than without usbhid task.
Regards Marc
Hi,
On Wed, Nov 07, 2007 at 06:21:50PM +0100, Marc CHALAND wrote:
Marc CHALAND l4@marc-chaland.net:
- one PS/2 which looses sync without usbhid task, but works perfectly
when usbhid task is started
Sorry, this info is not right. After some testing, sync is also lost but very less often than without usbhid task.
Hm, sounds strange... maybe your BIOS's USB legacy support interferes with the PS/2 mouse - just a guess.
Happy testing ;)
Hi
Christian Helmuth ch12@os.inf.tu-dresden.de:
Hm, sounds strange... maybe your BIOS's USB legacy support interferes with the PS/2 mouse - just a guess.
Even with USB legacy disabled, this happens. But now, I am not blocked. I think usbhid should be used as most of recent hardware use USB keyboard and mouse.
Regards Marc
l4-hackers@os.inf.tu-dresden.de
-
Christian Helmuth -
Marc CHALAND -
Marc CHALAND