For all those QNX support folks:
Story so far: (old thread on this group since 20th May)
The Intel EEPRO100 built into Sony VAIO PCG-Z505HS notebook does not
start up in QNX RTP if the notebook is rebooted from Windows. After a
coldstart it works fine. The “not working” symptom is that the driver
does not find the MMI, reports MAC address as all FF:…:FF and does not
get/send any packets.
New information:
The same behaviour was in Linux 2.2.x kernels. The recent Linux 2.4.x
kernel (RedHat 7.1) works fine.
To fix the problem, you need to do similar changes in the setup as Linux
has done between 2.2.x and 2.4.x (whatever those are).
Hint: Windows reports the Speedo on different addresses than Linux and
QNX. May it be the case that this mapping is still in place, but PCI
BIOS reports the “default” addresses?
Good luck in fixing this.
Petr Novak <Petr.Novak@i.cz>
ICZ a.s. www.i.cz
V Olsinach 75
CZ-100 97 Praha 10
Ph: +420 2 8100 2222
Fax: +420 2 8100 2244
I have similar problems with my father’s Dell desktop model (I forget the
exact model) - basically, he put an Intel NIC in (I forget the designation
now - argh!) and it works fine in Windows, but RTP (Patch A) doesn’t like
it. Whether a warm boot or cold.
“Petr Novak” <Petr.Novak@i.cz> wrote in message
news:3B1CD1C9.70C66EAF@i.cz…
For all those QNX support folks:
Story so far: (old thread on this group since 20th May)
The Intel EEPRO100 built into Sony VAIO PCG-Z505HS notebook does not
start up in QNX RTP if the notebook is rebooted from Windows. After a
coldstart it works fine. The “not working” symptom is that the driver
does not find the MMI, reports MAC address as all FF:…:FF and does not
get/send any packets.
New information:
The same behaviour was in Linux 2.2.x kernels. The recent Linux 2.4.x
kernel (RedHat 7.1) works fine.
To fix the problem, you need to do similar changes in the setup as Linux
has done between 2.2.x and 2.4.x (whatever those are).
Hint: Windows reports the Speedo on different addresses than Linux and
QNX. May it be the case that this mapping is still in place, but PCI
BIOS reports the “default” addresses?
Good luck in fixing this.
Petr Novak <> Petr.Novak@i.cz
ICZ a.s. > www.i.cz
V Olsinach 75
CZ-100 97 Praha 10
Ph: +420 2 8100 2222
Fax: +420 2 8100 2244
I think Windows reassigns PCI resources as it feels desirable, while QNX
simply takes them where BIOS left…
“Petr Novak” <Petr.Novak@i.cz> wrote in message
news:3B1CD1C9.70C66EAF@i.cz…
For all those QNX support folks:
Story so far: (old thread on this group since 20th May)
The Intel EEPRO100 built into Sony VAIO PCG-Z505HS notebook does not
start up in QNX RTP if the notebook is rebooted from Windows. After a
coldstart it works fine. The “not working” symptom is that the driver
does not find the MMI, reports MAC address as all FF:…:FF and does not
get/send any packets.
New information:
The same behaviour was in Linux 2.2.x kernels. The recent Linux 2.4.x
kernel (RedHat 7.1) works fine.
To fix the problem, you need to do similar changes in the setup as Linux
has done between 2.2.x and 2.4.x (whatever those are).
Hint: Windows reports the Speedo on different addresses than Linux and
QNX. May it be the case that this mapping is still in place, but PCI
BIOS reports the “default” addresses?
Good luck in fixing this.
Petr Novak <> Petr.Novak@i.cz
ICZ a.s. > www.i.cz
V Olsinach 75
CZ-100 97 Praha 10
Ph: +420 2 8100 2222
Fax: +420 2 8100 2244