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=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX AMD Features=0x400b10 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: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 +pci0: Host to PCI bridge (vendor=1039 device=5597) at 0.0 isab0: SiS 85c503 PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 atapci0: SiS 5591 ATA33 controller irq 0 at device 1.1 on pci0 @@ -25,30 +55,42 @@ atapci1: HighPoint HPT366 ATA66 controller port 0x6500-0x65ff,0x6400-0x6403,0x6300-0x6307 irq 15 at device 11.0 on pci0 ata2: at 0x6300 on atapci1 atapci2: HighPoint HPT366 ATA66 controller 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: ncr 53c875 fast20 wide scsi port 0x6900-0x69ff mem 0xe200-0xe2000fff,0xe2002000-0xe20020ff irq 11 at device 13.0 on pci0 pcm0: AudioPCI ES1370 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: keyboard controller (i8042) at port 0x60-0x6f on isa0 +pci0: NVidia Riva TNT graphics accelerator at 17.0 irq 9 +atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 -vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 -sc0: System console on isa0 -sc0: VGA 16 virtual consoles, flags=0x200 fdc0: NEC 72065B or clone 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: Parallel port 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:
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...
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: syscons scrolling broken
On 14 Jun, Alexander Langer wrote: it does not. It seems, as if screen output is still being deactivated, but scrolling does just not work. Anyone else? Yes, but it only applies to ttyv0. Bye, Alexander. -- The best things in life are free, but the expensive ones are still worth a look. 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: syscons rebooting when going to 80x50
On 14 Jun, Alfred Perlstein wrote: After taking the patches for config and booting my box reboots because I have: #allscreens_flags="-m on 80x50" #saver="logo" #font8x8="cp437-8x8" #font8x14="cp437-8x14" #font8x16="cp437-8x16" enabled in my rc.conf, a kernel from ~2 days ago is fine with this. Remove allscreens_flags, the other options should work. /etc/rc.conf:font8x8="iso-8x8" /etc/rc.conf:font8x14="iso-8x14" /etc/rc.conf:font8x16="iso-8x16" /etc/rc.conf:saver="green" /etc/rc.conf.local:#allscreens_flags="132x60" With allscrrens_flags it hangs while trying to switch the mode on ttyv0, switching the mode for ttyv1 works here. Bye, Alexander. -- Loose bits sink chips. 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: PNP can't assign resources +unknown: PNP0200 can't assign resources +unknown0: PNP0100 at port 0x40-0x43 irq 0 on isa0 +unknown1: PNP0b00 at port 0x70-0x71 irq 8 on isa0 +unknown: PNP0303 can't assign resources +unknown2: PNP0800 at port 0x61 on isa0 +npxisa0: Legacy ISA coprocessor support at port 0xf0-0xff irq 13 on isa0 +unknown3: PNP0c01 at iomem 0xe-0xf,0-0x9,0x2000-0x203f,0xffee-0xffef,0xfffe-0x,0x10-0xbff on isa0 +unknown4: PNP0a03 at port 0x4d0-0x4d1,0xcf8-0xcff,0x480-0x48f on isa0 +unknown5: PNP0c02 at port 0x6100-0x613f on isa0 +unknown: PNP0501 can't assign resources +unknown: PNP0700 can't assign resources +unknown: PNP0400 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: xmms broken by either libc_r or sound
On Wed, 14 Jun 2000, Dan Nelson wrote: In the last episode (Jun 14), Otter said: On Wed, 14 Jun 2000, Chris Piazza wrote: Yes backout recent changes to sys/dev/sound/pcm/channel.c. (a few days) How does one backout changes? I thought once it was committed, and the make world process is complete, it was just that: committed. You make another commit, undoing what your first commit did. That way there is a record of what you did, and hopefully why it was backed out. For more info: info -n "(cvs)Merging two revisions" I honestly don't think his question was from a committers standpoint. I think he wanted to know how to back them out locally for his own system. To do that he needs to read the handbook entries for staying current with FreeBSD, specifically the stuff on anoncvs. Then to back them out he needs to use cvs to retrieve an older revision of the affected files via anoncvs and make a new world. Brandon D. Valentine -- "You should believe in death, taxes, Larry Ellison's loathing of Bill Gates and Intel's inability to ship a working chipset." - Dr Spinola, The Register, 05/13/2000 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...
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=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX AMD Features=0x400b10 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: math processor on motherboard npx0: INT 16 interface @@ -55,7 +26,8 @@ atapci1: HighPoint HPT366 ATA66 controller port 0x6500-0x65ff,0x6400-0x6403,0x6300-0x6307 irq 15 at device 11.0 on pci0 ata2: at 0x6300 on atapci1 atapci2: HighPoint HPT366 ATA66 controller port 0x6800-0x68ff,0x6700-0x6703,0x6600-0x6607 irq 15 at device 11.1 on pci0 -ncr0: ncr 53c875 fast20 wide scsi 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: AudioPCI ES1370 port 0x6a00-0x6a3f irq 10 at device 15.0 on pci0 pci0: NVidia Riva TNT graphics accelerator at 17.0 irq 9 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 @@ -101,22 +73,23 @@ ad0: 26059MB Maxtor 92732U8 [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: QUANTUM FIREBALL ST2.1S 0F0C 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: PIONEER DVD-ROM DVD-303 1.10 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: IBM DCAS-34330W S65A 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: IBM DORS-32160 WA6A 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: syscons scrolling broken
it does not. It seems, as if screen output is still being deactivated, but scrolling does just not work. Anyone else? Yes, but it only applies to ttyv0. Same behaviour here. Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons scrolling broken
Also sprach Marc van Woerkom ([EMAIL PROTECTED]): Anyone else? Yes, but it only applies to ttyv0. Same behaviour here. Jup, here too. Unfortunately, that's the only one where I want it :) Alex 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...
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. 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: xmms broken by either libc_r or sound
On Thu, Jun 15, 2000 at 10:10:49AM -0400, Brandon D. Valentine wrote: I honestly don't think his question was from a committers standpoint. I think he wanted to know how to back them out locally for his own system. To do that he needs to read the handbook entries for staying current with FreeBSD, specifically the stuff on anoncvs. Then to back them out he needs to use cvs to retrieve an older revision of the affected files via anoncvs and make a new world. Or use cvsweb, which is probably easier for the casual user. http://www.freebsd.org/cgi/cvsweb.cgi/path/to/affected/file or just start at http://www.freebsd.org/cgi/cvsweb.cgi and navigate your way down. Good luck, -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xmms broken by either libc_r or sound
On Thu, 15 Jun 2000, Jacques A . Vidrine wrote: Or use cvsweb, which is probably easier for the casual user. Definitely easier for the casual user who's tracking -STABLE. However, I feel that to succeed tracking -CURRENT it pays to invest a minimal amount of time learning at least the basics of cvs. =) Brandon D. Valentine -- "You should believe in death, taxes, Larry Ellison's loathing of Bill Gates and Intel's inability to ship a working chipset." - Dr Spinola, The Register, 05/13/2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Hi, its for you !
Hi! We are Russian girls - Natali, Alla, Vika. We would like to correspond with you. Visit our site and see our photos. http://www.russiangirls.narod.ru/ With interest, Natali,Alla, Vika. P.S. (This is not spam. You can unsubscribe at any time by sending an email to [EMAIL PROTECTED] with the subject UNSUBSCRIBE.) 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
fatal trap 12 after lastest kernel build
I just built my kernel from kernel sources as of Thu Jun 15 13:49:59 EDT 2000, and immediately after the kernel is loaded, I get a "fatal trap 12: page fault while in supervisor mode". The uptime was 0s, so apparently, the boot loader must not like the kernel. But, I can boot a kernel from Jun 14 10:25 with the same boot loader. I did a make depend all install in /usr/src/sys/boot with the new sources, but still the same problem. Anyone else see this? - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fatal trap 12 after lastest kernel build
did you follow Peter Wemm's instructions on the new config changes? = | 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 Thu, 15 Jun 2000, Donn Miller wrote: I just built my kernel from kernel sources as of Thu Jun 15 13:49:59 EDT 2000, and immediately after the kernel is loaded, I get a "fatal trap 12: page fault while in supervisor mode". The uptime was 0s, so apparently, the boot loader must not like the kernel. But, I can boot a kernel from Jun 14 10:25 with the same boot loader. I did a make depend all install in /usr/src/sys/boot with the new sources, but still the same problem. Anyone else see this? - Donn 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: fatal trap 12 after lastest kernel build
Kenneth Wayne Culver wrote: did you follow Peter Wemm's instructions on the new config changes? Actually, I did. In fact, I built 2 or 3 kernels after the changes went into effect with no problems. It's just the sources that I cvsup'd as of an hour ago that's causing the problems. On Thu, 15 Jun 2000, Donn Miller wrote: I just built my kernel from kernel sources as of Thu Jun 15 13:49:59 EDT 2000, and immediately after the kernel is loaded, I get a "fatal trap 12: page fault while in supervisor mode". The uptime was 0s, so apparently, the boot loader must not like the kernel. But, I can boot a kernel from Jun 14 10:25 with the same boot loader. I did a make depend all install in /usr/src/sys/boot with the new sources, but still the same problem. Anyone else see this? - Donn 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 -- - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fatal trap 12 after lastest kernel build
Oh ok. well then I have no idea... :-) I thought that could be the problem... = | 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 Thu, 15 Jun 2000, Donn Miller wrote: Kenneth Wayne Culver wrote: did you follow Peter Wemm's instructions on the new config changes? Actually, I did. In fact, I built 2 or 3 kernels after the changes went into effect with no problems. It's just the sources that I cvsup'd as of an hour ago that's causing the problems. On Thu, 15 Jun 2000, Donn Miller wrote: I just built my kernel from kernel sources as of Thu Jun 15 13:49:59 EDT 2000, and immediately after the kernel is loaded, I get a "fatal trap 12: page fault while in supervisor mode". The uptime was 0s, so apparently, the boot loader must not like the kernel. But, I can boot a kernel from Jun 14 10:25 with the same boot loader. I did a make depend all install in /usr/src/sys/boot with the new sources, but still the same problem. Anyone else see this? - Donn 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 -- - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
WARNING /dev/wd compat hack removed...
--- Forwarded Message Message-Id: [EMAIL PROTECTED] From: Poul-Henning Kamp [EMAIL PROTECTED] Date: Thu, 15 Jun 2000 13:30:53 -0700 (PDT) To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: cvs commit: src/sys/dev/ata ata-disk.c src/sys/i386/i386 autoconf.c src/sys/kern subr_disk.c src/sys/sys disk.h phk 2000/06/15 13:30:53 PDT Modified files: sys/dev/ata ata-disk.c sys/i386/i386autoconf.c sys/kern subr_disk.c sys/sys disk.h Log: Add disk_enumerate() for finding names of disks. Vinum and libh will need this RSN. Remove a pointless warning in the root device locating code. Remove the "wd" compatibility name from the "ad" driver. WARNING: If you have not updated to use /dev/wd* in your /etc/fstab and modern bootblocks, it would be a very good idea to do so BEFORE you upgrade your kernel. Revision ChangesPath 1.72 +1 -25 src/sys/dev/ata/ata-disk.c 1.147 +2 -4 src/sys/i386/i386/autoconf.c 1.25 +16 -2 src/sys/kern/subr_disk.c 1.17 +5 -1 src/sys/sys/disk.h --- End of Forwarded Message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: WARNING /dev/wd compat hack removed...
On 15-Jun-00 Poul-Henning Kamp wrote: Remove the "wd" compatibility name from the "ad" driver. WARNING: If you have not updated to use /dev/wd* in your /etc/fstab You mean 'If you have not updated to use /dev/ad* in your /etc/fstab...' right? --- 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
-current kernel broken?
As of about 7pm EDT I can't boot a -current kernel. I _can_ boot a kernel from the 13th I snagged from a snapshot kernel disk, and I can boot the snapshot from the 15th (but since userconfig does not work the lnc device spams so many error messages the system never reaches a prompt). Already did the make clean depend all install for /sys/boot/i386 and that was no help. The kernel just freezes _right_ after trying to boot... I'm not sure how far its getting, I'll have to play around with a debug kernel and see what I can get from it (if anything). Cheers, WM -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current kernel broken?
Wes Morgan wrote: As of about 7pm EDT I can't boot a -current kernel. I _can_ boot a kernel from the 13th I snagged from a snapshot kernel disk, and I can boot the snapshot from the 15th (but since userconfig does not work the lnc device spams so many error messages the system never reaches a prompt). Already did the make clean depend all install for /sys/boot/i386 and that was no help. The kernel just freezes _right_ after trying to boot... I'm not sure how far its getting, I'll have to play around with a debug kernel and see what I can get from it (if anything). I can verify this. With sources cvsup'd this morning and later, I get a fatal trap 12 (page fault supervisor mode) the very instant the kernel boots. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current kernel broken?
On Thu, 15 Jun 2000, Wes Morgan wrote: As of about 7pm EDT I can't boot a -current kernel. I _can_ boot a kernel from the 13th I snagged from a snapshot kernel disk, and I can boot the snapshot from the 15th (but since userconfig does not work the lnc device spams so many error messages the system never reaches a prompt). Already did the make clean depend all install for /sys/boot/i386 and that was no help. The kernel just freezes _right_ after trying to boot... I'm not sure how far its getting, I'll have to play around with a debug kernel and see what I can get from it (if anything). okay, I see the same thing, but *believe* that this has to do with the whole thread on ttyv0 that just passed through here, so am just waiting and watching the commit logs for something that "looks" appropriate ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
