Re: Monitor dies and doesn't come back.
On Mon, Aug 28, 2000 at 06:04:42AM -0400, Systems Administrator wrote: > I did just notice something.. why would I have sc0/sc1 and > vga0/vga1? Or is that just because of the 'options SC_PIXEL_MODE' > that I have? Before you go any further, just compile a GENERIC kernel and see if the same problems are experienced. Then start merging in what you have in your custom kernel (line by line or section by section). I once deleted the syscons device, other similar things are possible. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Monitor dies and doesn't come back.
I did just notice something.. why would I have sc0/sc1 and vga0/vga1? Or is that just because of the 'options SC_PIXEL_MODE' that I have? Jason DiCioccio - IBM Global Services - [EMAIL PROTECTED] - www.ibm.com Systems Admin - Open Domain Server - [EMAIL PROTECTED] - www.ods.org FreeBSD - The Power to Serve - - www.freebsd.org On Mon, 28 Aug 2000, Greg Lehey wrote: > [dropping -questions, this is a -CURRENT problem] > > On Sunday, 27 August 2000 at 22:28:34 -0400, Systems Administrator wrote: > > I've been having a strange problem recently after installing a new > > harddrive.. the harddrive works fine in other OS's, but in FreeBSD, > > (seemingly after the HD install), the Monitor (CTX VL19") goes into > > powersaving and you cant get it back without doing a cold reboot.. not > > even a warm reboot will work. I am not sure exactly what is happening > > here, perhaps something borked? I have a Western Digital Caviar 45GB drive > > running at UDMA33. > > Well, this isn't the monitor, of course. Your system is probably > dying a horrible death and not producing any video output. > > > ad0: 9671MB [19650/16/63] at ata0-master using UDMA33 > > ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 > > acd0: CD-RW at ata1-master using WDMA2 > > acd1: CDROM at ata1-slave using PIO3 > > Mounting root from ufs:/dev/ad0s1a > > WARNING: / was not properly dismounted > > Well, it's not a good idea to put both disks on the same controller > anyway. What happens if you put the disks on the primaries of each > controller, and the CD-ROMS on the secondaries? If that doesn't help, > does the system at least work without the 45 GB drive? Anyway, how > far do you get in the book process? Can you get into single user mode > the way you are now? > > Greg > -- > When replying to this message, please copy the original recipients. > For more information, see http://www.lemis.com/questions.html > Finger [EMAIL PROTECTED] for PGP public key > See complete headers for address and phone numbers > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Monitor dies and doesn't come back.
Would the controller I have my drives on really cause that? Seems kind of strange :).. Jason DiCioccio - IBM Global Services - [EMAIL PROTECTED] - www.ibm.com Systems Admin - Open Domain Server - [EMAIL PROTECTED] - www.ods.org FreeBSD - The Power to Serve - - www.freebsd.org On Mon, 28 Aug 2000, Greg Lehey wrote: > [dropping -questions, this is a -CURRENT problem] > > On Sunday, 27 August 2000 at 22:28:34 -0400, Systems Administrator wrote: > > I've been having a strange problem recently after installing a new > > harddrive.. the harddrive works fine in other OS's, but in FreeBSD, > > (seemingly after the HD install), the Monitor (CTX VL19") goes into > > powersaving and you cant get it back without doing a cold reboot.. not > > even a warm reboot will work. I am not sure exactly what is happening > > here, perhaps something borked? I have a Western Digital Caviar 45GB drive > > running at UDMA33. > > Well, this isn't the monitor, of course. Your system is probably > dying a horrible death and not producing any video output. > > > ad0: 9671MB [19650/16/63] at ata0-master using UDMA33 > > ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 > > acd0: CD-RW at ata1-master using WDMA2 > > acd1: CDROM at ata1-slave using PIO3 > > Mounting root from ufs:/dev/ad0s1a > > WARNING: / was not properly dismounted > > Well, it's not a good idea to put both disks on the same controller > anyway. What happens if you put the disks on the primaries of each > controller, and the CD-ROMS on the secondaries? If that doesn't help, > does the system at least work without the 45 GB drive? Anyway, how > far do you get in the book process? Can you get into single user mode > the way you are now? > > Greg > -- > When replying to this message, please copy the original recipients. > For more information, see http://www.lemis.com/questions.html > Finger [EMAIL PROTECTED] for PGP public key > See complete headers for address and phone numbers > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Monitor dies and doesn't come back.
[dropping -questions, this is a -CURRENT problem] On Sunday, 27 August 2000 at 22:28:34 -0400, Systems Administrator wrote: > I've been having a strange problem recently after installing a new > harddrive.. the harddrive works fine in other OS's, but in FreeBSD, > (seemingly after the HD install), the Monitor (CTX VL19") goes into > powersaving and you cant get it back without doing a cold reboot.. not > even a warm reboot will work. I am not sure exactly what is happening > here, perhaps something borked? I have a Western Digital Caviar 45GB drive > running at UDMA33. Well, this isn't the monitor, of course. Your system is probably dying a horrible death and not producing any video output. > ad0: 9671MB [19650/16/63] at ata0-master using UDMA33 > ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 > acd0: CD-RW at ata1-master using WDMA2 > acd1: CDROM at ata1-slave using PIO3 > Mounting root from ufs:/dev/ad0s1a > WARNING: / was not properly dismounted Well, it's not a good idea to put both disks on the same controller anyway. What happens if you put the disks on the primaries of each controller, and the CD-ROMS on the secondaries? If that doesn't help, does the system at least work without the 45 GB drive? Anyway, how far do you get in the book process? Can you get into single user mode the way you are now? Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Monitor dies and doesn't come back.
I've been having a strange problem recently after installing a new harddrive.. the harddrive works fine in other OS's, but in FreeBSD, (seemingly after the HD install), the Monitor (CTX VL19") goes into powersaving and you cant get it back without doing a cold reboot.. not even a warm reboot will work. I am not sure exactly what is happening here, perhaps something borked? I have a Western Digital Caviar 45GB drive running at UDMA33. dmesg output follows: FreeBSD 5.0-CURRENT #1: Sat Aug 26 00:24:22 MDT 2000 [EMAIL PROTECTED]:/usr2/src/sys/compile/FREEBSD Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 501138733 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 134217728 (131072K bytes) avail memory = 127107072 (124128K bytes) Preloaded elf kernel "kernel" at 0xc037e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc037e09c. Preloaded elf module "splash_bmp.ko" at 0xc037e0ec. Preloaded elf module "vesa.ko" at 0xc037e190. Preloaded splash_image_data "/boot/splash.bmp" at 0xc037e22c. Preloaded elf module "snd_emu10k1.ko" at 0xc037e27c. Preloaded elf module "snd_pcm.ko" at 0xc037e320. Pentium Pro MTRR support enabled VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc02f43b7 (1000117) VESA: 3dfx Interactive, Inc. npx0: on motherboard pcib0: on motherboard pci0: on pcib0 pci0: at 0.0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 5 pci0: at 7.3 pcm0: port 0xe400-0xe41f irq 10 at device 13.0 on pci0 pci0: <3Dfx Voodoo 3 graphics accelerator> at 15.0 irq 11 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 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ed0 at port 0x240-0x25f iomem 0xd8000-0xd9fff irq 3 on isa0 ed0: address 00:e0:29:16:cb:72, type SMC8416T (16 bit) sc1: on isa0 sc1: MDA <16 virtual consoles, flags=0x0> vga1: at port 0x3b0-0x3bb iomem 0xb-0xb7fff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default IP Filter: v3.4.9 initialized. Default = pass all, Logging = enabled ad0: 9671MB [19650/16/63] at ata0-master using UDMA33 ad1: 42934MB [87233/16/63] at ata0-slave using UDMA33 acd0: CD-RW at ata1-master using WDMA2 acd1: CDROM at ata1-slave using PIO3 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted Any help would be appreciated. Thanks! (Sorry, no panic, so that's all I could get) -JD- Jason DiCioccio - IBM Global Services - [EMAIL PROTECTED] - www.ibm.com Systems Admin - Open Domain Server - [EMAIL PROTECTED] - www.ods.org FreeBSD - The Power to Serve - - www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
