Why ue0 do ARP on non local address when using static route?
This is 8.3-Release on a HP EliteBook 8460p (4-core i5) with an on board Intel (em0) interface. When attached a Trendent TU2-ET100 USB Ether dongle for a second interface, it has no problem to talk to the local network (10.234.37.0/24), but it has problem to talk to a remote network or host (10.227.148.0/24) via eu0 interface. When a remote host ping this host or this host ping that remote host, ARP request is always showing up. A static route is set and remote host is no part of the local sub net, why ARP is going on? Is any sysctl parameter can fix this problem? -Jin Internet: DestinationGatewayFlagsRefs Use Netif Expire default10.234.16.1UGS 0 2841993em0 10.227.148.52 10.234.37.80 UHS 0 26ue0 10.234.16.0/22 link#1 U 00em0 10.234.17.41 link#1 UHS 00lo0 10.234.37.0/24 link#8 U 03ue0 10.234.37.80 link#8 UHS 00lo0 127.0.0.1 link#7 UH 0 492lo0 ue0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=80008VLAN_MTU,LINKSTATE ether 00:50:b6:00:a4:91 inet 10.234.37.80 netmask 0xff00 broadcast 10.234.37.255 media: Ethernet autoselect (100baseTX full-duplex) status: active ping from 10.227.148.52 12:16:37.924425 IP 10.227.148.52 10.234.37.80: ICMP echo request, id 21002, seq 1, length 64 12:16:37.924442 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 12:16:38.931919 IP 10.227.148.52 10.234.37.80: ICMP echo request, id 21002, seq 2, length 64 12:16:38.931937 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 12:16:39.931662 IP 10.227.148.52 10.234.37.80: ICMP echo request, id 21002, seq 3, length 64 12:16:39.931680 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 12:16:40.931656 IP 10.227.148.52 10.234.37.80: ICMP echo request, id 21002, seq 4, length 64 12:16:40.931674 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 12:16:41.931519 IP 10.227.148.52 10.234.37.80: ICMP echo request, id 21002, seq 5, length 64 12:16:41.931533 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 12:16:42.931643 IP 10.227.148.52 10.234.37.80: ICMP echo request, id 21002, seq 6, length 64 ping to 10.227.148.52 12:16:42.931661 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 12:16:59.724724 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 12:17:00.725715 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 12:17:01.725883 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 12:17:02.726690 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 12:17:03.727677 ARP, Request who-has 10.227.148.52 tell 10.234.37.80, length 28 ^C 45 packets captured 1557 packets received by filter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why ue0 do ARP on non local address when using static route?
/etc/ethers does not help because there is no way resolve the IP by QFHN in ethers. The correct way is to use router IP (10.234.37.1) between 10.234.37.0 and 10.227.148.0 instead of interface IP (10.234.37.80) for static route. From: Chuck Swiger cswi...@mac.com To: Jin Guojun jguo...@sbcglobal.net Cc: questions freebsd questi...@freebsd.org Sent: Wed, February 13, 2013 12:55:07 PM Subject: Re: Why ue0 do ARP on non local address when using static route? On Feb 13, 2013, at 12:35 PM, Jin Guojun wrote: When attached a Trendent TU2-ET100 USB Ether dongle for a second interface, it has no problem to talk to the local network (10.234.37.0/24), but it has problem to talk to a remote network or host (10.227.148.0/24) via eu0 interface. When a remote host ping this host or this host ping that remote host, ARP request is always showing up. A static route is set and remote host is no part of the local sub net, why ARP is going on? You've told the interface that it can reach 10.227.148.52 via 10.234.37.80, which is the IP ue0 was configured to use. It sends ARPOP_REQUESTS to get the MAC address of 10.227.148.52 which is expected to be reachable. Is any sysctl parameter can fix this problem? You can do things like use proxy-arp, or setup /etc/ethers, or NAT, or even configure ue0 to be on the same subnet as 10.227.148.52 instead, perhaps using an alias. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why ue0 do ARP on non local address when using static route?
man page says that ethernet-address (MAC) + fully-qualified-host-name (FQHN). The issue is that host cannot resolve the address by using FQHN, thus no ARP any more, but no traffic either. After adding FQDH in the /etc/hosts file then, ARP request uses FQHN instead of IP (10.237.148.52). The question is why ARP occurs? The subnet (10.227.148.0) is not matching with the local network/netmask (10.234.37.0/24) unless somewhere in the system is using default 255.0.0.0 netmask for 10.0 A class network by mistake. From: Chuck Swiger cswi...@mac.com To: Jin Guojun jguo...@sbcglobal.net Cc: questions freebsd questi...@freebsd.org Sent: Wed, February 13, 2013 2:33:57 PM Subject: Re: Why ue0 do ARP on non local address when using static route? On Feb 13, 2013, at 2:17 PM, Jin Guojun wrote: /etc/ethers does not help because there is no way resolve the IP by QFHN in ethers. I'm not sure what QFHN is, but setting up an entry in /etc/ethers provides the IP to MAC address mapping that ARP attempts to provide dynamically. The correct way is to use router IP (10.234.37.1) between 10.234.37.0 and 10.227.148.0 instead of interface IP (10.234.37.80) for static route. Assuming there's a router at 10.234.37.1 which knows how to get to 10.227.148.52, yes. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.3-R cannot mount non-BSD burned DVD
Here are two DVDs burned by MS Windows. DVD1 is Visual Studio 2008 distributed by MS in UDF FS. mount_udf cannot mount it and mount_cd9660 can mount it but see only a readme.txt. % cdcontrol info Starting track = 1, ending track = 1, TOC size = 18 bytes track start duration block length type - 1 0:02.00 246:31.67 0 1109392 data 170 246:33.67 - 1109392 - - % file - /dev/acd0 /dev/stdin: UDF filesystem data (version 1.5) 'DVD1 DVD2 is burned under Windows XP by DVD utility in UFD FS. Although BSD file command does not recognize it, mount_udf can mount it correctly. It sounds like that we have issues in handling UDF FS. Attached are first two-page hexdump on both DVDs to help analyzing the problem. % cdcontrol info Starting track = 1, ending track = 1, TOC size = 18 bytes track start duration block length type - 1 0:02.00 0:18.26 01376 data 170 0:20.26 -1376 - - % file - /dev/acd0 /dev/stdin: data % ll /cdrom/4710/ total 3259 dr-xr-xr-x 1 root wheel2048 May 23 17:52 ./ dr-xr-xr-x 2 root wheel2048 May 23 17:52 ../ -r--r--r-- 1 root wheel 956262 May 23 17:36 ..-0003.amr -r--r--r-- 1 root wheel 24576 May 23 17:45 -3.doc -r--r--r-- 1 root wheel 688384 May 23 17:39 RealPlayer_cn.exe From: Polytropon free...@edvax.de To: Jin Guojun jguo...@sbcglobal.net Cc: questi...@freebsd.org Sent: Sat, September 29, 2012 11:12:05 PM Subject: Re: 8.3-R cannot mount non-BSD burned DVD On Sat, 29 Sep 2012 22:44:24 -0700 (PDT), Jin Guojun wrote: This problem seems having been there for a while, but was not pay attention to it till now. Most DVDs burned under Windows machine cannot be mounted on FreeBSD 8.3-R. It gives following error: # mount /cdrom mount_cd9660: /dev/acd0: Invalid argument Some of those DVD can be mount, but no content can be found: % df /cdrom Filesystem 512-blocks Used Avail Capacity Mounted on /dev/acd0 4687968 46879680 100%/cdrom % ll /cdrom total 4 dr-xr-xr-x 1 root wheel 112 Jul 13 2009 ./ drwxr-xr-x 24 root wheel 512 Sep 25 23:11 ../ -r-xr-xr-x 1 root wheel 135 Jul 13 2009 readme.txt* Searched bug report, but did not find related report. Does anyone have seen this problem? If so, is any working around for this problem? Cannot confirm that here, reading a various amount of data and media DVDs. Some of them are in ISO-9660 format, some of them are UDF. The reader is a cheap LiteOn drive, and OS version is 8.2-STABLE of last year. You can check a DVD's content by some tests before attempting to mount it. First check if they contain a data session, in this example it's a movie DVD from Russia: % cdcontrol info Starting track = 1, ending track = 1, TOC size = 18 bytes track start duration block length type - 1 0:02.00 222:10.26 0 999776 data 170 222:12.26 - 999776 - - Okay, one data track. Check _what_ data it is: % file - /dev/acd0 /dev/stdin: UDF filesystem data (version 1.5) 'NU POGODI' This media can be mounted like any data DVD, even if we assume a CD-9660 file system (commonly found on data CDs): # mount -t cd9660 -o ro /dev/acd0 /media/dvd # df -h /media/dvd FilesystemSizeUsed Avail Capacity Mounted on /dev/acd0 4.1G4.1G 0B 100%/media/dvd # umount /media/dvd You could do some similar tests to see where you experience problems. It's quite possible that the DVDs made in Windows have some problems, e. g. not being closed, or having some strange data format that doesn't conform to the standard. Check if they contain a CD-9660 or a UDF file system, and which version it is. Note that FreeBSD also has a mount_udf command which could be working for those? When the CD-9660 file system is used, there are several extensions that help to deal with restrictions in the original specification (like file name length or depth of directory hierarchy). The standard is the RockRidge extension as used in many operating systems (or, to be correct, by many pre- mastering and burning tools), but Windows uses the Joliet extension. However, FreeBSD can understand both - _if_ they are properly done. See man mkisofs for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... DVD-with-MS-UDF Description: Binary data DVD-with-1-dir Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs during dump + compress usb2-drive
From: Xin Li delp...@delphij.net To: Jin Guojun jguo...@sbcglobal.net Cc: questi...@freebsd.org; hack...@freebsd.org Sent: Sun, September 30, 2012 1:07:40 PM Subject: Re: system hangs during dump + compress usb2-drive On 9/29/12 10:49 PM, Jin Guojun wrote: In FreeBSD 8.3 release (possibly in earlier release), dump a file system has 2-3GB or more content can cause system hang in a specific case (pipe to compression): dump FS-on-SATA-drive usb-drive OK dump FS-on-SATA-drive | anyCompress sata-drive OK mv a-large-dump-file from STAT drive to a USB drive OK dump small-FS-on-SATA-drive | anyCompress usb-drive OK small -- 1.8GB or less dump large-FS-on-SATA-drive | anyCompress usb-drive hang content is 3GB or larger (did not try around 2GB yet) When system hangs, no sub system, such video, network, etc, will function. Typically, the unfinished compressed dump file is around 1.5-2.7GB, so guessing dumped file content is close to or over 2GB when failure occurred. Has anyone encountered the same problem? Because this usually takes a few hours to occur, this is hard to watch how/when it happens. Is any way to debug or determine what status the system is? For starters I'd use a different console for doing procstat -kk -a and see what the system is doing. (Perhaps also top) I *think* that if it's just hanging for some time, it's probably because the system is trying to take a snapshot? It takes time on UFS when creating and removing the snapshot. Just a guess... Cheers, --- Not sure how to use a different console. No tty is functioning (neither ttyv? nor over network). You are right on a different case -- mount /dev/da0s4d /mnt# mount a usb drive cd /mnt ssh remote-liux-host tar -cf - 8GB_FS | tar -xf - In this case, doing ls -l /mnt or df will hangs, but system is still alive. The network is 45Mbps. I have no idea how long it took the tar to finish since machine is 60 km away. When I left there last Friday, only 400MB was done in one hour. I will get the processing time tomorrow. The problem we can see now is that tar (probably the pipe) process only finish with 4GB. # df Filesystem1K-blocks Used Avail Capacity Mounted on /dev/ad4s3a 1012974355348 57659038%/ devfs 1 1 0 100%/dev ... /dev/da0s4d 1027486774 4198246 941089588 0%/mnt So, I suspect this is a pipe problem, not a compress issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
system hangs during dump + compress usb2-drive
In FreeBSD 8.3 release (possibly in earlier release), dump a file system has 2-3GB or more content can cause system hang in a specific case (pipe to compression): dump FS-on-SATA-drive usb-drive OK dump FS-on-SATA-drive | anyCompress sata-drive OK mv a-large-dump-file from STAT drive to a USB drive OK dump small-FS-on-SATA-drive | anyCompress usb-drive OK small -- 1.8GB or less dump large-FS-on-SATA-drive | anyCompress usb-drive hang content is 3GB or larger (did not try around 2GB yet) When system hangs, no sub system, such video, network, etc, will function. Typically, the unfinished compressed dump file is around 1.5-2.7GB, so guessing dumped file content is close to or over 2GB when failure occurred. Has anyone encountered the same problem? Because this usually takes a few hours to occur, this is hard to watch how/when it happens. Is any way to debug or determine what status the system is? -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
gs-8-8.71 under 8.1-Release missing x11 devices
gs 8-8.71 under FreeBSD 8.1-R seems missing x11 device. When use ghostview, it complains /unknown device x11 /By tracing around, I found it was caused by gs 8-8.71. As typing gs --help, it shows much less devices supported than gs 8-8.62 under FreeSBD 6.4-R. By searching on the Internet, one message says that this could be resulted by build config. Is this true? or can gs be dynamically configured to use x11 device? Hopefully, users do not have to recompile ghostscript. -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
What causes random disk access slow down
A 6-7 years old Xeon dual 2.4MHz CPU machine runs FreeBSD 6.4-Release suddenly becomes slow on some tasks requiring disk access. Typical things like ls, objdump etc. Be more specific, a couple of minutes objdump became a several hours job. A several seconds ls -RC became a 15-minute task (see output below). It sounds like a hard drive problem, but run sequential disk test on all drives, their throughput meet the original disk spec and disks run very quite, at random disk access, disks generate some rigid noise, so it looks like a random disk access problem. This machine has two IDE PATA drives (ignore da0 -- a USB stick), but No error message has been recorded in dmesg for any dirve a couple of weeks after the problem happened. Machine has been rebooted a few times after slowness occurred, but it won't help. Is there anyway/any tool to find out what is going wrong in the system? -Jin [165] bsd-ms: ls -RC Dir 3.756u 19.402s 15:29.37 2.4%30+2938k 49120+76io 0pf+0w monitored from the other terms -- [138] bsd-ms: ll ~/Dir -rw-r--r-- 1 src wheel 6152192 Oct 27 14:53 /home/users/src/Dir [139] bsd-ms: ll ~/Dir -rw-r--r-- 1 src wheel 8019968 Oct 27 14:56 /home/users/src/Dir [140] bsd-ms: ll ~/Dir -rw-r--r-- 1 src wheel 9915957 Oct 27 14:58 /home/users/src/Dir tty ad0 ad1 da0 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 9 365 9.14 6 0.05 12.08 6 0.07 121.91 0 0.00 2 0 1 0 97 0 1020 11.75 87 0.99 17.82 7 0.13 0.00 0 0.00 76 0 14 0 10 0 1005 8.54 262 2.19 52.94 23 1.21 0.00 0 0.00 61 0 29 1 9 0 893 7.54 184 1.36 85.76 34 2.82 0.00 0 0.00 53 0 32 1 14 0 551 3.35 265 0.87 9.38 4 0.04 0.00 0 0.00 47 0 33 1 19 0 594 6.81 201 1.33 37.82 4 0.14 0.00 0 0.00 54 0 16 0 30 0 1106 3.54 252 0.87 55.19 17 0.93 0.00 0 0.00 39 0 33 1 27 0 393 2.88 223 0.63 11.43 2 0.03 0.00 0 0.00 67 0 31 1 1 0 644 4.81 165 0.77 16.00 0 0.01 0.00 0 0.00 87 0 12 1 1 27 339 10.39 180 1.82 15.18 11 0.17 0.00 0 0.00 86 0 13 0 0 32 130 5.06 146 0.72 23.40 46 1.04 0.00 0 0.00 86 0 8 1 5 32 267 8.39 138 1.13 61.09 4 0.22 0.00 0 0.00 73 0 26 1 0 33 340 8.75 222 1.90 61.54 4 0.26 0.00 0 0.00 78 0 21 1 0 32 595 5.85 154 0.88 12.20 3 0.04 0.00 0 0.00 87 0 12 1 0 32 288 5.28 147 0.76 6.00 1 0.01 0.00 0 0.00 86 0 13 1 0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.0-Beta installation problem -- Unable to find /dev/ad0s1b
Tried to install from both 8.0-BETA{3, 4}-i386-dvd1.iso on a Phenom 9600
system and having
some disk problems.
The system is running 6.x and/or 7.2 FreeBSD (on different drives).
Disconnected rest drives and only left 7.2 drive in.
ad0: 76319MB Seagate ST3802110A 3.AAJ at ata0-master UDMA100
Boot 8.0-BETA3-i386-dvd1.iso and sees no partition at all on the 7.2 disk.
Boot back to 7.2 and everything works fine, so system has no hardware
problem.
Boot 8.0-BETA3-i386-dvd1.iso again, still sees no partition, so
reconfigured partition with
autoconfigure - A
512M for / on /dev/ad0s1a
about 4G for swap on /dev/ad0s1b
about 2.2G on /var
512M for /tmp
rest spaces are for /usr
After commit, installation says --
Unable to find device node for /dev/ad0s1b in /dev
The Creation of file system will abort.
OK
[Press enter or space]
Hit CR and see some other errors, then back to installation menu.
Reboot the system, 7.2 is gone.
Download 8.0-BETA4-i386-dvd1.iso and burned another DVD, also did verify
between DVD and ISO for OK.
Run installation from Beta4 DVD, the same problem presents again.
If my memory is correct, either 8.0-Beta1 or one version earlier than it
was working on this machine.
Is anything changed that requires different installation procedure? or
is this a bug introduced recently?
-Jin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
cc1: error: unrecognized command line option -mfdpic
This option -mfdpic is shown in manual page for gcc 4.1 or later -mfdpic Select the FDPIC ABI, that uses function descriptors to represent pointers to functions. Without any PIC/PIE-related options, it implies -fPIE. With -fpic or -fpie, it assumes GOT entries and small data are within a 12-bit range from the GOT base address; with -fPIC or -fPIE, GOT offsets are computed with 32 bits. With a bfin-elf target, this option implies -msim. However, tried all gcc 4.1.x, 4.2.x and 4.3.x with following test, and no one of them accept this option: %: echo #include stdio.h | gcc43 -mfdpic - -E cc1: error: unrecognized command line option -mfdpic # 1 stdin %: echo #include stdio.h | gcc43 -fdpic - -E cc1: error: unrecognized command line option -fdpic # 1 stdin where -dpic option is a voild option. Does anyone know why -mfdpic option is missing from gcc4.x in FreeBSD distribution? Is this due to some license issues? If so, what is the other option to subtitute it? Thanks, -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kdb and mouse are disabled on HP Pavilion dv5210us by X.org 7.4.1 (7.2-R)
Hi Saifi, Xorg 7.4_1 seems having some issues with dbus and hald. The -- Option AllowEmptyInput false -- is the must, but dbus and hald can cause system useless. On this laptop, I only run dbus and hald once. Then I disabled both of them and X window works well. On a couple of Desktop machines (4-core Phenom and Intel P4+506) with GeForce graphic cards, without dbus and halt, X Window run fine except no F-key works. Enable and run dbus and hald, All F-key work, but output device is almost dead. Top shows system is completely idle, but typing will not show on any xterm till the mouse is moving. For example, run TOP on a xterm, the entire window system has no thing change. The clock of on the upper right corner of the TOP xterm is stopped (actually is running, but no output to display). Once mouse is moving, the clock and top section are updated. Once mouse stops moving, then no thing is change (no output anywhere). Similar to the typing. Typing a command will not show on the Xterm still mouse is moved. About less than 5% of time, I can type and see the output right way. Without dbus and hald running, there is no such problem. Has anyone encountered the same problem? The other main difference between this xorg.conf and previous on is the Module section. This xorg.conf, generated by X -configure, has -- Load dri2 where previous one has -- Load GLcore. I am not sure if this is an issue. -Jin Saifi Khan wrote: On Sun, 17 May 2009, Jin Guojun[VFF] wrote: When installed FreeBSD 7.2 release with xorg-7.4.1, the X server does not work on HP Pavilion dv5210us laptop due to the key board and mouse are disabled somehow. Some Hot keys (Ctrl-Altr-F#) are working but mouse is not movable and cannot type in a Xterm. (**) ModulePath set to /usr/local/lib/xorg/modules (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling Mouse0 (WW) Disabling Keyboard0 Does anyone hasve an idea how to fix this problem? Both Xorg.0.log and xorg.conf are attached. Thanks, -Jin Hi Jin: You need to add an additional line to your 'ServerLayout' or 'ServerFlags'. Option AllowEmptyInput false Please see the sample xorg.conf file that i'm running on my Compaq laptop. Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceKeyboard0 CoreKeyboard InputDeviceMouse0 CorePointer # InputDeviceMouse1 SendCoreEvents EndSection Section ServerFlags Option DontZap Off Option AllowEmptyInput false Option AllowEmptyInput false # Option AllowMouseOpenFail on EndSection Section Files FontPathunix/:7101 FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/URW/ FontPath /usr/local/lib/X11/fonts/bistream-vera/ FontPath /usr/local/lib/X11/fonts/cyrillic/ FontPath /usr/local/lib/X11/fonts/dejavu/ FontPath /usr/local/lib/X11/fonts/freefont/ FontPath /usr/local/lib/X11/fonts/local/ FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/terminus-font/ FontPath /usr/local/lib/X11/fonts/urwfonts-ttf/ FontPath /usr/local/lib/X11/fonts/util/ FontPath /usr/local/lib/X11/fonts/webfonts/ FontPath /usr/local/share/ghostscript/fonts/ FontPath /usr/local/lib/X11/fonts/sharefont/ FontPath /usr/local/lib/X11/fonts/texcm-ttf/ FontPath /usr/local/lib/X11/fonts/local/sgi/ FontPath /usr/local/lib/X11/fonts/ppantsfonts/ ModulePath /usr/local/lib/xorg/modules EndSection Section Module Load extmod Load record Load dbe Load glx Load dri Load dri2 Loadfreetype EndSection Section InputDevice Identifier Keyboard0 Driver kbd Option ProtocolStandard Option XkbLayout us Option XkbModelpc104 EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection Section InputDevice Identifier Mouse1 Driver synaptics Option Device /dev/sysmouse Option Emulate3Buttons on Option SHMConfig on Option ZAxisMapping 4 5 EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model HorizSync30-62 VertRefresh 50-60 Option DPMS EndSection Section
kdb and mouse are disabled on HP Pavilion dv5210us by X.org 7.4.1 (7.2-R)
When installed FreeBSD 7.2 release with xorg-7.4.1, the X server does not work on HP Pavilion dv5210us laptop due to the key board and mouse are disabled somehow. Some Hot keys (Ctrl-Altr-F#) are working but mouse is not movable and cannot type in a Xterm. (**) ModulePath set to /usr/local/lib/xorg/modules (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling Mouse0 (WW) Disabling Keyboard0 Does anyone hasve an idea how to fix this problem? Both Xorg.0.log and xorg.conf are attached. Thanks, -Jin X.Org X Server 1.6.0 Release Date: 2009-2-25 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.2-PRERELEASE i386 Current Operating System: FreeBSD mobile32.Belkin 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 22 April 2009 02:40:51PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. 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: Sun May 17 10:02:22 2009 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout X.org Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Automatically adding devices (==) Automatically enabling devices (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, built-ins (**) ModulePath set to /usr/local/lib/xorg/modules (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling Mouse0 (WW) Disabling Keyboard0 (II) Loader magic: 0x6a0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0...@1:5:0) ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE) rev 0, Mem @ 0xc800/134217728, 0xc010/65536, I/O @ 0x9000/256, BIOS @ 0x/65536 (II) System resource ranges: [0] -1 0 0x000f - 0x000f (0x1) MX[B] [1] -1 0 0x000c - 0x000e (0x3) MX[B] [2] -1 0 0x - 0x0009 (0xa) MX[B] [3] -1 0 0x - 0x (0x1) IX[B] [4] -1 0 0x - 0x00ff (0x100) IX[B] (II) extmod will be loaded. This was enabled by default and also specified in the config file. (II) dbe will be loaded. This was enabled by default and also specified in the config file. (II) glx will be loaded. This was enabled by default and also specified in the config file. (II) record will be loaded. This was enabled by default and also specified in the config file. (II) dri will be loaded. This was enabled by default and also specified in the config file. (II) dri2 will be loaded. This was enabled by default and also specified in the config file. (II) LoadModule: dbe (II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.6.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: dri (II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor=X.Org Foundation compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: dri2 (II) Loading /usr/local/lib/xorg/modules/extensions//libdri2.so (II) Module dri2: vendor=X.Org Foundation compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (II) LoadModule: extmod (II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.6.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension
Re: Really strange resolution problems on xorg with a laptop
Has this problem been resolved? I have the same problem for a similar laptop (HP Pavilion dv5120us). The X Server 1.4.0 (FreeBSD 6.3-R) works fine, but 1.4.2 (From both 6.4 and 7.1) produce this problem. My screen is 13.25 inch x 8.25 inch in resolution 1280x800. The DPI shown in Xorg.0.log is (96, 96), which is correct according to the dpi expression listed below. Only strange # from the Xorg.0.log is the screen size 310 x 21. The screen size should be 330 x 301, which is corrected stated in xorg.conf. I wonder if this is a X Server 1.4.2 bug. Is anyway to correct this problem? or X 1.4.0 has to be used for this particular laptop till a new X Server released. -Jin - original message - On Wed, 24 Dec 2008 16:22:40 -0500, Aryeh M. Friedman aryeh.fried...@gmail.com wrote: Polytropon wrote: Check the DPI settings from your monitor and if they match the settings in xorg.conf. Some programs calculate font sizes according to these values. How do I check that... Eventually there's a setting in /etc/X11/xorg.conf called DisplaySize that does not match the display size of the monitor. Take a ruler and check. Then, calculate the dpi resolution from what the manufacturer says about the amount of pixels in X and Y (e. g. 1200x800). physical pixels x dpi(x) = - display width in inch and physical pixels y dpi(y) = -- display height in inch The dpi resolution chosen by the X server can be determined by % grep DPI /var/log/Xorg.0.log This should match the reality. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
install 6.4 on Dell OPTIPLEX 755 panics
Install 6.4 from DVD on DELL Optiplex 755 (Core 2 DUE E6550 CPU with 2GB memory) always panic at last stage of boot. Is this a hardware specific (this machine only) issue? or is it a known hardware problem for DELL Optiplex 755? Disable ACPI does not help. Also noticed that 6.4 did not detect second core on this machine. -Jin -- md0: Preload image /boot/mfsboot 4423680 bytes at 0xc0bc79dc ad8: 238418MB Seagate ST3250820AS 3.ADG at ata4-master SATA300 acd0: DVDROM TSSTcorpDVD-ROM TS-H353B/D200 at ata5-master SATA150 acd1: DVDR PBDS DVD+/-RW DH-16W1S/2D14 at ata6-master SATA150 umass0: at uhub6 port 2 (addr 2) disconected Fatal trap 12: page fault while in kernel mode fault virtual address= 0x20 fault code = supervisor read, page not present instruction pointer = 0x20:0xc045d1f6 stack pointer= 0x28:0xe56c8c64 frame pointer= 0x28:0xe56c8c68 code segment = base 0x0, limit 0d, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 1 current process = 11 (swi4: clock sio) trap number = 12 panic: page fault ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: some ipfw filter does not function under Release 6.3
Ian Smith wrote: On Sat, 15 Nov 2008, Jin Guojun[VFF] wrote: I think this is a bug in ipfw because after change the rule order, the problem persists: 0056626 3090 deny ip from 221.192.199.36 to any 65330 2018 983473 allow tcp from any to any established 65535 00 deny ip from any to any Are you saying that the packets shown below from 221.192.199.36 arrived =after= you added rule 566, which denys all traffic from that address? Are you showing us your entire ruleset; it is just those three rules? Is the tcpdump shown running on the same box as ipfw, or another box? If another box, how is it connected through the firewall, to the net? Which machine performs NAT for your network? None of this is obvious. Please show output of 'ifconfig' and 'netstat -rn' on the ipfw box? Let's clear this little bit. Above rule order actually worked after machine is rebooted. I do not know whay it was not working when changed rule 65330 from 00330. This may be another bug. But again, after rebooting the machine, this rule order works. This demonstrates that rule order 00330 did not block the Sync packet as it supposed to do. You also mentioned and confirmed it should do in this way below, -- working order - 0056626 3090 deny ip from 221.192.199.36 to any 65330 2018 983473 allow tcp from any to any established 65535 00 deny ip from any to any -- Non working order - 00330 2018 983473 allow tcp from any to any established 00566 00 deny ip from 221.192.199.36 to any 65535 00 deny ip from any to any -- In general the first matching rule is the one that is applied. In your case this means that if a packet matches your rule 330 then it will be allowed through, and the rules further down the list will not be considered. Erik is right; you'll have to deny unwanted traffic before allowing the established traffic. 'established' here really means 'not setup', ie not SYN-only packets; ipfw doesn't track TCP sessions, the stack does. We see this (Sync only packet) passed through, so this is the problem. Because once Sync packet is passed through, the receiver will respond Sync/ACK, then attacker knows the machine is in service. People can send bogus established packets, and though they won't have a socket to connect to, they're still inbound traffic you have to receive to even block, which can consume bandwidth and perhaps money. We saw this too, from 221.192.199.36, but I did not complain for this. Becasue we do not bother since receiving machine will not respond it. Attacker also sends bogus Reset packets, and the FreeBSD ignores it too. So, this is not the problem. Sometimes these are a result of someone sending TCP setup packets to some other host, with the source address forged as yours .. you get the SYN+ACK packets, which do pass as established through ipfw. It's possible that the host you see as attacking you may itself be victim .. Yes, did I read your PR .. no sign of that host here so far, so it might just be scanning networks a bit closer to home: http://www.iptools.com/dnstools.php?tool=ipwhoisuser_data=221.192.199.36submit=Go It does not matter if this is a fake machine or victim machine, ipfw should always block it as instructed to do so. We cannot give it mercy and let it pass through becasue it is a victim. Otherwise, we will be the victim :-) That is why I filed PR for problem for rule order 00330-00566-65535. I did not say rule order 00566-65330-65535 is the problem in the PR. Hopefully, this makes clear. BTW, the ipfw machine is the gateway (between WAN-LAN). Rest machines are behind it on LAN. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: some ipfw filter does not function under Release 6.3
Ian Smith wrote: On Sun, 16 Nov 2008, Jin Guojun[VFF] wrote: Ian Smith wrote: On Sat, 15 Nov 2008, Jin Guojun[VFF] wrote: I think this is a bug in ipfw because after change the rule order, the problem persists: 0056626 3090 deny ip from 221.192.199.36 to any 65330 2018 983473 allow tcp from any to any established 65535 00 deny ip from any to any snapped I have found the problem due to the NIC naming change after motherboard upgrading. The em0 was LAN port, but now it is WAN port. So, the following rule caused Sync coming in: 00123 12 528 allow tcp from any to 192.168.0.0/16 via em0 setup Ahah! This is my configuration fault, and we can close PR kern/128902. Thanks, -Jin Glad you found it so soon, Jin; that was one very short-lived PR :) This is kind hard one to catch since this machine was tested and working before. Traced many machines with R-6.1 and R-6.2 around country and found no problem. The recent change to this machine is a AMD to a P4 motherboard swapping for better memory bandwidth, but overlooked the NIC names changed. Now we had historical information for what could cause such failure. -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
some ipfw filter does not function under Release 6.3
Below is set of ipfw rules, but it seems that not all rules are functioning properly. From rule 361 to first two of rule 567 are not blocking any traffic and not measuring any traffic. Is this bacuse tcp rule )330) can overwrite the ip rule? or this is a known issue in R-6.3? The second and third rules in rule set 567 seem working well. -Jin ipfw rule sets - 00330 3108378 2700826874 allow tcp from any to any established 00361 0 0 deny ip from 203.83.248.93 to any 00361 0 0 deny ip from 72.30.142.215 to any 00567 0 0 deny ip from 193.200.241.171 to any 00567 0 0 deny ip from 221.192.199.36 to any 00567 3180 deny ip from 118.153.18.186 to any 00567 3180 deny ip from 203.78.214.180 to any 00567 0 0 deny ip from 118.219.232.123 to any 65500 220 20043 allow udp from any to any 65535 2120 deny ip from any to any -- traffic captured by tcpdump behind ipfw machine - 04:12:20.940095 IP 221.192.199.36.12200 192.168.2.14.80: S 200229998:200229998(0) win 8192 04:12:21.204430 IP 221.192.199.36.12200 192.168.2.14.80: R 20022:20022(0) win 0 04:31:16.262402 IP 221.192.199.36.12200 192.168.2.14.80: S 200233658:200233658(0) win 8192 04:31:16.541868 IP 221.192.199.36.12200 192.168.2.14.80: R 200233659:200233659(0) win 0 05:27:04.031434 IP 221.192.199.36.12200 192.168.2.14.80: S 200244634:200244634(0) win 8192 05:27:04.303262 IP 221.192.199.36.12200 192.168.2.14.80: R 200244635:200244635(0) win 0 05:28:18.099443 IP 221.192.199.36.3362 192.168.2.14.80: S 2422872529:2422872529(0) win 65535 mss 1452,nop,nop,sackOK 05:28:18.352083 IP 221.192.199.36.3362 192.168.2.14.80: . ack 3968474717 win 65535 05:28:18.367745 IP 221.192.199.36.3362 192.168.2.14.80: P 0:205(205) ack 1 win 65535 05:28:18.621538 IP 221.192.199.36.3362 192.168.2.14.80: R 205:205(0) ack 473 win 0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: some ipfw filter does not function under Release 6.3
But the rule 330 should only allow established TCP pass through. In other words, Sync should NOT allowed by rule 330, or I missed something for this rule? Erik Trulsson wrote: On Sat, Nov 15, 2008 at 01:38:02PM -0800, Jin Guojun[VFF] wrote: Below is set of ipfw rules, but it seems that not all rules are functioning properly. From rule 361 to first two of rule 567 are not blocking any traffic and not measuring any traffic. Is this bacuse tcp rule )330) can overwrite the ip rule? or this is a known issue in R-6.3? In general the first matching rule is the one that is applied. In your case this means that if a packet matches your rule 330 then it will be allowed through, and the rules further down the list will not be considered. The second and third rules in rule set 567 seem working well. -Jin ipfw rule sets - 00330 3108378 2700826874 allow tcp from any to any established 00361 0 0 deny ip from 203.83.248.93 to any 00361 0 0 deny ip from 72.30.142.215 to any 00567 0 0 deny ip from 193.200.241.171 to any 00567 0 0 deny ip from 221.192.199.36 to any 00567 3180 deny ip from 118.153.18.186 to any 00567 3180 deny ip from 203.78.214.180 to any 00567 0 0 deny ip from 118.219.232.123 to any 65500 220 20043 allow udp from any to any 65535 2120 deny ip from any to any -- traffic captured by tcpdump behind ipfw machine - 04:12:20.940095 IP 221.192.199.36.12200 192.168.2.14.80: S 200229998:200229998(0) win 8192 04:12:21.204430 IP 221.192.199.36.12200 192.168.2.14.80: R 20022:20022(0) win 0 04:31:16.262402 IP 221.192.199.36.12200 192.168.2.14.80: S 200233658:200233658(0) win 8192 04:31:16.541868 IP 221.192.199.36.12200 192.168.2.14.80: R 200233659:200233659(0) win 0 05:27:04.031434 IP 221.192.199.36.12200 192.168.2.14.80: S 200244634:200244634(0) win 8192 05:27:04.303262 IP 221.192.199.36.12200 192.168.2.14.80: R 200244635:200244635(0) win 0 05:28:18.099443 IP 221.192.199.36.3362 192.168.2.14.80: S 2422872529:2422872529(0) win 65535 mss 1452,nop,nop,sackOK 05:28:18.352083 IP 221.192.199.36.3362 192.168.2.14.80: . ack 3968474717 win 65535 05:28:18.367745 IP 221.192.199.36.3362 192.168.2.14.80: P 0:205(205) ack 1 win 65535 05:28:18.621538 IP 221.192.199.36.3362 192.168.2.14.80: R 205:205(0) ack 473 win 0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: some ipfw filter does not function under Release 6.3
I think this is a bug in ipfw because after change the rule order, the problem persists: 0056626 3090 deny ip from 221.192.199.36 to any 65330 2018 983473 allow tcp from any to any established 65535 00 deny ip from any to any 15:47:21.238720 IP 221.192.199.36.4469 192.168.2.14.80: S 3191960249:3191960249(0) win 65535 mss 1452,nop,nop,sackOK 15:47:21.238768 IP 192.168.2.14.80 221.192.199.36.4469: S 2102254306:2102254306(0) ack 3191960250 win 65535 mss 1460,sackOK,eol 15:47:21.483754 IP 221.192.199.36.4469 192.168.2.14.80: . ack 1 win 65535 15:47:21.499489 IP 221.192.199.36.4469 192.168.2.14.80: P 1:206(205) ack 1 win 65535 15:47:24.238570 IP 192.168.2.14.80 221.192.199.36.4469: S 2102254306:2102254306(0) ack 3191960250 win 65535 mss 1460,sackOK,eol 15:47:24.482113 IP 221.192.199.36.4469 192.168.2.14.80: . ack 1 win 65535 15:47:24.498613 IP 221.192.199.36.4469 192.168.2.14.80: P 1:206(205) ack 1 win 65535 15:47:30.238574 IP 192.168.2.14.80 221.192.199.36.4469: S 2102254306:2102254306(0) ack 3191960250 win 65535 mss 1460,sackOK,eol 15:47:30.482746 IP 221.192.199.36.4469 192.168.2.14.80: . ack 1 win 65535 15:47:30.513193 IP 221.192.199.36.4469 192.168.2.14.80: P 1:206(205) ack 1 win 65535 15:47:42.238577 IP 192.168.2.14.80 221.192.199.36.4469: S 2102254306:2102254306(0) ack 3191960250 win 65535 mss 1460,sackOK,eol 15:47:42.435040 IP 221.192.199.36.4469 192.168.2.14.80: P 1:206(205) ack 1 win 65535 15:47:42.466055 IP 221.192.199.36.4469 192.168.2.14.80: . ack 1 win 65535 15:47:54.466599 IP 221.192.199.36.4469 192.168.2.14.80: P 1:206(205) ack 1 win 65535 15:47:59.703272 IP 221.192.199.36.4469 192.168.2.14.80: R 206:206(0) ack 1 win 0 Jin Guojun[VFF] wrote: But the rule 330 should only allow established TCP pass through. In other words, Sync should NOT allowed by rule 330, or I missed something for this rule? Erik Trulsson wrote: On Sat, Nov 15, 2008 at 01:38:02PM -0800, Jin Guojun[VFF] wrote: Below is set of ipfw rules, but it seems that not all rules are functioning properly. From rule 361 to first two of rule 567 are not blocking any traffic and not measuring any traffic. Is this bacuse tcp rule )330) can overwrite the ip rule? or this is a known issue in R-6.3? In general the first matching rule is the one that is applied. In your case this means that if a packet matches your rule 330 then it will be allowed through, and the rules further down the list will not be considered. The second and third rules in rule set 567 seem working well. -Jin ipfw rule sets - 00330 3108378 2700826874 allow tcp from any to any established 00361 0 0 deny ip from 203.83.248.93 to any 00361 0 0 deny ip from 72.30.142.215 to any 00567 0 0 deny ip from 193.200.241.171 to any 00567 0 0 deny ip from 221.192.199.36 to any 00567 3180 deny ip from 118.153.18.186 to any 00567 3180 deny ip from 203.78.214.180 to any 00567 0 0 deny ip from 118.219.232.123 to any 65500 220 20043 allow udp from any to any 65535 2120 deny ip from any to any -- traffic captured by tcpdump behind ipfw machine - 04:12:20.940095 IP 221.192.199.36.12200 192.168.2.14.80: S 200229998:200229998(0) win 8192 04:12:21.204430 IP 221.192.199.36.12200 192.168.2.14.80: R 20022:20022(0) win 0 04:31:16.262402 IP 221.192.199.36.12200 192.168.2.14.80: S 200233658:200233658(0) win 8192 04:31:16.541868 IP 221.192.199.36.12200 192.168.2.14.80: R 200233659:200233659(0) win 0 05:27:04.031434 IP 221.192.199.36.12200 192.168.2.14.80: S 200244634:200244634(0) win 8192 05:27:04.303262 IP 221.192.199.36.12200 192.168.2.14.80: R 200244635:200244635(0) win 0 05:28:18.099443 IP 221.192.199.36.3362 192.168.2.14.80: S 2422872529:2422872529(0) win 65535 mss 1452,nop,nop,sackOK 05:28:18.352083 IP 221.192.199.36.3362 192.168.2.14.80: . ack 3968474717 win 65535 05:28:18.367745 IP 221.192.199.36.3362 192.168.2.14.80: P 0:205(205) ack 1 win 65535 05:28:18.621538 IP 221.192.199.36.3362 192.168.2.14.80: R 205:205(0) ack 473 win 0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
where to find old ports.tar.gz files
I need to get wine 0.9.37 to 0.9.39 ports build structure, mainly the ports/emulatoes/wine/Makefile to build these wine releases on FreeBSD 6.3-R, but I cannot find older ports.tar.gz files. Does anyone know where I can find older ports.tar.gz files that contain wine 0.9.37 to 0.9.39 releases? Thanks, -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: where to find old ports.tar.gz files
[EMAIL PROTECTED] wrote: I need to get wine 0.9.37 to 0.9.39 ports build structure, mainly the ports/emulatoes/wine/Makefile http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/wine/ The page can select only tags with released FreeBSD version. Is there any way to select an intermediate version (tag)? -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: where to find old ports.tar.gz files
Erik Trulsson wrote: On Sun, Feb 03, 2008 at 10:46:20AM -0800, Jin Guojun [VFFS] wrote: I need to get wine 0.9.37 to 0.9.39 ports build structure, mainly the ports/emulatoes/wine/Makefile to build these wine releases on FreeBSD 6.3-R, but I cannot find older ports.tar.gz files. Does anyone know where I can find older ports.tar.gz files that contain wine 0.9.37 to 0.9.39 releases? Thanks, -Jin You can always pull any version of source files (including the ports tree) directly from the CVS repository. See http://www.freebsd.org/developers/cvs.html for information on how to do that. You will however not find any version of the ports tree that include Wine 0.9.37 or 0.9.38 because support for those versions were never added to the ports tree as far as I can tell. Yup, only 0.9.36 and 0.9.39 are there. Thanks, -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: where to find old ports.tar.gz files
[EMAIL PROTECTED] wrote: I need to get wine 0.9.37 to 0.9.39 ports build structure, mainly the ports/emulatoes/wine/Makefile http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/wine/ The page can select only tags with released FreeBSD version. Is there any way to select an intermediate version (tag)? Don't select tags. Click the Makefile link. Got it. Thanks, -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X -configure fails on 6.3-Release
Predrag Punosevac wrote: Jim Guojun [VFFS] wrote: After installed FreeBSD 6.3 on two machines, and X server cannot be started somehow on either one. Both X -configure and X -probeonly failed and errors are in attached file -- Xerr. Also, Xorg.o.log is attached. (EE) Failed to load module ati (module does not exist, 0) (EE) Failed to load module fbdev (module does not exist, 0) (EE) Failed to load module vesa (module does not exist, 0) (EE) Failed to load module vga (module does not exist, 0) (EE) Failed to load module mouse (module does not exist, 0) (EE) Failed to load module kbd (module does not exist, 0) (EE) No drivers available. How did you add Xorg? It looks like you are completely missing drivers. Did you reboot the computers after the XOrg was added. I did not add Xorg. From installation, I selected either 5 (X-Developer) or 7 (X-Kern-Developer). This is what older FreeBSD installation used to add X Window system. Is this an issue for 6.3 installation? I will try to add Xorg manually to see if this can fix the problem. -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X -configure fails on 6.3-Release
Manolis Kiagias wrote: Jim Guojun [VFFS] wrote: After installed FreeBSD 6.3 on two machines, and X server cannot be started somehow on either one. Both X -configure and X -probeonly failed and errors are in attached file -- Xerr. Also, Xorg.o.log is attached. Both machines run FreeBSD 6.2 and X works fine. I search wiki.x.org and freebsd list, but did not see any information related to this problem. Can someone tell me what is going wrong on my installation or X configuration? Thanks, -Jin I rarely install X from packages during install myself (I most always compile the entire Xorg from ports afterwards). But wanting to test my CDs, I did, and got the exact same result. It seems that when installing the Standard distribution with X, several parts are not selected (like xorg-drivers, which is causing this exact symptom. You will also find out there is no startx command). Maybe the installation does not take into account that Xorg is now modular? However, when you reach the question about installing packages, you can actually select the entire xorg-7.3 package and install it. This will take care of the problem. This was not a problem of installation on FreeBSD 6.2 and earlier. It looks like a bug in 6.3 installation process. It does not matter how to select X package from the selection menu, the drivers are not installed. -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X -configure fails on 6.3-Release
Predrag Punosevac wrote: Jin Guojun [VFFS] wrote: Predrag Punosevac wrote: Jim Guojun [VFFS] wrote: After installed FreeBSD 6.3 on two machines, and X server cannot be started somehow on either one. Both X -configure and X -probeonly failed and errors are in attached file -- Xerr. Also, Xorg.o.log is attached. (EE) Failed to load module ati (module does not exist, 0) (EE) Failed to load module fbdev (module does not exist, 0) (EE) Failed to load module vesa (module does not exist, 0) (EE) Failed to load module vga (module does not exist, 0) (EE) Failed to load module mouse (module does not exist, 0) (EE) Failed to load module kbd (module does not exist, 0) (EE) No drivers available. How did you add Xorg? It looks like you are completely missing drivers. Did you reboot the computers after the XOrg was added. I did not add Xorg. From installation, I selected either 5 (X-Developer) or 7 (X-Kern-Developer). This is what older FreeBSD installation used to add X Window system. That should be enough. Did you create initial xorg.conf.new file with Xorg -configure? Nop, X -configure does not work due to missing many X related packages. Is this an issue for 6.3 installation? I will try to add Xorg manually to see if this can fix the problem. -Jin I have no clue. I tried to play recently with 7.0 which is not as stable as 6.3. I wanted to use Miro. Xorg was properly installed and configured but it was crushing right after the start. The same machine is running OpenBSD 4.2 without any issues.I actually tried to start X even with VESA driver (normaly I would use i810) and very conservative options but aval:-(. It is 10 year old PIII. So nothing fancy. Manually adding Xorg package resolves the problem -- it installs everything. So, the problem is likely a 6.3 installation bug, but I wonder no one else complained it :-( Thanks for help, -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to enable touchpad for DELL Latitude 100L laptop
Installed FreeBSD 6.2 on a DELL Latitude 100L laptop but cannot get its touchpad configured. By searching the handbook, it looks like PSM is the device for the touchpad, so enabled verbose during the boot and see some errors for psm0: kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0:current command byte:0065 psm0: the aux port is not functioning (-1) atkdbc: atkbdc0 already exists: skipping it That is all messsage for the psm0, which is in turn not being configured. Then, I tried this laptop under Windows XP and the touchpad works fine. Is touchpad not the device psm? or something else I need to enable to configure the touchpad? Can anyone help to configure the touchpad on this laptop? TIA, -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how sys_select, sys_fork, ... are defined for thread libraries?
I am trying to understand how these __sys_xxx functions are defined for thread libraries. Following string search tells that all thread libraries are using these __sys_xxx functions, for example, __sys_select(). However, the search also shows that these functions are not defined anywhere in the entire source tree. /usr/src: findstring sys_select *.[hcS] total files= 21687 : pattern= sys_select rootdir= /usr/src regular mode: Thu Aug 2 13:31:40 PDT 2007 ./lib/libc_r/uthread/uthread_fork.c 91: * __sys_select: ./lib/libpthread/thread/thr_private.h 1264:int __sys_select(int, fd_set *, fd_set *, fd_set *, struct timeval *); ./lib/libpthread/thread/thr_select.c 61: ret = __sys_select(numfds, readfds, writefds, exceptfds, timeout); ./lib/libthr/thread/thr_private.h 805:int __sys_select(int, fd_set *, fd_set *, fd_set *, struct timeval *); ./lib/libthr/thread/thr_syscalls.c 435:ret = __sys_select(numfds, readfds, writefds, exceptfds, timeout); By searching the usr/lib objects, I found them in libc, but they are not in libc source tree. Can someone shed some light on how these system calls are built into libc and what is the different between standard syscall APIs and these __sys_syscall APIs, e.g., __sys_read() vs. read(), etc. Thanks, -Jin nm /usr/lib/libc.a | grep __sys_ 0008 T __sys_sigreturn 0008 T __sys_setlogin 0008 T __sys_reboot ... snapped 0008 T __sys_kse_release 0008 T __sys_kse_thr_interrupt 0008 T __sys_kse_create 0008 T __sys_kse_wakeup ... skipped 0008 T __sys_getdtablesize 0008 T __sys_select 0008 T __sys_ioctl 0008 T __sys_close 0008 T __sys_write 0008 T __sys_read 0008 T __sys___syscall ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what causes error -- ELF interpreter /libexec/ld-elf.so.1 not found
John Baldwin wrote: On Tuesday 12 June 2007 09:20:02 pm Jin Guojun wrote: John Baldwin wrote: On Saturday 09 June 2007 08:53:18 pm Jin Guojun [VFFS] wrote: I believe that this is a memory sub-system bug somewhere because anything equal to or below 1G options MAXDSIZ=(1024*1024*1024) will work regardless how many memory is installed in the system. I doubt this could be a hardware related issue although is memory size related. Finally find cause but no idea why -- in kernel configuration, following line causes the problem: options MAXDSIZ=(2097152U*1024) Can anyone explain why this can cause /libexec/ld-elf.so.1 not seen for some program? This is setting aside 2GB for malloc which leaves only 1GB for all of mmap and stack. You probably don't have enough address space to map your binary. This does not quite explain the problem. First of all, the MAXDSIZ is the maximum size for users to set their own datas ize limit by 'limit' utility. If user do not set a high limit for datasize, it should not be a pro blem. UTSL. By default proc0 gets a hard limit (lim_max vs lim_cur) of MAXDSIZ, and the max limit is what the ELF image activator in the kernel uses when figuring out where to mmap the runtime linker: /* * We load the dynamic linker where a userland call * to mmap(0, ...) would put it. The rationale behind this * calculation is that it leaves room for the heap to grow to * its maximum allowed size. */ addr = round_page((vm_offset_t)imgp-proc-p_vmspace-vm_daddr + lim_max(imgp-proc, RLIMIT_DATA)); The second aspect also counters this assumption, for machines that have less t han or equal to 1 GB memory, and setting the MAXDISZ = the maximum memory size will not cause such problem. For example, if the physical memory size is 512 MB, and setting MAXDSIZ=(512*1 024*1024) will not cause this problem. Or if the physical memory is 1GB, setting MAXDSIZ =(1024*1024*1024) will not cause the problem either. Umm, the amount of physical memory has no bearing on how the virtual address space for userland is laid out. Do you know what virtual memory is and how it works? Your first e-mail seems to contradict this paragraph as in your first e-mail you noted that the physical memory doesn't matter, the solution was to not raise MAXDSIZ higher than 1GB and that is consistent with running out of virtual address space due to MAXDSIZ reserving too much address space for malloc(). No quite clear on this. Does this mean that the MAXDSIZ cannot exceeed 1GB regardless how many physical memory (say 16 GB) is installed? Then, this is definitiely a software bug. Then, somewhere the following checking is needed: #if (MAXDSIZ 1024 * 1024 * 1024) #undef MAXDSIZ #define MAXDSIZ (1024 * 1024 * 1024) #endif ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what causes error -- ELF interpreter /libexec/ld-elf.so.1 not found
John Baldwin wrote: On Saturday 09 June 2007 08:53:18 pm Jin Guojun [VFFS] wrote: I believe that this is a memory sub-system bug somewhere because anything equal to or below 1G options MAXDSIZ=(1024*1024*1024) will work regardless how many memory is installed in the system. I doubt this could be a hardware related issue although is memory size related. Finally find cause but no idea why -- in kernel configuration, following line causes the problem: options MAXDSIZ=(2097152U*1024) Can anyone explain why this can cause /libexec/ld-elf.so.1 not seen for some program? This is setting aside 2GB for malloc which leaves only 1GB for all of mmap and stack. You probably don't have enough address space to map your binary. This does not quite explain the problem. First of all, the MAXDSIZ is the maximum size for users to set their own datasize limit by 'limit' utility. If user do not set a high limit for datasize, it should not be a problem. The second aspect also counters this assumption, for machines that have less than or equal to 1 GB memory, and setting the MAXDISZ = the maximum memory size will not cause such problem. For example, if the physical memory size is 512 MB, and setting MAXDSIZ=(512*1024*1024) will not cause this problem. Or if the physical memory is 1GB, setting MAXDSIZ=(1024*1024*1024) will not cause the problem either. I will try to build a similar system on an AMD box with 2GB and more memory to see if this will be a problem. -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
what causes error -- ELF interpreter /libexec/ld-elf.so.1 not found
I have multiple FreeBSD 6.2 machines with different hardware, but one of them encountered this strange error when running program wine. I could not figure out what causes such error since /libexec/ld-elf.so.1 absolutely exists, otherwise no program will run. It does not matter if the wine is pre-compiled in packages or I built it from ports. All other machine do NOT have such problem. I reinstalled this machine a few times, and it always does the same thing. However other programs run well. Would this is related to some particular hardware issue? This one is ECS 848P-A7 motherboard with Intel P4 506+ CPU, plus 2 GB memory. Other machines are HP AMD64 laptop, DELL Dual XEON, DELL Intel Laptop, and AMD XP 2100+, and none of them ever had such problem. 129 /data: ldd `which wine` /usr/local/bin/wine: ELF interpreter /libexec/ld-elf.so.1 not found /usr/local/bin/wine: signal 6 130 /data: ll /libexec/ld-elf.so.1 -r-xr-xr-x 1 root wheel 158712 Jan 11 23:39 /libexec/ld-elf.so.1* 131 /data: wine ELF interpreter /libexec/ld-elf.so.1 not found Abort 132 /data: which wine /usr/local/bin/wine Does someone have an idea what is happening here? -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what causes error -- ELF interpreter /libexec/ld-elf.so.1 not found
Finally find cause but no idea why -- in kernel configuration, following line causes the problem: options MAXDSIZ=(2097152U*1024) Can anyone explain why this can cause /libexec/ld-elf.so.1 not seen for some program? Jin Guojun [VFFS] wrote: I have multiple FreeBSD 6.2 machines with different hardware, but one of them encountered this strange error when running program wine. I could not figure out what causes such error since /libexec/ld-elf.so.1 absolutely exists, otherwise no program will run. It does not matter if the wine is pre-compiled in packages or I built it from ports. All other machine do NOT have such problem. I reinstalled this machine a few times, and it always does the same thing. However other programs run well. Would this is related to some particular hardware issue? This one is ECS 848P-A7 motherboard with Intel P4 506+ CPU, plus 2 GB memory. Other machines are HP AMD64 laptop, DELL Dual XEON, DELL Intel Laptop, and AMD XP 2100+, and none of them ever had such problem. 129 /data: ldd `which wine` /usr/local/bin/wine: ELF interpreter /libexec/ld-elf.so.1 not found /usr/local/bin/wine: signal 6 130 /data: ll /libexec/ld-elf.so.1 -r-xr-xr-x 1 root wheel 158712 Jan 11 23:39 /libexec/ld-elf.so.1* 131 /data: wine ELF interpreter /libexec/ld-elf.so.1 not found Abort 132 /data: which wine /usr/local/bin/wine Does someone have an idea what is happening here? -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what causes error -- ELF interpreter /libexec/ld-elf.so.1 not found
I believe that this is a memory sub-system bug somewhere because anything equal to or below 1G options MAXDSIZ=(1024*1024*1024) will work regardless how many memory is installed in the system. I doubt this could be a hardware related issue although is memory size related. Finally find cause but no idea why -- in kernel configuration, following line causes the problem: options MAXDSIZ=(2097152U*1024) Can anyone explain why this can cause /libexec/ld-elf.so.1 not seen for some program? Jin Guojun [VFFS] wrote: I have multiple FreeBSD 6.2 machines with different hardware, but one of them encountered this strange error when running program wine. I could not figure out what causes such error since /libexec/ld-elf.so.1 absolutely exists, otherwise no program will run. It does not matter if the wine is pre-compiled in packages or I built it from ports. All other machine do NOT have such problem. I reinstalled this machine a few times, and it always does the same thing. However other programs run well. Would this is related to some particular hardware issue? This one is ECS 848P-A7 motherboard with Intel P4 506+ CPU, plus 2 GB memory. Other machines are HP AMD64 laptop, DELL Dual XEON, DELL Intel Laptop, and AMD XP 2100+, and none of them ever had such problem. 129 /data: ldd `which wine` /usr/local/bin/wine: ELF interpreter /libexec/ld-elf.so.1 not found /usr/local/bin/wine: signal 6 130 /data: ll /libexec/ld-elf.so.1 -r-xr-xr-x 1 root wheel 158712 Jan 11 23:39 /libexec/ld-elf.so.1* 131 /data: wine ELF interpreter /libexec/ld-elf.so.1 not found Abort 132 /data: which wine /usr/local/bin/wine Does someone have an idea what is happening here? -Jin -- Jin Guojun --- v --- [EMAIL PROTECTED] --- Distributed Systems Department http://www.dsd.lbl.gov/~jin Lawrence Berkeley National Laboratory, Berkeley, CA 94720 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to make fixed Direct Access device (da) ID
It is awkward that dynamically and/or statically attaching SCSI hard drive and USB hard drive to the system will have different da IDs. For example, boot system with a SCSI drive (SCSI = 1), will have a da0 for this SCSI drive. Then plugging in a USB hard drive, which will be configured as da1. If boot system with both drives online, system will boot from SCSI drive fine till mounting root point. It fails because USB drive has da0 and SCSI drive has da1. Is there anyway to configure the system to have fixed da ID for SCSI drive or even for USB drive regardless if they are dynamically/statically attached to the system? -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to configue ssmtp for authentication?
Try to use send-pr but cannot get ssmtp to work with DSL ISP mail server, because ISP mail server requires password for authentication. I could not find information on how to configure SSMTP to pass password to the ISP mail server. Can someone tell me if SSMTP is possible to accomplish such task? or I need to use some other mail programs. TIA, -Jin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Any open issue on yppush from 4.9 to 4.10
It seems that pushing YP from 4.9 to 4.10 does not work. Case: YP master is 4.9 YP slave is 4.10 In 4.9 (master) host in /var/yp directory, typing make (with PUSH enabled), nothing is updated on 4.10 slave. Tcpdump shows that infinite data transfer happens between 4.9 and 4.10 hosts over YP ports. Just want to know if there is known problem on this issue before starting further investigation. Thanks in advance for any related information. -Jin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what things can cause yppasswd failure?
The 5.2.1-R does not have yppasswdd coredump problem, so this could be something in 5.1 only. We have found what trigged this problem. When installing bash in a FreeBSD system, it is installed in /usr/local/bin. To make it consistent with other OS platforms, we made a link from /usr/local/bin to /bin . However, /etc/shells only knows /usr/local/bin/bash on NIS server. When a user with /bin/bash changes passwd, it causes NIS failure. Since 5.2.1-R does not have problem on catching SIG 11, I think that this is no longer a problem. Thanks, -Jin Matthew Seaman wrote: On Tue, Apr 20, 2004 at 02:47:03PM -0700, Jin Guojun [NCS] wrote: Jin Guojun [NCS] wrote: We have experience very strange problem on using NIS over FreeBSD 4.x and 5.x. Some uses can change passwd where other users cannot. case 1:Use FreeBSD 5.1 as NIS server -- NIS client is a FreeBSD 4.9 host I can change my passwd any time and any where, and most people cannot. If I change my home directory to anywhere else in the master.passwd file, re-make in /var/yp directory, then I cannot change my passwd any more. It causes yppasswdd dying on signal 11, which most users encountered. case 2: Use FreeBSD 4.10-BETA as NIS server -- same NIS client I have no problem to change passwd, other users do. Failure will not kill yppasswdd, but it returns following error: passwd: failed to change NIS password: RPC: Server can't decode arguments After this message I still can change my passwd. Also, changing my home directory in /var/yp/master.passwd and re-making DO NOT AFFECT me to change passwd. By searching mail archive, I did not find related problem. This is what we found: If users login with bash, these users are not able to change their passwd. The error is: passwd: failed to change NIS password: RPC: Server can't decode arguments Probably bash is not part of default FreeBSD syste, NIS system has not been tested with bash for changing password. Interesting: nice work deducing that. This is clearly a bug -- certainly if rpc.yppasswdd dies with a SEGV, which should never happen. Please do report this problem via send-pr(1). However, I think there must be something different about your systems, as bash(1) is a popular shell and if this was a general problem I should think someone would have complained about it by now. Does this apply to other shells than bash -- eg zsh(1), ksh(1)? Does using the '-v' (verbose logging) flag on rpc.yppasswdd get you any more information? Does this still apply if there's an entry for bash in /etc/shells on the NIS server? Cheers, Matthew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
what things can cause yppasswd failure?
We have experience very strange problem on using NIS over FreeBSD 4.x and 5.x. Some uses can change passwd where other users cannot. case 1:Use FreeBSD 5.1 as NIS server -- NIS client is a FreeBSD 4.9 host I can change my passwd any time and any where, and most people cannot. If I change my home directory to anywhere else in the master.passwd file, re-make in /var/yp directory, then I cannot change my passwd any more. It causes yppasswdd dying on signal 11, which most users encountered. case 2: Use FreeBSD 4.10-BETA as NIS server -- same NIS client I have no problem to change passwd, other users do. Failure will not kill yppasswdd, but it returns following error: passwd: failed to change NIS password: RPC: Server can't decode arguments After this message I still can change my passwd. Also, changing my home directory in /var/yp/master.passwd and re-making DO NOT AFFECT me to change passwd. -- Does any one know what could cause such weird NIS problem? It seems not ENV related problem (may be). Is there some known NIS issues? -Jin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what things can cause yppasswd failure?
Jin Guojun [NCS] wrote: We have experience very strange problem on using NIS over FreeBSD 4.x and 5.x. Some uses can change passwd where other users cannot. case 1:Use FreeBSD 5.1 as NIS server -- NIS client is a FreeBSD 4.9 host I can change my passwd any time and any where, and most people cannot. If I change my home directory to anywhere else in the master.passwd file, re-make in /var/yp directory, then I cannot change my passwd any more. It causes yppasswdd dying on signal 11, which most users encountered. case 2: Use FreeBSD 4.10-BETA as NIS server -- same NIS client I have no problem to change passwd, other users do. Failure will not kill yppasswdd, but it returns following error: passwd: failed to change NIS password: RPC: Server can't decode arguments After this message I still can change my passwd. Also, changing my home directory in /var/yp/master.passwd and re-making DO NOT AFFECT me to change passwd. By searching mail archive, I did not find related problem. This is what we found: If users login with bash, these users are not able to change their passwd. The error is: passwd: failed to change NIS password: RPC: Server can't decode arguments Probably bash is not part of default FreeBSD syste, NIS system has not been tested with bash for changing password. -Jin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New parts for new PC (need help - little knowledge of hardware)
Patrick Proniewski wrote: On 18 nov. 2003, at 03:01, Bryan Cassidy wrote: Next is to choose a mother board. I am wanting a ASUS just because I hear alot of people talking about it on the forums, irc etc and think I would be happy with it. you will, as long as you do not choose a cheap ASUS (SiS chipset and controllers) For max performance and better FreeBSD support, choose a motherboard with Intel chipset (if you choose to go with a pentium of course, I've no experience with AMD) This is fairly incomplete information. What performance and what Intel chipset implied here? Providing helpful information should be positive. Unclear information with bias does not help. Intel 875 chipset (P4) may provide 2-time memory bandwidth than Nvidia (AMD). However, spending the same amount $ on both motherboards and CPUs, this AMD system may produce twice computation power than this Intel system. This is an important fact if $ is an issue. Intel has tried to release new BIOS every other week or a month to fix 875 chipset booting problem (rev 005 to 015) because different I/O peripheral combination can cause its BIOS hang (not funny, I never see such serious problem on system design). For example, swap CDrom and IDE drive, or add some I/O controller, or use different video card, etc., all can cause system be unable to start from BIOS. We bought a 875 system, but could not use it for almost 6 months till its BIOS rev 015 was out. What a horrible story. We did benchmark for some good motherboards. The table it no pretty, but it may be helpful: http://dsd.lbl.gov/~jin/performance.pen.ps -Jin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IBM 120 G IDE -- problems
Jonas wrote: I have the exact same problem with two brand new MB's from Asus. The model is P4P800 and P4P800-VM and all the drives are brand new Seagate IDE drives. I have removed the CD-ROM drive and the box boots up fine with Primary and Secondary master but as soon as I add a 3rd drive the boot process hangs on ata0 (or ata1) Resetting devices. Changing the drive to Cable-Select or putting the slave at the end of the cable doesn't fix the problem either. I'm going to call Asus tech support tomorrow but any thoughts suggestions are appreciated. My friend had similar problem on his M/B with Intel 865 chipset, which is P4P800 uses. Switching the CDROM and IDE drives around may solve the problem. Since I have no one, I cannot confirm. Try to update the BIOS with very caution because only vertain version may work properly. Here is another example on latest Intel 875 chipset-based M/B. It has very headache booting problem with adding devices. Intel released a number of BIOS to fix related problem, but ??? BIOS versions 05, 06, 08, 10 and 11 are hanging on various things during boot. 07 and 09 kindly work in general cases, but must have some other issues so making Intel keep to update the BIOS. BIOS version 12 is out, but it still hangs during boot, and we do not know why because two identical machines, one can boot, where the other cannot. Common hanging issues: CDROM may need to be the master instead of slave additional I/O card, such as certain video adapters, IDE or SCSI controllers, additional external disk drives may cause system hang. -Jin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sendmail.cf
Prior to FreeBSD-4.6 release, the sendmail.cf allows to gethering email from all local hosts to a central mail server by specify DH option DHcentralmailserver However, DH option no longer works in sendmail under current FreeBSD systems. What is the alterative option to do this? This option is useful because users are getting mail from the central mail server. However, they may send email from their desktop machine, and end up having email replied to their desktop machines. The mail replied to users' desktop machine may never be read or maybe read years later. -- Jin Guojun --- v --- [EMAIL PROTECTED] --- Distributed Systems Department http://www.itg.lbl.gov/~jin M/S 50B-2239Ph#:(510) 486-7531 Fax: 486-6363 Lawrence Berkeley National Laboratory, Berkeley, CA 94720 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
