Re: USB Logitech QuickCam Ultra Vision
El día Friday, March 02, 2012 a las 05:48:11AM +0100, Daniel C. Dowse escribió: > Hi, > > usbconfig -d ugenX.Y do_request 0x22 0x01 0x100 0x86 0x03 0x80 0xBB 0x00 > usbconfig -d ugenX.Y reset > usbconfig -d ugenX.Y do_request 0x22 0x01 0x100 0x86 0x03 0x80 0xBB 0x00 > > and then restart webcamd. > > may help, it worked on my Logitech Business Pro Cam > > cheers FWHIW, such quirks are also shown in http://wiki.freebsd.org/WebcamCompat and once your webcam is working fine it could show up there too; HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: USB Logitech QuickCam Ultra Vision
On Fri, 02 Mar 2012 10:26:07 +1000, Da Rock wrote: >On 03/02/12 06:25, sean wrote: >> Hello All, >> >> I am unable to get the built in mic of a Logitech QuickCam Ultra >> Vision to capture sound. I have been testing it using Skype. >> >> -lsusb shows the logitech device. >> -Device "sound" and "snd_ich" is complied into my custom kernel. >> -running "FreeBSD 9.0-STABLE FreeBSD 9.0-STABLE #0: Mon Feb 20 >> 04:40:40 EST 2012 amd64" >> -The Skype test call produces sound and can capture video through the >> camera. >> -mixer show the mic at 97:97 >Which mixer? Check `ls /dev/mixer*`, and use `mixer -f >/dev/mixer> -webcamd_enabled="YES" entered into /etc/rc.conf >> >> Would anyone have some ideas on what check? > >___ >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" Hi, usbconfig -d ugenX.Y do_request 0x22 0x01 0x100 0x86 0x03 0x80 0xBB 0x00 usbconfig -d ugenX.Y reset usbconfig -d ugenX.Y do_request 0x22 0x01 0x100 0x86 0x03 0x80 0xBB 0x00 and then restart webcamd. may help, it worked on my Logitech Business Pro Cam cheers -- Daniel Dowse \\|// (o o) -ooO-(_)-Ooo- - "Jim, Wahnsinn dient keinem Zweck.- - Er kennt keine Vernunft, aber er kann ein Ziel haben!"- - (Spock) - - - []-/""| DISLIKE ! - - []-\ _| - - U www.fsf.org/facebook - - - () ascii ribbon campaign - against html mail - - /\- against microsoft attachments - - - - Please reply below quoted text section- - ___ 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"
default value for DESTDIR
During the new installer for 9.0, what is the default value for DESTDIR? The reason I'm asking is I setup my partitions manually in the shell provided for doing this, and I want to know where I need to leave them mounted before I exit the shell to continue installation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: USB Logitech QuickCam Ultra Vision
On 03/02/12 06:25, sean wrote: Hello All, I am unable to get the built in mic of a Logitech QuickCam Ultra Vision to capture sound. I have been testing it using Skype. -lsusb shows the logitech device. -Device "sound" and "snd_ich" is complied into my custom kernel. -running "FreeBSD 9.0-STABLE FreeBSD 9.0-STABLE #0: Mon Feb 20 04:40:40 EST 2012 amd64" -The Skype test call produces sound and can capture video through the camera. -mixer show the mic at 97:97 Which mixer? Check `ls /dev/mixer*`, and use `mixer -f /dev/mixer -webcamd_enabled="YES" entered into /etc/rc.conf Would anyone have some ideas on what check? ___ 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: THe number of cdrom in /dev
On Thu, 1 Mar 2012 15:52:46 -0800 (PST), Me Me wrote: > My system's been down for a while - anyway I wanted to add > data from a cd, but the prompt reads "can't have more than > 32 cd devices or drives." Which program does show this message? Please explain what you've done in order to get that text. How many _actual_ CD drives does your system have? Just to make sure this isn't the problem... :-) > I couldn't figure it out tried alot. So now I'd like to take > some of the devices out of the directory. However, I "rm" and > they mostly return. FreeBSD's current /dev directory is a dynamical thing. It gets populated automatically under the control of devfs (at boot time) and devd (at run time) which control several actions that can be taken. > I'm careful to keep those I see in the ref 4.2 book but do > I have to change permissions or file types or should I use > "mv" to another directory so I don't lose them permenetly? Which OS version are you currently using? > anyway if you've got an advisory or a fix for this and your > not to annoyed please send it. Just provide a bit more information so your problem can be diagnosed. At the moment, I'm just guessing. :-) -- 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"
THe number of cdrom in /dev
hi, I'm sorry to bother you. I know you probably got something better to do. So I'll just take a minute. My system's been down for a while - anyway I wanted to add data from a cd, but the prompt reads "can't have more than 32 cd devices or drives." I couldn't figure it out tried alot. So now I'd like to take some of the devices out of the directory. However, I "rm" and they mostly return. I'm careful to keep those I see in the ref 4.2 book but do I have to change permissions or file types or should I use "mv" to another directory so I don't lose them permenetly? Cause I need a job and all I want to do is -- Can you belive this! practice SQL admin and database --oh joy! anyway if you've got an advisory or a fix for this and your not to annoyed please send it. You guys do a great job I wouldn't miss this for nut'in. Thanks and Happy New year. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
USB Logitech QuickCam Ultra Vision
Hello All, I am unable to get the built in mic of a Logitech QuickCam Ultra Vision to capture sound. I have been testing it using Skype. -lsusb shows the logitech device. -Device "sound" and "snd_ich" is complied into my custom kernel. -running "FreeBSD 9.0-STABLE FreeBSD 9.0-STABLE #0: Mon Feb 20 04:40:40 EST 2012 amd64" -The Skype test call produces sound and can capture video through the camera. -mixer show the mic at 97:97 -webcamd_enabled="YES" entered into /etc/rc.conf Would anyone have some ideas on what check? Thanks in advance to all replies, Sean ___ 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"
"SCSI sense: UNIT ATTENTION"
Hi, I have: 9.0-RELEASE and this problem: ugen4.8: at usbus4 umass2: on usbus4 umass2: 8070i (ATAPI) over Bulk-Only; quirks = 0x0100 umass2:4:2:-1: Attached to scbus4 (probe0:umass-sim2:2:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim2:2:0:0): CAM status: SCSI Status Error (probe0:umass-sim2:2:0:0): SCSI status: Check Condition (probe0:umass-sim2:2:0:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) cd1 at umass-sim2 bus 2 scbus4 target 0 lun 0 cd1: <_NEC DVD_RW ND-3500AG 2.07> Removable CD-ROM SCSI-0 device cd1: 40.000MB/s transfers cd1: cd present [2295104 x 2048 byte records] (cd1:umass-sim2:2:0:0): READ(10). CDB: 28 0 0 23 5 3f 0 0 1 0 (cd1:umass-sim2:2:0:0): CAM status: SCSI Status Error (cd1:umass-sim2:2:0:0): SCSI status: Check Condition (cd1:umass-sim2:2:0:0): SCSI sense: ILLEGAL REQUEST asc:64,0 (Illegal mode for t his track) (cd1:umass-sim2:2:0:0): Info: 0x23053f (cd1:umass-sim2:2:0:0): cddone: got error 0x6 back The DVDRW don't work correctly, ant idea for solvent this problem ? 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: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
In the "new" way of booting... you need to have the cd because the own cd is the root filesystem... and in fact is live filesystem too so unless you're booting from mfsroot... I assume you should have that line in /etc/fstab inside the iso image but if you're using mfsroot... I really even am not creating etc dir inside the iso image... because it's not needed and in previous releases and iso images when always booted from mfsroot (and where not livefs cds and so) it wasn't necessary... On Thu, 01 Mar 2012 12:43:58 +, Karl Pielorz wrote: --On 01 March 2012 11:53 +0100 ego...@ramattack.net wrote: So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! For what it's worth - I've resolved the issue I had (which was basically the system booted, but failed trying to re-mount root as RW, and hence wouldn't go into the installer). The fix I did was to change the '/etc/fstab' on the Netboot server (i.e. the copy of FreeBSD that you're booting). It contains: " /dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 " Just commenting out that line, i.e. " #/dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 " Means the boot now completes, and I get offered the "Install / Shell / Live CD" prompt, instead of an error about not being able to remount root. I've yet to complete an install this way (so far we're just using a script to extract the new 9.x style '.txz' files). But that little change does let us netboot correctly now, enough for what we need. -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Running OS tftp vs. pxeboot tftp
Hi All, Are there significant differences in the implementation between the tftp client in FreeBSD 8.2-RELEASE and the client implementation in pxeboot.bs? I ask because I have encountered a scenario where pxeboot.bs is tftp'ing boot files from a PXE server and fails in random spots while attempting to download boot files to start a 8.2-RELEASE install. When we run the same sequence of tftp gets in a running 8.2-RELEASE instance continuously, we never received a single failure in a solid hour of attempts. -- Take care Rick Miller ___ 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: VBox network boot
On 03/01/12 08:31, Andrei Brezan wrote: On 29/02/2012 01:08, Da Rock wrote: On 02/29/12 03:04, Carl Johnson wrote: Warren Block writes: On Tue, 28 Feb 2012, Da Rock wrote: I'm starting to believe this dog won't hunt (in fact is dead, bloated, and full of worms...); but has anyone got a solution for network booting in VBox on FBSD host? To PXE-boot a VM guest, set networking to to Bridged and use the PCnet-PCI II (Am79C970A) adapter type. If the host is FreeBSD, the vboxnet kernel module has to be loaded. Please emphasize that the PCnet-PCI II card emulation is necessary. I was trying the Intel emulation and making no progress. I then noticed your page and tried the PCnet-PCI II card and it started working. I would guess that means their Intel card emulation is incomplete. I took it for granted the bridge part (I usually use it anyway), but I would never have guessed the PCnet card in a blue fit! There was even a PR on virtualbox for the issue of the lack of PXE with Oracle basically saying "too bad, so sad...". Apparently PXE licensing didn't allow them to distribute it directly, but offer an extension pack (which doesn't work on FBSD) instead. Ergo my conclusion. Apparently (based on this thread) it only affects intel cards though... Where is your page Warren, and why didn't it show up in my searches? ;) I'll follow it from here on out I think... Thanks guys... saved me a lot more fussing! ___ 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" Hi all, You can also look at https://www.virtualbox.org/wiki/Downloads and https://www.virtualbox.org/manual/ch01.html#intro-installing for info related to the extension pack where you can find the PXE boot ROM for the Intel E1000 cards, unfortunately it's PUEL, virtualbox on FBSD is OSE. My worst case scenario was with a custom linux kernel on the guest that didn't had drivers for Amd cards, I had to do something like this: NIC 1: MAC: 0800276F42C6, Attachment: Bridged Interface 'bridge0', Cable connected: on, Trace: off (file: none), Type: Am79C970A, Reported speed: 0 Mbps, Boot priority: 0 NIC 2: MAC: 0800276F42C6, Attachment: Bridged Interface 'bridge0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0 The extensions don't work with FBSD. Period. End of story. Oracle is _very_ clear about that- they won't support FBSD at all, and show no mercy to those who complain. It is possible to write your own though... BTW, is anyone aware if the patches are still required? I'm getting " is not in my arp table". I'm using booting techniques as describe by Warren (gpxelinux.0, menu, and chain loading), and I have pxeboot sent over using tftp and boot off nfs. And that is why the error shows up - the address is the nfs server. I'm not sure the patches help this though... This works (mostly) using real hardware. It snags on the next stage. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
--On 01 March 2012 11:53 +0100 ego...@ramattack.net wrote: So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! For what it's worth - I've resolved the issue I had (which was basically the system booted, but failed trying to re-mount root as RW, and hence wouldn't go into the installer). The fix I did was to change the '/etc/fstab' on the Netboot server (i.e. the copy of FreeBSD that you're booting). It contains: " /dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 " Just commenting out that line, i.e. " #/dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 " Means the boot now completes, and I get offered the "Install / Shell / Live CD" prompt, instead of an error about not being able to remount root. I've yet to complete an install this way (so far we're just using a script to extract the new 9.x style '.txz' files). But that little change does let us netboot correctly now, enough for what we need. -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
Take a look at freebsd-hackers mailing list... I have suggested some change in some Makefile and sh script in order to unless at this moment to be able to have an unattended system built with sysinstall (the idea I think it was to maintain sysinstall in 9.0 unless) and using you're install.cfg At freebsd-hackers seems that people is pretty busy and can't look at this in order for committing or unless saying something about it... perhaps they're working on another thing or so, or don't know I assume they can't check this now... but like changes are not significant... I am going to do with the changes suggested and have tested and release builts fine and you can use Jumpstart without issues.. this way... So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! El Jue, 1 de Marzo de 2012, 11:24 am, Karl Pielorz escribió: > Hi, > > > I've got a 9.0-R amd64 system I'm trying to netboot / pxeboot from the > network, to install other machines (and do fixups etc.) > > I set this up as we setup previous versions here - but setting up a tftp > server, and nfs server - and 'dumping' the contents of the install CD to a > directory on the dhcp server, which is exported via nfs (it's exported > as read/write). > > The system kind of boots, but falls over with: > > > " > Interface em0 IP-Address 192.168.0.47 Broadcast 192.168.0.255 > Entropy harvesting: interrupts ethernet point_to_pick kickstart. > Starting file system checks: > mount_nfs: no : nfs-name > Mounting root filesystem rw failed, startup aborted > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > Mar 1 118:10 init: /bin/sh on /etc/rc terminated abnormally, going to > single user mode Enter full pathname of shell or RETURN for /bin/sh: > " > > > It looks like it's failing to 'remount' / promote the root file system as > read/write (It's definitely exported as read/write - I've tested it by > mounting it on another machine). If you start a shell at this point and > run mount, you get: > > " > 192.168.0.37:/usr2/netboot/os/9.0-amd64 on / (nfs, read-only) > devfs on /dev (devfs, local, multilabel) " > > > Is there something I have to set (e.g. in '/etc/rc.conf') in order to fix > this? > > Previous systems setup this way would always boot through to the > sysinstall menu. > > > Thanks, > > > -Karl > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscr...@freebsd.org" > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
Hi, I've got a 9.0-R amd64 system I'm trying to netboot / pxeboot from the network, to install other machines (and do fixups etc.) I set this up as we setup previous versions here - but setting up a tftp server, and nfs server - and 'dumping' the contents of the install CD to a directory on the dhcp server, which is exported via nfs (it's exported as read/write). The system kind of boots, but falls over with: " Interface em0 IP-Address 192.168.0.47 Broadcast 192.168.0.255 Entropy harvesting: interrupts ethernet point_to_pick kickstart. Starting file system checks: mount_nfs: no : nfs-name Mounting root filesystem rw failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Mar 1 118:10 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: " It looks like it's failing to 'remount' / promote the root file system as read/write (It's definitely exported as read/write - I've tested it by mounting it on another machine). If you start a shell at this point and run mount, you get: " 192.168.0.37:/usr2/netboot/os/9.0-amd64 on / (nfs, read-only) devfs on /dev (devfs, local, multilabel) " Is there something I have to set (e.g. in '/etc/rc.conf') in order to fix this? Previous systems setup this way would always boot through to the sysinstall menu. Thanks, -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
