Re: Config problems
duh... that was too simple... :-) = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Mon, 26 Jun 2000, Peter Wemm wrote: > Chuck Robey wrote: > > > device da0 at scbus 0 target 0 > > device da1 at scbus 0 target 2 > > device da2 at scbus 1 target 1 > > > > device cd0 at scbus? > > device cd1 at scbus? > > Change 'scbus 0' to 'scbus0' and 'scbus 1' to 'scbus1' and the gethints.pl > script will understand it. > > Cheers, > -Peter > -- > Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Config problems
Chuck Robey wrote: > deviceda0 at scbus 0 target 0 > deviceda1 at scbus 0 target 2 > deviceda2 at scbus 1 target 1 > > devicecd0 at scbus? > devicecd1 at scbus? Change 'scbus 0' to 'scbus0' and 'scbus 1' to 'scbus1' and the gethints.pl script will understand it. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Config problems
On Mon, 26 Jun 2000, Peter Wemm wrote: > > What does ``hint.scbus.1.bus="0"'' mean? Do I have to stick a number > > after the "device ahc" and "device scbus" lines (the NOTES file > > doesn't). Are there any other oddities I ought to know of? > > It works the same as the other devices: > > 'device scbus1 at ahc1 bus 0' > > becomes: > > hint.scbus.1.at="ahc1" > hint.scbus.1.bus="0" > > When you have a trailing '?' character in an 'at' binding, you leave it out. > eg: hint.scbus.1.at="ahc" (which would have meant "device scbus1 at ahc?") > > You do not stick numbers after the 'device ahc' and 'device scbus' lines. > The device wiring comes from the hints (either /boot/device.hints or > the statically compiled in hints) > > Perhaps you should post your old *ORIGINAL* config file and I'll do a worked > example conversion... Sure, OK. Here's the last one I've been using, before I did any editing. I have five scsi devices. The disks are wired down, the cd's are not wired down here, but they show up on ahc1 targets 5 & 6 (show them floating, for more variety in the example). machine i386 cpu I586_CPU cpu I686_CPU ident CH maxusers64 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional, these are the defaults: options NCPU=2 # number of CPUs options NBUS=4 # number of busses options NAPIC=1 # number of IO APICs options NINTR=24# number of INTs options SYSVSHM options SYSVSEM options INCLUDE_CONFIG_FILE options SYSVMSG options MSGBUF_SIZE=40960 options NETATALK#Appletalk communications protocols options NETGRAPH#netgraph(4) system options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # Lets always enable the kernel debugger for SMP. options DDB options GPL_MATH_EMULATE#Support for x87 emulation via options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS_ROOT options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=8000 #Be pessimistic about Joe SCSI device options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SOFTUPDATES options VESA# needs VM86 defined too!! options COMPAT_LINUX # If you see the "calcru: negative time of %ld usec for pid %d (%s)\n" # message you probably have some broken sw/hw which disables interrupts # for too long. You can make the system more resistant to this by # choosing a high value for NTIMECOUNTER. The default is 5, there # is no upper limit but more than a couple of hundred are not productive. # A better strategy may be to sysctl -w kern.timecounter.method=1 options NTIMECOUNTER=20 options ROOTDEVNAME=\"ufs:da0s1a\" device isa0 device eisa0 #controller pnp0 device pci0 device fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. device ahc0 device ahc1 device scbus0 at ahc0 device scbus1 at ahc1 device pcm0 device bktr0 device iicbus0 device iicbb0 device smbus0 # The Numeric Processing eXtension driver. This should be configured if # your machine has a math co-processor, unless the coprocessor is very # buggy. If it is not configured then you *must* configure math emulation # (see above). If both npx0 and emulation are configured, then only npx0 # is used (provided it works). device npx0at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 device da0 at scbus 0 target 0 device da1 at scbus 0 target 2 device da2 at scbus 1 target 1 device cd0 at scbus? device cd1 at scbus? # The keyboard controller; it controlls the keyboard and the PS/2 mouse. device atkbdc0 at isa? port IO_KBD # The AT keyboard device atkbd0 at atkbdc? irq 1 # new syscons stuff device vga0at isa? port ? device s
Re: Config problems
Chuck Robey wrote: > On Sun, 25 Jun 2000, Kenneth Wayne Culver wrote: > > > Hey chuck, except for the SMP stuff, your config looks mostly like mine (I > > only have a cpu line for i686) Let me know if there's anything I can do to > > help though. > > I'm about ready to post again, so this is good timing. > > I got the totally vague warning from gethints.pl to quiet by making my > disk section look much like the NOTES file. I then ran it by a brand new > config, and out spewed more than 25 errors. The entire section on wiring > down disks fails, and also all the stuff on npx, even tho that part was > copied verbatim from NOTES. You should get no errors from gethints.pl based on the disk section in NOTES file because those entries are actual hints for device.hints, not something that you put in a config file and feed to gethints.pl. > I have an Adaptec dual channel controller on my motherboard, and I have 3 > disks and 2 cdroms, which I want to wire down. There's lines in the NOTES > examples whose meanings just make no sense to me. Let me do a bit of > quoting: > > [from NOTES] > hint.scbus.0.at="ahc0" > hint.scbus.1.at="ahc1" > hint.scbus.1.bus="0" > hint.scbus.3.at="ahc2" > hint.scbus.3.bus="0" > hint.scbus.2.at="ahc2" > hint.scbus.2.bus="1" > hint.da.0.at="scbus0" > hint.da.0.target="0" > hint.da.0.unit="0" > hint.da.1.at="scbus3" > hint.da.1.target="1" > hint.da.2.at="scbus2" > hint.da.2.target="3" > hint.sa.1.at="scbus1" > hint.sa.1.target="6" > > > What does ``hint.scbus.1.bus="0"'' mean? Do I have to stick a number > after the "device ahc" and "device scbus" lines (the NOTES file > doesn't). Are there any other oddities I ought to know of? It works the same as the other devices: 'device scbus1 at ahc1 bus 0' becomes: hint.scbus.1.at="ahc1" hint.scbus.1.bus="0" When you have a trailing '?' character in an 'at' binding, you leave it out. eg: hint.scbus.1.at="ahc" (which would have meant "device scbus1 at ahc?") You do not stick numbers after the 'device ahc' and 'device scbus' lines. The device wiring comes from the hints (either /boot/device.hints or the statically compiled in hints) Perhaps you should post your old *ORIGINAL* config file and I'll do a worked example conversion... Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Config problems
Chuck Robey wrote: > I am getting a config error with the new gethints.pl stuff: > > unrecognized config token 1 This means the decoder for 'device ed0 at isa? flags 1' style lines did not like what was in one of your device lines. I have added a new line number message in the error so that it should be easier to spot what is going on. /home/ncvs/src/sys/i386/conf/gethints.pl,v <-- gethints.pl new revision: 1.5; previous revision: 1.4 Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Config problems
Well, I think maybe you have to put a number in if you want stuff wired down.. but basically I'm not sure if all the kinks have been worked out yet... = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 25 Jun 2000, Chuck Robey wrote: > On Sun, 25 Jun 2000, Kenneth Wayne Culver wrote: > > > Hey chuck, except for the SMP stuff, your config looks mostly like mine (I > > only have a cpu line for i686) Let me know if there's anything I can do to > > help though. > > I'm about ready to post again, so this is good timing. > > I got the totally vague warning from gethints.pl to quiet by making my > disk section look much like the NOTES file. I then ran it by a brand new > config, and out spewed more than 25 errors. The entire section on wiring > down disks fails, and also all the stuff on npx, even tho that part was > copied verbatim from NOTES. > > I have an Adaptec dual channel controller on my motherboard, and I have 3 > disks and 2 cdroms, which I want to wire down. There's lines in the NOTES > examples whose meanings just make no sense to me. Let me do a bit of > quoting: > > [from NOTES] > hint.scbus.0.at="ahc0" > hint.scbus.1.at="ahc1" > hint.scbus.1.bus="0" > hint.scbus.3.at="ahc2" > hint.scbus.3.bus="0" > hint.scbus.2.at="ahc2" > hint.scbus.2.bus="1" > hint.da.0.at="scbus0" > hint.da.0.target="0" > hint.da.0.unit="0" > hint.da.1.at="scbus3" > hint.da.1.target="1" > hint.da.2.at="scbus2" > hint.da.2.target="3" > hint.sa.1.at="scbus1" > hint.sa.1.target="6" > > > What does ``hint.scbus.1.bus="0"'' mean? Do I have to stick a number > after the "device ahc" and "device scbus" lines (the NOTES file > doesn't). Are there any other oddities I ought to know of? > > > Chuck Robey| Interests include C & Java programming, FreeBSD, > [EMAIL PROTECTED] | electronics, communications, and signal processing. > > New Year's Resolution: I will not sphroxify gullible people into looking up > fictitious words in the dictionary. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Config problems
On Sun, 25 Jun 2000, Kenneth Wayne Culver wrote: > Hey chuck, except for the SMP stuff, your config looks mostly like mine (I > only have a cpu line for i686) Let me know if there's anything I can do to > help though. I'm about ready to post again, so this is good timing. I got the totally vague warning from gethints.pl to quiet by making my disk section look much like the NOTES file. I then ran it by a brand new config, and out spewed more than 25 errors. The entire section on wiring down disks fails, and also all the stuff on npx, even tho that part was copied verbatim from NOTES. I have an Adaptec dual channel controller on my motherboard, and I have 3 disks and 2 cdroms, which I want to wire down. There's lines in the NOTES examples whose meanings just make no sense to me. Let me do a bit of quoting: [from NOTES] hint.scbus.0.at="ahc0" hint.scbus.1.at="ahc1" hint.scbus.1.bus="0" hint.scbus.3.at="ahc2" hint.scbus.3.bus="0" hint.scbus.2.at="ahc2" hint.scbus.2.bus="1" hint.da.0.at="scbus0" hint.da.0.target="0" hint.da.0.unit="0" hint.da.1.at="scbus3" hint.da.1.target="1" hint.da.2.at="scbus2" hint.da.2.target="3" hint.sa.1.at="scbus1" hint.sa.1.target="6" What does ``hint.scbus.1.bus="0"'' mean? Do I have to stick a number after the "device ahc" and "device scbus" lines (the NOTES file doesn't). Are there any other oddities I ought to know of? Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Config problems
Hey chuck, except for the SMP stuff, your config looks mostly like mine (I only have a cpu line for i686) Let me know if there's anything I can do to help though. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 25 Jun 2000, Chuck Robey wrote: > I am getting a config error with the new gethints.pl stuff: > > unrecognized config token 1 > > This is with a newly cvsupped system, and I checked the version of > gethints.pl: > > ROOT:/usr/src/sys/i386/conf:472 >cvs status gethints.pl > === > File: gethints.pl Status: Up-to-date > >Working revision:1.4 Sun Jun 18 01:43:22 2000 >Repository revision: 1.4 /home/ncvs/src/sys/i386/conf/gethints.pl,v >Sticky Tag: (none) >Sticky Date: (none) >Sticky Options: (none) > > So I think that's right. My config file before had worked just fine, but > as a test, I went thru it and really tried to make it squeaky clean, but > it didn't seem to get rid of that error. I don't know if this message > indicates a fatal problem or just is a leftover printf, there's damned > little in the way of info in it. > > I don't know, maybe that error message is referring to line 1 of my config > file? Here's the start of the config file: > > machine i386 > > cpu I586_CPU > cpu I686_CPU > ident CH > maxusers64 > > # Create a SMP capable kernel (mandatory options): > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O > > If that doesn't do it, I'm attaching the entire config file to this mail. > > Sure would appreciate a hint; I'm not a perl hacker, but if I gotta become > one to puzzle this out, it's going to take me an long extra while trying > to get me a new kernel. > > > Chuck Robey| Interests include C & Java programming, FreeBSD, > [EMAIL PROTECTED] | electronics, communications, and signal processing. > > New Year's Resolution: I will not sphroxify gullible people into looking up > fictitious words in the dictionary. > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
