Re: 9.1-PRERELEASE jail_sysvipc_allow
Reading /etc/rc.d/jail script I found the answer: jail_*_parameters="allow.sysvipc=1" in /etc/rc.conf Paulo. On 14/11/2012 08:35, Paulo Fragoso wrote: I've instaled FreeBSD 9 for hosts some jails and setting jail_sysvipc_allow="YES" in host rc.conf, why is security.jail.sysvipc_allowed false in jail? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9.1-PRERELEASE jail_sysvipc_allow
I've instaled FreeBSD 9 for hosts some jails and setting jail_sysvipc_allow="YES" in host rc.conf, why is security.jail.sysvipc_allowed false in jail? -- BSDCG: BSDA - Digium: dCAP Electrical/Eletronic Engineer http://www.nlink.com.br +55 81 2121- Cel:81 9727- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: freebsd 8.0 stable amd64/x86 needs ~9min to bootup
This problem happened with me too. I don't know why boot loader makes
intensive reads when installed on partition created by another fdisk
(windows, linux, etc) and started by GRUB2.
There is a workaround for this, you have to create all partitions with
freebsd sysinstall included windows and linux partitions. After this do
install for all others OSes using those partitions created by sysinstall.
In my case there are 03 OSes installed on same HD:
1: Windows boot loader: 1023MB
2: Windows 7: 50GB
3: PCBSD 8.0: 70GB
* -> 5: Linux 108GB
6: Linux swap
This problem can be tested before install if you run sysinstall and
choses partiotion menu if you receive alerts like this: "Partition X
does not end on cylinder boundary" you will have problem with GRUB2.
I'm using GRUB2 from Ubuntu 9.10 with this entry in file
/etc/grub.d/40_custom:
menuentry "FreeBSD/PCBSD 8.0 AMD64" {
set root=(hd0,3)
chainloader +1
}
All works fine!
Paulo.
Em 05/02/2010 08:29, Zavam escreveu:
2010/1/28 Zavam, VinÃcius :
2010/1/28 Bruce Simpson :
Try GRUB4DOS. I use this so on boxes where I have Windows installed, I can
keep GRUB in the NTFS partition.
I haven't seen this issue and am tracking -STABLE on an ASUS V-series
machine.
Simpson,
I forgot to mention... but I tested it using boot0 (freebsd's
bootmanager) with no success ;<
had no shots with grub4dos, gag, lilo or grub2; I assume it may not be
a bootmanager issue, but freebsd's btx bootstrap loader.
my gentoo and windows o.s. can be loaded using grub or boot0.
--
Zavam, VinÃcius
gentlemen,
morning.
I just did new fresh installs using 80-STABLE/amd64 and
90-CURRENT/amd64 snapshots.
unfortunately, no success.
when tryied the 90-CURRENT I've created a slice to /boot (d) at the
beginning of the partition (ad4s4) and grub returned error code 18
[1].
strange. even installing in another slice, at the beginning of the
disk (ad4s1), the bootup process was slow too.
[1] http://wiki.linuxquestions.org/wiki/GRUB#Error_18
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 7.2-RC boot problem
Em 29/04/2009 09:18, Paulo Fragoso escreveu: Em 29/04/2009 09:01, Ken Smith escreveu: On Tue, 2009-04-28 at 09:52 -0300, Paulo Fragoso wrote: It doesn't print any message and after that short time BIOS try next device from boot order. First a question just to verify - is this i386 or amd64? I'm guessing i386. i386 One more thing to try if you don't mind. Could you try booting one of the other bootable iso images (either bootonly or livefs), and if that succeeds when it reaches the first screen of sysinstall swap in disc1 before proceeding with a normal install. Thanks. Appreciate any testing you can do. I will try this and boot from dvd too. Hardware: MB: Gigabyte GA-M61PME-S2 acd0: DVDR at ata3-master SATA150 ISO MEDIA BOOT 7.2-RC2-i386-dvd1.isoDVD-RW OK 7.2-RC2-i386-livefs.iso CD-RWOK! 7.2-RC2-amd64-disc1.iso CD-RWOK 7.2-RC2-i386-disc1.iso CD-RW,CD-R FAILS Paulo. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 7.2-RC boot problem
Em 29/04/2009 09:01, Ken Smith escreveu: On Tue, 2009-04-28 at 09:52 -0300, Paulo Fragoso wrote: It doesn't print any message and after that short time BIOS try next device from boot order. First a question just to verify - is this i386 or amd64? I'm guessing i386. i386 One more thing to try if you don't mind. Could you try booting one of the other bootable iso images (either bootonly or livefs), and if that succeeds when it reaches the first screen of sysinstall swap in disc1 before proceeding with a normal install. Thanks. Appreciate any testing you can do. I will try this and boot from dvd too. I've already tested at my home and it boots sucessful. This media fails on test pc. Paulo. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 7.2-RC boot problem
Em 28/04/2009 09:52, Paulo Fragoso escreveu: Em 27/04/2009 14:16, Ken Smith escreveu: On Mon, 2009-04-27 at 14:10 -0300, Paulo Fragoso wrote: Em 27/04/2009 12:05, Ken Smith escreveu: On Mon, 2009-04-27 at 11:03 -0300, Paulo Fragoso wrote: I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR at ata3-master SATA150 Just checking - is *everything* the same? For example is the media the same? Depending on a variety of things I've had issues with rewritable media versus write-once media, etc. The machine I test the release builds on before uploading them has a Gigabyte motherboard (G31M-ES2L) with a sata drive in it so it's not a generic "sata doesn't work" issue: acd0: DVDROM at ata0-slave SATA150 If none of that helps we'd need more information about how far it gets before it stops. I can say there is a problem to boot with cdrom since 7.2-BETA1. All system is same, all older version can boot in this machine: 6.1, 6.2, ...,7.1, etc. amd64 or i386. I've burnt 03 media to test 7.2-RC2, one cd-rw burnt with cdrecord and two cd-r burnt first with burncd and last was burnt with cdrecord. What I can do to help this release? We need more information about how far it gets before it stops. Does it seem like it attempts the boot off the CD at all or does it just fall through to booting off the hard drive? It try boot from cdrom and after a little time it boots from next device. If it does attempt to boot off the CD does it lock up with no messages? If there are messages what are the last few things it says? It doesn't print any message and after that short time BIOS try next device from boot order. Paulo. If I try boot from 7.1-RELEASE cdrom this mensagens are printed after POST: Verifing BMI Pool Data Boot from CD/DVD : CD Loader 1.2 Buildong the boot loader argumetns ... using 7.2-RC2 cdrom: Verifing BMI Pool Data Boot from CD/DVD : (4,35 seconds) NVIDIA Boot Agent 244.0538 ... Paulo. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 7.2-RC boot problem
Em 27/04/2009 14:16, Ken Smith escreveu: On Mon, 2009-04-27 at 14:10 -0300, Paulo Fragoso wrote: Em 27/04/2009 12:05, Ken Smith escreveu: On Mon, 2009-04-27 at 11:03 -0300, Paulo Fragoso wrote: I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR at ata3-master SATA150 Just checking - is *everything* the same? For example is the media the same? Depending on a variety of things I've had issues with rewritable media versus write-once media, etc. The machine I test the release builds on before uploading them has a Gigabyte motherboard (G31M-ES2L) with a sata drive in it so it's not a generic "sata doesn't work" issue: acd0: DVDROM at ata0-slave SATA150 If none of that helps we'd need more information about how far it gets before it stops. I can say there is a problem to boot with cdrom since 7.2-BETA1. All system is same, all older version can boot in this machine: 6.1, 6.2, ...,7.1, etc. amd64 or i386. I've burnt 03 media to test 7.2-RC2, one cd-rw burnt with cdrecord and two cd-r burnt first with burncd and last was burnt with cdrecord. What I can do to help this release? We need more information about how far it gets before it stops. Does it seem like it attempts the boot off the CD at all or does it just fall through to booting off the hard drive? It try boot from cdrom and after a little time it boots from next device. If it does attempt to boot off the CD does it lock up with no messages? If there are messages what are the last few things it says? It doesn't print any message and after that short time BIOS try next device from boot order. Paulo. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 7.2-RC boot problem
Em 27/04/2009 12:05, Ken Smith escreveu: On Mon, 2009-04-27 at 11:03 -0300, Paulo Fragoso wrote: I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR at ata3-master SATA150 Just checking - is *everything* the same? For example is the media the same? Depending on a variety of things I've had issues with rewritable media versus write-once media, etc. The machine I test the release builds on before uploading them has a Gigabyte motherboard (G31M-ES2L) with a sata drive in it so it's not a generic "sata doesn't work" issue: acd0: DVDROM at ata0-slave SATA150 If none of that helps we'd need more information about how far it gets before it stops. I can say there is a problem to boot with cdrom since 7.2-BETA1. All system is same, all older version can boot in this machine: 6.1, 6.2, ...,7.1, etc. amd64 or i386. I've burnt 03 media to test 7.2-RC2, one cd-rw burnt with cdrecord and two cd-r burnt first with burncd and last was burnt with cdrecord. What I can do to help this release? Paulo. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Freebsd 7.2-RC boot problem
Hi, I can't boot on cdrom sata, this problem doesn't exist in older releases. My motherboard is Gigabyte GA-M61PME-S2 On FreeBSD 7.1 my cdrom drive is detected this way: acd0: DVDR at ata3-master SATA150 Paulo. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freezes in wireless bridge
Paulo Fragoso wrote: Hi, We have two bridges running FreeBSD 6.1-BETA1 and we have a lot of freezes in a week, it's happening when trafic is high, but it has ever happened when we was changing dev.ath.0.acktimeout. There aren't dumps, all CPU is freezed, state of leds in kayboard doesn't change, only leds of wireless card (D-Link G520) are blinking. Some times is printed on console DMA erros of ad0 before system to freeze. After cvsup src-all upgrade (2006-03-04) which had changed version of ath_hal from 0.9.14.9 to 0.9.16.16 and after we had changed bridge configuration from net.link.ether.bridge.config="..." to added device if_bridge, we can't get anymore freezes: $ uptime 20:35 up 7 days, 4:38, 1 user, load averages: 0,03 0,03 0,00 Is there any problem with bridge (net.link.ether.bridge.config) or old ath_hal? We can't found any change.log about this problem. Paulo Fragoso. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Freezes in wireless bridge
Hi, We have two bridges running FreeBSD 6.1-BETA1 and we have a lot of freezes in a week, it's happening when trafic is high, but it has ever happened when we was changing dev.ath.0.acktimeout. There aren't dumps, all CPU is freezed, state of leds in kayboard doesn't change, only leds of wireless card (D-Link G520) are blinking. Some times is printed on console DMA erros of ad0 before system to freeze. We have already tried to disable ATA DMA (hw.ata.ata_dma=0, hw.ata.atapi_dma=0, hw.ata.wc=0), but system freezes yet. This bridge is runnig on motherboard MSI VIAK8M with 03 Atheros board (D-Link G520), but this problem happens using other motherboards and CPUs. Is there anyway to force dumps? Is there any watchdog hardware for FreeBSD 6.X? All sounds like when we were using FreeBSD 2.x + SCSI + ATI S3 Virge, the problem was XFree86. Paulo Fragoso. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem with atheros at 11b and FreeBSD 6.1-BETA2
Hi, We have a problem with atheros (D-Link AG530) using FreeBSD 6.1-BETA2 in client mode to associte our production bridge (mode 11b), this card change to associated state after a long time (9min): ath0: flags=8843 mtu 1500 inet 172.16.23.2 netmask 0xff00 broadcast 172.16.23.255 ether 00:13:46:9a:29:13 media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) status: associated ssid "WAVE BMARX" channel 3 bssid 00:02:2d:8d:b3:5c authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit txpowmax 18 protmode CTS burst bintval 100 it was configurated using this script: ifconfig ath0 inet 172.16.23.2 netmask 255.255.255.0 ssid 'WAVE BMARX' \ wepmode on wepkey 0x3132333435 weptxkey 1 media autoselect mode 11b Using same hardware and script but running FreeBSD 5.4, this card is associated immediately. What is happening when using FreeBSD 6.1-BETA2? Is there any problem with mode 11b and atheros driver? Our bridge is another PC running StarOS (www.stratos.com) with orinoco pccard (802.11b). This is working fine when using clients running FreeBSD 5.4, but we can't upgrade this stations clients to 6.1-BETA2. From FreeBSD 6.1-BETA2: # sysctl dev.ath dev.ath.0.%desc: Atheros 5212 dev.ath.0.%driver: ath dev.ath.0.%location: slot=8 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1186 subdevice=0x3a14 class=0x02 dev.ath.0.%parent: pci0 dev.ath.0.smoothing_rate: 95 dev.ath.0.sample_rate: 10 dev.ath.0.countrycode: 0 dev.ath.0.regdomain: 16 dev.ath.0.debug: 0 dev.ath.0.slottime: 20 dev.ath.0.acktimeout: 48 dev.ath.0.ctstimeout: 48 dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 2700 dev.ath.0.txantenna: 0 dev.ath.0.rxantenna: 1 dev.ath.0.diversity: 1 dev.ath.0.txintrperiod: 5 dev.ath.0.diag: 0 dev.ath.0.tpscale: 0 dev.ath.0.tpc: 0 dev.ath.0.monpass: 24 From FreeBSD 5.4 we have this: # sysctl dev.ath dev.ath.0.%desc: Atheros 5212 dev.ath.0.%driver: ath dev.ath.0.%location: slot=8 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1186 subdevice=0x3a14 class=0x02 dev.ath.0.%parent: pci0 Paulo Fragoso. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hi all.. Novice user having woes getting Atheros card up in FreeBSD 6.0
There is a problem with country code in DWL-AG530, you can solve setting country code, we can find instructions for this in: http://madwifi.org/wiki/Compatibility Our newest DWL-AG530 are working now on FreeBSD 5.4 and FreeBSD 6.0: FreeBSD 5.4 before load contry code: Jan 4 19:39:04 dl2 kernel: ath0: mem 0xee00-0xee00 irq 10 at device 8.0 on pci0 Jan 4 19:39:04 dl2 kernel: ath0: mac 5.9 phy 4.3 5ghz radio 3.6 Jan 4 19:39:04 dl2 kernel: ath0: unable to collect channel list from hal Jan 4 19:39:04 dl2 kernel: device_attach: ath0 attach returned 22 After set country code: Jan 11 15:10:19 dl2 kernel: ath0: mem 0xee00-0xee00 irq 10 at device 8.0 on pci0 Jan 11 15:10:19 dl2 kernel: ath0: mac 5.9 phy 4.3 5ghz radio 3.6 Jan 11 15:10:19 dl2 kernel: ath0: Ethernet address: 00:13:46:9a:29:18 Jan 11 15:10:19 dl2 kernel: ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 11 15:10:19 dl2 kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Jan 11 15:10:19 dl2 kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 11 15:10:19 dl2 kernel: ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Paulo Fragoso. Derek Evans wrote: I think the newest D-link DWL-AG530 must use the AR5213 chipset too. Before I got it I had done some checking and read somewhere that it used the AR5212, so I thought I'd be ok. When I tried it recently I got: FreeBSD rock 6.0-STABLE FreeBSD 6.0-STABLE #1: Sun Jan 22 10:45:11 EST 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/ROCK i386 ... ath0: mem 0xea00-0xea00 irq 11 at device 17.0 on pci0 ath0: unable to collect channel list from hal; regdomain likely 18 country code 0 device_attach: ath0 attach returned 22 I haven't tried Sam's patches yet. I'm assuming they're still current though. I have instructions for getting the patches, applying the patches, and testing them. I'll send them to you via BSDForums (since that's where they're saved). Can you point me to these instructions as well please? Yes, I already looked. :) -derek ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SATA RAID Controller (PCIe)
Hi, Are there any SATA RAID card controller for PCI Express bus working with FreeBSD 6.0-STABLE? Paulo. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Diskless /libexec/ld-elf.so.1: Cannot execute objects on /
Paulo Fragoso wrote: Hi, After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless machines didn't work correctly, many applications using dynamic libraries didn't start, this error was showed: /libexec/ld-elf.so.1: Cannot execute objects on / We found on all diskless machines had MNT_NOEXEC flags set on (fstatfs). After that we have changed rtld.c changed: Ops, all remote mount points defined with read-only on server has MNT_NOEXEC flag seted on the clients (diskless), is there a bug with fstatfs function? server: /usr/X11R6 -ro -network A.B.C.D -mask 255.255.255.0 client: A.B.C.S:/usr/X11R6 /usr/X11R6 nfs ro,tcp,nfsv3,-w=32768,-r=32768 0 0 On the cliente NFS the /usr/X11R6 has MNT_NOEXEC seted! Paulo Fragoso. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Diskless /libexec/ld-elf.so.1: Cannot execute objects on /
Hi,
After upgrade from FreeBSD 5.3 to FREEBSD_5_4 (cvs), our diskless
machines didn't work correctly, many applications using dynamic
libraries didn't start, this error was showed:
/libexec/ld-elf.so.1: Cannot execute objects on /
We found on all diskless machines had MNT_NOEXEC flags set on (fstatfs).
After that we have changed rtld.c changed:
--- rtld.c.orig Thu Dec 15 17:26:41 2005
+++ rtld.c Thu Dec 15 17:38:15 2005
@@ -1267,7 +1267,7 @@
close(fd);
return NULL;
}
- if (fs.f_flags & MNT_NOEXEC) {
+ if (fs.f_flags & MNT_NOEXEC && strcmp(fs.f_mntonname,"/") ) {
_rtld_error("Cannot execute objects on %s\n",
fs.f_mntonname);
close(fd);
return NULL;
Now, all diskless stations works fine.
Is there another solution for this case?
Thanks,
Paulo Fragoso.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Are there a make problem?
Hi, We are trying to create a jail with FreeBSD 5.3 but it's fails with this error: cc -O -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/games/fortune/strfile/strfile.c make: don't know how to make /j/usr/lib/libc.a. Stop *** Error code 2 We was using: export D=/j make world DESTDIR=$D After an advice from Jason DiCioccio we can make a jail successful: env DESTDIR=$D make world We have a similar problem with BATCH=YES using ports, after 5.2.1-RELEASE (not included) we are using: export BATCH=yes && make install instead BATCH=yes in main Makefile. Are there any problem with make? Paulo. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.6-RELEASE -> 4.5-RELENG
Oi, On Wed, 19 Jun 2002, Doug Barton wrote: > On Wed, 19 Jun 2002, Paulo Fragoso wrote: > > > On Wed, 19 Jun 2002, Alexandr Kovalenko wrote: > > > > > You also should update your MAKEDEV script with mergemaster. > > > And to sh MAKEDEV all again. Device minor/major numbers was changed with > > > ata(4) MFC. > > > > After we redid all following this steps: > > > > make buildworld > > make installworld > > make buildkernel KERNCONF=KERNEL6 > > make installkernel KERNCONF=KERNEL6 > > mergemaster -a > > cd /dev && sh MAKEDEV all > > mergemaster -a doesn't actually install anything for you. Did you go back > and install the new files by hand? Our /dev/MAKEDEV wasn't modified after first make installworld so we've decided rebuild everything again and to run mergemaster too (thanks to Alexandr Kovalenko). This way our MAKEDEV script is ok now and after run MAKEDEV all our CDROM device has returned to work fine. Thanks, Paulo. ps.: we was upgrading from 4.4-RELEASE to 4.6-RELEASE > > -- >"We have known freedom's price. We have shown freedom's power. > And in this great conflict, ... we will see freedom's victory." > - George W. Bush, President of the United States > State of the Union, January 28, 2002 > > Do YOU Yahoo!? > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Is wi with problems in RELENG_4_5?
We have already found same problem caused by conflicts using an ISA
pccard adpter, but this problema was a bit different we couldn't start the
traffic anyway. Now all works fine by 8 until 30 hours for this problem to
happen.
We've changed pccard for one new Avaya Wireless without firmeware upgrade
and we found same problem.
Our dmesg and pccard log is:
/kernel: FreeBSD 4.5-RELEASE-p4 #0: Mon May 6 10:28:58 BRT 2002
/kernel: Timecounter "i8254" frequency 1193182 Hz
/kernel: CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class
CPU)
/kernel: Origin = "GenuineIntel" Id = 0x660 Stepping = 0
/kernel:
Features=0x183f9ff
/kernel: real memory = 67108864 (65536K bytes)
/kernel: avail memory = 60424192 (59008K bytes)
/kernel: Preloaded elf kernel "kernel" at 0xc046e000.
/kernel: Pentium Pro MTRR support enabled
/kernel: md0: Malloc disk
/kernel: Using $PIR table, 7 entries at 0xc00f8740
/kernel: npx0: on motherboard
/kernel: npx0: INT 16 interface
/kernel: pcib0: on motherboard
/kernel: pci0: on pcib0
/kernel: pcib1: at device
1.0 on pci0
/kernel: pci1: on pcib1
/kernel: pci1: at 0.0 irq 11
/kernel: isab0: at device 7.0 on pci0
/kernel: isa0: on isab0
/kernel: atapci0: port 0xffa0-0xffaf at
device 7.1 on pci0
/kernel: ata0: at 0x1f0 irq 14 on atapci0
/kernel: uhci0: port
0xef80-0xef9f irq 10 at device 7.2 on pci0
/kernel: usb0: on uhci0
/kernel: usb0: USB revision 1.0
/kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
/kernel: uhub0: 2 ports with 2 removable, self powered
/kernel: chip1: port
0x5f00-0x5f0f at device 7.3 on pci0
/kernel: rl0: port 0xec00-0xecff mem
0xffafff00-0xffaf irq 11 at device 15.0 on pci0
/kernel: rl0: Ethernet address: 00:e0:4c:e2:14:76
/kernel: miibus0: on rl0
/kernel: rlphy0: on miibus0
/kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
/kernel: pci_cfgintr_search: linked (61) to configured irq 11 at 0:15:0
/kernel: pci_cfgintr: 0:16 INTA routed to irq 11
/kernel: pcic0: irq 11 at device 16.0 on
pci0
/kernel: pcic0: PCI Memory allocated: 0x4400
/kernel: pcic0: TI12XX PCI Config Reg: [pwr save][CSC parallel isa irq]
/kernel: pccard0: on pcic0
/kernel: orm0: at iomem 0xc-0xc7fff on isa0
/kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2
on isa0
/kernel: fdc0: FIFO enabled, 8 bytes threshold
/kernel: atkbdc0: at port 0x60,0x64 on isa0
/kernel: vga0: at port 0x3c0-0x3df iomem 0xa-0xb
on isa0
/kernel: sc0: at flags 0x100 on isa0
/kernel: sc0: VGA <16 virtual consoles, flags=0x300>
/kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
/kernel: sio0: type 16550A
/kernel: sio1: configured irq 3 not in bitmap of probed irqs 0
/kernel: ppc0: parallel port not found.
/kernel: DUMMYNET initialized (011031)
/kernel: IP packet filtering initialized, divert enabled, rule-based
forwarding enabled, default to accept, unlimited logging
/kernel: ad0: 4125MB [8940/15/63] at ata0-master
UDMA33
/kernel: Mounting root from ufs:/dev/ad0s1a
/kernel: pccard: card inserted, slot 0
/kernel: pccard: card removed, slot 0
/kernel: pccard: card inserted, slot 0
pccardd[50]: Card "Avaya Communication"("Avaya Wireless PC Card") [Version
01.01] [] matched "Avaya Communication" ("Avaya Wireless PC Card")
[(null)] [(null)]
squid[324]: Squid Parent: child process 327 started
/kernel: wi0: at port 0x240-0x27f irq 11 slot 0 on
pccard0
/kernel: wi0: Ethernet address: 00:02:2d:3f:82:77
pccardd[50]: wi0: Avaya Communication (Avaya Wireless PC Card) inserted.
pccard:wi0: Avaya Wireless PC Card inserted
pccardd[50]: pccardd started
Now in this router we are rebooting when it can't reach the wireless
network.
Thanks,
Paulo.
On Fri, 10 May 2002, Fred Clift wrote:
>
> I saw similar symptoms when I had either irq or io-range conflicts with a
> symbol card using the wi driver on my nortel emobility (rebadged Symbol
> la-3141) card. There is a section in the netbsd handbook that tells of
> such conflicts with their version of the wi driver and some suggested ways
> of fixing it.
>
> Honestly, I ended up giving up on my problem. (could get the symbol card
> to work fine by itself, but add a second pcmcia network card ed0 and
> neither would work right). I eventually installed netbsd on the 'wirless
> router'...
>
> Fred
>
>
> On Fri, 10 May 2002, Paulo Fragoso wrote:
>
> > Hi,
> >
> > We have got some wireless routers using lucent cards (WaveLAN/IEEE
> ...
> >
> > /kernel: wi0: xmit failed
> > /kernel: wi0: watchdog timeout
> > /kernel: wi0: init failed
> > /kernel: wi0: failed to allocate 1594 bytes on NIC
> > /kernel: wi0: tx buffer allocation failed
> > /kernel: wi0: failed to allocate 1594 bytes on NIC
> > /kernel: wi0: mgmt. buffer allocation failed
> > /kernel: wi0: timeout in wi_seek to 0/0; last
Re: Is wi with problems in RELENG_4_5?
There is another impotant point, when that card is frozen we try to restart using: pccardc power 0 0 and pccardc power 0 1 The card is turned off and turned on withou problems and using wicontrol -i wi0 there is signal like: Comms quality/signal/noise: [ 39 90 51 ] but any bit is sent or received. If we reomve the pccard from slot and put it again, it's detected and using wicontrol -i wi0 we can find signal but it doesn't send or receive any bit. Only rebooting (WITHOUT turn off that machine) all returns to work fine. We are thinking there is a problem related with software because only after reboot that card returns to work fine (without turn off the machine). Thanks, Paulo. On Fri, 10 May 2002, Michael Sierchio wrote: > Paulo Fragoso wrote: > > Hi, > > > > We have got some wireless routers using lucent cards (WaveLAN/IEEE > > 802.11), all works fine. Last week we had some problems with two routers > > (like broken cooler). On frist router we changed the hard disk to > > other disk which had installed 4.5-RELEASE this system was working fine > > too. Our problems started with second router which we had installed > > 4.5-RELEASE and had made world to RELENG_4_5, this system is reporting: > > > > /kernel: wi0: xmit failed > > /kernel: wi0: watchdog timeout > > /kernel: wi0: init failed > > /kernel: wi0: failed to allocate 1594 bytes on NIC > > /kernel: wi0: tx buffer allocation failed > > /kernel: wi0: failed to allocate 1594 bytes on NIC > > /kernel: wi0: mgmt. buffer allocation failed > > /kernel: wi0: timeout in wi_seek to 0/0; last status 4000 > > /kernel: wi0: timeout in wi_seek to 0/44; last status 4044 > > Firmware rev on the Lucent cards is.? > -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Is wi with problems in RELENG_4_5?
REV is 8.10 (WSU_810.exe). On Fri, 10 May 2002, Michael Sierchio wrote: > Paulo Fragoso wrote: > > Hi, > > > > We have got some wireless routers using lucent cards (WaveLAN/IEEE > > 802.11), all works fine. Last week we had some problems with two routers > > (like broken cooler). On frist router we changed the hard disk to > > other disk which had installed 4.5-RELEASE this system was working fine > > too. Our problems started with second router which we had installed > > 4.5-RELEASE and had made world to RELENG_4_5, this system is reporting: > > > > /kernel: wi0: xmit failed > > /kernel: wi0: watchdog timeout > > /kernel: wi0: init failed > > /kernel: wi0: failed to allocate 1594 bytes on NIC > > /kernel: wi0: tx buffer allocation failed > > /kernel: wi0: failed to allocate 1594 bytes on NIC > > /kernel: wi0: mgmt. buffer allocation failed > > /kernel: wi0: timeout in wi_seek to 0/0; last status 4000 > > /kernel: wi0: timeout in wi_seek to 0/44; last status 4044 > > Firmware rev on the Lucent cards is.? > -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: wi0 or isab0 trouble?
Hi, I've comited a little mistake. I've got a script install and its was changed one line: wicontrol -i wi0 -t 6 to wicontrol -t wi0 -t 6 Our suggestion is "wicontrol" report "invalid option" in cases like this. Excuse-me, Paulo. On Tue, 2 Jan 2001, Paulo Fragoso wrote: > Hi, > > We was using FreeBSD and WaveLAN without problems. But now we are trying > to use 4.2-20001219-STABLE and we are found some problems. We have got > one PII 350MHz (chiset 440 BX motherboard) working fine, but using some > old motherboards we get this error: > > wi0: device timeout > wi0: failed to allocate 1594 bytes on NIC > wi0: tx buffer allocation failed > wi0: failed to alloacte 1594 bytes on NIC > wi0: mgmt. buffer allocation failed > > That old motherboard has got the chipset VIA VT82C576M with a Pentium > 100MHz. Looking at result from dmesg there is a little difference: > > work->there are isab0 and isa0 at motherboard that works: > isab0: at device 7.0 on pci0 > isa0: on isab0 > > don't work-> there isn't isab0!!!: > isa0: on isab0 > > We've got another older motherboard (chipset intel TX) working fine with > FreeBSD 4.2-RELEASE, and we can found isab0 on dmesg: > isab0: at device 7.0 on pci0 > isa0: on isab0 > > Likely the wi0 require a isab0 (I think). Why when are we using FreeBSD > 4.2-STABLE we can't found a isab0 on old motherboard? Why don't wi0 works? > > We've installed FreeBSD 4.1-RELEASE on same VIA motherboard to test and > all works fine. But on that motherboard we can't found a isab0 with dmesg, > too. Are we thinking wrong? > > When we are using same motherboard (VIA VT82C576M) with FBSD 4.1-RELEASE > are all working fine? We've tested FBSD 4.2-RELEASE and > 4.2-20001219-STABLE and both don't work on this motherboard. > > Finally: Why are all versions tested of FreeBSD working fine using a 440BX > motherboard? > > Thanks, > Paulo Fragoso. > > -- >__O > _-\<,_ Why drive when you can bike? > (_)/ (_) > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Atapi CDRW
Hi, I'm using freebsd 3.4-RELEASE with CREATIVE CD-RW RW4224E: /kernel: wdc1: unit 0 (atapi): , removable, accel, dma, iordis /kernel: acd0: drive speed 4125KB/sec, 1860KB cache /kernel: acd0: supported read types: CD-R, CD-RW, CD-DA, packet track /kernel: acd0: supported write types: CD-R, CD-RW, test write /kernel: acd0: Audio: play, 255 volume levels /kernel: acd0: Mechanism: ejectable tray /kernel: acd0: Medium: no/blank disc inside, unlocked, lock protected I was burning my cds using wormcontrol, it was working fine. But now I've changed to 4.0-RELEASE and I'm having some problems. Some times the CDRW is detected this way: /kernel: ata1-master: timeout waiting for command=ef s=00 e=00 /kernel: acd0: CD-RW at ata1-master using BIOSPIO some times this way: /kernel: acd0: CD-RW at ata1-master using PIO4 And I'm losting several cds using burncd command, my drive freeze and only work after power cicle. I get this mesage when the CDRW freeze: /kernel: acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=00 /kernel: acd0: WRITE_BIG - HARDWARE ERROR asc=09 ascq=01 error=00 /kernel: acd0: REQUEST_SENSE command timeout - resetting /kernel: ata1: resetting devices .. device dissapeared! 1 ata1-master: timeout waiting to give command=ef s=90 e=20 /kernel: done /kernel: ata1-master: timeout waiting to give command=a0 s=90 e=20 /kernel: acd0: failure to send ATAPI packet command /kernel: acd0: failure to execute ATAPI packet command Is this problem solved in freebsd 4.0-STABLE? What is happening? Thanks, Paulo Fragoso. -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
