eth0: PHY id 0x00221619 is not supported! HELP

eth0: PHY id 0x00221619 is not supported! HELP

[Garcia Jérémie]

Hi everybody,
We are developping a custom board which uses a ppc405EP and on which one =
we'd like to load a linux hardhat.
During the boot process, we're getting error messages about the ethernet =
PHY. That is really annoying cause we plan to moubnt the file system via =
nfs. So no ethernet no NFS...
Could someone give us a tip and tell us if the messages displayed before =
seem to be normal cause we had to modify some part of the kernel in =
order to get Linux booting.
What those ethernet messages mean? Everythin seems to happen in the =
"ibm_ocp_enet.c" eand "ibm_ocp_phy.c" filesPlease help....
So here we go ---->>>>>>>>>

Linux/PPC load: console=3DttyS0,19200 root=3D/dev/nfs rw ip=3Don
Uncompressing Linux...done.
Now booting the kernel
Linux version 2.4.20_mvl31-405ep_eval =
(root@sop-dhcp-10-16-5-126.amcc.com) (version gcc 3.3.1 (MontaVista =
3.3.1-3.0.10.0300532 2003-12-24)) #26 ven mai 13 5
AMCC Q80G Board
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=3DttyS0,19200 root=3D/dev/nfs rw ip=3Don
hr_time_init: arch_to_nsec =3D 10485759, nsec_to_arch =3D 858993476
Calibrating delay loop... 199.47 BogoMIPS
Memory: 14416k available (1280k kernel code, 424k data, 64k init, 0k =
highmem)
Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
OCP uart ver 1.6.2 init complete
LSP Revision 1
ikconfig 0.5 with /proc/ikconfig
Starting kswapd
Disabling the Out Of Memory Killer
JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis =
Communications AB.
i2c-core.o: i2c core module version 2.6.2 (20011118)
i2c-dev.o: i2c /dev entries driver module version 2.6.2 (20011118)
i2c-proc.o version 2.6.2 (20011118)
pty: 256 Unix98 ptys configured
eeprom.o version 2.6.2 (20011118)
Serial driver version 5.05c (2001-07-08) with no serial options enabled
ttyS00 at 0xef600300 (irq =3D 0) is a 16550A
ttyS01 at 0xef600400 (irq =3D 1) is a 16550A
IBM gpio driver version 07.25.02
GPIO #0 at 0xc207d700
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
eth0: PHY id 0x00221619 is not supported!
eth0: PHY id 0x00221619 is not supported!
eth0: No PHY device found.
removing net dev
eth0: PHY id 0x00221619 is not supported!
eth0: PHY id 0x00221619 is not supported!
eth0: No PHY device found.
removing net dev
IBM IIC driver v2.0
ibm-iic: using compatibility value for OPB freq, fix your board specific =
setup
ibm-iic0: using standard (100 kHz) mode
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMPIP: routing cache hash table of 512 =
buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048)
IP-Config: No network devices available.
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
kmod: failed to exec /sbin/modprobe -s -k block-major-2, errno =3D 2
VFS: Cannot open root device "nfs" or 02:00
Please append a correct "root=3D" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00
 <0>Rebooting in 180 seconds..


Tks a lot for your precious help
Dj=E9

Re: eth0: PHY id 0x00221619 is not supported! HELP

[Clemens Koller]

[-- Attachment #1: Type: text/plain, Size: 4575 bytes --]

Hi, Garcia!

Well, it's usually not a big deal to add your phyid to the driver.
Maybe some generic support is sufficient for your needs.
Check the datasheet of your Board and the PHY.
When you are sure you use an unsupported PHY, read the *phy.c of
your driver and add it. YMMV

Just FYI, I attached a (quick and dirty) patch to add an Intel LXT971 PHY to
the gianfar driver. The LXT981 is a 100Mbit PHY on the gigabit capable TSEC
of a mpc8540 cpu.

Greets,

Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19

Garcia Jérémie wrote:
> Hi everybody,
> We are developping a custom board which uses a ppc405EP and on which one we'd like to load a linux hardhat.
> During the boot process, we're getting error messages about the ethernet PHY. That is really annoying cause we plan to moubnt the file system via nfs. So no ethernet no NFS...
> Could someone give us a tip and tell us if the messages displayed before seem to be normal cause we had to modify some part of the kernel in order to get Linux booting.
> What those ethernet messages mean? Everythin seems to happen in the "ibm_ocp_enet.c" eand "ibm_ocp_phy.c" filesPlease help....
> So here we go ---->>>>>>>>>
> 
> Linux/PPC load: console=ttyS0,19200 root=/dev/nfs rw ip=on
> Uncompressing Linux...done.
> Now booting the kernel
> Linux version 2.4.20_mvl31-405ep_eval (root@sop-dhcp-10-16-5-126.amcc.com) (version gcc 3.3.1 (MontaVista 3.3.1-3.0.10.0300532 2003-12-24)) #26 ven mai 13 5
> AMCC Q80G Board
> On node 0 totalpages: 4096
> zone(0): 4096 pages.
> zone(1): 0 pages.
> zone(2): 0 pages.
> Kernel command line: console=ttyS0,19200 root=/dev/nfs rw ip=on
> hr_time_init: arch_to_nsec = 10485759, nsec_to_arch = 858993476
> Calibrating delay loop... 199.47 BogoMIPS
> Memory: 14416k available (1280k kernel code, 424k data, 64k init, 0k highmem)
> Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
> Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> OCP uart ver 1.6.2 init complete
> LSP Revision 1
> ikconfig 0.5 with /proc/ikconfig
> Starting kswapd
> Disabling the Out Of Memory Killer
> JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis Communications AB.
> i2c-core.o: i2c core module version 2.6.2 (20011118)
> i2c-dev.o: i2c /dev entries driver module version 2.6.2 (20011118)
> i2c-proc.o version 2.6.2 (20011118)
> pty: 256 Unix98 ptys configured
> eeprom.o version 2.6.2 (20011118)
> Serial driver version 5.05c (2001-07-08) with no serial options enabled
> ttyS00 at 0xef600300 (irq = 0) is a 16550A
> ttyS01 at 0xef600400 (irq = 1) is a 16550A
> IBM gpio driver version 07.25.02
> GPIO #0 at 0xc207d700
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> loop: loaded (max 8 devices)
> eth0: PHY id 0x00221619 is not supported!
> eth0: PHY id 0x00221619 is not supported!
> eth0: No PHY device found.
> removing net dev
> eth0: PHY id 0x00221619 is not supported!
> eth0: PHY id 0x00221619 is not supported!
> eth0: No PHY device found.
> removing net dev
> IBM IIC driver v2.0
> ibm-iic: using compatibility value for OPB freq, fix your board specific setup
> ibm-iic0: using standard (100 kHz) mode
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMPIP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 1024 bind 2048)
> IP-Config: No network devices available.
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> Root-NFS: No NFS server available, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> kmod: failed to exec /sbin/modprobe -s -k block-major-2, errno = 2
> VFS: Cannot open root device "nfs" or 02:00
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 02:00
>  <0>Rebooting in 180 seconds..
> 
> 
> Tks a lot for your precious help
> Djé
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 

[-- Attachment #2: gianfar.diff --]
[-- Type: text/x-diff, Size: 1469 bytes --]

diff -Nur --exclude-from=exclude-files linux-2.6.11-clean/drivers/net/gianfar.h linux/drivers/net/gianfar.h
--- linux-2.6.11-clean/drivers/net/gianfar.h	2005-03-02 02:38:25.000000000 -0500
+++ linux/drivers/net/gianfar.h	2005-03-04 19:19:43.000000000 -0500
@@ -131,7 +131,9 @@
 #define MACCFG1_SYNCD_TX_EN	0x00000002
 #define MACCFG1_TX_EN		0x00000001
 
-#define MACCFG2_INIT_SETTINGS	0x00007205
+/* #define MACCFG2_INIT_SETTINGS	0x00007205*/
+/* CK--- changed to use MII instead of GMII */
+#define MACCFG2_INIT_SETTINGS	0x00007105
 #define MACCFG2_FULL_DUPLEX	0x00000001
 #define MACCFG2_IF              0x00000300
 #define MACCFG2_MII             0x00000100
diff -Nur --exclude-from=exclude-files linux-2.6.11-clean/drivers/net/gianfar_phy.c linux/drivers/net/gianfar_phy.c
--- linux-2.6.11-clean/drivers/net/gianfar_phy.c	2005-03-02 02:38:09.000000000 -0500
+++ linux/drivers/net/gianfar_phy.c	2005-03-04 18:24:54.000000000 -0500
@@ -580,6 +580,15 @@
 	.config_intr	= &marvell_config_intr,
 };
 
+static struct phy_info phy_info_lxt971 = {
+	.phy_id		= 0x001378e0,
+	.phy_id_mask	= 0xfffffff0,
+	.name		= "Intel LXT971",
+	.features	= MII_BASIC_FEATURES,
+	.config_aneg	= genmii_config_aneg,
+	.read_status	= genmii_read_status,
+};
+
 static struct phy_info phy_info_genmii= {
 	.phy_id		= 0x00000000,
 	.phy_id_mask	= 0x00000000,
@@ -593,6 +602,7 @@
 	&phy_info_cis820x,
 	&phy_info_marvell,
 	&phy_info_dm9161,
+	&phy_info_lxt971,
 	&phy_info_genmii,
 	NULL
 };

RE: eth0: PHY id 0x00221619 is not supported! HELP

[Nghiem, Tien]

Hi Garcia,

In the ibm_ocp_phy.c file, the function mii_phy_probe(struct mii_phy =
*phy, int mii_id) has not found the ID of your ethernet transceiver, so =
you can bypass it by doing the following:

         int rc;
         u32 id;
         struct mii_phy_def* def;
         int i;
       =20
         phy->autoneg =3D 0;
         phy->advertising =3D 0;
         phy->mii_id =3D mii_id;
         phy->speed =3D 0;
         phy->duplex =3D 0;
         phy->pause =3D 0;
        =20
        /* Take PHY out of isloate mode and reset it. */
         rc =3D reset_one_mii_phy(phy, mii_id);
        //if (rc)
        //        return -ENODEV;
=20
        /* Read ID and find matching entry */  =20
        //id =3D (phy_read(phy, MII_PHYSID1) << 16 | phy_read(phy, =
MII_PHYSID2))
                                 & 0xfffffff0;
        //for (i=3D0; (def =3D mii_phy_table[i]) !=3D NULL; i++)
        //        if ((id & def->phy_id_mask) =3D=3D def->phy_id)
        //                break;
       =20
        def =3D mii_phy_table[0];
           =20
        /* Should never be NULL (we have a generic entry), but... */
         if (def =3D=3D NULL)
                return -ENODEV;
=20
         phy->def =3D def;

         /* Setup default advertising */
         phy->advertising =3D def->features;
=20
         return 0;

I don't know the PPC 405EP, but I did it for my custom board (MPC8260). =
It should work.

Tien


-----Original Message-----
From: linuxppc-dev-bounces@ozlabs.org
[mailto:linuxppc-dev-bounces@ozlabs.org]On Behalf Of Garcia J=E9r=E9mie
Sent: Friday, May 13, 2005 11:15 AM
To: linuxppc-dev@ozlabs.org
Subject: eth0: PHY id 0x00221619 is not supported! HELP


Hi everybody,
We are developping a custom board which uses a ppc405EP and on which one =
we'd like to load a linux hardhat.
During the boot process, we're getting error messages about the ethernet =
PHY. That is really annoying cause we plan to moubnt the file system via =
nfs. So no ethernet no NFS...
Could someone give us a tip and tell us if the messages displayed before =
seem to be normal cause we had to modify some part of the kernel in =
order to get Linux booting.
What those ethernet messages mean? Everythin seems to happen in the =
"ibm_ocp_enet.c" eand "ibm_ocp_phy.c" filesPlease help....
So here we go ---->>>>>>>>>

Linux/PPC load: console=3DttyS0,19200 root=3D/dev/nfs rw ip=3Don
Uncompressing Linux...done.
Now booting the kernel
Linux version 2.4.20_mvl31-405ep_eval =
(root@sop-dhcp-10-16-5-126.amcc.com) (version gcc 3.3.1 (MontaVista =
3.3.1-3.0.10.0300532 2003-12-24)) #26 ven mai 13 5
AMCC Q80G Board
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=3DttyS0,19200 root=3D/dev/nfs rw ip=3Don
hr_time_init: arch_to_nsec =3D 10485759, nsec_to_arch =3D 858993476
Calibrating delay loop... 199.47 BogoMIPS
Memory: 14416k available (1280k kernel code, 424k data, 64k init, 0k =
highmem)
Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
OCP uart ver 1.6.2 init complete
LSP Revision 1
ikconfig 0.5 with /proc/ikconfig
Starting kswapd
Disabling the Out Of Memory Killer
JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis =
Communications AB.
i2c-core.o: i2c core module version 2.6.2 (20011118)
i2c-dev.o: i2c /dev entries driver module version 2.6.2 (20011118)
i2c-proc.o version 2.6.2 (20011118)
pty: 256 Unix98 ptys configured
eeprom.o version 2.6.2 (20011118)
Serial driver version 5.05c (2001-07-08) with no serial options enabled
ttyS00 at 0xef600300 (irq =3D 0) is a 16550A
ttyS01 at 0xef600400 (irq =3D 1) is a 16550A
IBM gpio driver version 07.25.02
GPIO #0 at 0xc207d700
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
eth0: PHY id 0x00221619 is not supported!
eth0: PHY id 0x00221619 is not supported!
eth0: No PHY device found.
removing net dev
eth0: PHY id 0x00221619 is not supported!
eth0: PHY id 0x00221619 is not supported!
eth0: No PHY device found.
removing net dev
IBM IIC driver v2.0
ibm-iic: using compatibility value for OPB freq, fix your board specific =
setup
ibm-iic0: using standard (100 kHz) mode
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMPIP: routing cache hash table of 512 =
buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048)
IP-Config: No network devices available.
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
kmod: failed to exec /sbin/modprobe -s -k block-major-2, errno =3D 2
VFS: Cannot open root device "nfs" or 02:00
Please append a correct "root=3D" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00
 <0>Rebooting in 180 seconds..


Tks a lot for your precious help
Dj=E9
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

Re: eth0: PHY id 0x00221619 is not supported! HELP

[Colin Leroy]

On 13 May 2005 at 14h05, Nghiem, Tien wrote:

Hi, 

>          rc = reset_one_mii_phy(phy, mii_id);
>         //if (rc)
>         //        return -ENODEV;

Why disabling such guards?

>         //for (i=0; (def = mii_phy_table[i]) != NULL; i++)
>         //        if ((id & def->phy_id_mask) == def->phy_id)
>         //                break;

Just an idea, I guess it'd be far more clean to add the phy id to
mii_phy_table[] (and, optionally, send the patch so you won't have to
do it everytime).

You're just asking for breakage there.
-- 
Colin

RE: eth0: PHY id 0x00221619 is not supported! HELP

[Nghiem, Tien]

Hi Colin,

I worked on a project 2 years ago, and the hardware supplier decided to
change the tranceiver twice during the course of the project.  So =
instead of modifying the mii_phy_table
each time the transeiver was changed, I bypassed the id check. =20

I did this because I doubt that in the future people are going to be =
interested in updating software, and delivering a new s/w version when a =
hardware fix is performed.

It's not clean, but it's easy and convenient.
This is just a suggestion of mine for a quick fix.

Tien

-----Original Message-----
From: Colin Leroy [mailto:colin@colino.net]
Sent: Friday, May 13, 2005 3:31 PM
To: Nghiem, Tien
Cc: Garcia J=E9r=E9mie; linuxppc-dev@ozlabs.org
Subject: Re: eth0: PHY id 0x00221619 is not supported! HELP


On 13 May 2005 at 14h05, Nghiem, Tien wrote:

Hi,=20

>          rc =3D reset_one_mii_phy(phy, mii_id);
>         //if (rc)
>         //        return -ENODEV;

Why disabling such guards?

>         //for (i=3D0; (def =3D mii_phy_table[i]) !=3D NULL; i++)
>         //        if ((id & def->phy_id_mask) =3D=3D def->phy_id)
>         //                break;

Just an idea, I guess it'd be far more clean to add the phy id to
mii_phy_table[] (and, optionally, send the patch so you won't have to
do it everytime).

You're just asking for breakage there.
--=20
Colin