Re: freebsd has problems with bios
The bios has 4 modes auto, large, lba, chs in which to access the hard disk. I ttried all 4 modes and it doesn't solve the problem. No, i didn't say to try different bios modes. I said (which fdisk also says) that you should: 1. Go into the bios, see what it reports as the CHS 2. Reboot (i thought this part was a given to get back to Fdisk) 3. When you get up to the fdisk section, enter the CHS value given to you by the bios using the g key, and writing it manually. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd has problems with bios
I was replying to both you and Andrew R. Andrew mentioned the hw may be unstable. I did enter the same values provided by BIOS -but it doesn't solve the problem. Most likely, the bios on my motherboard is not compaible with freebsd. regards -kamal On 13-Oct-05, at 11:35 AM, Peter Clutton wrote: The bios has 4 modes auto, large, lba, chs in which to access the hard disk. I ttried all 4 modes and it doesn't solve the problem. No, i didn't say to try different bios modes. I said (which fdisk also says) that you should: 1. Go into the bios, see what it reports as the CHS 2. Reboot (i thought this part was a given to get back to Fdisk) 3. When you get up to the fdisk section, enter the CHS value given to you by the bios using the g key, and writing it manually. Kamal R. Prasad UNIX systems consultant http://www.kamalprasad.com/ [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd has problems with bios
On 10/13/05, Kamal R. Prasad [EMAIL PROTECTED] wrote: I was replying to both you and Andrew R. Andrew mentioned the hw may be unstable. I did enter the same values provided by BIOS -but it doesn't solve the problem. Most likely, the bios on my motherboard is not compaible with freebsd. regards -kamal In fact FreeBSD bypasses BIOS and interacts directly with a disk controller. Could you tell us the exact vendor and make of your motherboard. It's an interesting case. Thanks, Andrew P. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd has problems with bios
Kamal R. Prasad [EMAIL PROTECTED] writes: I have verified integrity of the hard disk and this problem shows up on a new samsung 1604N hard disk too. It is a hard disk independet problem. On 13-Oct-05, at 5:49 AM, Peter Clutton wrote: For some reason, the values of hard disk geometry (cylinders/head/ sectors( are not accrptable to fdisk and when i agree to using freebsd 's idea of disk geometryt, during sysinstall -I get an error:-0 UDMA_100 error:READWRITE Failure ICRC error. Usually fdsisk asks you to check what the bios reports as the CHS and enter that manually, using the g option i believe. Have you tried this? The bios has 4 modes auto, large, lba, chs in which to access the hard disk. I ttried all 4 modes and it doesn't solve the problem. However as stated above, and looking at those errors, this may be a hardware problem. The hardware is stable and I expect any hard disk to give the same error essentially because the interaction between bios and freebsd is the cause of the problem. A CRC error? Doesn't seem likely. Why do you say so? It's not like FreeBSD is using the BIOS at all at that point... Personally, I'd try another ATA cable; that's the most frequent cause of this particular symptom. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd has problems with bios
The motherboard is from American Megatrends Corp and it runs Award Bios. I am pasting below info from dmesg below:- -- CPU: AMD Athalon(tm) XP(1468.47-Mhz 686 class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features -0x383f9ffFPu,VME,DE,PSE,F\PSE,TSC ,MSR,PAE,MCE,CXU,SEP,MTER,PGE,MCA,CMOV,PAT,PSE36,MMx,FXSR,SSE AMD Features=0xc0480800SYSCALL,MP,MMX+,3DNoq+,3DNow .. npx0:[FAST] npx0: math coprocessor on motherboard npx0: INT 16 interface acpi0: VIA694 AWRDACPI on motherboard ... ata0: ATA channel0 on atapci0 ata1: ATA Channel 1 on ataci0 ad0: Samsung SP1604N TM100-30 at ata0-master UDMA100 acd0: dvd r drive at ata0-slave UDMA33 ad2: 39083MB Maxtor 4D040H2 DAH017K0 at ata1-master UDMA100 ad0: WARTNING -READ_DMA UDMA ICRC error (retrying request) LBA=63 .. ad0: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=63 ad2: WARTNING -READ_DMA UDMA ICRC error (retrying request) LBA=63 .. ad2: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED - sector 63 is where the first partition starts. Both discs work perfectly in windows XP and the -and if there was a cable/hw [roblem it would have shown during their functioning under windows xp. pl. let me know if you need any more info from the system. thanks -kamal On 13-Oct-05, at 3:54 PM, Andrew P. wrote: On 10/13/05, Kamal R. Prasad [EMAIL PROTECTED] wrote: I was replying to both you and Andrew R. Andrew mentioned the hw may be unstable. I did enter the same values provided by BIOS -but it doesn't solve the problem. Most likely, the bios on my motherboard is not compaible with freebsd. regards -kamal In fact FreeBSD bypasses BIOS and interacts directly with a disk controller. Could you tell us the exact vendor and make of your motherboard. It's an interesting case. Thanks, Andrew P. Kamal R. Prasad UNIX systems consultant http://www.kamalprasad.com/ [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd has problems with bios
On 10/13/05, Kamal R. Prasad [EMAIL PROTECTED] wrote: The motherboard is from American Megatrends Corp and it runs Award Bios. I am pasting below info from dmesg below:- -- CPU: AMD Athalon(tm) XP(1468.47-Mhz 686 class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features -0x383f9ffFPu,VME,DE,PSE,F\PSE,TSC ,MSR,PAE,MCE,CXU,SEP,MTER,PGE,MCA,CMOV,PAT,PSE36,MMx,FXSR,SSE AMD Features=0xc0480800SYSCALL,MP,MMX+,3DNoq+,3DNow .. npx0:[FAST] npx0: math coprocessor on motherboard npx0: INT 16 interface acpi0: VIA694 AWRDACPI on motherboard ... ata0: ATA channel0 on atapci0 ata1: ATA Channel 1 on ataci0 ad0: Samsung SP1604N TM100-30 at ata0-master UDMA100 acd0: dvd r drive at ata0-slave UDMA33 ad2: 39083MB Maxtor 4D040H2 DAH017K0 at ata1-master UDMA100 ad0: WARTNING -READ_DMA UDMA ICRC error (retrying request) LBA=63 .. ad0: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED LBA=63 ad2: WARTNING -READ_DMA UDMA ICRC error (retrying request) LBA=63 .. ad2: FAILURE -READ_DMA status=51READY,DSC,ERROR error=84ICRC,ABORTED - sector 63 is where the first partition starts. Both discs work perfectly in windows XP and the -and if there was a cable/hw [roblem it would have shown during their functioning under windows xp. pl. let me know if you need any more info from the system. thanks -kamal Do you honestly believe that a leading BIOS vendor would manufacture a motherboard and install a BIOS from its main competitor? Anyway, AMI does not manufacture motherboards which support AMD processors. Your controller is probably recognized as atapci0: VIA 8233 UDMA100 controller ... It is fully supported, there's no doubt about that. I'll bet you have some problem with cables, they can claim to be ATA100-compatible, but you should try other ones, maybe more expensive ones. Windows and Linux might have a better (in some ways) driver implementation, which somehow handles faulty cables (by more aggressive CRC recovery mechanisms, for example). When you check your cables, recheck them, and redo it all over again - and you're dead sure that they are in top-notch condition (please, try at least two different 80-conductor ones, I mean apart from those that are there already, and at least one 40-conductor cable), you should try upgrading to at least RELENG_5 (5-stable), or better yet RELENG_6 (6-current). In case the problem persists you can try to reopen pr i386/62687: http://www.freebsd.org/cgi/query-pr.cgi?pr=62687 or to send a new pr, which references this old one. Thanks for your time. Post here any follow-ups, I'll try to help you. Cheerz, Andrew P. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freebsd has problems with bios
Hello. I have an american megatrends corp motherboard with an amd 2 ghz processor, For some reason, the values of hard disk geometry (cylinders/head/ sectors( are not accrptable to fdisk and when i agree to using freebsd 's idea of disk geometryt, during sysinstall -I get an error:-0 UDMA_100 error:READWRITE Failure ICRC error. can someone tell me how to get past this issue? The drive is a maxtor 40 Gb hard disk. thanks -kamal Kamal R. Prasad UNIX systems consultant http://www.kamalprasad.com/ [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd has problems with bios
On 10/12/05, Kamal R. Prasad [EMAIL PROTECTED] wrote: Hello. I have an american megatrends corp motherboard with an amd 2 ghz processor, For some reason, the values of hard disk geometry (cylinders/head/ sectors( are not accrptable to fdisk and when i agree to using freebsd 's idea of disk geometryt, during sysinstall -I get an error:-0 UDMA_100 error:READWRITE Failure ICRC error. can someone tell me how to get past this issue? The drive is a maxtor 40 Gb hard disk. thanks -kamal Kamal R. Prasad UNIX systems consultant http://www.kamalprasad.com/ [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Please, before we continue, verify your HDD integrity Download diagnostics software from www.maxtor.com Floppy disk: http://maxtor.com/portal/site/Maxtor/menuitem.3c67e325e0a6b1f6294198b091346068/?channelpath=/en_us/Support/Software%20Downloads/All%20DownloadsdownloadID=22 CD-ROM: http://maxtor.com/portal/site/Maxtor/menuitem.3c67e325e0a6b1f6294198b091346068/?channelpath=/en_us/Support/Software%20Downloads/All%20DownloadsdownloadID=113 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd has problems with bios
For some reason, the values of hard disk geometry (cylinders/head/ sectors( are not accrptable to fdisk and when i agree to using freebsd 's idea of disk geometryt, during sysinstall -I get an error:-0 UDMA_100 error:READWRITE Failure ICRC error. Usually fdsisk asks you to check what the bios reports as the CHS and enter that manually, using the g option i believe. Have you tried this? However as stated above, and looking at those errors, this may be a hardware problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd has problems with bios
I have verified integrity of the hard disk and this problem shows up on a new samsung 1604N hard disk too. It is a hard disk independet problem. On 13-Oct-05, at 5:49 AM, Peter Clutton wrote: For some reason, the values of hard disk geometry (cylinders/head/ sectors( are not accrptable to fdisk and when i agree to using freebsd 's idea of disk geometryt, during sysinstall -I get an error:-0 UDMA_100 error:READWRITE Failure ICRC error. Usually fdsisk asks you to check what the bios reports as the CHS and enter that manually, using the g option i believe. Have you tried this? The bios has 4 modes auto, large, lba, chs in which to access the hard disk. I ttried all 4 modes and it doesn't solve the problem. However as stated above, and looking at those errors, this may be a hardware problem. The hardware is stable and I expect any hard disk to give the same error essentially because the interaction between bios and freebsd is the cause of the problem. regards -kamal Kamal R. Prasad UNIX systems consultant http://www.kamalprasad.com/ [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
