Re: Bugfixed AMI MegaRAID driver for -stable available
On Tue, 14 Dec 1999, Mike Smith wrote: > > Due to a programming error, the previous release of the AMI MegaRAID > driver for FreeBSD 3.x would not work with Enterprise 418 and 428 > series controllers. This has been corrected, and the new driver is > available at > > http://www.freebsd.org/~msmith/RAID/ami/amr-stable-991214.tar.gz Will this make it into 3.4? Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: how to rewrite the data field replaceable unit?
On Tue, 14 Dec 1999, Rahul Dhesi wrote: > Mike Smith <[EMAIL PROTECTED]> writes: > > >>(da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data field >replaceable unit: 20 sks:80,a0 > ... > > >That's two things, 'data' and 'field replaceable unit'. The FRU code > >tells you which part of the drive is failing - in this case the vendor > >code for the broken bit is '20'. > > Thanks. > > A suggestion to the Device Driver Gods: Please make error messages > understandable to the rest of us. How is this not understandable? It presents the problem, "Unrecovered read error," and even is nice enough to suggest a solution, "recommend rewrite the data." How would you rewrite this to be more "understandable", yet still provide the same amount of information? This is like the newbies that ask "What does it mean when it says '/usr: file system full'?" :-/ Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org PS: If you like terse error messages, try Linux. Things go wrong and you *might* get a message. And if you do, it *might* bother to decode the ASC for you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Netgear FA410TXc
> Anyone now if the this PCMCIA ethernet card is going to make it in to > the main source tree. I have a laptop with this card and am currently > running OpenBSD which is supported. The problem is that my habits and > openbsd arre not the same. I know the card is supported in PAO but I > like staying with STABLE more than release. > > If anyone has any way of knowing if this is going to happen or if there > is a way to stay STABLE with PAO I am all ears. I'm using one right now under -current; it should probably work on -stable as well. -- \\ 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-stable" in the body of the message
Netgear FA410TXc
Anyone now if the this PCMCIA ethernet card is going to make it in to the main source tree. I have a laptop with this card and am currently running OpenBSD which is supported. The problem is that my habits and openbsd arre not the same. I know the card is supported in PAO but I like staying with STABLE more than release. If anyone has any way of knowing if this is going to happen or if there is a way to stay STABLE with PAO I am all ears. TIA -- --- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() --- Q: Best way to secure a Linux box? A: Place it behind a FreeBSD firewall. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problem with psm0
On Tue, 14 Dec 1999, Kazutaka YOKOTA wrote: > > >I have two systems, both now running 3.4-RC (built from the most recent > >source I had via CTM a couple of hours ago). I also have two very similar > >mice. However: > [...] > >system1 is a Gigabyte 71X Athlon motherboard (AMD chipset) > >system2 is a PC-Chips socket-7 motherboard (SiS chipset) > > > >mouse1 is a MouseSystems M5 PS/2 optical mouse (model 403011-001) > >mouse2 is a MouseSystems type 2544 PS/2 optical mouse (model 404273-001) > >Both have been in use for some time on FreeBSD 2.2 systems (the main > >difference between mouse1 and mouse2 is that mouse1 cost about 4 times as > >much and has slightly better buttons!). > > When you were running FreeBSD 2.2, were you using the above > motherboards? No, system 1 is brand-new (when upgrading from 2.2 to 3.x I replaced the whole machine, just keeping the kbd/mouse/screen). I just tried booting a 2.2.8-RELEASE CD in the problem machine, and it didn't detect psm0 either, so this is a red herring. I then went looking for a hardware problem. I thought I was onto something when I measured the +5V on-load voltage at the PS/2 keyboard/mouse ports as only 4.71V: this motherboard seems to have a high-resistance fuse. However, soldering a wire to bypass the fuse gave me a solid 5.01V but no change in the behaviour. I suppose I ought to try installing Windows and see if the mouse works there, though that will take some time as this is currently an all-SCSI machine. > >System1/Mouse1: > [...] > >psm0: current command byte:0047 > >kbdc: TEST_AUX_PORT status: > >kbdc: RESET_AUX return code:00fa > >kbdc: RESET_AUX status: > >kbdc: DIAGNOSE status:0055 > >kbdc: TEST_KBD_PORT status: > >psm0: failed to reset the aux device. > >psm0 not found > > Do you by any chance use any console switch? We may have a timing > problem here. Would you send us the full dmesg output? I do not have a switch: the mouse is plugged directly into the motherboard mouse port. Full dmesg output is attached. > In the meantime, try adding the following options in your kernel > configuration file. > > options KBDIO_MAXWAIT 10 > > The default value is 5. Increase the value if your mouse is not still > recognized. I assume you mean "options KBD_MAXWAIT=10" ? I tried this, but it had no effect. I also tried other values, including: options KBD_MAXWAIT=10 options KBD_RESETDELAY=1000 options KBD_MAXRETRY=10 but again no obvious effect (other than a noticeable delay at that point in the boot sequence). Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-RC #7: Wed Dec 15 00:46:57 GMT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ROCKET Calibrating clock(s) ... TSC clock: 598896444 Hz, i8254 clock: 1193301 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: AMD-K7(tm) Processor (598.84-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x612 Stepping = 2 Features=0x81f9ff AMD Features=0xc040<,,3DNow!> Data TLB: 24 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x002e8000 - 0x07ff5fff, 131129344 bytes (32014 pages) avail memory = 127516672 (124528K bytes) Found BIOS32 Service Directory header at 0xc00fafc0 Entry = 0xfb430 (0xc00fb430) Rev = 0 Len = 1 PCI BIOS entry at 0xb460 SMIBIOS header at 0xc00f5040 Version 2.1 Table at 0xf0800, 39 entries, 958 bytes, largest entry 74 bytes DMI header at 0xc00f5050 Version 2.1 Table at 0xf0800, 39 entries, 958 bytes Other BIOS signatures found: ACPI: $PnP: 000fc0a0 Preloaded elf kernel "kernel" at 0xc02cf000. VESA: information block 56 45 53 41 00 02 00 01 00 01 00 00 00 00 22 00 00 01 80 00 00 01 0b 01 00 01 21 01 00 01 2a 01 00 01 00 01 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 05 01 16 01 17 01 18 01 07 01 19 01 VESA: 3 mode(s) found Pentium Pro MTRR support enabled Math emulator present pci_open(1):mode 1 addr port (0x0cf8) is 0x80003840 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=80] is there (id=70061022) Probing for devices on PCI bus 0: found-> vendor=0x1022, dev=0x7006, revid=0x23 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 map[0]: type 3, range 32, base d800, size 26 map[1]: type 3, range 32, base e3101000, size 12 map[2]: type 4,
Bugfixed AMI MegaRAID driver for -stable available
Due to a programming error, the previous release of the AMI MegaRAID driver for FreeBSD 3.x would not work with Enterprise 418 and 428 series controllers. This has been corrected, and the new driver is available at http://www.freebsd.org/~msmith/RAID/ami/amr-stable-991214.tar.gz There are no other changes in this release. -- \\ 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-stable" in the body of the message
Re: how to rewrite the data field replaceable unit?
Mike Smith wrote in list.freebsd-stable: > > A suggestion to the Device Driver Gods: Please make error messages > > understandable to the rest of us. > > That's kinda difficult, actually. Error messages need to be accurate and > understandable to people that understand what's really going on. It's > not the job of an error message to explain how the hardware works. Is it really that difficult to (at least) insert a comma or something before "field replaceable unit"? I got bitten by that unrecognizable error message once, too... Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: how to rewrite the data field replaceable unit?
On Tue, Dec 14, 1999 at 09:57:11AM -0800, Mike Smith wrote: > > Mike Smith <[EMAIL PROTECTED]> writes: > > > > >>(da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data field >replaceable unit: 20 sks:80,a0 > > ... > > > > >That's two things, 'data' and 'field replaceable unit'. The FRU code > > >tells you which part of the drive is failing - in this case the vendor > > >code for the broken bit is '20'. > > > > Thanks. > > > > A suggestion to the Device Driver Gods: Please make error messages > > understandable to the rest of us. > > That's kinda difficult, actually. Error messages need to be accurate and > understandable to people that understand what's really going on. It's > not the job of an error message to explain how the hardware works. To add to that: FRU codes are vendor/product unique. So in this case you cannot be more specific from the driver's point of view. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: What all does installworld fail to install?
On Tue, Dec 14, 1999 at 11:53:08AM -0500, Michael R. Wayne wrote: > 3.4RC, using NFS and a box which has already had >"make buildworld ; make installworld" > done on it. What am I missing: You need to do ``make reinstall'' instead of ``make installworld''. Check for the pathnames, if you have /usr/src symlinked somewhere, you need to create that similar on the boxes where you do the NFS mounts. The pathnames are stored in /usr/obj extended to the original names, not as the symlinks. Regards, Martin -- /| /|| /| /,,You know, there's a lot of opportunities, / |/ | artin |/ |/ elk if you're knowing to take them, you know, there's a lot of opportunities, Freiberg/Saxony, Germany if there aren't you can make them, [EMAIL PROTECTED] / [EMAIL PROTECTED] make or break them!'' (Tennant/Lowe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
