fla.ko
I'm wondering what needs to be done to make the "fla" device into a kernel module. I made modules/fla/Makefile, but I am not sure what else needs to be done. It looks like you can't kldunload it after you kldload it... .PATH: ${.CURDIR}/../../contrib/dev/fla KMOD= fla SRCS= fla.c \ device_if.h bus_if.h OBJS+= msysosak.o msysosak.o: uudecode < ${.CURDIR}/../../contrib/dev/fla/i386/msysosak.o.uu .include __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: LG 5350 cell phone
Should this get a new vendor entry in usbdevs? --- Josef Karthauser <[EMAIL PROTECTED]> wrote: > On Wed, Jun 11, 2003 at 01:05:00PM -0500, Sean Welch wrote: > > I have this phone myself. I have two adapters for it -- one is > > a serial cable the other a "true" (as in no serial to usb > > conversion box in the middle) usb cable. > > > > The phone works great under FreeBSD on the serial cable (normal > > Hayes modem type at commands work fine), but no version of > > FreeBSD has worked with the usb cable so far. I tried 4.8, > > 5.0-RELEASE, and a few versions of 5.x-CURRENT. The phone is > > quite usable from my iBook so the cable isn't the issue (the > > iBook reports it as a Qualcomm -- which is what the sticker > > says too). I see the message you do, but when I try to use > > umodem with it the phone continuously "reboots" itself until > > detached. > > > > I tried something along the lines of what you did to usbdevs > > a while back but didn't get any improvement. > > > > The connection is appreciably faster over the usb port with > > the "true" cable when compared to the serial cable; it would > > be very nice to use it this way on FreeBSD... > > > >Sean > > Maybe the phone doesn't identify itself as a usb modem class, instead > relying on a vendor driver. > > An easy project for someone would be to write a general usb querying > tool for displaying the classes, etc that a usb device supports. > I've got code kicking around, mostly from Nick Hibma, but I never got > around to finishing it off. > > Joe > -- > Josef Karthauser ([EMAIL PROTECTED]) http://www.josef-k.net/ > FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ > Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ > An eclectic mix of fact and theory. = __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
VIA C3
Anyone have a VIA C3? I'm running FreeBSD current on one and I don't see any gcc flags for the VIA C3. I think it has MMX and 3dnow, but it does not have SSE? I was wondering what gcc flags other VIA C3 users are using on FreeBSD. I am not sure what optimizations are safe for this cpu running FreeBSD. Maybe it would be useful to have a CPUTYPE entry for the VIA C3? CPU: VIA/IDT Unknown (998.70-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x689 Stepping = 9 Features=0x803035 Regards, David Yeske __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
LG 5350 cell phone
I have a LG 5350, and I want it to work in FreeBSD. I think it is a Qualcomm adaptor, but I wanted to see if anyone else has this phone or similar hardware. I think this needs a new vendor in usbdevs. I'm not sure if 0x1004 is Qualcomm or LG or VLSI... RCS file: /home/ncvs/src/sys/dev/usb/usbdevs,v retrieving revision 1.125 diff -u -r1.125 usbdevs --- usbdevs 21 May 2003 00:22:06 - 1.125 +++ usbdevs 11 Jun 2003 04:50:39 - @@ -340,6 +340,7 @@ vendor AGATE 0x0c08 Agate Technologies vendor DMI 0x0c0b DMI vendor LUWEN 0x0c76 Luwen +vendor QUALCOMM0x1004 Qualcomm vendor MOTOROLA0x1063 Motorola vendor PLX 0x10b5 PLX vendor ASANTE 0x10bd Asante @@ -727,6 +728,9 @@ /* JRC products */ product JRC AH_J3001V_J3002V 0x0001 AirH\" PHONE AH-J3001V/J3002V + +/* Qualcomm products */ +product QUALCOMM MSM 0x6000 MSM /* Kawasaki products */ product KLSI DUH3E10BT 0x0008 USB ethernet controller engine here is more output ugen0: Qualcomm, Incorporated Qualcomm CDMA Technologies MSM, rev 1.01/0.00, addr 6 port 4 addr 6: full speed, power 100 mA, config 1, Qualcomm CDMA Technologies MSM(0x6000), Qualcomm, Incorporated(0x1004), rev 0.00 __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sendmail starts before rpc.statd and rpc.lockd
This is when sendmail is ran from virecover. Is this because sendmail is taking redirection, and it needs to flock() for that? I think a solution could be to make virecover called later on. Why are rpc.lockd and rpc.statd not started directly after rpcbind? Here is some more output. Recovering vi editor sessions:Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: SYSERR(root): cannot flock(./dfh5913dfn000292, fd=3, type=2, omode=40002, euid=25): Operation not supported collect: Cannot write ./dfh5913dfn000292 (bfcommit, uid=25, gid=25): Operation not supported cannot flock(./tfh5913dfn000292, fd=5, type=6, omode=40001, euid=25): Operation not supported cannot flock(./tfh5913dfn000292, fd=5, type=6, omode=40001, euid=25): Operation not supported Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: SYSERR(root): collect: Cannot write ./dfh5913dfn000292 (bfcommit, uid=25, gid=25): Operation not supported Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: SYSERR(root): cannot flock(./tfh5913dfn000292, fd=5, type=6, omode=40001, euid=25): Operation not supported Jun 8 21:03:39 photon sendmail[292]: h5913dfn000292: queueup: cannot lock ./tfh5913dfn000292: Operation not supported Here is what Control-T does load: 0.20 cmd: sendmail 292 [pause] 0.02u 0.04s 0% 2016k --- Robert Watson <[EMAIL PROTECTED]> wrote: > On Sat, 7 Jun 2003, David Yeske wrote: > > > Jun 8 00:52:33 photon sendmail[293]: h584pRfm000293: SYSERR(root): cannot > > flock(./tfh584pRfm000293, fd=5, type=6, omode=40001, euid=25^C. > > NFS access cache time=2 > > Starting statd. > > Starting lockd. > > > > It looks like sendmail starts before rpc.lockd and rpc.statd? This will > > cause diskless clients to hang? This is a nfs server and diskless > > client running 5.1-RELEASE. I'm running rpc.lockd and rpc.statd on the > > server and the client. Should rpc.lockd and rpc.statd be started before > > sendmail starts? > > Hmm. It shouldn't cause diskless clients to hang, or at least, doesn't > for me. The cause of the error message, however, is exactly as you > surmise -- befpre rpc.lockd, calls to flock() on the NFS file system will > return an error. Is the hang you're seeing immediately after the > "Starting lockd"? If you hit Ctrl-T, does it tell you anything useful? > Note that unless you're running 5.x pretty close to the release, pressing > Ctrl-T while a process is attempting to grab an NFS-backed file lock will > result in a slipped lock and many nasty failure modes. I disabled signal > delivery to processes while sleeping on an NFS lock as a workaround until > out rpc.lockd addresses the "process aborts the lock request" race, which > isn't handled right now. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > [EMAIL PROTECTED] Network Associates Laboratories > > __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sendmail starts before rpc.statd and rpc.lockd
Jun 8 00:52:33 photon sendmail[293]: h584pRfm000293: SYSERR(root): cannot flock(./tfh584pRfm000293, fd=5, type=6, omode=40001, euid=25^C. NFS access cache time=2 Starting statd. Starting lockd. I should clarify that /etc/rc.d/virecover is calling sendmail. Does virecover need to be called this early on? Regards, David Yeske __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sendmail starts before rpc.statd and rpc.lockd
Jun 8 00:52:33 photon sendmail[293]: h584pRfm000293: SYSERR(root): cannot flock(./tfh584pRfm000293, fd=5, type=6, omode=40001, euid=25^C. NFS access cache time=2 Starting statd. Starting lockd. It looks like sendmail starts before rpc.lockd and rpc.statd? This will cause diskless clients to hang? This is a nfs server and diskless client running 5.1-RELEASE. I'm running rpc.lockd and rpc.statd on the server and the client. Should rpc.lockd and rpc.statd be started before sendmail starts? Regards, David Yeske __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
imgact_gzip.c
imgact_gzip.c seems to be pretty stale. Has anyone considered fixing this? If this were fixed then kldload() / linker_load_module() could deal with a gzipped .ko file, and gzipped elf executables would work also? Regards, David Yeske __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BOOTP_NFSV3
I have a suggestion to deprecate the BOOTP_NFSV3 option, and I wanted to get some feedback. If NFS_ROOT and BOOTP_NFSV3 are defined, then it is a noop in sys/i386/i386/locore.s? If NFS_ROOT is defined and BOOTP_NFSV3 is undefined then it copies in a nfs_diskless structure in sys/i386/i386/locore.s? Is this still needed? If BOOTP_NFSV3 is defined in sys/nfsclient/bootp_subr.c, then it will attempt a nfsv3 mount and then fall back to a nfsv2 mount. Should that eventually be the default behavior? Regards, David Yeske __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
swapping over nfs might be broken
I've recently set up a diskless client and I noticed something. subnet mask 255.255.255.0 router 192.168.1.2 rootfs 192.168.1.100:/export/photon.freebsd/root swapfs 192.168.1.100:/export/photon.freebsd hostname photon Adjusted interface xl0 md_lookup_swap: Swap size is 131072 KB Mounting root from nfs:nfs:/export/photon.freebsd/root setrootbyname failed NFS ROOT: 192.168.1.100:/export/photon.freebsd/root NFS SWAP: 192.168.1.100:/export/photon.freebsd $ swapinfo Device 1K-blocks UsedAvail Capacity Type Everything looks normal except for swapinfo. It looks like nfs swapping is broken? Has anyone seen this? I have tried this with md.ko as a module or compiled into the kernel with the same results. I'm also using these flags in my kernel. options BOOTP options BOOTP_NFSROOT options BOOTP_NFSV3 options BOOTP_COMPAT My nfs server and diskless client are both running current from around may 25th. I'm also running rpc.lockd and rpc.statd on the nfs server. I also tried setting option-129, but that did not help. Why is option-129 limited to 4 bytes? I have also seen that "setrootbyname failed" message for at least a year. Should that message be removed or changed to something more useful? Regards, David Yeske __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysinstall and swap
I just tried to upgrade a machine with current, and sysinstall doesn't seem to identify swap anymore. Sometimes I want warnings, but I don't want swap. I made a quick patch to add a no swap option. Maybe some warnings should be wrapped with "if (msgYesNo())" to give the user more choice? http://pigseye.kennesaw.edu/~dyeske/freebsd/patch-swap Regards, David Yeske __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sound debugging
So right now there is no clean way to debug sound in FreeBSD. I modified my system running current so that I now have a PCM_DEBUG option. I set up oid's in the same way that many usb drivers do with DPRINTF / DPRINTFN. So I now have hw.snd.drivername.debug oid's. Is the method used for usb debugging the "best way". I am referring to the usage of USB_DEBUG which creates opt_usb.h. When USB_DEBUG is defined than the DPRINTF / DPRINTFN macros become defined with some sysctl's. If debugging is not defined do the DPRINTF / DPRINTFN lines go into the drivers once compiled and slow it down or bloat it? Regards, David Yeske __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
fatal: ssh_msg_send: write
Anyone else having issues with sshd on current? Dec 15 23:23:24 stuff sshd[843]: fatal: ssh_msg_send: write debug1: next auth method to try is keyboard-interactive Connection closed by 192.168.1.66 debug1: Calling cleanup 0x804bed0(0x0) __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs -rbranch:date + val-tags
I am still looking into the -j flag and (r)tag. This patch was done quickly, and I am still trying to see what it breaks. I realized some of the issues I had were also broken with an unpatched cvs. So I might have broken something that is already broken. I am looking through diff -rv1_11_2 -rHEAD in the FreeBSD repository and diff -rCVS1_11_2 -rHEAD in the NetBSD repository and comparing that with -rHEAD cvs/ccvs from the cvshome repository. I don't know what the CVS people think of my patch, but I based it off a patch on their website that they have had for over 4 years. http://www.cvshome.org/cyclic/cvs/dev-branch.html I would really appreciate it if anyone would give me feedback on what they feel is "broken" about cvs. --- Archie Cobbs <[EMAIL PROTECTED]> wrote: > David Yeske wrote: > > I am working on getting cvs more usable so I don't have to worry about > > val-tags when I have read only media, and so I can do stuff like this. > > > > cvs update -rRELENG_4:2002/10/01 > > > > cvs diff -rRELENG_4:2002/09/01 -rRELENG_4:2002/09/30 > > > > I would appreciate any testing or feedback. I have tested this some, > > but it probably has bugs. > > Awesome! I've wanted to be able to do tags like '-rRELENG_4:2002/09/01' > for years.. > > Haven't tested your changes but the patch looks reasonable to me. > > ISTR that the '-j' option allows some combinations of branch + date. > Are you aware of that? Does anything need to be rectified between > the '-j' stuff and your changes? Also, what do the CVS people think > of your patch? > > Cheers, > -Archie > > __ > Archie Cobbs * Packet Design * http://www.packetdesign.com __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Option 60: Vendor class identifier = "FreeBSD:i386:pxeboot"
Pxeboot currently sends "PXEclient" for option 60, so it is not easy to differentiate between pxeboot and a real pxe client. I modified libstand to follow the pattern per src/sys/nfsclient/bootp_subr.c, although maybe I should ask for MACHINE and ostype. I would appreciate any testing or feedback. I have tested this some, but it probably has bugs. http://pigseye.kennesaw.edu/~dyeske/freebsd/patch-src_lib_libstand Regards, David Yeske __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvs -rbranch:date + val-tags
I am working on getting cvs more usable so I don't have to worry about val-tags when I have read only media, and so I can do stuff like this. cvs update -rRELENG_4:2002/10/01 cvs diff -rRELENG_4:2002/09/01 -rRELENG_4:2002/09/30 I would appreciate any testing or feedback. I have tested this some, but it probably has bugs. http://pigseye.kennesaw.edu/~dyeske/freebsd/patch-src_contrib_cvs I have also tried modifying the HEAD branch of cvs/ccvs from cvshome, but it seems to blow away the $FreeBSD$ tag with or without my patch. Regards, David Yeske __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
smbfs install option questions
I got a smbfs install option working a while ago before drivers.flp came around, but there was no space on the floppies. Since drivers.flp came out, there is more space. I was wondering how I should go about making this usable, and which files should be on kern.flp, mfsroot.flp, drivers.flp, or somewhere else. Also I am generally looking for feedback... The following patch is NOT up to date though. The diff to GENERIC is NOT implying I think GENERIC should be modifed. I did that just to have those things added to GENERIC so they would make it onto BOOTMFS. The smbfs install option is based of the nfs install option, but it does not use dns. http://pigseye.kennesaw.edu/~dyeske/freebsd/smbfs_current.patch http://pigseye.kennesaw.edu/~dyeske/freebsd/smbfs.c Regards, David Yeske __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message