Weird partititon recocnising problem in 2.6.0-testX
We have a new boot log at
http://ludenkalle.de/ide_change_kernel.txt
With CONFIG_BLK_DEV_IDEDISK=y but unset CONFIG_BLK_DEV_HD_IDE and the inserted (and no used) printk stuff.
Regards, Konsti
Signature · 5 lines
2.6.0-test8-love3 Konstantin Kletschke <[email protected]>, <[email protected]> GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF keulator.homelinux.org up 1:01, 13 users
Quoted 6 lines · Konstantin Kletschke
We have a new boot log at
http://ludenkalle.de/ide_change_kernel.txt
With
CONFIG_BLK_DEV_IDEDISK=ybut unsetCONFIG_BLK_DEV_HD_IDEand the inserted (and no used) printk stuff.
Good. Now it really does partition reading.
At some later time we must come back and find out what is wrong with hd.c. You call the printk stuff unused, but it was used and printed
partition start 63 size 4096512 type 85 p1
partition start 4096575 size 15904350 type 85 p2
partition start 0 size 0 type 0
partition start 0 size 0 type 0
Let us compare with your data from earlier:
Device Boot Start End Blocks Id System /dev/hda1 * 1 365 2931831 83 Linux /dev/hda2 366 1245 7068600 5 Extended /dev/hda5 366 487 979933+ 83 Linux /dev/hda6 1185 1245 489951 82 Linux swap
Clearly, you have EZDrive installed, the table below is what is found in sector 1, the data printed above is what is in sector 0. The tables differ - fdisk was used after installation of EZDrive.
I suppose that booting with boot parameter "hda=remap" should work. At some later time we must worry about how to get rid of EZDrive.
Andries
Quoted 7 lines · Andries Brouwer
Quoted 3 lines
With
CONFIG_BLK_DEV_IDEDISK=ybut unsetCONFIG_BLK_DEV_HD_IDEand the inserted (and no used) printk stuff.At some later time we must come back and find out what is wrong with
hd.c. You call the printk stuff unused, but it was used and printed
It was unused earlier, now, with CONFIG_BLK_DEV_IDEDISK=y but _unset_ CONFIG_BLK_DEV_HD_IDE it gets printed (to clear that).
Quoted 4 lines
Clearly, you have EZDrive installed, the table below is what is found in sector 1, the data printed above is what is in sector 0. The tables differ - fdisk was used after installation of EZDrive.
Hm, interesting... I don't know what was on this disk in earlier days... So it may be a help dd'ing Sektor 0 and 1 and create new table?
But of course after debugging that if you are interesting in that (which seems to be the case here :)).
Here is what 2.6.0-test6-mm4 looks like when booting (wo printk mod):
http://ludenkalle.de/2.6.0-test6-mm4.txt
Quoted 2 lines
I suppose that booting with boot parameter "hda=remap" should work. At some later time we must worry about how to get rid of EZDrive.
OK, lets see...
Konsti
Signature · 5 lines
2.6.0-test8-love3 Konstantin Kletschke <[email protected]>, <[email protected]> GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF keulator.homelinux.org up 2:00, 18 users
Quoted 2 lines · Andries Brouwer
I suppose that booting with boot parameter "hda=remap" should work.
Seems so...
http://ludenkalle.de/2.6.0-test6-mm4-remap.txt
Konsti
Signature · 5 lines
2.6.0-test8-love3 Konstantin Kletschke <[email protected]>, <[email protected]> GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF keulator.homelinux.org up 2:35, 19 users