Re: How to check version of Make in FreeBSD
In the last episode (Oct 01), Paul B Mahol said: On 10/1/10, Devin Teske dte...@vicor.com wrote: On 10/1/10, Chetan Shukla chetan.shu...@aricent.com wrote: I need to check the version of Make installed in FreeBSD. make -v does not help here. What is the similar command in FreeBSD ? On Fri, 2010-10-01 at 18:33 +, Paul B Mahol wrote: gmake. On serious side there is no way to find version and freebsd make havent changed much in years... On the command-line... strings `which make` | grep -B1 MAKE_VERSION Or in a makefile... /usr/tmp/Makefile: all: @echo MAKE_VERSION='$(MAKE_VERSION)' make MAKE_VERSION='5200408120' Nice. Even nicer: make -V MAKE_VERSION Not that the version really helps; there have been many additions to make since 2004. -- Dan Nelson dnel...@allantgroup.com ___ 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: How to check version of Make in FreeBSD
Thanks everyone for the guidance. I got the VERSION number as 5200408120 Does it mean it has make-3.81? Also could someone provide guidance on How to run code(C C++) written for Linux/Solaris On FreeBSD machine without changing Makefiles? Thanks Regards, Chetan -Original Message- From: Dan Nelson [mailto:dnel...@allantgroup.com] Sent: Saturday, October 02, 2010 11:33 AM To: Paul B Mahol Cc: Devin Teske; Chetan Shukla; freebsd-questions@freebsd.org Subject: Re: How to check version of Make in FreeBSD In the last episode (Oct 01), Paul B Mahol said: On 10/1/10, Devin Teske dte...@vicor.com wrote: On 10/1/10, Chetan Shukla chetan.shu...@aricent.com wrote: I need to check the version of Make installed in FreeBSD. make -v does not help here. What is the similar command in FreeBSD ? On Fri, 2010-10-01 at 18:33 +, Paul B Mahol wrote: gmake. On serious side there is no way to find version and freebsd make havent changed much in years... On the command-line... strings `which make` | grep -B1 MAKE_VERSION Or in a makefile... /usr/tmp/Makefile: all: @echo MAKE_VERSION='$(MAKE_VERSION)' make MAKE_VERSION='5200408120' Nice. Even nicer: make -V MAKE_VERSION Not that the version really helps; there have been many additions to make since 2004. -- Dan Nelson dnel...@allantgroup.com DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ___ 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: How to check version of Make in FreeBSD
In the last episode (Oct 02), Chetan Shukla said: Thanks everyone for the guidance. I got the VERSION number as 5200408120 Does it mean it has make-3.81? No, it means it has make version 5200408120. make-3.81 is GNU make, while FreeBSD uses BSD make. They are mostly compatible, but there are differences (mainly concerning how you include other makefiles, variable expansion, and looping within a makefile). If you need GNU make, you can install it from the ports tree, and it will be called gmake. Also could someone provide guidance on How to run code(C C++) written for Linux/Solaris On FreeBSD machine without changing Makefiles? If it compiles on Solaris it should compile on FreeBSD, since Solaris doesn't use GNU make either. If you're trying to run some open source software, changes are it's already in the ports tee. If not, you can post your problems here and hopefully someone will help. http://www.freebsd.org/ports/ -- Dan Nelson dnel...@allantgroup.com ___ 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: Updating bzip2 to remove potential security vulnerability
On 01/10/2010 21:59:40, Jerry wrote: On Fri, 1 Oct 2010 12:14:20 -0500 Dan Nelson dnel...@allantgroup.com articulated: You must have missed http://security.freebsd.org/advisories/FreeBSD-SA-10:08.bzip2.asc ; patches for 6, 7, and 8 are available there, and freebsd-update has fixed binaries if you use that. Never saw it. So I am assuming that simply using something like: csup -L2 -h cvsup.FreeBSD.org /usr/src/share/examples/cvsup/standard-supfile Then rebuild Kernel World is not going to work. Is that correct? Not correct. csup(1) /after/ the date that fixes are published will obtain sources that contain the fixes on all affected and supported branches, including 8-STABLE and 9-CURRENT which aren't covered by freebsd-update(8). This will be documented in the security advisory, where they list the revision numbers (both SVN and CVS) at which the fixes were applied. You don't need to /both/ apply patches and use csup -- csup already contains the result of applying the patches. Patches are an alternative to csup, but the intended audience there is typically people running either heavily customized variants of the OS or installations with severely limited bandwidth or restricted internet connectivity. The majority of users should be using the standard update mechanisms -- csup or freebsd-update. Obviously, you will have to compile[*] and install the fixed software. Going through a full buildworld cycle will certainly do that, but in most cases you can achieve the required result by rebuilding and reinstalling significantly smaller chunks of the system. Again, procedures to do this should be described in the security advisory, together with any other requirements (eg. that you would have to reboot your system where there are significant changes to the kernel, or even to ubiquitous bits like libc.so.) Cheers, Matthew [*] Unless you're using freebsd-update, of course. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: 5.25 floppy drive
Thanks to all. Solved. It was a multiple cause issue: 1st: BIOS Setting was incorrect (had to enable 1.2MB 5.25 rather than 3.5 which was it set to - an oversight in the firts place, that occured to me). 2nd: Cable issue: I had a combined cable (3.5 connector at the end and edge connector second but last. 3rd: in combination with 2nd: DS0 jumper issue. Anyway, I found a cable that had two edge connectors. In the end it turns out that the floppies that were lying in a drawer for 19 years, are producing read errors. I also learnt about fdcontrol. Floppy interface has changed significantly since Joerg Wunsch and Bruce Evans worked on them in the early FreeBSD days back in 1995 :) -- Christoph Am 01.10.2010 19:18, schrieb Warren Block: On Fri, 1 Oct 2010, Christoph Kukulies wrote: I'm in the need of reading some data from old 5.25 floppy media (1.2MB). I lent 2 drives from neighbour institutes at the university and after having recalled that the floppies have to be enabled in the BIOS I'm now seeing the fd0 device in dmesg (FreeBSD 8.0 RELEASE). I can do a dd if=/dev/fd0 of=/root/fd0.dmp The select light is lit, the head motor seems to get power but the spindle doesn't spin. Possibly a drive select issue. Some drives had jumpers or switches, some cables have flipped-around wires so the connectors are specific to one drive or another. If your cabling is straight-through with no funny business at the connectors, set the drive to DS0. If the cable has split out and flipped-over sections, DS1 should be set in the jumpers --but then it depends on which connector is used. ...I think, anyway, it's been a few years since I've had to use a 5.25. I tried that with two TEAC drives to no avail. Any clues what I may have forgotten? The drive is connected with the edge connector and the end is open. Does it need to be terminated? None that I've seen. ___ 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 ___ 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: BIND: could not configure root hints from 'named.root': file not found
On 1 October 2010 21:16, CyberLeo Kitsana cyber...@cyberleo.net wrote:
On 10/01/2010 12:52 PM, Matthew wrote:
I would be grateful for any pointers on how to resolve this. I suspect
the error message may not be exactly descriptive of whats happening.
Kinda.
Here's a few points to keep in mind when working with bind in FreeBSD:
* By default, named runs in a chroot jail rooted at /var/named/.
* For security reasons, named cannot write to anything in that tree,
except the dynamic, slave, and working directories.
* named uses its current working directory to resolve relative pathnames
in the configuration file.
* With a recent change to ISC Bind 9, named started complaining if it
couldn't write to its current working directory. At the time, this was
(chroot)/etc/namedb/; this was subsequently changed to
(chroot)/etc/namedb/working/ to make named happy without compromising
security.
When the working directory for named was (chroot)/etc/namedb/,
everything was peachy. Since this was changed, relative pathnames no
longer work as expected because the reference point is different. The
easiest solution is to alter your configuration file to include only
absolute pathnames, relative to the root of the jail.
The default named config file (in /var/named/etc/namedb/named.conf) is
an excellent source of examples for this.
--
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net
cyber...@cyberleo.net
Furry Peace! - http://.fur.com/peace/
___
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
Hmm,
options {
directory.;
that doesnt look ideal. Not sure if you are meaning to do that but put an
explicit direcorty in eg /etc/namedb. Otherwise it will be looking in
whatever current directory you are in at that time. The main named.conf will
be found as its supplied via a cli switch by the rc script. However all
subsequent files will come from the current dir
___
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
Swap on ZFS
Hi I have a virtual server with only 512 MB of memory but still want to run ZFS on it. When there is IO load and only few memory left it occasionally happens that the server freezes, network ping will still work. As far as I know there was the problem that an IO request on ZFS first needs to allocate some memory before it can be run. So in the case where no memory is left and some swap must be used which lies also on ZFS, it would still first need some free memory for the request. This basically results in a deadlock and the system freezes. Would this not happen every time when the system is out of memory and swap must be used? So it basically makes swap on ZFS useless. Has there been any fix or workaround for this? I guess it does not help when I use a swap file on ZFS instead of a separate zvol. Appreciating any ideas Anselm ___ 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
Massive portupgrade without being interrupted by configuration screens?
How can one do a massive portupgrade, as with -r or -R, without being interrupted by options configuration screens for many individual ports? Idea is to let it run unattended such as when I might run it starting just before bedtime. Doing make config ahead of time also gives the chance to recover from a typo at the configuration screen (high risk). Best thing I can think of is, using multimedia/ffmpeg as an example, is doing a dry run portupgrade -Rn multimedia/ffmpeg | tee -a wouldbe.log This would show what other packages would need to be portupgraded and avoid reconfiguring up-to-date dependencies. Then I would go to each of those directories in the ports tree and run make config. Running make config-recursive in /usr/ports/multimedia/ffmpeg would produce configuration screens for all dependencies, including those that are up-to-date. I tried portupgrade -RCn multimedia/ffmpeg | tee -a wouldbe.log but then I got all dependency configuration screens, including those that were up-to-date, and also the interface didn't work right: I got garbage when trying to respond; it didn't write to the configuration screen but produced non-color garbage to the background. Running make config-recursive in /usr/ports/multimedia/ffmpeg would configure all dependencies, including those that are up-to-date and therefore not in need of portupgrading, though make config-recursive seems appropriate for a first build/install of a port. But I think there is no perfect way to be sure of doing all make configs in advance, since selectable options could require additional dependencies. If you try to portupgrade perl to 5.12 and everything that depends on it, as advised in UPDATING file, date 20100715, you will likely get a lot of configuration dialog screens: I speak from experience, would surely like a way to do all these make configs at the beginning. Tom ___ 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: Massive portupgrade without being interrupted by configuration screens?
On 2 October 2010 11:27, Thomas Mueller mueller6...@bellsouth.net wrote: How can one do a massive portupgrade, as with -r or -R, without being interrupted by options configuration screens for many individual ports? Idea is to let it run unattended such as when I might run it starting just before bedtime. Doing make config ahead of time also gives the chance to recover from a typo at the configuration screen (high risk). Best thing I can think of is, using multimedia/ffmpeg as an example, is doing a dry run portupgrade -Rn multimedia/ffmpeg | tee -a wouldbe.log This would show what other packages would need to be portupgraded and avoid reconfiguring up-to-date dependencies. Then I would go to each of those directories in the ports tree and run make config. Running make config-recursive in /usr/ports/multimedia/ffmpeg would produce configuration screens for all dependencies, including those that are up-to-date. I tried portupgrade -RCn multimedia/ffmpeg | tee -a wouldbe.log but then I got all dependency configuration screens, including those that were up-to-date, and also the interface didn't work right: I got garbage when trying to respond; it didn't write to the configuration screen but produced non-color garbage to the background. Running make config-recursive in /usr/ports/multimedia/ffmpeg would configure all dependencies, including those that are up-to-date and therefore not in need of portupgrading, though make config-recursive seems appropriate for a first build/install of a port. But I think there is no perfect way to be sure of doing all make configs in advance, since selectable options could require additional dependencies. If you try to portupgrade perl to 5.12 and everything that depends on it, as advised in UPDATING file, date 20100715, you will likely get a lot of configuration dialog screens: I speak from experience, would surely like a way to do all these make configs at the beginning. Tom ___ 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 have a look at portmaster. It gets all the config bits out of the way at the start then starts the builds ___ 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: FreeBSD on Compaq mini CQ10 anyone?
Le 02/10/2010 07:34, Gonzalo Nemmi a écrit : El 26/09/2010 01:32 p.m., BernardL escribió: Le 05/09/2010 06:04, Gonzalo Nemmi a écrit : I just got one and was wondering if anyone was running FreeBSD on it and how well does it work out of the box. All comments are welcome. I have one with FreeBSD 8.1. Some difficulties to install X11 (I had to use Driver vesa instead of intel in the section Device of xorg.config). And the internal Wifi device is not recognized by FreeBSD. Regards Bernard Lecuire Hi there Bernard and thanks for your comment! Can you tell me if suspend to ram (acpiconf -s3) works on the mini CQ10-120?, although I presume it doesn´t work that well, or at all, if you had to use vesa instead of the intel driver ... I would expect that would cause the screen not to come back after suspend and ACPI is my main concern in my netbook. Are you loading the i915 driver in your /boot/loader.conf? Thanks a lot and my best regards Gonzalo Nemmi Hi Gonzalo, As you expect, the screen doesn't come back. I didn't make any change to /boot/loader.conf. Have a good day Bernard Lecuire ___ 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: 5.25 floppy drive
from Christoph Kukulies k...@kukulies.org: Thanks to all. Solved. It was a multiple cause issue: 1st: BIOS Setting was incorrect (had to enable 1.2MB 5.25 rather than 3.5 which was it set to - an oversight in the firts place, that occured to me). 2nd: Cable issue: I had a combined cable (3.5 connector at the end and edge connector second but last. 3rd: in combination with 2nd: DS0 jumper issue. Anyway, I found a cable that had two edge connectors. In the end it turns out that the floppies that were lying in a drawer for 19 years, are producing read errors. I also learnt about fdcontrol. Floppy interface has changed significantly since Joerg Wunsch and Bruce Evans worked on them in the early FreeBSD days back in 1995 :) -- Christoph Congratulations on solving your floppy problem, but I can understand your problems with floppies. They've gone bad with age for me too. I can read but not write, then I can't read and in most cases can't even reformat. FreeBSD installation sets structure (base.aa, base.ab, base.ac etc.) suggests that one could install from a big set of floppies, but there's no way I could get such a good set of floppies together. I think my 5.25 floppies and drive hold out better than the 3.5 floppies and drives. Tom ___ 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: Massive portupgrade without being interrupted by configuration screens?
On Saturday 02 of October 2010 13:27:00 Thomas Mueller wrote: How can one do a massive portupgrade, as with -r or -R, without being interrupted by options configuration screens for many individual ports? Idea is to let it run unattended such as when I might run it starting just before bedtime. Doing make config ahead of time also gives the chance to recover from a typo at the configuration screen (high risk). Best thing I can think of is, using multimedia/ffmpeg as an example, is doing a dry run portupgrade -Rn multimedia/ffmpeg | tee -a wouldbe.log This would show what other packages would need to be portupgraded and avoid reconfiguring up-to-date dependencies. Then I would go to each of those directories in the ports tree and run make config. Running make config-recursive in /usr/ports/multimedia/ffmpeg would produce configuration screens for all dependencies, including those that are up-to-date. I tried portupgrade -RCn multimedia/ffmpeg | tee -a wouldbe.log but then I got all dependency configuration screens, including those that were up-to-date, and also the interface didn't work right: I got garbage when trying to respond; it didn't write to the configuration screen but produced non-color garbage to the background. Running make config-recursive in /usr/ports/multimedia/ffmpeg would configure all dependencies, including those that are up-to-date and therefore not in need of portupgrading, though make config-recursive seems appropriate for a first build/install of a port. But I think there is no perfect way to be sure of doing all make configs in advance, since selectable options could require additional dependencies. If you try to portupgrade perl to 5.12 and everything that depends on it, as advised in UPDATING file, date 20100715, you will likely get a lot of configuration dialog screens: I speak from experience, would surely like a way to do all these make configs at the beginning. Tom ___ 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 If you are sure that the default configuration settings are OK for you, then one way is to perform a portupgrade with the switches --batch --yes, like portupgrade --batch --yes -a This will assume that the default settings are those you like and will not ask you anything about configuration screens e.t.c. Elias ___ 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: 5.25 floppy drive
On Sat, 02 Oct 2010 10:50:00 + Thomas Mueller mueller6...@bellsouth.net articulated: from Christoph Kukulies k...@kukulies.org: Thanks to all. Solved. It was a multiple cause issue: 1st: BIOS Setting was incorrect (had to enable 1.2MB 5.25 rather than 3.5 which was it set to - an oversight in the firts place, that occured to me). 2nd: Cable issue: I had a combined cable (3.5 connector at the end and edge connector second but last. 3rd: in combination with 2nd: DS0 jumper issue. Anyway, I found a cable that had two edge connectors. In the end it turns out that the floppies that were lying in a drawer for 19 years, are producing read errors. I also learnt about fdcontrol. Floppy interface has changed significantly since Joerg Wunsch and Bruce Evans worked on them in the early FreeBSD days back in 1995 :) -- Christoph Congratulations on solving your floppy problem, but I can understand your problems with floppies. They've gone bad with age for me too. I can read but not write, then I can't read and in most cases can't even reformat. FreeBSD installation sets structure (base.aa, base.ab, base.ac etc.) suggests that one could install from a big set of floppies, but there's no way I could get such a good set of floppies together. I think my 5.25 floppies and drive hold out better than the 3.5 floppies and drives. I had a similar problem last year on a Windows platform when a local municipality asked to move the data from nearly 500 5.25 disks to CD. The disks were in storage since mid 1990. I located an external 5.25 disk drive, they are dirt cheap, and attempted to copy the data. Like you pointed out, the majority of the disks were severely damaged. I finally settled on Spin-Rite http://www.grc.com/spinrite.htm to repair the disks. I had used it before and was familiar with its workings. It took nearly a week for us to get the disks repaired and copied; however, with only a couple of exceptions, the job ended successfully. I cannot comment on 3.5 vs 5.25 disks, except to say good riddance to both formats. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: Cache Memory in top command
_ From: Bas Smeelen [mailto:b.smee...@ose.nl] To: freebsd-questions@freebsd.org Sent: Thu, 30 Sep 2010 14:44:57 +0200 Subject: Re: Cache Memory in top command On 09/30/2010 01:37 PM, RW wrote: On Thu, 30 Sep 2010 09:24:58 +0200 Bas Smeelen b.smee...@ose.nl wrote: *Wired:* number of pages wired down, including cached file data pages That refers to buffer pages (displayed as Buf), which are a subset of the cached file data pages. The pages in the cache queue are not specifically cached file data pages, they are clean pages from any source, including pages that have been written to swap. Thanks. I got this completely wrong, though I have read the FAQ a few years ago. http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#TOP-FREEMEM The values shown by top(1) labeled as Inact, Cache, and Buf are all cached data at different aging levels. DISCLAIMER: This e-mail is for the intended recipient(s) only. Access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you have received it by mistake please let us know by reply and then delete it from your system. ___ 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: 5.25 floppy drive
Hi Christoph, In the end it turns out that the floppies that were lying in a drawer for 19 years, are producing read errors. Do NOT throw them out. I have a tool that can rescue near all data. http://berklix.com/~jhs/src/bsd/jhs/bin/public/valid/ Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not HTML, quoted-printable base 64 spam formats. Avoid top posting, It cripples itemised cumulative responses. ___ 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: USB disk on CS5536 unstable
On 09/30/10 21:38, Hans Petter Selasky wrote: On Thursday 30 September 2010 21:10:59 Anselm Strauss wrote: Maybe sending it to just the USB list was too specific ... On 09/30/10 00:08, Anselm Strauss wrote: Hi I have an ALIX board that has an AMD Geode and the CS5536 companion chip with integrated USB on it. When I connect a USB disk I have observed various problems. For example when I run fsck_ufs on a 250 GB partition the process gets stuck in biord state and fsck reports unreadable sectors. When I do a dd over the whole disk and direct it to /dev/null it suddenly returns with no error, but having read only a small fraction of the disk. I tried it with two different disks and two different ALIX boards. I'm pretty sure the disks are okay since I tried them on other hardware. As far as I know there was some trouble with the chip regarding timeouts. Under load after some time the USB just stops responding. I have tried 8.0 and 8.1. Is there any known problem? How can I track this down? Anselm If you compile the kernel with USB_DEBUG, then there are some sysctls under hw.usb.ehci which you can tweak. Needs to be set before boot. --HPS Did not know that there were configurable bug workarounds in sysctl. When I set hw.usb.ehci.lostintrbug=1 in /boot/loader.conf the problems seem gone. Without this setting I got the following kernel message when dd did abort: ehci_timeout: xfer=0xc29cd3c8 Thanks, Anselm ___ 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: Massive portupgrade without being interrupted by configuration screens?
In the last episode (Oct 02), Thomas Mueller said: How can one do a massive portupgrade, as with -r or -R, without being interrupted by options configuration screens for many individual ports? Idea is to let it run unattended such as when I might run it starting just before bedtime. Doing make config ahead of time also gives the chance to recover from a typo at the configuration screen (high risk). Best thing I can think of is, using multimedia/ffmpeg as an example, is doing a dry run portupgrade -Rn multimedia/ffmpeg | tee -a wouldbe.log This would show what other packages would need to be portupgraded and avoid reconfiguring up-to-date dependencies. Then I would go to each of those directories in the ports tree and run make config. Running make config-recursive in /usr/ports/multimedia/ffmpeg would produce configuration screens for all dependencies, including those that are up-to-date. config-recursive does a config-conditional for each dependency. It should only up a config dialog for an installed up-to-date port if the port maintainer has added OPTIONS lines without bumping the portversion. That should be a rare occurance. I tried portupgrade -RCn multimedia/ffmpeg | tee -a wouldbe.log The -c flag is what you really wanted, I think. -C reconfigures every port, while -c calls make config-conditional. but then I got all dependency configuration screens, including those that were up-to-date, and also the interface didn't work right: I got garbage when trying to respond; it didn't write to the configuration screen but produced non-color garbage to the background. Probably because you tee'd the output, so all the child processes see is a pipe on stdout (and apps usually only try to do color and cursor positioning on ttys). With -n you're not building anything anyway, so there's really no need to log the output. Just run it without the tee, then run your regular portupgrade later with tee. Instead of using tee, I use /usr/bin/script, which gives child processes a real tty to interact with, so full-screen apps work correctly. -- Dan Nelson dnel...@allantgroup.com ___ 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: USB disk on CS5536 unstable
On Saturday 02 October 2010 14:44:07 Anselm Strauss wrote: On 09/30/10 21:38, Hans Petter Selasky wrote: On Thursday 30 September 2010 21:10:59 Anselm Strauss wrote: Maybe sending it to just the USB list was too specific ... On 09/30/10 00:08, Anselm Strauss wrote: Hi I have an ALIX board that has an AMD Geode and the CS5536 companion chip with integrated USB on it. When I connect a USB disk I have observed various problems. For example when I run fsck_ufs on a 250 GB partition the process gets stuck in biord state and fsck reports unreadable sectors. When I do a dd over the whole disk and direct it to /dev/null it suddenly returns with no error, but having read only a small fraction of the disk. I tried it with two different disks and two different ALIX boards. I'm pretty sure the disks are okay since I tried them on other hardware. As far as I know there was some trouble with the chip regarding timeouts. Under load after some time the USB just stops responding. I have tried 8.0 and 8.1. Is there any known problem? How can I track this down? Anselm If you compile the kernel with USB_DEBUG, then there are some sysctls under hw.usb.ehci which you can tweak. Needs to be set before boot. --HPS Did not know that there were configurable bug workarounds in sysctl. When I set hw.usb.ehci.lostintrbug=1 in /boot/loader.conf the problems seem gone. Without this setting I got the following kernel message when dd did abort: ehci_timeout: xfer=0xc29cd3c8 Thanks, Anselm Maybe you can report the PCI vendor ID and product so that we can add this quirk. --HPS ___ 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
ACPI battery issues
I see ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] (20100331/evregion-588) ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.BAT1._BST] (Node 0xc6adba60), AE_NO_HARDWARE_RESPONSE repeatedly in dmesg sysctl's relating to battery information is also slow: % time sysctl hw.acpi.battery.state hw.acpi.battery.state: 7 sysctl hw.acpi.battery.state 0.00s user 2.18s system 72% cpu 3.006 total % time sysctl hw.acpi.battery hw.acpi.battery.life: -1 hw.acpi.battery.time: -1 hw.acpi.battery.state: 7 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 sysctl hw.acpi.battery 0.00s user 6.58s system 67% cpu 9.779 total also note that the life and time are both negative one. This is on a Lenovo G530 laptop. -- Eitan Adler ___ 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: Massive portupgrade without being interrupted by configuration screens?
On Sat, Oct 2, 2010 at 5:27 AM, Thomas Mueller mueller6...@bellsouth.net wrote: How can one do a massive portupgrade, as with -r or -R, without being interrupted by options configuration screens for many individual ports? Idea is to let it run unattended such as when I might run it starting just before bedtime. Doing make config ahead of time also gives the chance to recover from a typo at the configuration screen (high risk). Best thing I can think of is, using multimedia/ffmpeg as an example, is doing a dry run portupgrade -Rn multimedia/ffmpeg | tee -a wouldbe.log This would show what other packages would need to be portupgraded and avoid reconfiguring up-to-date dependencies. Then I would go to each of those directories in the ports tree and run make config. Running make config-recursive in /usr/ports/multimedia/ffmpeg would produce configuration screens for all dependencies, including those that are up-to-date. I tried portupgrade -RCn multimedia/ffmpeg | tee -a wouldbe.log but then I got all dependency configuration screens, including those that were up-to-date, and also the interface didn't work right: I got garbage when trying to respond; it didn't write to the configuration screen but produced non-color garbage to the background. Running make config-recursive in /usr/ports/multimedia/ffmpeg would configure all dependencies, including those that are up-to-date and therefore not in need of portupgrading, though make config-recursive seems appropriate for a first build/install of a port. But I think there is no perfect way to be sure of doing all make configs in advance, since selectable options could require additional dependencies. If you try to portupgrade perl to 5.12 and everything that depends on it, as advised in UPDATING file, date 20100715, you will likely get a lot of configuration dialog screens: I speak from experience, would surely like a way to do all these make configs at the beginning. Tom Well, I'm not using portupgrade, but instead ports-mgmt/portmaster: # portmaster --force-config --no-confirm [...] lang/perl5.12 Gets all of the config menus out of the way (--force-config), and doesn't sit waiting for confirmation to proceed with install (--no-confirm). I do this only the first time I build a port, or if I need to change a config option and reinstall. Works for me! -Brandon ___ 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: Massive portupgrade without being interrupted by configuration screens?
On Sat, 2 Oct 2010 09:49:49 -0500 Brandon Gooch jamesbrandongo...@gmail.com wrote: Well, I'm not using portupgrade, but instead ports-mgmt/portmaster: +1 -- Bruce Cran ___ 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: Massive portupgrade without being interrupted by configuration screens?
On Oct 2, 2010, at 9:49, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Sat, Oct 2, 2010 at 5:27 AM, Thomas Mueller mueller6...@bellsouth.net wrote: How can one do a massive portupgrade, as with -r or -R, without being interrupted by options configuration screens for many individual ports? Idea is to let it run unattended such as when I might run it starting just before bedtime. Doing make config ahead of time also gives the chance to recover from a typo at the configuration screen (high risk). Best thing I can think of is, using multimedia/ffmpeg as an example, is doing a dry run portupgrade -Rn multimedia/ffmpeg | tee -a wouldbe.log This would show what other packages would need to be portupgraded and avoid reconfiguring up-to-date dependencies. Then I would go to each of those directories in the ports tree and run make config. Running make config-recursive in /usr/ports/multimedia/ffmpeg would produce configuration screens for all dependencies, including those that are up-to-date. I tried portupgrade -RCn multimedia/ffmpeg | tee -a wouldbe.log but then I got all dependency configuration screens, including those that were up-to-date, and also the interface didn't work right: I got garbage when trying to respond; it didn't write to the configuration screen but produced non-color garbage to the background. Running make config-recursive in /usr/ports/multimedia/ffmpeg would configure all dependencies, including those that are up-to-date and therefore not in need of portupgrading, though make config-recursive seems appropriate for a first build/install of a port. But I think there is no perfect way to be sure of doing all make configs in advance, since selectable options could require additional dependencies. If you try to portupgrade perl to 5.12 and everything that depends on it, as advised in UPDATING file, date 20100715, you will likely get a lot of configuration dialog screens: I speak from experience, would surely like a way to do all these make configs at the beginning. Tom Well, I'm not using portupgrade, but instead ports-mgmt/portmaster: # portmaster --force-config --no-confirm [...] lang/perl5.12 Gets all of the config menus out of the way (--force-config), and doesn't sit waiting for confirmation to proceed with install (--no-confirm). I do this only the first time I build a port, or if I need to change a config option and reinstall. Works for me! -Brandon If I understand the OPs question correctly, I believe setting the environment variable BATCH=yes will give desired results with portupgrade. This will cause port compile defaults to be used in lieu of an existing /var/db/ports/*/options file. ___ 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: Swap on ZFS
On Sat, Oct 2, 2010 at 4:30 AM, Anselm Strauss amsiba...@gmail.com wrote: Hi I have a virtual server with only 512 MB of memory but still want to run ZFS on it. snip Has there been any fix or workaround for this? I guess it does not help when I use a swap file on ZFS instead of a separate zvol. Make sure you are following this: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot Please note swap is not a ZVOL, it is a sepate partition. You'd have the same problem with ZVOL. Also use i386, that will save you a bit of memory. Follow the ZFS tuning guide. Even if you follow all those things, I'm not sure you'll be able to get it stable. 512MB is really tight. -- Adam Vande More ___ 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: Massive portupgrade without being interrupted by configuration screens?
On Sat, 2 Oct 2010 10:05:33 -0500 Doug Poland d...@polands.org articulated: If I understand the OPs question correctly, I believe setting the environment variable BATCH=yes will give desired results with portupgrade. This will cause port compile defaults to be used in lieu of an existing /var/db/ports/*/options file. I was of the opinion, and I could be wrong, that setting 'BATCH=yes' simply stopped the build process from attempting to create an options file; however, it would use an existing one if it was present. Perhaps someone with more intimate knowledge of this would care to comment. I say this because I have used the BATCH technique once I had all of my ports configured the way I wanted. Subsequent updates always appeared to use any existing configuration files. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ I can't mate in captivity. Gloria Steinem, on why she has never married ___ 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: Massive portupgrade without being interrupted by configuration screens?
On Sat, Oct 2, 2010 at 9:49 AM, Brandon Gooch jamesbrandongo...@gmail.comwrote: On Sat, Oct 2, 2010 at 5:27 AM, Thomas Mueller mueller6...@bellsouth.net wrote: Well, I'm not using portupgrade, but instead ports-mgmt/portmaster: # portmaster --force-config --no-confirm [...] lang/perl5.12 Gets all of the config menus out of the way (--force-config), and doesn't sit waiting for confirmation to proceed with install (--no-confirm). I do this only the first time I build a port, or if I need to change a config option and reinstall. On portmaster version 3, just use -G. No more options menus. -- Adam Vande More ___ 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: Massive portupgrade without being interrupted by configuration screens?
Jerry freebsd.u...@seibercom.net writes: On Sat, 2 Oct 2010 10:05:33 -0500 Doug Poland d...@polands.org articulated: If I understand the OPs question correctly, I believe setting the environment variable BATCH=yes will give desired results with portupgrade. This will cause port compile defaults to be used in lieu of an existing /var/db/ports/*/options file. I was of the opinion, and I could be wrong, that setting 'BATCH=yes' simply stopped the build process from attempting to create an options file; however, it would use an existing one if it was present. Perhaps someone with more intimate knowledge of this would care to comment. I say this because I have used the BATCH technique once I had all of my ports configured the way I wanted. Subsequent updates always appeared to use any existing configuration files. In two minutes of looking at bsd.port.mk, I confirmed that this is correct. ___ 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: Massive portupgrade without being interrupted by configuration screens?
On Sat, Oct 2, 2010 at 10:55 AM, Jerry freebsd.u...@seibercom.net wrote: I was of the opinion, and I could be wrong, that setting 'BATCH=yes' simply stopped the build process from attempting to create an options file; however, it would use an existing one if it was present. Perhaps someone with more intimate knowledge of this would care to comment. I say this because I have used the BATCH technique once I had all of my ports configured the way I wanted. Subsequent updates always appeared to use any existing configuration files. That approach doesn't really make a lot of sense if non-fault options aren't suitable for you. Once you set the port options, the options screen doesn't appear anyway(BATCH=no) unless options have changed. With your usage, a port with non-standard options could be changed, and your build wouldn't be what you expect it to be. -- Adam Vande More ___ 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
ANNOUNCE: Custom 64bit FreeBSD 8.1-RELEASE-p1 with XFCE packages released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, I have just completed an 8.1-RELEASE-p1 based build of the 'Custom releases' project hosted here: http://freebsd-custom.wikidot.com At the moment only the 64bit version is available, while a 32bit version is in the works and is expected later on this week. You may download the ISO file immediately using the downloads page: http://freebsd-custom.wikidot.com/downloads-page This release is based on the latest XFCE desktop and includes a wide variety of desktop-related packages, like OpenOffice, abiword, gnumeric, firefox35, gimp, inkscape, evince and so on. The base system is 8.1-RELEASE. A few other small window managers are included like windowmaker and fluxbox. Note this release does not include editors/zim and x11-wm/icewm due to build problems. Make sure to read the README file before installation. Also note that installing linux related packages during initial setup needs a few more steps. This is due to differences in sysinstall between 7.X and 8.X releases. A detailed explanation is provided in the README file. As always, please report any problems, success stories, comments and criticisms to mano...@freebsd.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyneVIACgkQZ/MxGm4PtJRLyACeJ9xaFnMqmbWG1Bqg215/UZJG t3YAniiuU+JXFARW7Z94TOaA1Ujqbi6p =bs0M -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
OT: fdisk
Greetings I am in deep with the wife. Her computer went belly up. It was running XP pro and I had backups going to a second drive. I can no longer access that drive. I pulled it and attached it via USB to one of my FreeBSD machines but it will not mount. It is a 500G hard drive and I get _wild_ results just looking at it with fdisk. ~ fdisk /dev/da1s1 *** Working on device /dev/da1s1 *** parameters extracted from in-core disklabel are: cylinders=60801 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=60801 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 114 (0x72),(unknown) start 218129509, size 1701990410 (831050 Meg), flag 63 beg: cyl 368/ head 111/ sector 45; end: cyl 371/ head 101/ sector 51 The data for partition 2 is: sysid 116 (0x74),(unknown) start 729050177, size 543974724 (265612 Meg), flag 73 beg: cyl 67/ head 115/ sector 32; end: cyl 299/ head 114/ sector 44 The data for partition 3 is: sysid 101 (0x65),(Novell Netware/386 3.xx) start 168653938, size 0 (0 Meg), flag 74 beg: cyl 114/ head 111/ sector 32; end: cyl 353/ head 115/ sector 52 The data for partition 4 is: sysid 0 (),(unused) start 2692939776, size 51635 (25 Meg), flag 0 beg: cyl 0/ head 0/ sector 0; end: cyl 0/ head 0/ sector 0 I tried to use dd and copy data to another spare drive. It appears to work but then I can no longer mount that drive. Other than taking it to a data recovery shop does anyone have any idea. I haven't told her that her data is lost yet. I may have to wait until we are drinking a bottle of wine. :-) Thanks for any suggestions. Robert ___ 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: router / firewall with PF and carp.
Le Fri, 01 Oct 2010 08:24:30 -0400, Kevin Kobb kk...@skylinecorp.com a écrit : Both would probably be fine. However, I would recommend taking a look at pfsense if I were you. It is made to do what you want without as much of the overhead as a full blown *BSD install. It is easier to configure, update, the documentation is good, and you can get top notch paid support from the developers if you want. Pfsense was our first choice but it does not handle IPv6 yet. http://doc.pfsense.org/index.php/Is_there_IPv6_support_available Thanks to all for yours replies, regards. ___ 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: OT: fdisk
Le Sat, 2 Oct 2010 11:36:40 -0700, Robert travelin...@cox.net a écrit : I tried to use dd and copy data to another spare drive. It appears to work but then I can no longer mount that drive. Other than taking it to a data recovery shop does anyone have any idea. May be photorec will help (in systutils/testdisk). http://www.cgsecurity.org/wiki/PhotoRec Good luck! ___ 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: OT: fdisk
On Sat, 2 Oct 2010 11:36:40 -0700 Robert travelin...@cox.net articulated: I am in deep with the wife. Her computer went belly up. It was running XP pro and I had backups going to a second drive. I can no longer access that drive. If the disk is the problem, I would suggest getting a copy of Spin-Rite http://www.grc.com/spinrite.htm and running it at level 6 maximum. It is the best disk recovery program I have come across. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ History books which contain no lies are extremely dull. ___ 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: OT: fdisk
On 02.10.2010 21:08, Jerry wrote: On Sat, 2 Oct 2010 11:36:40 -0700 Robert travelin...@cox.net articulated: I am in deep with the wife. Her computer went belly up. It was running XP pro and I had backups going to a second drive. I can no longer access that drive. If the disk is the problem, I would suggest getting a copy of Spin-Rite http://www.grc.com/spinrite.htm and running it at level 6 maximum. It is the best disk recovery program I have come across. +1 to that. I've been using spinrite for more than a decade, and have lost count of the times it has saved data for me (or rather: For people dumping their crashed pc in my lap, since _I_ have _BACKUPS_). When you're done recovering data, you might want to take a look at your backup strategy. Select a new one that doesn't depend on spinning metal just as fragile as the one you're backing up from. //Svein -- +---+--- /\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- If you really are in a hurry, mail me at svein-mob...@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: ACPI battery issues
Sorry for the top post - I'm on my mobile. I get the same messages with the stock acpi on a Lenovo S10e. Someone on the acpi list (who's name I forget) wrote a patch which removes the error. If you think it might help I'll root it out and forward it on. Regards, Peter Harrison www.4harrisons.blogspot.com - From: Eitan Adler li...@eitanadler.com Subject:ACPI battery issues Date: 02nd October 2010 15:43 I see ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] (20100331/evregion-588) ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.BAT1._BST] (Node 0xc6adba60), AE_NO_HARDWARE_RESPONSE repeatedly in dmesg sysctl's relating to battery information is also slow: % time sysctl hw.acpi.battery.state hw.acpi.battery.state: 7 sysctl hw.acpi.battery.state 0.00s user 2.18s system 72% cpu 3.006 total % time sysctl hw.acpi.battery hw.acpi.battery.life: -1 hw.acpi.battery.time: -1 hw.acpi.battery.state: 7 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 sysctl hw.acpi.battery 0.00s user 6.58s system 67% cpu 9.779 total also note that the life and time are both negative one. This is on a Lenovo G530 laptop. -- Eitan Adler ___ 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 ___ 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: ACPI battery issues
On Sat, Oct 2, 2010 at 4:01 PM, four.harris...@googlemail.com wrote: I get the same messages with the stock acpi on a Lenovo S10e. Someone on the acpi list (who's name I forget) wrote a patch which removes the error. If you think it might help I'll root it out and forward it on. I'll be happy to take a look at the patch and see if it solves my problem. does the patch just remove the error message or solve a specific problem that might be causing the issue? ... I see ACPI Exception: AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] (20100331/evregion-588) ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.LPCB.BAT1._BST] (Node 0xc6adba60), AE_NO_HARDWARE_RESPONSE repeatedly in dmesg sysctl's relating to battery information is also slow: % time sysctl hw.acpi.battery.state hw.acpi.battery.state: 7 sysctl hw.acpi.battery.state 0.00s user 2.18s system 72% cpu 3.006 total % time sysctl hw.acpi.battery hw.acpi.battery.life: -1 hw.acpi.battery.time: -1 hw.acpi.battery.state: 7 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 sysctl hw.acpi.battery 0.00s user 6.58s system 67% cpu 9.779 total also note that the life and time are both negative one. This is on a Lenovo G530 laptop. -- Eitan Adler ___ 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: OT: fdisk
On Sat, 2 Oct 2010, Robert wrote: Greetings I am in deep with the wife. Her computer went belly up. It was running XP pro and I had backups going to a second drive. I can no longer access that drive. I pulled it and attached it via USB to one of my FreeBSD machines but it will not mount. It is a 500G hard drive and I get _wild_ results just looking at it with fdisk. ~ fdisk /dev/da1s1 *** Working on device /dev/da1s1 *** Wait a minute... shouldn't that be just da1? da1s1 is the first slice (partition), and the data there should be your XP filesystem, probably NTFS. ___ 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: OT: fdisk
On Sat, 2 Oct 2010 17:00:00 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: On Sat, 2 Oct 2010, Robert wrote: Greetings I am in deep with the wife. Her computer went belly up. It was running XP pro and I had backups going to a second drive. I can no longer access that drive. I pulled it and attached it via USB to one of my FreeBSD machines but it will not mount. It is a 500G hard drive and I get _wild_ results just looking at it with fdisk. ~ fdisk /dev/da1s1 *** Working on device /dev/da1s1 *** Wait a minute... shouldn't that be just da1? da1s1 is the first slice (partition), and the data there should be your XP filesystem, probably NTFS. Warren, You are right. Here it is: ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=60801 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=60801 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 7 (0x07),(NTFS, OS/2 HPFS, QNX-2 (16 bit) or Advanced UNIX) start 63, size 976773105 (476939 Meg), flag 0 beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 15/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED Which looks a lot better. I can mount /dev/da1 and it shows ~ ls -l /mnt total 70044 -rwxr-xr-x 1 root wheel 2560 Dec 31 1600 $AttrDef -rwxr-xr-x 1 root wheel 0 Oct 1 09:09 $BadClus -rwxr-xr-x 1 root wheel 4194304 Dec 31 1600 $Bitmap -rwxr-xr-x 1 root wheel 8192 Oct 1 09:09 $Boot drwxr-xr-x 1 root wheel 0 Oct 1 09:09 $Extend -rwxr-xr-x 1 root wheel 67108864 Oct 1 09:09 $LogFile -rwxr-xr-x 1 root wheel 4096 Oct 1 09:09 $MFTMirr -rwxr-xr-x 1 root wheel 0 Dec 31 1600 $Secure -rwxr-xr-x 1 root wheel131072 Oct 1 09:09 $UpCase -rwxr-xr-x 1 root wheel 0 Oct 1 09:09 $Volume -rwxr-xr-x 1 root wheel 45124 Aug 18 2001 NTDETECT.COM drwxr-xr-x 1 root wheel 0 Oct 1 17:29 System Volume Information -rwxr-xr-x 1 root wheel 193 Oct 1 09:12 boot.ini -rwxr-xr-x 1 root wheel222368 Aug 18 2001 ntldr But I cannot mount /dev/da1s1 ~ sudo mount_ntfs /dev/da1s1 /mnt mount_ntfs: /dev/da1s1: Invalid argument Patrick wrote May be photorec will help (in systutils/testdisk). http://www.cgsecurity.org/wiki/PhotoRec I installed this and can successfully recover the date to a spare slice. The problem is the data is all over the place. There is a ton if png files from her playing games on facebook. This can be better than nothing because I can go through the files and move/rename the ones we want to keep. Thank you both. I am willing to try any other suggestions. It appears the the motherboard went gradually bad and hosed up this drive. Robert ___ 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: OT: fdisk
On Sat, 2 Oct 2010, Robert wrote: But I cannot mount /dev/da1s1 ~ sudo mount_ntfs /dev/da1s1 /mnt mount_ntfs: /dev/da1s1: Invalid argument It's weird that da1 can be mounted, but da1s1 can't. Maybe a problem with the filesystem. Might be repairable, although probably it would need proprietary programs. Don't experiment with the original drive, make a copy with dd for experimenting. ___ 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: OT: fdisk
On Sat, 2 Oct 2010 19:09:27 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: It's weird that da1 can be mounted, but da1s1 can't. Maybe a problem with the filesystem. Might be repairable, although probably it would need proprietary programs. Don't experiment with the original drive, make a copy with dd for experimenting. Warren I should have mentioned that before. dd was the first thing I tried. I had an unused drive setup as UFS. Then did dd if=/dev/da1s1 of=/dev/ad12s1d bs=1m count=2000 thinking I could try the first two gigabytes and then go from there. It look like it went fine but then I could not mount the ad12s1d partition. It was able to mount it previously. Going back even further, When I first realized there was a problem with this drive, I booted with 8.1 livefs. The drive had lost it's id that showed it was NTFS. I used sade and marked it as NTFS but was never able to mount it. It is very possible that I messed it up but I was having all sorts of problems with that computer and XP pro doesn't exactly help one out. Thanks again for your time. Robert ___ 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
