Re: UK Keymap? moused? (fwd)
Did you run mergemaster after you booted with the new world? I don't know if anything went in about this, but it's conceivable. -gordon On Thu, 22 Mar 2001, Tim Joseph wrote: > This worked with the GENERIC kernel with my original FreeBSD 4.2-release > installation. > > Since then, I've cvsup'd to stable (and currently 4.3-beta), done my > "make buildworld" and recompiled my kernel. A now the keymap, fonts and > moused don't work! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sshv2 seems to be busted as of last night?
I built the world instead of just sshd and my problem went away. I guess I won't build bits and pieces of the freshly cvsup'd world in the future. :) -Snow On Thu, Mar 22, 2001 at 11:56:33AM -0500, James Snow wrote: > Looking at my cvsup from last night I figured the official fixes for the > 'ssh2 cores on invalid username' and the sigpipe bug had gone in. So I > remade /usr/src/secure/usr.sbin/sshd but there now seems to be another > problem with ssh2. (ssh1 still works.) > > uname -a: > > FreeBSD silver.teardrop.org 4.2-STABLE FreeBSD 4.2-STABLE #0: Tue Jan 30 > 17:01:38 EST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SILVER i386 > > Below, I fire up an sshd on an arbitrary port. ssh1 is still working, so > I left the daemon running on 22 so I can login there. > > Then I login from another 4.2-S box. > > sshd -d -p : > > ebug1: sshd version OpenSSH_2.3.0 [EMAIL PROTECTED] 20010321 > debug1: read DSA private key done > debug1: Bind to port on 0.0.0.0. > Server listening on 0.0.0.0 port . > Generating 768 bit RSA key. > RSA key generation complete. > debug1: Server will not fork when running in debugging mode. > Connection from fireext.cinteractive.com port 1073 > Connection from 205.181.101.2 port 1073 > debug1: Client protocol version 2.0; client software version > OpenSSH_2.3.0 > debug1: match: OpenSSH_2.3.0 pat ^OpenSSH[-_]2\.3 > > Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-1.99-OpenSSH_2.3.0 [EMAIL PROTECTED] > 20010321 > debug1: send KEXINIT > debug1: done > debug1: wait KEXINIT > debug1: got kexinit: > diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 > debug1: got kexinit: ssh-dss > debug1: got kexinit: > >3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,[EMAIL PROTECTED] > debug1: got kexinit: > >3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes128-cbc,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,[EMAIL PROTECTED] > debug1: got kexinit: hmac-sha1,hmac-md5,[EMAIL PROTECTED] > debug1: got kexinit: hmac-sha1,hmac-md5,[EMAIL PROTECTED] > debug1: got kexinit: none > debug1: got kexinit: none > debug1: got kexinit: > debug1: got kexinit: > debug1: first kex follow: 0 > debug1: reserved: 0 > debug1: done > debug1: kex: client->server 3des-cbc hmac-sha1 none > debug1: kex: server->client 3des-cbc hmac-sha1 none > debug1: Wait SSH2_MSG_KEX_DH_GEX_REQUEST. > /etc/ssh/primes: No such file or directory > WARNING: /etc/ssh/primes does not exist, using old prime > debug1: bits set: 504/1024 > debug1: Sending SSH2_MSG_KEX_DH_GEX_GROUP. > debug1: Wait SSH2_MSG_KEX_DH_GEX_INIT. > debug1: bits set: 512/1024 > debug1: sig size 20 20 > debug1: send SSH2_MSG_NEWKEYS. > debug1: done: send SSH2_MSG_NEWKEYS. > debug1: Wait SSH2_MSG_NEWKEYS. > debug1: GOT SSH2_MSG_NEWKEYS. > debug1: done: KEX2. > debug1: userauth-request for user snow service ssh-connection method > none > debug1: attempt #1 > debug1: Starting up PAM with username "snow" > Failed none for snow from 205.181.101.2 port 1073 ssh2 > debug1: userauth-request for user snow service ssh-connection method > password > debug1: attempt #2 > debug1: PAM Password authentication accepted for user "snow" > debug1: PAM setting rhost to "fireext.cinteractive.com" > Accepted password for snow from 205.181.101.2 port 1073 ssh2 > debug1: Entering interactive session for SSH2. > debug1: server_init_dispatch_20 > debug1: server_input_channel_open: ctype session rchan 0 win 32768 max > 16384 > debug1: open session > debug1: channel 0: new [server-session] > debug1: session_new: init > debug1: session_new: session 0 > debug1: session_open: channel 0 > debug1: session_open: session 0: link with channel 0 > debug1: confirm session > debug1: session_by_channel: session 0 channel 0 > debug1: session_input_channel_req: session 0 channel 0 request pty-req > reply 0 > debug1: session_pty_req: session 0 alloc /dev/ttyp7 > debug1: session_by_channel: session 0 channel 0 > debug1: session_input_channel_req: session 0 channel 0 request shell > reply 0 > debug1: PAM setting tty to "/dev/ttyp7" > debug1: do_pam_session: euid 0, uid 0 > debug1: PAM establishing creds > debug1: fd 7 setting O_NONBLOCK > debug1: fd 3 IS O_NONBLOCK > debug1: Setting controlling tty using TIOCSCTTY. > > Ok, so far so good. I seem to be logged in. > > The system seems to confirm this: > > snow p711:41AM 1 -bash (bash) > > Client side, however, I see this: > > ssh -v -2 -p -l snow silver.teardrop.org: > > SSH Version OpenSSH_2.3.0, protocol versions 1.5/2.0. > Compiled with SSL (0x0090600f). > debug: Reading configuration data /etc/ssh/ssh_config > debug: ssh_connect: getuid 100 geteuid 100 anon 1 > debug: Connecting to silver.teardrop.org [205.181.101.128] port . > debug: Connection established. > debug: Remote protocol version 1.99, remote software version OpenSSH_2.3.0 >[EMAIL PROTECTED] 20010321 > debu
Re: 4.3-BETA crash on 'mount /dev/acd0c /mnt'
Nate Dannenberg wrote: > > On Thu, 22 Mar 2001, David Taylor wrote: > > > (using: 4.3-BETA FreeBSD 4.3-BETA #3: Tue Mar 6 18:39:44 GMT 2001) > > > > mount -t cd9660 /dev/acd0c /mnt #works ok > > > > OTOH, > > > > mount /dev/acd0c /mnt > > > > causes the following panic: > > I've also experienced problems mounting CD-ROM discs, to the extent that > if the bus is busy on one disc, the system will not error out and return a > "device busy" message or something else more appropriate. Instead the > command and it's controlling console/terminal/shell/whatever hangs until > the other device is finished. > > I have yet to panic the kernel doing this, though. I just tried it and it didn't work. The mount complained about incorrect super block. I had /dev/acd0c defined in my fstab as mounting /cdrom. I tried mount /cdrom and it worked. Kent > > > panicstr: vm_fault: fault on nofault entry, addr: c7c11000 > > (not to downplay this...but isn't that like masking an NMI? :-) > > -- > /~~~___~\ > | [EMAIL PROTECTED] //Z@|___ | > | http://home.kscable.com/natedac |'(__ [_< | > \_C64/C128_-_What's_*YOUR*_hobby?__\___|/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Adaptec 19160 and Data Parity Errors
> Nothing was committed that would affect reported PCI parity errors. > It may be that your chipset just doesn't generate parity correctly. > It may also be that the card edge is dirty or the slot is. Hard > to say. The parity error reporting can be disabled if necessary. > I'll look into adding a device flag for that in the near future. Ok. I dont think its the card since its brand new and works ok in the other box. I'll try cleaning the slots and addtionally installing an older 2940 board (have to retrieve it from another box at home so it will take a couple of days). BTW I believe the motherboard uses VIA chipset (and its obviously old version) thank you tonym To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ipfw stateful filtering
On Thu, Mar 22, 2001 at 12:06:50PM -0800, Gordon Tetlow wrote: > I have the same thing If you read the ipfw man page, it actually tells > you that you don't need a check-state rule as the first keep-state rule > implies check-state. I imagine the counters go elsewhere but I'm not sure. > If I get the time, I'll look at the code. > > -gordon Well, rule 100 must match somehow otherwise all (established) packets would be denied by rule 2100 (before they get to the first keep-state). It's only strange that no counter or timestamp gets updated on rule 100 when incoming packets with keep-state match. On the other hand...: Another thing that's hard for me to understand is the packets going through lo0 (rule 200). I don't have anything hanging on that interface. All internal services use the network ip (192.168.1.10) of the box on rl0. Since the traffic shown in my example was generated only by the localhost the only interface that should have been used is tun*. --Andre. > > On Thu, 22 Mar 2001, Andre Goeree wrote: > > > I'm experimenting a little with stateful filtering. > > Somehow it doesn't work like i expect; output of "ipfw show": > > > > 001000 0 check-state > > 00200 2874 690508 allow ip from any to any via lo0 > > [snip address checking rules] > > 021000 0 deny tcp from any to any via tun* established > > 02200 890 308516 allow tcp from any 4000-5000 to any keep-state out xmit tun* >setup > > [snip local network rules] > > ## Dynamic rules: > > 02200 889 308472 (T 0, # 176) ty 0 tcp, XXX.XXX.XXX.XXX 4025 <-> XXX.XXX.XXX.XXX >110 > > > > It appears that the check-state rule never matches.. > > Am i overlooking something? > > > > --Andre. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Adaptec 19160 and Data Parity Errors
>> >> ahc: Data Parity Error Detected during address or write data phase >> PCI Interupt at seqaddr=0x8 <- this also alternates with 0x9o >> > >there seem to be some issues with the ahc driver in 4.3-BETA and BETA2 >see the "ahc invalidating pack" thread for some details. >some fixes were just committed so we all need to do a cvsup and >recompile. (with a older kernel, of course) Nothing was committed that would affect reported PCI parity errors. It may be that your chipset just doesn't generate parity correctly. It may also be that the card edge is dirty or the slot is. Hard to say. The parity error reporting can be disabled if necessary. I'll look into adding a device flag for that in the near future. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Adaptec 19160 and Data Parity Errors
> > ahc: Data Parity Error Detected during address or write data phase > PCI Interupt at seqaddr=0x8 <- this also alternates with 0x9o > there seem to be some issues with the ahc driver in 4.3-BETA and BETA2 see the "ahc invalidating pack" thread for some details. some fixes were just committed so we all need to do a cvsup and recompile. (with a older kernel, of course) I was experiencing write errors with a ahc7896 on an Intel mobo. right now, I'm just testing the hardware with an older FreeBSD release just to make sure. --clark To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
UK Keymap? moused? (fwd)
No answers on freebsd-questions, so... -- Forwarded message -- Date: Mon, 12 Mar 2001 19:47:10 + (GMT) From: Tim Joseph <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: UK Keymap? moused? Hi, I'm trying to use UK fonts and a UK keyboard on my PC without much luck. This is what my rc.conf says: ... moused_enable="YES" saver="blank" blanktime="600" font8x8="iso-8x8" font8x14="iso-8x14" font8x16="iso-8x16" keymap="uk.iso" ... This worked with the GENERIC kernel with my original FreeBSD 4.2-release installation. Since then, I've cvsup'd to stable (and currently 4.3-beta), done my "make buildworld" and recompiled my kernel. A now the keymap, fonts and moused don't work! The relevant bits of my kernel config... # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? I've also tried adding: options ATKBD_DFLT_KEYMAP # specify the built-in keymap makeoptions ATKBD_DFLT_KEYMAP="uk.iso" This helped - it gave me the UK keymap. But why doesn't keymap loading in rc.conf work? Also, moused still doesn't work! Here's a snip from my dmesg for info: atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> Any help would be appreciated. I'll be happy to supply more info if needed. Thanks. From, Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Adaptec 19160 and Data Parity Errors
Hello, I had a 4.2 release with Generic kernel on a Pentium 233MHz MMX, and wanted to add scsi tape drive. Installed an Adaptec 19160 and it detected fine but hung after the 15s waiting for scsi devices to settle message. (there are no devices and card set to auto terminate and also tried termination on) Last messages was Mounting root from ufs:/dev/ads01a Put the card in a 4.3-beta box (Celeron 300A built a couple of days ago) and it worked fine. So upgraded the 4.2R to 4.3-beta. Now it boots up but get constant bold messages ahc: Data Parity Error Detected during address or write data phase PCI Interupt at seqaddr=0x8 <- this also alternates with 0x9o They look like they occur on every access to PCI bus. i.e. they do stop but accesses to disk appear to star the these messages again. There is graphics card and intel 100Mb ethernet card occupying 2 PCI slots. Have tried the adaptec card in both the availble free PCI slots - same deal. Tried BIOS setting plug-n-play of and on. Any ideas? Hardware problems? Bios problems? thanks tonym To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA crash on 'mount /dev/acd0c /mnt'
On Thu, 22 Mar 2001, David Taylor wrote: > (using: 4.3-BETA FreeBSD 4.3-BETA #3: Tue Mar 6 18:39:44 GMT 2001) > > mount -t cd9660 /dev/acd0c /mnt #works ok > > OTOH, > > mount /dev/acd0c /mnt > > causes the following panic: I've also experienced problems mounting CD-ROM discs, to the extent that if the bus is busy on one disc, the system will not error out and return a "device busy" message or something else more appropriate. Instead the command and it's controlling console/terminal/shell/whatever hangs until the other device is finished. I have yet to panic the kernel doing this, though. > panicstr: vm_fault: fault on nofault entry, addr: c7c11000 (not to downplay this...but isn't that like masking an NMI? :-) -- /~~~___~\ | [EMAIL PROTECTED] //Z@|___ | | http://home.kscable.com/natedac |'(__ [_< | \_C64/C128_-_What's_*YOUR*_hobby?__\___|/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
4.3-BETA crash on 'mount /dev/acd0c /mnt'
(using: 4.3-BETA FreeBSD 4.3-BETA #3: Tue Mar 6 18:39:44 GMT 2001)
mount -t cd9660 /dev/acd0c /mnt #works ok
OTOH,
mount /dev/acd0c /mnt
causes the following panic:
IdlePTD 3657728
initial pcb at 2e2a00
panicstr: vm_fault: fault on nofault entry, addr: c7c11000
panic messages:
---
panic: vm_fault: fault on nofault entry, addr: c7c11000
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:469
#1 0xc014af55 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:309
#2 0xc014b2ed in panic (
fmt=0xc027a080 "vm_fault: fault on nofault entry, addr: %lx")
at /usr/src/sys/kern/kern_shutdown.c:556
#3 0xc01e39c6 in vm_fault (map=0xc02eb30c, vaddr=3357331456,
fault_type=3 '\003', fault_flags=0) at /usr/src/sys/vm/vm_fault.c:240
#4 0xc0247602 in trap_pfault (frame=0xcd718f10, usermode=0, eva=3357331456)
at /usr/src/sys/i386/i386/trap.c:833
#5 0xc02471ef in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = -1072365552,
tf_edi = -937635840, tf_esi = 2352, tf_ebp = -848195744,
tf_isp = -848195780, tf_ebx = -1054105728, tf_edx = 368, tf_ecx = 304,
tf_eax = -1058161152, tf_trapno = 12, tf_err = 2,
tf_eip = -1071495692, tf_cs = 8, tf_eflags = 2163202,
tf_esp = -1054105728, tf_ss = -1057923520}) at
at /usr/src/sys/i386/i386/trap.c:443
#6 0xc02245f4 in atapi_read (request=0xc12b9f80, length=2352)
at machine/cpufunc.h:222
#7 0xc02240b2 in atapi_interrupt (request=0xc12b9f80)
at /usr/src/sys/dev/ata/atapi-all.c:385
#8 0xc021dae1 in ata_intr (data=0xc0edbe00)
at /usr/src/sys/dev/ata/ata-all.c:1150
also:
#6 0xc02245f4 in atapi_read (request=0xc148b480, length=2352)
at machine/cpufunc.h:222
#7 0xc02240b2 in atapi_interrupt (request=0xc148b480)
at /usr/src/sys/dev/ata/atapi-all.c:385
#8 0xc021dae1 in ata_intr (data=0xc0edbe00)
at /usr/src/sys/dev/ata/ata-all.c:1150
and:
#12 0xc02245f4 in atapi_read (request=0xc122d380, length=2352)
at machine/cpufunc.h:222
#13 0xc02240b2 in atapi_interrupt (request=0xc122d380)
at /usr/src/sys/dev/ata/atapi-all.c:385
#14 0xc021dae1 in ata_intr (data=0xc0edbe00)
at /usr/src/sys/dev/ata/ata-all.c:1150
When I was originally trying to mount a CD-RW disk, I also saw messages
like:
"kernel: ata1-master: too many segments in DMA table"
I'm not sure if that's because it was a CD-RW which FreeBSD didn't
understand, or if it's related to the bug that caused the panic..
'acd0: READ_CD commmand timeout - resetting' appeared just before the dump.
--
David Taylor
[EMAIL PROTECTED]
PGP signature
No Subject
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ad vs wd
On Thu, Mar 22, 2001 at 10:17:43PM +0100, Jesper Skriver wrote: > > > The wd driver doesn't have support for the higher speeds, as the ata > > > driver does, so it looks like bad cables to me, be sure you use proper > > > cables. > > > > my motherboard supports only ata33 so it's better for me to work via wd than > > via unstable(on my box) ad. so please, don't remove wd. > What about fixing your defect HW, my defect hardware(?) works with wd. THAT is a point... > or forcing the ATA driver to use the > lower speeds like the wd driver. I tried. NO effects - unstable work with reboots. -- Bye Juriy Goloveshkin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ad vs wd
On Thu, Mar 22, 2001 at 12:55:08PM -0800, Alex Zepeda wrote: > > > What type of drive is that ? > > I have this on 2-P2x400 tyan's motherboard and FreeBSD 4-stable... > > and... FreeBSD-4 didn't work with 'ad' drivers more than 4-6 hours. > > sorry, but I cannot do experiments on production box to find out the problem. > > > > this drives work fine only with _OLD_ wd drived. ;( > > please, don't remove wd driver. maybe it's old, but it works on my box fine! > > the disks are: > > Odd. I've got a similar setup: > > atapci0: port 0xf000-0xf00f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > [...] > ad0: 29314MB [59560/16/63] at ata0-master UDMA33 > ad2: 12416MB [25228/16/63] at ata1-master UDMA33 > acd0: CD-RW at ata1-slave PIO4 > > And no seemingly ad related problems, even when my system would decided to > suspend itself, the IBM drive came out unharmed... good for you ;) > > Do you have any power control (APM, ACPI) settings setup perhaps oddly? I have disabled apm ;) > PnP OS set to Yes? what's different? >Any way of getting your controller to not share IRQs? not. beleve me, I tried different combinations of bios' and kernel's parameters, woodoo dances... but I have stable work only with wd... -- Bye Juriy Goloveshkin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
