(Since this is a PC/104 based problem...maybe someone here has encountered this before...) I'm stumped.....I have to debug a kernel that is crashing at boot on a machine with no video hardware (a PC/104 embedded P133 AMPRO CM/P5i) and I cannot put a video card in...(money/time is short) I applied the 2.0.36 kernel (version I am using) patch for a serial console, but this seems to only display the kernel messages after boot is complete. I can't debug this on another machine because the crash is caused by some specific hardware (boots fine on a machine that does not have the hardware, a DiskOnChip2000, because that driver doesn't initialize) only present on the PC/104 box. Any ideas as to what I can do to see the kernel messages at boot to find out how the DoC2000 driver is crapping out? -- Eric LaForest Nascent Linux Borg -www.ncf.carleton.ca/~di458- #define Hacker !(Cracker) //FYI: http://sagan.earthspace.net/~esr/ Breaking into computers does not make one a hacker, for the same reasons that hotwiring cars does not make one a mechanic... paraphr. from ESR -- Subcription/unsubscription/info requests: send e-mail with subject of "subscribe", "unsubscribe", or "info" toWear-Hard Mailing List Archive (searchable): http://wearables.blu.org
From Wear-Hard Mailing list Archive (WH)
Maintained by R. Paul McCarty
Archive created with babymail