Re: HDD Problem
"David W. Chapman Jr." wrote: > > I have a KT7 with an athlon 1.1, no problems with ATA66, don't have a 100 > drive though. Works fine, does make worlds in a little over an hour with > 384mb of pc133, but I do have to downclock the pc133 to 100 because these > via chips have some problem with agp and pc133 at the moment. I'm also running the slow end on the bios memory setting. The wz beta bios is supposed to deal with some memory timing questions. I have downloaded wz but haven't flashed the bios yet. I am running uz, which became w? (their www server is overloaded and can't see what they called the uz when it was released). Abit is also up to KT7a and 686B. I have both Maxtor's (30 GB and 40 GB - ATA100's) set to do only UDMA 33 using Maxtor's udmaupdt.exe program. That didn't help FreeBSD. Windows 2000 didn't have any problems at the UDMA66 setting and just slowed down a little bit at the UDMA33 setting. I have three other systems based on the bx chipset that don't have problems doing UDMA33. If I time my upworld script, I see user times of 18xx seconds and 1.5-1.8 hours wall clock. I figure the difference between doing an update (cvsup of RELENG_4 to installworld) in 40 minutes wall-clock and what I have now is disk transfer speed related. Setiathome runs at ~40% cpu in the background (niced to 19). Because it is only using available cpu time, killing setiathome before I started the builds didn't change the build time significantly. I have a Promise ATA66 card that I am going to try but will have to move one of the HD's and CDROM before the 80-pin cable will reach. The main drive is all by itself on the ide1 controller. Kent > > > > I have an Abit KT7 with PC-133 memory and an Athlon 900 that doesn't > > like FreeBSD 4.2-stable and Maxtor ATA100 drives. Right now, it is > > running in PIO mode and that makes it less than half fast doing a > > system build. The first install of FreeBSD resulted in a trashed > > Win98se primary partition. There were timing issues in the bios that > > were supposed to fix the ATA100 Maxtor drives. The bios was flashed to > > include those fixes. I used sysctl and turned UDMA back on last night > > and it didn't help the ata-disk. It went back to PIO mode in a hurry. > > > > Kent > > > > > > > > -Søren > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > > Kent Stewart > > Richland, WA > > > > mailto:[EMAIL PROTECTED] > > http://kstewart.urx.com/kstewart/index.html > > FreeBSD News http://daily.daemonnews.org/ > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: options USER_LDT *(solved)
> Date: Wed, 27 Dec 2000 16:44:08 -0500 (EST) > From: Donn Miller <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > On Wed, 27 Dec 2000, Evren Yurtesen wrote: > > > is it enough if I make make buildworld ? > > > > anyway thanks for the help. now I could compile kernel > > without any problem. I didnt know that I have to make world etc. > > Since when this is required? (or is it required?) > > > > I knew it was the problem, since I've done the same thing myself. :-) > Generally, "make buildkernel" is used in conjunction with a "make world" > to update the world and kernel simulaneously. I think it's just a > convenience to make kernel building easier when you make the world. It's NOT just a convenience! Another explanation of this appears to be in order: "make buildkernel" makes use of the special knowledge make has of the new, uninstalled system to build the kernel using the updated tools. This assures that the kernel and user files are synchronized. ALWAYS use buildkernel/installkernel when you have updated sources and done a fresh buildworld. NEVER use buildkernel/installkernel if you have not previously done a buildworld. If /usr/obj is not populated, buildkernel will fail. If you are simply modifying the kernel configuration and rebuilding, the best way is to: cd /sys/i386/conf config YOURKERNELNAME and follow the instructions provided. This does not require that the /usr/src or /usr/obj trees be populated. If you have previously done a buildworld and installworld and have not updated your sources, the kernel may be built either way with identical results, but buildkernel/installkernel takes a bit longer. I hope that's clear. If you are confused, get back to me and I'll try to clarify. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
I have a KT7 with an athlon 1.1, no problems with ATA66, don't have a 100 drive though. Works fine, does make worlds in a little over an hour with 384mb of pc133, but I do have to downclock the pc133 to 100 because these via chips have some problem with agp and pc133 at the moment. > > I have an Abit KT7 with PC-133 memory and an Athlon 900 that doesn't > like FreeBSD 4.2-stable and Maxtor ATA100 drives. Right now, it is > running in PIO mode and that makes it less than half fast doing a > system build. The first install of FreeBSD resulted in a trashed > Win98se primary partition. There were timing issues in the bios that > were supposed to fix the ATA100 Maxtor drives. The bios was flashed to > include those fixes. I used sysctl and turned UDMA back on last night > and it didn't help the ata-disk. It went back to PIO mode in a hurry. > > Kent > > > > > -Søren > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > -- > Kent Stewart > Richland, WA > > mailto:[EMAIL PROTECTED] > http://kstewart.urx.com/kstewart/index.html > FreeBSD News http://daily.daemonnews.org/ > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
Soren Schmidt wrote: > > It seems Justin W. Pauler wrote: > > I've heard tell that there are problems with the VIA chipset and UDMA on > > FreeBSD. Is this true, and if so, what is the problem with? > > Hmm, there are no open problems as far as I'm aware... > > > FreeBSD 4.2-STABLE #0: Fri Dec 8 01:52:44 EST 2000 > > CPU: Pentium III/Pentium III Xeon/Celeron (601.37-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0x683 Stepping = 3 > > atapci0: port 0xe000-0xe00f at device 7.1 on > > pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > ad0: 19546MB [39714/16/63] at ata0-master UDMA66 > > > > The drive has enough space and I have 512MB RAM. If I hit the system hard, > > lets say, rm -rf /usr/ports, the system locks up. It doesn't just stop > > responding for a little bit. It locks up tight. It kills all network > > connections, doesn't respond to the console and doesn't respond to any > > network activity. A hard reboot is the only thing that can bring it back to > > life. > > > > One time, someone was able to see the console when this happened, and they > > said something about a page fault. Trying to solve this, we ordered two brand > > new 256MB modules and installed them. It is still happening. > > > > This is a production environment type of server. I've had no other problems > > with FreeBSD 4.2-S, and i'm hoping maybe this is something that has been > > fixed. > > Hmm, my main devbox is based on the VIA '686 although with an athlon > CPU, and there is no problems at all with it. I also dont belive that > this is the disk drivers fault, as in almost all cases you would get > error messages en-masse from the ATA driver I have an Abit KT7 with PC-133 memory and an Athlon 900 that doesn't like FreeBSD 4.2-stable and Maxtor ATA100 drives. Right now, it is running in PIO mode and that makes it less than half fast doing a system build. The first install of FreeBSD resulted in a trashed Win98se primary partition. There were timing issues in the bios that were supposed to fix the ATA100 Maxtor drives. The bios was flashed to include those fixes. I used sysctl and turned UDMA back on last night and it didn't help the ata-disk. It went back to PIO mode in a hurry. Kent > > -Søren > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: options USER_LDT *(solved)
On Wed, 27 Dec 2000, Evren Yurtesen wrote: > is it enough if I make make buildworld ? > > anyway thanks for the help. now I could compile kernel > without any problem. I didnt know that I have to make world etc. > Since when this is required? (or is it required?) > I knew it was the problem, since I've done the same thing myself. :-) Generally, "make buildkernel" is used in conjunction with a "make world" to update the world and kernel simulaneously. I think it's just a convenience to make kernel building easier when you make the world. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: options USER_LDT *(solved)
is it enough if I make make buildworld ?
anyway thanks for the help. now I could compile kernel
without any problem. I didnt know that I have to make world etc.
Since when this is required? (or is it required?)
On Wed, 27 Dec 2000, Donn Miller wrote:
> On Wed, 27 Dec 2000, Evren Yurtesen wrote:
>
> > > }> > .data" {.data section} - "KERNBASE" {*UND* section} at
> > > }file address 1496.
> > > }> > {standard input}:2444: Error: Subtraction of two symbols
> > > }in different
> > > }> > sections "IdlePTD" {.data section} - "KERNBASE" {*UND*
> > > }section} at file
>
> Looks to me like you're doing a make buildkernel in /usr/src without doing
> a make world first. In that case,
>
> cd /sys/i386/conf
> config -r CUSTOM
>
> cd [to the directory config gives you]
> make depend all install
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
On Wed, 27 Dec 2000, Louis A. Mamakos wrote: > > I've got two mobos with VIA MVP3 chipsets on-board. As these systems > (until recently) had only SCSI peripherals, I didn't notice any problem. > However, when I added an IDE CDRW drive, I got these very strange system > lock-ups/hangs. Specifically, this was an FIC VA-503+ mobo, with a > 450MHz K6-2 CPU. From earlier this year: - Begin included text >From [EMAIL PROTECTED] Thu Aug 24 10:35:34 2000 Date: Wed, 23 Aug 2000 19:31:26 -0700 (PDT) From: Jeff Wyman <[EMAIL PROTECTED]> To: Janko van Roosmalen <[EMAIL PROTECTED]> Cc: Robert Augustine <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Random Reboots On Wed, 23 Aug 2000, Janko van Roosmalen wrote: > Check your powersupply. > > If it is 250 Watt throw it out and get at least a 300 Watt. We import > and export computer cases by container and sell a lot of separate 300 > Watt PSU's to customers for ATHLON users. 250 Watt is just not enough for > this cpu. If this is an FIC SD-11 board, it should be known that this board is a very picky one when it comes to voltages - FIC released this board in a hurry when it was still a prototype, leaving many things in error on this board. One thing was the voltage regulators. There are very few on this board compared to other Athlon boards (including other FIC models) and this can make for rather dirty voltages being supplied to your CPU when combined with a culprit PS. However, 2 days is kind of a long time for these problems to arise. There's just too much crap that happens these days to rule it out though. - End included text It could be that the UDMA controller is another "[thing] in error" on this motherboard. -- Chris BeHanna Software Engineer [EMAIL PROTECTED] Remove "bogus" before responding. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ftpd incoming security
On Wed, 27 Dec 2000, Vivek Khera wrote: > MA> Can people change the permissions afterwards or the umask before > MA> uploading, thus circumventing these settings? I'm not too deep in ftpd. > > Hmmm. Yes. According to the ftpd man page, there are commands "SITE > CHMOD" and "SITE UMASK" that will allow that... I guess it is back to > using an alternate ftpd for complete security... I feared just that, that's why I asked. You might of course disable those SITE commands or restrict them. -- Matthias Andree To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ftpd incoming security
> "MA" == Matthias Andree <[EMAIL PROTECTED]> writes: >> --cut here-- >> me:\ >> :umask=0707:\ >> :tc=default: >> --cut here-- MA> Can people change the permissions afterwards or the umask before MA> uploading, thus circumventing these settings? I'm not too deep in ftpd. Hmmm. Yes. According to the ftpd man page, there are commands "SITE CHMOD" and "SITE UMASK" that will allow that... I guess it is back to using an alternate ftpd for complete security... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
REALLY need help with HPT370 ide controller card
please i need help... that hpt370 is starting to piss me off. i've been searching up and down the archives but all i did find was a mail by someone who modified line 212 in /usr/src/sys/dev/ata/ata-raid.c. i did that too and rebuilt the kernel but that didnt quite do the job. i have 2 HDDs, one connected to the hpt370 controller-card, one to the standard ide controller on the mainboard. that HDD works well and i have freebsd installed on it. the other HDD has win2k on it and works quite well too. so that kinda inst a problem, but i need to access the win2k disk from freebsd too. obviously, i cant because of the hpt370 the hpt370 should be supported (according to the ad on the hpt website: "freebsd 4.1 or later") but it seems that a little more work is involved to get this working. so, has anybody out there an idea or information on this? i know the topic "hpt370 raid controller" sucks, but i cant help asking. the archives didnt help me either. thanks and regards Andreas Ntaflos To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
I've got two mobos with VIA MVP3 chipsets on-board. As these systems (until recently) had only SCSI peripherals, I didn't notice any problem. However, when I added an IDE CDRW drive, I got these very strange system lock-ups/hangs. Specifically, this was an FIC VA-503+ mobo, with a 450MHz K6-2 CPU. I saw on a FreeBSD mailing list a suggestion to go into the BIOS setup, and disable "PCI Dynamic Bursting". At least that's what it's called in my Award BIOS. This seemed to have "fixed" the problem for me (or at least hidden it sufficiently well :-); perhaps it might be of some help in other situations? louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
> You guys are not overclocking are you ?? No! Just because I have a BP6 doesn't mean I'm overclocking it. The HPT controller has always done this. Would more messages help, eg bootverbose? I tried DDB on 4.0 and ctrl-esc didn't get out of this state. --Ben To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
On Wed, 27 Dec 2000, Soren Schmidt wrote: > It seems David W. Chapman Jr. wrote: > > You guys are not overclocking are you ?? > > > I've recently seen the same problem on 4.2-stable, probably a early version > > of it, I go to make my kernel and it locks up for a few mins, then I get > > some ata error and then it says resetting devices and it all runs ok, it > > resets the ata devices during boot also. > > > > > > - Original Message - > > From: "Ben Jackson" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Wednesday, December 27, 2000 2:28 PM > > Subject: Re: HDD Problem > > > > > > > > I've heard tell that there are problems with the VIA chipset and UDMA on > > > > FreeBSD. Is this true, and if so, what is the problem with? > > > > > > > > FreeBSD 4.2-STABLE #0: Fri Dec 8 01:52:44 EST 2000 > > > > atapci0: port 0xe000-0xe00f at device 7.1 > > on > > > > pci0 > > > > ad0: 19546MB [39714/16/63] at ata0-master UDMA66 > > > > > > Sounds similar to the problem I've had with the HPT controller on my > > > Abit BP6. If you look at the -stable archives from the last few days > > > you'll see some suggestions. I should really move this drive to one > > > of the ATA33 controllers since the drive itself only (??) does about > > > 30M/s sustained anyway. > > > > > > atapci1: port > > 0xd800-0xd8ff,0xd400-0xd403,0xd000-0xd007 irq 18 at device 19.0 on pci0 > > > ata2: at 0xd000 on atapci1 > > > ad4: 29311MB [59554/16/63] at ata2-master UDMA66 > > > > > > > The drive has enough space and I have 512MB RAM. If I hit the system > > hard, > > > > lets say, rm -rf /usr/ports, the system locks up. > > > > > > I have to hit mine harder. The more I upgrade FreeBSD, the more times > > > it successfully resets the devices after a read timeout, but eventually > > > it hangs while resetting. With 4.2 (or maybe it's softupdates) it > > > manages to save some of the errors in /var/log/messages. > > > > > > No page faults. Haven't had a persistant kernel "page not present" > > > problem since FreeBSD 1.1.5. Also, my UDMA66 problem is happening > > > on a machine with ECC mem. > > > > > > Another datapoint: my desktop machine (until yesterday running 3.4) > > > has an IBM disk in it which likes to spin down on its own, causing > > > timeouts on the first access afterwards. It's irritating (though not > > > enough that I've investigated jumpering it for always-on) but it has > > > never hung the system. > > > > > > --Ben > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > > -Søren > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: trouble with UDMA66 drive on Abit BP6: READ timeout
Hi all, I'd like to add some of my experiences with BP6. I tried to create software RAID using vinum (I tried RAID-1 and RAID-5) on 4x14GB drives connected to HighPoint ATA66 in UDMA66 mode. I experienced serious problems until I overclocked the bus to 78 MHz. I wasn't able even to do newfs on that vinum device - it always froze the box (usually with message "resetting devices"). After overclocking it runs pretty stable - although I know overclocking is highly unadvisable. I think making newfs on RAID-1 is high load operation and it seems bus doesn't catch up on normal frequency. I'm using BIOS of 11/17/1999. I'm runnig FreeBSD 4.0 Release. Petr Petr Holub Masaryk University Dept. Physical Chemistry Supercomputing Centre Brno Faculty of Science Institute of Compt. Science Kotlarska 2, 61137 Brno, CZBotanicka 68a, 60200 Brno, CZ phone: +420-5-41129312phone: +420-5-41512278 e-mail: [EMAIL PROTECTED]e-mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Rudy
On Tue, 26 Dec 2000, Rudy Gingles wrote: > I recently went through the same thing (still having intermittent sound > problems, but it's getting there). /dev/sndstats seems to be created when > you do sh MAKEDEV snd0. That created all the sound devices (mixer, dsp, > etc.). > > Rudyatek ... Thats somewhat strange... In the handbook it said that the "sh MAKEDEV snd0/1" should be done after a "cat /dev/sndstat" to find out wich number to use on the first command... Joao Fernandes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Roadmap for perl upgrades to STABLE?
> > Quite correct. I have done this for several perl versions now, and > > the work involved is quite scarey. > > Not that I'm a fan of the GPL, but wouldn't importation of gmake > into the toolchain that gets installed by default help this problem > along enormously? No. It will make it worse. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
