K Montgomery wrote: >Serkan and everyone, > >I think I have a similar problem. I'm currently running 8.1 and when I >try to upgrade to 8.2 from CD (booting from floppy), it crashes after I >tell the install I have no SCSI devices. Below are some of the messages >on the screens at the point of the freeze. (Forgive me if I didn't get >the "F" keys right.) > >I have an Abit BH6 motherboard with an Intel PII 350 processor >(overclocked). Other hardware includes an internal Iomega ZIP 250 and a >Western Digital Caviar ~8 GB hard drive (sorry I don't have the exact >model in front of me). I tried to follow the advice about disabling >USB, but I couldn't find an appropriate setting in my BIOS, either. > >ALT-F1, last message on screen is: > >Entering step `Setup filesystems' > >ALT-F3, last few lines on screen read: > >* running: /usr/bin/insmod_ 2 >/dev/tty5 /tmp/imm.o >* warning: insmod'ing module imm failed at >/usr/bin/perl-install/modules.pm line 625. >* running: /usr/bin/insmod_ 2 >/dev/tty5 /tmp/ppa.o >* warning: insmod'ing module ppa failed at >/usr/bin/perl-install/modules.pm line 625. >* step `setupSCSI' finished >* starting step `doPartitionDisks' >* warning: bad magic number at >/usr/bin/perl-install/partition_table_empty.pm line 29. >* found a dos partition table on /dev/hda at sector 0 >* test_for_bad_drives*/dev/hda) > >ALT-F4, last few lines: ><4>WARNING - no ppa compatible devices found. ><4> As of 31/Aug/1998 Iomega started shipping parallel ><4> port ZIP drives with a different interface which is ><4> supported by the imm (ZIP Plus) driver. If the ><4> cable is marked with "AutoDetect", this is what has ><4> happened. > >ALT-F5: >/tmp/imm.o: init_module: No such device >/tmp/ppa.o: init_module: No such device > >And finally, I attached a photo of my frozen blue install screen (oh, the irony). >Hope this turns on a light bulb for someone. > >- Kathy > >On Thu, 2002-05-16 at 18:24, Serkan Barut wrote: > >>Now i understand your point.But there is no switch for a usb controller in my >bios(or is there another way that i dont know how to disable it?)With two other >distros,JBLinux and Peanut i had no problem with the partition check process,it just >printed a few messages and then went on.Nevertheless i think i would use one of the >alt kernels for now.If you hear smth about the subject iwould be pleased to hear >about it. >> >> >>Serkan >> >> >> ------------------------------------------------------------------------ >> >> <cid:[EMAIL PROTECTED]> >> >> >>------------------------------------------------------------------------ >> >>Want to buy your Pack or Services from MandrakeSoft? >>Go to http://www.mandrakestore.com >> That is really a partition check hang.
1. Drop your clock rate. 2. make sure you have a 40-pin cable on the drive, not an 80 to limit UDMA to 33MHz or less. 3. Next drive acquisition, please consider NOT buying a brand which supports (officially) only Windows and Solaris (and the Solaris for SCSI drives at that). There is more trouble with WDs than all the others combined, in linux. 4. F1 at the splash screen and linux ide0=noautotune because WDs usually rate themselves higher than they run well at. (Example WD200AB on a PIII 933 with VIA KT133A running RH 7.1 was set to UDMA66 and producing a rousing 1.6M/sec when tested with hdparm -t /dev/hda 5. By dropping the data rate to 33MHz, a slight performance improbvement was noted, from a 1.6Mb/s at 66 to 9.4 Mb/s at 33. Obviously there were many errors and rereads at the higher speed. Finally on some WDs, there is a problem with estimation--since they are single-platter with two heads physically, their Cylinder, Head ans Sector numbers for Logical Block Addressing must be calculated. A few models show more capacity (closer to tru physical capacity) at a solution that provides 240 heads rather than 255. The difference is between the 32-bit math of the kernel and the 16-bit math of the BIOS. So see what the CHS numbers are in the BIOS and compare those to F1 at the splash screen and rescue booting a normal rescue and # fdisk -l /dev/hda anfd looking at the reported CHS numbers. By now, we think we have closed off those approximation errors but there is always the chance that there is a cheap drive out there that we missed in the exception table, and there is a method of overriding the calculated CHS numbers with a kernel message, so check. If the numbers are different, bingo. linux has much tighter timing that Windows in its drivers, so overclocking is often enough to kill a few devices... It is better unless you have top-notch hardware to run linux at designed clock speeds. Civileme
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
