Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Christoph Kukulies schrieb: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Final remark: I changed the motherboard in the end but actually I suspect that the reason the install got hung was not the READ BIG MEDIUM ERROR (I got this error also with the new motherboard and the install got past this error and continued), the reason was, that I had an ASUS ST-200 SCSI card (NCR Symbios chipset?) sticking in the system that could have caused all the trouble. Either it was the fact that this card had trouble with FreeBSD anyway (I remember something in this vein) or the card was defective or it was a problem with card and motherboard. Anyway, the problem has resolved. Thanks a lot for the good advice, explanations, tips etc. -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Jeremy Chadwick schrieb: acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x21 ascq=0x00 (asc=0x21 at this time FWIW). This won't help you get FreeBSD installed any quicker, but it will give you some insight to what the error messages mean. ATAPI essentially uses SCSI commands but over an ATA bus, which is why atapicam(4) exists (which is what's giving you the xpt_* errors). The problem is that not all drives are created equal, so some behave differently to certain commands than others. ASC and ASCQ are, in layman's terms, "error codes" with added degrees of granularity. ASC = Additional Sense Code, ASCQ = Additional Sense Code Qualifier. These are fairly well-documented all over the web, and per T10 specifications. Looking at a chart, specifically noting errors that are for CD (MMC) devices, we find: ASC 0x11, ASCQ 0x00 == Unrecovered Read Error ASC 0x21, ASCQ 0x00 == Logical Block Address (LBA) Out of Range Your first reaction will be "So does this mean I have a bad CD?", and the answer is "not necessarily". It could be that the drive does not support the commands FreeBSD expects available to read a CD in this particular fashion. But it could also be a badly burned CD, or a CD burned with buggy software. If at all possible, try another CD drive of some kind. Get one from a friend, borrow one, or buy one. People have had good experiences with Plextor and Pioneer drives, while recent Samsung drives have been hit-or-miss. I'm now at home at a different burner but I probably don't have a different CD recording software other than cdrecord available. that's Windows XP BTW, under which I burnt that CDs. I could prbably boot an older (4.x) FreeBSD on that machine but that would be CD record, too. Medium is also a 80 min 700 MB CD. Weren't they 650 MB in earlier times actually? Earlier times I mean, when I still had my FreeBSD subscription and got each release in a neat CD set :-) Oh well, I will give it another try and see how it works out. Later -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
On Wed, Nov 05, 2008 at 05:26:38PM +0100, Christoph Kukulies wrote: > Christoph Kukulies schrieb: >> Christoph Kukulies schrieb: >>> Hi Al, >>> >>> thanks for pointing me to safe mode install. That I will probably try >>> tomorrow. >>> The day ended up in havoc: I tried to boot a floppy to do an ASUS >>> BIOS upgrade and somehow messed with the power cable. >>> A big flash occurred originating from the power supply. I opened the >>> power supply, found a blown fuse, ran to the electronics store, >>> bought a new fuse (+ one in reserve), inserted the fuse, tried the >>> power supply, with connections off and a firework, prematurely - your >>> presidential elections aren't finished yet - , developed in front of >>> my face. Will continue tomorrow, when America has a new president. >>> >> >> Back at the problem: I chose 3. safe mode to no avail. Still get this >> >> acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 > I now tried with a 7.0 BETA Boot CD (which I had laying around from > possibly another fruitless attempt in the past to > update that system from 5.1 or something to 7.x). Same picture. Hangs on > this > > acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x21 ascq=0x00 > (asc=0x21 at this time FWIW). This won't help you get FreeBSD installed any quicker, but it will give you some insight to what the error messages mean. ATAPI essentially uses SCSI commands but over an ATA bus, which is why atapicam(4) exists (which is what's giving you the xpt_* errors). The problem is that not all drives are created equal, so some behave differently to certain commands than others. ASC and ASCQ are, in layman's terms, "error codes" with added degrees of granularity. ASC = Additional Sense Code, ASCQ = Additional Sense Code Qualifier. These are fairly well-documented all over the web, and per T10 specifications. Looking at a chart, specifically noting errors that are for CD (MMC) devices, we find: ASC 0x11, ASCQ 0x00 == Unrecovered Read Error ASC 0x21, ASCQ 0x00 == Logical Block Address (LBA) Out of Range Your first reaction will be "So does this mean I have a bad CD?", and the answer is "not necessarily". It could be that the drive does not support the commands FreeBSD expects available to read a CD in this particular fashion. But it could also be a badly burned CD, or a CD burned with buggy software. If at all possible, try another CD drive of some kind. Get one from a friend, borrow one, or buy one. People have had good experiences with Plextor and Pioneer drives, while recent Samsung drives have been hit-or-miss. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Christoph Kukulies schrieb: Christoph Kukulies schrieb: Hi Al, thanks for pointing me to safe mode install. That I will probably try tomorrow. The day ended up in havoc: I tried to boot a floppy to do an ASUS BIOS upgrade and somehow messed with the power cable. A big flash occurred originating from the power supply. I opened the power supply, found a blown fuse, ran to the electronics store, bought a new fuse (+ one in reserve), inserted the fuse, tried the power supply, with connections off and a firework, prematurely - your presidential elections aren't finished yet - , developed in front of my face. Will continue tomorrow, when America has a new president. Back at the problem: I chose 3. safe mode to no avail. Still get this acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 I now tried with a 7.0 BETA Boot CD (which I had laying around from possibly another fruitless attempt in the past to update that system from 5.1 or something to 7.x). Same picture. Hangs on this acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x21 ascq=0x00 (asc=0x21 at this time FWIW). Please help me in getting FreeBSD onto this machine iin whatever way. -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Christoph Kukulies schrieb: Hi Al, thanks for pointing me to safe mode install. That I will probably try tomorrow. The day ended up in havoc: I tried to boot a floppy to do an ASUS BIOS upgrade and somehow messed with the power cable. A big flash occurred originating from the power supply. I opened the power supply, found a blown fuse, ran to the electronics store, bought a new fuse (+ one in reserve), inserted the fuse, tried the power supply, with connections off and a firework, prematurely - your presidential elections aren't finished yet - , developed in front of my face. Will continue tomorrow, when America has a new president. Back at the problem: I chose 3. safe mode to no avail. Still get this acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config I even changed the CDROM drive to a very old slow one. I changes IDE busses (first vs. second IDE) to no avail. I'm now gonna burn another medium. No luck yet installing 7.1 BETA2. I'm also a long time FreeBSD user btw, from times where it was called "386bsd" :-) -- Christoph -- Christoph Al Plant schrieb: Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 This makes the HD and CD to work for me after the install. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Jeremy Chadwick wrote: On Tue, Nov 04, 2008 at 12:46:43PM -1000, Al Plant wrote: Jeremy Chadwick wrote: On Tue, Nov 04, 2008 at 08:13:34AM -1000, Al Plant wrote: Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 There is no hw.ata.ata-dma tunable. I think you mean hw.ata.ata_dma (note: underscore, not hyphen). If you really are using hw.ata.ata-dma, it does nothing. :-) Also folks, please remember that "ATA DMA" is for hard disks, and "ATAPI DMA" is for ATAPI devices (CD/DVD drives). Error messages from xpt_* functions are from by the ATAPI-to-CAM emulation layer (think: SCSI emulation for ATAPI devices), but are likely signs of underlying compatibility problems between the CD/DVD drive and FreeBSD, and not the fault of atapicam(4). I'm not sure if there's a loader hint to disable xpt. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. The "READ BIG MEDIUM ERROR" often indicates that the CD/DVD drive does not support a specific read operation mode; some CD/DVD manufacturers don't implement this command for various reasons. Aloha Jeremy, Thanks for catching the - vs _ . I hear you, but I have to do the hw settings like above or the servers wont boot they stick at a db> or mountroot> Those are two very different things. A db> prompt indicates you're hitting a kernel panic, while a mountroot> prompt indicates the OS can't find your root filesystem. I think the 7 and 8 series OS are looking for SATA and dont like the IDE drives I use. I understand, but what I'm saying is that "hw.ata.ata-dma=0" (note the hyphen) is not fixing/solving anything, because it contains a typo. I know the atapi setting is for CD's and These are brand new DVD/CD RW burners fwiw. A month or so back there were several people on line complaining about this. Maybe one of the FreeBSD comitters will have a look and see if something is wrong. The "I get dropped to a mountroot prompt" problem has been reported many times, and so far there haven't been any indications what causes it to happen for people. _ Aloha Jeremy, The - was not in the installs. I typed it correctly in the several cases where it was used. It will be interesting to see if anybody can find a solution to these issues. I am not a coder just a long time user of FreeBSD, (since 3.*) I think it was. It is such a rock solid system that most of us are curious when something like this happens and its hard to find out why. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + < email: [EMAIL PROTECTED] > "All that's really worth doing is what we do for others."- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
On Tue, Nov 04, 2008 at 12:46:43PM -1000, Al Plant wrote: > Jeremy Chadwick wrote: >> On Tue, Nov 04, 2008 at 08:13:34AM -1000, Al Plant wrote: >>> Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: > Hi, > > don't know whether it's the CDROM drive (a Creative 52x mx) or > the motherboard (ASUS P4S8X) or what. > Anyway, I tried to install a recent version of FreeBSD > (7.1-BETA2) and the installation > hangs right in the boot process of the installation CD disc1. > > I see > > acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 > run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config > > and so on. > > Any clues? > > -- > Christoph Kukulies > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" >>> >>> >>> Aloha, >>> >>> I have had similiar happen on 7 and 8 Freebsd installs recently. >>> >>> If you install using safe mode it will work. Then in /boot/loader.conf >>> >>> #boot/loader.conf >>> hw.ata.ata-dma=0 >>> hw.ata.atapi_dma=0 >> >> There is no hw.ata.ata-dma tunable. I think you mean hw.ata.ata_dma >> (note: underscore, not hyphen). If you really are using hw.ata.ata-dma, >> it does nothing. :-) >> >> Also folks, please remember that "ATA DMA" is for hard disks, and >> "ATAPI DMA" is for ATAPI devices (CD/DVD drives). >> >> Error messages from xpt_* functions are from by the ATAPI-to-CAM >> emulation layer (think: SCSI emulation for ATAPI devices), but are >> likely signs of underlying compatibility problems between the CD/DVD >> drive and FreeBSD, and not the fault of atapicam(4). >> >> I'm not sure if there's a loader hint to disable xpt. >> >>> The error that comes up when you burn a CD seems to be bogus as I >>> have used the CD's with out error for installing on other boxes. >> >> The "READ BIG MEDIUM ERROR" often indicates that the CD/DVD drive does >> not support a specific read operation mode; some CD/DVD manufacturers >> don't implement this command for various reasons. >> > Aloha Jeremy, > > Thanks for catching the - vs _ . > > I hear you, but I have to do the hw settings like above or the servers > wont boot they stick at a db> > or mountroot> Those are two very different things. A db> prompt indicates you're hitting a kernel panic, while a mountroot> prompt indicates the OS can't find your root filesystem. > I think the 7 and 8 series OS are looking for SATA and dont like the IDE > drives I use. I understand, but what I'm saying is that "hw.ata.ata-dma=0" (note the hyphen) is not fixing/solving anything, because it contains a typo. > I know the atapi setting is for CD's and These are brand new DVD/CD RW > burners fwiw. > > A month or so back there were several people on line complaining about > this. > > Maybe one of the FreeBSD comitters will have a look and see if > something is wrong. The "I get dropped to a mountroot prompt" problem has been reported many times, and so far there haven't been any indications what causes it to happen for people. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Jeremy Chadwick wrote: On Tue, Nov 04, 2008 at 08:13:34AM -1000, Al Plant wrote: Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 There is no hw.ata.ata-dma tunable. I think you mean hw.ata.ata_dma (note: underscore, not hyphen). If you really are using hw.ata.ata-dma, it does nothing. :-) Also folks, please remember that "ATA DMA" is for hard disks, and "ATAPI DMA" is for ATAPI devices (CD/DVD drives). Error messages from xpt_* functions are from by the ATAPI-to-CAM emulation layer (think: SCSI emulation for ATAPI devices), but are likely signs of underlying compatibility problems between the CD/DVD drive and FreeBSD, and not the fault of atapicam(4). I'm not sure if there's a loader hint to disable xpt. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. The "READ BIG MEDIUM ERROR" often indicates that the CD/DVD drive does not support a specific read operation mode; some CD/DVD manufacturers don't implement this command for various reasons. Aloha Jeremy, Thanks for catching the - vs _ . I hear you, but I have to do the hw settings like above or the servers wont boot they stick at a db> or mountroot> error I think the 7 and 8 series OS are looking for SATA and dont like the IDE drives I use. I know the atapi setting is for CD's and These are brand new DVD/CD RW burners fwiw. A month or so back there were several people on line complaining about this. Maybe one of the FreeBSD comitters will have a look and see if something is wrong. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + < email: [EMAIL PROTECTED] > "All that's really worth doing is what we do for others."- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
On Tue, Nov 04, 2008 at 08:13:34AM -1000, Al Plant wrote: > Julien Cigar wrote: >> I've this problem too on almost all my machines. The only solution I've >> found is to disable DMA (atapi_dma), but then performances are very poor >> (and I'm still unable to burn a CD/DVD) >> >> On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: >>> Hi, >>> >>> don't know whether it's the CDROM drive (a Creative 52x mx) or the >>> motherboard (ASUS P4S8X) or what. >>> Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) >>> and the installation >>> hangs right in the boot process of the installation CD disc1. >>> >>> I see >>> >>> acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 >>> run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config >>> run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config >>> run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config >>> >>> and so on. >>> >>> Any clues? >>> >>> -- >>> Christoph Kukulies >>> ___ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > Aloha, > > I have had similiar happen on 7 and 8 Freebsd installs recently. > > If you install using safe mode it will work. Then in /boot/loader.conf > > #boot/loader.conf > hw.ata.ata-dma=0 > hw.ata.atapi_dma=0 There is no hw.ata.ata-dma tunable. I think you mean hw.ata.ata_dma (note: underscore, not hyphen). If you really are using hw.ata.ata-dma, it does nothing. :-) Also folks, please remember that "ATA DMA" is for hard disks, and "ATAPI DMA" is for ATAPI devices (CD/DVD drives). Error messages from xpt_* functions are from by the ATAPI-to-CAM emulation layer (think: SCSI emulation for ATAPI devices), but are likely signs of underlying compatibility problems between the CD/DVD drive and FreeBSD, and not the fault of atapicam(4). I'm not sure if there's a loader hint to disable xpt. > The error that comes up when you burn a CD seems to be bogus as I have > used the CD's with out error for installing on other boxes. The "READ BIG MEDIUM ERROR" often indicates that the CD/DVD drive does not support a specific read operation mode; some CD/DVD manufacturers don't implement this command for various reasons. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Hi Al, thanks for pointing me to safe mode install. That I will probably try tomorrow. The day ended up in havoc: I tried to boot a floppy to do an ASUS BIOS upgrade and somehow messed with the power cable. A big flash occurred originating from the power supply. I opened the power supply, found a blown fuse, ran to the electronics store, bought a new fuse (+ one in reserve), inserted the fuse, tried the power supply, with connections off and a firework, prematurely - your presidential elections aren't finished yet - , developed in front of my face. Will continue tomorrow, when America has a new president. -- Christoph Al Plant schrieb: Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 This makes the HD and CD to work for me after the install. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + < email: [EMAIL PROTECTED] > "All that's really worth doing is what we do for others."- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Julien Cigar wrote: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Aloha, I have had similiar happen on 7 and 8 Freebsd installs recently. If you install using safe mode it will work. Then in /boot/loader.conf #boot/loader.conf hw.ata.ata-dma=0 hw.ata.atapi_dma=0 This makes the HD and CD to work for me after the install. The error that comes up when you burn a CD seems to be bogus as I have used the CD's with out error for installing on other boxes. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + < email: [EMAIL PROTECTED] > "All that's really worth doing is what we do for others."- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Christoph Kukulies schrieb: Julien Cigar schrieb: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor What I've found is enable/disable IDE Master in the BIOS settings. I disabled it to no avail. Just bought a SATA CD/DVD burner hoping to get along with this. Pitfall - SATA CDROM drive is not seen by the BIOS so I cannot boot from it or is there a way to get around this? Any other method to boot from? This motherboard isn't one of the newest, in contrary, quite old. Doesn't seem to support boot from USB device, so I depend on getting the system booted from CDROM. -- Christoph Kukulies -- Christoph Kukulies (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Julien Cigar schrieb: I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor What I've found is enable/disable IDE Master in the BIOS settings. I disabled it to no avail. Just bought a SATA CD/DVD burner hoping to get along with this. -- Christoph Kukulies (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
I've this problem too on almost all my machines. The only solution I've found is to disable DMA (atapi_dma), but then performances are very poor (and I'm still unable to burn a CD/DVD) On Tue, 2008-11-04 at 16:03 +0100, Christoph Kukulies wrote: > Hi, > > don't know whether it's the CDROM drive (a Creative 52x mx) or the > motherboard (ASUS P4S8X) or what. > Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and > the installation > hangs right in the boot process of the installation CD disc1. > > I see > > acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 > run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config > > and so on. > > Any clues? > > -- > Christoph Kukulies > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Julien Cigar Belgian Biodiversity Platform http://www.biodiversity.be Université Libre de Bruxelles (ULB) Campus de la Plaine CP 257 Bâtiment NO, Bureau 4 N4 115C (Niveau 4) Boulevard du Triomphe, entrée ULB 2 B-1050 Bruxelles Mail: [EMAIL PROTECTED] @biobel: http://biobel.biodiversity.be/person/show/471 Tel : 02 650 57 52 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.1-BETA2 installation on ASUS P4S8X fails BIG MEDIUM ERROR
Hi, don't know whether it's the CDROM drive (a Creative 52x mx) or the motherboard (ASUS P4S8X) or what. Anyway, I tried to install a recent version of FreeBSD (7.1-BETA2) and the installation hangs right in the boot process of the installation CD disc1. I see acd0: FAILURE - READ BIG MEDIUM ERROR asc=0x11 ascq=0x00 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config and so on. Any clues? -- Christoph Kukulies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
