Problems installing Kolibri (KERNEL MNT? ERROR)

Post here questions, problems and suggestions in English language
  • It is 1.40 am now in Russia and everyone already sleep - wait 8-10 hours till developers wake up.
    KERNEL MNT ? means - file not found AFAIK
  • WAIT, my PC has a x64 structure. It worked fine in x32-x86 . Is there a way to get it to work in x86?
  • Any modern processor x86-64 also supports the x86-32 (old protected mode of processor).

    Your description is not very accurate.
    Сan you describe the items in more detail what you were doing?
    Всем чмоки в этом проекте! Засуньте эти 11 лет себе в жопу!
  • You didn't read install instructions from distributive archive. You doing it wrong, read manual first (called hd load )
  • You don't need Win32 disk imager то load the .IMG file. Just copy kolibri.img to your usb drive and run inst.exe from here: http://builds.kolibrios.org/eng/svn4199 ... /USB_Boot/ for usb flash (see readme.txt). If inst.exe can't detect your drive (I'm not sure is it works for USB HDD too), maybe you should use special version of inst.exe from here: download/file.php?id=5455
  • art_zh wrote:Cessnapilot
    Triple offensive mistake in a simple word "Kolibri" look like a heavy insult of all us developers.
    People aren't perfect and make mistakes. You are insulting others and wasting space on this forum. What kind of a developer are you? With an attitude like that, I would fire you for no professionalism, disrespect, incorrect answers, and disability to contribute relevant information.

    I wish you the best and have a great day,
    Cessnapilot
  • Cessnapilot wrote:People aren't perfect and make mistakes. You are insulting others and wasting space on this forum.
    I am terribly sorry for art_zh's behavior. I have deleted his offending post now. No one should be treated like that just for making a mistake in our OS name. I was in army reserve service during that time, so I missed this post, and found it out only now. I apologize again for taking measures so late.

    Regarding your original question, below are instructions for USB flash disks. It should work the same for USB hard disk:

    1. Insert your USB stick into Windows PC and format it with FAT32.
    2. Download latest "Universal image Flash/HDD" from here: http://builds.kolibrios.org/eng/latest-distr.7z
    3. Unzip the downloaded file with 7zip.
    4. Go to folder ..latest-distr\HD_Load\USB_Boot and read file "readme.txt".
    5. Run file "inst.exe", select your USB stick and press OK.
    6. Copy file ..latest-distr\kolibri.img to the parent directory of USB stick.
    7. Try booting from this USB stick (remember to enable USB boot in BIOS, and give it highest priority).
    8. Only if it doesn't boot successfully, go to folder ..latest-distr\HD_Load\USB_Boot and run file "setmbr.exe"

    If you use Linux, then perform Linux-related instructions at the bottom of "readme.txt".
  • Soo.. i meet blue screen :lol: .. changed some options with all and always after exist of blue I geting black.. :(
    Tied instal by rufus, by kins, inst, and always this same situation.
    Attachments
    PROBLEM_1.JPG
    PROBLEM_1.JPG (641.29 KiB)
    Viewed 10597 times
  • Maybe should exist some loging to log.txt on usb/floopy to easy provide some info.
  • Debug on blue screen: press C, press key 1, enter, n and photo of the second column of the log.
    There is a problem with the graphics, something went wrong. Here is an example of a good log.
    Attachments
    goodLog.PNG
    goodLog.PNG (9.84 KiB)
    Viewed 10586 times
  • The 2nd part which I made after many experiments.
    Resolution - related problem?
    PROBLEM_2X.JPG
    PROBLEM_2X.JPG (705.52 KiB)
    Viewed 10552 times
  • Channel 1 Disk 1 C: NTFS
    Channel 2 Disk 0 D: NTFS+Bitlocker
    Channel 2 Disk 1 E: NTFS+Bitlocker

    There are not visible by NTFS I guess?

    What I can meet from rest of logs around drivers/adress?

    About log as
    K: something i sugesting listing as 1,2,3 eg. can be more easy talks about logs (and save the to small file kOS_sys_log.txt and others eg kOS_critical_log.txt - some dump after crash, or something)
    K0001:
    K0002:
  • You can turn on the disks visible in BIOS (mode V86) on the blue screen by pressing B and key 1. This problem is not in disks.

    I think the problem is in one of the three drivers: vidintel, UHCI, EHCI. Please note that XHCI is not supported (link, only ru language).
    It takes time to think ... For the sake of interest, while trying to run the old version KolibriOS 0.7.7.0. Report if the old version works.
  • Hello,

    You need to turn on "C" point at blue screen to get detailed log.
    Please, do it and send us a screenshot.

    Regards,
    Kiril
    Из хаоса в космос
  • Who is online

    Users browsing this forum: No registered users and 6 guests