Re: HEADS UP!: config changes...
On Mon, Jun 26, 2000 at 09:25:37PM +0200, Guido van Rooij wrote: > > How about adding a hint to the hint driver itself. E.g. > > SYNOPSIS > device isa > device ata > hint "hintsfile"# see hint(4) I don't think this is enough. If I botch my hints file enough (and lets say I fat finger some other files in /usr/src/sys/i386/conf. Been there, done that, so lets just assume that it will happen to other people), I should be able to figure out what I need to configure a device from the on-line man-pages. How about something like this: SYNOPSIS device isa device ata hints "hintsfile" # see hints(4) For ata devices on the isa bus, the hint file must contain: the bus that the device resides on (isa), the I/O port and IRQ. For the primary controller, port IO_WD1 and IRQ 14 are used. For the secondary controller, port IO_WD2 and IRQ 15 are used. Maybe the descriptive text could be replaced with something like: See the main text for a description of bus/port/IRQ/flag assignments. And then the main text would include something similar to what I typed above. Then hints(4) could tell the user the syntax they actually have to use and how to use it. If the syntax changes, then we only have to update the generic hints(4). >From looking at "NOTES", mostly ISA devices are affected. ppc/scsi/miibus seem to be the other devices (plus another oddball or two). I think as long as we can decide how to provide the needed information in the device specific man pages, this shouldn't be too hard to actually sit down and do. Then someone also has to sit down and write hints(4) to back it all up :-). -Mike -- Mike Pritchard [EMAIL PROTECTED] or [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
On Sat, Jun 24, 2000 at 06:32:47PM -0500, Mike Pritchard wrote: > > SYNOPSIS > device isa > device ata0 at isa? port IO_WD1 irq 14 > device ata1 at isa? port IO_WD2 irq 15 > > > Should this become: > > SYNOPSIS > device isa > device ata > hint.ata.0.at="isa" > hint.ata.0.port="0x1F0" > hint.ata.0.irq="14" > hint.ata.1.at="isa" > hint.ata.1.port="0x170" > How about adding a hint to the hint driver itself. E.g. SYNOPSIS device isa device ata hint "hintsfile"# see hint(4) -Guido To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Michael Wlliams wrote: > > I'm catching up on email, sorry if this was answered... are you talking > OBP/Forth > on Suns? Try > ok sifting foo > to get a list of words with foo in them (kinda like grep foo). Try > ok see foo > to see the details of the word (if you get forth this will help.) > > If you're not doing forth/obp... my apologies for the irrelevancy. > Mike Williams He is talking loader(8). Mm. Sifting looks cool. I may add it... -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Windows works, for sufficently small values of "works". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
On Sun, 25 Jun 2000 17:27:28 +0900, "Daniel C. Sobral" wrote: > This definitely needs some work. I'm not sure the hints syntax will > change much, if at all. OTOH, I don't know how to approach this. In > other words, suggestions (and specially patches) are welcome. Actually, I think that this is one of those rare occasions where patches are not welcome. :-) Right now, what we want is an assurance that the work we put into updating section 4 will not need to be duplicated because we tackled it too early. Peter, how far ahead are you looking? Can you picture what things will look like for 5.0-RELEASE? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
I'm catching up on email, sorry if this was answered... are you talking OBP/Forth on Suns? Try ok sifting foo to get a list of words with foo in them (kinda like grep foo). Try ok see foo to see the details of the word (if you get forth this will help.) If you're not doing forth/obp... my apologies for the irrelevancy. Mike Williams Mike Smith wrote: > > Uh, 'help' doesn't give you a list of commands I believe. > > Damn, it doesn't either. 'help' is the same as 'help help'. > > Suggestions for a better replacement for ? 'commands'? > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > 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
Re: HEADS UP!: config changes...
Mike Pritchard wrote: > > I just noticed that this change has now made a lot of the section 4 > man pages out of date. > > What is the best way to represent these changes in the man pages? > A good example is ata(4). Currently it reads like this: > > SYNOPSIS > device isa > device ata0 at isa? port IO_WD1 irq 14 > device ata1 at isa? port IO_WD2 irq 15 > > Should this become: > > SYNOPSIS > device isa > device ata > hint.ata.0.at="isa" > hint.ata.0.port="0x1F0" > hint.ata.0.irq="14" > hint.ata.1.at="isa" > hint.ata.1.port="0x170" > > Or some much mess? When will the hints file syntax be nailed down, > so that someone can go in and fix all the man pages without having > to worry about having to go through and do it all again when the > syntax changes? > > Something in the loader man pages should be updated to provide info > on the new hints stuff. Having a man page dedicated to describing the > hints stuff probably would also be a good idea to make it easy for people > to figure out how it works. This definitely needs some work. I'm not sure the hints syntax will change much, if at all. OTOH, I don't know how to approach this. In other words, suggestions (and specially patches) are welcome. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Windows works, for sufficently small values of "works". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
On Tue, Jun 13, 2000 at 04:18:29PM -0700, Peter Wemm wrote: > change *ALL* "device foo0 at isa? port blah etc" to "device foo" - see > GENERIC for examples. All the 'at ? port ?' stuff is handled by > the new /boot/device.hints > See GENERIC - if you use a static limited device (eg: fe, aha, le, etc) > where GENERIC has 'device le 1' *and* you had more than one device > (eg: device le0 at ..., device le1 at ...) then you will need to specify > more units. (eg: "device le 2" in the example above.) > > This is not quite yet complete, but is fully functional. There may still > be some syntax changes to the hints stuff in the future, so pay attention. I just noticed that this change has now made a lot of the section 4 man pages out of date. What is the best way to represent these changes in the man pages? A good example is ata(4). Currently it reads like this: SYNOPSIS device isa device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 Should this become: SYNOPSIS device isa device ata hint.ata.0.at="isa" hint.ata.0.port="0x1F0" hint.ata.0.irq="14" hint.ata.1.at="isa" hint.ata.1.port="0x170" Or some much mess? When will the hints file syntax be nailed down, so that someone can go in and fix all the man pages without having to worry about having to go through and do it all again when the syntax changes? Something in the loader man pages should be updated to provide info on the new hints stuff. Having a man page dedicated to describing the hints stuff probably would also be a good idea to make it easy for people to figure out how it works. -Mike -- Mike Pritchard [EMAIL PROTECTED] or [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Andrzej Bialecki wrote: > > That's fine. However, this practically makes using /boot/loader > mandatory. I still wonder if having some in-kernel interpreter wouldn't > give us more choice, with exactly the same functionality. Of course, it > would have to be run before any probing starts... If you do not want to use loader, then use the "hints" option in the config file. What is going to get deprecated, though, is being able to userconfig without using /boot/loader. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Windows works, for sufficently small values of "works". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
In message <[EMAIL PROTECTED]> Andrzej Bialecki writes: : That's fine. However, this practically makes using /boot/loader : mandatory. I still wonder if having some in-kernel interpreter wouldn't : give us more choice, with exactly the same functionality. Of course, it : would have to be run before any probing starts... All you'd need to do, if you don't want to compile it statically into the kernel, is arrange to read a file in from disk. With minor mods, you could read the entire environement which the hints mechanism now uses. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
On Wed, 21 Jun 2000, Daniel C. Sobral wrote: > Andrzej Bialecki wrote: > > > > This thread is long, so maybe I missed something.. Can we have the *.hints > > file loadable as a module of some special type (like kernel.conf), and > > searched for during configuration like userconfig did? > > Funny you got no reply. At last some merciful soul.. Thank you! :-) > > This is not necessary. If you copy said file to /boot/device.hints, it > will be read automatically as a loader .conf file and set environment > variables that will be read automatically by the kernel. > > If you wish to use alternate configurations without tweaking > device.hints, you can do > > loader_conf_files="xyzzy" > > And xyzzy will be read. Since device.hints is read right after > /boot/defaults/loader.conf, anything later will override it's values. That's fine. However, this practically makes using /boot/loader mandatory. I still wonder if having some in-kernel interpreter wouldn't give us more choice, with exactly the same functionality. Of course, it would have to be run before any probing starts... Andrzej Bialecki // <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Andrzej Bialecki wrote: > > This thread is long, so maybe I missed something.. Can we have the *.hints > file loadable as a module of some special type (like kernel.conf), and > searched for during configuration like userconfig did? Funny you got no reply. This is not necessary. If you copy said file to /boot/device.hints, it will be read automatically as a loader .conf file and set environment variables that will be read automatically by the kernel. If you wish to use alternate configurations without tweaking device.hints, you can do loader_conf_files="xyzzy" And xyzzy will be read. Since device.hints is read right after /boot/defaults/loader.conf, anything later will override it's values. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Windows works, for sufficently small values of "works". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
On Fri, 16 Jun 2000, Peter Wemm wrote: > Chia-liang Kao wrote: > > Hi, > > > > Is there anyway to put the device.hint stuff into kernel nevertheless? > > My diskless box fetches the kernel would know nothing about things reside > > in device.hint. > > That is what the hints directive is for. > > you could create a file "diskless.hints" and add the line to your config > file: > hints "/wherever/diskless.hints" > and the contents of that file would be statically compiled in. You can still > override them at boot time if you wish, but the basic set will be there. > > This is what GENERIC does right now. It compiles GENERIC.hints straight in. > (see hints.c in compile/YOURKERNEL) This thread is long, so maybe I missed something.. Can we have the *.hints file loadable as a module of some special type (like kernel.conf), and searched for during configuration like userconfig did? Andrzej Bialecki // <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: HEADS UP!: config changes...
On 13-Jun-00 Peter Wemm wrote: > *** CAUTION IS REQUIRED ***! > > FYI, an intrusive commit has been done that requires careful attention. If > you ignore this or mess it up, it can burn your house down, shoot your dog, > close your bank accounts, report you to the IRS, or maybe even something > bad. Well, I updated today (CVSup as of 16th June 20:00 UTC) And it worked fine except 1) the generated makefile for my kernel/modules build directory was broken (missing a ; \) - I've been told this is fixed, and 2) I had 'device sc' when it should have been 'device sc 1'. I had a minor problem where the perl script generated lines like -> hint.fdc.0.port=""0x3F0"" Which the loader barfed on.. easy to fix though. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Chia-liang Kao wrote: > Hi, > > Is there anyway to put the device.hint stuff into kernel nevertheless? > My diskless box fetches the kernel would know nothing about things reside > in device.hint. That is what the hints directive is for. you could create a file "diskless.hints" and add the line to your config file: hints "/wherever/diskless.hints" and the contents of that file would be statically compiled in. You can still override them at boot time if you wish, but the basic set will be there. This is what GENERIC does right now. It compiles GENERIC.hints straight in. (see hints.c in compile/YOURKERNEL) 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: HEADS UP!: config changes...
Hi, Is there anyway to put the device.hint stuff into kernel nevertheless? My diskless box fetches the kernel would know nothing about things reside in device.hint. Cheers, CLK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
> > Uh, 'help' doesn't give you a list of commands I believe. > > Damn, it doesn't either. 'help' is the same as 'help help'. > > Suggestions for a better replacement for ? 'commands'? Just change unadorned help to say 'help help' to get a list. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
> Uh, 'help' doesn't give you a list of commands I believe. According to loader(8) it means: ? Same as ``help index''. I did not try yet if that one works correctly. Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
> Uh, 'help' doesn't give you a list of commands I believe. Damn, it doesn't either. 'help' is the same as 'help help'. Suggestions for a better replacement for ? 'commands'? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Uh, 'help' doesn't give you a list of commands I believe. On Thu, 15 Jun 2000, Mike Smith wrote: > > On 15 Jun, Marc van Woerkom wrote: > > > > > 3. in the boot loader I miss the list of commands, > > >? (i hope this was the command) just yields a number > > > > I also see this. > > The use of ? was a bad idea, since it's special to Forth. Use 'help' > instead. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > > > > 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
Re: HEADS UP!: config changes...
> On 15 Jun, Marc van Woerkom wrote: > > > 3. in the boot loader I miss the list of commands, > >? (i hope this was the command) just yields a number > > I also see this. The use of ? was a bad idea, since it's special to Forth. Use 'help' instead. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
> 4. I thought I put just the sym driver in the kernel, why do I >see ncr? (see next item) Now it is back to using sym. Possibly some configuration mistake by me. Regards, Marc PS Here is the diff.. -FreeBSD 5.0-CURRENT #15: Thu Jun 15 00:25:51 CEST 2000 +FreeBSD 5.0-CURRENT #16: Thu Jun 15 11:31:41 CEST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/ORANJE Timecounter "i8254" frequency 1193182 Hz -Timecounter "TSC" frequency 300684562 Hz +Timecounter "TSC" frequency 300683613 Hz CPU: AMD-K6tm w/ multimedia extensions (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bf AMD Features=0x400<> real memory = 201326592 (196608K bytes) -avail memory = 192716800 (188200K bytes) -Preloaded elf kernel "kernel" at 0xc032c000. -VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc02cd122 (122) +avail memory = 192753664 (188236K bytes) +Preloaded elf kernel "kernel" at 0xc0323000. +VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc02c5142 (122) VESA: NVidia npx0: on motherboard npx0: INT 16 interface @@ -55,7 +26,8 @@ atapci1: port 0x6500-0x65ff,0x6400-0x6403,0x6300-0x6307 irq 15 at device 11.0 on pci0 ata2: at 0x6300 on atapci1 atapci2: port 0x6800-0x68ff,0x6700-0x6703,0x6600-0x6607 irq 15 at device 11.1 on pci0 -ncr0: port 0x6900-0x69ff mem 0xe200-0xe2000fff,0xe2002000-0xe20020ff irq 11 at device 13.0 on pci0 +sym0: <875> port 0x6900-0x69ff mem 0xe200-0xe2000fff,0xe2002000-0xe20020ff irq 11 at device 13.0 on pci0 +sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking pcm0: port 0x6a00-0x6a3f irq 10 at device 15.0 on pci0 pci0: at 17.0 irq 9 atkbdc0: at port 0x60,0x64 on isa0 @@ -101,22 +73,23 @@ ad0: 26059MB [52946/16/63] at ata2-master using UDMA66 Waiting 8 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s2a -da0 at ncr0 bus 0 target 0 lun 0 +da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 2068MB (4235629 512 byte sectors: 255H 63S/T 263C) -cd0 at ncr0 bus 0 target 4 lun 0 +cd0 at sym0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present -da1 at ncr0 bus 0 target 1 lun 0 +da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) -da2 at ncr0 bus 0 target 2 lun 0 +da2 at sym0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1s2: raw partition size != slice size da1s2: start 2120580, end 2536379, size 415800 da1s2c: start 2120580, end 8465687, size 6345108 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
On 15 Jun, Maxim Sobolev wrote: >> c) is much more interesting: With the new kernel my syscons scrolling >> stopped working. However, this could also be jake's fault, I'll ask >> him. > > Still works like a charm here. Maybe problem is elsewhere? I have the same problem as Alexander, nut it only applies to ttyv0. cvsup around 14. 11:10 CET. Bye, Alexander. -- I believe the technical term is "Oops!" http://www.Leidinger.net Alexander+Home @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
On 15 Jun, Marc van Woerkom wrote: > 3. in the boot loader I miss the list of commands, >? (i hope this was the command) just yields a number I also see this. > 5. Here are the dmesg differences between the February and the new >kernel. Could you explain the unassigned resources messages >to me? [...] > +unknown: can't assign resources > +unknown: can't assign resources > +unknown0: at port 0x40-0x43 irq 0 on isa0 > +unknown1: at port 0x70-0x71 irq 8 on isa0 > +unknown: can't assign resources > +unknown2: at port 0x61 on isa0 > +npxisa0: at port 0xf0-0xff irq 13 on isa0 > +unknown3: at iomem >0xe-0xf,0-0x9,0x2000-0x203f,0xffee-0xffef,0xfffe-0x,0x10-0xbff > on isa0 > +unknown4: at port 0x4d0-0x4d1,0xcf8-0xcff,0x480-0x48f on isa0 > +unknown5: at port 0x6100-0x613f on isa0 > +unknown: can't assign resources > +unknown: can't assign resources > +unknown: can't assign resources These are because "option PNPBIOS"(sp?) is now the default. Don't worry about them (or have a look into the archives). They are harmless. Bye, Alexander. -- Speak softly and carry a cellular phone. http://www.Leidinger.net Alexander+Home @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Another way to reboot the system is vidcontrol 80x50 Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Alexander Langer wrote: > c) is much more interesting: With the new kernel my syscons scrolling > stopped working. However, this could also be jake's fault, I'll ask > him. Still works like a charm here. Maybe problem is elsewhere? -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Hi! I was able to build and boot, starting from a February -CURRENT but there are some oddities. 1. I had to disable linux emulation, as it caused system hangup Yes I followed the hint on rebranding from src/UPDATING 2. My system seems to have a problem with fsck I had to use the old February kernel to boot and fsck with it, after the new kernel driven system crashed with the fs inconsistent 3. in the boot loader I miss the list of commands, ? (i hope this was the command) just yields a number 4. I thought I put just the sym driver in the kernel, why do I see ncr? (see next item) 5. Here are the dmesg differences between the February and the new kernel. Could you explain the unassigned resources messages to me? +Setting atkbd 0 at to atkbdc (string) +Setting atkbd 0 irq to 1 (int) +Setting atkbdc 0 at to isa (string) +Setting atkbdc 0 port to 96 (int) +Setting fd 0 at to fdc0 (string) +Setting fd 0 drive to 0 (int) +Setting fdc 0 at to isa (string) +Setting fdc 0 drq to 2 (int) +Setting fdc 0 irq to 6 (int) +Setting fdc 0 port to 1008 (int) +Setting isic 0 at to isa (string) +Setting isic 0 flags to 3 (int) +Setting isic 0 irq to 5 (int) +Setting isic 0 port to 3456 (int) +Setting joy 0 at to isa (string) +Setting joy 0 port to 513 (int) +Setting lpt 0 at to ppbus (string) +Setting npx 0 at to nexus (string) +Setting npx 0 flags to 0 (int) +Setting npx 0 irq to 13 (int) +Setting npx 0 port to 240 (int) +Setting ppc 0 at to isa (string) +Setting ppc 0 irq to 7 (int) +Setting sc 0 at to isa (string) +Setting sio 0 at to isa (string) +Setting sio 0 flags to 16 (int) +Setting sio 0 irq to 4 (int) +Setting sio 0 port to 1016 (int) +Setting vga 0 at to isa (string) +FreeBSD 5.0-CURRENT #15: Thu Jun 15 00:25:51 CEST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/ORANJE Timecounter "i8254" frequency 1193182 Hz -Timecounter "TSC" frequency 300684682 Hz -CPU: AMD-K6tm w/ multimedia extensions (300.68-MHz 586-class CPU) +Timecounter "TSC" frequency 300685025 Hz +CPU: AMD-K6tm w/ multimedia extensions (300.69-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bf AMD Features=0x400<> real memory = 201326592 (196608K bytes) -avail memory = 191733760 (187240K bytes) -Preloaded elf kernel "kernel" at 0xc030d000. -VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc02b3602 (122) +avail memory = 192716800 (188200K bytes) +Preloaded elf kernel "kernel" at 0xc032c000. +VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc02cd122 (122) VESA: NVidia npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 +pci0: at 0.0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: irq 0 at device 1.1 on pci0 @@ -25,30 +55,42 @@ atapci1: port 0x6500-0x65ff,0x6400-0x6403,0x6300-0x6307 irq 15 at device 11.0 on pci0 ata2: at 0x6300 on atapci1 atapci2: port 0x6800-0x68ff,0x6700-0x6703,0x6600-0x6607 irq 15 at device 11.1 on pci0 -sym0: <875> port 0x6900-0x69ff mem 0xe200-0xe2000fff,0xe2002000-0xe20020ff irq 11 at device 13.0 on pci0 -sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking +ncr0: port 0x6900-0x69ff mem 0xe200-0xe2000fff,0xe2002000-0xe20020ff irq 11 at device 13.0 on pci0 pcm0: port 0x6a00-0x6a3f irq 10 at device 15.0 on pci0 -pci0: NVidia Riva TNT graphics accelerator (vendor=0x10de, dev=0x0020) at 17.0 irq 9 -atkbdc0: at port 0x60-0x6f on isa0 +pci0: at 17.0 irq 9 +atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 -vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 -sc0: on isa0 -sc0: VGA <16 virtual consoles, flags=0x200> fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 -sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 -sio0: type 16550A -joy0 at port 0x201 on isa0 -isic0 at port 0xd80,0x960-0x99f,0x160-0x19f,0x560-0x59f irq 5 flags 0x3 on isa0 +isic0 at port 0xd80-0xd9f,0x980-0x99f,0x180-0x19f,0x580-0x59f irq 5 flags 0x3 on isa0 isic0: Teles S0/16.3 -ppc0: at port 0x378-0x37f irq 7 on isa0 +joy0 at port 0x201 on isa0 +ppc0: This ppc chipset does not support the extended I/O port range...no problem +ppc0: at port 0x378-0x37b irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode -ppbus0: IEEE1284 device found /NIBBLE -Probing for PnP devices on ppbus0: -ppbus0: PRINTER HP ENHANCED PCL5,PJL lpt0: on ppbus0 lpt0: Interrupt-driven port +sc0: on isa0 +sc0: VGA <16 virtual consoles, flags=0x200> +sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 +sio0: type 16550A +vga0: at port 0x
Re: HEADS UP!: config changes...
Hello Peter! I just have things running. I see that the kernel boots _much_ faster now. I don't know, if you wanted that or if this is a nice side-effect. However, a few comments, which might be of interest. Some of those are probably planned by you already. a) the device.hints file: It will probably be copied to /sys/compile by config(8) in future and installed by make install :) Good. b) Setting apm 0 at to nexus (string) Setting apm 0 disabled to 1 (int) Setting apm 0 flags to 32 (int) ... Can this be moved to verbose boot only? c) is much more interesting: With the new kernel my syscons scrolling stopped working. However, this could also be jake's fault, I'll ask him. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Peter Wemm wrote: > > The only change in /boot is /boot/defaults/loader.conf: > > diff -r1.26 -r1.27 > 24c24 > < loader_conf_files="/boot/loader.conf /boot/loader.conf.local" > --- > > loader_conf_files="/boot/device.hints /boot/loader.conf /boot/loader.conf.local" > > ie: /boot/device.hints is searched for. > > If you override loader_conf_files in your own loader.conf, you will need to > take care of it (or use static hints). loader_conf_files is not overridable. If that variable has a new value after a conf file has been read, it will process it recursively, an restore the original value afterwards. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "He is my minion, so he doesn't need a name." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
At 01:20 AM 6/14/2000 -0700, Peter Wemm wrote: >Peter Wemm wrote: > >> # update /boot/loader.conf >> cd src/sys/boot; make obj depend all install > >Of course, it would be just my luck that there is a loader bug right now, >and this command will throw you into the fire. ;-( If your loader >complains about not being version 0.3+ or later and aborting, comment the >version tests out of /boot/loader.4th as an interim. > >I have also just committed a last-minute introduced bug that prevented >static hints files with full-line comments in them from working properly. > >Cheers, >-Peter Peter I got this to work after some tweaking. I was getting syntax errors from the hints file when booting. I cut and pasted out of GENERIC.hints into my.hints and now it seems to boot without any errors. I noticed I now have a new link in the / directory :: lrwxr-xr-x 1 root wheel 10 Jun 14 11:18 ttyv0@ -> /dev/ttyv0 is this normal ? Also it seems that there is a order in the hints file that needs to be followed. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP!: config changes...
Peter Wemm wrote: > # update /boot/loader.conf > cd src/sys/boot; make obj depend all install Of course, it would be just my luck that there is a loader bug right now, and this command will throw you into the fire. ;-( If your loader complains about not being version 0.3+ or later and aborting, comment the version tests out of /boot/loader.4th as an interim. I have also just committed a last-minute introduced bug that prevented static hints files with full-line comments in them from working properly. 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: HEADS UP!: config changes...
Matthew Jacob wrote: > > > # I cannot stress this enough: **SAVE A WORKING /kernel** > > cp /kernel /kernel.works > > Save a working /modules and /boot as well. Which is always good advice, but I can clarify the effect on these... The only change in /boot is /boot/defaults/loader.conf: diff -r1.26 -r1.27 24c24 < loader_conf_files="/boot/loader.conf /boot/loader.conf.local" --- > loader_conf_files="/boot/device.hints /boot/loader.conf /boot/loader.conf.local" ie: /boot/device.hints is searched for. If you override loader_conf_files in your own loader.conf, you will need to take care of it (or use static hints). /modules should be unchanged by these commits. I wimped out and have not set GENERIC use device.hints yet as I'm not sure how best to connect that up to the release process. Also note: if you do not use loader(8), you *MUST* compile the hints in statically. 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: HEADS UP!: config changes...
> # I cannot stress this enough: **SAVE A WORKING /kernel** > cp /kernel /kernel.works Save a working /modules and /boot as well. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP!: config changes...
*** CAUTION IS REQUIRED ***! FYI, an intrusive commit has been done that requires careful attention. If you ignore this or mess it up, it can burn your house down, shoot your dog, close your bank accounts, report you to the IRS, or maybe even something bad. An old version 51 config(8) will (I think) generate a buildable config. If you ignore the dire warnings and manage to get a kernel built somehow, you will have a less than fulfilling experience. Most likely you just will not be able to type anything as your console would be dead as the atkbd controller will have failed to probe. In a nutshell, what you need to do is: # update /usr/sbin/config cd src/usr.sbin/config; make cleandir obj depend && make all install # update /boot/loader.conf cd src/sys/boot; make obj depend all install # update your kernel config files cd src/sys/i386/conf perl gethints.pl < YOURKERNEL > /boot/device.hints vi YOURKERNEL change *ALL* "device foo0 at isa? port blah etc" to "device foo" - see GENERIC for examples. All the 'at ? port ?' stuff is handled by the new /boot/device.hints See GENERIC - if you use a static limited device (eg: fe, aha, le, etc) where GENERIC has 'device le 1' *and* you had more than one device (eg: device le0 at ..., device le1 at ...) then you will need to specify more units. (eg: "device le 2" in the example above.) # I cannot stress this enough: **SAVE A WORKING /kernel** cp /kernel /kernel.works This is not quite yet complete, but is fully functional. There may still be some syntax changes to the hints stuff in the future, so pay attention. With respect to LINT - we had a lot of documentation in the file that would have been lost if the 'at isa? port ...' was removed, so I've copied it to a file called 'NOTES' which is NOT something you can feed to config. This file is documentation only. I chose to not keep both LINT and NOTES as they would have gotten out of sync fairly quickly. However, it is still possible to generate a buildable test-coverage LINT. ie: cd src/sys/i386/conf; make LINT; config LINT LINT will be generated from the NOTES file. Hopefully I have not forgotten anything. I had to make minor tweaks after I generated and uploaded the patches. I have not tested it as well on the Alpha as I have on the i386. --- Forwarded Message Date:Tue, 13 Jun 2000 15:28:50 -0700 From:Peter Wemm <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: cvs commit: src/usr.sbin/config Makefile config.h config.y ... peter 2000/06/13 15:28:50 PDT Modified files: usr.sbin/config Makefile config.h config.y configvers.h lang.l main.c mkheaders.c mkmakefile.c mkoptions.c sys/alpha/conf GENERIC SIMOS sys/boot/forth loader.conf sys/conf Makefile.alpha Makefile.i386 Makefile.pc98 files.alpha files.i386 files.pc98 sys/i386/confGENERIC NEWCARD NOTES sys/i386/isa if_cx.c sys/i4b/driver i4b_isppp.c sys/i4b/tina-dd i4b_tina_dd.c sys/kern subr_bus.c sys/pc98/confGENERIC sys/pc98/pc98wd.c Added files: sys/alpha/conf GENERIC.hints gethints.pl sys/i386/confGENERIC.hints Makefile NEWCARD.hints gethints.pl makeLINT.pl sys/pc98/confGENERIC.hints gethints.pl Removed files: usr.sbin/config mkioconf.c sys/i386/confLINT Log: Borrow phk's axe and apply the next stage of config(8)'s evolution. Use Warner Losh's "hint" driver to decode ascii strings to fill the resource table at boot time. config(8) no longer generates an ioconf.c table - ie: the configuration no longer has to be compiled into the kernel. You can reconfigure your isa devices with the likes of this at loader(8) time: set hint.ed.0.port=0x320 userconfig will be rewritten to use this style interface one day and will move to /boot/userconfig.4th or something like that. It is still possible to statically compile in a set of hints into a kernel if you do not wish to use loader(8). See the "hints" directive in GENERIC as an example. All device wiring has been moved out of config(8). There is a set of helper scripts (see i386/conf/gethints.pl, and the same for alpha and pc98) that extract the 'at isa? port foo irq bar' from the old files and produces a hints file. If you install this file as /boot/device.hints (and update /boot/defaults/loader.conf - You can do a build/install in sys/boot) then loader will load it automatically for you. You can also compile in the hints directly with: hints "device.hints" as well. There are a few things that I'm not too happy with yet. Under this scheme, things like LINT would no longer be useful as "documentation" of settings. I have renamed this file to 'NOTES' and st
