RE: Disappointed with version 6.0
Hmm, I've unplugged the PC every time I played with the cables (changing positions, etc) but never had it work. It's an older Compaq Deskpro EN. Maybe time for to update my hardware/PC with something more recent. Thanks -Original Message- From: Kent Stewart [mailto:kstew...@owt.com] Sent: Monday, May 18, 2009 10:44 AM To: freebsd-questions@freebsd.org Cc: David Roberts Subject: Re: Disappointed with version 6.0 On Monday 18 May 2009 09:56:07 am David Roberts wrote: > Hi, I was reading this thread as the problem I'm having seems quite > similar, and with version 7.2, although I had the same behavior with 6.3 as > well. > < > > ad0: 9541MB at ata0-master UDMA66 > > ad2: DMA limited to UDMA33, controller found non-ATA66 cable > > ad2: 76345MB at ata1-master UDMA33ad0: 9541MB > at ata0-master UDMA66 > > ad2: DMA limited to UDMA33, controller found non-ATA66 cable > > ad2: 76345MB at ata1-master UDMA33 > > > > Any ideas? > I had a motherboard that would do this. If I killed power to the system for ~15 seconds, it would go back to accepting everything. What I though was wrong was the controller developed a problem and if I cut the power to the system such that the system voltages bled off, it would go back to accepting ata66 cables. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Disappointed with version 6.0
On Monday 18 May 2009 09:56:07 am David Roberts wrote: > Hi, I was reading this thread as the problem I'm having seems quite > similar, and with version 7.2, although I had the same behavior with 6.3 as > well. > < > > ad0: 9541MB at ata0-master UDMA66 > > ad2: DMA limited to UDMA33, controller found non-ATA66 cable > > ad2: 76345MB at ata1-master UDMA33ad0: 9541MB > at ata0-master UDMA66 > > ad2: DMA limited to UDMA33, controller found non-ATA66 cable > > ad2: 76345MB at ata1-master UDMA33 > > > > Any ideas? > I had a motherboard that would do this. If I killed power to the system for ~15 seconds, it would go back to accepting everything. What I though was wrong was the controller developed a problem and if I cut the power to the system such that the system voltages bled off, it would go back to accepting ata66 cables. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Disappointed with version 6.0
-- Mike Jeays http://www.jeays.ca http://www.rotarycpmm.ca On May 18, 2009 12:56:07 pm David Roberts wrote: > Hi, I was reading this thread as the problem I'm having seems quite > similar, and with version 7.2, although I had the same behavior with 6.3 as > well. > > > > The only variation on the dialog below is I do not have any CDROM or other > device attached. My configuration is: > > primary IDE: 10GB Seagate > > seconardy IDE: 80GB Maxtor > > > > My dmesg is giving me > > ad0: 9541MB at ata0-master UDMA66 > > ad2: DMA limited to UDMA33, controller found non-ATA66 cable > > ad2: 76345MB at ata1-master UDMA33ad0: 9541MB > at ata0-master UDMA66 > > ad2: DMA limited to UDMA33, controller found non-ATA66 cable > > ad2: 76345MB at ata1-master UDMA33 > > > > Any ideas? > > On Friday 10 March 2006 22:57, Peter wrote: > > I'm setting up a new server on 6.0 I've been planning for a long time > > > > and I am very disappointed with two critical issues. My motherboard > > > > is the ASUS K8V-X SE that I chose because it was listed as compatible > > > > at the FreeBSD/amd64 Project: > > > > > > > > http://www.freebsd.org/platforms/amd64/motherboards.html > > > > > > > > I wonder if going back to 5.4 might help? > > > > > > > > Onto the problems... > > > > > > > > 1. I have 4 IDE drives: > > > > > > > > primary controller: Maxtor 40 GB hd (master) and LG cdrom (slave) > > > > secondary controller: Seagate Barracuda 200 GB hd (master) and > > > > Seagate Barracuda 300 GB (slave) > > > > > > > > Problem: The 300 GB drive is unusable. > > > > > > > > I set it up ok with sysinstall during the installation but the system > > > > will not boot properly if it has an entry in /etc/fstab. I get many > > > > errors like: > > > > > > > > "ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63" > > > > > > > > I also get input/output error if I try to examine its label with > > > > disklabel. > > > > > > > > dmesg output is at the end of this post when I booted without fstab > > > > line. > > > > > > > > The strange thing is that the two drives on the secondary controller > > > > are so similar. Same manufacturer, same product line, the speeds are > > > > the same. Everything is the same except the size. I ran dos-level > > > > diagnostics on it and no problems were found. > > > > > > > > 2. I can't use my USB ports! > > > > > > > > I get a line like this for each of my ports: > > > > > > > > uhci0: port 0xb800-0xb81f irq 21 at > > > > device 16.0 on pci0 > > > > uhci0: [GIANT-LOCKED] > > > > > > > > > > > > > > > > Copyright (c) 1992-2005 The FreeBSD Project. > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > > > > 1994 > > > > The Regents of the University of California. All rights reserved. > > > > FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 > > > > r...@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC > > > > ACPI APIC Table: > > > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > > > CPU: AMD Athlon(tm) 64 Processor 3000+ (2002.58-MHz 686-class CPU) > > > > Origin = "AuthenticAMD" Id = 0xf4a Stepping = 10 > > > > Features=0x78bfbffGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> AMD > > > > Features=0xe0500800 > > > > real memory = 536543232 (511 MB) > > > > avail memory = 515702784 (491 MB) > > < snip > > > > ad0: DMA limited to UDMA33, device found non-ATA66 cable > > > > ad0: 39205MB at ata0-master UDMA33 > > > > acd0: CDROM at ata0-slave PIO4 > > > > ad2: 190782MB at ata1-master UDMA100 > > > > ad3: 286168MB at ata1-slave UDMA100 > > > > Trying to mount root from ufs:/dev/ad0s1a > > > > > > > > __ > > You've got a problem alright, and you don't even see it. > > > > == > > The ata driver sets the maximum transfer mode supported by the hardware > > as default. However the ata driver sometimes warns: ``DMA limited to > > UDMA33, non-ATA66 cable or device''. This means that the ata driver > > has detected that the required 80 conductor cable is not present or > > could not be detected properly, or that one of the devices on the > > channel only accepts up to UDMA2/ATA33. > > == > > > > You've got your 40GB Maxtor (you've installed FreeBSD on it), an ATA100 > > device, connected with your CDROM, an ATA33 device. The result is: your > > boot drive is running at UDMA33 instead of UDMA100. This is not going > > to work real well, as you can see. > > > > Do you really need that 40GB Maxtor? If you do, you're going to have to > > try adding an ATA controller card into one of your PCI slots and use > > that to connect your hard drives to. > > > > Try removing the 40GB Maxtor and reinstalling FreeBSD on the other two > > drives. I think that will clear up some problems for you. > > > > Don > > > > > > > > > > > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listin
Re: Disappointed with version 6.0
Hi, I was reading this thread as the problem I'm having seems quite similar, and with version 7.2, although I had the same behavior with 6.3 as well. The only variation on the dialog below is I do not have any CDROM or other device attached. My configuration is: primary IDE: 10GB Seagate seconardy IDE: 80GB Maxtor My dmesg is giving me ad0: 9541MB at ata0-master UDMA66 ad2: DMA limited to UDMA33, controller found non-ATA66 cable ad2: 76345MB at ata1-master UDMA33ad0: 9541MB at ata0-master UDMA66 ad2: DMA limited to UDMA33, controller found non-ATA66 cable ad2: 76345MB at ata1-master UDMA33 Any ideas? On Friday 10 March 2006 22:57, Peter wrote: > I'm setting up a new server on 6.0 I've been planning for a long time > and I am very disappointed with two critical issues. My motherboard > is the ASUS K8V-X SE that I chose because it was listed as compatible > at the FreeBSD/amd64 Project: > > http://www.freebsd.org/platforms/amd64/motherboards.html > > I wonder if going back to 5.4 might help? > > Onto the problems... > > 1. I have 4 IDE drives: > > primary controller: Maxtor 40 GB hd (master) and LG cdrom (slave) > secondary controller: Seagate Barracuda 200 GB hd (master) and > Seagate Barracuda 300 GB (slave) > > Problem: The 300 GB drive is unusable. > > I set it up ok with sysinstall during the installation but the system > will not boot properly if it has an entry in /etc/fstab. I get many > errors like: > > "ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63" > > I also get input/output error if I try to examine its label with > disklabel. > > dmesg output is at the end of this post when I booted without fstab > line. > > The strange thing is that the two drives on the secondary controller > are so similar. Same manufacturer, same product line, the speeds are > the same. Everything is the same except the size. I ran dos-level > diagnostics on it and no problems were found. > > 2. I can't use my USB ports! > > I get a line like this for each of my ports: > > uhci0: port 0xb800-0xb81f irq 21 at > device 16.0 on pci0 > uhci0: [GIANT-LOCKED] > > > > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 > r...@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) 64 Processor 3000+ (2002.58-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0xf4a Stepping = 10 > Features=0x78bfbffGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> AMD > Features=0xe0500800 > real memory = 536543232 (511 MB) > avail memory = 515702784 (491 MB) < snip > > ad0: DMA limited to UDMA33, device found non-ATA66 cable > ad0: 39205MB at ata0-master UDMA33 > acd0: CDROM at ata0-slave PIO4 > ad2: 190782MB at ata1-master UDMA100 > ad3: 286168MB at ata1-slave UDMA100 > Trying to mount root from ufs:/dev/ad0s1a > > __ You've got a problem alright, and you don't even see it. == The ata driver sets the maximum transfer mode supported by the hardware as default. However the ata driver sometimes warns: ``DMA limited to UDMA33, non-ATA66 cable or device''. This means that the ata driver has detected that the required 80 conductor cable is not present or could not be detected properly, or that one of the devices on the channel only accepts up to UDMA2/ATA33. == You've got your 40GB Maxtor (you've installed FreeBSD on it), an ATA100 device, connected with your CDROM, an ATA33 device. The result is: your boot drive is running at UDMA33 instead of UDMA100. This is not going to work real well, as you can see. Do you really need that 40GB Maxtor? If you do, you're going to have to try adding an ATA controller card into one of your PCI slots and use that to connect your hard drives to. Try removing the 40GB Maxtor and reinstalling FreeBSD on the other two drives. I think that will clear up some problems for you. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Disappointed with version 6.0
Hi, I was reading this thread as the problem I'm having seems quite similar, and with version 7.2, although I had the same behavior with 6.3 as well. The only variation on the dialog below is I do not have any CDROM or other device attached. My configuration is: primary IDE: 10GB Seagate seconardy IDE: 80GB Maxtor My dmesg is giving me ad0: 9541MB at ata0-master UDMA66 ad2: DMA limited to UDMA33, controller found non-ATA66 cable ad2: 76345MB at ata1-master UDMA33ad0: 9541MB at ata0-master UDMA66 ad2: DMA limited to UDMA33, controller found non-ATA66 cable ad2: 76345MB at ata1-master UDMA33 Any ideas? On Friday 10 March 2006 22:57, Peter wrote: > I'm setting up a new server on 6.0 I've been planning for a long time > and I am very disappointed with two critical issues. My motherboard > is the ASUS K8V-X SE that I chose because it was listed as compatible > at the FreeBSD/amd64 Project: > > http://www.freebsd.org/platforms/amd64/motherboards.html > > I wonder if going back to 5.4 might help? > > Onto the problems... > > 1. I have 4 IDE drives: > > primary controller: Maxtor 40 GB hd (master) and LG cdrom (slave) > secondary controller: Seagate Barracuda 200 GB hd (master) and > Seagate Barracuda 300 GB (slave) > > Problem: The 300 GB drive is unusable. > > I set it up ok with sysinstall during the installation but the system > will not boot properly if it has an entry in /etc/fstab. I get many > errors like: > > "ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63" > > I also get input/output error if I try to examine its label with > disklabel. > > dmesg output is at the end of this post when I booted without fstab > line. > > The strange thing is that the two drives on the secondary controller > are so similar. Same manufacturer, same product line, the speeds are > the same. Everything is the same except the size. I ran dos-level > diagnostics on it and no problems were found. > > 2. I can't use my USB ports! > > I get a line like this for each of my ports: > > uhci0: port 0xb800-0xb81f irq 21 at > device 16.0 on pci0 > uhci0: [GIANT-LOCKED] > > > > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 > r...@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) 64 Processor 3000+ (2002.58-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0xf4a Stepping = 10 > Features=0x78bfbffGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> AMD > Features=0xe0500800 > real memory = 536543232 (511 MB) > avail memory = 515702784 (491 MB) < snip > > ad0: DMA limited to UDMA33, device found non-ATA66 cable > ad0: 39205MB at ata0-master UDMA33 > acd0: CDROM at ata0-slave PIO4 > ad2: 190782MB at ata1-master UDMA100 > ad3: 286168MB at ata1-slave UDMA100 > Trying to mount root from ufs:/dev/ad0s1a > > __ You've got a problem alright, and you don't even see it. == The ata driver sets the maximum transfer mode supported by the hardware as default. However the ata driver sometimes warns: ``DMA limited to UDMA33, non-ATA66 cable or device''. This means that the ata driver has detected that the required 80 conductor cable is not present or could not be detected properly, or that one of the devices on the channel only accepts up to UDMA2/ATA33. == You've got your 40GB Maxtor (you've installed FreeBSD on it), an ATA100 device, connected with your CDROM, an ATA33 device. The result is: your boot drive is running at UDMA33 instead of UDMA100. This is not going to work real well, as you can see. Do you really need that 40GB Maxtor? If you do, you're going to have to try adding an ATA controller card into one of your PCI slots and use that to connect your hard drives to. Try removing the 40GB Maxtor and reinstalling FreeBSD on the other two drives. I think that will clear up some problems for you. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Disappointed with version 6.0
>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Chris >Sent: Tuesday, March 14, 2006 11:00 PM >To: Ted Mittelstaedt >Cc: Peter; freebsd-questions >Subject: Re: Disappointed with version 6.0 > > >Sounds harsh, a low end board may have performance problems and less >capability but it shouldnt justify an operating system not working, or >are only high end boards supported? > You could ask Microsoft the same question. I've had Windows systems unstable due to crappy motherboards. Sometimes you just got to face it that crap is crap. With motherboards you simply don't know how they are going to work until you try them. I don't see why this is harsh though, the retailer simply returns the board to the manufacturer, who has to deal with problems that they caused. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Motherboards & FreeBSD [used to be "RE: Disappointed with version 6.0"]
>-Original Message- >From: Peter [mailto:[EMAIL PROTECTED] >Sent: Tuesday, March 14, 2006 5:53 PM >To: Ted Mittelstaedt; freebsd-questions >Subject: Motherboards & FreeBSD [used to be "RE: Disappointed with >version 6.0"] > > > >--- Ted Mittelstaedt <[EMAIL PROTECTED]> wrote: > >> >I'm setting up a new server on 6.0 I've been planning for a long >> time >> >and I am very disappointed with two critical issues. My motherboard >> is >> >the ASUS K8V-X SE that I chose because it was listed as compatible >> at >> >the FreeBSD/amd64 Project: >> > >> >http://www.freebsd.org/platforms/amd64/motherboards.html >> > >> >> Peter, >> >> That's really a poor choice as a server board. > >You get right to the point don't you? :| > I try, >> I don't know if you have a particular favorite of ASUS, but if your >> selecting a motherboard to build a server around from ASUS's product >> line you have to dig a bit. > >I don't mind digging a bit; I actually lean towards quality. And I'm >not partial towards any one maker either. My main issue is in >identifying boards that will have their components recognized by >FreeBSD. Is there a secret resource I haven't found? Please oblige. > It depends how far along the curve you want to be. Chipset manufacturers constantly change their products and new support is going into FreeBSD all the time, the problem is the newest boards probably won't be 100% supported. This is a separate issue from the reputation of the chipsets of course, SiS probably has the worst reputation, VIA is a bit better, Intel is better than that, etc. What you want to look for are chipsets that are built on older designs, for example the Intel ICH7 is a brushup of the ICH6 which is a brushup of the ICH5, etc. you get the idea. Thus it's really easy to add in support for it since the earlier variants are already supported. By contrast a brand new chipset line that has never seen FreeBSD before is going to take a lot longer to support. And of course, it's better to look for server quality hardware since more of that is going to be used for FreeBSD by the folks that are more advanced and will be supported faster. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
--- Alex Zbyslaw <[EMAIL PROTECTED]> wrote: > Peter wrote: > > >The values I'm getting fluctuate wildly. Sometimes with a > difference > >of 30 degrees after waiting just a couple of seconds. > > > > > That really doesn't sound good to me, but I don't really have enough > experience of system building to do more than guess at the cause. I > would strongly suspect the heatsink/processor bond but couldn't be > sure. I have no idea if the actually monitoring chip could be > faulty, > for example, or if it could be a BIOS problem (problems related to > bad > temperature readings certainly *can* exist but fluctuating temps is a > > bit different). I looked into the BIOS of my other system with different m/b and (better) heatsink and I get the same readings (~42). I use OCZ paste on both systems and followed their application instructions for the Athlon 64. Both heatsinks are just warm to the touch. I also see on the net that there are tons of people with similar "problems" so I am closing this file as "normal". Case closed (no pun intended). Thanks for your support. -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
Peter wrote: The values I'm getting fluctuate wildly. Sometimes with a difference of 30 degrees after waiting just a couple of seconds. That really doesn't sound good to me, but I don't really have enough experience of system building to do more than guess at the cause. I would strongly suspect the heatsink/processor bond but couldn't be sure. I have no idea if the actually monitoring chip could be faulty, for example, or if it could be a BIOS problem (problems related to bad temperature readings certainly *can* exist but fluctuating temps is a bit different). If no-one here can help, maybe try an overclockers forum - just because there tends to be a lot of system building experience there. Maybe ASUS support would help (but I wouldn't hold my breath). As I said, I went for arctic silver with my heatsink, but I got to apply it to clean components and it gets a bit harder if you have to clean the thermal paste off. They do a cleaner as well and had pretty good instructions on their website when I last looked. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
--- Alex Zbyslaw <[EMAIL PROTECTED]> wrote: > Peter wrote: > > >>You could check and see what sysutils/healthd reports. It doesn't > >>get all the volatges correct, but gets temps that, for me, reasonably match the > >> BIOS and seem believable. > >> > >Is it a science project or fairly simple? > Trivial. From memory but it should work: > > Install healthd: portupgrade -iNR sysutils/healthd (or just; cd > /usr/ports/sysutils/healthd; make install clean) > If (t)csh: rehash > Check temps etc: healthd -c 1 > First temp should be motherboard, second cpu (third is the 2nd CPU > which > you won't have an can ignore). The temps I get do agree with the > BIOS. The values I'm getting fluctuate wildly. Sometimes with a difference of 30 degrees after waiting just a couple of seconds. -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
Peter wrote: You could check and see what sysutils/healthd reports. It doesn't get all the volatges correct, but gets temps that, for me, reasonably match the BIOS and seem believable. Is it a science project or fairly simple? Trivial. From memory but it should work: Install healthd: portupgrade -iNR sysutils/healthd (or just; cd /usr/ports/sysutils/healthd; make install clean) If (t)csh: rehash Check temps etc: healthd -c 1 First temp should be motherboard, second cpu (third is the 2nd CPU which you won't have an can ignore). The temps I get do agree with the BIOS. I re-examined my heatsink and decided to redo the paste. I don't expect immediate results but I booted up and I see the temperature rise steadily from 30 to 43 in under a minute. That seems hot to me, but I believe it's well within the tolerance for the processor. AMD website would have that info. Maybe a google would reveal the kinds of temps people get for your specific processor. Mine's a 3700 with 120mm heatsink and arctic silver, so I don't think it could get much cooler. Even under load like buildworld, temp only rises a few degrees, which amazed me. If you haven't done a BIOS update, that might help your power-up issues. I have the latest BIOS installed. I actually don't have the latest BIOS but 1001, and power-up after power-fail appeared to work for me on a quick test last night. I don't have a UPS so all tests done by pulling the power lead and waiting a minute. BIOS: APM on, & the relevant setting to "Last State" and "Power On". I shutdown -p, pulled the power lead. Waited and then plugged back in. If set to Power On, machine came back on; if set to Last State, staid off. Then tried pulling power lead while BIOS was doing it's stuff. Power On, came back on and Last State also came back on. Maybe you need to check BIOS behaviour just using the power lead and not the UPS. *Maybe* it's the UPS somehow causing your problems, though I'm not sure how. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
Peter wrote: > No, I have a decent heatsink and a 120 mm chassis fan. I touch the heatsink and it is not even warm. This can actually indicate a problem - if the heatsink is not making proper contact with the cpu heat is not getting transferred = hot cpu and cool heatsink. Might be worth double checking that the heatsink is properly seated, eg there isn't dust or hair between, the heatsink isn't getting lodged up on something etc. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
--- Alex Zbyslaw <[EMAIL PROTECTED]> wrote: > Peter wrote: > > >Right now I am running the 40 GB and the 200 GB IDE drives as master > >and slave on the primary controller and the CDROM as master on the > >secondary. The USB and serial ports are working. I concluded that > the > >300 GB disk was bad so I am returning it. Currently I can say the > only > >problem I am experiencing is that the system will not come back up > >after a (simulated) power failure (I'm using a UPS) even though I > tell > >it to do so in the BIOS. Another point is that while in the BIOS > the > >CPU temperature shows around 45 C which does not seem possible. > > > > > [I think I got some attributions wrong in my original reply. > Apologies]. > > 45 is awfully hot. My norm is ~25 never even getting to 30, but I > have > a monster heatsink with a slow/quietish 120mm fan. However, even an > amd64 4000 with stock heatsink/fan doesn't get much above 40 for me > at > normal room temperatures. > > There are only three possibilities 1) the BIOS is lying - quite > possible and an update may fix that I have the latest BIOS installed. > 2) the cooling in your case sucks (or doesn't suck enough :-)) No, I have a decent heatsink and a 120 mm chassis fan. I touch the heatsink and it is not even warm. > 3) the heatsink isn't making that good thermal > contact, but that's painful to fix compared to 1 or 2. I re-examined my heatsink and decided to redo the paste. I don't expect immediate results but I booted up and I see the temperature rise steadily from 30 to 43 in under a minute. > You could check and see what sysutils/healthd reports. It doesn't get all the > volatges correct, but gets temps that, for me, reasonably match the BIOS and > seem believable. Is it a science project or fairly simple? > (mbmon doesn't, for me, recognise the monitoring chip on > this board). If you haven't done a BIOS update, that might help your > power-up issues. I have the latest BIOS installed. -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
Peter wrote: Right now I am running the 40 GB and the 200 GB IDE drives as master and slave on the primary controller and the CDROM as master on the secondary. The USB and serial ports are working. I concluded that the 300 GB disk was bad so I am returning it. Currently I can say the only problem I am experiencing is that the system will not come back up after a (simulated) power failure (I'm using a UPS) even though I tell it to do so in the BIOS. Another point is that while in the BIOS the CPU temperature shows around 45 C which does not seem possible. [I think I got some attributions wrong in my original reply. Apologies]. 45 is awfully hot. My norm is ~25 never even getting to 30, but I have a monster heatsink with a slow/quietish 120mm fan. However, even an amd64 4000 with stock heatsink/fan doesn't get much above 40 for me at normal room temperatures. There are only three possibilities 1) the BIOS is lying - quite possible and an update may fix that 2) the cooling in your case sucks (or doesn't suck enough :-)) 3) the heatsink isn't making that good thermal contact, but that's painful to fix compared to 1 or 2. You could check and see what sysutils/healthd reports. It doesn't get all the volatges correct, but gets temps that, for me, reasonably match the BIOS and seem believable. (mbmon doesn't, for me, recognise the monitoring chip on this board). If you haven't done a BIOS update, that might help your power-up issues. Have you looked at the ASUS support site? It may not have anything useful, but again, you have to try. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
--- Alex Zbyslaw <[EMAIL PROTECTED]> wrote: > Chris wrote: > > >[K8V-X SE] > >Sounds harsh, a low end board may have performance problems and less > >capability but it shouldnt justify an operating system not working, > or > >are only high end boards supported? > > > > > I have this board, and it works for what I do with it (single SATA > 200Gb > disk + built-in ethernet - under 5.4 i386). > > Having said that, this board is a low-end piece of crud and I > wouldn't > recommend it to anyone. I intended to get the non-X version (because > it > was cheap with Gigabit ether, but got bilked by the supplier and > didn't > realise until I'd built the damn thing). I've never used USB, or > stuck > multiple disks in it, so I have no idea if I would have the same > problems as you; sorry. > > If you want a better board without going all expensive-server, then > my > ASUS A8V deluxe (socket 939) has worked fine, though I've only used > USB > under windows. > > Should cheap boards work? Yes they should, and by and large they do. > > But a specific model of cheap board can easily have specific problems > > and there is no way for a project like FreeBSD to test every board on > > the market - they change too fast and there are just too many of 'em. > > FWIW, there are cheap boards which run really crap under Windows, as > well. > > My motherboard is > > >the ASUS K8V-X SE that I chose because it was listed as compatible > at > > >the FreeBSD/amd64 Project: > > > > > >http://www.freebsd.org/platforms/amd64/motherboards.html > > Are you running the amd64 version of FreeBSD? If so, try the i386 > version and see if that solves your problems. You also have to take > such compatibility information with a small pinch of salt. > Undoubtedly someone has reported that this motherboard booted amd64 > version of FreeBSD just fine, but they might not have pushed every > aspect of the board. > > I haven't followed this thread that closely, but IIUC, in your shoes > I would try the system with *just* the problem disk as a master (and > the CD) and see if you can do anything with it. (I think Ted > suggested that already). Also, since you seem to have gone for PATA > - check your cable or try a different one - probably won't help but > you have to try. > > If you are getting to the point where the disk is recognised by > FreeBSD then see what sysutils/smartmontools says about it. Just in > case. Right now I am running the 40 GB and the 200 GB IDE drives as master and slave on the primary controller and the CDROM as master on the secondary. The USB and serial ports are working. I concluded that the 300 GB disk was bad so I am returning it. Currently I can say the only problem I am experiencing is that the system will not come back up after a (simulated) power failure (I'm using a UPS) even though I tell it to do so in the BIOS. Another point is that while in the BIOS the CPU temperature shows around 45 C which does not seem possible. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
Chris wrote: [K8V-X SE] Sounds harsh, a low end board may have performance problems and less capability but it shouldnt justify an operating system not working, or are only high end boards supported? I have this board, and it works for what I do with it (single SATA 200Gb disk + built-in ethernet - under 5.4 i386). Having said that, this board is a low-end piece of crud and I wouldn't recommend it to anyone. I intended to get the non-X version (because it was cheap with Gigabit ether, but got bilked by the supplier and didn't realise until I'd built the damn thing). I've never used USB, or stuck multiple disks in it, so I have no idea if I would have the same problems as you; sorry. If you want a better board without going all expensive-server, then my ASUS A8V deluxe (socket 939) has worked fine, though I've only used USB under windows. Should cheap boards work? Yes they should, and by and large they do. But a specific model of cheap board can easily have specific problems and there is no way for a project like FreeBSD to test every board on the market - they change too fast and there are just too many of 'em. FWIW, there are cheap boards which run really crap under Windows, as well. My motherboard is >the ASUS K8V-X SE that I chose because it was listed as compatible at >the FreeBSD/amd64 Project: > >http://www.freebsd.org/platforms/amd64/motherboards.html Are you running the amd64 version of FreeBSD? If so, try the i386 version and see if that solves your problems. You also have to take such compatibility information with a small pinch of salt. Undoubtedly someone has reported that this motherboard booted amd64 version of FreeBSD just fine, but they might not have pushed every aspect of the board. I haven't followed this thread that closely, but IIUC, in your shoes I would try the system with *just* the problem disk as a master (and the CD) and see if you can do anything with it. (I think Ted suggested that already). Also, since you seem to have gone for PATA - check your cable or try a different one - probably won't help but you have to try. If you are getting to the point where the disk is recognised by FreeBSD then see what sysutils/smartmontools says about it. Just in case. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
On Tuesday 14 March 2006 22:00, Chris wrote: > On 14/03/06, Ted Mittelstaedt <[EMAIL PROTECTED]> wrote: > > >-Original Message- > > >From: [EMAIL PROTECTED] > > >[mailto:[EMAIL PROTECTED] Behalf Of Peter > > >Sent: Friday, March 10, 2006 8:58 PM > > >To: freebsd-questions > > >Subject: Disappointed with version 6.0 > > > > > > > > >I'm setting up a new server on 6.0 I've been planning for a long time > > >and I am very disappointed with two critical issues. My motherboard is > > >the ASUS K8V-X SE that I chose because it was listed as compatible at > > >the FreeBSD/amd64 Project: > > > > > >http://www.freebsd.org/platforms/amd64/motherboards.html > > > > Peter, > > > > That's really a poor choice as a server board. That is basically > > a low-end desktop board. VIA isn't known for making top of the > > line chipsets. > > > > I don't know if you have a particular favorite of ASUS, but if your > > selecting a motherboard to build a server around from ASUS's product > > line you have to dig a bit. ASUS has some server motherboards but > > they bury them in their product linueup. Some of the keys to look for > > are the existence of RAID on the motherboard, or the name "Premium" > > and stay away from any board marketed "for gamers" as a lot of ASUS > > boards are. > > > > For example, a typical ASUS motherboard positioned for the server > > market is the P5WD2-E Premium > > > > >I wonder if going back to 5.4 might help? > > > > > >Onto the problems... > > > > > >1. I have 4 IDE drives: > > > > > >primary controller: Maxtor 40 GB hd (master) and LG cdrom (slave) > > >secondary controller: Seagate Barracuda 200 GB hd (master) and Seagate > > >Barracuda 300 GB (slave) > > > > > >Problem: The 300 GB drive is unusable. > > > > > >I set it up ok with sysinstall during the installation but the system > > >will not boot properly if it has an entry in /etc/fstab. I get many > > >errors like: > > > > > >"ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63" > > > > What happens if you set the 300GB as the master on that controller > > and do not plug in the 200GB unit? > > > > >I also get input/output error if I try to examine its label with > > >disklabel. > > > > > >dmesg output is at the end of this post when I booted without fstab > > >line. > > > > > >The strange thing is that the two drives on the secondary controller > > >are so similar. Same manufacturer, same product line, the speeds are > > >the same. Everything is the same except the size. I ran dos-level > > >diagnostics on it and no problems were found. > > > > > >2. I can't use my USB ports! > > > > What in God's name is a USB peripheral doing on a server? > > > > I've said it before and I'll say it again, this is why you pay people > > to build clones for you. The motherboard manufacturers these days are > > coming out with a huge variety of products, and you have to do a lot of > > digging through their stuff to find the gems among the junk. > > > > The professional white box builders out there deal with problems like > > yours by returning the motherboard to their distributors and getting > > a different model, and testing that. Sometimes they will go through > > 4 -5 motherboard models before they find one they feel is a good one. > > Then 6 months later the motherboard manufacturers discontinue that model > > and they have to go through the same process again. If you want to play > > in that space you need to do it the same way they do. If you don't have > > the financial resources to do that, then you shouldn't be doing it. > > Instead, find a local computer shop that you can pay a few hundred > > bucks more than it would cost you to get all the little parts and pieces > > separately, and who will warranty the thing. It is well worth it. > > > > >I get a line like this for each of my ports: > > > > You are wasting time. Return the motherboard and get another. Repeat > > the process until it works. > > > > Ted > > Sounds harsh, a low end board may have performance problems and less > capability but it shouldnt justify an operating system not working, or >
Re: Disappointed with version 6.0
On 14/03/06, Ted Mittelstaedt <[EMAIL PROTECTED]> wrote: > > > >-Original Message- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] Behalf Of Peter > >Sent: Friday, March 10, 2006 8:58 PM > >To: freebsd-questions > >Subject: Disappointed with version 6.0 > > > > > >I'm setting up a new server on 6.0 I've been planning for a long time > >and I am very disappointed with two critical issues. My motherboard is > >the ASUS K8V-X SE that I chose because it was listed as compatible at > >the FreeBSD/amd64 Project: > > > >http://www.freebsd.org/platforms/amd64/motherboards.html > > > > Peter, > > That's really a poor choice as a server board. That is basically > a low-end desktop board. VIA isn't known for making top of the > line chipsets. > > I don't know if you have a particular favorite of ASUS, but if your > selecting a motherboard to build a server around from ASUS's product > line you have to dig a bit. ASUS has some server motherboards but > they bury them in their product linueup. Some of the keys to look for > are the existence of RAID on the motherboard, or the name "Premium" > and stay away from any board marketed "for gamers" as a lot of ASUS > boards are. > > For example, a typical ASUS motherboard positioned for the server > market is the P5WD2-E Premium > > >I wonder if going back to 5.4 might help? > > > >Onto the problems... > > > >1. I have 4 IDE drives: > > > >primary controller: Maxtor 40 GB hd (master) and LG cdrom (slave) > >secondary controller: Seagate Barracuda 200 GB hd (master) and Seagate > >Barracuda 300 GB (slave) > > > >Problem: The 300 GB drive is unusable. > > > >I set it up ok with sysinstall during the installation but the system > >will not boot properly if it has an entry in /etc/fstab. I get many > >errors like: > > > >"ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63" > > > > What happens if you set the 300GB as the master on that controller > and do not plug in the 200GB unit? > > >I also get input/output error if I try to examine its label with > >disklabel. > > > >dmesg output is at the end of this post when I booted without fstab > >line. > > > >The strange thing is that the two drives on the secondary controller > >are so similar. Same manufacturer, same product line, the speeds are > >the same. Everything is the same except the size. I ran dos-level > >diagnostics on it and no problems were found. > > > >2. I can't use my USB ports! > > > > What in God's name is a USB peripheral doing on a server? > > I've said it before and I'll say it again, this is why you pay people > to build clones for you. The motherboard manufacturers these days are > coming out with a huge variety of products, and you have to do a lot of > digging through their stuff to find the gems among the junk. > > The professional white box builders out there deal with problems like > yours by returning the motherboard to their distributors and getting > a different model, and testing that. Sometimes they will go through > 4 -5 motherboard models before they find one they feel is a good one. > Then 6 months later the motherboard manufacturers discontinue that model > and they have to go through the same process again. If you want to play > in that space you need to do it the same way they do. If you don't have > the financial resources to do that, then you shouldn't be doing it. > Instead, find a local computer shop that you can pay a few hundred > bucks more than it would cost you to get all the little parts and pieces > separately, and who will warranty the thing. It is well worth it. > > >I get a line like this for each of my ports: > > > > You are wasting time. Return the motherboard and get another. Repeat > the process until it works. > > Ted Sounds harsh, a low end board may have performance problems and less capability but it shouldnt justify an operating system not working, or are only high end boards supported? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Motherboards & FreeBSD [used to be "RE: Disappointed with version 6.0"]
On Tue, 14 Mar 2006 20:53:00 -0500 (EST) Peter <[EMAIL PROTECTED]> wrote: > Is there a secret resource I haven't found? [EMAIL PROTECTED] + its archives FWIW, we have a TYAN dual opteron box, 4 x SATA drives, 1 RU, works a treat. I think it's the something-24 model. search the archives for more info. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Motherboards & FreeBSD [used to be "RE: Disappointed with version 6.0"]
--- Ted Mittelstaedt <[EMAIL PROTECTED]> wrote: > >I'm setting up a new server on 6.0 I've been planning for a long > time > >and I am very disappointed with two critical issues. My motherboard > is > >the ASUS K8V-X SE that I chose because it was listed as compatible > at > >the FreeBSD/amd64 Project: > > > >http://www.freebsd.org/platforms/amd64/motherboards.html > > > > Peter, > > That's really a poor choice as a server board. You get right to the point don't you? :| > I don't know if you have a particular favorite of ASUS, but if your > selecting a motherboard to build a server around from ASUS's product > line you have to dig a bit. I don't mind digging a bit; I actually lean towards quality. And I'm not partial towards any one maker either. My main issue is in identifying boards that will have their components recognized by FreeBSD. Is there a secret resource I haven't found? Please oblige. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Disappointed with version 6.0
>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Peter >Sent: Friday, March 10, 2006 8:58 PM >To: freebsd-questions >Subject: Disappointed with version 6.0 > > >I'm setting up a new server on 6.0 I've been planning for a long time >and I am very disappointed with two critical issues. My motherboard is >the ASUS K8V-X SE that I chose because it was listed as compatible at >the FreeBSD/amd64 Project: > >http://www.freebsd.org/platforms/amd64/motherboards.html > Peter, That's really a poor choice as a server board. That is basically a low-end desktop board. VIA isn't known for making top of the line chipsets. I don't know if you have a particular favorite of ASUS, but if your selecting a motherboard to build a server around from ASUS's product line you have to dig a bit. ASUS has some server motherboards but they bury them in their product linueup. Some of the keys to look for are the existence of RAID on the motherboard, or the name "Premium" and stay away from any board marketed "for gamers" as a lot of ASUS boards are. For example, a typical ASUS motherboard positioned for the server market is the P5WD2-E Premium >I wonder if going back to 5.4 might help? > >Onto the problems... > >1. I have 4 IDE drives: > >primary controller: Maxtor 40 GB hd (master) and LG cdrom (slave) >secondary controller: Seagate Barracuda 200 GB hd (master) and Seagate >Barracuda 300 GB (slave) > >Problem: The 300 GB drive is unusable. > >I set it up ok with sysinstall during the installation but the system >will not boot properly if it has an entry in /etc/fstab. I get many >errors like: > >"ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63" > What happens if you set the 300GB as the master on that controller and do not plug in the 200GB unit? >I also get input/output error if I try to examine its label with >disklabel. > >dmesg output is at the end of this post when I booted without fstab >line. > >The strange thing is that the two drives on the secondary controller >are so similar. Same manufacturer, same product line, the speeds are >the same. Everything is the same except the size. I ran dos-level >diagnostics on it and no problems were found. > >2. I can't use my USB ports! > What in God's name is a USB peripheral doing on a server? I've said it before and I'll say it again, this is why you pay people to build clones for you. The motherboard manufacturers these days are coming out with a huge variety of products, and you have to do a lot of digging through their stuff to find the gems among the junk. The professional white box builders out there deal with problems like yours by returning the motherboard to their distributors and getting a different model, and testing that. Sometimes they will go through 4 -5 motherboard models before they find one they feel is a good one. Then 6 months later the motherboard manufacturers discontinue that model and they have to go through the same process again. If you want to play in that space you need to do it the same way they do. If you don't have the financial resources to do that, then you shouldn't be doing it. Instead, find a local computer shop that you can pay a few hundred bucks more than it would cost you to get all the little parts and pieces separately, and who will warranty the thing. It is well worth it. >I get a line like this for each of my ports: > You are wasting time. Return the motherboard and get another. Repeat the process until it works. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "cg 0: bad magic number" (used to be Disappointed with version 6.0)
On Saturday 11 March 2006 23:51, Peter wrote: > > Are you doing this through sysinstall or are you manually running > > fdisk > > and bsdlabel. > > Through sysinstall. Both disklabel and fdisk don't work. The former > gives "input/output error" and output to the latter I gave in my last > post. > > > > > Is this a brand new disk? Has it ever been used before? Is it still > > under warrantee? If it is, take it back and get it replaced. > > Yeah, I'm leaning that way too. > > > Hey, I just saw it. You made Google search. > > Huh? Yeah. Do a google search for Seagate ST3300831A, then search within for problems and there it is, at the bottom of the first page: Google Group results for Seagate ST3300831A problem Disappointed in version 6.0 - list.freebsd.questions - March 11, 2006 Seagate hard drive warranty - comp.sys.ibm.pc.hardware.stora ... If you search for petermatulis, there are about 263 hits. It appears at one time you were doing OpenBSD. Just a piece of trivia. I can be found also. > > > It looks to me like things just went through the motions and not > > the actuality of installing ufs on the drive. That's happened to me > > a couple of times and from what I remember, I had to start the > > install over from the beginning - and I seem to recall something > > about having > > > > to install windows first and reformatting all the hard-drives with > > NTFS, then I could go back in and install FreeBSD. Otherwise, I > > couldn't get FreeBSD to install, it just went through the motions, > > wiping out whatever was on the hard-drives but not putting in > > FreeBSD. > > Without a CDROM, it's going to be a little bit rough to do. > > I don't understand why you mention Windows. Surely I don't require > Windows to get this drive to work. As for the cdrom, I can always > put it back to do an install. It doesn't cause trouble -just slows > down the boot drive. > I had a hard drive one time that I just couldn't get FreeBSD to format, no matter what I did. I finally gave up and put WindowsXP on it, which was somewhat of struggle too. After that, since what I wanted was FreeBSD, I retried installing it, it worked this time, I don't know why but it did. I can only think that there was something wrong with the original installation of FreeBSD and I wasn't experienced enough, at that time to figure out what it was, other than it wasn't working right. If I'm remembering correctly, a while later the drive would operate intermittently and I put it in the basement. > -- > Peter > Hi Peter, Since you can play around a bit. Try reconnecting the CDROM and just the 300GB Seagate on the other ata channel. Then see if FreeBSD will successfully install on the drive. How much time do you have to work with this problem? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "cg 0: bad magic number" (used to be Disappointed with version 6.0)
On Saturday 11 March 2006 21:08, you wrote: > Hi Donald. It's me again. I sent this to the list and saw I didn't > include you. > I haven't seen the one on the list yet, this one got here first. > . > > Ok, I have narrowed down my problem a great deal. It appears that > FreeBSD cannot read the partition table of my 300 GB Seagate > Barracuda. My dos diagnostic utility works because it accesses the > disk in a different way. > > I used the entire disk (one slice/partition) and attempted to format > it. This is what I get after it reaches the end of the disk: > > "cg 0: bad magic number" > > It also slows down significantly about 3/4 through the procedure. > Are you doing this through sysinstall or are you manually running fdisk and bsdlabel. Well, maybe with a disk that big , it was getting tired and wanted to rest up before giving you the bad news. > Now the funny part. I create two partitions and the newfs output is > exactly the same as before when I try to format the first partition! > It tries to format as if there is only one partition and produces the > same error. > > If I remove the slice via sysinstall and then try fdisk I get this: > > # fdisk -vBI ad3 > *** Working on device /dev/ad3 *** > parameters extracted from in-core disklabel are: > cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl) > > Information from DOS bootblock is: > 1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 63, size 586072305 (286168 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 812/ head 15/ sector 63 > 2: > 3: > 4: > fdisk: Geom not found > > Anyone? > > -- > Peter > > __ Peter, Is this a brand new disk? Has it ever been used before? Is it still under warrantee? If it is, take it back and get it replaced. Hey, I just saw it. You made Google search. It looks to me like things just went through the motions and not the actuality of installing ufs on the drive. That's happened to me a couple of times and from what I remember, I had to start the install over from the beginning - and I seem to recall something about having to install windows first and reformatting all the hard-drives with NTFS, then I could go back in and install FreeBSD. Otherwise, I couldn't get FreeBSD to install, it just went through the motions, wiping out whatever was on the hard-drives but not putting in FreeBSD. Without a CDROM, it's going to be a little bit rough to do. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "cg 0: bad magic number" (used to be Disappointed with version 6.0)
--- "Donald J. O'Neill" <[EMAIL PROTECTED]> wrote: > > Ok, I have narrowed down my problem a great deal. It appears that > > FreeBSD cannot read the partition table of my 300 GB Seagate > > Barracuda. My dos diagnostic utility works because it accesses the > > disk in a different way. > > > > I used the entire disk (one slice/partition) and attempted to > format > > it. This is what I get after it reaches the end of the disk: > > > > "cg 0: bad magic number" > > > > It also slows down significantly about 3/4 through the procedure. > > > > Are you doing this through sysinstall or are you manually running > fdisk > and bsdlabel. > Through sysinstall. Both disklabel and fdisk don't work. The former gives "input/output error" and output to the latter I gave in my last post. > > Now the funny part. I create two partitions and the newfs output > is > > exactly the same as before when I try to format the first > partition! > > It tries to format as if there is only one partition and produces > the > > same error. > > > > If I remove the slice via sysinstall and then try fdisk I get this: > > > > # fdisk -vBI ad3 > > *** Working on device /dev/ad3 *** > > parameters extracted from in-core disklabel are: > > cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl) > > > > Figures below won't work with BIOS for partitions not in cyl 1 > > parameters to be used for BIOS calculations are: > > cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl) > > > > Information from DOS bootblock is: > > 1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > start 63, size 586072305 (286168 Meg), flag 80 (active) > > beg: cyl 0/ head 1/ sector 1; > > end: cyl 812/ head 15/ sector 63 > > 2: > > 3: > > 4: > > fdisk: Geom not found > Is this a brand new disk? Has it ever been used before? Is it still > under warrantee? If it is, take it back and get it replaced. Yeah, I'm leaning that way too. > Hey, I just saw it. You made Google search. Huh? > It looks to me like things just went through the motions and not the > actuality of installing ufs on the drive. That's happened to me a > couple of times and from what I remember, I had to start the install > over from the beginning - and I seem to recall something about having > > to install windows first and reformatting all the hard-drives with > NTFS, then I could go back in and install FreeBSD. Otherwise, I > couldn't get FreeBSD to install, it just went through the motions, > wiping out whatever was on the hard-drives but not putting in > FreeBSD. > Without a CDROM, it's going to be a little bit rough to do. I don't understand why you mention Windows. Surely I don't require Windows to get this drive to work. As for the cdrom, I can always put it back to do an install. It doesn't cause trouble -just slows down the boot drive. -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
On Saturday 11 March 2006 20:03, Peter wrote: > > OK, does dmesg still give this with the cdrom removed: > > > > ad0: DMA limited to UDMA33, device found non-ATA66 cable > > ad0: 39205MB at ata0-master UDMA33 > > acd0: CDROM at ata0-slave PIO4 > > ad2: 190782MB at ata1-master UDMA100 > > ad3: 286168MB at ata1-slave UDMA100 > > Trying to mount root from ufs:/dev/ad0s1a > > > > If the message for ad0 has changed, and it is now detected as an > > ata100 > > device and is running at UDMA100, you've solved part of your > > problem. > > dmesg now says: > > ad0: 39205MB at ata0-master UDMA133 > ad2: 190782MB at ata1-master UDMA100 > ad3: 286168MB at ata1-slave UDMA100 > > So ad0's speed has increased by 100 MB/s? > I was guessing that it was an ata100, it seems to be an ata133 instead. Now you can see what the difference is when connecting a hard-drive with a cdrom. > > Your system will access the boot drive at a higher speed. > > > > ad3 is still detected but you can't access it. So, I have to ask: > > when > > you set up the system, did you install a ufs system on it? Did you > > carve it up using bsdlabel? Or, did you leave it alone because you > > plane on using it for something else? This would be a reason for > > why it > > shows up on dmesg, but you can't access it. > > Yes, per install defaults ufs (and most probably soft updates) was > used. Everything was done via the default sysinstall procedure. I > said to use "entire drive" and then made one partition. It creates > /dev/ad3s1d. > > I just entered sysinstall again to start fresh and during the format > portion "Doing newfs" I hear some sounds I've never heard before on a > hard drive. Like a mechanical arm is trying to move but it keeps > bouncing back. Then I get: > > "Error mounting /dev/ad3s1d on /images : Input/output error" > > But if there was something mechanically wrong then my dos-level > diagnostics would of picked it up (I had an disk excercise tool > running on it for 20 minutes without any problems). > No, Microsloth makes things run (or appear to run) by hiding a lot of information from you. When did you run the dos-level diagnostics on the disk, before or after you installed FreeBSD? I ask because if it was after, well, dos-level disk diagnostics can't access a ufs formated disk without doing nasty things to what's on it. If was before, you should have run spinrite 6.0 on it, but that's going to run for about , oh say, at a wild guess, on a drive that size, 2 or 3 days. Your twenty minute run on that drive wouldn't really tell you much unless the drive was drastically failing. > > Now, you need to do something about the cdrom. It's kind of unhandy > > to > > be without one. That's why I asked if you really needed the 40GB > > Maxtor > > and if you did, suggested you get an ata controller card, then you > > could use all three drives. And I also asked if you could just > > remove > > > > that drive and use the two Seagates. > > I need all three drives: > > 1. system drive (40 GB) > 2. client data backups (200 GB) > 3. client data images (300 GB) > > The #3 drive (the problematic one) will actually be removed offsite > once the (client hard drive) images have been stored. And this is > where I might be able to weasel out of my current predicament. I can > put back the cdrom afterwards. > > > I guess there's one other question: how did you get from 5.4 to > > 6.0, and is it 6.0 or is it 6 STABLE? > > No, no. This is a brand new install of 6.0 (I can therefore mess > around with impunity). When I mentioned "go back to 5.4" I did not > mean to imply I upgraded. > Just don't cable back with the cdrom. > -- > Peter > Now, what about your usb? a message like: uhci0: port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] Nothing wrong with that message. Base on that message, you don't have a problem. It's when you see messages like irq storm on throttling source, or device returns some error message, or can't assign an irq, then you know you've got a problem that's going to require some swapping around on the pci bus. As a matter of fact, I was having usb problems until I went 6-RELEASE to 6-STABLE. Which at that time I was able to determine that it wasn't actually a usb problem, I was having a problem with a modem and bad usb mouse. I pulled the modem and was going to throw it away, put it away instead, until I had a need for one at which point I found out that it's position on the pci bus made the difference in whether it would play nicely with the cards or not. The mouse did get tossed, it would work intermittently under windows and FreeBSD would only get to a certain load point and then reboot. Actually, finding it was a little more difficult than I've said. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"cg 0: bad magic number" [used to be "Disappointed with version 6.0]
Ok, I have narrowed down my problem a great deal. It appears that FreeBSD cannot read the partition table of my 300 GB Seagate Barracuda. My dos diagnostic utility works because it accesses the disk in a different way. I used the entire disk (one slice/partition) and attempted to format it. This is what I get after it reaches the end of the disk: "cg 0: bad magic number" It also slows down significantly about 3/4 through the procedure. Now the funny part. I create two partitions and the newfs output is exactly the same as before when I try to format the first partition! It tries to format as if there is only one partition and produces the same error. If I remove the slice via sysinstall and then try fdisk I get this: # fdisk -vBI ad3 *** Working on device /dev/ad3 *** parameters extracted from in-core disklabel are: cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl) Information from DOS bootblock is: 1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 586072305 (286168 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 812/ head 15/ sector 63 2: 3: 4: fdisk: Geom not found Anyone? -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
--- "Donald J. O'Neill" <[EMAIL PROTECTED]> wrote: > On Saturday 11 March 2006 18:48, Peter wrote: > > > > You can answer me tomorrow if you like but here is an update: > > > > I removed the cdrom and the problem remains. I got the usb ports > to > > work as well by updating the bios and fiddling with some settings. > > It is truly a mystery why this 300 GB drive cannot talk to FreeBSD. > > Again, it is detected fine by the bios; it passes dos level > > diagnostics; it is on the same ide cable (as slave) as the 200 GB > > drive that is identical to it save for an extra 100 GB. My next > step > > is to boot with knoppix to see how it behaves. > > > > -- > > Peter > > > Hi Peter, > > I've recovered sufficiently enough that I can type without spending > all > my time correcting spelling errors that a spelling checker can't fix. > > OK, does dmesg still give this with the cdrom removed: > > ad0: DMA limited to UDMA33, device found non-ATA66 cable > ad0: 39205MB at ata0-master UDMA33 > acd0: CDROM at ata0-slave PIO4 > ad2: 190782MB at ata1-master UDMA100 > ad3: 286168MB at ata1-slave UDMA100 > Trying to mount root from ufs:/dev/ad0s1a > > If the message for ad0 has changed, and it is now detected as an > ata100 > device and is running at UDMA100, you've solved part of your problem. dmesg now says: ad0: 39205MB at ata0-master UDMA133 ad2: 190782MB at ata1-master UDMA100 ad3: 286168MB at ata1-slave UDMA100 So ad0's speed has increased by 100 MB/s? > Your system will access the boot drive at a higher speed. > > ad3 is still detected but you can't access it. So, I have to ask: > when > you set up the system, did you install a ufs system on it? Did you > carve it up using bsdlabel? Or, did you leave it alone because you > plane on using it for something else? This would be a reason for why > it > shows up on dmesg, but you can't access it. Yes, per install defaults ufs (and most probably soft updates) was used. Everything was done via the default sysinstall procedure. I said to use "entire drive" and then made one partition. It creates /dev/ad3s1d. I just entered sysinstall again to start fresh and during the format portion "Doing newfs" I hear some sounds I've never heard before on a hard drive. Like a mechanical arm is trying to move but it keeps bouncing back. Then I get: "Error mounting /dev/ad3s1d on /images : Input/output error" But if there was something mechanically wrong then my dos-level diagnostics would of picked it up (I had an disk excercise tool running on it for 20 minutes without any problems). > Now, you need to do something about the cdrom. It's kind of unhandy > to > be without one. That's why I asked if you really needed the 40GB > Maxtor > and if you did, suggested you get an ata controller card, then you > could use all three drives. And I also asked if you could just remove > that drive and use the two Seagates. I need all three drives: 1. system drive (40 GB) 2. client data backups (200 GB) 3. client data images (300 GB) The #3 drive (the problematic one) will actually be removed offsite once the (client hard drive) images have been stored. And this is where I might be able to weasel out of my current predicament. I can put back the cdrom afterwards. > I guess there's one other question: how did you get from 5.4 to 6.0, > and is it 6.0 or is it 6 STABLE? No, no. This is a brand new install of 6.0 (I can therefore mess around with impunity). When I mentioned "go back to 5.4" I did not mean to imply I upgraded. -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
--- "Donald J. O'Neill" <[EMAIL PROTECTED]> wrote: > On Saturday 11 March 2006 13:38, Peter wrote: > > --- "Donald J. O'Neill" <[EMAIL PROTECTED]> wrote: > > > > [...] > > > > > > ad0: DMA limited to UDMA33, device found non-ATA66 cable > > > > ad0: 39205MB at ata0-master UDMA33 > > > > acd0: CDROM at ata0-slave PIO4 > > > > ad2: 190782MB at ata1-master UDMA100 > > > > ad3: 286168MB at ata1-slave UDMA100 > > > > Trying to mount root from ufs:/dev/ad0s1a > > > > > > > > __ > > > > > > You've got a problem alright, and you don't even see it. > > > > > > == > > > The ata driver sets the maximum transfer mode supported by the > > > hardware > > > as default. However the ata driver sometimes warns: ``DMA > limited > > > to > > > > > > UDMA33, non-ATA66 cable or device''. This means that the ata > > > driver has detected that the required 80 conductor cable is not > > > present or could not be detected properly, or that one of the > > > devices on the channel only accepts up to UDMA2/ATA33. > > > == > > > > > > You've got your 40GB Maxtor (you've installed FreeBSD on it), an > > > ATA100 > > > device, connected with your CDROM, an ATA33 device. The result > is: > > > your > > > boot drive is running at UDMA33 instead of UDMA100. This is not > > > going > > > > > > to work real well, as you can see. > > > > > > Do you really need that 40GB Maxtor? If you do, you're going to > > > have to > > > try adding an ATA controller card into one of your PCI slots and > > > use that to connect your hard drives to. > > > > > > Try removing the 40GB Maxtor and reinstalling FreeBSD on the > other > > > two > > > drives. I think that will clear up some problems for you. > > > > Can this be causing the problem with the 300 GB drive on the other > > controller? What I don't understand is why is there a problem only > > with one drive on the secondary controller? > > > > As for the cdrom, how else can it be connected? It will ALWAYS be > > slower than the hard disk. Or do you mean it should just not be > > connected to the boot drive? I never had such a problem before. > > I'll move around my drives and see what happens. > > > > Thanks for your help. > > > > -- > > Peter > > > Hi Peter, > > You're going to have to have the cdrom connected, just not with a > hard-drive or you'll have problems. As for the third hard-drive, that > > may have more to do with the way you set up the system than the > problems with the connections as they are now. But, if you remove > that > drive and reinstall the system, I think (actually, I know, if you do > it > right) that will clear up a lot of problems. You've got two SATA > ports > on that MB, I think you would have problems then too. If you need > that > 40 GB drive, I suggest you go out and get a controller that you can > run > all three drives off of.. > > What I mean is, if you have the cdrom and the 40GB HD connected to > the > same port, on the same cable, as you have, it will only run at the > speed of the cdrom. You have to get the HD off of that port. Since > you've used the slave port with the other two HDs, your only choice > is > to install a Controller card, like a Promise or some other card. I > had > a problem like that at one time and that was the only way to fix it. > That's why I sent that snippet from the at man page, it tells you > what's going to happen if you do it this way. I don't think you're > going to like have at ATA100 drive as the system drive running at > UDMA33, it just might result in timing problems. > > Don > > PS At this point I probably can't answer anymore questions, at least > not > today. I've had too many beers and I'm having a tough time typing. I > can still make sense, I just am having a problem getting it from my > brain to the e-mail. And I intend to have some more. You can answer me tomorrow if you like but here is an update: I removed the cdrom and the problem remains. I got the usb ports to work as well by updating the bios and fiddling with some settings. It is truly a mystery why this 300 GB drive cannot talk to FreeBSD. Again, it is detected fine by the bios; it passes dos level diagnostics; it is on the same ide cable (as slave) as the 200 GB drive that is identical to it save for an extra 100 GB. My next step is to boot with knoppix to see how it behaves. -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
On Saturday 11 March 2006 18:48, Peter wrote: > > You can answer me tomorrow if you like but here is an update: > > I removed the cdrom and the problem remains. I got the usb ports to > work as well by updating the bios and fiddling with some settings. > It is truly a mystery why this 300 GB drive cannot talk to FreeBSD. > Again, it is detected fine by the bios; it passes dos level > diagnostics; it is on the same ide cable (as slave) as the 200 GB > drive that is identical to it save for an extra 100 GB. My next step > is to boot with knoppix to see how it behaves. > > -- > Peter > Hi Peter, I've recovered sufficiently enough that I can type without spending all my time correcting spelling errors that a spelling checker can't fix. OK, does dmesg still give this with the cdrom removed: ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB at ata0-master UDMA33 acd0: CDROM at ata0-slave PIO4 ad2: 190782MB at ata1-master UDMA100 ad3: 286168MB at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a If the message for ad0 has changed, and it is now detected as an ata100 device and is running at UDMA100, you've solved part of your problem. Your system will access the boot drive at a higher speed. ad3 is still detected but you can't access it. So, I have to ask: when you set up the system, did you install a ufs system on it? Did you carve it up using bsdlabel? Or, did you leave it alone because you plane on using it for something else? This would be a reason for why it shows up on dmesg, but you can't access it. Now, you need to do something about the cdrom. It's kind of unhandy to be without one. That's why I asked if you really needed the 40GB Maxtor and if you did, suggested you get an ata controller card, then you could use all three drives. And I also asked if you could just remove that drive and use the two Seagates. I guess there's one other question: how did you get from 5.4 to 6.0, and is it 6.0 or is it 6 STABLE? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
On Saturday 11 March 2006 13:38, Peter wrote: > --- "Donald J. O'Neill" <[EMAIL PROTECTED]> wrote: > > [...] > > > > ad0: DMA limited to UDMA33, device found non-ATA66 cable > > > ad0: 39205MB at ata0-master UDMA33 > > > acd0: CDROM at ata0-slave PIO4 > > > ad2: 190782MB at ata1-master UDMA100 > > > ad3: 286168MB at ata1-slave UDMA100 > > > Trying to mount root from ufs:/dev/ad0s1a > > > > > > __ > > > > You've got a problem alright, and you don't even see it. > > > > == > > The ata driver sets the maximum transfer mode supported by the > > hardware > > as default. However the ata driver sometimes warns: ``DMA limited > > to > > > > UDMA33, non-ATA66 cable or device''. This means that the ata > > driver has detected that the required 80 conductor cable is not > > present or could not be detected properly, or that one of the > > devices on the channel only accepts up to UDMA2/ATA33. > > == > > > > You've got your 40GB Maxtor (you've installed FreeBSD on it), an > > ATA100 > > device, connected with your CDROM, an ATA33 device. The result is: > > your > > boot drive is running at UDMA33 instead of UDMA100. This is not > > going > > > > to work real well, as you can see. > > > > Do you really need that 40GB Maxtor? If you do, you're going to > > have to > > try adding an ATA controller card into one of your PCI slots and > > use that to connect your hard drives to. > > > > Try removing the 40GB Maxtor and reinstalling FreeBSD on the other > > two > > drives. I think that will clear up some problems for you. > > Can this be causing the problem with the 300 GB drive on the other > controller? What I don't understand is why is there a problem only > with one drive on the secondary controller? > > As for the cdrom, how else can it be connected? It will ALWAYS be > slower than the hard disk. Or do you mean it should just not be > connected to the boot drive? I never had such a problem before. > I'll move around my drives and see what happens. > > Thanks for your help. > > -- > Peter > Hi Peter, You're going to have to have the cdrom connected, just not with a hard-drive or you'll have problems. As for the third hard-drive, that may have more to do with the way you set up the system than the problems with the connections as they are now. But, if you remove that drive and reinstall the system, I think (actually, I know, if you do it right) that will clear up a lot of problems. You've got two SATA ports on that MB, I think you would have problems then too. If you need that 40 GB drive, I suggest you go out and get a controller that you can run all three drives off of.. What I mean is, if you have the cdrom and the 40GB HD connected to the same port, on the same cable, as you have, it will only run at the speed of the cdrom. You have to get the HD off of that port. Since you've used the slave port with the other two HDs, your only choice is to install a Controller card, like a Promise or some other card. I had a problem like that at one time and that was the only way to fix it. That's why I sent that snippet from the at man page, it tells you what's going to happen if you do it this way. I don't think you're going to like have at ATA100 drive as the system drive running at UDMA33, it just might result in timing problems. Don PS At this point I probably can't answer anymore questions, at least not today. I've had too many beers and I'm having a tough time typing. I can still make sense, I just am having a problem getting it from my brain to the e-mail. And I intend to have some more. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
On Saturday 11 March 2006 02:42, Peter wrote: > --- Kris Kennaway <[EMAIL PROTECTED]> wrote: > > On Fri, Mar 10, 2006 at 11:57:59PM -0500, Peter wrote: > > > I'm setting up a new server on 6.0 I've been planning for a long > > > > time > > > > > and I am very disappointed with two critical issues. My > > > > motherboard is > > > > > the ASUS K8V-X SE that I chose because it was listed as compatible > > > > at > > > > > the FreeBSD/amd64 Project: > > > > > > http://www.freebsd.org/platforms/amd64/motherboards.html > > > > > > I wonder if going back to 5.4 might help? > > > > > > Onto the problems... > > > > You might have more luck if you also talk to [EMAIL PROTECTED] > > I'm not sure who this is but I'll look into it. > > > > 2. I can't use my USB ports! > > > > > > I get a line like this for each of my ports: > > > > > > uhci0: port 0xb800-0xb81f irq 21 at > > > > device > > > > > 16.0 on pci0 > > > uhci0: [GIANT-LOCKED] > > > > OK, but what is the problem? > > When something is plugged into a port and the system is powered up it > will freeze at the POST level with no errors. It just sits there. > I had similar problems with an Asus K8V a couple of months ago. Seems a lot of those boards had bios problems. Make sure you're using the latest bios upgrade. Fixed it for me. Beech -- --- Beech Rintoul - Sys. Administrator - [EMAIL PROTECTED] /"\ ASCII Ribbon Campaign | Alaska Paradise Travel \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com --- pgpWAZQNRFkfl.pgp Description: PGP signature
Re: Disappointed with version 6.0
--- "Donald J. O'Neill" <[EMAIL PROTECTED]> wrote: [...] > > ad0: DMA limited to UDMA33, device found non-ATA66 cable > > ad0: 39205MB at ata0-master UDMA33 > > acd0: CDROM at ata0-slave PIO4 > > ad2: 190782MB at ata1-master UDMA100 > > ad3: 286168MB at ata1-slave UDMA100 > > Trying to mount root from ufs:/dev/ad0s1a > > > > __ > You've got a problem alright, and you don't even see it. > > == > The ata driver sets the maximum transfer mode supported by the > hardware > as default. However the ata driver sometimes warns: ``DMA limited to > > UDMA33, non-ATA66 cable or device''. This means that the ata driver > has detected that the required 80 conductor cable is not present or > could not be detected properly, or that one of the devices on the > channel only accepts up to UDMA2/ATA33. > == > > You've got your 40GB Maxtor (you've installed FreeBSD on it), an > ATA100 > device, connected with your CDROM, an ATA33 device. The result is: > your > boot drive is running at UDMA33 instead of UDMA100. This is not going > > to work real well, as you can see. > > Do you really need that 40GB Maxtor? If you do, you're going to have > to > try adding an ATA controller card into one of your PCI slots and use > that to connect your hard drives to. > > Try removing the 40GB Maxtor and reinstalling FreeBSD on the other > two > drives. I think that will clear up some problems for you. Can this be causing the problem with the 300 GB drive on the other controller? What I don't understand is why is there a problem only with one drive on the secondary controller? As for the cdrom, how else can it be connected? It will ALWAYS be slower than the hard disk. Or do you mean it should just not be connected to the boot drive? I never had such a problem before. I'll move around my drives and see what happens. Thanks for your help. -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
On Sat, Mar 11, 2006 at 06:42:49AM -0500, Peter wrote: > > > 2. I can't use my USB ports! > > > > > > I get a line like this for each of my ports: > > > > > > uhci0: port 0xb800-0xb81f irq 21 at > > device > > > 16.0 on pci0 > > > uhci0: [GIANT-LOCKED] > > > > OK, but what is the problem? > > When something is plugged into a port and the system is powered up it > will freeze at the POST level with no errors. It just sits there. OK, so this is a problem with your BIOS or hardware itself, since FreeBSD isn't running during POST. Kris pgppvtmX3PFUG.pgp Description: PGP signature
Re: Disappointed with version 6.0
On 2006-03-11 06:42, Peter <[EMAIL PROTECTED]> wrote: > --- Kris Kennaway <[EMAIL PROTECTED]> wrote: > > On Fri, Mar 10, 2006 at 11:57:59PM -0500, Peter wrote: > > > Onto the problems... > > > > You might have more luck if you also talk to [EMAIL PROTECTED] > > I'm not sure who this is but I'll look into it. > > > > 2. I can't use my USB ports! > > > > > > I get a line like this for each of my ports: > > > > > > uhci0: port 0xb800-0xb81f irq 21 at device > > > 16.0 on pci0 > > > uhci0: [GIANT-LOCKED] > > > > OK, but what is the problem? > > When something is plugged into a port and the system is powered up it > will freeze at the POST level with no errors. It just sits there. At POST time, FreeBSD hasn't loaded at all. If you are having problems at that stage, it looks like a motherboard or BIOS problem :-( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
On Friday 10 March 2006 22:57, Peter wrote: > I'm setting up a new server on 6.0 I've been planning for a long time > and I am very disappointed with two critical issues. My motherboard > is the ASUS K8V-X SE that I chose because it was listed as compatible > at the FreeBSD/amd64 Project: > > http://www.freebsd.org/platforms/amd64/motherboards.html > > I wonder if going back to 5.4 might help? > > Onto the problems... > > 1. I have 4 IDE drives: > > primary controller: Maxtor 40 GB hd (master) and LG cdrom (slave) > secondary controller: Seagate Barracuda 200 GB hd (master) and > Seagate Barracuda 300 GB (slave) > > Problem: The 300 GB drive is unusable. > > I set it up ok with sysinstall during the installation but the system > will not boot properly if it has an entry in /etc/fstab. I get many > errors like: > > "ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63" > > I also get input/output error if I try to examine its label with > disklabel. > > dmesg output is at the end of this post when I booted without fstab > line. > > The strange thing is that the two drives on the secondary controller > are so similar. Same manufacturer, same product line, the speeds are > the same. Everything is the same except the size. I ran dos-level > diagnostics on it and no problems were found. > > 2. I can't use my USB ports! > > I get a line like this for each of my ports: > > uhci0: port 0xb800-0xb81f irq 21 at > device 16.0 on pci0 > uhci0: [GIANT-LOCKED] > > > > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) 64 Processor 3000+ (2002.58-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0xf4a Stepping = 10 > Features=0x78bfbffGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> AMD > Features=0xe0500800 > real memory = 536543232 (511 MB) > avail memory = 515702784 (491 MB) < snip > > ad0: DMA limited to UDMA33, device found non-ATA66 cable > ad0: 39205MB at ata0-master UDMA33 > acd0: CDROM at ata0-slave PIO4 > ad2: 190782MB at ata1-master UDMA100 > ad3: 286168MB at ata1-slave UDMA100 > Trying to mount root from ufs:/dev/ad0s1a > > __ You've got a problem alright, and you don't even see it. == The ata driver sets the maximum transfer mode supported by the hardware as default. However the ata driver sometimes warns: ``DMA limited to UDMA33, non-ATA66 cable or device''. This means that the ata driver has detected that the required 80 conductor cable is not present or could not be detected properly, or that one of the devices on the channel only accepts up to UDMA2/ATA33. == You've got your 40GB Maxtor (you've installed FreeBSD on it), an ATA100 device, connected with your CDROM, an ATA33 device. The result is: your boot drive is running at UDMA33 instead of UDMA100. This is not going to work real well, as you can see. Do you really need that 40GB Maxtor? If you do, you're going to have to try adding an ATA controller card into one of your PCI slots and use that to connect your hard drives to. Try removing the 40GB Maxtor and reinstalling FreeBSD on the other two drives. I think that will clear up some problems for you. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
On 3/11/06, Peter <[EMAIL PROTECTED]> wrote: > > --- Kris Kennaway <[EMAIL PROTECTED]> wrote: > > > You might have more luck if you also talk to [EMAIL PROTECTED] > > I'm not sure who this is but I'll look into it. The amd64-related mailing list > When something is plugged into a [USB] port and the system > is powered up it will freeze at the POST level with no errors. > It just sits there. And this is of course due to the evil FreeBSD daemon living somewhere under the hood of your PC ever since you placed the ominous disc into your CD-ROM drive... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
--- Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Fri, Mar 10, 2006 at 11:57:59PM -0500, Peter wrote: > > I'm setting up a new server on 6.0 I've been planning for a long > time > > and I am very disappointed with two critical issues. My > motherboard is > > the ASUS K8V-X SE that I chose because it was listed as compatible > at > > the FreeBSD/amd64 Project: > > > > http://www.freebsd.org/platforms/amd64/motherboards.html > > > > I wonder if going back to 5.4 might help? > > > > Onto the problems... > > You might have more luck if you also talk to [EMAIL PROTECTED] I'm not sure who this is but I'll look into it. > > 2. I can't use my USB ports! > > > > I get a line like this for each of my ports: > > > > uhci0: port 0xb800-0xb81f irq 21 at > device > > 16.0 on pci0 > > uhci0: [GIANT-LOCKED] > > OK, but what is the problem? When something is plugged into a port and the system is powered up it will freeze at the POST level with no errors. It just sits there. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
On 3/11/06, Peter <[EMAIL PROTECTED]> wrote: > I set it up ok with sysinstall during the installation but the system > will not boot properly if it has an entry in /etc/fstab. I get many > errors like: > > "ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63" Next time you might want to think of an intelligible subject line This seems like a hardware failure. If you have some spare time and bandwidth, download one of the thousand BSD, Linux or Windows live cd's and try to access all of your drives. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disappointed with version 6.0
On Fri, Mar 10, 2006 at 11:57:59PM -0500, Peter wrote: > I'm setting up a new server on 6.0 I've been planning for a long time > and I am very disappointed with two critical issues. My motherboard is > the ASUS K8V-X SE that I chose because it was listed as compatible at > the FreeBSD/amd64 Project: > > http://www.freebsd.org/platforms/amd64/motherboards.html > > I wonder if going back to 5.4 might help? > > Onto the problems... You might have more luck if you also talk to [EMAIL PROTECTED] > 2. I can't use my USB ports! > > I get a line like this for each of my ports: > > uhci0: port 0xb800-0xb81f irq 21 at device > 16.0 on pci0 > uhci0: [GIANT-LOCKED] OK, but what is the problem? Kris pgph7sTNadi6q.pgp Description: PGP signature
Disappointed with version 6.0
I'm setting up a new server on 6.0 I've been planning for a long time and I am very disappointed with two critical issues. My motherboard is the ASUS K8V-X SE that I chose because it was listed as compatible at the FreeBSD/amd64 Project: http://www.freebsd.org/platforms/amd64/motherboards.html I wonder if going back to 5.4 might help? Onto the problems... 1. I have 4 IDE drives: primary controller: Maxtor 40 GB hd (master) and LG cdrom (slave) secondary controller: Seagate Barracuda 200 GB hd (master) and Seagate Barracuda 300 GB (slave) Problem: The 300 GB drive is unusable. I set it up ok with sysinstall during the installation but the system will not boot properly if it has an entry in /etc/fstab. I get many errors like: "ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63" I also get input/output error if I try to examine its label with disklabel. dmesg output is at the end of this post when I booted without fstab line. The strange thing is that the two drives on the secondary controller are so similar. Same manufacturer, same product line, the speeds are the same. Everything is the same except the size. I ran dos-level diagnostics on it and no problems were found. 2. I can't use my USB ports! I get a line like this for each of my ports: uhci0: port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (2002.58-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0xf4a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 536543232 (511 MB) avail memory = 515702784 (491 MB) MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 10 on acpi0 pci_link2: irq 5 on acpi0 pci_link3: irq 0 on acpi0 pci_link4: irq 0 on acpi0 pci_link5: irq 0 on acpi0 pci_link6: irq 0 on acpi0 pci_link7: irq 0 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf400-0xf7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci0: at device 11.0 (no driver attached) atapci0: port 0xe800-0xe807,0xe400-0xe403,0xe000-0xe007,0xd800-0xd803,0xd400-0xd40f,0xd000-0xd0ff irq 20 at device 15.0 on pci0 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 ata0: on atapci1 ata1: on atapci1 uhci0: port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xc000-0xc01f irq 21 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xc400-0xc41f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xc800-0xc81f irq 21 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xfbc0-0xfbc000ff irq 21 at device 16.4 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered isab0: at device 17.0 on pci0 isa0: on isab0 vr0: port 0xb400-0xb4ff mem 0xfbb0-0xfbb000ff irq 23 at device 18.0 on pci0 miibus0: on vr0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:15:f2:17:7f:ac acpi_button0: on acpi0 acpi_button1: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port pp
