inputattach [SOLVED]

Non release banter
User avatar
fanthom
Site Admin
Site Admin
Posts: 4623
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: inputattach

Post#31 by fanthom » 17 Apr 2013, 09:00

upgraded to kernel 3.4.41 and changed 5 things only:

- removed cross-compile prefix as we do not cross-compile (it's still x86)
- removed ext2/3 fs support as ext4 handles them perfectly (smaller kernel)
- compiled in support for SCSI disk (otherwise booting from USB wont work)
- compiled in usb 2.0 support (i hope you are not limited to 1.1 in webdt 366?)
- compiled in support for CS5536 controller (otherwise booting from hd wont work, be aware that booting will work from this particular controller and nothing else.)

please run diff between my config/your config to find other changes (if any).

please download from:
http://www.mediafire.com/?eildvf8dw8446cc

crippled_configs contains aufs patch and kernel config in /user/src/linux/Porteus-patches folder.

did not try to boot it as this kernel is extremely stripped and my hardware is completely different.
please remember to recompile penmount against new kernel and tslib/other stuff against porteus-1.2 (different Xorg version than in porteus-2.0)

hopefully everything will be ok :wink:
Please add [Solved] to your thread title if the solution was found.

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: inputattach

Post#32 by quotaholic » 17 Apr 2013, 22:58

Dam you are fast. Great news, it boots just fine. You are most impressive sir.

Do you have any documentation on kernels that you would recommend? I would like to learn more on the subject and improve skills.

More great news, the buttons work! I have some work to do with xorg and penmount now.

Thank you so much for getting me over the hurdle I was stuck on! As well as the explanation on where I went wrong. Ill report back when I get it wrapped up.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4623
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: inputattach

Post#33 by fanthom » 19 Apr 2013, 18:48

glad to hear that :)

Code: Select all

Do you have any documentation on kernels that you would recommend?
i'm compiling kernels about 7 years (gentoo user) so the knowledge just come with time and experiments.
i used to follow phoronix.com and h-online.com regarding new features in new kernels (digging into lkml/lwn when need more details about specific subjects).
Please add [Solved] to your thread title if the solution was found.

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: inputattach

Post#34 by quotaholic » 27 Apr 2013, 17:20

It seems that I forgot a working console font in that last config file. My bad. No way to open a terminal to do anything. It just closes giving error about font.

I started over with a fresh install of Porteus 1.2 last night. Just this morning I got the touchscreen working and calibrated. Yayyyy!

You were correct that penmount kernel module works. I used inputattach from your xzm (really for porteus 2.0) and grabbed new xinput_calibrator.deb (debian sid) and converted. Added modprobe penmount & inputattach -pm9k /dev/ttyS0 to rc.local and I had a touchscreen and calibration method on reboot. Yay!

I am about to go through and try to rebuild this kernel again for support of atlas_btns. I just wanted to report back that touchscreen can and is working on all open source software. Thank you again.

quotaholic

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: inputattach

Post#35 by quotaholic » 19 Jun 2013, 01:38

This one took me a while. I just successfully recompiled a kernel and placed it into a nice xzm module thanks to great documentation and am now enjoying Porteus 1.2 on 500mhz hardware with 512 shared ddr3 ram and a 500MB 44 pin pata flash on module or DOM.

I had to grab a recent kernel as I could not get aufs to patch cleanly on 3.4 kernel versions. Running 3.9.6 patched and with only the hardware options I need on the DTResearch webdt 366 platform. It smokes now. Cant believe how responsive it is. I highly recommend grabbing a large usb stick and a good kernel reference. Make a custom kernel is cool. Porteus docs make it possible. Using up the rootcopy folder and scripting a lot of the needed files for the hardware on boot, ie rc.local and xorg.conf.d/99-calibration.conf and more. It's kinda funny but with enabling the mtd device in block layer for the cs5536 nand flash handling I enabled /mnt/hda1 as my internal hard drive. Good reference of age. Its fast on LX hardware, untested on GX series hardware. These are cheap x86 industrial tablets available on ebay. ISO files are available for anyone interested. *** ISO will only work on an amd geode based computer.

Hats off to Porteus and thank you to Fanthom for showing me it could be done. You were right. Get a little experience and it should start to come together. O'reilly press helped too. My custom ISO is just 332 mb leaving lots for changes. I had to get supplemental versions of glibc gcc and gcc+ for my touchscreen calibration tool to work however its all wrapped up and in testing phases.

One problem I am having is with TDE saving settings across boots. IT also seems that sometimes I boot in to root and other times in to guest. Using toroot cheatcode as well as autoconf=xconf;startx. Not sure... I need to disable the screen saver power manager too and have it stick as there is no good on screen keyboard in PPM. Installing kernel is proving easier than making ~/Xmodmap stick or getting somthing other than xvkbd to work. Any tips would be greatly appreciated. Thank you!

quotaholic
webdt.org

User avatar
fanthom
Site Admin
Site Admin
Posts: 4623
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: inputattach

Post#36 by fanthom » 19 Jun 2013, 06:38

glad that it's working for you :)
One problem I am having is with TDE saving settings across boots.
please evaluate - what exactly is not working? are you sure you are saving changes? please check this in /var/log/porteus-livedbg
IT also seems that sometimes I boot in to root and other times in to guest. Using toroot cheatcode as well as autoconf=xconf;startx.
'autoconf=xconf;startx' is way obsolete. this boot line is enough:

Code: Select all

APPEND initrd=/boot/initrd.xz changes=/porteus/ toroot
I need to disable the screen saver power manager too
if you are not sure which specific config files to save then just setup your system you want and create module from your changes through PPM.
you may give 'florence' (virtual keyboard) a try but i had mixed experience with it.

btw: i would drop TDE as is being developed slowly (and still has unresolved bugs) and jump straight to porteus-2.1 which offers variety of desktops. Mate should have footprint and functionality comparable to TDE.
Please add [Solved] to your thread title if the solution was found.

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: inputattach [SOLVED]

Post#37 by quotaholic » 19 Jun 2013, 13:27

Image
DT312-Ebay by admintde, on Flickr

Above is what the UPS guy should be delivering today. :Yahoo!: It seems that DT Research has announced end of life cycle on the first of their intel Atom based products.

This one is actually still being sold as new even through EOL has been called:

http://www.groupmobile.com/product.asp/ ... ablet.html

So I may not spend much more time on the AMD geode platform. The above tablet is industrial spec with 4 foot drop rating. For 132 that is a good savings and an amazing hardware set. Atom Z530 CPU, 1GB ram, 4GB flash DOM and a m-sata slot for expansion. Cant wait to get Porteus set up on the new tablet.

I hear you on TDE. I love KDE3 as it was the first window manager I used back on Suse 7.4 pro when I first started with linux. Today she is not so stable. I cant seem to get key bindings to stick. I tell the session manager that I want to poweroff on logout but it does not always do so. a /root/.Xmodmap is proving to be a difficult thing to make take as well. That atlas_btn driver I compiled in defaults to F1-Fx buttons for input so I try to remap them to unised keys and then again through the widow manager to scripts I write that toggle the keyboard on and off the screen, home direectory in the file manager, wifi settings, etc.

Ill try the boot line, thanks. If I am not hitting root consistently that would be most of the problem.

Speaking of atlas_btns... If you look at the picture of the tablet you may see the importance of this driver. All the buttons across the front of the unit will be useless without this ko. Having this driver compiled in to Porteus 2.1 would make it very easy to migrate. Currently this driver is not compiled in to Porteus 2.1 and this is the main reason why I am not using it. Is there any chance I can take the 000-kernel.xzm with 3.9.6 kernel in it that I built and transplant it over to Porteus 2.1?


quotaholic

User avatar
fanthom
Site Admin
Site Admin
Posts: 4623
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: inputattach [SOLVED]

Post#38 by fanthom » 19 Jun 2013, 14:31

Having this driver compiled in to Porteus 2.1 would make it very easy to migrate.
i believe that you would want to compile you custom kernel anyway to strip unneeded stuff and get 110% from the hardware - isn't it?
s there any chance I can take the 000-kernel.xzm with 3.9.6 kernel in it that I built and transplant it over to Porteus 2.1?
sure - just replace /boot/syslinux/vmlinuz and /porteus/base/000-kernel.xzm with your ones.
Please add [Solved] to your thread title if the solution was found.

quotaholic
Black ninja
Black ninja
Posts: 72
Joined: 15 May 2011, 16:20
Location: denver
Contact:

Re: inputattach [SOLVED]

Post#39 by quotaholic » 19 Jun 2013, 18:16

Mate is nearly unusable. Dmesg looks clean and hardware is associating well however it takes around 5 minutes to get to a gui. Init goes like it should but when it hands off to X it takes a long time to see anything on the screen. Mate boasts a 800mhz min cpu requirement. I would concur.

Has anyone built e17 for Porteus? Would it be as easy as getting slack-e17 and running "txz2xzm *.xzm /mnt/sda1/porteus/modules/e17.xzm" from within the e17 directory?

Post Reply