On Tuesday 26 February 2002 16:48, Kevin Donnelly wrote:
On Monday 25 February 2002 8:52 pm, Anders Johansson wrote:
Yep, but I think kdm's liloinfo barfs on the warning. It runs lilo -q and tries to parse the output, and I suspect this is throwing it. At least that's all I can think of, since your kdmrc looks just like mine. I suggest you investigate it, by for instance running lilo in very verbose mode and seeing why it's warning you
Interesting thread. I originally had a 30Gb drive with Windows on it (hda), and installed a second 4Gb one with Suse 7.1 (hdd). I could boot into both OSs OK. Then I took that out and replaced it with a 40Gb IBM drive. I had problems partitioning this, and had to use IBM's utility to "clear" the drive. Then I used Partition Magic to format it, and put 7.2 on it.
This sounds familiar. I have done a similar thing wiht my system. I posted a while ago with drive problems after formatting a new drive to FAT32 using Win2k. I have to wonder if my Linux install is seeing the new drive as 0x82. I am hoping to play around with the drives this weekend (if I have time) using this suggestion I was given then (and haven't had time to try yet): -=-=-=-=-=-=-=-=-===- repartition the disk using linux fdisk and create a partition table with the following entries: 01 extended (full disk size) 05 logical1 (20G) make this type 0b 06 logical2 (20G) make this type 0b 07 logical3 (17G) make this type 0b after fdisking the disk (assume its hdb) do the following dd if=/dev/zero of=/dev/hdb5 bs=512b count=2 and do the same with /dev/hdb6 and /dev/hdb7 sync sync init 6 and format the drives from windows2K using Fat32. -=-=-=-=-==-=-=-=-=-=-
lilo -T geom=0x82 gives: bios=0x82, cylinders=1024, heads=255, sectors=63 EDD packet calls allowed
With lilo -T geom=0x82, I get: bios=0x82, cylinders=4865, heads=255, sectors=63 EDD packet calls allowed
I note that dmesg gives the following info: hda: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(66) hdd: 80418240 sectors (41174 MB) w/380KiB Cache, CHS=79780/16/63, UDMA(33) and later: hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 > hdd: [PTBL] [5005/255/63] hdd1 hdd2 hdd3 hdd4 < hdd5 hdd6 hdd7 hdd8 hdd9 hdd10 hdd11 hdd12 hdd13 >
dmsg on my system gives me: hda: 16514064 sectors (8455 MB) w/418KiB Cache, CHS=1027/255/63, (U)DMA hdb: 117266688 sectors (60041 MB) w/1819KiB Cache, CHS=7299/255/63, UDMA(66) hdc: 78165361 sectors (40021 MB) w/1024KiB Cache, CHS=77545/16/63, UDMA(66) and of course.... my old friend: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x84 { DriveStatusError BadCRC } Looking at this now, it looks like the info for 0x82 matches one of the partitions on my 60Gig drive (hdb). I have been having problems accessing this drive from Linux (all partitions on hdb are fine when accessing from Windows2k, but Linux can only see the first partition)... thus the re-fdisk and re-format instructions I included above. So... the big experiment... archive the data I have on my 60Gig drive, do the steps to fdisk and format... try reading the drive, check what lilo -q has to say after hdb is supposedly fixed. Any other comments of suggestions before I launch into this?? C.