RE: Dual booting Intimate with CE.

well, that explains why it was reverting to 253 everytime I rebooted. That
fix nailed the coffin shut on it...

Thanks!

I am a happy CE / Intimate dual booter!! Now I have to figure out how to
get CE to stop running through the inane demo everytime I switch back to CE,
as it will drive me slowly insane...

-P

-----Original Message-----
From: James Conner [mailto:jim@secret.org.uk]
Sent: Friday, July 13, 2001 6:37 AM
To: intimate@handhelds.org
Subject: RE: [Intimate] Dual booting Intimate with CE.

There is a script called devfs which lives in init.d
It acts as a quick workaround for folks like you and me
The script you see provides support for those who're in a mess
It makes some nodes and symlinks for use with devfs

It kludges up support for X, for sound and PPP
and for added completeness, it fixes RTC
So what, you ask's the problem, why do we need this code
Well basically, it's simple... It helps the modules load

Let me explain, a little bit, exactly how this goes
Let's have a quick example, so that everybody knows
Let's start with sound, which you might know is dev/dsp
It's a char device with major 14, and a minor no. of 3

Our program starts, and opens up the dsp dev node,
The kernel sees it open, and works out which module to load
The module loads, and then starts up, with it's device ID,
Remember what we said before.. major 14, minor 3.

Some modules are different, they don't have a fixed ID
They're not mainstream in the kernel, so they get it dynamically
Now while this is dead handy for things just like PCCards
When we're dealing with the touchscreen, it's making our life hard.

The problem is the ts node doesn't have a fixed ID,
The major no it get's assigned is done dynamically.
If it's the first dynamic device that the kernel has to use,
It gives the device major 254 to generally abuse.

But if a different driver, that requires a dynamic ID,
gets loaded before the touchscreen, then ts will be 253.
The device nodes on the filesystem aren't the same as in the kernel
And that's where all the problems start, with things acting non-normal.

To fix things up, just hack the script that lives in etc
/etc/init.d/devfs it'll be.
cat /proc/devi* | grep h360
will tell you the node that ts is using, in case you need to know.

The first two lines (except the PATH) are the bits you need to see
if you're having problems with 254, change the major to 253
If your problem is with 253, then try with 254,
but if your hardware config then changes, you'll have problems like before.

Well.. that's enough of that.. I'm sure you all get the idea.

Jim / Tangent

-----Original Message-----
From: intimate-admin@handhelds.org
[mailto:intimate-admin@handhelds.org]On Behalf Of Hicks, Jamey
Sent: 13 July 2001 12:24
To: Patrick Glennon; intimate@handhelds.org
Subject: RE: [Intimate] Dual booting Intimate with CE.

Look in /proc/devices to find the major number used by h3600_ts. You do
not have to remove the module to make the device node. A short script
ought to be able to do the trick -- creating the right device node
before it is needed. Or we could switch to using devfs. I turned off
devfs in the 2.4.6 familiar kernels because I couldn't get the kernel to
fit in 512KB. I think either Familiar 0.5 should use a 768KB kernel
partition or else the bootldr should get jffs2 support.

Jamey

> -----Original Message-----
> From: Patrick Glennon [mailto:pglennon@ebates.com]
> Sent: Thursday, July 12, 2001 10:51 PM
> To: 'intimate@handhelds.org'
> Subject: RE: [Intimate] Dual booting Intimate with CE.
>
>
> ok, so it's fixed. sjohnson on #intimate helped me out on
> this, basically,
> the device file is set up in the intimate20010622.tgz file
> with a major node
> of 253, and it should be 254.
>
> if you try this at home, kids, just do the following to make it work:
>
> first, clear out all the modules that are locking h3600_ts ( apm,
> h3600-sleeve, and h3600-backpaq )
>
> then rmmod h3600_ts
> rm /dev/ts
> mknod /dev/ts c 254 0
>
> then just insmod h3600_ts, and all that other crap if you want it....
>
> cheers, and thanks again sjohnson....
>
> ----
> From: Patrick Glennon
> Sent: Thursday, July 12, 2001 7:13 PM
> To: 'intimate@handhelds.org'
> Subject: RE: [Intimate] Dual booting Intimate with CE.
>
>
> no luck whatsoever. uninstalled and reinstalled tons of
> packages, incluing
> hs_utils, and I am now convinced that something is wonky with h3600_ts
>
> the only real evidence that I have is when I try and launch
> xcalibrate:
>
> intimate:~# xcalibrate
>
>
> in makecursor: Success
>
> in makecursor: Success
> in makecursor: Success
> in makecursor: Success
> in makecursor: Success
> ERROR: TS_GET_CALIBRATION `raw_cal' ioctl fails!
>
> I also get bad ioctl calls when I launch x
>
> Any ideas? HELP!!
>
> -P
>
> -----Original Message-----
> From: Patrick Glennon
> Sent: Thursday, July 12, 2001 5:13 PM
> To: intimate@handhelds.org
> Subject: RE: [Intimate] Dual booting Intimate with CE.
>
>
> Finished the install, but the touchscreen seems dead. I'm
> still poking
> around, but so far, no luck. I've tried yanking out modules
> ( apm, backpaq
> ) that were loaded by default from the tarball, but so far no luck.
>
> I know that X is running, and I can even launch rxvt
> successfully, but the
> touch screen is a no go. I do have the following note I
> found on handhelds:
> http://handhelds.org/z/wiki/BootLinuxWithoutFlashing#34 which states:
>
> "3.4 Troubleshooting
>
> ts is linked to a bad node with 2.4.4-rmk3-np1-hh1 ... fix it"
>
> but Tangent's tarball uses 2.4.3-rmk2-np1
>
> so I will try reinstalling the hs_utils to see if that fixes
> it, but if
> anyone has any recommendations, i'm all ears....
>
> -P
>
> -----Original Message-----
> From: Patrick Glennon
> Sent: Thursday, July 12, 2001 12:58 PM
> To: intimate@handhelds.org
> Subject: RE: [Intimate] Dual booting Intimate with CE.
>
>
> also, intimate20010622.tgz is located at
> http://intimate.handhelds.org/intimate20010622.tgz and NOT under the
> installer directory. Don't know if this was mentioned, but
> it might save
> someone some time...
>
> -----Original Message-----
> From: Patrick Glennon
> Sent: Thursday, July 12, 2001 12:43 PM
> To: intimate@handhelds.org
> Subject: RE: [Intimate] Dual booting Intimate with CE.
>
>
> Might want to mention where to get mkreiserfs, which ( culled from the
> installer ) lives at
> http://intimate.handhelds.org/installer/util/mkreiserfs.tgz
>
> I'm installling this now through familiar, and mkreiserfs
> doesn't come with
> v.04...
>
> -P
>
> -----Original Message-----
> From: James Conner [mailto:jim@secret.org.uk]
> Sent: Friday, July 06, 2001 6:25 AM
> To: intimate@handhelds.org
> Subject: [Intimate] Dual booting Intimate with CE.
>
>
>
> Hi,
>
> I've got intimate dual-booting with CE now! I use the stuff
> that was posted
> the the ipaq@hh.org mailing list a couple of months ago by Arisme (
> http://firelemure.yi.org/ipaq/ ), and made my own kernel and
> ramdisk images.
>
> The install procedure is somewhat compilcated at the moment,
> but I'll work
> on that later.
>
> For now, you need to already have intimate installed to make
> it work... and
> you need to have it installed in a non-standard way. But
> before I tell you
> how it's done, here's a severe warning... so sever that I'm
> going to put
> asterisks around it and type it all in capitals...
>
> *** WHEN YOU BOOT INTIMATE FROM WITHIN CE, THE DEVICE NODES FOR
> /dev/mtdblock/x ARE ALL PRESENT. IF YOU WRITE ANY DATA TO
> THESE IN ANY WAY,
> YOU _WILL) SCREW UP CE. DO NOT UNDER ANY CIRCUMSTANCES 'mount
> /boot' BECAUSE
> IF YOU DO, JFFS2 WILL TURN YOUR CE ROMS INTO A JFFS2
> FILESYSTEM. DEFINATELY
> DO NOT DO _ANYTHING_ TO /dev/mtdblock/0. IT IS THE CE
> BOOTLOADER. MESS WITH
> THAT AND YOU HAVE A BRICK ***
>
> OK.. that's got that over with.. Now onto how it works.
>
> Here's how it goes...
>
> 1. Partition your microdrive into three partitions.
> hda1 = FAT16 partition for CE to use
> hda2 = swap (no more than 32767KB, or your ipaq will become
> unstable)
> hda3 = reiserfs / (We're going to put intimate onto here.)
>
> 2. Create and format (and mkswap) all the partitions.
>
> 3. Untar the intimate20010622.tgz image onto hda3
>
> 4. edit the /etc/fstab for the untarred image. It needs to
> know that hda3 =
> / reiserfs (it'll be set on hda1 by default)
>
> 5. Restore CE onto your iPAQ. (If you didn't already have it.)
>
> 6. Download
http://intimate.handhelds.org/installer/BootIntimate.zip and
unzip it onto the hda1 windows CE partition.. (i.e. use WinZip +
ActiveSync
to move the files). There should be 5 files in the archive. They all
need to
go onto the hda1 partition.

7. On the iPAQ, use 'File Explorer', and click the CyaCE-YACH.exe
executable. It'll load up linux.redboot, linux.kernel and linux.initrd,
and
then start up redboot. (You can monitor the progress at 38400 bps on the
serial port).

8. Linux will boot up.. find the microdrive.. pivot_root onto the
microdrive, unmount the ramdisk, and boot intiamte... Hey presto... You
get
all your memory back, and you have the microdrive as root.

Of course.... Sleep mode will not work, as that relies on the CRL
bootloader.. Getting installed either requires a laptop to configure,
format
and install onto the microdrive, or you already needed to have familiar
installed on your iPAQ in the first place. However.. Now that I've got
this
bit working, I may rig up an install from CE procedure, so that people
can
try out intimate before committing to reflashing the ipaq itself (which
of
course could be done from inside linux).

_______________________________________________
Intimate mailing list
Intimate@handhelds.org
http://handhelds.org/mailman/listinfo/intimate
_______________________________________________
Intimate mailing list
Intimate@handhelds.org
http://handhelds.org/mailman/listinfo/intimate
_______________________________________________
Intimate mailing list
Intimate@handhelds.org
http://handhelds.org/mailman/listinfo/intimate
_______________________________________________
Intimate mailing list
Intimate@handhelds.org
http://handhelds.org/mailman/listinfo/intimate
_______________________________________________
Intimate mailing list
Intimate@handhelds.org
http://handhelds.org/mailman/listinfo/intimate
_______________________________________________
Intimate mailing list
Intimate@handhelds.org
http://handhelds.org/mailman/listinfo/intimate

_______________________________________________
Intimate mailing list
Intimate@handhelds.org
http://handhelds.org/mailman/listinfo/intimate
Received on Fri Jul 13 10:33:06 2001