Search results

Mine's a slightly newer SyncMaster T200HD -- which is basically a TV and is fine for my PPC machines with later VGA and DVI but seems to lack coverage for graphics modes of the early Macs.

This startup circuit is relatively straightforward but prone to so many failures. After recapping a badly electrolyte-scarred board, I had a situation where things worked but the machine was left connected to power but soft-shut-down for a day or so, it would refuse to soft-start. I replaced...

I too have a non-functional Iici cache card that I'm debugging. Same failure mode at boot. It's SRAM chips are: CY7C128A-20VC 2kx8 24-pin TAG SRAM MT5C6408DJ-15 8kx8 28-pin SRAM I also have a good cache card which uses: MT5C1608DJ-20 2kx8 24-pin TAG SRAM CY7C185A-25VC 8kx8 28-pin SRAM...

I’m glad your machine checks out. There may be a dependency on the tantalums used. For the record, my misbehaving cap was a Kemet from Digikey - here’s the part info:

Oh .. and here's a recent 68kMLA post about how a reverse-polarized C22 indeed results in modem and printer port failure: https://68kmla.org/bb/index.php?threads/lc-iii-modem-port.42380/

I got the original TDK PSU back in operation; blown fuse, switching FET, current sensing resistor and opto-coupler. Here's a link to a post that includes a mostly correct schematic for the 699-0153 model which was close enough to my 699-0003 unit...

Before I flipped this cap, I measured a load of just about 0.5A on the -5V rail before the PSU tripped. After flipping, I see only 10mA. So, >0.5A being sunk by an incorrectly polarized C22 is not a good idea and it certainly exceeds the spec of both the cap and the supply. The -5V rail on the...

So I picked up an LCIII for repair. The TDK PSU was toast - caps are good but the optocoupler is open-circuit and I'm awaiting a replacement. So I bodged into service a spare Astec Beige G3 PSU and the machine booted-up fine on its aged caps. I quickly recapped with tantalums (as you do) but...

There so many ways to hork a G3 doing this stuff! I've often had to resort to an OFW init-nvram command or to pull the battery to a while! There's so many variables... but in particular: what firmware is flashed on the SATA card? what version of OpenFirmware does your bootrom have? You should...

I'd inject a word of caution here. On my SE/30, I had issues with the Rominator and BlueSCSI - so I reverted to the original ROM plus MODE32. And SE/30s can be temperamental with RAM configurations - so your mileage may vary.

Neither Beige or B&W have -5V. Here's the pinout for both:

Yep, my mistake. MODE32 must be installed on 7.5.3/7.5.5. When Apple licensed it from Connectix in 1994, they announced that a future release of MacOS would have it built-in. Never happened.

You need to change the clock divider ratio. Refer to https://lowendmac.com/1997/overclocking-beige-power-mac-g3/ You may be able to over-clock it beyond 400MHz.

A footnote to this: System 7.5.3 and 7.5.5 have MODE32 builtin. No need to install anything .. just enable 32-bit addressing in the Memory control panel and your dirty old SE/30 will happily see more than 8MB. I use 7.5.5 on my SE/30 with 16MB (4*4MB in bank A).

Yep, you grok the issue. My patch is just a cheap fix to get around the issue for my configuration. Lazy initialization would seem to be the solution so long as duplicate connections are permitted.

I did some debugging and the flashrom failure is due to a conflict between the pciutils and DirectHW libraries. The IOUserClient port is being obtained by the PCI library and the PCI bus is successfully probed. But the subsequently attempted memory mapping via the DirectHW library fails because...

I pulled your repos and rebuilt. See attached flashrom.txt and lspci.txt for the latest ouput. Better, but no cigar.

ADS Technologies USBX-500 is what's in my G3 Minitower. Reliable 2-port card.

I cloned your trees to my G3 Minitower running 10.4.11 with TigerBrew installed and built and installed everything. DirectHW and pciutils seem to work OK producing this output - see lspci.txt. But flashrom has trouble - see flashrom.txt. Running under gdb, I see this backtrace - see gdb.txt...

Although UTM is convenient for running potted configs from the gallery, I find that for creating other configurations it adds another level of complexity. In particular for QEMU, it makes configuration switches more difficult to set. I've been experimenting with QEMU instances (guests) on a...