Line 52: |
Line 52: |
| /etc/group | | /etc/group |
| Reboot, or set domainname and run ypbind. | | Reboot, or set domainname and run ypbind. |
| + | </pre> |
| + | |
| + | ===PCMCIA Support=== |
| + | <pre> |
| + | : My question is what PCMCIA card is known to work ( besides the |
| + | : impossible to find Xircom for which drivers are available at NexTanswers.) |
| + | : If someone has been able to make the 3C589 ( of which I see many |
| + | :variations ) work, what has to be done ? |
| + | for us, after chosing the right(!) interrupt (experiment a little bit |
| + | there), any 3Com589 card did - the last one we used was a version 'D' |
| + | (iirc, it might also be 'E'). |
| + | |
| + | The important part is to add the 'letter' behind 589 to the drivers' |
| + | id-strings (something like manufactuerer="3Com", type="589D") in the |
| + | /private/drivers/i386/"589-driver".config directory. I don't have a |
| + | version of these notebooks available, but it was quite trivial. |
| + | |
| + | Not so trivial was to find the right interrupt. With the "wrong", so |
| + | allowed ones, the card was detected but simply wouldn't work (i.e. it |
| + | wouldn't send, iirc). That was a decision between an IRQ either below or |
| + | above IRQ8 (so 3, 4, 5(used by PCIC-driver), 7, or 9, 10, 11), only one |
| + | group worked (for us); I think it were the 'lower ones' and I decided |
| + | to use '3', swapping it for the second serial port, but I'm not sure. |
| + | |
| + | : Hmmm, I may did something wrong, but I am not able to get a 589E to run. |
| + | : It is some kind of 'Megahertz', up to D the cards work fine. |
| + | No, caveat emptor, my memory could play me a trick; I'm just sure a |
| + | 'bunch of 589 cards' did work, not of the up to 'E' statement. For |
| + | certain I also do know it of the 'D' version, as I've put them into |
| + | to Toshibas (a Tecra 750 and a Satellite 4000) successfully. |
| </pre> | | </pre> |
| | | |