Re: eth0: PHY id 0x00221619 is not supported! HELP
From: Clemens Koller <hidden>
Date: 2005-05-13 15:39:12
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
Attachments
- gianfar.diff [text/x-diff] 1469 bytes · preview