Re: Moused broken on alpha
On Thu, 18 Apr 2002, Dermot McNally wrote: Folks, Moused refuses to build on alpha because the symbol MOUSE_PROTO_JOGDIAL (defined in the Intel version of mouse.h) isn't defined. Defining it fixes the problem, but is this the correct fix? Nobody else seems to have been bitten by this one... If I am correct jogdial is the funky wheel on a vaio, which aren't made with alpha cpu's ( or hell has frozen ) -- Sten Spans What does one do with ones money, when there is no more empty rackspace ? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Belkin 8-port KVM = keyboard inactive
On Thu, Apr 18, 2002 at 03:46:45PM -0500, Jim King wrote: Is the problem in the FreeBSD probe or this particular KVM switch? I don't recall having this problem with my Belkin Omnicube. Is anybody having problems with other KVM switches besides the Omniview 8-port? How long ago? This problem only started when the flags 0x1 lever was pulled. It won't bother you unless you have that in your kernel config. -- Christopher Masto CB461C61 8AFC E3A8 7CE5 9023 B35D C26A D849 1F6E CB46 1C61 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RE: Belkin 8-port KVM = keyboard inactive
It may be a design issue with the Omniview, but I would assume FreeBSD's checks are more stringent than those of Windows boxes -- I've got NT 4.0 and 2k on the same 8-port and they reboot remotely with no keyboard/mouse problems. -Yanek. -Original Message- From: Jim King [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 4:47 PM To: Christopher Masto; Kenneth D. Merry Cc: Yanek Korff; '[EMAIL PROTECTED]' Subject: Re: Belkin 8-port KVM = keyboard inactive Christopher Masto [EMAIL PROTECTED] wrote: On Wed, Apr 17, 2002 at 07:48:58PM -0600, Kenneth D. Merry wrote: I don't know if this has anything to do with your problem, but some of the Belkin Omniview 8 port KVM switches were manufactured with two EEPROMs swapped. See John Polstra's description of the message on -hackers: No, he had it right; it's the atkbd flags. It's a pain in the ass. I'm completely ignorant in this area, but obviously there is a difference between no keyboard and KVM switched to different port. The BIOS, for example, complains about the former but not the latter. I'd guess FreeBSD is requiring more of the keyboard than whatever the cheap KVM trick keyboard is providing. I wonder if FreeBSD's probe could be made less demanding so that it doesn't kill the keyboard driver in the KVM case. That would hopefully satisfy both the USB keyboard situation and those of us using these KVM switches. Is the problem in the FreeBSD probe or this particular KVM switch? I don't recall having this problem with my Belkin Omnicube. Is anybody having problems with other KVM switches besides the Omniview 8-port? Jim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Moused broken on alpha
Dermot McNally writes: Folks, Moused refuses to build on alpha because the symbol MOUSE_PROTO_JOGDIAL (defined in the Intel version of mouse.h) isn't defined. Defining it fixes the problem, but is this the correct fix? Nobody else seems to have been bitten by this one... The MOUSE_PROTO_JOGDIAL definition was forgotten about in the original MFC of some extra mouse support. ru caught the problem and added it to sys/alpha/include/Attic/mouse.h ( 1.16.2.2) 2 days ago. If you want to have everything pristeen, update your sources rebuild world. If not, I'm sure your definition should be fine.. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Trying SRA secure login:
How do I configure this to let me in from a remote telnet session Telnetting to the system gives me this , and then I can't login Trying SRA secure login: thanks Robert --- Quantum Radio: World Music with a difference. http://quantum-radio.net/ Now Playing: Jason Carter - Pilgrimage To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: options PNPBIOS
From: Drew Tomlinson [EMAIL PROTECTED] Date: Thu, 18 Apr 2002 10:24:00 -0700 Sender: [EMAIL PROTECTED] I compiled a kernel with options PNPBIOS as instructed in LINT to get my sound card working. The machine is a Pentium II Pro. I have ensured that the BIOS is configured for PNP OS but still get these messages: unknown: PNP can't assign resources unknown: PNP0303 can't assign resources unknown: PNP0f13 can't assign resources unknown: PNP0c01 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0400 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources I've searched Google and found others with this problem but no solutions. Is PNPBIOS documented somewhere? Where should I start? These are always present with PNPBIOS as there are several things that identify themselves via PNP that FreeBSD does not know/care about. They can almost always be ignored. As I understand it, PNPBIOS and having BIOS configured for PNP are very different things and the general advice I have seen is to not turn on PNP in BIOS. As I understand it, PNPBIOS causes FreeBSD to query BIOS for device information on all device. It eliminates the need to specify all sorts of stuff like iomem, irq, and drq in the kernel for ISA devices. I generally find it annoying and go ahead and define all of the parameters in my kernel config. Of course, it's entirely possible that I don't understand it. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: RAID spanning over two 2400A's supported?
On Wed, Apr 17, 2002 at 04:14:01AM -0500, Mark Nipper wrote: On Wed, Apr 17, 2002 at 10:57:28AM +0300, Vallo Kallaste wrote: We're considering Adaptec 2400A's for new server. Will the asr(4) driver support more than one controller and RAID spanning over two controllers? Our final goal is 8 disk RAID-5 array, not expecting great I/O but large storage area. I guess it's possible to concat or stripe the two RAID-5 arrays with vinum in case spanning is not supported? Every bit of advice will be welcome! I just recently assembled a system as our workgroup server using the Adaptec 2400A and four Western Digital Special Edition 120GB 7200RPM ATA hard drives with 8MB cache each. I must say it's fantastic! :) Good to know FreeBSD supports the 2400A. Wonder how it compares with the 3Ware 7000 series controllers (which offers a 4 and 8-port card). -- albert chin ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
3ware problem
ASUS P2B-DS mobo, dual p3. Promise fasttrak 66, 2 intel 10/100. Just upgraded to 4.5-stable as of 4/17, and put in a 3ware 7850 running 7.4 When it boots, right after the 3ware probes, I get this stream of errors (apparently unceasing): Waiting 15 seconds for SCSI devices to settle twe0: PCI parity error: Reseat card, move card or buggy device present.twed0: RAID5, Normal on twe0 twed0: 293112MB (600293760 sectors) twe0: command interrupt twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: unexpected status bit(s) 80PCIPERR Not sure what to do here. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Belkin 8-port KVM = keyboard inactive
Christopher Masto wrote: On Thu, Apr 18, 2002 at 03:46:45PM -0500, Jim King wrote: Is the problem in the FreeBSD probe or this particular KVM switch? I don't recall having this problem with my Belkin Omnicube. Is anybody having problems with other KVM switches besides the Omniview 8-port? How long ago? This problem only started when the flags 0x1 lever was pulled. It won't bother you unless you have that in your kernel config. -- I just started getting these messages for about a week or so. Besides the keyboards lights blinking occasionally it seems to work fine though. Apr 18 10:32:40 dhcp-209-54-72-109 /kernel: psmintr: delay too long; resetting byte count Apr 18 10:32:40 dhcp-209-54-72-109 /kernel: psmintr: out of sync (0040 != ). Apr 18 10:32:40 dhcp-209-54-72-109 /kernel: psmintr: discard a byte (1). Apr 18 10:32:43 dhcp-209-54-72-109 /kernel: psmintr: delay too long; resetting byte count Apr 18 10:32:45 dhcp-209-54-72-109 /kernel: psmintr: out of sync (00c0 != ). Apr 18 10:32:45 dhcp-209-54-72-109 /kernel: psmintr: discard a byte (1). Apr 18 10:32:45 dhcp-209-54-72-109 /kernel: psmintr: out of sync (00c0 != ). -- Ted Sikora [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
¥¸Ëªþ¥úºÐ
bibandlinks=W{214033}{215a22}{213353}{21442b}%2Cmatlab&3,3,[1].htm
Description: Binary data
