visopsys.org

I'm not really a kernel dev - I've always coded userland progs. But - in spite of my shortcomings there, I decided to be the dangerous guy and put some code into kernelNetwork.c to poke debug-print info into the kernel log, especially in the area of networkInitialization. I built the ISO by using th...

Maybe the TCP part could be ported from one of the BSDs. I suppose I could load the source and play with it. Could you give me some idea about the cross building system you're using for development ... things such as versions and whatnot - or pointers/hints to building the system? I see Visopsys is ...

Hello Andy, Visopsys devs, etc: Recently I installed Visopsys as a VirtualBox instance. It works fine, but there is an issue with the network. Looking at the boot sequence and hardware detection entries in the kernel log, I see: Added network adapter net0 (08:00:27:32:e5:28) link=UP "AMD PCnet/...

Hmmm. In terms of interrupt handling I might have the exceptional system. Anyway, in the morning I'll give the new ISO a go. I have a feeling it'll work. Thanks Andy! BTW: I'm really impressed by this OS project. Out of hundreds of projects that have been started to build the "next big OS"...

Yes, I think we're gonna fix this one. Judging from that code comment I mentioned, it's likely that I have a test system at home that fires these same 'no slave' interrupts. I'd like to see if I can find it and try out my changes before I upload a new version for you, probably in a few hours - is t...

Andy:

By the way - I have both USB (Microsoft) and PS/2 mouse plugged in.

Edit: But - now looking at the FreeBSD dmesg, I see it doesn't see the PS/2 mouse either. So, maybe a bad mouse. I usually use the MS USB mouse.

- Ron

Here is the NOAPIC run: Detecting hardware: IDE disk controller warning::kernelIdeDriver.c:waitOperationComplete(395): Disk 02 no interrupt received - timeout warning::kernelIdeDriver.c:identify(1201): unknown error Detecting hardware: PS/2 mouse warning::kernelPS2MouseDriver.c:command(352): Not res...

Exactly what caught my eye!

My setup is:
Maybe we're making some progress!

Ok Andy - the first run was with the IDEDebug image. The last page of debug output follows: DEBUG IDE controller 0 using standard interrupt=14 DEBUG IDE controller 0 using standard interrupt=15 DEBUG IDE controller 0 using legacy I/O ports 01f0-01f7 & 03f6 DEBUG IDE controller 0 using legacy I/O...

Hi again Andy: Tnx for looking at the dmesg. Visopsys .74 ran fine on my other machine, but crashed on this one. Unfortunately, this is the machine I could dedicate to Visopsys ;) I don't remember anything about the crash info, but could give it another go. About the test images, sure I can boot the...