FreeBSD 9 Xorg server failed to configure
Hi, colleagues! I am installing FreeBSD 9 + XORG + KDE4 to my Acer notebook. I have updated Freebsd using freebsd-update and ports using portsnap. Further I compiled Xorg using make BATCH=YES install clean. Xorg has been compiled successfully. But that is what happeing once I try configuring Xorg: root@FreeBSD:/usr/ports/x11/kde4 # Xorg -configure X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 9.1-RELEASE-p3 amd64 Current Operating System: FreeBSD FreeBSD.localdomain 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0: Mon Apr 29 18:27:25 UTC 2013 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 02 May 2013 04:48:53PM Current version of pixman: 0.24.2 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: Thu May 2 16:55:59 2013 List of video drivers: ati radeon mach64 nv r128 radeonhd openchrome intel vesa (++) Using config file: /root/xorg.conf.new Number of created screens does not match number of detected devices. Configuration failed. Could you help me investigate this case and make Xorg to configure successfully? == Thanks, Vlad ___ 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 9 port XORG failed to install
Hi, colleagues! I am trying to install FreeBSD 9 to my notebook Acer Aspire V3-571G. Ports I am trying to install: /usr/ports/x11/xorg My issue is that build fails on an unclear reason. Workflow is: 1. Install FreeBSD 2. Install system updates 3. Download and extract latest ports cd /usr/ports/x11/xorg make BATCH=YES install clean Please, help me on those questions: 1. How to fix this issue and build XORG properly 2. Are there any locations where I can take latest packages? (Using pkg_add -r package_name downloads rather old packages, I want the latest ones) == Regards, Vlad ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 port XORG failed to install
Hi Савельев Владимир, El día Saturday, April 27, 2013 a las 08:59:36PM +0400, Савельев Владимир escribió: Hi, colleagues! I am trying to install FreeBSD 9 to my notebook Acer Aspire V3-571G. Ports I am trying to install: /usr/ports/x11/xorg My issue is that build fails on an unclear reason. Workflow is: 1. Install FreeBSD 2. Install system updates 3. Download and extract latest ports How do you do this exactly? From SVN? cd /usr/ports/x11/xorg make BATCH=YES install clean Please show the last hundred lines of the output of this. Without messages nobody can help you. matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - Never being an iSlave WWW: http://www.unixarea.de/ | - No proprietary attachments, no HTML/RTF in E-mail phone: +49-170-4527211 | - Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
On Sat, 9 Mar 2013 12:07:41 -0800 (PST) leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? If so, how can this installation be done? In particular, is there a way to install 9.1 so that it can be booted from the traditional master boot record? It is important that, when I am done, I can still boot to Windows XP, as I must run some applications not available on FreeBSD. If the idea I am proposing is not feasible with version 9.1, will it work with 8.3? Any comments are appreciated. If this question has already been asked many times before, please just let me know where to look to find the answer. Thanks. Newbie502 As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. --- --- Eduardo Morras emorr...@yahoo.es ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
On Mon, 2013-03-11 at 13:51 +0100, Eduardo Morras wrote: As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. This does work? I've got XP as VBox's vdi and just a folder to share content with *nix. It would be possible to install XP bootable without VBox to a ntfs partition, to boot it directly and if wanted, to use it also as guest in VBox? I only use VBox to get applications for an iPad and to copy PDFs to an iPad, since ad-hoc networks until now never worked for me, but I also would like to test hardware sometimes, impossible with VBox, so sometimes it would be nice to have a real Windows install. If this should work, will it become impossible to use snapshots made by VBox? Will there be no confusion regarding to different drivers for the XP booted as VBox guest and booted directly? Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
On Mon, 11 Mar 2013 14:14:05 +0100 Ralf Mardorf ralf.mard...@rocketmail.com wrote: On Mon, 2013-03-11 at 13:51 +0100, Eduardo Morras wrote: As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. This does work? I followed the instructions (only once) from this page http://geekery.amhill.net/2010/01/27/virtualbox-with-existing-windows-partition/ and it works under FreeBSD 8.3 and WinXP. I've got XP as VBox's vdi and just a folder to share content with *nix. It would be possible to install XP bootable without VBox to a ntfs partition, to boot it directly and if wanted, to use it also as guest in VBox? I use it that way, my set up is 2 primary mbr partitions, one with XP ntfs, the other with FreeBSD ufs2+su. VBox installed on both. I only use VBox to get applications for an iPad and to copy PDFs to an iPad, since ad-hoc networks until now never worked for me, but I also would like to test hardware sometimes, impossible with VBox, so sometimes it would be nice to have a real Windows install. If this should work, will it become impossible to use snapshots made by VBox? Will there be no confusion regarding to different drivers for the XP booted as VBox guest and booted directly? Don't know if VBox snapshots are usable, never tried. There's no confusion, WinXP access directly to the XP partition and FreeBSD to FreeBSD partition. If you don't play with VBox internal commands you are safe. I got a dirty fs on FreeBSD when WinXP crashed once. HTH Regards, Ralf --- --- Eduardo Morras emorr...@yahoo.es ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
On Mon, 2013-03-11 at 14:31 +0100, Eduardo Morras wrote: On Mon, 11 Mar 2013 14:14:05 +0100 Ralf Mardorf ralf.mard...@rocketmail.com wrote: On Mon, 2013-03-11 at 13:51 +0100, Eduardo Morras wrote: As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. This does work? I followed the instructions (only once) from this page http://geekery.amhill.net/2010/01/27/virtualbox-with-existing-windows-partition/ and it works under FreeBSD 8.3 and WinXP. I've got XP as VBox's vdi and just a folder to share content with *nix. It would be possible to install XP bootable without VBox to a ntfs partition, to boot it directly and if wanted, to use it also as guest in VBox? I use it that way, my set up is 2 primary mbr partitions, one with XP ntfs, the other with FreeBSD ufs2+su. VBox installed on both. I only use VBox to get applications for an iPad and to copy PDFs to an iPad, since ad-hoc networks until now never worked for me, but I also would like to test hardware sometimes, impossible with VBox, so sometimes it would be nice to have a real Windows install. If this should work, will it become impossible to use snapshots made by VBox? Will there be no confusion regarding to different drivers for the XP booted as VBox guest and booted directly? Don't know if VBox snapshots are usable, never tried. There's no confusion, WinXP access directly to the XP partition and FreeBSD to FreeBSD partition. If you don't play with VBox internal commands you are safe. I got a dirty fs on FreeBSD when WinXP crashed once. Thank you :) I'll flag your reply as useful information, perhaps I come back to that later. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
Eduardo Morras emorr...@yahoo.es writes: On Sat, 9 Mar 2013 12:07:41 -0800 (PST) leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? If so, how can this installation be done? In particular, is there a way to install 9.1 so that it can be booted from the traditional master boot record? It is important that, when I am done, I can still boot to Windows XP, as I must run some applications not available on FreeBSD. If the idea I am proposing is not feasible with version 9.1, will it work with 8.3? Any comments are appreciated. If this question has already been asked many times before, please just let me know where to look to find the answer. Thanks. Newbie502 As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. It is my understanding that FreeBSD doesn't allow using part of a disk, but grabs the entire disk. That means that VirtualBox can't use partitions on a disk that any other partitions are being used by anything else, including FreeBSD itself. Am I wrong about this? I use VirtualBox using vdmk for an entire disk, but I have never been able to share with anything else. -- Carl Johnsonca...@peak.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: FreeBSD 9 and Windows XP
On Mon, 2013-03-11 at 09:05 -0700, Carl Johnson wrote:
It is my understanding that FreeBSD doesn't allow using part of a disk,
but grabs the entire disk. That means that VirtualBox can't use
partitions on a disk that any other partitions are being used by
anything else, including FreeBSD itself. Am I wrong about this? I use
VirtualBox using vdmk for an entire disk, but I have never been able to
share with anything else.
No, this is a misunderstanding. The primary below [1] is the ufs
including my FreeBSD, it's just that Linux's parted doesn't show it
(gparted does show) and I can't access BSD by my Linux installs. And no,
the ntfs isn't Windows.
FWIW my old drives have only one primary and a extended + tons of
logical partitions, but I started to partition new drives with 3 primary
and one extended including as much logical partitions as needed [2].
To have one partition that can be accessed by the BIOS I format one with
fat32, since it can't access ntfs partitions. Most Linux use ext4 by
default, I've got ext3 and ext4, because FreeBSD can share ext3
partitions without issues with Linux.
I'm using GRUB2 from Linux to boot FreeBSD [3], it's sharing a drive
with several Linux installs, more installs anybody does need ;). I'm not
maintaining all installs.
Regards,
Ralf
[1]
[rocketmouse@archlinux ~]$ sudo parted /dev/sda print
Model: ATA SAMSUNG HD321KJ (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End SizeType File system Flags
1 32.3kB 62.1GB 62.1GB primary boot
2 62.1GB 320GB 258GB extended
5 62.1GB 94.1GB 32.0GB logical ntfs
6 94.1GB 126GB 32.1GB logical ext3
7 126GB 158GB 32.2GB logical ext3
8 158GB 185GB 27.0GB logical ext3
9 185GB 223GB 37.7GB logical ext3
10 223GB 225GB 2328MB logical linux-swap(v1)
11 225GB 288GB 62.3GB logical ext3
12 288GB 291GB 3759MB logical ext3
13 291GB 315GB 23.7GB logical ext3
14 315GB 320GB 4927MB logical ext3
[2]
[rocketmouse@archlinux ~]$ sudo parted /dev/sdc print
Model: WD Ext HDD 1021 (scsi)
Disk /dev/sdc: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End SizeType File system Flags
1 1049kB 68.0GB 68.0GB primary ext3
2 68.0GB 138GB 69.6GB primary ext4
3 138GB 413GB 276GB primary ext4
4 413GB 2000GB 1587GB extended
[snip]
[3]
[rocketmouse@archlinux ~]$
cat /run/media/rocketmouse/q/boot/grub/grub.cfg
set timeout=8
set default='0'; if [ x$default = xsaved ]; then load_env; set
default=$saved_entry; fi
set color_normal='light-blue/black'; set
color_highlight='light-cyan/blue'
menuentry FreeBSD{
set root=(hd0,msdos1)
chainloader +1
}
menuentry 'Ubuntu Quantal,kernel 3.6.5-rt14' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb9' 'ro' 'quiet' ''
legacy_initrd '/boot/initrd.img-3.6.5-rt14'
'/boot/initrd.img-3.6.5-rt14'
}
menuentry 'Ubuntu Quantal,kernel 3.5.0-18-lowlatency
threadirqs' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb9' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Quantal,kernel 3.5.0-18-lowlatency (recovery
mode)' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb9' 'ro' 'single'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Studio Quantal, Kernel 3.6.5-rt14' {
set root='(hd1,13)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb13' 'ro' 'quiet'
legacy_initrd '/boot/initrd.img-3.6.5-rt14'
'/boot/initrd.img-3.6.5-rt14'
}
menuentry 'Ubuntu Studio Quantal, Kernel 3.5.0-18-lowlatency
threadirqs' {
set root='(hd1,13)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb13' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Studio Precise, Kernel 3.0.30 threadirqs' {
set root='(hd1,1)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.0.30' '/boot/vmlinuz-3.0.30'
'root=UUID=338316fb-364e-4a43-8deb-738127f878ce' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.0.30' '/boot/initrd.img-3.0.30'
}
menuentry 'Ubuntu Studio Precise, Kernel 3.2.0-23-lowlatency
threadirqs' {
set root='(hd1,1)'; set legacy_hdbias='0'
legacy_kernel
Re: FreeBSD 9 and Windows XP
On Mon, 11 Mar 2013, Carl Johnson wrote: Eduardo Morras emorr...@yahoo.es writes: On Sat, 9 Mar 2013 12:07:41 -0800 (PST) leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? If so, how can this installation be done? In particular, is there a way to install 9.1 so that it can be booted from the traditional master boot record? It is important that, when I am done, I can still boot to Windows XP, as I must run some applications not available on FreeBSD. If the idea I am proposing is not feasible with version 9.1, will it work with 8.3? Any comments are appreciated. If this question has already been asked many times before, please just let me know where to look to find the answer. Thanks. Newbie502 As an addon to other answers, you can install VirtualBox, create a minimal hard disk with MBR boot menu that points to the WindowsXP partition. This way you don't need to restart in WinXP. The same can be done from WinXP side, a minimal hd with MBR boot menu to startup the FreeBSD. It is my understanding that FreeBSD doesn't allow using part of a disk, but grabs the entire disk. That means that VirtualBox can't use partitions on a disk that any other partitions are being used by anything else, including FreeBSD itself. Am I wrong about this? I use VirtualBox using vdmk for an entire disk, but I have never been able to share with anything else. It's very hard to tell what situation is being described here. If the VMDK is a pointer to a whole physical disk, that would probably make the disk only usable by one VM. It should be possible to make the VMDK point to just one partition on the disk. Then other VMs or a physical machine could use those other partitions while the FreeBSD VM was running. Booting the same Windows install alternately in a VM and then on real hardware may trigger the Genuine Advantage annoyance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
On Mon, 2013-03-11 at 12:25 -0600, Warren Block wrote: Booting the same Windows install alternately in a VM and then on real hardware may trigger the Genuine Advantage annoyance. This is true, but for some exceptional cases perhaps untrue. I wasn't aware about this possibility, but it does sound interesting to me. I run Windows in VBox only to use an iPad I won and to transfer documents from my *nix to the iPad. So my exceptional cases is, that I've got something useful I didn't buy myself. This thing, the iPad, has a lot of disadvantages, I don't pay for apps etc., but it's useful as a reader and for some other tasks. I don't need and I don't use Windows, with this exception (to use the reader/iPad). It's a XP without admin account and service pack 2 only, I don't give a damn about the state of this Windows or the state of the reader. Ok, I made some snapshots, I use this advantage, but I could live without snapshots. I'm a *nix only user, the iPad and regarding to this, Windows XP too, fall into my lap. iPad and Windows aren't important for me, I don't need the security advantages of the virtual machine. I chose it, to avoid issues with installing Windows to a real partition, no primary was free and fixing the boot loader is work and I wish to access iTunes from my *nix ... however, since *nix tend to be problematic regarding to hardware, it can't harm to have a Windows to test hardware that does cause issues with *nix, to ensure that the hardware isn't broken. In my very exceptional, individual case it might be really interesting to share a real Windows install, directly booted and booted as guest in VBox. I'm thinking of making a backup of the virtual partition and to restore it on a real, primary ntfs partition or something similar, perhaps I can copy just the iTunes data and make a new Windows install ... OTOH I didn't use a Windows install before, disk space isn't expensive, so I'm uncertain, if I really want a real Windows install and if I should wish to have one, it's not to share it with VBox, but keep a separated version in VBox. I'm not sure that it's really easy to test hardware when booting it directly and to have completely different _virtual_ hardware by VBox. What would happen, if for the _virtual_ boot of XP, the professional audio card is missing? The setups might be that different, that it perhaps can't switch between a _real_ and a _virtual_ boot without much editing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
Warren Block wbl...@wonkity.com writes: On Mon, 11 Mar 2013, Carl Johnson wrote: It is my understanding that FreeBSD doesn't allow using part of a disk, but grabs the entire disk. That means that VirtualBox can't use partitions on a disk that any other partitions are being used by anything else, including FreeBSD itself. Am I wrong about this? I use VirtualBox using vdmk for an entire disk, but I have never been able to share with anything else. It's very hard to tell what situation is being described here. If the VMDK is a pointer to a whole physical disk, that would probably make the disk only usable by one VM. It should be possible to make the VMDK point to just one partition on the disk. Then other VMs or a physical machine could use those other partitions while the FreeBSD VM was running. I was thinking of the case where I tried to allow direct access by a virtual machine to a slice on the same disk that I was running FreeBSD off of. I just looked further into that and discovered that it is possible, but not allowed by geom by default. It can be done by setting 'sysctl kern.geom.debugflags=0x10'. I am sure that you are aware of the dangers, but for anybody else reading this check out the warning in the geom(4) manpage. They refer to this option as 'allow foot shooting' for a reason. -- Carl Johnsonca...@peak.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: FreeBSD 9 and Windows XP
On Mon, 11 Mar 2013, Carl Johnson wrote: Warren Block wbl...@wonkity.com writes: On Mon, 11 Mar 2013, Carl Johnson wrote: It is my understanding that FreeBSD doesn't allow using part of a disk, but grabs the entire disk. That means that VirtualBox can't use partitions on a disk that any other partitions are being used by anything else, including FreeBSD itself. Am I wrong about this? I use VirtualBox using vdmk for an entire disk, but I have never been able to share with anything else. It's very hard to tell what situation is being described here. If the VMDK is a pointer to a whole physical disk, that would probably make the disk only usable by one VM. It should be possible to make the VMDK point to just one partition on the disk. Then other VMs or a physical machine could use those other partitions while the FreeBSD VM was running. I was thinking of the case where I tried to allow direct access by a virtual machine to a slice on the same disk that I was running FreeBSD off of. I just looked further into that and discovered that it is possible, but not allowed by geom by default. It can be done by setting 'sysctl kern.geom.debugflags=0x10'. I am sure that you are aware of the dangers, but for anybody else reading this check out the warning in the geom(4) manpage. They refer to this option as 'allow foot shooting' for a reason. That's kind of what I was saying. If you can get the VMDK to refer to just the one slice/partition that the VM needs, it won't lock the whole disk. For example, ada0s2a rather than ada0s2. Of course, it would be bad to share the same partition between more than one VM or physical machine at the same time unless it is mounted read-only by all of them. ___ 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 9 and Windows XP
Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? If so, how can this installation be done? In particular, is there a way to install 9.1 so that it can be booted from the traditional master boot record? It is important that, when I am done, I can still boot to Windows XP, as I must run some applications not available on FreeBSD. If the idea I am proposing is not feasible with version 9.1, will it work with 8.3? Any comments are appreciated. If this question has already been asked many times before, please just let me know where to look to find the answer. Thanks. Newbie502 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
On Sat, 9 Mar 2013 12:07:41 -0800 (PST) leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? If so, how can this installation be done? In particular, is there a way to install 9.1 so that it can be booted from the traditional master boot record? It is important that, when I am done, I can still boot to Windows XP, as I must run some applications not available on FreeBSD. If the idea I am proposing is not feasible with version 9.1, will it work with 8.3? Any comments are appreciated. If this question has already been asked many times before, please just let me know where to look to find the answer. Thanks. Newbie502 When I did it, I shrunk the Windows partition and installed FreeBSD to the a new partition created on the free space of the drive. The multiboot version of the MBR stuff for FreeBSD should be able to handle it for you with out issue. I've not done it with 9.1, but when I did it with 6 way back when, it worked nicely. signature.asc Description: PGP signature
Re: FreeBSD 9 and Windows XP
On Sat, Mar 9, 2013 at 3:07 PM, leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? As others have already answered, yes. The risks are minimal if you are careful but you will always have the risk of breaking something so make a backup of your XP before doing _anything_. Also, even before doing that, run a de-fragmenter. -- Alejandro Imass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
On Sat, 2013-03-09 at 21:27 +0100, Polytropon wrote: Partition Magic I would avoid to use proprietary software, ntfs, fat16 and fat32 are full supported by Linux gparted, available for free as in beer at http://partedmagic.com as a live media. Perhaps you need to defragment the Windows partitions first. You need to add a primary partition for FreeBSD, an extended partition with logical partitions can't be used to install FreeBSD. I've got FreeBSD and tons of Linux installed, no Windows. However, my partition table is MBR based, as yours. Gparted can't create the FreeBSD slice, you need to do this with e.g. the FreeBSD installer. I had to use 8.3 and than to update to 9.1, I tested 9.0 first, but I couldn't create the slice, resp. the partitions in that slice. Hth, Ralf -- http://sacom.hk/mission ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and Windows XP
On Sat, 09 Mar 2013 21:49:29 +0100, Ralf Mardorf wrote: On Sat, 2013-03-09 at 21:27 +0100, Polytropon wrote: Partition Magic I would avoid to use proprietary software, ntfs, fat16 and fat32 are full supported by Linux gparted, available for free as in beer at http://partedmagic.com as a live media. Thanks for mentioning it - Parted Magic was the project I was actually refering to. :-) -- 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: FreeBSD 9 and Windows XP
On Sat, 09 Mar 2013 21:27:45 +0100, Polytropon free...@edvax.de wrote: On Sat, 9 Mar 2013 12:07:41 -0800 (PST), leeoliveshackelf...@surewest.net wrote: Good afternoon, FreeBSD enthusiasts. Can FreeBSD 9.1 be installed on a computer on which Windows XP currently resides? Yes. If so, how can this installation be done? First of all, you need a tool to make disk space available; you can do this by adding an additional hard disk, or by resizing the Windows partition. As Windows does not seem to provide native tools to do this I may misremember, but Win7 does have a functional shrink drive in the drive administration console, and I do think that was there in XP already. 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
Re: audio/baresip on FreeBSD 9
On 01/03/13 04:19, Joseph Olatt wrote:
I've been trying to get baresip to work on my FreeBSD 9.x laptop and
haven't had much success. I register successfully to callcentric.com and
it appears that I can connect and there is a stream of data coming
through based on the status display:
[0:00:08] audio=0/0 (bit/s) []
However, there is no sound.
Is anybody on the list successfully using baresip? If so, could they
please provide some pointers on how to get sound?
There doesn't seem to be much documentation anywhere on the Internet for
baresip.
My config file (~/.baresip/config) is:
/* Begin ~/.baresip/config */
#
# baresip configuration
#
#--
# Core
poll_method poll# poll, select, epoll ..
# Input
input_device /dev/event0
input_port
# SIP
sip_trans_bsize 128
#sip_listen 127.0.0.1:5050
# Audio
audio_dev /dev/audio0.0
audio_srate 8000-48000
audio_channels1-2
#audio_aec_length 128 # [ms]
# Video
video_dev
video_size352x288
video_bitrate 384000
video_fps 25
#video_selfview window # {window,pip}
# AVT - Audio/Video Transport
rtp_tos 184
#rtp_ports1-2
#rtp_bandwidth512-1024 # [kbit/s]
rtcp_enable yes
rtcp_mux no
jitter_buffer_delay 5-10# frames
# Network
#dns_server 10.0.0.1:53
#--
# Modules
module_path /usr/local/lib/baresip/modules
# UI Modules
modulestdio.so
modulecons.so
#module evdev.so
# Audio codec Modules (in order)
#module g7221.so
#module g722.so
moduleg711.so
#module gsm.so
#module l16.so
#module speex.so
#module celt.so
#module bv32.so
# Audio filter Modules (in order)
# NOTE: AEC should be before Preproc
#module sndfile.so
#module speex_aec.so
#module speex_pp.so
#module speex_resamp.so
#module plc.so
# Audio driver Modules
#module oss.so
#module alsa.so
#module portaudio.so
#module gst.so
# Video codec Modules (in order)
moduleavcodec.so
#module vpx.so
# Video source modules
#module avformat.so
#module v4l.so
#module v4l2.so
# Video display modules
#module sdl.so
#module x11.so
# Media NAT modules
#module stun.so
#module turn.so
#module ice.so
# Media encoding modules
#module srtp.so
# Other modules
#module natbd.so
#--
# Module parameters
# Speex codec parameters
speex_quality 7 # 0-10
speex_complexity 7 # 0-10
speex_enhancement 0 # 0-1
speex_vbr 0 # Variable Bit Rate 0-1
speex_vad 0 # Voice Activity Detection 0-1
speex_agc_level 8000
# NAT Behavior Discovery
#natbd_server creytiv.com
#natbd_interval 600 # in seconds
/* End ~/.baresip/config */
/* uname -a */
FreeBSD peace 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #4 r244062: Mon Dec
10 17:56:25 CST 2012 root@peace:/usr/obj/usr/src/sys/PEACE i386
Thanks.
___
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 works for me (not sure about video, works with video loop but have
not found a free sip server that supports video streams..):
#
# baresip configuration
#
#--
# Core
poll_method select # poll, select, epoll ..
# Input
input_device/dev/event0
input_port
# SIP
sip_trans_bsize 128
#sip_listen 127.0.0.1:5050
# Audio
audio_dev /dev/dsp
audio_srate 8000-48000
audio_channels 1-2
audio_aec_length128 # [ms]
# Video
video_dev /dev/video0
Re: audio/baresip on FreeBSD 9
On Thu, Jan 03, 2013 at 08:15:41AM +0100, Matthias Apitz wrote:
Hi,
El d?a Wednesday, January 02, 2013 a las 08:19:11PM -0800, Joseph Olatt
escribi?:
I've been trying to get baresip to work on my FreeBSD 9.x laptop and
haven't had much success. I register successfully to callcentric.com and
it appears that I can connect and there is a stream of data coming
through based on the status display:
[0:00:08] audio=0/0 (bit/s) []
The display shows zero audio data!
However, there is no sound.
Have you tried the local audio loop with pressing the single letter 'a'?
Is anybody on the list successfully using baresip? If so, could they
please provide some pointers on how to get sound?
I'm attaching my config file which works fine; in your config file it
looks stange to me:
# Audio
audio_dev /dev/audio0.0
do you have such a device file '/dev/audio0.0'?
# Audio codec Modules (in order)
#module g7221.so
#module g722.so
module g711.so
#module gsm.so
#module l16.so
#module speex.so
#module celt.so
#module bv32.so
# Audio filter Modules (in order)
# NOTE: AEC should be before Preproc
#module sndfile.so
#module speex_aec.so
#module speex_pp.so
#module speex_resamp.so
#module plc.so
# Audio driver Modules
#module oss.so
#module alsa.so
#module portaudio.so
#module gst.so
you have no audio driver loaded, try 'oss.so'
Once you get the local loop working you could contact me off-list for my
SIP and try to call me.
HIH
matthias
--
Sent from my FreeBSD netbook
Matthias Apitz | - No system with backdoors like Apple/Android
E-mail: g...@unixarea.de | - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ | - No proprietary attachments
phone: +49-170-4527211 | - Respect for open standards
#
# baresip configuration
#
#--
# Core
poll_method poll# poll, select, epoll ..
# Input
input_device /dev/event0
input_port
# SIP
sip_trans_bsize 128
#sip_listen 127.0.0.1:5050
# Audio
audio_dev /dev/dsp
audio_srate 8000-48000
audio_channels1-2
#audio_aec_length 128 # [ms]
# Video
video_dev /dev/video0
video_size352x288
video_bitrate 384000
video_fps 25
#video_selfview window # {window,pip}
# AVT - Audio/Video Transport
rtp_tos 184
#rtp_ports1-2
rtp_ports 1024-1030
#rtp_bandwidth512-1024 # [kbit/s]
rtcp_enable yes
rtcp_mux no
jitter_buffer_delay 5-10# frames
# Network
#dns_server 10.0.0.1:53
#--
# Modules
module_path /usr/local/lib/baresip/modules
# UI Modules
modulestdio.so
modulecons.so
#module evdev.so
# Audio codec Modules (in order)
#module g7221.so
#module g722.so
moduleg711.so
#module gsm.so
#module l16.so
#module speex.so
#module celt.so
#module bv32.so
# Audio filter Modules (in order)
# NOTE: AEC should be before Preproc
#module sndfile.so
#module speex_aec.so
#module speex_pp.so
#module speex_resamp.so
#module plc.so
# Audio driver Modules
moduleoss.so
#module alsa.so
#module portaudio.so
#module gst.so
# Video codec Modules (in order)
moduleavcodec.so
#module vpx.so
# Video source modules
modulev4l2.so
#module avformat.so
#module v4l.so
# Video display modules
modulex11.so
# module sdl.so
# Media NAT modules
modulestun.so
moduleturn.so
moduleice.so
# Media encoding modules
#module srtp.so
# Other modules
#module
audio/baresip on FreeBSD 9
I've been trying to get baresip to work on my FreeBSD 9.x laptop and
haven't had much success. I register successfully to callcentric.com and
it appears that I can connect and there is a stream of data coming
through based on the status display:
[0:00:08] audio=0/0 (bit/s) []
However, there is no sound.
Is anybody on the list successfully using baresip? If so, could they
please provide some pointers on how to get sound?
There doesn't seem to be much documentation anywhere on the Internet for
baresip.
My config file (~/.baresip/config) is:
/* Begin ~/.baresip/config */
#
# baresip configuration
#
#--
# Core
poll_method poll# poll, select, epoll ..
# Input
input_device/dev/event0
input_port
# SIP
sip_trans_bsize 128
#sip_listen 127.0.0.1:5050
# Audio
audio_dev /dev/audio0.0
audio_srate 8000-48000
audio_channels 1-2
#audio_aec_length 128 # [ms]
# Video
video_dev
video_size 352x288
video_bitrate 384000
video_fps 25
#video_selfview window # {window,pip}
# AVT - Audio/Video Transport
rtp_tos 184
#rtp_ports 1-2
#rtp_bandwidth 512-1024 # [kbit/s]
rtcp_enable yes
rtcp_muxno
jitter_buffer_delay 5-10# frames
# Network
#dns_server 10.0.0.1:53
#--
# Modules
module_path /usr/local/lib/baresip/modules
# UI Modules
module stdio.so
module cons.so
#module evdev.so
# Audio codec Modules (in order)
#module g7221.so
#module g722.so
module g711.so
#module gsm.so
#module l16.so
#module speex.so
#module celt.so
#module bv32.so
# Audio filter Modules (in order)
# NOTE: AEC should be before Preproc
#module sndfile.so
#module speex_aec.so
#module speex_pp.so
#module speex_resamp.so
#module plc.so
# Audio driver Modules
#module oss.so
#module alsa.so
#module portaudio.so
#module gst.so
# Video codec Modules (in order)
module avcodec.so
#module vpx.so
# Video source modules
#module avformat.so
#module v4l.so
#module v4l2.so
# Video display modules
#module sdl.so
#module x11.so
# Media NAT modules
#module stun.so
#module turn.so
#module ice.so
# Media encoding modules
#module srtp.so
# Other modules
#module natbd.so
#--
# Module parameters
# Speex codec parameters
speex_quality 7 # 0-10
speex_complexity7 # 0-10
speex_enhancement 0 # 0-1
speex_vbr 0 # Variable Bit Rate 0-1
speex_vad 0 # Voice Activity Detection 0-1
speex_agc_level 8000
# NAT Behavior Discovery
#natbd_server creytiv.com
#natbd_interval 600 # in seconds
/* End ~/.baresip/config */
/* uname -a */
FreeBSD peace 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #4 r244062: Mon Dec
10 17:56:25 CST 2012 root@peace:/usr/obj/usr/src/sys/PEACE i386
Thanks.
___
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: audio/baresip on FreeBSD 9
Hi,
El día Wednesday, January 02, 2013 a las 08:19:11PM -0800, Joseph Olatt
escribió:
I've been trying to get baresip to work on my FreeBSD 9.x laptop and
haven't had much success. I register successfully to callcentric.com and
it appears that I can connect and there is a stream of data coming
through based on the status display:
[0:00:08] audio=0/0 (bit/s) []
The display shows zero audio data!
However, there is no sound.
Have you tried the local audio loop with pressing the single letter 'a'?
Is anybody on the list successfully using baresip? If so, could they
please provide some pointers on how to get sound?
I'm attaching my config file which works fine; in your config file it
looks stange to me:
# Audio
audio_dev /dev/audio0.0
do you have such a device file '/dev/audio0.0'?
# Audio codec Modules (in order)
#module g7221.so
#module g722.so
moduleg711.so
#module gsm.so
#module l16.so
#module speex.so
#module celt.so
#module bv32.so
# Audio filter Modules (in order)
# NOTE: AEC should be before Preproc
#module sndfile.so
#module speex_aec.so
#module speex_pp.so
#module speex_resamp.so
#module plc.so
# Audio driver Modules
#module oss.so
#module alsa.so
#module portaudio.so
#module gst.so
you have no audio driver loaded, try 'oss.so'
Once you get the local loop working you could contact me off-list for my
SIP and try to call me.
HIH
matthias
--
Sent from my FreeBSD netbook
Matthias Apitz | - No system with backdoors like Apple/Android
E-mail: g...@unixarea.de | - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ | - No proprietary attachments
phone: +49-170-4527211 | - Respect for open standards
#
# baresip configuration
#
#--
# Core
poll_method poll# poll, select, epoll ..
# Input
input_device/dev/event0
input_port
# SIP
sip_trans_bsize 128
#sip_listen 127.0.0.1:5050
# Audio
audio_dev /dev/dsp
audio_srate 8000-48000
audio_channels 1-2
#audio_aec_length 128 # [ms]
# Video
video_dev /dev/video0
video_size 352x288
video_bitrate 384000
video_fps 25
#video_selfview window # {window,pip}
# AVT - Audio/Video Transport
rtp_tos 184
#rtp_ports 1-2
rtp_ports 1024-1030
#rtp_bandwidth 512-1024 # [kbit/s]
rtcp_enable yes
rtcp_muxno
jitter_buffer_delay 5-10# frames
# Network
#dns_server 10.0.0.1:53
#--
# Modules
module_path /usr/local/lib/baresip/modules
# UI Modules
module stdio.so
module cons.so
#module evdev.so
# Audio codec Modules (in order)
#module g7221.so
#module g722.so
module g711.so
#module gsm.so
#module l16.so
#module speex.so
#module celt.so
#module bv32.so
# Audio filter Modules (in order)
# NOTE: AEC should be before Preproc
#module sndfile.so
#module speex_aec.so
#module speex_pp.so
#module speex_resamp.so
#module plc.so
# Audio driver Modules
module oss.so
#module alsa.so
#module portaudio.so
#module gst.so
# Video codec Modules (in order)
module avcodec.so
#module vpx.so
# Video source modules
module v4l2.so
#module avformat.so
#module v4l.so
# Video display modules
module x11.so
# modulesdl.so
# Media NAT modules
module stun.so
module turn.so
module ice.so
# Media encoding modules
#module srtp.so
# Other modules
#module natbd.so
#--
# Module parameters
# Speex codec parameters
speex_quality 7 # 0-10
speex_complexity7 # 0-10
speex_enhancement 0 # 0-1
speex_vbr 0 # Variable Bit Rate 0-1
speex_vad 0 # Voice Activity Detection 0-1
speex_agc_level 8000
Is FreeBSD 9 Production Ready?
I am currently running FBSD 8.3-STABLE on a production server that provides http, dns, smtp, and so on for a small domain. This is not a high arrival rate environment but it does need to be rock solid (which FBSD 4-8 have been). I am contemplating moving to the FBSD 9 family. Is this branch ready for production or should I wait a while yet? I ordinarily avoid x.0 releases of anything and I know 9.1 is soon going to be with us. In a related note, if I do move to 9.x is it sufficient to grab the appropriate source tree and compile world and kernels, install and reboot? That is, it is reasonable to do an in-place upgrade. This is how I migrated 4-6, 6-7, and 7-8 and I am hoping this is till the case since a complete reinstall is painful and slow. TIA, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Is FreeBSD 9 Production Ready?
On 2012.11.24 17:38, Tim Daneliuk wrote: I am contemplating moving to the FBSD 9 family. Is this branch ready for production or should I wait a while yet? This probably won't help much, but I wouldn't call any system production ready until I've tested it as thoroughly as possible and qualified it myself for the purpose I intend to use it. I wouldn't blindly trust and drop an operating system on production servers, no matter how good the feedback from outside my organization sounds. As far as FreeBSD release engineering goes, I believe all -RELEASE versions are aimed at maximum stability. But obviously no person or organization can ever test all possible hardware, software and settings combinations. ___ 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: Is FreeBSD 9 Production Ready?
On 11/24/2012 11:19 AM, Lucas B. Cohen wrote: I wouldn't blindly trust and drop an operating system on production servers, no matter how good the feedback from outside my organization sounds. In general, I'd agree with you. Certainly, that's been the case with Linux, AIX, and so on over the years. But I have had essentially no problems doing in-place major rev updates with FreeBSD thus far. The only breakage I am worried about now is whether the new compiler change breaks things that used to work just fine. For example, will my make.conf settings be properly observed by the new tool chain? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Is FreeBSD 9 Production Ready?
Tim Daneliuk tun...@tundraware.com writes: On 11/24/2012 11:19 AM, Lucas B. Cohen wrote: I wouldn't blindly trust and drop an operating system on production servers, no matter how good the feedback from outside my organization sounds. In general, I'd agree with you. Certainly, that's been the case with Linux, AIX, and so on over the years. I have a very small server of my own for the house, and I generally update it to major versions within a few weeks of updating. I think I had it on RELENG_9 within two months of 9.0 being released. As far as I recall, I had very few problems making the jump. But I have had essentially no problems doing in-place major rev updates with FreeBSD thus far. The only breakage I am worried about now is whether the new compiler change breaks things that used to work just fine. For example, will my make.conf settings be properly observed by the new tool chain? I wouldn't use the new toolchain for this server. The old toolchain is still the default anyway. ___ 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: Is FreeBSD 9 Production Ready?
On 24/11/2012 16:38, Tim Daneliuk wrote: I am contemplating moving to the FBSD 9 family. Is this branch ready for production or should I wait a while yet? I ordinarily avoid x.0 releases of anything and I know 9.1 is soon going to be with us. 9-STABLE works for me. I've run into a few quite minor bugs, but certainly nothing really significant. Stability is rock-solid as ever. In a related note, if I do move to 9.x is it sufficient to grab the appropriate source tree and compile world and kernels, install and reboot? That is, it is reasonable to do an in-place upgrade. This is how I migrated 4-6, 6-7, and 7-8 and I am hoping this is till the case since a complete reinstall is painful and slow. Upgrading by compiling world+kernel from source is an effective method. Works just as well for 8-9 as for any of the previous upgrades you mention. It is not however sufficient to get you a completely upgraded system: you will still have to re-install all of your ports. Otherwise, as you end up trying to upgrade ports by ones and twos over time, you'll end up with a complete rat's nest of contradictory shared library dependencies and programs crashing left, right and centre. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Is FreeBSD 9 Production Ready?
On 11/24/2012 03:48 PM, Matthew Seaman wrote: It is not however sufficient to get you a completely upgraded system: you will still have to re-install all of your ports. Otherwise, as you end up trying to upgrade ports by ones and twos over time, you'll end up with a complete rat's nest of contradictory shared library dependencies and programs crashing left, right and centre. So I am discovering. I moved the system to 9.1-PRE today with a source compile. After I then did a make remove-old, the system started complaining about missing libraries. So ... I temporarily fixed this with appropriate /etc/libmap.conf entires. I am now about to do a portupgrade -aARrvf to redo the ports. We'll see how that goes... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Is FreeBSD 9 Production Ready?
Hi, On Sat, 24 Nov 2012 10:38:35 -0600 Tim Daneliuk tun...@tundraware.com wrote: I am currently running FBSD 8.3-STABLE on a production server that provides http, dns, smtp, and so on for a small domain. This is not a high arrival rate environment but it does need to be rock solid (which FBSD 4-8 have been). why would you like to break a running system? I am contemplating moving to the FBSD 9 family. Is this branch ready I would stay with 8.x until the end of its support and move only then to a new branch. It could be then 9.x or 10.y. I would then - but only then - prefer the 10.y branch. I retired my 7.4 only because of lightning strike this spring. Robustness is my main goal here. Any change which brings only the risk is avoided. Irony is now that I am writing you this on a 10.0 machine. Only 10 has had the support I needed for my new toy. Erich ___ 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: Is FreeBSD 9 Production Ready?
On 25/11/2012 04:06, Tim Daneliuk wrote: But I have had essentially no problems doing in-place major rev updates with FreeBSD thus far. The only breakage I am worried about now is whether the new compiler change breaks things that used to work just fine. For example, will my make.conf settings be properly observed by the new tool chain? If you want to build with clang wait for 9.1 http://www.freebsd.org/cgi/query-pr.cgi?pr=threads/165173 I have been running 9.0 built with clang for most of the year as my desktop machine without any other issues. As far as your make.conf goes that will depend on what you have in there. Most gcc flags will either work or be ignored. ___ 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: Is FreeBSD 9 Production Ready?
On 11/24/2012 05:58 PM, Erich Dollansky wrote: Hi, On Sat, 24 Nov 2012 10:38:35 -0600 Tim Daneliuk tun...@tundraware.com wrote: I am currently running FBSD 8.3-STABLE on a production server that provides http, dns, smtp, and so on for a small domain. This is not a high arrival rate environment but it does need to be rock solid (which FBSD 4-8 have been). why would you like to break a running system? That's exactly what I don't want to do. I am contemplating moving to the FBSD 9 family. Is this branch ready I would stay with 8.x until the end of its support and move only then to a new branch. It could be then 9.x or 10.y. I would then - but only then - prefer the 10.y branch. I retired my 7.4 only because of lightning strike this spring. Robustness is my main goal here. Any change which brings only the risk is avoided. I used to take this approach. However, I discovered the pain of fixing a configuration that jumped several major releases was way higher than tracking them each as they became stable. I did the 9.1-PRE upgrade today and - once the new system was compiled and ready to be installed - had only very minor conversion issues. In my case, the most painful part of conversion is the mail infrastructure. The server in question is the domain's mail server and it has a LOT of moving parts with custom configurations: sendmail, greylisting, mailscanner, spam assassin, mailman, SASL ... That is pretty much always what breaks. Doing smaller leaps tends to make this more tractable to control. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Is FreeBSD 9 Production Ready?
On 11/24/2012 06:16 PM, Shane Ambler wrote: On 25/11/2012 04:06, Tim Daneliuk wrote: But I have had essentially no problems doing in-place major rev updates with FreeBSD thus far. The only breakage I am worried about now is whether the new compiler change breaks things that used to work just fine. For example, will my make.conf settings be properly observed by the new tool chain? If you want to build with clang wait for 9.1 http://www.freebsd.org/cgi/query-pr.cgi?pr=threads/165173 I plan to stay conservative and only switch to clang when it is THE way to build everything. i.e., When GCC is finally retired for use in the base OS. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Is FreeBSD 9 Production Ready?
On Sat, 24 Nov 2012, Tim Daneliuk wrote: On 11/24/2012 03:48 PM, Matthew Seaman wrote: It is not however sufficient to get you a completely upgraded system: you will still have to re-install all of your ports. Otherwise, as you end up trying to upgrade ports by ones and twos over time, you'll end up with a complete rat's nest of contradictory shared library dependencies and programs crashing left, right and centre. So I am discovering. I moved the system to 9.1-PRE today with a source compile. After I then did a make remove-old, the system started complaining about missing libraries. So ... I temporarily fixed this with appropriate /etc/libmap.conf entires. I am now about to do a portupgrade -aARrvf to redo the ports. We'll see how that goes... portupgrade -avf is equivalent (-r and -R are redundant with -a). Including -c helps to get the config screens out of the way up front. ___ 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: Is FreeBSD 9 Production Ready?
--On November 24, 2012 10:38:35 AM -0600 Tim Daneliuk tun...@tundraware.com wrote: I am currently running FBSD 8.3-STABLE on a production server that provides http, dns, smtp, and so on for a small domain. This is not a high arrival rate environment but it does need to be rock solid (which FBSD 4-8 have been). I am contemplating moving to the FBSD 9 family. Is this branch ready for production or should I wait a while yet? I ordinarily avoid x.0 releases of anything and I know 9.1 is soon going to be with us. In a related note, if I do move to 9.x is it sufficient to grab the appropriate source tree and compile world and kernels, install and reboot? That is, it is reasonable to do an in-place upgrade. This is how I migrated 4-6, 6-7, and 7-8 and I am hoping this is till the case since a complete reinstall is painful and slow. I upgraded to 9 on a server that is basically doing what yours is. I used freebsd-update and it did all the right things no problems. Been running on 9 without any issues pretty much since it came out. However, the only thing remotely fancy I'm doing is running root ZFS and link aggregation on my NIC's. ___ 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: Is FreeBSD 9 Production Ready?
On 24 November 2012, at 16:36, Tim Daneliuk wrote: On 11/24/2012 05:58 PM, Erich Dollansky wrote: Hi, On Sat, 24 Nov 2012 10:38:35 -0600 Tim Daneliuk tun...@tundraware.com wrote: I am currently running FBSD 8.3-STABLE on a production server that provides http, dns, smtp, and so on for a small domain. This is not a high arrival rate environment but it does need to be rock solid (which FBSD 4-8 have been). why would you like to break a running system? That's exactly what I don't want to do. I am contemplating moving to the FBSD 9 family. Is this branch ready I would stay with 8.x until the end of its support and move only then to a new branch. It could be then 9.x or 10.y. I would then - but only then - prefer the 10.y branch. I retired my 7.4 only because of lightning strike this spring. Robustness is my main goal here. Any change which brings only the risk is avoided. I used to take this approach. However, I discovered the pain of fixing a configuration that jumped several major releases was way higher than tracking them each as they became stable. I did the 9.1-PRE upgrade today and - once the new system was compiled and ready to be installed - had only very minor conversion issues. In my case, the most painful part of conversion is the mail infrastructure. The server in question is the domain's mail server and it has a LOT of moving parts with custom configurations: sendmail, greylisting, mailscanner, spam assassin, mailman, SASL ... That is pretty much always what breaks. Doing smaller leaps tends to make this more tractable to control. I am in a similar situation. Reliability is more important than anything else. I run similar mail configurations on one server, although I use different machines for incoming and outgoing mail. Jumps across versions have been more difficult. I have kept records of the steps I used for each upgrade and theose help me prepare for the next one. I am in the middle of jumping from 7.2 to 9.1. One machine is completely converted and working just fine. I had reliability problems with 9.0. It kept rebooting or crashing every few days. I am on 9.1-RC2 at the moment and its been up and working for 34 days now. I will upgrade it to 9.1 when its released. This one had to be upgraded early because it was new hardware. The old machine completely died. I have another server also running 9.1-RC2 but it is not moved into production yet. It is primarily a news server and has a large news cache that has to be moved. I am waiting for 9.1 for that. On some of my test machines I have found that 9.1 is the first release to support the built-in wireless NICs. The service command is really helpful. I frequently can't remember which service is in etc and which in /usr/local/etc. The largest problem I encountered in the upgrade was the disk structure. My disks were setup when using FreeBSD 3.5/3.7. As a result, the root partition is way too small today. I was able to shoe horn 7.2 in by deleting the kernel symbol files while they were being installed. 9.0/9.1 just didn't fit at all. Restructuring the disks is a time consuming job and fairly error prone in getting everything back that is needed to run production. There is also the issue that the default formatting uses SU+J which is not compatible with dump live filesystems. Now I am going to have to find the time to bring the systems down to remove journaling with no one on-site who has a clue what they are doing. I currently have 9.1-RCx running on 5 systems and have not had any stability issues with it. One system is in production but the others are lightly used. One of them is a 200 MHz machine with either 32 Meg or 64 Meg memory. It seems to be faster then when it ran 8.2 but I haven't actually done any measurements. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Freebsd 9 Startx
Issue solved; I forgot to edit .xinitrc. Cheers, Hooman On Mon, Nov 19, 2012 at 6:06 AM, Polytropon free...@edvax.de wrote: On Mon, 19 Nov 2012 01:28:13 +, Hooman Oroojeni wrote: Dear All, I would like to use GUI in Freebsd 9, but I face with following error. Any idea to help is appreciated. You need to show the error message for diagnostics and suggestions better than pure guessing. :-) Meanwhile, allow me to point you do helpful resources that might be worth reading (just in case you didn't follow them yet): http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html http://wiki.freebsd.org/KDE4 http://www.freebsd.org/gnome/docs/faq2.html In case you have different trouble, please name the software you're intending to run (e. g. which window manager), what you have installed, the content of config files (such as .xinitrc or .xsession) and the commands you've entered, plus their output and error messages. -- 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: Freebsd 9 Startx
Hi, On Mon, 19 Nov 2012 01:28:13 + Hooman Oroojeni orooj...@gmail.com wrote: Dear All, I would like to use GUI in Freebsd 9, but I face with following error. I think that you have mist a paste command here. Anyway, what graphics adaptor are you using? Intel? It it is Intel, read about Intel KMS. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Freebsd 9 Startx
On Mon, 19 Nov 2012 01:28:13 +, Hooman Oroojeni wrote: Dear All, I would like to use GUI in Freebsd 9, but I face with following error. Any idea to help is appreciated. You need to show the error message for diagnostics and suggestions better than pure guessing. :-) Meanwhile, allow me to point you do helpful resources that might be worth reading (just in case you didn't follow them yet): http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html http://wiki.freebsd.org/KDE4 http://www.freebsd.org/gnome/docs/faq2.html In case you have different trouble, please name the software you're intending to run (e. g. which window manager), what you have installed, the content of config files (such as .xinitrc or .xsession) and the commands you've entered, plus their output and error messages. -- 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: how many memory is needed for FreeBSD 9 ?
Le Mon, 22 Oct 2012 03:49:50 +1100, andrew clarke m...@ozzmosis.com a écrit : Hello, I'm updating an old laptop running FreeBSD 8.1 with 64 MB ram (44MB available) but now FreeBSD 9.1 panics at boot time: panic: kmem_malloc(4194304): kmem_map too small: 24584192 allocated? That's one very old laptop. I think you'll need to install more memory or downgrade FreeBSD to an earlier version. 1998, I think (HP Omnibook 900). I use it for small network testing and serial console access. It works well for this. Well I've put 8-STABLE on it (two days to make buildworld/buildkernel). Looks good. From my limited testing under VirtualBox, 96 MB RAM is about the lower limit that will allow FreeBSD 9.1-RC2 to boot before the swap partition is enabled. Any less and the kernel will freeze or panic at boot. This was with the amd64 version though, not i386. Thanks for this, 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
how many memory is needed for FreeBSD 9 ?
Hi, I'm updating an old laptop running FreeBSD 8.1 with 64 MB ram (44MB available) but now FreeBSD 9.1 panics at boot time: panic: kmem_malloc(4194304): kmem_map too small: 24584192 allocated? Any work-around? Thanks 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: how many memory is needed for FreeBSD 9 ?
On Sun 2012-10-21 18:21:59 UTC+0200, Patrick Lamaiziere (patf...@davenulle.org) wrote: I'm updating an old laptop running FreeBSD 8.1 with 64 MB ram (44MB available) but now FreeBSD 9.1 panics at boot time: panic: kmem_malloc(4194304): kmem_map too small: 24584192 allocated? That's one very old laptop. I think you'll need to install more memory or downgrade FreeBSD to an earlier version. 9.1-RELEASE isn't available yet, only 9.1-RC1 RC2. Given it's prerelease code it's plausible the 9.1-RC2 kernel requires more memory at boot than 9.1-REL will. Attempting to boot 9.0-REL from CD on your laptop should answer that question. From my limited testing under VirtualBox, 96 MB RAM is about the lower limit that will allow FreeBSD 9.1-RC2 to boot before the swap partition is enabled. Any less and the kernel will freeze or panic at boot. This was with the amd64 version though, not i386. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how many memory is needed for FreeBSD 9 ?
On 21 October 2012 12:49, andrew clarke m...@ozzmosis.com wrote: On Sun 2012-10-21 18:21:59 UTC+0200, Patrick Lamaiziere (patf...@davenulle.org) wrote: I'm updating an old laptop running FreeBSD 8.1 with 64 MB ram (44MB available) but now FreeBSD 9.1 panics at boot time: panic: kmem_malloc(4194304): kmem_map too small: 24584192 allocated? That's one very old laptop. I think you'll need to install more memory or downgrade FreeBSD to an earlier version. 9.1-RELEASE isn't available yet, only 9.1-RC1 RC2. Given it's prerelease code it's plausible the 9.1-RC2 kernel requires more memory at boot than 9.1-REL will. Attempting to boot 9.0-REL from CD on your laptop should answer that question. From my limited testing under VirtualBox, 96 MB RAM is about the lower limit that will allow FreeBSD 9.1-RC2 to boot before the swap partition is enabled. Any less and the kernel will freeze or panic at boot. This was with the amd64 version though, not i386. Keep in mind that the installer will take some memory on top of what is needed to boot FreeBSD. -- -- ___ 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
Huawei E173 modem doesn't work on FreeBSD 9
Hi Folks, I'm failed to access E173 modem on FreeBSD 9.0 using serial port. Yes, I got information from the web that this device is not supported yet by the default driver, and the u3g driver need to be updated. ( http://freebsd.1045724.n5.nabble.com/usb-159919-Patch-for-HUAWEI-E173-u3g-umodem-td4716191.html). I already follow all the instruction but unfortunately still failed. Till now i'm stuck with this device. I turn to Ubuntu server, the modem works well there. Bellow is output of usbconfig: # usbconfig ugen0.1: UHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen1.1: UHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen2.1: UHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen3.1: UHCI root HUB Intel at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen4.1: EHCI root HUB Intel at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen4.2: HUAWEI Mobile HUAWEI at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.2: USB Keykoard USB at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON # usbconfig -d 4.2 dump_device_desc ugen4.2: HUAWEI Mobile HUAWEI at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x12d1 idProduct = 0x1c05 bcdDevice = 0x0102 iManufacturer = 0x0002 HUAWEI iProduct = 0x0001 HUAWEI Mobile iSerialNumber = 0x no string bNumConfigurations = 0x0001 Do you have any suggestions guys? thanks ___ 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: No sound in my FreeBSD 9
Maybe i should use audio/oss instead of snd_ich ? - e^(π.i) + 1 = 0 -- View this message in context: http://freebsd.1045724.n5.nabble.com/No-sound-in-my-FreeBSD-9-tp5720280p5724585.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
Hi, On Saturday 23 June 2012 15:08:53 Thomas Mueller wrote: I don't think I ever tried to connect a USB 2.0 device to 3.0 port, but I tried the opposite. I have here 2 hard disks and 2 flash drives with USB 2.0. Three of them work on FreeBSD on an USB 3.0 port. One hard disk only works on a USB 3.0 port. One hard drive with USB 3.0 does not work on USB 3.0 but only on 2.0. Irony is that the PCBSD installer installed PCBSD on the USB 3.0 disk but it did not boot afterward. I tried to access that USB 3.0 hard drive on the new computer from USB 2.0 port because NetBSD has no USB 3.0 support: no go. Let me check this out. But when I installed USB 2.0 brackets to USB 2.0 headers on the motherboard, the USB 3.0 hard drive was accessible from those USB 2.0 ports. Same as in my case. USB is more a lottery than real computing for me. Erich I suppose I could say NetBSD is more a lottery than real computing, especially on the new computer. But some of the bugs are consistent. My USB 3.0 hard drive is not bootable (motherboard issue?), also does not show on Grub2 Super Grub Disk on the System Rescue CD menu sysresccd.org Maybe the latter could be fixed by building Grub2 from source under either Linux or FreeBSD Ports. I think I'd also like to build the gdisk port, both on main hard drive and on a bootable FreeBSD USB stick. One USB stick (PNY 1 GB) is no longer readable/mountable from FreeBSD though it is from Linux. I thought that might be corruption. Since I have all that data now on an Ativa 4 GB USB stick, I could install the latest System Rescue CD to the PNY 1 GB USB stick (runs Linux on FAT32), see if there are any problems. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On 06/22/12 08:22, Hans Petter Selasky wrote: On Friday 22 June 2012 08:01:38 O. Hartmann wrote: I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: Lexar at usbus7 umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted Hi, After plugging the device, try: usbconfig -d 7.6 add_quirk UQ_MSC_NO_INQUIRY Then re-plug it. I'm sorry to say a lot of USB flash sticks out there are broken and only tested with the timing of MS Windows. Part of the problem is that it is difficult to autodetect these issues, because once you trigger the non- supported SCSI command, then the flash key stops working like you experience. I would be more than glad to open up an office to certify USB devices for use with FreeBSD :-) --HPS I tried the USB drive this morning with the recommended quirk shown above on FreeBSD 10.0-CURRENT #1 r237462: Sat Jun 23 01:00:35 CEST 2012 without success. I get the same error message as shown above. With or without quirk. I then started Windows 7 on the same box. The USB drive is seen as expected and reflects what I experienced on every other non-FreeBSD box and hardware in the lab on last week. I reformatted the USB drive with extFAT and standard block size on Windows 7. The USB drive is now seen again on FreeBSD and recognized as a drive. Seen in my sloppy terminology means: recognized as a disk. The hardware is recognized, but it is not recognized as a drive. The fact, that the very first time after I bought that USB drive, I was able to put several GB on it, use it on both FreeBSD 9-STABLE and 10-CURRENT, and then it broke, drives me nuts. Using the very same pen drive on other OSes even on the same hardware without issues makes me believe FreeBSD does have an issue, not the USB drive. I will fill the USB drive with data and try to use it very often on FreeBSD. Last time the error occured, it was read by a Suse Linux box. If I wouldn't know better I would say Linux tries to kill the USB drive ... But Linux did see it all the time. A usual customer would see it the same way, I guess. I will test and report next week when I have access to the other boxes and OSes again. Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
and hardware in the lab on last week. I reformatted the USB drive with extFAT and standard block size on Windows 7. The USB drive is now seen again on FreeBSD and recognized as this points that the pendrive's controller is not just flaky but horrid. The communiation with OS, and how/whether it is configured properly should not depend on what data is written to it - in your case exFAT metadata. It seems that controller manufacturer just did something to run on windows and linux instead of something that conform to USB mass storage interface standard :( Sorry but it may be hopeless case. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
My elder colleague often told me that it is the easiest and well-working way to check whether the one is certified to work for Mac OS X to get USB mass storage devices which work with *BSD :) Just my 5 yen, -|-__ YAMAMOTO, Taku | __ t...@tackymt.homeip.net What if a USB mass storage device works with some BSDs but not all? I had Kingston Data Travelers, 2 GB, from one lot that were good with Linux and FreeBSD but not NetBSD. Other USB sticks, including Kingston Data Tavelers, worked with Linux, FreeBSD and NetBSD. I even installed FreeDOS 1.1 prerelease on one of those NetBSD-averse Kingstom Data Travelers. But I think either Mac OS X, Linux or FreeBSD is much more production-ready than NetBSD. There are 3 drivers, one for 3.0, 2.0 and 1.0, and they are associated to corresponding devices at boot. I'll play around with it this weekend and see how to switch, i've also noticed issue connecting 2.0 device to 3.0 port. Waitman Gobble San Jose California USA I don't think I ever tried to connect a USB 2.0 device to 3.0 port, but I tried the opposite. My Western Digital My Book Essential 3.0 TB USB 3.0 drive works even on the old computer whose motherboard's USB is 1.1. I tried to access that USB 3.0 hard drive on the new computer from USB 2.0 port because NetBSD has no USB 3.0 support: no go. But when I installed USB 2.0 brackets to USB 2.0 headers on the motherboard, the USB 3.0 hard drive was accessible from those USB 2.0 ports. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
What if a USB mass storage device works with some BSDs but not all? well the only thing i never experiences with USB pendrives is a one that works everytime properly. Everything else is 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: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On 21 June 2012 23:22, Hans Petter Selasky hsela...@c2i.net wrote: usbconfig -d 7.6 add_quirk UQ_MSC_NO_INQUIRY Then re-plug it. I'm sorry to say a lot of USB flash sticks out there are broken and only tested with the timing of MS Windows. Part of the problem is that it is difficult to autodetect these issues, because once you trigger the non- supported SCSI command, then the flash key stops working like you experience. I would be more than glad to open up an office to certify USB devices for use with FreeBSD :-) Question - if that's the case, then why are we even doing that by default? Adrian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
Hi, On Saturday 23 June 2012 15:08:53 Thomas Mueller wrote: I don't think I ever tried to connect a USB 2.0 device to 3.0 port, but I tried the opposite. I have here 2 hard disks and 2 flash drives with USB 2.0. Three of them work on FreeBSD on an USB 3.0 port. One hard disk only works on a USB 3.0 port. One hard drive with USB 3.0 does not work on USB 3.0 but only on 2.0. Irony is that the PCBSD installer installed PCBSD on the USB 3.0 disk but it did not boot afterward. I tried to access that USB 3.0 hard drive on the new computer from USB 2.0 port because NetBSD has no USB 3.0 support: no go. Let me check this out. But when I installed USB 2.0 brackets to USB 2.0 headers on the motherboard, the USB 3.0 hard drive was accessible from those USB 2.0 ports. Same as in my case. USB is more a lottery than real computing for me. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Saturday 23 June 2012 11:52:53 Adrian Chadd wrote: On 21 June 2012 23:22, Hans Petter Selasky hsela...@c2i.net wrote: usbconfig -d 7.6 add_quirk UQ_MSC_NO_INQUIRY Then re-plug it. I'm sorry to say a lot of USB flash sticks out there are broken and only tested with the timing of MS Windows. Part of the problem is that it is difficult to autodetect these issues, because once you trigger the non- supported SCSI command, then the flash key stops working like you experience. I would be more than glad to open up an office to certify USB devices for use with FreeBSD :-) Question - if that's the case, then why are we even doing that by default? Hi, Do you want a blacklist or do you want a whitelist? Please explain the pros and cons. I believe that those that program wrong shall be held responsible for that and given a chance to clean up, and not the opposite way around. As a senior programmer I can only testify that many people care equally little about what their computer is made of and what they eat. We probably need a control body to certify USB devices that is cheaper than USB.org, simply put. I think it is a bad idea to cripple all USB SCSI devices because what looks like the majority do not obey the rules of the specifications they are supposed to support. Else we need to make a new USB SCSI class for devices that are certified and one for devices that are not certified. Non-certified devices can have a limited SCSI command set, which should be implemented in the CAM layer like some kind of flag. If we could join heads on the Linux guys on this, we might be able to do something! Like having a pop-up every time a USB device fails certain tests. From the history we can predict what people will do when they do not know what they are doing. They will nail the guy doing it right and let the guy doing it wrong go free. And it seems like this happened before too ;-) I have a personal FreeBSD-native USB test utilty that runs mass storage devices through a series of tests. Most USB mass storage devices I've tested so far have obvious bugs, which either means their firmware can be hacked or made to crash. Also worth noting, that many USB device are not certified at all. It might be clever to look for the USB logo from USB.org next time you want to transfer X GB of personal data from location X to Y. --HPS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Sat, 23 Jun 2012 15:50:05 +0700 Erich Dollansky articulated: USB is more a lottery than real computing for me. That is really sad. I am sort of forced to use USB devices on a daily basis, Luckily, very few of them involve FreeBSD, which is why I do not exhibit such a negative attitude, except of course when I do attempt to plug one in a FreeBSD machine with negative results. I do not know what is more pathetic; the fact that so many devices fail to operate correctly -- if at all --, or the willingness of the FreeBSD community to accept it as the norm. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
Hi, On Saturday 23 June 2012 18:18:58 Jerry wrote: On Sat, 23 Jun 2012 15:50:05 +0700 Erich Dollansky articulated: USB is more a lottery than real computing for me. That is really sad. I am sort of forced to use USB devices on a daily basis, Luckily, very few of them involve FreeBSD, which is why I do not exhibit such a negative attitude, except of course when I do attempt to plug one in a FreeBSD machine with negative results. I do not know what is more pathetic; the fact that so many devices fail to operate correctly -- if at all --, or the willingness of the FreeBSD community to accept it as the norm. I see it a bit different. There are standards. I hope that FreeBSD follows them as close as possible. There are also some grey areas in every standard. The grey areas can only be filled with manpower. This is the point where FreeBSD hits a wall. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Sat, Jun 23, 2012 at 1:08 AM, Thomas Mueller muelle...@insightbb.comwrote: My elder colleague often told me that it is the easiest and well-working way to check whether the one is certified to work for Mac OS X to get USB mass storage devices which work with *BSD :) Just my 5 yen, -|-__ YAMAMOTO, Taku | __ t...@tackymt.homeip.net What if a USB mass storage device works with some BSDs but not all? I had Kingston Data Travelers, 2 GB, from one lot that were good with Linux and FreeBSD but not NetBSD. Other USB sticks, including Kingston Data Tavelers, worked with Linux, FreeBSD and NetBSD. I even installed FreeDOS 1.1 prerelease on one of those NetBSD-averse Kingstom Data Travelers. But I think either Mac OS X, Linux or FreeBSD is much more production-ready than NetBSD. There are 3 drivers, one for 3.0, 2.0 and 1.0, and they are associated to corresponding devices at boot. I'll play around with it this weekend and see how to switch, i've also noticed issue connecting 2.0 device to 3.0 port. Waitman Gobble San Jose California USA I don't think I ever tried to connect a USB 2.0 device to 3.0 port, but I tried the opposite. My Western Digital My Book Essential 3.0 TB USB 3.0 drive works even on the old computer whose motherboard's USB is 1.1. I tried to access that USB 3.0 hard drive on the new computer from USB 2.0 port because NetBSD has no USB 3.0 support: no go. But when I installed USB 2.0 brackets to USB 2.0 headers on the motherboard, the USB 3.0 hard drive was accessible from those USB 2.0 ports. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org One possible 'caveat'.. I've noticed occasionally it will take 75 seconds or so for a USB 3.0 drive to 'connect'.. at first I thought the drive was not being 'recognized'. Someone has posted here that they believe it could be b/c a USB 3.0 uses 2x the power of 2.0 (i've not confirmed that) and it could be due to some kind of power management on the computer.. I've not yet taken the time to sort that out. anyhow this issue initially led me to believe there was some problem with the driver, but it seems likely not the case. Waitman Gobble San Jose California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
ports. Same as in my case. USB is more a lottery than real computing for me. but this is not USB standard fault, but USB device manufacturers that cannot really read standard specifications. It works (under windoze, under linux) is enough. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
daily basis, Luckily, very few of them involve FreeBSD, which is why I do not exhibit such a negative attitude, except of course when I do attempt to plug one in a FreeBSD machine with negative results. I do not know what is more pathetic; the fact that so many devices fail to operate correctly -- if at all --, or the willingness of the FreeBSD community to accept it as the norm. usb_quirks.c is already quite large as you may see... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Sat, 23 Jun 2012 15:00:29 +0200 (CEST) Wojciech Puchar articulated: ports. Same as in my case. USB is more a lottery than real computing for me. but this is not USB standard fault, but USB device manufacturers that cannot really read standard specifications. It works (under windoze, under linux) is enough. If the ROI does not exceed the expenditure to meet a specification that only applies to a niche segment of the potential market, then it is in all probability not going to happen. Furthermore, I have seen no documented proof that the problem actually exists with the device and not with the FreeBSD implementation of the specification nor with its supplied drivers. FreeBSD has not exactly been a leader in the implementation of USB. Apparently, it doesn't fully support all variants of USB http://wiki.freebsd.org/USB although that might have recently changed. In any case, as a wise man once stated, it is better to light a candle than curse the darkness. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
windoze, under linux) is enough. If the ROI does not exceed the expenditure to meet a specification that only applies to a niche segment of the potential market, then it is in all probability not going to happen. Right. Fine. There is not written on them conforms to USB Mass Storage standard ;) ___ 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
USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: Lexar at usbus7 umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted signature.asc Description: OpenPGP digital signature
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Thu, Jun 21, 2012 at 11:01 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? I don't personally have any relevant experience with this device, but having the exact revisions of code where this was working and where it was failing would be helpful, in order to perform a binary search to determine whether or not this is a regression. Thanks, -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: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Friday 22 June 2012 08:01:38 O. Hartmann wrote: I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: Lexar at usbus7 umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted Hi, After plugging the device, try: usbconfig -d 7.6 add_quirk UQ_MSC_NO_INQUIRY Then re-plug it. I'm sorry to say a lot of USB flash sticks out there are broken and only tested with the timing of MS Windows. Part of the problem is that it is difficult to autodetect these issues, because once you trigger the non- supported SCSI command, then the flash key stops working like you experience. I would be more than glad to open up an office to certify USB devices for use with FreeBSD :-) --HPS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
incapable of handling the 64GB drive. I do not have issues with USB it's not about capacity. But seems some quirks for that pendrive (which have buggy firmware) has to be added, as it doesn't respond for inquiry command. sorry i am not USB expert. umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Fri, Jun 22, 2012 at 1:01 AM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: Lexar at usbus7 umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted I see similar behavior and output on my Dell M6500 notebook running CURRENT, but only on two ports which are some type of hybrid USB 2.0/3.0 (configurable via BIOS setting). If I use either of these ports with a USB 2.0 device while running the ports in USB 3.0 mode (using xhci(4)), I can't reliably get a device to properly attach. I say reliably, because every once in a while, I can plug a device in and it works fine, even multiple times and after reboots. If I configure these ports to run in USB 2.0 mode (using ehci(4)), all of my USB 2.0 devices seem to work without fail. However, USB 3.0 devices do not attach on these ports when they are configured as USB 2.0 ports. So, at least on my notebook, these ports must be configured at either 2.0 or 3.0, depending on which device I plan on using :( I have one other port on this same system that is USB 2.0-only, and it works all of the time :) I'll have to try and add a hub into the mix to see if perhaps it is a power issue (although with a recent Linux kernel and Windows 7, all is well no matter what configuration I provide). It may be that FreeBSD's USB subsystem lacks some extra bit of code required to configure the ports properly in regard to power. -Brandon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
On Jun 22, 2012 10:45 AM, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Fri, Jun 22, 2012 at 1:01 AM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD shown below. When first used, I was able to put approx. 30 GB of data on it - it was visible to FreeBSD 9 and 10 as expected. A Linux system at the lab was also capable of recognizing it. After that, I tried to operate on the stick on a Notebook, FreeBSD 9, and another station, FreeBSD 10. But FreeBSD didn't recognize the USB drive anymore - sometimes, but this seems to be a gambling issue :-( Trying Linux on different hardware platforms and even those machines prior not recognizing the USB drive do recognize the drive as Lexar USB Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push and pull data from it. So, since the USB drive won't work with three different FreeBSD boxes (one running 9-STABLE, two 10-CURRENT, all systems most recent sources and buildworld from a day ago). I suspect either a weird configuration issue I use on all platforms in questions in common triggering the weird beviour - or FreeBSD is simply incapable of handling the 64GB drive. I do not have issues with USB drives with capacities of 32, 8 or 4 GB of different brands. As shown in the portion of the dmesg below, the USB drive is recognized physically. It doesn't matter whether USB port I use (I tried all available on all boxes and in most cases I use a Dell UltraSharp powered in-screen HUB). Since other OSes handle the drive as expected, I exclude hardware issues. All FreeBSD in common is the fact I use the new device ahaci/device ata CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!). Apart from trying a GENERIC kernel (which is next I will do this weekend), does anyone have similar experiences and probably solutions? Regards, oh ugen7.6: Lexar at usbus7 umass1: Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6 on usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Retrying command (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted I see similar behavior and output on my Dell M6500 notebook running CURRENT, but only on two ports which are some type of hybrid USB 2.0/3.0 (configurable via BIOS setting). If I use either of these ports with a USB 2.0 device while running the ports in USB 3.0 mode (using xhci(4)), I can't reliably get a device to properly attach. I say reliably, because every once in a while, I can plug a device in and it works fine, even multiple times and after reboots. If I configure these ports to run in USB 2.0 mode (using ehci(4)), all of my USB 2.0 devices seem to work without fail. However, USB 3.0 devices do not attach on these ports when they are configured as USB 2.0 ports. So, at least on my notebook, these ports must be configured at either 2.0 or 3.0, depending on which device I plan on using :( I have one other port on this same system that is USB 2.0-only, and it works all of the time :) I'll have to try and add a hub into the mix to see if perhaps it is a power issue (although with a recent Linux kernel and Windows 7, all is well no matter what configuration I provide). It may be that FreeBSD's USB subsystem lacks some extra bit of code required to configure the ports properly in regard to power. -Brandon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org There are 3 drivers, one for 3.0, 2.0 and 1.0, and they are associated to corresponding devices at boot. I'll play around with it this weekend and see how to switch, i've also noticed issue connecting 2.0 device to 3.0 port. Waitman Gobble San Jose California USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail
No sound in my FreeBSD 9
$uname -a
FreeBSD mybsd.zsoft.com 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3
07:15:25 UTC 2012
r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
$sudo sysctl -w hw.snd.verbose=2
$cat /dev/sndstat
FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386)
Installed devices:
pcm0: Intel ICH4 (82801DB) at io 0xde081000, 0xde082000 irq 17 bufsz 16384
(1p:1v/1r:1v) default
snddev flags=0x2e2AUTOVCHAN,BUSY,MPSAFE,REGISTERED,VPC
[pcm0:play:dsp0.p0]: spd 48000, fmt 0x00200010, flags 0x2100,
0x0004
interrupts 44126, underruns 0, feed 44126, ready 0
[b:4096/2048/2|bs:4096/2048/2]
channel flags=0x2100BUSY,HAS_VCHAN
{userland} - feeder_mixer(0x00200010) - {hardware}
pcm0:play:dsp0.p0[pcm0:virtual:dsp0.vp0]: spd 44100/48000, fmt
0x00200010, flags 0x1000, 0x0029
interrupts 0, underruns 0, feed 0, ready 0
[b:0/0/0|bs:65536/2048/32]
channel flags=0x1000VIRTUAL
{userland} - feeder_root(0x00200010) - feeder_volume(0x00200010)
- feeder_rate(0x00200010 q:1 44100 - 48000) - {hardware}
[pcm0:record:dsp0.r0]: spd 48000, fmt 0x00200010, flags 0x2100,
0x0005
interrupts 0, overruns 0, feed 0, hfree 4096, sfree 4096
[b:4096/2048/2|bs:4096/2048/2]
channel flags=0x2100BUSY,HAS_VCHAN
{hardware} - feeder_root(0x00200010) - feeder_mixer(0x00200010) -
{userland}
pcm0:record:dsp0.r0[pcm0:virtual:dsp0.vr0]: spd 8000, fmt
0x0018, flags 0x1000, 0x
interrupts 0, overruns 0, feed 0, hfree 0, sfree 0
[b:0/0/0|bs:0/0/0]
channel flags=0x1000VIRTUAL
{hardware} - feeder_root(0x) - {userland}
$mixer
Mixer vol is currently set to 75:75
Mixer pcm is currently set to 75:75
Mixer speaker is currently set to 75:75
Mixer line is currently set to 75:75
Mixer mic is currently set to 0:0
Mixer cd is currently set to 75:75
Mixer rec is currently set to 75:75
Mixer igainis currently set to 0:0
Mixer line1is currently set to 75:75
Mixer phin is currently set to 0:0
$pciconf -lv | grep -i audio
device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio
Controller'
subclass = audio
subclass = audio
$dmesg | grep -i audio
pci1: multimedia, audio at device 0.0 (no driver attached)
However the sound is OK using XP on the same box (so the sound card has no
problem)
$gpart show ada0
= 63 39874304 ada0 MBR (19G)
63 19534977 1 !12 [active] (9.3G)
19535040 20338668 2 freebsd (9.7G)
39873708 659- free - (329k)
The GENERIC kernel has loaded driver( snd_ich ), but i can hear nothing.
Any suggestion is appreciated!
-
e^(π.i) + 1 = 0
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/No-sound-in-my-FreeBSD-9-tp5720280.html
Sent from the freebsd-questions mailing list archive at Nabble.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: No sound in my FreeBSD 9
On Wed, Jun 20, 2012 at 7:21 PM, sw2wolf czsq...@163.com wrote: pci1: multimedia, audio at device 0.0 (no driver attached) http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html -- 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
Wterm and FreeBSD 9
Greetings...
For FreeBSD 8, we see this for wterm:
BROKEN= does not compile
.if ${OSVERSION} 97
BROKEN= fails to build with new utmpx
.endif
I'd like to confirm that wterm will build and run on 9. I'm currently
running 8.3-RELEASE-p1 FreeBSD 8.3-RELEASE-p1 #0.
Does anyone know?
Thanks, and best regards,
Joe
___
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: Wterm and FreeBSD 9
On 7 May 2012 19:35, Joe Altman freebsd-annou...@chthonic.com wrote:
Greetings...
For FreeBSD 8, we see this for wterm:
BROKEN= does not compile
.if ${OSVERSION} 97
BROKEN= fails to build with new utmpx
.endif
I'd like to confirm that wterm will build and run on 9. I'm currently
running 8.3-RELEASE-p1 FreeBSD 8.3-RELEASE-p1 #0.
Does anyone know?
Dunno, it wants WMaker.h, which they aren't shipping any more.
Looks like wterm may be obsolete.
--
--
___
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
Installing VMware Tools on FreeBSD 9, amd64
I've installed the compat6x libraries and made a symlink to /lib for libc.so.6 as per some docs I found; however, the vmware tools installation is still failing with: Unable to copy the source file /usr/local/lib/vmware-tools/modules/binary/FreeBSD8.0-amd64/vmxnet.ko to the destination file /boot/modules/vmxnet.ko. The reason being is that /usr/local/lib/vmware-tools/modules/binary/ only contains: FreeBSD6.0-amd64FreeBSD6.0-i386FreeBSD7.0-amd64 FreeBSD7.0-i386 Is this a bug in the vmware install script or have I missed something--or can I use a different option? Thing is, I'm on 9.0 RELEASE. Thanks. ___ 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: Changes in Jails from FreeBSD 6 to FreeBSD 9 -- particularly, networking and routing
On Apr 13, 2012, at 4:58 PM, Mark Felder wrote: On Fri, 13 Apr 2012 15:53:49 -0500, Chad Leigh Shire.Net LLC c...@shire.net wrote: No NAT needed since they share the network stack under Jails v1 they share the routing tables. It works. Try it. You're clearly exploiting a bug in FreeBSD 6's jails. It was a documented behavior when I first started using jails ca. 2004 in FreeBSD 5. Which is why I did it that way. ___ 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
Changes in Jails from FreeBSD 6 to FreeBSD 9 -- particularly, networking and routing
Hi All OK, so I have a server that has been running FreeBSD 6.1 and a bunch of jails, providing a few limited services. I am migrating these from real hardware and FreeBSD 6.1 with jail running, to a Xen based VPS running FreeBSD 9.0-R with a kernel rebuild from a GENERIC kernel to GENERIC plus the Xen pci device. There is one network device on the new server and it shares all addresses and the default route goes out it. Because jails in FBSD 6 shared a network stack, I could have a public network x.x.x.0/24 and public address on the host machine, and a default route in that network as well, and use a 192.168.1.0/24 address aliased on the same network interface as the IP for my jail. When doing that, from inside the jail, I could still reach the internet since it shared the route with the underlying machine. That seems to have changed on FBSD 9. Now, if I add in the 192.168.1.0/24 address and run a jail on it, with the host machine in a public network/address/route as described above, from inside the jail I CANNOT reach the internet (it is not a resolver issue as services going to numeric addresses also fail). However, the jail with the private 192.168.1.0/24 address CAN reach the host machines services even if it cannot get out onto the internet. And the HOST machine can access services on the jail running on the private IP address. (The purpose of the jail is to provide services to other jails and hosts on the same public network [all VPS on the same public vlan] and NOT to provide services to the internet. Things like local ldap or a local dns etc. But the private jail still needs to reach the internet for things like name servers it needs to access that are outside of the public network the host lives in. So I don't care if the internet itself can reach the private jail, just the local jails and hosts it co-exists with. The answer shouldn't be natd etc (was not needed in 6.0 and I am not sharing one public address with a range of private jails behind it). If I launch the jail with an address from the same public range as the host, it works fine. The jail can access the internet fine and vice versa. The host can access the jail services as well. If I launch the jail with a private address, the jail cannot reach the internet. It can reach the host in the public network, but not other machines in the same public network (ie, the other VPS I have running which are all in the same public network). If I launch the jail with both a private address and a public address, it can reach the internet and other VPS on the same public network. I may have to end up doing that and just not having any services run on the public IP but I'd rather avoid using up an address like that. What changes happened in the jails between FBSD 6 and FBSD 9 that would give the symptoms I have been experiencing? Thanks Chad ___ 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: Changes in Jails from FreeBSD 6 to FreeBSD 9 -- particularly, networking and routing
Do I understand this right? Working in FreeBSD 6.x: interface em0: 1.2.3.4/24 -- public IP, host only 192.168.1.1/24 -- private IP, host only 192.168.1.2/24 -- Jail #1 192.168.1.3/24 -- Jail #2 With this configuration you had no problems accessing the internet from the jails. Is this correct? This seems bizarre; this should only be possible if you're doing NAT somewhere in there and that is not possible with Jails v1 (which share a network stack) and is only possible in Jails v2 (vnet). ___ 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: Changes in Jails from FreeBSD 6 to FreeBSD 9 -- particularly, networking and routing
On Apr 13, 2012, at 1:50 PM, Mark Felder wrote: Do I understand this right? Working in FreeBSD 6.x: interface em0: 1.2.3.4/24 -- public IP, host only 192.168.1.1/24 -- private IP, host only 192.168.1.2/24 -- Jail #1 192.168.1.3/24 -- Jail #2 With this configuration you had no problems accessing the internet from the jails. correct. (not that it did not matter I don't think is the private IP, host only exists and ALL IP exist on the host in addition to whatever Jail they are assigned to) Is this correct? This seems bizarre; this should only be possible if you're doing NAT somewhere in there and that is not possible with Jails v1 (which share a network stack) and is only possible in Jails v2 (vnet). No NAT needed since they share the network stack under Jails v1 they share the routing tables. It works. Try it. The question is, is it possible to do something similar with FreeBSD 9 jails (v2 I guess) without the overhead of running NAT? The jail with the private IP *can* access the HOST's public services but not anyone else's Chad ___ 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: Changes in Jails from FreeBSD 6 to FreeBSD 9 -- particularly, networking and routing
On Fri, 13 Apr 2012 15:53:49 -0500, Chad Leigh Shire.Net LLC c...@shire.net wrote: No NAT needed since they share the network stack under Jails v1 they share the routing tables. It works. Try it. You're clearly exploiting a bug in FreeBSD 6's jails. It must get confused and send your public IP on those packets. I have no idea how it processes the return traffic successfully, but that's a neat trick!. There is no possible way for this to work without NAT or whatever bug this is. If a Jail has a 192.168 IP all packets would leave with a source of 192.168. When Google or whoever on the internet gets your packets it would see 192.168 and probably drop it because that's not a publicly routable network. Without NAT it's impossible for any device anywhere on the planet to access the internet with an RFC 1918 IP address. I urge you to share your experience on the freebsd-jail@ mailing list. Those guys might be able to lend some further insight. I bet the change came with the update to jails that allows multiple IPs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9's SSH HPN
On Mon, Mar 19, 2012 at 8:45 PM, Mark Felder f...@feld.me wrote: Is the HPN patchset included with the base OpenSSH the full patchset? Does it include the threaded CTR patch? I can't seem to find a clear answer to this. crypto/openssh/README.hpn references it so I would assume so. -- 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
FreeBSD 9's SSH HPN
Is the HPN patchset included with the base OpenSSH the full patchset? Does it include the threaded CTR patch? I can't seem to find a clear answer to this. Thanks, Mark ___ 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 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
Hi, I've got a 9.0-R amd64 system I'm trying to netboot / pxeboot from the network, to install other machines (and do fixups etc.) I set this up as we setup previous versions here - but setting up a tftp server, and nfs server - and 'dumping' the contents of the install CD to a directory on the dhcp server, which is exported via nfs (it's exported as read/write). The system kind of boots, but falls over with: Interface em0 IP-Address 192.168.0.47 Broadcast 192.168.0.255 Entropy harvesting: interrupts ethernet point_to_pick kickstart. Starting file system checks: mount_nfs: no host:dirpath nfs-name Mounting root filesystem rw failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Mar 1 118:10 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: It looks like it's failing to 'remount' / promote the root file system as read/write (It's definitely exported as read/write - I've tested it by mounting it on another machine). If you start a shell at this point and run mount, you get: 192.168.0.37:/usr2/netboot/os/9.0-amd64 on / (nfs, read-only) devfs on /dev (devfs, local, multilabel) Is there something I have to set (e.g. in '/etc/rc.conf') in order to fix this? Previous systems setup this way would always boot through to the sysinstall menu. Thanks, -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
Take a look at freebsd-hackers mailing list... I have suggested some change in some Makefile and sh script in order to unless at this moment to be able to have an unattended system built with sysinstall (the idea I think it was to maintain sysinstall in 9.0 unless) and using you're install.cfg At freebsd-hackers seems that people is pretty busy and can't look at this in order for committing or unless saying something about it... perhaps they're working on another thing or so, or don't know I assume they can't check this now... but like changes are not significant... I am going to do with the changes suggested and have tested and release builts fine and you can use Jumpstart without issues.. this way... So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! El Jue, 1 de Marzo de 2012, 11:24 am, Karl Pielorz escribió: Hi, I've got a 9.0-R amd64 system I'm trying to netboot / pxeboot from the network, to install other machines (and do fixups etc.) I set this up as we setup previous versions here - but setting up a tftp server, and nfs server - and 'dumping' the contents of the install CD to a directory on the dhcp server, which is exported via nfs (it's exported as read/write). The system kind of boots, but falls over with: Interface em0 IP-Address 192.168.0.47 Broadcast 192.168.0.255 Entropy harvesting: interrupts ethernet point_to_pick kickstart. Starting file system checks: mount_nfs: no host:dirpath nfs-name Mounting root filesystem rw failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Mar 1 118:10 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: It looks like it's failing to 'remount' / promote the root file system as read/write (It's definitely exported as read/write - I've tested it by mounting it on another machine). If you start a shell at this point and run mount, you get: 192.168.0.37:/usr2/netboot/os/9.0-amd64 on / (nfs, read-only) devfs on /dev (devfs, local, multilabel) Is there something I have to set (e.g. in '/etc/rc.conf') in order to fix this? Previous systems setup this way would always boot through to the sysinstall menu. Thanks, -Karl ___ 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: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
--On 01 March 2012 11:53 +0100 ego...@ramattack.net wrote: So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! For what it's worth - I've resolved the issue I had (which was basically the system booted, but failed trying to re-mount root as RW, and hence wouldn't go into the installer). The fix I did was to change the '/etc/fstab' on the Netboot server (i.e. the copy of FreeBSD that you're booting). It contains: /dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Just commenting out that line, i.e. #/dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Means the boot now completes, and I get offered the Install / Shell / Live CD prompt, instead of an error about not being able to remount root. I've yet to complete an install this way (so far we're just using a script to extract the new 9.x style '.txz' files). But that little change does let us netboot correctly now, enough for what we need. -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
In the new way of booting... you need to have the cd because the own cd is the root filesystem... and in fact is live filesystem too so unless you're booting from mfsroot... I assume you should have that line in /etc/fstab inside the iso image but if you're using mfsroot... I really even am not creating etc dir inside the iso image... because it's not needed and in previous releases and iso images when always booted from mfsroot (and where not livefs cds and so) it wasn't necessary... On Thu, 01 Mar 2012 12:43:58 +, Karl Pielorz wrote: --On 01 March 2012 11:53 +0100 ego...@ramattack.net wrote: So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! For what it's worth - I've resolved the issue I had (which was basically the system booted, but failed trying to re-mount root as RW, and hence wouldn't go into the installer). The fix I did was to change the '/etc/fstab' on the Netboot server (i.e. the copy of FreeBSD that you're booting). It contains: /dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Just commenting out that line, i.e. #/dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Means the boot now completes, and I get offered the Install / Shell / Live CD prompt, instead of an error about not being able to remount root. I've yet to complete an install this way (so far we're just using a script to extract the new 9.x style '.txz' files). But that little change does let us netboot correctly now, enough for what we need. -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9, GPT and gmirror
On Thu, 09 Feb 2012 07:02:29 -0800 per...@pluto.rain.com wrote: Janos Dohanics w...@3dresearch.com wrote: 1. The Guided partitioning doesn't suggest any more to create /var, /tmp, /usr, etc. file systems. Is it really the recommendation to go with just / ? Depends on who you ask :) and on your intended usage. 2. Is there a way to use the old sysinstall to install FreeBSD 9? Not using the standard distribution IIUC. You might want to look at http://druidbsd.sf.net/ [...] This may be just what I need - thank you. -- Janos Dohanics ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9, GPT and gmirror
On Thu, 09 Feb 2012 20:20:03 +0100 Michael Cardell Widerkrantz m...@hack.org wrote: Janos Dohanics w...@3dresearch.com, 2012-02-08 19:42 (+0100): 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? I think the guide you linked to: http://blather.michaelwlucas.com/archives/1071 meant that you have to be in single user mode until you have edited /etc/fstab to point to the mirror, otherwise you wouldn't boot with root on the mirror. The synchronization between the disks works fine in multi-user mode as well. I have two 2 TiB disks in gmirror set up just like that. Synchronization was done running in multi-user. You are right - just removed and then re-inserted a component in one of the mirrors and the mirror synchronized fine in multi-user mode. -- Janos Dohanics ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9, GPT and gmirror
Janos Dohanics w...@3dresearch.com wrote: 1. The Guided partitioning doesn't suggest any more to create /var, /tmp, /usr, etc. file systems. Is it really the recommendation to go with just / ? Depends on who you ask :) and on your intended usage. 2. Is there a way to use the old sysinstall to install FreeBSD 9? Not using the standard distribution IIUC. You might want to look at http://druidbsd.sf.net/ 3. It seems that setting up gmirror is more involved with GPT (http://blather.michaelwlucas.com/archives/1071); now I have a mirror for each of the filesystems /, /var, /tmp, etc. Is it OK to use gmirror in this way at all? Yes, indeed it is the only way to combine GPT and gmirror without getting into trouble of one sort or another. (The conflict between GPT and a full-disk gmirror is actually not new.) 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? Dunno about this one. 3. Assuming one has enough RAM, is zfs mirror or raidz recommended over gmirror? Same situation as with #1. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9, GPT and gmirror
Janos Dohanics w...@3dresearch.com, 2012-02-08 19:42 (+0100): 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? I think the guide you linked to: http://blather.michaelwlucas.com/archives/1071 meant that you have to be in single user mode until you have edited /etc/fstab to point to the mirror, otherwise you wouldn't boot with root on the mirror. The synchronization between the disks works fine in multi-user mode as well. I have two 2 TiB disks in gmirror set up just like that. Synchronization was done running in multi-user. -- http://hack.org/mc/ Warning! Plain text e-mail, please. HTML e-mail deleted unread. OpenPGP: 673B 563E 3C78 1BA0 6525 2344 B22E 2C10 E4C9 2FA5 ___ 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: pkg_rmleaves in FreeBSD 9
On 08/02/2012 04:55, Kevin Zheng wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I often use pkg_rmleaves(1) to uninstall unused programs on FreeBSD. I'm in the process of test-driving a FreeBSD 9 system on a virtual machine. I've noticed that pkg_rmleaves doesn't take up the entire width of the window anymore. Quite frankly, I like it when pkg_rmleaves takes up the entire window, so is there any nice way to get it (or dialog) to take the entire screen? Thanks, Kevin Zheng For me, it takes the entire screen, I advise you to try out ports-mgmt/pkg_cleanup it is exactly more up to date as pkg_rmleaves is completely outdated. Cheers, -- David Demelier ___ 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 9, GPT and gmirror
Hello Everyone, May be I should have searched more for answers, but after installing FreeBSD 9 with gmirror, I am wondering if the experts here have some recommendations for best practices. 1. The Guided partitioning doesn't suggest any more to create /var, /tmp, /usr, etc. file systems. Is it really the recommendation to go with just / ? 2. Is there a way to use the old sysinstall to install FreeBSD 9? 3. It seems that setting up gmirror is more involved with GPT (http://blather.michaelwlucas.com/archives/1071); now I have a mirror for each of the filesystems /, /var, /tmp, etc. Is it OK to use gmirror in this way at all? 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? 3. Assuming one has enough RAM, is zfs mirror or raidz recommended over gmirror? Prior to FreeBSD 9, I used to take the the sysinstall defaults with some overrides as I thought appropriate and proceeded to set up gmirror - it was simple and not a lot of work, and a good way to make use of older systems... -- Janos Dohanics ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9, GPT and gmirror
On Wed, 8 Feb 2012 13:42:59 -0500 Janos Dohanics w...@3dresearch.com wrote: Hello Everyone, May be I should have searched more for answers, but after installing FreeBSD 9 with gmirror, I am wondering if the experts here have some recommendations for best practices. 1. The Guided partitioning doesn't suggest any more to create /var, /tmp, /usr, etc. file systems. Is it really the recommendation to go with just / ? This is a bad recommendation I think, but you can accept guidance and the adjust to your needs. 2. Is there a way to use the old sysinstall to install FreeBSD 9? Yes, harder to use, or no the new installer should have some more sane defaults 3. It seems that setting up gmirror is more involved with GPT (http://blather.michaelwlucas.com/archives/1071); now I have a mirror for each of the filesystems /, /var, /tmp, etc. Is it OK to use gmirror in this way at all? 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? 3. Assuming one has enough RAM, is zfs mirror or raidz recommended over gmirror? gmirror, still I think Prior to FreeBSD 9, I used to take the the sysinstall defaults with some overrides as I thought appropriate and proceeded to set up gmirror - it was simple and not a lot of work, and a good way to make use of older systems... I think the new installer is quite good, but needs some shaving around the rough edges Cheers Disclaimer: http://www.ose.nl/email ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9, GPT and gmirror
3. Assuming one has enough RAM, is zfs mirror or raidz recommended over gmirror? zfs mirror but I would not recommend a raidz root on zfs. -- George Kontostanos Aicom telecoms ltd http://www.aisecure.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9, GPT and gmirror
I can't speak to the mirror issue, but I had difficulty trying to tweak the defaults in the install on a 128G SSD: When manually configuring the SSD, I tried to leave some extra space at the end of the SSD. Not sure that is necessary or not. In any case, I had a 128GB SSD, reported as 119GB. Auto config laid it out as ada1 119GB ada1p1 64KB freebsd-boot ada1p2 115GB freebsd-ufs / ada1p34GB freebsd-swap I then deleted the last 2 and re-created as 100GB and 4GB, at which point it showed ada1 119GB ada1p1 64KB freebsd-boot ada1p2 100GB freebsd-ufs / ada1p3 -15GB freebsd-swap (I may have the -15 wrong; main point is it was negative) After deleting and recreating in different order I managed to get it to ada1 119GB ada1p1 64KB freebsd-boot ada1p34GB freebsd-swap ada1p2 100GB freebsd-ufs / but when I tried to commit it, I got the error: Error mounting partition /mnt: mount: /dev/ada1p2: Operation not permitted The only way I could get it to actually write the distribution was to use auto and keep what it came up with. Is this problem specific to SSDs (seems unlikely)? Is there some magic sequence needed to tweak the Auto result to get it to work? Gary On 2/8/2012 12:00 PM, Bas Smeelen wrote: On Wed, 8 Feb 2012 13:42:59 -0500 Janos Dohanicsw...@3dresearch.com wrote: Hello Everyone, May be I should have searched more for answers, but after installing FreeBSD 9 with gmirror, I am wondering if the experts here have some recommendations for best practices. 1. The Guided partitioning doesn't suggest any more to create /var, /tmp, /usr, etc. file systems. Is it really the recommendation to go with just / ? This is a bad recommendation I think, but you can accept guidance and the adjust to your needs. 2. Is there a way to use the old sysinstall to install FreeBSD 9? Yes, harder to use, or no the new installer should have some more sane defaults 3. It seems that setting up gmirror is more involved with GPT (http://blather.michaelwlucas.com/archives/1071); now I have a mirror for each of the filesystems /, /var, /tmp, etc. Is it OK to use gmirror in this way at all? 4. Also, with GPT, one has to be in single user mode to synchronize disks - correct? 3. Assuming one has enough RAM, is zfs mirror or raidz recommended over gmirror? gmirror, still I think Prior to FreeBSD 9, I used to take the the sysinstall defaults with some overrides as I thought appropriate and proceeded to set up gmirror - it was simple and not a lot of work, and a good way to make use of older systems... I think the new installer is quite good, but needs some shaving around the rough edges Cheers Disclaimer: http://www.ose.nl/email ___ 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
pkg_rmleaves in FreeBSD 9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I often use pkg_rmleaves(1) to uninstall unused programs on FreeBSD. I'm in the process of test-driving a FreeBSD 9 system on a virtual machine. I've noticed that pkg_rmleaves doesn't take up the entire width of the window anymore. Quite frankly, I like it when pkg_rmleaves takes up the entire window, so is there any nice way to get it (or dialog) to take the entire screen? Thanks, Kevin Zheng -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPMfIeAAoJEII9RSpevmRH3D8IAIvKEUaiE4EWvk7+i4X90Whq V43ldUAYmnHNWoWLKz7iBHvxFfnH6+2VSJevIkIvlrk0fI1o7fIgI9pWck/wi9tn 4NuXX7TdRMB4uX0JPRhRqZ5gIbMtsxemH0KLbyyL3IyTu/cb0GHc8gpmQ8eNZh1u Z78ZTOviQV20e9MQ9bpneNWtcMInOIms2wwg9VCSUAtwtr6eNkFiNmHXHUvRavJy CZiPtTC2az2jK3U0i2NX1NNMnk/VmRSOjHBwgo1Lf4GICi96N19g945Ivof5S9Gb w2jgacHvQMWiPmWRI+P75E/xaHmNfmn0NOzB9Zb4YsD6jsg93R+GOKfpyEFQKeo= =HcYG -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 buildworld with clang failure
On 02.02.2012 15:12, ill...@gmail.com wrote: Might try: Commenting out CFLAGS= Setting NO_WERROR= in /etc/make.conf Removing the CFLAGS= line made no difference, after some searching for info about the NO_WERROR=, I went ahead and added the CFLAGS line back in added NO_WERROR= WERROR= lines both in the /etc/make.conf, and it completed. Now to find out how many ports will compile, and then actually test everything, fortunately the production system I am modeling this test after only has 123 ports installed. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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 9 buildworld with clang failure
I am trying to rebuild everything in a development machine with clang
to test for production, and ran into a problem on the buildworld
process. This machine was already rebuilt from source using gcc, here
are the options I have set in make.conf and src.conf. The lines I added
to enable clang, and the steps I took to compile.
Options in /etc/src.conf
WITHOUT_BIND_DNSSEC=YES
WITHOUT_BIND_LIBS_LWRES=YES
WITHOUT_BIND_NAMED=YES
WITHOUT_BIND_UTILS=YES
WITHOUT_NTP=YES
WITHOUT_PROFILE=YES
Options already in /etc/make.conf
WITH_OPENSSL_PORT=yes
WITHOUT_X11=yes
CFLAGS= -O -pipe
PERL_VERSION=5.12.4
Added to /etc/make.conf
.if !defined(USE_GCC)
.if !defined(CC) || ${CC} == cc
CC=clang
.endif
.if !defined(CXX) || ${CXX} == c++
CXX=clang++
.endif
.if !defined(CPP) || ${CPP} == cpp
CPP=clang-cpp
.endif
.endif
Did the cleanup process from previous build and currently installed
setup.
chflags -R noschg /usr/obj/usr
rm -rf /usr/obj/usr
cd /usr/src
make cleandir
make cleandir
Then ran make buildworld, it died on libc with the following output:
=== lib/libc (obj,depend,all,install)
clang -O -pipe -I/usr/src/lib/libc/include
-I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -DNLS
-D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6
-I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv -D_ACL_PRIVATE
-DPOSIX_MISTAKE -I/usr/src/lib/libc/../../contrib/tzcode/stdtime
-I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -DBROKEN_DES
-DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING
-DSYMBOL_VERSIONING -std=gnu99 -fstack-protector -Wsystem-headers
-Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c
/usr/src/lib/libc/gen/setjmperr.c
In file included from /usr/src/lib/libc/gen/setjmperr.c:44:
/usr/src/lib/libc/../../include/setjmp.h:58:5: error: incompatible
redeclaration of library function
'sigsetjmp' [-Werror]
int sigsetjmp(sigjmp_buf, int);
^
/usr/src/lib/libc/../../include/setjmp.h:58:5: note: 'sigsetjmp' is a
builtin with type
'int (struct _jmp_buf *, int)'
1 error generated.
*** Error code 1
Stop in /usr/src/lib/libc.
*** Error code 1
Anyone have any idea where I went wrong?
--
Thanks,
Dean E. Weimer
http://www.dweimer.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 buildworld with clang failure
On 2 February 2012 14:43, Dean E. Weimer dwei...@dweimer.net wrote:
I am trying to rebuild everything in a development machine with clang to
test for production, and ran into a problem on the buildworld process. This
machine was already rebuilt from source using gcc, here are the options I
have set in make.conf and src.conf. The lines I added to enable clang, and
the steps I took to compile.
Options in /etc/src.conf
WITHOUT_BIND_DNSSEC=YES
WITHOUT_BIND_LIBS_LWRES=YES
WITHOUT_BIND_NAMED=YES
WITHOUT_BIND_UTILS=YES
WITHOUT_NTP=YES
WITHOUT_PROFILE=YES
Options already in /etc/make.conf
WITH_OPENSSL_PORT=yes
WITHOUT_X11=yes
CFLAGS= -O -pipe
PERL_VERSION=5.12.4
Added to /etc/make.conf
.if !defined(USE_GCC)
.if !defined(CC) || ${CC} == cc
CC=clang
.endif
.if !defined(CXX) || ${CXX} == c++
CXX=clang++
.endif
.if !defined(CPP) || ${CPP} == cpp
CPP=clang-cpp
.endif
.endif
Did the cleanup process from previous build and currently installed setup.
chflags -R noschg /usr/obj/usr
rm -rf /usr/obj/usr
cd /usr/src
make cleandir
make cleandir
Then ran make buildworld, it died on libc with the following output:
=== lib/libc (obj,depend,all,install)
clang -O -pipe -I/usr/src/lib/libc/include
-I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -DNLS
-D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6
-I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv -D_ACL_PRIVATE
-DPOSIX_MISTAKE -I/usr/src/lib/libc/../../contrib/tzcode/stdtime
-I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -DBROKEN_DES
-DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING
-DSYMBOL_VERSIONING -std=gnu99 -fstack-protector -Wsystem-headers -Werror
-Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c
/usr/src/lib/libc/gen/setjmperr.c
In file included from /usr/src/lib/libc/gen/setjmperr.c:44:
/usr/src/lib/libc/../../include/setjmp.h:58:5: error: incompatible
redeclaration of library function
'sigsetjmp' [-Werror]
int sigsetjmp(sigjmp_buf, int);
^
/usr/src/lib/libc/../../include/setjmp.h:58:5: note: 'sigsetjmp' is a
builtin with type
'int (struct _jmp_buf *, int)'
1 error generated.
*** Error code 1
Stop in /usr/src/lib/libc.
*** Error code 1
Might try:
Commenting out CFLAGS=
Setting NO_WERROR= in /etc/make.conf
--
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 on Lenovo X200 what works?
On 01/26/2012 01:57 AM, Da Rock wrote: Despite having similar hardware, you're only real best bet is to suck it and see. Try installing and seeing what you can get to work (dmesg, pciconf -lv, usbconfig, kldload modules, questions here, etc). I've had mixed success with laptops (they're just about all I have as a desktop), and about my only problems have been with wifi- though that has mostly disappeared with Adrian's excellent work. I will have a go as Salix (which is on there now isn't cutting it and spent all night trying to get things in order but didn't :( Tested the live FBSD9 disk in the meantime and the wireless gets detected out of the box. As long as I get wifi and HD video and sound coming out of the headphone socket I will be fine I'm running 8.2 on an X200. For the most part everything works. My main complaint is that the sound is very quiet, and I haven't found the setting to fix that. Video and wifi work fine. The kernel sees the camera and the thumb reader but I haven't looked for applications that use them. Ok this sounds promising - for wifi see above! App for camera is Googletalk if supported on Firefox 9, and PAM for the figureprint reader. Just thinkin about WWAN now but there was a post floating around about 3G modems so I might just be in luck not that I've ever used WiMax before. Thanks for the replies guys :-) Regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9 and 3G Modems
On Wed, Jan 25, 2012 at 18:54, Mike Tancsa m...@sentex.net wrote: On 1/25/2012 5:43 AM, Odhiambo Washington wrote: I have a Huawei E1820 I will also try RTFM. Hi, kldload u3g kldload umodem Done, although kldload u3g tells me that file already exists! Perhaps because I booted up with my Huawei dongle plugged in. kldstat | grep u3g shows me nothing though. plug in the modem Show the output of usbconfig [wash@pcbsd9] /home/wash# usbconfig ugen0.1: UHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen1.1: UHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen2.1: EHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.1: UHCI root HUB Intel at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen4.1: UHCI root HUB Intel at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen5.1: UHCI root HUB Intel at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen6.1: EHCI root HUB Intel at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen6.2: HUAWEI Mobile Huawei Technologies at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: BCM2045B Broadcom Corp at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.3: Biometric Coprocessor STMicroelectronics at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.2: Microsoft Nano Transceiver v1.0 Microsoft at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON then sysctl -a dev.u3g [wash@pcbsd9] /home/wash# sysctl -a dev.u3g dev.u3g.0.%desc: Huawei Technologies HUAWEI Mobile, class 0/0, rev 2.00/0.00, addr 2 dev.u3g.0.%driver: u3g dev.u3g.0.%location: bus=1 hubaddr=1 port=6 devaddr=2 interface=0 dev.u3g.0.%pnpinfo: vendor=0x12d1 product=0x1001 devclass=0x00 devsubclass=0x00 sernum= release=0x mode=host intclass=0xff intsubclass=0xff intprotocol=0xff ttyname=U0 ttyports=3 dev.u3g.0.%parent: uhub and ls -l /dev/cuaU* [wash@pcbsd9] /home/wash# ls -l /dev/cuaU* crw-rw 1 uucp dialer0, 117 Jan 26 18:23 /dev/cuaU0.0 crw-rw 1 uucp dialer0, 118 Jan 26 18:23 /dev/cuaU0.0.init crw-rw 1 uucp dialer0, 119 Jan 26 18:23 /dev/cuaU0.0.lock crw-rw 1 uucp dialer0, 123 Jan 26 18:23 /dev/cuaU0.1 crw-rw 1 uucp dialer0, 124 Jan 26 18:23 /dev/cuaU0.1.init crw-rw 1 uucp dialer0, 125 Jan 26 18:23 /dev/cuaU0.1.lock crw-rw 1 uucp dialer0, 129 Jan 26 18:23 /dev/cuaU0.2 crw-rw 1 uucp dialer0, 130 Jan 26 18:23 /dev/cuaU0.2.init crw-rw 1 uucp dialer0, 131 Jan 26 18:23 /dev/cuaU0.2.lock and dmesg [wash@pcbsd9] /home/wash# dmesg Copyright (c) 1992-2011 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 9.0-RELEASE #3: Tue Dec 27 14:14:29 PST 2011 r...@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC amd64 CPU: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz (1995.05-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6fa Family = 6 Model = f 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=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 4000251904 (3814 MB) Event timer LAPIC quality 400 ACPI APIC Table: LENOVO TP-7L FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32 (20110527/tbfadt-556) ACPI Warning: Optional field Gpe1Block has zero address or length: 0x102C/0x0 (20110527/tbfadt-586) ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 cryptosoft0: software crypto on motherboard acpi0: LENOVO TP-7L on motherboard CPU0: local APIC error 0x40 acpi_ec0: Embedded Controller: GPE 0x12, ECDT port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bff0 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x2000-0x207f mem 0xd600-0xd6ff,0xe000-0xefff,0xd400-0xd5ff irq 16 at device 0.0 o n pci1 nvidia0: Quadro NVS 140M on vgapci0 vgapci0: child nvidia0 requested pci_enable_io
Re: FreeBSD 9 and 3G Modems
On 1/26/2012 10:58 AM, Odhiambo Washington wrote: Hi, kldload u3g kldload umodem Done, although kldload u3g tells me that file already exists! Perhaps because I booted up with my Huawei dongle plugged in. kldstat | grep u3g shows me nothing though. Looks like its already defined in the kernel! ugen6.2: HUAWEI Mobile Huawei Technologies at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON It sees it. then sysctl -a dev.u3g [wash@pcbsd9] /home/wash# sysctl -a dev.u3g dev.u3g.0.%desc: Huawei Technologies HUAWEI Mobile, class 0/0, rev 2.00/0.00, addr 2 dev.u3g.0.%driver: u3g dev.u3g.0.%location: bus=1 hubaddr=1 port=6 devaddr=2 interface=0 dev.u3g.0.%pnpinfo: vendor=0x12d1 product=0x1001 devclass=0x00 devsubclass=0x00 sernum= release=0x mode=host intclass=0xff intsubclass=0xff intprotocol=0xff ttyname=U0 ttyports=3 dev.u3g.0.%parent: uhub More importantly, the driver sees it and has used cuaU0.* and ls -l /dev/cuaU* [wash@pcbsd9] /home/wash# ls -l /dev/cuaU* crw-rw 1 uucp dialer0, 117 Jan 26 18:23 /dev/cuaU0.0 crw-rw 1 uucp dialer0, 118 Jan 26 18:23 /dev/cuaU0.0.init crw-rw 1 uucp dialer0, 119 Jan 26 18:23 /dev/cuaU0.0.lock crw-rw 1 uucp dialer0, 123 Jan 26 18:23 /dev/cuaU0.1 crw-rw 1 uucp dialer0, 124 Jan 26 18:23 /dev/cuaU0.1.init crw-rw 1 uucp dialer0, 125 Jan 26 18:23 /dev/cuaU0.1.lock crw-rw 1 uucp dialer0, 129 Jan 26 18:23 /dev/cuaU0.2 crw-rw 1 uucp dialer0, 130 Jan 26 18:23 /dev/cuaU0.2.init crw-rw 1 uucp dialer0, 131 Jan 26 18:23 /dev/cuaU0.2.lock This is where you need to do a bit of experimenting. Some modems register these sub ports and others do not. Some are for out of band control and one will be the device you actually use in your ppp config. The init string sort of depends on your carrier. But a basic one to try in ppp.conf is below. For the set device line, you might need to change it to /dev/cuaU0.1 or /dev/cuaU0.2 invoke with ppp -ddial u3g You might need the authname and auth key, you might not. For the context you might need to change it from internet.com to something else. Again, ask your carrier for that info. Try first without the CGDCONT line as the default in the modem might do the trick. u3g: set device /dev/cuaU0.0 set server /var/run/gprs-internet 0177 set speed 921600 set timeout 0 set authname wapuser1 set authkey wap set dial ABORT BUSY TIMEOUT 2 \ \\ \ AT OK-AT-OK \ AT+CFUN=1 OK-AT-OK \ AT+CMEE=2 OK-AT-OK \ AT+CSQ OK \ AT+CGDCONT=1,\\\IP\\\,\\\internet.com\\\ OK \ ATv OK \ ATD*99# CONNECT set crtscts on disable vjcomp disable acfcomp disable deflate disable deflate24 disable pred1 disable protocomp disable mppe disable ipv6cp disable lqr disable echo #nat enable yes enable dns resolv writable set dns 8.8.8.8 set ifaddr 10.1.0.2/0 10.1.0.1/0 255.255.255.255 0.0.0.0 add default HISADDR # See ppp.link* -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.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: FreeBSD 9 and 3G Modems
On Thu, Jan 26, 2012 at 19:12, Mike Tancsa m...@sentex.net wrote: On 1/26/2012 10:58 AM, Odhiambo Washington wrote: Hi, kldload u3g kldload umodem Done, although kldload u3g tells me that file already exists! Perhaps because I booted up with my Huawei dongle plugged in. kldstat | grep u3g shows me nothing though. Looks like its already defined in the kernel! ugen6.2: HUAWEI Mobile Huawei Technologies at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON It sees it. then sysctl -a dev.u3g [wash@pcbsd9] /home/wash# sysctl -a dev.u3g dev.u3g.0.%desc: Huawei Technologies HUAWEI Mobile, class 0/0, rev 2.00/0.00, addr 2 dev.u3g.0.%driver: u3g dev.u3g.0.%location: bus=1 hubaddr=1 port=6 devaddr=2 interface=0 dev.u3g.0.%pnpinfo: vendor=0x12d1 product=0x1001 devclass=0x00 devsubclass=0x00 sernum= release=0x mode=host intclass=0xff intsubclass=0xff intprotocol=0xff ttyname=U0 ttyports=3 dev.u3g.0.%parent: uhub More importantly, the driver sees it and has used cuaU0.* and ls -l /dev/cuaU* [wash@pcbsd9] /home/wash# ls -l /dev/cuaU* crw-rw 1 uucp dialer0, 117 Jan 26 18:23 /dev/cuaU0.0 crw-rw 1 uucp dialer0, 118 Jan 26 18:23 /dev/cuaU0.0.init crw-rw 1 uucp dialer0, 119 Jan 26 18:23 /dev/cuaU0.0.lock crw-rw 1 uucp dialer0, 123 Jan 26 18:23 /dev/cuaU0.1 crw-rw 1 uucp dialer0, 124 Jan 26 18:23 /dev/cuaU0.1.init crw-rw 1 uucp dialer0, 125 Jan 26 18:23 /dev/cuaU0.1.lock crw-rw 1 uucp dialer0, 129 Jan 26 18:23 /dev/cuaU0.2 crw-rw 1 uucp dialer0, 130 Jan 26 18:23 /dev/cuaU0.2.init crw-rw 1 uucp dialer0, 131 Jan 26 18:23 /dev/cuaU0.2.lock This is where you need to do a bit of experimenting. Some modems register these sub ports and others do not. Some are for out of band control and one will be the device you actually use in your ppp config. The init string sort of depends on your carrier. But a basic one to try in ppp.conf is below. For the set device line, you might need to change it to /dev/cuaU0.1 or /dev/cuaU0.2 invoke with ppp -ddial u3g You might need the authname and auth key, you might not. For the context you might need to change it from internet.com to something else. Again, ask your carrier for that info. Try first without the CGDCONT line as the default in the modem might do the trick. u3g: set device /dev/cuaU0.0 set server /var/run/gprs-internet 0177 set speed 921600 set timeout 0 set authname wapuser1 set authkey wap set dial ABORT BUSY TIMEOUT 2 \ \\ \ AT OK-AT-OK \ AT+CFUN=1 OK-AT-OK \ AT+CMEE=2 OK-AT-OK \ AT+CSQ OK \ AT+CGDCONT=1,\\\IP\\\,\\\internet.com\\\ OK \ ATv OK \ ATD*99# CONNECT set crtscts on disable vjcomp disable acfcomp disable deflate disable deflate24 disable pred1 disable protocomp disable mppe disable ipv6cp disable lqr disable echo #nat enable yes enable dns resolv writable set dns 8.8.8.8 set ifaddr 10.1.0.2/0 10.1.0.1/0 255.255.255.255 0.0.0.0 add default HISADDR # See ppp.link* Hi Mike, I guess the internet.com in AT+CGDCONT=1,\\\IP\\\,\\\internet.com\\\ OK \ refer to the APN? I know I need to read ppp.conf again soon :) ppp.log: Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: default: set timeout 180 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: default: enable dns Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set device /dev/cuaU0.0 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set server /var/run/gprs-internet 0177 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Warning: Local: bind: Address already in use Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Warning: set server: Failed 2 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set speed 921600 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set timeout 0 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set authname saf Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set authkey Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set dial ABORT BUSY TIMEOUT 2AT OK-AT-OKAT+CFUN=1 OK-AT-OK AT+CMEE=2 OK-AT-OKAT+CSQ OK AT+CGDCONT=1,\IP\,\safaricom\ OKATv OKATD*99# CONNECT Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: set crtscts on Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable vjcomp Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable acfcomp Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable deflate Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable deflate24 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable pred1 Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable protocomp Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command: u3g: disable mppe Jan 26 19:58:39 pcbsd9 ppp[7367]: tun0: Command:
Re: FreeBSD 9 and 3G Modems
Odhiambo Washington odhia...@gmail.com writes: On Wed, Jan 25, 2012 at 18:54, Mike Tancsa m...@sentex.net wrote: On 1/25/2012 5:43 AM, Odhiambo Washington wrote: I have a Huawei E1820 I will also try RTFM. Hi, kldload u3g kldload umodem Done, although kldload u3g tells me that file already exists! Perhaps because I booted up with my Huawei dongle plugged in. kldstat | grep u3g shows me nothing though. The command 'kldstat -v' shows that u3g is already compiled in for the 9.0-RELEASE kernel. -- Carl Johnsonca...@peak.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
