| lastebil | NoctisBE: ping Franky, see if he still has any of the ones that we collected from work that were up for sale | 09:19 |
|---|---|---|
| lastebil | (yes Jope that's the same place the one I gave you came from) | 09:19 |
| + CottonUndies (~CottonUnd@2405:6580:33c0:b400:18c7:fc3a:117a:61ec) | 10:37 | |
| CottonUndies | Hello there, it's been awhile, and that means I have problem=questions..... | 10:37 |
| CottonUndies | 1. Under 1.8 I was using a specially provided firmware on my 3000 that was called BOOT_NOZ3Fast_fixed, and this required another file to be installed called ZZ9DMA60.card . Are these special versions still needed for 1.9 and upward? Is there anywhere to go to get these special versions, the main firmware page doesn't seem to list them? | 10:39 |
| CottonUndies | 2. After upgrading to 1.9.x I figured out that FAT32 USB is no longer possible. So I tried to downgrade, which I think worked, but now when writing to my USB drive I get GURU 8xxxx4 mediations. This was working before, I and I have restored my working drive image, and think I have properly moved back to the firmware that was working for me, but now | 10:42 |
| CottonUndies | I'm not 100% sure. Note: I was using a NOZ3Fast ram option firmware as it was crashy for me, but FYI, under 1,9 the RAM seemed to work well! | 10:42 |
| _Bnu | The files in http://www.apehead.se/snakes9000 should work fine with 1.9, or at least as close to 1.9 as my firmware is. | 10:58 |
| CottonUndies | First time for me to access that site! Is there any way a lamer like myself can figure out the naming convention and purpose for the ZZ9DMAxx.card files and others such as ZZZ9020? Or should I just mind my own business :-) | 11:04 |
| _Bnu | The numbers at the end are just for which CPU they're compiled, it usually doesn't make much of a difference in terms of performance. | 11:18 |
| _Bnu | DMA is the one that uses the DMARTG stuff, it's faster than the regular one as long as it works properly. | 11:18 |
| _Bnu | If it doesn't work properly, you can try DME, which has a dummy memory access to trick the data cache. | 11:18 |
| CottonUndies | Thanks, I really appreciate you taking time to educate. I'll probably stick to the installters! But for now, I'm pulling my teeth trying to get back to 1.8.... | 11:20 |
| CottonUndies | Probably stupid Q regarding my USB: If my ZZ9000USBStorage.device in devs: reports as 1.7 , how can I find out if that works with firmware 1.8? For example, I know from here (https://mntre.com/media/ZZ9000_info_md/zz9000-firmware-archive/zz9000-firmware-archive.html) that ZZ9000USBStorage.device 1.5.1 needs 1.6 or 1.7 firmware. I'm just asking as | 11:29 |
| CottonUndies | now I'm not sure which installer version I am on! Which could be a problem if I'm using 1.8. Is there a way to confirm which SOFTWARE/INSTALLER I'm currently using on my system? | 11:29 |
| CottonUndies | "Which could be a problem if I'm using 1.8." should read "Which could be a problem if I'm using Firmware 1.8." | 11:30 |
| _Bnu | Ah, sorry. Keeping track of the old firmware and drivers is really tough for me, since I've basically always been using my own builds. | 11:55 |
| _Bnu | Does the new firmware released recently with AX support not work for you? | 11:55 |
| _Bnu | It should have DMA RTG drivers and some other things as options in the installer already, I believe. | 11:56 |
| - xet7 (QUIT: Remote host closed the connection) (~xet7@user/xet7) | 12:08 | |
| + xet7 (~xet7@user/xet7) | 12:09 | |
| - CottonUndies (QUIT: Quit: Client closed) (~CottonUnd@2405:6580:33c0:b400:18c7:fc3a:117a:61ec) | 12:10 | |
| minute | yeah people should upgrade to 1.11 | 12:28 |
| minute | i don't even remember what 1.8 was like | 12:28 |
| minute | _Bnu: btw did the ax ever arrive? | 12:29 |
| _Bnu | Yeah, it's here, haven't had time to install it yet. Face deep in the final Don Rosa duck book. | 12:43 |
| minute | cool | 13:17 |
| minute | oh don rosa | 13:17 |
| minute | i had a bunch of bark's library | 13:17 |
| - xet7 (QUIT: Remote host closed the connection) (~xet7@user/xet7) | 14:09 | |
| + xet7 (~xet7@user/xet7) | 14:10 | |
| Jope | mmh.. upgrade to 1.11 finally this weekend hopefully :-D | 15:01 |
| + CottonUndies (~CottonUnd@2405:6580:33c0:b400:18c7:fc3a:117a:61ec) | 16:44 | |
| - CottonUndies (QUIT: Quit: Client closed) (~CottonUnd@2405:6580:33c0:b400:18c7:fc3a:117a:61ec) | 17:32 | |
| NoctisBE | Alright, so, I've got the 2k up and running. Is there a way to allocate ZZ9000 RAM to fast memory? | 18:05 |
| _Bnu | Yes/no. | 18:08 |
| _Bnu | Because there's only 8MB of Z2 address space and Z2 is so slow to begin with, it would inherently not be very useful. | 18:08 |
| _Bnu | But you can use AddMem to assign part of the allocated memory space as Fast RAM. It will however mess with the frame buffer. | 18:09 |
| NoctisBE | Alright. I'll give that a shot | 18:10 |
| NoctisBE | It seems P96 uses a LOT of ram and I didn't realise that. So the 4 megs of RAM on my TF534 isn't enough | 18:11 |
| _Bnu | But yeah, the best way to do Fast RAM on an A2000 or 500 is to have 32/64/something megabytes on the CPU bus only, so it can be accessed using 32-bit space. | 18:12 |
| _Bnu | (Typically on the accelerator, or something that goes in the CPU socket on the A2000.) | 18:12 |
| NoctisBE | does anyone happen to know the address space to use for Addmem? | 19:39 |
| _Bnu | Well, yeah. It's the address range the ZZ9000 has been assigned to. | 21:23 |
| _Bnu | You can see it in ShowConfig. | 21:24 |
| _Bnu | You can not add some other random address range, the ZZ9000 will only respond on the memory range it has been assigned to by AutoConf. | 21:24 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!