Cyborg wrote:Lumby wrote:
My problem is I can not get my RTL8029AS to function at all.
The reason is that rtl8029.device (and also rtl8139 and rtl8169) only check for the default realtek PCI IDs. Back when I wrote those drivers, I only had cards with default Realtek IDs and the same for the betatesters. So I never had a chance to add more cards to the list of supported cards. BUT luckily I gave the user the ability to overwrite those default IDs
Then why wasn't there a script created to extract the VendorID, and the DeviceID, and fill that into the found hardware solving these problems for people spending about £100 (GBP) for an Amiga Operating System that won't let you get online to be able to ask the questions ONLINE in this forum.
I have registered MorphOS for a MacMini, and had no problems installing it - and that's Apple hardware, not an original piece of Amiga hardware, which this OS4.1 doesn't currently work properly on.
MorphOS also seems to support more legacy software than OS4, and I can use it with USB hardware, which with OS4 on my A1200 I can't because there's no support for USB hardware using the PCI ports, only for no longer produced/unobtainable USB 1.1 clockport Subway or Deneb Zorro port - unusable in my Mediator A1200 which are also not manufactured any more.
Either you provide the solution WITH the OS or it's not a proper solution, and Hyperion and all the other betatesters should have asked via Amiga websites for people intending to upgrade to OS4.x what hardware they had so it could be checked that there were not going to be these problems with drivers, or any other hardware nuances that should have had little chance of slipping by unaccounted for.
The number of betatesters was not large enough it seems, as I'm sure the card I'm using was one that Eyetech supplied to me, so there must be lots of people with the same type of card, but you just don't happen to have encountered it - not enough checking on this kind of available hardware for OS4 in my opinion. Maybe lots of work went on, but not enough as these problems should have been resolved and a solution that worked for all with such hardware should have been implemented. They work on a PC without this crazy VendorID, or DeviceID being a problem, so it should work without this kind of a problem on an Amiga - don't you think?
More checks on more hardware should have been done, and a solution for all users with supported hardware should have been achieved BEFORE OS4.0 was released and definitely before OS4.1 was released.
OK, back to my problem.
How, do I edit a hardware ENV: file that doesn't exist? Using which editor, if required, and by whatever other means.
I could just create a file called rtl8029.device with "ed" - is that what you are saying? If so, that doesn't seem right as you've made it look like a directory, but there is no directory in ENV: that is called rtl8029.device.
I know the other user managed to work out what you meant, BUT, your directions as to how to accomplish it were not very specific. You seemed to think that anyone would know what you meant, but I can assure it you it was/is not that clear to me as to what is required to solve my problem, that I shouldn't even be experiencing anyway.
I have installed Ranger, and can see that basically my product is the same ID as the previous OS4.1 user who has this problem - maybe they too got their PCI NIC from Eyetech, as my ID seems to be the same VENDORID 0x4A14 and DEVICEID 0x5000, so 2 users with the same ID, and betatesters who never came across this ID on this kind of hardware, yet here we are 2 purchasers caught out with this problem, because not enough checking, and preparing for such eventualities while beta-testing - that is where this problem should have been found, and a fix-all solution put in place.
There is no file in ENV: that is named as you've stated, so there is nothing to edit - full explanation required.
The driver reads a file from "ENV:rtl8029.device/" named "unit<X>" where
<X> replaced by the unit number (0-7). The variable must contain one line
of configuration text which follows this template:
HALFDUPLEX/S,FULLDUPLEX/S,NOFLOWCONTROL/S,FLOWCONTROL/S,
VENDORID/K,DEVICEID/K
The options should be fairly self-explanatory, so just a few words
regarding VENDORID/K and DEVICEID/K: These two are meant to overwrite
the standard Realtek vendor and device PCI IDs, which might be usefull
for rebranded network cards with a supported Realtek chip. To get both
IDs, run "pciscan" in a shell and look for your card. The ID's *must*
be given as 16-bit hex values, e.g. 0x10EC or just 10EC. Case is
ignored.
I tried to run "pciscan" in a Shell window, but "unknown command" is the result I got from that Shell input.
Hope to get some more help to solve this problem, but I am somewhat disappointed with OS4.1 so far.