thegeezer <[email protected]> [14-10-06 20:48]: > On 06/10/14 17:34, [email protected] wrote: > > Hinnerk van Bruinehsen <[email protected]> [14-10-06 17:56]: > >> On Sun, Oct 05, 2014 at 07:44:03PM +0200, [email protected] wrote: > >>> walt <[email protected]> [14-10-05 19:36]: > >>>> On 10/05/2014 07:54 AM, [email protected] wrote: > >>>>> walt <[email protected]> [14-10-05 16:16]: > >>>>>>> On 10/05/2014 06:52 AM, [email protected] wrote: > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>> while trying to get a mt7601sta (UWN200 WiFi dongle) driver running > >>>>>>>>> and working I came accross this in the dmesg output: > >>>>>>>>> > >>>>>>>>> [ 9.931938] usb 2-1: device v148f p7601 is not supported > >>>>>>> This looks to me like it's the real error, not the one below. > >>>>> What I dont understand is: If I provide the kernel driver...why does > >>>>> the kernel "decides" not to support the hardware the driver itsself > >>>>> supports...? > >>>> Where did you get the driver? Are you sure it's really the right one? > >>>> > >>>> > >>>> > >>> One of the main maintainer for the Beaglebone black kernel sources > >>> (Robert C. Nelson) point me to his git repository of this driver. > >>> > >>> I am now back to kernel 3.8.13, where this stuff runs... > >>> (The kernel I tried it before was 3.14.19) > >>> But this kernel version get no much updates thess days and is > >>> somehow old... > >>> > >> So you tried to run a driver for 3.8.x on a 3.14.x kernel? > >> Such things often result in breakage as, while the kernels interface to > >> userspace is very stable, the internal interfaces aren't stable at all. > >> Likely > >> there would be some other stuff necessary to get the driver to work > >> properly. > >> Some googling around led me to [1] though, which seems to imply that there > >> is > >> support on newer kernels (3.15.10 and newer), if you use the right patch... > >> > >> So maybe you are sucessful with that... > >> > >> WKR > >> Hinnerk > >> > >> [1] http://www.spinics.net/lists/linux-wireless/msg126291.html > > > > Moin Hinnerk, > > (hopefully have guessed this greet correctly...I am from that > > part of Germany ;) > > > > I have the source of the driver exclusivly compiled for 3.8.13 > > as for 3.14.something (cant remember). > > 3.14.x has some other problems (on that embedded platform) like > > not powering off when shutdown, random reboots and such. > > So decided to go back to 3.8.13. > > Yesterday I started updateing (eix-sync and emerge) that Gentoo > > and it ends up in an endless loop (bash update) of configureing > > (damn slow on that mini iron) and compiling - > > just a small aside - you might like to read up on cross compiling and > save yourself a world of pain > http://dev.gentoo.org/~armin76/arm/beaglebone/install.xml
Thank you for the hint! I heard that before... ;) yeah...I walk through all this pain (cross compiling, distcc,...) allready. ;) Beside the kernel, which I compile on my PC and which got an excellent own cross compilling setup made by Robert Nelson, I compile all stuff natively on the embedded system itsself. Reason: The kernel does not depend on other things (especially header files, libs) except the cross compiler itsself and therefore is safe to be cross compiled. For everything else: I repeatedly struggled over software, which includes suddenly header files and libs from my PCs environment instead of the cross compiling sandbox for various reasons. Mostly hardcoded paths and such are the reason. Sometimes it works even with the PCs headers, sometimes it fails when executed, often it suddenly stops compiling. My PC is 64 bit, my embedded system is 32 bit. > > as it looks - > > of a single file. > > After more than 10 hours I CTRL-C that, reupated and now I am > > ...updateing the bash again. > > Sigh. > > Currently "fun" is something else... > > > > Is the 3.15.10++ branch free of things like random reboot and > > not powering off? > > > > Best regards, > > mcc > > > > > > > >
