If you are running the onboard flash TSlinux image, then I've found the
best way to deal with USB devices is to load the modules manually.
I believe TS implicitly recommend that - why else would they have scripts
for loading the USB mass storage stuff etc?
On Wed, 16 Mar 2011, ksudeadeye81 wrote:
> Hey All:
>
> I'm not sure whether or not this board hates me at this point, but every time
> I try to get something seemingly simple working on the TS-7260 I just fall
> down another rabbit hole.
>
> So this time around it's hotplug support. I added a couple lines to the init
> script (linuxrc). Here's the important one:
>
> echo /sbin/mdev > /proc/sys/kernel/hotplug
>
> Once I rebooted the board I tried a couple USB modems, and the file
> descriptors in /dev did indeed get added when I plugged the modems in and
> cleaned up when I removed them. So far so good.
>
> Once I tried to actually open the ports I got hit with a "device not found"
> error or some such crap. Then I tried opening the third serial port on the
> board (ttts0) and got the same result. I knew the files were in /dev, so I
> checked out the listing before and after enabling hotplug support, and
> there's one big difference in all the serial ports that get added by mdev
> when hotplugging is enabled:
>
> # hotplug
> brw-rw---- 1 0 0 234, 1 Jan 1 00:00 ttts0
>
> # no hotplug
> crw-rw---- 1 0 0 234, 1 Jan 1 00:00 ttts0
>
> Notice with hotplugging enabled the serial ports are listed as 'block' and
> not 'char' devices. Just to check, I deleted the block file in /dev and added
> a char file for ttts0 manually with mknod. Everything started working fine
> again.
>
> After some research, it seems this is either an issue with a config setting
> for mdev or a bug in mdev itself. I wanted to try and get another version of
> busybox running, so I grabbed the latest version (1.18.4), added a few
> patches to fix some known build errors, built it, and finally installed it on
> the board by just copying over the old busybox binary.
>
> I rebooted the board and...nothing. The kernel loads and then as soon as
> linuxrc is supposed to start, it just stalls. I replaced the original busybox
> binary (1.7.1) and the board starting behaving again.
>
> The hilarious part is I can run the new busybox binary from an NFS share
> after the old one has booted and it works just fine. I even tried the shell
> with this command:
>
> ./busybox sh
>
> So I'm kind of stuck. The binary runs so I don't think I have a toolchain
> issue (crosstool-linux-gcc-3.3.4-glibc-2.3.2-0.28rc39.tar.bz2). Here's a
> couple questions:
>
> 1) Am I missing something with the mdev configuration? I tried creating
> /etc/mdev.conf and messing with a few settings but Technologic seems to have
> configured mdev to ignore the config file.
>
> 2) Any suggestions for getting a new busybox binary to run when the board
> boots.
>
> Thanks much.
>
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|