NVRAM replaced in Sun Ultra 60, but no longer booting

I picked up a “new” (new old stock most likely since I don’t think these chips are still manufactured, and haven’t been for 10+ years) NVRAM timekeeper chip since the one in the Sun Ultra 60 I picked up cheap on ebay was dead. Luckily it seems to still have charge and is keeping the host id and mac address values between power off/on, so that’s great.

To reprogram the hostid and mac address that are stored in the NVRAM memory, following the guide here which seems to be the definite source for reprogramming Sun NVRAMs, I used the following steps to reconfigure the new chip. The value of 80 on line 2 is the machine type for Ultra models:

1 0 mkp
80 1 mkp
8 2 mkp
0 3 mkp
20 4 mkp
c0 5 mkp
ff 6 mkp
ee 7 mkp
0 8 mkp
0 9 mkp
0 a mkp
0 b mkp
c0 c mkp
ff d mkp
ee e mkp
0 f 0 do i idprom@ xor loop f mkp

The odd thing now is I’m running into this issue that I didn’t see before:


I’m not going to type in all this text so it’s searchable, but here’s the text for almost the same error (same issue, different version of Solaris perhaps?) :

Hardware watchdog enabled svc.configd: smf(5) database integrity check of:    
/etc/svc/repository.db
failed. The database might be damaged or a media error might have prevented it from being verified. Additional information useful to your service provider is in:
/etc/svc/volatile/db_errors
The system will not be able to boot until you have restored a working database. svc.startd(1M) will provide a sulogin(1M) prompt for recovery purposes. The command:
/lib/svc/bin/restore_repository
can be run to restore a backup version of your repository. See
http://sun.com/msg/SMF-8000-MY for more information.
Requesting System Maintenance Mode
svc.configd exited with status 102 (database initialization failure)

If I could get to a single user logon prompt then I could follow these instructions to repair, but the above error is just looping continuously, so I’m unable to do the repair.

When I first installed Solaris 10 from CDs, I got through the first couple of disks and then the cd drive would just eject any disk inserted, and won’t stay closed. I managed to complete the install by copying across ISO disk images and completing the install from those.

Since I can’t get a physical install cd to stay in the drive, I’m not sure I can boot recovery, so I’m kinda stuck. I think it’s time to pick up a replacement cdrom drive (might as well get a dvd drive) otherwise I’m kinda stuck in the water with this machine at this point.

cal-heatmap with more than 6 heatmap ranges

By default cal-heatmap supports 5 ranges of values for the heatmap colors, so this config:

[10,20,30,40]

will give you the ranges:

  • 0 to 10
  • 11 to 20
  • 21 to 30
  • 31 to 40
  • > 40 (the 5th range)

If you attempt to define more than 5 ranges, cells in the 6th range and above will just have a default background color. In my www.spotviz.info app I tried to create 6 ranges, so the darkest color is for > 6000. On 9/28 and 9/29 (and the other blank dates in October in the screenshot below) have values more than 6000 but are showing as the default color:

The config I had for this was:

legend : [10,100,2000,4000,6000]

The ranges I was expecting from this config was:

  • 0 to 10
  • 11 to 100,
  • 101 to 2000
  • 2001 to 4000
  • 4001 to 6000
  • > 6000

Changing this to 4 values configuring 5 ranges fixed this issue:

legend : [1000, 2000, 4000, 6000]

MacOS 10.15 Catalina fails to burn bootable cdroms from ISOs

Not likely to impact most people, but occasionally I use an external USB dvd burner to make bootable disks for installing various OSes on older computers.

Previously before Catalina I would right click an ISO and select “Burn Image to…’ and this would work as it has for the past several MacOS releases. Now though when I click this option the menu disappears and nothing happens. A tip here suggested to double click this iso to mount it, and then right click the mounted disk and select “Burn Image’. While this does work to burn to a blank cdrom, the disk is not bootable, it appears to only copy the files to the cdrom and not burn it as a bootable disk, even if the iso is from a bootable disk.

Reading through the above post on the Apple site, this sounds like a bug in Catalina and has been logged.