Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
I think I've fixed the spontaneous reboot and system hang problem I've been having with FBSD 6.1 6.2 as described in earlier threads of the same subject. I'm now using FBSD 6.2 to send this message. What I did was to set a hint in /boot/device.hints and also /boot/loader.conf to disable acpi hint.acpi.0.disabled=1 and then I set a hint to enable apm hint.apm.0.disabled=0 hint.apm.0.flags=0x20 plus I set apm and apmd to start at boot in /etc/rc.conf apm_enable=YES apmd_enable=YES and in /boot/loader.conf, I put apm_load=YES The messages log shows that APM is being detected, and the computer now fully powers down via shutdown -p now. I've a suggestion. It would be nice if freebsd could try to detect if acpi is supported on the computer in which it is being installed, and if none is found, it should completely disable acpi and then check if apm is supported. It should then set the appropriate settings to enable the correct power management support for the computer. This would prevent this particular spontaneous rebooting and hanging on old computers like mine which are pre-acpi but have apm support. So far, I haven't had any problems using KPPP. I've been up for over an hour and I've never been able keep the computer up for this long before making these changes. Joe Vender ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
On Tue, Jan 30, 2007 at 07:20:47PM -0600, Joe Vender wrote: I think I've fixed the spontaneous reboot and system hang problem I've been having with FBSD 6.1 6.2 as described in earlier threads of the same subject. I'm now using FBSD 6.2 to send this message. What I did was to set a hint in /boot/device.hints and also /boot/loader.conf to disable acpi hint.acpi.0.disabled=1 and then I set a hint to enable apm hint.apm.0.disabled=0 hint.apm.0.flags=0x20 plus I set apm and apmd to start at boot in /etc/rc.conf apm_enable=YES apmd_enable=YES and in /boot/loader.conf, I put apm_load=YES The messages log shows that APM is being detected, and the computer now fully powers down via shutdown -p now. I've a suggestion. It would be nice if freebsd could try to detect if acpi is supported on the computer in which it is being installed, and if none is found, it should completely disable acpi and then check if apm is supported. It should then set the appropriate settings to enable the correct power management support for the computer. This would prevent this particular spontaneous rebooting and hanging on old computers like mine which are pre-acpi but have apm support. It does try to detect it; the problem is apparently that your BIOS lies and says yep, ACPI capable!, but is in fact too buggy to use. Look for a BIOS update if possible. kris pgpr3BrAB0T6o.pgp Description: PGP signature
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
On Tuesday 30 January 2007 19:39, Kris Kennaway wrote: snipped It does try to detect it; the problem is apparently that your BIOS lies and says yep, ACPI capable!, but is in fact too buggy to use. Look for a BIOS update if possible. kris I hate to say it, but I spoke to soon or jinxed myself! Right after I sent the email to the list, my computer locked up tighter than a drum while loading a webpage. Argh! Here's my messages log. Hope someone can help. Jan 30 19:35:14 psi-lab syslogd: kernel boot file is /boot/kernel/kernel Jan 30 19:35:14 psi-lab kernel: Copyright (c) 1992-2007 The FreeBSD Project. Jan 30 19:35:14 psi-lab kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 30 19:35:14 psi-lab kernel: The Regents of the University of California. All rights reserved. Jan 30 19:35:14 psi-lab kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Jan 30 19:35:14 psi-lab kernel: FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 Jan 30 19:35:14 psi-lab kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP Jan 30 19:35:14 psi-lab kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Jan 30 19:35:14 psi-lab kernel: CPU: AMD-K6(tm) 3D processor (381.03-MHz 586-class CPU) Jan 30 19:35:14 psi-lab kernel: Origin = AuthenticAMD Id = 0x58c Stepping = 12 Jan 30 19:35:14 psi-lab kernel: Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX Jan 30 19:35:14 psi-lab kernel: AMD Features=0x8800SYSCALL,3DNow Jan 30 19:35:14 psi-lab kernel: real memory = 327155712 (312 MB) Jan 30 19:35:14 psi-lab kernel: avail memory = 310476800 (296 MB) Jan 30 19:35:14 psi-lab kernel: kbd1 at kbdmux0 Jan 30 19:35:14 psi-lab kernel: K6-family MTRR support enabled (2 registers) Jan 30 19:35:14 psi-lab kernel: ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Jan 30 19:35:14 psi-lab kernel: module_register_init: MOD_LOAD (splash_bmp, 0xc0b089e4, 0) error 2 Jan 30 19:35:14 psi-lab kernel: cpu0 on motherboard Jan 30 19:35:14 psi-lab kernel: apm0: APM BIOS on motherboard Jan 30 19:35:14 psi-lab kernel: apm0: found APM BIOS v1.2, connected at v1.2 Jan 30 19:35:14 psi-lab kernel: pcib0: Host to PCI bridge pcibus 0 on motherboard Jan 30 19:35:14 psi-lab kernel: pir0: PCI Interrupt Routing Table: 7 Entries on motherboard Jan 30 19:35:14 psi-lab kernel: pci0: PCI bus on pcib0 Jan 30 19:35:14 psi-lab kernel: agp0: SiS 530 host to AGP bridge mem 0x5000-0x5fff at device 0.0 on pci0 Jan 30 19:35:14 psi-lab kernel: atapci0: SiS 530 UDMA66 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2040-0x204f at device 0.1 on pci0 Jan 30 19:35:14 psi-lab kernel: ata0: ATA channel 0 on atapci0 Jan 30 19:35:14 psi-lab kernel: ata1: ATA channel 1 on atapci0 Jan 30 19:35:14 psi-lab kernel: isab0: PCI-ISA bridge at device 1.0 on pci0 Jan 30 19:35:14 psi-lab kernel: isa0: ISA bus on isab0 Jan 30 19:35:14 psi-lab kernel: pci0: unknown at device 1.1 (no driver attached) Jan 30 19:35:14 psi-lab kernel: ohci0: SiS 5571 USB controller mem 0x4020-0x40200fff irq 11 at device 1.2 on pci0 Jan 30 19:35:14 psi-lab kernel: ohci0: [GIANT-LOCKED] Jan 30 19:35:14 psi-lab kernel: usb0: OHCI version 1.0, legacy support Jan 30 19:35:14 psi-lab kernel: usb0: SiS 5571 USB controller on ohci0 Jan 30 19:35:14 psi-lab kernel: usb0: USB revision 1.0 Jan 30 19:35:14 psi-lab kernel: uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jan 30 19:35:14 psi-lab kernel: uhub0: 2 ports with 2 removable, self powered Jan 30 19:35:14 psi-lab kernel: pcib1: PCIBIOS PCI-PCI bridge at device 2.0 on pci0 Jan 30 19:35:14 psi-lab kernel: pci1: PCI bus on pcib1 Jan 30 19:35:14 psi-lab kernel: pci1: display, VGA at device 0.0 (no driver attached) Jan 30 19:35:14 psi-lab kernel: pcm0: ESS Solo-1E port 0x2000-0x203f,0x2050-0x205f,0x2060-0x206f,0x2070-0x2073,0x2074-0x2077 irq 5 at device 10.0 on pci0 Jan 30 19:35:14 psi-lab kernel: pmtimer0 on isa0 Jan 30 19:35:14 psi-lab kernel: orm0: ISA Option ROM at iomem 0xc-0xc7fff on isa0 Jan 30 19:35:14 psi-lab kernel: atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 Jan 30 19:35:14 psi-lab kernel: atkbd0: AT Keyboard irq 1 on atkbdc0 Jan 30 19:35:14 psi-lab kernel: kbd0 at atkbd0 Jan 30 19:35:14 psi-lab kernel: atkbd0: [GIANT-LOCKED] Jan 30 19:35:14 psi-lab kernel: psm0: PS/2 Mouse irq 12 on atkbdc0 Jan 30 19:35:14 psi-lab kernel: psm0: [GIANT-LOCKED] Jan 30 19:35:14 psi-lab kernel: psm0: model Generic PS/2 mouse, device ID 0 Jan 30 19:35:14 psi-lab kernel: fdc0: Enhanced floppy controller at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Jan 30 19:35:14 psi-lab kernel: fdc0: [FAST] Jan 30 19:35:14 psi-lab kernel: fd0: 1440-KB 3.5 drive on fdc0 drive 0 Jan 30 19:35:14 psi-lab kernel: ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 Jan 30 19:35:14 psi-lab kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode Jan 30 19:35:14 psi-lab kernel: ppbus0: Parallel port bus on ppc0 Jan 30 19:35:14 psi-lab kernel:
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
On Tue, Jan 30, 2007 at 08:01:18PM -0600, Joe Vender wrote: On Tuesday 30 January 2007 19:39, Kris Kennaway wrote: snipped It does try to detect it; the problem is apparently that your BIOS lies and says yep, ACPI capable!, but is in fact too buggy to use. Look for a BIOS update if possible. kris I hate to say it, but I spoke to soon or jinxed myself! Right after I sent the email to the list, my computer locked up tighter than a drum while loading a webpage. Argh! Here's my messages log. Hope someone can help. OK, I see you're using pppd - unfortunately this is known to have serious problems and is essentially unmaintained in FreeBSD. Use ppp(8) instead, or if you really don't want to change over then you'll have to configure debugging as in the developers' handbook chapter on kernel debugging, and try to determine whether or not pppd is really to blame. Kris pgp70FgHtovqy.pgp Description: PGP signature
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
On Saturday 27 January 2007 00:41, Ian Smith wrote: In freebsd-questions Digest, Vol 162, Issue 17 As Message: 14 On Fri, 26 Jan 2007 14:15:10 -0600 Joe Vender [EMAIL PROTECTED] wrote: Joe, I'm going to hack your message pretty mercilessly .. I need Help with a FBSD spontaneous rebooting and freezing issue. Here's a quick description of my computer system: I have a Compaq Presario 5184 desktop about 7 or 8 years old AMD K6-2 processor @ 380MHz 320Mb RAM, 8Mb dedicated to video via BIOS Quantum Bigfoot TS-6.4A Hard Drive (~6Gb capacity) SiS 530 integrated graphics Zoom 56k DUALMODE external modem connected to the serial port CTX VL700 monitor (30-70/50-120 refresh rates) [..] worked fine under FBSD until I dial up the internet and start browsing, emailing or whatever. Then, when the computer is busy transferring packets, it suddenly reboots without warning. Sometimes, Konqueror will freeze, the mouse pointer will freeze for a few seconds before the reboot. It doesn't take very long on the internet before the lockup/reboot happens, only minutes. It happens over and over and over. I can't stay on the internet long enough to even use it. Nothing at all reported in /var/log/messages? Not that I can recall. As I stated earlier, I had to remove FBSD and install Linux to be able to use this mailing list, but I did look through the logs after the spontaneous reboots and found nothing that indicated what was wrong. Remember, the spontaneous reboots and hangs only happen when I dial up the internet and start browsing or sending email or such, basically start sending/receiving packets. It doesn't happen when no packets are moving over the modem, only when its busy. It isn't the modem failing either, obviously, since the modem works flawlessly under Linux and windows. Ok. You mean it sometimes 'hangs' and sometimes just reboots? When I was using FBSD 6.1, it was always a spontaneous reboot, but the system would usually freeze for a couple of seconds before the reboot occurred. I found a notice in the errata on the FBSD website that sounded like it addressed what could be causing this problem: FreeBSD-EN-06:02.net, and I applied the patch to 6.1 and rebuilt the kernel. I thought that this had fixed the problem because I didn't get a spontaneous reboot after being on the net for a short time. But, I was wrong because It did spontaneous reboot, just not immediately after starting to use the net. So, that's when I moved on to FBSD 6.2. After setting it up to dial up using KPPP, I was on the net for maybe a half hour when it suddenly froze up. The computer was locked up. I had to hard reboot using the power button. After that, I put linux back on the system to seek help, since I didn't know what the problem was and I coundn't use FBSD to seek help. One more thing that may or may not be important. I remember seeing a message at boot up about IRQ 3 not in the list of probed ports or something to that effect. But, KPPP recognized my external modem without a problem. Its on /dev/ttyS0 in KPPP. My computer came with an internal winmodem piece of @#!$, but I removed that when I plugged in the Zoom external. The internal modem is no longer present. The external is plugged in to the serial port. Could this be an IRQ conflict or something like that? I'm assuming that the message was about the absent internal modem. Interrupts in KInfoCenter reports that serial is using interrupt 4. Please help. I don't mind going through the reinstall if I can get FreeBSD working. Ah, so you're using KPPP rather than FreeBSD's user PPP? Have you tried using 'regular' user PPP? No. I'm new to FreeBSD, and KPPP was quicker and easier for me to get up and going, plus I like to have the icon docked into the system tray when I'm online. I don't know anything about KPPP, but would expect with KDE's linux leanings that it would be using pppd instead. Where and how have you configured ppp? I configured KPPP with the info needed to dial up. In ancient PC tradition, IRQ 4 is used for the first serial port, IRQ 3 for the second. Eg from /var/run/dmesg.boot here (also an older box): sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A I have sio1 disabled in /boot/loader.conf, just to quell such messages, but it seems yours is using the correct IRQ (4) for your ext. modem. My computer originally came with an internal modem which was on COM1 under windows. COM2 would have been the serial nipple on the back of the computer. I removed the internal modem, and when I attached the external modem, I assume the serial controller on the motherboard reassigned the external nipple to COM1 and disabled COM2. The internal slot is empty, which I guess is why FBSD throws the error message about it being disabled. One last question. How do I get FBSD to completely power off my computer
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
Sounds like an IRQ conflict as your serial port is not on IRQ 3. I would look into the BIOS settings, and set the port explicitly for IRQ 3, and not automatic if this is possible. -Derek At 02:15 PM 1/26/2007, Joe Vender wrote: I need Help with a FBSD spontaneous rebooting and freezing issue. Here's a quick description of my computer system: I have a Compaq Presario 5184 desktop about 7 or 8 years old AMD K6-2 processor @ 380MHz 320Mb RAM, 8Mb dedicated to video via BIOS Quantum Bigfoot TS-6.4A Hard Drive (~6Gb capacity) SiS 530 integrated graphics Zoom 56k DUALMODE external modem connected to the serial port CTX VL700 monitor (30-70/50-120 refresh rates) I'm new to FreeBSD, but I've some experience with Linux, so FreeBSD isn't totally unfamiliar to me. I zero-filled my HDD on which I'd been running Slackware 11.0 without issue and started from scratch with a clean install of FreeBSD 6.1-release. FreeBSD 6.1 was then the only OS on the system, no multi-boot environment. Everything worked fine under FBSD until I dial up the internet and start browsing, emailing or whatever. Then, when the computer is busy transferring packets, it suddenly reboots without warning. Sometimes, Konqueror will freeze, the mouse pointer will freeze for a few seconds before the reboot. It doesn't take very long on the internet before the lockup/reboot happens, only minutes. It happens over and over and over. I can't stay on the internet long enough to even use it. Now, I've been using Slackware Linux without issue for a long time, same with Ubuntu Kubuntu Windows prior to that. This isn't a hardware failure, because it doesn't occur with these other OSs at all. Linux was what I was using before I wiped the drive and installed FreeBSD. I've tested the RAM and HDD and they are OK. I repeat, there are no problems like this with the other OS's, only when FreeBSD is put on the system. I've only tried FBSD 6.1-release FBSD 6.2-release, nothing prior to that. Since I wasn't even able to use the internet because of the freeze/reboot, I reinstalled Slackware and, as always, it is running without a hitch. But, I want to use FreeBSD, so I got a copy of FreeBSD 6.2 CDs, thinking maybe it was a fixed in the new release. FreeBSD 6.2 gives me the same behavior. After a few minutes of browsing, the system just froze up and required a hard restart. I REALLY like FreeBSD, the features and ease of use. If I could get it working on this computer as smoothly as Slackware does, I'd use it exclusively. This is the only computer I have, so in order to even send this message, I had to put Slackware back on the computer. That's what I'm using now. If anyone can help me figure out what the problem is here, I'd really appreciate it. Remember, the spontaneous reboots and hangs only happen when I dial up the internet and start browsing or sending email or such, basically start sending/receiving packets. It doesn't happen when no packets are moving over the modem, only when its busy. It isn't the modem failing either, obviously, since the modem works flawlessly under Linux and windows. Keep in mind that this is my only computer. I will have to wipe the HDD and reinstall FBSD in order to try any suggestions, so please give as much info as possible, since when I'm back to FBSD, I may not be able to get back on the net for further communication if I can't fix the problem first. At least, not until I go through the process of reinstalling Slackware. I'm hoping that someone has run into this problem before and knows a way to fix it. One more thing that may or may not be important. I remember seeing a message at boot up about IRQ 3 not in the list of probed ports or something to that effect. But, KPPP recognized my external modem without a problem. Its on /dev/ttyS0 in KPPP. My computer came with an internal winmodem piece of @#!$, but I removed that when I plugged in the Zoom external. The internal modem is no longer present. The external is plugged in to the serial port. Could this be an IRQ conflict or something like that? I'm assuming that the message was about the absent internal modem. Interrupts in KInfoCenter reports that serial is using interrupt 4. Please help. I don't mind going through the reinstall if I can get FreeBSD working. One last question. How do I get FBSD to completely power off my computer when I shut down, both from KDE and from console? When I shutdown, it just gets to the system halted, press any key to reboot prompt and doesn't completely power off. In slackware, all I have to do is uncomment the modprobe apm line in rc.modules. Sorry for such a long email, but I wanted to be as thourough as possible with the little I have to go on. Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
On Friday 26 January 2007 15:04, Derek Ragona wrote: Sounds like an IRQ conflict as your serial port is not on IRQ 3. I would look into the BIOS settings, and set the port explicitly for IRQ 3, and not automatic if this is possible. The configurable settings in my BIOS setup don't include the ability to set the serial port IRQ. How is FreeBSD able to communicate with the modem if the irq is not set correctly? Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
Joe Vender wrote: One last question. How do I get FBSD to completely power off my computer when I shut down, both from KDE and from console? When I shutdown, it just gets to the system halted, press any key to reboot prompt and doesn't completely power off. In slackware, all I have to do is uncomment the modprobe apm line in rc.modules. You issue the command shutdown -p now. This should work with any BIOS that has apm or acpi, as far as I know. As Derek says, you have an IRQ conflict that needs to be resolved. Afraid I don't remember much about that. When I first installed FreeBSD (seven years ago), I had to settle several such conflicts, but I seem to recall that it was fairly easy. -- Tore ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
On Friday 26 January 2007 17:41, Tore Lund wrote: You issue the command shutdown -p now. This should work with any BIOS that has apm or acpi, as far as I know. I've tried that, but it didn't power off, just got to the halted step. What about issuing the Shutdown computer from KDE logout? Shouldn't it power off the computer? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
On Jan 26, 2007, at 4:04 PM, Joe Vender wrote: On Friday 26 January 2007 17:41, Tore Lund wrote: You issue the command shutdown -p now. This should work with any BIOS that has apm or acpi, as far as I know. I've tried that, but it didn't power off, just got to the halted step. What about issuing the Shutdown computer from KDE logout? Shouldn't it power off the computer? The GUI commands within KDE are going to invoke the command-line shutdown command with the appropriate arguments. What may be going on is that your old hardware only supports the older form of power management/shutdown mechanism, called APM, rather than the newer APCI. You might find that reading man 4 apm and man acpi will give you some hints on debugging the issue. It might help to try updating your machines BIOS, or to recompile a kernel with ACPI disabled but the older APM enabled, and see whether that gets you somewhere. The fact that you can shutdown within Linux suggests that your hardware does have the capability, so it's just a matter of figuring out what's different. Note that you might find that trying to run FreeBSD 4.11 to be informative, as the defaults for that older version might correspond with your hardware better, although, 4.11 is at the end of it's supported lifespan... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
On Friday 26 January 2007 18:18, Chuck Swiger wrote: The GUI commands within KDE are going to invoke the command-line shutdown command with the appropriate arguments. What may be going on is that your old hardware only supports the older form of power management/shutdown mechanism, called APM, rather than the newer APCI. You might find that reading man 4 apm and man acpi will give you some hints on debugging the issue. It might help to try updating your machines BIOS, or to recompile a kernel with ACPI disabled but the older APM enabled, and see whether that gets you somewhere. There is no update to my machine BIOS as far as I know. What I have now is the last software that was released for it, and that was years ago. I have actually wondered if I should disable ACPI and enable APM in a new kernel build. I'll give it a try if I can get the real issue, which is the spontaneous reboots freezes, solved. The fact that you can shutdown within Linux suggests that your hardware does have the capability, so it's just a matter of figuring out what's different. Note that you might find that trying to run FreeBSD 4.11 to be informative, as the defaults for that older version might correspond with your hardware better, although, 4.11 is at the end of it's supported lifespan... I've been seriously thinking about getting a copy of the legacy FBSD 5.5 that's on the website. Maybe there isn't a difference between it and the 6.2 as far as this powerdown issue is concerned. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
On Jan 26, 2007, at 4:36 PM, Joe Vender wrote: The fact that you can shutdown within Linux suggests that your hardware does have the capability, so it's just a matter of figuring out what's different. Note that you might find that trying to run FreeBSD 4.11 to be informative, as the defaults for that older version might correspond with your hardware better, although, 4.11 is at the end of it's supported lifespan... I've been seriously thinking about getting a copy of the legacy FBSD 5.5 that's on the website. Maybe there isn't a difference between it and the 6.2 as far as this powerdown issue is concerned. You're likely to have better luck with 4.11 than 5.2; if you want to try a 5.x release, go with 5.5, as the early 5.x releases were only so-so in terms of stability before 5.3... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
In freebsd-questions Digest, Vol 162, Issue 17 As Message: 14 On Fri, 26 Jan 2007 14:15:10 -0600 Joe Vender [EMAIL PROTECTED] wrote: Joe, I'm going to hack your message pretty mercilessly .. I need Help with a FBSD spontaneous rebooting and freezing issue. Here's a quick description of my computer system: I have a Compaq Presario 5184 desktop about 7 or 8 years old AMD K6-2 processor @ 380MHz 320Mb RAM, 8Mb dedicated to video via BIOS Quantum Bigfoot TS-6.4A Hard Drive (~6Gb capacity) SiS 530 integrated graphics Zoom 56k DUALMODE external modem connected to the serial port CTX VL700 monitor (30-70/50-120 refresh rates) [..] worked fine under FBSD until I dial up the internet and start browsing, emailing or whatever. Then, when the computer is busy transferring packets, it suddenly reboots without warning. Sometimes, Konqueror will freeze, the mouse pointer will freeze for a few seconds before the reboot. It doesn't take very long on the internet before the lockup/reboot happens, only minutes. It happens over and over and over. I can't stay on the internet long enough to even use it. Nothing at all reported in /var/log/messages? Remember, the spontaneous reboots and hangs only happen when I dial up the internet and start browsing or sending email or such, basically start sending/receiving packets. It doesn't happen when no packets are moving over the modem, only when its busy. It isn't the modem failing either, obviously, since the modem works flawlessly under Linux and windows. Ok. You mean it sometimes 'hangs' and sometimes just reboots? One more thing that may or may not be important. I remember seeing a message at boot up about IRQ 3 not in the list of probed ports or something to that effect. But, KPPP recognized my external modem without a problem. Its on /dev/ttyS0 in KPPP. My computer came with an internal winmodem piece of @#!$, but I removed that when I plugged in the Zoom external. The internal modem is no longer present. The external is plugged in to the serial port. Could this be an IRQ conflict or something like that? I'm assuming that the message was about the absent internal modem. Interrupts in KInfoCenter reports that serial is using interrupt 4. Please help. I don't mind going through the reinstall if I can get FreeBSD working. Ah, so you're using KPPP rather than FreeBSD's user PPP? Have you tried using 'regular' user PPP? I don't know anything about KPPP, but would expect with KDE's linux leanings that it would be using pppd instead. Where and how have you configured ppp? In ancient PC tradition, IRQ 4 is used for the first serial port, IRQ 3 for the second. Eg from /var/run/dmesg.boot here (also an older box): sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A I have sio1 disabled in /boot/loader.conf, just to quell such messages, but it seems yours is using the correct IRQ (4) for your ext. modem. One last question. How do I get FBSD to completely power off my computer when I shut down, both from KDE and from console? When I shutdown, it just gets to the system halted, press any key to reboot prompt and doesn't completely power off. In slackware, all I have to do is uncomment the modprobe apm line in rc.modules. Well that begs more questions. Are you using APM? or ACPI? What exact command are you using to shutdown? What does running just 'apm' say? Sorry for such a long email, but I wanted to be as thourough as possible with the little I have to go on. Posting latest /var/run/dmesg.boot would tell us more about what FreeBSD thinks it's detecting, and I suspect that setting up user PPP by the handbook would determine whether this is a FreeBSD or KPPP problem. Cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
In freebsd-questions Digest, Vol 162, Issue 18 As Message: 6 On Fri, 26 Jan 2007 18:36:14 -0600 Joe Vender [EMAIL PROTECTED] wrote: Argh, digests .. sorry, this came in just after my previous post: On Friday 26 January 2007 18:18, Chuck Swiger wrote: The GUI commands within KDE are going to invoke the command-line shutdown command with the appropriate arguments. What may be going on is that your old hardware only supports the older form of power management/shutdown mechanism, called APM, rather than the newer APCI. You might find that reading man 4 apm and man acpi will give you some hints on debugging the issue. It might help to try updating your machines BIOS, or to recompile a kernel with ACPI disabled but the older APM enabled, and see whether that gets you somewhere. Sounds like an issue, but I don't think you need to recompile a kernel to get APM, if you add 'hint.apm.0.disabled=0' to /boot/loader.conf it should load with GENERIC. It does on 5.x anyway, though I did compile an APM kernel later, after getting things going that way. There is no update to my machine BIOS as far as I know. What I have now is the last software that was released for it, and that was years ago. I have actually wondered if I should disable ACPI and enable APM in a new kernel build. I'll give it a try if I can get the real issue, which is the spontaneous reboots freezes, solved. I still think that may be a KPPP issue, but we need to see your dmesg as to whether ACPI is being used/detected (which likely won't work well if at all with a machine that old, whereas APM is much more likely to). Check that APM, rather than ACPI, is enabled in your BIOS. The fact that you can shutdown within Linux suggests that your hardware does have the capability, so it's just a matter of figuring out what's different. Note that you might find that trying to run FreeBSD 4.11 to be informative, as the defaults for that older version might correspond with your hardware better, although, 4.11 is at the end of it's supported lifespan... Sad but true. 4.x GENERIC had APM in kernel iirc, 5.x and 6.x don't. I've been seriously thinking about getting a copy of the legacy FBSD 5.5 that's on the website. Maybe there isn't a difference between it and the 6.2 as far as this powerdown issue is concerned. I'm running 5.5-STABLE here on a Compaq Armada 1500c, using APM. I could be wrong, but I don't think the APM code has changed noticeably between 5.5 and 6.x, so I really wouldn't recommend going back to 5.5 until you've tried resolving this on 6.2 first, using the hints in /boot/loader.conf first, and if necessary compiling APM into kernel. Your /var/run/dmesg.boot, please, both re this and the sio issue. Cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 6.2 hanging and/or spontaneous rebooting
On Sat, 27 Jan 2007, Ian Smith wrote: Sounds like an issue, but I don't think you need to recompile a kernel to get APM, if you add 'hint.apm.0.disabled=0' to /boot/loader.conf it should load with GENERIC. It does on 5.x anyway, though I did compile an APM kernel later, after getting things going that way. Oops; just noticed that before compiling my kernel with APM, as well as hint.apm.0.disabled=0 I'd also had apm_load=YES in /boot/loader.conf While trying it, also add hint.ata.1.disabled=1 to quell your IRQ 3 msg. Cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
