Re: stange console problem
If I copy GENERIC to DEBUG and recompile the kernel it will not boot properly copy the file back to GENERIC and everything seems fine? I have searched the archives and read UPDATING, but nothing jumps out at me. Does anybody have any idea where I could look next? Chad On Sun, Jan 28, 2001 at 10:16:02PM -0700, Chad David wrote: On a current from last Sunday I recompiled a new kernel with just makeoptions DEBUG=-g and options DDB added to GENERIC and when I boot I see the first few spins of the loader booting the kernel and then all video output stops. After the boot finishs I get a login prompt but no keyboard response or video after that. Have you tried removing the 'makeoptions' line and using 'config -g KERNCONF' instead? That's how I build my debug kernels, and that worked fine last time I did it (last week or so). Also, when you copy the GENERIC file to another name, do you update the ident line? This should normally not matter but you never know with debugging kernels. In both cases you would need to examine the config utility. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
"Rogier R. Mulhuijzen" [EMAIL PROTECTED] writes: Have you tried removing the 'makeoptions' line and using 'config -g KERNCONF' instead? [...] Also, when you copy the GENERIC file to another name, do you update the ident line? None of this has any bearing on the problem, which was caused by a bug in gensetdefs.pl. Please update your source tree and rebuild your kernel. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
None of this has any bearing on the problem, which was caused by a bug in gensetdefs.pl. Please update your source tree and rebuild your kernel. Eek. I had the gensetdefs.pl problem too, but my machine just seemed to lock. He says his machine does go on running. I have been pretty tied up lately, so maybe I read his post a bit too quickly. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
Problem solved. cp GENERIC.hints DEBUG.hints Without them it isn't very happy... did I miss this as a requirement somewhere, or is my hardware/timing just a little funky? Chad On Tue, Jan 30, 2001 at 04:03:10PM +0100, Rogier R. Mulhuijzen wrote: None of this has any bearing on the problem, which was caused by a bug in gensetdefs.pl. Please update your source tree and rebuild your kernel. Eek. I had the gensetdefs.pl problem too, but my machine just seemed to lock. He says his machine does go on running. I have been pretty tied up lately, so maybe I read his post a bit too quickly. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
Chad David wrote: Problem solved. cp GENERIC.hints DEBUG.hints Without them it isn't very happy... did I miss this as a requirement somewhere, or is my hardware/timing just a little funky? Yes, you were not reading the commit messages or UPDATING or -current. You should have a /boot/device.hints for your machine. You dont need GENERIC.hints or DEBUG.hints if you have this set up correctly. As a head start, you can cp GENERIC.hints to /boot/device.hints and you're done. config and 'make install' will not let you forget this.. Were you installing your kernel by hand or something? Chad On Tue, Jan 30, 2001 at 04:03:10PM +0100, Rogier R. Mulhuijzen wrote: None of this has any bearing on the problem, which was caused by a bug in gensetdefs.pl. Please update your source tree and rebuild your kernel. Eek. I had the gensetdefs.pl problem too, but my machine just seemed to lock. He says his machine does go on running. I have been pretty tied up lately, so maybe I read his post a bit too quick ly. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message 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: stange console problem
In reply to my own post (which nobody has replied to, perhaps because I never actually phrased a question :-) )... I have found that if the kernel config file is named GENERIC, it will boot just fine; otherwise, I loose the console. I have done a cvsup tonight as well as a make world and many different kernels. If I copy GENERIC to DEBUG and recompile the kernel it will not boot properly copy the file back to GENERIC and everything seems fine? I have searched the archives and read UPDATING, but nothing jumps out at me. Does anybody have any idea where I could look next? Chad On Sun, Jan 28, 2001 at 10:16:02PM -0700, Chad David wrote: On a current from last Sunday I recompiled a new kernel with just makeoptions DEBUG=-g and options DDB added to GENERIC and when I boot I see the first few spins of the loader booting the kernel and then all video output stops. After the boot finishs I get a login prompt but no keyboard response or video after that. I am able to ssh into the box, and all seems well from the "inside". If I recompile GENERIC it works just fine. Here is a dmesg, I noticed a few things but nothing I know how to fix.. Chad To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
stange console problem
On a current from last Sunday I recompiled a new kernel with just makeoptions DEBUG=-g and options DDB added to GENERIC and when I boot I see the first few spins of the loader booting the kernel and then all video output stops. After the boot finishs I get a login prompt but no keyboard response or video after that. I am able to ssh into the box, and all seems well from the "inside". If I recompile GENERIC it works just fine. Here is a dmesg, I noticed a few things but nothing I know how to fix.. Chad Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Sun Jan 28 23:17:40 MST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/DEBUG Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (367.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 134152192 (131008K bytes) avail memory = 125595648 (122652K bytes) Preloaded elf kernel "kernel" at 0xc04e7000. Pentium Pro MTRR support enabled WARNING: Driver mistake: destroy_dev on 154/0 Using $PIR table, 6 entries at 0xc00fded0 apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f at device 7.2 on pci0 pci_cfgintr_virgin: using routable PCI-only interrupt 11 pci_cfgintr: 0:7 INTD routed to irq 11 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: bridge, PCI-unknown at 7.3 (no driver attached) xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xe400-0xe47f mem 0xe500-0xe57f irq 11 at device 9.0 on pci0 xl0: Ethernet address: 00:10:4b:6e:0a:87 miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sio0: 16550A-compatible COM port at port 0x3f8-0x407 irq 4 on isa0 sio0: type 16550A fdc0: NEC 72065B or clone at port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: Standard parallel printer port at port 0x378-0x387 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio1: 16550A-compatible COM port at port 0x2f8-0x307 irq 3 on isa0 sio1: type 16550A sbc0: Creative SB AWE64 at port 0x220-0x22f,0x331-0x332,0x388-0x38b irq 5 drq 1,5 on isa0 pcm0: SB16 DSP 4.16 on sbc0 xl0 XXX: driver didn't initialize queue mtx lp0 XXX: driver didn't initialize queue mtx gif0 XXX: driver didn't initialize queue mtx gif1 XXX: driver didn't initialize queue mtx gif2 XXX: driver didn't initialize queue mtx gif3 XXX: driver didn't initialize queue mtx lo0 XXX: driver didn't initialize queue mtx ppp0 XXX: driver didn't initialize queue mtx faith0 XXX: driver didn't initialize queue mtx ad0: 6187MB FUJITSU MPB3064ATU E [13410/15/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s4a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
