xfburn and k3b on FreeBSD9.0-RELEASE can't find LITE-ON DVDRW
Hi, I can't get any GUI tool working with my LITE-ON DVDRW SHW-160P6S (IDE) on 9.0-RELEASE (packages and ports tree are in sync from the release date). atapicam is compiled in GENERIC kernel now, so no need for this module. I recompiled cdrtools, dvd+rw-tools, and hal. cdrecord works after that (tried to blank some CDs and burn some ISOs). But xfburn crashes: (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 ** Message: Using Thunar-VFS 1.2.0 ** Message: Using HAL xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device ** ERROR **: Device address does not lead to a burner '/dev/cd0' (ret=0). aborting... [1]Abort xfburn (core dumped) Exactly the same result when run as root. k3b starts but shows a warning message in a popup window: No optical drive found. K3b did not find any optical device in your system. Solution: Make sure HAL daemon is running, it is used by K3b for finding devices. Of course, HAL is running. brasero starts ok and doesn't complain at all; it just doesn't show any devices. camcontrol devlist output: SAMSUNG SP80A4H RT100-07 at scbus0 target 0 lun 0 (pass0,ada0) SAMSUNG HD400LD WQ100-15 at scbus0 target 1 lun 0 (pass1,ada1) LITE-ON DVDRW SHW-160P6S PS08at scbus1 target 0 lun 0 (cd0,pass2) This is what I tried to set to make it work: /etc/devfs.conf: # CDROM own cd0 root:operator perm cd0 0660 own pass2 root:operator permpass2 0666 own xpt0 root:operator permxpt0 0666 /etc/devfs.rules: [system=5] #CD/DVD add path 'cd*' mode 0666 group operator add path 'pass*' mode 0666 group operator add path 'xpt*' mode 0666 group operator /etc/rc.conf: devfs_system_ruleset=system No CD-related entries in /etc/fstab. Added myself to the operator group. SUID flags: ll /usr/local/bin | grep cdr -rws--x--- 1 root operator578088 Dec 3 02:30 cdrdao -rws--x--- 1 root operator402768 Feb 22 15:33 cdrecord -rws--x--- 1 root operator136428 Dec 3 10:08 cdrskin Permissions on /dev files: #ll /dev |grep cd crw-rw 1 rootoperator 0, 91 Apr 6 15:18 cd0 # ll /dev | grep pass crw-rw 1 rootoperator 0, 83 Apr 6 15:18 pass0 crw-rw 1 rootoperator 0, 84 Apr 6 15:18 pass1 crw-rw 1 rootoperator 0, 85 Apr 6 15:18 pass2 # ll /dev | grep xpt crw-rw 1 rootoperator 0, 68 Apr 6 15:18 xpt0 # sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 1 What could be wrong? ___ 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
define a default username for logging in
Hi All :) i'm trying to find a way to enable a required feature : to set *default username *in my Freebsd 8.2 server.. i mean, i wanna be able to login with just entering My Master Password(no usernames needed.. also prefer it to be per tty), which is *not related to my root account, *but is the password of a user which i have defined as my default user.. is it possible for, e.g. pam_login module (i couldn't find any manuals on such feature yet..), to have such a config or is there any other ways to set such default username for login? i've googled most of the keywords i thought might be related, but haven't find any related answers except for maybe working on nsswitch.conf or master.passwd or login.conf options (which are, as you see, really *different ways, *and also none seems to be behaved per tty..) and now, i'm not quite sure whether i'm taking the correct steps or not.. and i've got a bit confused.. would anyone please helps me find the way? thanks a lot for your helps :) Best Regards, takCoder ___ 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: define a default username for logging in
On Sat, 7 Apr 2012 12:21:57 +0430, takCoder wrote: Hi All :) i'm trying to find a way to enable a required feature : to set *default username *in my Freebsd 8.2 server.. i mean, i wanna be able to login with just entering My Master Password(no usernames needed.. also prefer it to be per tty), which is *not related to my root account, *but is the password of a user which i have defined as my default user.. is it possible for, e.g. pam_login module (i couldn't find any manuals on such feature yet..), to have such a config or is there any other ways to set such default username for login? It is, but I assume my answer will just be a half of the whole story. The problem will be: no password. But maybe you can find some inspiration and then extend the procedure to fit your needs. 1. Modify /etc/gettytab as follows: default:\ ... localautologin:\ :al=USERNAME:tc=Pc: a|std.110|110-baud:\ ... where USERNAME is the name of the user you want to login as (given by the al= parameter, and inheriting the tc= settings). Make sure the user does exist in the system. 2. Modify /etc/ttys as follows: ttyv0 /usr/libexec/getty localautologin cons25 on secure and maybe change cons25 to cons25l1 (or any other value that might be required). As I said initially, this does _not_ prompt for a password! Maybe /etc/passwd's shell field allows you to add the password protection. If you're logging in remotely, ssh USERNAME@yourserver.qw.er.tzu will only prompt for a password. This idea offers an opportunity to something overcomplicated: Create a user for localautologin that is _not_ your default user name. Make this user login automatically, and into his ~/.login, place the command ssh USERNAME@localhost so right after performing the localautologin, ssh will attempt to connect to localhost _as USERNAME_ and _prompt for_ the password. Terrible, I know. :-) To milden the pain of this approach, you could allow telnet for localhost, i. e. from 127.0.0.1 to 127.0.0.1 _ONLY_ and nothing more, and use telnet instead of ssh in the ~/.login command. -- 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
Wine-fbsd64 updated to 1.5.1 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.1 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.1,1.tbz) = f8e1c24fc18dea444aed84b4bde8db25 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.1,1.txz) = 05a2c1baed81108041fa650a6ee0d78a [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Re: xfburn and k3b on FreeBSD9.0-RELEASE can't find LITE-ON DVDRW
On 04/07/2012 09:13, Jeff Tipton wrote: Hi, I can't get any GUI tool working with my LITE-ON DVDRW SHW-160P6S (IDE) on 9.0-RELEASE (packages and ports tree are in sync from the release date). atapicam is compiled in GENERIC kernel now, so no need for this module. I recompiled cdrtools, dvd+rw-tools, and hal. cdrecord works after that (tried to blank some CDs and burn some ISOs). But xfburn crashes: (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 ** Message: Using Thunar-VFS 1.2.0 ** Message: Using HAL xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device ** ERROR **: Device address does not lead to a burner '/dev/cd0' (ret=0). aborting... [1]Abort xfburn (core dumped) Exactly the same result when run as root. k3b starts but shows a warning message in a popup window: No optical drive found. K3b did not find any optical device in your system. Solution: Make sure HAL daemon is running, it is used by K3b for finding devices. Of course, HAL is running. brasero starts ok and doesn't complain at all; it just doesn't show any devices. camcontrol devlist output: SAMSUNG SP80A4H RT100-07 at scbus0 target 0 lun 0 (pass0,ada0) SAMSUNG HD400LD WQ100-15 at scbus0 target 1 lun 0 (pass1,ada1) LITE-ON DVDRW SHW-160P6S PS08at scbus1 target 0 lun 0 (cd0,pass2) This is what I tried to set to make it work: /etc/devfs.conf: # CDROM own cd0 root:operator perm cd0 0660 own pass2 root:operator permpass2 0666 own xpt0 root:operator permxpt0 0666 /etc/devfs.rules: [system=5] #CD/DVD add path 'cd*' mode 0666 group operator add path 'pass*' mode 0666 group operator add path 'xpt*' mode 0666 group operator /etc/rc.conf: devfs_system_ruleset=system No CD-related entries in /etc/fstab. Added myself to the operator group. SUID flags: ll /usr/local/bin | grep cdr -rws--x--- 1 root operator578088 Dec 3 02:30 cdrdao -rws--x--- 1 root operator402768 Feb 22 15:33 cdrecord -rws--x--- 1 root operator136428 Dec 3 10:08 cdrskin Permissions on /dev files: #ll /dev |grep cd crw-rw 1 rootoperator 0, 91 Apr 6 15:18 cd0 # ll /dev | grep pass crw-rw 1 rootoperator 0, 83 Apr 6 15:18 pass0 crw-rw 1 rootoperator 0, 84 Apr 6 15:18 pass1 crw-rw 1 rootoperator 0, 85 Apr 6 15:18 pass2 # ll /dev | grep xpt crw-rw 1 rootoperator 0, 68 Apr 6 15:18 xpt0 # sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 1 What could be wrong? ___ 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 Some news. I found out that xfburn depends on libburn, so I recompiled libburn, too. Now xfburn seems to work (could blank a disk, write an ISO image, write files to a disk). As for k3b (which I would prefer), nothing changed. Only I found that when I insert a disk before launching k3b, it finds the drive as read-only. Now the popup window says: No CD/DVD/BD writer found. K3b did not find an optical writing device in your system. Thus, you will not be able to burn CDs or DVDs. However, you can still use other K3b features such as audio track extraction, audio transcoding or ISO9660 image creation. In Settings Devices dialog, Writers are shown as none, and /dev/cd0 is under Read-only Drives. There are blank squares against Vendor and Firmware, and Error against Write Capabilities:. ___ 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
Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
Hi to all, I have: casa# disktype /dev/da1 --- /dev/da1 Character device, size 3.771 GiB (4048551936 bytes) FreeBSD boot loader (i386 boot2/BTX 1.02 at sector 2) BSD disklabel (at sector 1), 8 partitions Partition c: 2.145 GiB (2302711808 bytes, 4497484 sectors from 0) Type 0 (Unused) DOS/MBR partition map Partition 1: 3.547 GiB (3808272384 bytes, 7438032 sectors from 63) Type 0x83 (Linux) Ext3 file system UUID D1A7E6D6-3A34-4864-B6E8-C4DAA34AD776 (DCE, v4) Last mounted at / Volume size 3.547 GiB (3808272384 bytes, 929754 blocks of 4 KiB) Partition 2: 227.5 MiB (238533120 bytes, 465885 sectors from 7438095) Type 0x05 (Extended) Partition 5: 227.5 MiB (238500864 bytes, 465822 sectors from 7438095+63) Type 0x82 (Linux swap / Solaris) Linux swap, version 2, subversion 1, 4 KiB pages, little-endian Swap size 227.4 MiB (238489600 bytes, 58225 pages of 4 KiB) I'm running from FreeBSD 9.0-RELEASE I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument How can I mount it ? 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: Xorg bug or better Xorg file problems
Hello first of all. This is my first post here.. a test.. i stream on line as i read todays post. So about xorg file cause i make 6 months with nvidia 9200fx let talk first for the card. second there is no xorg need it so u can back up and delete it, and test you X with xrandr -q man xrandr and more. The last think that comes in my mind cause doug speaks for flashing is the DFP screen maybe need and edid.bin file into you etx/X11 ofcaurce search forums data for xorg confg option. Thank you. and Hello there -- My webpages egelor http://egelor.tumblr.com : egepresshttp://egepress.wordpress.com : My Server Actapus http://egelor.dyndns.org Piece Love Unity_ ___ 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: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On Sat, Apr 07, 2012 at 10:06:44PM +0300, Odhiambo Washington wrote: Hi Odhiambo, man mount mount fstype device mount-point Yes, but look: I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument I don't know why !? Thanks, see you. ___ 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: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On 7 April 2012 13:53, Xavier xavierfreebsdquesti...@gmail.com wrote: Hi to all, I have: casa# disktype /dev/da1 --- /dev/da1 Character device, size 3.771 GiB (4048551936 bytes) FreeBSD boot loader (i386 boot2/BTX 1.02 at sector 2) BSD disklabel (at sector 1), 8 partitions Partition c: 2.145 GiB (2302711808 bytes, 4497484 sectors from 0) Type 0 (Unused) DOS/MBR partition map Partition 1: 3.547 GiB (3808272384 bytes, 7438032 sectors from 63) Type 0x83 (Linux) Ext3 file system UUID D1A7E6D6-3A34-4864-B6E8-C4DAA34AD776 (DCE, v4) Last mounted at / Volume size 3.547 GiB (3808272384 bytes, 929754 blocks of 4 KiB) Partition 2: 227.5 MiB (238533120 bytes, 465885 sectors from 7438095) Type 0x05 (Extended) Partition 5: 227.5 MiB (238500864 bytes, 465822 sectors from 7438095+63) Type 0x82 (Linux swap / Solaris) Linux swap, version 2, subversion 1, 4 KiB pages, little-endian Swap size 227.4 MiB (238489600 bytes, 58225 pages of 4 KiB) I'm running from FreeBSD 9.0-RELEASE I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument How can I mount it ? mount -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ perhaps? Note---^^ If that still doesn't work, try adding -r in there (as ext2fs might not support r/w in your configuration). -- -- ___ 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: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On Sat, Apr 07, 2012 at 04:15:41PM -0400, ill...@gmail.com wrote: Hi, On 7 April 2012 13:53, Xavier xavierfreebsdquesti...@gmail.com wrote: Hi to all, I have: casa# disktype /dev/da1 --- /dev/da1 Character device, size 3.771 GiB (4048551936 bytes) FreeBSD boot loader (i386 boot2/BTX 1.02 at sector 2) BSD disklabel (at sector 1), 8 partitions Partition c: 2.145 GiB (2302711808 bytes, 4497484 sectors from 0) Type 0 (Unused) DOS/MBR partition map Partition 1: 3.547 GiB (3808272384 bytes, 7438032 sectors from 63) Type 0x83 (Linux) Ext3 file system UUID D1A7E6D6-3A34-4864-B6E8-C4DAA34AD776 (DCE, v4) Last mounted at / Volume size 3.547 GiB (3808272384 bytes, 929754 blocks of 4 KiB) Partition 2: 227.5 MiB (238533120 bytes, 465885 sectors from 7438095) Type 0x05 (Extended) Partition 5: 227.5 MiB (238500864 bytes, 465822 sectors from 7438095+63) Type 0x82 (Linux swap / Solaris) Linux swap, version 2, subversion 1, 4 KiB pages, little-endian Swap size 227.4 MiB (238489600 bytes, 58225 pages of 4 KiB) I'm running from FreeBSD 9.0-RELEASE I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument How can I mount it ? mount -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ perhaps? Note---^^ If that still doesn't work, try adding -r in there (as ext2fs might not support r/w in your configuration). casa# mount -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1s1 : No such file or directory casa# casa# mount -r -t ext2fs /dev/da1s1 /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1s1 : No such file or directory casa# You have more ideas ? Thanks, see you. ___ 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: order of source_dirs in cp(1)
On Thu Apr 5 12, Matthias Apitz wrote: Hello, I was doing $ cp -Rv 10 11 12 13 14 15 16 17 2 /mnt/osm and was surprised seeing that source_dir 17 was done before 16; the man page does not specify the order, but I was thinking it just goes through the list in the given order... Why this is done this way? i can't remember the reason, but the question has been raised quite often. try searching the archives. i think it had something to do with performance or getting better disk locality, but i'm not sure. however people were argueing whether copying the files in reverse order is really a benefit or not. cheers. alex Thanks matthias -- Matthias Apitz e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
I don't know why !? Is ext2fs.ko loaded? Does /var/log/messages reveal anything? Yes : casa# kldstat | grep ext 91 0xc8806000 1ext2fs.ko casa# I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument /var/log/messages : Apr 7 22:16:35 casa kernel: ext2fs: da1a: wrong magic number 0 (expected 0xef53 What is the output from gpart list? -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can FreeBSD 9.0-RELEASE mount Ext3 file system ?
On Sat, Apr 07, 2012 at 06:25:29PM -0500, Adam Vande More wrote: Hi Adam, I don't know why !? Is ext2fs.ko loaded? Does /var/log/messages reveal anything? Yes : casa# kldstat | grep ext 91 0xc8806000 1ext2fs.ko casa# I try: casa# mount -t ext2fs /dev/da1a /mnt/JetFlash\ Transcend\ 4GB\ 1100/ mount: /dev/da1a : Invalid argument /var/log/messages : Apr 7 22:16:35 casa kernel: ext2fs: da1a: wrong magic number 0 (expected 0xef53 What is the output from gpart list? ###cut here### Geom name: da1 modified: false state: OK fwheads: 255 fwsectors: 63 last: 7907327 first: 0 entries: 8 scheme: BSD Providers: 1. Name: da1a Mediasize: 2302703616 (2.1G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 8192 Mode: r0w0e0 rawtype: 0 length: 2302703616 offset: 8192 type: !0 index: 1 end: 4497483 start: 16 Consumers: 1. Name: da1 Mediasize: 4048551936 (3.8G) Sectorsize: 512 Mode: r0w0e0 ###cut here### Have ideas ? Thanks, see you. ___ 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
Music production on FreeBSD
Hello! Is anybody aware of any talented producers who produce their music primarily on FreeBSD? Thanks! Tony ___ 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: xfburn and k3b on FreeBSD9.0-RELEASE can't find LITE-ON DVDRW
On Sat, 07 Apr 2012 18:57:09 +0300 Jeff Tipton jef...@mail.com wrote: On 04/07/2012 09:13, Jeff Tipton wrote: Hi, I can't get any GUI tool working with my LITE-ON DVDRW SHW-160P6S (IDE) on 9.0-RELEASE (packages and ports tree are in sync from the release date). atapicam is compiled in GENERIC kernel now, so no need for this module. I recompiled cdrtools, dvd+rw-tools, and hal. cdrecord works after that (tried to blank some CDs and burn some ISOs). But xfburn crashes: (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 ** Message: Using Thunar-VFS 1.2.0 ** Message: Using HAL xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device ** ERROR **: Device address does not lead to a burner '/dev/cd0' (ret=0). aborting... [1]Abort xfburn (core dumped) Exactly the same result when run as root. k3b starts but shows a warning message in a popup window: No optical drive found. K3b did not find any optical device in your system. Solution: Make sure HAL daemon is running, it is used by K3b for finding devices. Of course, HAL is running. brasero starts ok and doesn't complain at all; it just doesn't show any devices. camcontrol devlist output: SAMSUNG SP80A4H RT100-07 at scbus0 target 0 lun 0 (pass0,ada0) SAMSUNG HD400LD WQ100-15 at scbus0 target 1 lun 0 (pass1,ada1) LITE-ON DVDRW SHW-160P6S PS08at scbus1 target 0 lun 0 (cd0,pass2) This is what I tried to set to make it work: /etc/devfs.conf: # CDROM own cd0 root:operator perm cd0 0660 own pass2 root:operator permpass2 0666 own xpt0 root:operator permxpt0 0666 /etc/devfs.rules: [system=5] #CD/DVD add path 'cd*' mode 0666 group operator add path 'pass*' mode 0666 group operator add path 'xpt*' mode 0666 group operator /etc/rc.conf: devfs_system_ruleset=system No CD-related entries in /etc/fstab. Added myself to the operator group. SUID flags: ll /usr/local/bin | grep cdr -rws--x--- 1 root operator578088 Dec 3 02:30 cdrdao -rws--x--- 1 root operator402768 Feb 22 15:33 cdrecord -rws--x--- 1 root operator136428 Dec 3 10:08 cdrskin Permissions on /dev files: #ll /dev |grep cd crw-rw 1 rootoperator 0, 91 Apr 6 15:18 cd0 # ll /dev | grep pass crw-rw 1 rootoperator 0, 83 Apr 6 15:18 pass0 crw-rw 1 rootoperator 0, 84 Apr 6 15:18 pass1 crw-rw 1 rootoperator 0, 85 Apr 6 15:18 pass2 # ll /dev | grep xpt crw-rw 1 rootoperator 0, 68 Apr 6 15:18 xpt0 # sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 1 What could be wrong? ___ 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 Some news. I found out that xfburn depends on libburn, so I recompiled libburn, too. Now xfburn seems to work (could blank a disk, write an ISO image, write files to a disk). As for k3b (which I would prefer), nothing changed. Only I found that when I insert a disk before launching k3b, it finds the drive as read-only. Now the popup window says: No CD/DVD/BD writer found. K3b did not find an optical writing device in your system. Thus, you will not be able to burn CDs or DVDs. However, you can still use other K3b features such as audio track extraction, audio transcoding or ISO9660 image creation. In Settings Devices dialog, Writers are shown as none, and /dev/cd0 is under Read-only Drives. There are blank squares against Vendor and Firmware, and Error against Write Capabilities:. For what it is worth, I had a similar problem with FreeBSD 9 back in the Beta days. IIRC I had to rebuild cdparanoia and then K3B and all was working again. YMMV Good Luck Robert ___ 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: Music production on FreeBSD
On Saturday 07 April 2012 21:04:41 Tony wrote: Hello! Is anybody aware of any talented producers who produce their music primarily on FreeBSD? Thanks! Tony Man, that has been my dream for a good while! Ardour is a fine multitrack but no MIDI, at least on FreeBSD. And FBSD itself has lots of issues with MIDI. Besides that, there is the driver problem with most professional sound boards. I am going to attempt something a quite bit out of my league which is try to port the alsa drivers for my echo Gina3G board to FBSD. If I can manage to do that, then I believe the rest will fall on my lap by gravity. I hope I don't blow up my desktop. I'm eager to read the replies to the OP. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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: Music production on FreeBSD
On 04/08/12 11:39, Mario Lobo wrote: On Saturday 07 April 2012 21:04:41 Tony wrote: Hello! Is anybody aware of any talented producers who produce their music primarily on FreeBSD? Thanks! Tony Man, that has been my dream for a good while! Ardour is a fine multitrack but no MIDI, at least on FreeBSD. And FBSD itself has lots of issues with MIDI. Besides that, there is the driver problem with most professional sound boards. I am going to attempt something a quite bit out of my league which is try to port the alsa drivers for my echo Gina3G board to FBSD. If I can manage to do that, then I believe the rest will fall on my lap by gravity. I hope I don't blow up my desktop. I'm eager to read the replies to the OP. I have. Or more accurately my wife and co have, with me behind the wheel. My wife is a musician and music teacher, and we only use FreeBSD, so its a given here (and a massive drive for me to find a way to support it). We used simple tools: audacity, rosegarden, and hydrogen. We used a usb yamaha sound board, and a ribbon mic for the vocals. The biggest problem here is that rosegarden refuses to use jack for midi transport now, so even though there is a jack_umidi daemon in the ports it still wont pick it up. I'll have to look at another app like ardour and see if it is better there. Other than that, all good. Incidentally, the reason for the emphasis on rosegarden is that it does midi and audio multitrack; as well as notation editing. Apparently they're hell bent on only using alsa (God only knows why - must have a death wish or something...), with marginal support for jack. Hence they only support midi through alsa, not jack. Madness... The usb audio was a good call; the uaudio driver worked well in our case with jack, and given all work was done on a laptop it made sense. These days I think it makes more sense because of the portability, not to mention if the power happens to go off in the midst of a take you can keep going and finish the track ;) The only other option that would be ideal would be firewire audio - if that ever comes to FBSD. I think there may be some support through jack, but I haven't investigated that fully yet. And dont forget lilypond for notation... :) ___ 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: Music production on FreeBSD
On Sat, 7 Apr 2012 22:39:02 -0300 Mario Lobo l...@bsd.com.br wrote: On Saturday 07 April 2012 21:04:41 Tony wrote: Hello! Is anybody aware of any talented producers who produce their music primarily on FreeBSD? Thanks! Tony Man, that has been my dream for a good while! Ardour is a fine multitrack but no MIDI, at least on FreeBSD. And FBSD itself has lots of issues with MIDI. Besides that, there is the driver problem with most professional sound boards. I am going to attempt something a quite bit out of my league which is try to port the alsa drivers for my echo Gina3G board to FBSD. If I can manage to do that, then I believe the rest will fall on my lap by gravity. I hope I don't blow up my desktop. I'm eager to read the replies to the OP. And I'm sure I'm not the only one here who's eager to hear of any progress you may make with this most ambitious undertaking of yours. :-) Keep us posted, please? Conrad (who can't even get Rosegarden to run at all lately) :-( -- Conrad J. Sabatier conr...@cox.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: Music production on FreeBSD
On Sun, 08 Apr 2012 13:28:51 +1000 Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: On 04/08/12 11:39, Mario Lobo wrote: On Saturday 07 April 2012 21:04:41 Tony wrote: Hello! Is anybody aware of any talented producers who produce their music primarily on FreeBSD? Thanks! Tony Man, that has been my dream for a good while! Ardour is a fine multitrack but no MIDI, at least on FreeBSD. And FBSD itself has lots of issues with MIDI. Besides that, there is the driver problem with most professional sound boards. I am going to attempt something a quite bit out of my league which is try to port the alsa drivers for my echo Gina3G board to FBSD. If I can manage to do that, then I believe the rest will fall on my lap by gravity. I hope I don't blow up my desktop. I'm eager to read the replies to the OP. I have. Or more accurately my wife and co have, with me behind the wheel. My wife is a musician and music teacher, and we only use FreeBSD, so its a given here (and a massive drive for me to find a way to support it). We used simple tools: audacity, rosegarden, and hydrogen. We used a usb yamaha sound board, and a ribbon mic for the vocals. The biggest problem here is that rosegarden refuses to use jack for midi transport now, so even though there is a jack_umidi daemon in the ports it still wont pick it up. I'll have to look at another app like ardour and see if it is better there. Other than that, all good. Incidentally, the reason for the emphasis on rosegarden is that it does midi and audio multitrack; as well as notation editing. Apparently they're hell bent on only using alsa (God only knows why - must have a death wish or something...), with marginal support for jack. Hence they only support midi through alsa, not jack. Madness... Yes, Rosegarden is a very nice app; it's just too bad we can't get true MIDI working with it under FreeBSD. As an amateur (frustrated?) composer, I *really* like the notation editing. For several months now, I've been unable to use Rosegarden at all (under 10-CURRENT). It crashes very early on startup. Haven't been able to track this one down yet. Gosh, how I miss my early days with FreeBSD and my Soundblaster AWE64 with the special MIDI apps for it in the ports collection (back in the good ol' days when OSS was our soundsystem). The usb audio was a good call; the uaudio driver worked well in our case with jack, and given all work was done on a laptop it made sense. These days I think it makes more sense because of the portability, not to mention if the power happens to go off in the midst of a take you can keep going and finish the track ;) The only other option that would be ideal would be firewire audio - if that ever comes to FBSD. I think there may be some support through jack, but I haven't investigated that fully yet. And dont forget lilypond for notation... :) I wish driver coding and such were more my area of expertise; I'd gladly lend a hand to any efforts to improve our MIDI support. Unfortunately, every time I've tried looking at any of the actual code for the sound subsystem, it's left me in a veritable mystified stupor. :-) And lately, even some of the timidity++ stuff isn't working right. The Xaw interface refuses to build/install properly, ever since the removal of X11BASE from the ports infrastructure. This is really my single, my one-and-only gripe with FreeBSD: MIDI! Used to have a nice setup that was working beautifully, pretty much comparable to what you might find under Windows or Mac. But the whole thing got yanked out and replaced with the newpcm stuff back in -- what year was it? -- sometime in the late 90s. Most unfortunate. I and a number of others protested at the time, that we were having functionality ripped out with no viable replacement in sight, and sadly, that's still pretty much the case. MIDI support in FreeBSD has never been the same since. :-( Oh well, I'll shut up now. Hate to come off as a whiner or something. :-) -- Conrad J. Sabatier conr...@cox.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: xfburn and k3b on FreeBSD9.0-RELEASE can't find LITE-ON DVDRW
On 04/08/2012 03:33, Robert wrote: On Sat, 07 Apr 2012 18:57:09 +0300 Jeff Tiptonjef...@mail.com wrote: On 04/07/2012 09:13, Jeff Tipton wrote: Hi, I can't get any GUI tool working with my LITE-ON DVDRW SHW-160P6S (IDE) on 9.0-RELEASE (packages and ports tree are in sync from the release date). atapicam is compiled in GENERIC kernel now, so no need for this module. I recompiled cdrtools, dvd+rw-tools, and hal. cdrecord works after that (tried to blank some CDs and burn some ISOs). But xfburn crashes: (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 (process:6957): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 ** Message: Using Thunar-VFS 1.2.0 ** Message: Using HAL xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device xfburn: error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device ** ERROR **: Device address does not lead to a burner '/dev/cd0' (ret=0). aborting... [1]Abort xfburn (core dumped) Exactly the same result when run as root. k3b starts but shows a warning message in a popup window: No optical drive found. K3b did not find any optical device in your system. Solution: Make sure HAL daemon is running, it is used by K3b for finding devices. Of course, HAL is running. brasero starts ok and doesn't complain at all; it just doesn't show any devices. camcontrol devlist output: SAMSUNG SP80A4H RT100-07 at scbus0 target 0 lun 0 (pass0,ada0)SAMSUNG HD400LD WQ100-15 at scbus0 target 1 lun 0 (pass1,ada1)LITE-ON DVDRW SHW-160P6S PS08 at scbus1 target 0 lun 0 (cd0,pass2) This is what I tried to set to make it work: /etc/devfs.conf: # CDROM own cd0 root:operator perm cd0 0660 own pass2 root:operator permpass2 0666 own xpt0 root:operator permxpt0 0666 /etc/devfs.rules: [system=5] #CD/DVD add path 'cd*' mode 0666 group operator add path 'pass*' mode 0666 group operator add path 'xpt*' mode 0666 group operator /etc/rc.conf: devfs_system_ruleset=system No CD-related entries in /etc/fstab. Added myself to the operator group. SUID flags: ll /usr/local/bin | grep cdr -rws--x--- 1 root operator578088 Dec 3 02:30 cdrdao -rws--x--- 1 root operator402768 Feb 22 15:33 cdrecord -rws--x--- 1 root operator136428 Dec 3 10:08 cdrskin Permissions on /dev files: #ll /dev |grep cd crw-rw 1 rootoperator 0, 91 Apr 6 15:18 cd0 # ll /dev | grep pass crw-rw 1 rootoperator 0, 83 Apr 6 15:18 pass0 crw-rw 1 rootoperator 0, 84 Apr 6 15:18 pass1 crw-rw 1 rootoperator 0, 85 Apr 6 15:18 pass2 # ll /dev | grep xpt crw-rw 1 rootoperator 0, 68 Apr 6 15:18 xpt0 # sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 1 What could be wrong? ___ 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 Some news. I found out that xfburn depends on libburn, so I recompiled libburn, too. Now xfburn seems to work (could blank a disk, write an ISO image, write files to a disk). As for k3b (which I would prefer), nothing changed. Only I found that when I insert a disk before launching k3b, it finds the drive as read-only. Now the popup window says: No CD/DVD/BD writer found. K3b did not find an optical writing device in your system. Thus, you will not be able to burn CDs or DVDs. However, you can still use other K3b features such as audio track extraction, audio transcoding or ISO9660 image creation. In Settings Devices dialog, Writers are shown as none, and /dev/cd0 is under Read-only Drives. There are blank squares against Vendor and Firmware, and Error against Write Capabilities:. For what it is worth, I had a similar problem with FreeBSD 9 back in the Beta days. IIRC I had to rebuild cdparanoia and then K3B and all was working again. YMMV Good Luck Robert Thank you, it works now! ___ 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
