Re: 3c509b getting `eeprom failed to come ready' in current
In message [EMAIL PROTECTED], "Matthew N. Dodd" writes: Yes, and when I converted if_ep to newbus I mentioned that hardwire was no longer supported. Couldn't we simply ignore such hardwiring (with a warning) if present ? I'm a little annoyed that if_ep has issues working with if_ex/if_ie and I'll add that to my list of things to look at when I get a chance to fix a few outstanding issues with if_ep. Can we somehow mark the if_ep as "fickle hardware" so it gets probed before the if_ex/it_ie ? We used to have such a facility. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3c509b getting `eeprom failed to come ready' in current
On Fri, 26 Nov 1999, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], "Matthew N. Dodd" writes: Yes, and when I converted if_ep to newbus I mentioned that hardwire was no longer supported. Couldn't we simply ignore such hardwiring (with a warning) if present ? I'm not sure that I can tell the difference between a hardwired device and one that is setup by the PnP/ISA 3c5x9 enumerator. I suppose I could cheat and init the softc in the IDENTIFY or something... Can we somehow mark the if_ep as "fickle hardware" so it gets probed before the if_ex/it_ie ? We used to have such a facility. I'm going to look closer at those two drivers and find the place where they disagree with if_ep. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3c509b getting `eeprom failed to come ready' in current
In message [EMAIL PROTECTED], "Matthew N. Dodd" writes: On Fri, 26 Nov 1999, Poul-Henning Kamp wrote: Can we somehow mark the if_ep as "fickle hardware" so it gets probed before the if_ex/it_ie ? We used to have such a facility. I'm going to look closer at those two drivers and find the place where they disagree with if_ep. They don't disagree, they do some stuff to some registers to detect their respective hardware, which unfortunately hoses a ep0 card if one happens to be there instead. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3c509b getting `eeprom failed to come ready' in current
On Fri, 26 Nov 1999, Poul-Henning Kamp wrote: I'm going to look closer at those two drivers and find the place where they disagree with if_ep. They don't disagree, they do some stuff to some registers to detect their respective hardware, which unfortunately hoses a ep0 card if one happens to be there instead. By 'disagree' I meant 'where they conflict eachother'. :) What is really needed here is for the resource manager to handle 'requests' as well as allocations. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Boot error
First things first; try using English for your problem reports. A large slice of the community that might be able to answer your questions don't use it as their first language, and by using leet-speek you immediately eliminate them as a source of help. Before I go do a fresh SNAP install, I wanted to see if there was an easier way to fix this problem... My -current box was a celeron...I had to switch the celeron and mboard to my windoze machine to get a vidcard werkin...I recompiled the kernel to 486, 586, and 686, and moved the HD, the cards, etc, over to the K6-2 400 I had...now, everytime at boot, before it even prompts for which OS to start, it has a bootloader problem...if I recall it was something like: BTX 1.0.0 BTX Loader 1.0.1 then "System Halted" I tried the fixit floppy, etc, and that partially worked, but locked when it was mounting the filesystem. I'm sorry that I cant provide any more info...I only have 1 monitor and cant copy/paste between 2 pcs. I'm sorry, but without a lot more information all I can say is "you done something wrong". You might start with an exhaustive list of the relevant hardware in the actual system in question, followed by the actual set of physical changes which took it from "working" to "not working". We're not telepathic, and we don't have the time to hunt you down and steal all your hardware to solve your own problems, so you're going to have to help us out here. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
more observations to the zip-drive problem: First the relevant dmesg-line: atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 afd0: IOMEGA ZIP 100 ATAPI/23.D rewriteable drive at ata0 as master afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S afd0: 4096KB/s, transfer limit 64 blks, PIO afd0: Medium: Unknown media (0x0) second : the first 512 bytes of /dev/rfd* are identical, here are checksums: 61088 1 rafd0.txt 61088 1 rafd0s4.txt here are some lines of the files in emacs hexl-mode: : eb2e 4950 4152 5420 636f 6465 2030 3039 ..IPART code 009 0010: 202d 2049 6f6d 6567 6120 436f 7270 6f72 - Iomega Corpor 0020: 6174 696f 6e20 2d20 3131 2f32 332f 3930 ation - 11/23/90 0030: fafc 8cc8 8ed0 bc00 7c8e d88e c0b9 0002 |... the zip disks where formatted under windows, of course. trying to mount the zip-drive gives: msdos: /dev/afd0s4: Invalid argument -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
It seems F. Heinrichmeyer wrote: more observations to the zip-drive problem: First the relevant dmesg-line: atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 afd0: IOMEGA ZIP 100 ATAPI/23.D rewriteable drive at ata0 as master afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B/S afd0: 4096KB/s, transfer limit 64 blks, PIO afd0: Medium: Unknown media (0x0) That looks like it should... second : the first 512 bytes of /dev/rfd* are identical, here are checksums: 61088 1 rafd0.txt 61088 1 rafd0s4.txt here are some lines of the files in emacs hexl-mode: : eb2e 4950 4152 5420 636f 6465 2030 3039 ..IPART code 009 0010: 202d 2049 6f6d 6567 6120 436f 7270 6f72 - Iomega Corpor 0020: 6174 696f 6e20 2d20 3131 2f32 332f 3930 ation - 11/23/90 0030: fafc 8cc8 8ed0 bc00 7c8e d88e c0b9 0002 |... the zip disks where formatted under windows, of course. trying to mount the zip-drive gives: msdos: /dev/afd0s4: Invalid argument This has appeared before IIRC, I've no idea why this doesn't work, but I can rig up my ZIP drive, but I dont have DOS nor WINDOWS, do it fail also if the disk is formatted under FreeBSD ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AHC0 fireworks ?
On 20 Nov 1999 11:20:23 +0200, Gianmarco Giovannelli [EMAIL PROTECTED] wrote: But I have now a lot of errors (as you can see in this logs) on my scsi chain. I had never experienced such things in the near past (even if as an old current user sometimes I see also worse things :-) Btw I don't see in the current mailing list threads about iussues on the scsi subsystem recently so it can be a problem related to my hardware (even if I didn't experience it before)... Nov 20 09:17:49 gmarco /kernel: ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter irq 19 at device 6.0 on pci0 Nov 20 09:17:49 gmarco /kernel: (da0:ahc0:0:0:0): parity error during Data-In phase. Please look up the following discussion in freebsd-questions. I'm reading these lists on Usenet, so I'm going to give you Usenet message-Id's: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] The last one is a log extract quite similar to yours ... it's Adaptec that's seemingly causing the problems here. I'm running 3.3-RELEASE, and problems started on two machines with a lot of disk usage (both news related) when I upgraded from 3.1/3.2 - 3.3. The fact that this hasn't been fixed anywhere in the cvsup route makes me rather sad. I'm really waiting for fixes/patches .. -- - Ben C. O. Grimm - [EMAIL PROTECTED] - - Wirehub! Internet Engineering - http://www.wirehub.net/ - - Wirehub! Backbone --- http://doema.wirehub.net/wirehub/ - - Private Ponderings --- http://libertas.wirehub.net/ - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
On Fri, 26 Nov 1999, Soren Schmidt wrote: It seems F. Heinrichmeyer wrote: more observations to the zip-drive problem: First the relevant dmesg-line: I'm also still having a small problem with the ata driver and my HP Colorado 8G. I have it hanging off an ATAPI CDROM as a slave. The dmesg says: ata-pci1: AcerLabs Aladdin IDE controller irq 0 at device 11.0 on pci0 ata-pci1: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=00 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0xc ata0 at 0x01f0 irq 14 on ata-pci1 This indicates that it sees two ATAPI devices. But when the system starts up, all I get is: ata0-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: DELTA OPC-K101/ST1 F/W by OIPD/VER-3.40 CDROM drive at ata0 as master acd0: read 687KB/s (6875KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked No tape drive is found. All worked well with the old drivers. == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED] Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
It seems Bryan Liesner wrote: On Fri, 26 Nov 1999, Soren Schmidt wrote: It seems F. Heinrichmeyer wrote: more observations to the zip-drive problem: First the relevant dmesg-line: I'm also still having a small problem with the ata driver and my HP Colorado 8G. I have it hanging off an ATAPI CDROM as a slave. The dmesg says: ata-pci1: AcerLabs Aladdin IDE controller irq 0 at device 11.0 on pci0 ata-pci1: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=00 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0xc ata0 at 0x01f0 irq 14 on ata-pci1 This indicates that it sees two ATAPI devices. But when the system starts up, all I get is: ata0-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: DELTA OPC-K101/ST1 F/W by OIPD/VER-3.40 CDROM drive at ata0 as master acd0: read 687KB/s (6875KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked No tape drive is found. All worked well with the old drivers. Hmm, what can I say, I use a simlar setup, just with either a Seagate or an Onstream tape, both work well. You should probably sprinkle a couple of printf's in the atapi probe code and the tape driver an see where it fails... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
On 26 Nov, Soren Schmidt wrote: trying to mount the zip-drive gives: msdos: /dev/afd0s4: Invalid argument This has appeared before IIRC, I've no idea why this doesn't work, but I can rig up my ZIP drive, but I dont have DOS nor WINDOWS, do it fail also if the disk is formatted under FreeBSD ?? I didn´t tried to reproduce this recently, but you could try to format the ZIP-disc with mtools: mformat -t 96 -h 64 -s 32 -H 32 z: Fritz: could you post the output of "minfo z:" (ata-controller)? Here´s the one with wd (perhaps a diff between them gives someone a hint): ---snip--- (101) netchild@ttyp2 minfo z: device information: === filename="/dev/rwfd0s4" sectors per track: 32 heads: 64 cylinders: 96 mformat command line: mformat -t 96 -h 64 -s 32 -H 32 z: bootsector information == banner:"(?6;1IHC" sector size: 512 bytes cluster size: 4 sectors reserved (boot) sectors: 1 fats: 2 max available root directory slots: 512 small size: 0 sectors media descriptor byte: 0xf8 sectors per fat: 192 sectors per track: 32 heads: 64 hidden sectors: 32 big size: 196576 sectors physical drive id: 0x80 reserved=0x0 dos4=0x29 serial number: 39BC1102 disk label="ZIP-100" disk type="FAT16 " ---snip--- And here the boot-message: ---snip--- wdc0: unit 1 (atapi): IOMEGA ZIP 100 ATAPI/23.D, removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set ---snip--- Søren, I assume the ata-controller knows about the last line, right? Bye, Alexander. -- I'll be damned if I can't win when I'm keeping score. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: observations with the ata-driver (hd and zip drive)
It seems Alexander Leidinger wrote: I didn´t tried to reproduce this recently, but you could try to format the ZIP-disc with mtools: mformat -t 96 -h 64 -s 32 -H 32 z: I'll dig out my ZIP drive tonight a do some testing... ---snip--- wdc0: unit 1 (atapi): IOMEGA ZIP 100 ATAPI/23.D, removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set ---snip--- Søren, I assume the ata-controller knows about the last line, right? It does, and it also says so in the probe... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD-audit mailing list set up.
Hello FreeBSD person! We now have a mailing list for the discussion of the FreeBSD Audit Project. Thanks to Jon Bresler, our postmaster! All of you who want to contribute to this project, please sign up. There was a very heartening response to the announcement, and a few slowcoaches even got stuck in straight away. Wonderful! Topics for discussion will be audit methodology, audit progress, and if there are significant events, they will be announced there. If something is of relevance to -current or -security, then it may be discussed there _instead_ _of_ -audit. Crossposting, flaming, -stable and other offtopic content is not allowed. Lets keep the signal ratio high! I'll give it a day or two, then kick off a summary of the responses seen to my first announcement of the Audit Project in -Current. As usual, to sign up you could: $ echo subscribe freebsd-audit | mail -s Subscribe [EMAIL PROTECTED] Thanks! M To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3c509b getting `eeprom failed to come ready' in current
On Fri, 26 Nov 1999 03:29:16 -0500 (EST), "Matthew N. Dodd" [EMAIL PROTECTED] said: What is really needed here is for the resource manager to handle 'requests' as well as allocations. It does. That's the difference between `allocate' and `activate'. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3c509b getting `eeprom failed to come ready' in current
On Fri, 26 Nov 1999, Thierry Herbelot wrote: If it is not possible to hardwire the ep boards, how do I recognize them in a "router" setting ? (I have an oldish PC with to ep boards, used as a WAN simulator, with dummynet : how do I tell ep0 form ep1 ?) The ISA enumerator detects cards in order of ethernet MAC address. I don't have two PnP cards so I'm not sure of the order that the PnP enumerator uses. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Guido's recent 3.3.3 IpFilter commit
Chances are I'm missing something or a step, but I've ran out of ideas and mailing lists to search through. I'm running -current as of today with IPFilter 3.3.3 (big thanks to Guido for adding it back into FreeBSD's tree and updating it to the latest version). It starts successfully, but when I try to load any rule sets (or remove rules with if -Fa) I get: open device: Device not configured ioctl(SIOCIPFFL): Bad file descriptor This was a move from -current Oct. 10 (right before ipfilter was removed from the kernel), so I know it works with IPFilter. BFP is compiled as well as options IPFILTER in the kernel, and the rule set worked with the oct. 10 version of IPFilter. There are /dev/bpf? devices, as well as /dev/ipl etc. What have I missed? Any help/suggestions/tips would be appreciated. Thanks. Davec [EMAIL PROTECTED] Get your free email from AltaVista at http://altavista.iname.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Promotion offer
Good moning! Today I visited Your web-site and thought "May be it needs promotion?" I made some automatic promotion tools and needs to improve and test it. If You interesting a web advertising and promotion You can visit http://www.terra.ee/noo/ and launch automatic promotion by filling a form and placing small text in Your page. First stage recommended, it is free of charge. May be my know-how is greate, may be it is nothing. Sorry, if You will decide this is spam. My e-mail is [EMAIL PROTECTED], this is one time offer to e-mail from Your web page. Any questions are welcome. Best regards Artur Frolov To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Boot error
Ok...for hardware, all I have in the machine is: A Linksys 10/100 ethernet (uses pn0) A SCSI card (uses bt0) A S3 Virge video card A FIC VA-503+ motherboard w/ 32meg PC66 sdram and a K6-2 400 the only thing changed between the 2 machines was the other was a Shuttle Socket 370 motherboard, and a Celeron 366 cpu. Everything was moved from one case/motherboard to the other case/motherboard. The kernel had "ata" compiled in, the options for my hardware, and the basic floppy and video, nothing that I though was unusual. Sorrry about the way I typed before...I actually talk like that (or worse) half the time, and I have to remember when to talk/type normally. Doug - Original Message - From: "Mike Smith" [EMAIL PROTECTED] To: "Douglas Kuntz" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, November 26, 1999 3:32 AM Subject: Re: Boot error First things first; try using English for your problem reports. A large slice of the community that might be able to answer your questions don't use it as their first language, and by using leet-speek you immediately eliminate them as a source of help. Before I go do a fresh SNAP install, I wanted to see if there was an easier way to fix this problem... My -current box was a celeron...I had to switch the celeron and mboard to my windoze machine to get a vidcard werkin...I recompiled the kernel to 486, 586, and 686, and moved the HD, the cards, etc, over to the K6-2 400 I had...now, everytime at boot, before it even prompts for which OS to start, it has a bootloader problem...if I recall it was something like: BTX 1.0.0 BTX Loader 1.0.1 then "System Halted" I tried the fixit floppy, etc, and that partially worked, but locked when it was mounting the filesystem. I'm sorry that I cant provide any more info...I only have 1 monitor and cant copy/paste between 2 pcs. I'm sorry, but without a lot more information all I can say is "you done something wrong". You might start with an exhaustive list of the relevant hardware in the actual system in question, followed by the actual set of physical changes which took it from "working" to "not working". We're not telepathic, and we don't have the time to hunt you down and steal all your hardware to solve your own problems, so you're going to have to help us out here. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AHC0 fireworks ?
Ben C. O. Grimm wrote... On 20 Nov 1999 11:20:23 +0200, Gianmarco Giovannelli [EMAIL PROTECTED] wrote: But I have now a lot of errors (as you can see in this logs) on my scsi chain. I had never experienced such things in the near past (even if as an old current user sometimes I see also worse things :-) Btw I don't see in the current mailing list threads about iussues on the scsi subsystem recently so it can be a problem related to my hardware (even if I didn't experience it before)... Nov 20 09:17:49 gmarco /kernel: ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter irq 19 at device 6.0 on pci0 Nov 20 09:17:49 gmarco /kernel: (da0:ahc0:0:0:0): parity error during Data-In phase. Please look up the following discussion in freebsd-questions. I'm reading these lists on Usenet, so I'm going to give you Usenet message-Id's: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] The last one is a log extract quite similar to yours ... it's Adaptec that's seemingly causing the problems here. I'm running 3.3-RELEASE, and problems started on two machines with a lot of disk usage (both news related) when I upgraded from 3.1/3.2 - 3.3. The fact that this hasn't been fixed anywhere in the cvsup route makes me rather sad. I'm really waiting for fixes/patches .. There was a corruption problem caused by a bug in the 7890/1 chips that Justin worked around in the ahc driver shortly after 3.3 went out the door. This generally only manifested itself under high load. Your problem is probably very different than Gianmarco's problem, since he has the fix. His problem is most likely cabling or termination. In any case, you need to upgrade to the latest -stable, or wait until 3.4 comes out to fix your problem. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ST-506, ESDI and BAD144 ?
In message [EMAIL PROTECTED], Greg Lehey writes: On Wednesday, 24 November 1999 at 10:39:44 +0100, Poul-Henning Kamp wrote: So I would like to propose that we discontinue support for ST-506, ESDI disks and BAD144 bad-sector remapping starting with the 4.0 release. So, is anyone running -current on ESDI or ST-506 disks in actual applications (as opposed for the gadget/novelty thrill or testing purposes) ? I don't suppose it would be that big a deal to remove the old driver, but what speaks against leaving it in the tree along with a comment in the GENERIC config file saying "if you use antediluvial disk hardware, you may prefer to use an old driver too"? Well, couldn't we just as well say "if you use pre-cambrian disks please stick with the 3.X release branch" ? There are many indicies which support killing the wd.c driver: New hardware is supported (much) better by ata driver The ATAPI stuff in wd.c is a rather crude hack, ata driver handles it better. Wd.c is the only driver which keeps the BAD144 code alive in our tree, and nobody uses it. Modern drives do their own bad sector handling. The kind of hardware it supports which the ata doesn't is usually found in machines with less than 32Mbyte of RAM anyway, running 4.0 on such a machine is not even close to fun. (And modern motherboards/bioses seem to have lost the ability to handle old disks, at least the ones I tried here in my lab.) There is a long time until 5.0 which is our next chance. so, speak now, or forever bite your tongue... -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
World breakage in libpam?
Seeing this trying to build world, cvsup'd earlier today. cc -O -pipe -static -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall -I/usr/src/libexec/ftpd/../../contrib-crypto/telnet -DINTERNAL_LS -Dmain=ls_main -I/usr/src/libexec/ftpd/../../bin/ls -I/usr/obj/usr/src/tmp/usr/include -o ftpd ftpd.o ftpcmd.o logwtmp.o popen.o skey-stuff.o ls.o cmp.o print.o stat_flags.o util.o -lskey -lmd -lcrypt -lutil -lpam /usr/obj/usr/src/tmp/usr/lib/libpam.a(pam_static_modules.o): In function `_pam_get_static_sym': pam_static_modules.o(.text+0x299): undefined reference to `rad_create_request' pam_static_modules.o(.text+0x2af): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x2cc): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x2e9): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x319): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x32d): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x34d): undefined reference to `rad_put_attr' pam_static_modules.o(.text+0x363): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x379): undefined reference to `rad_put_int' pam_static_modules.o(.text+0x394): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x3db): undefined reference to `rad_cvt_string' pam_static_modules.o(.text+0x40d): undefined reference to `rad_get_attr' pam_static_modules.o(.text+0x438): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x4b7): undefined reference to `rad_cvt_string' pam_static_modules.o(.text+0x4f2): undefined reference to `rad_get_attr' pam_static_modules.o(.text+0x50a): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x760): undefined reference to `rad_open' pam_static_modules.o(.text+0x789): undefined reference to `rad_config' pam_static_modules.o(.text+0x79d): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x7dd): undefined reference to `rad_send_request' pam_static_modules.o(.text+0x821): undefined reference to `rad_close' pam_static_modules.o(.text+0x881): undefined reference to `rad_close' pam_static_modules.o(.text+0x8ab): undefined reference to `rad_close' pam_static_modules.o(.text+0x8bc): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x8d5): undefined reference to `rad_close' pam_static_modules.o(.text+0x8f4): undefined reference to `rad_close' pam_static_modules.o(.text+0xb07): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xb23): undefined reference to `tac_close' pam_static_modules.o(.text+0xb4b): undefined reference to `tac_get_msg' pam_static_modules.o(.text+0xb5e): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xb77): undefined reference to `tac_close' pam_static_modules.o(.text+0xb96): undefined reference to `tac_set_msg' pam_static_modules.o(.text+0xbb0): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xbc9): undefined reference to `tac_close' pam_static_modules.o(.text+0xc60): undefined reference to `tac_open' pam_static_modules.o(.text+0xc90): undefined reference to `tac_config' pam_static_modules.o(.text+0xca7): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xcc3): undefined reference to `tac_create_authen' pam_static_modules.o(.text+0xcda): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xcf6): undefined reference to `tac_close' pam_static_modules.o(.text+0xd09): undefined reference to `tac_set_user' pam_static_modules.o(.text+0xd32): undefined reference to `tac_set_port' pam_static_modules.o(.text+0xd5b): undefined reference to `tac_set_rem_addr' pam_static_modules.o(.text+0xd84): undefined reference to `tac_send_authen' pam_static_modules.o(.text+0xd9b): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xde8): undefined reference to `tac_close' pam_static_modules.o(.text+0xe48): undefined reference to `tac_close' pam_static_modules.o(.text+0xf52): undefined reference to `tac_close' pam_static_modules.o(.text+0xfbc): undefined reference to `tac_get_data' pam_static_modules.o(.text+0x101c): undefined reference to `tac_close' *** Error code 1 Stop in /usr/src/libexec/ftpd. *** Error code 1 Stop in /usr/src/libexec. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sv: Dr Neuhaus niccy go not recognized
On Sun, 7 Nov 1999, German Tischler wrote: On Sun, Nov 07, 1999 at 06:27:37PM +0100, Leif Neland wrote: I'd like to test, So how do I proceed from here? Get the latest i4b-dev snapshot (00.83.11), get my patches from http://www.mayn.franken.de/home/tanis/i4b-11.tar.gz, get a recent current source tree, unpack i4b, unpack the layer1 patches over it, use the overinstall script, use device isic0 in your kernel config file (no at isa? or similiar). Compile the userland programs and install them, build a kernel and see if it works, and tell me what goes wrong. Sorry, I have not had any time to do much testing; I now use a non-pnp itk instead. I just wanted to do some dialin-logging on my voice-phones. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3c509b getting `eeprom failed to come ready' in current
On Fri, 26 Nov 1999, Thierry Herbelot wrote: If it is not possible to hardwire the ep boards, how do I recognize them in a "router" setting ? (I have an oldish PC with to ep boards, used as a WAN simulator, with dummynet : how do I tell ep0 form ep1 ?) Look for the "ether" (mac-adress): # ifconfig -a ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.14 netmask 0xff00 broadcast 192.168.0.255 ether 00:80:ad:50:40:cf Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Route table leaks
I think I've finally found the route table leak. At least I found _a_
leak, and I think it's the one that's been plaguing cvsup-master. I
have a question or two (see below) before I commit the fix.
Here's how to leak a route table entry. Establish a TCP connection
with another machine so that you have a cloned route to that host.
With the connection idle, use "route delete" to remove the cloned
route. The route disappears from the routing table, but it is
not freed. (The Leak.) Now cause some packets to travel on the
connection. A new cloned route is created and added to the routing
table.
Each time you do that, you leak a struct rtentry and also a 32-byte
chunk that's used to hold a couple of address structures. Routed is
doing these route deletions regularly on cvsup-master. I haven't
tried to figure out why.
The leak is in rtalloc() and rtalloc_ign(), and here's the patch I'm
using to fix it:
Index: route.c
===
RCS file: /home/ncvs/src/sys/net/route.c,v
retrieving revision 1.53
diff -u -r1.53 route.c
--- route.c 1999/08/28 00:48:28 1.53
+++ route.c 1999/11/27 01:21:56
@@ -88,8 +88,16 @@
rtalloc(ro)
register struct route *ro;
{
- if (ro-ro_rt ro-ro_rt-rt_ifp (ro-ro_rt-rt_flags RTF_UP))
- return; /* XXX */
+ struct rtentry *rt;
+ int s;
+
+ if ((rt = ro-ro_rt) != NULL) {
+ if (rt-rt_ifp != NULL rt-rt_flags RTF_UP)
+ return;
+ s = splnet();
+ RTFREE(rt);
+ splx(s);
+ }
ro-ro_rt = rtalloc1(ro-ro_dst, 1, 0UL);
}
@@ -98,8 +106,16 @@
register struct route *ro;
u_long ignore;
{
- if (ro-ro_rt ro-ro_rt-rt_ifp (ro-ro_rt-rt_flags RTF_UP))
- return; /* XXX */
+ struct rtentry *rt;
+ int s;
+
+ if ((rt = ro-ro_rt) != NULL) {
+ if (rt-rt_ifp != NULL rt-rt_flags RTF_UP)
+ return;
+ s = splnet();
+ RTFREE(rt);
+ splx(s);
+ }
ro-ro_rt = rtalloc1(ro-ro_dst, 1, ignore);
}
The original code was jamming a new pointer into ro-ro_rt, but it
didn't free the old rtentry that was referenced there.
Now for my questions:
1. Do I really need the splnet calls around RTFREE?
2. To eliminate all the duplicated code, shall I make rtalloc just
call rtalloc_ign(ro, 0UL)? I assume that was avoided originally for
performance reasons, but now there's more code than before.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra Co., Inc.Seattle, Washington USA
"No matter how cynical I get, I just can't keep up."-- Nora Ephron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
