Page 1 of 1

checking 386/387 coupling failed : trying to reset

Posted: 8. May 2018, 15:49
by Me56
Hi everyone

I've Debian 9.4 and i installed VirtualBox the last version.
I tried to install Debian 2.2 or Mandrake 6 and i've the same message for the both :

Code: Select all

checking 386/387 coupling failed :  trying to reset

trying to reset
trying to reset
trying to reset
trying to reset
trying to reset
trying to reset

...

What should i do ? do you have any idea ?
I select a lot of different option ... but it changed nothing I've always this message

Thanks for your help

Re: checking 386/387 coupling failed : trying to reset

Posted: 8. May 2018, 16:08
by socratis
Me56 wrote:i installed VirtualBox the last version.
That's not a version. The complete output of "VBoxManage -version" should tell us the version... ;)

And Debian 2.2 or Mandrake 6 sound really old ones, where did you get them? Do you have a download link? If you can't post a link directly, obfuscate them and we'll fix them...

Re: checking 386/387 coupling failed : trying to reset

Posted: 8. May 2018, 17:49
by Me56
Hi and thks for your answer !
Version 5.2.10 r122088 (Qt5.7.1)

It's more for the fun, i tried Mandrake more than 10 years ago, but i really didn't like at all. And today I left definitively Windows for Linux lol :) So i would like to remember which kind of OS i didn't like at this time :)


sorry i can't put the address because this website told me : You must be a member for 1 days and have 1 posts before you can post ur..l

Re: checking 386/387 coupling failed : trying to reset

Posted: 8. May 2018, 17:50
by Me56
It's old-linux the website com
It's https://old-linux.com/

Re: checking 386/387 coupling failed : trying to reset

Posted: 8. May 2018, 18:27
by socratis
I'll try to install them. I don't promise any fast response time on this one though... ;)

PS. That's the website you meant, right? I hope I got it right...

Re: checking 386/387 coupling failed : trying to reset

Posted: 8. May 2018, 19:21
by Me56
yes it was the WS because even this word this forum doesn't want to let me ..

Re: checking 386/387 coupling failed : trying to reset

Posted: 9. May 2018, 00:57
by socratis
I downloaded and installed Mandrake 6.0-i386 (3 CDs). I chose the "Linux 2.2" template. Couldn't get X to start, but I didn't try for more than 2 min either. Didn't care enough to do ;)

The point is that I didn't get the error you got. Check that you selected the correct template, re-create the VM.

Re: checking 386/387 coupling failed : trying to reset

Posted: 9. May 2018, 10:00
by Me56
I did all that ... This morning i tried on another computer and it's the same result ...
So it does mean it's not the ISO if you confirmed you could do it

Re: checking 386/387 coupling failed : trying to reset

Posted: 9. May 2018, 10:49
by socratis
Here's what I did, and I'm repeating again, because I kept the ISOs, I had a feeling that I'd need them... ;)
  • From https://old-linux.com/ downloaded Mandrake 6.0 CD1, CD2, CD3, Linux 2.2.9 (Release 27 may 1999).
  • SHA256 of the downloaded CDs:
    • [*]CD 1: d910764eb0d4428d45ee7fbb100cab5004dd7caeb3ee5431a907bbb4781721bc
      [*]CD 2: 7223e68cbd3a7686bc22e689580837fbf13008b3e6367c55659ba11bb683e517
      [*]CD 3: 622be85c79726fb7c4c4019f3121145d5f4b5681a8470c3b0fac9959c3e54c46
  • New VM, Type: Linux, Version: Linux 2.2, RAM: 64 MB, New HD: 2 GB, the rest as is. Pretty much everything set to default.
  • Start the VM, proceed without any issues, all defaults, Workstation installation, all of the disk, proceed with the install, cancel out of the network setup, set up users, select "Generic VGA"/"Generic Monitor"/"2mb"/"No clocking setting", cancel out of the X setup because it failed, done.
  • Rebooted, removed CD1, reset the VM, all set!
At which point did yours fail? When if fails, close the VM (do not pause or save-state, close it completely). Right-click on the VM, "Show Log". Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.


PS. I never needed CD2 or CD3, so you can skip them if you need the setup described above.

Re: checking 386/387 coupling failed : trying to reset

Posted: 9. May 2018, 10:50
by mpack
Me56 wrote:So it does mean it's not the ISO if you confirmed you could do it
Socratis proved that the ISO is not corrupted at source, not that your copy is good. An MD5 or SHA comparison should test that.

Re: checking 386/387 coupling failed : trying to reset

Posted: 9. May 2018, 11:46
by Me56
Thanks you for your help :)
I attached a screenshot, i try the log as well but it doesn't accept the extension ... en impossible to insert in this post i've the same message of yesterday..

Re: checking 386/387 coupling failed : trying to reset

Posted: 9. May 2018, 11:48
by Me56
Sorry i changed it.
So i just boot on the ISO, I've the first screen where they asked to press ENTER so start the installation, i press it and as you can see on the screenshot, it block on this line (checking 386/387 coupling failed : trying to reset) and keep putting this same line again again and again.... and most of the time it close the virtual box like it "switch off" the virtual computer without asking anything to me.

I hope i was enough clear :?

Sorry again

Re: checking 386/387 coupling failed : trying to reset

Posted: 9. May 2018, 13:44
by socratis
[color=#00AA00]socratis[/color] wrote:At which point did yours fail?
I did ask for the specific step that it failed, more like a "I did this, I did that, it failed at that point", not for a screenshot, because I have not the faintest idea at which point your installation failed, where does this screenshot is supposed to show me.
[color=#00AA00]socratis[/color] wrote:... "VBox.log", ZIP it and ...
I asked for a compressed log. Which part of the bold, red underlined part was so easy to miss?

Please edit your message, delete your .txt file, and replace it with its ZIPPED version.

Re: checking 386/387 coupling failed : trying to reset

Posted: 9. May 2018, 18:01
by mpack
386/387? Just how ancient is this thing? It would have to be early 1990s? Wasn't the 486 around by the Win3 era? (the 486 was the first family member to have the FPU built in).

Anyhoo, I suspect that the major difference between you and Socratis is this:
VBox.log wrote: 00:00:00.834805 HM: HMR3Init: Falling back to raw-mode: VT-x is not available
According to Intel, your Core 2 Duo T6500 doesn't support VT-x, so I'm afraid this ancient OS may just be a little too ancient if you don't have VT-x.