Re: kldxref problem
On Sun, Mar 31, 2002 at 12:38:24PM +0200, Emiel Kollof wrote: On Sun, 2002-03-31 at 09:51, Terry Lambert wrote: Perhaps if the kernel printf also ignored the request to print the little S.O.B. out, there would be less confusion... I'm still sticking to the idea that one could test for kldxref, and if it isn't there, don't execute it. [ -x /usr/sbin/kldxref ] /usr/sbin/kldxref like so, which is perfectly sane bourne shell syntax, which is also used by BSD make. Not really. Use: target: deps tabrule1 tabrule2 .if exists(/usr/sbin/kldxref) tab/usr/sbin/kldxref .endif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Superfast clock on current.
In message [EMAIL PROTECTED], Kyle Butt writes: I've stared at the data file and I'll be damned if I can find anything which would case the clock to double its speed :-( Perhaps something else is causing the clock to run twice as fast? Maybe two things that are working properly are both incrementing the clock? Well, obviously something causes it, but I have no idea what at this moment. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Ports broken by OpenPAM
Joe Marcus Clarke [EMAIL PROTECTED] writes: I think I found why pam_ldap wouldn't work with OpenPAM on -CURRENT. Attached is my proposed patch to OpenPAM. With this applied, pam_ldap works like a champ. But of course! Thank you very much, that was a stupid braino. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: LINT compiled with icc
On 27 Mär, I wrote: The compressed log is at http://www.leidnger.net/FreeBSD/LINT_with_icc_20020327.log.bz2 (71k), it's about 3MB uncompressed. There's a new log in the FreeBSD directory. It's generated with the new portrevision of icc. A lot more errors, ~7 MB uncompressed. Bye, Alexander. -- Loose bits sink chips. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: asr can not map memory?
On Sat, Mar 30, 2002 at 10:28:05PM -0800, Michael Smith wrote: This avoids a panic when probing, there's probably still some badness going on with make/destroy dev in this driver. Pending commentary from Scott, I think you should commit this. Yes, there is a lot of evilness in the asr driver. A whole lot. The original author does not have time/desire to maintain it, so obrien volunteered to take over maintainership. Thanks obrien ;-} Scott? Hm? Where is a pitchfork when you need it ;- Time and micro-managed priorities limit my usefulness currently, Scott is right ... Driver is just asking for it's `just deserved' mappings to the card, I put my vote with Michael with regards to the PCI system not differentiating non-prefetched (hardware) and prefetched (memory) mappings (said with an aire of pretending to know unintentional). Should I hold onto this card or should I suck it up and get a 3ware online somewhere? Be a man and buy a SCSI RAID controller. The Adaptec 5400S is all you'll ever need =-) SCSI is too expensive for many folk, that is why we made the 2400A. However, IDE looses 2ms on every access because it can not overlap commands -- much of that delay is reduced with the SCSI origined 2400A's cache/coalesce/elevator code, we see performance that has us wondering out loud about the SCSI price differential. Good luck, hope I could help ... Sincerely -- Mark Salyzyn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Card has no functions
Hi, I'm having problem with the TI cardbus bridge to recognize PCCARD in NEWCARD kernel. I have a desktop with TI PCI1250 adaptor and an IBM Thinkpad with TI 1450. Both recognize PC Cards in GENERIC kernel, but get Card has no functions in NEWCARD. I checked the maillist and found no answer. The same kernel ran fine in a Toshiba Portege with ToPIC100 cardbus bridge. Is this something unique to TI chips? Any suggestion I should try? __ Do You Yahoo!? Yahoo! Greetings - send holiday greetings for Easter, Passover http://greetings.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Patch for -CURRENT (share/dict/tech - freebsd repo-copy)
Untested as yet; just fired up the make -DNOCLEAN buildworld after the
breakage (Don't know how to make tech in /usr/src/share/dict):
Index: share/dict/Makefile
===
RCS file: /cvs/freebsd/src/share/dict/Makefile,v
retrieving revision 1.11
diff -u -r1.11 Makefile
--- share/dict/Makefile 26 Mar 2002 11:21:58 - 1.11
+++ share/dict/Makefile 1 Apr 2002 15:58:06 -
@@ -4,7 +4,7 @@
NOOBJ= noobj
# XXX MISSING: connectives words
-FILES= README propernames web2 web2a tech
+FILES= README propernames web2 web2a freebsd
FILESDIR= ${BINDIR}/dict
SYMLINKS= web2 ${FILESDIR}/words
Cheers,
david
--
David H. Wolfskill [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
libusbhid.h and make includes
Argh, it seems that libusbhid.h doesn't get installed by make includes thus if one is trying to use make includes to update headers prior to doing a make depend or make all in /usr/src on a machine that can't do buildworld (like, say, sparc64), then it dies. Can the USB maintainer please add appropriate magic to src/include/Makefile so that make includes installs this header? Thanks. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: libusbhid.h and make includes
On Mon, Apr 01, 2002 at 11:39:16AM -0500, John Baldwin wrote: Argh, it seems that libusbhid.h doesn't get installed by make includes thus if one is trying to use make includes to update headers prior to doing a make depend or make all in /usr/src on a machine that can't do buildworld (like, say, sparc64), then it dies. Can the USB maintainer please add appropriate magic to src/include/Makefile so that make includes installs this header? Thanks. It looks like libusb.h wasn't installed either. Either way -current should now do the right thing. Joe msg36858/pgp0.pgp Description: PGP signature
Re: Patch for -CURRENT (share/dict/tech - freebsd repo-copy)
On Mon, 2002-04-01 at 11:01, David Wolfskill wrote:
Untested as yet; just fired up the make -DNOCLEAN buildworld after the
breakage (Don't know how to make tech in /usr/src/share/dict):
phk just submitted a patch to fix this. Yours looks suspiciously like
it ;-).
Joe
Index: share/dict/Makefile
===
RCS file: /cvs/freebsd/src/share/dict/Makefile,v
retrieving revision 1.11
diff -u -r1.11 Makefile
--- share/dict/Makefile 26 Mar 2002 11:21:58 - 1.11
+++ share/dict/Makefile 1 Apr 2002 15:58:06 -
@@ -4,7 +4,7 @@
NOOBJ= noobj
# XXX MISSING: connectives words
-FILES= README propernames web2 web2a tech
+FILES= README propernames web2 web2a freebsd
FILESDIR=${BINDIR}/dict
SYMLINKS=web2 ${FILESDIR}/words
Cheers,
david
--
David H. Wolfskill[EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
PGP Key: http://www.marucscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
Re: libusbhid.h and make includes
On 01-Apr-2002 Josef Karthauser wrote: On Mon, Apr 01, 2002 at 11:39:16AM -0500, John Baldwin wrote: Argh, it seems that libusbhid.h doesn't get installed by make includes thus if one is trying to use make includes to update headers prior to doing a make depend or make all in /usr/src on a machine that can't do buildworld (like, say, sparc64), then it dies. Can the USB maintainer please add appropriate magic to src/include/Makefile so that make includes installs this header? Thanks. It looks like libusb.h wasn't installed either. Either way -current should now do the right thing. Thanks! Joe -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
FreeBSD-localised OpenSSH hangs with Foundry SSH1 server
I had problems connecting with the FreeBSD openssh client to a Foundry BigIron gigabit switch running ssh 1.2.27, whereas I can connect fine to the same switch when using a locally-compiled OpenSSH 3.1p1. The culprit is apparently the length of the version string sent by FreeBSD and received by the Foundry switch. If it is over 24 characters, the Foundry ssh daemon just sits there and hangs for a few minutes until it timeouts and closes the connection. If I shorten the client version string to be OpenSSH_3.1 FreeBSD, everything works ok again. The closest thing to a standard description of the SSH1 protocol I could find is below. It clearly sets a upper limit of 40 characters for the version part of the identification string. This is lower than the 42 chars of OpenSSH_3.1 FreeBSD localisations 20020318, but higher than the maximum of 24 character accepted by the Foundry implementation. So it looks like neither side is strictly compliant to something that's not really a standard anyway. It would be easier on me (and other Foundry switch users) and in the interest of interoperability with broken ssh implementations if the FreeBSD-specific string could be shortened (to at most 11 chars, which is exactly enough to put des20020307 in there for example ;-), made user-configurable, or altogether removed. http://www.snailbook.com/docs/protocol-1.5.txt Protocol Version Identification After the socket is opened, the server sends an identification string, which is of the form SSH-protocolmajor.protocolminor- version\n, where protocolmajor and protocolminor are integers and specify the protocol version number (not software distribution version). version is server side software version string (max 40 characters); it is not interpreted by the remote side but may be use- ful for debugging. Pierre To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kldxref problem
On Mon, Apr 01, 2002 at 12:35:21AM -0800, David O'Brien wrote: On Sun, Mar 31, 2002 at 12:38:24PM +0200, Emiel Kollof wrote: On Sun, 2002-03-31 at 09:51, Terry Lambert wrote: Perhaps if the kernel printf also ignored the request to print the little S.O.B. out, there would be less confusion... I'm still sticking to the idea that one could test for kldxref, and if it isn't there, don't execute it. [ -x /usr/sbin/kldxref ] /usr/sbin/kldxref like so, which is perfectly sane bourne shell syntax, which is also used by BSD make. Not really. Use: target: deps tabrule1 tabrule2 .if exists(/usr/sbin/kldxref) tab/usr/sbin/kldxref .endif This whole argument ignores what the real problem is. The really correct way to handle this is to use the kldxref(8) built in the 'buildworld' phase. (It's bad form to be using any executables from the base system if we have a full object tree.) Actually using the one in /usr/obj/usr/src/usr.sbin/kldxref seems pretty ugly. The better thing to do is to have a version in /usr/obj/usr/src/arch/usr/sbin by making it a crosstool. The failure should not be ignored in this case. -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Card has no functions
On Mon, Apr 01, 2002 at 07:42:59AM -0800, Shizuka Kudo wrote: Hi there, I'm having problem with the TI cardbus bridge to recognize PCCARD in NEWCARD kernel. I have a desktop with TI PCI1250 adaptor and an IBM Thinkpad with TI 1450. Both recognize PC Cards in GENERIC kernel, but get Card has no functions in NEWCARD. I checked the maillist and found no answer. The same kernel ran fine in a Toshiba Portege with ToPIC100 cardbus bridge. Is this something unique to TI chips? Any suggestion I should try? My Thinkpad 310 is running -CURRENT as of the 29th of March. I normally use a CARDBUS nic, but I've just inserted a PCCARD nic on the second slot and it's recognized as ed0. My hardware has a TI1131 PCI-CardBus Bridge. It seems to work here, when did you last cvsup your src? Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36863/pgp0.pgp Description: PGP signature
Re: disklabel(8) floppy panic
Crist J. Clark [EMAIL PROTECTED] wrote: Have a crash box handy? $ disklabel fd0.1440 The patch below should fix that, thanks for the bug report. fdioctl() historically attempted to determine the raw partition (`c') of the device in order to read the label. However, the floppy driver never really supported UFS-style partitions anyway. This ended up in selecting the wrong device for reading the label, which was a not-so-fatal error before the last floppy driver rewrite (it actually selected the fdX.1480 device then, which was obviously benign for 3.5 drives). However, now it hits an unitialized device which becomes fatal in readdisklabel() by attempting an indirect call to the strategy routine that hasn't been entered in the struct dev passed down. The call to dkmodpart() entered in rev. 1.64 of fd.c, so i'm Cc'ing Bruce for a comment whether the fix below is indeed TRT. Index: sys/isa/fd.c === RCS file: /home/ncvs/src/sys/isa/fd.c,v retrieving revision 1.224 diff -u -r1.224 fd.c --- isa/fd.c18 Dec 2001 22:16:33 - 1.224 +++ isa/fd.c1 Apr 2002 20:56:22 - @@ -2704,7 +2704,7 @@ fdt = fd-ft; lp-d_secpercyl = fdt-size / fdt-tracks; lp-d_type = DTYPE_FLOPPY; - if (readdisklabel(dkmodpart(dev, RAW_PART), lp) != NULL) + if (readdisklabel(dev, lp) != NULL) error = EINVAL; else *(struct disklabel *)addr = *lp; -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD-localised OpenSSH hangs with Foundry SSH1 server
Pierre Beyssac [EMAIL PROTECTED] writes: It would be easier on me (and other Foundry switch users) and in the interest of interoperability with broken ssh implementations if the FreeBSD-specific string could be shortened (to at most 11 chars, which is exactly enough to put des20020307 in there for example ;-), made user-configurable, or altogether removed. Look for VersionAddendum in /etc/ssh/sshd_config (it can be used in ssh_config as well). DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: ports/lang Makefile ports/lang/icc Makefile distinfo pkg-comment pkg-descr pkg-plist ports/lang/icc/files patch-include
On Sat, Mar 30, 2002 at 10:03:47AM +0100, Alexander Leidinger wrote:
On 29 Mär, David O'Brien wrote:
My patches to src/share/mk/ are here:
ftp://ftp.jurai.net/users/winter/icc.mk.diff
This allows you to set 'USE_ICC' and 'ICFLAGS' and build stuff.
This is fine just to get things working. But please consider Doing It
Right -- that being wrap the definitions of CC, CFLAGS, and PICFLAG with
USE_ICC rather than strew USE_ICC all over the place. For instance:
/usr/share/mk/sys.mk
.if defined(USE_ICC)
CC= icc
.else
CC= cc
.endif
- How do you want to solve the single suffix rules then?
What is the problem with them?
.c:
${CC} ${CFLAGS} ${LDFLAGS} -o ${.TARGET} ${.IMPSRC}
CC and CFLAGS is used.
- Do we use ${LD} in every significant place?
If we don't it is a bug -- send in a patch. But LD is `ld', does ICC
come with its own linker?
- What about ports with CC=${CC} in CONFIGURE_ENV (they would break
in the USE_ICC case)?
How would they?? CC=icc if you have USE_ICC defined. Either in
/etc/make.conf or `make USE_ICC=yes'.
It seems you do not realize the whole reason for ${CC} rather than just
cc.
-D__attribute__(x)=
-D__GNUC__=2
Ok as a short term solution, but IMHO this should get solved in the
source.
Totally agreed for defining __GNUC__.
And the __attribute__ line is the reason why libc doesn't work.
Explain does not work.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
login looping
I've just finished updating a system to -CURRENT from mid-April (just before the DP1 branch). When I try to login, login(8) goes into a loop. ktrace shows it's in userland and the last syscall was closing /etc/auth.conf. I've tried with two different users and gotten the same result. A third user without a password starts successfully. Logging in via ssh works. I did remember to do a mergemaster. There's nothing in UPDATING and I don't recall seeing anyone else report these symptoms here. Does anyone have any ideas? Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kldxref problem
Crist J. Clark wrote: This whole argument ignores what the real problem is. The really correct way to handle this is to use the kldxref(8) built in the 'buildworld' phase. (It's bad form to be using any executables from the base system if we have a full object tree.) Actually using the one in /usr/obj/usr/src/usr.sbin/kldxref seems pretty ugly. The better thing to do is to have a version in /usr/obj/usr/src/arch/usr/sbin by making it a crosstool. The failure should not be ignored in this case. Uh, that doesn't work incredibly well when the machine you are on is an x86, and the machine that the buildworld targets is, say, the Alpha. This came up in the first place because it's a cross-envrionment issue that needs resolving. The workaround exists because the workaround cops out on the cross-environment part of the process and spits out the warnming, instead. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kldxref problem
On Mon, Apr 01, 2002 at 03:07:46PM -0800, Terry Lambert wrote: Crist J. Clark wrote: This whole argument ignores what the real problem is. The really correct way to handle this is to use the kldxref(8) built in the 'buildworld' phase. (It's bad form to be using any executables from the base system if we have a full object tree.) Actually using the one in /usr/obj/usr/src/usr.sbin/kldxref seems pretty ugly. The better thing to do is to have a version in /usr/obj/usr/src/arch/usr/sbin by making it a crosstool. The failure should not be ignored in this case. Uh, that doesn't work incredibly well when the machine you are on is an x86, and the machine that the buildworld targets is, say, the Alpha. This came up in the first place because it's a cross-envrionment issue that needs resolving. The workaround exists because the workaround cops out on the cross-environment part of the process and spits out the warnming, instead. An 'installworld' doesn't even come close to working in a cross environment for a whole variety of reasons, so I don't see the relevance. The situation this question comes up is typically 5-CURRENT builds on 4-STABLE systems, not in cross-archetecture builds. -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Perl build uses 'cc' and maybe 'gcc' directly.
Any chance of getting the Perl build to properly use ${CC} rather than
hard coding 'cc'? Also a find . -type f | xargs grep gcc shows that
GCC may be called directly also.
This is a problem for cross builds, and using alternate versions of of
the compiler (say gcc31 for testing).
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: kldxref problem
Crist J. Clark wrote: This came up in the first place because it's a cross-envrionment issue that needs resolving. The workaround exists because the workaround cops out on the cross-environment part of the process and spits out the warnming, instead. An 'installworld' doesn't even come close to working in a cross environment for a whole variety of reasons, so I don't see the relevance. The situation this question comes up is typically 5-CURRENT builds on 4-STABLE systems, not in cross-archetecture builds. Since this is the recommended upgrade path for going from 4.x to 5.x right now, it's an issue, if you can't cross-build 5.x on 4.x. That other things are broken doesn't really excuse this being broken. The problem is that the kldxref deserves to get its own tools build, so that there is a version that works against 5.x code that can be built on 4.x (or NetBSD or Linux or Solaris or whatever). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Card has no functions
--- Miguel Mendez [EMAIL PROTECTED] wrote: Hi there, I'm having problem with the TI cardbus bridge to recognize PCCARD in NEWCARD kernel. I have a desktop with TI PCI1250 adaptor and an IBM Thinkpad with TI 1450. Both recognize PC Cards in GENERIC kernel, but get Card has no functions in NEWCARD. I checked the maillist and found no answer. The same kernel ran fine in a Toshiba Portege with ToPIC100 cardbus bridge. Is this something unique to TI chips? Any suggestion I should try? My Thinkpad 310 is running -CURRENT as of the 29th of March. I normally use a CARDBUS nic, but I've just inserted a PCCARD nic on the second slot and it's recognized as ed0. My hardware has a TI1131 PCI-CardBus Bridge. It seems to work here, when did you last cvsup your src? Cheers, Hi Miguel, I have an IBM Thinkpad 600X with latest BIOS from their web site. CURRENT was updated 31 Mar. I also had no problem with CARDBUS (a realtek 3190B). I tried 3com CCFEM556B (a combo card), Xircom CreditCard Ethernet 10/100, Orinoco Silver, all showed same error no matter the cards were inserted before power on or after boot up. Attached is the dmesg from my desktop (ASUS CUSL2 with PIII 750MHz) if this may help. Cheers, __ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://http://taxes.yahoo.com/ Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #20020317: Sun Mar 17 23:51:21 HKT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SHIZUKA Preloaded elf kernel /boot/kernel/kernel at 0xc048b000. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 757461721 Hz CPU: Pentium III/Pentium III Xeon/Celeron (757.46-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 268349440 (262060K bytes) avail memory = 256212992 (250208K bytes) Pentium Pro MTRR support enabled Using $PIR table, 10 entries at 0xc00f1360 acpi0: ASUS CUSL2on motherboard acpi0: power button is handled as a fixed feature programming model. ACPI timer looks GOOD min = 3, max = 3, width = 1 ACPI timer looks GOOD min = 3, max = 3, width = 1 ACPI timer looks GOOD min = 3, max = 3, width = 1 ACPI timer looks GOOD min = 3, max = 3, width = 1 ACPI timer looks GOOD min = 3, max = 3, width = 1 ACPI timer looks GOOD min = 3, max = 3, width = 1 ACPI timer looks GOOD min = 3, max = 3, width = 1 ACPI timer looks GOOD min = 3, max = 3, width = 1 ACPI timer looks GOOD min = 3, max = 3, width = 1 ACPI timer looks GOOD min = 3, max = 3, width = 1 Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_pcib0: Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: PCI bus on acpi_pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: PCI-PCI bridge at device 30.0 on pci0 pci2: PCI bus on pcib2 pccbb0: TI1225 PCI-CardBus Bridge irq 9 at device 10.0 on pci2 pccbb0: PCI Memory allocated: ed00 cardbus0: CardBus bus on pccbb0 pccard0: 16-bit PCCard bus on pccbb0 pccbb1: TI1225 PCI-CardBus Bridge irq 9 at device 10.1 on pci2 pccbb1: PCI Memory allocated: ed001000 cardbus1: CardBus bus on pccbb1 pccard1: 16-bit PCCard bus on pccbb1 pci2: serial bus, FireWire at device 12.0 (no driver attached) pcm0: Creative EMU10K1 port 0xd800-0xd81f irq 5 at device 14.0 on pci2 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 ATA100 controller port 0xb800-0xb80f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xb400-0xb41f irq 9 at device 31.2 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: OmniVision OV511+ Camera, rev 1.00/1.00, addr 2 ichsmb0: Intel 82801BA (ICH2) SMBus controller port 0xe800-0xe80f irq 10 at device 31.3 on pci0 smbus0: System Management Bus on ichsmb0 smb0: SMBus general purpose I/O on smbus0 uhci1: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0xb000-0xb01f irq 9 at device 31.4 on pci0 usb1: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub2: ALCOR Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2 uhub2: 4 ports with 4 removable, self powered fdc0: enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 irq 6 on acpi0 fdc0:
Re: Problem with ssh
On Sat, Mar 30, 2002 at 01:14:07PM +0100, Dag-Erling Smorgrav wrote: David O'Brien [EMAIL PROTECTED] writes: Something is still very wrong: ssh foo@releng4 otp-md5 350 re9786 ext S/Key Password: otp-md5 134 re2584 ext S/Key Password: otp-md5 417 re5381 ext S/Key Password: otp-md5 198 re2571 ext S/Key Password: Uh, why does my sequence keep changing when I just hit return??? Because it's generating fake S/Key challenges, and badly. Especially since RELENG_4 does NOT use OPIE. Who this fake S/Key challenge that and turned it on? No, I haven't seen it, but I've had similar reports. It's actually a bug on the server side, in older OpenSSH servers, that is exposed by newer OpenSSH clients. Will OpenSSH 3.1 be MFC'ed soon? Considering I DO want SKeyAuthentication (USENIX is comming up); what is the real fix? -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with ssh
David O'Brien [EMAIL PROTECTED] writes: On Sat, Mar 30, 2002 at 01:14:07PM +0100, Dag-Erling Smorgrav wrote: David O'Brien [EMAIL PROTECTED] writes: Uh, why does my sequence keep changing when I just hit return??? Because it's generating fake S/Key challenges, and badly. Especially since RELENG_4 does NOT use OPIE. Who this fake S/Key challenge that and turned it on? OpenSSH in RELENG_4 does use S/Key, and generates fake challenges when the client attempts challenge-response authentication, which is what is used for PAM. No, I haven't seen it, but I've had similar reports. It's actually a bug on the server side, in older OpenSSH servers, that is exposed by newer OpenSSH clients. Will OpenSSH 3.1 be MFC'ed soon? Not likely. There are a number of problems that still need fixing. Considering I DO want SKeyAuthentication (USENIX is comming up); what is the real fix? Enable it only for servers that need it. It used to be disabled by default in the client, so this shouldn't make much of a difference. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
latest kernel busted
=== umodem cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -fno-common -g -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -c /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:840: syntax error before `uio' /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c: In function `umodemread': /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:841: number of arguments doesn't match prototype /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:156: prototype declaration /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:845: `dev' undeclared (first use in this function) /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:845: (Each undeclared identifier is reported only once /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:845: for each function it appears in.) /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:852: `uio' undeclared (first use in this function) /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:852: `flag' undeclared (first use in this function) /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c: At top level: /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1089: conflicting types for `umodem_set_line_coding' /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:188: previous declaration of `umodem_set_line_coding' /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c: In function `umodem_set_line_coding': /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1097: incompatible type for argument 1 of `bcmp' /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1109: incompatible type for argument 3 of `usbd_do_request' /dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1116: invalid type argument of `unary *' *** Error code 1 Ideas? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: latest kernel busted
In article [EMAIL PROTECTED]
M. Warner Losh [EMAIL PROTECTED] wrote:
=== umodem
cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -fno-common -g
-mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -c
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:840: syntax error
before `uio'
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c: In function
`umodemread':
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:841: number of
arguments doesn't match prototype
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:156: prototype
declaration
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:845: `dev'
undeclared (first use in this function)
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:845: (Each
undeclared identifier is reported only once
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:845: for each
function it appears in.)
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:852: `uio'
undeclared (first use in this function)
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:852: `flag'
undeclared (first use in this function)
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c: At top level:
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1089: conflicting
types for `umodem_set_line_coding'
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:188: previous
declaration of `umodem_set_line_coding'
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c: In function
`umodem_set_line_coding':
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1097: incompatible
type for argument 1 of `bcmp'
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1109: incompatible
type for argument 3 of `usbd_do_request'
/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1116: invalid type
argument of `unary *'
*** Error code 1
Ideas?
Warner
Next patch at least unbreaks the kernel building for me.
N.Dudorov
=
Index: sys/dev/usb/umodem.c
===
RCS file: /home/CVS/src/sys/dev/usb/umodem.c,v
retrieving revision 1.38
diff -b -u -r1.38 umodem.c
--- sys/dev/usb/umodem.c1 Apr 2002 21:30:36 - 1.38
+++ sys/dev/usb/umodem.c2 Apr 2002 02:06:53 -
@@ -837,7 +837,7 @@
}
int
-umodemread(dev_t dev, uio *uio, int flag)
+umodemread(dev_t dev, struct uio *uio, int flag)
{
struct umodem_softc *sc;
struct tty *tp;
@@ -1085,7 +1085,7 @@
}
usbd_status
-umodem_set_line_coding(struct umodem_softc *sc, usb_cdc_line_state_t state)
+umodem_set_line_coding(struct umodem_softc *sc, usb_cdc_line_state_t *state)
{
usb_device_request_t req;
usbd_status err;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: latest kernel busted
On Mon, 1 Apr 2002, M. Warner Losh wrote: :=== umodem :cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes :-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi :-DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -fno-common -g :-mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs :-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual :-fformat-extensions -ansi -c :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:840: syntax error :before `uio' :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c: In function :`umodemread': someone forgot a struct before the ``uio *uio'' :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:841: number of :arguments doesn't match prototype :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:156: prototype :declaration :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:845: `dev' undeclared :(first use in this function) :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:845: (Each undeclared :identifier is reported only once :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:845: for each :function it appears in.) :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:852: `uio' undeclared :(first use in this function) :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:852: `flag' :undeclared (first use in this function) :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c: At top level: :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1089: conflicting :types for `umodem_set_line_coding' :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:188: previous :declaration of `umodem_set_line_coding' :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c: In function :`umodem_set_line_coding': :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1097: incompatible :type for argument 1 of `bcmp' :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1109: incompatible :type for argument 3 of `usbd_do_request' :/dell/imp/FreeBSD/src/sys/modules/umodem/../../dev/usb/umodem.c:1116: invalid type :argument of `unary *' :*** Error code 1 : :Ideas? : :Warner : :To Unsubscribe: send mail to [EMAIL PROTECTED] :with unsubscribe freebsd-current in the body of the message : -- Andrew R. Reiter [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: latest kernel busted
Looks like two, tiny fixes, so I went ahead and committed them. It shouldn't interfere with the NetBSD merge. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Mirrored disk on HPT370 is not detected.
Hi, I cannot update my current system after Jan 29 2002, because the latest kernel cannot detect my mirrored disk on HPT370 as ar. Is there any problem or large change around ata driver? The dmesg outputs for old and new kernels and kernel configuration file are available at http://www.rc.tutrp.tut.ac.jp/~nakaji/FreeBSD/20020402/ dmesg.boot old kernel dmesg.noar.20020402 today's kernel NAKAJI kernel configuration I checked the difference between them to find that ata device on HPT370 is not detected, -pcib2: device atapci0 requested decoded I/O range 0x9c02-0x9c00 -pcib2: device ata2 requested decoded I/O range 0xa800-0xa807 -ata2: iobase=0x9800 altiobase=0x9c02 bmaddr=0xa800 -ata2: mask=03 ostat0=50 ostat2=00 -ata2-master: ATAPI 00 00 -ata2-slave: ATAPI 00 00 -ata2: mask=03 stat0=50 stat1=00 -ata2-master: ATA 01 a5 -ata2: devices=01 -ata2: at 0x9800 on atapci0 +pcib2: device atapci0 requested unsupported I/O range 0x0-0x9c00 (decoding +0x9000-0xafff) +ata2: probe allocation failed -pcib2: device atapci0 requested decoded I/O range 0xa402-0xa400 -pcib2: device ata3 requested decoded I/O range 0xa808-0xa80f -ata3: iobase=0xa000 altiobase=0xa402 bmaddr=0xa808 -ata3: mask=03 ostat0=50 ostat2=00 -ata3-master: ATAPI 00 00 -ata3-slave: ATAPI 00 00 -ata3: mask=03 stat0=50 stat1=00 -ata3-master: ATA 01 a5 -ata3: devices=01 -ata3: at 0xa000 on atapci0 +pcib2: device atapci0 requested unsupported I/O range 0x0-0xa400 (decoding +0x9000-0xafff) +ata3: probe allocation failed and then ar disk mirrored with disks on ata[23] is not created. +ar: FreeBSD check1 failed Any hint is appreciated. Thanks in advance. -- NAKAJI Hiroyuki To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mirrored disk on HPT370 is not detected.
It seems NAKAJI Hiroyuki wrote: I checked the difference between them to find that ata device on HPT370 is not detected, +pcib2: device atapci0 requested unsupported I/O range 0x0-0x9c00 (decoding 0x9000-0xafff) +ata2: probe allocation failed You need the options PCI_ALLOW_UNSUPPORTED_IO_RANGE option in your kernel config file, the changes Warner did to the sanity checking of io ranges breaks on more or less all PCI based ATA controllers :( -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with ssh
On Tue, Apr 02, 2002 at 01:48:56AM +0200, Dag-Erling Smorgrav wrote: David O'Brien [EMAIL PROTECTED] writes: On Sat, Mar 30, 2002 at 01:14:07PM +0100, Dag-Erling Smorgrav wrote: David O'Brien [EMAIL PROTECTED] writes: Uh, why does my sequence keep changing when I just hit return??? Because it's generating fake S/Key challenges, and badly. Especially since RELENG_4 does NOT use OPIE. Who this fake S/Key challenge that and turned it on? OpenSSH in RELENG_4 does use S/Key, and generates fake challenges when Yes. But it is obvious it is fake: This is an S/Key challenge: s/key 90 re95460 this is an OPIE challenge: otp-md5 315 re7955 ext so getting an OPIE formatted challenge on RELENG_4 immediately lets someone know it is fake and bogus. the client attempts challenge-response authentication, which is what is used for PAM. I do not follow what you are saying. No, I haven't seen it, but I've had similar reports. It's actually a bug on the server side, in older OpenSSH servers, that is exposed by newer OpenSSH clients. Will OpenSSH 3.1 be MFC'ed soon? Not likely. There are a number of problems that still need fixing. I thought 3.1 was imported due to a security problem with 3.0. Considering I DO want SKeyAuthentication (USENIX is comming up); what is the real fix? Enable it only for servers that need it. I just said I need it. The user from ssh user@server does have a properly setup S/Key entry in /etc/skeykeys It used to be disabled by default in the client, so this shouldn't make much of a difference. I admit to having problems getting this working in the past. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD-localised OpenSSH hangs with Foundry SSH1 server
On Mon, Apr 01, 2002 at 11:32:07PM +0200, Dag-Erling Smorgrav wrote: if the FreeBSD-specific string could be shortened (to at most 11 chars, which is exactly enough to put des20020307 in there for example ;-), made user-configurable, or altogether removed. Look for VersionAddendum in /etc/ssh/sshd_config (it can be used in ssh_config as well). Uh, no, it does not seem to work in ssh_config, only in sshd_config. Pierre To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mirrored disk on HPT370 is not detected.
sos You need the sos options PCI_ALLOW_UNSUPPORTED_IO_RANGE It workd. Thanks! -- NAKAJI Hiroyuki To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: USB mouse problem
On Sat, Mar 30, 2002 at 03:24:08PM +0200, Andrew Bliznak wrote: On Sat, 30 Mar 2002, Masahide -mac- NODA wrote: Same here, solid lock, debug key not work. If I setup X to use /dev/ums0 computer hang just after startx. All worked with kernel/world from Mar 12. Me too. In my case I use an OmniView USB KVM switch. When I switch to my MacOS X box (which causes the keyboard and mouse to be disconnected from the FreeBSD machine), FreeBSD locks solid. This was working fine in -CURRENT just 2 weeks ago, and it works fine in -STABLE as of today. One of the recent NetBSD merges must be causing this. Any thoughts, Joe? - Murray msg36884/pgp0.pgp Description: PGP signature
Please HELP with Zyxel Prestige P641 (router adsl)
Please, I need some help, my adsl access router (Zyxel Prestige P641) blow up last night (really exploded). A sourface mounted capacitor CP53 exploded destroying mother board. I need a zoomed scan of that area or even better of schematics of power section of the router, to try to adjust myself. You can see a zoomed image of explosion here: http://www.torrini.org/riccardo/images/p641-explosion.jpg Yes, this is a bit of off topic, please excuse me, but with router I can continue cvsup/debug/report of -CURRENT ;^) Thanks in advance, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
