In a previous message, Joe Morris (NTM) wrote:

On 03/08/2003 12:38 AM, John Pettigrew wrote:

...

I've just bought myself a new Palm Tungsten T. However, it isn't recognised by my system when I try to sync it. The "not claimed by any active driver" means there is no kernel support. [snip] you need to recompile your kernel.

OK. I thought there might be something like that in store! I've never tried compiling a kernel (although I've compiled plenty of software). Is there anything I should watch out for? I gather SuSE kernels are rather complicated? Can I just get the source for a kernel (which version?) from the DVD and change the relevant file (once I know which one and how to change it!)? Many thanks, John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!

In a previous message, Joe Morris (NTM) wrote:

On 03/08/2003 12:38 AM, John Pettigrew wrote:

...

I've just bought myself a new Palm Tungsten T. However, it isn't recognised by my system when I try to sync it. The "not claimed by any active driver" means there is no kernel support.

OK, I'm ready to compile my first kernel - I've got the sources off the DVD, I have checked the visor.c and visor.h files for the lines I need to add. However, before I do this, I want to check a couple of things. First, how do I ensure that I build a kernel that is the same as my current one (SuSE-shipped) except for the changes to the visor module? Second, how do I configure GRUB to use my new kernel? And, preferably, to continue offering my original kernel as a boot option for the moment? TiA John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Knossos: escape the ever-changing labyrinth before the Minotaur catches you!

On 03/10/2003 06:13 PM, John Pettigrew wrote:

In a previous message, John Pettigrew wrote:

...

OK, I'm ready to compile my first kernel [snip] I have checked the visor.c and visor.h files for the lines I need to add.

Sorry to follow up my own post, but I was wondering (in my complete ignorance of kernel magic) - do I have to recompile the whole kernel just for one module? Or can I somehow just alter the visor module?

If you run make cloneconfig, which should give you the same config as the running kernel, make dep and make modules, then backup your present visor.o file and copy only that file from your source tree, it should work. Maybe run depmod -a, then lsmod to make sure it is not in memory, then modprobe visor, you may be working. Hope so. :-) -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.

On 03/10/2003 07:41 PM, John Pettigrew wrote:

Do I have to compile the whole kernel just for this module, or is it possible to compile only the visor module? My experience of compiling so far is ./configure, make and checkinstall (with some tweaking of config). It looks to me like the kernel would take quite a while to compile, which seems wasted effort for one module!

I'm not sure. When the drm modules are rebuilt, only the modules that need it get rebuilt. If you want to try, IIANM cd to the correct directory and make -f Makefile.module (at least that is the principle from the drm modules). I do know that after you recompile your kernel, if you change only the source for one module that is the only one that gets built, as the others have not changed. I would recommend running at least make dep and make modules (in the source root, i.e /usr/src/linux). It may not take as long as you think. This would actually skip building the kernel, i.e. make bzImage. HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.

On 03/11/2003 11:21 PM, John Pettigrew wrote:

This is where I had a few problems - I get lots of error messages when I connect the palm ("error getting string descriptor") with several beeps rather than the usual single "successful hotplug" beep. Also, the Tungsten binds to ttyUSB0 rather than ttyUSB1 for hotsyncing, which my old Visor used, which confused me further.

It may help to restart hotplug, and I would have used modprobe instead of insmod, as AFAIK modprobe loads any dependent modules as well, whereas insmod loads only that module (though I could be wrong).

However, it is now working, despite the error messages. Does anyone know what these mean (a snippet shown below)? And whether I need to worry about them?

Mar 11 15:11:35 linux kernel: hub.c: USB new device connect on bus1/2/1, assigned device number 30 Mar 11 15:11:35 linux kernel: usbserial.c: Palm 4.0 converter detected Mar 11 15:11:36 linux kernel: usb-uhci.c: ENXIO 80001e80, flags 0, urb c3ca90c0, burb c3ca9440 Mar 11 15:11:36 linux kernel: usb.c: error getting string descriptor 0 (error=-6)

Assuming there are no other modules needed, or no other work hotplug would have done, my only suggestion, after getting my Scanlogic USB HD case going, is that sometimes the different revisions of the hardware change the lines added to the source. On the plus side, you only need to run make modules after rechanging the source again, and it only rebuilds the affected module, so it only takes seconds. HTH -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.

On Mon, 10 Mar 2003 11:41:17 GMT John Pettigrew wrote:

Do I have to compile the whole kernel just for this module, or is it possible to compile only the visor module? My experience of compiling so far is ./configure, make and checkinstall (with some tweaking of config). It looks to me like the kernel would take quite a while to compile, which seems wasted effort for one module!

Yeah, usually you can just do make modules make modules_install If you just need to alter some module. but I think this assumes that the corresponding kernel has already been built, and all the files are still in /usr/src/linux. -- use Perl; #powerful programmable prestidigitation

In a previous message, Joe Morris (NTM) wrote:

If you run make cloneconfig, which should give you the same config as the running kernel, make dep and make modules, then backup your present visor.o file and copy only that file from your source tree, it should work.

OK, I've tried replacing visor.o with my newly compiled version. The system now manages to recognise that the visor module should take charge of this device, but it won't talk to the Palm (lots of errors. According to what I've read, it should only take the addition of two lines to visor.c and one to visor.h so that the system recognises the vendor/device ids of the Tungsten. However, it seems like there is something else needed, too. The errors I'm getting are like this: Mar 10 15:54:10 linux kernel: hub.c: USB new device connect on bus1/2/1, assigned device number 10 Mar 10 15:54:10 linux kernel: usbserial.c: Palm 4.0 converter detected Mar 10 15:54:10 linux kernel: usb-uhci.c: interrupt, status 2, frame# 223 Mar 10 15:54:10 linux kernel: visor.c: visor_startup - error getting connection information Mar 10 15:54:10 linux kernel: visor.c: visor_startup - error getting first unknown palm command Mar 10 15:54:10 linux kernel: visor.c: visor_startup - error getting second unknown palm command Mar 10 15:54:10 linux kernel: visor.c: visor_startup - error getting bytes available request Mar 10 15:54:10 linux kernel: usbserial.c: Palm 4.0 converter now attached to ttyUSB0 (or usb/tts/0 for devfs) Mar 10 15:54:10 linux kernel: usbserial.c: Palm 4.0 converter now attached to ttyUSB1 (or usb/tts/1 for devfs) Mar 10 15:54:10 linux kernel: usb.c: USB disconnect on device 10 Mar 10 15:54:10 linux kernel: usbserial.c: Palm 4.0 converter now disconnected from ttyUSB0 Mar 10 15:54:10 linux kernel: usbserial.c: Palm 4.0 converter now disconnected from ttyUSB1 Any ideas? Does anyone know what the latest available kernel is for SuSE? Because I have seen that 2.4.21 should have Tungsten support built in. Thanks for the help anyway! John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Fields of Valour: 2 Norse clans battle on one of 3 different boards

In a previous message, zentara wrote:

On Mon, 10 Mar 2003 16:14:48 GMT John Pettigrew wrote:

...

The errors I'm getting are like this:

Mar 10 15:54:10 linux kernel: hub.c: USB new device connect on bus1/2/1,

...

Mar 10 15:54:10 linux kernel: usb.c: USB disconnect on device 10 Mar 10 15:54:10 linux kernel: usbserial.c: Palm 4.0 converter now disconnected from ttyUSB0 Mar 10 15:54:10 linux kernel: usbserial.c: Palm 4.0 converter now disconnected from ttyUSB1

Any ideas?

Maybe the patch for the visor is conflicting with some other patch which suse has applied.

The "patch" involved is simply adding two lines to visor.c (to insert the "PALM_TUNGSTEN_T_ID" lines into the two relevant structs) and one to visor.h (to add the device id value). I don't quite see how this could conflict with something else, but then I know very little about it! What seemed more likely to me is that something more is needed to allow the linux box to talk to the new PalmOS 5 device. I'll try more research, but there doesn't seem to be much out there and what little there is suggests that these lines are all that is needed! I'm puzzled, and vexed to have to go back to booting Windows just to sync my Tungsten!

I would get a vanilla kernel, from kernel.org, apply the patch, compile and see if it works. If it dosn't work, then you know the patch isn't good. Even if a plain vanilla kernel dosn't have all the functionality you need, at least you will determine if the patch works for the visor.

Good idea - I'll try that when I get the chance. Thanks, John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Fields of Valour: 2 Norse clans battle on one of 3 different boards

On Mon, 10 Mar 2003, Dave Smith wrote:

On Mon, Mar 10, 2003 at 10:10:47AM +0000, john@xl-cambridge.com wrote:

...

First, how do I ensure that I build a kernel that is the same as my current one (SuSE-shipped) except for the changes to the visor module?

run 'make cloneconfig' before 'make xconfig'.

...

Second, how do I configure GRUB to use my new kernel? And, preferably, to continue offering my original kernel as a boot option for the moment?

Not sure. Never used GRUB in that much detail. Sorry.

HTH...

This can be done is yast anyway...

-- David Smith | Tel: +44 (0)1454 462380 Home: +44 (0)1454 616963 STMicroelectronics | Fax: +44 (0)1454 617910 Mobile: +44 (0)7932 642724 1000 Aztec West | TINA: 065 2380 GPG Key: 0xF13192F2 Almondsbury | Work Email: Dave.Smith@st.com BRISTOL, BS32 4SQ | Home Email: David.Smith@ds-electronics.co.uk