Re: Quickie question on UDMA/33
At 05:53 AM 4/12/00 -0400, Trevor Johnson wrote: >> Western Digital Caviar hard drives that should support UDMA/33, as should >> the Chipset. >> >> Both boot up, trying UDMA mode, throwing ICRC READ ERROR's then kick back >> down to PIO mode 4. > >> Bios's are set to do auto-chose pio/dma modes. > >There may be a BIOS option that will disable DMA entirely. > >> I've resolved to simply adding in the rc to reset them to pio mode, to get >> it over with (but I still get the errors at boot-up prior to the rc doing >> them). >> >> I simply use 'device ata' etc. forms in the knerel config. > >You might try commenting out this option (if you're using it): > >options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices That would apply only to the DVD, not the hard drives of course, but still there is no reason that reasonably modern equipment shouldn't work in UDMA/33 mode. Are the IDE cables new and in good shape? Using each end connector before attaching a device to the middle one... Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
[...] > > Another issue is the size. Many factors determine how quickly one can > > obtain the ISO. It would be nice if it were broken into smaller > > volumes. About 10-20 MB each would be good. That way should something > > fail, there less time and bandwidth wasted should one need to start over. > >That would just make things more complicated, and there's no >reason for that. That's what the "reget" command is good for >-- no reason to start over at all. I would like to mention one case where it would have been helpful to have the .iso broken into smaller pieces. I have a 21,600bps net connection which my ISP will disconnect after 6 hours of uptime, and once had a friend (whom is not nearby, but I see on on occasion) download the 3.3-STABLE ISO image for me via his cable modem for me to burn to CD. As luck would have it the file's MD5 checksum did not match up, and I was forced to redownload the entire file over my sloow modem connection (took around 6 days). Had the file been split and a checksum computed for each piece, I could have grabbed only the affected portion of the ISO. This said, I still do not believe it is worthwhile to split the ISO into smaller files, as it only adds complexity to the situation. Concatenating the files back into an ISO would be OS-dependant and perhaps a bit too much for first time users to cope with. I just assume things stay the way they are. Also, should anyone care, I feel that gzipping these files is a waste of time, unless server bandwith is a serious concern. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0R ?
At 19:05 03/13/2000 +, Ben Smithurst wrote: >Jim Bloom wrote: > >> The tag was laid down earlier today. Here is what my current kernel >> claims to be at the moment: > >I saw the RELENG_4 tag in my cvsup log, but I don't think that's the >same as the 4.0 release tag is it? That would be RELENG_4_0_0_RELEASE >surely. > I believe RELENG_4 would refer to the 4.x-STABLE branch (??maybe??), since it is different from 5.0-CURRENT but still not ready for it's first release. I'm no authority on the subject, though. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
At 22:01 01/25/2000 +0100, you wrote: >It seems Tom Embt wrote: >> Don't mean to butt in here, I haven't really been following the thread - >> but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) >> on secondary master of the PIIX4 on my BP6. By going into the BIOS (the >> section of it where you would set CHS numbers, LBA, etc) and changing the >> secondary master device from "none" to "auto", I have gone from: >> >> BTW, this was on a kernel from around 20:00 GMT Jan 25 > >Interesting... > >What version is you ata-all.c ?? its damn close to the commit I just >made, that should fix that problem... > >-Søren > That was with 1.43 I just updated all the files in /usr/src/sys/dev/ata (ata-all.c v1.44) and made a new kernel. While rebooting I set the BIOS back to "none" and watched FreeBSD boot. No error :) - then I rebooted to kernel.old (1.43) without touching the BIOS and the error came back. Looks like you got it. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
At 09:47 01/25/2000 +0100, Soren Schmidt wrote: >It seems Anders Andersson wrote: >> I have the same problem: >> >> [anders@enterprise:anders] $ dmesg | grep ata >> ata-pci0: port 0xffa0-0xffaf at device 7.1 >> on pci0 >> ata0 at 0x01f0 irq 14 on ata-pci0 >> ata-isa0: already registered as ata0 >> ata0-slave: ata_command: timeout waiting for intr >> ata0-slave: identify failed > >Could I please have a complete dmesg from that ?? > >-Søren > Don't mean to butt in here, I haven't really been following the thread - but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) on secondary master of the PIIX4 on my BP6. By going into the BIOS (the section of it where you would set CHS numbers, LBA, etc) and changing the secondary master device from "none" to "auto", I have gone from: SMP: AP CPU #1 Launched! ata1-master: ata_command: timeout waiting for intr ata1-master: identify failed ad0: 9671MB disk at ata0 as master mode UDMA33 Mounting root from ufs:/dev/ad0s1a to: SMP: AP CPU #1 Launched! ad0: 9671MB disk at ata0 as master mode UDMA33 acd0: CDROM at ata1 as master mode PIO0 Mounting root from ufs:/dev/ad0s1a I stumbled upon this quite by accident, but maybe it'll be of some help to somebody... BTW, this was on a kernel from around 20:00 GMT Jan 25 Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why is my current so .... stable?
At 10:52 01/13/2000 +1030, Mark Newton wrote: >On Wed, Jan 12, 2000 at 08:29:44AM -0500, Tom Embt wrote: > > > >This would be great, but I wonder from what source we could take reliable > > >data about -current's stability. > > > > How 'bout some sort of client program that is run via the rc.d and > > rc.shutdown scripts? > >One of the more annoying aspects of IRIX in its default config is >that whenever you do a halt or reboot it'd pop up a menu to ask why. >That information, together with crash dump info and other data about >system failures, can be funnelled into a mail filter which records >historical reliability data; That data can (optionally) be sent back >to SGI too. > >We could provide something like this, but (a) if it's on by default >it'll suck rocks, and (b) if it's off by default nobody will bother >turning it on. Hey ho! > >- mark > Hmm, well the menu thing would surely suck, but we wouldn't really need that info anyway. Perhaps if the startup/shutdown info was just written to /var/log/ and people could optionally enable (as in off by default) something in /etc/rc.conf to actually send the info back to a master server on a regular basis. Even if the info isn't sent to the master it could be parsed locally if so desired. Again, just ideas.. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why is my current so .... stable?
At 14:27 01/12/2000 +0100, Christian Carstensen wrote: >On Wed, 12 Jan 2000, Donn Miller wrote: > >> My guess is that once -current gets closer to the release date, it becomes >> more and more stable. I guess the period of greatest instability occurs >> somewhere about 1/4 to 1/2 through the -current life cycle. We could do a >> chart plotting stability vs. time for the life cycle of a given >> -current. That could help people decide whether or not they want to run >> -current. > >This would be great, but I wonder from what source we could take reliable >data about -current's stability. >But what I've meant was: I've had these ugly system freezes not perfactly >reproducable, but very often. From what I've read on current list, the >problems still exist, but not on my system. At least this system runs >stable for 1 day now. I'm wondering, why. > How 'bout some sort of client program that is run via the rc.d and rc.shutdown scripts? When run on bootup it checks dmesg for "WARNING: / was not properly dismounted", and tells a master server whether or not the last reboot was intentional. When run at shutdown it tells the master server the machine's uptime. Of course it would also help to send a 'uname -v' in both situations. This system would have statistical flaws, but it is still an interesting idea. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Additional option to ls -l for large files
>> kB and kiB are the proper abreviations, not KB and KiB. I don't know >> if miB or MiB is correct, likely MiB. > > I always thought it was "k/m/b = 1,000/1,000,000/1,000,000,000" >and "K/M/G = 2^10/2^20/2^30". Or was this just some convention I >learned somewhere that I mistakenly thought of as an actual accepted >rule? But, with the letter "M" for example, m = milli-, M = mega- Like Donn was saying, there's no reason not to do it every way. Have the different options selectable by either an environmental variable or a command line switch. I'd vote for default behavior as the traditional: K = 2^10 M = 2^20 G = 2^30 T = 2^40 P = 2^50 .. but also have options for showing the entire unclipped file length, "binary mode international abbreviation standard", and maybe even scientific or engineering notation (for kicks). Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Port of ext2fs fsck
OK for starters, a disclaimer: I have nearly zero experience with Linux. ..but I would guess that it is naming the disk much like BSD does, with hdb1...hdb4 being the four bios partitions (BSD slices) and hdb5 and up being the logical DOS-style partitions inside the other "DOS extended partition(s)". I believe Linux does make use of DOS "extended partitions" in this way. If this is true your RH /usr would be /dev/ad1s6, I think. The entry in /dev might not yet exist, though. At 12:26 12/23/1999 -0500, Donn Miller wrote: >Is there such a beast? This would be a big big help to those who >administer Linux boxes from FreeBSD machines. And, it would make >life easier for those of us who dual-boot with FreeBSD and >Linux. Basically, I'd like to see a port of e2fsck in the ports >collection. > >Also, I had this weird problem in the past. See, I've got >another IDE disk on my primary slave IDE controller (1.1 GB). I >installed RedHat Linux on there. Basically, that disk had 3 >Linux partitions: > >120M / /dev/hdb1 >120M swap/dev/hdb5 >~800MB /usr/dev/hdb6 > >Don't ask; the RedHat installer partitioned it this way. >Anyhow, when I do fdisk /dev/rad1, FBSD's fsck only sees 2 >partitions. Partition one is the 120M / partition, which I can >mount OK. But, fdisk claims the 2nd partition is a 920 MB >extended DOS partition. Hmmm... well, it may be that my second >disk needs low-level formatted or something. > >- Donn > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > > Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BP6 (Was Re: Success with ATA drivers and UDMA66)
>[SNIP] > >> I would like to know how HOT other people's processors get. In the >> stationary situation I have a system core (= processor average) temperature >> of 46 and a case temperature of 50 degrees Celcius/Centigrade. > >What do you use for temp. watching ? (I fetched a little hack which is >called wmtempmon). My temps are somewhat lower : around 35/36 °C, as >I've installed "Alpha" coolers, bought from www.3dfx.com. One colleague >at work uses the same sink/fan combo, but with peltier and a monstrous >PSU to get to 572MHz. I've also loaded the latest BIOS from Abit. Perhaps you mean www.3dfxcool.com? Here's my story: I have two PHO fans from that place on my SL36C 366's (540's now). I had to do alot of tinkering to get them stable at that speed, in the end it all comes down to temperature and luck. One of my CPUs will do 550MHz (my goal) with a little TLC, but the other has to be prodded harshly to get it to 540Mhz. In the end I have done the following: - Realize that my heatsinks wouldn't fit over the angled levers on the ZIF sockets. Disassemble ZIF sockets and straighten metal levers in small vise; reassemble ZIF sockets. - Lapp the poorer CPU with successively finer grits of wet/dry sandpaper (it's mirror-like copper color now :) - Lapp the heatsink for this CPU - Turn around the fans on the heatsinks (quieter and works with well with next modification), using 3/16" standoffs made from vinyl hose and covering the side gap with electrical tape to create a ducted "sucking" effect. - Create a complicated cardboard air ducting system inside my case (I kid you not!!) which uses a case80HO (80mm case fan) to suck air in the side vents, blow it in between the CPUs and the AGP card, where the CPU fans suck it back up through the heatsinks, and it gets ducted back out the rear of the case. This dropped CPU temperature by something like 4-5 degrees Celsius IIRC, and is the key to this whole thing working reliably. I think the reason it helps so much is that it bathes the heatsinks in room-temperature air instead of internal case-temperature air, and does not allow "dead air" to recirculate around the heatsinks. On the downside it can reduce circulation for the rest of the components in the case, and should be done with caution. - Determine the "right" amount of heatsink goop to use, get it right and don't ever touch them again. Tip: apply this stuff with a clean single edged razor blade. - Play with CPU speeds and voltages doing ALOT of "make -j 12 buildworld" on a nice warm summer day to seperate the settings that _mostly_ worked from the ones that _really_ worked. Some would run for >30 minutes without a hitch only to sig11 at the last minute. Turns out 2.2V is the sweet spot for both CPUs. In the end I have a very stable dual 540MHz system who's CPUs NEVER exceed 45C and case temp NEVER exceeds 40C (BTW, no A/C here, ambient 65-80F). Was it worth it? It depends what you're time is worth and if you enjoy this sort of thing. It's not for most people, but I certainly had fun. Next project will be a water cooler (faster & quieter, yeah!), and after that I may put a pair of peltiers between the water plates and the CPUs. One must remember that a pair of fast CPUs is not always super useful. My compiling is still pretty much disk/memory bound, and what else uses the real horsepower of two fast Celerons? Games? hah - I've only an original TNT in this box, which is certainly the limiting factor in 3D stuff. One place I've found this system to really shine is running distributed.net clients. In RC5-64 I can get just over 3.0 Mkeys/sec, however right now I'm trying to win the CSC contest (I've personally done about 0.006% of the keyspace so far, out of ~57% total by all distributed.net members). Am I sick and twisted for being so concerned about busting keys? The BP6 is certainly a fun board to play with in FreeBSD, particularly now that the HPT366 is supported (Thanks Soren!), SMP is getting better every day, and there's always new sources to compile. PS - should this be moved to -hardware??? Man, I'm going to regret writing all that, now I've got replies to deal with ;) Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Success with ATA drivers and UDMA66
[snip] >> What is the rating of your Power supply ? > >Not quite high enough :-( >It's a 300 Watt power supply. > Hehe - I'm running dual 540's (2.2V) on a BP6 (I'm guessing around 30 Watts per CPU), extra case fan, big CPU fans, CD, TNT and an IDE drive (I've had three hooked up once) - on a 235W power supply :) (Although it is probably a better-than-average PS, it's the one that comes with the AOpen HX45 case). One of these days I'm going to hook up a multimeter and see what it draws... Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MajorDomo Problems
I've been mysteriously unsubscribed from -questions sometime between Oct 7th and Oct 10th. My guess puts it at late morning/early afternoon EDT on the 7th. It would seem something is up... good thing somebody mentioned the 'which' command (I'd never heard of it), I was wondering why noone was responding to an earlier post ;) Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-3.3.5/kde-1.1.2/Current today.
At 12:11 AM 9/25/99 +, you wrote: >This morning I made world, updated XFree86 and kde, which didn´t seem to >be a problem until I started X and nowI get revers Icon's - silhouettes >on the kde background. I get no text but a block where the text is and >the mouse will often change to a block. I have never seen anything like >it. I have recompiled X-11 3 times and kde twice. I have erased the >.kde, .kderc, .klogin, Desktop each time. I have no idea where to >look. It was fine yesterday with XFree86-3.3.4 and kde-1.1.1. Also >tried twm and same problem so I can assume the it isn´t kde but .. . >Does the same at -bpp 8/16/24/32 and 640x, 800x y 1024x. > >The video card is a sis-6326 8MB and am running the SVGA server. > >Thanks in advance or any suggestions. > >ed > IIRC someone changed something in KDE recently to make icons work on big Endian machines, perhaps they botched it. If I'm not imagining this, you could probably find it on www.kde.org. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Compupic - yes, it works.
At 09:51 AM 9/11/99 +1200, you wrote: >YOU DA MAN.. that works fine on -current also I'll second that, THANK YOU for this silly but effective solution! >"Gray, David W." wrote: > >> MOVE YOUR /usr/compat DIRECTORY aside - rename it temporarily. Run compupic >> once. You should now be able >> to move /usr/compat back into place (or /compat, if you left it there...) >> Why? I dunno. Found it by accident. > Now another question: Have you been able to get to /usr? When I try to bring it up I get /compat/linux/usr instead. At least /home works.. :) Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone running CompuPic?
At 11:21 AM 9/10/99 -0400, you wrote: >On Fri, 10 Sep 1999, Mike Muir wrote: > >> I get the same problem, after brandelfing to linux and running it, the >> splash screen comes up and...disappears with: >> >> compupic: abnormal termination: (null) >> >> Brandelf -t FreeBSD segfaults it without even showing the splash screen. >> >> Nice helpful error message.. can anyone shed some light on that? > >If I were you, I would truss it: > > $ truss -o truss.out compupic > >and see what it's doing just before it dies. > >-- > Ben Rosengart > I just tried to run it again and both compupic and truss core dumped. Both cores as well as truss.out and dmesg available at http://www.embt.com/tom/compupic-crash.tar.gz . Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Anyone running CompuPic?
Not sure which list this should go to, so if I'm in error feel free to point me in the right direction. I was wondering if anyone has had any luck running CompuPic (http://linux.compupic.com) under FreeBSD? It's an excellent image viewer that can do some basic file management as well. Along with Agent, it's one of the few good apps available for Windoze, and I was excited when I heard there was a free *NIX version available. Unfortunately, I haven't been able to get it to run. I'm not in FreeBSD right now so I'm working from memory, but I had some trouble with the install process (it is obviously not as portable as they'd have you believe). I seem to recall setting $UID and installing bash, but the script still bombed after it was installed. Then I had to brandelf it. I tried both "Linux" and "FreeBSD" branding and one was working better than the other though I don't recall which. End result: It starts to load, brings up a splash screen, and exits. I do recall it leaving messages on the console but forget which signal it was dying with. I can get more info if it's wanted but first I'm just asking if anyone else has either had better luck than I. Here's a quote from the website: "CompuPic is highly portable, and Photodex intends to support as many target platforms as possible over time. CompuPic for Linux (and UNIX) is available as a statically linked executable with no library dependencies whatsoever. You need only a Linux or UNIX kernel to run CompuPic. CompuPic has been tested with major Linux and BSD distributions and had no distribution specific issues. If you represent a hardware manufacturer or Linux/UNIX distribution publisher, you can contact Paul Schmidt to discuss Photodex's development plans for a specific platform. Paul Schmidt VP Technology Photodex Corporation 1106 Clayton Lane #200W Austin, TX 78723 (512) 406-3061 - voice (512) 452-6825 - fax [EMAIL PROTECTED]" They seem to make a point of saying "Linux/UNIX" and not referring to all of *NIX OS's as "Linux", even going so far as to mention BSD once. I was therefor a bit surprised when the binary wouldn't run on FreeBSD. I wonder if The Powers That Be would be interested in pursuing the last sentence there? FYI: My system is SMP 4.0-CURRENT from a day or two ago, XFree86 3.3.3.4 from packages, KDE-1.1 from packages, Linux emu running, etc. As far as my FreeBSD proficiency, lets just say I'm probably not the kind of person that ought to be running -CURRENT :) so I don't think I'd be much help in tracking down the problem (aside from being a guinea pig). of course there also exists the possibility that I forgot to insert tab A into slot B and CompuPic indeed runs perfectly in FBSD for everyone else.. and how did it get to be 3AM ? Ugh. well thanks to anyone who can clue me in, Tom Embt ICQ UIN: 11245398 [EMAIL PROTECTED] d:-)> -- "You're one of those condescending Unix computer users!" "Here's a nickel, kid. Get yourself a better computer" - Dilbert. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
