Re: Unable to install -stable snap via FTP
hi, there! On Sat, Oct 27, 2001 at 04:26:20PM -0400, Joe Clarke wrote: > I've been trying to install a -stable snapshot on a few of my machines so > that I get dirpref off the bat. However, everytime I try to install using > passive FTP from releng4.freebsd.org, it fails fetching the bin > distribution. What's weird is that when I go to Alt+F2, I don't see any > error messages, and it looks like bin transfered correctly (i.e. I see the > block size of the distribution at the end). > > When I go to Alt+F4, I see a kernel.GENERIC, but no kernel (not sure where > in the install process kernel should exist, though). I've tried this with > the 10/21, 10/26, and 10/27 snaps. Doing 4.4-RELEASE from passive FTP > works fine. > > Anyone else experiencing this? yes. if you are talking about sysinstall complaining it can't fetch distribution you can simply ignore those errors. (I do not know of any available fixes for this problem) /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: adding athlon xp to bsd.cpu.mk
On Mon, Oct 29, 2001 at 10:29:00AM -0800, matt wrote: > any one know if my 4.3 stable work with all AMD > processors, as well as with SMP enabled? Yes it will. I certifed 4.3 RELEASE (and thus 4.3-STABLE) on the SMP Thunder for AMD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: adding athlon xp to bsd.cpu.mk
any one know if my 4.3 stable work with all AMD processors, as well as with SMP enabled? == WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. == - Original Message - From: "David O'Brien" <[EMAIL PROTECTED]> To: "cameron grant" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, October 28, 2001 4:42 PM Subject: Re: adding athlon xp to bsd.cpu.mk > On Sun, Oct 28, 2001 at 02:06:00PM -, cameron grant wrote: > > my system with dual 1.1ghz durons identifies as: > > > > CPU: AMD Duron(tm) MP Processor (1110.94-MHz 686-class CPU) > > Origin = "AuthenticAMD" Id = 0x670 Stepping = 0 > > > > Features=0x383fbff > CMOV,PAT,PSE36,MMX,FXSR,SSE> > > AMD Features=0xc044<,AMIE,DSP,3DNow!> > > > > the entire "AMD Duron(tm) MP Processor" string appears to originate > > Wonder why you get the 'MP' and I don't: > > CPU: AMD Athlon(tm) Processor (1194.46-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x661 Stepping = 1 > Features=0x383fbff > AMD Features=0xc044<,AMIE,DSP,3DNow!> > > This is from my AMD pre-release Tyan Thunder Athon MP system that I > certified FreeBSD SMP support on. > > -- > -- David ([EMAIL PROTECTED]) > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Crash Using ogle
On Sunday 28 October 2001 05:40 pm, Chris BeHanna wrote: > I attempted to view a DVD with the ogle port (nice DVD menu > support), and I crashed my machine (4.4-STABLE, cvsup'd at > Fri Oct 19 01:08:36 EDT 2001). There was no crashdump, but the last > messages logged before the crash were: > > Oct 28 17:35:38 topperwein /kernel: ata1-master: too many segments in DMA > table Oct 28 17:36:37 topperwein /kernel: ata1-master: too many segments in > DMA table > > What does this mean, and how do I fix it? I've reported the same problem. It *seems* to involve the ATA driver (or at least that is what is being executed when my panic occurs). I filed my info under the following PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=31530 It's nice to know I'm not the only one having this problem. Heath To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Crash Using ogle
I attempted to view a DVD with the ogle port (nice DVD menu
support), and I crashed my machine (4.4-STABLE, cvsup'd at
Fri Oct 19 01:08:36 EDT 2001). There was no crashdump, but the last
messages logged before the crash were:
Oct 28 17:35:38 topperwein /kernel: ata1-master: too many segments in DMA table
Oct 28 17:36:37 topperwein /kernel: ata1-master: too many segments in DMA table
What does this mean, and how do I fix it?
This is on a system with the following hardware:
AMD 1.333 GHz T-bird
Gigabyte GA-7DX mobo (AMD 761 chipset)
ATI Radeon QD ("ViVo") video board
WD Caviar IDE hard drive on ata0-master using UDMA
Hitachi GD-2000 DVD-ROM on ata1-master using WDMA2
dmesg is attached.
--
Chris BeHanna
Software Engineer (Remove "bogus" before responding.)
[EMAIL PROTECTED]
I was raised by a pack of wild corn dogs.
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.4-STABLE #1: Thu Oct 25 21:41:34 EDT 2001
[EMAIL PROTECTED]:/usr/obj.k7/usr/src/sys/TOPPERWEIN
Timecounter "i8254" frequency 1193182 Hz
CPU: AMD Athlon(tm) Processor (1333.39-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x642 Stepping = 2
Features=0x183f9ff
AMD Features=0xc044<,AMIE,DSP,3DNow!>
real memory = 268369920 (262080K bytes)
config> di sn0
config> di lnc0
config> di le0
config> di ie0
config> di cs0
config> q
avail memory = 256630784 (250616K bytes)
Preloaded elf kernel "kernel" at 0xc0462000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc046209c.
Preloaded elf module "splash_bmp.ko" at 0xc04620ec.
Preloaded elf module "vesa.ko" at 0xc0462190.
Preloaded splash_image_data "/boot/daemon_freebsd-1.bmp" at 0xc046222c.
VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc0414262 (122)
VESA: ATI RADEON
Pentium Pro MTRR support enabled
md0: Malloc disk
splash_bmp: No appropriate video mode found
module_register_init: MOD_LOAD (splash_bmp, c040c7b8, 0) error 19
Using $PIR table, 10 entries at 0xc00fddb0
apm0: on motherboard
apm: found APM BIOS v1.2, connected at v1.2
npx0: on motherboard
npx0: INT 16 interface
pcib0: on motherboard
pci0: on pcib0
pcib1: at device 1.0 on pci0
pci1: on pcib1
pci1: at 5.0 irq 10
isab0: at device 7.0 on pci0
isa0: on isab0
atapci0: port 0xb400-0xb40f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: port 0xb800-0xb81f irq 11 at device 7.2 on pci0
usb0: on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: port 0xbc00-0xbc1f irq 11 at device 7.3 on pci0
usb1: on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
chip1: at device 7.4 on pci0
dc0: <82c169 PNIC 10/100BaseTX> port 0xd000-0xd0ff mem 0xdb00-0xdbff irq 10 at
device 12.0 on pci0
dc0: Ethernet address: 00:a0:cc:d4:0a:6d
miibus0: on dc0
ukphy0: on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd400-0xd47f mem 0xdb002000-0xdb00207f
irq 5 at device 13.0 on pci0
xl0: Ethernet address: 00:10:5a:00:a9:20
miibus1: on xl0
xlphy0: <3Com internal media interface> on miibus1
xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pcm0: port 0xd800-0xd83f irq 11 at device 14.0 on pci0
ahc0: port 0xdc00-0xdcff mem 0xdb003000-0xdb003fff
irq 11 at device 15.0 on pci0
aic7896/97: Ultra2 Wide Channel A, SCSI Id=7, 32/255 SCBs
ahc1: port 0xe000-0xe0ff mem 0xdb004000-0xdb004fff
irq 11 at device 15.1 on pci0
aic7896/97: Ultra2 Wide Channel B, SCSI Id=7, 32/255 SCBs
orm0: at iomem 0xc-0xcbfff,0xcc000-0xcc7ff on isa0
fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: at port 0x60,0x64 on isa0
atkbd0: flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
ppc0: at port 0x378-0x37f flags 0x21 on isa0
ppc0: Generic chipset (NIBBLE-only) in NIBBLE mode
ppbus0: IEEE1284 device found /NIBBLE/ECP
Probing for PnP devices on ppbus0:
ppbus0: MLC,PCL,PML
lpt0: on ppbus0
lpt0: Polled port
ppi0: on ppbus0
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
sio1: <16550A-compatible COM port> at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
unknown: can't assign resources
IP pa
Re: pathname length over NFS
Chad R. Larson <[EMAIL PROTECTED]> wrote: > Why is there an overlap > between the recommended codes in sysexits(3) and "/usr/include/errno.h"? They serve different purposes, and are used for different things, so there shouldn't be a conflict. The errno values are used as return values from syscalls and library functions. They are _not_ used for program exit codes. Unfortunately, some programs print numerical errno values because they're too stupid (or too lazy) to use perror() or strerror() or some similar way to display a readable error string. Normally, the user should not need to care about errno numbers at all. They are for programmers. The sysexits(3) values were originally intended as a way to communicate between programs: When sendmail calls an external program (e.g. mail_local or procmail), it checks the exit code to find out if everything is alright, or if a transient problem occured, or if something went out of resources, or if a fatal error occured. Depending on that, sendmail deletes the mail, or spools it locally for another delivery attempt at a later time, or bounces it back with an appropriate error message. Other, non mail-related tools use sysexits(3) values, too, to further classify the result beyond the traditional 0/ok and 1/failure, so that scripts and other programs have a better chance to do sensible things when something went wrong. This is a good thing, IMO. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pathname length over NFS
At 11:02 PM 10/21/01 +0200, Oliver Fromme wrote: > > The system message for error number 71 is: > > Too many levels of remote in path > > > > install -c -o root -g wheel -m 444 libcom_err_p.a /usr/lib > > *** Error code 71 > >The install tool doesn't use errno numbers for exit codes, >but it uses sysexit values. See the sysexits(3) manpage: I must apologize to the list for wasting it's time. This turned out to be cockpit error. The problem was I didn't sync the "/etc/defaults/make.conf" files between the server and the client before trying the "make install". The result was the client attempted to install profiled libraries that weren't built on the server. My only defense is the misleading error code. Why is there an overlap between the recommended codes in sysexits(3) and "/usr/include/errno.h"? -crl -- Chad R. Larson (CRL22)[EMAIL PROTECTED] Eldorado Computing, Inc. 602-604-3100 5353 North 16th Street, Suite 400 Phoenix, Arizona 85016-3228 -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Nasty USB + SMBFS interaction
Pretty simple problem to replicate: Compile the following into your kernel: options NETSMB #SMB/CIFS requester options NETSMBCRYPTO#encrypted password support for SMB # mchain library. It can be either loaded as KLD or compiled into kernel options LIBMCHAIN #mbuf management library # Kernel side iconv library options LIBICONV options SMBFS Plug a Microsoft USB mouse in and try to mount an SMB share after the USB mouse has detected. This will return a "no buffer space available" message. All other networking functions are unimpaired. Tested this with all but umass compiled directly into the kernel, and no modules. I will be able to do further tests on monday, e.g. does an existing share stop responding when the mouse is plugged in? Disconnecting the mouse does not solve the issue; shares remain non-mountable. Using 4.4-STABLE cvsuped to Friday, and smbfs userland version 1.4.1, from ports, an EtherExpress Pro 10/100, and both Windows 98 and Windows 2000 AS servers. Let me know if there is anything more I should look for and report. Brad // -- http://www.BRAD-X.com/ -- // To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
"VIA '686b southbridge fix applied" & -stable
I found this in the archives: http://groups.google.com/groups?th=4a63e650c2dd8fc5 Oct 11 11:55:53 ws-ilmar /boot/kernel/kernel: atapci0: VIA '686b \ southbridge fix applied A couple questions: 1) Is this in checked into -stable? 2) What does the fix do? 3) Would it be safe to put a Soundblaster Live in a FreeBSD box with a VIA 686B southbridge with (or w/o) this fix? BTW, I own an ASUS A7M266 motherboard which has the VIA southbridge. I'm contemplating a new soundcard and considering my options. Thanks, Randall -- Randall Hopper [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: dirpref gives massive performance boost
On 2001-Oct-27 21:48:38 -0500, Glenn Johnson <[EMAIL PROTECTED]> wrote: >I figured out what I did wrong. In the instructions above it says to >edit 'etc/fstab'; I edited '/etc/fstab' instead. A very easy mistake to make. It can get very confusing when you have multiple, almost-identical partitions mounted. I'm glad that you sorted it out >Also, the line in the instructions that says > >'0,ad(0,b)/boot/loader' should be > >'0:ad(0,b)/boot/loader' That's what I get for writing from memory. Luckily boot0 reports the syntax so hopefully this didn't cause you too much confusion. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Unable to install -stable snap via FTP
Nope , this is happening during local FTP install also. IMO this is sysinstall's problem. > I was thinking about this some more. Stephen Hilton said just to say "No" > when it asks to try and refetch the dist, and that works, so we know it's > downloading everything correctly. Also, you don't get this when you point > sysinstall at ftp.freebsd.org. I didn't break a sniffer out, but perhaps > there's a problem with the releng4.freebsd.org FTP server not Ack'ing the > last packet or something. It would explain why this problem is occuring > for only -stable snaps, and not any of the releases. Just a thought. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: adding athlon xp to bsd.cpu.mk
On Sun, 28 Oct 2001, Maxim Sobolev wrote: >AFAIK, not quite. The core name is Palomino and there are three >processors based on it: Athlon XP, Athlon MP and Duron. The AMD Athlon XP, MP, and mobile Athlon4 are based on the Palomino core. The 1Ghz+ Durons are based on the Morgan core, a Palomino derivative with less cache. The previous generations of Athlons were based on the K7, K75, and Thunderbird cores. What is a bit misleading about the naming of AMD's processors is that at present they are all SMP capable. You can use dual Thunderbirds or Durons or XPs without a problem, generally. In fact, you can even use processors of different clock speeds in an SMP configuration fairly successfully, though it is not recommended. What you pay for when you buy Athlon MP processors is AMD's SmartMP technology. SmartMP includes a more advanced cache coherency protocol and an inter-processor "snoop" bus that allows the processors to exchange data from their caches instead of going directly to main memory all the time. -- "Never put off until tomorrow what you can do today. There might be a law against it by that time." -- /usr/games/fortune, 07/30/2001 Brandon D. Valentine To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: adding athlon xp to bsd.cpu.mk
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>how about the following patch (untested) regarding the newer athlon xp
>processor type ? if needed, I could submit a PR.
AthlonXP is same as AthlonMP. It's better of the name "palomino",
isn't it? (But "morgan" Duron will have same feature such as SSE.)
What is the best name of the AMD's CPU core that can use SSE?
>Index: bsd.cpu.mk
>===
>RCS file: /home/ncvs/src/share/mk/bsd.cpu.mk,v
>retrieving revision 1.2.2.4
>diff -u -r1.2.2.4 bsd.cpu.mk
>@@ -28,8 +30,10 @@
>
> .if !defined(NO_CPU_CFLAGS) || !defined(NO_CPU_COPTFLAGS)
> . if ${MACHINE_ARCH} == "i386"
>-. if ${CPUTYPE} == "k7"
>+. if ${CPUTYPE} == "xp"
> _CPUCFLAGS = -march=k6# gcc doesn't support athlon yet, but it will
>+. elif ${CPUTYPE} == "k7"
>+_CPUCFLAGS = -march=k6# gcc doesn't support athlon yet, but it will
> . elif ${CPUTYPE} == "k6-2"
> _CPUCFLAGS = -march=k6
> . elif ${CPUTYPE} == "k6"
My dual AthlonXP is offen better performance at "-mcpu=i686" than "-mk6".
(gcc 2.95.3)
My dual AthlonXP's WWW page(in Japanese,sorry):
http://kobe1995.net/~kaz/FreeBSD/AthlonDual.html
Thank you & sorry for my poor English.
--
NAKAMURA Kazushi@KOBE
- Break the hate chain. No more kill!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
