Thank you for the response.
I was able to get WiFi drivers for the Encore Wireless N150 USB
Adapter<http://www.encore-usa.com/us/support/ENUWI-1XN42> working
for my beagleboard by building a new Angstrom build on
http://narcissus.angstrom-distribution.org/ and then building for the
BeagleBoard using advanced settings and selecting "next" for the release,
"extended" for the base system, "all kernel modules" under Additional
console packages, "wireless-tools" under Network related packages and
"Bootloader Files (x-load/u-boot/scripts)" under Texas Instruments
OMAP3x/AM3x family.
Then I acquired the binary file rtl8192cufw.bin and put it into
/lib/firmware/rtlwifi
Then I inserted the driver into the kernel with "modprobe rtl8192cu"
I have the Wi-Fi drivers installed but now I have the problem of trying to
configure the adaptor to go onto a network.
NetworkManager seems to be built for X, which is not good because I'm using
the CLI, it has a CLI utility called nmcli but I haven't been able to
configure the Wireless to go onto a network.
Can anyone suggest a way to connect to a network, using Wi-Fi, in Angstrom,
on an ARM CPU, using the command line?
On Sat, Apr 7, 2012 at 7:00 AM, hfs98 <hf...@overtracks.com> wrote:
> Hi Garrett,
> short version: try make config
>
> Long version:
> (my first post to the group). I recently bought a beaglebone but I'm in
> way over my head. Apologies if this is obvious or not helpful (or
> wrong).
>
> I believe the rule make is looking for should be in the MAKEFILE itself.
> If you un-zip / un-tgz until you get to the MAKEFILE, the actual
> building starts at line 444:
>
> all: modules
>
> modules:
> $(MAKE) ARCH=$(ARCH) CROSS_COMPILE=$(CROSS_COMPILE) -C $(KSRC)..
>
> strip:
> $(CROSS_COMPILE)strip $(MODULE_NAME).ko --strip-unneeded
>
> install:
> install -p -m 644 $(MODULE_NAME).ko $(MODDESTDIR)
> /sbin/depmod -a ${KVER}
>
> uninstall:
> rm -f $(MODDESTDIR)/$(MODULE_NAME).ko
> /sbin/depmod -a ${KVER}
>
>
> config_r:
> @echo "make config"
> /bin/bash script/Configure script/config.in
>
> All those $(variables) need to be defined. At line 37:
> CONFIG_PLATFORM_I386_PC = y
> CONFIG_PLATFORM_ANDROID_X86 = n
> CONFIG_PLATFORM_ARM_S3C2K4 = n
> CONFIG_PLATFORM_ARM_PXA2XX = n
> CONFIG_PLATFORM_ARM_S3C6K4 = n
> CONFIG_PLATFORM_MIPS_RMI = n
> CONFIG_PLATFORM_RTD2880B = n
> CONFIG_PLATFORM_MIPS_AR9132 = n
> CONFIG_PLATFORM_RTK_DMP = n
> CONFIG_PLATFORM_MIPS_PLM = n
> CONFIG_PLATFORM_MSTAR389 = n
> CONFIG_PLATFORM_MT53XX = n
> CONFIG_PLATFORM_ARM_MX51_241H = n
> CONFIG_PLATFORM_ACTIONS_ATJ227X = n
> CONFIG_PLATFORM_ARM_TCC8900 = n
> CONFIG_PLATFORM_ARM_RK2818 = n
> CONFIG_PLATFORM_MIPS_JZ4760 = n
> CONFIG_PLATFORM_DMP_PHILIPS = n
> CONFIG_PLATFORM_TI_DM365 = n
> CONFIG_PLATFORM_MN10300 = n
> CONFIG_PLATFORM_MSTAR_TITANIA12 = n
>
> and then farther down there are sections like:
> ifeq ($(CONFIG_PLATFORM_ARM_MX51_241H), y)
> EXTRA_CFLAGS += -DCONFIG_LITTLE_ENDIAN -DCONFIG_WISTRON_PLATFORM
> ARCH := arm
> CROSS_COMPILE :=
> /opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-
> KVER := 2.6.31
> KSRC ?= /lib/modules/2.6.31-770-g0e46b52/source
> endif
>
>
> There is no obvious "canned" entry for beagle, but somehow you have to
> define those variables. ARCH obviously is arm, and CROSS_COMPILE has to
> be the path to your gcc. You can probably figure out KVER and KSRC. That
> leaves the EXTRA_FLAGS. I haven't the foggiest there. Ditto re
> MODULE_NAME and MODDESTDIR.
>
> The supplied .sh file appears not to even attempt 'make config', which
> doesn't inspire confidence. But it might be worth a try anyways.
>
> -Hugh
>
> On Thu, 2012-04-05 at 07:04 -0700, W.A. Garrett Weaver wrote:
> > Angstrom Users,
> >
> > I've been trying to install Wi-Fi drivers on the
> > BeagleBoard-xM<http://beagleboard.org/hardware-xM>for theEncore
> > Wireless N150 USB
> > Adapter<http://www.encore-usa.com/us/support/ENUWI-1XN42>.
> > I downloaded the source <
> http://www.encore-usa.com/us/support/ENUWI-1XN42>for
> > linux and installed make and the gcc compiler with opkg. When I tried to
> > run make, the terminal responded that "make: ***
> /lib/modules/2.6.32/build:
> > No such file or directory. Stop." so when I created the directory and
> > tried to rebuild it responded:
> > "make[1]: Entering directory `/lib/modules/2.6.32/build'
> > make[1]: *** No rule to make target `modules'. Stop."
> >
> > I would assume that a 'rule' should exist somewhere and that the make
> file
> > isn't pointing to the right directory, the question is, where could the
> > rule file be? How can it be found?
> >
>
>
>
> _______________________________________________
> Angstrom-distro-users mailing list
> Angstrom-distro-users@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
>
--
*W.A. Garrett Weaver *
weav...@email.arizona.edu
_______________________________________________
Angstrom-distro-users mailing list
Angstrom-distro-users@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
