Re: mount: /dev/ada0p1: Device busy Busy with what?
On 2013-09-13 01:30, Polytropon wrote: > On Fri, 13 Sep 2013 00:54:01 +0200, Per olof Ljungmark wrote: >> I have apart from the boot drives a SATA disk for storage. Usually I >> would mount it with >> mount /dev/ada0p1 /archive >> but as my last reboot into >> FreeBSD 9.1-STABLE #0 r252369 >> I cannot mount the disk, I get >> mount: /dev/ada0p1: Device busy >> >> Well, busy with what? >> >> fuser -m /dev/ada0p1 >> /dev/ada0p1: >> >> I REALLY need to acces trhis UFS formatted drive, how can I convice it >> that everything is ok and it's not really busy with anything? >> >> Could anyone please help to sort this please? > > Maybe a fsck is running on the disk device? Also check "mount -v" > if the disk is really unmounted. Make sure any running fsck has > been finished and try again. In worst case, manually initiate a > file system check. Then try mounting the disk again. Yes, I've done at least five fsck's with different options and there has not been any complaints. The drive is not mounted at boot time. Anyway, mount -v seems to have sorted it. It was already mounted to a different mountpoint due to my own brain damage apparently although I cannot recall ever doing it. Problem solved. Thank you! //per ___ 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"
mount: /dev/ada0p1: Device busy Busy with what?
I have apart from the boot drives a SATA disk for storage. Usually I would mount it with mount /dev/ada0p1 /archive but as my last reboot into FreeBSD 9.1-STABLE #0 r252369 I cannot mount the disk, I get mount: /dev/ada0p1: Device busy Well, busy with what? fuser -m /dev/ada0p1 /dev/ada0p1: I REALLY need to acces trhis UFS formatted drive, how can I convice it that everything is ok and it's not really busy with anything? Could anyone please help to sort this please? TIA //per ___ 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: mount: /dev/ada0p1: Device busy Busy with what?
On Fri, 13 Sep 2013 00:54:01 +0200, Per olof Ljungmark wrote: > I have apart from the boot drives a SATA disk for storage. Usually I > would mount it with > mount /dev/ada0p1 /archive > but as my last reboot into > FreeBSD 9.1-STABLE #0 r252369 > I cannot mount the disk, I get > mount: /dev/ada0p1: Device busy > > Well, busy with what? > > fuser -m /dev/ada0p1 > /dev/ada0p1: > > I REALLY need to acces trhis UFS formatted drive, how can I convice it > that everything is ok and it's not really busy with anything? > > Could anyone please help to sort this please? Maybe a fsck is running on the disk device? Also check "mount -v" if the disk is really unmounted. Make sure any running fsck has been finished and try again. In worst case, manually initiate a file system check. Then try mounting the disk again. -- 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: umount device busy
On 06/04/12 13:40, Polytropon wrote: > On Mon, 04 Jun 2012 13:15:33 -0600, Gary Aitken wrote: >> Can you tell me where any of this is documented? >> I can't find squat about gamin. >> no man page and no docs in the /usr/local tree > > Welcome to the realm of modern software and its aversion > against documentation. :-) > > In such cases, you often need to use a web browser, google, > and search for keywords related to your problem. Actually, did, but missed it. I know I had the spelling right because I was flooded with "gaRmin" results and had to check. I'll go hide in the corner now... >> Checked the port options for gamin itself and see there's >> a place to turn on the poller, to that should solve that problem. > > No, this setting is done in a configuration file (installed > version of course). The setting is > > poll /mnt/* > poll /media/* > > or > > poll /dev/* > > or the like - not sure, I'm not using it. It's also an option at build time. Or at least it shows up there: [*] GAM_POLLER Use gamin's poller instead of kqueue's >> But where does one learn about disabling specific directories >> or other info? > > In arbitrary web forums, wikis and user pages. :-) > > Here's an example: > > http://people.gnome.org/~veillard/gamin/config.html Found that easily now, 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: umount device busy
On Mon, 4 Jun 2012, Gary Aitken wrote: On 06/04/12 08:15, Warren Block wrote: gamin opens the directory (of the newly-mounted device) so it can check for new files being created or files being renamed, and then notify the window manager, which updates the user's desktop. The open makes the device in-use, preventing an unmount. Setting gamin to "poll" helps. (I assume it opens the directory, scans, then closes it again, so there's a race condition there, but I haven't encountered it.) gamin can also be disabled for certain directories. That works (AFAIR, it's been a while), but then you lose instant icon updates on the very directories where it is the most useful. Can you tell me where any of this is documented? I can't find squat about gamin. Found on a google-quest after lsof or stat showed gamin locking the directory where I was mounting stuff: http://people.gnome.org/~veillard/gamin/config.html ___ 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: umount device busy
On 06/04/12 02:28, Lars Eighner wrote: >>> This almost always means someone (i.e. you) is sitting in the directory. >>> If you tried this while su'ed and the un-su'ed you were still in the >>> directory /mnt/goflex, you'd get this message. This may also happen if >>> someone (i.e. you) is in the directory on another vtty. Naturally it can >>> also mean some operation is in progress, but generally you would have >>> recognized and avoided that. >> >> That's what I kept thinking. Backed out of all su ops, checked all >> xterms; nada. no other vtys opened. In any case, the mount was done >> after X was started, and switching vtys crashes X so I don't do that. > > This needs fixing. no kidding. at the moment, other stuff has priority... 3. I tried lsof but I don't get any output from it: lsof +d /mnt/goflex -x -- /mnt/goflex Where does it go if not to stdout? > >>> You've got me! But why is there anything after -x? I don't quite >>> understand. >> >> Otherwise -x thinks the /mnt/goflex belongs to it. > > But what if you leave out ALL the stuff after -x. Isn't it redundant with > the +d switch? (That's not a Socratic question: I don't know.) That's what you get when you build a command line while reading the man page :-) At least in this instance, you get the same result. > Anyway, I found the lsof FAQ by make extract in the port. I quess I am not > too good at reading Makefiles because I don't see why it isn't copied to > /usr/local/share/lsof with the README and whatnot. Thanks, got it. Gary ___ 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: umount device busy
On Mon, 04 Jun 2012 13:15:33 -0600, Gary Aitken wrote: > Can you tell me where any of this is documented? > I can't find squat about gamin. > no man page and no docs in the /usr/local tree Welcome to the realm of modern software and its aversion against documentation. :-) In such cases, you often need to use a web browser, google, and search for keywords related to your problem. > Checked the port options for gamin itself and see there's > a place to turn on the poller, to that should solve that problem. No, this setting is done in a configuration file (installed version of course). The setting is poll /mnt/* poll /media/* or poll /dev/* or the like - not sure, I'm not using it. > But where does one learn about disabling specific directories > or other info? In arbitrary web forums, wikis and user pages. :-) Here's an example: http://people.gnome.org/~veillard/gamin/config.html Of course you need to conclude to use either ~/.gaminrc for your user, or something different than /etc/gamin/mandatory_gaminrc for system-wide use. -- 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: umount device busy
On 06/04/12 08:15, Warren Block wrote: > gamin opens the directory (of the newly-mounted device) so it can check for > new files being created or files being renamed, and then notify the window > manager, which updates the user's desktop. The open makes the device in-use, > preventing an unmount. > > Setting gamin to "poll" helps. (I assume it opens the directory, scans, then > closes it again, so there's a race condition there, but I haven't encountered > it.) > > gamin can also be disabled for certain directories. That works (AFAIR, it's > been a while), but then you lose instant icon updates on the very directories > where it is the most useful. Can you tell me where any of this is documented? I can't find squat about gamin. no man page and no docs in the /usr/local tree Checked the port options for gamin itself and see there's a place to turn on the poller, to that should solve that problem. But where does one learn about disabling specific directories or other info? Thanks, Gary ___ 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: umount device busy
As nearly as I can tell, I don't have anything pointing at that drive. Questions: 1. What does the "No such file or directory" mean from mkdir? It's a relative dir name, and I'm sitting at a valid dir. no NTFS driver for FreeBSD is really well done. fusefs based ntfs driver in my opinion is more usable (but not really good) try umount -f ___ 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: umount device busy
On Mon, 4 Jun 2012, Gary Aitken wrote: On 06/03/12 21:05, Polytropon wrote: Maybe the ganim "lock" is regarding a device file? Not sure about that, I'm not using it here. I'm not sure what the deal is here, but exiting X does solve the problem. I didn't try just killing the environment by shutting down the wm and leaving X up, but if I forget and do something like that again I'll try to remember to try it. gamin opens the directory (of the newly-mounted device) so it can check for new files being created or files being renamed, and then notify the window manager, which updates the user's desktop. The open makes the device in-use, preventing an unmount. Setting gamin to "poll" helps. (I assume it opens the directory, scans, then closes it again, so there's a race condition there, but I haven't encountered it.) gamin can also be disabled for certain directories. That works (AFAIR, it's been a while), but then you lose instant icon updates on the very directories where it is the most useful. ___ 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: umount device busy
On Mon, 04 Jun 2012 01:56:49 -0600, Gary Aitken wrote: > On 06/03/12 21:05, Polytropon wrote: > > Maybe the ganim "lock" is regarding a device file? Not sure > > about that, I'm not using it here. > > I'm not sure what the deal is here, but exiting X does solve > the problem. I didn't try just killing the environment by > shutting down the wm and leaving X up, but if I forget and > do something like that again I'll try to remember to try it. I assume ganim get launched as a background process by Xfce when starting X, and fortunately it exits when exiting X (and _not_ staying active as a daemon). > >> In any case, the mount was done after X was started, and switching > >> vtys crashes X so I don't do that. > > > > That sounds a bit wrong... > > Agreed, but I saw someone else was having a similar problem > with 9.0 release a bit earlier on a system, and no problem > with 8.3. At least I think that was it. Hmmm, just looked > and there's a firefox-bin.core and an xfce-appfinder.core. > Timestamps look about right for when I did a vty switch. So it's not only X crashing, it's also applications crashing (and so causing a core dump). -- 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: umount device busy
On Sun, 3 Jun 2012, Gary Aitken wrote: This almost always means someone (i.e. you) is sitting in the directory. If you tried this while su'ed and the un-su'ed you were still in the directory /mnt/goflex, you'd get this message. This may also happen if someone (i.e. you) is in the directory on another vtty. Naturally it can also mean some operation is in progress, but generally you would have recognized and avoided that. That's what I kept thinking. Backed out of all su ops, checked all xterms; nada. no other vtys opened. In any case, the mount was done after X was started, and switching vtys crashes X so I don't do that. This needs fixing. I thought maybe so, but didn't know for sure. Thanks. But Lars' "mount -p" is more assuring. I like it because if you happen to have a configuration you would like to use again, you can capture the output and make it your fstab, + or - automount adjustments. 3. I tried lsof but I don't get any output from it: lsof +d /mnt/goflex -x -- /mnt/goflex Where does it go if not to stdout? You've got me! But why is there anything after -x? I don't quite understand. Otherwise -x thinks the /mnt/goflex belongs to it. But what if you leave out ALL the stuff after -x. Isn't it redundant with the +d switch? (That's not a Socratic question: I don't know.) Anyway, I found the lsof FAQ by make extract in the port. I quess I am not too good at reading Makefiles because I don't see why it isn't copied to /usr/local/share/lsof with the README and whatnot. man -t lsof | sp2ascii > savefile.txt Where'd you get/find sp2ascii? I don't see one anywhere, not even on google. (Except this thread...) Secret weapon? That's a good question. Turns out all kinds of ps converters are installed by ghostscript. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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: umount device busy
On 06/03/12 21:05, Polytropon wrote: > Good idea. However, you can do efficient backups of "Windows" > data by using the "ntfsprogs" tools. This makes sure they can > even be read under non-"Windows" systems. I'll look into that. >>> if you are using xfce4, then you have most likely got gamin >>> running as well, this caused the same problem for me when >>> trying to umount an external USB drive >> >> gamin *is* installed, and I did have the file browser up and >> using it to look at the ntfs disk. I thought it might be >> holding a file open, so first I backed it out to something >> not on the ntfs disk, then exited it. Made no difference. > > Maybe the ganim "lock" is regarding a device file? Not sure > about that, I'm not using it here. I'm not sure what the deal is here, but exiting X does solve the problem. I didn't try just killing the environment by shutting down the wm and leaving X up, but if I forget and do something like that again I'll try to remember to try it. >> In any case, the mount was done after X was started, and switching >> vtys crashes X so I don't do that. > > That sounds a bit wrong... Agreed, but I saw someone else was having a similar problem with 9.0 release a bit earlier on a system, and no problem with 8.3. At least I think that was it. Hmmm, just looked and there's a firefox-bin.core and an xfce-appfinder.core. Timestamps look about right for when I did a vty switch. > Typo maybe? A command like "ps2ascii" sounds more reasonable if > we consider PS being the output format. The command duh. need sleep. 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: umount device busy
On Sun, 03 Jun 2012 20:28:28 -0600, Gary Aitken wrote: > > Consider NTFS being part of the problem, i. e. problems with the > > _ntfs file system driver provided by the OS (as it seems you're > > not using FUSE tools here - there are "fusefs-ntfs" and "ntfsprogs" > > in the ports collection which may provide a functionality the > > base system is missing here). > > may try that but will probably decide to use two different drives > for removable backup, one for windoze and one for fbsd. Good idea. However, you can do efficient backups of "Windows" data by using the "ntfsprogs" tools. This makes sure they can even be read under non-"Windows" systems. > > if you are using xfce4, then you have most likely got gamin > > running as well, this caused the same problem for me when > > trying to umount an external USB drive > > gamin *is* installed, and I did have the file browser up and > using it to look at the ntfs disk. I thought it might be > holding a file open, so first I backed it out to something > not on the ntfs disk, then exited it. Made no difference. Maybe the ganim "lock" is regarding a device file? Not sure about that, I'm not using it here. > In any case, the mount was done after X was started, and switching > vtys crashes X so I don't do that. That sounds a bit wrong... > >> 4. lsof has a *long* man page, so I'd like to save it temporarily > >> so I can search it in an editor. If I do man lsof>temp.tmp > >> the output contains backspace sequences which screw up searching. > >> How do I get man to produce plain text without the control sequences? > > > > You can use less's search (key "/") when using the "man lsof" > > command. You can also use a PDF viewer (including text search > > functionality) so you can keep the formatting details. > > > > The following command does the trick: > > > > zcat `man -w lsof` | groff -Tps -dpaper=a4 -P-pa4 -mandoc | ps2pdf - > > /tmp/man_1_lsof.pdf > > > > To convert to pure text, use -Tascii or -Tlatin1; however, this > > renders to pure text without keeping the formatting intact. > > Thanks. I get a > grops: can't open file `a4` but I'll deal with that later. That's just for formatting the paper format (ISO A4 here). You can omit those options, the default format (in your case I assume it will be letter) will be selected. > > man -t lsof | sp2ascii > savefile.txt > > Where'd you get/find sp2ascii? I don't see one anywhere, not even on google. > (Except this thread...) Secret weapon? Typo maybe? A command like "ps2ascii" sounds more reasonable if we consider PS being the output format. The command % man -t lsof | ps2ascii > man_1_lsof.txt works as intended. The only remaining control character is ^L, means "page break" (for "form feed" to be precise). > > 6. And finally, any idea why umount says the device is busy? > > > You could use "umount -f" to force it, but that may result in > > files missing. > > hope not, but not a heck of a lot of choices at this point. > Since I didn't do squat because of the failed mkdir, seems hopeful. You can always call the command % sync to request writing any pending buffers; however, the system will decide when the actual writes to the media will happen. :-) > I've mounted them ro a number of times, but never tried writing before. In that case, using "fuse-ntfs" seems to be the better choice as the NTFS support of the base system is considered "good enough for r/o". > > something that *might* be helpful to you, it's a basic little man page > > browser in Qt > > left side of the pane shows a treeview of filesystem, so you can navigate > > /bin, /usr/bin, etc.. when you click on a file it looks for the > > corresponding man page and shows it on the right pane formatted html, which > > is a webkit panel. > > > > https://github.com/creamy/man-browser > > > > it is intended as a way to quickly look at what's installed on your system > > and possibly 'discover' and learn about previously 'unknown' commands. > > Thanks. There's also a traditional way: xman. You can use it like % xman -bothshown then select "Manual Page" and then select a command from the directory on top. It's quite simple, but renders fast. -- 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: umount device busy
Combining several responses to save traffic; thanks all >> Something I'm overlooking here and a lot of questions I can't seem to find >> the answers to... >> >> I mounted a usb drive >> mount -t ntfs /dev/da0s1 /mnt/goflex >> >> Then, as nearly as I can remember... >> I then poked around a bit using the xfce4 browser. >> I tried to mkdir from the mount point as a normal user: >> cd /mnt/goflex >> %mkdir breakaway >> mkdir: .: No such file or directory >> After checking write premissions, which I didn't have, >> I did an su -l and tried again, with the same results. >> >> I then tried to unmount the drive, believing it was mounted read-only: >> #umount /mnt/goflex >> umount: unmount of /mnt/goflex failed: Device busy >> >> As nearly as I can tell, I don't have anything pointing at that drive. >> >> Questions: >> >> 1. What does the "No such file or directory" mean from mkdir? >> It's a relative dir name, and I'm sitting at a valid dir.On 06/03/12 09:24, >> Polytropon wrote: > On Sun, 03 Jun 2012 08:59:11 -0600, Gary Aitken wrote: >> Something I'm overlooking here and a lot of questions I can't >> seem to find the answers to... >> >> I mounted a usb drive >>mount -t ntfs /dev/da0s1 /mnt/goflex >> >> Then, as nearly as I can remember... >>I then poked around a bit using the xfce4 browser. >>I tried to mkdir from the mount point as a normal user: >> cd /mnt/goflex >> %mkdir breakaway >> mkdir: .: No such file or directory >>After checking write premissions, which I didn't have, >>I did an su -l and tried again, with the same results. >> >> I then tried to unmount the drive, believing it was mounted read-only: >> #umount /mnt/goflex >> umount: unmount of /mnt/goflex failed: Device busy >> >> As nearly as I can tell, I don't have anything pointing at that drive. >> >> Questions: >> >> 1. What does the "No such file or directory" mean from mkdir? >> It's a relative dir name, and I'm sitting at a valid dir. > I think I remember having read about problems with "Windows"-based > file system use, such as valid directories becoming invalid. The > error message you mentioned states /mnt/goflex is not a valid > directory (anymore), that's why no directory entry can be created > here. It's still valid. I can cd there and look at anything in the subtree. > Consider NTFS being part of the problem, i. e. problems with the > _ntfs file system driver provided by the OS (as it seems you're > not using FUSE tools here - there are "fusefs-ntfs" and "ntfsprogs" > in the ports collection which may provide a functionality the > base system is missing here). may try that but will probably decide to use two different drives for removable backup, one for windoze and one for fbsd. > if you are using xfce4, then you have most likely got gamin running as well, > this caused the same problem for me when trying to umount an external USB > drive gamin *is* installed, and I did have the file browser up and using it to look at the ntfs disk. I thought it might be holding a file open, so first I backed it out to something not on the ntfs disk, then exited it. Made no difference. Also, no gamin currently running. But as Warren Block noted, it causes this problem, so I'm assuming that is it. > I resolved my umount problem by including the -f switch > > #umount -f /mnt/goflex Which is what I am ending up doing. > This almost always means someone (i.e. you) is sitting in the directory. > If you tried this while su'ed and the un-su'ed you were still in the > directory /mnt/goflex, you'd get this message. This may also happen if > someone (i.e. you) is in the directory on another vtty. Naturally it can > also mean some operation is in progress, but generally you would have > recognized and avoided that. That's what I kept thinking. Backed out of all su ops, checked all xterms; nada. no other vtys opened. In any case, the mount was done after X was started, and switching vtys crashes X so I don't do that. > You did not provide a history with this problem, but generally it means some > part of the path before the last does not exist. I get it for using a > leading /, when I meant a relative path, or not using the leading slash when > I meant an absolute path -- and of course for misspelling some part of the > path. Nice to know someone else admits to that too :-). In this case, not the problem. >> 2. How do I find out how
Re: umount device busy
On Sun, Jun 3, 2012 at 7:59 AM, Gary Aitken wrote: > Something I'm overlooking here and a lot of questions I can't seem to find > the answers to... > > I mounted a usb drive > mount -t ntfs /dev/da0s1 /mnt/goflex > > Then, as nearly as I can remember... > I then poked around a bit using the xfce4 browser. > I tried to mkdir from the mount point as a normal user: >cd /mnt/goflex >%mkdir breakaway >mkdir: .: No such file or directory > After checking write premissions, which I didn't have, > I did an su -l and tried again, with the same results. > > I then tried to unmount the drive, believing it was mounted read-only: > #umount /mnt/goflex >umount: unmount of /mnt/goflex failed: Device busy > > As nearly as I can tell, I don't have anything pointing at that drive. > > Questions: > > 1. What does the "No such file or directory" mean from mkdir? >It's a relative dir name, and I'm sitting at a valid dir. > > 2. How do I find out how the file-system was mounted? >mount (noargs) does not show read/write status > > 3. I tried lsof but I don't get any output from it: > lsof +d /mnt/goflex -x -- /mnt/goflex >Where does it go if not to stdout? > > 4. lsof has a *long* man page, so I'd like to save it temporarily so I > can search it in an editor. If I do man lsof >temp.tmp the output contains > backspace sequences which screw up searching. How do I get man to produce > plain text without the control sequences? > > 5. The lsof man page references a faq which is supposed to be part of the > distribution. >find . -ls | grep lsof doesn't show any faq. > > 6. And finally, any idea why umount says the device is busy? > > Seems like I should have been able to find the answer to at least one of > those but I'm coming up short. > > Thanks for relevant pointers, > > Gary > ___ > 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" > something that *might* be helpful to you, it's a basic little man page browser in Qt left side of the pane shows a treeview of filesystem, so you can navigate /bin, /usr/bin, etc.. when you click on a file it looks for the corresponding man page and shows it on the right pane formatted html, which is a webkit panel. https://github.com/creamy/man-browser i built it on a FreeBSD machine but it also works with cygwin systems and probably GNU/Linux as well but i have not tried it. it is intended as a way to quickly look at what's installed on your system and possibly 'discover' and learn about previously 'unknown' commands. 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: umount device busy
On Sun, 3 Jun 2012, Gary Aitken wrote: 6. And finally, any idea why umount says the device is busy? xfce uses gamin to scan for new files and directories, but it causes just this problem. Edit /usr/local/etc/gamin/gaminrc and set it to poll the device directory: poll /mnt/* ___ 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: umount device busy
Gary Aitken wrote: > > Something I'm overlooking here and a lot of questions I can't seem to find > the answers to... > > I mounted a usb drive > mount -t ntfs /dev/da0s1 /mnt/goflex > > Then, as nearly as I can remember... > I then poked around a bit using the xfce4 browser. > I tried to mkdir from the mount point as a normal user: > cd /mnt/goflex > %mkdir breakaway > mkdir: .: No such file or directory > After checking write premissions, which I didn't have, > I did an su -l and tried again, with the same results. > > Questions: > > 1. What does the "No such file or directory" mean from mkdir? > It's a relative dir name, and I'm sitting at a valid dir. The specific complaint was concerning '.' this indicates a filesystem error. Note: it is (or, at least 'used to be') documented that _writing_ to NTFS filesystems was likely to have problems. > > 2. How do I find out how the file-system was mounted? > mount (noargs) does not show read/write status Yes, it does. :) 'readonly' means just that. 'readonly' NOT shown means read/write. > 6. And finally, any idea why umount says the device is busy? ABSOLUTELY! *GRIN* You did a cd to a directory located on that device. you started a 'su' process. Maybe you did a cd to 'somewhere else', or maybe not. Then you tried to umount the device. The current process may have the 'working directory' open on that drive. The _PARENT_ of the su process *DOES* have the 'working directory' open there. The O/S rightly refuses to unmount the device in such a situation. :) ___ 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: umount device busy
On Sun, 3 Jun 2012, Gary Aitken wrote: Something I'm overlooking here and a lot of questions I can't seem to find the answers to... I mounted a usb drive mount -t ntfs /dev/da0s1 /mnt/goflex Then, as nearly as I can remember... I then poked around a bit using the xfce4 browser. I tried to mkdir from the mount point as a normal user: cd /mnt/goflex %mkdir breakaway mkdir: .: No such file or directory After checking write premissions, which I didn't have, I did an su -l and tried again, with the same results. I then tried to unmount the drive, believing it was mounted read-only: #umount /mnt/goflex umount: unmount of /mnt/goflex failed: Device busy This almost always means someone (i.e. you) is sitting in the directory. If you tried this while su'ed and the un-su'ed you were still in the directory /mnt/goflex, you'd get this message. This may also happen if someone (i.e. you) is in the directory on another vtty. Naturally it can also mean some operation is in progress, but generally you would have recognized and avoided that. As nearly as I can tell, I don't have anything pointing at that drive. As I said, were you in the directory when you su'd? If so, you need to drop back and get out before you su again an umount. Questions: 1. What does the "No such file or directory" mean from mkdir? It's a relative dir name, and I'm sitting at a valid dir. You did not provide a history with this problem, but generally it means some part of the path before the last does not exist. I get it for using a leading /, when I meant a relative path, or not using the leading slash when I meant an absolute path -- and of course for misspelling some part of the path. 2. How do I find out how the file-system was mounted? mount (noargs) does not show read/write status Did you try $mount -p ? 3. I tried lsof but I don't get any output from it: lsof +d /mnt/goflex -x -- /mnt/goflex Where does it go if not to stdout? You've got me! But why is there anything after -x? I don't quite understand. 4. lsof has a *long* man page, so I'd like to save it temporarily so I can search it in an editor. If I do man lsof >temp.tmp the output contains backspace sequences which screw up searching. How do I get man to produce plain text without the control sequences? man -t lsof | sp2ascii > savefile.txt 5. The lsof man page references a faq which is supposed to be part of the distribution. find . -ls | grep lsof doesn't show any faq. I can't find it either, but I don't know why the above did not show /usr/local/share/lsof . /usr/local/share is where to look for such things, and /usr/local/share/doc is generally where any docs that are install are / found. 6. And finally, any idea why umount says the device is busy? Answered above. When you su, where you may go while su'd has no effect on where you left yourself. You (as a normal user) are still on the mounted directory so the mounted device is busy. You have to drop back (exit su) and move out of the device before you can umount it. Seems like I should have been able to find the answer to at least one of those but I'm coming up short. Thanks for relevant pointers, -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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: umount device busy
Hi Gary, if you are using xfce4, then you have most likely got gamin running as well, this caused the same problem for me when trying to umount an external USB drive I resolved my umount problem by including the -f switch #umount -f /mnt/goflex Dave Whytcross - Original Message - From: "Gary Aitken" To: "FreeBSD Mailing List" Sent: Monday, June 04, 2012 12:59 AM Subject: umount device busy Something I'm overlooking here and a lot of questions I can't seem to find the answers to... I mounted a usb drive mount -t ntfs /dev/da0s1 /mnt/goflex Then, as nearly as I can remember... I then poked around a bit using the xfce4 browser. I tried to mkdir from the mount point as a normal user: cd /mnt/goflex %mkdir breakaway mkdir: .: No such file or directory After checking write premissions, which I didn't have, I did an su -l and tried again, with the same results. I then tried to unmount the drive, believing it was mounted read-only: #umount /mnt/goflex umount: unmount of /mnt/goflex failed: Device busy As nearly as I can tell, I don't have anything pointing at that drive. Questions: 1. What does the "No such file or directory" mean from mkdir? It's a relative dir name, and I'm sitting at a valid dir. 2. How do I find out how the file-system was mounted? mount (noargs) does not show read/write status 3. I tried lsof but I don't get any output from it: lsof +d /mnt/goflex -x -- /mnt/goflex Where does it go if not to stdout? 4. lsof has a *long* man page, so I'd like to save it temporarily so I can search it in an editor. If I do man lsof >temp.tmp the output contains backspace sequences which screw up searching. How do I get man to produce plain text without the control sequences? 5. The lsof man page references a faq which is supposed to be part of the distribution. find . -ls | grep lsof doesn't show any faq. 6. And finally, any idea why umount says the device is busy? Seems like I should have been able to find the answer to at least one of those but I'm coming up short. Thanks for relevant pointers, Gary ___ 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: umount device busy
On Sun, 03 Jun 2012 08:59:11 -0600, Gary Aitken wrote: > Something I'm overlooking here and a lot of questions I can't > seem to find the answers to... > > I mounted a usb drive > mount -t ntfs /dev/da0s1 /mnt/goflex > > Then, as nearly as I can remember... > I then poked around a bit using the xfce4 browser. > I tried to mkdir from the mount point as a normal user: > cd /mnt/goflex > %mkdir breakaway > mkdir: .: No such file or directory > After checking write premissions, which I didn't have, > I did an su -l and tried again, with the same results. > > I then tried to unmount the drive, believing it was mounted read-only: > #umount /mnt/goflex > umount: unmount of /mnt/goflex failed: Device busy > > As nearly as I can tell, I don't have anything pointing at that drive. > > Questions: > > 1. What does the "No such file or directory" mean from mkdir? > It's a relative dir name, and I'm sitting at a valid dir. I think I remember having read about problems with "Windows"-based file system use, such as valid directories becoming invalid. The error message you mentioned states /mnt/goflex is not a valid directory (anymore), that's why no directory entry can be created here. Consider NTFS being part of the problem, i. e. problems with the _ntfs file system driver provided by the OS (as it seems you're not using FUSE tools here - there are "fusefs-ntfs" and "ntfsprogs" in the ports collection which may provide a functionality the base system is missing here). > 2. How do I find out how the file-system was mounted? > mount (noargs) does not show read/write status It does - implicitely. For -o ro, it shows "read-only". > 3. I tried lsof but I don't get any output from it: > lsof +d /mnt/goflex -x -- /mnt/goflex > Where does it go if not to stdout? If no output redirection is applied, consider the output being empty, as no error message is displayed (so both stdout and stderr are silent). > 4. lsof has a *long* man page, so I'd like to save it temporarily > so I can search it in an editor. If I do man lsof >temp.tmp > the output contains backspace sequences which screw up searching. > How do I get man to produce plain text without the control sequences? You can use less's search (key "/") when using the "man lsof" command. You can also use a PDF viewer (including text search functionality) so you can keep the formatting details. The following command does the trick: zcat `man -w lsof` | groff -Tps -dpaper=a4 -P-pa4 -mandoc | ps2pdf - /tmp/man_1_lsof.pdf To convert to pure text, use -Tascii or -Tlatin1; however, this renders to pure text without keeping the formatting intact. > 6. And finally, any idea why umount says the device is busy? Maybe there are writes pending, or it's just "held open" by Xfce. Make sure no terminal session has the mount point as current working directory, which would imply "device busy", even if there's no actual reading or writing action. > Seems like I should have been able to find the answer to at > least one of those but I'm coming up short. You could use "umount -f" to force it, but that may result in files missing. Anyway, I've never actually used NTFS with FreeBSD so this could also be a source of the problem. -- 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"
umount device busy
Something I'm overlooking here and a lot of questions I can't seem to find the answers to... I mounted a usb drive mount -t ntfs /dev/da0s1 /mnt/goflex Then, as nearly as I can remember... I then poked around a bit using the xfce4 browser. I tried to mkdir from the mount point as a normal user: cd /mnt/goflex %mkdir breakaway mkdir: .: No such file or directory After checking write premissions, which I didn't have, I did an su -l and tried again, with the same results. I then tried to unmount the drive, believing it was mounted read-only: #umount /mnt/goflex umount: unmount of /mnt/goflex failed: Device busy As nearly as I can tell, I don't have anything pointing at that drive. Questions: 1. What does the "No such file or directory" mean from mkdir? It's a relative dir name, and I'm sitting at a valid dir. 2. How do I find out how the file-system was mounted? mount (noargs) does not show read/write status 3. I tried lsof but I don't get any output from it: lsof +d /mnt/goflex -x -- /mnt/goflex Where does it go if not to stdout? 4. lsof has a *long* man page, so I'd like to save it temporarily so I can search it in an editor. If I do man lsof >temp.tmp the output contains backspace sequences which screw up searching. How do I get man to produce plain text without the control sequences? 5. The lsof man page references a faq which is supposed to be part of the distribution. find . -ls | grep lsof doesn't show any faq. 6. And finally, any idea why umount says the device is busy? Seems like I should have been able to find the answer to at least one of those but I'm coming up short. Thanks for relevant pointers, Gary ___ 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"
lpt0 "device busy"
Just recently I've started having a problem with my HP 5N it was printing fine. Now, whatever I do lpt0 shows "device busy". I've googled reinstalled apsfilter and put the printer through all the self tests (passed) and verified there's nothing in the printer's memory. I've rebuilt userland and kernel. Even tried cups and anything sent to /dev/lpt0 returns that error. dmesg: ppc1: port 0xe800-0xe807,0xe400-0xe407,0xe000-0xe007,0xd800-0xd807,0xd400-0xd407,0xd000-0xd00f irq 21 at device 3.0 on pci3 ppc1: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppc1: [ITHREAD] ppbus0: on ppc1 ppbus0: IEEE1284 device found /NIBBLE/ECP/ECP_RLE ppbus0: Probing for PnP devices: ppbus0: PJL,MLC,PCL,PCLXL lpt0: on ppbus0 lpt0: [ITHREAD] lpt0: Interrupt-driven port ppi0: on ppbus0 uname: FreeBSD pinnacle.akherb.com 8.0-CURRENT FreeBSD 8.0-CURRENT #70: Mon Feb 2 03:17:26 AKST 2009 r...@pinnacle.akherb.com:/usr/obj/usr/src/sys/PINNACLE i386 fstat /dev/lpt0 and fstat /pt0.ctl show nothing. Ant attempt at changing settings with lptcontrol also result in a "device busy" error. pinnacle# lptcontrol -p -d /dev/lpt0.ctl lptcontrol: open: Device busy I'm totally at a loss to figure out what's changed does anyone have any suggestions? I really need to get this working. Beech -- --- Beech Rintoul - FreeBSD Developer - be...@freebsd.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.1R/announce.html --- ___ 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"
Solved: Re: /dev/lpt0: Device busy, lptcontrol: ioctl: Operation not supported
On Wed, Jan 23, 2008 at 12:47:56PM +, Anton Shterenlikht wrote: > > My printing stopped working quite suddenly. > > Until today I used FBSD-6.3-prerelease (today I updated to 6.3-stable) > on compaq armada 1700 laptop to print on a parallel HP laserjet 2100 > printer in text mode and for postscript via apsfilter. All was fine. > > Then I got another parallel printer, epson lq-550 24-pin dot matrix, > and played with printing on both printers by just unplugging one > and plugging the other to the laptop's parallel port. For a while > all was fine. > > However, after several days, I cannot now print on either printer. > With laserjet I get > > # lptest 20 20 > /dev/lpt0 > /dev/lpt0: Device busy. > > With matrix printer I get > # lptest 20 20 > /dev/lpt0 > # > > but nothing is printed. > > I tried to play with lptcontrol, but I get the following: > > # lptcontrol -i -d /dev/lpt0.ctl > lptcontrol: ioctl: Operation not supported > # lptcontrol -s -d /dev/lpt0.ctl > lptcontrol: ioctl: Operation not supported > > I updated the OS and rebuilt the kernel: FreeBSD 6.3-STABLE > Wed Jan 23 10:46:54 GMT 2008, but that didn't help. > > In my device.hints I have the following printer related lines: > hint.ppc.0.at="isa" > #hint.ppc.0.irq="7" > > to enable the polling mode. > > My parallel port settings: > > # grep ppc /var/run/dmesg.boot > ppc0: at port 0x378-0x37f on isa0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > ppbus0: on ppc0 > # > > There is nothing in the /var/log/lpd-errs. > > My questions: > > 1.Could I have fried my parallel chip by changing the printers with > laptop powered on? How can I check this? Well, it seems there was some problem with the parallel chip. I tried various flags with ppc(4), polling and interrupt mode, with no luck, the "device busy" message was still there, and nothing would print. After that I decided to switch the machine off and on again, not just a hot reboot. And that did help, both printers are working fine. Perhaps due to hot swithching of printers there was some charge(?) on the parallel port chip, which made it appear busy.. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/lpt0: Device busy, lptcontrol: ioctl: Operation not supported
My printing stopped working quite suddenly. Until today I used FBSD-6.3-prerelease (today I updated to 6.3-stable) on compaq armada 1700 laptop to print on a parallel HP laserjet 2100 printer in text mode and for postscript via apsfilter. All was fine. i use my laptop to print on my laserjet, and it works by default settings, but /usr/sbin/lptcontrol -d /dev/lpt0.ctl -e make it much faster. but nothing like you say. check under DOS, but it may be cable problem. ppc0: at port 0x378-0x37f on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 what i have (i don't disable interrupt) ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 1 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold check BIOS settings too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/dev/lpt0: Device busy, lptcontrol: ioctl: Operation not supported
Hello My printing stopped working quite suddenly. Until today I used FBSD-6.3-prerelease (today I updated to 6.3-stable) on compaq armada 1700 laptop to print on a parallel HP laserjet 2100 printer in text mode and for postscript via apsfilter. All was fine. Then I got another parallel printer, epson lq-550 24-pin dot matrix, and played with printing on both printers by just unplugging one and plugging the other to the laptop's parallel port. For a while all was fine. However, after several days, I cannot now print on either printer. With laserjet I get # lptest 20 20 > /dev/lpt0 /dev/lpt0: Device busy. With matrix printer I get # lptest 20 20 > /dev/lpt0 # but nothing is printed. If I use the spooling system with laserjet I get # lpq waiting for lp to become ready (offline?) Rank Owner Job Files Total Size 1stroot 9(standard input) 317 bytes # cat /var/spool/lpd/good/log PAGE: 1 1 INFO: Printing page 1... # # cat /var/spool/lpd/good/status waiting for lp to become ready (offline?) # and the printer never becomes online. With matrix printer I get # lpq lp is ready and printing Rank Owner Job Files Total Size active root 8(standard input) 317 bytes # lpq no entries but again nothing is printed. I tried to play with lptcontrol, but I get the following: # lptcontrol -i -d /dev/lpt0.ctl lptcontrol: ioctl: Operation not supported # lptcontrol -s -d /dev/lpt0.ctl lptcontrol: ioctl: Operation not supported I updated the OS and rebuilt the kernel: FreeBSD 6.3-STABLE Wed Jan 23 10:46:54 GMT 2008 but that didn't help. In my device.hints I have the following printer related lines: hint.ppc.0.at="isa" #hint.ppc.0.irq="7" to enable the polling mode. My parallel port settings: # grep ppc /var/run/dmesg.boot ppc0: at port 0x378-0x37f on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 # There is nothing in the /var/log/lpd-errs. I did find some similar posts in various archives, but couldn't see any suggestions. My questions: 1. Could I have fried my parallel chip by changing the printers with laptop powered on? How can I check this? 2. What does "Device busy" really mean, and why I cannot change the setting with lptcontrol? 3. Any other tests I could do to pinpoint the source of the problem? many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
HP LaserJet 1020 "Device Busy"
If anyone out there has this printer or knows anything about printing in general... My printer: HP LaserJet 1020 www.linuxprinting.org recommended driver: foo2zjs 1. I install the port /usr/ports/print/foo2zjs. 2. I plug the printer into the USB port, dmesg reports: ulpt0: Hewlett-Packard HP LaserJet 1020, rev 2.00/1.00, addr 2, iclass 7/1 ulpt0: using bi-directional mode 3. The foo2zjs docs state the printer needs to have its firmware uploaded first: # cat ./sihp1020.dl > /dev/ulpt0 After several minutes (5, maybe 10) I get: "/dev/ulpt0: Device busy." Where did I go wrong? -Modulok- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Device Busy
Hello, I am installing a FreeBSD 6.1 i386 machine and using IPF. When I apply some variables to sysctl for IPF I end up with a device busy response. the variables in question are: net.inet.ipf.fr_tcpclosed=1 net.inet.ipf.fr_tcpclosewait=60 net.inet.ipf.fr_tcphalfclosed=300 net.inet.ipf.fr_tcpidletimeout=7200 net.inet.ipf.fr_tcplastack=20 net.inet.ipf.fr_tcptimeout=120 net.inet.ipf.fr_udptimeout=120 The problem occurs both on startup with these in sysctl.conf and if I try do enter it manually: imap# sysctl net.inet.ipf.fr_tcpclosed=1 net.inet.ipf.fr_tcpclosed: 120 sysctl: net.inet.ipf.fr_tcpclosed: Device busy These are the same variables that I have been using successfully on other versions of FreeBSD (5.x and 4.x) so I am inclined to think that I am missing something obvious in this latest version. I am running: FreeBSD 6.1-RELEASE-p2 with: ipf: IP Filter: v4.1.8 (416) Any pointers? Thanks, Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Device busy
Guus De Graeve wrote: Hello, I was wondering if someone could help me with an anoying problem i having for a while now. It's about my printer a 'Brother HL-2030', it's attached to my first usb port and recognized by the kernel as /dev/ulpt0. ulpt0: Brother HL-2030 series, rev 2.00/1.00, addr 2, iclass 7/1 ulpt0: using bi-directional mode When i try to print to my printer with a basic test like 'echo Test > /dev/ulpt0' i get the message "/dev/ulpt0: Device busy". The problem is that i can't think of any other running proces that could be using the port to. My FreeBSD version is 6.0 Thanks, Greetings Guus De Graeve, ___ Hi, I believe the problem is actually that your printer does not accept plain text input. You need to run it through a filter first. The problem is that many new printers only accept input in the form of a binary command language. In the case of this printer it is through GDI, a windows standard. I notice on the Brother website that a linux driver is available. Perhaps this would be a starting point. It would definitely be worth checking out CUPS, the Common UNIX Printing System. I don't know if it supports this particular printer but it seems to offer support for a lot of different printing devices. Hope this helps, Duane Whitty, -- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Device busy
Hello, I was wondering if someone could help me with an anoying problem i having for a while now. It's about my printer a 'Brother HL-2030', it's attached to my first usb port and recognized by the kernel as /dev/ulpt0. ulpt0: Brother HL-2030 series, rev 2.00/1.00, addr 2, iclass 7/1 ulpt0: using bi-directional mode When i try to print to my printer with a basic test like 'echo Test > /dev/ulpt0' i get the message "/dev/ulpt0: Device busy". The problem is that i can't think of any other running proces that could be using the port to. My FreeBSD version is 6.0 Thanks, Greetings Guus De Graeve, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
2 probs w/ backup.sh: "Device busy" and "dangling vnode"
Dear All, I am experiencing two problems with the following backup script: #!/bin/sh /sbin/mount /backup/ /usr/local/bin/rsync -ax --delete /usr/ /backup/ /bin/sleep 15 /sbin/umount /backup/ echo 'backup of IWS complete' Here is the cron entry that calls it: 0 3 * * * time -h /root/backup.sh Over the past 3 months, this script has yielded the following error perhaps once every two weeks or so: umount: unmount of /backup failed: Device busy backup of IWS complete 1m28.42s real 2.60s user 6.76s sys As a result, I upped the sleep time from 5 to 15 seconds 2 days ago. This morning, the script seemingly caused the system to crash, given the following evidence from /var/log/messages: Mar 2 20:11:48 www2 ntpd[442]: kernel time sync enabled 2001 Mar 2 21:20:08 www2 ntpd[442]: kernel time sync enabled 6001 Mar 2 23:02:33 www2 ntpd[442]: kernel time sync enabled 2001 Mar 2 23:36:43 www2 ntpd[442]: kernel time sync enabled 6001 Mar 2 23:53:47 www2 ntpd[442]: kernel time sync enabled 2001 Mar 3 01:19:04 www2 ntpd[442]: kernel time sync enabled 6001 Mar 3 01:36:07 www2 ntpd[442]: kernel time sync enabled 2001 Mar 3 02:10:19 www2 ntpd[442]: kernel time sync enabled 6001 Mar 3 02:27:23 www2 ntpd[442]: kernel time sync enabled 2001 Mar 3 08:18:30 www2 syslogd: kernel boot file is /boot/kernel/kernel Mar 3 08:18:30 www2 kernel: panic: unmount: dangling vnode Mar 3 08:18:30 www2 kernel: Uptime: 55d11h50m47s Mar 3 08:18:30 www2 kernel: Dumping 511 MB (2 chunks) Mar 3 08:18:30 www2 kernel: chunk 0: 1MB (159 pages) (CTRL-C to abort) Mar 3 08:18:30 www2 kernel: Dump aborted Mar 3 08:18:30 www2 kernel: Automatic reboot in 15 seconds - press a key on the console to abort Mar 3 08:18:30 www2 kernel: --> Press a key on the console to reboot, Mar 3 08:18:30 www2 kernel: --> or switch off the system now. Mar 3 08:18:30 www2 kernel: Rebooting... Mar 3 08:18:30 www2 kernel: Copyright (c) 1992-2005 The FreeBSD Project. Mar 3 08:18:30 www2 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Mar 3 08:18:30 www2 kernel: The Regents of the University of California. All rights reserved. Mar 3 08:18:30 www2 kernel: FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 Mar 3 08:18:30 www2 kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC As you can see, the machine apparently died sometime this morning after 2:27. The front-line sysadmin (not myself) rebooted the machine this morning at 8:18, and reports that at the "chunk 0: 1MB (159 pages) (CTRL-C to abort)" message, the system seemed to hang, with no apparent hard drive or other activity. He hit CTRL-C, receiving the "Automatic reboot in 15 seconds" message, but then the system seemed to hang again, at which point he hit CTRL-C a second time, and the machine rebooted. Any advice on debugging these two problems? Thank you. Chad Whitacre http://www.zetadev.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't open audio device /dev/dsp: Device busy
Hi, Running a pretty current 4.11-STABLE, my pcm is toshiba# dmesg|grep pcm Preloaded elf module "snd_pcm.ko" at 0xc05f81dc. pcm0: port 0xfebc-0xfebf,0xfec0-0xfeff mem 0xefdf-0xefdf7fff irq 11 at device 12.0 on pci0 pcm0: and sndstat toshiba# cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: at memory 0xefdf irq 11 (4p/2r/0v channels duplex) When I first boot things are fine. I start GAIM with "Automatic" and thats fine. But at some point it just stops working for GAIM and anything else like mplayerxp. I start to get "Can't open audio device /dev/dsp: Device busy" but with fstat I get : toshiba# fstat|grep dsp toshiba# What do I do?? Thanks, Tuc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB printing problem: /dev/ulpt0: device busy
On Fri, 4 Mar 2005, Eugene Rogoza wrote: I'm experiencing certain problems with USB printing. I have a Minolta PagePro 1300W printer connected to USB port. FreeBSD 5.3 recognizes the printer just fine and creates /dev/ulpt0 and /dev/unlpt0 device nodes. Printer model numbers that end in "W" are often Winprinters, lacking the ability to print plain text. There's more information on this printer and a PBM filter for it here: http://www.linuxprinting.org/show_printer.cgi?recnum=Minolta-PagePro_1300W So you'll have to set up Ghostscript to create PBMs, and then feed them to the PBM-to-Minolta filter, which then feeds them to the printer. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB printing problem: /dev/ulpt0: device busy
Hello everybody, I'm experiencing certain problems with USB printing. I have a Minolta PagePro 1300W printer connected to USB port. FreeBSD 5.3 recognizes the printer just fine and creates /dev/ulpt0 and /dev/unlpt0 device nodes. But the simple test like echo "test" > /dev/ulpt0 (or /dev/unlpt0) fails with the message "/dev/ulpt0: device busy". And, respectively, if simple tests fail, then the complicated printing via ghostscript -> filter -> driver also doesn't work. I suppose some program uses the device already, but I don't know what it can be - I'm not running lpd (device is busy either with lpd running or not). There isn't really much regarding this problem on the net. Usually people have their USB printers working. Any suggestions are appreciated. Eugene Rogoza ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd: "device busy" error when writing .iso
On Wed, Jan 12, 2005 at 01:42:43PM -0500, Jason Morgan wrote: > I am attempting to burn an .iso of the 5.3 mini distribution and keep > running into the following error: > > # burncd -f /dev/acd0 data 5.3-RELEASE-i386-miniinst.iso fixate > next writeable LBA 0 > writing from file 5.3-RELEASE-i386-miniinst.iso size 274400 KB > written this track 640 KB (0%) total 640 KB > only wrote -1 of 32768 bytes: Device busy > > fixating CD, please wait.. > > I have verified that the drive is working and is accessible. I have > tried different media and keep running into the same result. > > # dmesg | grep acd0 > acd0: DVDR at ata1-master PIO4 > > This is a new drive, that I just recently installed. > > Oh, I'm running FreeBSD 5.2.1-RELEASE-p11 #7. > > Any suggestions? I've only burned CDs with FreeBSD a few times and > never on this system, so I'm kinda a newb. > > Thanks for your time. I finally solved the problem. I had to include "device atapicam" in my kernel, then used cdrecord instead of burncd, using the drive as a scsi device. Hope this info will help some newb in the future. Cheers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd: "device busy" error when writing .iso
I am attempting to burn an .iso of the 5.3 mini distribution and keep running into the following error: # burncd -f /dev/acd0 data 5.3-RELEASE-i386-miniinst.iso fixate next writeable LBA 0 writing from file 5.3-RELEASE-i386-miniinst.iso size 274400 KB written this track 640 KB (0%) total 640 KB only wrote -1 of 32768 bytes: Device busy fixating CD, please wait.. I have verified that the drive is working and is accessible. I have tried different media and keep running into the same result. # dmesg | grep acd0 acd0: DVDR at ata1-master PIO4 This is a new drive, that I just recently installed. Oh, I'm running FreeBSD 5.2.1-RELEASE-p11 #7. Any suggestions? I've only burned CDs with FreeBSD a few times and never on this system, so I'm kinda a newb. Thanks for your time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Device busy...
On Dec 27, 2004, at 4:21 PM, Kris Kennaway wrote: On Mon, Dec 27, 2004 at 04:20:48PM -0600, Eric F Crist wrote: Hello list, How do I check what process is using a device to kill/rehup it? Try fstat or lsof Kris Thanks! That's what I was looking for. ___ Eric F Crist "I am so smart, S.M.R.T!" Secure Computing Networks -Homer J Simpson PGP.sig Description: This is a digitally signed message part
Re: Device busy...
On Mon, Dec 27, 2004 at 04:20:48PM -0600, Eric F Crist wrote: > Hello list, > > How do I check what process is using a device to kill/rehup it? Try fstat or lsof Kris pgpydOp1gQddV.pgp Description: PGP signature
Device busy...
Hello list, How do I check what process is using a device to kill/rehup it? I output certain syslog events to an Okidata line printer, and every so often, the printer stops printing, and when I try to output to /dev/lpt0, I get a device busy error. thanks ___ Eric F Crist "I am so smart, S.M.R.T!" Secure Computing Networks -Homer J Simpson PGP.sig Description: This is a digitally signed message part
Re: burncd: ioctl(CDIOCSTART): Device busy
More of a question, really. Why are you using 'fstat -n'? The -n option would appear to print only device numbers, not device names - therefore grepping for 'acd' will be fruitless, correct?. okay, so fstat | grep cd doesn't reveal anything either. cheers iain ORIGINAL MESSAGE hi there, i'm running freebsd 4.10 with a kodak CR-R drive. i can mount CD-ROM's in the drive with no problems, but when i insert a blank CD-R (cdr not cdrw... i checked!!) into the drive and attempt burncd i get the error burncd: ioctl(CDIOCSTART): Device busy i tried "fstat -n | grep acd" but no programs appear to be using the drive. the light on the CD drive keeps blinking orange too, indicating that it is trying to read the drive or something similar, but i have not issued any 'mount /cdrom' command. i found a similar problem in the lists archive posted by a guy named willian denton last year, but couldn't find any resolution to the problem. i emailed him to find out if he ever solved his problem but have not yet received a reply. [actually, i have now received a reply... he said he never solved the problem, he just bought a new drive. my drive works fine in other machines, and i can mount CD-ROM's with it, so i don't think it is broken] http://lists.freebsd.org/pipermail/freebsd-stable/2003-October/004262.html _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd: ioctl(CDIOCSTART): Device busy
On Tue, 10 Aug 2004, Iain Dooley wrote: i tried "fstat -n | grep acd" but no programs appear to be using the drive. the light on the CD drive keeps blinking orange too, indicating that it is trying to read the drive or something similar, but i have not issued any 'mount /cdrom' command. [...] any ideas? More of a question, really. Why are you using 'fstat -n'? The -n option would appear to print only device numbers, not device names - therefore grepping for 'acd' will be fruitless, correct?. -- David Fleck [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
burncd: ioctl(CDIOCSTART): Device busy
hi there, i'm running freebsd 4.10 with a kodak CR-R drive. i can mount CD-ROM's in the drive with no problems, but when i insert a blank CD-R (cdr not cdrw... i checked!!) into the drive and attempt burncd i get the error burncd: ioctl(CDIOCSTART): Device busy i tried "fstat -n | grep acd" but no programs appear to be using the drive. the light on the CD drive keeps blinking orange too, indicating that it is trying to read the drive or something similar, but i have not issued any 'mount /cdrom' command. i found a similar problem in the lists archive posted by a guy named willian denton last year, but couldn't find any resolution to the problem. i emailed him to find out if he ever solved his problem but have not yet received a reply. http://lists.freebsd.org/pipermail/freebsd-stable/2003-October/004262.html any ideas? cheers iain _ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp "device busy" - one possible solution
On Monday 09 February 2004 01:37, Mike Harding wrote: > I was playing around with kde 3.2 and a crashing artsd was locking up > my sound system - any further attempts to use sound from gnome or xmms > or anything failed with > > /dev/dsp - device busy > > messages. fstat and lsof showed nothing holding the device. A reboot > would fix it, but why reboot FreeBSD? > > I then remembered from a while ago that if I did the following... > > # cat /dev/dsp > > and then of course cntl-C to stop the output > > the device was no longer busy! What would be interesting to know, if that output stops sometime. Try: cat /dev/dsp > /var/tmp/out.wav That would mean, that arts has something written to the device upon crash and the device blocks, waiting for somebody to unload it. -- Melvyn === FreeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Jan 28 18:01:18 CET 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG i386 === pgp0.pgp Description: signature
/dev/dsp "device busy" - one possible solution
I was playing around with kde 3.2 and a crashing artsd was locking up my sound system - any further attempts to use sound from gnome or xmms or anything failed with /dev/dsp - device busy messages. fstat and lsof showed nothing holding the device. A reboot would fix it, but why reboot FreeBSD? I then remembered from a while ago that if I did the following... # cat /dev/dsp and then of course cntl-C to stop the output the device was no longer busy! I don't know why, but on my hardware at least (Turtle Beach Santa Cruz) this will 'unfreeze' the dsp output device. I'm just sending to the group as I searched for a while before I remembered my fix, and found no answers. So, if you are having the same problem looking for an answer, give this a try and report on your success. Maybe we can get this in to the FAQ. - Mike H. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Acer CDRW [ burncd: ioctl(CDRIOCBLANK): Device busy ]
I'm having a bad month. My harddrive died and I lost ALOT of data that is gonna take time to get back, I didn't have a good backup policy. I now have installed a cd-rewriter into my box, and plan to burn a cd once a week or so. My problem is that I can't seem to get it working... FreeBSD nowhere.nowhere.com 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Nov 27 23:17:53 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/NOWHERE i386 gaspra# burncd -f /dev/acd0c blank burncd: ioctl(CDRIOCBLANK): Device busy gaspra# /usr/sbin/burncd -f /dev/acd0 data /backup.iso fixate burncd: ioctl(CDIOCSTART): Input/output error When I burn with a normal cdr disc, it works fine. I gives the above errors for cdrw discs. What does this mean? How do I fix it? A search on google and the mail list doesn't exactly report a slew of questions or answers. Thanks, Matt. -- Matt Gostick <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Acer CDRW [ burncd: ioctl(CDRIOCBLANK): Device busy ]
I'm having a bad month. My harddrive died and I lost ALOT of data that is gonna take time to get back, I didn't have a good backup policy. I now have installed a cd-rewriter into my box, and plan to burn a cd once a week or so. My problem is that I can't seem to get it working... FreeBSD nowhere.nowhere.com 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Nov 27 23:17:53 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/NOWHERE i386 gaspra# burncd -f /dev/acd0c blank burncd: ioctl(CDRIOCBLANK): Device busy gaspra# /usr/sbin/burncd -f /dev/acd0 data /backup.iso fixate burncd: ioctl(CDIOCSTART): Input/output error When I burn with a normal cdr disc, it works fine. I gives the above errors for cdrw discs. What does this mean? How do I fix it? A search on google and the mail list doesn't exactly report a slew of questions or answers. Thanks, Matt. -- Matt Gostick <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Acer CDRW [ burncd: ioctl(CDRIOCBLANK): Device busy ]
I'm having a bad month. My harddrive died and I lost ALOT of data that is gonna take time to get back, I didn't have a good backup policy. I now have installed a cd-rewriter into my box, and plan to burn a cd once a week or so. My problem is that I can't seem to get is working... even though I've the same drive working on another FreeBSD box. FreeBSD nowhere.nowhere.com 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Nov 27 23:17:53 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/NOWHERE i386 gaspra# burncd -f /dev/acd0c blank burncd: ioctl(CDRIOCBLANK): Device busy gaspra# /usr/sbin/burncd -f /dev/acd0 data /backup.iso fixate burncd: ioctl(CDIOCSTART): Input/output error When I burn with a normal cdr disc, it works fine. What does this mean? How do I fix it? A search on google and the mail list doesn't exactly report a slew or questions or answers. Thanks, Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
On Sunday 25 January 2004 15:25, Geert Hendrickx wrote: > Unfortunately, when I click Ok, KDE wants to restart the Arts daemon, and > then, tragically, it complains dat /dev/dsp is busy... I think artsd just > doesn't "free" the device when it is killed manually, and therefore it > won't restart either. But I'll try it again on my next reboot, I think > this may solve the problem! Just recode your mp3's to ogg files and use `ogg123 -d arts' or Noatun, use kmplayer for movies and then think hard what you need esd/oss for again -:). I can say that the autosuspend feature works for me(tm) on -CURRENT and KDE 3.2-CVS, which will be released real soon now. Just make sure you disable a lot of unneeded sounds in the desktop, like 'shwoosh' on window resize, 'whammm' on window closure and so on, as these add to the 5 seconds. -- Melvyn === FreeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #3: Tue Dec 30 14:31:47 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG i386 === pgp0.pgp Description: signature
Re: /dev/dsp: Device busy
On Sat, 24 Jan 2004 11:54 pm, Geert Hendrickx wrote: > Hello, > > I have a problem playing sounds in FreeBSD. Sometimes it works, sometimes > it doesn't, and then I get the following error message: > > /dev/dsp: Device busy > > but "lsof | grep dsp" yields nothing. > > Can anyone help me with this mystery? :-) > > Thanks in advance, > > GH I dont know if this is the problem but it sounds similar to one I had recently. Sound was working then I portupgraded some things. Sound was a bit iffy for a while until I updated a bunch of other stuff, actually everything. It worked ok after that. Now running 5.2. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
On Sunday 25 January 2004 14:42, Stephen Martin wrote: > Geert, > > I was having this specific problem when trying to use mplayer. What I did > was change the "Autosuspend if idle for" setting. It can be found in > Control Center -> Sounds & Multimedia -> Sound System -> aRTs tab (feels > vaguely like describing a windows problem :). I set mine at 5 seconds. > Your's will of coarse depend. > > Stephen L. Martin That looks like the solution! :-) Unfortunately, when I click Ok, KDE wants to restart the Arts daemon, and then, tragically, it complains dat /dev/dsp is busy... I think artsd just doesn't "free" the device when it is killed manually, and therefore it won't restart either. But I'll try it again on my next reboot, I think this may solve the problem! Thanks! GH -- powered by FreeBSD ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
Geert, I was having this specific problem when trying to use mplayer. What I did was change the "Autosuspend if idle for" setting. It can be found in Control Center -> Sounds & Multimedia -> Sound System -> aRTs tab (feels vaguely like describing a windows problem :). I set mine at 5 seconds. Your's will of coarse depend. Stephen L. Martin > Hello, > > I have a problem playing sounds in FreeBSD. Sometimes it works, sometimes > it > doesn't, and then I get the following error message: > > /dev/dsp: Device busy > > but "lsof | grep dsp" yields nothing. > > Can anyone help me with this mystery? :-) > > Thanks in advance, > > GH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
On Sunday 25 January 2004 09:51, Geert Hendrickx wrote: > On Sunday 25 January 2004 02:46, George Vagner wrote: > > if your dual booting i found you must turn off power before you boot into > > bsd > > something with windows on a "restart" dont fully reset the soundcard on > > mine. > > toshiba satellite S2805-401 P3 700 with yamaha 741 soundcard. > > No Windows involved here. :-) > > Besides, it works fine when I reboot, it only stops working after a while. Check out sysctl: hw.snd.maxautovchans hw.snd.pcm0.vchans That way, you can give every app its own channel. No more busy soundcards. There is one drawback: If you want just one app to be able to play sound at a time, you can only remove write permission for the other channels. Daniela ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
On Sunday 25 January 2004 02:46, George Vagner wrote: > if your dual booting i found you must turn off power before you boot into > bsd > something with windows on a "restart" dont fully reset the soundcard on > mine. > toshiba satellite S2805-401 P3 700 with yamaha 741 soundcard. No Windows involved here. :-) Besides, it works fine when I reboot, it only stops working after a while. GH -- powered by FreeBSD ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
On Saturday 24 January 2004 8:19 pm, Dorin H. wrote: >--- Geert Hendrickx <[EMAIL PROTECTED]> wrote: >> Hello, >> >> I have a problem playing sounds in FreeBSD. >> Sometimes it works, sometimes it >> doesn't, and then I get the following error message: >> >> >> /dev/dsp: Device busy >> >> but "lsof | grep dsp" yields nothing. >> >> Can anyone help me with this mystery? :-) >> >> Thanks in advance, >> >> GH > >Same here. Toshiba laptop. FBSD 4.9. KDE 3.1.4. >/dev/dsp is from time to time hold by artsd. > > Problem is, it is hold even when nothing is played. >fstat /dev/dsp shows the problem. >If anyone find a solution, pls. let me know. >TIA, >/Dorin. While it's not a real solution, I told KDE not to start arts. Most of the sound apps I use are non-KDE, so thus far, I don't miss it. Oddly enough, this isn't a problem with debian. I'm too new to bsd to have figured out why one OS works and one doesn't. Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
if your dual booting i found you must turn off power before you boot into bsd something with windows on a "restart" dont fully reset the soundcard on mine. toshiba satellite S2805-401 P3 700 with yamaha 741 soundcard. - Original Message - From: "Dorin H." <[EMAIL PROTECTED]> To: "Geert Hendrickx" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, January 24, 2004 8:19 PM Subject: Re: /dev/dsp: Device busy > > --- Geert Hendrickx <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I have a problem playing sounds in FreeBSD. > > Sometimes it works, sometimes it > > doesn't, and then I get the following error message: > > > > > > /dev/dsp: Device busy > > > > but "lsof | grep dsp" yields nothing. > > > > Can anyone help me with this mystery? :-) > > > > Thanks in advance, > > > > GH > > > > Same here. Toshiba laptop. FBSD 4.9. KDE 3.1.4. > /dev/dsp is from time to time hold by artsd. > > Problem is, it is hold even when nothing is played. > fstat /dev/dsp shows the problem. > If anyone find a solution, pls. let me know. > TIA, > /Dorin. > > > > -- > > powered by FreeBSD/Postfix/KMail > > > > ___ > > [EMAIL PROTECTED] mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > __ > Do you Yahoo!? > Yahoo! SiteBuilder - Free web site building tool. Try it! > http://webhosting.yahoo.com/ps/sb/ > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
--- Geert Hendrickx <[EMAIL PROTECTED]> wrote: > Hello, > > I have a problem playing sounds in FreeBSD. > Sometimes it works, sometimes it > doesn't, and then I get the following error message: > > > /dev/dsp: Device busy > > but "lsof | grep dsp" yields nothing. > > Can anyone help me with this mystery? :-) > > Thanks in advance, > > GH > Same here. Toshiba laptop. FBSD 4.9. KDE 3.1.4. /dev/dsp is from time to time hold by artsd. Problem is, it is hold even when nothing is played. fstat /dev/dsp shows the problem. If anyone find a solution, pls. let me know. TIA, /Dorin. > -- > powered by FreeBSD/Postfix/KMail > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" __ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
> > > /dev/dsp: Device busy > > esd is the culprit. > But esd is not running... I checked it with ps. I'm having the same problem with mpg123, which uses esd: $ ps ax|grep esd $ mpg123 somefile.mp3 /dev/dsp: Device busy audio: Device busy $ ps ax|grep esd 11041 ?? Ss 0:00.14 esd -terminate -nobeeps -as 2 -spawnfd 5 $ kill 11041 $ ps ax|grep esd $ mpg123 somefile.mp3 This happens every time. It's definitively esd that doesn't let go of /dev/dsp, and for some reason, can't accept connections on its unix socket /tmp/.esd/socket. It's perhaps related to permissions (who starts esd)? I dunno exactly. I'm using a brute-force work-around here: #!/bin/sh # playmp3.sh -- brute force mpg123 (Bug: /dev/dsp: Device busy) until (mpg123 "$1") do sleep 1; done Ugly, but better than nothing. -- Cordula's Web. http://www.cordula.ws/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
On Saturday 24 January 2004 16:15, Michael Clark wrote: > Do you have a onboard sound card as well as a pci sound card? > > I use to run into this when I forgot to disable my onboard sound in bios. I don't think so. It's a laptop (Toshiba), and I doubt they'd put a second sound card in it. I really don't think it's a hardware problem, since it sometimes works under FreeBSD, and it always worked under Linux, without any problems. I guess arts has something to do with it, because I use KDE now, and I didn't use it with Linux. However, as said, "lsof | grep dsp" yields no results. GH -- powered by FreeBSD/Postfix/KMail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
On Saturday 24 January 2004 16:00, Cordula's Web wrote: > > /dev/dsp: Device busy > > esd is the culprit. But esd is not running... I checked it with ps. Besides, "esdplay foo.wav" gives the same error. GH -- powered by FreeBSD/Postfix/KMail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: Device busy
> /dev/dsp: Device busy esd is the culprit. -- Cordula's Web. http://www.cordula.ws/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/dev/dsp: Device busy
Hello, I have a problem playing sounds in FreeBSD. Sometimes it works, sometimes it doesn't, and then I get the following error message: /dev/dsp: Device busy but "lsof | grep dsp" yields nothing. Can anyone help me with this mystery? :-) Thanks in advance, GH -- powered by FreeBSD/Postfix/KMail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Device Busy
Dear Sir or Madam, I am trying to use my Epson Stylus Color 600 printer as a network printer running off my FreeBSD (version 5.1) server. The printer works fine, via the parallel port, on Windows 98. Why, when I move the cable to the FreeBSD server and execute a lptest > /dev/lpt0 do I only get a /dev/lpt0: Device busy. response. What do I have to do to make the device not busy? Gerry Isaacson [EMAIL PROTECTED] (952) 541-0051 cell: (612) 940-9164 http://www.tgico.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't open audio device /dev/dsp: Device busy ?
fstat | grep dsp Also, take a look here (if you haven't already): http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html - Original Message - From: "Rob Lahaye" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, September 14, 2003 4:56 PM Subject: Can't open audio device /dev/dsp: Device busy ? > > > Hi, > > How can I find out which app. keeps /dev/dsp busy? > > Without any other sound application running, I got this message when > starting mplayer or realaudio. Somehow the system got muddled up. > > After some random trial and error, I finally discovered that everything > came back to normal when I killed xscreensaver. > So for some reason xscreensaver kept /dev/dsp busy. > > Is there a command to find out directly which app. keeps /dev/dsp busy? > > Thanks, > Rob. > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't open audio device /dev/dsp: Device busy ?
Hi, How can I find out which app. keeps /dev/dsp busy? Without any other sound application running, I got this message when starting mplayer or realaudio. Somehow the system got muddled up. After some random trial and error, I finally discovered that everything came back to normal when I killed xscreensaver. So for some reason xscreensaver kept /dev/dsp busy. Is there a command to find out directly which app. keeps /dev/dsp busy? Thanks, Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Quantum DLT4000 on 4.5-R: "Device busy"
Hi,
> Greetings,
> (Apologies in advance if this is not the correct list for this question)
>
> I am attemping to get a new tape drive (Quantum DLT4000, external) working
> on my FreeBSD (4.5-R, i386) machine. The kernel detects the drive during
> boot:
>
> ahc0: port 0xdc00-0xdcff mem
> 0xe7003000-0xe7003fff irq 11 at device 13.0 on pci0
> aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs
> sa0 at ahc0 bus 0 target 4 lun 0
> sa0: Removable Sequential Access SCSI-2 device
> sa0: 10.000MB/s transfers (10.000MHz, offset 15)
>
> However, when trying to interact with the /dev/sa0 device via mt and tar
> commands, the device is reported to be busy:
>
> [EMAIL PROTECTED]:/dev $ mt status
> mt: /dev/nsa0: Device busy
> ('mt offline' fails with the same message, as well)
>
> I have tried resetting the drive, changing SCSI IDs, rebooting, reseating
> the tape cartridge, to no avail. The tape drive works under a
> Solaris/Sparc 8 machine, so I do not believe the drive or cable are at
> fault.
>
> I am unfamiliar with tape drives in general under BSD. Am I doing
> something wrong?
First, I presume you have waited for the tape to quite cycling after
it is first inserted. If not, then it actually is busy.
Second, we have seen this (or something that looks like it) with several
machines that have DAT (DDS) drives. Of about 65 supposedly identical
machines it happens on about 10 or 15 of them and we have not been able
to discover a reliable solution. Sometimes a reboot with power-cycle (eg
turn the power off and pull all power cords for a couple of minutes to
let everything drain) clears it up, but most often not.
So, if anyone has any good insight, I would also appreciate hearing
about it.
jerry
>
> -Luke
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Quantum DLT4000 on 4.5-R: "Device busy"
Luke Lussier wrote:
> Greetings,
>
> (Apologies in advance if this is not the correct list for this question)
>
> I am attemping to get a new tape drive (Quantum DLT4000, external) working
> on my FreeBSD (4.5-R, i386) machine. The kernel detects the drive during
> boot:
>
> ahc0: port 0xdc00-0xdcff mem
> 0xe7003000-0xe7003fff irq 11 at device 13.0 on pci0
> aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs
> sa0 at ahc0 bus 0 target 4 lun 0
> sa0: Removable Sequential Access SCSI-2 device
> sa0: 10.000MB/s transfers (10.000MHz, offset 15)
>
> However, when trying to interact with the /dev/sa0 device via mt and tar
> commands, the device is reported to be busy:
>
> [EMAIL PROTECTED]:/dev $ mt status
> mt: /dev/nsa0: Device busy
> ('mt offline' fails with the same message, as well)
>
> I have tried resetting the drive, changing SCSI IDs, rebooting, reseating
> the tape cartridge, to no avail. The tape drive works under a
> Solaris/Sparc 8 machine, so I do not believe the drive or cable are at
> fault.
>
> I am unfamiliar with tape drives in general under BSD. Am I doing
> something wrong?
>
> -Luke
>
Have you tried to interact with the device on "scsi-level" using
the camcontrol(8) program
-Riaan
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Quantum DLT4000 on 4.5-R: "Device busy"
Greetings,
(Apologies in advance if this is not the correct list for this question)
I am attemping to get a new tape drive (Quantum DLT4000, external) working
on my FreeBSD (4.5-R, i386) machine. The kernel detects the drive during
boot:
ahc0: port 0xdc00-0xdcff mem
0xe7003000-0xe7003fff irq 11 at device 13.0 on pci0
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs
sa0 at ahc0 bus 0 target 4 lun 0
sa0: Removable Sequential Access SCSI-2 device
sa0: 10.000MB/s transfers (10.000MHz, offset 15)
However, when trying to interact with the /dev/sa0 device via mt and tar
commands, the device is reported to be busy:
[EMAIL PROTECTED]:/dev $ mt status
mt: /dev/nsa0: Device busy
('mt offline' fails with the same message, as well)
I have tried resetting the drive, changing SCSI IDs, rebooting, reseating
the tape cartridge, to no avail. The tape drive works under a
Solaris/Sparc 8 machine, so I do not believe the drive or cable are at
fault.
I am unfamiliar with tape drives in general under BSD. Am I doing
something wrong?
-Luke
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: device busy
On Mon, Sep 01, 2003 at 10:39:59AM -0400, Monah Baki wrote: > I'm running windowmaker Try installing the sysutils/lsof port, and run lsof | grep dsp > > > On Mon, 1 Sep 2003 13:46:52 +, Alexander Farber wrote > > Do you maybe run KDE and arts which blocks /dev/dsp? > > > > On Mon, Sep 01, 2003 at 09:54:34AM -0400, Monah Baki wrote: > > > I'm using Freebsd 4.8 and mozilla 1.4. Whenever I go to google.com or yahoo.com > > > to > search for > > > something, I get /dev/dsp: Device busy. I can get to any url, but can't seem to > > > search for > > > anything (cnn.com, in the dialog box to getting my home town weather, will not > > > work). -- ___ "ONE TURPENTINE FOR THE MAN, COMING RIGHT UP!" - Mr. Nutty from "ONE GLASS OF TURPENTINE COMING RIGHT UP" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: device busy
I'm running windowmaker On Mon, 1 Sep 2003 13:46:52 +, Alexander Farber wrote > Do you maybe run KDE and arts which blocks /dev/dsp? > > On Mon, Sep 01, 2003 at 09:54:34AM -0400, Monah Baki wrote: > > I'm using Freebsd 4.8 and mozilla 1.4. Whenever I go to google.com or yahoo.com to search for > > something, I get /dev/dsp: Device busy. I can get to any url, but can't seem to > > search for > > anything (cnn.com, in the dialog box to getting my home town weather, will not > > work). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/dsp: device busy
Do you maybe run KDE and arts which blocks /dev/dsp? On Mon, Sep 01, 2003 at 09:54:34AM -0400, Monah Baki wrote: > I'm using Freebsd 4.8 and mozilla 1.4. Whenever I go to google.com or yahoo.com to > search for > something, I get /dev/dsp: Device busy. I can get to any url, but can't seem to > search for > anything (cnn.com, in the dialog box to getting my home town weather, will not work). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/dev/dsp: device busy
Hi all, I'm using Freebsd 4.8 and mozilla 1.4. Whenever I go to google.com or yahoo.com to search for something, I get /dev/dsp: Device busy. I can get to any url, but can't seem to search for anything (cnn.com, in the dialog box to getting my home town weather, will not work). Thank you. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/dev/lpt0: Device busy
FreeBSD 4.8 HP LaserJet 3100 multi-function printer plugged into the parallel port. Canon BJC 3000 plugged into a USB port. For more info, a portion of "dmesg" output is pasted below. I'm trying to set up FreeBSD for the first time and I am stuck at setting up my printer. When I type the command: #lptest > /dev/lpt0 I get the response: /dev/lpt0: Device busy. Don't know what to do. Thanks. Output of "dmesg": FreeBSD 4.8-RELEASE #0: Thu Apr 3 10:53:38 GMT 2003 [EMAIL PROTECTED] frequency 1193182 Hz CPU: AMD Athlon(tm) XP 1700+ (1468.47-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 AMD Features=0xc048 on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xe800-0xebff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 pci0: (vendor=0x1813, dev=0x4100) at 9.0 irq 11 pci0: (vendor=0x1813, dev=0x4100) at 9.1 irq 11 pci0: (vendor=0x1102, dev=0x0004) at 11.0 irq 5 pci0: (vendor=0x1102, dev=0x7003) at 11.1 pci0: (vendor=0x1102, dev=0x4001) at 11.2 irq 3 sis0: port 0xdc00-0xdcff mem 0xef105000- 0xef105fff irq 5 at device 15.0 on pci0 sis0: Ethernet address: 00:02:e3:24:9f:18 miibus0: on sis0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe00f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xe400-0xe41f irq 3 at device 17.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ulpt0: Canon product 0x1051, rev 1.10/1.00, addr 2, iclass 7/1 uhub0: device problem, disabling port 2 uhci1: port 0xe800-0xe81f irq 3 at device 17.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, r v 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xec00-0xec1f irq 3 at device 17.4 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered orm0: at iomem 0xc-0xcbfff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: HP GDI plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ad0: 78167MB [158816/16/63] at ata0-master UDMA100 ad1: 38172MB [77557/16/63] at ata0-slave UDMA100 acd0: CD-RW <24X10> at ata1-master PIO4 Mounting root from ufs:/dev/ad1s1a fd0c: hard error writing fsbn 0 (No status) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Printing : "lptcontrol : open : device busy" on IBM Proprinter II
I want to use my old IBM ProprinterII (BW 9 (or 24?) pin printer) on my FreeBSD, essentially to print long pages of program codes (gaining some ink for my un*x-badly supported Lexmark 2030 JetPrinter). I followed the handbook very carefully and properly (as always :) ) and at the dmesg , I get (I powered on my PC with the printer plugged) : ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/1 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 At first sight, everything seems normal. But lptcontrol -* -d /dev/lpt0 always returns a : lptcontrol: open: Device busy lptest isnt working either. Cables are OK (checked) Printer is OK (checked and renewed yesterday, after 5 years of no-use). What am I missing ? Matthieu Bonavita GPG Key : http://membres.lycos.fr/almacinnis/pubkey.asc Running on : FreeBSD 5.0-RELEASE-p7 i386 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: disklabel device busy
I'll answer my own question. The devices were mounted. They shouldn't be. -Jason On Wed, Dec 04, 2002 at 01:48:16PM -0500, Jason Morgan wrote: > I am attempting to set up a new system with vinum. I've never used > vinum before, but I found a good guide for what I want to do here > (Case 2): > > http://org.netbase.org/vinum-mirrored.html > > Anyway, I have come to the point where I have to label my disks and I > am getting the following: > > First try: > > # disklabel -e /dev/ad0s1e > disklabel: Device busy > > Second try (completely empty disk): > > # disklabel -e /dev/ad2s1f > disklabel: Device busy > > Then I tried 'disklabel -e -r' for each of these and still: Device busy. > > Could someone point me in the right direction? > > > Thanks, > -Jason > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
disklabel device busy
I am attempting to set up a new system with vinum. I've never used vinum before, but I found a good guide for what I want to do here (Case 2): http://org.netbase.org/vinum-mirrored.html Anyway, I have come to the point where I have to label my disks and I am getting the following: First try: # disklabel -e /dev/ad0s1e disklabel: Device busy Second try (completely empty disk): # disklabel -e /dev/ad2s1f disklabel: Device busy Then I tried 'disklabel -e -r' for each of these and still: Device busy. Could someone point me in the right direction? Thanks, -Jason To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: floppy device busy
At 09:19 AM 10.21.2002 -0700, Terry Cooper wrote: >Not sure, I used a script to create the floppy. Is there a way to tell? Can >I just unmount rfd0 (floppy drive) ? Or is that going to leave a file open >still? > >- Original Message - >From: "Jerry McAllister" <[EMAIL PROTECTED]> >To: "Terry Cooper" <[EMAIL PROTECTED]> >Cc: <[EMAIL PROTECTED]> >Sent: Monday, October 21, 2002 7:58 AM >Subject: Re: floppy device busy > > >> > >> > I was trying to create a bootable floppy from using a script I found >from >> > http://www.svbug.com/developer/documentation/handbook/handbook139.html >> > >> > and well it failed. Big newbie surprize. grr. Well now I get >this >> > error after I modified the script. >> > >> > fdformat: /dev/fd0: Device busy >> > Bad floppy, please use a newone >> >> Were you CDed to something on the floppy or did you have some file >> there open? >> >> jerry >> >> > >> > I rebooted my computer to fix it but there must be a simple command to >fix >> > this. >> > >> > Try cding to "/" and running #df to see if a floppy is mounted. If so, #umount the floppy using the floppy device shown in above df info... That will free up the device so you can rerun your script Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: floppy device busy
> > I was trying to create a bootable floppy from using a script I found from > http://www.svbug.com/developer/documentation/handbook/handbook139.html > > and well it failed. Big newbie surprize. grr. Well now I get this > error after I modified the script. > > fdformat: /dev/fd0: Device busy > Bad floppy, please use a newone Were you CDed to something on the floppy or did you have some file there open? jerry > > I rebooted my computer to fix it but there must be a simple command to fix > this. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: floppy device busy
> > Not sure, I used a script to create the floppy. Is there a way to tell? Can > I just unmount rfd0 (floppy drive) ? Or is that going to leave a file open > still? Well, if you have a file open or are CDed into a directory on the floppy, it won't let you umount it. It will tell you it is busy. jerry > > - Original Message - > From: "Jerry McAllister" <[EMAIL PROTECTED]> > To: "Terry Cooper" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Monday, October 21, 2002 7:58 AM > Subject: Re: floppy device busy > > > > > > > > I was trying to create a bootable floppy from using a script I found > from > > > http://www.svbug.com/developer/documentation/handbook/handbook139.html > > > > > > and well it failed. Big newbie surprize. grr. Well now I get > this > > > error after I modified the script. > > > > > > fdformat: /dev/fd0: Device busy > > > Bad floppy, please use a newone > > > > Were you CDed to something on the floppy or did you have some file > > there open? > > > > jerry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Printer (lpt0) Device Busy (Epson Stylus Color 740)
On Tue, 17 Sep 2002, Evan Dower wrote: > On the bright side, > though, it does work now (on both the parallel and USB ports), and I even > got my USB camera working... sort of. It starts out fine. It gets detected > and mounts fine. but when I umount it, the camera's display does not change > from "USB" to "REMOVE OK." Also, if I unplug it and then plug it in a second > time, it doesn't work. Any clues? Any idea where I should look? To get the "REMOVE OK", try "camcontrol eject da0" (assuming the camera is da0). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Printer (lpt0) Device Busy (Epson Stylus Color 740)
I'm sorry. I'm really sorry. The problem with my printer... was that it was out of ink. I'm very sorry. As it turns out, and Epson Stylus Color 740 will continue to print after the ink low LED turns on, but only for a limited time. After a while, it will simply stop accepting jobs, and your computer will report a communication error of some kind. I know, it's one of the first things I should have checked for, and I apologize. On the bright side, though, it does work now (on both the parallel and USB ports), and I even got my USB camera working... sort of. It starts out fine. It gets detected and mounts fine. but when I umount it, the camera's display does not change from "USB" to "REMOVE OK." Also, if I unplug it and then plug it in a second time, it doesn't work. Any clues? Any idea where I should look? Thanks again, Evan Dower >From: Dominic Marks <[EMAIL PROTECTED]> >To: Evan Dower <[EMAIL PROTECTED]> >CC: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED], >[EMAIL PROTECTED],[EMAIL PROTECTED], >[EMAIL PROTECTED] >Subject: Re: Printer (lpt0) Device Busy (Epson Stylus Color 740) >Date: Mon, 16 Sep 2002 10:16:03 +0100 >MIME-Version: 1.0 >Received: from mc3-f13.law16.hotmail.com ([65.54.236.148]) by >mc3-s19.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Mon, 16 >Sep 2002 02:16:52 -0700 >Received: from mx2.freebsd.org ([216.136.204.119]) by >mc3-f13.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Mon, 16 >Sep 2002 02:16:45 -0700 >Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18])by >mx2.freebsd.org (Postfix) with ESMTPid A502055C97; Mon, 16 Sep 2002 >02:15:44 -0700 (PDT)(envelope-from [EMAIL PROTECTED]) >Received: by hub.freebsd.org (Postfix, from userid 538)id A89BE37B412; Mon, >16 Sep 2002 02:15:30 -0700 (PDT) >Received: from localhost (localhost [127.0.0.1])by hub.freebsd.org >(Postfix) with SMTPid 8AB0B2E8024; Mon, 16 Sep 2002 02:15:30 -0700 (PDT) >Received: by hub.freebsd.org (bulk_mailer v1.12); Mon, 16 Sep 2002 02:15:30 >-0700 >Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])by >hub.freebsd.org (Postfix) with ESMTPid 0ECFD37B400; Mon, 16 Sep 2002 >02:15:16 -0700 (PDT) >Received: from host217-41-22-89.in-addr.btopenworld.com >(host217-41-22-89.in-addr.btopenworld.com [217.41.22.89])by mx1.FreeBSD.org >(Postfix) with ESMTPid 14F3043E3B; Mon, 16 Sep 2002 02:15:15 -0700 >(PDT)(envelope-from [EMAIL PROTECTED]) >Received: by host217-41-22-89.in-addr.btopenworld.com (Postfix, from userid >1001)id 7050A533; Mon, 16 Sep 2002 10:16:03 +0100 (BST) >Delivered-To: [EMAIL PROTECTED] >Message-ID: <20020916091603.GA429@gallium> >References: <[EMAIL PROTECTED]> >In-Reply-To: <[EMAIL PROTECTED]> >User-Agent: Mutt/1.5.1i >Sender: [EMAIL PROTECTED] >List-ID: >List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) >List-Help: <mailto:[EMAIL PROTECTED]?subject=help> (List Instructions) >List-Subscribe: ><mailto:[EMAIL PROTECTED]?subject=subscribe%20freebsd-stable> >List-Unsubscribe: ><mailto:[EMAIL PROTECTED]?subject=unsubscribe%20freebsd-stable> >X-Loop: FreeBSD.ORG >Precedence: bulk >Return-Path: [EMAIL PROTECTED] >X-OriginalArrivalTime: 16 Sep 2002 09:16:45.0228 (UTC) >FILETIME=[C70946C0:01C25D61] > >On Sun, Sep 15, 2002 at 10:12:56PM -0700, Evan Dower wrote: > > Truth is I do have a USB card and a USB camera. The camera gets detected > > and recognized as a USB mass storage device, but I haven't figured out >how > > to get it to mount (what with the scsi emulations and crap). Anyway, the > >I mount my FujiFilm FinePix A101 like this: > ># mkdir /camera ># chmod 777 /camera ># mount_msdos /dev/da0s1 /camera > >In my kernel configuration I have: > >device usb >device uhci >device ohci >device umass >device scbus >device da >device pass > > > hidden point here is that I would love to hear how you set it up for >USB. > > Please, please, please tell me all about it. > > Thanks, > > Evan Dower > > > > > > >From: Neal Nelson <[EMAIL PROTECTED]> > > >Reply-To: [EMAIL PROTECTED] > > >To: Evan Dower <[EMAIL PROTECTED]> > > >CC: [EMAIL PROTECTED], > > >[EMAIL PROTECTED],[EMAIL PROTECTED], > > >[EMAIL PROTECTED],[EMAIL PROTECTED] > > >Subject: Re: Printer (lpt0) Device Busy (Epson Stylus Color 740) > > >Date: Mon, 16 Sep 2002 15:12:44 +1000 > > >MIME-Version: 1.0 > > >Received: from mx2.freebsd.org ([216.136.204.119]) by > > >mc3-f37.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Sun, >15 > > >Sep 2002 22:08:07 -0700 > >
Re: Printer (lpt0) Device Busy (Epson Stylus Color 740)
I'm sorry. I'm really sorry. The problem with my printer... was that it was out of ink. I'm very sorry. As it turns out, and Epson Stylus Color 740 will continue to print after the ink low LED turns on, but only for a limited time. After a while, it will simply stop accepting jobs, and your computer will report a communication error of some kind. I know, it's one of the first things I should have checked for, and I apologize. On the bright side, though, it does work now (on both the parallel and USB ports), and I even got my USB camera working... sort of. It starts out fine. It gets detected and mounts fine. but when I umount it, the camera's display does not change from "USB" to "REMOVE OK." Also, if I unplug it and then plug it in a second time, it doesn't work. Any clues? Any idea where I should look? Thanks again, Evan Dower >From: Dominic Marks <[EMAIL PROTECTED]> >To: Evan Dower <[EMAIL PROTECTED]> >CC: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED], >[EMAIL PROTECTED],[EMAIL PROTECTED], >[EMAIL PROTECTED] >Subject: Re: Printer (lpt0) Device Busy (Epson Stylus Color 740) >Date: Mon, 16 Sep 2002 10:16:03 +0100 >MIME-Version: 1.0 >Received: from mc3-f13.law16.hotmail.com ([65.54.236.148]) by >mc3-s19.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Mon, 16 >Sep 2002 02:16:52 -0700 >Received: from mx2.freebsd.org ([216.136.204.119]) by >mc3-f13.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Mon, 16 >Sep 2002 02:16:45 -0700 >Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18])by >mx2.freebsd.org (Postfix) with ESMTPid A502055C97; Mon, 16 Sep 2002 >02:15:44 -0700 (PDT)(envelope-from [EMAIL PROTECTED]) >Received: by hub.freebsd.org (Postfix, from userid 538)id A89BE37B412; Mon, >16 Sep 2002 02:15:30 -0700 (PDT) >Received: from localhost (localhost [127.0.0.1])by hub.freebsd.org >(Postfix) with SMTPid 8AB0B2E8024; Mon, 16 Sep 2002 02:15:30 -0700 (PDT) >Received: by hub.freebsd.org (bulk_mailer v1.12); Mon, 16 Sep 2002 02:15:30 >-0700 >Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])by >hub.freebsd.org (Postfix) with ESMTPid 0ECFD37B400; Mon, 16 Sep 2002 >02:15:16 -0700 (PDT) >Received: from host217-41-22-89.in-addr.btopenworld.com >(host217-41-22-89.in-addr.btopenworld.com [217.41.22.89])by mx1.FreeBSD.org >(Postfix) with ESMTPid 14F3043E3B; Mon, 16 Sep 2002 02:15:15 -0700 >(PDT)(envelope-from [EMAIL PROTECTED]) >Received: by host217-41-22-89.in-addr.btopenworld.com (Postfix, from userid >1001)id 7050A533; Mon, 16 Sep 2002 10:16:03 +0100 (BST) >Delivered-To: [EMAIL PROTECTED] >Message-ID: <20020916091603.GA429@gallium> >References: <[EMAIL PROTECTED]> >In-Reply-To: <[EMAIL PROTECTED]> >User-Agent: Mutt/1.5.1i >Sender: [EMAIL PROTECTED] >List-ID: >List-Archive: <http://docs.freebsd.org/mail/> (Web Archive) >List-Help: <mailto:[EMAIL PROTECTED]?subject=help> (List Instructions) >List-Subscribe: ><mailto:[EMAIL PROTECTED]?subject=subscribe%20freebsd-stable> >List-Unsubscribe: ><mailto:[EMAIL PROTECTED]?subject=unsubscribe%20freebsd-stable> >X-Loop: FreeBSD.ORG >Precedence: bulk >Return-Path: [EMAIL PROTECTED] >X-OriginalArrivalTime: 16 Sep 2002 09:16:45.0228 (UTC) >FILETIME=[C70946C0:01C25D61] > >On Sun, Sep 15, 2002 at 10:12:56PM -0700, Evan Dower wrote: > > Truth is I do have a USB card and a USB camera. The camera gets detected > > and recognized as a USB mass storage device, but I haven't figured out >how > > to get it to mount (what with the scsi emulations and crap). Anyway, the > >I mount my FujiFilm FinePix A101 like this: > ># mkdir /camera ># chmod 777 /camera ># mount_msdos /dev/da0s1 /camera > >In my kernel configuration I have: > >device usb >device uhci >device ohci >device umass >device scbus >device da >device pass > > > hidden point here is that I would love to hear how you set it up for >USB. > > Please, please, please tell me all about it. > > Thanks, > > Evan Dower > > > > > > >From: Neal Nelson <[EMAIL PROTECTED]> > > >Reply-To: [EMAIL PROTECTED] > > >To: Evan Dower <[EMAIL PROTECTED]> > > >CC: [EMAIL PROTECTED], > > >[EMAIL PROTECTED],[EMAIL PROTECTED], > > >[EMAIL PROTECTED],[EMAIL PROTECTED] > > >Subject: Re: Printer (lpt0) Device Busy (Epson Stylus Color 740) > > >Date: Mon, 16 Sep 2002 15:12:44 +1000 > > >MIME-Version: 1.0 > > >Received: from mx2.freebsd.org ([216.136.204.119]) by > > >mc3-f37.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Sun, >15 > > >Sep 2002 22:08:07 -0700 > >
Re: /dev/dsp reports "device busy" but nothing using it
On Sat, 13 Jul 2002 03:36:36 -0400 "Andrew Martin" <[EMAIL PROTECTED]> wrote: > Hello, > > I was playing audio with mplayer and when it finished, mplayer closed as > usual, however when trying to play something else I now receive "device > busy" messages about /dev/dsp. I do _NOT_ have esd or any other sound > daemon running (checked ps ax), nor do I have any other app that plays > audio running. In addition, grep'ing fstat for the inode of /dev/dsp > gives no results. I get the error with any app, including just cat'ing > files to /dev/dsp. I don't see how /dev/dsp could possibly be still in > use. I have discovered I can play sounds using /dev/dsp0.1 .2 .3 for > now > (/dev/dsp0.0 still reports device busy until I reboot). I was getting this too until I applied the patch in PR kern/35004 from February 16. You can see it here: <http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/35004> I was hoping this would make it into 4.6 but apparently its still tagged as an open issue. It's worked for me (as I noted in the PR) fine for a few months on the RELENG_4_5 branch. -Scott -- Scott Lampert <[EMAIL PROTECTED]> "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, 1759 Public Key: http://www.lampert.org/lampert.key msg00242/pgp0.pgp Description: PGP signature
/dev/dsp reports "device busy" but nothing using it
Hello, I was playing audio with mplayer and when it finished, mplayer closed as usual, however when trying to play something else I now receive "device busy" messages about /dev/dsp. I do _NOT_ have esd or any other sound daemon running (checked ps ax), nor do I have any other app that plays audio running. In addition, grep'ing fstat for the inode of /dev/dsp gives no results. I get the error with any app, including just cat'ing files to /dev/dsp. I don't see how /dev/dsp could possibly be still in use. I have discovered I can play sounds using /dev/dsp0.1 .2 .3 for now (/dev/dsp0.0 still reports device busy until I reboot). I do NOT have KDE running or GDM or anything else that starts a soundserver.. uname output: FreeBSD whorism 4.6-STABLE FreeBSD 4.6-STABLE #0: Wed Jul 10 20:07:35 EDT 2002 I have pcm compiled into the kernel: pcm0: port 0x14e0-0x14ff irq 10 at device 13.0 on pci0 And this is a fairly recent source tree - from just about a week ago I believe. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
