yet another se/30 problem thread.

M

mmmlinux

Well-known member

• Apr 21, 2024

• #1

I have an se/30 that will chime show a gray screen but no mouse cursor. it has been recapped, and I checked all connections from the ADB chip and they are good. Any idea of where I should look next? Is there a good sequence list somewhere of the order it tries to check things during boot? Also, are replacement ADB chips available or some modern clone?

 

unity

Well-known member

• Apr 21, 2024

• #2

That can be a ROM issue. If there is a bit of non moving static on the screen then it could also be RAM. If things are working properly, the cursor will always appear even if the ADB hardware is damaged, its just that the cursor will not move.

 

M

mmmlinux

Well-known member

• Apr 22, 2024

• #3

No static, nice solid screen. I’ll try swapping in a rominator II from a different machine and report back.

 

M

mmmlinux

Well-known member

• Apr 22, 2024

• #4

No difference with replacement rom. Just a static screen. I did notice two clicks after the chime. Just like small speaker pops. I beeped out all the rom pins to the pds slot. But I’m going to check the cpu pins too to make sure.

 

unity

Well-known member

• Apr 22, 2024

• #5

Hard to tell, but the screen looks ultra wide. Could the cursor be off-screen? Are you booting with anything connected internally, like floppy or HD? I would suggest not if you are. Have any other ROMs on hand you can swap with? IIfx for example - just to rule it out but if it pins out good I kinda dont think the ROM is the issue.

 

M

mmmlinux

Well-known member

• Apr 22, 2024

• #6

I guess that an interesting point. I’ll try adjusting down the screen width to see if it’s just hiding. I swapped with a rominator ii and it was the same. Happy chime and then this. No hdd or fdd connected.

 

bibilit

Well-known member

• Apr 22, 2024

• #7

Can be an issue with UF8 LS166.

 

M

mmmlinux

Well-known member

• Apr 23, 2024

• #8

Shrunk the image, cursor definately not hiding. I have also noticed that if i press the debug button i get dumped to a sad mac with 0000000F 0000000D. Ill take a look at UF8 and the LS166 next to it next.

 

DemagnetizedMedia

Member

• Apr 24, 2024

• #9

Every mac will throw up 0000000F 0000000D when you press the interrupt button during startup since the debugger isn't available.

 

M

mmmlinux

Well-known member

• Apr 24, 2024

• #10

Yeah, but it does at least do stuff and draw the screen properly and clearly. ordered some new chips to replace those guys suggested. ill report back when i get them in and get around to swapping them.

 

DemagnetizedMedia

Member

• Apr 24, 2024

• #11

Sounds good, you might want to fiddle with the ram as well. Usually when you boot these macs it does quick a self-ram-check (the mouse isn't present when this happens). It may be getting stuck in the ram check for some reason.

 

M

mmmlinux

Well-known member

• Apr 24, 2024

• #12

I thought that was before the chime, but thats a fair point I have other ram I can try. although it also gets stuck the same on my rominator which I believe skips the ram check.