@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 )

@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.

@arfcarl

No, sorry.

@utri007

No progress unfortunately as I've been spending my sparse Amiga time on recovering from two HD crashes/corruption!

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.

Hi,

I recently turned on my X1000 after not using it for a while, and got SFS errors from my system partition that prevented booting. I get this loop of errors:

1. "This volume tried to access a block outside its partition."
2. "Updating the volume failed due to an unknown error. The errorcode is 99 (free blocks = 0)"
3. "The transaction couldn't be re-applied to the volume because of error 1662623744." (Is there really such an error number?)
4. "Unable to flush all buffers correctly"
5. "Not a DOS disk"

Is there anything I can do to repair the volume, or even copy some of the data off before I reformat it?

I tried booting from CD, but it hangs when the problematic disk is attached. I also tried booting from CD and attaching the disk as a USB disk through a converter, but I get Gurus from the FS and DOS locks up.

@arfcarl

PCI/PCI-E initially.

@kas1e

Whether you should leave a device open or not depends on the use case. Could other programs need to access it in between your accesses? Will your having the device open block other accesses? (I'm too lazy to read the serial.device AutoDoc right now )

Again, I'm not sure of the use case. My guess is you have custom monitoring hardware attached to one of the X5000's serial headers. Or is it standard? Ideally, there would be a hardware monitor API that would share out this information to multiple listeners. Then it wouldn't matter much if the "API" blocked other direct access to the serial device.

@arfcarl

Ralink RT28xx. Yes.

@NinjaCyborg

Perhaps the wired interface needs to be disabled.

@Tuskagee

Sorry, those eBay links are dead now.

No, 802.11n isn't supported. There will be a new driver for a different chipset that will support it.

@Tuskagee

Thanks for all the reports. I've added the information to the next version of the driver manual.

Does the mini-PCIe card you got working have any brand or model number printed on it? Also, did you get your hands on the Netgear WG311 to try?

@Tuskagee

Thanks for the information.

Yes, cards that are compatible with the Linux drivers ath5k or MadWiFi should work, as long as they support 802.11g (my driver doesn't support 802.11a). Any additions to the compatibility list would be welcome

BTW I'm away on holidays at the moment, so I can't easily access the driver docs for comparison, but I'll update them when I'm home.

@Mikey_C

Do the cards in the photos work for you then? If so, in which machines?

@Tuskagee

Thanks for the information on the DWA-643. I've removed it from the compatibility list for the next release.

I don't know if I can help any further with getting these cards working on your SAM460, as the problem seems to be with the hardware or OS rather than the driver.

@Tuskagee

That's strange. Is there some Uboot setting needed to enable the slots? I know you said previously that you used a sound card in the PCIe slot, but do other network cards work in any of the slots, e.g. RTL8139 cards?

What do you mean by the wrong class?

@Tuskagee

Don't pay too much attention to the lights on the card. They are software controlled and my driver may not light them up. But if the card isn't visble in Ranger's PCI list it could be a sign of a broken card, unless the slot is deactivated (see nbache's post).

@utri007

I might be able to do that in the near future. I'm working on a new version of WirelessManager, and I could activate a simple MUI GUI that's already used in the AROS version.

@Tuskagee

Yes, it's apparently the onboard SATA port that has a conflict with the PCIe 1x slot. So are you using an add-in SATA card? (Maybe that's what everyone does: as I said, I don't know much about the 460.)

Even if you don't want to use a PCI card in the 460 in the long term, I'd be interested to know if it works, as I haven't had anyone else report the results of using the new driver version on a 460. However, if that's inconvenient, don't worry about it.

@Tuskagee

The only ones I'm aware of are in the list included with the driver. What exactly happens when you try to use the card?

I don't know much about the 460, but I did read that the PCIe 1x slot can't be used at the same time as the SATA port: have you previously used another card in the same slot? Alternatively, it's possible the 460 has a separate incompatibility to the one I fixed for the 440.

Also, would it be possible to try your PCI card in the 460 for comparison?

@Tuskagee

The error message "Replay counter did not increase" can appear when WirelessManager is running twice. When testing it in the shell, make sure to remove it from the Startup-Sequence (and reboot of course).

Apart from that, the connection looks successful; specifically the "CTRL-EVENT CONNECTED" message. What problems are you seeing getting online, i.e. from the TCP/IP stack?

A GUI may be available in future.

@Tuskagee

What machine and exact card? Does the machine lock up? I presume the message mentioned a network name but you removed it for privacy. What kind of encryption does the network use?