Denniske1976
Experienced Member
Hi guys,
I have a little issue with my SS2 (kinda hard to explain in good English, but at least we still have the photo's): I picked up another SS2 (and a very cool SS20 with 2 CPU's) after "that other SS2" seemed to have memory mapping problems. So now I had this one, obviously RTC battery was dead, so I fixed that. Weird thing I have now with this one is that (again, don't know if I'm explaining this right) boot works OK, until I get to the part after "loading vmunix" and getting to the login prompt, at that point the screen gets garbled:
Weird thing is, blindly typing in commands seems to work (of course the output is also rubbish)... so "ls -la" shows something (I also can't read), "reboot" show something (unreadable) and the system reboots and again all of the POST is OK and after "loading vmunix" and "uncompressing" the screen goes weird again, then I login as root (and I don't need a password for some reason but happy that way) and again "shutdown -h now" does stuff and I can turn the system off. I wanted to get into the system to find the host ID from the boot log (as it doesn't seem to be on the orange sticker with this system, there's just a number on it and nothing that looks like a host ID).
I'm using a serial connection (as I always do with SUN systems) and haven't seen this happening before, not on any of the Ultra's I have and not on the Fire v440 or SS20. I was thinking maybe the serial jumper (RS432 and not RS232?) but wouldn't I see weird stuff before getting to the Solaris part (at least I think it's Solaris, the SS20 I got has Aurora Linux on it but it has a password so I either have to reinstall that one or find a way to get to edit the password file).
Anyone here have an idea? Thanks in advance, Dennis
I have a little issue with my SS2 (kinda hard to explain in good English, but at least we still have the photo's): I picked up another SS2 (and a very cool SS20 with 2 CPU's) after "that other SS2" seemed to have memory mapping problems. So now I had this one, obviously RTC battery was dead, so I fixed that. Weird thing I have now with this one is that (again, don't know if I'm explaining this right) boot works OK, until I get to the part after "loading vmunix" and getting to the login prompt, at that point the screen gets garbled:
Weird thing is, blindly typing in commands seems to work (of course the output is also rubbish)... so "ls -la" shows something (I also can't read), "reboot" show something (unreadable) and the system reboots and again all of the POST is OK and after "loading vmunix" and "uncompressing" the screen goes weird again, then I login as root (and I don't need a password for some reason but happy that way) and again "shutdown -h now" does stuff and I can turn the system off. I wanted to get into the system to find the host ID from the boot log (as it doesn't seem to be on the orange sticker with this system, there's just a number on it and nothing that looks like a host ID).
I'm using a serial connection (as I always do with SUN systems) and haven't seen this happening before, not on any of the Ultra's I have and not on the Fire v440 or SS20. I was thinking maybe the serial jumper (RS432 and not RS232?) but wouldn't I see weird stuff before getting to the Solaris part (at least I think it's Solaris, the SS20 I got has Aurora Linux on it but it has a password so I either have to reinstall that one or find a way to get to edit the password file).
Anyone here have an idea? Thanks in advance, Dennis