Re: PCI Plug 'n' Pray and old BIOSes
Olaf Hoyer wrote: Hi! The card normally should act and behave at least as a normal NE2000 clone (ed0) But as stated before, you might have to jumper it into the mobo. Yes, that was the problem. I managed to find the manual and discovered it had been jumpered as non-PnP (not by me; I inherited this machine a couple of years back to use as a PPP dialer and had an ISA NIC in it until now). Also the PCI latency is IMHO too high. Try setting it at around 40. That will affect the throughput of the NIC, or its reliability? Or both? I'm not too concerned if its just throughput, because (horror!) it has only ancient 16450 UARTs (one byte FIFO) on the multi-I/O card which are driving a 56k modem. I think its a very positive reflection on FreeBSD that despite this antique UART, which is being driven at 115200 baud, the PPP connection works very reliably and with pretty good throughput (there are the odd silo overflow log messages, but they don't seem to be a real problem). In fact this ancient 486 with 16Mb RAM is doing a fine job as a web cache, print and mail server. -- Dr Graham WheelerE-mail: [EMAIL PROTECTED] Director, Research and Development WWW:http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN SpecialistsFax:+27(21)424-3656 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PCI Plug 'n' Pray and old BIOSes
On 2000-06-20 10:41 +0200, Graham Wheeler [EMAIL PROTECTED] wrote: Also the PCI latency is IMHO too high. Try setting it at around 40. That will affect the throughput of the NIC, or its reliability? Or both? It won't do anything, in your particular case. The latency timer is the maximum number of PCI bus-master cycles that this card will be granted, if some higher priority PCI device is requesting the bus. Your Ethernet card doesn't support bus-master transfers ... The latency timer has to be set to a value that prevents buffer under- / overflows in PCI devices with limited FIFO sizes. (For example a bus-master 10baseT Ethernet chip with just 16 bytes of buffer has a maximum latency of 16 microseconds or roughly 500 PCI clocks. If there are 5 possible bus-masters and priorities are round-robin, then each bus-master may occupy the bus for no longer than 100 clocks.) There are "minimum grant" and "maximum latency" registers in each PCI device, which hold constant values denoting the number of bus clocks the device requires for efficient operation and the maximum latency between requesting the bus and getting it granted the device can tolerate. Reagrds, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PCI Plug 'n' Pray and old BIOSes
On 2000-06-19 11:05 +0200, Graham Wheeler [EMAIL PROTECTED] wrote: As I was under time pressure, I pulled the card out and put it in a different machine, this one a P166 which works fine (with the same IRQ). Anyway, when I get a chance I would like to try it again in the 486. The 486 has three PCI slots, and the BIOS has some additional settings which may be the reason it wasn't working. I'm unfamiliar with what some of these do, and am hoping that someone on the list may have experience with early days of PCI and Plug 'n Play, and be able to help. These are the settings: Slot n IRQ Line (this is the only one I set on my first attempt, to 12) Is the PS/2 mouse interface enabled ? It will try to grab IRQ 12, and may do so in a way that the IRQ can't be delivered from ISA or PCI slots ... Perhaps all I need to do is toggle the PnP BIOS setting, but before I pull out the screwdrivers and tear the two machines apart again, I'm hoping to draw on someone else's experience here. Depending on the time when the mainboard was built, this may be a board that needs jumpers configured accordingly (i.e. you have to enter the jumper settings in the BIOS, which will put the number in the appropriate config space register, but interrupt routing is implemented via jumper fields ...) The first ASUS 486 board, for example, (the 486-SP3, based on the Saturn 1, chip revision 2) used jumpers, while the SP3G used the Saturn II (chip rev. 4) and there was an IRQ routing matrix in the chipset, which allowed for BIOS-only IRQ assignment. Regards, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PCI Plug 'n' Pray and old BIOSes
Stefan Esser wrote: On 2000-06-19 11:05 +0200, Graham Wheeler [EMAIL PROTECTED] wrote: As I was under time pressure, I pulled the card out and put it in a different machine, this one a P166 which works fine (with the same IRQ). These are the settings: Slot n IRQ Line (this is the only one I set on my first attempt, to 12) Is the PS/2 mouse interface enabled ? It will try to grab IRQ 12, and may do so in a way that the IRQ can't be delivered from ISA or PCI slots ... The may be a psm driver in the kernel, but there is no PS/2 mouse device on the motherboard or on any of the cards. Perhaps all I need to do is toggle the PnP BIOS setting, but before I pull out the screwdrivers and tear the two machines apart again, I'm hoping to draw on someone else's experience here. BTW will setting the PnP BIOS to `enabled' have any effect? Depending on the time when the mainboard was built, this may be a board that needs jumpers configured accordingly (i.e. you have to enter the jumper settings in the BIOS, which will put the number in the appropriate config space register, but interrupt routing is implemented via jumper fields ...) I'll have to check that; I do still have the mboard manual somewhere. regards gram -- Dr Graham WheelerE-mail: [EMAIL PROTECTED] Director, Research and Development WWW:http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN SpecialistsFax:+27(21)424-3656 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PCI Plug 'n' Pray and old BIOSes
On 2000-06-19 15:32 +0200, Graham Wheeler [EMAIL PROTECTED] wrote: Stefan Esser wrote: Is the PS/2 mouse interface enabled ? It will try to grab IRQ 12, and may do so in a way that the IRQ can't be delivered from ISA or PCI slots ... The may be a psm driver in the kernel, but there is no PS/2 mouse device on the motherboard or on any of the cards. The BIOS may configure the chip-set to directly connect the PS/2 mouse to IRQ 12 in a hardware specific way. Use of IRQ 12 for PCI interrupts may be impossible, but the PCI or Ethernet drivers can't tell, because it is all a function of chip-set internals. It doesn't matter whether there are any PS/2 drivers or even a PS/2 plug. Perhaps all I need to do is toggle the PnP BIOS setting, but before I pull out the screwdrivers and tear the two machines apart again, I'm hoping to draw on someone else's experience here. BTW will setting the PnP BIOS to `enabled' have any effect? Not sure. You didn't tell anything about the system. I assume it is one of the Saturn I or Saturn II based boards, which were the first reliably working PCI based PC mainboards. Verbose boot messages may help, too, since they provide a lot of details about the hardware and the configuration performed by the BIOS. PnP BIOS usually applies to ISA PnP cards and should have no impact on PCI. But if your system predates ISA PnP, the term may well be used to toggle a PCI chip-set or bus initialisation feature. I'll have to check that; I do still have the mboard manual somewhere. Ok. If you can't get it to work, then please send at least the following information: * name of mainboard (brand and model) * verbose boot message log Regards, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PCI Plug 'n' Pray and old BIOSes
At 11:05 19.06.00 +0200, Graham Wheeler wrote: Hi all I have a Genius Hub Card (basically an Ethernet NIC that also acts as a four port hub). I would ideally like to use this card in an old 486DX4 machine which acts as a ppp router. The card is detected (under both Windoze and FreeBSD) as a RealTek card (the model number escapes me right now). I installed 4.0-R on this machine, which detects the card, but gives me "ed0: device timeout" messages. Usually this is because the interrupt is misconfigured, but I don't think that is the case here. As I was under time pressure, I pulled the card out and put it in a different machine, this one a P166 which works fine (with the same IRQ). Anyway, when I get a chance I would like to try it again in the 486. The 486 has three PCI slots, and the BIOS has some additional settings which may be the reason it wasn't working. I'm unfamiliar with what some of these do, and am hoping that someone on the list may have experience with early days of PCI and Plug 'n Play, and be able to help. These are the settings: Slot n IRQ Line (this is the only one I set on my first attempt, to 12) Slot n Latency Timer (ranges from 0..255 PCICLK) (was on 255) On Board PCI/SCSI BIOS Enabled/Disabled (was disabled) CC State Machine: Data Write 0 WS Enabled/Disabled (was disabled) Data Read 0 WS Enabled/Disabled (was disabled) Hi! The card normally should act and behave at least as a normal NE2000 clone (ed0) But as stated before, you might have to jumper it into the mobo. Also the PCI latency is IMHO too high. Try setting it at around 40. If you want to check out possible IRQ conflicts (at least on PCI bus with vid cards), there are some programs (ok, DOS based) that give out very reliable figures. Otherwise try the config utility of the card and put it into jumperless mode, no pnp. Regards Olaf Hoyer Olaf Hoyer www.nightfire.demailto:[EMAIL PROTECTED] FreeBSD- Turning PC's into workstations ICQ:22838075 Liebe und Hass sind nicht blind, aber geblendet vom Feuer, dass sie selber mit sich tragen. (Nietzsche) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PCI Plug 'n' Pray and old BIOSes
Perhaps all I need to do is toggle the PnP BIOS setting, but before I pull out the screwdrivers and tear the two machines apart again, I'm hoping to draw on someone else's experience here. BTW will setting the PnP BIOS to `enabled' have any effect? It shouldn't in your case, as you're performing your own resource allocation. It's possible that IRQ 12 is a poor choice with your board. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
