problems with Logitech iFeel MouseMan mouce
Hello! I have problems with an usb Logitech iFeel MouseMan mouce. When I connect it, boot log looks like: === uhci0: port 0xe400-0xe41f irq 9 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered < long delay > ums0: Logitech product 0xc032, rev 1.00/1.01, addr 2, iclass 3/1 < long delay > device_probe_and_attach: ums0 attach returned 6 < long delay > ugen0: Logitech product 0xc032, rev 1.00/1.01, addr 2 < long delay > ugen0: setting configuration index 0 failed < long delay > device_probe_and_attach: ugen0 attach returned 6 uhub1: Texas Instruments TUSB2046 hub, class 9/0, rev 1.10/1.25, addr 3 uhub1: 4 ports with 4 removable, self powered === and FreeBSD can not use it: # usbdevs -dv Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub0 port 1 addr 2: low speed, power 500 mA, unconfigured, product 0xc032(0xc032), Logitech(0x046d), rev 1.01 port 2 addr 3: self powered, config 1, TUSB2046 hub(0x2046), Texas Instruments(0x0451), rev 1.25 How can I use my mouse? # uname -r 4.7-STABLE # strings -n 3 /kernel | sed -n 's/^___//p' | g -i '\(usb\|ums\)' device uhci# UHCI PCI->USB interface device ohci# OHCI PCI->USB interface device usb # USB Bus (required) device ums # Mouse To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.4 jail and udp
Poul-Henning Kamp wrote: > > > RTFM. thank you very much! === === # man jail | g socket Formatting page, please wait...Done. jail.socket_unixiproute_only UNIX domain sockets, IPv4 addresses, and routing sockets. To enable # man jail | g raw Exit 1 # === === can you tell me please what poor user must read to know about magic words "raw socket"? ;) sorry... > > UDP works fine. ICMP and other raw socket magic doesn't. > ... and shouldn't? Will it work in future releases, or it is better to forget about icmp for me? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
4.4 jail and udp
Hi! Looks like jailed processes can't use udp or icmp, but can use tcp: # ping www.freebsd.org ping: socket: Operation not permitted # telnet www.freebsd.org 80 Trying 216.136.204.21... Connected to freefall.freebsd.org. Escape character is '^]'. ^] telnet> q Connection closed. # options IPFIREWALL is enabled, net.inet.ip.fw.enable is 0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
FreeBSD-4.2 and svr4
Hello! Can someone tell me how to install sol7 under svr4 please? I tried to install it this way: 1) added to kernel config: options KTRACE #kernel tracing options COMPAT_SVR4 # build emulator statically pseudo-device streams # STREAMS network driver (required for svr4). 2) installed http://slash.dotat.org/~newton/freebsd-svr4/compat_sol26.tar.gz into /usr/compat/svr4 3) cd /compat/svr4/dev sh ./SVR4_MAKEDEV all 4) mounted colaris 7 cd-rom, deleted /usr/compat/svr4/usr and moved /cdrom/Solaris_2.7/Tools/Boot/usr into /usr/compat/svr4/usr 5) help@please:/usr/compat/svr4# brandelf -t SVR4 usr/bin/ls help@please:/usr/compat/svr4# ./usr/bin/ls ELF interpreter /usr/lib/ld.so.1 not found Abort Exit 134 what did I miss and how can make it work? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
mounting filesystem multiple times
Hi! I want to mount one filesystem rw once and ro multiple times (lets say, 500 times). Can I do it? And if yes, will it slow FreeBSD down and will it use additional memory, cpu and other system resources in this case? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
4.0 and compaq smart array
Hi! I'm trying to install 4.0-curr on compaq (proliant 6500) with only 1 disk controller - Smart Array 3200. But I found that kernel from kern.flp does not have drivers for this controller. So, on another 4.0 machine I built kernel (took GENERIC, added device ida device id configured and compiled it), gzipped it and put on kern.flp instead of original kernel.gz. Then, I mounted mfsroot on /mnt, "cd" to /mnt/dev and said "./MAKEDEV ida0", and put new mfsroot on mfsroot.flp. Then I booted from those disks and installed FreeBSD. (It found disk ida0). After installation I put modified GENERIC kernel on /mnt and rebooted. Here is the log of boot: (some kernel checks skipped) FreeBSD 4.0-2224-CURRENT #0: Fri Feb 25 19:20:37 MSK 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC ... ida0: port 0x4000-0x40ff mem 0xc6ff-0xc6ff00ff irq 11 at device 0.0 on pci5 ida0: drives=1 firm_rev=4.16 id0: on ida0 id0: 69459MB (142253280 sectors), blocksize=512 ... ata0-slave: identify retries exceeded acd0: CDROM at ata0-master using PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ida0s1a no such device 'ida' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Mounting root from ufs:id0s1a swapon: adding /dev/ida0s1b as swap device Automatic reboot in progress... /dev/ida0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ida0s1a: clean, 39674 free (570 frags, 4888 blocks, 0.9% fragmentation) /dev/ida0s1e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ida0s1e: clean, 2533812 free (23132 frags, 313835 blocks, 0.8% fragmentation) /dev/ida0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ida0s1f: clean, 9886 free (14 frags, 1234 blocks, 0.1% fragmentation) /dev/ida0s1g: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ida0s1g: clean, 20325785 free (281 frags, 2540688 blocks, 0.0% fragmentation) /dev/ida0s1h: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ida0s1h: clean, 44544505 free (9 frags, 5568062 blocks, 0.0% fragmentation) mount: /dev/ida0s1a on /: specified device does not match mounted device Mounting /etc/fstab filesystems failed, startup aborted Enter full pathname of shell or RETURN for /bin/sh: == What did I do wrong and how can I install (if can) FreeBSD on my machine? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
