I'm going to dig this one back from the grave.
Charlie (or anybody),
Is there any way I could convince you (or anybody else on here for that matter)
to elaborate on backporting. I feel that I am very close in getting this
bluetooth problem snuffed out with my TS-7350. I have compiled the kernel with
the new bluetooth drivers successfully and I have a file called zImage.
What I tried to do right away was copy the zImage file to the sdb2 parition
using "dd if=zImage of=/dev/sdb2". I power on the board and it looks like it's
actually going to boot into something, but then I get a messy error with no
clear beginning but a sure end: "Kernel Panic - Not Syncing: attempted to kill
init!". The beginning is a mess of numbers with the most clear indicator being
at the top: "No redboot partition table. Searching for NAND flash."
So, something doesn't seem to be ready yet. I restored my backup copy of sdb2
and booted successfully again. I took another look at the guide online
(http://www.embeddedarm.com/software/arm-linux-26-ts72xx.php) and notice the
section about bootloader.o. It states: "Once the above files [bootloader
files] are installed at your TS-72XX system, use the following commands to boot
to a zImage file:" When I issue the "insmod -f bootloader.o", I get this error
message: "error inserting bootloader.o: -1 invalid module format".
I'm new at this, and I have just hit a brick wall. What should I do from here?
What steps should I take?
I would really appreciate any help you (or you guys) can give me.
Thanks,
Derek Hildreth
PS. This is a time sensitive project that I'm working on. A quick response
will be greatly appreciated.
--- In "charliem_1216" <> wrote:
>
> Hi Josh --
>
> --- In "notnerdyenough" <farray@> wrote:
> >
> > Hi Fabio & Charlie,
> >
> > I realize this one is a bit old but I'm having the same problem. I'm
> > running 2.6.21-ts on a TS-7800 board. I've tried a number of
> > different dongles but the result is the same. "hcitool scan" always
> > shifts scanned addresses by prepending "02 01" and truncating the
> > last 2 octets.
> >
> > For example, if I have bluetooth device with address
> > 11:22:33:44:55:66 hcitool scan will return
> >
> > Scanning ...
> > 02:01:11:22:33:44 n/a
> >
> > I'm assuming that backporting the Bluetooth & USB patches from a more
> > recent version will fix the problem (since yours seemed to work fine
> > on 2.6.23) but I am new to Linux and am not sure where to go to learn
> > how to do this. Any pointers?
> >
> > Much thanks,
> > josh
>
> Well, a quick and dirty way would be to just take these:
>
> include/net/bluetooth
> net/bluetooth
> drivers/bluetooth
>
> directories from a modern tree and replace existing directories in
> your 2.6.21-TS tree.
>
> But first, please be sure you can configure, build, install & boot an
> *unmodified* TS kernel. Once you can do that, then you can start
> backporting. Or, throw caution to the wind, and use a recent vanilla
> kernel with Matt's patch set ...
>
> regards, .......... Charlie
>
> >
> > --- In "Fabio Vaz" <fvazsilva@> wrote:
> > >
> > > Charliem,
> > >
> > > I had to use the TS 2.6.21 because it has support for ZD1211 and
> > for
> > > the TSGSM1. I didn't manage to compile these drivers on 2.6.23.
> > >
> > > Now I don't know if it is harder to try to make Bluetooth work on
> > TS
> > > 2.6.21 or make TS-GSM1 and ZD1211 work on 2.6.23.
> > >
> > > Best,
> > > Fabio.
> > >
> > > --- In "charliem_1216" <charliem_1216@>
> > > wrote:
> > > >
> > > > Hi --
> > > >
> > > > --- In "Fabio Vaz" <fvazsilva@> wrote:
> > > > >
> > > > > Hi guys,
> > > > >
> > > > > I have a problem with Bluetooth running Kernel 2.6.21 on a
> > > > TS-7200. I
> > > > > was running Dan Smolik 2.6.23 Kernel and it was working fine.
> > > >
> > > > Well, I guess you have a reason to revert to 2.6.21? Which one,
> > > > vanilla or TS? There were lots of bluetooth changes in patch-
> > > 2.6.22
> > > > and patch-2.6.23; perhaps you could back-port them if you need to
> > > > stay at 2.6.21.
> > > >
> > > > >
> > > > > On Kernel 2.6.23 I scan and connect to devices just fine. You
> > can
> > > > see
> > > > > the scan bellow :
> > > > >
> > > > > :root# hcitool scan
> > > > > Scanning ...
> > > > > 00:07:CF:58:CD:AB Pen LZ8170501X8
> > > > ----------^^^^^^^^^^^
> > > > Hmm, this data ...
> > > >
> > > > >
> > > > > On Kernel 2.6.21 the scan doesn't return the name of the device
> > > > and
> > > > > after that I can't pair it too using the hcitool cc. See the
> > scan
> > > > > following :
> > > > >
> > > > > :dex# hcitool scan
> > > > > Scanning ...
> > > > > 00:01:00:07:CF:58 n/a
> > > > ----------------^^^^^^^^^^^
> > > > ... is now shifted; interesting. You might ask on a bluetooth
> > > > list; it doesn't look like an arm or TS board problem.
> > > >
> > > > Regards, ...... Charlie
> > > >
> > > > >
> > > > >
> > > > >
> > > > > Is this a known issue ?
> > > > >
> > > > >
> > > > > Regards,
> > > > > Fabio Vaz.
> > > > >
> > > >
> > >
> >
>
------------------------------------
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/
|