2008-05-19 05:39:09 PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vincent Puig (SPAIN)
Message: 56006
Hi all.
When I boot the image:
## Starting application at 0x0015a000 ...
Linux version 2.6.22.18-ADI-2008R1-svn (vincent@canutet) (gcc version 4.1.2 (ADI svn)) #17 Mon May 19 11:24:08 CEST 2008
Hardware Trace Active and Enabled
Warning: limiting memory to 26MB due to hardware anomaly 05000263
Blackfin support (C) 2004-2007 Analog Devices, Inc.
Compiled for ADSP-BF537 Rev 0.2
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 500 MHz core clock and 100 MHz System Clock
Board Memory: 32MB
Kernel Managed Memory: 32MB
Memory map:
text = 0x00001000-0x00116070
rodata = 0x00117000-0x00149db8
data = 0x0014a000-0x0015a000
stack = 0x0014a000-0x0014c000
init = 0x0015a000-0x0016e000
bss = 0x0016e000-0x0017e064
available = 0x0017e064-0x01a00000
rootfs = 0x01a00000-0x01f00000
DMA Zone = 0x01f00000-0x02000000
Instruction Cache Enabled
Data Cache Enabled (write-through)
Built 1 zonelists. Total pages: 6604
Kernel command line: root=/dev/mtdblock0 rw ip=xxx:CM_BF537:eth0:off console=ttyBF0,115200
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 128 (order: 7, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory available: 24796k/32768k RAM, (80k init code, 1108k kernel code, 336k data, 1024k dma, 5424k reserved)
Blackfin Scratchpad data SRAM: 4 KB
Blackfin Data A SRAM: 16 KB (9 KB free)
Blackfin Data B SRAM: 16 KB (16 KB free)
Blackfin Instruction SRAM: 48 KB (40 KB free)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
cm_bf537_init(): registering device resources
Generic PHY: Registered new driver
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
io scheduler noop registered (default)
io scheduler cfq registered
pfx: pfbits driver for bf5xx
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART
bfin-uart.1: ttyBF1 at MMIO 0xffc02000 (irq = 20) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
bfin_mac_mdio: probed
bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=19)@sclk=100MHz)
bfin_mac: Version 1.1, Blackfin BF53[67] BF527 on-chip Ethernet MAC driver
uclinux[mtd]: RAM probe address=0x1a00000 size=0x500000
Creating 1 MTD partitions on "RAM":
0x00000000-0x00500000 : "ROMfs"
bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, dma channel@7
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Complete:
device=eth0, addr=192.168.0.180, mask=255.255.255.0, gw==192.168.0.152,
host=CM_BF537, domain=, nis-domain=(none),
bootserver=192.168.0.135, rootserver=192.168.0.135, rootpath=
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 80k freed
dma_alloc_init: dma_page @ 0x0015a000 - 256 pages at 0x01f00000
root:/> PHY: 0:01 - Link is Up - 100/Full
root:/>
Why does this message appear?
Anyway, I still have a telnet problem. When I try to telnet to the target, it gives me:
Trying 192.168.0.180...
Connected to 192.168.0.180.
Escape character is '^]'.
telnetd: All network ports in use.
Connection closed by foreign host.
why is it?
QuoteReplyEditDelete
2008-05-19 10:39:13 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Robin Getz (UNITED STATES)
Message: 56015
Vincent:
You get the "Link up" message, since you told the kernel to configure the network, with the bootargs "ip=xxx" in U-Boot.
As for the "ports in use" error, check the faq:
https://docs.blackfin.uclinux.org/doku.php?id=faq
"How do I allow more telnet sessions".
-Robin
QuoteReplyEditDelete
2008-05-20 04:19:22 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vincent Puig (SPAIN)
Message: 56040
My u-boot variables:
baudrate=115200
loads_echo=1
ethaddr=02:80:ad:20:31:b8
ramboot=tftpboot 0x1000000 linux;run ramargs;run addip;bootelf
nfsboot=tftp 0x1000000 linux;run nfsargs;run addip;bootelf
flashboot=bootm 0x20040000
nfsargs=set bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)
ramargs=set bootargs root=/dev/mtdblock0 rw
flashargs=set bootargs root=/dev/mtdblock2 rw rootfstype=jffs2
ramargs2=set bootargs root=/dev/mtdblock0 rw,no_root_squash
rootpath=/home/vincent/uClinux-dist-2008R1-RC8/rootfs
update=tftpboot 0x1000000 u-boot.bin;protect off 0x20000000 0x2007FFFF;erase 0x20000000 0x2007FFFF;cp.b 0x1000000 0x20000000 $(filesize)
bootcmd=run ramboot
bootdelay=2
fileaddr=1000000
netmask=255.255.255.0
gateway=192.168.0.152
ipaddr=192.168.0.180
serverip=192.168.0.135
addip=set bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gateway}:${netmask} :${hostname}::off console=ttyBF0,115200
stdin=serial
stdout=serial
stderr=serial
However, that is not the most importat problem I have.
I followed the faq and I think it's a poblem about mounting the devpts pseudo filesystem on /dev/pts. If I do "mount":
root:/> mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
proc on /proc type proc (rw)
ramfs on /var type ramfs (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw)
But then in dev/pts/ there is nothing, is it correct?, What am I doing wrong?
I've also allowed more telnet sessions, but I still can not connect to the target with telnet.
QuoteReplyEditDelete
2008-05-20 05:43:52 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vincent Puig (SPAIN)
Message: 56046
If I change addip:
addip=set bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gateway}:${netmask} :${hostname}:eth0:off console=ttyBF0,115200
Then I don't get the PHY message when I boot, and when I telnet I see:
telnet: Unable to connect to remote host: No route to host
--------------------------------
It doesn't happen again, silly mistake, I forgot to add the gateway ip.
But I still have the main problem, I can not connect to the target with telnet, all network port in use, why does it happen?.
Inside /dev/
root:/dev> ls
console null ram10 ram14 ram4 ram8
mtd0 pts ram11 ram15 ram5 ram9
mtd0ro ram0 ram12 ram2 ram6 root
mtdblock0 ram1 ram13 ram3 ram7 zero
I don't have /dev/ptmx, could it be the problem?.
Furthermore, I have to disable the console, but if console=null, it doesn't work:
bootargs=root=/dev/mtdblock0 rw console=null ip=192.168.0.180:192.168.0.135:192.168.0.152 :255.255.255.0:CM_BF537:eth0:off
I don't know how to go on with this...
QuoteReplyEditDelete
2008-05-20 09:36:29 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Robin Getz (UNITED STATES)
Message: 56051
Vincent:
Are you xxx'ing out the IP addresses? or is that the actual value in U-Boot?
-Robin
QuoteReplyEditDelete
2008-05-21 03:10:44 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vincent Puig (SPAIN)
Message: 56074
Yes, xxx means an IP adress. I did it because I've seen people doing it, for security. But it's not a problem from now on.
Any idea of my problem?.
QuoteReplyEditDelete
2008-05-21 03:28:43 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vitja Makarov (RUSSIAN FEDERATION)
Message: 56075
do you have /dev/pts mounted?
QuoteReplyEditDelete
2008-05-21 04:50:02 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vincent Puig (SPAIN)
Message: 56089
Hi Vitja.
If I do "mount":
root:/> mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
proc on /proc type proc (rw)
ramfs on /var type ramfs (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw)
But the folder is empty
root:/dev> cd pts/
root:/dev/pts> ls
root:/dev/pts>
Could it be the problem?, how can I solve it?.
QuoteReplyEditDelete
2008-05-21 07:10:43 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vitja Makarov (RUSSIAN FEDERATION)
Message: 56090
> Could it be the problem?, how can I solve it?.
Error message you see means, that telnetd couldn't create pseudo-terminal device, the reason could be:
no free pty nodes, no nodes created
what's about /dev/ptypXX nodes? and /dev/ptmx?
Do you use mdev for nodes creation or device_table.txt?
QuoteReplyEditDelete
2008-05-21 08:01:28 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vincent Puig (SPAIN)
Message: 56091
Thanks for replaying.
There are neither ptypXX nodes nor ptmx...
root:/dev> ls
console null ram10 ram14 ram4 ram8
mtd0 pts ram11 ram15 ram5 ram9
mtd0ro ram0 ram12 ram2 ram6 root
mtdblock0 ram1 ram13 ram3 ram7 zero
I think it's using device_table.txt, but how could I know it?. Sorry, I am begginner.
I am using CM-BF537E from Bluetechnix, maybe it helps.
QuoteReplyEditDelete
2008-05-21 08:16:53 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vitja Makarov (RUSSIAN FEDERATION)
Message: 56092
Try 'mdev -s' that should create device nodes, or try to disable CONFIG_USER_DEV_DYNAMIC option.
That seems you use DEV_DYNAMIC and there is not mdev in /etc/rc
QuoteReplyEditDelete
2008-05-22 03:56:42 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vincent Puig (SPAIN)
Message: 56130
Hi Vitja
I did what you said, and it seems to work!!, I changed the CONFIG_USER_DEV from DYNAMIC to STATIC, and now, when I see the 'ls dev' there are lots of files.
And when I telnet to the target, it asks me for a login and password. That's my problem now, I don't know which login/passwd.
Thank you so much!
QuoteReplyEditDelete
2008-05-22 04:23:20 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vitja Makarov (RUSSIAN FEDERATION)
Message: 56137
You better update your /etc/rc to upstream one.
that creates device nodes dynamicly using mdev.
About login use passwd command to set one, that will write /etc/passwd file (or /etc/shadow)
QuoteReplyEditDelete
2008-05-22 04:37:35 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vincent Puig (SPAIN)
Message: 56138
Thiis is how my 'rc' looks like:
hostname blackfin
mount -t proc proc /proc
mount -t ramfs ramfs /var
mount -t sysfs sysfs /sys
mount -t devpts devpts /dev/pts
[ -d /proc/bus/usb ] && mount -t usbfs usbfs /proc/bus/usb
if [ -e /bin/mdev ] ; then
echo /bin/mdev 2>/dev/null > /proc/sys/kernel/hotplug
/bin/mdev -s 2> /dev/null
fi
mkdir /var/tmp
mkdir /var/log
mkdir /var/run
mkdir /var/lock
#dhcpcd &
#ifconfig eth0 192.168.0.180
ifconfig lo 127.0.0.1
inetd &
#cat /etc/issue
cat /etc/motd
Should I add anything?.
About login/password, I used the command 'passwd' in the target, and I changed it, but then when I telnet, it doesn't work:
vincent@canutet:~/uClinux-dist-2008R1-RC8$ telnet 192.168.0.180
Trying 192.168.0.180...
Connected to 192.168.0.180.
Escape character is '^]'.
login: root
Password:(password I wrote)
Connection closed by foreign host.
QuoteReplyEditDelete
2008-05-22 05:12:40 Re: PHY: 0:01 - Link is Up - 100/Full message and telnet problem
Vincent Puig (SPAIN)
Message: 56139
Uooo, I did!, problem is solved!, I can telnet!!, hehe.
Although I still get the PHY message ''PHY: 0:01 - Link is Up - 100/Full", it seems to work fine.
Thanks Vitja.
------------------------------------------------------------------
Ok, problem is not solved yet... I can telnet, by root, but I can write whatever I want for password, and it connects.
vincent@canutet:~$ telnet 192.168.0.180
Trying 192.168.0.180...
Connected to 192.168.0.180.
Escape character is '^]'.
login: root
Password:
BusyBox v1.4.1 (2008-05-19 12:33:26 CEST) Built-in shell (msh)
Enter 'help' for a list of built-in commands.
root:/>
In the target, I use the command passwd, but it doesn't work:
root:/> passwd
Enter new Unix password:
Re-enter new Unix password:
root:/> cat etc/passwd
root::0:0::/root:/bin/sh
It doesn't modify the passwd file.
-rwxrwxrwx 1 1000 1000 26 May 22 2008 etc/passwd
I changed with chmod the permissions, but nothing happens either.
--> grep PAS config/.config
# CONFIG_USER_OLD_PASSWORDS is not set
CONFIG_USER_LOGIN_PASSWD=y
CONFIG_USER_BUSYBOX_PASSWORD_MINLEN=6
# CONFIG_USER_BUSYBOX_FEATURE_SHADOWPASSWDS is not set
CONFIG_USER_BUSYBOX_PASSWD=y
# CONFIG_USER_BUSYBOX_FEATURE_PASSWD_WEAK_CHECK is not set