[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: GRUB lockup during boot



Robert,

Thank you for the information.  I've been attempting to cross-compile
the mach kernel with my Debian system but have been getting the below error
during the "make", so I've been busy trying to determine what is causing it to
occur, and haven't seen yet if the custom kernel will solve the boot problem,
although I suspect it will.
 
../../../i386/linux/../../linux/dev/lib/vsprintf.c: In function 
`linux_vsprintf':
../../linux/dev/include/asm/string.h:551: Invalid `asm' statement:
../../linux/dev/include/asm/string.h:551: fixed or forbidden register 1 (dx) 
was spilled for class DREG.
make[2]: *** [vsprintf.o] Error 1
make[2]: Leaving directory `/usr/src/gnumach-1.2/build/i386/linux'
make[1]: *** [linux/linux.o] Error 2
make[1]: Leaving directory `/usr/src/gnumach-1.2/build/i386'
make: *** [i386/sysdep.o] Error 2

Your second thought was the correct one, I have an ASUS board which does have
the VIA chipset onboard.  To be more specific its an ASUS K7M/500/WA the WA 
just stands for "with audio".  Its a Slot A type board.  

I will keep you informed of my progress with this... unfortunately I've been 
quite busy lately and haven't had much time to just hack.  I'm pretty sure I
will get it straightened out eventually.

Thank you for again for the assistance,

Roger Williams

> That's usually a problem with a specific mach driver. The general
> solution is to (cross-)compile gnumach with only the drivers you need
> (the distributed binary includes almost all available drivers).
> 
> Do you happen to use a FIC SD11 mobo? In this case the eatadma driver
> is very probably the culprit. See
> <URL:http://lists.debian.org/debian-hurd-0010/msg00167.html>.
> 
> On second thought, the conflict I encountered may be with the VIA
> chipset that is used by many Athlon boards. So disabling eatadma may
> be a good idea even if you use another board.
> 
> Please report what motherboard you have and whether disabling eatadma
> fixes it. Because if this affects most Athlon boxes, it would be good
> to turn the eatadma driver off per default.
> 
> -- 
> Robbe



Reply to: