[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel 2.2 and 2.4: boot differences?



Thanks,  I had already seen in dmesg and ifconfig that the ethernet
was configured.  There is a difference that I had not thought
consequential:

with 2.2.20 I get 

eth0: Accton EN1217/EN2242 (ADMtek Comet) rev 17 at 0xc6022000, 00:D0:59:24:04:C0, IRQ 11.
eth0:  MII transceiver #1 config 3000 status 786d advertising 01e1.

whereas with 2.4.18 I get

eth0: ADMtek Comet rev 17 at 0x1c00, 00:D0:59:24:04:C0, IRQ 11.

Either way ifconfig says I have eth0 configured bid I NOW NOTICE that
the base address reported by ifconfig is not the same.  Perhaps the
driver for 2.4.18 got it wrong?  How can I force 2.4.18 to use the
other driver?

J Adrian Zimmer
   www.ossm.edu/~azimmer
   azimmer --dot-- ossm.edu


>>> Ron Johnson <ron.l.johnson@cox.net> 07/28/03 04:07PM >>>
On Mon, 2003-07-28 at 15:46, Adrian Zimmer wrote:
> I have version 2.2.20  (idepci downloaded) running OK (at runlevel 2).    
> 
> I have version 2.4.18 (compiled myself under 2.2.20) running sort-of OK
> (again runlevel 2).
> 
> One difference is that my self-configured/compiled version isn't establishing a network connection.  Here are my thoughts as to why --
> my thinking isn't good enough yet:
> 
> Something is different about the way these are booting up.  Since
> I see no error messages in /var/log/dmesg (or nothing I recognized as
> an error message) and since the same /etc configuration files are
> being used,  I'm thinking the difference must come from tests of things 
> in the /proc system.  So grep for "/proc" within the files found in 

First thing is:
$ dmesg|grep -n eth

For example, here's my output:
$ dmesg|grep -n eth
233:eth0: VIA VT86C100A Rhine at 0xa000, 00:80:c8:e9:a7:b8, IRQ 4.
234:eth0: MII PHY found at address 8, status 0x782d advertising 05e1
          Link 4de1.
275:eth0: Setting full-duplex based on MII #8 link partner capability
          of 4de1.

Another good preliminary diagnostic tool is lspci and it's "-v"
option.  In my case:
$ lspci | grep [eE]ther
00:0a.0 Ethernet controller: VIA Technologies, Inc. VT86C100A 
        [Rhine] (rev 06)
$ lspci -v -s 00:0a.0
00:0a.0 Ethernet controller: VIA Technologies, Inc. VT86C100A 
        [Rhine] (rev 06)
        Subsystem: D-Link System Inc DFE-530TX rev A
        Flags: bus master, stepping, medium devsel, latency 32, IRQ 4
        I/O ports at a000 [size=128]
        Memory at df000000 (32-bit, non-prefetchable) [size=128]
        Expansion ROM at <unassigned> [disabled] [size=64K]

Ron
-- 
+-----------------------------------------------------------------+
| Ron Johnson, Jr.        Home: ron.l.johnson@cox.net             |
| Jefferson, LA  USA                                              |
|                                                                 |
| "I'm not a vegetarian because I love animals, I'm a vegetarian  |
|  because I hate vegetables!"                                    |
|    unknown                                                      |
+-----------------------------------------------------------------+



-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org 




Reply to: