trackball is too clicky

Does booting with 'psmouse.proto=bare' help at all?

I typed...

  live psmouse.proto=bare

... at the (LILO?) boot prompt.

Trackball is still just as clicky as before.

This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.

This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.

If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).

Thanks for your help.

Trackball is just as clicky in Breezy. Since the bug is in still in state
UNCONFIRMED even though the comment talks about NEEDSINFO I don't know what to
do to keep it from being closed.

If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.

Let me know if this bug still exists with this kernel.

Unforturnately Flight CD 2 doesn't even boot on this system, so the answer to
your question is undefined :-(.

A short time into the boot I get a black screen with only the following line of
text at the top:
"
[127.487976] BUG: soft lockup detected on CPU#0!
"
Then nothing happens.

(In reply to comment #6)
> Unforturnately Flight CD 2 doesn't even boot on this system, so the answer to
> your question is undefined :-(.
>
> A short time into the boot I get a black screen with only the following line of
> text at the top:
> "
> [127.487976] BUG: soft lockup detected on CPU#0!
> "
> Then nothing happens.

This is booting just the installer or livecd? Which arch is this?

LiveCD, Dapper Flight CD 2, PowerPC, tried both "live" and "live-powerpc" (are
they the same?), same result.

This is on a blue / white 400MHz ppc Macintosh.

(In reply to comment #8)
> LiveCD, Dapper Flight CD 2, PowerPC, tried both "live" and "live-powerpc" (are
> they the same?), same result.
>
> This is on a blue / white 400MHz ppc Macintosh.

Ok, can you give me more context to the error? There should be a trace or
something around it. Even a digital photo of the screen would be fine.

My desktop is a grey G4 ppc, so this error is really surprising.

No trace, no nothing, only that one line of text at the top of an otherwise
entirely black screen.

I'll try to get you a photo of it though.

Ok, try booting with "live debug" and see if you get any extra output.

Thanks

Created an attachment (id=5468)
Almost unreadable photo of screen with more data

Booting with "live debug" actually did get me a lot more data. After a long
while (and two kernel BUG messages) I even got to a prompt! Just a prompt, no
network access or any LiveCD thing, but so far so good. It scares me a bit
that the system keeps on running after doing the BUG() thingy.

I know the attached screenshot is almost unreadable, so I'm not saying "here
you go, please fix now". My cell phone's camera isn't better than that
unforturnately.

What I'd* really* like to do is to get you the full output from "dmesg". Any
idea how to do that? AFAICT my only options are to write to the HD and then
e-mail it from MacOS9, or to somehow get a network connection up. That machine
has neither any floppy drive nor any CD writer (or printer).

Can Linux (as in "Dapper Flight CD 2") reliably write to whatever file system
is used by MacOS9? Or do you have any ideas what modules I should try to load
to get the network up?

My fallback plan is to write the complete BUG() message down on a piece of dead
tree, but I'd rather avoid that if at all possible...

Flight CD 4 boots fine, which is good. The trackball is still just as clicky as before though.

Haven't tried FCD5 yet.

I've confirmed that this is still an issue on the live Dapper FCD4. If you need more information than this, please ask and put this back in NEEDINFO.

I set this to UNCONFIRMED, don't know if that's correct.

Is there any way you could test this one more time with Dapper 6.06.1 or Edgy Beta 1 so we could update the status on this bug.

Unforturnately not, the hardware has recently been scrapped.

This looks like a dead-end report.

I'd say we should give it a while, just in case somebody with this hardware match cares to test some more.

After a few weeks it might as well be scrapped.

nothing new in this report.

Can it be closed?

Sure.

Closing bug as "Invalid" after having been mostly ignored for two years :-p.

There should be some other closed status than "Invalid" and "Fix Released", since neither of them makes any sense for this bug.