Re: 3DNow! support?
On Mon, 10 May 1999, W Gerald Hicks wrote: > > > Is anyone planning on upgrading the binutils gas to a later version > > > so that we can get 3DNow! support? I'd like to use it, but I can't > > > seem to get binutils to work right manually. > > > I will update binutils when/if 2.9.2 comes out. > > I've seen some post-2.9.1 patches from the Debian folks... > I'm waiting for the official gnu release. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/pci pcisupport.c
On Tue, 11 May 1999, NAKAGAWA Yoshihisa wrote: > > I was thinking of doing this, the same as alpm and intpm: > > > > case 0x: > > #if NUHCI > 0 > > return NULL; > > #else > > return "VIA blah USB controller"; > > #endif > > It depends on old-config, so poor mechanism. newconfig already > implimented best match probe/attach. And a very useful mechanism it is. Which is why I implemented priority ordered probes in -current. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Tonight make world failed at isdnmonitor...
On Mon, 10 May 1999, Steve Kargl wrote: > I sent a patch for this about 8 hours ago. No one seems > to read -current. well it still is broken and i must of missed that patch somewhere in my mail, 3:58 a.m east coast time tuesday 11 rob To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
ROOTDEVNAME changes break MFS_ROOT only kernels
Prior to the ROOTDEVNAME changes, I used to build embedded kernels with MFS_ROOT and MFS_ROOT_SIZE options, plus the config line as: config foo root on wd0 but _without_ any disk devices or disk controllers. The "root on wd0" on the config line was to satisfy the config(8) syntax, but was overriden by the use of MFS_ROOT AFAIK. After the ROOTDEVNAME changes, the kernel always tries to mount a root file system from a _device_ regardless of the MFS_ROOT option. Such a kernel will always panic with: "error 6: panic: cannot mount root (2)". FWIW, this is the kernel config file for an embedded kernel (called gizmo): # # GIZMO -- A little gizmo thingy. # machine "i386" cpu "I386_CPU" ident GENERIC maxusers2 options MATH_EMULATE# Support for x87 emulation options INET# InterNETworking options MFS # Memory filesystem options "COMPAT_43" # Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE# Allow users to grab the console options FAILSAFE# Be conservative options MFS_ROOT# Use a memory file system as root. options MFS_ROOT_SIZE=2048 # Space for MFS root filesystem. options INIT_PATH="/gizmo" config gizmo controller isa0 device npx0at nexus? port IO_NPX irq 13 device sio0at isa? port IO_COM1 flags 0x10 irq 4 device ed0 at isa? port 0x300 irq 11 iomem 0xd8000 pseudo-device loop pseudo-device ether Nice and simple, but after the ROOTDEVNAME changes, it cannot work. Sulk. The ROOTDEVNAME stuff needs to be fixed to allow this. Local disks and disk controllers should be optional. -- John Birrell - j...@cimlogic.com.au; j...@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Tonight make world failed at isdnmonitor...
> > I sent a patch for this about 8 hours ago. No one seems > > to read -current. > well it still is broken and i must of missed that patch somewhere in my > mail, > > 3:58 a.m east coast time tuesday 11 just read mail, tested Steves fix, committed. 10:23 am central european summer time tuesday 11 The world is round and needs 24 hours to rotate once. ;-) hellmuth -- Hellmuth MichaelisTel +49 40 559747-70 HCS Hanseatischer Computerservice GmbHFax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: SPAM
Chuck Robey writes: > Garrett's points are why I sugggested that it would not be a useable > approach for -questions, newbies, and mabye hackers, 'cause they all get > a fair amount of posts like what Garrett describes. Current and > committers do NOT get such an audience, and the argument doesn't hold > for those lists, which do get spammed. Oh no? I regularly send mail to -current and -committers from at least three different addresses, none of which are subscribed. Listen up. We've been through this before. We all agreed it wouldn't work. If you wanna know why, search the archives instead of making the problem considerably worse by starting (and fueling) threads such as this. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: SPAM
here's an idea..
why not have two addresses for the list.
the first would be the public address, and would be restricted to subscribers.
the second would be a non-published address, which would be unrestricted,
and would feed the published list via a side door.
only the first list would be open for subscriptions.
-- Welcome My Son, Welcome To The Machine --
Bob Vaughan | tec...@{w6yx|tantivy}.stanford.edu | kc6...@w6yx.ampr.org
| P.O. Box 9792, Stanford, Ca 94309-9792
-- I am Me, I am only Me, And no one else is Me, What could be simpler? --
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: Tonight make world failed at isdnmonitor...
> > ===> usr.sbin/i4b/isdnmonitor
> > cc -Os -pipe -mpentium -DDEBUG -I/usr/obj/usr/src/tmp/usr/include -c
> > /usr/src/usr.sbin/i4b/isdn
> > monitor/main.c
> > /usr/src/usr.sbin/i4b/isdnmonitor/main.c:103: `major' redeclared as
> > different kind of symbol
> > /usr/obj/usr/src/tmp/usr/include/sys/types.h:114: previous declaration of
> > `major'
> > /usr/src/usr.sbin/i4b/isdnmonitor/main.c:104: `minor' redeclared as
> > different kind of symbol
> > /usr/obj/usr/src/tmp/usr/include/sys/types.h:108: previous declaration of
> > `minor'
> > {standard input}: Assembler messages:
> > {standard input}:1510: Fatal error: Symbol minor already defined.
> > *** Error code 1
>
> tell phk thanks this ones related to his changes to types.h as well
phk has another patch in the pipeline right now that fixes this (ie:
major() etc become macros again in userlant.) I'd have jumped in and
tweaked types.h to fix this particular problem, but that would be just
adding more deltas to dead-end code. I think phk was planning a
checkpoint commit sometime shortly. If he gets delayed, I'll give types.h
a tweak to avoid the problems and to buy some time.
Please remember, this is -current, we've got to expect things to be broken
every so often - but on the other hand, staying broken for too long is an
inconvenience for the developers who -current is intended for.
> Rob
Cheers,
-Peter
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Doug Rabson wrote ... > On Sun, 9 May 1999, Wilko Bulte wrote: > > > As Doug Rabson wrote ... > > > On Sun, 9 May 1999, Khaled Daham wrote: > > > > > > > Hello folks > > > > > > > > I cvsupped,made world, built a kernel today and from now on the de > > > > > > Some tulip boards in alpha systems don't autonegociate properly so the SRM > > > has a way of forcing them to a particular mode. A change was made recently > > > > Recently... I think it's been there for a couple of years. > > Maybe you are remembering a NetBSD change? We just started doing the same > thing in FreeBSD recently. Oops I was confusing things with another email about the messages the driver spits out on dma not keeping up. > > > to respect the SRM setting instead of using autoneg. The variable is > > > typically called ewa0_mode. To find the right setting, type > > > > > > >>>set ewa0_mode > > > > > > from the SRM prompt and it will give you a list of settings. Choose one, > > > then type e.g.: > > > > > > >>>set ewa0_mode Twisted-Pair > > > > Keep in mind that older SRMs that understand the older Tulip 10/100Mbit > > chips (21140 IRRC) might not recognise the new ones (is that the 21143?) > > > > Bit me once.. > > Yeah. That must be why my 164lx won't netboot. Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit only) worked just dandy. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Make World Fails - minor and major conflict
I am running -current SMP as of last week.
I cvsup'ed last night and started a 'Make -j12 world'.
tomdean
===> usr.sbin/i4b/isdnmonitor
cc -O2 -m486 -pipe -DDEBUG -I/usr/obj/usr/src/tmp/usr/include -c
/usr/src/usr.sbin/i4b/isdnmonitor/main.c
gzip -cn /usr/src/usr.sbin/i4b/isdnmonitor/isdnmonitor.8 > isdnmonitor.8.gz
/usr/src/usr.sbin/i4b/isdnmonitor/main.c:103: `major' redeclared as different
kind of symbol
/usr/obj/usr/src/tmp/usr/include/sys/types.h:114: previous declaration of
`major'
/usr/src/usr.sbin/i4b/isdnmonitor/main.c:104: `minor' redeclared as different
kind of symbol
/usr/obj/usr/src/tmp/usr/include/sys/types.h:108: previous declaration of
`minor'
{standard input}: Assembler messages:
{standard input}:1519: Fatal error: Symbol minor already defined.
*** Error code 1
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: Tonight make world failed at isdnmonitor...
On Tue, 11 May 1999, Hellmuth Michaelis wrote: > > > > I sent a patch for this about 8 hours ago. No one seems > > > to read -current. > > well it still is broken and i must of missed that patch somewhere in my > > mail, > > > > 3:58 a.m east coast time tuesday 11 > > just read mail, tested Steves fix, committed. > > 10:23 am central european summer time tuesday 11 > > The world is round and needs 24 hours to rotate once. ;-) > > hellmuth O.k. I admit it i've been an ass over changing the names of 2 variables in what was it 8 lines of code. rob To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Make World Fails - minor and major conflict
On Tue, 11 May 1999, Thomas Dean wrote: > I am running -current SMP as of last week. > > I cvsup'ed last night and started a 'Make -j12 world'. > cvsup again that should fix it. if it doesnt add my or anything else for that matter, to all occurances of the variable minor and major in that file. Rob To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Anybody actually using gigabit ethernet?
I'm wondering if anybody out there has actually done any experimentation with gigabit ethernet boards using the Alteon Tigon driver. I know that it works on my hardware, but it's nice to actually have some feedback from people so that I know if it's actually working worth a damn. So far I have not heard a peep out of anybody, other than a couple of people who were nice enough to help out with some driver testing, and that was months ago. I usually consider this a good thing, because it means that at least nobody is complaining. But when people ask me "hey Bill, how well do these boards work with FreeBSD?" all I can tell them is that they seem to work okay in my limited test environment. This does not exactly provide a lot of motivation to go out and buy some gigabit ethernet cards. Also, I only have access to a limited selection of cards (I have a 3Com and a Netgear board, and others have tested AceNIC boards) so I don't know for sure if some of the ones that I claim to support actually work. (I don't have any reason to believe they won't, but Murphy's Law applies.) I also don't have access to a gigabit switch, so my testing is limited to blasting traffic between two hosts through a fiber patch. So, if anybody is actually using a Tigon-based gigabit board with STABLE or CURRENT, let me know. Is it working reliably? Is performance good? Is it bad? Inquiring minds want to know. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: wp...@ctr.columbia.edu | Center for Telecommunications Research Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City = "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" = To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
In reading your message I felt compelled to ask you a question. Are you using gb end-to-end? That probably isn't a good idea because in TCP the sequence numbers can wrap within timeout periods and the data stream become undetectably (from a TCP perspective) corrupt. -- Dennis Glatting Copyright (c) 1999 Software Munitions To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
Of all the gin joints in all the towns in all the world, Dennis Glatting had to walk into mine and say: > In reading your message I felt compelled to ask you a question. Are > you using gb end-to-end? That probably isn't a good idea because in > TCP the sequence numbers can wrap within timeout periods and the data > stream become undetectably (from a TCP perspective) corrupt. You didn't read what I said. I don't have a gigabit ethernet switch. I only have cards. Therefore the *only* way I can test the operation of the driver and adapters is to connect two machines with gigabit cards back to back with a patch cable. This automatically implies 'using gb end-to-end.' As for corruption due to TCP sequence number wrapping, I don't know what to tell you. I never noticed such behavior in my tests, but that's why I'm asking for feedback from other people. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: wp...@ctr.columbia.edu | Center for Telecommunications Research Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City = "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" = To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Feedback on new drivers (was: Re: Anybody actually using gigabit ethernet?)
There should be a more general mechanism for this. I have the same problem with the USB stuff. 100+ people on the usb-bsd mailing list and only answers to directed questions. What about, like 'HEADS-UP', a 'FEEDBACK: ' message that should invite people to send 'it works' messages. And maybe provide a template of commands to cut and paste. Something like: (echo it works for me uname -a ident dmesg | grep '^' ) | mail -s "" per...@address assuming that people are too lazy to type things in themselves. Cheers, Nick On Tue, 11 May 1999, Bill Paul wrote: > I'm wondering if anybody out there has actually done any experimentation > with gigabit ethernet boards using the Alteon Tigon driver. I know that > it works on my hardware, but it's nice to actually have some feedback > from people so that I know if it's actually working worth a damn. So > far I have not heard a peep out of anybody, other than a couple of people > who were nice enough to help out with some driver testing, and that > was months ago. > > I usually consider this a good thing, because it means that at least > nobody is complaining. But when people ask me "hey Bill, how well do > these boards work with FreeBSD?" all I can tell them is that they seem > to work okay in my limited test environment. This does not exactly > provide a lot of motivation to go out and buy some gigabit ethernet > cards. > > Also, I only have access to a limited selection of cards (I have a 3Com > and a Netgear board, and others have tested AceNIC boards) so I don't > know for sure if some of the ones that I claim to support actually > work. (I don't have any reason to believe they won't, but Murphy's > Law applies.) I also don't have access to a gigabit switch, so my > testing is limited to blasting traffic between two hosts through a > fiber patch. > > So, if anybody is actually using a Tigon-based gigabit board with > STABLE or CURRENT, let me know. Is it working reliably? Is performance > good? Is it bad? Inquiring minds want to know. > > -Bill > > -- > = > -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu > Work: wp...@ctr.columbia.edu | Center for Telecommunications Research > Home: wp...@skynet.ctr.columbia.edu | Columbia University, New York City > = > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" > = > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
On Tue, 11 May 1999, Dennis Glatting wrote: > In reading your message I felt compelled to ask you a question. Are > you using gb end-to-end? That probably isn't a good idea because in > TCP the sequence numbers can wrap within timeout periods and the data > stream become undetectably (from a TCP perspective) corrupt. Isn't that adequately covered by the PAWS extension from RFC 1323? Ben @narcissus.net -- finally To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
> You didn't read what I said. I don't have a gigabit ethernet switch. > I only have cards. Therefore the *only* way I can test the operation > of the driver and adapters is to connect two machines with gigabit > cards back to back with a patch cable. This automatically implies 'using > gb end-to-end.' > > As for corruption due to TCP sequence number wrapping, I don't know > what to tell you. I never noticed such behavior in my tests, but that's > why I'm asking for feedback from other people. The obvious answer to the TCP sequence number problem is RFC 1323. I assume anybody who wants to use gigabit Ethernet over significant distances *will* use RFC 1323, if they are interested in any performance at all. Otherwise the 64 kbyte window will kill you. As for me, I have tested the driver with Netgear cards. Works great here, I got 470 Mbps (effective application to application) with ttcp, running back to back on a PII-350 and a Celeron 300A (overclocked to 337, thus PCI bus clocked at 37.5 Mhz). The limit in my case is clearly the CPU. However I did *not* see any better performance when I turned on jumbo frames. Next I'll put one card in an old PPro-200 and see what I can get from that. Steinar Haug, Nethelp consulting, sth...@nethelp.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
Snob Art Genre wrote: > On Tue, 11 May 1999, Dennis Glatting wrote: > > > In reading your message I felt compelled to ask you a question. Are > > you using gb end-to-end? That probably isn't a good idea because in > > TCP the sequence numbers can wrap within timeout periods and the data > > stream become undetectably (from a TCP perspective) corrupt. > > Isn't that adequately covered by the PAWS extension from RFC 1323? Well, maybe it would, but [1:09am]~src/etc-111# grep tcp_ext defaults/rc.conf tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). It's off by default. :-( Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
< As for me, I have tested the driver with Netgear cards. Works great here, > I got 470 Mbps (effective application to application) with ttcp, running > back to back on a PII-350 and a Celeron 300A (overclocked to 337, thus PCI > bus clocked at 37.5 Mhz). The limit in my case is clearly the CPU. However > I did *not* see any better performance when I turned on jumbo > frames. I'm buying one of these cards today ($319.99 from NECX) and will stick it into a machine here on our new Gigabit backbone. I'm particularly interested to test out the VLAN support, since my Secret Plan is to have this one machine serve as the DHCP server for the whole Lab (17 subnets). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | 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 majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
On Wed, 12 May 1999, Peter Wemm wrote: > > Isn't that adequately covered by the PAWS extension from RFC 1323? > > Well, maybe it would, but > > [1:09am]~src/etc-111# grep tcp_ext defaults/rc.conf > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). > > It's off by default. :-( IMO that's a good thing, because for some reason, the RFC 1323 extensions break a lot of older terminal servers. Ben @narcissus.net -- finally To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
RE: Anybody actually using gigabit ethernet?
> IMO that's a good thing, because for some reason, the RFC 1323 > extensions break a lot of older terminal servers. One could argue that it's more accurate to state that the terminal servers break RFC1323, but alas the effect is the same. DS To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
On Wed, May 12, 1999 at 01:11:43AM +0800, Peter Wemm wrote: > Snob Art Genre wrote: > > On Tue, 11 May 1999, Dennis Glatting wrote: > > > > > In reading your message I felt compelled to ask you a question. Are > > > you using gb end-to-end? That probably isn't a good idea because in > > > TCP the sequence numbers can wrap within timeout periods and the data > > > stream become undetectably (from a TCP perspective) corrupt. > > > > Isn't that adequately covered by the PAWS extension from RFC 1323? > > Well, maybe it would, but > > [1:09am]~src/etc-111# grep tcp_ext defaults/rc.conf > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). No.. it's _on_ by default. (YES to disallow.) Joe -- Josef KarthauserFreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [...@pavilion.net, j...@uk.freebsd.org, j...@tao.org.uk] To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
Where did you learn to read? Chuck Youse Director of Systems cyo...@cybersites.com On Tue, 11 May 1999, Josef Karthauser wrote: > On Wed, May 12, 1999 at 01:11:43AM +0800, Peter Wemm wrote: > > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). > > No.. it's _on_ by default. (YES to disallow.) > > Joe > -- > Josef Karthauser FreeBSD: How many times have you booted today? > Technical Manager Viagra for your server (http://www.uk.freebsd.org) > Pavilion Internet plc. [...@pavilion.net, j...@uk.freebsd.org, > j...@tao.org.uk] To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Anybody actually using gigabit ethernet?
Isn't it more appropriate to ask where he didn't learn to read ? :-) Poul-Henning In message , Chuc k Youse writes: > >Where did you learn to read? > >Chuck Youse >Director of Systems >cyo...@cybersites.com > > >On Tue, 11 May 1999, Josef Karthauser wrote: > >> On Wed, May 12, 1999 at 01:11:43AM +0800, Peter Wemm wrote: > >> > tcp_extensions="NO" # Disallow RFC1323 extensions (or YES). >> >> No.. it's _on_ by default. (YES to disallow.) >> >> Joe >> -- >> Josef Karthauser FreeBSD: How many times have you booted today? >> Technical ManagerViagra for your server (http://www.uk.freebsd.org) >> Pavilion Internet plc. [...@pavilion.net, j...@uk.freebsd.org, >> j...@tao.org.uk] > > > >To Unsubscribe: send mail to majord...@freebsd.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Scanners
i got a new UMAX Atrsa 1220P scanner, i have no idea how to configure this in FreeBSD or Linux (or if i even can), im on 4.0-CURRENT. == Tomer Weller s...@i.am well...@netvision.net.il "Drugs are good, and if you do'em pepole think that you're cool", NoFX To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: somebody has broken sysctlbyname() in -current
On Sat, 8 May 1999, Peter Wemm wrote: > It's interesting that the ANSI emulation in loader(8) is good enough to do > full-screen displays. It still seems to make sense to move userconfig-like > functionality into the pre-kernel stages including moving config(8)'s hints > to a loaded and parsed file. Forth, bah.. :-] Heh... To tell you the truth, that was my initial dream which prompted me to start writing it. It could be done now, really... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
On Mon, 10 May 1999, Wilko Bulte wrote: > > > > Yeah. That must be why my 164lx won't netboot. > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > only) worked just dandy. That reminds me. Does your Alpine still work after the new-bus stuff? I wasn't sure I hadn't broken it when I changed the apecs driver. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
the new config and booting
I switched to the new config(8) today, where the ``config kernel root on..'' line is no longer tolerated in the config file. I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't necessary before. I know I can probably put something into /boot/ to automate this. Just thought I'd report my (negative) experience. Gary Jennejohn Home - ga...@muc.de Work - ga...@fkr.dec.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: the new config and booting
In message <199905111939.vaa02...@peedub.muc.de>, Gary Jennejohn writes: >I switched to the new config(8) today, where the ``config kernel root on..'' >line is no longer tolerated in the config file. > >I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't >necessary before. > >I know I can probably put something into /boot/ to automate this. >Just thought I'd report my (negative) experience. What's your config ? It sounds like the boot code isn't telling the kernel the right thing... I belive it picks the bootmajor from the type field in the disklabel. (right Mike ?) So do you have a IDE/ATA disk labeled as SCSI by any chance ? -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/pci pcisupport.c
Doug Rabson wrote: > On Tue, 11 May 1999, NAKAGAWA Yoshihisa wrote: > > > > I was thinking of doing this, the same as alpm and intpm: > > > > > > case 0x: > > > #if NUHCI > 0 > > > return NULL; > > > #else > > > return "VIA blah USB controller"; > > > #endif > > > > It depends on old-config, so poor mechanism. newconfig already > > implimented best match probe/attach. > > And a very useful mechanism it is. Which is why I implemented priority > ordered probes in -current. For the sake of the thread, this got committed a day or two ago, and these hacks have been replaced with a low priority match. Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Tonight make world failed at isdnmonitor...
According to Hellmuth Michaelis: > hellmuth BTW do you plan to import i4b 0.80 into CURRENT ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Incorrect memory sizes reported
I'm not sure if this is related to the bug I found in 3.1, regarding mmaping devices, then forking, but with my -current NFS server: PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd 257M? :) ps shows similar info... Kevin To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
RE: Incorrect memory sizes reported
This is normal. It's using a lot of virtual memory. Fortunately, virtual memory is cheap. DS > I'm not sure if this is related to the bug I found in 3.1, > regarding mmaping > devices, then forking, but with my -current NFS server: > > PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND > 139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd > > 257M? :) ps shows similar info... > > > Kevin To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Incorrect memory sizes reported
> > This is normal. It's using a lot of virtual memory. Fortunately, virtual > memory is cheap. > > DS > > > I'm not sure if this is related to the bug I found in 3.1, > > regarding mmaping > > devices, then forking, but with my -current NFS server: > > > > PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND > > 139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd > > > > 257M? :) ps shows similar info... > > > > > > Kevin > > Ok, I stand corrected then I hadn't seen this before... 2.2.8: root 14127 0.0 0.1 176 492 ?? Ss5:14PM0:00.00 rpc.statd 3.1: root 853 0.0 0.7 172 416 ?? Ss7:18AM 0:00.00 rpc.statd There still is the issue I described a while back that would make children show negative numbers in 'size' though, that i can confirm isn't sucking that much VM. Kevin To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: FBSDBOOT.EXE
Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF. If anybody else needs it, please let me know and I'll see what I can do for you. ps. I had to use my old Microsoft Visual C++ (ver 1.5) to do this modification. Carlos C. Tapang http://www.genericwindows.com -Original Message- From: Jordan K. Hubbard To: Carlos C. Tapang Cc: freebsd-current@FreeBSD.ORG Date: Saturday, May 01, 1999 5:54 PM Subject: Re: FBSDBOOT.EXE >> Is there anybody out there working on upgrading fbsdboot.exe so that it can >> recognize ELF? > >I believe that fbsdboot.exe has, instead, simply been retired. Sorry >I don't have better news than this. > >- Jordan > > >To Unsubscribe: send mail to majord...@freebsd.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
problem with dev_t changes and pageout..
It looks like something has come unstuck: Fatal trap 12: page fault while in kernel mode mp_lock = 0002; cpuid = 0; lapic.id = fault virtual address = 0x28 fault code = supervisor read, page not present instruction pointer = 0x8:0xc017bb67 stack pointer = 0x10:0xc5d97de4 frame pointer = 0x10:0xc5d97df0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 2 (pagedaemon) interrupt mask = net bio cam <- SMP: XXX kernel: type 12 trap, code=0 Stopped at spec_strategy+0x93: movl0x28(%edx),%eax ^^^ %edx = null db> trace spec_strategy(c5d97e1c) at spec_strategy+0x93 swap_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at swap_pager_putpages+0x3e1 default_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at default_pager_putpages+0x17 vm_pageout_flush(c5d97ecc,2,0,c5d97eb0,c02182cf) at vm_pageout_flush+0x91 vm_pageout_clean(c04d6b60,8000,c013e290,2000,c5d97f78) at vm_pageout_clean+0x1f1 vm_pageout_scan(8000,c02789c0,c02789c0,c5d97fac,c013e2c3) at vm_pageout_scan+0x45e vm_pageout(c5d8fdf7,c0255500,c02789c0,c020c640,c020c748) at vm_pageout+0x221 kproc_start(c02789c0) at kproc_start+0x33 fork_trampoline(10b8a0,d88e,18b8c08e,8e00,24448be0) at fork_trampoline+0x30 db> ps pid proc addruid ppid pgrp flag stat wmesg wchan cmd 438 c680da40 c6818000 495 282 277 04 3 biord c332d9c0 p4d 437 c5d8c340 c6802000 433 417 415 004084 3 piperd c6760660 tee 436 c680dd00 c681 433 417 415 004004 3 biord c33626f8 p4 418 c680dba0 c6815000 433 415 415 004084 3 piperd c6760700 mail 417 c680de60 c680e000 433 415 415 004084 3wait c680de60 sh [..] The offending line in spec_strategy is: (*bdevsw(bp->b_dev)->d_strategy)(bp); d_strategy was null.. I'm still looking. (I think this is the first time the box paged out since booting a few hours ago, it's got 128M, but p4d has got a lot of stuff to deal with and can hit a vsize of 70MB or so.) Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Nt source licenses...
Hi, maybe i am the last one in the world to know, but were you guys aware of this: http://research.microsoft.com/programs/NTSrcLicInfo.htm Microsoft makes Windows NT source code available to universities and other "not-for-profit" research institutions at no charge. Currently, there are over 55 universities and government agencies with source licenses. ... I still have to check the exact conditions though. The above web page says this: Features of the license * No cost * Intellectual property created with the use of NT source code is owned by the researcher. * Source licensees can share source or other source-based work with other NT Source licensees. * Source is licensed to the requesting organization, not individuals to insure broad internal access. * No employment restrictions as the result of viewing or using the source. cheers luigi ---+- Luigi RIZZO, lu...@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) http://www.iet.unipi.it/~luigi/ngc99/ First International Workshop on Networked Group Communication ---+- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: de driver problem
As Doug Rabson wrote ... > On Mon, 10 May 1999, Wilko Bulte wrote: > > > > > > > Yeah. That must be why my 164lx won't netboot. > > > > Could well be. My Aspen Alpine refused to with a DE500. A DE435 (10mbit > > only) worked just dandy. > > That reminds me. Does your Alpine still work after the new-bus stuff? I > wasn't sure I hadn't broken it when I changed the apecs driver. My Alpine is on a not so current -current, but it is rebuilding world now. Stay tuned, I can probably tell you more tomorrow. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: the new config and booting
> I switched to the new config(8) today, where the ``config kernel root on..'' > line is no longer tolerated in the config file. > > I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't > necessary before. > > I know I can probably put something into /boot/ to automate this. > Just thought I'd report my (negative) experience. Can you tell us what it's trying to mount vs. what it should be mounting? I'm in the process of rewriting parts of this code again to fix the mess that's been made of it. I'm not sure I'll get all the way, but in conjunction with some small changes in the loader it *should* make problems like yours history. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: FBSDBOOT.EXE
Hi, At 15:22 11/05/99 -0700, you wrote: >Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF. >If anybody else needs it, please let me know and I'll see what I can do for >you. I'm going to have a use for it RSN >ps. I had to use my old Microsoft Visual C++ (ver 1.5) to do this >modification. Ick. I was hoping for a 32bit build at least, although I suppose it doesn't matter much. Will you be posting diffs? -- Bob Bishop +44 118 977 4017 r...@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/pci pcisupport.c
> For the sake of the thread, this got committed a day or two ago, and these > hacks have been replaced with a low priority match. Why do you use another mechanism of 4.4BSD ? Don't loss time and loss inter-operability between other BSDs. -- NAKAGAWA, Yoshihisa y-nak...@nwsl.mesh.ad.jp nakag...@jp.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: tosha after CAM changes
I must have missed a step making world, so everything works just fine now. Thanks for the concern. -- Eric Hodel hodel...@seattleu.edu "If you understand what you're doing, you're not learning anything." -- A. L. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
/usr/src/release/Makefile patch
Hi,
Could you please consider the following patch to
/usr/src/release/Makefile? It may not be entirely correct,
but it allows a 'cd /usr/src/release && make release' to
run to completion. In the kernel makefile, 'kernel'
is not a target, ${KERNEL} is, and ${KERNEL} has the value
'GENERIC'.
Comments welcome!
Thanks!
John
# $Id: Makefile,v 1.482 1999/05/09 17:00:04 obrien Exp $
--- /snap/release/usr/src/release/Makefile~ Tue May 11 23:50:52 1999
+++ /snap/release/usr/src/release/Makefile Tue May 11 23:43:49 1999
@@ -634,9 +634,9 @@
@rm -f ${RD}/kernels/${KERNEL}
@cd ${.CURDIR}/../sys/${MACHINE_ARCH}/conf && config ${KERNEL}
@cd ${.CURDIR}/../sys/compile/${KERNEL} && \
- make depend && \
- make kernel && \
- cp kernel ${RD}/kernels/${KERNEL}
+ make depend && pwd && \
+ make ${KERNEL} && \
+ cp ${KERNEL} ${RD}/kernels/${KERNEL}
#
# --==## Put a filesystem into a BOOTMFS kernel ##==--
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/pci pcisupport.c
> Because 4.4BSD got it wrong. It has always been the belief of the > FreeBSD Project's management that 4.4's totally-static configuration No! 4.4BSD mechanism is good. Newconfig already support dynamic configuration and *good* module support (not yet merge newconfig CVS). > mechanism was unacceptable -- else we would have used it years ago. It is not formal core decision. > Our policy in all areas has been that we'd rather do the Right Thing > than follow the crowd. new-bus is wrong way. You are misunderstanding 4.4BSD mechanism. -- NAKAGAWA, Yoshihisa y-nak...@nwsl.mesh.ad.jp nakag...@jp.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Incorrect memory sizes reported
hi, there! On Tue, 11 May 1999, Kevin Day wrote: > I'm not sure if this is related to the bug I found in 3.1, regarding mmaping > devices, then forking, but with my -current NFS server: > > PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND > 139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd > > 257M? :) ps shows similar info... got the same on -stable machine (built 28 Apr) about a week ago /fjoe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: FBSDBOOT.EXE
hi, there! On Tue, 11 May 1999, Carlos C. Tapang wrote: > Because I need it, I have upgraded fbsdboot.exe so now it can recognize ELF. > If anybody else needs it, please let me know and I'll see what I can do for > you. > ps. I had to use my old Microsoft Visual C++ (ver 1.5) to do this > modification. where can I get the diffs or binaries? /fjoe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
