smc12011

Joaquin_Ferruz_Meler · November 14, 2000, 1:22pm

Hello,

I have installed QNX RTP in a desktop PC with a SMC1211 Ethernet
board. The system boots (provided that PnP ISA enumerator is not run)
and
seems to use VGA correctly. However, it is not possible to use the
network
card.

Executing “pci”:

Class Network(Ethernet)
Vendor 1113h Accton Tech. Corporation
Dev ID 1211h Unknown
PCI index 0h
IO 0h (disabled)
PCI Int A
Int. line No connection

In /etc/system/enum/devices/net there is an entry for such Dev Id and
Vendor,
but is associated to Realtek. However, it can be read as a comment “SMC
1211”.
With nettrap start, the driver is identified as “devn-rtl”, but the
message
“io-net cannot init devn-rtl; no such device” is displayed. The same
result is
obtained if io-net is “slayed” and restarted:

/bin/slay io-net
io-net -d rtl -p ttcpip -p pppmgr

It seems strange that there is no such device, when it is correctly
detected by “pci”, and (sort of) identified by nettrap.

How can I use SMC 1211? If it is present in the list of devices, I
should
think that it is supported.

Thanks in advance,

Joaquin Ferruz

Chris_McKillop1 · November 14, 2000, 7:31pm

Joaquin Ferruz Melero <ferruz@cartuja.us.es> wrote:

/bin/slay io-net
io-net -d rtl -p ttcpip -p pppmgr

It seems strange that there is no such device, when it is correctly
detected by “pci”, and (sort of) identified by nettrap.

It is strange. If you could try running with the verbose option…

io-net -d rtp verbose=3 …

and post the results, that would be great.

chris

–

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Joaquin_Ferruz_Meler · November 15, 2000, 10:04am

Chris McKillop wrote:

Joaquin Ferruz Melero <> ferruz@cartuja.us.es> > wrote:
/bin/slay io-net
io-net -d rtl -p ttcpip -p pppmgr

It seems strange that there is no such device, when it is correctly
detected by “pci”, and (sort of) identified by nettrap.

It is strange. If you could try running with the verbose option…

io-net -d rtp verbose=3 …

“-d rtl”, I suppose.

and post the results, that would be great.

chris

–

cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL

Well, I tried this today:

first, slay io-net:

/bin/slay io-net

there are two io-net processes. I have to kill both of them. I
think that
this also happened yesterday.

second, start io-net:

io-net -d rtl verbose=3 -p ttcpip -p pppmgr

now, things do not happen the same way as before; the system ALWAYS
gets hung after a few seconds. And it does not have anything to do with
“verbose”;
I tried to do the same as I did yesterday, but (today…) it keeps hanging
up.

The displayed messages are:

Checking(10ec, 8139) at index 0
" " " 1
…
" " " 10
Checking(1113, 1211) at index 0
rtl(Lan:0): Reset timeout
rtl(Lan:0): Reset timeout

…it usually hangs at this point. However, I have seen a couple of times
the following:

Vendor 0x1113
Device 0x1211
Rev 0x0
I/O port base 0x10000000
Int 0x7
Mac ADDR. dff07df20001

…but this does not prevent the hang up. Other times it’s worse: Photon
exits. In this case, I have seen the following on the text screen:

io-graphics received signal 8 (or something similar)
IP:b04cdab4 set:b04cdab4
symbol ffb_core_blit1e libfffb.so.1 file offset 2978

I list a few potentially useful data:

There are two io-net processes.
All the devices on the PCI have the same index, among them the SB-PCI
sound board which does not work either (I wonder wether this is correct)
If the PnP ISA enumerator is not disabled on boot, the system hangs, just

before a message about swap space should be printed. In other desktop
system I have, this also happened until I managed to install the network

card correctly – then magically ceased to happen.

The board is a P3C2000 from ASUS, with an i820 chipset.
Neither Windows 2000 nor Windows 98 seem to have any problem with
PCI or the Ethernet board. I remember though that W. NT 4.0 did have
some problems to see the PCI boards.

Best regards,

Joaquin
Ferruz

Hugh_Brown1 · November 15, 2000, 6:00pm

Previously, Joaquin Ferruz Melero wrote in qdn.public.qnxrtp.installation:

Chris McKillop wrote:

Joaquin Ferruz Melero <> ferruz@cartuja.us.es> > wrote:
/bin/slay io-net
io-net -d rtl -p ttcpip -p pppmgr

It seems strange that there is no such device, when it is correctly
detected by “pci”, and (sort of) identified by nettrap.

It is strange. If you could try running with the verbose option…

io-net -d rtp verbose=3 …

“-d rtl”, I suppose.

and post the results, that would be great.

chris

Well, I tried this today:

first, slay io-net:

/bin/slay io-net

there are two io-net processes. I have to kill both of them. I
think that
this also happened yesterday.

second, start io-net:

io-net -d rtl verbose=3 -p ttcpip -p pppmgr

now, things do not happen the same way as before; the system ALWAYS
gets hung after a few seconds. And it does not have anything to do with
“verbose”;
I tried to do the same as I did yesterday, but (today…) it keeps hanging
up.

The displayed messages are:

Checking(10ec, 8139) at index 0
" " " 1
…
" " " 10
Checking(1113, 1211) at index 0
rtl(Lan:0): Reset timeout
rtl(Lan:0): Reset timeout

…it usually hangs at this point. However, I have seen a couple of times
the following:

Vendor 0x1113
Device 0x1211
Rev 0x0
I/O port base 0x10000000
^^^^^^^^^^

Are you sure this is correct?

Int 0x7
Mac ADDR. dff07df20001

…but this does not prevent the hang up. Other times it’s worse: Photon
exits. In this case, I have seen the following on the text screen:

io-graphics received signal 8 (or something similar)
IP:b04cdab4 set:b04cdab4
symbol ffb_core_blit1e libfffb.so.1 file offset 2978

I list a few potentially useful data:

There are two io-net processes.

All the devices on the PCI have the same index, among them the SB-PCI
sound board which does not work either (I wonder wether this is correct)

If the PnP ISA enumerator is not disabled on boot, the system hangs, just

before a message about swap space should be printed. In other desktop
system I have, this also happened until I managed to install the network

card correctly – then magically ceased to happen.

The board is a P3C2000 from ASUS, with an i820 chipset.

Neither Windows 2000 nor Windows 98 seem to have any problem with
PCI or the Ethernet board. I remember though that W. NT 4.0 did have
some problems to see the PCI boards.

Best regards,

Joaquin
Ferruz

Please will you do the following:

Exit Photon to a text mode screen
slay -9 io-net
io-net -d rtl verbose=3 -p ttcpip -p pppmgr
pci -v > file
post the output ‘file’

Thanks, Hugh.

–

Hugh Brown (613) 591-0931 ext. 209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8

Joaquin_Ferruz_Meler · November 16, 2000, 9:00am

Hugh Brown wrote:

(…)

The displayed messages are:

Checking(10ec, 8139) at index 0
" " " 1
…
" " " 10
Checking(1113, 1211) at index 0
rtl(Lan:0): Reset timeout
rtl(Lan:0): Reset timeout

…it usually hangs at this point. However, I have seen a couple of times
the following:

Vendor 0x1113
Device 0x1211
Rev 0x0
I/O port base 0x10000000
^^^^^^^^^^
Are you sure this is correct?

Yes, it is the displayed value

Int 0x7
Mac ADDR. dff07df20001

Please will you do the following:

Exit Photon to a text mode screen

slay -9 io-net

io-net -d rtl verbose=3 -p ttcpip -p pppmgr

pci -v > file

post the output ‘file’

Thanks, Hugh.

I tried that several times:

Exit Photon – done
slay -9 io-net – done (two io-net processes, as usual)
io-net -d rtl verbose=3 -p ttcpip -p pppmgr – done
– hang — (always)
I cannot do that…

io-net displays the same; I correct here a few copy errors:

Checking(10ec, 8139) at index 0
" " " 1
…
" " " 10
Checking(1113, 1211) at index 0
rtl(Lan:0): Reset timeout
rtl(Lan:0): Reset timeout
Realtek(SMC-1211) – now, it knows which board!
Vendor 0x1113
Device 0x1211
Rev 0x0
I/O port base 0x10000000 – yes, this value…
Int 0x7
Mac ADDR. fff07bfa0001

I even tried:

io-net -d rtl verbose=3 -p ttcpip -p pppmgr; pci -v > file

or

io-net -d rtl verbose=3 -p ttcpip -p pppmgr > file1; pci -v > file2

but I only got empty files or corrupt files (“Corrupt file system detected…”)

Best regards,

Joaquin Ferruz

Hugh_Brown1 · November 16, 2000, 1:23pm

Previously, Joaquin Ferruz Melero wrote in qdn.public.qnxrtp.installation:

Hugh Brown wrote:

(…)

The displayed messages are:

Checking(10ec, 8139) at index 0
" " " 1
…
" " " 10
Checking(1113, 1211) at index 0
rtl(Lan:0): Reset timeout
rtl(Lan:0): Reset timeout

…it usually hangs at this point. However, I have seen a couple of times
the following:

Vendor 0x1113
Device 0x1211
Rev 0x0
I/O port base 0x10000000
^^^^^^^^^^
Are you sure this is correct?

Yes, it is the displayed value

I tried that several times:

Exit Photon – done

slay -9 io-net – done (two io-net processes, as usual)

io-net -d rtl verbose=3 -p ttcpip -p pppmgr – done
– hang — (always)

I cannot do that…

io-net displays the same; I correct here a few copy errors:

Please post the output of ‘pci -v’ after you have re-booted the
machine and before your start the network driver.

Thanks, Hugh.

Checking(10ec, 8139) at index 0
" " " 1
…
" " " 10
Checking(1113, 1211) at index 0
rtl(Lan:0): Reset timeout
rtl(Lan:0): Reset timeout
Realtek(SMC-1211) – now, it knows which board!
Vendor 0x1113
Device 0x1211
Rev 0x0
I/O port base 0x10000000 – yes, this value…
Int 0x7
Mac ADDR. fff07bfa0001

I even tried:

io-net -d rtl verbose=3 -p ttcpip -p pppmgr; pci -v > file

or

io-net -d rtl verbose=3 -p ttcpip -p pppmgr > file1; pci -v > file2

but I only got empty files or corrupt files (“Corrupt file system detected…”)

Best regards,

Joaquin Ferruz

–

Hugh Brown (613) 591-0931 ext. 209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8

Joaquin_Ferruz_Meler · November 17, 2000, 12:02pm

Hugh Brown wrote:

Please post the output of ‘pci -v’ after you have re-booted the
machine and before your start the network driver.

There is what pci -v displays after boot in Photon; if I exit Photon and
enter text mode, it is the same (as expected, I suppose):

PCI version = 2.10

Class = Bridge (Host/PCI)
Vendor ID = 8086h, Intel Corporation
Device ID = 2501h, Unknown Unknown
PCI index = 0h
Class Codes = 060000h
Revision ID = 3h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 2010h
Command Reg = 106h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Subsystem Vendor ID = 1043h
Subsystem ID = 801ch
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0
Capabilities Pointer = a0h
Capability ID = 2h
Capabilities = 20h - 1f000213h

Class = Bridge (PCI/PCI)
Vendor ID = 8086h, Intel Corporation
Device ID = 250fh, 82820 AGP Bridge
PCI index = 0h
Class Codes = 060400h
Revision ID = 3h
Bus number = 0
Device number = 1
Function num = 0
Status Reg = 20h
Command Reg = 107h
Header type = 1h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Primary Bus Number = 0h
Secondary Bus Number = 1h
Subordinate Bus Number = 1h
Secondary Latency Timer = 40h
I/O Base = d0h
I/O Limit = d0h
Secondary Status = 22a0h
Memory Base = cd80h
Memory Limit = cfe0h
Prefetchable Memory Base = cff0h
Prefetchable Memory Limit= cff0h
Prefetchable Base Upper 32 Bits = 0h
Prefetchable Limit Upper 32 Bits = 0h
I/O Base Upper 16 Bits = 0h
I/O Limit Upper 16 Bits = 0h
Bridge Control = 8ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (PCI/PCI)
Vendor ID = 8086h, Intel Corporation
Device ID = 2418h, 82801AA Hub Interface-to-PCI Bridge
PCI index = 0h
Class Codes = 060400h
Revision ID = 2h
Bus number = 0
Device number = 30
Function num = 0
Status Reg = 80h
Command Reg = 107h
Header type = 1h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Primary Bus Number = 0h
Secondary Bus Number = 2h
Subordinate Bus Number = 2h
Secondary Latency Timer = 20h
I/O Base = b0h
I/O Limit = b0h
Secondary Status = 2280h
Memory Base = cd00h
Memory Limit = cd70h
Prefetchable Memory Base = cff0h
Prefetchable Memory Limit= cfe0h
Prefetchable Base Upper 32 Bits = 0h
Prefetchable Limit Upper 32 Bits = 0h
I/O Base Upper 16 Bits = 0h
I/O Limit Upper 16 Bits = 0h
Bridge Control = 6ns
PCI Int Pin = NC
Interrupt line = 0

Class = Bridge (PCI/ISA)
Vendor ID = 8086h, Intel Corporation
Device ID = 2410h, 82801AA LPC Interface
PCI index = 0h
Class Codes = 060100h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 0
Status Reg = 280h
Command Reg = 10fh
Header type = 0h Multi-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Mass Storage (IDE)
Vendor ID = 8086h, Intel Corporation
Device ID = 2411h, 82801AA IDE Controller
PCI index = 0h
Class Codes = 010180h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 1
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
IO Address = a800h length 16 enabled
Subsystem Vendor ID = 8086h
Subsystem ID = 2411h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = NC
Interrupt line = 0

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 2412h, 82801AA USB Controller
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 2
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
IO Address = a400h length 32 enabled
Subsystem Vendor ID = 8086h
Subsystem ID = 2412h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 9

Class = Serial Bus (SMBus)
Vendor ID = 8086h, Intel Corporation
Device ID = 2413h, 82801AA SMBus Controller
PCI index = 0h
Class Codes = 0c0500h
Revision ID = 2h
Bus number = 0
Device number = 31
Function num = 3
Status Reg = 280h
Command Reg = 1h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h
IO Address = e800h length 16 enabled
Subsystem Vendor ID = 8086h
Subsystem ID = 2413h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT B
Interrupt line = 10

Class = Display (VGA)
Vendor ID = 1002h, ATI Technologies
Device ID = 4c42h, Unknown Unknown
PCI index = 0h
Class Codes = 030000h
Revision ID = dch
Bus number = 1
Device number = 0
Function num = 0
Status Reg = 290h
Command Reg = 87h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
Mem Address = ce000000h 32bit length 16777216 enabled
IO Address = d800h length 256 enabled
Mem Address = cd800000h 32bit length 4096 enabled
Subsystem Vendor ID = 1002h
Subsystem ID = 44h
Expansion ROM = cffe0000h length 131072 disabled
Max Lat = 0ns
Min Gnt = 8ns
PCI Int Pin = INT A
Interrupt line = 11
Capabilities Pointer = 50h
Capability ID = 2h
Capabilities = 10h - ff000203h
Capability ID = 1h
Capabilities = 601h - 0h

Class = Network (Ethernet)
Vendor ID = 1113h, Accton Technology Corporation
Device ID = 1211h, Unknown Unknown
PCI index = 0h
Class Codes = 020000h
Revision ID = 10h
Bus number = 2
Device number = 9
Function num = 0
Status Reg = 290h
Command Reg = 4h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
IO Address = 0h length 256 disabled
Subsystem Vendor ID = 1113h
Subsystem ID = 1211h
Max Lat = 64ns
Min Gnt = 32ns
PCI Int Pin = INT A
Interrupt line = no connection
Capabilities Pointer = 50h
Capability ID = 1h
Capabilities = ffc2h - 0h

Class = Multimedia (Audio)
Vendor ID = 1274h, Ensoniq
Device ID = 1371h, ES1371 AudioPCI
PCI index = 0h
Class Codes = 040100h
Revision ID = 8h
Bus number = 2
Device number = 11
Function num = 0
Status Reg = 410h
Command Reg = 4h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
IO Address = 0h length 64 disabled
Subsystem Vendor ID = 1274h
Subsystem ID = 1371h
Max Lat = 128ns
Min Gnt = 12ns
PCI Int Pin = INT A
Interrupt line = no connection
Capabilities Pointer = dch
Capability ID = 1h
Capabilities = 421h - 3h

…and this is the output after /bin/slay io-net (the same, if I am not mistaken):

PCI version = 2.10