mcdudeabides wrote: > I'm not completely sure if it is related. This is definitely new ground > for me. I was able to eventually get my wifi adapter to connect > reliably and I am now exercising it (on hour 1.25). To me, it appeared > than the bootlocal script had a flaw in trying to reconnect the wifi > adapter. I don't remember the original code, but I will include my boot > script below. Keep in mind that I am using an open router now. I > haven't tried to go through the wpa supplicant process just yet. I > wanted to make sure the Pi was a viable receiver platform before sinking > too much more time. > > My /opt/bootlocal.sh > > Code: -------------------- > > tc@box:~$ cat /opt/bootlocal.sh > #!/bin/sh > # put other system startup commands here > usr/local/etc/init.d/dropbear start > iwconfig wlan0 essid McHouse > ifconfig wlan0 up > udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid > amixer set PCM 100 unmute > mnt/mmcblk0p1/tce/squeezelite-armv6hf -o sysdefault:CARD=ALSA -n piCorePlayer -a 80:4 -m ab:cd:ef:12:34:01 > -------------------- > >
Thanks for this. I seemed to have neither the iwconfig or the udhcpc line in my bootlocal.sh or bootsync.sh files which confused me for a while. However, what did fix the problem was connecting to wi-fi through Option 7 of Picoreplayer, Option 10 to exit and then a manual sudo filetool.sh -b before rebooting. All seems fine now but don't know why it didn't work by using Option 9 on the menu. New question: is there a way to set up the wireless config manually so I can send it to my son ready to go? Where he is, he has access to wifi but no ethernet. ------------------------------------------------------------------------ kingswindsor's Profile: http://forums.slimdevices.com/member.php?userid=61926 View this thread: http://forums.slimdevices.com/showthread.php?t=97803 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
