Index
> OS Construction > xOS v0.07 -- testing needed! |
| Author |
|
|
omarrx024 28 Jan 2017, 19:03
Hey guys!
After more than 5 months since my last release, I finally make another alpha release of xOS. A lot can happen in 5 months, and a lot has happened. New things:
I've also moved to the MIT license instead of the GPL. Here's the GitHub release. Your feedback is greatly appreciated! _________________ Byte me; OS site, source code. "Hang out with people who know more than you." -dchapiesky |
|||
28 Jan 2017, 19:03 |
|
|
EvolutionEXE 28 Jan 2017, 20:15
Very very good OS. This is for micro ships or for free use any where?
 |
|||
|
28 Jan 2017, 20:15 |
|
|
omarrx024 28 Jan 2017, 21:27
EvolutionEXE wrote: Very very good OS. This is for micro ships or for free use any where? Thanks! xOS runs on the PC only. If you mean free for use anywhere, xOS is licensed under the MIT license, which means you can do most anything you want with it, as long as I receive original credit. _________________ Byte me; OS site, source code. "Hang out with people who know more than you." -dchapiesky |
|||
|
28 Jan 2017, 21:27 |
|
|
omarrx024 28 Jan 2017, 23:26
zhak wrote: Very cute! Thanks for the feedback!  _________________ Byte me; OS site, source code. "Hang out with people who know more than you." -dchapiesky |
|||
|
28 Jan 2017, 23:26 |
|
|
system error 29 Jan 2017, 14:06
For a one man project, this is very impressive!
I'm not into OS development, but it is soothing to see new OSes popping up here and there. One of these days, one will become a giant killer. |
|||
|
29 Jan 2017, 14:06 |
|
|
neville 03 Feb 2017, 01:28
I'm not much of a fan of emulators (I prefer the real thing!) so I wrote the xOS0.07a image to a flashdrive and tried booting it on 4 different machines.
It didn't successfully boot on any of them, and they all failed for a different reported reason. I'm pretty sure the image has been written ok. Thinking back 12 years to my early days of FAMOS I'm not too surprised. Allowing for different BIOS's was a real (pun!) headache. Maybe more universal UEFI booting would be "easier" these days? But I somehow doubt it. Quick summary: 1. Sony Vaio VGN-NW15G with 3Gb RAM "KERNEL PANIC: Out of Physical Memory" with a register dump on a VESA screen. 2. Asus EeePC Intel Atom with 1Gb RAM xOS splash screen on a grey background, no mouse pointer, copyright message on bottom line, frozen. 3. Homebuilt desktop with 2Gb RAM (and ACPI!) xOS splash screen which then changed to a red screen with the message: An error has occured and xOS has failed to start. Error information: Failed to find the ACPI system bus. 4. Toshiba Satellite L300 with 1Gb RAM As for 3. above, but Error information: Unable to determine the boot device. Now that's a strange one
In all cases the boot process began with about 5.5 lines of "." printed on the real-mode text screen along with some copyright text etc. Happy to help with further test results if you wish. _________________ FAMOS - the first memory operating system |
|||
|
03 Feb 2017, 01:28 |
|
|
omarrx024 03 Feb 2017, 22:49
neville: xOS doesn't have good support for real hardware yet. Maybe I should make this a little more obvious in the README files... Specifically, first xOS has no support for any USB devices, and thus it cannot boot from your flash disk. Second, it's very likely you are using USB keyboard and mouse, while, as I just mentioned, xOS doesn't support any USB devices. I'm saving this for a later time.
xOS runs best in VirtualBox, and it's acceptable in QEMU, and they are the only places I would recommend testing xOS in this stage. The ACPI system bus issue has been fixed after the 0.07 alpha was released. _________________ Byte me; OS site, source code. "Hang out with people who know more than you." -dchapiesky |
|||
|
03 Feb 2017, 22:49 |
|
|
neville 04 Feb 2017, 07:00
Your OS should be able to boot from a flashdrive without native USB support until you switch to PM. The USB support is provided by the BIOS until you leave real mode (with "legacy USB support" enabled in Setup if necessary).
And it does, as is clearly demonstrated by the fact that all 4 of my machines were running your code. So the crashes can't be related to lack of USB support unless the crashes occurred in PM? I'll have a look at your sources and see what I can find. _________________ FAMOS - the first memory operating system |
|||
|
04 Feb 2017, 07:00 |
|
|
Roman 04 Feb 2017, 14:08
Did you have screenshots xOS v0.07 ?
And good luck witch xOS ! |
|||
|
04 Feb 2017, 14:08 |
|
|
omarrx024 04 Feb 2017, 20:13
neville wrote: Your OS should be able to boot from a flashdrive without native USB support until you switch to PM. The USB support is provided by the BIOS until you leave real mode (with "legacy USB support" enabled in Setup if necessary). You seem to be missing that my OS doesn't depend on the BIOS; xOS is entirely 32-bit system and only depends on the BIOS for early initialization, like detecting memory/setting VBE mode/etc... Roman wrote: Did you have screenshots xOS v0.07 ? There are some stuff here. Thanks! _________________ Byte me; OS site, source code. "Hang out with people who know more than you." -dchapiesky |
|||
|
04 Feb 2017, 20:13 |
|
|
neville 04 Feb 2017, 21:14
omarrx024 wrote: You seem to be missing that my OS doesn't depend on the BIOS; omarrx024 wrote: xOS ...depends on the BIOS for early initialization 
So I guess you are absolutely sure there are no problems with any of your real mode code? Enabling A20 etc. Looking at your sources I see you've started to write a USB Host Controller/Driver. I will await with interest until you implement it! _________________ FAMOS - the first memory operating system |
|||
|
04 Feb 2017, 21:14 |
|
|
omarrx024 04 Feb 2017, 22:22
neville wrote: So I guess you are absolutely sure there are no problems with any of your real mode code? Enabling A20 etc. Obviously, nothing is wrong with my early real mode code. If it failed to set a VBE mode, you wouldn't have a graphical screen at all. If it failed to detect memory, the error will be handled in real mode as well. If it failed to enable A20, you wouldn't see anything in the screen (because the framebuffer is higher than 1 MB.) My disk reading code doesn't depend on the real mode code at all. My USB drivers are undergoing really slow development, because I'm still learning about USB as I develop, and for now, I'm only doing UHCI as my test PC supports UHCI. I will do OHCI, EHCI and xHCI later, though, as most of them share the same concepts, just different methods of achieving the same goals. Even when I finish UHCI, it will still take a lot of time for it to be functional; I still need a driver for the USB hub, and every USB device I wish to support (for now, I plan to support the mass storage device and HID devices.) _________________ Byte me; OS site, source code. "Hang out with people who know more than you." -dchapiesky |
|||
|
04 Feb 2017, 22:22 |
|
|
rugxulo 05 Feb 2017, 00:16
omarrx024 wrote:
Just for the record, one FreeDOS contributor, Bret Johnson, wrote his own (third-party, sources available, installable, non-kernel) USB drivers, which are still "UHCI only". He says it's too complex to fully do the rest (yet), and unfortunately some machines (like this one I'm using now) don't support UHCI at all. My point would be that you should probably take a look at his sources or contact him or both (if you haven't already). Hey, misery loves company.  |
|||
|
05 Feb 2017, 00:16 |
|
|
omarrx024 05 Feb 2017, 04:30
rugxulo wrote: Just for the record, one FreeDOS contributor, Bret Johnson, wrote his own (third-party, sources available, installable, non-kernel) USB drivers, which are still "UHCI only". He says it's too complex to fully do the rest (yet), and unfortunately some machines (like this one I'm using now) don't support UHCI at all. Nah, it's not that bad; it's just slow because I'm still learning. Maybe I'll contact him after I finish UHCI and OHCI in a few months.  _________________ Byte me; OS site, source code. "Hang out with people who know more than you." -dchapiesky |
|||
|
05 Feb 2017, 04:30 |
|
|
neville 06 Feb 2017, 04:19
Just out of curiosity I wrote the image to my Sony Vaio's hard disk (which is available for such purposes
) The result was the same as obtained when booting from the pendrive - "KERNEL PANIC: Out of Physical Memory" with a register dump. Also no splash screen beforehand.
I re-checked booting the Sony Vaio from the flashdrive and confirmed there was no splash screen with that either. My other 3 machines did produce splash screens before crashing but none of those machines have a hard disk available for trashing So I think the problem is not caused by lack of USB support on the Sony Vaio at least. The register dump shows PMode has probably been entered. Unfortunately EIP seems to be omitted:
Code: [00000000] KERNEL PANIC: Out of physical memory. [00000000] --- beginning register dump at time of fault --- [00000000] eax: 00001000 ebx: C0000000 ecx: 00000009 edx: 00000001 [00000000] esi: 00006767 edi: 20000004 esp: 0000185C ebp: 00000000 [00000000] cs: 0008 ss: 0010 ds: 0010 es: 0010 eflags: 00000006 [00000000] cr0: 80000013 cr2: 00000000 cr3: 0009C000 cr4: 00000700 [00000000] --- end of register dump --- _________________ FAMOS - the first memory operating system |
|||
|
06 Feb 2017, 04:19 |
|
< Last Thread | Next Thread > |
Forum Rules:
|