Updated 2014-05-11!
Well, well, what do we have here? This is a full Debian Unstable installation with the relatively new MATE Desktop Environment http://mate-desktop.org/, which has finally made it's way to the Debian Unstable. MATE is essentially a continuation of the Gnome 2 desktop, and runs great on lower end hardware.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This DOES NOT have the NVIDIA drivers, as I'm using the very latest X releases. The only thing the NVIDIA drivers really get you is good video playback and 3D performance. I don't find the NVIDIA drivers give better 2D performance.
Minor Issues
As you can see in the screenshot, the battery indicator shows as not working. However, if you hover your mouse over the battery indicator, it does show the battery level of both batteries.
Systemd recently came the default system and service manager in Debian unstable. Systemd says it requires the AUTOFS4 kernel module, however that module does not seem to exist in @jrohwer's kernel, so you'll see systemd failures during boot. It does boot fine anyway, but see the next bullet point.
systemd is unable to do an fsck on the root file system (maybe because AUTOFS4 kernel module) during boot, so it ends up leaving the root filesystem in read-only mode. I have worked around this by adding a line to the /etc/rc.local to remount / as readwrite, which seems to do the trick.
Gnome Network Manager has a bit of odd behaviour. After trying to connect to your wireless network for the first time, it will fail, but it will add your network to the list of available networks. Right-click the Network Manager icon, select "Edit Connections...", select your wireless network, click Edit, go to the "Wi-Fi Security" tab and manually enter your wireless passphrase. After doing this once, it will connect normally after that.
As before, sound is hit and miss. Powering down and booting again has a tendency to fix it for a while.
Periodically, when it boots into MATE, the touchpad will stop working. Undock and dock again and it'll come back.
Power management doesn't work.
Good things
Touchscreen works!
You don't need to undock your keyboard during boot. Nice!
Bluetooth and HDMI was not tested (I don't use them).
DOWNLOAD
http://goo.gl/LfydG7
USAGE
Default user is "debian" with a password of "debian".
INSTALLATION
In Android, if you have an existing linuxroot in your /data/ directory, rename/move it.
Extract the Debian image into /data/
Code:
su
busybox mount -o remount,rw /
mv /data/linuxroot /data/linuxroot-old
cd /data
tar -pxvzf /pathto/debian-unstable-mate-2014-05-11.tar.gz
busybox mount -o remount,ro /
Reboot to recovery, install @jrohwer's kernel and you're away.
THANKS
@jrohwer
@DjDill
@Sni
Below is my original post for anyone that want's the older Debian Unstable with the NVIDIA drivers
**************************
Original Post!
This is a basic Debian Unstable (mostly unstable) image for @jrohwer's rootbind method/kernel found here (see post 3):
http://forum.xda-developers.com/showthread.php?t=2347581
It uses the 3.1.10-12 oc kernel.
Obligatory Screenshot:
This has the latest Linux For Tegra binary drivers installed (R16.3) and working. es2_info shows the renderer as "NVIDIA Tegra" and I've included a 720p trailer in the Videos directory which can be played with nvgstplayer with great quality and sound. (nvgstplayer --uri "The Simpsons Movie - Trailer.mp4")
HOW I CREATED IT
I started with a Debian stable install and got the NVidia Tegra drivers working with it. Debian stable's X is at ABI 12. I then held the xserver-xorg-core (apt-mark hold xerver-xorg-core) package to prevent it from automatically updating. Then upgraded everything else to the unstable versions. It seems very few packages are dependent on newer X releases. I did try to upgrade X to the last ABI 14 version that Debian did, but got bad screen corruption with newer X releases and the Tegra driver.
I tried get gstreamer hardware accelerated playback by following this guide (http://ac100.grandou.net/hw_accelerated_video_playback) but did not have success.
DOWNLOAD
http://goo.gl/ZSYoZC
(Mirrors welcome! I suspect Google Drive will shut it down if too many people go for it.)
It's 850 MB download.
USAGE
Default user is "debian" with a password of "debian".
Ensure your tablet is not docked until you get the login screen.
INSTALLATION
In Android, if you have an existing linuxroot in your /data/ directory, rename/move it.
Extract the Debian image into /data/
Code:
su
busybox mount -o remount,rw /
mv /data/linuxroot /data/linuxroot-old
cd /data
tar -pxvzf /pathto/debian-unstable.tar.gz
busybox mount -o remount,ro /
Reboot to recovery, install @jrohwer's kernel and you're away.
MISCELLANEOUS
Wireless works, sound mostly works (it seems to randomly stop working for no apparent reason.. @DjDill complained about the same thing for his Ubuntu image as well. As mentioned, hardware acceleration is working.
I didn't test bluetooth, HDMI, or power management.
I'll test it ASAP and post the results in here.
Meanwhile, I would like to ask some questions about Linux in the TF101G:
1st - Using jrohwer Kernel, I need to extract the IMG to /data/linuxroot, right?
2nd - I should never use the Dock until it boots?
3rd - Using the netinstaller v7 my tab freezes while downloading, using DjDill it wont even boot up
I know here is not the right place to ask (hypocrisy), but I'll try ur Debian now and post the results :good:
Hi vbob.
vbob said:
I'll test it ASAP and post the results in here.
Meanwhile, I would like to ask some questions about Linux in the TF101G:
1st - Using jrohwer Kernel, I need to extract the IMG to /data/linuxroot, right?
Click to expand...
Click to collapse
No, you need to flash jrohwer's kernel in recovery.
vbob said:
2nd - I should never use the Dock until it boots?
Click to expand...
Click to collapse
Correct. There's weirdness with the kernel, if the dock is connected, it continually logs errors to the console during boot. I think it'll boot up eventually with it docked, but you might be waiting a few hours.
vbob said:
3rd - Using the netinstaller v7 my tab freezes while downloading, using DjDill it wont even boot up
Click to expand...
Click to collapse
Sorry, not sure on this one!
I've managed to install on the TF101G, and it worked like a charm, except there is no wifi! Even running "sudo depmod -a", copying nvram and typing iwlist, etc it refuses to connect.
Hi! I tried this debian image today. Unfortunately the touch screen doesn't work and the usb mouse does not too. If I update from terminal t required xorg-input-abi-20. After this update the xserver crashed.
How did you create this image? Could you create a new stable (wheezy) image?
Thanks!
vbob said:
I've managed to install on the TF101G, and it worked like a charm, except there is no wifi! Even running "sudo depmod -a", copying nvram and typing iwlist, etc it refuses to connect.
Click to expand...
Click to collapse
Hmm. You could try add this to your /etc/network/interfaces file:
Code:
auto wlan0
iface wlan0 inet dhcp
wpa-ssid <ssid>
wpa-psk <passphrase>
This assumes a WPA2 personal protected access point. This will cause the wifi to try to connect when the network interface is brought up, instead of using network manager. See if that works.
szigeza said:
Hi! I tried this debian image today. Unfortunately the touch screen doesn't work and the usb mouse does not too. If I update from terminal t required xorg-input-abi-20. After this update the xserver crashed.
How did you create this image? Could you create a new stable (wheezy) image?
Thanks!
Click to expand...
Click to collapse
Pfft! Who uses a touchscreen nowadays! I actually noticed that after the fact as well, but I never really use the touchscreen, so didn't notice. In fact, it seems that if you try to use the touch screen, it actually screws up the touchpad and button click stops working. Maybe that your problem. Don't touch the screen and you'll be golden. I tried a USB mouse and it works fine for me.
I can provide the steps I used to create the base stable (wheeezy) image if it would be useful, then you (or anyone else) could build their own.
Ok, please tell me steps, I will try make a stable image.
Thanks!
Hey guys.
Good news, Nvidia has updated their Linux for Tegra driver to 16.4, which has some important fixes.
You can easily download and install it on your Debian image. Head over to my Hardware Acceleration thread for details and installation instructions.
For those interested, I made a guide for setting up rootbind linux :
http://forum.xda-developers.com/showthread.php?t=2684854
I'll update and link your thread too
Thanks to all dev/users making img for our TF101, it's really great to make it a working laptop
Thanks for your work.
Experimenting with newer X releases
Hey guys.
I've been playing around with a newer X release (ABI 14), which the latest Nvidia drivers support. While it works, I experience disappearing text in mainly GTk applications. QT apps are absolutely fine.
Being able to run a newer X release also allows the latest Gnome to run, which isn't possible with my current Debian image, where X is locked at ABI 12. The good news, Gnome Shell works surprisingly well with the Nvidia drivers. KDE Plasma is not usable, in my experiments, though.
I plan on releasing a test Debian image with various desktop environments installed based on this newer X release and the Nvidia drivers. I suspect it's a buggy Nvidia driver causing the text issues, but maybe if I release it, you guys can help find a workaround or something. Or, you could use it as a QT environment only, where it seems to be fine.
TravellingGuy said:
Hey guys.
I've been playing around with a newer X release (ABI 14), which the latest Nvidia drivers support. While it works, I experience disappearing text in mainly GTk applications. QT apps are absolutely fine.
Being able to run a newer X release also allows the latest Gnome to run, which isn't possible with my current Debian image, where X is locked at ABI 12. The good news, Gnome Shell works surprisingly well with the Nvidia drivers. KDE Plasma is not usable, in my experiments, though.
I plan on releasing a test Debian image with various desktop environments installed based on this newer X release and the Nvidia drivers. I suspect it's a buggy Nvidia driver causing the text issues, but maybe if I release it, you guys can help find a workaround or something. Or, you could use it as a QT environment only, where it seems to be fine.
Click to expand...
Click to collapse
I can confirm this. Tried upgrading my working Ubuntu 13.04 (ABI13) to 13.10 (ABI 14). Indeed GTk apps (such as firefox or thunderbird) show bad text corruption. The ABI13 Nvidia driver works fine on 13.04. In the end I got it to work by pinning xserver-xorg-core and packages depending on ot to the 13.04 release. I attach my preferences file (remove the .txt extension and copy to /etc/apt/preferences.d). I now have a perfectly working 13.10 installation, and will try to upgrade it to 14.04 which is a long term support release using the same strategy.
I realise this is ubuntu and not debian but under the hood they are very similar in the workings of apt and friends, so some of this might be useful to you. The advantage is that Ubuntu 13.04 has abi 13 which is more recent than abi 12 for debian stable, so you might get compatibility with newer features. If you are adventurous, you might even add the Ubuntu repos in your sources list and install these packages from raring (13.04). Who knows it might work???
MATE Desktop
Hey all.
Original post updated with a new image, full Debian Unstable with the new MATE Desktop. This image DOES NOT have the NVIDIA drivers, so it's a full on Debian Unstable image. See original post for details.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This thread was created to make it possible to run and use Android on our devices.
What is Google Android?
Android is a software stack for mobile devices that includes an operating system, middleware and key applications.
Androids Architecture
We need all the help we could get to make this work
Other threads on Google Android
Google Android for Kaiser!!
Linux and Android for Vogue
Other helpful Links
Android on OMAP thanks to mswiss
http://it029000.massey.ac.nz/vogue/
This is the version that still has root access to the OS which makes it possible to edited the rom with-in the rom, thats if we get it ported first of course.
Also I dont have the tools right now to take apart the .nbh and rip it apart so if any can please do. The link is below.
DREAIMG.NBH
This popped up a week ago its the Orange France RUU update for the french G1
Could a kitchen be made out of this??
RUU_DREAM
VIA:imfloflo
This thread will remain open for any advancement of android getting ported onto the wing.
PLEASE REPORT ALL ISSUES TO THE ORIGINAL THREAD!!!
Visit darkstar62's thread (click here) for he has really gotten far with ported linux onto the wing.
darkstar62 said:
I've developed a kernel and base linux system suitable for installation on the HTC Herald / T-Mobile Wing series of phones. This image is for installation of a root filesystem directly to an SD storage card (no need for a root FS image). Several things don't work so far -- this is early development. But it's enough to play with. My hope is that we can use development on this as a jumping point for getting Google Android to run on the wing.
UPDATE (2/10/09):
I've added a Resources section to collect the useful information and links that have been posted here and in the other thread. I've also updated the known issues section for Android to reflect what I've discovered so far.
UPDATE (2/9/09):
I've got an updated kernel config and images for starting Android now! Android will now pull up the boot animation and begin startup. It still does not complete startup, but at least we know we've got the right stuff in the kernel now!
I've added instructions at the bottom for installing these and using them with an already set up linux system (per the first set of instructions).
UPDATE (2/7/09):
Here's some extra files you can grab if you're interested in development: (The patches don't apply cleanly yet against the linwizard kernel)
Kernel .config file I've used (against the linwizard 2.6.25 kernel): http://dl.getdropbox.com/u/198699/linux_wing/wing_config
Android diffs (between SDK android kernel and kernel.org 2.6.27 kernel): http://dl.getdropbox.com/u/198699/linux_wing/android-2.6.27.patch
Contents
Part 1: Linux Base System Installation Instructions
Part 2: Android Installation Instructions
Resources
Part 1: Linux Base System Installation Instructions:
The below instructions assume you have access to Linux and can read/write to your SD storage card.
To start out with, here's what you'll need:
Haret + default.txt + kernel (.zip, 1.4mb)
Root filesystem contents (.tar.gz, 13.1mb)
1. Repartition your SD card.
For this, you'll need to use something like Partition Magic or some other suitable partitioner (in Linux, you can use gparted to resize your Windows partition.) I recommend the following layout:
Partition 1: Primary, FAT16 or FAT32 containing your original Windows files (any size of your choosing)
Partition 2: Primary, Linux Swap, 128mb
Partition 3: Primary, EXT3, >=64mbMy linux partition is 650mb with a 1.2gb Windows partition and 128mb swap -- adjust to preference.2. Format the swap and linux partitions.
In linux, run the following: (I assume your SD card is /dev/sdb -- adjust if different)
Code:
# sudo mkswap /dev/sdb2
# sudo mkfs.ext3 /dev/sdb3
I'm assuming the layout in step 1 as well.
3. Mount the new Linux partition.
Run the following:
Code:
# sudo mount /dev/sdb3 /mnt
4. Copy the base linux system into the new Linux partition.
Save the root filesystem .tar.gz file from above to somewhere (I'll assume $HOME). Then run:
Code:
# cd /mnt
# sudo tar -xzvf $HOME/rootfs.tar.gz
# cd ..
5. Unmount the linux partition.
Run the following command:
Code:
# sudo umount /mnt
6. Mount the windows partition and copy the Haret executable + kernel.
I'll again assume you saved the "haret+kernel.zip" file to $HOME. Run the following:
Code:
# sudo mount /dev/sdb1 /mnt
# cd /mnt
# mkdir linux
# cd linux
# sudo unzip $HOME/haret+kernel.zip
# cd /
# sudo umount /mnt
At this stage, your Linux base system and kernel should be installed. All that's left is to remove your SD card and re-insert it into your phone, start up HaRET and enjoy.
7. Log in
Once you're booted into Linux, you can log in with:
Username: root
Password: wing
Plug in a USB cord to log in on your laptop. If your laptop runs linux, you'll need to make sure that the usb0 network interface has the right address:
Code:
# sudo ifconfig usb0 10.100.0.2 up
The phone's address will be 10.100.0.1. You should be able to SSH or telnet in to the phone and mess around. Run "startx" to bring up X and such.
What's Working
Minimal X server capable of landscape and portrait video modes (KDrive, using the framebuffer (omapfb))
Touch screen support + calibration software (TSC2046 driver + tslib)
Console keyboard (some characters are difficult / impossible to type due to the limited key layout and driver)
USB gadget support for connecting with my laptop (I can SSH / telnet into the phone, or ssh/telnet from the phone into my laptop)
Full access to the SD card (even the Windows FAT side -- mmci-omap driver)
Known Issues
Bluetooth -- haven't been able to get a working driver, or anything to even recognize that it exists
WLAN -- same as bluetooth
GPRS / Phone -- same. There appears to be a GSM device, but I haven't been able to do anything with it.
Most of the extra buttons don't fire any events
LEDs for the most part don't work
Battery and power stats aren't available, as well as power management
No control of the backlight or display power
Sound not functional -- don't have any drivers / software compiled for sound, so I don't know if this would work or not
No real time clock (RTC) functionality
Part 2: Android Installation Instructions:
For these instructions, the recommended procedure is to copy the files you'll need to the Windows side of your SD card and install using the Linux boot system. Make sure you follow the instructions for getting a Linxu base system installed first before following this.
First off, grab the following files (Required)
Android patched kernel for the wing (same as the below kernel, but with android patches): http://dl.getdropbox.com/u/198699/android/zImage2
Android root filesystem, compiled for the wing: http://dl.getdropbox.com/u/198699/android/root.tar.gz
Android /system partition, compiled for the wing: http://dl.getdropbox.com/u/198699/android/system.tar.gz
Script for starting Android: http://dl.getdropbox.com/u/198699/android/start_android
You can also grab the kernel config file if you're interested in building the kernel (I'll have the android patch set available soon) (Optional):
Kernel .config file for the modified kernel: http://dl.getdropbox.com/u/198699/android/kernel_config
1. Copy all files to your wing
From Windows Mobile, download the 4 required files above and place them on your storage card:
root.tar.gz -- Place in /Storage Card/
system.tar.gz -- Place in /Storage Card/
zImage2 -- Place in /Storage Card/linux (overwrite the file that's already there, or re-name the original first)
start_android -- Place in /Storage Card/
2. Install Android
Run HaRET.exe to start Linux. It should boot the new kernel (you most likely won't notice a difference). Once in Linux, run the following commands (you can do it directly with the wing keyboard, or you may elect to use SSH (see instructions above) -- SSH is easer in my opinion):
Code:
# cd ../..
# mkdir android
# cd android
# tar -xzf ../mnt/windows/root.tar.gz
# tar -xzf ../mnt/windows/system.tar.gz
# cp ../mnt/windows/start_android ../bin
# chmod 775 ../bin/start_android
If using the Wing's keyboard, you'll need to use the following key mapping:
'/' --> 'Tab'
'-' --> 'Alt + x'
'_' --> 'Alt + c' (I think -- it's Alt + one of the letter keys)
Numbers -> 'Alt + <top row>'
3. Start Android
At this point, android is now installed and ready to run. Simply execute the following command to start Android:
Code:
# start_android
After a few seconds, you should see the Android startup animation appear.Known Issues
The omapfb driver currently in use does not support page flipping, preventing the Android GUI from being displayed
Resources
WMStorage -- turn your wing into a USB SD card reader (Kudos to Kuff!): http://forum.xda-developers.com/showpost.php?p=3263023&postcount=5
Wing Service Manual (kudos to drmidnight!): http://forum.xda-developers.com/showpost.php?p=3291171&postcount=132
Google Andriod for Herald and Tmobile Wing -- the thread that started it all: http://forum.xda-developers.com/showthread.php?t=398830
Enjoy
Click to expand...
Click to collapse
Thanks
EDIT: Added darkstar62's most current update (2/10/09)
EDIT: Added Wing Linux 0.3 pre3 instructions. Thanks to darkstar62
Current Status
Bluetooth -- haven't been able to get a working driver, or anything to even recognize that it exists
WLAN -- same as bluetooth
GPRS / Phone -- same. There appears to be a GSM device, but I haven't been able to do anything with it.
Most of the extra buttons don't fire any events
LEDs for the most part don't work
Battery and power stats aren't available, as well as power management
No control of the backlight or display power
Sound not functional -- don't have any drivers / software compiled for sound, so I don't know if this would work or not
No real time clock (RTC) functionality
Can anyone take photos of these stages.
I would love to post them here.
Thanks
Good idea. Wondered when someone will come up with it....BUT the main problem will be to port the GSM over...think until now they didn´t succede - did they?
Good luck
i think the first thing we should look at is porting linux over to the wing
then go from there
BUT another thing that i don´t understand...correct me...
WE can only run Android like a VM on a PC.
First XDA boots WM6 and then starts an image from android...so it is more like an application running under WM??
And will there be a time where we can delete WM???
thx
we can delete WM when we have a full set of drivers for android
And linux- i've never understood people's compulsion for linux. Sure it's opensource and therefore free, but that does not automatically make it better.
fzzyrn said:
we can delete WM when we have a full set of drivers for android
And linux- i've never understood people's compulsion for linux. Sure it's opensource and therefore free, but that does not automatically make it better.
Click to expand...
Click to collapse
True true free doesnt make it better but atleast it gives us varieties...instead of just WM we could linux(android) also.
papamopps said:
Good idea. Wondered when someone will come up with it....BUT the main problem will be to port the GSM over...think until now they didn´t succede - did they?
Good luck
Click to expand...
Click to collapse
yeah i think its in that stage for now but imagine if we could make a very Clean rom and cook android into it and make it start at startup we could have it running and a decent speed
I think we can have android running as soon as we complete the "linux kernel" part of the dev roadmap along with the runtime. At this point, android would be "running" but not functioning
alright cool, you guys go work on the linux kernel and ill go.... drink this soda
fzzyrn said:
I think we can have android running as soon as we complete the "linux kernel" part of the dev roadmap along with the runtime. At this point, android would be "running" but not functioning
Click to expand...
Click to collapse
how could we get this started? im willing to try anything right now
you would probably need a coder. I haven't read much about android, but you could probably port over WM6 drivers (depending on programming language?)
fzzyrn said:
you would probably need a coder. I haven't read much about android, but you could probably port over WM6 drivers (depending on programming language?)
Click to expand...
Click to collapse
I don't think that that will work. I think that you need to start with the basic linux drivers and see if you can port them to mobile.
And yes, you would need a coder for that. And sorry to say, that isn't me. But, it t-mobile gets the diamond/whatever they're going to call it, I think that I will be first in line.
N3xt2N0N3 said:
yeah i think its in that stage for now but imagine if we could make a very Clean rom and cook android into it and make it start at startup we could have it running and a decent speed
Click to expand...
Click to collapse
Perfect reason for an Just2Clean variant! lol
WM6 are hardly running on our 200 MHz OMAPs and you want to put another OS on top of it? Laughing out loud.
CommZ said:
WM6 are hardly running on our 200 MHz OMAPs and you want to put another OS on top of it? Laughing out loud.
Click to expand...
Click to collapse
are you serious? hardly running? its sometimes (quite often to be honest) faster than qualcomm 400mhz... (most of users are still believers of MHZ GOD... ).
I know how fast my machine is. It is often annoyingly slow.
these days, frequency doesn't matter as much as FSB does!
But anyway, you would definitely have to write your own drivers, which makes android porting more the responsibility of the manufacturer than of the end user
SUCCESS. I now have Ubuntu 11.04 booting on the Gtab. Using Pershoots kernel and files from the Vega folks, we now have touch screen working. Wireless is not up yet, and have not tested sound.
Thread from the Vegan folks:
http://android.modaco.com/content/a...-com/332887/ubuntu-linux-11-04-natty-on-vega/
From vega get the boot intrd image and the vegan root files.
http://www.adebenham.com/vega/
Follow the instructions to copy and build Pershoots kernel. Edit drivers/video/console/fbcon.c and searching for 'navy' and uncomment the line. This will give you the boot messages on the screen.
Formant the card to ext3. Unzip the vega_root file to an micro sd card of 4GB or better. use unzip -vxf vega_root.tgz
This will take awhile.
Edit /etc/fstab on the card and change mmcblk3p2 to mmcblk2p1
Copy the following files from the staging directory that you made after building Pershoots kernel:
sudo cp location-of-staging-dir location-sd/boot
sudo cp -Rp location-of-staging-dir/system/lib/modules/ location-sd/lib/modules/
Command to build the boot image:
./mkbootimg --kernel zImage --ramdisk initrd.img-2.6.32-custom --cmdline "root=/dev/mmcblk2p1 rootdelay=5 [email protected] [email protected] vmalloc=192M video=tegrafb console=tty0,115200 fbcon=rotate:1 fbcon=font:VGA8x8 usbcore.old_scheme_first=1 cpuid=200102 devicetype=1002 btmac=9c5ed6131a00 tegraboot=nand mtdparts=tegra_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](bootbmp),[email protected](logodata)" -o boot.img
Once you have the boot image, grab a copy of the boot-karmac.zip file. Replace boot.img in the zip file with the one that you created and rename the zip file.
Power down the Gtab, if need be. Put your micro sd card in that has the ubuntu files. Boot into CWM and go to mounts and mount the usbdrive, and connect to your computer. Copy the zip file that you made to the root of the usbdrive. Unmount the usbdrive from your computer and then umount in CWM. Now use CWM to zip the file into the Gtab and reboot.
You should see text scroll by and and it should boot into Ubuntu.
If you do the updates, it will cause problems with libgc. If you do the updates, then log into a terminal window and do sudo dpkg -i /root/glibc/*.deb
This will restore the glibc files needed.
3-23-11 Update
The latest image from the Vega folks fails due to nvrm_daemon. It causes you to loose the external sd card that your booting from. I'm using the first version that they posted.
I've gotten wireless to see AP's. I had to use the bcm4329 driver from Chenglu.
http://forum.xda-developers.com/showthread.php?t=892308
The Gnome nm-applet does not run, as it has issues with libappmenu.so, so I've not been able to test using it to connect to any AP.
Slow headway.
NMCBR600 said:
SUCCESS. I now have Ubuntu 11.04 booting on the Gtab. Using Pershoots kernel and files from the Vega folks, we now have touch screen working. Wireless is not up yet, and have not tested sound.
Click to expand...
Click to collapse
Interesting! Could you please clarify one thing:
> Unzip the vega_root file to an micro sd card of 4GB or better. Formant the card to ext3. use unzip -vxf vega_root.tgz
Do you reformat the sdcard before or after unzip the files to the card? (I thought formating would destory all content of the card)
THANKS!
Format before unzipping the files.
Awesome
Thanks for the great work
obviously we would need wireless (wifi) to make it all useful but the touch screen working is awesome
do you know if this will be able to run or support any of the following: Now or in the Future
1 usb dvd or cd drives- will they be able to be mounted and or even read/writable
2 flash- will flash video be able to be played in browser etc.
3 wine- would wine be able to be installed and used
I do not know how much of these are possible or impossible but all of them would be great
Thanks again
I'm new to the G tab and haven't had any experience at all with ubuntu, but I always want the latest and greatest thing in terms of tech.
Having said that I'm wondering just what are the possibilities of having ubuntu on the G tab, what can be done with it, how will it effect what I can do with the tablet once it is complete?
Thanks in advance.
doihaveto said:
Thanks for the great work
obviously we would need wireless (wifi) to make it all useful but the touch screen working is awesome
do you know if this will be able to run or support any of the following: Now or in the Future
1 usb dvd or cd drives- will they be able to be mounted and or even read/writable
2 flash- will flash video be able to be played in browser etc.
3 wine- would wine be able to be installed and used
I do not know how much of these are possible or impossible but all of them would be great
Thanks again
Click to expand...
Click to collapse
To add cdrom support, you need to add the modules to the kernel. The cdrom drive will need external power as the usb port does not supply enough power to run external hd or cd drives.
Flash -- if there is an arm version for linux
wine -- would have to compile the source code for arm
Roxxas049 said:
I'm new to the G tab and haven't had any experience at all with ubuntu, but I always want the latest and greatest thing in terms of tech.
Having said that I'm wondering just what are the possibilities of having ubuntu on the G tab, what can be done with it, how will it effect what I can do with the tablet once it is complete?
Thanks in advance.
Click to expand...
Click to collapse
Limited by your imagination and needs.
will wicd work for wireless
in this post about ubuntu on the gtablet
http://forum.xda-developers.com/showthread.php?t=894960
the wireless works only with wicd
would this maybe allow wireless to work in this port
At this time, the driver is not coming up. Running ifconfig does not show wlan0 at all, so I know I have an issue with driver. It does see my Verizon usb modem and my usb ethernet unit. With the ethernet unit, I can get online and surf. Currently, openoffice/librioffice are not available as there are dependencies between the two that cannot be resolved due to missing modules. The camera is not seen and I do not have any audio or power management.
I'll be working on this as I can over the weekend.
Using a 2.6.32 kernel with natty might not be the best idea.. 2.6.38 also has broadcom drivers.. this is great and all. but whats preventing us from stepping away from the android kernel? In specific if you can..
I've pulled the nvida 2.6.36 tree but if fails to compile. Complaints about asm using odd registers cause the compile to fail. At this time, 2.6.32 tree has drivers for the hardware. If I can get the 2.6.36 to compile, I'll try it.
Right now, sound, battery monitoring, camera are not working. Buttons on the side and the volume up/down are also not working. This is a starting point.
Forget about wine. Wine is an API translation layer, program loader plus libraries, it does not emulate x86, you are supposed to have it in the hardware. Wine on Gtab with ARM CPU will not do you any good, unless your windows applications are already compiled under ARM. And for that to happen you will have to wait until Microsoft comes up with windows on ARM first
Try the latest git commit of 2.6.38 - its on rc8 fwiw.. I run it on my server (heh).. I also compiled it using a modded pershoot defconfig (in a silly attempt to see if I could be cooler than 2.6.36 xoom folk - and to get the new cpu stuff)
It did not boot android.... but it did compile with no errors. I think I disabled wifi tho.. so yeah, disable as much as you can... get a basic system running on 2.6.38, then start building up
is there any progress here
just checking to see if there is any progress with wireless and or the kernel and drivers being used, is anyone trying this yet themselves besides op
i find this topic very interesting. I'd love to have this fully functional
I have not had luck with wireless. It looks like there is something missing the the vega image. I have gotten the wireless driver to load, but iwlist scan does not return any AP's. I pulled one of the 11.04 arm images for TI boards and tried to use the kernel that I built. I do not get a graphical screen and I cannot log in at a command prompt as I do not have a root password for that load. I've just built a generic 2.6.38 kernel to test on that image to see what happens.
I'm watching the vega forum on what they are doing.
I'm finding moving from working on x86 processors to arm interesting. As I get more information, I'll update the instructions. I want to get this running so I can use this on at a meeting in the first part of April.
get this running and expect a donate from me! i love android but compared to ubuntu it just doesnt cut it. i know you are using 11.04, but what ever happened to the ubuntu/kubuntu 9.04 (i think) MID Edition? Wasnt it made for arm? Did they stop development on this version?
Also, this may be a bit much to ask but could we get a pre-made image so we can test progress so far?
You guys are great! Keep up the good work!
edit: fixed my grammer
At this time I don't have a site to upload images to. I'm wanting to get the wireless sorted out, but as I make headway, I'll update the information that I posted on the first page. The vegan folks updated their vega image, but I cannot get it to boot. I get errors about inode from the sd card, but I know that the sd card checks out fine with fsck, so I've dropped back to their first image. I'm beginning to think that part of the problem is the modified driver for our wireless chip is different from the stock b43 driver in linux.
Headway
Update at the bottom of post #1. Wireless is working. Also, I tested an external CD drive and it was seen. The usb port did not supply enough power to spin the disk in the drive and I did not have an external power supply with me.
This is great,but....
I am in no way knowledgeable of how to compile all this together, can we get more intensive instruction on how to get this running or can anyone get this done in a way that we can simply get it going by the same methods it takes to get this version running:
http://forum.xda-developers.com/showthread.php?t=894960
download the two files extract files to the sd card and flash the kernel that easy.
if not I may never get this up, I would appreciate it greatly
I could provide a drop box account to share the files if it is needed to get them available online just let me know
thanks
[Q&A] How to build/modify your own linux image for eMMC install Debian sample inside
This thread is for help and support with all linux distributions instalable in eeepad asus transformer. I will explain how to build your own image file or modify existing one in order to use lilstive OLife script.
As ubuntu is the most popular distro, please, all de questions related with ubuntu post them in lilstevie's thread.
You can install any distribution with arm architecture support, but you'll need to make some tweaks in the image in order to work propperly. As my experience in linux is most of it related with debian is the distro i will give the best support, but i'll try to answer every question you ask.
I've chosen debian armHardFloat port instead of debian armel fore many reasons, you can read about this port here:
http : //wiki. debian.org/ArmHardFloatPort
This port is still young so right now there are packages still unaviable to install but they are entering in wheeze day to day. If you preffer to use armel instead or armhf you can always do, you will loose improvement but you will have (at the time of writting this) less packages aviable. In the future (not far away) it will be the best option.
Building your own image:
There are many ways to create a image file but because we are going to need qemu in order to debootstrap the instalation the easiest way to create it is with qemu-img
Code:
qemu-img create debian-armhf.img 400M
I have only given 400M of space because is going to be a minimal instalation without desktop enviroment, it could be smaller but, just in case, that's the size i've chosen. The transfer with OLife it will be faster if the image is smaller.
When you boot for your first time you will find an error because there is no valid MSDOS partition table, this is ok, nothing happens because of that but if you want to avoid it use fdisk to create a partition table
Code:
fdisk debian-armhf.img
we need now to give format to the filesistem:
Code:
mkfs.ext4 debian-armhf.img
It will ask if you really want to do because it's not an ordinary partition and you have to type "s" to proceed
Now whe have ready the image and we have to mount it in some folder to install debian in it:
Code:
mount -o loop debian-armhf.img debian
asuming debian as the created folder for that.
We are ready to debootstrap de instalation:
Code:
debootstrap --verbose --arch armhf --foreign --include=btrfs-tools,locales,kbd,wpasupplicant wheezy debian http://ftp.de.debian.org/debian
this will make the first step to install wheezy armhf, --foreing parameter is because the target architecture is different from the host one and it's going to stop before de second-stage, it will include the packages btrfs-tools locales and kbd, you can add as many as you want but it will be always faster if you install them manually once installed in the transformer. I didn't install ssh server because i have a dock, but if you don't have it will be needed to complete the instalation with a remote shell, but you can also install packages later with chroot after the second stage.
In order to be able to chroot we will need qemu-user-static, with armhf it's needed 1.0 version with armel it's not necesary, it can be any version not too old. Also if you have an i386 system it's recomendable to install an amd64 kernel to do chroot or debootstrap will fail configuring cron. Actually i think in this sample image there is anacron instead of cron because there was an issue i thought it was related with that but later twb found out the problem was another different and now it's solved.
we will add qemu-arm-static to the instalation to be able to chroot
Code:
cp /usr/bin/qemu-arm-static debian/usr/bin/
we chroot to the new enviroment:
Code:
chroot debian
and execute the second stage of debootstrap:
Code:
./debootstrap/debootstrap --second-stage
After finish the instalation we will set the root password
Code:
passwd
and now it's ready, you can make tweaks, install packages (as ssh if you need it) or whatever you want, but you will have to add a repository to /etc/apt/sources.list in order to install any packages.
In this image and debootstrap proccess i've used german repositories because are the fastest for me, but you can use another one, right now it's neede also experimental repository to have working touch screen, but as soon xserver-xorg-input-evdev with full multitouch support enters sid as it won't be necesary
example of /etc/apt/sources.list
Code:
http://ftp.de.debian.org/debian unstable main contrib non-free
http://ftp.de.debian.org/debian experimental main contrib non-free
I have already installed in this image necesary packages for that and experimental repositories won't interfiere unless you pass the parameter for apt-file so you can forget about this if you want, but if you are building your own image apt-get install -t experimental xserver-xorg will do the work.
we have ready now our image but it need some files and tweaks to make everithing work in the eepad.
From here you can apply this to any arm image you want to test.
(all the files needed are in the attached file files.tar.gz in the rigth folders)
we need to add modules and firmware, i've extracted them from lilstive ubuntu.img
strictly necesary are:
Code:
/lib/firmware/nvram.txt
/lib/firmware/brcm/*
but you may need another ones if you are going to use external hardware, that's on you.
there are also two folder in /lib/modules one is for the asus kernel and the other one for chrome os kernel, i suggest to add both of them because it's just a bit space and you will be able to use the image with both kernels.
In order to make wifi work i've made /etc/modprobe.d/options.conf file with some parameters found in one of the threads of lilstevie and /etc/modules with the modules to load.
You will also need to configure /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf all this files are in the attached files.tar.gz but wpa_supplicant.conf is not because it depends of each ones wifi, but there is a wpa_supplicant.conf.example and you can always google for it a bit. If you don't have a dock make sure you do this correctly or you won't be able to connect to the internet and ssh device to continue instalation easily
if you want to be able to use adb (wich is really usefull if you for example did not correctly configure wpa_supplicant) you will have tu add also "/usr/bin/adbd" and /etc/init.d/adbd"
I've modify the original init.d script to avid LSB tags missing warning error, it's not really necesary rsyslog as previous service started but ... it works.
In order to make adb service start automatically we will execute (inside the chroot of course)
Code:
update-rc.d /etc/init.d/adb defaults
This may be different in non debian based distributions, but you can always ln manually to rcX.d
Finally, there is the "bug" it has made me think something was wrong and change cron with anacron, when you boot it appears to stop booting starting a service (cron, dbus, deppending what you have installed) but it isn't you can login pressing ctrl + alt + F2 (touchpad key),
we think it's related with the bootloader and default tty as 7 or something like that.
As workaround add in /etc/rc.local "chvt 1" (without quotes) just before exit 0 line
Because there is not oem-installation like in ubuntu after the first boot there are a couple of things to do, we have to resize the image to fit the partition, change password, configure locales and xorg keyboard-layout (if you have more than one locales) add an user and include in relevant groups and maybe more in the future so i've made a postinstalation.sh script included in /usr/bin:
Code:
#!/bin/sh
echo "Making online resize of the root partition"
partition=`mount -l | grep " / " | awk '{print $1}'`
resize2fs $partition
echo "changing root password"
passwd
echo "configure locales"
dpkg-reconfigure locales
echo "configure xserver keyboard layout"
dpkg-reconfigure keyboard-configuration
echo "configure localtime"
dpkg-reconfigure tzdata
echo "Please anter a user name"
read username1
adduser $username1
echo "adding user to relevant groups"
adduser $username1 audio
adduser $username1 video
adduser $username1 netdev
adduser $username1 plugdev
adduser $username1 bluetooth
adduser to bluetooth will fil because there is not installed any bluetooth manager so there is not bluetooth group yet, and remeber tu use OLife script to inject bluetooth firmware in order to have bluetooth working.
And that's it i think i haven't miss anything but i will update this when needed. You can now install your image with lilstevie's OLife script, you will have to rename it to ubuntu.img from now. If everithing went ok you can now install the desktop enviroment you prefer, on screen keyboard or whatever you like.
I haven't test network manager and i've only tested kde-netbook, but there are still broken dependencies and it's a bit slow. This will improve as soon as we have hardware acceleration (if we ever do), and armhf port goes ahead.
Lilstevie is going to host my images and maybe OLife script will have more options in the future, but from now you can download from here:
http://dl.dropbox.com/u/60048492/debian-armhf.img.tar.gz
(md5sum inside)
http://dl.dropbox.com/u/60048492/files.tar.gz
All credits and many thanks for lilstevie and twb for all the help they gave me.
I will apreciate any correction not only in this process but also in my english grammar/ortography
Please, any mod or admin can correct the word modufy in the title?
reserved
Thanks
Following your instructions, I can finally replace ubuntu with debian, which resides my home laptops, office desktop, and now, on my tablet as well. Unfortunately debian has no "onboard" package... and it's rather inconvenient without a dock.
Thanks anyway for bring debian to this tablet.
boseliquid said:
Following your instructions, I can finally replace ubuntu with debian, which resides my home laptops, office desktop, and now, on my tablet as well. Unfortunately debian has no "onboard" package... and it's rather inconvenient without a dock.
Thanks anyway for bring debian to this tablet.
Click to expand...
Click to collapse
What has onboard that haven't other onscreen keyboards? i haven't ever tried onboard and i just tried a couple of onboard keyboards in debian, i also did managed to load it automatically in login screen, But i did never went deeper, like "only appear if the focus is in textbox" or something like that.
Anyway i has to be easy to rebuild that package for debian or just install it from ubuntu. What do you exactly need?
onboard onboard
Onboard has keys that simulate middle-click and right-click of mouse. I tried to install ubuntu's deb file, but runs into problem with dependencies. Compiling the source on the tablet led to error related to gdk/gdk.h which i couldn't figure out how to resolve.
Onboard respond better than others, e.g. xvkbd and florence both have run-away key presses, i.e. a string of letters appear even for a quick single tap on a key.
Also, onboard integrates nicely with lightdm. I used xdm plus florence to log in (the screen keyboard hides most of xdm's GUI).
With fluxbox, debian seems faster than ubuntu+fluxbox on the tablet. That's why onboard is nice since fluxbox menu requires right-clicking on the desktop. Fortunately, fluxbox keys are easily configurable, so i still can shutdown by pressing some key combination.
Hopefully lilstevie has the time to work on hardware acceleration, which would then allows to dump android completely.
boseliquid said:
Onboard has keys that simulate middle-click and right-click of mouse. I tried to install ubuntu's deb file, but runs into problem with dependencies. Compiling the source on the tablet led to error related to gdk/gdk.h which i couldn't figure out how to resolve.
Onboard respond better than others, e.g. xvkbd and florence both have run-away key presses, i.e. a string of letters appear even for a quick single tap on a key.
Also, onboard integrates nicely with lightdm. I used xdm plus florence to log in (the screen keyboard hides most of xdm's GUI).
With fluxbox, debian seems faster than ubuntu+fluxbox on the tablet. That's why onboard is nice since fluxbox menu requires right-clicking on the desktop. Fortunately, fluxbox keys are easily configurable, so i still can shutdown by pressing some key combination.
Hopefully lilstevie has the time to work on hardware acceleration, which would then allows to dump android completely.
Click to expand...
Click to collapse
Ok, i'll give it a look and if i can i will build a debian package in order to include it in the image
I've managed to build a couple of packages for onboard. You can't imagine how much crap it's in building dependencies, mono, unity and so many things, so i've removed appindicator dependency because i don't think it's going to be really necesary. The true is that i don't have so much time right now so,
Can you please test it and tell me if you have any problem? I can try to rebuild another older version in order to avoid unity crap and those things without messing the code, but if this works well it's the eassiest solution.
You have to install both packages, the other dependencies are instalable from debian oficial repository, at least i haven't got any problem installing it in my building environment.
http://dl.dropbox.com/u/60048492/onboard_0.95.1-1_all.deb
http://dl.dropbox.com/u/60048492/python-virtkey_0.60.0-1_armel.deb
arch of python-virtkey is armel instead of armhf
Almost there... but obtained the following error msg:
Unpacking onboard (from onboard_0.95.1-1_all.deb) ...
dpkg: dependency problems prevent configuration of onboard:
onboard depends on python-virtkey (>= 0.60.0); however:
Package python-virtkey is not installed.
onboard depends on python-gconf; however:
Package python-gconf is not installed.
dpkg: error processing onboard (--install):
dependency problems - leaving unconfigured
Thanks again.
boseliquid said:
Almost there... but obtained the following error msg:
Unpacking onboard (from onboard_0.95.1-1_all.deb) ...
dpkg: dependency problems prevent configuration of onboard:
onboard depends on python-virtkey (>= 0.60.0); however:
Package python-virtkey is not installed.
onboard depends on python-gconf; however:
Package python-gconf is not installed.
dpkg: error processing onboard (--install):
dependency problems - leaving unconfigured
Thanks again.
Click to expand...
Click to collapse
python-virtkey is provided in my previous post, just install it, after that
#apt-get install -f
will resolve and install automatically pending dependencies.
I've already tried and it works.
EDIT: i have been working in the suppose you are runnin debian armel and not armhf
To get bluetooth working, you need an armhf build of brcm_patchram_plus.
Thankfully it's GPL'd, so here's a copy.
Hi,
I'm having a bit of trouble getting Debian on my TF101 using OLiFE.
I'm forced to use the android/Ubuntu dual-boot option, but that's another story.
Basically, there's a kernel panic and I can't see the entire screen without it rebooting one second later. I am able to flash my TF101 properly without bricking (it's a B60), but everytime I boot it up as my default OS, I get that rebooting screen.
NothingMuchHereToSay said:
Hi,
I'm having a bit of trouble getting Debian on my TF101 using OLiFE.
I'm forced to use the android/Ubuntu dual-boot option, but that's another story.
Basically, there's a kernel panic and I can't see the entire screen without it rebooting one second later. I am able to flash my TF101 properly without bricking (it's a B60), but everytime I boot it up as my default OS, I get that rebooting screen.
Click to expand...
Click to collapse
Kernel panic kinda implies the problem is with the kernel, not with Debian. If you're using the 3.1 kernel, try the 2.6 one by lilstevie. Whichever kernel you're using, you're better off seeking help in one of the kernel-specific threads.
rdnetto said:
Kernel panic kinda implies the problem is with the kernel, not with Debian. If you're using the 3.1 kernel, try the 2.6 one by lilstevie. Whichever kernel you're using, you're better off seeking help in one of the kernel-specific threads.
Click to expand...
Click to collapse
Could or couldn't it may also be a problem with initramfs and boot parameters. I now because i experienced it. So if you give us more information, better, try to record a video of the bootloop and pass it slowly to see the error, i did that and it worked for me
Franks Tools-new modified Ubuntu install
Hello i dont know if this is right thread,i like to ask you advanced users for some help.I wanna install ubuntua via new modified Franks tools by kenshin,released few days ago,i cannot find exact answer what i need to progress.
My questions are: How can i made nvflashable files system.img boot.img recovery.img and others to use franks tools? how to obtain these images?
2.) and if i will use those images that can be found here on forum can i then just flash for example Revolution HD rom? ,or does it destroy my installation of ubuntu via franks tools?
because i know that there is little play with partitions so i am not sure if i can flash any rom after use of franks tools dual boot option.thank you for help
shaola said:
Could or couldn't it may also be a problem with initramfs and boot parameters. I now because i experienced it. So if you give us more information, better, try to record a video of the bootloop and pass it slowly to see the error, i did that and it worked for me
Click to expand...
Click to collapse
I did everything stock and did exactly what you said to do for Debian, though I used the armel architecture and the adb wouldn't work with an error.
By everything stock, I mean that I didn't alter anything from the OLiFE folder except adding the ubuntu.img file.
NothingMuchHereToSay said:
I did everything stock and did exactly what you said to do for Debian, though I used the armel architecture and the adb wouldn't work with an error.
By everything stock, I mean that I didn't alter anything from the OLiFE folder except adding the ubuntu.img file.
Click to expand...
Click to collapse
The original kernel from OLiFE didn't work for me - I had a boot loop. Try manually compiling the lilstevie kernel, or using a kernel from Jhinta's kernel thread.
The packed kernels (CWM zips) for Ubuntu will work exactly the same under Debian. (or at least in the direct mount case - I don't know about loop mount)
i can't get wifi up ... could someone help?
it is shown in iwlist wlan0 scan but i can't find an network ...
while boot it sends many intervals and abort this progress with givin' up.
i just copied li/firmware file from olife.img und files from this thread over it ...
anyone could help please?
NoDiskNoFun said:
i can't get wifi up ... could someone help?
it is shown in iwlist wlan0 scan but i can't find an network ...
while boot it sends many intervals and abort this progress with givin' up.
i just copied li/firmware file from olife.img und files from this thread over it ...
anyone could help please?
Click to expand...
Click to collapse
what are you uing to scan? this driver ony supports wpasupplicant, not iw nor iwconfig
hi,
i installed the ubuntu image with olife on my transformer. i don't like ubuntu very much, i prefer debian which i run debian on my computer as well. i stumbled over this thread so i wondered what's the status of debian on our transformer.
can anyone tell me whats currently working.
hanswurschtus said:
hi,
i installed the ubuntu image with olife on my transformer. i don't like ubuntu very much, i prefer debian which i run debian on my computer as well. i stumbled over this thread so i wondered what's the status of debian on our transformer.
can anyone tell me whats currently working.
Click to expand...
Click to collapse
The same as in ubuntu. But you may need some tweeks. Depends of the kernel you are using. nvidia has released also a beta of the nvidia drivers for armhf and not only armel so you may use armhf or armel with jintha's kernel and have almost everithung working.
10/15/15 - This project is closed. Lost all files pertaining to the Arch Linux specific install. Kexec thread is still active. Sorry
[FONT=Verdana, sans-serif][FONT=Verdana, sans-serif]Disclaimer: Use at your own risk. You CAN BRICK your device[/FONT]:
[/FONT]9/2/2013
- Wifi still needs to be connected manually.
From Android, download these two packages: netctl and dialog and place in somewhere you can get to from Arch...
In Arch open a terminal and remove the following (I can't remember which was installed so ignore any errors...):
Code:
sudo systemctl stop wicd
sudo systemctl NetworkManager
sudo systemctl disable wicd
sudo systemctl disable NetworkManager
sudo pacman -R wicd-gtk
sudo pacman -R networkmanager
Next install the following:
Code:
sudo pacman -U /pathyousavedto/dialog-1.2_20130523-2-armv7h.pkg.tar.xz
sudo pacman -U /pathyousavedto/netctl-1.3-1-any.pkg.tar.xz
Then each time you login (sorry ), open a terminal and enter:
Code:
sudo wifi-menu wlan0
I'm still trying to figure out what the issue is with wifi...
8/31/2013
Dev work contines again...
- Fixed the DPI issue, in /etc/X11/xorg.conf, add the red to the monitor section
Code:
Section "Monitor"
Identifier "MonitorLVDS"
VendorName "Nvidia"
ModelName "T33 Tegra3"
Option "DPMS" "true"
[COLOR=Red]Option "DPI" "240 x 240"[/COLOR]
[COLOR=Red]#[/COLOR]DisplaySize 218 136
EndSection
You could use 213 if you wanted smaller... I'll fix the font sizes too in the next update.
- Onscreen keyboard in lightdm: edit as root (sudo) /etc/lightdm/lightdm-gtk-greeter, remove red - add blue
Code:
[COLOR=Red]#[/COLOR]keyboard= [COLOR=Blue]xvkbd -secure -geometry 1500x400+250+750[/COLOR]
Looks like you still have to click the Accessibility icon in the top right to make it show though.
8/14/2013
New rootfs is up. Auto-connect wifi is not working. See the Arch wiki Wireless Setup for manual instructions. I left NetworkManager service running (may work for someone?) so be sure to disable it before trying to connect manually. Also I suggest you not install /home to mmcblk0p8, I haven't updated my home files yet.
8/13/2013
I am putting my old rootfs and home files links back up. They "work" (wifi doesn't, I think). I have a rootfs with no auto wifi upped but not tested yet. Maybe tomorrow.
See the Dual-boot Linux on Asus Infinity TF700t thread for beta installers.... Remember to NOT choose /home on mccblk0p8, only in the rootfs!
Development thread is here - Not updated....
[FONT=Verdana, sans-serif]This rootfs is designed for those who are experienced Linux users. If you are not comfortable with or don't know what the command line is, this is not for you.[/FONT]
SUGGESTED Requirements[FONT=Verdana, sans-serif]: TWRP 2.5+ and CROMI 4.X/5 CROMi-Xenogenisis[/FONT] - *NEW*
[FONT=Verdana, sans-serif]Downloads:[/FONT]
[FONT=Verdana, sans-serif]1) rootfs-archtf700t-8-14-2013.tar.lzma[/FONT]
[FONT=Verdana, sans-serif] md5sum dad956c791e54eb1e841db41438601f0[/FONT]
[FONT=Verdana, sans-serif]2) archtf700t-home.tar - /home files for those installing home to Sdcard[/FONT] (Also see below)NOT UPDATED
[FONT=Verdana, sans-serif]3) moreD_cn installer - arch-42-kexec-installer-v0.9.zip[/FONT] (13 Mb)
MD5: 8b4f79b27807f94d8561b83c943e65eeSee Dual-boot thread
I have a modified moreD_cn's installer to allow you to correctly install your /home to SDcard. It is best if you only use this during a fresh install. REMEMBER if you have an existing install you MUST back up your home directory first or you WILL loose your /home files. Once installed you can copy them back.[FONT=Verdana, sans-serif]
Installing:[/FONT]
[FONT=Verdana, sans-serif]1) In Terminal Emulator:
Code:
# su
# mkdir /data/media/linux
2) Copy "[/FONT][FONT=Verdana, sans-serif]installer??.zip"[/FONT][FONT=Verdana, sans-serif] to /sdcard
3) Copy [/FONT][FONT=Verdana, sans-serif][FONT=Verdana, sans-serif]rootfs-archtf700t-8-14-2013.tar.lzma[/FONT] to microsd or SD
4) Boot to recovery
5) NANDROID BACKUP!!!
5) Install "[/FONT][FONT=Verdana, sans-serif][FONT=Verdana, sans-serif]installer??.zip"[/FONT] - It stays at 90% for a while ~20 minutes
6) Enjoy dual-boot Linux Again...[/FONT]
[FONT=Verdana, sans-serif]7) REMEMBER, if you installed /home to anywhere other than in the rootfs (ie mmcblk0p8) and didn't use the modified installer, [/FONT]see roscop2k's excellent Linux tutorial (Thank you roscop2k!)
[FONT=Verdana, sans-serif]When logging in using Pad-Mode (no dock), make sure to tap the password text box TWICE and then tap Focus on the xvkbd.[/FONT]
[FONT=Verdana, sans-serif]Also type your login password carefully, if you make a mistake you will need to reboot... I'm working on it...[/FONT]
[FONT=Verdana, sans-serif]When you do updates for the time being use this – “sudo packer -Syyu --ignore xorg-server,xf86-input-evdev” otherwise you WILL break X[/FONT]
[FONT=Verdana, sans-serif]Highly suggest changing user and root passwords because here they are:[/FONT]
[FONT=Verdana, sans-serif]User:root Password:root[/FONT]
[FONT=Verdana, sans-serif]User:archtf700t Password:archarm[/FONT]
[FONT=Verdana, sans-serif]Thanks again to rabits, roscop2k and others for the help and encouragement![/FONT]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Openbox
[FONT=Verdana, sans-serif]Keyboard remapping layout[/FONT]
Basic rootfs
For anyone daring, here is the plain jane *basic rootfs. You can start a fresh adventure here. Also this will be the base for future patch updating. I will add a short tutorial on getting wireless and touch working soon?...
June 16th, 2013
rootfs-archarm-tf700t.tar.lzma 122mb
I will update this base monthly.
Reserved
Reserved
workdowg said:
[*]accelerated graphics (not using proprietary drivers yet ) - Any suggestions? I have no idea where to start
Click to expand...
Click to collapse
Get the "Linux for Tegra" stuff from NVidia - it includes drivers for X. Or grab them from rabits' Ubuntu image.
_that said:
Get the "Linux for Tegra" stuff from NVidia - it includes drivers for X. Or grab them from rabits' Ubuntu image.
Click to expand...
Click to collapse
I'm working on a PKGBUILD to install them right now... I'll need to do this because Arch is a rolling release and I want to just keep adding to to the original rootfs.
Edit: I have to find a different way to install. I broke my rootfs... My problem is Arch handles things a little different than Ubuntu, so I can't just copy some stuff, it comes from different places. And I'll have to figure that out...
workdowg said:
I'm working on a PKGBUILD to install them right now... I'll need to do this because Arch is a rolling release and I want to just keep adding to to the original rootfs.
Edit: I have to find a different way to install. I broke my rootfs... My problem is Arch handles things a little different than Ubuntu, so I can't just copy some stuff, it comes from different places. And I'll have to figure that out...
Click to expand...
Click to collapse
_that said:
Get the "Linux for Tegra" stuff from NVidia - it includes drivers for X. Or grab them from rabits' Ubuntu image.
Click to expand...
Click to collapse
Got a working rootfs and a backup image... Trying linux4tegra again...
I'm preparing a rootfs image using a modified script from rabits repo... Going to test it installing fresh and see how it goes...
Re: Native Arch Linux on TF700t
workdowg said:
I'm preparing a rootfs image using a modified script from rabits repo... Going to test it installing fresh and see how it goes...
Click to expand...
Click to collapse
Success! My new roots installed it boots I will be uploading to my website tomorrow. I'm on my way to work right now...
Edit: I also got the new Tegra 3 drivers working! Yea!
Sent from my VM "Evo 3D" using 2ʞןɐʇɐdɐʇ .
New rootfs build 0.7
Rootfs is posted for downloading...
Hello,
First, thank you, for your work, archlinux is a nice alternative to ubuntu.
I installed it today, without any problem during install process.
Booted a first time in Arch without the dock, arrived to gdm and has explained i your install doc, i focused the login window then the xvkbd to enter password for archtf700t but it's not returned to login window, no dot or nothing happen once i hit enter. If i type password from xvkbd then clic on log in button, auth fail (Authentification failure).
So then i docked the tf700, this time dot appear on password field, i tried archtf700t password but once password entered i still on gdm screen with "currently logged in" green checked on right of the user name, but i don't log in. Tried then root, once password is typed and confirmed login button became grayed and stay like this forever (wait 5 minutes).
Tried with openbox, Gnome, Gnome Openbox and xfce session, same result.
For archtf700t there's maybe something wrong with home directory, and maybe root isn't allowed to log in by gdm ?
I don't found how to switch to vt1 in order to test terminal log in (considering i never was able to log from gdm thus i never disabled gdm as suggested )
I probably missed something, keep trying.
Thank in advance
Regards
roscop2k said:
Hello,
First, thank you, for your work, archlinux is a nice alternative to ubuntu.
I installed it today, without any problem during install process.
Click to expand...
Click to collapse
Glad to hear it!
Booted a first time in Arch without the dock, arrived to gdm and has explained i your install doc, i focused the login window then the xvkbd to enter password for archtf700t but it's not returned to login window, no dot or nothing happen once i hit enter. If i type password from xvkbd then clic on log in button, auth fail (Authentification failure).
So then i docked the tf700, this time dot appear on password field, i tried archtf700t password but once password entered i still on gdm screen with "currently logged in" green checked on right of the user name, but i don't log in. Tried then root, once password is typed and confirmed login button became grayed and stay like this forever (wait 5 minutes).
Tried with openbox, Gnome, Gnome Openbox and xfce session, same result.
For archtf700t there's maybe something wrong with home directory, and maybe root isn't allowed to log in by gdm ?
Click to expand...
Click to collapse
It seem to be a feature with xvkbd. you have to make sure to click the password line first, then vlick focus button and then click password line again(should have a flashing cursor).
I didn't like Onboard keyboard because it is ugly in gdm, but may have to go back to it for next update...because it works correctly.
I don't found how to switch to vt1 in order to test terminal log in (considering i never was able to log from gdm thus i never disabled gdm as suggested )
I probably missed something, keep trying.
Thank in advance
Regards
Click to expand...
Click to collapse
Keyboard remapping is only happening in X right now, so F keys aren't mapped yet...
Re: Native Arch Linux on TF700t
Links are wrong. I have to fix it in a few hours, when I get to work. It is Ok to use, just the wrong version, 0.7.
Sent from my VM "Evo 3D" using 2ʞןɐʇɐdɐʇ .
workdowg,
First i find why i can't login before (even with keyboard) my microsd inserted in the tablet is formated in ext4, once i remove it, i don't have any authentification failure anymore. Probably the same thing with sdcard port on dock, didn't it ? I'll try this tomorrow.
so the reason why i wasn't able to login with xvkbd before (if we exclude the microsd card issue) is because i don't clicked to passwd field again after pressing focus, my bad so.
root still don't login from gdm (probably disabled for security reason i guess)
archtf700t log in from openbox (don't yet tried other sessions) but just after i still have an empty blue screen (no guys, not the same from Microsoft ...) with xvkbd. I wait several minutes but nothing happen, need to power off the tf700
i'll update with 0.75 tomorrow. By the way, to update i need to restart the installer with the new rootfs image, right ?
One last thing, did you kept e17 in your setup ? should be more handy for tablet style, normally.
Regards.
Re: Native Arch Linux on TF700t
roscop2k said:
workdowg,
First i find why i can't login before (even with keyboard) my microsd inserted in the tablet is formated in ext4, once i remove it, i don't have any authentification failure anymore. Probably the same thing with sdcard port on dock, didn't it ? I'll try this tomorrow.
so the reason why i wasn't able to login with xvkbd before (if we exclude the microsd card issue) is because i don't clicked to passwd field again after pressing focus, my bad so.
root still don't login from gdm (probably disabled for security reason i guess)
archtf700t log in from openbox (don't yet tried other sessions) but just after i still have an empty blue screen (no guys, not the same from Microsoft ...) with xvkbd. I wait several minutes but nothing happen, need to power off the tf700
i'll update with 0.75 tomorrow. By the way, to update i need to restart the installer with the new rootfs image, right ?
One last thing, did you kept e17 in your setup ? should be more handy for tablet style, normally.
Regards.
Click to expand...
Click to collapse
Root login is a no no....
I pulled v0.7.5. I build the wrong rootfs. I was messing around with the new Tegra drivers and got a little mixed up. They didn't work correctly, I need to follow all of the link files.
I have to build and upload it again in the morning/afternoon. E17 worked well. I didn't have the Tegra3 drivers then... I'll definitely try it again. Maybe in .8.0
Sent from my VM "Evo 3D" using 2ʞןɐʇɐdɐʇ .
a few things in my experence so far. first as one the issue of what roscop2k was having where i go to login and it hands with the login greyed out. this happens on both root and the tf700t account. this doesnt happen all the time but it does happen. root login is not disabled i have done it.
roscop2k the blue screen you got with just the keyboard is all openbox gives you. there are no menu bars or anything in the openbox setup you have to right click to get a menu with applications.
the big issue i am having is with date/time. it doesnt remember the date and defaults to like 1999 or something silly and it is making all my ssl connections complain so i have to change it each time i boot and with a dual boot it will prolly happen often as the android side gets better battery life.
i have played around a bit with changing users and stuff it would be cool if there was a way to on the first boot of the image it knows to prompt the user to create an accound so it has the username they like and such. and for some reason the /etc/ssh/ssh_config has the default port set to 12222 is there a reason that is set as the default that i am just not getting.
--jezzirolk
Hi jezzirolk,
Thank for the tip about "blue screen", how did you guess i never used Openbox before ?
ok, get logged as user, start testing environment by installing e17 and walking around.
Re: Native Arch Linux on TF700t
jezzirolk said:
i have played around a bit with changing users and stuff it would be cool if there was a way to on the first boot of the image it knows to prompt the user to create an accound so it has the username they like and such. and for some reason the /etc/ssh/ssh_config has the default port set to 12222 is there a reason that is set as the default that i am just not getting.
--jezzirolk
Click to expand...
Click to collapse
I'll work on a boot user script. Thanks for reminding me about the ports. I forgot I used that...
Time is another story. You need to make sure you set it up. Search the Arch wiki.
Also the REAL new rootfs is up... I triple checked it this time...
Sent from my VM "Evo 3D" using 2ʞןɐʇɐdɐʇ .
Hi workdowg,
0.75 work like a charm.
i'll try to test bluetooth soon, need some mods here (localisation, homedir, etc)
ToDo:
(...)
Install and configure E17 as a third option (v0.8.0??)
Click to expand...
Click to collapse
Openbox looks great, xfce is a bit heavier but comfy too, if people want e17 (like me) or something else, they just have to install it. In previous message i asked if you kept it (e17) because you set it in 0.6.0, that's all. Don't bother you with e17 setup imho.
btw, you should tips people about the space requirement of the setup itself. When you install rootfs from Aroma installer, you need to choose rootfs size, 4Gb should be enough if home is outside i think.
If you've tests to do feel free to ask.
Regards
Re: Native Arch Linux on TF700t - v0.7.9
roscop2k said:
Hi workdowg,
0.75 work like a charm.
i'll try to test bluetooth soon, need some mods here (localisation, homedir, etc)
Openbox looks great, xfce is a bit heavier but comfy too, if people want e17 (like me) or something else, they just have to install it. In previous message i asked if you kept it (e17) because you set it in 0.6.0, that's all. Don't bother you with e17 setup imho.
btw, you should tips people about the space requirement of the setup itself. When you install rootfs from Aroma installer, you need to choose rootfs size, 4Gb should be enough if home is outside i think.
If you've tests to do feel free to ask.
Regards
Click to expand...
Click to collapse
v0.7.9 is up. Many little tweaks for those who aren't as familiar with Arch.
I did add the min requirements in the OP.
Thank for testing...
I'm working on E17. If I can get the Tegra 3 drivers to behave it will probably be my default. I used it on my desktop for a while. Since I got a 8core AMD with 16gb ram and an ssd drive I've been running KDE. It flies on my system...
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Hi, I have installed Arch Linux but I never used Arch Linux before and I was hoping someone that has got it up and running on their Asus would be willing to write up a noobs guide to installing and setting up the basic items needed.
Thanks.
Alan
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reaver for Android v1.30
Reaver-WPS GUI for rooted devices with bcm4329/4330 wifi chipset or working external wifi card.
INFO:
Reaver for Android, short RfA, is a simple-to-use Reaver-GUI for Android devices with monitor-mode support.
It has some very cool features:
Detects automatically WPS-enabled routers.
All Reaver-Settings are accessible from a simple-to-use GUI.
Activates and deactivates Monitor-Mode automatically when needed.
Provides a simple way to connect when Reaver finds the WPA-Key.
External script support
Project status: PRE-FINAL
What does this mean?
There are some features which are not implemented yet.
Developement will continue very soon.
Installation
Download/install bcmon.apk from HERE and RfA.apk from the bottom of this post. RfA may also download bcmon automatically.
Run bcmon, if it crashes try a second time.
If all runs fine, start RfA. If not, your device may be not bcmon compatible. Please see second post.
After selecting an WPS-enabled router, click on "Test Monitor-Mode".
Now you can use RfA, don't uninstall bcmon.
Steps 1 - 4 are only for the installation, they don't have to be repeated once done.
FAQ:
What is this awesome app actually usefull for?
Well, RfA is able to unveil the actual WPA(2)-Key of many routers within 2 - 10 hours.
WHAT?! I though WPA(2) is safe?
It used to be, but then many router models got WiFi Protected Setup, short WPS, implemeted, which is pretty vulnerable. (Details)
Basically it's a Brute-Force attack with Reaver against a 8 digit pin with 10^4 + 10^3 possibilities.
What is Reaver?
Reaver-WPS is a pentesting tool developed by Tactical Network Solutions.
It attacks WPS-enabled routers and after the WPS-Pin is cracked, it retrieves the actual WPA-key.
Reaver provides only a terminal interface, which is ok for notebooks etc., however it's a pain on Android devices.
Because of this I developed RfA.
Doesn't Reaver requires monitor-mode and so can't work on Android?
Yes, Reaver needs monitor-mode, but thanks to bcmon (or external wifi cards) some Android devices are now monitor-mode capable.
bcmon compatibility
Developed and tested on: Nexus 7 2012 (Stock 4.3)
RfA *should* work on all devices with bcmon support (Broadcom bcm4329/bcm4330 chipsets)
Simply try by installing bcmon. Don't worry, if something goes wrong a simple reboot should fix everything.
For external wifi cards please see second post.
Tested & works on:
Nexus 7 2012 (Stock 4.3, Cyanogen 9)
Huawei Honour (Cyanogen Mod based ROM)
bcmon does NOT work on:
Samsung Galaxy S3/4/5
HTC One
LG G2
Nexus 4/5
Nexus 7 (2013)
Credits & used tools:
Monitor-Mode over bcmon.apk:
Omri Ildis, Ruby Feinstein & Yuval Ofir
See: bcmon.blogspot.com
Reaver-WPS:
Tactical Network Solutions
See: code.google.com/p/reaver-wps/
Disclaimer
Attention: Hacking of networks is illegal without having the permission of the owner! The developer is not responsible for any damage etc. this app could cause.
This software is only intended to show a big security hole, not to be able to surf in the neighbours Wifi
XDA:DevDB Information
Reaver-GUI for Android, App for all devices (see above for details)
Contributors
SOEDI, bcmon team & Tactical Network Solutions
Version Information
Status: Stable
Current Stable Version: 1.30
Stable Release Date: 2014-07-01
Beta Release Date: 2013-11-04
Created 2013-09-24
Last Updated 2014-09-27
Second Post
If anyone has working Andorid drivers for external Wifi cards, please let me know,
If the layout looks strange on your phone, please send me a screenshot, so I can fix it
I have only a tablet and HD phone (emulator works to slow), so can't test the layout properly.
Usage of custom-scripts
To make RfA less dependent from bcmon, which seems to be dicontinued, I introduced custom monitor-mode-activation scripts.
Please note that those scripts only have sense for you, if you are already able to use monitor-mode on your device. Ether via special firmware for the internel wifi card or a kernel, which properly supports external wifi cards. Those scripts serve only as a "connector" between your wifi interface and RfA.
In order to enable this function you need to open RfA settings, tap on "Monitor-Mode settings" and disable the "Use bcmon" checkbox.
There are 3 different scripts you can specify:
Activation script
This script will be executed in it's own directory.
It should enable monitor-mode and exit.
Example:
Code:
#!/bin/bash
svc wifi disable
LD_LIBRARY_PATH=/data/data/com.bcmon.bcmon/files/libs
LD_PRELOAD=/data/data/com.bcmon.bcmon/files/libs/libfake_driver.so sh
cd /data/data/com.bcmon.bcmon/files/tools
./enable_bcmon
echo "rfasuccess"
exit
Click to expand...
Click to collapse
Warm-up script
RfA will read in this script as textfile and execute the commands internally. This is needed to execute reaver in the same terminal session as the script.
It should do all prepartions before Reaver is started. At least it has to cd into the directory where the reaver binary is.
Example:
Code:
#!/bin/bash
LD_LIBRARY_PATH=/data/data/com.bcmon.bcmon/files/libs
LD_PRELOAD=/data/data/com.bcmon.bcmon/files/libs/libfake_driver.so sh
cd /data/data/com.bcmon.bcmon/files/tools
Click to expand...
Click to collapse
Stop script
This script will be executed in it's own directory.
It should disable monitor-mode and exit.
Code:
#!/bin/bash
svc wifi enable
echo "rfasuccess"
Click to expand...
Click to collapse
Additional Information
You have also to specify your wifi-interface.
The given examples are those scripts, which RfA uses by default when you enable the "Use bcmon" checkbox.
The activation and stop script have to echo "rfasuccess" in order to tell RfA that they were executed properly. With this method you can also implement a sort of error-checking, by returning "rfasuccess" only when everything went fine.
Click to expand...
Click to collapse
Interesting.... nice job.
But better not let this get into the wrong hands, with these Admin Password hacking apps going on, anyone can take over someones router.
Sent from my super rare, old Scroll Excel running Android 2.3 using the offical app.
DOES DAT APP RUN ON DEVICES STILL ROCKIN 2.3?
Great job folks.
But for some reason user mode bcmode do not work well on HTC HD2 and my custom firmware, so I am using system module bcmon which create eth0 monitor interface instead of wlan0 (wifi0).
Can you please add interface selection or auto-detect interface in monitor mode ?
Tnx !
interface support
Hi,
RfA supports wlan0 and eth0 interface.
The problem seems to be the startup script and location of the Reaver binary, which seems to be different on your HD2.
Please describe exactly how you start monitor-mode, so I can update RfA
regards,
SOEDI
SOEDI said:
Please describe exactly how you start monitor-mode, so I can update RfA
Click to expand...
Click to collapse
Ok.
I have downloaded module src code from https://code.google.com/p/bcmon/source/browse/#svn/trunk/bcm4329/driver/src/bcm4329
Compile for my kernel and use with script that switch drivers with:
Code:
insmod bcm4329.ko firmware_path=fw_bcm4329.bcmon.bin
Firmware version is from https://code.google.com/p/bcmon/source/browse/#svn/trunk/bcm4329/fw
After that I can use sniffer like airodump (airodump -i eth0) and aireplay without need to switch monitor mode with airmon.
---------- Post added at 08:01 AM ---------- Previous post was at 07:11 AM ----------
Ahh, I have just researched the problem.
Problem is at enable_bcmon
Code:
./enable_bcmon
error: SIOCGIFFLAGS (No such device)
error: SIOCGIFFLAGS (No such device)
Couldn't find device index: No such device
I have also tried to start reaver with ./reaver -i eth0 -b 90:F6:52:C0:22:9C -c 1 -a -vv -w -S, but old problem with this drivers occurred, failed to associate to AP (it is not range problem, it is old known inject problem with kernel module driver)
Just have to find a way to make new bcmon working.
[/COLOR]Ahh, I have just researched the problem.
Problem is at enable_bcmon
Code:
./enable_bcmon
error: SIOCGIFFLAGS (No such device)
error: SIOCGIFFLAGS (No such device)
Couldn't find device index: No such device
I have also tried to start reaver with ./reaver -i eth0 -b 90:F6:52:C0:22:9C -c 1 -a -vv -w -S, but old problem with this drivers occurred, failed to associate to AP (it is not range problem, it is old known inject problem with kernel module driver)
Just have to find a way to make new bcmon working.
Click to expand...
Click to collapse
Ok, I see where the problem is....
The method to activate Monitor-Mode over bcmon.apk is:
Code:
define some paths
./enable_bcmon
But if you have self compiled modules:
Code:
sh setup.sh
?define tools path?.
Also on the bcmon website they said they fixed injection. Have you installed the newest firmware files and modules?
If you want to use bcmon.apk instead, maybe try to reinstall BusyBox. Some users reported this fixed their problems.
After you got your Monitor-Mode working, post it and I will update RfA.
reagrds,
SOEDI
First of all thank You SOEDI
Finally someone did it.. reaver is on android...
However i find the job of making it functional only half done...
as i understood from reaver forums it works best with wireless cards based on RTL8187 chipsets
in addition on the site of those modded bcmon drivers there is a statement that it doesn't support radiotap (be it mode or whatever) wich reaver seems to require..
so my idea is why not expanding Your application by adding linux kernel driver to support usb OTG (on the go) plugged in the android device's usb port...
search for phrase "android pcap" in google and You'll find it on kismet wireless
sorry for lack of link.. aperently i'd have to write 9 additional posts to post one
there is a source code down on that site too.. and it's monitor mode with no root priviledges..
plus additionally You also could add a functionality to Your gui to choose between built-in card and the one plugged in via USB-OTG to select wich one the gui is going to use..
So.. how about it? it could be mindblowing if You'd suceed
I'd bet You'd probably make a lot of peapole happy out there
sorry 4 my eventual spelling mistakes engilsh is not my native though..
regards
GusT.
Radiotap Headers
Hi,
The new bcmon.apk method supports radiotap headers, tested and worked At least with bcm4330 on Nexus7.
Monitor-Mode over USB-OTG would be cool, but I'm working on 3 other projects, so this will take some time...
At least it's working pretty good for a beta release
For me, the precess stops at "Switching wlan0 to channel 6".
I have a Galaxy S2 (i think it has a bcm4330 chipset) and android 4.2.2
I got stuck on "Waiting for bacon from etc etc.." is it normal?
ElmirBuljubasic said:
I got stuck on "Waiting for bacon from etc etc.." is it normal?
Click to expand...
Click to collapse
typically that means nobody is using the AP at that time
Reaver
Stuck on waiting for beacon:
Usually this is a range problem.
Try to start another attack, maybe on a different router.
Stuck on switching wlan0 to channel....:
The only solution I have is to simply restart the attack.
Usually this fixes the problem...
Hey great job on getting this working! Been waiting for this for a while, the aircrack solutions out there just take too long for a phone to crack through wpa/wpa2.
I'm having some issues though btw im on samsung galazy s2x which has the bcm4330. First off the bcmon starts up and enables monitor mode just fine but when I come to scan networks in reaver it nevers successfully finds any. I've tried to increase scan time and i've enables scan fix but nothing seems to work. I know my device is in monitor mode since i can scan for networks on another app, I can also reveice data packets but it's just not working on here any ideas? thanks awesome work!
The solution is pretty simple:
RfA scans in Managed-Mode, then enables Monitor-Mode and passes the data to Reaver.
So RfA can handle the Monitor-Mode on it’s own, no need to start bcmon first
Simply start RfA with wifi on
regards,
SOEDI
Thanks for the clarification now once I've scanned for networks connections come up like it should but i'm getting a new problem when testing monitoring mode it fails. I believe that this could be because of bcmon since the app doesn't seem to properly install the modded drivers. I could be wrong. I think i'm running into compatibility issues with my rom. I'm using MIUI I'm gonna try cyanogenmod to see if it helps anything.
hi
great work but im having a problem i have a htc wildfire s
evry time i start cracking a network i get (illigal instruction ./reaver wlan....)
and then nothing i think this is from my rom mostly but im not sure
my phone is fully rooted thx in advance
Alright well guess mini was causing problems with it so I guess that's not compatible working great on 4.3
Sent from my SGH-T989 using XDA Premium 4 mobile app
I'm on 09/26 cm 10.2 nightly and using galaxy s2, router is Linksys wrt110. First I wasn't able to get past "switching wlan0 to channel 1"
And if I enabled monitor mode in bcmon before scanning in rfa no router is found. how I got it to work was to scan first and once I found my router i tested for monitor mode. Before starting attack i used home button and then open bcmon and enabled monitor mode ( I had already said yes to install tool on first run), press and held home button and went back to rfa and started attack.
This was the result.
I do have a question though.. This was tested on my own router and my password is set to 0123456789 on the router. So what exactly do I have to enter from the result to connect?
I tried this on Kali as well and I got similar result, can remember if it was exact same.
I tried the WPA psk and the pin as passwords and was not able to connect to router. And my router is set to wpa2. Is that why? I kno this is off topic but I'm curious
Sent from my GT-I9100 using Tapatalk 4 Beta
Wow, seems like RfA has some problems with the S2.
Cool workaround!
Regarding your problem:
The shown WPA PSK is the hash of your real WPA Key.
Sometimes Reaver fails to get the plaintext Key and shows instead the hash.
However, if you use the hash as WPA Key it should work. Had tried this a few times and worked fine
regards,
SOEDI
EDIT:
Of course, you have to use the hash withoud the ' ' as key. Wanted only to mention this
RfA should have shown a Dialog with the Key and a connect button. Did it?