"Alfred M\. Szmidt" <[EMAIL PROTECTED]> writes:
> [Adding CC to bug-hurd, _again_, don't remove it!]
>
> 22: 9186 IO-APIC-level libata, NVidia CK804
> 23: 13705 IO-APIC-level libata, eth0
>
> These two could cause problems, I don't know what libata or nvidia is.
> But if G
You might try unsharing the IRQ's for those devices, or some such. Or
compile a really utterly bare kernel.
In wichfile do I find the main() function for gnumah?
_start() in i386/i386at/boothdr.S.
You can also use the kernel debugger to help you out. See the manual
for details about it, it
Alfred M. Szmidt wrote:
[Adding CC to bug-hurd, _again_, don't remove it!]
22: 9186 IO-APIC-level libata, NVidia CK804
23: 13705 IO-APIC-level libata, eth0
These two could cause problems, I don't know what libata or nvidia is.
A quick search on the Internet provided t
[Adding CC to bug-hurd, _again_, don't remove it!]
22: 9186 IO-APIC-level libata, NVidia CK804
23: 13705 IO-APIC-level libata, eth0
These two could cause problems, I don't know what libata or nvidia is.
But if GNU Mach has support for your NIC and any of these two, it
mig
[CCing bug-hurd]
I have done a number of attempts to boot Gnu/Hurd, but mostly the
computer interrupts and reboots in the middle of the process.
No idea if you checked this, but check if you have shared IRQ's. cat
/proc/interrupts in GNU/Linux or some such.
Partitions check: (DOS parti
