sbp wrote: > fourwed > > I just did what you did (almost) and it is showing up fine in the LMS. > > I booted a fresh version of piCorePlayer, used advanced IP scanner to > find its IP address, then used Putty to log in. > Then it showed: > //\ Core is distributed with ABSOLUTELY NO WARRANTY. > v_/_ www.tinycorelinux.com > > tc@box:~$ ifconfig > eth0 Link encap:Ethernet HWaddr B8:27:EB:05:E8:E8 > inet addr:192.168.1.17 Bcast:255.255.255.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:423 errors:0 dropped:0 overruns:0 frame:0 > TX packets:307 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:37236 (36.3 KiB) TX bytes:37188 (36.3 KiB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:65536 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) (it then had the > address 192.168.1.17 > > > Then I used: > TC@BOX:~$ SUDO IFCONFIG ETH0 192.168.1.57 NETMASK 255.255.255.0 UP > > I then checked in LMS and now the info page show: > Player model: SqueezeLite > Player IP-adresse: 192.168.1.57 > Player MAC-adresse: ab:cd:ef:12:34:01 > > After login via putty using IP 168.192.1.57 > tc@box:~$ ifconfig > eth0 Link encap:Ethernet HWaddr B8:27:EB:05:E8:E8 > inet addr:192.168.1.57 Bcast:192.168.1.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:19011 errors:0 dropped:0 overruns:0 frame:0 > TX packets:5232 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:22971219 (21.9 MiB) TX bytes:457923 (447.1 KiB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:65536 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > And I can play music through it. So I'm able to give it a new and fixed > IP address without any problems. > > ________________________ > The difference is: > 1. the IP address you used is rather special - could that be of > importance? > 2. I didn't use sudo su - this is not possible on the piCorePlayer > 3. The piCorePlayer and the computer is connected through a switch and a > router is serving as DHCP server (but both the computer and piCorePlayer > were given manuel IP) > > Steen
Thanks for your info. Very helpful. 1. the IP address you used is rather special - could that be of importance? I am using class A subnet. This could be the problem but I need further testing. 2. I didn't use sudo su - this is not possible on the piCorePlayer I am sure it is possible. It is also possible in v0.9 too I will test it further and let you know the result. ------------------------------------------------------------------------ fourwed's Profile: http://forums.slimdevices.com/member.php?userid=60662 View this thread: http://forums.slimdevices.com/showthread.php?t=97803 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
