Page 1 of 2
Installing Debian 32-bit on Windows 7 t4300 with Virtual Box
Posted: 10. Feb 2016, 18:31
by rootseire
Hi,
I have been looking through this for over a week now. I am trying to install Virtual Box on an older HP laptop (t4300 processor), with no hyper-threading or virtualization. I have checked on the BIOS with normal start up but the option for enabling virtualization is not there. I have also flashed the BIOS form F.31 to F.46 using "Insyde Flash". This has worked successfully. But F.46 still does not support virtualization even when I see it show up in the BIOS.
However, I have actually been able to install debian 32-bit on virtual box, and get all the way to the boot screen. Problem is, once I start it, the screen shows black and blank, with a cursor showing that doesn't blink.
I was hoping to find out is it still not possible to install debian 32-bit on this machine even though I have got this far? Reading through a bunch of debian and other tech sites, it seems that what it is trying to do is load video but is not able. I also noticed that because of virtualization not present, it cannot show the options for "Acceleration" under the "System" tab of Virtual Box settings.
Have attached a screenshot of spec for laptop, settings for virtual box and the result when started...
Thank you,
Pat
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 10. Feb 2016, 19:09
by mpack
As you say, and as
Intel says, the T4300 does not have VT-x, so there is no point in looking for a way to enable it.
As to your Debian 32bit VM, post a VM log file for it: With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 10. Feb 2016, 19:14
by rootseire
Many thanks for this advice, no hope for the VT-x anyway.
Log file is attached.
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 10. Feb 2016, 19:16
by socratis
Some guests require VT-x, even if they're 32-bit. Windows 8 and greater come to mind. I'm not sure if Debian 8 is. Not, according to a (
REALLY outdated)
page from the wiki.
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 10. Feb 2016, 20:06
by mpack
The VM recipe looks adequate for a 32bit VM. I would perhaps try turning off 3D acceleration unless I was certain that the host OpenGL support was beyond reproach.
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 10. Feb 2016, 20:27
by socratis
Since we're at it, can you disable I/O APIC, which is not part of the defaults in any event?
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 10. Feb 2016, 20:37
by rootseire
Unchecked 3D acceleration and disabled I/O APIC, no change to the black screen yet. I've attached OpenGL viewer screenshot.
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 10. Feb 2016, 21:01
by socratis
OK, I tried with the same ISO, and it worked flawlessly. Do you mind posting the .vbox file for the affected machine?
- Right-click on the VM in the VirtualBox Manager.
- Select "Show in Explorer".
- ZIP it and attach it in your response.
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 10. Feb 2016, 21:36
by rootseire
Thought that it might not be the ISO alright. VBox attached.
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 10. Feb 2016, 22:13
by socratis
OK, let's take things one at at time. If I lose my temper, don't worry, it's because I'm Mediterranean
- I asked for the ".vbox" file, you attached the ".vbox-prev". I really hope that you haven't made any significant changes that will change what I'm commenting on.
- I didn't see the I/O APIC or the 3D enabled, which was something that was clearly enabled when I was looking at the logs. Maybe you disabled them based on previous comments.That's OK, none of them are enabled by default in any event.
- You changed the VRAM to 29(?) MB. Any particular reason for such an odd number? (no pun intended)
- You changed the boot order: HD, Floppy, DVD. You do remember that you have to boot from the DVD, right? Why did you change it? Thankfully VirtualBox works around ... that.
- You disabled the host I/O cache for your IDE controller. Any particular reason? In fact I would enable it for the SATA as well.
- You changed the CD to a "Live CD/DVD". Any particular reason?
- You changed your only network card to Host-Only. On a Net-Install!!! That means that you can ONLY access your host. Host-Only.
OK, now that I got it out of my system, I still got Debian to boot. Graphical and text-only. Of course it wouldn't install because there was no network access, but still, I didn't get stuck at the cursor.
I don't know what might be wrong with the setup. It doesn't seem like it would be.
Do you mind creating a new VM, stick with the defaults (
PLEASE) and see if it works?
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 10. Feb 2016, 22:32
by rootseire
Thanks for this, my original install was all default options and I ended up at the cursor, just recently I changed the other settings out of last ditch attempts to see if something might work. To go back on those pointers:
1) Vbox file wasn't available in the Explorer window, only vbox-prev (poss cause of aforementioned changes)
2) I/O APIC and 3D were disabled - because of previous comments in the thread here asking me to do so.
3) My mistake on the VRAM - I changed this after the original config and suggested updates didn't work. Same with
4) Boot order, host I/O cache, Live CD/DVD and network card - were all changed just recently when it wouldn't.
I'll wipe and go with another default install.
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 11. Feb 2016, 01:27
by rootseire
Ok after a default install this time I am brought back to the Debian installer boot menu - not yet loading Grub2 package but it is allowing me to move around. Is there something I can set here that will take me further?
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 11. Feb 2016, 02:14
by socratis
rootseire wrote:Ok after a default install this time I am brought back to the Debian installer boot menu
OK then, I hope that a lesson has been learned; do not mess with things that you do not quite understand, until you understand what ramifications your actions might have.
rootseire wrote:Is there something I can set here that will take me further?
I'm not sure I quite understand your question. Where do you want to go? Press the "Show" green arrow and the VM window will be the front one. Then just follow the instructions on the VM window.
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 11. Feb 2016, 05:39
by rootseire
So I was getting the installation screen and I tried to use rescue mode to get the Grub loader to show up again. Turns out I had to set controller to "Host Drive E" and Debian loaded up. I got to the login screen and then added two new users from command line. But just when I login, I get the following errors on both user accounts:
patrick:
cannot enter home directory using ./
call to lnusertemp failed (temporary directories full?). Check your installation
/home/admin:
Xsession: warning: unable to symlink "/tmp/xsession-home/admin" to "/tmp/fileTVwYv5"; look for session
log/errors in "tmp/xsession-home/admin"
I thought at first this was an issue with permissions on tmp folder and others, but after CHMODing into those folders I haven't been able to get any further. I also tried to give full access to /home for each account, but the same errors keep coming up.
Is there something else I should be doing here?
Thanks,
P
Re: Installing Debian 32-bit on Windows 7 t4300 with Virtual
Posted: 11. Feb 2016, 10:49
by socratis
rootseire wrote:So I was getting the installation screen and I tried to use rescue mode to get the Grub loader to show up again.
???????????
What does this have anything to do with installing Debian on your laptop? What are you trying to do? I have a feeling that you're not telling us the whole story.
In my eyes, since we've managed (after a lot of back and forth, time and effort) to get your installation going, that this should be marked as "Solved".
I won't even try to address the rest of your questions, because they seem completely guest-OS related and have absolutely nothing to do with VirtualBox.