Re: "System is too big. Try using bzImage or modules."

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: kernel@draper.net: "Porting vfork()"
• Previous message: I Lee Hetherington: "[patch] NFS NetworkAppliance .snapshot"
• In reply to: Nat Lanza: "Re: us.kernel.org mirroring inconsistency"
• Next in thread: Michael H. Warfield: "Re: "System is too big. Try using bzImage or modules.""

> I got this message trying "make zImage." Uncompressed vmlinux is
> 1500675 bytes. Make bzImage works fine, and the system boots
> fine. Below I attached the .config. If someone could gimme a
> clue, I'd be grateful.

CLUE 1: RTFM.
CLUE 2: the subject says it all -- you should try bzImage or
compile stuff as modules ( [M] option )

cheers,

Rik -- If a Microsoft product fails, who do you sue?
+-------------------------------------------------------------------+
| Linux memory management tour guide. riel@humbolt.geo.uu.nl |
| Scouting Vries cubscout leader. http://humbolt.geo.uu.nl/~riel |
+-------------------------------------------------------------------+

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: kernel@draper.net: "Porting vfork()"
• Previous message: I Lee Hetherington: "[patch] NFS NetworkAppliance .snapshot"
• In reply to: Nat Lanza: "Re: us.kernel.org mirroring inconsistency"
• Next in thread: Michael H. Warfield: "Re: "System is too big. Try using bzImage or modules.""