PRO/100 VE on thinkpad R40 is missing PHY - no MII?

I just bought a thinkpad R40, and after updating the default
eepro100 driver in debian woody to a newer version that supports the
Intel PRO/100 VE card it seems that it's working OK.  Except, it seems
that either there is no MII transceiver on this card or the driver can't
find it properly.  This is a problem because I wish to use a program
(laptop-net) which must monitor the link status through MII.
I have include the output from different diagnostic commands, they were
run while the link was up (and working fine).  For any other information
I might have forgotten please ask.  Is it a possibility that this card
just doesn't have a MII transceiver?

thanks in advance for any help.

Below is the driver output from dmesg:

   eth0: Intel Corp. 82801BD PRO/100 VE (MOB) Ethernet Controller,
   00:06:1B:C0:8A:95, IRQ 11.
     Receiver lock-up bug exists -- enabling work-around.
     Board assembly a43917-002, Physical connectors present:
     Primary interface chip None PHY #0.
     General self-test: passed.
     Serial sub-system self-test: passed.
     Internal registers self-test: passed.
     ROM checksum self-test: passed (0x04f4518b).
     Receiver lock-up workaround activated.

the relevant output of 'cat /proc/pci':

    Ethernet controller: Intel Corp. 82801BD PRO/100 VE (MOB) Ethernet
    Controller (rev 131).
    IRQ 11.
    Master Capable.  Latency=66.  Min Gnt=8.Max Lat=56.
    Non-prefetchable 32 bit memory at 0xd0204000
    [0xd0204fff].
    I/O at 0x8000 [0x803f].

Also the output of the eepro100-diag command:

   root@panic:~# eepro100-diag 
   eepro100-diag.c:v2.09 7/15/2002 Donald Becker ([email protected])
    http://www.scyld.com/diag/index.html
    Unable to find a recognized card in /proc/pci.
    If there is a card in the machine, explicitly set the I/O port address
    using '-p <ioaddr> -t <chip_type_index>'
    Use '-t -1' to see the valid chip types.

   root@panic:~# eepro100-diag -p 0x8000
   eepro100-diag.c:v2.09 7/15/2002 Donald Becker ([email protected])
    http://www.scyld.com/diag/index.html
    Assuming a Intel i82557/8/9 EtherExpressPro100 adapter at 0x8000.
    A potential i82557 chip has been found, but it appears to be active.
    Either shutdown the network, or use the '-f' flag.
     Use '-a' or '-aa' to show device registers,
     '-e' to show EEPROM contents, -ee for parsed contents,
     or '-m' or '-mm' to show MII management registers.

   root@panic:~# eepro100-diag -p 0x8000 -f -aaeemm 
   eepro100-diag.c:v2.09 7/15/2002 Donald Becker ([email protected])
    http://www.scyld.com/diag/index.html
   Assuming a Intel i82557/8/9 EtherExpressPro100 adapter at 0x8000.
   i82557 chip registers at 0x8000:
     0c000050 0f516000 00000000 00080002 1801ffff 00000600
     No interrupt sources are pending.
      The transmit unit state is 'Suspended'.
      The receive unit state is 'Ready'.
     This status is normal for an activated but idle interface.
    The Command register has an unprocessed command 0c00(?!).
   EEPROM contents, size 64x16:
       00: 0600 c01b 958a 0000 0000 0000 0000 0000
     0x08: a439 1702 58a2 0522 1014 103d 8086 c844
         ...
     0x20: 0000 0000 0000 103d 0000 0000 0000 0000
         ...
     0x30: 0120 4000 4107 0000 0000 0000 0000 0000
     0x38: 0000 0000 0000 0000 0000 0000 0000 4a97
    The EEPROM checksum is correct.
   Intel EtherExpress Pro 10/100 EEPROM contents:
     Station address 00:06:1B:C0:8A:95.
     Receiver lock-up bug exists. (The driver work-around *is* implemented.)
     Board assembly a43917-002, Physical connectors present:
     Primary interface chip None PHY #0.
      Sleep mode is enabled.  This is not recommended.
      Under high load the card may not respond to
      PCI requests, and thus cause a master abort.
      To clear sleep mode use the '-G 0 -w -w -f' options.
      No MII transceiver present to monitor.

Below is the mii-diag output:

   root@panic:~# mii-diag 
   Using the default interface 'eth0'.
   Basic registers of MII PHY #0:  ffff ffff ffff ffff ffff ffff ffff ffff.
     No MII transceiver present!.
     Use '--force' to view the information anyway.

   root@panic:~# mii-diag --force
   Using the default interface 'eth0'.
   Basic registers of MII PHY #0:  ffff ffff ffff ffff ffff ffff ffff
   ffff.
   No MII transceiver present!.
   The autonegotiated capability is 03e0.
   The autonegotiated media type is 100baseTx-FD.
   Basic mode control register 0xffff: Auto-negotiation enabled.
   Internal Collision-Test enabled!
   Restarted auto-negotiation in progress!
   Transceiver isolated from the MII!
   Transceiver powered down!
   Transceiver in loopback mode!
   Transceiver currently being reset!
   Basic mode status register 0xffff ... ffff.
   Link status: established.
   Remote fault detected!
   *** Link Jabber! ***
   Your link partner advertised ffff:
   Flow-control 100baseT4 100baseTx-FD
   100baseTx 10baseT-FD 10baseT, w/ 802.3X
   flow control.
   End of basic transceiver information.


-- 
___.o._________ ,,_ ____________________________                
 =..'`.     ,","_ '>                         
    `) ) ,"," _  '>                         
     , )//  _   '>                         
   ,'  // _  '>",'  http://www.di.uoa.gr/~stud1242
   (  (/   _'>   '                          
____`. `-"'    ,'swan'_________________________                      
      ``````````