Hello,
I have twice compiled kernel 2.6.27.8 from source. During make it detects 5 problems but they don't look significant and 'make CONFIG_DEBUG_SECTION_MISMATCH=y' resolves this problem. However after booting from this kernel and its relative initrd.img, the process stops at devfs and kernel panic. The system is unable to read /lib/modules/[kernel]/modules.dep. IMHO this is basically an indicator of the ide drivers not working.
During make menuconfig, I observed that the IDE modules can only be included as modules <M>, not 'in-built' in the kernel like <*>. In one section, the Help contents even mention that this option should not be used if your root system is on the IDE drive. This could mean that while the booting drive is not IDE ( means SATA ), the other drive detected after booting can be IDE.
My system is an Intel 845 with IDE drives. Has anyone on this list successfully booted from 2.6.27.8 using an IDE HDD on an 845 chipset mobo? Do the new kernels mean goodbye to old hardware? Could this be one reason why K/Ubuntu 8.10 does not boot live into an old 845 chipset + IDE system?
On Mon, Dec 22, 2008 at 10:20 PM, Rony wrote:
My system is an Intel 845 with IDE drives. Has anyone on this list successfully booted from 2.6.27.8 using an IDE HDD on an 845 chipset mobo? Do the new kernels mean goodbye to old hardware? Could this be one reason why K/Ubuntu 8.10 does not boot live into an old 845 chipset + IDE system?
I don't know what's the cause of your issue, but I'm currently using Ubuntu 8.10 with the generic 2.6.27-9 and my Intel 845GL system with IDE HDD is working perfectly fine. You've probably missed out some option in menuconfig.
Also with respect to the inability to boot from the K/Ubuntu live CD, that's due to a bug with intel driver and/or compiz: https://bugs.launchpad.net/ubuntu/+bug/259385 As a workaround, you can remove compiz before logging in. (Details in the bug report.)
On Mon, Dec 22, 2008 at 11:50 AM, Rony gnulinuxist@gmail.com wrote:
I have twice compiled kernel 2.6.27.8 from source. During make it
You're short on details. How did you compile the kernel from source? What did your config look like? Which distro are we talking about? Did you use the vanilla kernel or the distro specific kernel? Details buddy, details!
On Monday 22 December 2008 22:20, Rony wrote:
Hello,
I have twice compiled kernel 2.6.27.8 from source. During make it detects 5 problems but they don't look significant and 'make CONFIG_DEBUG_SECTION_MISMATCH=y' resolves this problem. However after booting from this kernel and its relative initrd.img, the process stops at devfs and kernel panic. The system is unable to read /lib/modules/[kernel]/modules.dep. IMHO this is basically an indicator of the ide drivers not working.
If IDE drivers are modules, they should be in initrd.img. Better just untar the source and overwrite. Then do make oldconfig.
During make menuconfig, I observed that the IDE modules can only be included as modules <M>, not 'in-built' in the kernel like <*>. In one section, the Help contents even mention that this option should not be used if your root system is on the IDE drive. This could mean that while the booting drive is not IDE ( means SATA ), the other drive detected after booting can be IDE.
<*> ATA/ATAPI/MFM/RLL support ---> <*> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support <*> Include IDE/ATA-2 DISK support <*> generic/default IDE chipset support <*> PNP EIDE support <*> Generic PCI IDE Chipset Support <*> Intel PIIX/ICH chipsets support
this should be * along with block devices. They can also be modules. But then you must include them in initrd.img by adding them in /etc/initramfs-tools/modules and rebuilding the initrd.img. update-initramfs should do that.
My system is an Intel 845 with IDE drives. Has anyone on this list successfully booted from 2.6.27.8 using an IDE HDD on an 845 chipset mobo? Do the new kernels mean goodbye to old hardware? Could this be one reason why K/Ubuntu 8.10 does not boot live into an old 845 chipset + IDE system?
2.6.27.6 works on via 8237. no reason why it should not work on i845
First, thanks to all those who replied.
My system is Etch and the kernel was downloaded from kernel.org using the F (Full source) link. Commands used were... make menuconfig make make modules modules_install make install mkinitrd -o /boot/image
jtd wrote:
On Monday 22 December 2008 22:20, Rony wrote:
During make menuconfig, I observed that the IDE modules can only be included as modules <M>, not 'in-built' in the kernel like <*>. In one section, the Help contents even mention that this option should not be used if your root system is on the IDE drive. This could mean that while the booting drive is not IDE ( means SATA ), the other drive detected after booting can be IDE.
<*> ATA/ATAPI/MFM/RLL support ---> <*> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support <*> Include IDE/ATA-2 DISK support <*> generic/default IDE chipset support <*> PNP EIDE support <*> Generic PCI IDE Chipset Support <*> Intel PIIX/ICH chipsets support
this should be * along with block devices. They can also be modules. But then you must include them in initrd.img by adding them in /etc/initramfs-tools/modules and rebuilding the initrd.img. update-initramfs should do that.
--- Block devices ? ? ? ? <M> Normal floppy disk support ? ? ? ? <M> XT hard disk support ? ? ? ? <M> Parallel port IDE device support ? ? ? ? *** Parallel IDE high-level drivers *** ? ? ? ? <M> Parallel port IDE disks ? ? ? ? <M> Parallel port ATAPI CD-ROMs ? ? ? ? <M> Parallel port ATAPI disks ? ? ? ? <M> Parallel port ATAPI tapes ? ? ? ? <M> Parallel port generic ATAPI devices ? ? ? ? *** Parallel IDE protocol modules *** ? ? ? ? <M> ATEN EH-100 protocol ? ? ? ? <M> MicroSolutions backpack (Series 5) protocol ? ? ? ? <M> MicroSolutions backpack (Series 6) protocol <M> DataStor Commuter protocol ? ? ? ? <M> DataStor EP-2000 protocol ? ? ? ? <M> FIT TD-2000 protocol ? ? ? ? <M> FIT TD-3000 protocol <M> DataStor Commuter protocol ? ? ? ? <M> DataStor EP-2000 protocol ? ? ? ? <M> FIT TD-2000 protocol ? ? ? ? <M> FIT TD-3000 protocol ? ? ? ? <M> Shuttle EPAT/EPEZ protocol ? ? ? ? [ ] Support c7/c8 chips (EXPERIMENTAL) ? ? ? ? <M> Shuttle EPIA protocol ? ? ? ? <M> Freecom IQ ASIC-2 protocol ? ? ? ? <M> FreeCom power protocol ? ? ? ? <M> KingByte KBIC-951A/971A protocols ? ? ? ? <M> KT PHd protocol ? ? ? ? <M> OnSpec 90c20 protocol ? ? ? ? <M> OnSpec 90c26 protocol ? ? ? ? <M> Compaq SMART2 support ? ? ? ? <M> Shuttle EPAT/EPEZ protocol ? ? ? ? [ ] Support c7/c8 chips (EXPERIMENTAL) ? ? ? ? <M> Shuttle EPIA protocol ? ? ? ? <M> Freecom IQ ASIC-2 protocol ? ? ? ? <M> FreeCom power protocol ? ? ? ? <M> KingByte KBIC-951A/971A protocols ? ? ? ? <M> KT PHd protocol ? ? ? ? <M> OnSpec 90c20 protocol ? ? ? ? <M> OnSpec 90c26 protocol ? ? ? ? <M> Compaq SMART2 support <M> Compaq Smart Array 5xxx support ? ? ? ? [*] SCSI tape drive support for Smart Array 5xxx ? ? ? ? <M> Mylex DAC960/DAC1100 PCI RAID Controller support ? ? ? ? <M> Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL) ? ? ? ? <M> Loopback device support ? ? ? ? <M> Cryptoloop Support ? ? ? ? <M> Network block device support ? ? ? ? <M> Promise SATA SX8 support ? ? ? ? < > Low Performance USB Block driver ? ? ? ? <*> RAM block device support ? ? ? ? (16) Default number of RAM disks ? ? ? ? (8192) Default RAM disk size (kbytes) ? ? ? ? [ ] Support XIP filesystems on RAM block device ? ? ? ? <M> Packet writing on CD/DVD media (8) Free buffers for data gathering ? ? ? ? [ ] Enable write caching (EXPERIMENTAL) ? ? ? ? <M> ATA over Ethernet support ? ? ? ? [(8) Free buffers for data gathering ? ? ? ? [ ] Enable write caching (EXPERIMENTAL) ? ? ? ? <M> ATA over Ethernet support ? ? ? ? [ ] Very old hard disk (MFM/RLL/IDE) driver ] Very old hard disk (MFM/RLL/IDE) driver
This is the page for block devices. There is hardly any entry for generic IDE devices. Do I have the wrong source?
On Wed, Dec 24, 2008 at 11:58 AM, Rony gnulinuxist@gmail.com wrote:
My system is Etch and the kernel was downloaded from kernel.org using the F (Full source) link. Commands used were...
dumb question... did you copy over your current .config to the new kernel's source tree before you actually did the make menuconfig?
On Wednesday 24 December 2008 22:28, Rony wrote:
--- Block devices ? ? ? ? <M> Normal floppy disk support ? ? ? ? <M> XT hard disk support ? ?
? ? <M> ATA over Ethernet support ? ? ? ? [ ] Very old hard disk (MFM/RLL/IDE) driver ] Very old hard disk (MFM/RLL/IDE) driver This is the page for block devices. There is hardly any entry for generic IDE devices. Do I have the wrong source?
General setup- Device Drivers ---> [*] Block devices --->
Then the next entry <*> ATA/ATAPI/MFM/RLL support ---> inside the above a submenu for <*> generic/default IDE chipset support
This is from 2.6.27.6. But afair the menu options for our area of interest hasnt changed in years. If it does not appear here something is wrong with your .config. make clean;make mrproper will clean up everything including .config. You will now have to redo the whole thing manually, a very educating process, and a strongly recommended experience.
A year or so ago I could not get SATA booting without initrd, inspite of compiling in kernel sata. I simply coud not figure out what was wrong. However a few weeks later i used a newer kernel and recompiled from scratch and everything worked.
jtd wrote:
On Wednesday 24 December 2008 22:28, Rony wrote:
--- Block devices ? ? ? ? <M> Normal floppy disk support ? ? ? ? <M> XT hard disk support ? ?
? ? <M> ATA over Ethernet support ? ? ? ? [ ] Very old hard disk (MFM/RLL/IDE) driver ] Very old hard disk (MFM/RLL/IDE) driver This is the page for block devices. There is hardly any entry for generic IDE devices. Do I have the wrong source?
General setup- Device Drivers ---> [*] Block devices --->
Then the next entry <*> ATA/ATAPI/MFM/RLL support ---> inside the above a submenu for <*> generic/default IDE chipset support
This is from 2.6.27.6. But afair the menu options for our area of interest hasnt changed in years. If it does not appear here something is wrong with your .config. make clean;make mrproper will clean up everything including .config. You will now have to redo the whole thing manually, a very educating process, and a strongly recommended experience.
A year or so ago I could not get SATA booting without initrd, inspite of compiling in kernel sata. I simply coud not figure out what was wrong. However a few weeks later i used a newer kernel and recompiled from scratch and everything worked.
Will definitely try it out.
-
Dinesh Joshi -
jtd -
Osric Fernandes -
Rony