apm problems.
Hi, Apm does not seem to be behaving correctly on my computer (running yesterday's CURRENT) eg: with a make world running, the following happens after about 15 mins of not touching the keyboard. Received APM Event: PMEV_STANDBYREQ Execute APM hook "pcm suspend handler" Called APM sound suspend hook for unit 1 Execute APM hook "default suspend" However, disk activity continues and the monitor isn't blanked. then, if a key is pressed: Recieved APM Event: PMEV_STANDBYRESUME Execute APM hook "default resume" resume from suspended mode (Slept 00:28:34) Execute APM Hook "pcm resume handler" Called APM sound resume hook for unit 1 If apm -z is given, then the computer does go to sleep, monitor blanks, no disk activity. However, if apm -z is used while the computer is doing something (eg: compiling a kernel) then the computer goes to sleep, and everything stops, but will not wake up properly. no new process can be started ie: any command typed in starts but does not appear to do anything, and can't be stopped (control -c) if top is runing before apm -z is done then after resuming,top shows and continues to update: process state top RUN makeSELECT ld getblk apmdbiord syncer drainv etc. alt-ctl-delete also does not work. if more info is needed, just let me know what to do. Thanks =). (I also don't need the apm features of the motherboard that much, so if its likely to take a lot of work making apm work right just for this motherboard it probably isn't worth the effort) DMESG: apm0: APM BIOS on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f, Data 0xc400 apm: Code entry 0xef50, Idling CPU disabled, Management enabled apm: CS_limit=0x, DS_limit=0x apm: Engaged control enabled apm: found APM BIOS v1.2, connected at v1.2 apm: Slow Idling CPU disabled Add hook "default suspend" Add hook "default resume" [I didn't originally have the 'idling CPU disabled' set in the bios, but then the cpu would be put into a slow state while actually busy, resulting in make world taking many more hours than usual...] apm: APM version: 1.2 APM Managment: Enabled AC Line status: on-line Battery status: unknown Remaining battery life: unknown Remaining battery time: unknown Number of batteries: 0 Resume timer: Wed Dec 31 18:59:59 1969 Resume on ring indicator: enabled APM Capacities: global standby state global suspend state resume timer from suspend -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Problems with 4.0 keyboard input!
Hello Brian, I get the bktr device usurping its own cdevsw[] as well - I was told it was "most likely" benign, so I've been waiting for others' comments. I have looked in the source code, but what does usurping means? My English is not that good ;) The messages comes from /usr/src/sys/kern/kern_conf.c I also get the keyboard problem periodically, and I've been trying to isolate just what I do to cause it. Generally, if I reboot and don't hit a key before FreeBSD boots, it never happens. If I tap enter to abort the countdown, the keyboard scrambles perhaps one time in five. Thats what I have been doing the last five reboots, I pressed Return to let it boot faster. I shall try without. Resetting seems to be the only remedy. This persists with two different keyboard models and on unplugging and reinserting the keyboard. cut - ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: IBM-DTTA-371440/T71OA73A ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 31 depth queue, DMA mode ata0: slave: setting up UDMA2 mode on PIIX4 chip OK ad1: IBM-DJNA-372200/J71OA30K ATA-4 disk at ata0 as slave ad1: 21557MB (44150400 sectors), 43800 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 31 depth queue, DMA mode ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: IBM-DTTA-371440/T71OA73A ATA-4 disk at ata1 as master ad2: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S --- cut Do you have enough disk space ;-))) Thanks for you reaction. Regards, Ron. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with 4.0 keyboard input!
In message 000401bee65b$b6fd0440$0264a8c0@.demon.nl, "Ron Klinkien" writes: I get the bktr device usurping its own cdevsw[] as well - I was told it was "most likely" benign, so I've been waiting for others' comments. I have looked in the source code, but what does usurping means? My English is not that good ;) It means "to take or assume and hold (something) by force or without right". Usually used about power in subsaharan our south american countries. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Problems with 4.0 keyboard input!
I have looked in the source code, but what does usurping means? My English is not that good ;) 'opslorpen' in Dutch. Nick -- e-Mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SUPFLAGS in /etc/make.conf
This looks like commit it and see what happens to me. Nick On Sat, 14 Aug 1999, Sheldon Hearn wrote: On Fri, 13 Aug 1999 15:17:47 -0400, Ben Rosengart wrote: I submit that putting "-z" in here is silly, because the sample cvsup config files turn on compression, and suggest commenting it out if you have a fast link. It seems counterintuitive that one can comment out the compression in the standard supfiles and then have it enabled by default with "make update" anyway. This looks like PR material. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- e-Mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Problems with 4.0 keyboard input!
In message 000401bee65b$b6fd0440$0264a8c0@.demon.nl, "Ron Klinkien" writes: I get the bktr device usurping its own cdevsw[] as well - I was told it was "most likely" benign, so I've been waiting for others' comments. I have looked in the source code, but what does usurping means? My English is not that good ;) It means "to take or assume and hold (something) by force or without right". Usually used about power in subsaharan our south american countries. Aha ok. Thanks for the explanation. Ron. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
a couple of warnings
asus p2b-ds, dual P2/350s, 128mb current as of 99.08.13 evening dmesg has a few things which worry me. but the hauppauge/brootree works fine with mbone tools and fxtv. randy Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Aug 14 09:01:38 PDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/RIP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 134205440 (131060K bytes) config pnp 1 0 enable os port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5 config pnp 1 1 enable os port0 0x200 config pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 config quit avail memory = 126959616 (123984K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc02f5000. Preloaded userconfig_script "/kernel.config" at 0xc02f509c. Pentium Pro MTRR support enabled ccd0-5: Concatenated disk drivers Probing for PnP devices: CSN 1 Vendor ID: CTL00c3 [0xc3008c0e] Serial 0x1fd0a682 Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp SB16 PnP sn 0x1fd0a682) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[]*** pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: Matrox model 051f graphics accelerator irq 16 at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 chip1: Intel PIIX4 IDE controller at device 4.1 on pci0 chip2: UHCI USB controller irq 19 at device 4.2 on pci0 intpm0: Intel 82371AB Power management controller at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: System Management Bus on intsmb0 smb0: SMBus general purpose I/O on smbus0 intpm0: PM I/O mapped e400 ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter irq 19 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: Intel EtherExpress Pro 10/100B Ethernet irq 19 at device 9.0 on pci0 fxp0: Ethernet address 00:a0:c9:df:c8:4e bktr0: BrookTree 878 irq 18 at device 10.0 on pci0 iicbb0: I2C generic bit-banging driver on bti2c0 iicbus0: Philips I2C bus on iicbb0 master-only iicsmb0: I2C to SMB bridge on iicbus0 smbus1: System Management Bus on iicsmb0 smb1: SMBus general purpose I/O on smbus1 WARNING: "iic" is usurping "iic"'s cdevsw[] *** iic0: I2C general purpose I/O on iicbus0 smbus2: System Management Bus on bti2c0 smb2: SMBus general purpose I/O on smbus2 Hauppauge Model 6 A M Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo. Detected a MSP3430G-A1 pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 10.1 irq 18 isa0: ISA bus on motherboard fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 4 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A wl0 at port 0x300-0x30f irq 7 on isa0 wl0: address 08:00:6a:2b:dd:a7, NWID 0x APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 wl0 XXX: driver didn't set ifq_maxlen Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 6 lun 0 sa0: DEC DLT2000 8B37 Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: SEAGATE ST34573LW 5702 Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4340MB (924 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 1 lun 0 da1: SEAGATE ST34573LW 5702 Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4340MB (924 512 byte sectors: 255H 63S/T 553C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: TEAC CD-ROM CD-532S 1.0A Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed:
Re: a couple of warnings
asus p2b-ds, dual P2/350s, 128mb current as of 99.08.13 evening dmesg has a few things which worry me. but the hauppauge/brootree works fine with mbone tools and fxtv. WARNING: "bktr" is usurping "bktr"'s cdevsw[]* WARNING: "iic" is usurping "iic"'s cdevsw[] * As is understand it, these are just advisory and can be safely ignored; I get the same messages. -- we are but packets in the internet of life To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: a couple of warnings
asus p2b-ds, dual P2/350s, 128mb current as of 99.08.13 evening dmesg has a few things which worry me. but the hauppauge/brootree works fine with mbone tools and fxtv. WARNING: "bktr" is usurping "bktr"'s cdevsw[]* WARNING: "iic" is usurping "iic"'s cdevsw[] * As is understand it, these are just advisory and can be safely ignored; I get the same messages. Actually, they're caused by the driver registering it's cdev twice; they're harmless but indicate that the driver needs to be fixed. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes
"MS" == Mike Smith [EMAIL PROTECTED] writes: Then after 5 seconds the screen blanks, the power light starts flashing (indicating suspend mode), but when I hit a key, the console says (slept 00:00:02) only, and programs in fact continued running (thus it didn't go or remain in suspend mode at all). MS I think you'll find that programs didn't, in fact, continue MS running; rather they paused and then resumed when you came out MS of suspend. I'm running seti@home, and it really continued while my computer was 'suspended'. Also a little test program continued running. -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know [EMAIL PROTECTED] | the Netherlands| what I'm doing. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes
"MS" == Mike Smith [EMAIL PROTECTED] writes: Then after 5 seconds the screen blanks, the power light starts flashing (indicating suspend mode), but when I hit a key, the console says (slept 00:00:02) only, and programs in fact continued running (thus it didn't go or remain in suspend mode at all). MS I think you'll find that programs didn't, in fact, continue MS running; rather they paused and then resumed when you came out MS of suspend. I'm running seti@home, and it really continued while my computer was 'suspended'. Also a little test program continued running. What you're failing to offer here, and thus why I remain skeptical, is any evidence that suggests that these programs were "running" while the system believed itself to be suspended. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pex5 and xie load errors
i just upgraded to current. i still have the following in my /etc/XF86Config Section "Module" Load"pex5.so" Load"xie.so" EndSection during X startup i get load errors for these. but i can see nothing unappy with X. do i delete them from /etc/XF86Config or rebuild X or what? thanks. randy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
"Matthew N. Dodd" wrote: Agreed. I like what I see there. Maybe it is time to hoist something like that into bus_subr.c Lets define exactly what we want before we start our charge. What should be printed? device ID attachment point resource reservation device additional When should it be printed? bootverbose levels? Years ago I provided diffs to the kernel boot to report some probes Before as well as after, so one could see which probe was about to hang, - more use than which probe was last to pass. Idea was rejected as some thought it was too verbose, but Nobody (me included) thought of having a bootverbose levels switch to hang on it on. ... Nice Idea ! Some Computer mags reccomend MS-* users to keep a boot flop for Linux or BSD, as we provide much more diagnostics than MS*, Before-probe-announcements would make it more valuable still. Imagine if the more competent of the MS crowd actually wanted to keep a FreeBSD boot floppy around :-) Julian Julian H. Staceyhttp://www.freebsd.org/~jhs/ Considering Linux ? Then also consider the 2000+ free packages for FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
