Re: ASUS A8N-SLI Deluxe supported by FreeBSD 5.3?
O. Hartmann [EMAIL PROTECTED] probably said: Furthermore I would like to equippt this system by a ATI Radeon X600 based PCIe graphics board I had FreeBSD 4 on a machine with an X600 PCIe graphics card briefly. Worked ok as a text console but had no X support whatsoever. P. -- pir ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
USB flash not working anymore
I'm running FreeBSD 4-STABLE from Dec 28 on an IBM X30 laptop. I'm having increasingly worse USB problems as time goes on. Nothing that I try new works and various older devices that I bought specificly because they were supported and worked fine for years now do not work. My SanDisk CF reader (SDDR-31) used to work perfectly, now gives me; umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09, addr 2 umass0: Get Max Lun not supported (STALLED) usb_block_allocmem: in interrupt context, size=4096 da0 at umass-sim0 bus 0 target 0 lun 0 da0: SanDisk ImageMate II 1.30 Removable Direct Access SCSI-2 device da0: 650KB/s transfers da0: 489MB (1001953 512 byte sectors: 64H 32S/T 489C) here I try to mount hte filesystem or use mtools; usb_block_allocmem: in interrupt context, size=4096 usb_block_allocmem: in interrupt context, size=4096 usb_block_allocmem: in interrupt context, size=4096 usb_block_allocmem: in interrupt context, size=65536 usb_block_allocmem: in interrupt context, failed umass0: BBB reset failed, STALLED usb_block_allocmem: in interrupt context, size=65536 usb_block_allocmem: in interrupt context, failed umass0: BBB reset failed, STALLED usb_block_allocmem: in interrupt context, size=65536 usb_block_allocmem: in interrupt context, failed umass0: BBB reset failed, STALLED and it hangs. Sometimes the process hangs, sometimes the machine hangs. My crucial gizmo flashdrive gives me; umass0: Crucial Gizmo, rev 2.00/0.01, addr 2 usb_block_allocmem: in interrupt context, size=4096 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Crucial Gizmo 1.00 Fixed Direct Access SCSI-CCS device da0: 650KB/s transfers da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) [mount the drive] usb_block_allocmem: in interrupt context, size=4096 usb_block_allocmem: in interrupt context, size=4096 [repeated about 30 times] usb_block_allocmem: in interrupt context, size=4096 usb_block_allocmem: in interrupt context, size=4096 umass0: at uhub1 port 1 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached This at least works when mounted but mtools will hang hard. The Iomega mini flashdrive hard hung my machine so I have no logs. Anyone seen these problems before or working on usb in 4.x ? I'll do what I can to help debugging... Thanks, P. -- pir ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB flash not working anymore
Julian Elischer [EMAIL PROTECTED] probably said: this means exactly what it sounds like... something in the usb system tried to allocate memory while in an interrupt context. I don't know anything about the USB subsystem, nor what can or cannot be done while handling an interrupt. I don't see what USB controller you have. OHCI or UHCI (or EHCI). uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x1800-0x181f irq 11 at device 29.0 on pci0 usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0 uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x1820-0x183f irq 3 at device 29.1 on pci0 usb1: Intel 82801CA/CAM (ICH3) USB controller USB-B on uhci1 uhci2: Intel 82801CA/CAM (ICH3) USB controller USB-C port 0x1840-0x185f irq 5 at device 29.2 on pci0 usb2: Intel 82801CA/CAM (ICH3) USB controller USB-C on uhci2 P. -- pir ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB flash not working anymore
Julian Elischer [EMAIL PROTECTED] probably said: do you have access to anything with an EHCI or OHCI controller for comparison with that device? My (now usually windows only) amd64 desktop box has ohci, but it doesn't have any ethernet devices that 4 has support for (5 does, apparently) so I can't easily give direct logs. Booting i386 FreeBSD from an old partition taken to 4-STABLE from earlier this month shows that the SanDisk CF redaer works fine with mtools to read from (when I try to write to it I get lots of umass0: BBB reset failed, STALLED) and the Iomega micro mini thumbdrive also works fine with mtools for read/write. The crucial gizmo does not work at all, I get a umass0 message, a disconnection and then detatch message and then another umass0: Crucial Gizmo, rev 2.00/0.01, addr message and nothing else, no da0; can't re-use a leaf (minimum_cmd_size)! umass0: at uhub1 port 4 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached umass0: Crucial Gizmo, rev 2.00/0.01, addr 2 umass0: at uhub1 port 4 (addr 2) disconnected umass0: detached umass0: Crucial Gizmo, rev 2.00/0.01, addr 2 Shortly after removing the Gizmo the machine page faulted in kernel mode and crashed. After enabling crashdumps I tried this again and the gizmo as the first device worked; umass0: Crucial Gizmo, rev 2.00/0.01, addr 2 umass0: at uhub1 port 4 (addr 2) disconnected da0 at umass-sim0 bus 0 target 0 lun 0 da0: Crucial Gizmo 1.00 Fixed Direct Access SCSI-CCS device da0: 650KB/s transfers da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached umass0: Crucial Gizmo, rev 2.00/0.01, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Crucial Gizmo 1.00 Fixed Direct Access SCSI-CCS device da0: 650KB/s transfers da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) can't re-use a leaf (minimum_cmd_size)! then I got a panic: ohci_abort_xfer: not in process context and a very big crashdump; IdlePTD at physical address 0x003ef000 initial pcb at physical address 0x00346b20 panicstr: ohci_abort_xfer: not in process context panic messages: --- panic: ohci_abort_xfer: not in process context syncing disks... done Uptime: 4m35s (kgdb) bt #0 0xc018b9aa in dumpsys () #1 0xc018b77b in boot () #2 0xc018bba0 in poweroff_wait () #3 0xc0246760 in ohci_abort_xfer () #4 0xc024641f in ohci_timeout_task () #5 0xc024a101 in usb_task_thread () Further down the rabbit hole, I build a kernel.debug and try to copy things over to a flash drive to get them to another machine; umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09, addr 2 umass0: Get Max Lun not supported (STALLED) da0 at umass-sim0 bus 0 target 0 lun 0 da0: SanDisk ImageMate II 1.30 Removable Direct Access SCSI-2 device da0: 650KB/s transfers da0: 489MB (1001953 512 byte sectors: 64H 32S/T 489C) umass0: BBB reset failed, STALLED umass0: Invalid CSW: tag 96 should be 97 umass0: BBB reset failed, STALLED umass0: Invalid CSW: tag 97 should be 98 [lots of these pairs] umass0: Invalid CSW: tag 150 should be 151 umass0: BBB reset failed, STALLED (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Invalid CSW: tag 151 should be 152 umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED umass0: Invalid CSW: tag 234 should be 235 umass0: BBB reset failed, STALLED [lots more of these pairs] umass0: Invalid CSW: tag 235 should be 236 umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Invalid CSW: tag 248 should be 250 umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED This didn't crash the machine, at least. Trying to reprovoke the crash it seems to only fail with a panic from one pair of usb ports, the rest work better. I get another page fault in kernel mode and it dumps; IdlePTD at physical address 0x003ec000 initial pcb at physical address 0x00346b20 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4c fault code = supervisor read, page not present instruction pointer = 0x8:0xc024b23e stack pointer = 0x10:0xe1d91f30 frame pointer = 0x10:0xe1d91f44 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 4 (usbtask) interrupt mask = bio trap number = 12 panic: page fault syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1
Re: cdrecord cannot see DVD-RW with ATAPICAM
Zahemszky Gbor [EMAIL PROTECTED] probably said: TSSTcorp CD/DVDW TS-H552B TS05 at scbus2 target 0 lun 0 (cd1,pass3) Can somebody help me to find the reason of this special error? Have you checked that /dev/pass3 and other device files existx ? P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Randy Bush [EMAIL PROTECTED] probably said: $20 just sent via paypal Got it, thanks ! P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Peter Radcliffe [EMAIL PROTECTED] probably said: If anyone would like to contribute a little towards it, feel free to paypal me at this address :) The only gotcha is that I can't take credit card sourced payments, I only have a basic paypal account and don't want to upgrade it (because then paypal take a cut of everything). P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Sren Schmidt [EMAIL PROTECTED] probably said: SATA ATAPI devices are not supported yet. There are a few gotcha's though. Not all SATA controllers does support SATA ATAPI even if out driver would, so its a mixed blessing for now. Anyhow, as soon as I can get my hands on a SATA ATAPI device, be certain that I'll get support in there If it's something you'd like to work on I'd happily put some money towards sending a drive in your direction... P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Rob [EMAIL PROTECTED] probably said: Same here, I could remove it and ship it to you today, probably 2nd day air, or one of the cheaper but fast services. If P, however, doesn't have to tear his computer all apart LOL, maybe that might be a better solution for me. I was more suggesting buying one and having it directly shipped... The support would likely be useful to me in the medium term so if I can contribute towards helping that happen I would. P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Sren Schmidt [EMAIL PROTECTED] probably said: Well, you probably should take care of your sister first :) And no I dont have a paypal account, so far I've got by fine without it, by using other means as checks, wiretransfers etc etc... Do you have a list of things (particular devices or general categories) that would be useful for your work and an address ? :) P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sounblaster Live Card
Derrick Edwards [EMAIL PROTECTED] probably said: Is there a manual way to bind a snd driver to my soundcard. Or is this card not supported? Looks like you've got an Audigy, not an SBLive. The SBLive is supported (I use them in several places) and they show up like this; [EMAIL PROTECTED]:5:0: class=0x040100 card=0x80311102 chip=0x00021102 rev=0x07 hdr=0x00 vendor = 'Creative Labs' device = 'EMU1 Sound Blaster Live! (Also Live! 5.1) - OEM from DELL - CT4780' class= multimedia subclass = audio I'm assuming you don't have a supported card. P. On Monday 29 November 2004 01:00 am, Derrick Edwards wrote: I went out and bought a Sound Blaster Live sound card. I have searched and tried various things such as: [EMAIL PROTECTED]:1:0: class=0x040100 card=0x10061102 chip=0x00071102 rev=0x00 hdr=0x00 vendor = 'Creative Labs' device = 'CA0106-DAT Audigy LS' class= multimedia subclass = audio -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Groups 12 and 14
S. Anthony Sequeira [EMAIL PROTECTED] probably said: Can anyone tell me which groups 12 and 14 are, on a 4.10 system please. http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/group?rev=1.19.2.3content-type=text/x-cvsweb-markup $ ls -ld /usr/compat/linux/var/lock /usr/compat/linux/var/spool/mail drwxrwxr-x 3 root 14 512B Apr 18 2004 /usr/compat/linux/var/lock drwxrwxr-x 2 root 12 512B Feb 6 1996 /usr/compat/linux/var/spool/mail Those are not part of the base system, they're part of the linux port. Mine are the same. P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: supporting broadcom gig BCM5751
Paul Saab [EMAIL PROTECTED] probably said: Can you try http://yogurt.org/FreeBSD/bge_5750.diff It got my 5751 working. Unfortunately the further problems I had involved not being able to get the PCI-extreme ATI graphics card working with XFree86 so the box became a windows machine and is in use, I can't test things on it anymore :/ P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
MFC of bluetooth stack ?
Is there any likelyhood of the bluetooth stack being MFCed ? I'm assuming not, since 5.x is due to become -stable fairly soon... P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't install 'bin/sh'
Bjarne Wichmann Petersen [EMAIL PROTECTED] probably said: So shouldn't cvsup correct and remove any leftovers from CURRENT? Or should I delete some directories in /usr/src (and which ones)? The way to be sure is to nuke the contents of /usr/src/ and /usr/obj and re-cvsup from scratch after double checking *default tag=. Make sure you save your kernel configs, first. P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
prism 2.5 mini-pci issues
I tried my intel/xircom prism 2.5 mini-pci card again, yesterday, with -stable. wi0: Intersil Prism2.5 mem 0xf800-0xf8000fff irq 11 at device 2.0 on pci1 wi0: 802.11 address: 00:05:3c:06:34:c9 wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary 1.01.00, Station 1.04.09 It behaved itself for a while and then got very unhappy; wi0: timeout in wi_cmd 0x010b; event status 0x wi0: xmit failed wi0: watchdog timeout wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: init failed wi0: timeout in wi_seek to fc07/0; last status 800b wi0: timeout in wi_seek to fc00/0; last status 800b wi0: timeout in wi_seek to fc81/0; last status 800b wi0: timeout in wi_seek to fc83/0; last status 800b wi0: timeout in wi_cmd 0x010b; event status 0x wi0: xmit failed wi0: watchdog timeout wi0: timeout in wi_cmd 0x0002; event status 0x wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: init failed The machine hung up for a little while during some of the failures but after it started having issues it never really recovered. P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
module build failing in -STABLE
buildworld fails for me right now, consistantly in the same place, with freshly cvsuped source from cvsup.freebsd.org with the following error. P. === nullfs cc -O -pipe -include /usr/src/sys/compile/DISAPP/opt_global.h -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -g -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -c /usr/src/sys/modules/nullfs/../../miscfs/nullfs/null_subr.c cc -O -pipe -include /usr/src/sys/compile/DISAPP/opt_global.h -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -g -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -c /usr/src/sys/modules/nullfs/../../miscfs/nullfs/null_vfsops.c cc -O -pipe -include /usr/src/sys/compile/DISAPP/opt_global.h -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -g -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -c /usr/src/sys/modules/nullfs/../../miscfs/nullfs/null_vnops.c /usr/src/sys/modules/nullfs/../../miscfs/nullfs/null_subr.c:284: opt_ddb.h: No such file or directory *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rocketport (rp) PCI card on stable ?
Mike Tancsa [EMAIL PROTECTED] probably said: I picked up a surplus Rocketport PCI card but am having problems getting it to run on STABLE. I can get it to work just fine under windows, so I know it works. But I cant get it to work with FreeBSD. I have the /dev/cuaR# devices, but alas, no joy. All I want to do is just be able to use it as a terminal server to connect to other FreeBSD boxes. I'm using a 4 port PCI rocketport RJ45 card fine under -STABLE; rp0: RocketPort PCI port 0xa000-0xa0ff mem 0xef045000-0xef045fff, 0xef044000-0xef044fff irq 11 at device 1.0 on pci2 RocketPort0 (Version 3.02) 16 ports. (no idea why it says 16 ports, it is the 4 port version). I am just using cu, but I tried minicom as well without luck. Has anyone used this card with luck under STABLE ? I use kermit to /dev/cuaR0 and can get out to the console of other machines fine. P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: FreeBSD 4.6.1 RC1 (i386)
Bruce A. Mah [EMAIL PROTECTED] probably said: The latter. 4.6.1-RELEASE is a point along the RELENG_4_6 security branch. There will be a RELENG_4_6_1_RELEASE tag to mark this, but no RELENG_4_6_1 branch. Good, the sensible line :) Thanks. P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: PQI travel flash (Re: Problem with compact flash reader under -stable)
Mike E. Matsnev [EMAIL PROTECTED] probably said: On Wed, Jan 02, 2002 at 05:10:16AM -0500, Peter Radcliffe wrote: The travel flash works roughly as fast under windows as the sandisk does under freebsd. Were you testing with current or stable ? -current A bit more testing shows the problem seems to be with mtools interacting with the travel flash. If I mount the flash as a msdos disk it's jus as fast as my SanDisk. Mike, have you been using mtools or mounting the FS ? Anyone got any mtools hints that might fix the slowness ? P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problem with compact flash reader under -stable
Duane H. Hesser [EMAIL PROTECTED] probably said: It appears to me, though, that the USB spec merely gives vendors a target to avoid. Apparently, they interpret it as Unspecified Serial Bus, since they all seem to go their own way. I have a Microtech Zio flash card reader which is too large for a keychain holder and too small for a paperweight. It is recognized by the ugen driver as SHUTTLE SCM Micro USBAT-02 and usbdevs -v reveals its ID as 04e6:1010, so I know it's there (but then, I knew that, as it was me that plugged it in :=). I played with one of these last night - got it recognised by umass but all I managed to do was hang my machine with any tweaks that I tried. Another SHUTTLE device is '#if 0'-ed out in umass because the ATAPI code isn't ready for primtime and I'm wondering if the other devices made by them are similar. The sandisk SDDR-31 was my answer - works just fine, shame it's not as small as some of them (at some point I'll hack on the travel flash which is at least recognised and probably just needs quirking. P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: loopback not working for anything other than 127.0.0.1
Lamont Granquist [EMAIL PROTECTED] probably said: All my 4.3 and 4.4 boxen have problems with the only lookback address being valid is 127.0.0.1 instead of the entire /8. My ifconfig looks like: lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 (note that this is the correct netmask) and note that the only ipv4 address listed is '127.0.0.1'. --- 127.0.0.2 ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss it does not work like it should. Looks perfectly normal to me. What is like it should ? You don't have anything listening on the ip 127.0.0.2, why should anything answer ? P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Cisco Aironet 350..
Sergey Eremin [EMAIL PROTECTED] probably said: In other words Aironet 350 works fine with 4-stable? I'm using one to type this. Works just fine. ancontrol works just fine with some earlier versions but the an driver got various improvements in -STABLE. P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Making a bootable disk2 from a make release?
Jordan Hubbard [EMAIL PROTECTED] probably said: There's nothing like that, either in docs or tools. Contributions always accepted. :) From: Chad R. Larson [EMAIL PROTECTED] Is there a write up or a cookbook on creating custom, bootable CDs? The last time I made up some custom bootable CDs I built the image on a disk to test it, created a custom kernel and edited the image of the 2.88mb boot floppy to use my custom kernel and not do any config things, then put the whole thing (including boot floppy image) on a CD with cdrecord as I would with any other x86 bootable CD ... P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: setting pci pnp SMC2602W
Peter Blok [EMAIL PROTECTED] probably said: I am running 4.3-STABLE, version of 2 july. I have a SMC2602W card (PCI to PCMCIA bridge to SMC2632W) wireless LAN adapter. The kernel recognizes the adapter, bit fails to allocate an interrupt No irq?! message because the IRQ is already occupied. The if_wi driver doesn't allow RF_SHAREABLE irqs. This has been discussed in depth in the -mobile list. Search the archives. The short answer is that this should be working in -CURRENT now, but not -STABLE. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: pcmcia insert/remove problems recently
Warner Losh [EMAIL PROTECTED] probably said: I just committed a fix that Ian suggested to pcic.c in stable. You might want to give that a spin. Mug me Friday if it doesn't work. I havn't had any irq storms since updating, but I have had a fairly large number of remove events missed. This may be entirely co-incidential, though, since my normal usage is to suspend/resume with the card in place more than insert/remove as I'm doing at usenix. So far I've been able to recover from the missed events by using pccardc power 0 0 ; pccardc power 0 1 and occasionally also restarting pccardd. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: sshd revealing too much stuff.
Graywane [EMAIL PROTECTED] probably said: Yes, it is security by obscurity and no, most people thinking about security on the net do not believe it is an effective technique to secure a site. You secure a site by: Security by obscurity is a bad thing to _rely_ on, but why make it any easier to get information which is useful ? The less a cracker knows about any system the more work/time it will take for them to break into it. Personally I only allow connections from hosts that need to connect to ssh, so the rest wouldn't see it ... but if I notice this extra info appearing on any of my machines, I'll get rid of it. It would be easier if it wasn't there in the first place. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sshd revealing too much stuff.
Kris Kennaway [EMAIL PROTECTED] probably said: Making it easy for the _administrator_ to get information that is useful for administration is a good thing. This can be done without providing the same information to an attacker. Think about the audit for vulnerable versions of SSH using e.g. scanssh. How is the administrator to differentiate between the standard, vulnerable, version of OpenSSH 2.3.0 and the fixed, non-vulnerable version included in FreeBSD 4.2-STABLE unless it reports itself differently? It's running ssh, it's accessable from the network. Put the changed version string in ssh --version or similar and connect to the machine to check it. Information does not have to be available to an attacker. Perhaps you're unaware of how easy it is to fingerprint an OS by simply examining the behaviour of the IP stack and the response to various packets. If you can receive *any* packets from a host you can No, I'm perfectly aware of this. This doesn't mean I want to inform a potential attacker exactly what sub-version of ssh I'm running, though. Again, fine-grained OS fingerprinting is trivial and there are many automated tools for doing it which work reliably, so complaining about this instance is just tilting at windmills. Getting an OS version is different from getting _exactly_ which application version is there. I've seen, and indeed use, the fine-grained OS fingerprinting. I find that quite beside the point when talking about application versions. *sigh* Something else to fix every time I install a machine. Currently I don't even use FreeBSD's OpenSSH installation since it's so out of date anyway. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: openssh not setting DISPLAY
Randy Bush [EMAIL PROTECTED] probably said: -stable of yesterday X 4.02 openssh, moving from /usr/ports/security/ssh1 DISPLAY env var not being set. i expect `hostname`:10.0 x forward not seeming to happen even if i set it manually. /etc/ssh/ssh_config Host * ForwardX11 yes P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Intel PRO/1000F NIC wx driver
Lars Eggert [EMAIL PROTECTED] probably said: Lars Eggert wrote: The Intel PRO/1000F NIC does not seem to be fully supported by the wx driver. Sorry for not mentioning this in the original post: This card uses the Intel 82543GC chip. I realise this isn't very useful to you for getting that card working, but if you need gig ether working sooner than a fix I've been using the Netgear GA620, both fibre and copper versions; ti0: Netgear GA620 1000baseT Gigabit Ethernet mem 0xf400-0xf4003fff irq 10 at device 15.0 on pci0 ti0: gigabit link up ti0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 130.64.1.222 netmask 0xff00 broadcast 130.64.1.255 ether 00:02:e3:00:3d:a0 media: autoselect (1000baseTX full-duplex) status: active supported media: autoselect 1000baseTX full-duplex 1000baseTX 100baseTX full-duplex 100baseTX 10baseT/UTP full-duplex 10baseT/UTP Negotiates fine with the Foundry kit we use, at 100bT fdx and gbit fdx. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.2-BETA hangs on boot
Nate Williams [EMAIL PROTECTED] probably said: Polling 'should' work in all cases, although suspend/resume may not work reliably (races and such). If it doesn't work on Steve's laptop, something is messed up with the PCIC probing/setup, since it should work fine. Completely unreliable on my sony Z505HS. Using it hangs the machine, every time. The biggest advantage for supporting 'polling by default' is the fact that IRQ's are a precious commodity on newer hardware, and 'wasting' one just for insertion/removal events seems a waste. (Steve, on a whim, is PnP turned *OFF* in your BIOS?) It's off in my bios. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: isc-dhcp3-3.0.b2.9 core dumping on FreeBSD-4.2 BETA
Dan Larsson [EMAIL PROTECTED] probably said: The dhcpd daemon keeps coredumping after a couple of hours. It leaves a dhcpd.core file, what tools can I use to figure out why? I wouldn't put too much effort into tracking this down. There are several known issues with 3.0b2pl9 which will take the server out (but if you do want to help with dhcpd development, get the most recent version - pl9 - and subscribe to the dhcp-server mailing list. Details for both at www.isc.org). 3.0b2 is by no means stable and is in the rapid patchlevel stage, ironing out problems, and is not ready for prime time. I'm still using 3.0b1pl16 or 3.0b1pl17 on my production systems. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.1-RELEASE pccard?
John Reynolds~ [EMAIL PROTECTED] probably said: When you do this in 4.1.1, do you already have an 'ed0' device in your machine? The PAO example shows 'ed0' as the device while 4.1.1 shows ed1. I'm currently having problems with any 4.1.1 kernel probing my two ed cards incorrectly (I get ed1 but not ed0), I just haven't had time to debug it. Hopefully tonight I can back out the if_ed.c file to the last RELENG_4 commit and see if that fixes my problem. One of my standard procedures for 4.* laptops is to change any ethernet lines from, say; device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 to device ed Then all the device names seem to be right and start at 0. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: I'll be rolling a 4.1.1 release on September 25th
Kris Kennaway [EMAIL PROTECTED] probably said: My point was that you need to either ask one of the committers directly, or ask in a forum where the committerss hang out. Thats not -stable - there are only a few of us here, so asking here is almost akin to asking in a vacuum. Ok, some partly useful information. However, I don't know who the committers are, or where they hang out. 5) I know how the system works, but it requires someone to commit the patches and no one will. Works for you..they have to go through -current first in case they break I was talking about the committing system, not my computer system. I know how the committing system is supposed to work and it going through -current first. I'm not a raving newbie, please don't treat me like one. Reply-To: [EMAIL PROTECTED] Mail-Followup-To: [EMAIL PROTECTED] So your MTA should take one or the other, not both. My question still stands, can these patches get in, somewhere ? You're still talking to the wrong list. You're still not giving me any information on which list to talk to or what else to do. I don't run -current, so I don't read freebsd-current. I run -stable. Around the 2.1.* era I spent time working on things, this problem is one of the reasons why I never bother developing or tracking down problems that don't directly impact me - even if I do, that information can sit in a PR for years and never be touched. Once something is in a PR, that needs to be looked at by someone with the ability to say "yes, this is good and should be committed to current" or "this needs some work or could be done better" or "this isn't appropriate". This often doesn't happen (even allowing for the volunteer nature of the project) and IMO is impacting the project negatively. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Anyone having dial-up problem with sendmail 8.11.0 ? (FIXED)
Gerhard Sittig [EMAIL PROTECTED] probably said: 127.0.0.1 localhost greatoak.home I had 127.0.0.1 localhost myname.my.domain not exactly this but this is the idea. It's generally considered a Bad Idea(TM) anyway to have any other name assigned to 127.x.x.x but localhost. Just don't do so and assign a "real" address to your NIF and name your machine appropriately. Even if you don't get official IPs from ARIN and friends, RFC1918 has plenty of them for your toying ... That isn't entirely true. As long as the first entry on the line is "localhost", everything will still work as expected. On any mobile machine I have that may or may not have real (or RFC private) addresses to use at any given time I put an entry for the name of the machine on the localhost line so it can resolve it's own name when not connected. I also dislike fully qualified node names, so just use the short form. On a laptop that may connect to someone's internal RFC private network and use DHCP you can't rely on any address space being legitimate for a "private" interface or name on a mobile machine. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Which applications are using kqueue ?
Kris Kennaway [EMAIL PROTECTED] probably said: On Fri, 28 Jul 2000, Andrew Reilly wrote: The boa HTTP server might be as good a place to start too: it doesn't fork either (except to run CGI scripts). Actually, thttpd sounds pretty similar. I hadn't looked at it before. Have you compared them at all? Nope, but the 't' appealed to me as a good one to start with :-) I've been using phttpd on machines where I want to serve a small amount of information via http and don't want to install something major like apache. Modular (literally loaded modules) for the different functions, so if you don't want a particular thing, like cgi, you don't install the module and comment it out of the config file. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Fixit media (Re: URGENT: bad superblock)
Gerhard Sittig [EMAIL PROTECTED] probably said: Which turns out to be a little hard sometimes (been there with the 4.0 CD set this week) when the fixit media doesn't have slice entries in /dev and you don't have access to the (yet to be mounted!) filesystem with the appropriate /dev entries. Funnily Speaking of fixit media, is there still a fixit CD image ? My new laptop has (amongst it's other minor problems) a USB floppy, which works to boot/install from, but sysinstall doesn't see it as a floppy for use with the fixit floppy (it appears as da0). Now, I do have a bootable cdrom drive, so a bootable fixit CD with an image on it would be very useful to me - is there one (to purchase or an image), which sysinstall can use as the "live" image ? Can I just burn a CD with boot.flp as the boot image and the filesystem from my existing machine and expect it to work ? Thanks, P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: README.TXT and RELNOTES.TXT not updated before release tag?
John Reynolds~ [EMAIL PROTECTED] probably said: I know one thing that needs to be rebuilt for sure--if you use GNOME and or anything that depends on libgtop, pkd_delete it and rebuild libgtop. I use the "cpumon" applet and it happily won't load when we transition across STABLE-RC and RC-RELEASE-STABLE transitions. When the OS "version" changes lsof will whine, but still work. I tend to only recompile things that I need to or that I want newer versions of. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: newpcm and RealPlayer woes
Matt Heckaman [EMAIL PROTECTED] probably said: I do not have any of the 'weird sound' problem though. I did through XMMS but their new version fixed that out. Similar problems occured with things that used certain mixers. I believe this was an issue of the *program* not the OS. Either way, xmms 1.2.x fixed it. I'm using xmms 1.2.1. I get the static on open as I described with xmms, x11amp and mpg123. With the same software on a machine using an SBLive, I don't get any static problems. I also haven't seen the mose movement or console change noise, just static on open, sometimes ... P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pxeboot problems with 4.0-stable (continued)
Gerhard Sittig [EMAIL PROTECTED] probably said: Listening on BPF/fxp1/00:50:8b:d3:0b:ba/10.25.1.0 Sending on BPF/fxp1/00:50:8b:d3:0b:ba/10.25.1.0 Sending on Socket/fallback/fallback-net I would expect the daemon to listen on and to send to a "real" address (i.e. 10.25.1.1) instead of the network address. No, dhcp listens on interfaces and also lists the networks assosicated with those interfaces. If you read that line, it's listening on fxp1 via BPF which has that ethernet address and that network associated with it. Startup messages like that are perfectly normal. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Follow-up: XirCom Realport Cardbus Modem/Ethernet PC card
Please be polite and trim quoted text to a minium. Will Mitayai Keeso Rowe [EMAIL PROTECTED] probably said: Cardbus cards are not yet supported. are there any plans to have it included in the near future? As soon as the good people who are working on the code get it finished. The last timeframe I heard was a matter of months. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.0-Stable Kernel Error?
John [EMAIL PROTECTED] probably said: May 18 12:55:17 merlin /kernel: arp: unknown hardware address format (0x0800) It's showed up 3 times in the past 36 or so hours, but not at any point in time that I can narrow it down to occurring near/after/during any specific system event. Any idea what would be causing the error and how to go about fixing it? My guess would be, apart from a possible bug, that you have a broken network card on your network spewing bad packets. Previous OS version might not have reported them. Try tcpdump to catch them ? Might be able to limit the display to packets not of type ether. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: dufus.[...] daily run output -- summer time
"Donald R. Tyson" [EMAIL PROTECTED] probably said: As a moderately humorous aside, when I booted the Windows side of my home machine on Sunday afternoon, it proudly informed me that it had adjusted for the time change, and then displayed a **2-hour** leap ahead. At least the 4.0-STABLE side, despite the error reported by several on this list, managed to get the time right. This is normal. 'doze keeps the PC's system time as local time, so all it does when it works out it's booted the first time after a timechange (and probably if it is up over a timechange) is add/subtract an hour from the current time. If you run a FreeBSD box with local time in the system clock (which of course you have to to make doze have the correct time), it does the same thing. Boot both after a timechange, you get 2 hours difference, 1 from each. On my dualboot boxes I turn off automatic time changes in doze. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Small spaces
Laurence Berland [EMAIL PROTECTED] probably said: I'm trying to install FreeBSD 3.4 on an old 486 I've got lying around to use as a NATing firewall for my home network, but I've only got a 200 Meg HD around. I'm gonna go get another HD later, but right now I'd I had a 2.2.something 486 as a dialup router many moons ago, on a 160Mb disk. like to get running with just that. So far I've been trying with 16 to swap and various other combinations, but it always seems to run out of /usr space. I figure / should be at least 32MB, and the rest (~152MB) goes to /usr. I'm trying to install the binaries, the docs, and the kernel source (but not the rest of the source). Any idea if it's even possible? Should I shrink down the root partition more? I've done You could leave /usr in / and share the spare space ... and go through the binaries deleting things you won't need on another disk (or via NFS) ? A minimal NAT box doesn't need that much in the way of binaries. loads of installs at this point, but all on HDs with at least a gig for FreeBSD. Any ideas where I can get a bigger HD that's still under the limit for old BIOSen? Thanks in advance for any help. You could get a cheap bootable scsi card like the adaptec 1542 (from memory, ISA bootable) and drop a 1gb scsi disk in it ? That or look at picobsd ? P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: disk cloning
"Waite, Michael" [EMAIL PROTECTED] probably said: The disk is indeed showing up as da2 now the dd shows this as the error: da2 rwa partition size ! slice size da2 start0, end 13523, size bla bla bla more bla bla bla dd: /dev/da2 : Read-Only fuilesystem 1+0 in 0+0 out and on to the next problem. Disk cloning with dd is evil. Don't Do That. My recommendation is to partition the disk as you desire, newfs and mount the partitions then use cd /new/partition; dump 0f - /original/partition | restore rf - This really belongs in freebsd-questions. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Warner's PCI Modem Driver
Dan Zerkle [EMAIL PROTECTED] probably said: I believe that they were bought by 3COM a few years back. I also believe that they *invented* winmodems, so be careful. Pretty much, yes. That said, the modem I got from them was just fine. I did have to revert to Windows to flash its ROM's, though. I am a _big_ fan of external USR couriers, their top of the line modem. They are _not_ cheap, but for me they are worth it because of the saved hassle because they pretty much just work and being flash upgradable essentially forever (14.4k couriers can be upgraded to V.90). I like the external models since I can move them between machines easily (and use them on non-PCs) as well as being able to reset them without rebooting the machine. Never bought another modem ... P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: routing over a dual t1 connection (fwd)
David Schwartz [EMAIL PROTECTED] probably said: I have done this is a production environment, the traffic balanced perfectly. Then perhaps you'd care to share with us how you told the router whether it This is a) nothing to do with freebsd and b) specificly nothing to do with -stable. Would you care to take cisco discussions elsewhere, please. P. -- pir [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
