Logitech Wireless USB Keyboard + Mouse (Cordless Desktop EX110) prevents Haiku booting

[franxico]

I built Haiku (~hrev30800) from Linux and installed it in a partition, real hardware. I have a Vostro 410 Quad Core with SATA and no PS/2 ports. Haiku hangs at the rocket icon. Maybe ​http://dev.haiku-os.org/ticket/2253 related. I'm opening this ticket at mmlr's request.

[franxico]

last debug output page

[mmlr]

That's not the last page of output. It's just the last page that you could reach by pressing something. Please press "p" before getting there to disable paging and take another picture of the actual last page.

[franxico]

Following your instruction I discoverd that Haiku doesn't hang. Actually, it falls in a infinite (?) loop. The pictures dsc 1154 an 55 show the debug stage when the message "usb_disk: acquire_sem failed while waiting for data transfer" starts to repeat forever (I waited for ten minutes or so).

I have a card reader, but no cards were inserted. I have also an USB printer (HP Deskjet 5550).

[mmlr]

It's trapped in an interrupt storm. If you remove all USB hardware from the system, does it then boot? You should be able to simply connect the keyboard and mouse after the boot process. Can you then please enter KDL using the F12 key and post here what the "ints" command prints out?

[franxico]

YAY! It's the first time I could boot Haiku on this computer =D \o/ So yes, removing the Cordless Desktop and then connecting it after boot works, thanks! :)

I took two pictures. First, the 'int' command and second, the 'sc' command (don't know if it is useful).

[franxico]

Int

[franxico]

sc

[bga]

BTW, I do have a similar problem. If my printer is connected and tuirned on during boot, Haiku will not boot (I didn't investigate, but as this is a lock up and not a crash, I am prety sure it is the same problem as reported here.

[franxico]

Is there any other info I could give?

Otherwise, what can we do for the moment to avoid this problem (without having to disconnect the hardware)? Thanks

[mmlr]

Replying to franxico:

Is there any other info I could give?

Basically I would need access to a machine having that problem to really be able to investigate. Sadly all of my hardware (7 machines) do not exhibit that problem, so I'm pretty much clueless.

Otherwise, what can we do for the moment to avoid this problem (without having to disconnect the hardware)? Thanks

Not really. You could try flipping BIOS options. Usually stuff like this is related to legacy emulation. But as you stated your BIOS options are severely limited, so there's not too much you can do.

[scottmc]

Can you recheck this with a recent Haiku build? It may have been fixed recently.

[franxico]

If everybody is OK, maybe we could close this one and continue in #6041 ? BGA, do you still have the same problem? I don't have anymore my HP printer.