Re: Several minor annoyances on Current
hm, I have similar experience with 10-stable see http://lists.freebsd.org/pipermail/freebsd-questions/2014-July/259067.html Thankfully, my boot time is not so severe. I have no ideas to help however. * preventing coredump files: setting in ~/.cshrc below does not work. What is the correct syntax? ulimit -c 0 setenv ulimit -c 0 * What is the error below? Could this output hold clues to finding deeper errors? This occurred during an install requiring opengl, but could Radeon-KMS be a contributing cause? Not running in a graphics capable console, and unable to find one. svgalib: ark: Unknown chiptype 29. Not running in a graphics capable console, and unable to find one. Not running in a graphics capable console, and unable to find one. *** Error code 1 - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5933755.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
Hi, * I have a kernel with all witness/debug code disabled, and the zfs root is on a Sata3-SSD. The boot process seems a little slow to me and I'm curious as to possible reasons. Other than disabling debug, what else can I do to speed-up boot process (CPU: AMD Phenom II X4 B60 3415.38-MHz K8-class) hm, I have similar experience with 10-stable see http://lists.freebsd.org/pipermail/freebsd-questions/2014-July/259067.html If anybody has any idea/suggestion please please share. Thanks. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
@ Ian: I added your code and rebuilt the kernel. /boot/loader.conf also has vfs.nfs.bootp_disable=YES Previously described problem persists. SEPARATE KBD_KEYMAP ISSUE: The keymap for keyboard fails to be set from rc.conf with keymap=fr.iso.kbd Boot message shows this but there is no record of the message in log files/dmesg: Configuring syscons: keymapkbdcontrol: keymap file fr.iso.kbd not found: No such file or directory Keymap gets set when I change rc.conf entry to: keymap=/usr/share/syscons/keymaps/fr.iso.kbd - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931938.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
On Sat, Jul 26, 2014 at 02:03:09AM -0700, Beeblebrox wrote: @ Ian: I added your code and rebuilt the kernel. /boot/loader.conf also has vfs.nfs.bootp_disable=YES Previously described problem persists. SEPARATE KBD_KEYMAP ISSUE: The keymap for keyboard fails to be set from rc.conf with keymap=fr.iso.kbd Boot message shows this but there is no record of the message in log files/dmesg: Configuring syscons: keymapkbdcontrol: keymap file fr.iso.kbd not found: No such file or directory Keymap gets set when I change rc.conf entry to: keymap=/usr/share/syscons/keymaps/fr.iso.kbd Yes, I also stumbled upon this. Usually the following worked: # kbdcontrol -l german.iso # kbdcontrol -l german.iso.kbd # kbdcontrol -l /usr/share/syscons/keymaps/german.iso.kbd In the last few months on HEAD only the latest invocation works. pgpwzACgGt9XY.pgp Description: PGP signature
Re: Several minor annoyances on Current
Am 26.07.2014 um 13:24 schrieb Lars Engels: On Sat, Jul 26, 2014 at 02:03:09AM -0700, Beeblebrox wrote: @ Ian: I added your code and rebuilt the kernel. /boot/loader.conf also has vfs.nfs.bootp_disable=YES Previously described problem persists. SEPARATE KBD_KEYMAP ISSUE: The keymap for keyboard fails to be set from rc.conf with keymap=fr.iso.kbd Boot message shows this but there is no record of the message in log files/dmesg: Configuring syscons: keymapkbdcontrol: keymap file fr.iso.kbd not found: No such file or directory Keymap gets set when I change rc.conf entry to: keymap=/usr/share/syscons/keymaps/fr.iso.kbd Yes, I also stumbled upon this. Usually the following worked: # kbdcontrol -l german.iso # kbdcontrol -l german.iso.kbd # kbdcontrol -l /usr/share/syscons/keymaps/german.iso.kbd In the last few months on HEAD only the latest invocation works. Please retry with kbdcontrol as of SVN revision 269120. With this change, kbdcontrol -l looks at up to 4 places for keyboard map definitions: 1) Under the path found in the environment variable KEYMAP_PATH 2) Under the full path name specified as parameter to -l 3) Under the newcons-specific path (/usr/share/vt/keymaps) (***) 4) Under the old path used for syscons (/usr/share/syscons/keymaps) (***) Only if using newcons as reported by sysctl kern.vty For newcons, there was no case 4), it only looked into vt/keymaps. But many keymaps are identical for syscons and newcons and only a few have been converted and placed into /usr/share/vt/keymaps. Regards, STefan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
On Sat, Jul 26, 2014 at 03:18:27PM +0200, Stefan Esser wrote: Am 26.07.2014 um 13:24 schrieb Lars Engels: On Sat, Jul 26, 2014 at 02:03:09AM -0700, Beeblebrox wrote: @ Ian: I added your code and rebuilt the kernel. /boot/loader.conf also has vfs.nfs.bootp_disable=YES Previously described problem persists. SEPARATE KBD_KEYMAP ISSUE: The keymap for keyboard fails to be set from rc.conf with keymap=fr.iso.kbd Boot message shows this but there is no record of the message in log files/dmesg: Configuring syscons: keymapkbdcontrol: keymap file fr.iso.kbd not found: No such file or directory Keymap gets set when I change rc.conf entry to: keymap=/usr/share/syscons/keymaps/fr.iso.kbd Yes, I also stumbled upon this. Usually the following worked: # kbdcontrol -l german.iso # kbdcontrol -l german.iso.kbd # kbdcontrol -l /usr/share/syscons/keymaps/german.iso.kbd In the last few months on HEAD only the latest invocation works. Please retry with kbdcontrol as of SVN revision 269120. With this change, kbdcontrol -l looks at up to 4 places for keyboard map definitions: 1) Under the path found in the environment variable KEYMAP_PATH 2) Under the full path name specified as parameter to -l 3) Under the newcons-specific path (/usr/share/vt/keymaps) (***) 4) Under the old path used for syscons (/usr/share/syscons/keymaps) (***) Only if using newcons as reported by sysctl kern.vty For newcons, there was no case 4), it only looked into vt/keymaps. But many keymaps are identical for syscons and newcons and only a few have been converted and placed into /usr/share/vt/keymaps. Regards, STefan Thanks, that revision works for me. pgpZ8AJdE4jFu.pgp Description: PGP signature
Re: Several minor annoyances on Current
On Sat, 2014-07-26 at 02:03 -0700, Beeblebrox wrote: @ Ian: I added your code and rebuilt the kernel. /boot/loader.conf also has vfs.nfs.bootp_disable=YES Previously described problem persists. It needs to be set to =1, not =YES. -- Ian SEPARATE KBD_KEYMAP ISSUE: The keymap for keyboard fails to be set from rc.conf with keymap=fr.iso.kbd Boot message shows this but there is no record of the message in log files/dmesg: Configuring syscons: keymapkbdcontrol: keymap file fr.iso.kbd not found: No such file or directory Keymap gets set when I change rc.conf entry to: keymap=/usr/share/syscons/keymaps/fr.iso.kbd - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931938.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Several minor annoyances on Current
Hello. Several questions for 11-Current: * I keep getting appname.core (gedit.core, midori.core, etc) files being created either in /home/myuser or in the folder I run the command in on terminal emulator (for example if I'm in ~/mydocs on terminal and run $ gedit filename, that folder gets a gedit.core file). Any way to stop this? * I noticed the system now does a dhcp lookup during boot, while in the past it did not do so (I have static IP defined in rc.conf). Any reason for this change, and how can I disable it (already have dhclient_enable=NO in rc.conf) * Are there any tweaks (sysctl or such) for fastest possible shutdown for poweroff? * I have a kernel with all witness/debug code disabled, and the zfs root is on a Sata3-SSD. The boot process seems a little slow to me and I'm curious as to possible reasons. Other than disabling debug, what else can I do to speed-up boot process (CPU: AMD Phenom II X4 B60 3415.38-MHz K8-class) Thanks and Regards. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
Damian Weber wrote: is there ifconfig_em0=DHCP or anything like that in your rc.conf? No, network related rc.conf entries: network_interfaces=lo0 re0 re1 ifconfig_lo0=inet 127.0.0.1/24 ifconfig_re0=inet 192.168.1.10/24 ifconfig_re1=inet 192.168.2.1/24 gateway_enable=YES defaultrouter=192.168.1.1 dhclient_enable=NO Thanks regards. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931665.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
Kurt Jaeger wrote: Can you check whether one of your ethernet-ports has a double life as IPMI port and that one sends out the DHCP ? No such setup. This is my workstation, with wake-on-lan and pxe-boot disabled in bios. Checking boot messages provides a little more insight - Its not one but *both* NIC's that look for DHCP. Also, this is before root gets mounted, so what's in rc.conf is irrelevant: Sending DHCP Discover packet from interface re0 (mac#) Sending DHCP Discover packet from interface re1 (mac#) Received DHCP Offer packet on re0 from 192.168.1.1 (accepted) Received DHCP Offer packet on re0 from 192.168.1.1 (ignored) Received DHCP Offer packet on re0 from 192.168.1.1 (ignored) Sending DHCP Request packet from interface re0 (mac#) Received DHCP Ack packet on re0 from 192.168.1.1 (accepted) DHCP timeout for interface re1 re0 at 192.168.1.11 server 192.168.1.1 subnet mask 255.255.255.0 router 192.168.1.1 Adjusted interface re0 Shutdown interface re1 Trying to mount root from zfs:bsd []... I compile and use the same kernel for both host and pxe-booted diskless clients. So my kernel config file has options NFSCL # Network Filesystem Client options NFS_ROOT# NFS usable as /, requires NFSCL options BOOTP # Needed for non-btx PXE options BOOTP_NFSROOT # Needed for non-btx PXE It's probably what's causing this behavior. Kernel must receive IP before it can try and mount an NFS volume as root. However, I would have assumed that the vfs.root.mountfrom= setting in loader.conf would be read before such attempt... - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931678.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
On Fri, 2014-07-25 at 05:04 -0700, Beeblebrox wrote: Kurt Jaeger wrote: Can you check whether one of your ethernet-ports has a double life as IPMI port and that one sends out the DHCP ? No such setup. This is my workstation, with wake-on-lan and pxe-boot disabled in bios. Checking boot messages provides a little more insight - Its not one but *both* NIC's that look for DHCP. Also, this is before root gets mounted, so what's in rc.conf is irrelevant: Sending DHCP Discover packet from interface re0 (mac#) Sending DHCP Discover packet from interface re1 (mac#) Received DHCP Offer packet on re0 from 192.168.1.1 (accepted) Received DHCP Offer packet on re0 from 192.168.1.1 (ignored) Received DHCP Offer packet on re0 from 192.168.1.1 (ignored) Sending DHCP Request packet from interface re0 (mac#) Received DHCP Ack packet on re0 from 192.168.1.1 (accepted) DHCP timeout for interface re1 re0 at 192.168.1.11 server 192.168.1.1 subnet mask 255.255.255.0 router 192.168.1.1 Adjusted interface re0 Shutdown interface re1 Trying to mount root from zfs:bsd []... I compile and use the same kernel for both host and pxe-booted diskless clients. So my kernel config file has options NFSCL # Network Filesystem Client options NFS_ROOT# NFS usable as /, requires NFSCL options BOOTP # Needed for non-btx PXE options BOOTP_NFSROOT # Needed for non-btx PXE It's probably what's causing this behavior. Kernel must receive IP before it can try and mount an NFS volume as root. However, I would have assumed that the vfs.root.mountfrom= setting in loader.conf would be read before such attempt... I made changes last year that allowed vfs.root.mountfrom to unconditionally override any path provided by the bootp/dhcp server. While it overrides the server-provided path, it doesn't prevent contacting the server (the override may be for a different nfs path). See http://svnweb.freebsd.org/base?view=revisionrevision=253847 for details. I didn't consider at the time that someone might want to avoid doing any bootp configuration at all, but in retrospect I can think of several good reasons to turn off bootp on a per-boot basis. The attached patch provides a knob for that, I'll commit it if there are no objections. -- Ian Index: sys/nfs/bootp_subr.c === --- sys/nfs/bootp_subr.c (revision 268986) +++ sys/nfs/bootp_subr.c (working copy) @@ -1551,8 +1551,11 @@ bootpc_init(void) struct nfsv3_diskless *nd; struct thread *td; int timeout; - int delay; + int delay, disable; + if (TUNABLE_INT_FETCH(vfs.nfs.bootp_disable, disable) disable) + return; + timeout = BOOTP_IFACE_WAIT_TIMEOUT * hz; delay = hz / 10; ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
... in retrospect I can think of several good reasons to turn off bootp on a per-boot basis. The attached patch provides a knob for that, I'll commit it if there are no objections. Thanks - a knob in /boot/loader.conf as vfs.nfs.bootp_disable=YES should do nicely. Regards. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931753.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
On Fri, 25 Jul 2014, Beeblebrox wrote: Hello. Several questions for 11-Current: * I keep getting appname.core (gedit.core, midori.core, etc) files being created either in /home/myuser or in the folder I run the command in on terminal emulator (for example if I'm in ~/mydocs on terminal and run $ gedit filename, that folder gets a gedit.core file). Any way to stop this? This seems like a job for ulimit. Though, I would be more curious about why your applications are crashing so as to generate core files in the first place. -Ben ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
Hi This seems like a job for ulimit. Damien pointed that out as: ulimit -c 0 Though, I would be more curious about why your applications are crashing so as to generate core files in the first place. Well, this MAJOR annoyance lies somewhere between Radeon-KMS and gnome3's graphics/cairo. This started some 3 months back and I can only get some level of normalcy when I build cairo using with_debug=1. Very strange. Also, a number of apps just flat-out refuse to start; most notably mozilla's firefox seamonkey. Monsieur Pédron is aware of the problem, although as stated it's been over 3 months. While I'm on a roll :P One major peeve is that installed apps fail to create an icon in the desktop menu structure. I know that a) maintainer must set DESKTOP_ENTRIES in the Makefile OR b) users can add appname.desktop in /usr/local/share/applications/ but as a dreamer, I know there has to be a better solution other than badgering maintainers or slogging through the task of adding menu shortcut items? - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931761.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
Beeblebrox wrote: Hello. Several questions for 11-Current: * I keep getting appname.core (gedit.core, midori.core, etc) files being created either in /home/myuser or in the folder I run the command in on terminal emulator (for example if I'm in ~/mydocs on terminal and run $ gedit filename, that folder gets a gedit.core file). Any way to stop this? I use this in /etc/sysctl.conf: kern.corefile=/tmp/cores/%N.core (You need to create the directory manually) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Several minor annoyances on Current
Hi I use this in /etc/sysctl.conf: kern.corefile=/tmp/cores/%N.core In rc.conf I have clear_tmp_enable=YES I would have used tmpfs for /tmp but my zpool/tmp is on an SSD which gives about the same result as far as /tmp is concerned. The ulimit setting seems to have solved it. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Several-minor-annoyances-on-Current-tp5931653p5931773.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
