Re: Installing FreeBSD 6.0 on IBM BladeCenter HS20
Damian Gerow wrote: Thus spake fbsd_user ([EMAIL PROTECTED]) [10/03/06 08:59]: : I see you both have Bladecenters. : Have you had any luck with getting FreeBSD to install on it yet. : : What is the status of your efforts. : : Been offered contract to do this for client, : but need to know if it can be done before I accept the job. I have yet to get it working, but I've been focusing explicitly on an Opteron blade using an amd64 install. It seems as though you may have luck by using an Intel blade (these are by far more common), and doing the install via the Java-based console provided by the Management Module. It seems as though the keyboard just 'works' once you boot into an installed system. However, as I've not personally gotten it to work (and won't be able to play with it for at least another two weeks), I can only say I suspect that approach will work. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Maybe this might help: http://wiki.bsdforen.de/index.php/FreeBSD_On_IBM_Blade ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Local portaudit server.
David Robillard wrote:
Hello,
We use the port security/portaudit on all of our FreeBSD servers.
Currently, every machine has to out on the internet to download the
portaudit vulnerability database from the FreeBSD server.
Since all of the machines are downloading the exact same file, we
would like to setup a local portaudit server. This server would fetch
the vulnerabilty file and all the rest of our servers would fetch it
from the local portaudit server.
Has anyone done this setup? Any help/pointers would be great.
Hi
I haven't done it but I don't think it should be a problem:
If you look at the portaudit script
/usr/local/sbin/portaudit
you'll find that the auditfile is located here:
http://www.freebsd.org/ports/auditfile.tbz
You can get it manually, try.
So by changing some variables in
portaudit_confs()
{
: ${portaudit_dir=/var/db/portaudit}
: ${portaudit_filename=auditfile.tbz}
: ${portaudit_fetch_env=}
: ${portaudit_fetch_cmd=fetch -1mp}
: ${portaudit_sites=http://www.FreeBSD.org/ports/}
: ${portaudit_fixed=}
if [ -r /usr/local/etc/portaudit.conf ]; then
. /usr/local/etc/portaudit.conf
fi
}
on each machine you should be able to guide them to your local machine.
hth
lars.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
make installworld fails
Hi all, After doing a svsup yesterday and doing a 'make -j4 buildworld' i've (my script that is) tried to proceed with a 'make installworld'. But it failed : www# make installworld ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have checked /usr/src/UPDATING but there isn't any entry new about new groups and 'grep -w audit /etc/group' does not show any audit-group present. I also did a 'rm -rf /usr/obj/* ' and ran 'make -j4 buildworld' again, which endend without errors but the following 'make installworld' stops with the mentioned error again. I am using the '*default release=cvs tag=RELENG_6' in the supfile and am running 6.1-PRERELEASE now. What am I doing wrong ? Any clues are welcome. Beni. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
[EMAIL PROTECTED] wrote: Hi all, After doing a svsup yesterday and doing a 'make -j4 buildworld' i've (my script that is) tried to proceed with a 'make installworld'. But it failed : www# make installworld ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have checked /usr/src/UPDATING but there isn't any entry new about new groups and 'grep -w audit /etc/group' does not show any audit-group present. I also did a 'rm -rf /usr/obj/* ' and ran 'make -j4 buildworld' again, which endend without errors but the following 'make installworld' stops with the mentioned error again. I am using the '*default release=cvs tag=RELENG_6' in the supfile and am running 6.1-PRERELEASE now. What am I doing wrong ? Any clues are welcome. The error message is wrong. There is a new group in '/etc/group' called 'audit:*:77:'. I recommend you don't automate mergemaster operations, and rerun the whole procedure manually. hth lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dge-530T Gigabit Ethernet Adapter
Hi, I am using FreeBSD6.0(6.0-RELEASE FreeBSD 6.0-RELEASE #1). I just bought two dge-530T gigabyte ethernet cards and installed them in my computer. I have sk compiled into my kernel, but on boot they are not recognized. Is there any additional steps I need to take? My kernel config file(PCI-Ethernet Portion) as well as pertaining snippet of dmesg are below. When doing a sysinstall to add a new network interface it is also not listed. Thank you for your time in reading this message. Freesbie # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support #device bfe # Broadcom BCM440x 10/100 Ethernet #device bge # Broadcom BCM570xx Gigabit Ethernet #device dc # DEC/Intel 21143 and various workalikes #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device lge # Level 1 LXT1001 gigabit Ethernet #device nge # NatSemi DP83820 gigabit Ethernet #device nve # nVidia nForce MCP on-board Ethernet Networking #device pcn # AMD Am79C97x PCI 10/100(precedence over 'lnc') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 device sk # SysKonnect SK-984x SK-982x gigabit Ethernet #device ste # Sundance ST201 (D-Link DFE-550TX) #device ti # Alteon Networks Tigon I/II gigabit Ethernet #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vge # VIA VT612x gigabit Ethernet #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') Dmesg Snippet pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: network, ethernet at device 9.0 (no driver attached) pci1: network, ethernet at device 10.0 (no driver attached) pci1: simple comms at device 11.0 (no driver attached) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
[EMAIL PROTECTED] wrote: Hi all, After doing a svsup yesterday and doing a 'make -j4 buildworld' i've (my script that is) tried to proceed with a 'make installworld'. But it failed : www# make installworld ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have checked /usr/src/UPDATING but there isn't any entry new about new groups and 'grep -w audit /etc/group' does not show any audit-group present. I also did a 'rm -rf /usr/obj/* ' and ran 'make -j4 buildworld' again, which endend without errors but the following 'make installworld' stops with the mentioned error again. I am using the '*default release=cvs tag=RELENG_6' in the supfile and am running 6.1-PRERELEASE now. What am I doing wrong ? Any clues are welcome. The error message is wrong. There is a new group in '/etc/group' called 'audit:*:77:'. I recommend you don't automate mergemaster operations, and rerun the whole procedure manually. hth lars. Lars, This is the script in question : #!/bin/sh echo Subject: `hostname` weekly cvsup run output /usr/local/bin/cvsup -g -L 2 /root/supfile cd /usr/src echo === echo Make buildworld now... echo === make -j4 buildworld echo === echo Make buildkernel now... echo === make buildkernel KERNCONF=BENI-60 echo === echo Make installkernel now... echo === make installkernel KERNCONF=BENI-60 echo === echo Make installworld now... echo === make installworld echo === echo `date` : Build Completed echo === if [ $? -eq 0 ]; then echo === echo `date` : BENI-60 kernel build completed echo === else echo '**' echo `date`: BENI-60 kernel build failed echo '**' fi echo === echo updating portstree now... echo === /usr/sbin/portsnap fetch update echo === echo These ports need updating... echo === pkg_version -l '' I didn't re-cvsup after doing the 'rm -rf /usr/obj/*', but did a manually 'make -j4 make buildworld' which ended without problems or errors. I don't mergemaster. If I manually add the group 'audit' the problem should be fixed ? Is this a new group or is it needed for some program ? Thanks, Beni. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On Sat, Mar 11, 2006 at 10:52:01AM +0100, [EMAIL PROTECTED] wrote: [no he didn't; please use a mail client that quotes properly - it is confusing to read your emails otherwise, since Lars wrote some of the below text and not you] The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. There is a new group in '/etc/group' called 'audit:*:77:'. I recommend you don't automate mergemaster operations, and rerun the whole procedure manually. Yes, this script is just asking for trouble. Still, I bet you'll stop using it after the first time it destroys your FreeBSD installation :-) This is the script in question : #!/bin/sh echo Subject: `hostname` weekly cvsup run output /usr/local/bin/cvsup -g -L 2 /root/supfile cd /usr/src echo === echo Make buildworld now... echo === make -j4 buildworld echo === echo Make buildkernel now... echo === make buildkernel KERNCONF=BENI-60 echo === echo Make installkernel now... echo === make installkernel KERNCONF=BENI-60 echo === echo Make installworld now... echo === make installworld echo === echo `date` : Build Completed echo === if [ $? -eq 0 ]; then echo === echo `date` : BENI-60 kernel build completed echo === else echo '**' echo `date`: BENI-60 kernel build failed echo '**' fi echo === echo updating portstree now... echo === /usr/sbin/portsnap fetch update echo === echo These ports need updating... echo === pkg_version -l '' I didn't re-cvsup after doing the 'rm -rf /usr/obj/*', but did a manually 'make -j4 make buildworld' which ended without problems or errors. I don't mergemaster. You need to. If you insist on not doing so, any problems that result are your own concern. If I manually add the group 'audit' the problem should be fixed ? Is this a new group or is it needed for some program ? It's needed by parts of FreeBSD, which is why it's there. Kris pgpefc7JHHYDz.pgp Description: PGP signature
Re: I have one question?
On 3/10/06, Marko Bukovinsky [EMAIL PROTECTED] wrote: Where i can find a list of comands using them in FreeBSD? And second ,how to download apache server and how to configure it in Xterm?(how to open file,set it,copy files in the directory,config mysql database,and start server) all this in Xterm(not X window) As to question zero: ls /bin /sbin /libexec /usr/bin /usr/sbin /usr/libexec \ /usr/local/bin /usr/local/sbin /usr/X11R6/bin As to question one: try building it from ports? -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: disklabel messup.
On 3/10/06, Steve P. [EMAIL PROTECTED] wrote: I was using sysinstall's disklabel facility to poke around. I accidentally did Undo on my installed 6.0 working slice. Are you sure you actually did anything? If /etc/fstab shows them correctly still and running 'df' shows them still as they should be, I'm pretty sure that running sysinstall again will show the slices and partitions correctly. I would advise that 'bsdlabel /dev/ad0' will show you your label just as effectively, and that df(1) is probably the correct method of gazing in rapture at your mounted partitions. Other commands to read up on might be fdisk and diskinfo. Good luck. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On Sat, Mar 11, 2006 at 10:52:01AM +0100, [EMAIL PROTECTED] wrote: [no he didn't; please use a mail client that quotes properly - it is confusing to read your emails otherwise, since Lars wrote some of the below text and not you] Yes he did, but i don't see the relevance of this remark to the initial question. But to answer your question, this is written via webmail, so any issues your reader has, please contact my provider (dommel.be) so that he can change this webmail program. The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. There is a new group in '/etc/group' called 'audit:*:77:'. I recommend you don't automate mergemaster operations, and rerun the whole procedure manually. Yes, this script is just asking for trouble. Still, I bet you'll stop using it after the first time it destroys your FreeBSD installation :-) Until now this script did exactly what is was supposed to do, so I don't see why I should stop now. I didn't re-cvsup after doing the 'rm -rf /usr/obj/*', but did a manually 'make -j4 make buildworld' which ended without problems or errors. I don't mergemaster. You need to. If you insist on not doing so, any problems that result are your own concern. So why didn't the maintainers/programmers add an entry to UPDATING ? That's why the file is for, no ? To explain any changes made and to prevent destroying your fbsd installation I thought... If I manually add the group 'audit' the problem should be fixed ? Is this a new group or is it needed for some program ? It's needed by parts of FreeBSD, which is why it's there. Then it's very recently added, cause I used the same script last week without any problems. But your suggestion to 'mergemaster -p' added the new group and the 'make installworld' completed without any further problems. Thanks. Beni([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: a stupid question about sound
On 3/10/06, Tsu-Fan Cheng [EMAIL PROTECTED] wrote: hi, I got a situation, for some reason, only root can use audio device when playing movies with mplayer on my freebsd 6.0/amd64 now, not user. But vlc is fine for both. I guess there is some audio wrapper issue but couldn't put a finger on it, any idea? If you do: ls -l /dev | grep dsp crw-rw-rw- 1 rootwheel 0, 38 Mar 10 00:57 dsp0.0 crw-rw-rw- 1 rootwheel 0, 41 Mar 6 12:43 dsp0.1 crw-rw-rw- 1 rootwheel 0, 39 Mar 6 12:43 dspW0.0 crw-rw-rw- 1 rootwheel 0, 42 Mar 6 12:43 dspW0.1 crw-rw-rw- 1 rootwheel 0, 44 Mar 6 12:43 dspr0.1 Does it look mostly like that? If you don't have a problem there, it might be with mplayer. I noticed a minor update sometime in the last few days, but I haven't actually done the update. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On Sat, Mar 11, 2006 at 11:39:17AM +0100, [EMAIL PROTECTED] wrote: On Sat, Mar 11, 2006 at 10:52:01AM +0100, [EMAIL PROTECTED] wrote: [no he didn't; please use a mail client that quotes properly - it is confusing to read your emails otherwise, since Lars wrote some of the below text and not you] Yes he did, but i don't see the relevance of this remark to the initial question. It's in your own interests to write easily readable emails, otherwise people won't read them. But to answer your question, this is written via webmail, so any issues your reader has, please contact my provider (dommel.be) so that he can change this webmail program. The error message is wrong. Actually it's correct, just a bit unclear. ?UPDATING includes the complete procedure you should always follow when building world. ?It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. There is a new group in '/etc/group' called 'audit:*:77:'. I recommend you don't automate mergemaster operations, and rerun the whole procedure manually. Yes, this script is just asking for trouble. ?Still, I bet you'll stop using it after the first time it destroys your FreeBSD installation :-) Until now this script did exactly what is was supposed to do, so I don't see why I should stop now. OK. I hope you remember this conversation when that day comes :-) Kris pgpowimgmpecZ.pgp Description: PGP signature
Re: Help with IP Filter 4.1.8
Roman Serbski wrote: Start over with a clean /usr/src and /usr/obj tree and read the file ``/usr/src/UPDATING'' for instructions about upgrading from source. Dear Erik and Giorgos, Thanks a lot for your assistance! I just cvsuped one hour ago, build/install kernel/world and now everything is working just fine! I had probably a bad luck during first cvsup... One last question (just for curiosity). What is the procedure for _upgrading_ of ipf? I mean, since ipf is already included in the base (v4.1.8), is it possible to upgrade it to v4.1.10? The ipf source is as I understand it compiled as kernel modules or into the kernel and some administrative applications are compiled to interact with the kernel. Hence, as mentioned by Giorgos, upgrading by downloading the source from the official site should be done with care. The recommended way is as Giorgos say to update your source and go with the current version included in FreeBSD. When I suggested to look at more resent versions it was more to check the history and see if there was some bug discovered in 4.1.8 that had been corrected and could have been causing your troubles. If there are such bugs you should file a problem report. If changes are minor it may be possible to merge the newer version into the FreeBSD code, but at the cost that on next cvsup you will have to do it again unless the newer version has been adopted. If there are no such problems, don't bother to update. In such a crucial part of the system it is important to be aware of the actual benefit from upgrading. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD cluseter ?
RJ45 skrev: Hello, I have the tastk to make a project of a server cluster for 20.000 mailboxes. In which way may I create a cluseter of imap servers using FreeBSD ? any suggestions or hints ? The is the problem of the imap mailboxes. How can I syncronize them in real time on both machines ? I as thinking to cyrus imapd or dovecot as imap server, but anyway 20.000 mailboxes are really huge... And with cyrus imapd is impossible to achieve a real fail over system even using cyrus murder. Have you looked at cyrus-imapd23? Anyone knows which kind of solutions are used by yahoo for example ? thank you The replication features in cyrus-imapd23 is AFAIK originally developed by or for fastmail.fm. It is still considered beta software, but at least some versions of it has been used in large setups for some time. -- Regards from Lars Rick ___ 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]
Arplookup strange messages
Hi list, today in the daily security report (periodic) of a i386 machine there is this message repeated about 30 times: +arplookup 0.0.0.0 failed: host is not on local network The machine is the router (ipnat) and firewall (ipfilter) for a small home network. It runs postfix, sshd and nfsd. Since I'm away from home now, I can't sit in front of it and check what's wrong. Furthermore, it seams that the machine is not accepting ssh logins anymore, after those strange messages. Any ideas about the cause of it? Thanks, -- Pietro Cerutti [EMAIL PROTECTED] Non lasciar calpestare i TUOI diritti! Don't let 'em take YOUR rights! NO al Trusted Computing! Say NO to Trusted Computing! www.no1984.org www.againsttcpa.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
Kris Kennaway wrote: The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. Dear Kris I have a few questions related to this error message ERROR: Required audit group is missing, see /usr/src/UPDATING I know that updating requires the mergemaster steps because I read the handbook. But I don't understand why this message tells me to look in that file, when there's nothing about that in it. Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Or is there a file which describes how I can manually insert needed groups and users when I mess up mergemaster runs? Or is that pointless anyway since I could just remove /usr/obj and rerun the whole updating procedure again before I reboot? And finally, is it really necessary to reboot after 'mergemaster -p'? Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) I would be very grateful for any explanations. Thanks lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
md0: Preloaded image - system hangs on install
Hello, all. I trying to install 6.0 on a old box K-6/180(still ok with system requirements) and it hangs when gets to this message: md0: Preloaded image (/boot/mfsroot) xxx bytes at xx. I saw that question several times, but no answer. What should I do? Thanks in advance. Roman Gorohov. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Fri, Mar 10, 2006 at 11:57:59PM -0500, Peter wrote: I'm setting up a new server on 6.0 I've been planning for a long time and I am very disappointed with two critical issues. My motherboard is the ASUS K8V-X SE that I chose because it was listed as compatible at the FreeBSD/amd64 Project: http://www.freebsd.org/platforms/amd64/motherboards.html I wonder if going back to 5.4 might help? Onto the problems... You might have more luck if you also talk to [EMAIL PROTECTED] I'm not sure who this is but I'll look into it. 2. I can't use my USB ports! I get a line like this for each of my ports: uhci0: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] OK, but what is the problem? When something is plugged into a port and the system is powered up it will freeze at the POST level with no errors. It just sits there. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Arplookup strange messages
Pietro Cerutti wrote: Hi list, today in the daily security report (periodic) of a i386 machine there is this message repeated about 30 times: +arplookup 0.0.0.0 failed: host is not on local network From rfc 3330: 0.0.0.0/8 - Addresses in this block refer to source hosts on this network. Address 0.0.0.0/32 may be used as a source address for this host on this network; other addresses within 0.0.0.0/8 may be used to refer to specified hosts on this network [RFC1700, page 4]. I think in packet filter you can specify 0/32 and it will automatically be replaced by the ip on the relevant interface, this is useful when you have nics configured with dhcp. However, not all programs support this and will instead try to make an arplookup which is bound to fail. So first question is, what program causes this arplookup? - Do you in your firewall rules specify 0/32? - Do you have correctly set antispoofing? If your firewall does not drop packets from 0/8 then it may try to send a response to the invalid ip. - Do you have dhcp configured somewhere for some host? IIRC dhcp requests are sent with source 0/32 to destination 255.255.255.255/0 (rfc 2131). Your firewall may (it shouldn't, but check anyway) incorrectly try to route it if you don't have the antispoofing setup. If dhcp configuration fails, sometimes the interface gets assigned the address 0/32 unless some fallback have been configured. This could be a client on your network that is misconfigured. The machine is the router (ipnat) and firewall (ipfilter) for a small home network. It runs postfix, sshd and nfsd. My guess is to take a look at your firewall rules and check if there are any misbehaving dhcp clients. Since I'm away from home now, I can't sit in front of it and check what's wrong. Furthermore, it seams that the machine is not accepting ssh logins anymore, after those strange messages. Well, then you have a problem correcting this - maybe someone can reboot the machine for you? Hope this helps, Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On Sat, Mar 11, 2006 at 12:28:32PM +0100, [EMAIL PROTECTED] wrote: Kris Kennaway wrote: The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. Dear Kris I have a few questions related to this error message ERROR: Required audit group is missing, see /usr/src/UPDATING I know that updating requires the mergemaster steps because I read the handbook. But I don't understand why this message tells me to look in that file, when there's nothing about that in it. Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Yes, /usr/src/UPDATING does describe the correct updating procedure. If you follow that procedure you should not have any problems with missing groups. Look under COMMON ITEMS at the end of /usr/src/UPDATING. Or is there a file which describes how I can manually insert needed groups and users when I mess up mergemaster runs? Or is that pointless anyway since I could just remove /usr/obj and rerun the whole updating procedure again before I reboot? And finally, is it really necessary to reboot after 'mergemaster -p'? Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) It is sometimes necessary to reboot with the new kernel to have 'make installworld' work correctly (and the recommended procedure is to reboot into single user mode *before* running 'mergemaster -p' (which in turn is to be done before 'make installworld'). I would be very grateful for any explanations. Thanks lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Insert your favourite quote here. Erik Trulsson [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: make installworld fails
Erik Trulsson wrote: Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Yes, /usr/src/UPDATING does describe the correct updating procedure. If you follow that procedure you should not have any problems with missing groups. Look under COMMON ITEMS at the end of /usr/src/UPDATING. Right, thanks. And finally, is it really necessary to reboot after 'mergemaster -p'? Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) It is sometimes necessary to reboot with the new kernel to have 'make installworld' work correctly (and the recommended procedure is to reboot into single user mode *before* running 'mergemaster -p' (which in turn is to be done before 'make installworld'). Correct, I forgot since I hadn't been doing it in a while (so much for reading the handbook...). But how do I know when it's necessary? Or should I just reboot twice no matter what? Thanks, Lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
On 3/11/06, Peter [EMAIL PROTECTED] wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: You might have more luck if you also talk to [EMAIL PROTECTED] I'm not sure who this is but I'll look into it. The amd64-related mailing list When something is plugged into a [USB] port and the system is powered up it will freeze at the POST level with no errors. It just sits there. And this is of course due to the evil FreeBSD daemon living somewhere under the hood of your PC ever since you placed the ominous disc into your CD-ROM drive... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: from Anang in Indonesia
On 3/10/06, anang prihantono anang [EMAIL PROTECTED] wrote: How can I make FreeBSD as internet gateway(router)only for dial up router and DSL line.Thaks.. It took me about 20 hours of reading the handbook and googling to set up my first FreeBSD LAN-to-DSL gateway with no prior *nix experience whatsoever. Of course, I had to improve the setup in almost every way later, but the initial learning curve is very short. It's the desire and excitement that you'll need. Look at http://www.m0n0.ch/wall/ for a specialized FreeBSD-based appliance. Good luck! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to build or update vcdimager
Norikatsu Shigemura wrote: On Fri, 10 Mar 2006 17:42:36 -0500 (EST) Gerard Seibert [EMAIL PROTECTED] wrote: I have been attempting to update the vcdimager port. It always fails with this message: install-info --quiet /usr/local/info/vcd-info.info /usr/local/info/dir install-info: menu item `vcd-info' already exists, for file `vcdimager' *** Error code 1 I have used pkg_delete to remove the port, but the build process still fails. I have attached a copy of the build process. I am using FreeBSD 5.4 with no special make flags, etc. SEE ALSO: http://www.freebsd.org/cgi/query-pr.cgi?pr=93916 Please test following patch. Sorry, I didn't contact this issue. So I don't know that this patch is OK. Index: files/patch-docs-vcdimager.texi === RCS file: files/patch-docs-vcdimager.texi diff -N files/patch-docs-vcdimager.texi --- /dev/null 1 Jan 1970 00:00:00 - +++ files/patch-docs-vcdimager.texi 11 Mar 2006 01:51:05 - @@ -0,0 +1,10 @@ +--- docs/vcdimager.texi.orig Sat Jun 18 13:11:08 2005 docs/vcdimager.texi Sat Mar 11 10:50:22 2006 +@@ -61,7 +61,6 @@ + @direntry + * VCDImager: (vcdimager). GNU Video CD imaging utilities + * vcdimager: (vcdimager)vcdimager. Video CD simple formatter +-* vcd-info: (vcdimager)vcd-info. Video CD diagnostic tool + * cdxa2mpeg: (vcdimager)cdxa2mpeg. Strip RIFF/CD-XA container + * vcdxminfo: (vcdimager)vcdxminfo. Display MPEG stream properties + * vcdxgen: (vcdimager)vcdxgen. Video CD XML template generator I apologize, but I am a rather new user of FreeBSD. I have no idea what I am suppose to do with the information that you supplied me with. Should I copy that information below the === line and place it some where? Thanks! -- Gerard Seibert [EMAIL PROTECTED] PGP: http://www.seibercom.net/sig/gerard.asc pgpFKcjo5DDfG.pgp Description: PGP signature
Re: Unable to build or update vcdimager
On Sat, 11 Mar 2006 07:34:53 -0500 Gerard Seibert [EMAIL PROTECTED] wrote: I apologize, but I am a rather new user of FreeBSD. I have no idea what I am suppose to do with the information that you supplied me with. Should I copy that information below the === line and place it some where? OK. vcdimager.diff attached my mail put into /usr/ports/multimedia/vcdimager/files/ as patch-vcdimager.texi. Now /usr/ports/multimedia/vcdimager/files is not exists, please mkdir /usr/ports/multimedia/vcdimager before putting file. And make clean make install. This is OK? Index: files/patch-docs-vcdimager.texi === RCS file: files/patch-docs-vcdimager.texi diff -N files/patch-docs-vcdimager.texi --- /dev/null 1 Jan 1970 00:00:00 - +++ files/patch-docs-vcdimager.texi 11 Mar 2006 01:51:05 - @@ -0,0 +1,10 @@ +--- docs/vcdimager.texi.orig Sat Jun 18 13:11:08 2005 docs/vcdimager.texiSat Mar 11 10:50:22 2006 +@@ -61,7 +61,6 @@ + @direntry + * VCDImager: (vcdimager). GNU Video CD imaging utilities + * vcdimager: (vcdimager)vcdimager. Video CD simple formatter +-* vcd-info: (vcdimager)vcd-info. Video CD diagnostic tool + * cdxa2mpeg: (vcdimager)cdxa2mpeg. Strip RIFF/CD-XA container + * vcdxminfo: (vcdimager)vcdxminfo. Display MPEG stream properties + * vcdxgen: (vcdimager)vcdxgen. Video CD XML template generator ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
On Friday 10 March 2006 22:57, Peter wrote: I'm setting up a new server on 6.0 I've been planning for a long time and I am very disappointed with two critical issues. My motherboard is the ASUS K8V-X SE that I chose because it was listed as compatible at the FreeBSD/amd64 Project: http://www.freebsd.org/platforms/amd64/motherboards.html I wonder if going back to 5.4 might help? Onto the problems... 1. I have 4 IDE drives: primary controller: Maxtor 40 GB hd (master) and LG cdrom (slave) secondary controller: Seagate Barracuda 200 GB hd (master) and Seagate Barracuda 300 GB (slave) Problem: The 300 GB drive is unusable. I set it up ok with sysinstall during the installation but the system will not boot properly if it has an entry in /etc/fstab. I get many errors like: ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63 I also get input/output error if I try to examine its label with disklabel. dmesg output is at the end of this post when I booted without fstab line. The strange thing is that the two drives on the secondary controller are so similar. Same manufacturer, same product line, the speeds are the same. Everything is the same except the size. I ran dos-level diagnostics on it and no problems were found. 2. I can't use my USB ports! I get a line like this for each of my ports: uhci0: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] Copyright (c) 1992-2005 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 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: A M I OEMAPIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (2002.58-MHz 686-class CPU) Origin = AuthenticAMD Id = 0xf4a Stepping = 10 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,P GE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow real memory = 536543232 (511 MB) avail memory = 515702784 (491 MB) snip ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a __ You've got a problem alright, and you don't even see it. == The ata driver sets the maximum transfer mode supported by the hardware as default. However the ata driver sometimes warns: ``DMA limited to UDMA33, non-ATA66 cable or device''. This means that the ata driver has detected that the required 80 conductor cable is not present or could not be detected properly, or that one of the devices on the channel only accepts up to UDMA2/ATA33. == You've got your 40GB Maxtor (you've installed FreeBSD on it), an ATA100 device, connected with your CDROM, an ATA33 device. The result is: your boot drive is running at UDMA33 instead of UDMA100. This is not going to work real well, as you can see. Do you really need that 40GB Maxtor? If you do, you're going to have to try adding an ATA controller card into one of your PCI slots and use that to connect your hard drives to. Try removing the 40GB Maxtor and reinstalling FreeBSD on the other two drives. I think that will clear up some problems for you. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Local portaudit server.
David Robillard wrote: We use the port security/portaudit on all of our FreeBSD servers. Currently, every machine has to out on the internet to download the portaudit vulnerability database from the FreeBSD server. If your internal machines need to talk to the web, and you wish to control or restrict that behavior, the canonical solution is to setup a proxy server and firewall which blocks Internet access for everything except the proxy. Since all of the machines are downloading the exact same file, we would like to setup a local portaudit server. This server would fetch the vulnerabilty file and all the rest of our servers would fetch it from the local portaudit server. Has anyone done this setup? Any help/pointers would be great. You could also use rsync to copy /var/db/portaudit from the external server to your internal machines on a daily basis via a cron job. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
[EMAIL PROTECTED] wrote: Erik Trulsson wrote: [ ... ] It is sometimes necessary to reboot with the new kernel to have 'make installworld' work correctly (and the recommended procedure is to reboot into single user mode *before* running 'mergemaster -p' (which in turn is to be done before 'make installworld'). Correct, I forgot since I hadn't been doing it in a while (so much for reading the handbook...). But how do I know when it's necessary? If you know what the differences are between the installed system and what you are updating to, then you can figure out for yourself whether rebooting is necessary. Or should I just reboot twice no matter what? UPDATING is supposed to mention sufficiently important changes that make rebooting necessary, but if you want the process of updating your system to always work properly, you should follow the steps as provided, without taking any shortcuts. But if you get it wrong, boot off the most recent ISO image, and either fix the problem or do a binary upgrade reinstallation... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dd - cloning a disk.
Hi all, Here is a simple (I think!) question for the I/O savy among you: If I had two identical disks, say, 73 GB Seagate 10K SCSIs, one completely operational fully setup FreeBSD with all the trimmings, and the other blank, or perhaps loaded but no longer usable, is 'dd' and appropriate tool to completely clone the Good disk to the not so good disktherefor making the second disk identical to the first? Bootable and all? -Grant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fw: dd - cloning a disk. Second Part!
Sorry, I forgpt to add this, I the answer is yes to the first question (original question), then, what happens if one 'dd's a small, say 36 GM disk to a larger one, say 73 GB. Can the newly made disk be resized so as not to loose 1/2 of it? -GRant - Original Message - From: Grant Peel [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Saturday, March 11, 2006 9:25 AM Subject: dd - cloning a disk. Hi all, Here is a simple (I think!) question for the I/O savy among you: If I had two identical disks, say, 73 GB Seagate 10K SCSIs, one completely operational fully setup FreeBSD with all the trimmings, and the other blank, or perhaps loaded but no longer usable, is 'dd' and appropriate tool to completely clone the Good disk to the not so good disktherefor making the second disk identical to the first? Bootable and all? -Grant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
At 14:17 07.03.2006, Stijn Hoop wrote: On Mon, Mar 06, 2006 at 05:29:36PM +0100, Kristian Vaaf wrote: At 22:08 04.03.2006, Stijn Hoop wrote: On Sat, Mar 04, 2006 at 05:45:29PM +0100, Kristian Vaaf wrote: At 12:05 03.03.2006, Stijn Hoop wrote: On Fri, Mar 03, 2006 at 11:58:37AM +0100, Kristian Vaaf wrote: I run the script to save time. Basically I'd run the exact same chain of commands otherwise. You're missing the point: you'd run the exact same chain of commands -- _if everything goes according to plan_ -- What this list has been telling you is that it sometimes doesn't work like anyone expects to, and you need to make an informed decision about the next command to enter instead of having the script proceed. Whether I have my commands in my script or in my head doesn't make any difference. Yes I do read UPDATING and if I notice any changes they will be applied respectively. The moment one step does NOT work in the command sequence, you need to alter your next move. No script can be prepared for all the things that can happen. Which is why everyone is recommending you NOT to run things in a script. I understand what you mean. No you apparently do not. What I'm saying is, I do not expect a script to be prepared. Good. I am the one reading UPDATING and modifying the script if there is a change. Manually. Whether I write the sequence in the command line or into a script that I execute doesn't make no difference! It doesn't, but you're missing the point again. Let's say for the sake of argument that your computer's internal clock broke down. FreeBSD will keep the time just fine so long as your machine has power, so you don't notice anything. Now you run your script. It will go through the stages of building world, building kernel, installing the kernel, and then rebooting. At this point your computer loses power for a few seconds and *presto* your clock is set to 1970. Now, your script proceeds after the reboot with the new kernel. Because your clock is WAY off, 'make installworld' will complain (well it could work, but let's assume it doesn't). Your script however, doesn't see this. It therefore proceeds with mergemaster, and rebooting again. Now you're running a new kernel with older binaries, that may or may not work. If this had happened to me [1], I would have stopped at the point where 'make installworld' throws an error, and wondered what went wrong. I could backout my kernel install, reboot into my working configuration, and figure things out before it all got out of hand (edited configuration files etc). And this is just ONE example of a admittedly minor thing that can go wrong. This is why you should not automate the installation yourself. What do you mean, mailing list in the loop? I mean that you should keep CC'ing [EMAIL PROTECTED] so that other who wonder why automating this is not a good idea can search the archives to find out my answer to you. Hartelijk dank, Stijn! Geen probleem. --Stijn -- Thus again, we have succesfully proven that I cannot read minds. It doesn't help. Almost all you ever get is This mind intentionally left blank. -- Steve VanDevender, alt.sysadmin.recovery Interesting statement. I'd say that, however, is kinda like the chance of getting shot by African guerilla when you live on the North Pole. Ain't gonna happen :) So, to everyone who has tried helping me: I guess there is no solution to this? FreeBSD will NOT successfully make my world no matter what I do. I've tried all the sequences. Please stop flaming me for using the wrong sequence. I've used ALL sequences. So I know that's not the problem. But then, what can it be? Is it time for the list to admit there's nothing we can do? All the best, Vaaf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
On 2006-03-11 06:42, Peter [EMAIL PROTECTED] wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: On Fri, Mar 10, 2006 at 11:57:59PM -0500, Peter wrote: Onto the problems... You might have more luck if you also talk to [EMAIL PROTECTED] I'm not sure who this is but I'll look into it. 2. I can't use my USB ports! I get a line like this for each of my ports: uhci0: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] OK, but what is the problem? When something is plugged into a port and the system is powered up it will freeze at the POST level with no errors. It just sits there. At POST time, FreeBSD hasn't loaded at all. If you are having problems at that stage, it looks like a motherboard or BIOS problem :-( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange error code 1 when compile kernel on 6.1-PRERELEASE
Dikshie [EMAIL PROTECTED] writes: I got following strange error when compiled kernel: === aic7xxx/ahd (depend) @ - /usr/src/sys machine - /usr/src/sys/i386/include ( cd /usr/src/sys/modules/aic7xxx/ahd/../aicasm; make aicasm; ) cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/m odules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm -g -c /usr/src/sys/modules/ai c7xxx/aicasm/../../../dev/aic7xxx/aicasm/aicasm.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/m odules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm -g -c /usr/src/sys/modules/ai c7xxx/aicasm/../../../dev/aic7xxx/aicasm/aicasm_symbol.c yacc -b aicasm_gram -d -o aicasm_gram.c /usr/src/sys/modules/aic7xxx/aicasm/../ ../../dev/aic7xxx/aicasm/aicasm_gram.y cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/m odules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm -g -c aicasm_gram.c yacc -b aicasm_macro_gram -p mm -d -o aicasm_macro_gram.c /usr/src/sys/modules/a ic7xxx/aicasm/../../../dev/aic7xxx/aicasm/aicasm_macro_gram.y cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/m odules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm -g -c aicasm_macro_gram.c lex -t /usr/src/sys/modules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm/aicasm_ scan.l aicasm_scan.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/m odules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm -g -c aicasm_scan.c lex -t -Pmm /usr/src/sys/modules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm/aic asm_macro_scan.l aicasm_macro_scan.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/m odules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm -g -c aicasm_macro_scan.c cc -O2 -fno-strict-aliasing -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/m odules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm -g -o aicasm aicasm.o aicasm _symbol.o aicasm_gram.o aicasm_macro_gram.o aicasm_scan.o aicasm_macro_scan.o -l l /usr/obj/usr/src/tmp/usr/bin/ld: cannot find -ll *** Error code 1 Stop in /usr/src/sys/modules/aic7xxx/aicasm. *** Error code 1 Stop in /usr/src/sys/modules/aic7xxx/ahd. *** Error code 1 Stop in /usr/src/sys/modules/aic7xxx. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/soi. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. vic-rat# any solutions ? Hard to say. It actually seems to be building a module at the point it fails. Have you done a full buildworld beforehand? Have you successfully built at all since downloading that set of sources? How did you install your sources? If those sources never built successfully, have you tried another update in case it was a transient problems in the codebase? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fw: dd - cloning a disk. Second Part!
Grant Peel wrote: I the answer is yes to the first question (original question), then, what happens if one 'dd's a small, say 36 GM disk to a larger one, say 73 GB. Can the newly made disk be resized so as not to loose 1/2 of it? If you partition the bigger disk into two fdisk partitions, one of which is exactly the size of your original disk, you could use dd to copy the contents of the BSD slice from one disk to the other, and then use newfs to create a separate filesystem on the second fdisk partition. However, if you want to use the entire 73GB space at once, use dump and restore to copy the data instead. There's detailed documentation on this on the FreeBSD website... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem running Adobe acroread7
Donald T Hayford [EMAIL PROTECTED] writes: I get the following error message when I try to open a file in Adobe acroread7, after which acroread quits: (acroread:7605): Gtk-WARNING **: Could not find the icon 'gnome-fs-home'. The 'hicolor' theme was not found either, perhaps you need to install it. You can get a copy from: http://freedesktop.org/Software/icon-theme/releases When I run pkg_info, I find the following items installed (among many others): gtk-1.2.10_13 Gimp Toolkit for X11 GUI (previous stable version) gtk-2.8.12 Gimp Toolkit for X11 GUI (current stable version) hicolor-icon-theme-0.5 A high-color icon theme shell from the FreeDesktop project I couldn't find anything on 'gnome-fs-home'. I am running the KDE desktop, not gnome. Are you running acroread from a command line? It doesn't require any FreeBSD Gnome or gtk support; it does the linux-gtk2 and linux-pango ports, but those are direct dependencies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On 2006-03-11 12:28, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Kris Kennaway wrote: The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. Dear Kris I have a few questions related to this error message ERROR: Required audit group is missing, see /usr/src/UPDATING I know that updating requires the mergemaster steps because I read the handbook. But I don't understand why this message tells me to look in that file, when there's nothing about that in it. Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? By definition, yes. Or is there a file which describes how I can manually insert needed groups and users when I mess up mergemaster runs? The documented procedure in `/usr/src/UPDATING', as Kris has already mentioned includes a run of mergemaster with the -p option. Copying from my CURRENT's version of `UPDATING': % To rebuild everything and install it on the current system. % --- % # Note: sometimes if you are running current you gotta do more than % # is listed here if you are upgrading from a really old current. % % make sure you have good level 0 dumps % make buildworld % make kernel KERNCONF=YOUR_KERNEL_HERE % [1] % reboot in single user [3] % mergemaster -p [5] % make installworld % make delete-old % mergemaster [4] % reboot % % [1] If you have third party modules, such as vmware, you % should disable them at this point so they don't crash your % system on reboot. % % [3] From the bootblocks, boot -s, and then do % fsck -p % mount -u / % mount -a % cd src % adjkerntz -i# if CMOS is wall time % Also, when doing a major release upgrade, it is required that % you boot into single user mode to do the installworld. % % [4] Note: This step is non-optional. Failure to do this step % can result in a significant reduction in the functionality of the % system. Attempting to do it by hand is not recommended and those % that pursue this avenue should read this file carefully, as well % as the archives of freebsd-current and freebsd-hackers mailing lists % for potential gotchas. % % [5] Usually this step is a noop. However, from time to time % you may need to do this if you get unknown user in the following % step. It never hurts to do it all the time. You may need to % install a new mergemaster (cd src/usr.sbin/mergemaster make % install) after the buildworld before this step if you last updated % from current before 20020224 or from -stable before 20020408. Read these instructions. Then read them again. Then throw away that script and start over :) And finally, is it really necessary to reboot after 'mergemaster -p'? No. `UPDATING' mentions running `mergemaster -p' *AFTER* rebooting into single user mode, not *BEFORE*. Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) You'll start booting into single user mode again, when you try to run `make installworld' with an old kernel and have it blow up, leaving you with a half installed base system and a lot of `interesting' work in front of you. Or when you install everything without a reboot, replace your old working userland and then find out that your new kernel is unbootable and your new userland is unusable without a new kernel. Booting into single user mode guarantees that you have verified at least once that the new kernel works. There's a very good reason why this is recommended :) - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
Vaaf wrote: [ ... ] So, to everyone who has tried helping me: I guess there is no solution to this? I would perform a binary reinstallation of the OS from a known-good ISO image, and retry from a clean environment. Use script or nohup to track the commands you run and their exact output if you encounter problems from a clean start. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
On 2006-03-11 15:30, Vaaf [EMAIL PROTECTED] wrote: So, to everyone who has tried helping me: I guess there is no solution to this? FreeBSD will NOT successfully make my world no matter what I do. I've tried all the sequences. Please stop flaming me for using the wrong sequence. I've used ALL sequences. So I know that's not the problem. You haven't replied very usefully to some of my suggestions, at least. One of them was that with all these scripted trickery you had been using, your /usr/include headers may be out of touch with reality. # Date: Mon, 6 Mar 2006 18:52:16 +0200 # From: Giorgos Keramidas [EMAIL PROTECTED] # Subject: Re: Haven't been able to make world in about a year # To: Kristian Vaaf [EMAIL PROTECTED] # Cc: Donald J. O'Neill [EMAIL PROTECTED], # freebsd-questions@freebsd.org # # [...] # # -- # stage 2.3: build tools # -- # cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj INSTALL=sh # /usr/src/tools/install.sh # # [...] # # It looks like your system headers may have serious problems. Is this # system a clean installation of 5.4-RELEASE or one where you may have # updated the system headers manually at some time? Any idea what a possible useful answer to that question is? But then, what can it be? Is it time for the list to admit there's nothing we can do? No. It's time for you to start actually taking some of the suggestions that you have missed, *and* replying to the questions that have been unanswered (some time for weeks now), though :) It is highly unlikely that an upgrade process that works for hundreds of systems around the world, even through a simple serial console connection, somehow has decided to mysteriously fail only for you. It is obvious that you are doing something wrong (or that you have done something wrong in the past, and are now seeing the consequences). We just have to find out what that is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fw: dd - cloning a disk. Second Part!
Thanks Chuck, I was kinda thinkning Dump and Restore might be the way to go. I have never tried to use it to make a bootable disk though...does it do it automaticly or should I read something? (What)? Thanks again, -Grant - Original Message - From: Chuck Swiger [EMAIL PROTECTED] To: Grant Peel [EMAIL PROTECTED]; freebsd-questions freebsd-questions@freebsd.org Sent: Saturday, March 11, 2006 9:39 AM Subject: Re: Fw: dd - cloning a disk. Second Part! Grant Peel wrote: I the answer is yes to the first question (original question), then, what happens if one 'dd's a small, say 36 GM disk to a larger one, say 73 GB. Can the newly made disk be resized so as not to loose 1/2 of it? If you partition the bigger disk into two fdisk partitions, one of which is exactly the size of your original disk, you could use dd to copy the contents of the BSD slice from one disk to the other, and then use newfs to create a separate filesystem on the second fdisk partition. However, if you want to use the entire 73GB space at once, use dump and restore to copy the data instead. There's detailed documentation on this on the FreeBSD website... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fw: dd - cloning a disk. Second Part!
Grant Peel wrote: I was kinda thinkning Dump and Restore might be the way to go. I have never tried to use it to make a bootable disk though...does it do it automaticly or should I read something? (What)? See the nice FAQ entry: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NEW-HUGE-DISK -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Haven't been able to make world in about a year
Can you think about giving root access to one of us? I would be glad to try and diagnose your issue, 'cuz it looks like a brick wall. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dd - cloning a disk.
On 3/11/06, Grant Peel [EMAIL PROTECTED] wrote: Hi all, Here is a simple (I think!) question for the I/O savy among you: If I had two identical disks, say, 73 GB Seagate 10K SCSIs, one completely operational fully setup FreeBSD with all the trimmings, and the other blank, or perhaps loaded but no longer usable, is 'dd' and appropriate tool to completely clone the Good disk to the not so good disktherefor making the second disk identical to the first? Bootable and all? It is, with a few 'buts'. Firstly, the source should be mounted read-only. Secondly, you should copy the drive device itself (ie da0 to da1) instead of its partitions (ie da0c). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GNOME Gdk
Hello, the last day i've installed gnome2, it result very very slow .. gedit, to example, open after 32seconds and put that error: [EMAIL PROTECTED] ~]$ gedit (gedit:50388): Gdk-WARNING **: shmget failed: error 28 (No space left on device) or .. (gedit:23354): Gdk-WARNING **: shmget failed: error 12 (Cannot allocate memory) All application on gnome make that error .. on fluxbox, the gnome application (gedit) open without error but very slowly .. after 20/30 seconds .. Totem to example: [08:08:26] Shocker : [EMAIL PROTECTED] ~]$ totem (totem:23353): Gdk-WARNING **: shmget failed: error 12 (Cannot allocate memory) The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadShmSeg (invalid shared segment parameter)'. (Details: serial 44 error_code 164 request_code 146 minor_code 2) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) [EMAIL PROTECTED] ~]$ What can I do ? .. Thanks a lot and sorry for my terrible english .. :) _ 250MB per la tua casella di posta http://www.msn.it/hotmail/minisite_10 Trova immediatamente qualsiasi tipo di file. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
Giorgos Keramidas wrote: No. `UPDATING' mentions running `mergemaster -p' *AFTER* rebooting into single user mode, not *BEFORE*. Yes, sorry, I'm mixing things up. Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) You'll start booting into single user mode again, when you try to run `make installworld' with an old kernel and have it blow up, leaving you with a half installed base system and a lot of `interesting' work in front of you. Or when you install everything without a reboot, replace your old working userland and then find out that your new kernel is unbootable and your new userland is unusable without a new kernel. Booting into single user mode guarantees that you have verified at least once that the new kernel works. There's a very good reason why this is recommended :) You're right, the time saved with one less reboot is not worth the risk of salvaging a half-updated system. Thanks for the clarification. lars. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SV: freebsd-questions Digest, Vol 126, Issue 17
Hi all, After doing a svsup yesterday and doing a 'make -j4 buildworld' i've (my script that is) tried to proceed with a 'make installworld'. But it failed : www# make installworld ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have checked /usr/src/UPDATING but there isn't any entry new about new groups and 'grep -w audit /etc/group' does not show any audit-group present. I also did a 'rm -rf /usr/obj/* ' and ran 'make -j4 buildworld' again, which endend without errors but the following 'make installworld' stops with the mentioned error again. I am using the '*default release=cvs tag=RELENG_6' in the supfile and am running 6.1-PRERELEASE now. What am I doing wrong ? Any clues are welcome. Beni. Hi Beni ! Why dont you try: -- Start with downloading latest sourcecode - cvsup -g -L 2 standard-supfile cvsup -g -L 2 ports-supfile 1. cd /usr/src 2. make buildworld make buildkernel KERNCONF=kernelname make installkernel KERNCONF=kernelname reboot 3. boot in single user mode 4. fsck -p 5. mount -u / 6. mount -a 7. cd /usr/src 8. adjkerntz -i 9. mergemaster -p 10. make installworld 11. mergemaster 12. shutdown -r now Yours //Johan FreeBSD 7.0-CURRENT #11: Thu Feb 9 20:26:41 CET 2006 -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Xorg config problems
I recycle old P2 class machines for a set of applications at work. I switched to Xorg for these machines a while back, and was pleased to find that I did not have to create a config file for Xorg as it was able to autodetect all the correct stuff. Today, though I ran up on 2 machines that are the older end of the spectrum of machines that I use for this, and for some reason this does not seem to be working. Here's the Xorg logfiel from oen of these amchines: X Window System Version 6.9.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: FreeBSD 6.1 i386 [ELF] Current Operating System: FreeBSD pulpsysal.fas.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Sat Mar 4 13:00:51 EST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 06 March 2006 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sat Mar 11 10:55:35 2006 (EE) Unable to locate/open config file (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.8 X.Org XInput driver : 0.5 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on freebsd (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.so (II) Module bitmap: vendor=X.Org Foundation compiled for 6.9.0, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1237 card , rev 02 class 06,00,00 hdr 00 (II) PCI: 00:04:0: chip 8086,7000 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:04:1: chip 8086,7010 card , rev 00 class 01,01,80 hdr 00 (II) PCI: 00:06:0: chip 8086,1229 card 8086,0001 rev 02 class 02,00,00 hdr 00 (II) PCI: 00:0d:0: chip 1013,00b8 card ,00ff rev 45 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:4:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:13:0) Cirrus Logic GD 5446 rev 69, Mem @ 0xfc00/25, 0xfecff000/12 xf86AutoConfig: Primary PCI is 0:13:0 Running /usr/X11R6/bin/getconfig -X 6090 -I /etc/X11,/usr/X11R6/etc/X11,/usr/X11R6/lib/modules,/usr/X11R6/lib/X11/getconfig -v 0x1013 -d 0x00b8 -r 0x45 -s 0x -b 0x00ff -c 0x0300 New driver is cirrus (==) Using default built-in configuration (53 lines) (==) --- Start of built-in configuration --- Section Module Loadextmod Loaddbe Loadglx Loadfreetype EndSection Section Monitor Identifier Builtin Default Monitor Option TargetRefresh 75.0 EndSection Section Device Identifier Builtin Default cirrus Device 0 Driver cirrus EndSection Section Screen Identifier Builtin Default cirrus Screen 0 Device Builtin Default cirrus Device 0 Monitor Builtin Default Monitor EndSection Section Device Identifier Builtin Default fbdev Device 0 Driver fbdev EndSection Section Screen Identifier Builtin Default fbdev Screen 0 Device Builtin Default fbdev Device 0 Monitor Builtin Default Monitor EndSection Section Device Identifier Builtin Default vesa Device 0 Driver vesa EndSection Section Screen Identifier Builtin Default vesa Screen 0 Device Builtin Default vesa Device 0 Monitor Builtin Default Monitor EndSection Section Device Identifier
Re: Epson C66 doesn't work with Epson drivers (print/pips-sc65_66s port)
Chris Maness wrote: I originally posted this in -ports but despite some suggestions it is still a problem. Hopefully someone here may be able to shed some light? I'm (now) running *FreeBSD* postie 4.10-RELEASE *FreeBSD* 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004 r... http://groups.google.com/groups/unlock?msg=57e1002676b041a9hl=en_done=/group/lucky.freebsd.questions/browse_thread/thread/c39a4602aa4702d3/57e1002676b041a9%3Flnk%3Dst%26q%3Dpips%2Bfreebsd%2Bcannot%2Bcommunicate%2Bwith%2Bprinter%26rnum%3D1%26hl%3Den@perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 I got my Epson C66 Photo up and running using CUPS, ESP Ghostscript, and the gimp-print drivers (using C64 since C66 isn't listed explicitly). It all works and I exported it through Samba and printed successfully from a Windows box :-) Then I found that the Epson KOWA drivers were in the ports - print/*pips*-sc65_66s - so installed them as they are better drivers, changed the configuration in CUPS as per readme-sc65_66s-cups but the *printer* wouldn't work. I deleted the *printer* and re-added it from scratch but still it won't work. When I click Print Test Page in CUPS the *printer* head shuffles which shows there is some communication with the *printer* but it just shows Processing... for a while then the job appears under Completed Jobs with a status of aborted. I've set CUPS to log at debug2 level but that doesn't show anything useful (to me anyway): D [06/Sep/2004:20:08:51 +0100] [Job 32] cups-ppd = 0x83f5400 D [06/Sep/2004:20:08:51 +0100] [Job 32] cups-ppd-flip_duplex = 0 D [06/Sep/2004:20:08:51 +0100] [Job 32] width = 827, height = 1039 D [06/Sep/2004:20:08:51 +0100] [Job 32] PageSize = [ 612 792 ], HWResolution = [ 100 100 ] D [06/Sep/2004:20:08:51 +0100] [Job 32] HWMargins = [ 8.400 35.400 8.400 8.400 ] D [06/Sep/2004:20:08:51 +0100] [Job 32] matrix = [ 1.389 0.000 0.000 -1.389 -11.667 1088.333 ] d [06/Sep/2004:20:08:51 +0100] PID 689 exited with no errors. d [06/Sep/2004:20:08:51 +0100] PID 690 exited with no errors. D [06/Sep/2004:20:08:51 +0100] UpdateJob: job 32, file 0 is complete. d [06/Sep/2004:20:08:51 +0100] UpdateJob: Removing fd 9 from InputSet... D [06/Sep/2004:20:08:51 +0100] CancelJob: id = 32 D [06/Sep/2004:20:08:51 +0100] StopJob: id = 32, force = 0 D [06/Sep/2004:20:08:51 +0100] StopJob: *printer* state is 3 d [06/Sep/2004:20:08:51 +0100] StopJob: Freeing status buffer... d [06/Sep/2004:20:08:51 +0100] SaveJob: Closing file 7... d [06/Sep/2004:20:08:51 +0100] SaveJob: Closing file 7... The ekpstm program (Status Monitor) shows a Communication Error and the *pips*-sc65_66s program shows *Cannot **communicate* with a *printer* on the Utility tab. Can anyone offer any help/advice on this please? BTW, the port appears to be missing a build dependency for autoconf253 - my build stopped part way through as it couldn't find /usr/local/bin/autoconf253. Thanks. Regards, Mark Did you every get this resolved? (I know this post was very old) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg config problems
stan wrote: I recycle old P2 class machines for a set of applications at work. I switched to Xorg for these machines a while back, and was pleased to find that I did not have to create a config file for Xorg as it was able to autodetect all the correct stuff. Today, though I ran up on 2 machines that are the older end of the spectrum of machines that I use for this, and for some reason this does not seem to be working. Here's the Xorg logfiel from oen of these amchines: *SNIP* My guess is thta the graphics cards on these machiens ahve too lilltle memory to work with the default set of assumptions on these machines. However I really don't need very hi-res displays on these amchines. Any sugestions as to how to get Xorg to work with these machines? Try doing an X -configure, which will write out an xorg.conf file for you. You can then tweak the settings to something that works. It looks like, from the log you sent, that the hsync refresh rate that Xorg is guessing is wrong. You might be able to google on your video card and find the right setting. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sending large amount of data securely
Dave wrote: Hi, Unfortunately, the box doesn't have the room on it to make the tar backup, so i'd have to tar over ssh, then untar on the other box. Is this doable? Thanks. Dave. - Original Message - From: Micah [EMAIL PROTECTED] To: Dave [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Wednesday, March 08, 2006 11:49 AM Subject: Re: sending large amount of data securely Dave wrote: Hello, I've got two freebsd6 boxes on one i have a large collection of files, like about 3.5 gb worth, that i want to send securely to the other box. I've tried: scp -24Cpr to do it, it transfered 1gb of data then quit. I'm suspecting it didn't get the sym links if any in this data. Any suggestions appreciated. Thanks. Dave. Some options are to tar then scp, or to use rsync+ssh. I've transfered 6gb tar backups via scp in the past with no problems. HTH, Micah Yes, you can direct the output of tar into ssh and have that output into tar on the other end. Google for specifics, but a the simple search terms tar over ssh turned up this thread: http://lists.debian.org/debian-user/2003/03/msg05757.html P.S. Don't forget to CC the list. Someone there surely could've answered your question in a more timely fashion that I could this last week. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Trouble with if_bridge and wlan nic in infrastructure mode
I have a problem with if_bridge if one of the members is a wlan nic in infrastructure mode. Bridges between the following device combinations work: em0 and tap0; em0 and wi0 in hostap mode; em0 and ath0 in hostap mode; rl0 and re0 (different system); Bridges between the following don't: em0 and ndis0 in infrastructure mode; em0 and wi0 in infrastructure mode; em0 and ath0 infrastructure mode; tap0 and ndis0 in infrastructure mode; My bridge is a ThinkPad R51 running FreeBSD 6.1-PRERELEASE #11: Fri Mar 10 13:05:07 CET 2006. PF is disabled and all net.link.bridge sysctls are set to 0. I tested two Access Points for the infrastructure mode, a Netgear WGT624 and another Laptop running Anonym.OS. The ThinkPad can ping the AP and the system behind em0 (or tap0), but the system behind em0 (or tap0) can't reach the AP and can't be reached by the AP either. Both systems between the bridge can ping the bridge itself. If I run tcpdump on the members of the bridge I can see arp requests (who has IP foo tell bar) on both members, but answers coming in on em0 don't appear on the wlan nic in infrastructure mode and the wlan nic doesn't get any answers which could be bridged to em0 at all. I'm under the impression that even the arp requests coming in on em0 and shown on the wlan nic in infrastructure mode aren't send out. At least I can't see them on the AP running Anonym.OS. Arp requests made my the AP are bridged and answered by the system behind em0, but the answers itself aren't bridged. man if_bridge's wi0 example assumes the 802.11 interface is in ad-hoc mode but it doesn't say wlan bridging would be limited to ad-hoc and hostap mode. I worked around the problem by using NAT, but I'm still interested if anybody is using an if_bridge member in infrastructure mode or if there's a reason why it shouldn't work. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: Xorg config problems
stan wrote: I recycle old P2 class machines for a set of applications at work. I switched to Xorg for these machines a while back, and was pleased to find that I did not have to create a config file for Xorg as it was able to autodetect all the correct stuff. Today, though I ran up on 2 machines that are the older end of the spectrum of machines that I use for this, and for some reason this does not seem to be working. Here's the Xorg logfiel from oen of these amchines: snipped (WW) CIRRUS(0): Mode pool is empty (EE) CIRRUS(0): No valid modes found (II) UnloadModule: cirrus (II) UnloadModule: ddc (II) Unloading /usr/X11R6/lib/modules/libddc.so (II) UnloadModule: i2c (II) Unloading /usr/X11R6/lib/modules/libi2c.so (II) UnloadModule: int10 (II) Unloading /usr/X11R6/lib/modules/libint10.so (II) UnloadModule: vgahw (II) Unloading /usr/X11R6/lib/modules/libvgahw.so (II) UnloadModule: cirrus_alpine (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. My guess is thta the graphics cards on these machiens ahve too lilltle memory to work with the default set of assumptions on these machines. However I really don't need very hi-res displays on these amchines. Any sugestions as to how to get Xorg to work with these machines? Hmm. Looks like you'll need to make some spec changes in a config file. Generate one with `Xorg -configure` ... it won't actually run X, but will test and tell you where it placed the file. Try X again, and make sure it's finding said file (check the output on ttyv0 or wherever ... log file will say also IIRC). You'll then need to tweak Refresh rates and Sync for your monitors and see what happens. Please include standard disclaimers, waivers of damages and remember YMMV and all that. ;-) HTH, Kevin Kinsey -- The meta-Turing test counts a thing as intelligent if it seeks to devise and apply Turing tests to objects of its own creation. -- Lew Mammel, Jr. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg config problems
On 3/11/06, stan [EMAIL PROTECTED] wrote: I recycle old P2 class machines for a set of applications at work. I switched to Xorg for these machines a while back, and was pleased to find that I did not have to create a config file for Xorg as it was able to autodetect all the correct stuff. Today, though I ran up on 2 machines that are the older end of the spectrum of machines that I use for this, and for some reason this does not seem to be working. snip (WW) CIRRUS(0): Mode pool is empty (EE) CIRRUS(0): No valid modes found Usually this means you need to specify your horizontal and vertical sync and refresh rates. I would run: X -configure cp xorg.conf.new /etc/X11/xorg.conf then add some lines like: Section Monitor Identifier Barfy HorizSync 31-92 # Taken from my monitor, VertRefresh 55-160 # Don't use these values. EndSection and change Section Screen Monitor Barfy Frequently on older cards the monitor's capabilities cannot be detected which can lead to very conservative defaults which can lead to no valid modes. There is a database of these values (I've found it to be accurate, if incomplete): http://www.monitorworld.com/monitors_home.html -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Spamd keeps falling over
I have had spamd die about 3 times in the last couple days, this is what I saw in the logs this morning: Mar 11 06:00:37 mail spamd[28178]: prefork: ordered child to accept, but child reported state '1' at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Spam dForkScaling.pm line 390 What does it mean? Can I get some suggestions on an application that will monitor this process and if it dies restart it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[SOLVED] Re: Arplookup strange messages
Hi Erik and List, yesterday my calbe modem went down for a while due to a problem on the line. This also is the reason why I couldn't connect to the machine ;-) My external interface (rl0) recieves the IP address from the cable modem via DHCP, and when the line is down the modem assigns a private IP to the machine. In /var/log/messages, the logs of the new DHCP lease are followed from the ones of arplookup: Mar 10 15:19:24 gahr dhclient: New IP Address (rl0): 192.168.100.10 Mar 10 15:19:24 gahr dhclient: New Subnet Mask (rl0): 255.255.255.0 Mar 10 15:19:24 gahr dhclient: New Broadcast Address (rl0): 192.168.100.255 Mar 10 15:19:24 gahr dhclient: New Routers (rl0): 192.168.100.1 Mar 10 15:19:53 gahr kernel: arplookup 0.0.0.0 failed: host is not on local network Mar 10 15:20:24 gahr kernel: arplookup 0.0.0.0 failed: host is not on local network So the problem only raises when the cable modem is down, and when line failures happen, the arplookup messages really aren't the things I worry about.. Thank you! Best Regards, On 3/11/06, Erik Nørgaard [EMAIL PROTECTED] wrote: Pietro Cerutti wrote: Hi list, today in the daily security report (periodic) of a i386 machine there is this message repeated about 30 times: +arplookup 0.0.0.0 failed: host is not on local network From rfc 3330: 0.0.0.0/8 - Addresses in this block refer to source hosts on this network. Address 0.0.0.0/32 may be used as a source address for this host on this network; other addresses within 0.0.0.0/8 may be used to refer to specified hosts on this network [RFC1700, page 4]. I think in packet filter you can specify 0/32 and it will automatically be replaced by the ip on the relevant interface, this is useful when you have nics configured with dhcp. However, not all programs support this and will instead try to make an arplookup which is bound to fail. So first question is, what program causes this arplookup? - Do you in your firewall rules specify 0/32? - Do you have correctly set antispoofing? If your firewall does not drop packets from 0/8 then it may try to send a response to the invalid ip. - Do you have dhcp configured somewhere for some host? IIRC dhcp requests are sent with source 0/32 to destination 255.255.255.255/0 (rfc 2131). Your firewall may (it shouldn't, but check anyway) incorrectly try to route it if you don't have the antispoofing setup. If dhcp configuration fails, sometimes the interface gets assigned the address 0/32 unless some fallback have been configured. This could be a client on your network that is misconfigured. The machine is the router (ipnat) and firewall (ipfilter) for a small home network. It runs postfix, sshd and nfsd. My guess is to take a look at your firewall rules and check if there are any misbehaving dhcp clients. Since I'm away from home now, I can't sit in front of it and check what's wrong. Furthermore, it seams that the machine is not accepting ssh logins anymore, after those strange messages. Well, then you have a problem correcting this - maybe someone can reboot the machine for you? Hope this helps, Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 -- Pietro Cerutti [EMAIL PROTECTED] Non lasciar calpestare i TUOI diritti! Don't let 'em take YOUR rights! NO al Trusted Computing! Say NO to Trusted Computing! www.no1984.org www.againsttcpa.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Spamd keeps falling over
Derrick try asking on users@spamassassin.apache.org, theres a few other people seeing something similar wuth Perl 5.8.8 -- Martin On 3/11/06, Derrick MacPherson [EMAIL PROTECTED] wrote: I have had spamd die about 3 times in the last couple days, this is what I saw in the logs this morning: Mar 11 06:00:37 mail spamd[28178]: prefork: ordered child to accept, but child reported state '1' at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Spam dForkScaling.pm line 390 What does it mean? Can I get some suggestions on an application that will monitor this process and if it dies restart it? ___ 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: Disappointed with version 6.0
On Sat, Mar 11, 2006 at 06:42:49AM -0500, Peter wrote: 2. I can't use my USB ports! I get a line like this for each of my ports: uhci0: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] OK, but what is the problem? When something is plugged into a port and the system is powered up it will freeze at the POST level with no errors. It just sits there. OK, so this is a problem with your BIOS or hardware itself, since FreeBSD isn't running during POST. Kris pgppvtmX3PFUG.pgp Description: PGP signature
GNOME help PLEASE
while i'm not regular user of gnome, i have to configure it for users. the problem is how to make configuration template default for every new user. i tried to copy whole or partial user directory to other users+chown but no success. always something crashes or doesn't work. only copying desktop icons ends in full success. any idea, help or RTFM how to modify/make default configuration for many gnome users on same machine? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
--- Donald J. O'Neill [EMAIL PROTECTED] wrote: [...] ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a __ You've got a problem alright, and you don't even see it. == The ata driver sets the maximum transfer mode supported by the hardware as default. However the ata driver sometimes warns: ``DMA limited to UDMA33, non-ATA66 cable or device''. This means that the ata driver has detected that the required 80 conductor cable is not present or could not be detected properly, or that one of the devices on the channel only accepts up to UDMA2/ATA33. == You've got your 40GB Maxtor (you've installed FreeBSD on it), an ATA100 device, connected with your CDROM, an ATA33 device. The result is: your boot drive is running at UDMA33 instead of UDMA100. This is not going to work real well, as you can see. Do you really need that 40GB Maxtor? If you do, you're going to have to try adding an ATA controller card into one of your PCI slots and use that to connect your hard drives to. Try removing the 40GB Maxtor and reinstalling FreeBSD on the other two drives. I think that will clear up some problems for you. Can this be causing the problem with the 300 GB drive on the other controller? What I don't understand is why is there a problem only with one drive on the secondary controller? As for the cdrom, how else can it be connected? It will ALWAYS be slower than the hard disk. Or do you mean it should just not be connected to the boot drive? I never had such a problem before. I'll move around my drives and see what happens. Thanks for your help. -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make installworld fails
On Sat, Mar 11, 2006 at 12:28:32PM +0100, [EMAIL PROTECTED] wrote: Kris Kennaway wrote: The error message is wrong. Actually it's correct, just a bit unclear. UPDATING includes the complete procedure you should always follow when building world. It includes a 'mergemaster -p' step, precisely for the purpose of adding new users and groups when they appear. Dear Kris I have a few questions related to this error message ERROR: Required audit group is missing, see /usr/src/UPDATING I know that updating requires the mergemaster steps because I read the handbook. But I don't understand why this message tells me to look in that file, when there's nothing about that in it. Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Yes. -- Updating Information for FreeBSD STABLE users This file is maintained and copyrighted by M. Warner Losh [EMAIL PROTECTED]. See end of file for further details. For commonly done items, please see the COMMON ITEMS: section later in the file. [...] [...special items applicable to special situations...] COMMON ITEMS: General Notes - ... To build a kernel - ... To rebuild everything and install it on the current system. --- # Note: sometimes if you are running current you gotta do more than # is listed here if you are upgrading from a really old current. make sure you have good level 0 dumps make buildworld make kernel KERNCONF=YOUR_KERNEL_HERE [1] reboot in single user [3] mergemaster -p [5] here make installworld make delete-old mergemaster [4] reboot Or is there a file which describes how I can manually insert needed groups and users when I mess up mergemaster runs? I think you can just rerun mergemaster -p. If you mess up a full mergemaster, you can use mergemaster -s to repair it. And finally, is it really necessary to reboot after 'mergemaster -p'? Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) No, it just adds the users/groups, and rebooting won't gain you anything. Kris pgpx4Q68ts7B3.pgp Description: PGP signature
Re: make installworld fails
On Sat, Mar 11, 2006 at 01:04:33PM +0100, [EMAIL PROTECTED] wrote: Erik Trulsson wrote: Is /usr/src/UPDATING synonymous to 'the correct updating procedure'? Yes, /usr/src/UPDATING does describe the correct updating procedure. If you follow that procedure you should not have any problems with missing groups. Look under COMMON ITEMS at the end of /usr/src/UPDATING. Right, thanks. And finally, is it really necessary to reboot after 'mergemaster -p'? Lately I've skipped that step with no adverse side-effects, saves me one reboot :-) It is sometimes necessary to reboot with the new kernel to have 'make installworld' work correctly (and the recommended procedure is to reboot into single user mode *before* running 'mergemaster -p' (which in turn is to be done before 'make installworld'). Correct, I forgot since I hadn't been doing it in a while (so much for reading the handbook...). But how do I know when it's necessary? Or should I just reboot twice no matter what? *Every* *single* *step* in that list is needed in some situations. Some steps are not needed in *every* situation, so the temptation is to skip them to save your fingers some typing. But you'll regret this when you unexpectedly hit a situation in which the step should not have been omitted. In the worst case scenario this can damage or destroy your FreeBSD installation, or at least require some head-scratching and possible hand-holding from the community to help you recover. Here's an example of a worst case scenario: one reason for rebooting into single-user mode is to test whether your new kernel works. If your new kernel doesn't work (e.g. panics during boot), you can back it out at that point and all is well. If you blindly charge on without testing it, and proceed with the installworld, you may then find that your new world cannot be used with your old kernel (e.g. every FreeBSD command crashes when run with the old kernel, because they all now depend on an extra syscall or something). Oops. Since there is no way to back out an installworld, your only recourses at this point are: to fiddle around with /rescue and try to reconstruct a working system by hand (needs expert knowledge); or to remember where you put your install CD and pray that your last backup was up-to-date; This is a very rare situation, and it mostly occurs when updating to a new major version of FreeBSD, or at certain times during the development of -CURRENT. However, it's a real situation that you may encounter depending on how you use FreeBSD. There are other situations that are both more common and less severe. However, with a little discipline in following the instructions you'll never notice them. Kris pgpXVLCqRhkDC.pgp Description: PGP signature
Re: Disappointed with version 6.0
On Saturday 11 March 2006 02:42, Peter wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: On Fri, Mar 10, 2006 at 11:57:59PM -0500, Peter wrote: I'm setting up a new server on 6.0 I've been planning for a long time and I am very disappointed with two critical issues. My motherboard is the ASUS K8V-X SE that I chose because it was listed as compatible at the FreeBSD/amd64 Project: http://www.freebsd.org/platforms/amd64/motherboards.html I wonder if going back to 5.4 might help? Onto the problems... You might have more luck if you also talk to [EMAIL PROTECTED] I'm not sure who this is but I'll look into it. 2. I can't use my USB ports! I get a line like this for each of my ports: uhci0: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] OK, but what is the problem? When something is plugged into a port and the system is powered up it will freeze at the POST level with no errors. It just sits there. I had similar problems with an Asus K8V a couple of months ago. Seems a lot of those boards had bios problems. Make sure you're using the latest bios upgrade. Fixed it for me. Beech -- --- Beech Rintoul - Sys. Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Alaska Paradise Travel \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com --- pgpWAZQNRFkfl.pgp Description: PGP signature
Re: disklabel messup.
Illoai, You were right. There is nothing wrong. Part of my problem was that I had never had or seen anything on other slices. Now I have two fbsd installs, ad0s1 and ad02 and I mistook ad0s2's missing info as applying to ad0s1. What I really want to do is use ad0s1 as my production install and ad0s2 as my test install. I guess my procedure would be to copy prod to test, then perform any testing for new ports, etc. Then once tested, perform those same actions on ad0s1. I have been reading up on how to clone a disk, so I can boot into a copy. Seems like some say tar can do it, but I have seen a place that said to only use dump. Oh, well. I am not quite there yet, working on baby steps. - Original Message - From: [EMAIL PROTECTED] To: Steve P. Subject: Re: disklabel messup. Date: Sat, 11 Mar 2006 04:33:25 -0600 On 3/10/06, Steve P. wrote: I was using sysinstall's disklabel facility to poke around. I accidentally did Undo on my installed 6.0 working slice. Are you sure you actually did anything? If /etc/fstab shows them correctly still and running 'df' shows them still as they should be, I'm pretty sure that running sysinstall again will show the slices and partitions correctly. I would advise that 'bsdlabel /dev/ad0' will show you your label just as effectively, and that df(1) is probably the correct method of gazing in rapture at your mounted partitions. Other commands to read up on might be fdisk and diskinfo. Good luck. -- -- -- ___ Play 100s of games for FREE! http://games.mail.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
On Saturday 11 March 2006 13:38, Peter wrote: --- Donald J. O'Neill [EMAIL PROTECTED] wrote: [...] ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a __ You've got a problem alright, and you don't even see it. == The ata driver sets the maximum transfer mode supported by the hardware as default. However the ata driver sometimes warns: ``DMA limited to UDMA33, non-ATA66 cable or device''. This means that the ata driver has detected that the required 80 conductor cable is not present or could not be detected properly, or that one of the devices on the channel only accepts up to UDMA2/ATA33. == You've got your 40GB Maxtor (you've installed FreeBSD on it), an ATA100 device, connected with your CDROM, an ATA33 device. The result is: your boot drive is running at UDMA33 instead of UDMA100. This is not going to work real well, as you can see. Do you really need that 40GB Maxtor? If you do, you're going to have to try adding an ATA controller card into one of your PCI slots and use that to connect your hard drives to. Try removing the 40GB Maxtor and reinstalling FreeBSD on the other two drives. I think that will clear up some problems for you. Can this be causing the problem with the 300 GB drive on the other controller? What I don't understand is why is there a problem only with one drive on the secondary controller? As for the cdrom, how else can it be connected? It will ALWAYS be slower than the hard disk. Or do you mean it should just not be connected to the boot drive? I never had such a problem before. I'll move around my drives and see what happens. Thanks for your help. -- Peter Hi Peter, You're going to have to have the cdrom connected, just not with a hard-drive or you'll have problems. As for the third hard-drive, that may have more to do with the way you set up the system than the problems with the connections as they are now. But, if you remove that drive and reinstall the system, I think (actually, I know, if you do it right) that will clear up a lot of problems. You've got two SATA ports on that MB, I think you would have problems then too. If you need that 40 GB drive, I suggest you go out and get a controller that you can run all three drives off of.. What I mean is, if you have the cdrom and the 40GB HD connected to the same port, on the same cable, as you have, it will only run at the speed of the cdrom. You have to get the HD off of that port. Since you've used the slave port with the other two HDs, your only choice is to install a Controller card, like a Promise or some other card. I had a problem like that at one time and that was the only way to fix it. That's why I sent that snippet from the at man page, it tells you what's going to happen if you do it this way. I don't think you're going to like have at ATA100 drive as the system drive running at UDMA33, it just might result in timing problems. Don PS At this point I probably can't answer anymore questions, at least not today. I've had too many beers and I'm having a tough time typing. I can still make sense, I just am having a problem getting it from my brain to the e-mail. And I intend to have some more. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem running Adobe acroread7
Lowell Gilbert wrote: Donald T Hayford [EMAIL PROTECTED] writes: I get the following error message when I try to open a file in Adobe acroread7, after which acroread quits: (acroread:7605): Gtk-WARNING **: Could not find the icon 'gnome-fs-home'. The 'hicolor' theme was not found either, perhaps you need to install it. You can get a copy from: http://freedesktop.org/Software/icon-theme/releases When I run pkg_info, I find the following items installed (among many others): gtk-1.2.10_13 Gimp Toolkit for X11 GUI (previous stable version) gtk-2.8.12 Gimp Toolkit for X11 GUI (current stable version) hicolor-icon-theme-0.5 A high-color icon theme shell from the FreeDesktop project I couldn't find anything on 'gnome-fs-home'. I am running the KDE desktop, not gnome. Are you running acroread from a command line? It doesn't require any FreeBSD Gnome or gtk support; it does the linux-gtk2 and linux-pango ports, but those are direct dependencies. The message above came when running from the command line and trying to open a file. If I run it from the KDE gui (by adding it to the menu), it just quietly disappears when I try to open a file. I didn't see any logged messages with the same information, but I don't know where to look. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mod_perl2 problems
Greetings, I'm trying to get mod_perl2 running on a apache20 server but when I try to load the module, apache does a segmentation fault. I'm using the latest available versions of apache20 and mod_perl2 available in ports. Has anyone else had this problem? FreeBSD 5.3-RELEASE apache-2.0.55_4 mod_perl2-2.0.2,3 perl-threaded-5.8.8 I run the same combination on a Gentoo Linux box and it works fine. Maybe not the exact same versions, but its still apache 2.0, mod_perl2 and perl-threaded. regards, Andréas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Xorg config problems
switched to Xorg for these machines a while back, and was pleased to find that I did not have to create a config file for Xorg as it was able to autodetect all the correct stuff. anyway - it's always better to create this file based on autoconfig made by -configure option. it's quite unlikely autodetect will get the most of your monitor and card. and in your case - autoconfig can't deal with such cases. but for CL5446 i have my config already done for 1024x768x16bit display - if you like. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GNOME Gdk
[EMAIL PROTECTED] ~]$ gedit (gedit:50388): Gdk-WARNING **: shmget failed: error 28 (No space left on device) or .. (gedit:23354): Gdk-WARNING **: shmget failed: error 12 (Cannot allocate memory) df and ulimit? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dd - cloning a disk.
Here is a simple (I think!) question for the I/O savy among you: If I had two identical disks, say, 73 GB Seagate 10K SCSIs, one completely operational fully setup FreeBSD with all the trimmings, and the other blank, or perhaps loaded but no longer usable, is 'dd' and appropriate tool to completely clone the Good disk to the not so good disktherefor making the second disk identical to the first? Bootable and all? yes dd if=/dev/firstdisk of=/dev/seconddisk bs=64k and yes it is bootable, but if you boot from second disk, FreeBSD kernel will mount root from first disk anyway, unless you will reconfigure it. so for booting from 2-nd disk, swap SCSI IDs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fw: dd - cloning a disk. Second Part!
Sorry, I forgpt to add this, I the answer is yes to the first question (original question), then, what happens if one 'dd's a small, say 36 GM disk to a larger one, say 73 GB. Can the newly made disk be resized so as not to loose 1/2 of it? yes - with growisofs and disklabel i actually did this, when joining 2 partition to one. i had chance to copy files from smaller to bigger partition (fitted), then with dd i MOVED this partition on disk, then did disklabel and did growfs to resize ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dd - cloning a disk.
It is, with a few 'buts'. Firstly, the source should be mounted but may not - unless system is generally idle. fsck will be checking the copy then, but with success. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem Installing FreeBSD 6.0, asking for help
Hello, may I ask you for help with the following Problem: When I try to install FreeBsd6.0, there is the following error during the boot process (because the system is not able to boot from CD, I have to boot from floppy) occurs: ahc0: probe1:ahc0:0:1:0: SCB 6: immediate reset Flags 0x620 ahc0: probe1:ahc0:0:1:0: No longer in timeout, status=25b ahc0: Issued channel A bus reset, SCBs 6 aborted. ... ... ... There are variants of the messages with different SCB, flags and status. As a result, the install program does not find any disk. FreeBSD5.2 is running and dmesg produces the following output: Copyright (c) 1992-2004 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 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0a35000. Preloaded elf module /boot/kernel/acpi.ko at 0xc0a351f4. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (797.97-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 268369920 (255 MB) avail memory = 251047936 (239 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: GBTAWRDACPI on motherboard pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00fdee0 acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 9 INTA is routed to irq 10 pcib0: slot 10 INTA is routed to irq 12 pcib0: slot 11 INTA is routed to irq 5 agp0: VIA 82C691 (Apollo Pro) host to PCI bridge mem 0xd800-0xdbff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pcib0: slot 1 INTA is routed to irq 11 pcib1: slot 0 INTA is routed to irq 11 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C596B UDMA66 controller port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: bridge, HOST-PCI at device 7.3 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xd800-0xd8ff mem 0xe3001000-0xe30010ff irq 10 at device 9.0 on pci0 rl0: Ethernet address: 00:40:33:ab:df:66 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: multimedia, audio at device 10.0 (no driver attached) ahc0: Adaptec 2940 SCSI adapter port 0xe000-0xe0ff mem 0xe300-0xe3000fff irq 5 at device 11.0 on pci0 aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 orm0: Option ROMs at iomem 0xc8000-0xca7ff,0xc-0xc7fff on isa0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 797967629 Hz quality 800 Timecounters tick every 10.000 msec Waiting 15 seconds for SCSI devices to settle acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0% GEOM: create disk cd0 dp=0xc2d77600 GEOM: create disk cd1 dp=0xc2d77e00 GEOM: create disk da0 dp=0xc2e24050 GEOM: create disk da1 dp=0xc2e26850 GEOM: create disk da2 dp=0xc2e26450 cd0 at ahc0 bus 0 target 4 lun 0 cd0: PLEXTOR CD-ROM PX-32TS 1.02 Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: cd present [329666 x 2048 byte records] cd1 at ahc0 bus 0 target 5 lun 0 cd1: YAMAHA CRW4416S 1.0f Removable CD-ROM SCSI-2 device cd1: 8.333MB/s transfers (8.333MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed da2 at ahc0 bus 0 target 2 lun 0 da2: IBM DCAS-34330 S65A Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15) da2: 4134MB
Re: Disappointed with version 6.0
On Saturday 11 March 2006 18:48, Peter wrote: You can answer me tomorrow if you like but here is an update: I removed the cdrom and the problem remains. I got the usb ports to work as well by updating the bios and fiddling with some settings. It is truly a mystery why this 300 GB drive cannot talk to FreeBSD. Again, it is detected fine by the bios; it passes dos level diagnostics; it is on the same ide cable (as slave) as the 200 GB drive that is identical to it save for an extra 100 GB. My next step is to boot with knoppix to see how it behaves. -- Peter Hi Peter, I've recovered sufficiently enough that I can type without spending all my time correcting spelling errors that a spelling checker can't fix. OK, does dmesg still give this with the cdrom removed: ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a If the message for ad0 has changed, and it is now detected as an ata100 device and is running at UDMA100, you've solved part of your problem. Your system will access the boot drive at a higher speed. ad3 is still detected but you can't access it. So, I have to ask: when you set up the system, did you install a ufs system on it? Did you carve it up using bsdlabel? Or, did you leave it alone because you plane on using it for something else? This would be a reason for why it shows up on dmesg, but you can't access it. Now, you need to do something about the cdrom. It's kind of unhandy to be without one. That's why I asked if you really needed the 40GB Maxtor and if you did, suggested you get an ata controller card, then you could use all three drives. And I also asked if you could just remove that drive and use the two Seagates. I guess there's one other question: how did you get from 5.4 to 6.0, and is it 6.0 or is it 6 STABLE? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dd - cloning a disk.
On Saturday 11 March 2006 14:43, Wojciech Puchar wrote: Here is a simple (I think!) question for the I/O savy among you: If I had two identical disks, say, 73 GB Seagate 10K SCSIs, one completely operational fully setup FreeBSD with all the trimmings, and the other blank, or perhaps loaded but no longer usable, is 'dd' and appropriate tool to completely clone the Good disk to the not so good disktherefor making the second disk identical to the first? Bootable and all? yes dd if=/dev/firstdisk of=/dev/seconddisk bs=64k and yes it is bootable, but if you boot from second disk, FreeBSD kernel will mount root from first disk anyway, unless you will reconfigure it. Would this also work to copy CDs? If so, does it matter what os and/or format they would have? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to build or update vcdimager
Matthew D. Fuller wrote: On Sat, Mar 11, 2006 at 03:37:59PM +0900 I heard the voice of Norikatsu Shigemura, and lo! it spake thus: SEE ALSO: http://www.freebsd.org/cgi/query-pr.cgi?pr=93916 I got a similar error from dirmngr. It seems like the program installs its own INFO files, then the port tries to install INFO again (note the --quiet; that only appears in the bsd.port.mk version, not in the port's makefiles). I hacked around it by just using make -k install to make it ignore the error. OK, I tried your suggest and it appears to have worked. The build exited with this message: install-info --quiet /usr/local/info/vcd-info.info /usr/local/info/dir install-info: menu item `vcd-info' already exists, for file `vcdimager' *** Error code 1 (continuing) === Compressing manual pages for vcdimager-0.7.23_1 === Running ldconfig /sbin/ldconfig -m /usr/local/lib === Registering installation for vcdimager-0.7.23_1 `install' not remade because of errors. However, it does seem to have worked. I would have thought that the port maintainer would have foreseen this predicament and taken steps to alleviate it however. -- Gerard Seibert [EMAIL PROTECTED] PGP: http://www.seibercom.net/sig/gerard.asc pgppdsVMqRxKv.pgp Description: PGP signature
gmirror on a laptop.
List; I wanted to fiddle around with gmirror(8) on a Dell C-600 Laptop. It has a 2-slice, 20 Gig HD, and I essentially wanted to mirror ad0s1 to ad0s2. I realize this will put the HD under stress, but otherwise it seems do-able. What I want to know is whether this is such an incredibly bad idea I shouldn't even consider it --or-- it seems like a good way to get familiar with gmirror, so go for it. Thanks, Patrick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems mounting msdosfs
Lowell Gilbert wrote on Thu, 09 Mar 2006 08:00: Jakob Breivik Grimstveit [EMAIL PROTECTED] writes: I'm still experiencing same problems Christer Solskogen reported two years ago on FreeBSD 5.2.1 with msdosfs mount failure upon boot making it go into single-user-mode (having to press enter (into shell) and ctrl+d (to continue booting) to get box up after reboot: http://groups.google.no/group/mailing.freebsd.current/browse_thread/thread/4e660419935ea6e5/80580ef045e0e1d1 However, doing a `mount -a` after boot brings them both in. I have the following in my fstab: $ grep msdosfs /etc/fstab /dev/ad4s5 /mnt/share1 msdosfs rw 2 2 /dev/ad4s6 /mnt/share2 msdosfs rw 2 2 $ uname -r 5.4-RELEASE-p7 $ grep 'boot.c' /usr/src/sbin/fsck_msdosfs/boot.c __RCSID($NetBSD: boot.c,v 1.9 2003/07/24 19:25:46 ws Exp $); $FreeBSD: src/sbin/fsck_msdosfs/boot.c,v 1.4 2004/04/20 11:41:57 tjr Exp $; Any suggestions as to what to do with this? Maybe it's having trouble loading the msdosfs kernel module before boot? Try building that into your kernel. Actually, this seems to be a very strict parsing of the fstab when it comes to msdosfs file systems. I Googled a lot (even further, I've been struggling with this problem for several years now), and suddenly, the below worked nicely. Case closed! $ cat /etc/fstab | grep share /dev/ad4s5 /mnt/share1 msdosfs rw,-m644,-M755,-ujakobbg,-gjakobbg 0 0 /dev/ad4s6 /mnt/share2 msdosfs rw,-m644,-M755,-ujakobbg,-gjakobbg 0 0 Thanks for a great list! -- Jakob Breivik Grimstveit, http://www.grimstveit.no/jakob/, 48298152 Besøk Newsergalleriet: http://www.newsergalleriet.no/ All power corrupts, but we need electricity. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: a stupid question about sound
the same thing happened to mpg321 too. as a regular user, I can't run mpg321, only root can run mpg321 to play mp3 files. TFC On 3/11/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On 3/10/06, Tsu-Fan Cheng [EMAIL PROTECTED] wrote: hi, I got a situation, for some reason, only root can use audio device when playing movies with mplayer on my freebsd 6.0/amd64 now, not user. But vlc is fine for both. I guess there is some audio wrapper issue but couldn't put a finger on it, any idea? If you do: ls -l /dev | grep dsp crw-rw-rw- 1 rootwheel 0, 38 Mar 10 00:57 dsp0.0 crw-rw-rw- 1 rootwheel 0, 41 Mar 6 12:43 dsp0.1 crw-rw-rw- 1 rootwheel 0, 39 Mar 6 12:43 dspW0.0 crw-rw-rw- 1 rootwheel 0, 42 Mar 6 12:43 dspW0.1 crw-rw-rw- 1 rootwheel 0, 44 Mar 6 12:43 dspr0.1 Does it look mostly like that? If you don't have a problem there, it might be with mplayer. I noticed a minor update sometime in the last few days, but I haven't actually done the update. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
--- Donald J. O'Neill [EMAIL PROTECTED] wrote: On Saturday 11 March 2006 13:38, Peter wrote: --- Donald J. O'Neill [EMAIL PROTECTED] wrote: [...] ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a __ You've got a problem alright, and you don't even see it. == The ata driver sets the maximum transfer mode supported by the hardware as default. However the ata driver sometimes warns: ``DMA limited to UDMA33, non-ATA66 cable or device''. This means that the ata driver has detected that the required 80 conductor cable is not present or could not be detected properly, or that one of the devices on the channel only accepts up to UDMA2/ATA33. == You've got your 40GB Maxtor (you've installed FreeBSD on it), an ATA100 device, connected with your CDROM, an ATA33 device. The result is: your boot drive is running at UDMA33 instead of UDMA100. This is not going to work real well, as you can see. Do you really need that 40GB Maxtor? If you do, you're going to have to try adding an ATA controller card into one of your PCI slots and use that to connect your hard drives to. Try removing the 40GB Maxtor and reinstalling FreeBSD on the other two drives. I think that will clear up some problems for you. Can this be causing the problem with the 300 GB drive on the other controller? What I don't understand is why is there a problem only with one drive on the secondary controller? As for the cdrom, how else can it be connected? It will ALWAYS be slower than the hard disk. Or do you mean it should just not be connected to the boot drive? I never had such a problem before. I'll move around my drives and see what happens. Thanks for your help. -- Peter Hi Peter, You're going to have to have the cdrom connected, just not with a hard-drive or you'll have problems. As for the third hard-drive, that may have more to do with the way you set up the system than the problems with the connections as they are now. But, if you remove that drive and reinstall the system, I think (actually, I know, if you do it right) that will clear up a lot of problems. You've got two SATA ports on that MB, I think you would have problems then too. If you need that 40 GB drive, I suggest you go out and get a controller that you can run all three drives off of.. What I mean is, if you have the cdrom and the 40GB HD connected to the same port, on the same cable, as you have, it will only run at the speed of the cdrom. You have to get the HD off of that port. Since you've used the slave port with the other two HDs, your only choice is to install a Controller card, like a Promise or some other card. I had a problem like that at one time and that was the only way to fix it. That's why I sent that snippet from the at man page, it tells you what's going to happen if you do it this way. I don't think you're going to like have at ATA100 drive as the system drive running at UDMA33, it just might result in timing problems. Don PS At this point I probably can't answer anymore questions, at least not today. I've had too many beers and I'm having a tough time typing. I can still make sense, I just am having a problem getting it from my brain to the e-mail. And I intend to have some more. You can answer me tomorrow if you like but here is an update: I removed the cdrom and the problem remains. I got the usb ports to work as well by updating the bios and fiddling with some settings. It is truly a mystery why this 300 GB drive cannot talk to FreeBSD. Again, it is detected fine by the bios; it passes dos level diagnostics; it is on the same ide cable (as slave) as the 200 GB drive that is identical to it save for an extra 100 GB. My next step is to boot with knoppix to see how it behaves. -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to build or update vcdimager
On Sat, Mar 11, 2006 at 09:29:15PM -0500 I heard the voice of Gerard Seibert, and lo! it spake thus: I would have thought that the port maintainer would have foreseen this predicament and taken steps to alleviate it however. My offhand guess (based on coincidence, not any knowledge that it actually is so) is that it's fallout from the recent libtool changes. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problem Installing FreeBSD 6.0, asking for help
I believe you are saying that 5.2 is currently installed on the hard drive and you want to do a fresh install from scratch of 6.0. You have to change the pc bios setup to boot from the cd drive instead of from the hard drive. The pc will then boot from the 6.0 cd and install 6.0 destroying the 5.2 system on the hard drive along with any user data you had. After 6.0 is installed you have to change the bios back to booting from the hard drive. Be sure you have a backup of any user data on the 5.2 system you want saved. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Saturday, March 11, 2006 5:44 PM To: [EMAIL PROTECTED] Subject: Problem Installing FreeBSD 6.0, asking for help Hello, may I ask you for help with the following Problem: When I try to install FreeBsd6.0, there is the following error during the boot process (because the system is not able to boot from CD, I have to boot from floppy) occurs: ahc0: probe1:ahc0:0:1:0: SCB 6: immediate reset Flags 0x620 ahc0: probe1:ahc0:0:1:0: No longer in timeout, status=25b ahc0: Issued channel A bus reset, SCBs 6 aborted. ... ... ... There are variants of the messages with different SCB, flags and status. As a result, the install program does not find any disk. FreeBSD5.2 is running and dmesg produces the following output: Copyright (c) 1992-2004 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 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0a35000. Preloaded elf module /boot/kernel/acpi.ko at 0xc0a351f4. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (797.97-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,M CA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 268369920 (255 MB) avail memory = 251047936 (239 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: GBTAWRDACPI on motherboard pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00fdee0 acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 9 INTA is routed to irq 10 pcib0: slot 10 INTA is routed to irq 12 pcib0: slot 11 INTA is routed to irq 5 agp0: VIA 82C691 (Apollo Pro) host to PCI bridge mem 0xd800-0xdbff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pcib0: slot 1 INTA is routed to irq 11 pcib1: slot 0 INTA is routed to irq 11 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C596B UDMA66 controller port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: bridge, HOST-PCI at device 7.3 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xd800-0xd8ff mem 0xe3001000-0xe30010ff irq 10 at device 9.0 on pci0 rl0: Ethernet address: 00:40:33:ab:df:66 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: multimedia, audio at device 10.0 (no driver attached) ahc0: Adaptec 2940 SCSI adapter port 0xe000-0xe0ff mem 0xe300-0xe3000fff irq 5 at device 11.0 on pci0 aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 orm0: Option ROMs at iomem 0xc8000-0xca7ff,0xc-0xc7fff on isa0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 797967629 Hz quality 800 Timecounters tick every 10.000 msec Waiting 15 seconds for SCSI devices to settle acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0%
Re: Disappointed with version 6.0
--- Donald J. O'Neill [EMAIL PROTECTED] wrote: On Saturday 11 March 2006 18:48, Peter wrote: You can answer me tomorrow if you like but here is an update: I removed the cdrom and the problem remains. I got the usb ports to work as well by updating the bios and fiddling with some settings. It is truly a mystery why this 300 GB drive cannot talk to FreeBSD. Again, it is detected fine by the bios; it passes dos level diagnostics; it is on the same ide cable (as slave) as the 200 GB drive that is identical to it save for an extra 100 GB. My next step is to boot with knoppix to see how it behaves. -- Peter Hi Peter, I've recovered sufficiently enough that I can type without spending all my time correcting spelling errors that a spelling checker can't fix. OK, does dmesg still give this with the cdrom removed: ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a If the message for ad0 has changed, and it is now detected as an ata100 device and is running at UDMA100, you've solved part of your problem. dmesg now says: ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA133 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 So ad0's speed has increased by 100 MB/s? Your system will access the boot drive at a higher speed. ad3 is still detected but you can't access it. So, I have to ask: when you set up the system, did you install a ufs system on it? Did you carve it up using bsdlabel? Or, did you leave it alone because you plane on using it for something else? This would be a reason for why it shows up on dmesg, but you can't access it. Yes, per install defaults ufs (and most probably soft updates) was used. Everything was done via the default sysinstall procedure. I said to use entire drive and then made one partition. It creates /dev/ad3s1d. I just entered sysinstall again to start fresh and during the format portion Doing newfs I hear some sounds I've never heard before on a hard drive. Like a mechanical arm is trying to move but it keeps bouncing back. Then I get: Error mounting /dev/ad3s1d on /images : Input/output error But if there was something mechanically wrong then my dos-level diagnostics would of picked it up (I had an disk excercise tool running on it for 20 minutes without any problems). Now, you need to do something about the cdrom. It's kind of unhandy to be without one. That's why I asked if you really needed the 40GB Maxtor and if you did, suggested you get an ata controller card, then you could use all three drives. And I also asked if you could just remove that drive and use the two Seagates. I need all three drives: 1. system drive (40 GB) 2. client data backups (200 GB) 3. client data images (300 GB) The #3 drive (the problematic one) will actually be removed offsite once the (client hard drive) images have been stored. And this is where I might be able to weasel out of my current predicament. I can put back the cdrom afterwards. I guess there's one other question: how did you get from 5.4 to 6.0, and is it 6.0 or is it 6 STABLE? No, no. This is a brand new install of 6.0 (I can therefore mess around with impunity). When I mentioned go back to 5.4 I did not mean to imply I upgraded. -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
cg 0: bad magic number [used to be Disappointed with version 6.0]
Ok, I have narrowed down my problem a great deal. It appears that FreeBSD cannot read the partition table of my 300 GB Seagate Barracuda. My dos diagnostic utility works because it accesses the disk in a different way. I used the entire disk (one slice/partition) and attempted to format it. This is what I get after it reaches the end of the disk: cg 0: bad magic number It also slows down significantly about 3/4 through the procedure. Now the funny part. I create two partitions and the newfs output is exactly the same as before when I try to format the first partition! It tries to format as if there is only one partition and produces the same error. If I remove the slice via sysinstall and then try fdisk I get this: # fdisk -vBI ad3 *** Working on device /dev/ad3 *** parameters extracted from in-core disklabel are: cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=581421 heads=16 sectors/track=63 (1008 blks/cyl) Information from DOS bootblock is: 1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 586072305 (286168 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 812/ head 15/ sector 63 2: UNUSED 3: UNUSED 4: UNUSED fdisk: Geom not found Anyone? -- Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dd - cloning a disk.
Grant Peel wrote: Hi all, Here is a simple (I think!) question for the I/O savy among you: If I had two identical disks, say, 73 GB Seagate 10K SCSIs, one completely operational fully setup FreeBSD with all the trimmings, and the other blank, or perhaps loaded but no longer usable, is 'dd' and appropriate tool to completely clone the Good disk to the not so good disktherefor making the second disk identical to the first? Bootable and all? -Grant Hi, Grant: Yes, dd, will copy/clone a disk. There was a fairly long, good thread on this subject on this list sometime in the last 3-5 weeks. Giorgios Keramidas commented that dd was too slow for his tastes and suggested dump and restore for this type of work. Now, I'm no expert at fdisk and bsdlabel scripting, but here's a plan I adopted as a result of that thread. It includes manual labor via the sysinstall front end to fdisk and bsdlabel, and then is automagic. 1. Set up the hardware--- I'm assuming extant drive on primary IDE master and new drive as same channel slave. 2. Run sysinstall as root, choose Configure (Post Install Configuration) and run Fdisk. Dedicate the entire new disk and set it bootable. Write out the changes with, um W, isn't it (IIRC) 3. Exit sysinstall and then start it up again. Run the disk label editor and set up partitions of a sufficient size for the clone procedure (generally, same size or larger; in a pinch, could be smaller than the original partition but, obviously, must be large enough for the data on the original partition). Write out the changes, exist sysinstall. 4. Run this script (edit it to reflect your actual layout): #!/bin/sh mkdir -p /1 mkdir -p /2 mkdir -p /3 mount /dev/ad1s1a /1 mount /dev/ad1s1d /2 mount /dev/ad1s1e /3 dump -0 -a -L -f - / | ( cd /1 ; restore -ruvf - ) dump -0 -a -L -f - /var | ( cd /2 ; restore -ruvf - ) dump -0 -a -L -f - /usr | ( cd /3 ; restore -ruvf - ) Quick, easy, fast. Probably someone with a better handle on fdisk/bsdlabel could script steps 2-3 above. And, with thought, #4 could be improved, too. But, it is faster. Basically, I'm thinking this: A. With the dd approach, you don't need to know anything about the extant filesystem's layout. B. But, if you use dump | restore, you trade a little foreknowledge of the extant filesystem's layout for flexibility (disk doesn't have to be identical); and speed (the only thing copied is the data, not the blank space, and from a filesystem viewpoint instead of block level copying). We've used this successfully to create a number of disks for cheap workstations at a client of ours---as a result, they have plenty of stations available with almost no time spent in tweaking the installation other than hostname and interface configuration in rc.conf. YMMV, and all that. HTH, (or at least provides another perspective). Kevin Kinsey -- My doctorate's in Literature, but it seems like a pretty good pulse to me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disappointed with version 6.0
On Saturday 11 March 2006 20:03, Peter wrote: OK, does dmesg still give this with the cdrom removed: ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA33 acd0: CDROM GCR-8525B/1.02 at ata0-slave PIO4 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 Trying to mount root from ufs:/dev/ad0s1a If the message for ad0 has changed, and it is now detected as an ata100 device and is running at UDMA100, you've solved part of your problem. dmesg now says: ad0: 39205MB Maxtor 6K040L0 NAR61HA0 at ata0-master UDMA133 ad2: 190782MB Seagate ST3200826A 3.03 at ata1-master UDMA100 ad3: 286168MB Seagate ST3300831A 3.03 at ata1-slave UDMA100 So ad0's speed has increased by 100 MB/s? I was guessing that it was an ata100, it seems to be an ata133 instead. Now you can see what the difference is when connecting a hard-drive with a cdrom. Your system will access the boot drive at a higher speed. ad3 is still detected but you can't access it. So, I have to ask: when you set up the system, did you install a ufs system on it? Did you carve it up using bsdlabel? Or, did you leave it alone because you plane on using it for something else? This would be a reason for why it shows up on dmesg, but you can't access it. Yes, per install defaults ufs (and most probably soft updates) was used. Everything was done via the default sysinstall procedure. I said to use entire drive and then made one partition. It creates /dev/ad3s1d. I just entered sysinstall again to start fresh and during the format portion Doing newfs I hear some sounds I've never heard before on a hard drive. Like a mechanical arm is trying to move but it keeps bouncing back. Then I get: Error mounting /dev/ad3s1d on /images : Input/output error But if there was something mechanically wrong then my dos-level diagnostics would of picked it up (I had an disk excercise tool running on it for 20 minutes without any problems). No, Microsloth makes things run (or appear to run) by hiding a lot of information from you. When did you run the dos-level diagnostics on the disk, before or after you installed FreeBSD? I ask because if it was after, well, dos-level disk diagnostics can't access a ufs formated disk without doing nasty things to what's on it. If was before, you should have run spinrite 6.0 on it, but that's going to run for about , oh say, at a wild guess, on a drive that size, 2 or 3 days. Your twenty minute run on that drive wouldn't really tell you much unless the drive was drastically failing. Now, you need to do something about the cdrom. It's kind of unhandy to be without one. That's why I asked if you really needed the 40GB Maxtor and if you did, suggested you get an ata controller card, then you could use all three drives. And I also asked if you could just remove that drive and use the two Seagates. I need all three drives: 1. system drive (40 GB) 2. client data backups (200 GB) 3. client data images (300 GB) The #3 drive (the problematic one) will actually be removed offsite once the (client hard drive) images have been stored. And this is where I might be able to weasel out of my current predicament. I can put back the cdrom afterwards. I guess there's one other question: how did you get from 5.4 to 6.0, and is it 6.0 or is it 6 STABLE? No, no. This is a brand new install of 6.0 (I can therefore mess around with impunity). When I mentioned go back to 5.4 I did not mean to imply I upgraded. Just don't cable back with the cdrom. -- Peter Now, what about your usb? a message like: uhci0: VIA 83C572 USB controller port 0xb800-0xb81f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] Nothing wrong with that message. Base on that message, you don't have a problem. It's when you see messages like irq storm on some device throttling source, or device returns some error message, or can't assign an irq, then you know you've got a problem that's going to require some swapping around on the pci bus. As a matter of fact, I was having usb problems until I went 6-RELEASE to 6-STABLE. Which at that time I was able to determine that it wasn't actually a usb problem, I was having a problem with a modem and bad usb mouse. I pulled the modem and was going to throw it away, put it away instead, until I had a need for one at which point I found out that it's position on the pci bus made the difference in whether it would play nicely with the cards or not. The mouse did get tossed, it would work intermittently under windows and FreeBSD would only get to a certain load point and then reboot. Actually, finding it was a little more difficult than I've said. Don ___ freebsd-questions@freebsd.org mailing list
