From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Apple Message framework v1084) From: Daniel Lyons In-Reply-To: <1B92247E-7395-4001-B962-182457A7B4D3@9srv.net> Date: Fri, 6 May 2011 07:36:31 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <0EE887DB-FE5A-4D8E-9375-6BB6136A46FD@storytotell.org> References: <2FFCB958-CD20-4E6B-9164-AA5DEADD866E@storytotell.org> <1B92247E-7395-4001-B962-182457A7B4D3@9srv.net> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Parallels 5 Topicbox-Message-UUID: deaa82b0-ead6-11e9-9d60-3106f5b1d025 On May 6, 2011, at 1:36 AM, Anthony Sorace wrote: > I have a VM that I created under Parallels 5 and am currently running = under 6. It's several months old. I seem to have gotten my version numbers mixed up. It's Parallels 6 over = here as well. >> 1. ps2intellimouse: scrolling works if you're scrolling down, but if = you make the scroll up gesture, the mouse skitters off to the right and = really doesn't scroll back up. Anyone seen this or have a tricky = solution? >=20 > I saw this for the first time today. In my case, scrolling up *also* = creates occasional b2 presses. Weird. I haven't used the GUI on = Parallels much for two years, so I can't help with when it was = introduced. >=20 >> 2. Ethernet card is not detected. I am not 100% sure there's nothing = different in the configuration, but I've made the plan9.ini look the = same in both VMs and still it fails to detect the NE2000 emulated = ethernet card. There are also ominous messages about usbd: no hub during = bootup that don't happen under the old one. >=20 > Ethernet works here (and did under Parallels 5, as well), and I've got = nothing in plan9.ini to trick it. You don't see the device at all (not = just no data or whatnot)? There's no /net/ether0, so I can't run ip/ipconfig to get any further. >> Is there a boot log somewhere I can examine for messages I may not = have seen, or any other debugging information I can go looking for? >=20 > /dev/kmesg will give you the console prints so far; /dev/kprint will = wait for new ones (and prevent them going to your actual console). I don't see anything interesting there, except that it couldn't = initialize usbd. Does usbd work for you? =97=20 Daniel Lyons