Who's Online |
108 user(s) are online ( 61 user(s) are browsing Forums)
Members: 0
Guests: 108
more...
|
|
|
|
|
Re: Is your X1000 unstable, and sometimes hangs on bootup?
|
|
Just popping in 
|
@Deniil
I too have been frustrated by stability problems with my X1000 recently. Replacing the CR2032 battery (which had run down to a very low voltage) and reseating SATA cables seems to have solved the problem.
Before I checked the SATA cables, I had also reseated RAM, put it in different slots and tried different DIMMs, partly because of the misleading error messages given from CFE when there are drive errors, but I don't think the RAM was an issue in the end.
|
|
|
|
|
|
Re: x1000 onboard network opensource driver in progress
|
|
Just popping in 
|
@kas1e Quote: kas1e wrote:@All Now, when i switch to cables which handle 1GB fine, i lockups IMMEDEATELY always when trying to run stress tests. Switched back to 100mb/s cable , and lockup happens not as fast, and take longer. Once again back 1GB - immediately.
Did it give us any clue ? Only that something overflows ?
Are you just changing the cable, or the physical ports? I.e. when you say you're switching the cable, do you mean you're switching between cat 5e, cat 6e etc., or changing from a 100 Mbit link partner to a Gigabit link partner? BTW, have you tried doing a ping flood from another machine to the X1000?
|
|
|
|
|
|
Re: x1000 onboard network opensource driver in progress
|
|
Just popping in 
|
One more thought: you mentioned the DMA list wrapping around when the driver is stress tested. Is it possible the driver doesn't properly handle the situation where the DMA list wraps around?
Maybe try using a very small number of descriptors (like two) so that this condition is reached easily and you can examine the behaviour.
|
|
|
|
|
|
Re: x1000 onboard network opensource driver in progress
|
|
Just popping in 
|
@kas1e
Maybe you need to add (more) cache flushing calls?
|
|
|
|
|
|
Re: x1000 onboard network opensource driver in progress
|
|
Just popping in 
|
@balaton
OS4 has different virtual and physical addresses. GetDMAList() can provide the translation.
|
|
|
|
|
|
Re: x1000 onboard network opensource driver in progress
|
|
Just popping in 
|
@joergQuote: joerg wrote:@ncafferkey Quote:Ranger shows each PCI device’s interrupt number. But it can't display the list of interrupt handlers, unlike Scout for example. Yes, a live list is better, but there was a suggestion in a previous post that Scout might not work on current OS4, so Ranger's PCI list may be better than nothing. But in fact, I just remembered that Ranger has a list of interrupt handlers too (Exec->IntHandlers). Quote: Quote:AFAIR the devices involved in NIC usage each have unique interrupt numbers, so I don’t think it’s likely some other random device is getting in the way. Even on the AmigaOne and Sam440/460 (emulation) PCI IRQs might me shared, but on the Pegasos2 (emulation) all PCI devices use the same IRQ number and everything (PATA, SATA, XHCI USB, NIC, sound, gfx, etc.) uses the same shared IRQ and interrupt handler list.
I was referring specifically to the X1000's built-in NIC. I know NICs in general often share IRQ numbers.
|
|
|
|
|
|
Re: x1000 onboard network opensource driver in progress
|
|
Just popping in 
|
Ranger shows each PCI device’s interrupt number. AFAIR the devices involved in NIC usage each have unique interrupt numbers, so I don’t think it’s likely some other random device is getting in the way.
However, with the driver needing several of the PCI devices, is it possible that one of them is triggering an interrupt you’re not expecting, e.g. for a statistics counter?
|
|
|
|
|
|
Re: x1000 onboard network opensource driver in progress
|
|
Just popping in 
|
@kas1e Quote: kas1e wrote: ps. is the batter in x1000 are 3v one right ? And i read somewhere that better to go with BR2032 than CR20232 , like BR2032 better for long run Yes, 3V. Personally I find CR2032 is fine, as it lasted several years in my X1000. It didn't give problems until it got extremely low (1V).
|
|
|
|
|
|
Re: x1000 onboard network opensource driver in progress
|
|
Just popping in 
|
@kas1e This NIC sounds very unusual. I think you mentioned that there is no publicly available documentation? Is the Linux driver in the main kernel source, and what's it called? Quote: Btw, may i ask why in your driver you use EmulateTags() copy for RX/TX/etc ? Just for having same code working for os3/os4 , or there were other reasson for ?
Yes, to have compatibility with OS3/AROS/MorphOS. Also, I don't think I was aware of an alternative approach when I first wrote those drivers. Quote: Also can we call ReadConfigLong() from IRQ context ? Probably not ?
AFAIR you're only allowed to call system functions that explicitly say they are interrupt-safe (but I could well be wrong). Is there dynamic information in the config registers that can't be cached during initialisation? BTW I usually use a local FTP server for network testing. Ping in flood mode can be useful for stress testing too, but unfortunately Roadshow's ping command doesn't allow that.
|
|
|
|
|
|
Re: x1000 onboard network opensource driver in progress
|
Posted on: 3/10 20:33
#10
|
Just popping in 
|
My DMA-based network drivers assume there is no cache coherency. They use Exec cache-related commands (wrapped in macros for compatibility) to flush caches before and after DMA transfers.
I wasn't aware of the MEMATTRF_CACHEINHIBIT flag until now, so I can't say for sure if that could be used instead.
It is strange to me that the two on-board NICs enumerated by PCI don't have BARs (is the one that's actually connected to the RJ45 port the 1 Gb or 10 Gb one?). Normally, driver code just gets the virtual address from the BAR and doesn't need to care about the offsets etc. you mentioned.
However, the PCI entries do have interrupt numbers, so why shouldn't AddIntServer() work with them?
I also second what Niels said about the battery: a low voltage can have strange effects, as I found out recently: my X1000 wouldn't turn off!
|
|
|
|
|
|
Re: X1000 won't turn off
|
|
Just popping in 
|
Thanks everyone! Changing the CMOS battery worked a treat. The old one was down to 1 Volt!
Thankfully I didn't have to re-enter any settings after the battery change either.
|
|
|
|
|
|
Re: X1000 won't turn off
|
|
Just popping in 
|
@Tuvok
Thanks for the tips. I should have mentioned that I tried bypassing the power button on the case by shorting the power button pins on the motherboard, but the symptoms were the same.
|
|
|
|
|
|
X1000 won't turn off
|
|
Just popping in 
|
Hi,
I've recently had the problem with my X1000 that I can't turn it off except by flicking the switch on the PSU. Previously, when I tapped the power button on the front of the case, it turned off after a few seconds. Now that doesn't happen, and even holding down the power button for several seconds doesn't turn it off.
I also sometimes have the problem that it doesn't turn on on the first press of the power button. Is this likely to be a motherboard or a PSU problem?
|
|
|
|
|
|
Re: Get MAC Address od AmigaOS4 Machine
|
Posted on: 2025/4/2 22:55
#14
|
Just popping in 
|
I used to use a Netgear wireless bridge and IIRC it may have hidden the true MAC addresses from the router it connects to, so watch out for that.
One way to get the MAC address that works on any Amiga is to use SanaUtil from Aminet, e.g.
sanautil -d 3c589.device status
...shows the default MAC address as well as other stats. Of course, you need to change 3c589.device to the network device name on your system.
BTW, is it the X5000 that always uses the same MAC address (for every machine), or has that bug been fixed?
|
|
|
|
|
|
Re: Poseidon USB Stack as Open Source?
|
Posted on: 2025/3/28 17:41
#15
|
Just popping in 
|
@Swisso
AFAIR Poseidon was already the MorphOS USB stack before it was open sourced for AROS, so their licence is different.
|
|
|
|
|
|
Re: Tell me I bought the correct card(s)
|
Posted on: 2022/3/16 3:57
#16
|
Just popping in 
|
@Raziel A DMA NIC does a lot of the work without the CPU being involved, but not all (e.g. it doesn't have a TCP/IP stack  )
|
|
|
|
|
|
Re: DMA buffer for PCI busmaster headache
|
Posted on: 2021/2/22 0:27
#17
|
Just popping in 
|
@geennaam
Using StartDMA()/EndDMA() would be a lot simpler. If the buffer you pass to it is physically contiguous, you'll only get one address in the returned list. So these functions don't require scatter/gather, they just support it.
Then you won't need to worry about supervisor mode, low level functions for cache flushing and getting physical addresses etc.
CachePreDMA()/CachePostDMA() are broken on OS4, so don't use them.
One other thing to watch out for: the DMAF_ReadFromRAM flag must be passed to StartDMA()/EndDMA() if the device will only read your buffer OR if it will read AND write your buffer. I.e. the only time it shouldn't be set is if you're sure the device will only write to the buffer.
|
|
|
|
|
|
Re: atheros wlan device is working
|
Posted on: 2021/1/28 2:18
#18
|
Just popping in 
|
@arfcarl
No, sorry.
|
|
|
|
|
|
Re: atheros wlan device is working
|
Posted on: 2021/1/28 2:15
#19
|
Just popping in 
|
@utri007
No progress unfortunately as I've been spending my sparse Amiga time on recovering from two HD crashes/corruption!
|
|
|
|
|
|
Re: SFS2 errors on X1000
|
Posted on: 2021/1/5 0:31
#20
|
Just popping in 
|
It's a Kingston SATA SSD. It's not a connection issue, as I've attached it to a USB converter and other computers since discovering the problem. I was able to take an image of the drive on a Linux PC without any errors being logged, so the drive seems OK for reading at least. But regardless of whether there's a hardware or software/logical/FS fault, my main concern now is to see if I can get useable data off the drive.
I've read that SFS2 doesn't have any recovery tools. Is there anything at all I can do to read files off the drive?
BTW, there definitely seems to be a bug in the filesystem code in that it crashes when attempting to read this volume through USB.
|
|
|
|
|