Re: CALL FOR TESTERS of new ATA/ATAPI driver..
Søren Schmidt writes : Good work, no more stinky delay :-) Thanks!, and I hate delays too :) It works beautifully for me. I can imagine that the people with UDMA drives can't wait for DMA support in it. :-) I've run some tests with Bonnie. Need to still reboot with my old kernel, and run the same test to see what it did. Geoff. -- Geoff Rehmet, The Internet Solution geo...@is.co.za; ge...@rucus.ru.ac.za; c...@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CALL FOR TESTERS of new ATA/ATAPI driver..
It seems Geoff Rehmet wrote: Søren Schmidt writes : Good work, no more stinky delay :-) Thanks!, and I hate delays too :) It works beautifully for me. I can imagine that the people with UDMA drives can't wait for DMA support in it. :-) Its in the works, together with the tagged queuing some of the newer drives supports. I've run some tests with Bonnie. Need to still reboot with my old kernel, and run the same test to see what it did. Let me know how that works out. -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
ATA driver
Just some results of testing the comparison of wd and ata: Both bonnie tests were run on a freshly booted machine, P133, 64M RAM, running X and netscape, but only Bonnie active: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 It may be worth testing with a larger file, freshly booted, with no X running. For reference, here is output of dmesg from my system: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Mar 2 08:26:46 SAST 1999 ge...@hangdog.is.co.za:/usr/src/sys/compile/HANGDOG.ata Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 133269971 Hz CPU: Pentium/P54C (133.27-MHz 586-class CPU) Origin = GenuineIntel Id = 0x52c Stepping=12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 67108864 (65536K bytes) avail memory = 63021056 (61544K bytes) Preloaded elf kernel kernel at 0xf023d000. Probing for devices on PCI bus 0: chip0: Intel 82437VX PCI cache memory controller rev 0x02 on pci0.0.0 chip1: Intel 82371SB PCI to ISA bridge rev 0x01 on pci0.7.0 ata-pci0: Intel PIIX3 IDE controller rev 0x00 on pci0.7.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 vga0: S3 Trio graphics accelerator rev 0x00 int a irq 11 on pci0.11.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in ata-isa1: already registered as ata0 ata1 not found at 0x1f0 ata-isa2: already registered as ata1 ata2 not found at 0x170 ppc0 at 0x378 irq 7 on isa ppc0: W83877F chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp/bnc[*UTP*] address 00:60:97:3d:ff:fc vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface ata1: unwanted interrupt ata1: unwanted interrupt Intel Pentium detected, installing workaround for F00F bug ep0 XXX: driver didn't set ifq_maxlen ad0: Maxtor 71084 A/QA3S1D20 ATA-? disk at ata0 as master ad0: 1036MB (2122780 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue ad1: Conner Peripherals 850MB - CFS850A/8.32 ATA-? disk at ata0 as slave ad1: 812MB (1664583 sectors), 1651 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue acd0: ATAPI CDROM/V1.50 CDROM drive at ata1 as master acd0: drive speed 687 - 5500KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked changing root device to ad0s1a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Geoff. -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geo...@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATA driver
It seems Geoff Rehmet wrote: Interesting, what flags did you use with the old driver (wd) ?? Just some results of testing the comparison of wd and ata: Both bonnie tests were run on a freshly booted machine, P133, 64M RAM, running X and netscape, but only Bonnie active: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATA driver
Just some results of testing the comparison of wd and ata: ... -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 It may be worth testing with a larger file, freshly booted, with no X running. or a newer disk:) i use to see much better performance -- say 5MB/s even without DMA - on modern (say 3GB or greater) disks even on 133MHz machines. (on a PPro200 i think my 6.4GB IBM disk runs close to 10MB/s... cheers luigi ---+- Luigi RIZZO . EMAIL: lu...@iet.unipi.it. Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) ---+- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: egcs and gcc
On Mon, 1 Mar 1999, Chuck Robey wrote: On Mon, 1 Mar 1999, Thomas Dean wrote: As suspected, eg++ is using libstdc++.a, not libstdc++.so.2, as it should. How does this get fixed? I just noticed that the egcs Makefile has a buried: .if defined(WANT_SHAREDLIBS) CONFIGURE_ARGS+= --enable-shared .endif in it. That's not particularly friendly, I wonder why it was put in there, unless the feature is somehow broken? I'm trying to rebuild it now to see what it then installs. That was put in extremely recently. The reason it doesn't build a shared library by default is to avoid potential conflict with the system libstdc++. If you enable it, the port will install the shared lib in /usr/lib/gcc-lib/.../libstdc++.so. You may need to add a runpath option to your link to point the executable at the directory. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lptdriver undefined in kernel compile...
On Tue, 02 Mar 1999 01:42:00 -0400, The Hermit Hacker wrote: this one I *can't* seem to figure out...looked through GENERIC and swear I've added everything I need: Have you checked src/UPDATING and what it has to say about the nlpt-lpt driver changes? Have you made sure your KERNEL config file matches LINT's lpt stuff? If you're still stuck, someone will need to see your KERNEL config file. :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
ATAPI and ATAPI_STATIC with the new ATA* driver?
On Mon, 01 Mar 1999 13:19:20 PST, Søren Schmidt wrote: # for a PCI only system (most modern machines) controller ata0 device atadisk0# ATA disks device atapicd0# ATAPI CDROM's device atapist0# ATAPI tapes Hi Soren, Am I correct in assuming that we can toast ATAPI and ATAPI_STATIC in our kernel configs if we're using your new driver? Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
It seems Sheldon Hearn wrote: On Mon, 01 Mar 1999 13:19:20 PST, Søren Schmidt wrote: # for a PCI only system (most modern machines) controllerata0 deviceatadisk0# ATA disks deviceatapicd0# ATAPI CDROM's deviceatapist0# ATAPI tapes Hi Soren, Am I correct in assuming that we can toast ATAPI and ATAPI_STATIC in our kernel configs if we're using your new driver? Yes, they are not used by the new driver, it only needs the above lines in config, depending on how many subdrivers you want of cause. -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
On Tue, 02 Mar 1999 10:49:17 +0100, Søren Schmidt wrote: Yes, they are not used by the new driver, it only needs the above lines in config, depending on how many subdrivers you want of cause. Excellent. :-) The only thing that bit me was that I used wd0 and wd2 with the older driver, whereas the newer driver automatically decided to use ad0 and ad1. This is expected behaviour, but it's something for other weenies to watch out for. :-) Sadly, cdcontrol still doesn't work with the newer driver and my braindead Creative Labs Infra36 CDROM drive. My older quad speed HITACHI still works. I noticed that the error message has changed, though. I used to get cdcontrol play cdcontrol: Input/output error Now I get cdcontrol play cdcontrol: Unknown error: 84 I guess no amount of programmer cleverness is going to get around crap hardware. Still, if you want me to try things with the hardware I've got, I'm happy to try. I'd offer you shell access, but South African connectivity isn't the best. :-) acd1: CREATIVECD2421E/1.04 CDROM drive at ata1 as slave acd1: drive speed 112 - 4133KB/sec, 240KB cache acd1: supported read types: CD-DA acd1: Audio: play, 255 volume levels acd1: Mechanism: ejectable tray acd1: Medium: no/blank disc inside, unlocked Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
It seems Sheldon Hearn wrote: The only thing that bit me was that I used wd0 and wd2 with the older driver, whereas the newer driver automatically decided to use ad0 and ad1. This is expected behaviour, but it's something for other weenies to watch out for. :-) I warned about that in the anounce :) Sadly, cdcontrol still doesn't work with the newer driver and my braindead Creative Labs Infra36 CDROM drive. My older quad speed HITACHI still works. I noticed that the error message has changed, though. I used to get cdcontrol play cdcontrol: Input/output error Now I get cdcontrol play cdcontrol: Unknown error: 84 Hmm, you could try to enable the debug in atapi-all.c atapi-cd.c and mail me the output of that. The unknown error is because the new driver doesn't translate the atapi errors to errno errors yet. I guess no amount of programmer cleverness is going to get around crap hardware. Still, if you want me to try things with the hardware I've got, I'm happy to try. I'd offer you shell access, but South African connectivity isn't the best. :-) :) lets see what we can do before that, I still have alot of little things I need to get in there, this is just to get people banging on the driver to get feedback early in the development cycle. -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: gcc
How about getting profiling working for ELF kernels before before completely abandoning a.out? There are patches for that in kern/9413 but I haven't got any feedback on them at all. I did try them, they allow the kernel to compile, but they don't seem to work. In particular, the entries made in the flat profile section are all out of whack. Also, all local assembler names are wrong (gprof -u doesn't hide them), and high resolution profiling (config -pp) is completely broken (i386/prof_machdep.c doesn't even compile). I should make it the default so that it gets maintained. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: IDE CDROM not found with PIIX4 chipset, -current kernel
On Sat, 27 Feb 1999 19:20:34 +1100, Bruce Evans wrote: I sent this in for review a year or so ago, but received no reply. The main points are that it honours ATA timing in atapi_wait() and checks for ARS_BUSY in atapi_wait(). I guess we'll need to wait and see whether this is still an issue with Soren's new driver. :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
bmake/contrib framework for egcs
I've put the bmake contrib framework for EGCS at ftp://ftp.nuxi.com/pub/FreeBSD/egcs (ftp://ftp.nuxi.com/pub/FreeBSD/egcs/cvs is all you really need) This is very rough work, but should help us towards our goal. In there you will find a CVS tree under ``cvs''. This CVS tree corresponds to /usr/src in that you will find src/gnu/usr.bin/cc, src/gnu/lib/libstdc++, and src/contrib/egcs. Currently everything under src/gnu/usr.bin/cc builds and installs fine. I've tested the resulting ``cc'' by building working kernels and large parts of /usr/src. I have not yet tested a ``make world''. Everything I've done is w/in the source tree building components. ``cc -elf'' works, ``cc -aout'' doesn't due at least to a path problem finding crt0.o. c++ builds, but is getting segfaults right now. I'll be looking into that. src/gnu/lib/libstdc++ almost builds with ``make CXX=eg++'' where ``eg++'' is from the EGCS port. Please remember to backup your existing: /usr/bin/cc /usr/libexec/ /usr/lib/libgcc* /usr/lib/libg++* /usr/lib/libstdc++* /usr/include/g++/ If you play with ``make world'', you will probably want to disconnect groff from the build until the c++ compiler is working properly. I'll continue to update this cvs tree, so `ncftp3' with recursive get (and only for changed files) is your friend. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
The only thing that bit me was that I used wd0 and wd2 with the older driver, whereas the newer driver automatically decided to use ad0 and ad1. This is expected behaviour, but it's something for other weenies to watch out for. :-) This breakage was announced :-). Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lockmgr panic with mmap()
Until you modify the map, an exclusive lock on the map is overkill. Try using read locks. (See vm_map_lookup.) In the meantime, I can't see any reason why mincore acquires an exclusive lock either. (It never modifies the map.) I'm going to remedy that. Doesn't it modify the map indirectly vi subyte()? I think it wants to prevent modifications, but this is impossible. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATA driver
Just some results of testing the comparison of wd and ata: Both bonnie tests were run on a freshly booted machine, P133, 64M RAM, running X and netscape, but only Bonnie active: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 WD 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 Some results from a Celeron 300A with 66 Mhz bus OC to 75 Mhz (ie. processor running at 337 MHz), 256 MB memory. The disk is a 10 GB IBM Deskstar-16GP, one of the better 5400 RPM disks IMO. With only a 64 MB test, you can clearly see memory caching - for instance the insane numbers for seeks: WD 64 12030 62.4 11295 15.6 12118 29.5 18309 100.0 103363 99.9 1254.2 12.1 ATA64 5803 37.3 7346 18.7 7127 22.5 18220 99.0 102285 99.5 1384.2 13.8 Here's a test with 512 MB, which is bigger than physical memory. Considerably more realistic numbers: WD512 10480 53.8 10333 14.6 3645 7.3 12121 69.6 12133 15.1 129.5 1.8 ATA 512 5745 38.0 7120 17.6 2745 6.6 5475 32.4 7292 10.0 123.2 2.8 I'm using DMA for the WD driver: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): IBM-DTTA-351010, DMA, 32-bit, multi-block-16 wd0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S Bootup messages for the ATA driver: ata-pci0: Intel PIIX4 IDE controller rev 0x01 on pci0.4.1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0: IBM-DTTA-351010/T56OA73A ATA-4 disk at ata0 as master ad0: 9671MB (19807200 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 31 depth queue acd0: ASUS CD-S400/V2.40 CDROM drive at ata1 as slave acd0: drive speed 0 - 6875KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked The CDROM player seems to work - I can play CDs and get sound trough the sound card. Eject works. Haven't tried CD-DA yet. On the first track I played, I got atapi: error = 20 acd0: read_toc failed atapi: error = 20 but this didn't happen for subsequent tracks. Steinar Haug, Nethelp consulting, sth...@nethelp.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
On Tue, 02 Mar 1999 22:26:50 +1100, Bruce Evans wrote: This breakage was announced :-). My only defense is my use of the phrase other weenies in my original mail. ;-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
anyone knows what does it mean
Hello, I recently compile the egcs-1.1.1 and the system report to me that the ahc0:A:0 refuses tagged commands performance non-tagged I/O. The transfer speed drop from 20.00M/s to 3.3 M/s. Is there anyone have the same problem ? Cheers Clarence === Part of the dmesg === da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DCAS-34330 S65A Fixed Direct Access SCSI-2 device da0: 3.300MB/s transfers, Tagged Queueing Enabled ^ poor performance drop from 20.00 to 3.3 da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ahc0 bus 0 target 2 lun 0 da2: FUJITSU M2513A 1500 Removable Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 10) da2: 508MB (1041500 512 byte sectors: 64H 32S/T 508C) cd0 at ahc0 bus 0 target 3 lun 0 cd0: PLEXTOR CD-ROM PX-20TS 1.00 Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ahc0 bus 0 target 1 lun 0 da1: IBM DCAS-32160W !# S63A Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) ahc0:A:0: refuses tagged commands. Performing non-tagged I/O === Part of the dmesg === To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
Sheldon Hearn wrote: On Tue, 02 Mar 1999 10:49:17 +0100, Søren Schmidt wrote: Yes, they are not used by the new driver, it only needs the above lines in config, depending on how many subdrivers you want of cause. Excellent. :-) The only thing that bit me was that I used wd0 and wd2 with the older driver, whereas the newer driver automatically decided to use ad0 and ad1. This is expected behaviour, but it's something for other weenies to watch out for. :-) Is/will there be a way to wire the devices down like you can with SCSI devices? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CALL FOR TESTERS of new ATA/ATAPI driver..
Will the new ATAPI drivers still work with wormcontrol for ATAPI CD Writers? Since it is a WIP, will it support it if it doesn't? Tom Veldhouse ve...@visi.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: gcc
Dienstag, Dienstag, 02. März 1999, you wrote: DOB Netscape uses a *A.OUT* libg++. We are an *ELF* system now. If you want DOB to run Netscape (also a piece of a.out code) you would install the DOB compat22 distribution bits. Then I probably misinterpreted the term abandon it entirely. DOB What we are talking about here has nothing to do with Netscape. Maybe. But what if Netscape decides to make the next fbsd release ELF (and still keeps linking with libg++) ? What about Mozilla ? Is it libg++ - free ? I agree that libg++ is (almost) useless today, but dropping it from the source and making it a port shouldn't disturb anyone. -- Alexander To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: gcc
Hi, On Tue, Mar 02, 1999 at 03:25:20PM +0100, Alexander Sanda wrote: Maybe. But what if Netscape decides to make the next fbsd release ELF (and still keeps linking with libg++) ? What about Mozilla ? Is it libg++ - free ? I agree that libg++ is (almost) useless today, but dropping it from the source and making it a port shouldn't disturb anyone. Mozilla will only be ELF, since it is very likely that the minumum compiler will be egcs. It will also need GTK+, not Motif. I'm surprised the old Netscape needed libg++... Regards, -Jeremy -- | Come home my prodigal son, come home and lets be one, --+-- don't want to see you cry, don't make me tell you why, |you've lived in a house with me, my blood has set you free, |in the world you'll surely die, nothing else will satisfy. -MIC To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
gcj (was Re: egcs and gcc)
I'm learning here, don't get upset if I'm all wet. Another thing I note is that, unlike all the rest of the snapshots of egcs, the pre-release version (and seemingly only the prerelease version) that the port uses has gcj, the java tool, cut out. That seems kind of a shame, doesn't it? Actually no, since the libthreads library is not 'yet released', so the java compiler is kind of useless since you can't build stand-alone executables with the compiler, which is the point of gcj. Nate To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
Bruce Evans wrote: The only thing that bit me was that I used wd0 and wd2 with the older driver, whereas the newer driver automatically decided to use ad0 and ad1. This is expected behaviour, but it's something for other weenies to watch out for. :-) This breakage was announced :-). Besides, it is not even a breakage. It finally got _unbroken_. :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org FreeBSD is Yoda, Linux is Luke Skywalker. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
The only thing that bit me was that I used wd0 and wd2 with the older driver, whereas the newer driver automatically decided to use ad0 and ad1. This is expected behaviour, but it's something for other weenies to watch out for. :-) This breakage was announced :-). Besides, it is not even a breakage. It finally got _unbroken_. :-) It is breakage, and should be fixed. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
On Wed, 03 Mar 1999 00:53:37 +0900, Daniel C. Sobral wrote: The only thing that bit me was that I used wd0 and wd2 with the older driver, whereas the newer driver automatically decided to use ad0 and ad1. [...] Besides, it is not even a breakage. It finally got _unbroken_. :-) All I'm trying to say (and I agree that I really should learn to say exactly what I mean on this mailing list) is that this is something about which much song and dance will need to be made when the driver makes it into STABLE. I didn't read the announcement carefully enough. Nevertheless, I think it'll be useful for any future announcement to STABLE to say something like: Remember that disks are now numbered in the sequence in which they are found (as under the SCSI system), not in absolute positions as they were with the old system. For example, if you had wd0 and wd2 but no wd1, you'll now have wd0 and wd1. Watch out for this, because you may need to change your /etc/fstab and create appropriate entriess in /dev/ before booting your new kernel. I think that Soren's announcement was perfectly adequate for the intended audience, but I do believe that something like the suggestion above will help other weenies like me even more. :-) Ciao, Sheldon. Microsoft Windows NT - now sporting cutting-edge features cribbed from operating systems that only introduced them 20 years ago. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lockmgr panic with mmap()
On Tue, Mar 02, 1999 at 10:41:46PM +1100, Bruce Evans wrote: Doesn't it modify the map indirectly vi subyte()? I think it wants to prevent modifications, but this is impossible. Bear with me, I'll have to split some hairs... We're only interested in whether mincore directly changes the vm_map, literally modifying a vm_map_entry, etc. subyte is writing to memory, not a vm_map_entry. subyte is only indirectly changing the map because a page fault occurs. That page fault *is* (frequently) changing the map, and we're deadlocking when it attempts to acquire the write lock on the map. Basically, what I believe that you suggested yesterday, that mincore release the lock around the subyte is correct. Code will appear shortly... Alan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
In message 199903021646.daa26...@godzilla.zeta.org.au, Bruce Evans writes: The only thing that bit me was that I used wd0 and wd2 with the older driver, whereas the newer driver automatically decided to use ad0 and ad1. This is expected behaviour, but it's something for other weenies to watch out for. :-) This breakage was announced :-). Besides, it is not even a breakage. It finally got _unbroken_. :-) It is breakage, and should be fixed. It isn't breakage when everybody else assigns identities to ATA disks sequentially, irespective of how much other gunk (Ie: CD, Tape) is present on the busses. -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
This breakage was announced :-). Besides, it is not even a breakage. It finally got _unbroken_. :-) It is breakage, and should be fixed. It isn't breakage when everybody else assigns identities to ATA disks sequentially, irespective of how much other gunk (Ie: CD, Tape) is present on the busses. Linux doesn't. It IDE cdroms to IDE drive minor numbers, e.g., hda = 1st controller, IDE drive hdb = 1st controller, IDE cdrom hdc = 2nd controller, IDE drive The sequencing of controllers isn't unique, so the breakage doesn't even work around the problem of mapping BIOS drive numbers to FreeBSD device names except in simple cases. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
In message 199903021812.faa32...@godzilla.zeta.org.au, Bruce Evans writes: This breakage was announced :-). Besides, it is not even a breakage. It finally got _unbroken_. :-) It is breakage, and should be fixed. It isn't breakage when everybody else assigns identities to ATA disks sequentially, irespective of how much other gunk (Ie: CD, Tape) is present on the busses. Linux doesn't. Linux isn't everybody else. -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATAPI and ATAPI_STATIC with the new ATA* driver?
It isn't breakage when everybody else assigns identities to ATA disks
sequentially, irespective of how much other gunk (Ie: CD, Tape) is
present on the busses.
Linux doesn't.
Linux isn't everybody else.
Neither is { everybody else } - { linux }.
Bruce
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: CALL FOR TESTERS of new ATA/ATAPI driver..
[.] I would very much like to hear from you, both good and bad news are very welcome. [.] Looks good on my laptop ! ad0: FUJITSU MHC2040AT/0819 ATA-3 disk at ata0 as master ad0: 3909MB (8007552 sectors), 7944 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue acd0: TOSHIBA CD-ROM XM-1802B/1615 CDROM drive at ata1 as master acd0: drive speed 4134KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked changing root device to ad0s1a It seems stable too (I haven't done any speed tests). Good work, and thanks. -- Brian br...@awfulhak.org br...@freebsd.org br...@openbsd.org http://www.Awfulhak.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CALL FOR TESTERS of new ATA/ATAPI driver..
It seems Thomas T. Veldhouse wrote: Will the new ATAPI drivers still work with wormcontrol for ATAPI CD Writers? Since it is a WIP, will it support it if it doesn't? It should, but i just found out that it somehow fails, I'm bughunting... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Heads up: Linux Thread port changes.
A number of people have downloaded the linux threads port located at http://lt.tar.com . It has been updated today, with minor bug fixes, and a change to make it compatible with kernel patches committed yesterday to both -current and -stable. While I haven't actually tested it, I would expect problems using post-March 1 kernels with the older port, and vice-versa. If you are experimenting with this port, you should update the port when you update your kernel. *NOTE* This port has nothing to do with linux threads running in linux emulation mode. If you're only running linux apps in emulation mode you don't have to worry about this. -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
compiler egcs 1.1.1 error
Hello, I tried to compile the egcs 1.1.1 yesterday and encountered the following error. Can anyone show me hoe to solve it. Thanks. Clarence === Error === === Generating temporary packing list ln -f /usr/bin/gcc /usr/bin/egcc ln -f /usr/bin/g++ /usr/bin/eg++ /bin/mv /usr/lib/libiberty.a /usr/lib/gcc-lib/i386-unknown-freebsd4.0/egcs-2.9 1.60 /bin/mv -f /usr/lib/libstdc++.a /usr/lib/gcc-lib/i386-unknown-freebsd4.0/egcs- 2.91.60/libstdc++.a if [ ! -f /usr/info/dir ]; then /usr/bin/sed -ne '1,/Menu:/p' /usr/share/info/d ir /usr/info/dir; fi install-info /usr/info/cpp.info /usr/info/dir install-info: Undefined error: 0 for /usr/info/dir *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. === Error === To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
fdimage.exe
Hi to all, Can anyone tell me where l can find this fdimage.exe on the ftp-server? I looked in the tools/ directory but l didnt find it. Please a detailed address:-) Thanks, Wim Vermeyen wim.verme...@advalvas.be To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: fdimage.exe
[Moved to -questions] Wim en Debby wrote: Can anyone tell me where l can find this fdimage.exe on the ftp-server? I looked in the tools/ directory but l didnt find it. Please a detailed address:-) ftp://ftp.freebsd.org/pub/FreeBSD/tools/fdimage.exe There's an out-of-date version at some mirror sites, so best fetch it as above. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lockmgr panic with mmap()
On Tue, 2 Mar 1999, Alan Cox wrote: On Tue, Mar 02, 1999 at 10:41:46PM +1100, Bruce Evans wrote: Doesn't it modify the map indirectly vi subyte()? I think it wants to prevent modifications, but this is impossible. Bear with me, I'll have to split some hairs... We're only interested in whether mincore directly changes the vm_map, literally modifying a vm_map_entry, etc. subyte is writing to memory, not a vm_map_entry. subyte is only indirectly changing the map because a page fault occurs. That page fault *is* (frequently) changing the map, and we're deadlocking when it attempts to acquire the write lock on the map. Basically, what I believe that you suggested yesterday, that mincore release the lock around the subyte is correct. Code will appear shortly... Where exactly does thrd_sleep come in, since that's where the program locks up now? Can't be killed, of course... Alan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CALL FOR TESTERS of new ATA/ATAPI driver..
On 02-Mar-99 SXren Schmidt wrote: Its in the works, together with the tagged queuing some of the newer drives supports. Wow! :) Is there any chance od adding the ability to 'wire' devices a la SCSI? :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lockmgr panic with mmap()
On Tue, Mar 02, 1999 at 06:16:50PM -0500, Brian Feldman wrote: Where exactly does thrd_sleep come in, since that's where the program locks up now? Can't be killed, of course... The lock manager isn't bright enough to detect that the process already holds a read lock when it attempts to get the write lock. Thus, you get the thrd_sleep instead of a panic. In short, same bug, different symptoms. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: lockmgr panic with mmap()
On Tue, 2 Mar 1999, Alan Cox wrote: On Tue, Mar 02, 1999 at 06:16:50PM -0500, Brian Feldman wrote: Where exactly does thrd_sleep come in, since that's where the program locks up now? Can't be killed, of course... The lock manager isn't bright enough to detect that the process already holds a read lock when it attempts to get the write lock. Thus, you get the thrd_sleep instead of a panic. In short, same bug, different symptoms. Ahh, makes sense. Quick question: how in the heck did you learn this whole VM system? Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
ATAPI Drive Naming System
Remember that disks are now numbered in the sequence in which they are found (as under the SCSI system), not in absolute positions as they were with the old system. For example, if you had wd0 and wd2 but no wd1, you'll now have wd0 and wd1. Watch out for this, because you may need to change your /etc/fstab and create appropriate entriess in /dev/ before booting your new kernel. This may make a flame war, but why not give SCSI ide devices the SAME device names? Ie. drv0 == first ide controller (harddisk) drv1 == first ide controller (CD-ROM) drv2 == scsi harddrive drv3 == scsi tape backup In my example, I booted from the ide controller (so it started looking there first). If I booted from the scsi harddrive, the 2 scsi drives would be 'found' first? This would simplify (or possibly mutilate) the current naming system for drives. However, is there anyway I can make drv1 (or at3) remain drv1 or at3 when I add more devices? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
New driver and ATAPI DMA?
Will this new ATA driver finally support DMA correctly on ATAPI devices (as opposed to pure ATA disk devices)? This is a feature that could really come in handy for me (as well as a reason to migrate back to -current from 3.1 :) -- ++ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| |lcrem...@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: egcs and gcc
On Tue, 2 Mar 1999, Doug Rabson wrote: That was put in extremely recently. The reason it doesn't build a shared library by default is to avoid potential conflict with the system libstdc++. If you enable it, the port will install the shared lib in /usr/lib/gcc-lib/.../libstdc++.so. You may need to add a runpath option to your link to point the executable at the directory. Doug, my egcs (when I tell it to --enable-shared) installs: libstdc++.so libstdc++.so.2.9 and libstdc++.so.2.9.0 How about I just keep the first one, kill the middle one, and make the real file libstdc++.so.3 (so it keeps our numbering). I'm not sure about the rules for this, since elf ... will stuff looking for libstdc++.so.2 find my new libstdc++.so.3, or will the new one (with it's incompatible format, like you said) be safe? +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
cvsup.ca.freebsd.org available again.
Greetings, Just a quick note to let everyone know that cvsup.ca.freebsd.org is available again. Regards, -- Dan Moschuk (tfreak...@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: compiler egcs 1.1.1 error
On Wed, Mar 03, 1999 at 05:39:04AM +0800, Chan Yiu Wah wrote: Hello, I tried to compile the egcs 1.1.1 yesterday and encountered the following error. Can anyone show me hoe to solve it. Thanks. Clarence JFYI, the port is now at: egcs-1.1.2-pre2 Maybe upgrading the port might help. It compiled and installed fine on 3.1-STABLE, but I didn't get a make world through ... fails at the very beginning when building make. -- Andreas Klemmhttp://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html NT = Not Today (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New driver and ATAPI DMA?
It seems Lee Cremeans wrote: Will this new ATA driver finally support DMA correctly on ATAPI devices (as opposed to pure ATA disk devices)? This is a feature that could really come in handy for me (as well as a reason to migrate back to -current from 3.1 :) Its on my list of wanted items, so there :) -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: CALL FOR TESTERS of new ATA/ATAPI driver..
It seems Daniel O'Connor wrote: On 02-Mar-99 SXren Schmidt wrote: Its in the works, together with the tagged queuing some of the newer drives supports. Wow! :) Is there any chance od adding the ability to 'wire' devices a la SCSI? :) I'll think about it, but lots of things has higher priority... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Printing is vvveeerrryyy slow
I am running smp, 4.0-current, as of Mon Feb 15 03:34:29 PST 1999. Printing is very slow. I have a HP LaserJet III attached to lpt0. Printing in the pcl, text, mode is slower than I expect. Printing in the postscipt mode is extremely slow. A 30K postscript file has been OVER 5 minutes and is not finished!
RE: CALL FOR TESTERS of new ATA/ATAPI driver..
On 02-Mar-99 SXren Schmidt wrote: Its in the works, together with the tagged queuing some of the newer drives supports. Wow! :) Is there any chance od adding the ability to 'wire' devices a la SCSI? :) I'll think about it, but lots of things has higher priority... -Søren I just repeated the Bonnie tests without X running, on a freshly booted machine. (WD is still with X and netscape.) As I said, I am not running any flags on WD, but asl Luigi pointed out, I could probably do with some newer hard drives! Geoff. ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ATA+X+Nets 64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 55.9 2.4 WD+X+Netsc 64 2556 54.5 2902 13.3 1457 9.7 1987 40.3 3082 13.2 59.1 2.0 ATA-noX64 3340 69.7 2984 11.9 1400 8.6 3135 62.4 3182 9.4 135.3 4.4 ATA-noX1 128 3221 68.5 2860 13.4 1169 7.6 2961 58.4 3038 12.2 54.2 2.3 Geoff. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
