Re: Spanish keyboard in X
El día Sunday, July 18, 2010 a las 11:32:05AM -0700, Leonardo M. Ramé escribió: Yes,I have modified xorg.conf the same way as you mentioned. Anyway, now the problem is solved by adding setxkbmap es to my .xsession Thanks. Leonardo M. Ramé http://leonardorame.blogspot.com A bit related to the question: If you need Spanish Tilde chars but you have only an English or German keyboard (like I have), you can make use of the so called WindowsKey in X11 and define the keys like shown below. After this, for example, the combination WindowsKey+a gives á (a-tilde). # $Id: xmod.sh,v 1.1 2008/08/25 10:04:41 guru Exp $ # # para español: # xmodmap -e keycode 0x73 = Mode_switch xmodmap -e keycode 0x39 = n N ntilde Ntilde xmodmap -e keycode 0x1a = e E eacute Eacute xmodmap -e keycode 0x26 = a A aacute Aacute xmodmap -e keycode 0x1f = i I iacute Iacute xmodmap -e keycode 0x1e = u U uacute Uacute xmodmap -e keycode 0x20 = o O oacute Oacute xmodmap -e keycode 0x14 = questiondown question backslash ssharp xmodmap -e keycode 0x0a = 1 exclam exclamdown onesuperior # xmodmap -e keycode 94 = less greater guillemotleft guillemotright bar brokenbar Espero que te ayude. Saludos matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Solidarity with the zionistic pirates of Israel? Not in my name! ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre! ___ 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
sockets stuck in use
I was working on an application I've been developing, and I closed the last instance a bit over 12 hours ago, but some of the sockets are still stuck in use: [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED Is there any way to get rid of them without restarting the machine? I was playing with sockopt SO_KEEPALIVE and SO_LINGER when I caused this issue.. Thanks, -Jim Stapleton ___ 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: utf8 characters in terminal
El día Sunday, July 18, 2010 a las 11:45:40AM -0700, Leonardo M. Ramé escribió: Hi, I installed Freebsd 8.1-RC2 in my home server to be used mainly as a file server, it used to have Ubuntu 9.10-Server installed on it, then I backed up (.tar.gz) the /home directory, that contains many spanish accented files and subdirectories in UTF8. Now, when I access this machine using ssh, some of those files include ?? and \303 or similar characters instead of the correct accents. What can I do to show the files in the correct way?. Leonardo M. Ramé http://leonardorame.blogspot.com I assume your are talking about the names of the files and dir (and not about the content). Check if the names contain correct UTF-8 encoding with something like: $ ls | od -t x1 | more The have UTF-8 inside the xterm you need somethink like this: Port xterm from the ports to get UTF-8 support: # cd /usr/ports/x11/xterm # make install WITH_256_COLOR=yes WITH_WIDE_CHARS=yes Then you may use: $ LANG=es_ES.UTF-8 xterm -T utf8 -fn 10x20 -sb -sl 1024 -cr blue HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Solidarity with the zionistic pirates of Israel? Not in my name! ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre! ___ 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: samba pam_smbpass passwd seg fault
Hi! On Mon, Jul 19, 2010 at 4:44 AM, Michael McGrew mmcgr...@mail.csuchico.edu wrote: I'm trying to sync the local unix account passwords to the samba smbpass db using pam. When i run passwd, after it's done it seg faults and produces a core dump. The odd thing is that it works, the users local unix password gets synced to the smbpass db, but it seg faults. Below are my relevant config files. Is this a bug or am I doing something wrong? The relevant information would be the version of the samba you are using and analysis of the coredump. Make sure your samba is compiled with debug information. Timur. ___ 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: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
On Sun, Jul 18, 2010 at 10:42 PM, David Brodbeck g...@gull.us wrote: On Jul 7, 2010, at 10:12 AM, David Brodbeck wrote: On Wed, July 7, 2010 2:20 am, mcoyles wrote: David - have a look here... http://lists.freebsd.org/pipermail/freebsd-current/2010-April/016405.html OK, I see. It looks like rtld is part of world, not a port, so then the question becomes, why didn't freebsd-update update it for me? Is there a way I can force a binary upgrade, or do I need to download the source and rebuild things that way? I ended up downloading the 7.3 livefs ISO, booting off of it, and replacing /libexec/ld-elf.so.1 with the one from the CD. That fixed the problem. I suspect the reason freebsd-update didn't upgrade it properly is it appears it's impossible to replace this file on a running system, even in single-user mode. Maybe there should be something in the release notes about a 7.2 - 7.3 upgrade being impossible to do properly except by booting from CD? make installworld happily does it, so can you - by renaming file to the *.old and then putting new on in it's place. So, it could be that freebsd-update isn't sophisticated enough to do such a trick. Timur. ___ 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: Xorg dumps core
On Sun, Jul 18, 2010 at 01:44:11PM +0100, Anton Shterenlikht wrote: I've seen this problem before, but on a complex configuration: Xorg running on FreeBSD spar64 and connecting via -query to clients running on FreeBSD ia64. Now I get this core dump on a simple amd64 installation, so I'm trying to provide a full report. On amd64 -current (r210043) I've xorg-server-1.7.5,1 xf86-video-ati-6.13.0 xdm-1.1.8_2 I start X with ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure in /etc/ttys I open ssh -XY connection to a linux server. I start an application (Paraview, www.paraview.org). When I close the Paraview normally - Xorg dumps core. After 1-2 seconds I'm back at the xdm login screen. Here's xdm.log % cat /val/log/xdm.log X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 9.0-CURRENT amd64 Current Operating System: FreeBSD mech-aslap239.men.bris.ac.uk 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r210043: Thu Jul 15 12:01:58 BST 2010 r...@mech-aslap239.men.bris.ac.uk:/usr/obj/usr/src/sys/BUZI amd64 Build Date: 16 June 2010 02:51:23PM Current version of pixman: 0.16.6 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 Jul 18 13:16:26 2010 (==) Using config file: /etc/X11/xorg.conf (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM [dri] Disabling DRI. XRANDR name: VGA-0 Connector: VGA CRT1: INTERNAL_KLDSCP_DAC1 DDC reg: 0x7e50 XRANDR name: LVDS Connector: LVDS LCD1: INTERNAL_LVTM1 DDC reg: 0x7e40 Dac detection success finished output detect: 0 finished output detect: 1 finished all detect Dac detection success Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Output CRT1 disable success Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Mode 1280x800 - 1440 823 10 Picked PLL 0 best_freq: 71152 best_feedback_div: 159 best_frac_feedback_div: 0 best_ref_div: 2 best_post_div: 16 Set CRTC 0 PLL success Set CRTC Timing success Set CRTC 0 Overscan success Not using RMX scaler 0 setup success Set CRTC 0 Source success crtc 0 YUV disable setup success Output digital setup success Output LCD1 enable success Enable CRTC 0 success Unblank CRTC 0 success Output CRT1 disable success Blank CRTC 1 success Disable CRTC 1 success record: RECORD extension enabled at configure time. record: This extension is known to be broken, disabling extension now.. record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 Bus error: 10 at address 0x802257ddb Fatal server error: Caught signal 10 (Bus error: 10). Server aborting 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. Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Enable CRTC 0 success Unblank CRTC 0 success XIO: fatal IO error 35 (Resource temporarily unavailable) on X server :0.0 after 131 requests (131 known processed) with 0 events remaining. xdm error (pid 1146): Server for display :0 terminated unexpectedly: 1536 Here's the gdb output: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... Core was generated by `Xorg'. Program terminated with signal 6, Aborted. Reading symbols from /usr/local/lib/libpciaccess.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpciaccess.so.0 Reading symbols from /usr/local/lib/libXfont.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXfont.so.1 Reading symbols from /usr/local/lib/libfreetype.so.9...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libfreetype.so.9 Reading symbols from /usr/local/lib/libfontenc.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libfontenc.so.1 Reading symbols from /lib/libz.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.6 Reading symbols from
Re: ipfw nat and jails on loopback - is it possible?
Michael wrote: Hello. Does anybody has a working configuration with ipfw nated jails on loopback interface? It simply doesn't work on my system. I can not get any connections to outside world from within a jail. FreeBSD 8.0-p3 amd64 laptop connected to internet via wlan0 (ath0) with 192.168.1.111 address. Jail with IP 127.127.127.1 aliased on lo0. Host system configuration: /etc/rc.conf ifconfig_wlan0=WPA DHCP ifconfig_lo0_alias0=inet 127.127.127.1 netmask 255.255.255.255 gateway_enable=YES firewall_enable=YES firewall_script=/etc/ipfw.rules firewall_nat_enable=YES firewall_nat_interface=wlan0 /etc/resolve.conf nameserver 208.67.222.222 nameserver 208.67.220.220 /etc/ipfw.conf ipfw -q -f flush ipfw add 1 allow all from 127.0.0.1 to 127.0.0.1 via lo0 ipfw add 2 nat 100 ip from 127.127.127.1 to any via wlan0 keep-state ipfw nat 100 config ip 192.168.1.111 ipfw add 3 allow all from any to any Jailed system configuration: /etc/rc.conf network_interfaces= /etc/resolve.conf nameserver 208.67.222.222 nameserver 208.67.220.220 Now I'm doing ssh into a jailed system (127.127.127.1). Then on jail system I'm trying to do for example: host freebsd.org ;; connection timed out; no servers could be reached And on host system: ipfw -d show 1 0 0 allow ip from 127.0.0.1 to 127.0.0.1 via lo0 2 4 228 nat 100 ip from 127.127.127.1 to any via wlan0 keep-state 3 182 24627 allow ip from any to any 65535 0 0 deny ip from any to any ## Dynamic rules (2): 2 157 (1s) STATE udp 127.127.127.1 58340 - 208.67.222.222 53 2 157 (2s) STATE udp 127.127.127.1 39870 - 208.67.220.220 53 So no packets got blocked but still it doesn't work properly. I'm trying to get it working for couple weeks now and I'm afraid I just run out of ideas so any help would be very appreciated. you have to put your hosts /etc/resolve.conf in each jail before you can get network connection. ___ 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.1-rc2 journal overflow error
Hello, I am using a hefty server with a single SSD drive as the main drive (Corsair CMFSSD-64D1). It worked nicely until today where I got a journal overflow error, i took a screenshot here: http://picasaweb.google.fr/frlinux/Computers#5495597160219915298 I am using a RAID array on a 3ware card (twa0: INFO: (0x15: 0x1300): Controller details:: Model 9650SE-24M8, 24 ports, Firmware FE9X 4.10.00.007, BIOS BE9X 4.08.00.002) where I have (12 drives attached to it). The RAID array seems healthy. I am using journal on the unit : GEOM_JOURNAL: Journal 3769207394: da0 contains data. GEOM_JOURNAL: Journal 3769207394: da0 contains journal. Root mount waiting for: GJOURNAL GEOM_JOURNAL: Journal da0 consistent. I have googled for a solution but have failed to find any. This server is a clean install of 8.1-rc2 where it used to host 7.2-RELEASE which was fairly stable (hardly a crash). So in short, anything I can do to help debug this problem? (dmesg below) Cheers, Steph Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RC2 #0: Tue Jun 29 20:21:55 UTC 2010 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5405 @ 2.00GHz (2004.98-MHz K8-class CPU) Origin = GenuineIntel Id = 0x1067a Family = 6 Model = 17 Stepping = 10 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x40ce33dSSE3,DTES64,MON,DS_CPL,VMX,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,XSAVE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 8226881536 (7845 MB) ACPI APIC Table: INTEL S5000PSL FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 acpi0: INTEL S5000PSL on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 acpi_button0: Sleep Button on acpi0 acpi_button1: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xca2,0xca3,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci2 pci3: ACPI PCI bus on pcib3 3ware device driver for 9000 series storage controllers, version: 3.70.05.001 twa0: 3ware 9000 series Storage Controller port 0x3000-0x30ff mem 0xb800-0xb9ff,0xba90-0xba900fff irq 16 at device 0.0 on pci3 twa0: [ITHREAD] twa0: INFO: (0x04: 0x0053): Battery capacity test is overdue: twa0: INFO: (0x15: 0x1300): Controller details:: Model 9650SE-24M8, 24 ports, Firmware FE9X 4.10.00.007, BIOS BE9X 4.08.00.002 pcib4: ACPI PCI-PCI bridge irq 18 at device 2.0 on pci2 pci4: ACPI PCI bus on pcib4 em0: Intel(R) PRO/1000 Network Connection 7.0.5 port 0x2020-0x203f mem 0xba82-0xba83,0xba40-0xba7f irq 18 at device 0.0 on pci4 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:15:17:82:b3:b8 em1: Intel(R) PRO/1000 Network Connection 7.0.5 port 0x2000-0x201f mem 0xba80-0xba81,0xba00-0xba3f irq 19 at device 0.1 on pci4 em1: Using MSI interrupt em1: [FILTER] em1: Ethernet address: 00:15:17:82:b3:b9 pcib5: ACPI PCI-PCI bridge at device 0.3 on pci1 pci5: ACPI PCI bus on pcib5 pcib6: PCI-PCI bridge at device 3.0 on pci0 pci6: PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 4.0 on pci0 pci7: ACPI PCI bus on pcib7 pcib8: ACPI PCI-PCI bridge at device 5.0 on pci0 pci8: ACPI PCI bus on pcib8 pcib9: ACPI PCI-PCI bridge at device 6.0 on pci0 pci9: ACPI PCI bus on pcib9 pcib10: PCI-PCI bridge at device 7.0 on pci0 pci10: PCI bus on pcib10 pci0: base peripheral at device 8.0 (no driver attached) pcib11: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci11: ACPI PCI bus on pcib11 uhci0: Intel 631XESB/632XESB/3100 USB controller USB-1 port 0x40a0-0x40bf irq 23 at device 29.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x2f00 usbus0: Intel 631XESB/632XESB/3100 USB controller USB-1 on uhci0 uhci1: Intel 631XESB/632XESB/3100 USB controller USB-2 port
8.1-rc2 journal overflow error
Hello, I am using a hefty server with a single SSD drive as the main drive (Corsair CMFSSD-64D1). It worked nicely until today where I got a journal overflow error, i took a screenshot here: http://picasaweb.google.fr/frlinux/Computers#5495597160219915298 I am using a RAID array on a 3ware card (twa0: INFO: (0x15: 0x1300): Controller details:: Model 9650SE-24M8, 24 ports, Firmware FE9X 4.10.00.007, BIOS BE9X 4.08.00.002) where I have (12 drives attached to it). The RAID array seems healthy. I am using journal on the unit : GEOM_JOURNAL: Journal 3769207394: da0 contains data. GEOM_JOURNAL: Journal 3769207394: da0 contains journal. Root mount waiting for: GJOURNAL GEOM_JOURNAL: Journal da0 consistent. I have googled for a solution but have failed to find any. This server is a clean install of 8.1-rc2 where it used to host 7.2-RELEASE which was fairly stable (hardly a crash). So in short, anything I can do to help debug this problem? (dmesg below) Cheers, Steph Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RC2 #0: Tue Jun 29 20:21:55 UTC 2010 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5405 @ 2.00GHz (2004.98-MHz K8-class CPU) Origin = GenuineIntel Id = 0x1067a Family = 6 Model = 17 Stepping = 10 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x40ce33dSSE3,DTES64,MON,DS_CPL,VMX,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,XSAVE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 8226881536 (7845 MB) ACPI APIC Table: INTEL S5000PSL FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 acpi0: INTEL S5000PSL on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 acpi_button0: Sleep Button on acpi0 acpi_button1: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xca2,0xca3,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci2 pci3: ACPI PCI bus on pcib3 3ware device driver for 9000 series storage controllers, version: 3.70.05.001 twa0: 3ware 9000 series Storage Controller port 0x3000-0x30ff mem 0xb800-0xb9ff,0xba90-0xba900fff irq 16 at device 0.0 on pci3 twa0: [ITHREAD] twa0: INFO: (0x04: 0x0053): Battery capacity test is overdue: twa0: INFO: (0x15: 0x1300): Controller details:: Model 9650SE-24M8, 24 ports, Firmware FE9X 4.10.00.007, BIOS BE9X 4.08.00.002 pcib4: ACPI PCI-PCI bridge irq 18 at device 2.0 on pci2 pci4: ACPI PCI bus on pcib4 em0: Intel(R) PRO/1000 Network Connection 7.0.5 port 0x2020-0x203f mem 0xba82-0xba83,0xba40-0xba7f irq 18 at device 0.0 on pci4 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:15:17:82:b3:b8 em1: Intel(R) PRO/1000 Network Connection 7.0.5 port 0x2000-0x201f mem 0xba80-0xba81,0xba00-0xba3f irq 19 at device 0.1 on pci4 em1: Using MSI interrupt em1: [FILTER] em1: Ethernet address: 00:15:17:82:b3:b9 pcib5: ACPI PCI-PCI bridge at device 0.3 on pci1 pci5: ACPI PCI bus on pcib5 pcib6: PCI-PCI bridge at device 3.0 on pci0 pci6: PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 4.0 on pci0 pci7: ACPI PCI bus on pcib7 pcib8: ACPI PCI-PCI bridge at device 5.0 on pci0 pci8: ACPI PCI bus on pcib8 pcib9: ACPI PCI-PCI bridge at device 6.0 on pci0 pci9: ACPI PCI bus on pcib9 pcib10: PCI-PCI bridge at device 7.0 on pci0 pci10: PCI bus on pcib10 pci0: base peripheral at device 8.0 (no driver attached) pcib11: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci11: ACPI PCI bus on pcib11 uhci0: Intel 631XESB/632XESB/3100 USB controller USB-1 port 0x40a0-0x40bf irq 23 at device 29.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x2f00 usbus0: Intel 631XESB/632XESB/3100 USB controller USB-1 on uhci0 uhci1: Intel 631XESB/632XESB/3100 USB controller
Re: Xorg dumps core
On Mon, Jul 19, 2010 at 09:50:13AM +0100, Anton Shterenlikht wrote: On Sun, Jul 18, 2010 at 01:44:11PM +0100, Anton Shterenlikht wrote: I've seen this problem before, but on a complex configuration: Xorg running on FreeBSD spar64 and connecting via -query to clients running on FreeBSD ia64. Now I get this core dump on a simple amd64 installation, so I'm trying to provide a full report. On amd64 -current (r210043) I've xorg-server-1.7.5,1 xf86-video-ati-6.13.0 xdm-1.1.8_2 I start X with ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure in /etc/ttys I open ssh -XY connection to a linux server. I start an application (Paraview, www.paraview.org). When I close the Paraview normally - Xorg dumps core. After 1-2 seconds I'm back at the xdm login screen. Here's xdm.log % cat /val/log/xdm.log X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 9.0-CURRENT amd64 Current Operating System: FreeBSD mech-aslap239.men.bris.ac.uk 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r210043: Thu Jul 15 12:01:58 BST 2010 r...@mech-aslap239.men.bris.ac.uk:/usr/obj/usr/src/sys/BUZI amd64 Build Date: 16 June 2010 02:51:23PM Current version of pixman: 0.16.6 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 Jul 18 13:16:26 2010 (==) Using config file: /etc/X11/xorg.conf (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM [dri] Disabling DRI. XRANDR name: VGA-0 Connector: VGA CRT1: INTERNAL_KLDSCP_DAC1 DDC reg: 0x7e50 XRANDR name: LVDS Connector: LVDS LCD1: INTERNAL_LVTM1 DDC reg: 0x7e40 Dac detection success finished output detect: 0 finished output detect: 1 finished all detect Dac detection success Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Output CRT1 disable success Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Mode 1280x800 - 1440 823 10 Picked PLL 0 best_freq: 71152 best_feedback_div: 159 best_frac_feedback_div: 0 best_ref_div: 2 best_post_div: 16 Set CRTC 0 PLL success Set CRTC Timing success Set CRTC 0 Overscan success Not using RMX scaler 0 setup success Set CRTC 0 Source success crtc 0 YUV disable setup success Output digital setup success Output LCD1 enable success Enable CRTC 0 success Unblank CRTC 0 success Output CRT1 disable success Blank CRTC 1 success Disable CRTC 1 success record: RECORD extension enabled at configure time. record: This extension is known to be broken, disabling extension now.. record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 Bus error: 10 at address 0x802257ddb Fatal server error: Caught signal 10 (Bus error: 10). Server aborting 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. Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Enable CRTC 0 success Unblank CRTC 0 success XIO: fatal IO error 35 (Resource temporarily unavailable) on X server :0.0 after 131 requests (131 known processed) with 0 events remaining. xdm error (pid 1146): Server for display :0 terminated unexpectedly: 1536 Here's the gdb output: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... Core was generated by `Xorg'. Program terminated with signal 6, Aborted. Reading symbols from /usr/local/lib/libpciaccess.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpciaccess.so.0 Reading symbols from /usr/local/lib/libXfont.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXfont.so.1 Reading symbols from /usr/local/lib/libfreetype.so.9...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libfreetype.so.9 Reading symbols from /usr/local/lib/libfontenc.so.1...(no debugging
nautilus crashing on right click properties
FreeBSD 8.1-PRERELEASE / amd64
Platform Version 4.4.5 (KDE 4.4.5)
I installed nautilus via the /usr/ports/sysutils/eiciel port. I can
start nautilus successfully, however, whenever I right click on a file
or directory and choose properties, nautilus crashes. I tried to
build it with debug support; however, I am not getting much info back.
This session was run under gdb.
Script started on Mon Jul 19 09:38:26 2010
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under
certain conditions. Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details. This GDB was configured as amd64-marcel-freebsd...
(gdb) rruunn
Starting program: /usr/home/gerard/nautilus
[New LWP 100093]
[New Thread 8058041c0 (LWP 100093)]
:1: error: unexpected character `\1', expected keyword - e.g. `style'
[New Thread 808c5d4c0 (LWP 100284)]
[New Thread 808c5cdc0 (LWP 100316)]
[Thread 808c5d4c0 (LWP 100284) exited]
[New Thread 808c5c500 (LWP 100284)]
[New Thread 808c5c340 (LWP 100386)]
[New Thread 808c5b8c0 (LWP 100417)]
[New Thread 808c5b700 (LWP 100419)]
[Thread 808c5c500 (LWP 100284) exited]
[Thread 808c5b700 (LWP 100419) exited]
[Thread 808c5b8c0 (LWP 100417) exited]
[Thread 808c5cdc0 (LWP 100316) exited]
[Thread 808c5c340 (LWP 100386) exited]
[New Thread 808c5d4c0 (LWP 100284)]
(nautilus:51180): GLib-CRITICAL **: g_hash_table_lookup: assertion
`hash_table != NULL' failed
(nautilus:51180): libgnomevfs-WARNING **: Internal error: the
configuration system was not initialized. Did you call
_gnome_vfs_configuration_init?
(nautilus:51180): GLib-CRITICAL **: g_hash_table_lookup: assertion
`hash_table != NULL' failed
(nautilus:51180): libgnomevfs-WARNING **: Internal error: the
configuration system was not initialized. Did you call
_gnome_vfs_configuration_init? **
Eel:ERROR:eel-wrap-table.c:494:wrap_table_get_num_fitting: assertion
failed: (max_child_size 0)
Program received signal SIGABRT, Aborted.
[Switching to Thread 8058041c0 (LWP 100093)]
0x0008052aad7c in thr_kill () from /lib/libc.so.7
(gdb) rruunn bbtt ffuu
#0 0x0008052aad7c in thr_kill () from /lib/libc.so.7
No symbol table info available.
#1 0x000805344b6b in abort () from /lib/libc.so.7
No symbol table info available.
#2 0x000803b46f35 in g_assertion_message ()
from /usr/local/lib/libglib-2.0.so.0 No symbol table info available.
#3 0x000803b474a2 in g_assertion_message_expr ()
from /usr/local/lib/libglib-2.0.so.0 No symbol table info available.
#4 0x005823bd in wrap_table_get_num_fitting (available=370,
spacing=0, max_child_size=0) at eel-wrap-table.c:494 num = 8
__PRETTY_FUNCTION__ = wrap_table_get_num_fitting
#5 0x00582570 in wrap_table_layout (wrap_table=0x8092f2b30) at
eel-wrap-table.c:521 iterator = (GList *) 0x7fffb770
pos = {x = 12, y = 12}
max_child_dimensions = {width = 0, height = 0}
content_bounds = {x0 = 12, y0 = 12, x1 = 382, y1 = 276}
num_cols = 8
__PRETTY_FUNCTION__ = wrap_table_layout
#6 0x005817f5 in eel_wrap_table_size_allocate
(widget=0x8092f2b30, allocation=0x7fffbaf0) at eel-wrap-table.c:312
wrap_table = (EelWrapTable *) 0x8092f2b30 __PRETTY_FUNCTION__ =
eel_wrap_table_size_allocate #7 0x0008038add8a in
g_closure_invoke () from /usr/local/lib/libgobject-2.0.so.0 No symbol
table info available. #8 0x0008038c14a7 in g_signal_parse_name ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#9 0x0008038c36c2 in g_signal_emit_valist ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#10 0x0008038c3ad3 in g_signal_emit ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#11 0x0008014e6008 in gtk_widget_size_allocate ()
from /usr/local/lib/libgtk-x11-2.0.so.0 No symbol table info available.
#12 0x0008014dd99e in gtk_viewport_new ()
from /usr/local/lib/libgtk-x11-2.0.so.0 No symbol table info available.
#13 0x0008038add8a in g_closure_invoke ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#14 0x0008038c14a7 in g_signal_parse_name ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#15 0x0008038c36c2 in g_signal_emit_valist ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#16 0x0008038c3ad3 in g_signal_emit ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#17 0x0008014e6008 in gtk_widget_size_allocate ()
from /usr/local/lib/libgtk-x11-2.0.so.0 No symbol table info available.
#18 0x00080143240c in gtk_scrolled_window_new ()
from /usr/local/lib/libgtk-x11-2.0.so.0 No symbol table info available.
#19 0x0008038add8a in g_closure_invoke ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#20
Re: sockets stuck in use
Jim stapleton...@gmail.com writes: I was working on an application I've been developing, and I closed the last instance a bit over 12 hours ago, but some of the sockets are still stuck in use: [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED Is there any way to get rid of them without restarting the machine? I was playing with sockopt SO_KEEPALIVE and SO_LINGER when I caused this issue.. Does tcpdrop(8) help? ___ 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: Xorg dumps core
On Mon, Jul 19, 2010 at 03:55:33PM +0200, Gary Jennejohn wrote: On Mon, 19 Jul 2010 14:28:31 +0100 Anton Shterenlikht me...@bristol.ac.uk wrote: How can I not load the GLX extension? The X logs indicate that this module is loaded by default. man xorg.conf in particular MODULE SECTION - Disable modulename Gary, thank you, I disabled glx and record. /var/log/Xorg.0.log has some funny messages: (WW) glx will not be loaded unless you've specified it to be loaded elsewhere. (WW) record will not be loaded unless you've specified it to be loaded elsewhere. (II) glx will be loaded even though the default is to disable it. (II) record will be loaded even though the default is to disable it. but I don't see the modules being reported as loaded after that. So I presume the above 2 info lines are plain wrong. many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: Xorg dumps core
On Mon, 19 Jul 2010 14:28:31 +0100 Anton Shterenlikht me...@bristol.ac.uk wrote: How can I not load the GLX extension? The X logs indicate that this module is loaded by default. man xorg.conf in particular MODULE SECTION - Disable modulename -- Gary Jennejohn ___ 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: Xorg dumps core
On Mon, Jul 19, 2010 at 02:28:31PM +0100, Anton Shterenlikht wrote: On Mon, Jul 19, 2010 at 09:50:13AM +0100, Anton Shterenlikht wrote: On Sun, Jul 18, 2010 at 01:44:11PM +0100, Anton Shterenlikht wrote: I've seen this problem before, but on a complex configuration: Xorg running on FreeBSD spar64 and connecting via -query to clients running on FreeBSD ia64. Now I get this core dump on a simple amd64 installation, so I'm trying to provide a full report. On amd64 -current (r210043) I've xorg-server-1.7.5,1 xf86-video-ati-6.13.0 xdm-1.1.8_2 I start X with ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure in /etc/ttys I open ssh -XY connection to a linux server. I start an application (Paraview, www.paraview.org). When I close the Paraview normally - Xorg dumps core. After 1-2 seconds I'm back at the xdm login screen. Here's xdm.log % cat /val/log/xdm.log X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 9.0-CURRENT amd64 Current Operating System: FreeBSD mech-aslap239.men.bris.ac.uk 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r210043: Thu Jul 15 12:01:58 BST 2010 r...@mech-aslap239.men.bris.ac.uk:/usr/obj/usr/src/sys/BUZI amd64 Build Date: 16 June 2010 02:51:23PM Current version of pixman: 0.16.6 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 Jul 18 13:16:26 2010 (==) Using config file: /etc/X11/xorg.conf (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM [dri] Disabling DRI. XRANDR name: VGA-0 Connector: VGA CRT1: INTERNAL_KLDSCP_DAC1 DDC reg: 0x7e50 XRANDR name: LVDS Connector: LVDS LCD1: INTERNAL_LVTM1 DDC reg: 0x7e40 Dac detection success finished output detect: 0 finished output detect: 1 finished all detect Dac detection success Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Output CRT1 disable success Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Mode 1280x800 - 1440 823 10 Picked PLL 0 best_freq: 71152 best_feedback_div: 159 best_frac_feedback_div: 0 best_ref_div: 2 best_post_div: 16 Set CRTC 0 PLL success Set CRTC Timing success Set CRTC 0 Overscan success Not using RMX scaler 0 setup success Set CRTC 0 Source success crtc 0 YUV disable setup success Output digital setup success Output LCD1 enable success Enable CRTC 0 success Unblank CRTC 0 success Output CRT1 disable success Blank CRTC 1 success Disable CRTC 1 success record: RECORD extension enabled at configure time. record: This extension is known to be broken, disabling extension now.. record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 Bus error: 10 at address 0x802257ddb Fatal server error: Caught signal 10 (Bus error: 10). Server aborting 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. Output LCD1 disable success Blank CRTC 0 success Disable CRTC 0 success Blank CRTC 1 success Disable CRTC 1 success Enable CRTC 0 success Unblank CRTC 0 success XIO: fatal IO error 35 (Resource temporarily unavailable) on X server :0.0 after 131 requests (131 known processed) with 0 events remaining. xdm error (pid 1146): Server for display :0 terminated unexpectedly: 1536 Here's the gdb output: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... Core was generated by `Xorg'. Program terminated with signal 6, Aborted. Reading symbols from /usr/local/lib/libpciaccess.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libpciaccess.so.0 Reading symbols from /usr/local/lib/libXfont.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/libXfont.so.1 Reading
Re: ipnat.conf - map and rdr won't work!
On Sat, Jul 17, 2010 at 7:51 AM, Erik Norgaard norga...@locolomo.org wrote: On 16/07/10 02.56, alexus wrote: su-3.2# cat /etc/ipnat.rules map fxp0 lama - 0/32 rdr fxp0 64.52.58.58 port ssh - lama port ssh tcp What's that first rule supposed to do? provides a NAT within jail Just guessing, try to put the rdr rule first. Another thing, the firewall/nat may be loaded before starting the jail and thus unaware of interfaces etc assigned to the jail. tried switching rules - didn't help tried restarting ipnat after everything is started it su-3.2# ifconfig vr0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 inet 172.16.172.16 netmask 0x broadcast 172.16.172.16 fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 inet 64.52.58.58 netmask 0xffe0 broadcast 64.52.58.63 Where is this? this su-3.2 is a bit confusing, would be useful to set your hostname to jail within the jail... su-3.2 is a host environment where jail is hosted And from within the jail, what do you see? From what I understand 172.16.172.16 is the jail IP? from host's rc.conf su-3.2# grep ^jail /etc/rc.conf jail_enable=YES jail_lama_devfs_enable=YES jail_lama_hostname=lama jail_lama_ip=172.16.172.16 jail_lama_rootdir=/usr/jail/lama jail_list=lama su-3.2# this is within jail -bash-3.2$ ifconfig vr0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=2808VLAN_MTU,WOL_UCAST,WOL_MAGIC ether 00:19:5b:68:9b:01 inet 172.16.172.16 netmask 0x broadcast 172.16.172.16 media: Ethernet autoselect (none) status: no carrier fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=2009RXCSUM,VLAN_MTU,WOL_MAGIC ether 00:0f:fe:aa:f4:61 media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT metric 0 mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 -bash-3.2$ I think it is typical for jails to clone the loopback interface for this setup. not sure what you mean by this... if you referring this statement as if you though this is jail itself then this is not jail this is host environment (where jail is hosted) Use tcpdump, you should see if your rdr/map rules work as expected. Also, pfctl -ss and similar. su-3.2# pfctl -ss pfctl: /dev/pf: No such file or directory su-3.2# Ah, you use ipfilter? yes, i use ipfilter ipnat su-3.2# grep ^ip /etc/rc.conf ipfilter_enable=YES ipmon_enable=YES ipnat_enable=YES su-3.2# i don't know how to use tcpdump, can you provide exact syntax so i can run it? The man-page is excelent. tried that, unfortunately not really sure what am i doing.. still anyone? If nobody replies, maybe try to rephrase your question, investigate further and provide additional information rather than just repost. i was under impression that i pretty much covered all basis, or at least i thought i so ... apparently not... Honestly, I don't have a clear picture of what works and what doesn't or where. You haven't posted your jail config from rc.conf and you could help by making it clear when running any command that this is in the jail, jail# this is on the hosting system hostname# and this is the client client# etc... BR, Erik lama is a jail environment (see rc.conf output from earlier) su-3.2 is a host environment any other questions? please just ask i'll provide you with whatever information is needed thanks again -- http://alexus.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.1-rc2 journal overflow error
On 07/19/10 15:16, FRLinux wrote: Hello, I am using a hefty server with a single SSD drive as the main drive (Corsair CMFSSD-64D1). It worked nicely until today where I got a journal overflow error, i took a screenshot here: http://picasaweb.google.fr/frlinux/Computers#5495597160219915298 There could be several reasons for this specific panic but as a general solution you will have to increase your journal size. For start, try doubling it. ___ 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
Is Mobile Intel HM57 Express chipset compatible with FreeBSD?
Hi all I'm planing to buy a Dell Vostro laptop which comes with a Mobile Intel HM57 Express chipset. Could I know from the list, is FreeBSD either 7.2 or 7.3 compatible with the above chipset? Above laptop comes with Nvidia Geforce 310M graphics chipset and I plan to install KDE 4.4 too, could I get a graphical desktop running FreeBSD 7 series? Many thanks in advance. Unga ___ 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.1-rc2 journal overflow error
On Mon, Jul 19, 2010 at 3:53 PM, Ivan Voras ivo...@freebsd.org wrote: There could be several reasons for this specific panic but as a general solution you will have to increase your journal size. For start, try doubling it. Thanks for this, i will look into it. I found the reason of the crash although I do not know why just yet. Apparently polling of munin plugins caused this. As soon as I disabled it, it no longer crashed. Cheers, Steph ___ 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: nautilus crashing on right click properties
On 7/19/10 9:49 AM, Jerry wrote:
FreeBSD 8.1-PRERELEASE / amd64
Platform Version 4.4.5 (KDE 4.4.5)
I installed nautilus via the /usr/ports/sysutils/eiciel port. I can
start nautilus successfully, however, whenever I right click on a file
or directory and choose properties, nautilus crashes. I tried to
build it with debug support; however, I am not getting much info back.
This session was run under gdb.
Script started on Mon Jul 19 09:38:26 2010
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under
certain conditions. Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details. This GDB was configured as amd64-marcel-freebsd...
(gdb) rruunn
Starting program: /usr/home/gerard/nautilus
[New LWP 100093]
[New Thread 8058041c0 (LWP 100093)]
:1: error: unexpected character `\1', expected keyword - e.g. `style'
[New Thread 808c5d4c0 (LWP 100284)]
[New Thread 808c5cdc0 (LWP 100316)]
[Thread 808c5d4c0 (LWP 100284) exited]
[New Thread 808c5c500 (LWP 100284)]
[New Thread 808c5c340 (LWP 100386)]
[New Thread 808c5b8c0 (LWP 100417)]
[New Thread 808c5b700 (LWP 100419)]
[Thread 808c5c500 (LWP 100284) exited]
[Thread 808c5b700 (LWP 100419) exited]
[Thread 808c5b8c0 (LWP 100417) exited]
[Thread 808c5cdc0 (LWP 100316) exited]
[Thread 808c5c340 (LWP 100386) exited]
[New Thread 808c5d4c0 (LWP 100284)]
(nautilus:51180): GLib-CRITICAL **: g_hash_table_lookup: assertion
`hash_table != NULL' failed
(nautilus:51180): libgnomevfs-WARNING **: Internal error: the
configuration system was not initialized. Did you call
_gnome_vfs_configuration_init?
(nautilus:51180): GLib-CRITICAL **: g_hash_table_lookup: assertion
`hash_table != NULL' failed
(nautilus:51180): libgnomevfs-WARNING **: Internal error: the
configuration system was not initialized. Did you call
_gnome_vfs_configuration_init? **
Eel:ERROR:eel-wrap-table.c:494:wrap_table_get_num_fitting: assertion
failed: (max_child_size 0)
Program received signal SIGABRT, Aborted.
[Switching to Thread 8058041c0 (LWP 100093)]
0x0008052aad7c in thr_kill () from /lib/libc.so.7
(gdb) rruunn bbtt ffuu
#0 0x0008052aad7c in thr_kill () from /lib/libc.so.7
No symbol table info available.
#1 0x000805344b6b in abort () from /lib/libc.so.7
No symbol table info available.
#2 0x000803b46f35 in g_assertion_message ()
from /usr/local/lib/libglib-2.0.so.0 No symbol table info available.
#3 0x000803b474a2 in g_assertion_message_expr ()
from /usr/local/lib/libglib-2.0.so.0 No symbol table info available.
#4 0x005823bd in wrap_table_get_num_fitting (available=370,
spacing=0, max_child_size=0) at eel-wrap-table.c:494 num = 8
__PRETTY_FUNCTION__ = wrap_table_get_num_fitting
#5 0x00582570 in wrap_table_layout (wrap_table=0x8092f2b30) at
eel-wrap-table.c:521 iterator = (GList *) 0x7fffb770
pos = {x = 12, y = 12}
max_child_dimensions = {width = 0, height = 0}
content_bounds = {x0 = 12, y0 = 12, x1 = 382, y1 = 276}
num_cols = 8
__PRETTY_FUNCTION__ = wrap_table_layout
#6 0x005817f5 in eel_wrap_table_size_allocate
(widget=0x8092f2b30, allocation=0x7fffbaf0) at eel-wrap-table.c:312
wrap_table = (EelWrapTable *) 0x8092f2b30 __PRETTY_FUNCTION__ =
eel_wrap_table_size_allocate #7 0x0008038add8a in
g_closure_invoke () from /usr/local/lib/libgobject-2.0.so.0 No symbol
table info available. #8 0x0008038c14a7 in g_signal_parse_name ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#9 0x0008038c36c2 in g_signal_emit_valist ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#10 0x0008038c3ad3 in g_signal_emit ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#11 0x0008014e6008 in gtk_widget_size_allocate ()
from /usr/local/lib/libgtk-x11-2.0.so.0 No symbol table info available.
#12 0x0008014dd99e in gtk_viewport_new ()
from /usr/local/lib/libgtk-x11-2.0.so.0 No symbol table info available.
#13 0x0008038add8a in g_closure_invoke ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#14 0x0008038c14a7 in g_signal_parse_name ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#15 0x0008038c36c2 in g_signal_emit_valist ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#16 0x0008038c3ad3 in g_signal_emit ()
from /usr/local/lib/libgobject-2.0.so.0 No symbol table info available.
#17 0x0008014e6008 in gtk_widget_size_allocate ()
from /usr/local/lib/libgtk-x11-2.0.so.0 No symbol table info available.
#18 0x00080143240c in gtk_scrolled_window_new ()
from /usr/local/lib/libgtk-x11-2.0.so.0 No symbol table info available.
#19
Re: ipnat.conf - map and rdr won't work!
On 19/07/10 16.46, alexus wrote: Use tcpdump, you should see if your rdr/map rules work as expected. Also, pfctl -ss and similar. i don't know how to use tcpdump, can you provide exact syntax so i can run it? The man-page is excelent. tried that, unfortunately not really sure what am i doing.. still Can't help you more, really, you need to investigate where packets are dropped, tcpdump is a great tool and the man-page is excelent, can't explain it better, if you don't like tcpdump then use any other packet sniffing tool at hand, snort for example. Do packets can get dropped because of your firewall default policy? For stealth it may be set to simply drop packets which result in a connection time-out rather than send a TCP-RST. Do packets get dropped because of nat on the way in? or on the way out? What if you just disable ipnat? What if you flush the firewall rules? (disconnect from the Internet first) Do you have any logs in the jail that indicate that the first packet is actually received? Do your firewall log connections? If not, see how you can enable logs on all rules to get more information. Can you connect out from the jail, to external servers? only to the jail hosting server? Did the jail's ssh log tell anything? You wrote you can connect with ssh from the hosting server to the jail, but it took a long time, did you investigate this? Is there some DNS issue that times out and causes the connection to fail? Can you ping your jail? Can you ping out? Default route is configured? There are tons of tests you can do to figure out what's failing. BR, Erik ___ 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: samba pam_smbpass passwd seg fault
Thank you for the response, I have the latest port version of samba, samba34-3.4.8. The core does not give much info here is a snippet of the end of the trace. Here is a link to the end of the truss trace of the process. http://mmcgrew.net/out #636 0x792f6e69622f7273 in ?? () #637 0x0064777373617070 in ?? () #638 0x247c8d48002454ff in ?? () #639 0x01a1c0c748006a10 in ?? () #640 0x66fdebf4050f in ?? () #641 0x90909066 in ?? () #642 0x7fffec18 in ?? () #643 0x0001 in ?? () #644 0x7fffec28 in ?? () #645 0x0010 in ?? () Cannot access memory at address 0x8000 /var/log/messages Jul 19 10:11:49 kernel: Jul 19 10:11:49 kernel: pid 58460 (passwd), uid 0: exited on signal 11 On Mon, Jul 19, 2010 at 1:31 AM, Timur I. Bakeyev ti...@com.bat.ru wrote: Hi! On Mon, Jul 19, 2010 at 4:44 AM, Michael McGrew mmcgr...@mail.csuchico.edu wrote: I'm trying to sync the local unix account passwords to the samba smbpass db using pam. When i run passwd, after it's done it seg faults and produces a core dump. The odd thing is that it works, the users local unix password gets synced to the smbpass db, but it seg faults. Below are my relevant config files. Is this a bug or am I doing something wrong? The relevant information would be the version of the samba you are using and analysis of the coredump. Make sure your samba is compiled with debug information. Timur. ___ 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: Has anybody got a *working* example of getpwnam_r() ??
Date: Mon, 19 Jul 2010 01:13:25 -0400 From: Brad Mettee bmet...@pchotshots.com Subject: Re: Has anybody got a *working* example of getpwnam_r() ?? Robert Bonomi wrote: I've _got_ to be doing something wrong, sine I'm getting heap corruption calling it. But for the life of me, I can't figure out -what- is wrong. [[.. sniparoo ..]] the offending call is : getpwnam_r(cp3, pw_data, buffer2, sizeof(buffer2), pwd); data declaration at the beginning of the function: char buffer[1024]; char buffer2[1024]; char mailbox[1024]; *cp,*cp2,*cp3,*cp4 = buffer; struct passwd pw_data,pw_data2,*pwd=pw_data2; int i; [[.. sneck gory details ..]] anybody got _any_ ideas? This might help. Just above the crashing call, open a file, and dump the contents of the vars you're sending to the function with fprintf, then close the file. I've verified everything with GDB immediately before the getwpnam_r() call. everyting is what I expect -- cp3 points to 'buffer' (*not* 'buffer2', the scratchpad buffer for the function) which has a valid username in it. (gdb instruction 'p *cp3' returns bonomi) And I checked things immediately _after_ the getpwnam_r() call. heap (not stack) corruption, out of the blue, at a CONSTANT location, regardless of changes to the input variables (value _or_ location). I suspect cp3 doesn't point to valid data and is causing the function call to fail (it looks like it's pointing to the same thing as buffer, which doesn't look like how the function should be called). Having the contents of the individual vars will help you narrow down exactly what's occuring. Data you want to see is the pointers themselves, and maybe the first 8 or so characters of data that it's pointing to. BTDT, GTTS. no joy. The call returns, signalling no error (return value zero), pw_data is filled in with the correct user information, and pwd is set to the address of (the passed-in parameter) pw_data. Everything is as it should be on a successful call -- *EXCEPT* for the unexpected corruption of the heap. Im in the position of His Majesty in 'The King and I'. I quote: Tis a *PUZZLEMENT*!! (emphasis added. wry grin) And if this doesn't help, there's always Google CodeSearch http://www.google.com/codesearch , for examples of how to call it. I apparently don't know how to use codesearch. All I get is various source-code for the function itself, not a 'how to use' illustration. Appreciate the thoughts. I'll re-iterate my query -- does anybody have a _working_ example _ON_FREEBSD_ of getpwnam_r() ?? I'm about at my wit's end -- short of re-compiling libc with a '-g', so I can trace through the library calls, and see what's happening 'underneath the covers', I can't thing of anything else to try. ___ 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
KDE won't start
Whenever I try to start KDE4, I get this output: # /usr/local/kde4/etc/rc.d/kdm4 start Startink kdm4. Updating KDM configuration Information: reading pre-existing kdmrc /usr/local/kde4/share/config/kdm/kdmrc (config version 2.4) # info: [drm] Setting GART location based on new memory map info: [drm] Loading RV710 Microcode info: [drm] Resetting GPU info: [drm] writeback test succeeded in 2 usecs drm0: [ITHREAD] Jul 19 03:59:47 FreeBSD kdm-bin: :0[28893]: Received unknown or unexpected command -2 from greeter Jul 19 03:59:47 FreeBSD kdm-bin: :0[28893]: Abnormal termination of greeter for display :0, code 125, signal 0 info: [drm] Resetting GPU The same thing happens when I try to run Gnome or Xfce. It all started when I accidentally deleted graphics/jpeg and graphics/png. I tried reinstalling them, but it didn't work. I have done portupgrade -a three times, but none of them helped. How can I fix this issue without having to reinstall? ___ 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: Has anybody got a *working* example of getpwnam_r() ??
Robert Bonomi wrote: snippage And if this doesn't help, there's always Google CodeSearch http://www.google.com/codesearch , for examples of how to call it. ALL I find at www.google.com/codesearch, when I ask for 'getpwnam_r' is source- code for the getpwnam_r function. Needless to say, that's =no= help. except for confirming that the parameters match what I'm doing. *sigh* Thanks for the thoughts, though. Here are a few links to FreeBSD code using the function: Search criteria for codesearch was: 'lang:c freebsd getpwnam_r' (it did take me a few minutes to sift through the samples vs the declarations). http://www.google.com/codesearch/p?hl=en#hv2-lQo77SI/nss_ldap-249/tests/testpw.cq=lang:%22c%22%20getpwnam_r%20freebsdsa=Ncd=7ct=rc http://www.google.com/codesearch/p?hl=en#-wKRNbYkeKI/pub/FreeBSD/distfiles/cadaver-0.22.5.tar.gz|DXHv6JvXDfo/cadaver-0.22.5/lib/glob.cq=lang:%22c%22%20getpwnam_r http://www.google.com/codesearch/p?hl=en#bQvTeDN3Ef0/dspam-3.6.5/src/pgsql_drv.cq=lang:%22c%22%20getpwnam_r%20freebsdsa=Ncd=14ct=rc Hope the links aren't too badly mangled by mail. ___ 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: KDE won't start
On 7/19/10 2:15 PM, Caleb Stein wrote: Whenever I try to start KDE4, I get this output: # /usr/local/kde4/etc/rc.d/kdm4 start Startink kdm4. Updating KDM configuration Information: reading pre-existing kdmrc /usr/local/kde4/share/config/kdm/kdmrc (config version 2.4) # info: [drm] Setting GART location based on new memory map info: [drm] Loading RV710 Microcode info: [drm] Resetting GPU info: [drm] writeback test succeeded in 2 usecs drm0: [ITHREAD] Jul 19 03:59:47 FreeBSD kdm-bin: :0[28893]: Received unknown or unexpected command -2 from greeter Jul 19 03:59:47 FreeBSD kdm-bin: :0[28893]: Abnormal termination of greeter for display :0, code 125, signal 0 info: [drm] Resetting GPU The same thing happens when I try to run Gnome or Xfce. It all started when I accidentally deleted graphics/jpeg and graphics/png. I tried reinstalling them, but it didn't work. I have done portupgrade -a three times, but none of them helped. How can I fix this issue without having to reinstall? Hello, If you reinstalled a newer version of jpeg and png, you will need to rebuild all ports that linked against them. Take a look at ports/UPDATING for portupgrade syntax. Regards, -- Glen Barber ___ 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: KDE won't start
On 7/19/10 2:21 PM, Glen Barber wrote: If you reinstalled a newer version of jpeg and png, you will need to rebuild all ports that linked against them. Take a look at ports/UPDATING for portupgrade syntax. Sorry, should have included the entry number - 20100328. Regards, -- Glen Barber ___ 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: KDE won't start
Hmmm, I may just reinstall. I updated KDE, GNOME, XFCE, jpeg, and png to the latest versions, and the desktops just won't start. I think I will just reinstall. On Mon, 19 Jul 2010 11:21:50 -0700, Glen Barber glen.j.bar...@gmail.com wrote: On 7/19/10 2:15 PM, Caleb Stein wrote: Whenever I try to start KDE4, I get this output: # /usr/local/kde4/etc/rc.d/kdm4 start Startink kdm4. Updating KDM configuration Information: reading pre-existing kdmrc /usr/local/kde4/share/config/kdm/kdmrc (config version 2.4) # info: [drm] Setting GART location based on new memory map info: [drm] Loading RV710 Microcode info: [drm] Resetting GPU info: [drm] writeback test succeeded in 2 usecs drm0: [ITHREAD] Jul 19 03:59:47 FreeBSD kdm-bin: :0[28893]: Received unknown or unexpected command -2 from greeter Jul 19 03:59:47 FreeBSD kdm-bin: :0[28893]: Abnormal termination of greeter for display :0, code 125, signal 0 info: [drm] Resetting GPU The same thing happens when I try to run Gnome or Xfce. It all started when I accidentally deleted graphics/jpeg and graphics/png. I tried reinstalling them, but it didn't work. I have done portupgrade -a three times, but none of them helped. How can I fix this issue without having to reinstall? Hello, If you reinstalled a newer version of jpeg and png, you will need to rebuild all ports that linked against them. Take a look at ports/UPDATING for portupgrade syntax. Regards, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why googleearth keeps crashing when photo window is closed?
On Wed, Jul 14, 2010 at 03:44:54AM -0700, Yuri wrote: For some reason googleearth crashes when the popup with photo is closed. Crashes are intermittent, depending on system updates and port updates. After some crashes disappear and after other updates crashes come back again. Hi! I didn't answer at first since my ports weren't up to date and I couldn't reproduce the issue, now after updating to latest ports and RELENG_8_1 (amd64) googleearth still seems to work just fine for me, only gl doesn't work since a) our linux versions of the gl-related libs are too old for my card (radeon r730pro i.e. HD 4650) and b) I'm on amd64 and I've been told the dri interface may be different between i386 and amd64 so the linuxolator could have issues emulating gl anyway. (or only with the xorg drivers since the nvidia blob may already be handling this problem?) Crash stack is below. Yuri Major Version 5 Minor Version 2 Build Number 0001 Build Date Jun 10 2010 Build Time 16:15:55 OS Type 3 OS Major Version 2 OS Minor Version 6 OS Build Version 16 OS Patch Version 0 Crash Signal 11 Crash Time 1279103869 Up Time 31.366 Stacktrace from glibc: ./libgoogleearth_free.so[0x33d3c30b] [0xbfbfffbb] ./libQtWebKit.so.4[0x34bf7f23] ./libQtWebKit.so.4[0x34bf7f5f] ./libQtWebKit.so.4[0x34bf7f79] ./libQtWebKit.so.4[0x34bf7fd3] ./libQtWebKit.so.4[0x34cb5da8] ./libQtWebKit.so.4[0x34cb5d1c] ./libQtWebKit.so.4[0x35057709] ./libQtWebKit.so.4[0x350577ad] ./libQtWebKit.so.4[0x3516a908] ./libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x112)[0x33fdbfca] ./libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xa0)[0x3423ae20] ./libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x22e)[0x34244962] ./libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x70)[0x33fcdd50] ./libQtCore.so.4[0x33ff3743] ./libQtCore.so.4(_ZN20QEventDispatcherUNIX14activateTimersEv+0x17)[0x33ff381f] ./libQtCore.so.4(_ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0xd9)[0x33ff39ed] ./libQtGui.so.4[0x342cfca4] ./libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x47)[0x33fccfbf] ./libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xff)[0x33fcd223] ./libQtCore.so.4(_ZN16QCoreApplication4execEv+0x9d)[0x33fcec05] ./libQtGui.so.4(_ZN12QApplication4execEv+0x25)[0x3423a7a1] ./libgoogleearth_free.so(_ZN5earth6client11Application3runEv+0x4bc)[0x33d4750c] ./libgoogleearth_free.so(earthmain+0x27d)[0x33d3b73d] ./googleearth-bin(_init+0x122)[0x80486c2] /lib/libc.so.6(__libc_start_main+0xe5)[0x358596e5] ./googleearth-bin(_init+0x91)[0x8048631] I see you also posted this on the googlearth forum, lets hope they know more... Good luck! :) Juergen ___ 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: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
On Mon, July 19, 2010 1:37 am, Timur I. Bakeyev wrote: On Sun, Jul 18, 2010 at 10:42 PM, David Brodbeck g...@gull.us wrote: On Jul 7, 2010, at 10:12 AM, David Brodbeck wrote: On Wed, July 7, 2010 2:20 am, mcoyles wrote: David - have a look here... http://lists.freebsd.org/pipermail/freebsd-current/2010-April/016405.html OK, I see. It looks like rtld is part of world, not a port, so then the question becomes, why didn't freebsd-update update it for me? Is there a way I can force a binary upgrade, or do I need to download the source and rebuild things that way? I ended up downloading the 7.3 livefs ISO, booting off of it, and replacing /libexec/ld-elf.so.1 with the one from the CD. That fixed the problem. I suspect the reason freebsd-update didn't upgrade it properly is it appears it's impossible to replace this file on a running system, even in single-user mode. Maybe there should be something in the release notes about a 7.2 - 7.3 upgrade being impossible to do properly except by booting from CD? make installworld happily does it, so can you - by renaming file to the *.old and then putting new on in it's place. So, it could be that freebsd-update isn't sophisticated enough to do such a trick. That doesn't work, unfortunately. Once you rename ld-elf.so.1 to ld-elf.so.1.old, trying to run any further commands -- even mv and cp -- fails with an error. (I didn't write down which one; something about failing to load the ELF interpreter, I think.) I know, I managed to cripple my system that way. I had to boot a LiveCD to recover, because it couldn't even load /bin/sh to get into single-user mode. ___ 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 googleearth keeps crashing when photo window is closed?
On 07/19/2010 11:32, Juergen Lock wrote: Hi! I didn't answer at first since my ports weren't up to date and I couldn't reproduce the issue, now after updating to latest ports and RELENG_8_1 (amd64) googleearth still seems to work just fine for me, only gl doesn't work since a) our linux versions of the gl-related libs are too old for my card (radeon r730pro i.e. HD 4650) and b) I'm on amd64 and I've been told the dri interface may be different between i386 and amd64 so the linuxolator could have issues emulating gl anyway. (or only with the xorg drivers since the nvidia blob may already be handling this problem?) I see you also posted this on the googlearth forum, lets hope they know more... It's very strange, but the problem seems intermittent. It works after some updates and breaks with some other ones. At the moment with the current 8.1 and updated ports it works fine again. Thank you, Yuri ___ 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: Spanish keyboard in X
On Mon, 19 Jul 2010 10:09:00 +0200, Matthias Apitz g...@unixarea.de wrote: El día Sunday, July 18, 2010 a las 11:32:05AM -0700, Leonardo M. Ramé escribió: Yes,I have modified xorg.conf the same way as you mentioned. Anyway, now the problem is solved by adding setxkbmap es to my .xsession Thanks. Leonardo M. Ramé http://leonardorame.blogspot.com A bit related to the question: If you need Spanish Tilde chars but you have only an English or German keyboard (like I have), you can make use of the so called WindowsKey in X11 and define the keys like shown below. Just for completeness, there is another option I'd like to add: You define a key to be the multi key, usually labelled Compose, at least on the Sun keyboard I use; in ~/.xmodmaprc: add mod4 = Multi_key keycode 117 = Multi_key Then you can compose any characters you need that aren't even part of your localized keymap, e. g. Compose char1 char2 (as a sequence, not a combination) will give you the combination of both characters, at least if there's a symbol matching in the character table. Examples: Compose a a - å (svedish a-circle) Compose s s - ß (Eszett) Compose o / - ø (danish o-stroke) Compose U - Ü (german U Umlaut, capital) Compose L / - Ł (polish L-stroke, capital) Compose k k - ĸ (greek kappa, not sure if it really is) Compose n ' - ń (n with accent grave) This can also be used to generate tilde characters, as well as the weirdest use of accents. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Emacs splash screen went to textmode only
Ashish SHUKLA writes: Can you upload the screenshot of what you're getting ? Hi, I've uploaded a screenshot right here: http://www.abload.de/img/emacs-splashaws1.png The image shows four incarnations of Emacs. These are, clockwise starting from upper left: 1) Emacs started remotely on my laptop through ssh. This Emacs is slightly older (23.1.1) than the one on my desktop (23.2.1). This is what an unfiddled-with splash screen is supposed to look like in recent versions. 2) Emacs started on my desktop, using -q -no-site-file as per your suggestion. There are no graphics and no colors. 3) Another instance of Emacs started on my desktop, also with -q -no-site-file. I switched to *scratch* and evaluated (fancy-startup-screen). The fancy startup screen pops up without a hitch. 4) Another instance of Emacs on my desktop, this time running in a terminal. The startup screen is yet another one. Any clues? regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 ___ 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: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
In the last episode (Jul 19), David Brodbeck said: On Mon, July 19, 2010 1:37 am, Timur I. Bakeyev wrote: On Sun, Jul 18, 2010 at 10:42 PM, David Brodbeck g...@gull.us wrote: On Jul 7, 2010, at 10:12 AM, David Brodbeck wrote: On Wed, July 7, 2010 2:20 am, mcoyles wrote: David - have a look here... http://lists.freebsd.org/pipermail/freebsd-current/2010-April/016405.html OK, I see. It looks like rtld is part of world, not a port, so then the question becomes, why didn't freebsd-update update it for me? Is there a way I can force a binary upgrade, or do I need to download the source and rebuild things that way? I ended up downloading the 7.3 livefs ISO, booting off of it, and replacing /libexec/ld-elf.so.1 with the one from the CD. That fixed the problem. I suspect the reason freebsd-update didn't upgrade it properly is it appears it's impossible to replace this file on a running system, even in single-user mode. Maybe there should be something in the release notes about a 7.2 - 7.3 upgrade being impossible to do properly except by booting from CD? make installworld happily does it, so can you - by renaming file to the *.old and then putting new on in it's place. So, it could be that freebsd-update isn't sophisticated enough to do such a trick. That doesn't work, unfortunately. Once you rename ld-elf.so.1 to ld-elf.so.1.old, trying to run any further commands -- even mv and cp -- fails with an error. (I didn't write down which one; something about failing to load the ELF interpreter, I think.) I know, I managed to cripple my system that way. I had to boot a LiveCD to recover, because it couldn't even load /bin/sh to get into single-user mode. A better method would be to copy (not move) the file to a backup location, then either use mv or install to install the new version. Also, the programs in /rescue/ are statically linked so they can be used to recover if you end up losing ld-elf.so.1 or other critical shared libs. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipfw nat and jails on loopback - is it possible?
On 19/07/2010 10:05, Aiza wrote: you have to put your hosts /etc/resolve.conf in each jail before you can get network connection. I did. It contains: nameserver 208.67.222.222 nameserver 208.67.220.220 I believe that it's not a problem with jail configuration because NAT works fine on the same jail when I switch to pf. Michael ___ 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 on; Probing devices, please wait (this can take a while)...
I'm trying to boot on the 9.0 Current or 8.0 Release CD to install and it just hangs on; Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM Drive: Seagate ST31000333AS ___ 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: Samba gives invalid PT_PHDR after upgrading from 7.2-RELEASE to 7.3-RELEASE
On Mon, July 19, 2010 12:47 pm, Dan Nelson wrote: In the last episode (Jul 19), David Brodbeck said: That doesn't work, unfortunately. Once you rename ld-elf.so.1 to ld-elf.so.1.old, trying to run any further commands -- even mv and cp -- fails with an error. (I didn't write down which one; something about failing to load the ELF interpreter, I think.) I know, I managed to cripple my system that way. I had to boot a LiveCD to recover, because it couldn't even load /bin/sh to get into single-user mode. A better method would be to copy (not move) the file to a backup location, then either use mv or install to install the new version. Also, the programs in /rescue/ are statically linked so they can be used to recover if you end up losing ld-elf.so.1 or other critical shared libs. That was actually what I tried first, but I got a file in use error when I tried to overwrite it with the new version. Good to know about /rescue. I'll remember that next time something like this happens. ___ 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 on; Probing devices, please wait (this can take a while)...
On Mon, 19 Jul 2010 13:16:46 -0700 (PDT) Rich rl...@pacbell.net wrote: Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. It should take less than a second to complete. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sockets stuck in use
On Mon, Jul 19, 2010 at 10:20 AM, Anonymous swel...@gmail.com wrote: Jim stapleton...@gmail.com writes: I was working on an application I've been developing, and I closed the last instance a bit over 12 hours ago, but some of the sockets are still stuck in use: [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED Is there any way to get rid of them without restarting the machine? I was playing with sockopt SO_KEEPALIVE and SO_LINGER when I caused this issue.. Does tcpdrop(8) help? No, the result (The first command is what I figured would be correct, given the man page, the second was just to be paranoid - although this machine is both the host and destination, having glommed onto several ports. The .80 IPs are within the web server's jail. I cannot tcpdrop within the jail [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED [s...@elrond ~/dev/pipe/scripts]$ sudo tcpdrop 192.168.1.80 46116 192.168.1.2 9612 tcpdrop: 192.168.1.80 46116 192.168.1.2 9612: No such process [s...@elrond ~/dev/pipe/scripts]$ sudo tcpdrop 192.168.1.2 9612 192.168.1.80 46116 tcpdrop: 192.168.1.2 9612 192.168.1.80 46116: No such process [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED [s...@elrond ~/dev/pipe/scripts]$ cd /data/jail/ [s...@elrond /data/jail]$ sudo ./bilbo_web_shell [r...@bilbo_web /data/jail]# tcpdrop 192.168.1.80 46116 192.168.1.2 9612 tcpdrop: 192.168.1.80 46116 192.168.1.2 9612: Operation not permitted Thanks, -Jim Stapleton ___ 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 on; Probing devices, please wait (this can take a while)...
Ok well at least that's good to know. So I disconnected my hard drives and now it boots up further on the CD only but obviously I can't install it with no hard drives. Why does it hang on my drives and what can I do about it? They are just regular Seagate SATA drives. I have windows 7 installed on the first partition and trying to dual-boot FreeBSD on a second partition (well actually the third since win 7 needs two). AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM Drives: Seagate ST31000333AS From: Bruce Cran br...@cran.org.uk To: Rich rl...@pacbell.net Cc: freebsd-questions@freebsd.org Sent: Mon, July 19, 2010 3:05:32 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Mon, 19 Jul 2010 13:16:46 -0700 (PDT) Rich rl...@pacbell.net wrote: Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. It should take less than a second to complete. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ 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 on; Probing devices, please wait (this can take a while)...
On Mon, 19 Jul 2010 15:38:20 -0700 (PDT), Rich rl...@pacbell.net wrote: Ok well at least that's good to know. So I disconnected my hard drives and now it boots up further on the CD only but obviously I can't install it with no hard drives. Why does it hang on my drives and what can I do about it? They are just regular Seagate SATA drives. I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
WLAN stops working when idle
I have noted that my wlan stops responding when the O.S. does not use the
network for a while (10 minutes aprox), and I have to do ifconfig wlan0 down
ifconfig wlan0 up dhclient wlan0 to reconnect.
The network card is the internal Wi-Fi from my Dell Inspiron 1525, and uses
ndis to wrap the WinXp driver.
/etc/rc.conf:
...
wlans_ndis0=wlan0
ifconfig_wlan0=WPA SYNCDHCP
wpa_supplicant_enable=YES
...
/etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
ap_scan=1
network={
ssid=strada
key_mgmt=WPA-PSK
psk=martin13
}
uname -a:
FreeBSD inspiron-1521 8.1-RC2 FreeBSD 8.1-RC2 #0: Tue Jun 29 20:42:40 UTC 2010
r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
Any hint?
Leonardo M. Ramé
http://leonardorame.blogspot.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Tue, 20 Jul 2010 00:59:58 +0200 Polytropon free...@edvax.de wrote: I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). Unfortunately the LiveFS CD does run sysinstall by default - you need to go to the Fixit menu to get the shell. I'd suggest trying to boot with debug output enabled and seeing if that produces any clues - I suspect not, but it's worth a go. To do that, press 6 when you see the boot menu to get command prompt and enter boot -v. You should see any debug output on the 2nd console (press F2 when sysinstall hangs). -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Hi-- On Jul 19, 2010, at 3:38 PM, Rich wrote: Ok well at least that's good to know. So I disconnected my hard drives and now it boots up further on the CD only but obviously I can't install it with no hard drives. Why does it hang on my drives and what can I do about it? They are just regular Seagate SATA drives. I have windows 7 installed on the first partition and trying to dual-boot FreeBSD on a second partition (well actually the third since win 7 needs two). AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. 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: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, Jul 19, 2010 at 1:16 PM, Rich rl...@pacbell.net wrote: I'm trying to boot on the 9.0 Current or 8.0 Release CD to install and it just hangs on; Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM Drive: Seagate ST31000333AS ___ 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 This is probably just grasping at straws, but any chance your hard drive is failing? -- randi ___ 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 on; Probing devices, please wait (this can take a while)...
On Tue, 20 Jul 2010 00:16:27 +0100, Bruce Cran br...@cran.org.uk wrote: On Tue, 20 Jul 2010 00:59:58 +0200 Polytropon free...@edvax.de wrote: I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). Unfortunately the LiveFS CD does run sysinstall by default - you need to go to the Fixit menu to get the shell. Yes - that's what I intended to suggest. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 on; Probing devices, please wait (this can take a while)...
I tried this but pressing F2 doesn't do anything. From: Bruce Cran br...@cran.org.uk To: Polytropon free...@edvax.de Cc: freebsd-questions@freebsd.org; Rich rl...@pacbell.net Sent: Mon, July 19, 2010 4:16:27 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Tue, 20 Jul 2010 00:59:58 +0200 Polytropon free...@edvax.de wrote: I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). Unfortunately the LiveFS CD does run sysinstall by default - you need to go to the Fixit menu to get the shell. I'd suggest trying to boot with debug output enabled and seeing if that produces any clues - I suspect not, but it's worth a go. To do that, press 6 when you see the boot menu to get command prompt and enter boot -v. You should see any debug output on the 2nd console (press F2 when sysinstall hangs). -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ 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 on; Probing devices, please wait (this can take a while)...
Drive is perfectly fine. Windows runs perfect on first partition. BTW both drives are doing it, I doubt both drives would go bad at the same time. Windows and Linux workfine. Only FreeBSD has trouble. From: Garrett Cooper gcoo...@freebsd.org To: Randi Harper ra...@freebsd.org Cc: Rich rl...@pacbell.net; freebsd-questions@freebsd.org; freebsd-sysinst...@freebsd.org Sent: Mon, July 19, 2010 5:53:21 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Mon, Jul 19, 2010 at 4:32 PM, Randi Harper ra...@freebsd.org wrote: On Mon, Jul 19, 2010 at 1:16 PM, Rich rl...@pacbell.net wrote: I'm trying to boot on the 9.0 Current or 8.0 Release CD to install and it just hangs on; Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM Drive: Seagate ST31000333AS This is probably just grasping at straws, but any chance your hard drive is failing? Time to try checking the SMART data on the drive? Cheers, -Garrett ___ 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 on; Probing devices, please wait (this can take a while)...
Motherbd is Foxconn Digitalife A79A-S. BIOS settings don't make any difference. From: Chuck Swiger cswi...@mac.com To: Rich rl...@pacbell.net Cc: FreeBSD - freebsd-questions@freebsd.org Sent: Mon, July 19, 2010 4:17:06 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... Hi-- On Jul 19, 2010, at 3:38 PM, Rich wrote: Ok well at least that's good to know. So I disconnected my hard drives and now it boots up further on the CD only but obviously I can't install it with no hard drives. Why does it hang on my drives and what can I do about it? They are just regular Seagate SATA drives. I have windows 7 installed on the first partition and trying to dual-boot FreeBSD on a second partition (well actually the third since win 7 needs two). AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. 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 ___ 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 on; Probing devices, please wait (this can take a while)...
I couldn't find a live CD fro 8.0 Release. All I could find was at this site; http://livecd.sourceforge.net/download.php It's 4.6, is that useful? Anyway, it booted up to the login prompt without hanging. What does that tell us? Is there anything I can check with this disk or is there somewhere I can get the 8.0 live CD? From: Polytropon free...@edvax.de To: Bruce Cran br...@cran.org.uk Cc: freebsd-questions@freebsd.org; Rich rl...@pacbell.net Sent: Mon, July 19, 2010 4:34:18 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Tue, 20 Jul 2010 00:16:27 +0100, Bruce Cran br...@cran.org.uk wrote: On Tue, 20 Jul 2010 00:59:58 +0200 Polytropon free...@edvax.de wrote: I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). Unfortunately the LiveFS CD does run sysinstall by default - you need to go to the Fixit menu to get the shell. Yes - that's what I intended to suggest. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, Jul 19, 2010 at 4:32 PM, Randi Harper ra...@freebsd.org wrote: On Mon, Jul 19, 2010 at 1:16 PM, Rich rl...@pacbell.net wrote: I'm trying to boot on the 9.0 Current or 8.0 Release CD to install and it just hangs on; Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM Drive: Seagate ST31000333AS This is probably just grasping at straws, but any chance your hard drive is failing? Time to try checking the SMART data on the drive? Cheers, -Garrett ___ 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: Emacs splash screen went to textmode only
Hi, 4) Another instance of Emacs on my desktop, this time running in a terminal. The startup screen is yet another one. In this one, I clearly recognize emacs being run inside an ascii terminal. Ascii terminal do not have graphic possibility (nor mousse) so it is only normal that there is no graphic splash screen. If it is the same version of emacs that you run on the instances 2 and 3, I would look for a X issue. Do you have an environment variable set in the xterm? In that xterm, can you launch another xterm? Olivier ___ 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: sockets stuck in use
On Mon, Jul 19, 2010 at 3:12 AM, Jim stapleton...@gmail.com wrote: I was working on an application I've been developing, and I closed the last instance a bit over 12 hours ago, but some of the sockets are still stuck in use: [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED Is there any way to get rid of them without restarting the machine? I was playing with sockopt SO_KEEPALIVE and SO_LINGER when I caused this issue.. sockstat(1) will tell you process that has the socket open, can you kill it from there? -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
Ok I booted on that disc and it hangs at the same place. not sure what to do next. What is the fixit menu? From: Ryan Coleman ryan.cole...@cwis.biz To: Rich rl...@pacbell.net Sent: Mon, July 19, 2010 6:23:45 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... Rich, Here they are: 8.0 i386: ftp://ftp11.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/8.0/8.0-RELEASE-i386-livefs.iso 8.0 AMD64: ftp://ftp11.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/8.0/8.0-RELEASE-amd64-livefs.iso Each is 640MB On Jul 19, 2010, at 8:11 PM, Rich wrote: I couldn't find a live CD fro 8.0 Release. All I could find was at this site; http://livecd.sourceforge.net/download.php It's 4.6, is that useful? Anyway, it booted up to the login prompt without hanging. What does that tell us? Is there anything I can check with this disk or is there somewhere I can get the 8.0 live CD? From: Polytropon free...@edvax.de To: Bruce Cran br...@cran.org.uk Cc: freebsd-questions@freebsd.org; Rich rl...@pacbell.net Sent: Mon, July 19, 2010 4:34:18 PM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On Tue, 20 Jul 2010 00:16:27 +0100, Bruce Cran br...@cran.org.uk wrote: On Tue, 20 Jul 2010 00:59:58 +0200 Polytropon free...@edvax.de wrote: I would suggest to boot with the live system CD, e. g. of 8.0-RELEASE. It should not launch sysinstall automatically (you can even boot the CD into SUM), so you end up with a regular shell. First, check all the kernel's output for things that look... strange... and maybe you even decide to install the system without sysinstall (if THAT is what's causing all the trouble). Unfortunately the LiveFS CD does run sysinstall by default - you need to go to the Fixit menu to get the shell. Yes - that's what I intended to suggest. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ 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
new jail utility is available. announcement.
This is a news announcement to inform people who have interest in jails, that a new jail utility is available. http://sourceforge.net/projects/qjail/ Has a file suitable for the pkg_add command or the port make files can be downloaded and a make install run. Qjail [ q = quick ] is a 4th generation wrapper for the basic chroot jail system that includes security and performance enhancements. Plus a new level of user friendliness enhancements dealing with deploying just a few jails or large jail environments consisting of 100's of jails. Qjail requires no knowledge of the jail command usage. It uses nullfs for read-only system binaries, sharing one copy of them with all the jails. Uses mdconfig to create sparse image jails. Sparse image jails provide a method to limit the total disk space a jail can consume, while only occupying disk space of the sum size of the files in the image jail. Ability to assign ip address with their network device name, so aliases are auto created on jail start and auto removed on jail stop. Ability to create ZONEs of identical qjail systems, each with their own group of jails. Ability to designate a portion of the jail name as a group prefix so the command being executed will apply to only those jail names matching that prefix. Qjail reduces the complexities of small and large jail deployments to the novice level. Qjail has a fully documented manpage written for easy comprehension. Details are given to felicitate the use of qjail's capabilities to the fullest extent possible. ___ 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 on; Probing devices, please wait (this can take a while)...
On Mon, 19 Jul 2010 17:53:30 -0700 (PDT) Rich rl...@pacbell.net wrote: I tried this but pressing F2 doesn't do anything. Sorry - I meant Alt-F2 to switch VTYs. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
