ah . . .
#In a single partition setup, dont load g_multi, as we could trash the
linux file system...
if [ "x${root_drive}" = "x/dev/mmcblk0p1" ] || [ "x${root_drive}" =
"x/dev/mmcblk1p1" ] ; then
#serial:
#modprobe g_serial || true
#Make sure (# CONFIG_USB_ETH_EEM is not set), otherwise this shows
up as "usb0" instead of ethX on host pc..
*modprobe g_ether iSerialNumber=${SERIAL_NUMBER}
iManufacturer=Circuitco iProduct=BeagleBone${BLACK} host_addr=${cpsw_1_mac}
|| true*
else
boot_drive="${root_drive%?}1"
modprobe g_multi file=${boot_drive} cdrom=0 ro=0 stall=0
removable=1 nofua=1 iSerialNumber=${SERIAL_NUMBER} iManufacturer=Circuitco
iProduct=BeagleBone${BLACK} host_addr=${cpsw_1_mac} || true
fi
On Fri, Dec 4, 2015 at 1:47 PM, William Hermans <[email protected]> wrote:
>
>> *These get modprobe'd from /opt/scripts/boot/am335x_evm.**sh*
>>
>
> Thanks for the reply Robert. Yeah, that was driving me insane( short trip
> ). Apparently I need an advanced class on grep, but I used grep as much as
> I could on the rootfs, and apparently missed that. However, I'm also using
> Wheezy 7.8 rootfs, and I went through your build guide again, found the 7.8
> barefs, set it all up, and . . . somehow the file system, and boot loaders
> are all messed up.
>
> As an example, the output from ttyO0 was largely garbled . . . However,
> I'm thinking that's somehow my fault and not yours / your guides fault.
> Basically I just "ripped" the first and second stage boot loaders via dd .
> . . then added them with the 7.8 barefs + kernel I built.
>
> Another issue I ran into . . .
>
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be
>> preloaded: ignored.
>> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be
>> preloaded: ignored.
>> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be
>> preloaded: ignored.
>> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be
>> preloaded: ignored.
>>
>> Over, and over, and over when running ./build_deb.sh. Initially I took
> this literally, as an error. Later, as in this morning I found some obscure
> post on one of the original beagleboards, where the person says it's just
> an annoyance related to 32bit compiler, and 64bit fakeroot. So, I let the
> script run out, and the deb works fine. I wonder if it would be a good idea
> to just pipe stderror to /dev/null when that script is running ?
>
> Anyway, looking into /opt/scripts . . .
>
>
> On Fri, Dec 4, 2015 at 1:33 PM, Robert Nelson <[email protected]>
> wrote:
>
>>
>>
>> On Fri, Dec 4, 2015 at 2:27 PM, William Hermans <[email protected]>
>> wrote:
>>
>>> Ok . . . So here is the deal.
>>>
>>> $ lsmod
>>> Module Size Used by
>>> bnep 13297 2
>>>
>>
>>
>>
>>> rfcomm 52320 0
>>> bluetooth 394459 10 bnep,rfcomm
>>>
>>
>> connman in jessie does these two..
>>
>>
>>
>>> usb_f_ecm 9505 1
>>> g_ether 4794 0
>>> usb_f_rndis 22459 2 g_ether
>>> u_ether 11057 3 usb_f_ecm,usb_f_rndis,g_ether
>>> libcomposite 43376 3 usb_f_ecm,usb_f_rndis,g_ether
>>>
>>
>> These get modprobe'd from /opt/scripts/boot/am335x_evm.sh
>>
>>
>>
>>> nfsd 220016 2
>>> evdev 7956 0
>>> tda998x 11683 1
>>> omap_aes 13033 0
>>> omap_sham 19152 0
>>> tilcdc 27869 0
>>> omap_rng 4346 0
>>> rng_core 7233 1 omap_rng
>>> drm_kms_helper 106705 3 tda998x,tilcdc
>>> uio_pdrv_genirq 3313 0
>>> uio 8350 1 uio_pdrv_genirq
>>> leds_gpio 3102 0
>>>
>>> That's a bit ridiculous especially considering I only use a few of those
>>> modules. nfsd obviously I use, but what has been on my nerves lately are
>>> all these gadget drivers I never use. Or even if I were to use them I would
>>> prefer to load them, or even just g_ether / g_serial as I need them. uio
>>> related modules do not bother me as I use those often enough, and leds_gpio
>>> . . . well I can take it or leave it. The rest, as far as I'm concerned
>>> need to go. The bluetooth modules, I would probably need to remove the
>>> bluetooth package to get rid of these, or fake install . . .
>>>
>>
>> Regards,
>>
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
