Re: freeze PHP5 at specific version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doug Sampson wrote: Recently I discovered that PHP 5.3.x broke my Viart installation. It turned out that ZendOptimizer 3.3.0.a cannot function with PHP 5.3.x. Thus I was forced to downgrade down to PHP5-5.2.12_2. Question: How can I force portupgrade not to upgrade to PHP5-5.3.x? I've tried googling and researching ports management manpages to no avail. I noticed that there's a line for Perl in /etc/make.conf that freezes Perl at a specific version (i.e. PERL_VERSION=5.10.1) but I do not see anything similar to that for PHP5. I must be missing something! I do not know the appropriate search keyword for freezing a port at a specific version. ~Doug Hi Doug, Have a look at this page: http://myfreebsd.homeunix.net/hints_n_kinks/ports-pkgtools.html. If you add the php port names to the HOLD_PKGS array, that prevents portupgrade from touching them. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLyKGx0sRouByUApARAn4FAJ96DDcZu/3tcACFePe1BBLitmo4oACgvjpY fT3m2G7AvkAta/PbYmDpOO8= =7Cho -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: freeze PHP5 at specific version
Have a look at this page: http://myfreebsd.homeunix.net/hints_n_kinks/ports-pkgtools.html. If you add the php port names to the HOLD_PKGS array, that prevents portupgrade from touching them. Bingo! That is what I'm looking for! Say, do I need to list each PHP5 extension in the HOLD_PKG section? For example, I have the following PHP5 extensions on top of the lang/php5 as follows: corvus-root@/usr/ports/databases/php5-sqlite: portversion -v | g php5 php5-5.2.12_2 needs updating (port has 5.3.2) php5-bcmath-5.2.12_2 needs updating (port has 5.3.2) php5-bz2-5.2.12_2 needs updating (port has 5.3.2) php5-ctype-5.2.12_2 needs updating (port has 5.3.2) php5-curl-5.2.12_2needs updating (port has 5.3.2) php5-dba-5.2.12_2 needs updating (port has 5.3.2) php5-dom-5.2.12_2 needs updating (port has 5.3.2) php5-exif-5.2.12_2needs updating (port has 5.3.2) php5-filter-5.2.12_2 needs updating (port has 5.3.2) php5-ftp-5.2.12_2 needs updating (port has 5.3.2) php5-gd-5.2.12_2 needs updating (port has 5.3.2) php5-gettext-5.2.12_2 needs updating (port has 5.3.2) php5-hash-5.2.12_2needs updating (port has 5.3.2) php5-iconv-5.2.12_2 needs updating (port has 5.3.2) php5-json-5.2.12_2needs updating (port has 5.3.2) php5-mbstring-5.2.12_2needs updating (port has 5.3.2) php5-mcrypt-5.2.12_2 needs updating (port has 5.3.2) php5-mhash-5.2.12_2 = up-to-date with port php5-ncurses-5.2.12_2 = up-to-date with port php5-openssl-5.2.12_2 needs updating (port has 5.3.2) php5-pcre-5.2.12_2 = up-to-date with port php5-pdo-5.2.12_2 needs updating (port has 5.3.2) php5-pdo_sqlite-5.2.12_2 needs updating (port has 5.3.2) php5-pgsql-5.2.12_2 needs updating (port has 5.3.2) php5-posix-5.2.12_2 needs updating (port has 5.3.2) php5-pspell-5.2.12_2 needs updating (port has 5.3.2) php5-readline-5.2.12_2needs updating (port has 5.3.2) php5-session-5.2.12_2 needs updating (port has 5.3.2) php5-simplexml-5.2.12_2 needs updating (port has 5.3.2) php5-soap-5.2.12_2needs updating (port has 5.3.2) php5-sockets-5.2.12_2 needs updating (port has 5.3.2) php5-spl-5.2.12_2 = up-to-date with port php5-sqlite-5.2.12_2 needs updating (port has 5.3.2) php5-tidy-5.2.12_2needs updating (port has 5.3.2) php5-tokenizer-5.2.12_2 needs updating (port has 5.3.2) php5-xml-5.2.12_2 needs updating (port has 5.3.2) php5-xmlreader-5.2.12_2 needs updating (port has 5.3.2) php5-xmlrpc-5.2.12_2 needs updating (port has 5.3.2) php5-xmlwriter-5.2.12_2 needs updating (port has 5.3.2) php5-xsl-5.2.12_2 needs updating (port has 5.3.2) php5-zip-5.2.12_2 needs updating (port has 5.3.2) php5-zlib-5.2.12_2needs updating (port has 5.3.2) corvus-root@/usr/ports/databases/php5-sqlite: Is pkgtools a port that I need to install? Another question: I also use portmaster and portmanager. Does these two tools make use of the /usr/local/etc/pkgtools.conf file? ~Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freeze PHP5 at specific version
On Fri, 16 Apr 2010 13:43:13 -0400, Greg Larkin glar...@freebsd.org articulated: Have a look at this page: http://myfreebsd.homeunix.net/hints_n_kinks/ports-pkgtools.html. If you add the php port names to the HOLD_PKGS array, that prevents portupgrade from touching them. WOT http://www.mywot.com/en/scorecard/myfreebsd.homeunix.net gives a warning when accessing that site. I assume it is harmless, although I wonder why it is doing it. -- Jerry freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Self Test for Paranoia: You know you have it when you can't think of anything that's your own fault. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freeze PHP5 at specific version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doug Sampson wrote: Have a look at this page: http://myfreebsd.homeunix.net/hints_n_kinks/ports-pkgtools.html. If you add the php port names to the HOLD_PKGS array, that prevents portupgrade from touching them. Bingo! That is what I'm looking for! Say, do I need to list each PHP5 extension in the HOLD_PKG section? For example, I have the following PHP5 extensions on top of the lang/php5 as follows: corvus-root@/usr/ports/databases/php5-sqlite: portversion -v | g php5 php5-5.2.12_2 needs updating (port has 5.3.2) [...] corvus-root@/usr/ports/databases/php5-sqlite: Is pkgtools a port that I need to install? Another question: I also use portmaster and portmanager. Does these two tools make use of the /usr/local/etc/pkgtools.conf file? ~Doug Hi Doug, This should work, but please test it to make sure: HOLD_PKGS = [ 'bsdpan-*', 'php5*', ] /usr/local/etc/pkgtools.conf is installed as part of the portupgrade port (ports-mgmt/portupgrade or ports-mgmt/portupgrade-devel). portmaster has a -x option where you can specify a glob, like so: portmaster -x 'php5*' -x 'foobar*' ... I have not tested that either, so experimentat on some throwaway port first. For portmanager, it reads pkgtools.conf for setting port build options, but it looks to me like the pkgtools-to-portmanager.rb script converts the contents of HOLD_PKGS to a form that portmanager understands. Cheers, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLyLA30sRouByUApARApTqAJ9o14/4fv1z5IVYzeKh8jIiGOblIACdHcD1 sdbAUZ4Cz+Nf8yXeW+O2FmM= =sHIe -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freeze and crashes
Hi Alain: Without more details its hard to understand where your hang or freeze is coming from. What I DO suggest is that you build a debug kernel and/or minimally enable the kernel debugger (DDB). Then when the box is frozen you can get into the debugger (CTRL-ALT-ESC), type bt, and post it on the list to give everybody a chance to understand what is hanging (show msgbuf as well actually). Here is some good documentation on how to build kernels (and debug ones) if you don't already know: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html Generally speaking I would enable in my KERNCONF file (GENERIC, etc. under src/sys/arch/conf/) # Turn off debugging symbols makeoptions DEBUG=-g # Debugger support options KDB options DDB options KDB_TRACE If you want to go further, for example you believe this is a locking issue then you can go whole hog and do: # Heavy duty debugger options options DEBUG_LOCKS options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN Be warned that the kernel.debug KO (kernel object) will run a lot slower than a stock non-debug kernel (the extra metadata the kernel is keeping track off etc.) so there are instances where running a debug kernels could make a timing bug disappear or appear more/less frequently. In any event, if the problem is easily reproducible, I whole-heartily recommend you minimally enable KDB/DDB support so you can dump things on the appropriate list AS WELL AS build a complete debug kernel that may catch the issue (you will see console messages including lock order reversals and other nastiness). Here is some good documentation about kernel debugging: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Let us know how things go, -aps PS Make sure that new disk is good! On Fri, Apr 25, 2008 at 9:01 AM, Alain G. Fabry [EMAIL PROTECTED] wrote: Have a issue here. I've been running FreeBSD 6.3 release for about 6 months now without problem. Then last week I purchase another external HD and installed release 7.0. Everything went great for about 3 weeks. Then suddenly my 7.0 started to crash (kde freezing, sudden reboots, etc). The first time happened when I was performing a portsnap on a FreeBSD Qemu session. It came up to the point where this 7.0 installation wasn't workable anymore. Since I need to work to earn money as the rest of us, I fell back to my 6.3 release external HD - copied over my data files and now I'm starting to get the same symthoms. Input/output errors, reboot when performing a simple 'man something'. - could this be a virus or something? I'm not sure how or what I can do to find out what could be the cause of this problem? Is there anywhere I can find out more about debugging such strange behavior. (everything works fine and then suddenly it freezes permanently or just reboots on its own) Thanks, PS: I'm about to reinstall the 7.0 release and hope that that will work normal again. Alain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freeze and crashes
On Fri, Apr 25, 2008 at 03:01:53PM +0200, Alain G. Fabry wrote: Have a issue here. I've been running FreeBSD 6.3 release for about 6 months now without problem. Then last week I purchase another external HD and installed release 7.0. Everything went great for about 3 weeks. Then suddenly my 7.0 started to crash (kde freezing, sudden reboots, etc). The first time happened when I was performing a portsnap on a FreeBSD Qemu session. It came up to the point where this 7.0 installation wasn't workable anymore. Since I need to work to earn money as the rest of us, I fell back to my 6.3 release external HD - copied over my data files and now I'm starting to get the same symthoms. Input/output errors, reboot when performing a simple 'man something'. - could this be a virus or something? More likely bad hardware, bad RAM in particular. Or a power supply that's about to give up. I'm not sure how or what I can do to find out what could be the cause of this problem? Run a memory test program. Use a health monitoring program like mbmon to check if the on-board voltage and temperature sensors produce strange values. Hardware problems are notoriously difficult to debug. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpYgoBQX9VvC.pgp Description: PGP signature
Re: freeze and crashes
On Fri, Apr 25, 2008 at 10:47:34AM -0400, Alexander Sack wrote: Thanks everybody for the feedback. I'm not going to bring out the champagne yet but I believe I might have found the problem. Replaced my USB cable and now everything seems to be stable again. I'll definitely look into the info provided below by everybody, don't want to be as frustraded as I was without having a clue what was happening. In case the issue returns, I want to be prepared Thanks, PS Sorry for top posting. Alain Hi Alain: Without more details its hard to understand where your hang or freeze is coming from. What I DO suggest is that you build a debug kernel and/or minimally enable the kernel debugger (DDB). Then when the box is frozen you can get into the debugger (CTRL-ALT-ESC), type bt, and post it on the list to give everybody a chance to understand what is hanging (show msgbuf as well actually). Here is some good documentation on how to build kernels (and debug ones) if you don't already know: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html Generally speaking I would enable in my KERNCONF file (GENERIC, etc. under src/sys/arch/conf/) # Turn off debugging symbols makeoptions DEBUG=-g # Debugger support options KDB options DDB options KDB_TRACE If you want to go further, for example you believe this is a locking issue then you can go whole hog and do: # Heavy duty debugger options options DEBUG_LOCKS options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN Be warned that the kernel.debug KO (kernel object) will run a lot slower than a stock non-debug kernel (the extra metadata the kernel is keeping track off etc.) so there are instances where running a debug kernels could make a timing bug disappear or appear more/less frequently. In any event, if the problem is easily reproducible, I whole-heartily recommend you minimally enable KDB/DDB support so you can dump things on the appropriate list AS WELL AS build a complete debug kernel that may catch the issue (you will see console messages including lock order reversals and other nastiness). Here is some good documentation about kernel debugging: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Let us know how things go, -aps PS Make sure that new disk is good! On Fri, Apr 25, 2008 at 9:01 AM, Alain G. Fabry [EMAIL PROTECTED] wrote: Have a issue here. I've been running FreeBSD 6.3 release for about 6 months now without problem. Then last week I purchase another external HD and installed release 7.0. Everything went great for about 3 weeks. Then suddenly my 7.0 started to crash (kde freezing, sudden reboots, etc). The first time happened when I was performing a portsnap on a FreeBSD Qemu session. It came up to the point where this 7.0 installation wasn't workable anymore. Since I need to work to earn money as the rest of us, I fell back to my 6.3 release external HD - copied over my data files and now I'm starting to get the same symthoms. Input/output errors, reboot when performing a simple 'man something'. - could this be a virus or something? I'm not sure how or what I can do to find out what could be the cause of this problem? Is there anywhere I can find out more about debugging such strange behavior. (everything works fine and then suddenly it freezes permanently or just reboots on its own) Thanks, PS: I'm about to reinstall the 7.0 release and hope that that will work normal again. Alain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freeze During Boot With 6.2-RELEASE Install Disk
On 20/07/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've got a machine that I'm trying to get 6.2-RELEASE installed on, in order to act as a backup/test config server for a production box I have running the same version of FreeBSD. The machine previously had 5.3-RELEASE on a single SCSI disk, with a 4-drive SATA RAID that wasn't quite working right (according to the previous owner; I just got the system a few days ago); unfortunately, the system now refuses to recognize the SCSI disk, even in the Adaptec SCSI card's BIOS. That said, when I pop in my 6.2-RELEASE boot disk, it comes up, loads devices, sees the SATA RAID...and then just hangs. I've tried booting in safe mode and with verbose logging...and it won't work either way, and I get no error messages. FWIW, I took the same boot CD and popped it into an Acer laptop I had handy, and it went straight into the system setup menus, asking me to choose a country; so the CD itself seems unlikely to be the culprit. Additionally, I popped an OpenBSD 3.9 boot CD into the freezing machine, and it came right up to an install prompt -- though it saw the SATA disks as individual entities, and not a RAID. Does anyone have any clue what might be causing this, and/or how to solve it? I'll be happy to provide additional details, I'm just not sure what would be helpful right now. Does the machine still boot 5.3, or does the line: the system now refuses to recognize the SCSI disk, even in the Adaptec SCSI card's BIOS. mean that the drive/controller is actually mussed up? If you can boot 5.3, it would be very helpful to see a dmesg from that. If not, it might still be somewhat enlightening to see where the 6.2 bootup stops, if you can capture that. If the SCSI drive or controller really has gone south in some fun, horrible way, you might try physically removing them, as a malfunctioning controller can cause a rather long* pause in the disk-probing sequence. If you have already removed the SCSI stuff and the 6.2 disk still hangs after the SATA probe and you can't find any way to capture the output, you might try posting the make and model, as there are some dreadful pieces of garbage out there that FreeBSD has some difficulty with. * Potentially limited only by how long your machine continues to have power connected. NB: In my experience OpenBSD is much better at playing fastloose with garbage hardware than FreeBSD. Whether this is a good thing I would not hazard to guess. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freeze During Boot With 6.2-RELEASE Install Disk
I've got a machine that I'm trying to get 6.2-RELEASE installed on, in order to act as a backup/test config server for a production box I have running the same version of FreeBSD. The machine previously had 5.3-RELEASE on a single SCSI disk, with a 4-drive SATA RAID that wasn't quite working right (according to the previous owner; I just got the system a few days ago); unfortunately, the system now refuses to recognize the SCSI disk, even in the Adaptec SCSI card's BIOS. That said, when I pop in my 6.2-RELEASE boot disk, it comes up, loads devices, sees the SATA RAID...and then just hangs. I've tried booting in safe mode and with verbose logging...and it won't work either way, and I get no error messages. FWIW, I took the same boot CD and popped it into an Acer laptop I had handy, and it went straight into the system setup menus, asking me to choose a country; so the CD itself seems unlikely to be the culprit. Additionally, I popped an OpenBSD 3.9 boot CD into the freezing machine, and it came right up to an install prompt -- though it saw the SATA disks as individual entities, and not a RAID. Does anyone have any clue what might be causing this, and/or how to solve it? I'll be happy to provide additional details, I'm just not sure what would be helpful right now. Does the machine still boot 5.3, or does the line: the system now refuses to recognize the SCSI disk, even in the Adaptec SCSI card's BIOS. mean that the drive/controller is actually mussed up? The controller seems to be OK...the drive itself I have no idea about, since I have no other SCSI systems to plug it into to check, and I can't get the controller to recognize it. If you can boot 5.3, it would be very helpful to see a dmesg from that. If not, it might still be somewhat enlightening to see where the 6.2 bootup stops, if you can capture that. If the SCSI drive or controller really has gone south in some fun, horrible way, you might try physically removing them, as a malfunctioning controller can cause a rather long* pause in the disk-probing sequence. Here's where it gets really interesting. I decided yesterday after poking with it for a while that it'd be worth leaving it on while I went and got lunch, just in case the hang was really a ridiculously long pause. When I came back a half-hour or so later, the machine had finished booting into setup, so I installed on the SATA RAID, which went flawlessly. That said, even booting off of that RAID, I'm getting a pause of at least 5 minutes when I boot, so something is either misconfigured on my end, or perhaps FreeBSD doesn't play nice with this particular setup. Dmesg below, in case anyone can comment on this (it's less critical now that the machine will boot, but it'd be nice to have an eventual answer). NB: In my experience OpenBSD is much better at playing fastloose with garbage hardware than FreeBSD. Whether this is a good thing I would not hazard to guess. Me neither. There are real pros and cons there, but this is good to know. Anyway, dmesg: Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: INTEL D945GTP Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3200.02-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf43 Stepping = 3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x649dSSE3,RSVD2,MON,DS_CPL,EST,CNTX-ID,CX16,b14 AMD Features=0x2010NX,LM real memory = 2137509888 (2038 MB) avail memory = 2086703104 (1990 MB) ioapic0: Changing APIC ID to 2 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: INTEL D945GTP on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: display, VGA at device 2.0 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 28.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 28.2 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 28.3 on pci0 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 28.4 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge at device 28.5 on pci0 pci5: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge at device 30.0 on pci0 pci6: ACPI PCI bus on pcib6 fxp0: Intel 82550 Pro/100 Ethernet port 0x1140-0x117f mem
Re: Freeze
On Sun, 11 Jun 2006, NgD Vulto wrote: 2006/6/11, Garrett Cooper [EMAIL PROTECTED]: On Jun 11, 2006, at 3:07 PM, NgD Vulto wrote: I just hate when it happens. I am here on tty1, then I go to tty2...3...and It's ok, but if I keep changing the tty, sometimes when I change the tty it freezes, my screen gets black, and my cpu leds start to blink. Specially when I am on X and I want to go to some tty1. There are systems that have a sleep function which when pressed the sleep button of the keyboard it waits the wake up button to wake up, it seems to me like it's sleeping, but the wake up button doesn't work, neither I pressed the sleep button. I was using the FeeBSD 6.0 and I thought it was a bug, but now I am using the freebsd 6.1 and It still bothers me. Somehow I believe I did not lose the system's control, I believe it's just waiting me to call it up again, just don't know how, and I wonder why it happens. If I wasn't too clear, ask me anything and I can make it clear :) PS: My computer is new and it's all ok, I do use linux also and I had never any kind of problem like that there, I'm totally sure It's not my hardware, when I say I am totally sure, I really mean it. :) Hardware specs? Computer maker (if there is one)? -Garrett What do you mean with computer maker ? Dude, I repeat, it has nothing to do with my hardware, I have a semprom 2.6GHZ. 512 MB (memory) 60gb (hd) ...and It happened to my old computer also, but I upgraded to my semprom. It's something about the tty, because it never happened out of there, just when I change the tty so much... Thanks. 'Dude', it may very well have to deal with who makes your motherboard and how it is supported in FreeBSD. Don't assume that since you have an AMD chipset you are unaffected and just because you don't have problems in one OS, doesn't mean that your problems will be universally unexistent in all OSes. If and when you are asking a question hardware related, it is helpful if you provide information on this list as to what hardware you have, what version of FreeBSD you are running (uname -a does the trick), and some information as to what you have compiled into your kernel (linking to another site with your kernel conf is the best way to deal with that issue). So, again... (and a bit more defined/directed this time in my question, I admit), do you know who makes your motherboard and also are you sure that the BIOS is completely updated? -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freeze
On Jun 11, 2006, at 3:07 PM, NgD Vulto wrote: I just hate when it happens. I am here on tty1, then I go to tty2...3...and It's ok, but if I keep changing the tty, sometimes when I change the tty it freezes, my screen gets black, and my cpu leds start to blink. Specially when I am on X and I want to go to some tty1. There are systems that have a sleep function which when pressed the sleep button of the keyboard it waits the wake up button to wake up, it seems to me like it's sleeping, but the wake up button doesn't work, neither I pressed the sleep button. I was using the FeeBSD 6.0 and I thought it was a bug, but now I am using the freebsd 6.1 and It still bothers me. Somehow I believe I did not lose the system's control, I believe it's just waiting me to call it up again, just don't know how, and I wonder why it happens. If I wasn't too clear, ask me anything and I can make it clear :) PS: My computer is new and it's all ok, I do use linux also and I had never any kind of problem like that there, I'm totally sure It's not my hardware, when I say I am totally sure, I really mean it. :) Hardware specs? Computer maker (if there is one)? -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
