Re: Touch not detected
Xinput-calibrator does not work with tslib. Regards, Divya Subramanian On Mon, Jun 16, 2014 at 9:34 PM, Tzafrir Cohen tzaf...@cohens.org.il wrote: On Mon, Jun 16, 2014 at 04:07:24PM +0530, Divya Subramanian wrote: Hi, I working to port debian on a13-olinuxino board. I want to build a image having touch screen support in it. i followed this link http://www.dimrobotics.com/2013/06/olinuxino-a13-touchscreen-support-in.html when i Run ts_calibrate, I get Touch Cross hair . But touch is not detected. Slightly OT: is there any use in ts_calibrate? Shouldn't you use xinput-calibrator (from Jessie) or whatever? -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best tzaf...@debian.org|| friend -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140616160359.gz2...@lemon.cohens.org.il
Touch not detected
Hi, I working to port debian on a13-olinuxino board. I want to build a image having touch screen support in it. i followed this link http://www.dimrobotics.com/2013/06/olinuxino-a13-touchscreen-support-in.html when i Run ts_calibrate, I get Touch Cross hair . But touch is not detected. I checked cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 which are almost same. event1 is the event of sun4i-ts,.which I got after dmesg |grep sun4i-ts. can anyone help ? If this is not the right forum, can anyone tell me which forum to seek ? Regards, Divya Subramanian
Touchscreen
I want to connect LCD touchscreen to a13-olinuxino board . I followed this link http://www.dimrobotics.com/2013/06/olinuxino-a13-touchscreen-support-in.html but when I execute modprobe sun4i-ts . it throws error root@divya-HP-Compaq-Elite-8300-SFF:/home/aakash/tslib# modprobe sun4i-ts libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/2.6.32/modules.dep.bin' The filesystem which I generated has /lib/modules/3.0.76+. Is the error being due to this issue . If so, how to correct ? Please help Regards, Divya Subramanian
application launcher should give listed view
I want my application launcher to give listed view. I have LXDE environment on my system wth cairo-dock. can anyone help ? Regards, Divya Subramanian
Shutdown button not working on LXDE environment
Hi all, I am working on porting debian wheezy to a13-olinuxino board. I am using LXDE as desktop environment, openbox as windows manager. Shut Down button doesn't work after I installed cairo-dock. Earlier I had SysVinit as service manager, after which I have installed systemd. From the terminal I can shutdown using either systemctl shutdown or init 0. Does that mean I have two service managers ? can anyone help me ? Regards, Divya Subramanian
Re: Shutdown button not working on LXDE environment
I checked it but no such packages are removed. Is there any other way to do so ? Where does the shut down button from application menu mapsto ? Regards, Divya Subramanian On Thu, May 15, 2014 at 3:15 PM, Paul Wise p...@debian.org wrote: Sounds like you installed systemd and are running that. systemd supports `systemctl poweroff`, `init 0` and `shutdown -h now` as shutdown methods. I suggest you look at the apt history (/var/log/apt/history.log) and try to figure out if any hardware-specific packages were removed. For example on amd64 machines, acpid/acpi-support/acpi-support-base are responsible for turning the button press event into shutdown. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6HnBwRn6ZH2onB6pcSEj1=9b7NuoRaJiOD-=p-umv0...@mail.gmail.com
Issue with Gnome-mplayer VIdeo player
I want a video player working on a13_olinuxino board. I am using gnome-mplayer on LXDE desktop environment . Though it is working but there is no sync between audio and video. Please help . Also please tell if any other lightweight video player is available for LXDE environment on a13_olinuxino. Regards, Divya Subramanian
Re: Running video using smplayer
I made it run as user but still not working Regards, Divya Subramanian On Tue, Apr 29, 2014 at 5:38 PM, Eike Lantzsch zp6...@gmx.net wrote: On Tuesday 29 April 2014 06:28:25 Eike Lantzsch wrote: On Tuesday 29 April 2014 15:30:23 Divya Subramanian wrote: Hi, I want to run .mp4 files using smplayer on a13-olinuxio board. I have installed debian on it. But whenever I run the file on terminal I get this No protocol specified smplayer: cannot connect to X server :0 Please help Regards, Divya Subramanian are you running smplayer as root? Divya answerd yes to this Q off-list. Divya: There is your problem. Run it as a user, provided there IS an X-server up and well. In that case you better use an X-terminal instead of a console. I don't know if by terminal you mean a console or an X- terminal. If there is no X-server than you need to install one. You are using the VGA output, aren't you? Further: To maintain a readable flow of Q-A-Q-A please don't top-post when the reply you get is posted below your post. Also please reply to list so everybody can follow the discussion. In some cases a personal reply off-list is appropriate but use it with discretion. Kind regards and I wish you success Eike -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/15720555.LdNJojeEDD@lxcl01
Running video using smplayer
Hi, I want to run .mp4 files using smplayer on a13-olinuxio board. I have installed debian on it. But whenever I run the file on terminal I get this No protocol specified smplayer: cannot connect to X server :0 Please help Regards, Divya Subramanian
Re: Boot time speed up
I am unable to find a site through which I can download depinit Regards, Divya Subramanian On Fri, Apr 18, 2014 at 4:44 PM, Luke Kenneth Casson Leighton l...@lkcl.net wrote: ... if you're feeling really adventurous look at depinit rather than systemd :) i recall a few years back there was some company claiming they'd managed a 1 second boot time (was it redhat or was it IBM?), and there were also some embedded companies that managed under 350ms including starting up a single-screen dedicated QT app. this was on 720mhz TI OMAPs so it's definitely doable. one of the things i remember them doing was removing damn udev! i recall having (back in only 2005) having a 90mhz Pentium-I system which i used as a firewall. the depth of the bash shell scripts fired up by udev was flat-out *insane*. the fork/process tree was in some cases well over 30 deep. it was only because i had such a slow system that i was able to catch udev in the act so to speak. i think i ended up reporting a debian bug for the pty / tty creation at the time, because there were 256 ptys, 256 ttys, and another mad bunch of 256 ttys somewhere else. this resulted in 768 *separate* instances of udev insanity at shell script depth 30 each. it was therefore no wonder that that poor pentium I system, with little in the way of process context switching support that modern CPUs now have, was flipping its nuts off and took over *twenty seconds* to complete the udev setup phase. now, the relevance here to ARM is that context-switching on ARM CPUs is not as heavily hardware-optimised as it is in the high-end x86 world with hyperthreading and 4+ mbytes of 2nd level cache pushing the number of transistors close to and in some cases above a billion. the recommendation was therefore, if you want to keep udev, to recompile the kernel reducing the number of MAX_TTYs. now, the reason i mentioned depinit was because when i explored this i took a different approach. basically what i did was create two *separate* udev initialisation trigger scripts, and created separate parallel dependencies on each. the first udev trigger script fired off the absolute minimum necessary stuff: only 10 ptys, /dev/sd*, /dev/hd*, that sort of thing. following on from that it was possible to make networking, disks and so on depend on that. the *second* udev trigger script was the normal one that you get every day on the majority of linux distros. it fired eeeverything. dependent on the completion of this script i therefore had everything else. cups printer service. ssh server. etc. etc. it worked like a charm and i had a boot time on a 1ghz pentium-III laptop *including* X-Server startup at something like 15 seconds. shutdown time (thanks to depinit) was something like 3 seconds, and much of that was the actual hardware shutting down. depinit didn't mess about there :) you _should_ be able to replicate this if it really bothers you that udev's too slow, with other parallel startup systems, but the advice to find out *where* the main time is being spent, first, is very very good! also wasn't there something recently about the 3.15 kernel having a more parallel approach to hardware startup? although... you're a bit buggered there because you'd need to patch together your own kernel... l.
Re: Boot time speed up
Any other way of cutting down boot time? Regards, Divya Subramanian On Wed, Apr 16, 2014 at 7:10 PM, David Hicks d...@nastylittlehorse.netwrote: The initramfs isn't the source of the slowdown, unless you have a really huge one. It could be a part of it, though maybe not a massive part. On my hacked up NAS uboot takes a few seconds to copy the initramfs from onboard NAND into the system RAM before it launches the kernel. If you ditched ramfs you could cut those few seconds out. It's not masses I suppose On Tue, Apr 15, 2014 at 5:35 PM, Bill Gatliff b...@billgatliff.comwrote: On Fri, Apr 11, 2014 at 8:42 AM, David Hicks d...@nastylittlehorse.netwrote: I'm not exactly the foremost expert on this but ... my understanding is that the initramfs, or initrd or whatever it is, contains a bunch of useful things the kernel needs to boot the board fully. Primarily these include hardware driver modules needed by the kernel ahead of when the main filesystem becomes available. For instance disk controllers and filesystem drivers. One way to reduce the use of the initramfs/initrd is to build a kernel that has the drivers you need built into it rather than loaded as modules from the ramfs. You would need to build a custom kernel (relatively easy with debian already on the device and using make-kpkg) with the kernel config customised to achieve this. I have no idea how much this would speed up boot time, if at all. You also lose some of the other benefits of using an initramfs/initrd, which I'm having trouble remembering right now. (recovery shell? various scripts for mdadm/lve? stuff...) Actually, baking the necessary modules into the kernel rather than loading them from initramfs would speed things up quite a bit, especially if the modules are demand-loaded. Reasons include the fact that you'd be doing the linking at build-time on your fast PC, rather than at run-time on a slow(er) ARM core. The initramfs isn't the source of the slowdown, unless you have a really huge one. The bootloader already has to load the kernel, and having the filesystem in RAM at the same time will usually speed things along. At least until you have to scour the eMMC to find the final root filesystem, but there's no avoiding that really... Granted, you can put things into initramfs that DO slow you down: hardware probing, lack of parallelism, sleeps, lots of shell scripts, and so on. But the initramfs concept itself doesn't present any speed issues. I haven't looked at Debian's initramfs lately, since I tend to build my own. But since Debian favors generalism over performance (as they should), it wouldn't surprise me to see one built from the ordinary Debian tools that drags its feet a lot before going to the user prompt. b.g. -- Bill Gatliff b...@billgatliff.com
Boot time speed up
Hi, I am working to reduce boot up time of debian on a20 processor. I came across a website which states Avoiding Ramfs can speed up boot time. what is the procedure to do so and will that be helpful to a great extent ? Thanks Divya
Unable to boot using qemu
Hi, I want to boot linux kernel and root file system on qemu. I followed this blog http://emreboy.wordpress.com/2012/12/15/how-to-cross-compile-u-boot-and-work-it-on-qemu/ But this is for versatile board, I want it for a13 allwinner board. The blog asks to add a line to uboot/include/configs/versatile.h #define CONFIG_ARCH_VERSATILE_QEMU so that qemu works on it. What is the substitute for it Regards, Divya Subramanian
Creating a mobile OS for arm architecture
I want to create a mobile OS for arm-architecture. I am a newbie in this arena. Can anyone tell me how to start making it ? How to test ? Thanks, Divya Subramanian
Re: Porting debian on Nvidia tegra 2
How is it suboptimal? I could not understand how UI constraints come into scene . Regards, Divya Subramanian On Thu, Feb 13, 2014 at 1:54 PM, Gordan Bobic gor...@bobich.net wrote: You should be able to get this working pretty trivially in a chroot. Google for running Linux in a chroot on Android. Running it as the primary OS on tablets tends to be suboptimal due to the UI constraints of tablets. Divya Subramanian divyaenginee...@gmail.com wrote: Hi, I am trying to port debian on Samsung galaxy Tab 10.1, working on Nvidia Tegra 2 processor. I am a newbie. Can anyone help? Regards, Divya Subramanian
Re: Porting debian on Nvidia tegra 2
how is the merging done and how are the binary blobs grabbed and merged ? On Fri, Feb 14, 2014 at 7:05 AM, Paul Wise p...@debian.org wrote: On Thu, Feb 13, 2014 at 8:30 PM, Divya Subramanian wrote: I have tried this but I want debian to be installed as Primary OS. Following Ubuntu-touch porting instructions, they are flashing a image, but no information is given on how to create that image. If anyone could tell me how is the boot image created then it would have been a great help. There is an application which helps to flash images. They basically take the CyanogenMod/Android version of the Linux kernel for the specific device and merge that into a normal Ubuntu touch install. Then they grab binary blobs from CyanogenMod/Android and merge those too. https://wiki.ubuntu.com/Touch/Porting This approach is not suitable for Debian because we only support one version of the Linux kernel. Debian will only officially support mobile devices when people start merging support for them to Linux mainline. In the meantime what you can do depends on how locked down your bootloader is and how easily you can modify your Linux kernel+initramfs partition. -- bye, pabs http://wiki.debian.org/PaulWise
Porting debian on Nvidia tegra 2
Hi, I am trying to port debian on Samsung galaxy Tab 10.1, working on Nvidia Tegra 2 processor. I am a newbie. Can anyone help? Regards, Divya Subramanian
