[Q] Wifi driver - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

This is more of a developer question, but I'm too new to post there. I'm looking for a phone or tablet with a replaceable TI WL127x/8x wifi driver. Does the G9 have it as a loadable module (the usual file name for it would be tiwlan_drv.ko or wlan_drv.ko)? Or if it's built into the kernel, is it possible to replace the kernel?

Why?
Gen8 has the 1271 driver it is loaded as a module.
BTW sources are https://www.gitorious.org/archos/archos-gpl-gen8/trees/master/hardware/ti/wlan
BTW my guess is that gen9 also have a module. Sources will also be on the archos git.
Gen8 has already SDE released so you can install your own kernel. For gen9 it still has to be released, however there are ways to go around this. Look at posts from Letama.
Also of interest can be http://www.openaos.org
divx118

Yes, gen9 also have tiwlan_drv.ko as module (wl1283), source for both kernel and tiwlan are on Archos gitorious gits even though they are a bit old compared to released firmwares.
If you're interested in sde for gen9, look at my signature.

Thanks for confirming that.
As for why, I just happen to know something about the driver and was thinking about doing a little android driver work. Maybe a roaming speedup, or possibly power management improvements.

Allow me to jump in.
My A10.1IT runs UrukDroid 1.6.2 and is normally connected to the LAN. It has some external shares mounted (Samba/CIFS).
I've noticed on several occasions that, when I move the device to another location (where the LAN is not available) the device totally and completely locks up. The green light is lit, and stays lit. A hard reset is necessary.
Any ideas?

sciurius said:
Any ideas?
Click to expand...
Click to collapse
I'd suggest to report it to "UrukDroid troubles" thread and, at least, let them know what is logged into syslog (or how they call it).

Related

Ubuntu on A101

Ive managed to run Ubuntu Netbook Remix on the A101 in SDE.
By run i mean i see GDM, because the driver for the touchscreen seems not to be working.
What ive did was, i took an image from here: http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/10.10/release/ and copied everything from the data partition to a new .img file. Also ive copied the modules from the angstrom rootfs.img.
Then just copied over my rootfs.img over the angstrom one and booted.
There seems to be lots of issues, mainly, i guess, because the init script in the initrd should do something, the one from angstrom doesnt.
Also the kernel-log says it cant read the /proc/ filesystem.
I uploaded my rootfs img to rapidshare for you to try for yourselfes, maybe someone can pick up from here and build a really working kernel+initramfs.
http://rapidshare.com/users/KVLF41
I know it's not working out of the box but it's still pretty cool! IBy netbook remix you mean the new Unity UI correct>
Yes, but as i could not login,i havent seen if the windowmanager works correctly.
gomork said:
Ive managed to run Ubuntu Netbook Remix on the A101 in SDE.
By run i mean i see GDM, because the driver for the touchscreen seems not to be working.
Click to expand...
Click to collapse
Kudos! - You could just try to plug in a usb mouse/keyboard into the usb port - it's usb host (mouse and keyboard work in android)
I'd love to see some more action with this. A mouse+keyboard should at elast get you access to the desktop and thus, terminal. From there, enabling the touch screen should be within arms reach.
To experiment for myself, could you write together a fool proof (noob proof) guide to get to where you're at?
casimir007 said:
Kudos! - You could just try to plug in a usb mouse/keyboard into the usb port - it's usb host (mouse and keyboard work in android)
Click to expand...
Click to collapse
i tried that, but it did not work. But that might be because the only Device i have here to test is some wireless usb mouse, which might need some other drivers.
Im currently working on an image with the xserver-xorg-input-evtouch driver built-in. I hope that gets the touchscreen working in X11.
To get started:
Get some Ubuntu.
Install rootstock using: sudo apt-get install rootstock.
Run rootstock:
sudo rootstock --fqdn archos-ubuntu --login ubuntu --password ubuntu --keepimage --imagesize 2G --seed ubuntu-netbook
That one generates an .img file you can copy over your existing rootfs.img.
hi,
I'm very interested to get ubuntu working on archos 101
I've tried your instructions to build an image but it stops after:
...
Setting up software-center (3.0.4) ...
No protocol specified
/usr/lib/pymodules/python2.6/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
WARNING:root:Failed to setup dbus (ignoring)
Setting up xul-ext-ubufox (0.9~rc2-0ubuntu5) ...
Setting up ubufox (0.9~rc2-0ubuntu5) ...
Processing triggers for python-central ...
Setting up xserver-xorg-core (2:1.9.0-0ubuntu7) ...
Setting up gamin (0.1.10-1ubuntu3) ...
Setting up firefox-branding (3.6.10+build1+nobinonly-0ubuntu3) ...
Setting up mono-2.0-gac (2.6.7-3ubuntu1) ...
Setting up mono-gac (2.6.7-3ubuntu1) ...
* Installing 3 assemblies from libappindicator0.1-cil into Mono
i had to ctrl+c, because i tas going no where for about an hour.
I guess it needs display ? ..but i don't know how to solve this
Maybe you could try with an imagesize of 3G or another release like karmic.
i did, my first try was with 2Gb, but didn't finish because it went out of space
then I've tried with 3Gb and stoped as i wrote
I had that problem too once.. Just trying again might work rootstock seems to be a bit buggy.
A little update: usb-mice work, when the modules are copied in /lib/modules in the image, but only when no computer is connected on the mini-usb port, that was the problem in the first place.
Wlan driver extracted from stock archos android can be loaded too, but i didnt manage to get the firmware to load yet.
Ps: a happy new year to all of you.
Sent from my U20i using XDA App
I've tried this image http://forum.xda-developers.com/showpost.php?p=10190468&postcount=38
boots really fast to desktop (10 seconds), but touchscreen don't work, also tried with mouse but nothing
please delete post
could be nice if we run Ubuntu on Gen8
Maybe the image from this thread:
http://forum.xda-developers.com/showthread.php?p=10486278
will get us a little further?
gomork said:
Im currently working on an image with the xserver-xorg-input-evtouch driver built-in. I hope that gets the touchscreen working in X11.
Click to expand...
Click to collapse
Any luck with this?
Would offer to help, but am pretty much a n00b dev at this point >.<
Good God, how awesome it'd be to have a USEABLE distro of linux on the 101 or 70. I love using linux (i have linux mint installed on all 3 computers in my home) and it'd be excellent if i could install an embedded version on my tablet, but alas, i'm a plumber not a programmer! So if someone could post a few links or tutorials to get us started ( as i'm sure there are plenty of gen 8 owners who feel the same as me ) it'd be much appreciated.
Q. Does the 101 it have the same hardware components as the 5 it? The reason i ask is that i think there is a working version of ubuntu nbr for this device and im pretty sure it has the same processor as the gen 8 tablets ( cortex arm a8 ).
Q. Would an amature linux geek like me have any hope of porting it over to our device?
Q. Would it work natively or would we need to modify it?
If anyone else has an interest in having ubuntu on their tablet please post as we have to get this bumped up the list of to do's. BTW, thanks to all you guys in advance and best of luck.
shameless bump for a worthwhile cause!
EDIT:
also, if they can port it to the nook color...
http://forum.xda-developers.com/showthread.php?p=10306407
and, here is a link to a german site where the dev managed to use ubuntu nbr on an a70it using the vpn method:
http://www.android-hilfe.de/archos-70-forum/59607-ubuntu-auf-dem-a70it-es-laeuft.html
pfarrelliv said:
shameless bump for a worthwhile cause!
and, here is a link to a german site where the dev managed to use ubuntu nbr on an a70it using the vpn method:
http://www.android-hilfe.de/archos-70-forum/59607-ubuntu-auf-dem-a70it-es-laeuft.html
Click to expand...
Click to collapse
that's only running via vnc - that means no drivers for display and touchscreen and unfortunately won't get us much further
yes it's just a chroot so you can imagine as a ubuntu running with the android kernel. you could try mux the drivers from the angström to the ubuntu kernel and compile the kernel for arm processors this could work, at least integrating ev-touch will help a lot. search for google for ubuntu4arm and you will find some howto.
the reason why i'm outta this is i have not much time at the moment and without a usable on-screen-keyboard (and at the moment there is none) ubuntu is worthless for me on the tablet.
Why o why have there been so few posts on this subject? Are we the only one's interested or is it just too much work to get another version of linux on the gen 8 devices? Really not trying to be rude to any of the developers on xda because i think you guys are awesome, really, but could someone please tell us if this is a worthwhile cause or a pure waste of time and effort.

[Q][DEV] Archos G9 series firmware extracting?

I've been playing with the new firmware file for a few hours now, but can't really extract it. I'm really interested in the apps, etc, so could someone tell me if there's any way to extract it? OpenAOS, and other archos AOS extractors didn't work sadly.
If someone could do me a system dump of the 101 G9, it would make this whole extraction unneeded (for me atleast!).
Thanks in advance!
And what do you want to do?
None of the Apps will work as they are for HoneyComp.
They all need a newer OS and all the other things that come with the new tablet.
It would be the same useless try that has been done in the beginning of the year with the HC SDK Binaries.
Stop hurting yourself and wait for ICS Sourcecode and then we will see.
fzelle said:
And what do you want to do?
None of the Apps will work as they are for HoneyComp.
They all need a newer OS and all the other things that come with the new tablet.
It would be the same useless try that has been done in the beginning of the year with the HC SDK Binaries.
Stop hurting yourself and wait for ICS Sourcecode and then we will see.
Click to expand...
Click to collapse
So my Asus Transformer isn't HC? Good to know...
I exactly know what I want to do with the apps, so please, no more non helping posts. I started this thread to find answers, not stupid people commenting on everything without reading.
And where did you state that you want to use them on a Transformer?
Even then, none of the Archos APK will work there, as Archos has also changed some underlying OS Funktions and drivers.
As the Gen9 has a completely different SOC ( Tegra2 vs TI OMAP 4430/4460) none of those needed Drivers are working.
So again, what do you want?
fonix232 said:
I exactly know what I want to do with the apps, so please, no more non helping posts. I started this thread to find answers, not stupid people commenting on everything without reading.
Click to expand...
Click to collapse
To simply answer your question...
I'm not familiar with the gen9 devices, but i assume that archos did not change their basic infrastructure on these devices (using squashfs).
If that's the case there are basically three ways i'm aware of:
1. Gain root access on your device and directly copy the files to an external device. Of course this is not very comfortable and you'll have to take care of symlink's, etc.
2. Make a dump of the partition where androidmerged.squashfs.secure is
included using a dd tool or similar.
After doing so, you'll have to investigate the raw data for squashfs signature and remove the leading header.
Then you might be able to get the raw squashfs file containing all data.
This file could be mounted as loop on a linux machine supporting squashfs files.
As i pointed out, i'm not aware of the internal structure in gen9 devices, so i can't tell you which partition is the right one.
Maybe you could post some output of your device (e.g. cat /proc/partitions or mount)
Anyway i guess you'll have to be root to access the mtd devices in the end.
3. Extract the androidmerged.squashfs.secure file directly from the .aos.
Using this way you'll neet to tweak aos-tools with the correct key for gen9 devices. This key has not been published yet and that's why aos-tools is lacking support for gen9 devices.
To be honest we don't know anything about the security mechanism on gen9 yet.
Some words in common...
Please respect the rules!
Abusing other users is a no go
Regards,
scholbert
fzelle said:
And where did you state that you want to use them on a Transformer?
Even then, none of the Archos APK will work there, as Archos has also changed some underlying OS Funktions and drivers.
As the Gen9 has a completely different SOC ( Tegra2 vs TI OMAP 4430/4460) none of those needed Drivers are working.
So again, what do you want?
Click to expand...
Click to collapse
Please, do check my signature...
I want to check out the apps what aren't stock, etc.
wait the SDE
Hey fonix232,
did you see this:
http://forum.xda-developers.com/showthread.php?t=1349184
With the gen9 keys, the aos-tools could be tweaked to extract gen9 firmware files.
Ask letama for help/code.
He already successfully extracted the firmware!
Regards,
scholbert
Hi there,
Here it is:
extracted 3.6.29 firmware
Almost untouched, just with su+SuperUser.apk added.
LeTama

[DEV] Ubuntu 11.10 for A43/A101 [RELEASE 1]

Last summer I got Ubuntu 11.04 working on my A43 but didn't post anything about it. With the progress made on kexec and the new kboot bootloader, it is now possible to have multiple kernels for multiple OS'es. This means it just got a whole lot easier to boot Ubuntu without losing the ability to run OpenAOS or UrukDroid Android OS'es.
As far as I'm aware, Ubuntu doesn't work on the 2.6.29-omap1 kernel that Archos uses and is the base for most other development on gen8. However, for A43 and A101 users, OpenAOS member Nicktime made some headway in porting the 2.6.37+ kernel to gen8, but appears to have abandoned the project. I've cloned his repository and have been working to add features that he did not finish implementing. However, his kernel did have the ability to boot an Ubuntu rootfs and it works very well for desktop Linux distributions (this also works on Debian and I would assume other ARM distros as well).
As I have been unable to build an Ubuntu 11.10 rootfs using the rootstock method that Ubuntu describes here, I've started working with the HP TouchPadBuntu rootfs from this thread. This rootfs boots well on my TouchPad and I've removed the TP-specific items from it and added the gen8 items as necessary. The display is working and the touchscreen works as well (calibrated correctly as I copied my calibration from my 11.04 install). It boots into Unity 2D which is the default. I'm having issues getting the wl1271 wireless module up, I have had it running once but NetworkManager said device was not ready despite being able to iwlist scan and see a list of AP's and then connect to them manually.
RELEASE 1
You will need the rootfs and the modifications.
To install, mount your destination partition (should be at least 4GB and ext3 formatted) to a location, then run the following:
Code:
cd /media/UbuntuPartition (change this to wherever your Ubuntu partition is mounted)
tar xzf /path/to/TouchPadBuntuRootfs.tgz ./
tar xzf /path/to/Gen8Modifications.tar.gz ./
If you do not have a microSD card in the slot, you need to edit the file etc/fstab and change anything mmcblk1 to mmcblk0, this is because the SD card will identify as mmcblk0 if it exists, but if it does not exist then the internal storage gets identified as mmcblk0 instead. This is a kernel issue I have yet to find a solution to.
Kernels for Release 1
These boot from partition 3 of internal memory (/dev/mmcblk2p3)
Normal and Rotated 90 Degrees
This boots from partition 1 of external sdcard (/dev/mmcblk0p1)
Normal
These files do not need an initramfs, but to flash to device or to use with kboot you need one anyways. Simply create an empty (0 byte) file named 'initramfs.cpio.gz' and use it for this purpose.
INFO ON KERNEL MMC/SD INITIALIZATION
mmc0 (mmcblk0pX) - Micro SD card
mmc1 (mmcblk1pX, mmcblk2pX) - System and Data blocks of internal memory
mmc2 - wl1271 SDIO interface
I installed the rootfs to an 8GB microSD and boot it using root=/dev/mmcblk0p1 on the kernel command line.
USEFUL LINKS
http://dev.openaos.org/wiki/Gen8Linux2.6.37
https://github.com/CalcProgrammer1/archos-gen8-kernel-2.6.37
http://forum.xda-developers.com/showthread.php?t=1304475
http://www.omappedia.org/wiki/OMAP_WiLink_Connectivity_Home
http://www.omappedia.org/wiki/MAC802.11_based_Wilink
TIPS AND TRICKS
Disk Usage Power LED:
It is possible to make the Power LED function as a disk usage LED. This will let you know when the system is reading or writing to the memory and can be incredibly helpful in determining whether your system has locked up or is just being slow.
Simply write "mmc0" or "mmc1" (depending on what interface you wish to monitor) to:
/sys/class/leds/power/trigger (maybe power_led can't remember)
This can be changed in the kernel source in the file "archos-leds.c" as well if you want it to apply during boot time.
Charging the battery on A43:
(as root)
echo 1 > /sys/devices/platform/battery/usb_online
echo 3 > /sys/devices/platform/battery/charge_level
Enabling WiFi:
The wl1271 driver from linux-wireless requires firmware files to be placed in /lib/firmware. These files can be downloaded from here. The MAC address on the wl1271 is not stored on the actual wireless chip and instead resides in a configuration file on the system data directory in a file called system/persist.archos.WIFI_mac. This file is in the form:
Code:
Wifi MAC XX:XX:XX:XX:XX:XX
To extract just the MAC address, use
Code:
cut -f3 -d" " /media/data/system/persist.archos.WIFI_mac
Then, to set the MAC of the actual device you can do
Code:
ifconfig wlan0 hw ether `cut -f3 -d" " /media/data/system/persist.archos.WIFI_mac
ifconfig wlan0 up
I'm doing this in /etc/rc.local which is run on boot. This means the WiFi card is prepared when the system boots. However, NetworkManager still sees the card as "not ready" and you must Disable Networking and then Enable Networking before it will start showing AP's. After doing this, the WiFi works properly.
Screen Rotation:
The A43's display is 480x854 ("tall screen" orientation). For Ubuntu it is likely more useful to have a widescreen 854x480 orientation. Fortunately, this is not hard. It involves adding two parameters to your kernel's command line (either via kboot or by adding them to .config and recompiling your kernel). THIS DOES NOT ROTATE THE TOUCHSCREEN INPUT, so make sure you have an alternate input device when using rotation (BT keyboard/mouse, USB keyboard/mouse).
Code:
omapfb.vrfb=y omapfb.rotate=1
Enabling Audio:
This is pretty easy. Audio is installed and ready to go, the only issue is that the default settings in the mixer for this chip happen to disable the output entirely. To fix this, open ALSA Mixer (alsamixer) and turn on either speakers or headphones, then turn on Left Mixer and Right Mixer (hit 'M' to unmute/mute a channel). Finally, turn up the 'PCM' volume and start playing music. I recommend getting rid of Pulse Audio, but I'm still trying to figure out the best way to do so as it uses a lot of resources and provides little benefit.
PowerVR SGX 530 GPU:
The OMAP 3630 CPU has an on-board PowerVR SGX 530 graphics processor. TI provides an SDK that contains the userspace driver libraries as well as the open-source kernel drivers. There are three modules that must be built (pvrsrvkm.ko, omaplfb.ko, bufferclass_ti.ko) and loaded into the system. Then the userspace stuff must be installed. There is information here that should help. So far I've got the drivers to compile, but they aren't properly loading yet. More work to be done on getting the modules to work.
RC.LOCAL START-UP SCRIPT
This script should enable everything at boot time and should make Ubuntu easier to use on gen8 tablets. It starts WiFi and Bluetooth as well as enables USB charging.
Code:
#!/bin/sh -e
#
# rc.local
#
#MAC_ADDRESS='00:22:33:44:55:66'
MAC_ADDRESS=`cut -f3 -d" " /media/data/system/persist.archos.WIFI_mac`
ifconfig wlan0 hw ether $MAC_ADDRESS
ifconfig wlan0 up
modprobe btwilink
sleep 10
hciattach /dev/ttyS0 texas 3000000
/etc/init.d/network-manager restart
echo 1 > /sys/devices/platform/battery/usb_online
echo 3 > /sys/devices/platform/battery/charge_level
exit 0
You must have /media/data mounted in your /etc/fstab file, the entry should look like this:
Code:
/dev/mmcblk1p4 /media/data ext3 defaults 0 0
If this entry isn't in /etc/fstab, the /media/data partition will not be available at the time rc.local is run, and it will fail trying to read the MAC address. Alternatively, you can uncomment the hard-coded MAC address and use that but it's not as clean.
First off, Thanks for the effort you've put in, I just cant wait to get this up and running on my 101. Hopefully I'll have some time this weekend to sort it out but I've questions, How well does it perform? Is unity actually working? & have you tried any other distros? The reason i ask is because i was gonna buy a linux tab running plasma active but if i could eventually run it reasonably well on my 101 i'd hold out and save a couple.
Cheers again and nice work.
It runs fairly well. Unity works (2D only at the moment, not 3D), but whether that's a good thing or not I'll leave up to you (personally I don't like the Unity interface at all, and I find it slow when in 2D mode). I have GNOME 3.0 Fallback installed which runs pretty smooth and fast as it is fairly lightweight. You can use any non-3D-accelerated interface at the moment (Xfce, fluxbox, LXDE, MATE/GNOME2, etc). I've heard of people running plasma active on other non-accelerated systems (including the HP TouchPad, which is where I got my starting image). I haven't bothered as I prefer a traditional desktop-style interface.
That said, if you're willing to test I'd love feedback on how this performs on A101. I don't have an A101 and I am not sure of the status of A101 support. I'm taking Nicktime's word for it that the kernel supports A101. The actual Ubuntu image should be pretty independent of the device but the kernel needs to specifically support each individual board.
To start I'd just download the TouchPadBuntu rootfs I posted (which despite its name doesn't have anything TouchPad related in it and should at very least boot to login screen on the Archos 2.6.37 kernel without modifications). I'll hopefully get a package of modifications up soon including drivers for WiFi, Bluetooth, and a script to get everything running properly at boot.
As for 3D acceleration, I think it should be possible. There are apparently user-space drivers for OMAP3 that will work under Ubuntu. The bigger issue is getting a version of Compiz/Unity3D/Gnome Shell/whatever accelerated desktop you prefer that is compile for OpenGL ES.
Hey dude, could you give me some instructions as to how you installed the roofs.tgz to the memory card? I've got the new boot loader installed and I'm mad to get this going this weekend. Cheers in advance.
P.s. if there is a link to a tut for it that'd be excellent because I don't mind searching for myself just couldn't find any info on it. Thanks.
EDIT:
First post updated, see it for full installation details and feel free to post any questions or problems you have during or after installation. I really want to know how well this plays on A101 devices, as I don't have one to test with. Also, anyone with kernel experience that wants to take on adding additional devices, go for it! It would be great to get A70 support at least, as that is a popular device that has seen Debian/Angstrom activity in the past.
I tar'd the files to the sdcard, created a folder inside OS called ubuntu and placed the zimage & intramfs inside but it wont boot? I probably missed something so feel free to tear me one .
Wasn't even thinking...Duh...the kernels provided assume the root device is /dev/mmcblk2p3 (my Ubuntu partition on internal SD card). You probably want /dev/mmcblk0p1 (first partition on external SD card). I'll build a new kernel and post it soon, or you can take a shot at compiling your own kernel (my GitHub sources need work, for now I'd go with Nicktime's sources at Gitorious as I realized I broke some things).
Kboot should have a cmdline option where you can specify a kernel command line (and thus a root device) but I couldn't get it to work. To clarify, you ARE seeing the kernel boot messages right? If you aren't then kboot probably isn't set up correctly. Try booting another kernel (such as OpenAOS boot menu) from kboot and see if that works.
EDIT: here
CalcProgrammer1 said:
As for 3D acceleration, I think it should be possible. There are apparently user-space drivers for OMAP3 that will work under Ubuntu. The bigger issue is getting a version of Compiz/Unity3D/Gnome Shell/whatever accelerated desktop you prefer that is compile for OpenGL ES.
Click to expand...
Click to collapse
I know they
http://www.linaro.org/
are working on the Open GL ES port of Unity 3D.
Maybe u can find some sources there
And KDE should also have a builf of KDE Plasma wiht OpenGL ES.
Maybe you could add it? would be awesome.
Archos 70
Does/Will this work on the Archos 70? I'm trying to get it working but all I'm getting is static on my screen when Kboot tries to boot Ubuntu. This could be my fault and I could have just messed up the installation but I don't think so.
Thoughts?
shrewdlove said:
Does/Will this work on the Archos 70? I'm trying to get it working but all I'm getting is static on my screen when Kboot tries to boot Ubuntu. This could be my fault and I could have just messed up the installation but I don't think so.
Thoughts?
Click to expand...
Click to collapse
If you read the first post, you will see that this currently only works with A43 and A101. This is due to the kernel I'm using, which was ported by an OpenAOS user who hasn't been active in 6 months. Chances of him resuming his project are slim, so I've forked his kernel progress but don't have an A70 to work with. I could attempt to add A70 support to the kernel but I would be blind to the progress and would need testers. There aren't a ton of changes necessary, mainly just need to add the right LCD driver to make the screen work and then update the board file with the changes that have been made to the A43/A101 boards.
Unfortunately, I don't have much time as of late, I've got a senior design project and school work to deal with, plus I've been working on getting CM9 ICS to compile for gen8, and I've also been working on the HP TouchPad Ubuntu port. Adding A70 support to the kernel is low priority for me, but if any A70 owners want to take a stab at the kernel go right ahead, I'll gladly accept changes to the kernel. As far as Gen8 Ubuntu is concerned, my current focus is getting the SGX GPU up and running with TI's Graphics SDK. If successful, this GPU should be able to run hardware-accelerated Unity 3D and Compiz for a fast, fancy desktop experience.
shrewdlove said:
Does/Will this work on the Archos 70? I'm trying to get it working but all I'm getting is static on my screen when Kboot tries to boot Ubuntu. This could be my fault and I could have just messed up the installation but I don't think so.
Thoughts?
Click to expand...
Click to collapse
I've the exact same problem with my 101, at first I thought it was an issue with kboot but its able to boot uruk and bull. Every time I choose to run ubuntu it stalls with a static on the screen and I have to force a re-boot. I'm using a 2GB sd with only one partition if thats any help and the zimage in question is the one for boot from sd.
Any input?
Oh! Just looked at my kernel configuration again and I forgot to enable A101 support in the configuration file. I'll build a new kernel later today with A101 support enabled! Sorry about that. Should fix A101 but A70 still needs some real work before it will be supported.
EDIT:
Here it is
http://www.box.com/s/18d0e43877b5877ce79f
CalcProgrammer1 said:
Oh! Just looked at my kernel configuration again and I forgot to enable A101 support in the configuration file. I'll build a new kernel later today with A101 support enabled! Sorry about that. Should fix A101 but A70 still needs some real work before it will be supported.
Click to expand...
Click to collapse
Dude, don't apologize. I, and this community, appreciate what your doing. I'd love to have the knowledge to compile my own kernel and have a fully functional distro on this device, but I don't yet have that ability. You do, so any time you give up your time and effort to provide us with something new and cool is fricking brilliant. Keep working and let us know how you get on, but don't cause yourself too much hassle.
Thanks.
I've updated my previous post with an image with A101 support included. I have no way to test it. If any A101 users could take a short video or picture of the device booting Ubuntu I would like to see how it works on that device. I've also looked a bit into A70 support and it looks like the necessary modifications would be relatively straightforward, seeing as all the gen8's have essentially the same core hardware (OMAP3, Wolfson Audio, WL1271 WiFi/BT, MicroSD, POWER/VOL+/-, Power LED, etc). The primary difference (and probably most significant code change required) is the LCD panel, but seeing how the A43 got the short end of the stick on this one, the A70 should be easier to port (A43 has a DSI-interfaced serial LCD while the other gen8's have a DPI parallel LCD, DSI support is flaky at best in this kernel release).
Managed to get it to boot to ubuntu login screen but my usb keyboard doesnt get picked up, I dont know if the touch screen should register at this point but for me it doesnt. I've no bt keyboard but I can't see the device when I scan for bt from my phone either. If you want, I can take a vid of it booting to this point and send it to you. Just in case I get it to work, what are the login details (password) ?
The login is ubuntu/ubuntu (user/pass). I haven't tested the USB yet, and I'm not sure how the A101's host port is set up (the A43 supports USB OTG host but has no dedicated host port). It is a kernel issue for sure. As for the touchscreen, the A101 I think uses a USB touchscreen, so again with the USB issue. You can try forcing automatic login by modifying one of the files on the rootfs (would have to look up which one, can't remember, but should be possible). The fact that it boots is great and the fact that the panel works is also great. I'll look into USB host some more when I get a chance.
Cheers for getting back to me. Is there anyway we can pull something from either the bodhi image or android itself? or would it have to be changed at the kernel?
Pretty sure this is kernel level, the USB driver is being compiled differently than on the stock kernel (musb_hdrc should be a module, but this kernel it is built in, preventing you from loading in different modes). I booted up my A43 with a USB mouse attached, the kernel detected the mouse but then disconnected it before it could be used.

[Q] Onda V975w ROM is too slow, HAL, and ro.hardware?

I'm trying to build a 32-bit UEFI ROM for the Onda V975w. It's an X86 tablet with a very similar SoC to the ASUS T100. I found a build of the Android-IA live image compiled by Chi-Wei Huang for T100 which boots and functions on the V975w, although none of the hardware works so it has to be used with keyboard and mouse plugged into USB. Even video works perfectly, despite being the wrong density. It seems fast and smooth enough.
I have tried to build my own, following the tutorial here to the letter, using Ubuntu 12.04.
https://01.org/android-ia/guides/developers/workstation-setup
I am using the source specified in the tutorial as well. I'm building for baytrail_generic. I have used git to apply Mr. Huang's patches for 32-bit UEFI which seems to have worked.
Problem is it will boot and Android will come up, but it is extremely slow. Unusably slow, as in I click something, and it takes 5-full minutes or longer for it to respond. Mouse pointer is also laggy.
I've reached out to Mr. Huang to see if he could assist. His reply:
You need deeper knowledge about Android inside to debug such a difficult problem.
At least, check the ro.hardware property and logcat to see if the correct gralloc hal and GLES libs are loaded.
Click to expand...
Click to collapse
I'm not sure how I check these things. From what I can find, ro.hardware is a property from ADB and I'd have to be able to ADB to the tablet to see a logcat, right? Or at least have some kind of terminal program installed to read the logcat, but I have neither ADB nor network access because there's no hardware support. So I'm not sure how to check these things. I've asked Mr. Huang for more clarification, but unfortunately didn't hear back from him. Already tried twice and don't want to be a stalker, so I hope someone here can help. I feel like he must have some changes that I need to duplicate, because his build has normal performance while mine does not.
How can I figure out if he's made any changes, and if he has, where is the most likely place for these changes? In the kernel, RAMDisk, or system?

TP-LINK WN722N (ath9k driver) install on Ubuntu touch 15.04 (Nexus 10- Manta)

I've been through all the relevant threads on AskUbuntu and they are either outdated, conflicting and/or dont work.
My Nexus10 sees the atheros AR9271 device on Bus 001 USB but does not create an additional WLAN for it.(wlan0 is the normal integrated wifi) I assume I need the ath9k or ath9k_htc driver? I installed backports 4.4.2-1 and unzipped it. If I try to do a 'make' or 'make clean' I get:'your kernel headers are incomplete/not installed'. I've already got the latest version of build-essential. If I try to install 'firmware-atheros', it cannot find the package. I've been through several other things to no avail.
I've read the driver is installed with 15.x+ anyway, true? and if so how to install it? If someone could do a step-by-step wifi driver install for a U-touch or at least Ubuntu 15.x I'd be very very grateful.
I do not want to bridge the 722n, I want to use it instead of the integrated card. Not even there yet, but just in case it matters.
Thanks!
roninisc said:
I've been through all the relevant threads on AskUbuntu and they are either outdated, conflicting and/or dont work.
My Nexus10 sees the atheros AR9271 device on Bus 001 USB but does not create an additional WLAN for it.(wlan0 is the normal integrated wifi) I assume I need the ath9k or ath9k_htc driver? I installed backports 4.4.2-1 and unzipped it. If I try to do a 'make' or 'make clean' I get:'your kernel headers are incomplete/not installed'. I've already got the latest version of build-essential. If I try to install 'firmware-atheros', it cannot find the package. I've been through several other things to no avail.
I've read the driver is installed with 15.x+ anyway, true? and if so how to install it? If someone could do a step-by-step wifi driver install for a U-touch or at least Ubuntu 15.x I'd be very very grateful.
I do not want to bridge the 722n, I want to use it instead of the integrated card. Not even there yet, but just in case it matters.
Thanks!
Click to expand...
Click to collapse
anyone anyone, Beuller...
Hey, saw this was unanswered and figured I could help. First off, you will not be able to compile or install headers in the Ubuntu Touch system, as /lib/modules/<kernel version> is a bind-mount into the read-only LXC system image, one way to work around this issue on device is to mount the LXC container's system image read-write somewhere, move out the lib/modules directory to someplace else, umount, reboot and then link your moved lib/modules back into /lib/modules. You will need to do this compilation outside of your Nexus 10 in a cross-compilation environment or in an armhf chroot (imho, a chroot running the ARM build of Ubuntu works very well for this).
Once you have that, you can install the kernel package for your device (which I believe are labeled linux-headers-manta and linux-image-manta respectively) and build the driver you seek. However the kernel already comes with backports 4.4.2 in it's tree, so you may be able to apt-get source linux-image-manta and build the driver and/or the kernel itself if you wish. (I believe building the kernel builds the firmware needed for the drivers as well, but I have no way of knowing as I haven't actually rebuilt any drivers with firmware yet in my foray into linux-image-flo's source.)
One piece of advice: Make sure to join together the config.*.ubuntu files under the debian.flo and debian.master folders to get the working .config for your device. The defconfig from arch/arm/configs doesn't have all the needed options for uTouch and won't boot it.
Your 'thanks meter' improved, and big thanks for answering, but this is beyond my level. Was hoping I could run an external wifi stick on a tablet with some flavor of linux, but looks like a no go for mortal users.
roninisc said:
Your 'thanks meter' improved, and big thanks for answering, but this is beyond my level. Was hoping I could run an external wifi stick on a tablet with some flavor of linux, but looks like a no go for mortal users.
Click to expand...
Click to collapse
Sadly at this time, it definitely seems to be. The normal linux way of building drivers doesn't work on here because the modules directory (/lib/modules/3.4.0-5-flo) is read-only, also due to this kernel headers cannot be installed, this can be worked around, but it is definitely not something that the casual user can do easily. I hope this will change so I could start compiling modules and NOT need to rebuild the entire kernel for it.
Glad I could be of help and I love answering questions, I am currently using Ubuntu Touch as my main OS on my Nexus 7 as I'm trying to make it into my own portable workstation. So I'm constantly digging into the system and learning what I can, and I love to share.

Categories

Resources