Hi!
I don't know if you remember some query about compiling a new
kernel for Athlon based systems. Basically, my kernel just woudln't
work. In the end, I found out that this wasn't due to a wrong processor
or anything like that: it was due to the motherboard (WS-6167), and in
particular of its IDE controller (Viper 756, IIRC). Right, AFAIK, 2.2.14
does not have Viper 756 controller, so no wonder my kernels weren't
working! I downloaded 2.3.42 (the latest unstable), and had a go at it.
Now, it sort of boots up, and it detects the actual chipset. This is the
old output with 2.2.13 (as installed in the bootdisks)
PCI_IDE: unknown IDE controller on PCI bus 00 device 39, VID=1022,
DID=7409
PCI_IDE: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio
and this is the log for the 2.3 kernel
AMD7409: IDE controller on PCI bus 00 dev 39
AMD7409: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio
However, the new kernel seems to splutter about. In particular,
I had loads of segfaults, so I rebooted into my old kernel, which
wouldn't boot up properly, as libm.so.6 didn't have a proper ELF header.
I solved this by installing libc6 again, as libm is quite widely used.
My question is: I don't want to live on the bleeding edge kernel
stuff, but I'd like to compile a kernel with the Viper chip support (and
whatever else that needs). Is there any way to patch my 2.2.14 sources
so that this is possible?
Thanks,
José
--
José L Gómez Dans PhD student
Radar & Communications Group
Department of Electronic Engineering
University of Sheffield UK
