Greetings,

* Neal Lippman <[EMAIL PROTECTED]> [2003-Sep-16 19:17 AKDT]:
> Unfortunately, it's a bit hard to provide full details because, as I
> outlined above, I cannot even get a system working well enough to log in
> and review dmesg.

Does it get far enough to log messages to /var/log/kern.log?  Boot back 
into a working 2.4 kernel and see what shows up there.

> For the record:
> Hardware is: AMD Athlon XP 1700+ on MSI K7T-266Pro motherboard, 512 MB
> Mushkin PC2100 DRAM.
>       1 WD 80 GB HD, IDE, as hda
>       1 Pioneer 106S DVD reader as hdc
>       1 HP CDRW as hdd (ide-scsi under 2.4.x)

FYI, unless something has changed recently, ide-scsi is not working with 
2.6.  I don't use any SCSI stuff, or SCSI emulation and everything works 
fine.  You need a new cdrecord, and pass dev=/dev/hdd to make it work.

> With my own complied 2.6.0-test2, I am finally able to boot, but kdm
> cannot start. At the login prompt, I cannot log in as the keyboard does
> not work. I will review the .config and maybe I made the keyboard a
> module and it is not getting loaded.

To start, you might try building everything into the kernel.  Why make 
things complicated with modules if you're already building a custom 
kernel for your hardware.  If you really do want modules, make sure you 
have a recent 'module-init-tools' Debian package.  Modules are different 
in 2.6.

> Oh yes, I am running sarge. gcc version is 3.3.1 20030626 Debian
> prerelease.

I haven't really been able to figure out what the "approved" version of 
gcc for kernel compiles is, but according to the documentation that 
comes with the source, you should be using gcc-2.95.  I've got a 
2.6.0-test3 built with this, and also a 2.6.0-test5 with 3.2.  But you 
might not want to use 3.3 because it's more experimental.  I'm not sure 
how you're supposed to change the version, but what I do is edit the top 
level Makefile and replace the 'gcc' lines with 'gcc-2.95' (it's in two 
places but I can't remember exactly what they're called).

Also, you may get user-level kernel panics from some sort of Athlon 
prefetch problem.  The kernel developers are currently discussing how 
best to resolve this issue, but if you run into this (the kernel boots 
and runs, but you get kernel panics that don't hang the system later 
when running other programs) let me know and I can send you the simple 
patch Andrew Morton sent me to turn it off.

Hope that helps.

Chris
-- 
Christopher S. Swingley          email: [EMAIL PROTECTED]
IARC -- Frontier Program         Please use encryption.  GPG key at:
University of Alaska Fairbanks   www.frontier.iarc.uaf.edu/~cswingle/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to