2022-05-04.log

+ gdonner (~gdonner@c-98-253-93-116.hsd1.in.comcast.net)01:40
gdonnerminute: I'm suspect the boot gurus were linked to the ZZ9000 autoboot and Fast RAM add-on01:41
gdonnerusing the noautoboot, no Z3 FastRAM, boots without a guru01:42
gdonnerbut still getting the occasional ZZ9000AX.audio crash (8000 0004)01:42
gdonner(in a requester)01:43
gdonner*suspecting01:43
gdonnerI also noticed that AXMP3, after playing one or two MP3s, starts to play a second or two of the previous MP3 track at the beginning of the current MP3 you're trying to play01:44
gdonnerlike something isn't getting cleared somehow?01:44
gdonnerin any case, those are the biggest issues I've noticed in fw/drivers 1.1101:45
gdonnerthis is still on my A3000/04001:48
gdonnerhaven't updated my A4000 to 1.11 yet01:48
- gdonner (QUIT: ) (~gdonner@c-98-253-93-116.hsd1.in.comcast.net)02:05
+ mnemotron (mnemotron@194.135.47.239)08:09
- js (QUIT: Quit: Bridge terminating on SIGTERM) (~js@2001:470:69fc:105::232)09:14
- apolkosnik[m] (QUIT: Quit: Bridge terminating on SIGTERM) (~apolkosni@2001:470:69fc:105::ff7)09:14
+ js (~js@2001:470:69fc:105::232)09:17
+ apolkosnik[m] (~apolkosni@2001:470:69fc:105::ff7)09:24
+ NoctisBE (~NoctisBE@d54c34cde.access.telenet.be)14:20
NoctisBEHiya! Hope everyone is well. Just received my ZZ9000 and I'm having some issues so I was hoping anyone might be able to help me :)14:21
apolkosnik[m]NoctisBE: Hey, what's the problem? 14:24
NoctisBEI've installed it in my A2000, but I only get a flickering image. Tried the latest FW by downloading it and placing boot.bin on the sd-card as well, but same result. Hold on, I'll link a video14:24
NoctisBEhttps://youtu.be/bJ6_Otnx1wo14:24
NoctisBEI've reseated the boards already, as well as the flatcable, and tried several zorro slots14:25
NoctisBEalso cleaned the slots using canned air etc14:26
apolkosnik[m]can your monitor handle 50Hz?14:27
apolkosnik[m]You used the 1.11 driver for Z2? 14:28
NoctisBEThe same monitor works with an rgb2hdmi, but I can try a different monitor14:28
NoctisBEYep, although I was confused with the 4mb/2mb versions. I tried the 4mb version from the mnt repository14:29
NoctisBEI'll try a TV with HDMI input14:30
apolkosnik[m]if you have a memory expansion, you might be better off with 2MB version 14:30
apolkosnik[m]Don't try to "clean" connectors with DeOxit (just stating preemptively) 14:32
apolkosnik[m]At this stage, your problem seems to be limited to the video capture system, e.g. the card that goes into video slot + the flat cable (I replaced mine with a straight floppy cable on my A3000 and A4000)14:34
NoctisBEThere's a tf534 in this machine14:35
NoctisBEnot sure if that matters14:36
apolkosnik[m]try booting without it and see if anything changes14:36
NoctisBETried with a TV now, which states it's getting an 800x600, 60hz signal14:36
NoctisBEI'll try14:37
apolkosnik[m]I recall that there was a special TF fw for some TF cards to make them play nice with A2000, but I don't remember the details anymore 14:38
NoctisBEHm. Honestly never had issues with the TF14:41
NoctisBEWith the standard 68k cpu I get the same issue. Also tried replacing the flatcable with a straight floppy one, but still the same. Think it would help if I try cleaning the video slot with IPA?14:48
apolkosnik[m]It may help14:55
NoctisBEAlso this particular machine has a Super Denise. I vaguely recall issues with the rgb2hdmi on some machines with that specific chip. Not sure if the zz9000 had similar things going on?14:56
apolkosnik[m]On your video, it looks like it's loosing sync signal.14:57
apolkosnik[m]You can try also older firmwares and see if it changes anything 14:59
NoctisBEWhat's the difference between the 2mb and 4mb firmware versions?15:01
_BnuOne gives you 2MB of video RAM and the other gives you 4MB.15:16
_BnuAlso, I'm pretty sure the RGB2HDMI upscales everything to 1080p60? YouTube video very much looks like the monitor can't handle the video signal.15:18
minute_Bnu: we're sending you an AX15:19
minute_Bnu: i assume you did not move to another house15:19
minute_Bnu: you should have gotten a tracking email?15:20
NoctisBEOK it's definitely not the monitor. I have a semi-stable image now with a flicker now and then. But the machine has been running for 10 minutes or so. This may be a long shot but... Is it possible that I need to replace some caps on the mainboard? I see a few electrolytical ones right next to the video slot15:20
NoctisBEhttps://youtu.be/goaJZyi6zGs15:26
_BnuNo, I haven't moved, hahah. I doubt I'd be able to afford to live anywhere else.15:29
NoctisBEI'm checking the A2K schematics now if those caps have anything to do with the video circuitry. The RGB2HDMI board I used is one that piggybacks off the Denise chip.15:30
NoctisBESorry for infodumping here btw, I'm kind of rubber ducky-ing :p 15:30
apolkosnik[m]NoctisBE: any chance you can put back regular Denise in there and try again? 15:34
apolkosnik[m]or try the A500+ fw15:34
NoctisBEI don't have a regular denise15:34
NoctisBEit's the one that came with this machine15:35
NoctisBEI can try thr a500+ fw15:35
NoctisBEthe*15:35
NoctisBEThe a500+ firmware gives me weird colours15:39
apolkosnik[m]but does the display goes blank or is it OK? 15:41
NoctisBEIt's still like it gives me sync issues, along with the background being black and the kickstart boing ball being yellow15:43
apolkosnik[m]Oh, so on the latest video that you posted it looks like you are just getting some interference 15:43
apolkosnik[m]Lol, go back to A2k fw15:44
_BnuWeird, you definitely shouldn't be getting weird colors with the 500+ firmware if it is indeed a Super Denise.15:45
_BnuWait, hold on.15:46
_BnuYou're using the video slot, right?15:46
NoctisBEI am, yes15:46
_BnuIn that case, you can't really use the A500 or A500+ firmware. You might need some different phase offset, but that's different.15:46
apolkosnik[m]You'd see some artifacts on straight lines15:49
NoctisBEHmm. Just reinstalled the latest fw, and it's definitely losing sync. Just not consistently now15:49
NoctisBEStill not sure if this is hardware related or firmware15:50
NoctisBEThe caps I meant earlier are for composite sync apparently15:54
NoctisBEwait no. Those are for vcc for the hy200 (vidiot) chip. I doubt that's the issue15:56
NoctisBEI'm honestly grasping at straws atm15:57
apolkosnik[m]can you try booting into the early startup menu and switching between PAL and NTSC? 16:00
apolkosnik[m]power off, hold both mouse buttons, then power on16:00
NoctisBEok so, the early startup seems stable. If I select ntsc and click "boot" to go back to kickstart, it loses sync again. Not sure if it reverts back to pal at that point though16:09
NoctisBEBut the moment I enter early startup, everything is stable, even without selecting ntsc16:09
apolkosnik[m]you can hit space in the boot menu screen and it will switch between PAL and NTSC on the spot16:10
NoctisBEI'll record it, sec16:11
NoctisBEhttps://youtu.be/7nbCabW4Z1Y16:15
NoctisBESo early startup works perfectly in both PAL and NTSC16:16
NoctisBEthis is with firmware 1.9 btw. Not sure if kick 3.2 does some weird shenanigans, resolution/refreshrate-wise16:17
NoctisBEI think I'm just going to try and install the rest of the hardware now, and reinstall Workbench16:21
NoctisBEif it's just the kickstart that's being weird it's not the end of the world :p16:21
- xet7 (QUIT: Read error: Connection reset by peer) (~xet7@user/xet7)16:59
- mnemotron (QUIT: Quit: Quit) (mnemotron@194.135.47.239)17:45
pasikhmm, which firmware fixed the broken sync ? 17:46
pasiki can't remember the exact version17:46
pasikbut sync was totally broken on a number of dell displays for example17:46
Jopethat was quite some time ago.. 17:47
Jopewish I kept logs17:47
pasiki think it was 1.8 that fixed it17:48
pasikor actually, when checking the release notes17:48
pasikit's probably 1.9.1 that fixed it17:48
pasikNoctisBE: so if you're running 1.9 you need to upgrade17:49
Jopebest to just run the latest anyway?17:50
pasikyup17:51
minuteNoctisBE: the A500+ firmware only works with the denise adapter (it uses composite sync)19:36
minuteNoctisBE: on your first video it looks like hsync is breaking off due to interference perhaps? does it change if you route the videoslot cable somehow differently? 19:37
+ xet7 (~xet7@user/xet7)20:02
- NoctisBE (QUIT: Ping timeout: 248 seconds) (~NoctisBE@d54c34cde.access.telenet.be)23:29

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!