<firstname.lastname@example.org> wrote in message news:email@example.com…
So I’ve got an Intel 8255x NIC plugged into a Motorola cable modem
through Road Runner. I get told that there’s no response from the MII
transceiver. Eh? Even after a nice crisp cold reboot, no go. The card
detected 100% by nettrap. No problem there. As far as I know,
is detected just spiffy. I slay io-net and run it again, making sure of
the parameters I am sure of, and I still get the same error.
Try not rebooting so crisply. Sometimes a slushier reboot is preferred.
Well, the first time I tried, while the 25M version of QNX was
downloading for Windows I was looking around in the Knowledge Center (I
think it’s called?) looking up all the info I could on setting up a cable
modem through a standard NIC (RR originally installed it through USB…
Hah!). Copied down all the info I could find (love winipcfg for that), and
entered it as I could when I rebooted into QNX. Like I said, nettrap finds
it fine, io-net starts, but it tells me that it can’t find the MII
transceiver. Is this a driver issue, perhaps? So, a reboot out of Win98
into QNX or a cold boot straight into QNX (BIOS setting PnP OS set to NO,
like so many posts say to do), and it won’t go. It’s like the system
finds the card, but it won’t talk to it.
Your hostname is just the part. Your email address has very
little to do with your hostname.
Huh, okay, that’s cool. If I recall, it’s something we entered just for
our LAN; I don’t recall RR giving us a hostname. But the only thing I can
find is that.
It could be that (as far as it’s concerned) the dhcp.client does
it’s job instantly and goes away before you can run `ps’.
So, how come when I first boot in, dhcp.client is there, but when I slay
and attempt to restart it, it’s gone?
I’m configured static now, but I seem to remember when I was
using it, it would come up, do it’s job, and then go away. If things
weren’t tiggety-boo with the NIC, it would hang around for a while and
‘tiggety-boo’? Care to elaborate?
So, technically, if dhcp.client works right, it shouldn’t pop up in
‘ps’. So if upon bootup I’m seeing it, something’s wrong?
Erf. I’m not used to being so… helpless. In Windows, I at least know
where to go and what to change to TRY and make things work. In QNX, I’m
lost. Could this possibly be a symptom of IRQ conflict? (I’m not a
hardware guy; I’m a software guy. My father’s the hardware guy.) How can I
tell what devices are taking what IO ranges and IRQs in QNX?