Related
I have two PC's, one is a XP Media Center Edition. It had a virus on it and kept getting a corrupt file, so my techyish relative came and wiped the hard drive from scratch ( or so he says but it was a partial wipe) and reloaded the OS onto it. It worked fine, but then kept getting the corrupt file again. I then decided to order the recovery disks from HP, which is the computer manufactuer. They arrived and I put them in, followed the steps, and all wen well until I came to the recovery partition. It was backing everything up ( one time process only) into the recovery partition all fine and dandy until it came to a file that had to do with Microsoft Office. It stayed their for about 45 minutes backing up this file where the longest had been 10 minutes max for all the others. I looked the file up and it said it was a small 10 mb file, so I turned the computer off and went to normal without the recovery partition. Worked fine until one day something happened and I guess I needed to do the recovery again (it's been a few months since this has happened) and did all the steps, but it wouldn't take. It gets to about 4% and then dies with a BSOD and this message:
A problem has been detected and Windows has been shut down to prevent damage to your computer.
DATA_KERNAL_INPAGE_ERROR
If this is the first time you’ve seen this stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
Technical information:
*** STOP: 0x0000007A (0xE121F318, 0xC0000185, 0xBF8B6147, 0x1C610860)
*** win32k.sys – Address BF8B6147 base at BF800000, Datestamp 3b7de698
Copied it down word for word, space for space. Can anyone help me get this thing up and running again? It's now getting important.
Forgot to mention that I get the same problem each time I put the recovery disk in.
I'd recommend using a NON-Recovery Disk, but rather a Clean, Non-OEM, Windows Disk. If the issue pertains to the Kernal, it's usually unfixable without a Hard Boot of the Drive. You should do more than Re-Format.. you should delete all the partitions off of your Hard Drive with a Windows Disk, then pop in the Recovery Disks and do the OEM install.
So I need to wipe the hard drive clean again and put in another non OEM OS?
Not quite. Wipe the HDD clean with the NON-OEM Windows Disk, as most Recovery Disks do not allow you to alter the Partitions [Everything is done for you], then pop in your Recovery Disk and let it install the new Primary, and possibly the Recovery, Drives.
I see what your saying now, so what exactly happened to it?
Get Windows 7
I have windows 7, that's my other computer.
The guy at the un paso store got you too!!
At the step store? Lol.
PurpleLlamaLover said:
I see what your saying now, so what exactly happened to it?
Click to expand...
Click to collapse
When your supposed "Tech Savvy" friend attempted to fix your computer.. he, I'm assuming, did a simple "Repair" of the partition with an XP Disc. That is LITERALLY the most unwanted version of a fix ever... All it does is replace the system files, but keeps all of the other software that may have been conflicting with the system itself, BUT usually, all of the software is inaccessible. It's still on your computer, f*cking it up, but you can't see it.
Thus I always say, "If you get a bluescreen... more than once, and don't know what the code means... don't repair your computer.. re-format that b*tch after recreating the partitions."
But, if your XP compy has the specs to support Windows 7, your best bet, all in all, would be to install Windows 7. Doing so will save you the hassle of having to manually download all of the drivers for it... unlike installing a non OEM Windows XP [have to download & install the drivers manually].
PurpleLlamaLover
it sounds like the HP recovery disk could well be corrupt,
So you now have 3 options:
1. Try Linux Ubunut 10.4 LTS (Free Distro)
2. Buy a ligit copy of Windows 7
3. Download Windows Vista / 7 / XP from a torrent
and try untill you find a OS you lyk
Agent Zach said:
When your supposed "Tech Savvy" friend attempted to fix your computer.. he, I'm assuming, did a simple "Repair" of the partition with an XP Disc. That is LITERALLY the most unwanted version of a fix ever... All it does is replace the system files, but keeps all of the other software that may have been conflicting with the system itself, BUT usually, all of the software is inaccessible. It's still on your computer, f*cking it up, but you can't see it.
Thus I always say, "If you get a bluescreen... more than once, and don't know what the code means... don't repair your computer.. re-format that b*tch after recreating the partitions."
But, if your XP compy has the specs to support Windows 7, your best bet, all in all, would be to install Windows 7. Doing so will save you the hassle of having to manually download all of the drivers for it... unlike installing a non OEM Windows XP [have to download & install the drivers manually].
Click to expand...
Click to collapse
I'll try and get 7 for it. It was the last of the XP models, just before vista so i'd think it should be able to run 7. Think I need a new hard drive?
Bro that Simon_WM guys a genius. Listen to him.
Yea. This is my computer here, http://h10025.www1.hp.com/ewfrf/wc/...en&dlc=en&cc=us&product=3257746&lang=en#N1030
Think it'll run it?
PurpleLlamaLover said:
Yea. This is my computer here, http://h10025.www1.hp.com/ewfrf/wc/...en&dlc=en&cc=us&product=3257746&lang=en#N1030
Think it'll run it?
Click to expand...
Click to collapse
it may run with a lag
I just want it back up and running, I don't want vista though. On the little windows sticker is says "Vista Capable" but i've heard bad things about it, especially rom updating.
PurpleLlamaLover said:
I just want it back up and running, I don't want vista though. On the little windows sticker is says "Vista Capable" but i've heard bad things about it, especially rom updating.
Click to expand...
Click to collapse
ummm i use vista and have updated all my win mo phones on it...never had a problem
Really? Well, i'll keep in mind if I can't get XP back on it. I'd rather just have 7 and XP. I don't care what it runs as long as it runs again.
the best suggestion in this thread was install linux , however i take it that isn't a possibility. so here's what you need to do, you will require the following:
1) a fresh mind
2) a freshly burned copy of XPwhateverflavoryouwant
3) you do not care about anything on that drive.
put in freshly burned xp into computer, boot to cd drive, follow onscreen instructions, delete all partitions, create new NTFS partition, install to new partition.
if error comes back, it is not a software issue. fixing a xp bsod really is simple if it isnt hardware related.
I'm an experienced computer user in Windows and (X)Ubuntu, but some things I don't know I search online... but this problem I get only gets me somewhat upset by "Search Overload" (See some United States commercials).
## My computer setup ##
OS: dual-boot Windows XP; Xubuntu 10.04 LTS
Boot Loader: grub
In the partitions:
- Windows XP
- Xubuntu 10.04 LTS
- swap
- factory OEM partition
I need to reinstall Windows completely. I can either...
1. get that ISO of "The Windows 9x Project" burnt (I have an XP upgrade version),
2. borrow my friends OEM disk (I DO have a legit XP CD but it is only an Upgrade version ), or
3. try to get that special partition to install EXACTLY the way I want it to (most likely impossible)
Also, I've been trying to reinstall the grub bootloader (which originaly comes with my Xubuntu disk) manually, but it has been unsuccessful so far.
This will also be able to help me in case a Windows program rewrites the MBR (or I need to do this task again).
What I don't want to do unless it is the only possible way:
- Reinstall Xubuntu 10.04 LTS (plus install all of those updates and change Firefox... again!!!)
==================================================
Current Status:
==================================================
Will try to use the Windows 9x Project .iso and use my legit XP upgrade CD+key
- will take a lot of time to accomplish, IF successful
- I hope that Windows ME will work with my system -_-'
"I'm an experienced computer user in Windows and (X)Ubuntu"
I lol'd a little.
I don't get what you're asking for. Advice on loading grub? Telling you that XP needs to die as an outdated OS? Ubuntu should be illegal under computer misuse legislation?
You state your current progress and methods to get where you're going, there is no "where now?"question to your post.
Have you considered virtualisation as an alternative to your lack of understanding dealing? This way you can still have the "I'm cool I run ubuntu", without having to try and understand it.
For the record, ubuntu is an abomination and should never have been made. Debian is good, don't mess with perfection.
If this reply succeeds in posting, lock this post due to inactivity (my 100G HDD is too small for dual-booting WinXP & Xubuntu, imo)
EDIT: I totally know Ubuntu sucks (one example: poorly made packages require only one type of sound interface -- read: pulseaudio)
Sent from my HTC Evo 4G using Tapatalk (GetJar version)
First off this is completely from Rennat over at PreCentral
-------------------------------------------------------------------------------------
TUTORIAL: How to get the UbuntuChroot up and running for your HP TouchPad
Intro:
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card.
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.
Warnings:
I nor WebOS Internals take no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do endup messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.
Step Zero:
- I have provided 2 different ways to set your device up to install the UbuntuChroot onto your device; use the meta-doctor and create your own doctor (Step 1-A) or do as Step 1-B says and contact my army of monkeys for an easier alternitive that won't take forever.
##You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so! And done hesitate to ask questions.
Step 1-A: Creating a WebOS Doctor
- We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.
- Use the WebOS Internals Guide to installing and running the Meta Doctor. In Step 2 you will have to rename you downloaded webOS doctor to the name of the Bell Mobility doctor they have under Step 2'3 (webosdoctorp100ewwbellmo.jar) go ahead and add the webOS version after it like it advises.
- In Step 2'6, if you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.
- Once the Meta Doctor is done, run the Web's Doctor it created under the 'builds' folder. And setup your device.
Step 1-B: Contacting My Army of Monkeys
- If you are having trouble with or are intimidated by Step 1-A go ahead and contact my army of monkeys at [email protected]. Simple.
Step 2: Mounting the new ext3fc partition on bootup
- Now before we continue we have to make sure we have the partition fully setup and mounted on bootup. To do this follow the below WebOS Internals instructions.
All of this is done on device either via novaterm or an SSH login. (simpler terms mean use WebOS Quick install by connecting you device, opening WebOSQuickInstall, and click Tools-Command Line.) If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:
Code:
mount -o remount,rw /
mkdir -p /media/ext3fs
it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.
After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.
Code:
mount -o remount,rw /
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab
Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.
Code:
mount -a
If you do not want it mounted at bootup, but you do need it mounted, you can use this command.
Code:
mount /dev/mapper/store-ext3fs /media/ext3fs
Click to expand...
Click to collapse
Step 3: Adding Testing Feeds
- Follow these WebOS Internals Instructions to add the Testing Feeds.
NOTE: These are edited slightly and will only work on a Wifi only TouchPad.
- Open Preware and wait for it to finish loading.
- Open the App Menu (tap "Preware" in the top left corner of the screen) and tap Manage feeds.
- Scroll to the bottom until you see the New Feed box.
- Type or paste a name (webos-testing-armv7) and URL (Right Click - Copy Address) sure the URL does *not* have a slash at the end.
- Make sure the IS COMPRESSED option is set to YES.
- Tap Add Feed and then tap Yes when the alert pops up.
- Gesture swipe back. Preware will alert you that you have added feeds and ask if you want to update them now. Choose YES.
Click to expand...
Click to collapse
Step 4: Installing UbuntuChroot, Xecutah, and XServer
- Open up Preware and tap List Of Everything.
- Search for and install the following: UbuntuChroot, Xecutah, and XServer
- Now opened Xecutah and tap XServer and a new card will come up.
- Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.
- Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:
Step 5: Installing Programs
- Now to have some fun after all that work you put in!
- Type the below and it will update the program lists.
Code:
apt-get update
- Now type the following to install what ever you wish!
Code:
/***type the below for AbiWord
apt-get install abiword
/***type the below for the Chromium Browser
apt-get install chromium-browser
/***type the below for GIMP
apt-get install gimp
/***type the below for Eclipse
apt-get install eclipse
/**type the below for LibreOffice
apt-get install LibreOffice
/***type the below for LXDE (a windows graphical interface) and then launch it by typing lxsession.
apt-get install lxde
---------------------------------------------------------------------------------------
agian from precentral enjoy guys
Mods please move to there thread i was in a rush (dead battery) and put it in the wrong forum
Does anything else besides chromium, abiword, eclipse, libreoffice, lxde and gimp work?
linkinpark4175 said:
Does anything else besides chromium, abiword, eclipse, libreoffice, lxde and gimp work?
Click to expand...
Click to collapse
anything you can compile for ARM or want to compile for ARM. there is a apt repository.
You could also find a complete guide to install Ubuntu Linux on HP TouchPad here
same thing
XDAnoobr said:
You could also find a complete guide to install Ubuntu Linux on HP TouchPad here
Click to expand...
Click to collapse
agian that is only for Chroot which is the exact same thing
Works great, now I have lxde on my touchpad.
able to get ubuntu chroot working properly, with libreoffice
now, hunting for a Bluetooth Keyboard
any one going to test if BT Mouses work? (yeah, i know theres a touchscreen)
Is multi-touch supported on this?
what version of libreoffice does it install the latest one? And if anyone has installed it the ubuntu laggy or is it normal.
harsh3090416 said:
what version of libreoffice does it install the latest one? And if anyone has installed it the ubuntu laggy or is it normal.
Click to expand...
Click to collapse
a little laggy sometimes, but still usable most of the time without any problems
libreoffice 3.3.2... you should probably check the ubuntu ARM 11.04 repository to see what is there
top says 1gb ram, 0.90gb used.... not sure why......
EDIT: Tried pairing a BT Mouse... able to find the device via "BT->Search other", but unable to pair properly. Mouse said paired successful, but touchpad couldnt continue, kept searching for devices
Tried "BT->Search Keyboard", but couldnt find the mouse this way
Now they have Debian chroot. Works great as well. Both can coexist at once. All it is is a folder at /media/extfs
Btw, has anyone gotten gnome working? I keep getting segmentation faults.
Is there a way to make that partition without meta doctor?
DJGonzo said:
Is there a way to make that partition without meta doctor?
Click to expand...
Click to collapse
metadoctor makes a partition
you could loop a filesystem ontop of the existing partition to avoid this issue, but the page below recommends against it
http://www.webos-internals.org/wiki/Chrooting
mount: mounting /dev/mapper/store-ext3fs on /media/ext3fs failed: No such file o
r directory
Why am i getting this error when trying to mount? It's really ticking me off as I haven't done anything different from the instructions.
I just spent an hour redoing the whole thing and guess what... i'm pissed off
same ****
samvillian said:
mount: mounting /dev/mapper/store-ext3fs on /media/ext3fs failed: No such file o
r directory
Why am i getting this error when trying to mount? It's really ticking me off as I haven't done anything different from the instructions.
I just spent an hour redoing the whole thing and guess what... i'm pissed off
same ****
Click to expand...
Click to collapse
looks like you didn't do metadoctor properly,
or you didn't make the /media/ext3fs directory,
or "mount -o remount,rw" didn't execute properly
1st problem: your touchpad should have around 10GB free(out of 16GB, or do the math if you have a 32/64gb)
2nd problem: go back to cmd prompt and check that /media/ext3fs exists
3rd problem: reinstall via webos doctor and do it again
kevina90 said:
Now they have Debian chroot. Works great as well. Both can coexist at once. All it is is a folder at /media/extfs
Btw, has anyone gotten gnome working? I keep getting segmentation faults.
Click to expand...
Click to collapse
Sorry, this is off topic. I'm sure Android will get here, but I really want to use my Touchpad (I haven't done much because I figured everything would get wiped anyway this weekend), so I think I'm going to give Linux a go. My understanding of Linux is rather crap. I thought Linux was the OS, and Ubuntu and other things were just GUIs to make it easier for people unfamiliar with command line. How could Debian simultaneously coexist?
I know I could go to wikipedia and look around and try to understand it, but by chance does anyone know any website that kinda describes Linux to beginners? I don't just want to follow the directions step by step on the guide (although its brilliant, looks very easy)without having the slightest effin idea what everything is, you know? Its weird, Linux confuses me, I don't know why. I've used ubuntu a number of times but it's just browsing firefox, not exactly rocket science!
Thanks if you can easily give link and press send then thanks but don't go out of your way, I can find something eventually, but I don't want someone else mucking around for my sake. Its no emergency.
Komodo Rogue said:
Sorry, this is off topic. I'm sure Android will get here, but I really want to use my Touchpad (I haven't done much because I figured everything would get wiped anyway this weekend), so I think I'm going to give Linux a go. My understanding of Linux is rather crap. I thought Linux was the OS, and Ubuntu and other things were just GUIs to make it easier for people unfamiliar with command line. How could Debian simultaneously coexist?
I know I could go to wikipedia and look around and try to understand it, but by chance does anyone know any website that kinda describes Linux to beginners? I don't just want to follow the directions step by step on the guide (although its brilliant, looks very easy)without having the slightest effin idea what everything is, you know? Its weird, Linux confuses me, I don't know why. I've used ubuntu a number of times but it's just browsing firefox, not exactly rocket science!
Thanks if you can easily give link and press send then thanks but don't go out of your way, I can find something eventually, but I don't want someone else mucking around for my sake. Its no emergency.
Click to expand...
Click to collapse
I would just find a book on amazon about linux with good reviews made in the past 1-2 years. I would look for one that is distribution neutral.
The reason you can have webos on there and another version of linux is because it's basically installed in another partition (not really, but that's the easiest way I can describe it to you). The actual details of how chroot works are different, but that should relate enough to you to get what it it is.
Linux is the Kernel. Debian, Ubuntu, Fedora and the rest are distributions of that kernel along with a GUI, and programs to make it a fully functional OS like Windows or OS X.
The Debian and Ubuntu on WebOS is minimal pared down distribution with no gui.
I just went thru all the steps , contacting the army of monkeys, and installed all the preware stuff.
I get Service Error Unable to run command : /sbin/initctl start org.webinternals.debian-squeeze etc etc
Unknown job org.webosinternals.debian-squeeze-chroot.
I got this with the Ubuntu chroot too. any ideas?
paperWastage said:
looks like you didn't do metadoctor properly,
or you didn't make the /media/ext3fs directory,
or "mount -o remount,rw" didn't execute properly
1st problem: your touchpad should have around 10GB free(out of 16GB, or do the math if you have a 32/64gb)
2nd problem: go back to cmd prompt and check that /media/ext3fs exists
3rd problem: reinstall via webos doctor and do it again
Click to expand...
Click to collapse
I've redone webos doctor like 4 times already.
How do I check if the directory exists? Plus i'm on a fresh 32gb, so its not that.
thanks
edit: i tested to see if the directories existed and i found a possible error.
i just cd to the folder to see if it exists, and media/ext3fs existed.
but the /dev/mapper/store-ext3fs doesn't exist apparently...
would that be the issue?
Right before the Introduction, I am not responsible for anything you do to you Phone, you are free to do or not to do what I am explaining to you so its on your own risk...
Introduction:
Ok guys so here we are, trying to install a Linux Distro on our awesome x86 Phone...
Damn this doesnt work because our Android is compiled in a different way than ARM Android so we have to wait for better Docs or someone who can get the bootloader to laod a different OS...
But you dont want to wait right?
So here we go, the only alternative:
Chroot into Linux
Description:
Chrooting lets you run annother Linux on top of the currently running Linux (what Android actually is...more or less).
So you mount an existing Linux and simply run it.
What I want to do:
I want to guide you through chrooting and setting up an Arch Linux on your RAZR i.
Requirements:
You need:
A micro SD card (I used a 8GB sized one but 4GB/more than 8 should also work, you just have to adjust some Steps)
An Arch Linux Image (I will give you a link)
(Not required but I will focus on this Platform because I use it myself and it works best, I guess)
A Linux PC running Virtual Box
Tutorial:
First you need an Arch Linux Image. Any other Linux Distro should work fine, but others also take up a lot more Space and Ubuntu for Example has many Problems running in Chroot (because Canonical did some S***).
I used this one:
Arch Linux 2012.10.06
Again, any Version should work fine, just took the latest one
So lets set up our System...
Start Virtual Box and create a new System.
Create a new Hard Drive and size it so it fits onto your micro SD.
I used 5 GB-7.5GB on a 8GB micro SD.
Insert the downloaded ISO FIle into the Virtual Box CD Drive and start your Virtual Machine.
Select the i686 mode (because or CPU is 32bit not 64bit)
If you have the wrong Keyboard Layout Follow this Keyboard Setup Keyboard Config
Next you need to partition the HDD: Partitioning the HDD
Now Install the Base System: Install the Base System
After this follow the next Steps on the Arch WIki (Generate an fstab, Chroot and configure the base system, Set the root password and add a regular user)
DO not reboot because you didnt create a Bootloader (not required for chrooting), instead go to the "Extra" Section and follow all Steps till troubleshooting (DO NOT REBOOT AND DO NOT STARTX this didnt work for, might for you, might not and then you have to cold reboot the VM)
Now you can reboot Again enter the Live System, load your keymap and chroot into the system
You might already install some Packages like a VNC server (pacman -S tightvnc) which will be required for a Graphical User Interface later...
To create the Image you need later, the easiest way for me to pull the Image out of the VM (which has no space for this Image) because the Virtual Box Plugin didnt work for me is sshfs.
I highly recommend to install an ssh server ond the sshfs system into you arch.
If you have done so, mount your PC from inside the VM so you can put the Image on your PC's HDD.
now to create an Image of your Arch theres one command and two ways:
You create an Image of the whole HDD (what I did)
You create an Image of the one Partition
I chose the first because i didnt want to put anything else on my micro SD, I cant confirm that the second way works but it is suppoes to so lets create the Image:
We make use of the Linux command dd, really, REALLY mke sure that you are executing from inside the VM since you can harm your HDD and dont forget the file extension....
First method:
Code:
dd if=/dev/sda of=/location/to/your/PC/HDD/imagefilename.img
The Second method (not confirmed):
Code:
dd if=/dev/sda1 of=/location/to/your/PC/HDD/imagefilename.img
where sda1 should be the partition you want to image...
This might take a loooooooong time
Now you have this Image, put your micro SD into an Adapter and put it into your PC.
Now find out the name of the SD, I used gparted and I found out that the name is sdc (could be sd + letter of alphabet)
Here the Ways split again:
The first Method completly overwrites anything that is on your microSD so make a backup, the second Way is just putting the created .img file onto the micro SD:
Method One:
Code:
dd if=/path/of/the/img/file of=/dev/sdc
Replace sdc with your micro SD letter, if you put in a wrong letter, you might overwrite your HDD so be careful, I am not responsible for what you do...
For me my Phone said, the micro SD is empty or has a wrong FIlesystem (its ext4) but you shouldnt care, we can mount it anyway...
Now copy the FIle mountscript.sh to the internal SD (the FIle is in this Posts Attachements)
Next open up a Terminal and type in:
Code:
cat /proc/partitions
You should get a list of all your Partitions, if you followed my Way, the last one should be your micro SD (look at the size) and called like mmcblk1p1
If you followed the Second Way, you dont need this Step...
Now type in the Terminal:
Code:
busybox sh /mnt/sdcard/mountscript.sh
the busybox in the beginning seemed required for me because our busybox is kinda strange...
You will be guide through a little setup, I hope it is selfexplaining...
When the script ran through successfully your terminal should look like [[email protected] /]#
In the next Post I will guide you through the Setup of the VNC Server
Any questions or something doesnt work? Just tell me
//Robert
Post reserved for VNC Tutorial
You can start by grabbing yourself this App...
Guess I forgot something
Added the mountscript as Attachemenet
did anybody try?
//Robert
this should fix network issues:
https://blog.tuinslak.org/socket-permission-denied
Hai Robbilie, After install with Ubuntu PC & turn off pc & All seem ok & at phone till [[email protected] /]# & open installed VNCwith name DLKS & 192.168.0.9 & port 5900 but cant handshake & also try many similar VNC still the same. Unlike our PC where on>boot>desktop shown & can play ? Pls advice. Thks.
i advice tiger vnc, but the console tells you the vnc server started?
btw its only 5900 when its on display 0 when its on display 1 its 5901 and so on...
the used display is shown in the console...
are you running the vnc from root?
How to run vnc from root? i only start separately,pls advice.Thks
if you have a vnc server installed in the chroot environment you need to run
vncserver -geometry 888x540
this is just to fit the phones resolution
I'm following your instructions for this. They are well written but I can't figure out the part about ssh and sshfs. What do you do for that step?
Is there seriously not an easier way such as opening the vdi image with some program and copying and pasting the files to my Windows desktop and then using something like IMGBurn to create an iso file and then convert it to an img file?
Ubuntu ?
Hello
I just see this old news when i would like to install Linux Mobile , any news about or link ?
http://www.firstpost.com/topic/prod...otorola-razr-i-video-9n_E6aapPSo-51417-1.html
Thanks
EDIT : http://sourceforge.net/projects/mpsdk/
Hello, recently purchased a asus tf701t laptop/tablet hyrbid and the device itself is perfect. Powerful cpu, good storage and an insane 2k resolution for a 10' inch screen which I don't think has been done before.
However I absolutely hate android (no offense to android developers) and decided to try installing Linux Mint 17 which can be installed on any regular laptop easily. Essentially, I want to get rid of both android bootloader and the OS itself and replace that with Grub bootloader and Linux Mint 17 OS. But android is fighting me every step of the way trying to prevent me from doing just that I unlocked the bootloader so my warrenty is void now.
But beyond that I can't install linux iso because the android bootloader isn't registering the usb stick (with linux iso on it) so I can't launch the linux live iso at all. I tried using cdrom iso using disk to launch through usb and still doesn't come up in the bootloader options. I know its possible to use linux on these devices because I've seen people have done it before on the internet.
I am now at this point starting to consider android itself as malware as the very definition of the word, ....lets start with the fact that they locked the bootloader, prompting me to give ip address just to enable me to unlock the bootloader (malicious and very dodgy). No root access therefore, third party programs are required to enable root which further my belief that android os is more malware than it is a legitimate operating system. Lastly, either possibly no usb driver for bootloader or usb port is locked out by design at bootloader (either way, might explain why I can't use usb linux iso).
What I can't understand is, why google can lock down a device tighter than fort knox on a Asus brand device. This is like buying a brand new car and not being able to open your own car even though you purchased it. What google has done is borderline illegal and I'm abit astonished how they can get away with it...
Sorry for the rant guys I'm abit fustrated atm. Can anyone please help me? I really love linux mint and if its possible to format android and install linux mint on this device I would be eternally grateful
Update: I attempted to flash the device with the command: fastboot -i 0x0B05 flash recovery recovery.img which works...but when I reboot and push power and down volume into bootloader...and try to get into recovery...the screen looks like its about to load into it but then resumes boot of android.
I'm really puzzled by this. So cannot flash a custom recovery for some strange reason
Its not so simple I dont think. You might want to watch whats happening on this thread for now.
http://forum.xda-developers.com/transformer-tf701/general/native-linux-asus-tf701t-t2973119
I would think you would have to completely replace the bootloader with something like uboot maybe if you wanted to wipe the tablet. But I dont think anyone knows. Then you could end up with some permanent brick. There would be no recovery or fastboot option if you were somehow able to get some kind of boot loader on this thing. I have no idea.
Edit: Also there is no arm based Linux Mint afiak.
YayYouFixedIt said:
Its not so simple I dont think. You might want to watch whats happening on this thread for now.
I would think you would have to completely replace the bootloader with something like uboot maybe if you wanted to wipe the tablet. But I dont think anyone knows. Then you could end up with some permanent brick. There would be no recovery or fastboot option if you were somehow able to get some kind of boot loader on this thing. I have no idea.
Edit: Also there is no arm based Linux Mint afiak.
Click to expand...
Click to collapse
Thanks I appreciate the reply. I understand this won't be easy but I'm stubborn that way
Can you give me some advice on where I can start learning how to place a native linux os on the device? Would grub bootloader work with tf701t?
have you considered returning your tf701 and replacing it with the tf700 infinity? you can replace the OS with ubuntu.. theres much more support for that model than the tf701
tf701mega said:
have you considered returning your tf701 and replacing it with the tf700 infinity? you can replace the OS with ubuntu.. theres much more support for that model than the tf701
Click to expand...
Click to collapse
Out of curiosity, have you used the tf700t? it is good for development, but it could run pretty slow at times. It might of been because of the tegra 3 processor, because the tf300t also had this performance issue. I was barely able to type up documents on a CM Rom because the tablet would lag when typing out and would then force close and corrupt my document.
atleast for me, that was the reason why I went with this one rather than the tf700t. This is just my 2 cents about getting the tf700t. I would suggest trying it out before getting it.
Sent from my K00C using Tapatalk 2
Just how stubborn are you?
How much work do you want to put into this? There are two options, the easy route that you probably will consider imperfect, and the much more complicated route that I'm not certain will work. I'll do my best to explain both.
The method I use is to install a linux distro (in my case, ubuntu) inside a chroot. There are several apps on the android market to help you set this up. The one I used sets up an Xvnc server, so you can view your linux desktop by using an android VNC viewer -- but it's just connecting locally, not going over the network.
This works nicely out of the box, but it's slow, partly because it's using the VNC protocol and partly because there's no 2d hardware acceleration. I tinkered with my setup and installed XSDL, a native android X server with hardware acceleration. I had to modify the linux startup script to skip starting Xvnc and instead connect to XSDL (which is on :0.0 like a normal X server).
This works great and is fairly fast. For me, this is a good compromise between a full-fledged linux laptop and the convenience of android apps written specifically for a multitouch screen. I generally do most of my stuff in Android, but I can drop into my Ubuntu desktop whenever I need more power.
The really big downside is that it's hard to prevent Android's low-memory killer from sacrificing XSDL when I haven't used it for awhile. I've mucked about with various solutions involving oom_score_adj and such, and that helps, but android still ends up killing my X server sometimes.
So, that's the easy method. For the more complicated method, I'm just theorizing, and this stuff may not work. You're going to need to either already have somewhat deep linux knowledge or be willing to learn Here goes.
In this post, I described how I managed to boot my tf701t after the internal memory card died a horrible death. The important bit here is that I learned how to boot any initrd/kernel combination using fastboot, and how to roll that combination into a boot.img so that the tablet always boots it. This is what you'll need to do both for the installation and for future boots into your Linux install.
First off, choose your Linux distro. I don't think you'll be able to use Mint, since, as someone pointed out above, there's no ARM build of Mint. However, there is an ARM build of Debian and Mint has the "debian edition", so maybe there is an ARM version. It may be, though, that the Mint folks only built their special stuff (Cinnamon/mate/whatever) for x86 platforms. I'd recommend Ubuntu as a compromise since I know it runs on the tf701t.
For the initial installation, put the contents of the install ISO onto an SD card -- just copying your bootable USB drive over should work. Now for the tricky bit: you'll need to pull the kernel and initrd ("ramdisk", "initial ramdisk" -- usually initrd-<something>.gz) off of the usb drive and into a working directory on a Linux laptop or desktop (let's call it the "host"). You might get away with just fastbooting this kernel/ramdisk directly. Install the fastboot package for your distro (Ubuntu has one, anyway). Connect up your tablet, put it in fastboot mode (I think that's done by booting with volume up and down held) and do 'fastboot boot <your kernel> <your ramdisk>'.
This will boot the kernel and load up the initrd, which is a tiny little linux filesystem stored in memory. The kernel runs a program called init inside the ramdisk and init takes over and boots into the actual installer. The question in my mind is how it goes about finding the ISO contents. If it searches by filesystem UUID, and there's a good chance that it does, then it will find your the ISO contents on the SD card just fine and the installer will start up.
If not, well, things will get a lot more complicated. Normally what one would do in a case like this would be to pass kernel command-line arguments (you do this in the SYSLINUX bootloader for distros like Ubuntu) telling it where to find the installation media. We can't do that because fastboot doesn't let you pass command-line arguments. Instead, you'd need to extract the initrd on the Host machine, modify the init script in some way to tell it where to find the installation media (probably /dev/block/mmcblk1p1), and then repackage it. I went into somewhat shallow detail on how to do the extract/repackage parts of this, but this is where either prior linux knowledge or a willingness to do some research comes in. Hints: gunzip the initrd, then use the cpio tool to extract it.
Okay, so let's say that you get the installer booting. The next big question is whether it's going to work at all. In theory the graphics chip inside the tf701t is supported by linux, but in practice, maybe it's only supported by a kernel module that Samsung built. Maybe you'd need to substitute the stock kernel. The next question is whether X has a module that will work with the graphics chip. But maybe even if it doesn't you can use a text-mode installer. That would at least let you get a system installed that you could then hack on to try to get X running.
So, let's say you do get linux installed (probably onto the internal SD card, /dev/block/mmcblk0). Now you want to boot it. You'll need to look into the installed system and steal its kernel and ramdisk, and get them onto the Host machine. Or maybe you could just extract them from the debian packages, since I'm not sure how you'd get things off of that internal SD at this stage. As a hint, these may well NOT be the same kernel/initrd as in the installer.
Once you've got the kernel/ramdisk, you can try to boot into them with fastboot. If that works (big if), then you'll want to be able to boot them without fastboot. That's where the 'fastboot flash:raw' command comes in. It takes a kernel/ramdisk, builds an android boot.img out of them, and flashes it to the device. From then on, the device will boot that kernel and ramdisk by default.
So, in theory this could work. The biggest potential stumbling block is whether X is going to natively support the graphics chip. If it doesn't, you may be stuck using the basic framebuffer driver, or maybe that won't even work at all. ...or you could just settle for the chroot method and be done with it
Good luck. I'm very interested to hear whether this works. I'm probably not going to try it myself since I like Android enough that I want to keep it around. I also can't walk you through this in finer detail because of external limits on my time, but I'd be happy to answer theoretical questions and specific technical questions, so long as you're willing to do the legwork of reading manpages and such I hope this works out for you!
Oh, one thing just occurred to me: skip the part in the installer about installing grub. It's not going to work on this device and may cause problems. You'll take care of the bootloader part yourself with the fastboot flash:raw command.
Oh, I see there's already some decent progress in this thread. Also it looks like I totally missed the -c option in fastboot that lets you pass kernel command-line arguments... that'll definitely be a time-saver. Given what I see over in that thread, it looks like we may actually get a reasonable native linux on our TF701t. Not sure how far the OP has gotten on things like mouse/keyboard input, though.
I have to say, I'm pretty excited! It'd be super cool to be able to dual-boot native linux and android on this tablet. Best of both worlds.
lexelby said:
How much work do you want to put into this? There are two options, the easy route that you probably will consider imperfect, and the much more complicated route that I'm not certain will work. I'll do my best to explain both.
The method I use is to install a linux distro (in my case, ubuntu) inside a chroot. There are several apps on the android market to help you set this up. The one I used sets up an Xvnc server, so you can view your linux desktop by using an android VNC viewer -- but it's just connecting locally, not going over the network.
This works nicely out of the box, but it's slow, partly because it's using the VNC protocol and partly because there's no 2d hardware acceleration. I tinkered with my setup and installed XSDL, a native android X server with hardware acceleration. I had to modify the linux startup script to skip starting Xvnc and instead connect to XSDL (which is on :0.0 like a normal X server).
This works great and is fairly fast. For me, this is a good compromise between a full-fledged linux laptop and the convenience of android apps written specifically for a multitouch screen. I generally do most of my stuff in Android, but I can drop into my Ubuntu desktop whenever I need more power.
The really big downside is that it's hard to prevent Android's low-memory killer from sacrificing XSDL when I haven't used it for awhile. I've mucked about with various solutions involving oom_score_adj and such, and that helps, but android still ends up killing my X server sometimes.
So, that's the easy method. For the more complicated method, I'm just theorizing, and this stuff may not work. You're going to need to either already have somewhat deep linux knowledge or be willing to learn Here goes.
In this post, I described how I managed to boot my tf701t after the internal memory card died a horrible death. The important bit here is that I learned how to boot any initrd/kernel combination using fastboot, and how to roll that combination into a boot.img so that the tablet always boots it. This is what you'll need to do both for the installation and for future boots into your Linux install.
First off, choose your Linux distro. I don't think you'll be able to use Mint, since, as someone pointed out above, there's no ARM build of Mint. However, there is an ARM build of Debian and Mint has the "debian edition", so maybe there is an ARM version. It may be, though, that the Mint folks only built their special stuff (Cinnamon/mate/whatever) for x86 platforms. I'd recommend Ubuntu as a compromise since I know it runs on the tf701t.
For the initial installation, put the contents of the install ISO onto an SD card -- just copying your bootable USB drive over should work. Now for the tricky bit: you'll need to pull the kernel and initrd ("ramdisk", "initial ramdisk" -- usually initrd-<something>.gz) off of the usb drive and into a working directory on a Linux laptop or desktop (let's call it the "host"). You might get away with just fastbooting this kernel/ramdisk directly. Install the fastboot package for your distro (Ubuntu has one, anyway). Connect up your tablet, put it in fastboot mode (I think that's done by booting with volume up and down held) and do 'fastboot boot <your kernel> <your ramdisk>'.
This will boot the kernel and load up the initrd, which is a tiny little linux filesystem stored in memory. The kernel runs a program called init inside the ramdisk and init takes over and boots into the actual installer. The question in my mind is how it goes about finding the ISO contents. If it searches by filesystem UUID, and there's a good chance that it does, then it will find your the ISO contents on the SD card just fine and the installer will start up.
If not, well, things will get a lot more complicated. Normally what one would do in a case like this would be to pass kernel command-line arguments (you do this in the SYSLINUX bootloader for distros like Ubuntu) telling it where to find the installation media. We can't do that because fastboot doesn't let you pass command-line arguments. Instead, you'd need to extract the initrd on the Host machine, modify the init script in some way to tell it where to find the installation media (probably /dev/block/mmcblk1p1), and then repackage it. I went into somewhat shallow detail on how to do the extract/repackage parts of this, but this is where either prior linux knowledge or a willingness to do some research comes in. Hints: gunzip the initrd, then use the cpio tool to extract it.
Okay, so let's say that you get the installer booting. The next big question is whether it's going to work at all. In theory the graphics chip inside the tf701t is supported by linux, but in practice, maybe it's only supported by a kernel module that Samsung built. Maybe you'd need to substitute the stock kernel. The next question is whether X has a module that will work with the graphics chip. But maybe even if it doesn't you can use a text-mode installer. That would at least let you get a system installed that you could then hack on to try to get X running.
So, let's say you do get linux installed (probably onto the internal SD card, /dev/block/mmcblk0). Now you want to boot it. You'll need to look into the installed system and steal its kernel and ramdisk, and get them onto the Host machine. Or maybe you could just extract them from the debian packages, since I'm not sure how you'd get things off of that internal SD at this stage. As a hint, these may well NOT be the same kernel/initrd as in the installer.
Once you've got the kernel/ramdisk, you can try to boot into them with fastboot. If that works (big if), then you'll want to be able to boot them without fastboot. That's where the 'fastboot flash:raw' command comes in. It takes a kernel/ramdisk, builds an android boot.img out of them, and flashes it to the device. From then on, the device will boot that kernel and ramdisk by default.
So, in theory this could work. The biggest potential stumbling block is whether X is going to natively support the graphics chip. If it doesn't, you may be stuck using the basic framebuffer driver, or maybe that won't even work at all. ...or you could just settle for the chroot method and be done with it
Good luck. I'm very interested to hear whether this works. I'm probably not going to try it myself since I like Android enough that I want to keep it around. I also can't walk you through this in finer detail because of external limits on my time, but I'd be happy to answer theoretical questions and specific technical questions, so long as you're willing to do the legwork of reading manpages and such I hope this works out for you!
Oh, one thing just occurred to me: skip the part in the installer about installing grub. It's not going to work on this device and may cause problems. You'll take care of the bootloader part yourself with the fastboot flash:raw command.
Click to expand...
Click to collapse
Very stubborn
Sorry I didn't respond sooner as I was away with family for Christmas.
Thank you for the guide, it was extremely helpful. I am still working on getting the device ready so I'll update as I progress.
Thanks again