Re: em and bge driver MPSAFE?
Mipam wrote this message on Wed, May 11, 2005 at 16:39 +0200: Perhaps lame to ask, But are the em and bge driver MPSAFE? I couldn't find notes about being mpsafe in the man pages of these drivers? I was about to point you to: http://www.freebsd.org/projects/busdma/ But realized that you probably wanted status on 5.x, and not HEAD... a quick look at the code shows that both em and bge are MPSAFE... I can tell because of no references to Giant or GIANT, and that it using XX_LOCK and has functions ending in _locked in them... Maybe we need to expand the busdma project to include which driver status for 5.x and HEAD? -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
snd_via8233 problems on 5.4-STABLE WAS: Re: CMI9761 soundchip
On Sun, May 22, 2005 at 12:53:20PM +0300, Vladimir Terziev wrote: i have ASRock motherboard with CMI9761 sound chip, same as you. Also i have the same problem with FreeBSD 5.4-R as you :( Did you find some solution? No. If I load snd_via8233 via loader.conf, it will not set all volumes to 75:75 (maybe it bails out at ogain which it can't find), so speaker is left at 0:0 wich results in this terrible beep. Loading snd_via8233 afterwards by hand works, though. The only thing I then get in /var/log/messages is: pcm0: VIA VT8237 port 0xd000-0xd0ff irq 22 at device 17.5 on pci0 pcm0: Unknown AC97 Codec (id = 0x434d4983) (this is ASRock K7UPGRADE-880/A/ASR-Board) Patches eg to snd_via8233 are welcome :-) Regards, Holger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
usb-mouse initialization timing on 5.4-STABLE ?
Hello, since my last upgrade (about a week ago) the system sometimes won't recognise my usb-mouse during boot.(*) Is it possible that this is a timing issue, ie usb- initialisation and mouse-initialization have a race-condition here? Replugging usb-mouse does help, though. (*) unfortunately this also coincides with changing the mainboard from ASRock K7VT2/SA/LAN/ASRK to K7UPGRADE-880/A/ASR :-( Regards, Holger Kipp dmesg (where initialization worked) below. Copyright (c) 1992-2005 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 5.4-STABLE #8: Sat May 21 14:47:17 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KATRIN ACPI APIC Table: A M I OEMAPIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Duron(tm) (1300.06-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x671 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc040AMIE,DSP,3DNow! real memory = 536543232 (511 MB) avail memory = 515383296 (491 MB) ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 0.3 irqs 0-23 on motherboard npx0: math processor on motherboard npx0: INT 16 interface acpi0: A M I OEMRSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: VIA KT880 host to PCI bridge mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) atapci0: VIA 6420 SATA150 controller port 0xd800-0xd8ff,0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00-0xec07 irq 20 at device 15.0 on pci0 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 atapci1: VIA 8237 UDMA133 controller port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 uhci0: VIA 83C572 USB controller port 0xc000-0xc01f irq 21 at device 16.0 on pci0 usb0: VIA 83C572 USB controller 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: VIA 83C572 USB controller port 0xc400-0xc41f irq 21 at device 16.1 on pci0 usb1: VIA 83C572 USB controller 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 uhci2: VIA 83C572 USB controller port 0xc800-0xc81f irq 21 at device 16.2 on pci0 usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: VIA 83C572 USB controller port 0xcc00-0xcc1f irq 21 at device 16.3 on pci0 usb3: VIA 83C572 USB controller on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: serial bus, USB at device 16.4 (no driver attached) isab0: PCI-ISA bridge at device 17.0 on pci0 isa0: ISA bus on isab0 pci0: multimedia, audio at device 17.5 (no driver attached) vr0: VIA VT6102 Rhine II 10/100BaseTX port 0xd400-0xd4ff mem 0xfebffc00-0xfebffcff irq 23 at device 18.0 on pci0 miibus0: MII bus on vr0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:0b:6a:c0:00:ce acpi_button0: Power Button on acpi0 fdc0: floppy drive controller (FDE) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: ECP parallel printer port port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: Parallel port bus on ppc0 ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: HEWLETT-PACKARD DESKJET 640C MLC,PCL,PML plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ums0: vendor 0x1241 product 0x1122, rev 1.00/1.00, addr 2, iclass 3/1 ums0: 5
Re: snd_via8233 problems on 5.4-STABLE WAS: Re: CMI9761 soundchip
On Sun, May 22, 2005 at 01:39:48PM +0300, Vladimir Terziev wrote:
Currently i have the same situation. pcm driver says:
pcm0: Unknown AC97 Codec (id = 0x434d4983)
The id 0x434d4983 is CMI9761, but it seems the kernel doesn't know
nothing about it :(
This could be changed simply by
--- ac97.c.orig Sun May 22 13:18:03 2005
+++ ac97.c Sun May 22 13:19:59 2005
@@ -156,6 +156,7 @@
{ 0x43525940, 0x07, 0, CS4201,0 },
{ 0x43525958, 0x07, 0, CS4205,0 },
{ 0x43525960, 0x07, 0, CS4291A, 0 },
+ { 0x434d4983, 0x00, 0, CMI9761, 0 },
{ 0x434d4961, 0x00, 0, CMI9739, 0 },
{ 0x434d4941, 0x00, 0, CMI9738, 0 },
{ 0x43585421, 0x00, 0, HSD11246, 0 },
but I doubt that this will really help, because the CMI9761
also supports 5.1-Sound, at least according to alsa-changes:
http://alsa.mirror.fr/kernel-patches/mm/3118.patch
so some additional handling of specific bits is presumably needed.
Regards,
Holger Kipp
On Sun, 22 May 2005 12:33:50 +0200
Holger Kipp [EMAIL PROTECTED] wrote:
On Sun, May 22, 2005 at 12:53:20PM +0300, Vladimir Terziev wrote:
i have ASRock motherboard with CMI9761 sound chip, same as you.
Also i have the same problem with FreeBSD 5.4-R as you :(
Did you find some solution?
No. If I load snd_via8233 via loader.conf, it will not set all
volumes to 75:75 (maybe it bails out at ogain which it can't
find), so speaker is left at 0:0 wich results in this terrible
beep.
Loading snd_via8233 afterwards by hand works, though.
The only thing I then get in /var/log/messages is:
pcm0: VIA VT8237 port 0xd000-0xd0ff irq 22 at device 17.5 on pci0
pcm0: Unknown AC97 Codec (id = 0x434d4983)
(this is ASRock K7UPGRADE-880/A/ASR-Board)
Patches eg to snd_via8233 are welcome :-)
Regards,
Holger
___
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 and [EMAIL PROTECTED]
Would it be possible to force the mailing list software to rename recipient header freebsd-stable@freebsd.org to [EMAIL PROTECTED] or vice versa and then remove duplicates? I mean it seems like half the people on the list use freebsd-stable@freebsd.org address and the other half [EMAIL PROTECTED] A lot of times people manage to add the missing version of the list address to their reply to someone's post and I (along with the rest of the list readers) end up getting the same message twice. It's bad enough when you get the same message twice if you get it both via pm and list, but getting two copies of the same post via list is just stupid. Any chance of having something done to change this? -- Tuomo ... Q: How many hardware engineers does it take to change a lightbulb? A: None. We'll fix it in software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: snd_via8233 problems on 5.4-STABLE WAS: Re: CMI9761 soundchip
On Sun, May 22, 2005 at 01:35:46PM +0200, Holger Kipp wrote:
On Sun, May 22, 2005 at 01:39:48PM +0300, Vladimir Terziev wrote:
Currently i have the same situation. pcm driver says:
pcm0: Unknown AC97 Codec (id = 0x434d4983)
The id 0x434d4983 is CMI9761, but it seems the kernel
doesn't know nothing about it :(
This could be changed simply by
--- ac97.c.orig Sun May 22 13:18:03 2005
+++ ac97.c Sun May 22 13:19:59 2005
@@ -156,6 +156,7 @@
{ 0x43525940, 0x07, 0, CS4201,0 },
{ 0x43525958, 0x07, 0, CS4205,0 },
{ 0x43525960, 0x07, 0, CS4291A, 0 },
+ { 0x434d4983, 0x00, 0, CMI9761, 0 },
{ 0x434d4961, 0x00, 0, CMI9739, 0 },
{ 0x434d4941, 0x00, 0, CMI9738, 0 },
{ 0x43585421, 0x00, 0, HSD11246, 0 },
Yes, that helps with recognizing, but not with the anoying tone.
# kldload snd_via8233
pcm0: VIA VT8237 port 0xd000-0xd0ff irq 22 at device 17.5 on pci0
pcm0: C-Media Electronics CMI9761 AC97 Codec
# kldunload snd_via8233
= loud xHz-tone.
i have ASRock motherboard with CMI9761 sound chip, same as you.
Also i have the same problem with FreeBSD 5.4-R as you :(
Did you find some solution?
No. If I load snd_via8233 via loader.conf, it will not set all
volumes to 75:75 (maybe it bails out at ogain which it can't
find), so speaker is left at 0:0 wich results in this terrible
beep.
Loading snd_via8233 afterwards by hand works, though.
The only thing I then get in /var/log/messages is:
pcm0: VIA VT8237 port 0xd000-0xd0ff irq 22 at device 17.5 on pci0
pcm0: Unknown AC97 Codec (id = 0x434d4983)
(this is ASRock K7UPGRADE-880/A/ASR-Board)
Patches eg to snd_via8233 are welcome :-)
Regards,
Holger
___
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]
Highpoint HPT371 support (kern/59624)
Hi, Why is kern/59624 still open? It's about 1,5 years old. Would someone please commit it? Or, if it cannot be commited, please tell me why. If any information is missing (pcicon -lv output, verbose dmesg or whatever), I'd be happy to provide it. The patch in that PR brings support for the Highpoint HPT371 ATA133 controller to FreeBSD 4-stable (it's supported in FreeBSD 5 for a long time already). The patch is fairly trivial, and I'm running 4.x with that patch for almost two years, using various devices connected to my HPT371 (a DVD- ROM drive, a DVD-R/W recorder, several UDMA harddisks using hot-swap via atacontrol detach/attach). Zero problems so far, except that I have to merge the patch each time I update my world. :-) Thank you very much. Best 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. I invented Ctrl-Alt-Delete, but Bill Gates made it famous. -- David Bradley, original IBM PC design team ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[4.11-STABLE] sporatic directory corruption with unionfs ...
I have 6 servers in place right now, with the 6th being a brand new Intel 1U box, using a 3Ware 9500 controller to do RAID5 for 3xSATA drives ... yesterday, for the first time, I've started to get a sort of file system corruption that I've never seen before ... basically, it looks like the directory entries are getting corrupted, but the files themselves are fine ... Basically, I have a jail, with /usr in the jail being a unionfs from a template ... so: mount_union -b /template/usr /jail/usr in the template, there is a directory /usr/local/cyrus/bin, for instance ... the binaries under /usr/local/cyrus/bin are literally disappearing, as if someone were entring that directory and doing a 'rm' of those files ... I have a serial console attached to this server, and there are no errors being reported by the operating system ... tw_cli is showing that drives and unit are both functioning properly ... so I can find no reasons for the apparent corruption ... I just brought the server down to single user mode, and umounted everything so that I could do an fsck on the file system itself, and *its* checking as being clean ... its still running though, so there may be something at the end ... When I first noticed this, yesterday, the server had been running 11 days, and nothing in /var/log/messages to indicate a problem ... today, after 24hrs, its done it again, and again, no errors being generated anywhere to indicate a problem ... All the other 5 servers are running SCSI ... but unless there is a bug in the 9500 driver, I can't see it being hardware related ... I've kinda always expected something like this might happen with unionfs as a result of the server crashing, but not when its running fine ... I don't know what else to add to this, unfortunately, since neither the hardware, or the operating system, seem to want to give anything up :( The OS is from April 11th, so is relatively recent ... Any suggestions/ideas on what else to look at would be much appreciated ... Thank you ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[4.11-STABLE] sporatic directory corruption with unionfs ...
I have 6 servers in place right now, with the 6th being a brand new Intel 1U box, using a 3Ware 9500 controller to do RAID5 for 3xSATA drives ... yesterday, for the first time, I've started to get a sort of file system corruption that I've never seen before ... basically, it looks like the directory entries are getting corrupted, but the files themselves are fine ... Basically, I have a jail, with /usr in the jail being a unionfs from a template ... so: mount_union -b /template/usr /jail/usr in the template, there is a directory /usr/local/cyrus/bin, for instance ... the binaries under /usr/local/cyrus/bin are literally disappearing, as if someone were entring that directory and doing a 'rm' of those files ... I have a serial console attached to this server, and there are no errors being reported by the operating system ... tw_cli is showing that drives and unit are both functioning properly ... so I can find no reasons for the apparent corruption ... I just brought the server down to single user mode, and umounted everything so that I could do an fsck on the file system itself, and *its* checking as being clean ... its still running though, so there may be something at the end ... When I first noticed this, yesterday, the server had been running 11 days, and nothing in /var/log/messages to indicate a problem ... today, after 24hrs, its done it again, and again, no errors being generated anywhere to indicate a problem ... All the other 5 servers are running SCSI ... but unless there is a bug in the 9500 driver, I can't see it being hardware related ... I've kinda always expected something like this might happen with unionfs as a result of the server crashing, but not when its running fine ... I don't know what else to add to this, unfortunately, since neither the hardware, or the operating system, seem to want to give anything up :( The OS is from April 11th, so is relatively recent ... Any suggestions/ideas on what else to look at would be much appreciated ... Thank you ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions 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]
can't assign requested address with ntpd on 5-STABLE
On 5-STABLE, when I try to start ntpd, I get the following error: bind() fd 7, family 28, port 123, addr fe80:1::2a0:c9ff:fec8:ea25, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address I've used netstat to check and nothing else is on that port (other than sshd, there is nothing else on the box). My ntp.conf line only has one line server time-a.nist.gov. All other configuration for ntpd is the default. I googled for this error and got several hits. It was suggested to add the line disable auth to ntp.conf. But in this case I still received the same error. I'm am running a recent 5-STABLE box (built yesterday). The kernel is equivalant to GENERIC with the exception that I've commented out the I486_CPU and i586_CPU lines. Anyone else seen this recently. Richard Coleman [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell PowerEdge 1855
Hi Doug, Sorry for taking so long to reply on this, been on 3 weeks leave... On Fri, 8 Apr 2005, Doug White wrote: On Wed, 6 Apr 2005, Carl Makin wrote: The boot sequence will hang if the USB drive is attached at boot. There It seems to be acting like Uthe USB controller isn't getting interrupts. Does the problem recur on the installed system? Yes it did however that chassis and the servers were a test loaner and have been returned. We have decided to go with the 1855 though (our windows guy was *very* enthusiastic about them) and when they arrive I'll run the tests you suggested. Thanks! so now i'm testing one too :-), any nice things to say about this blade? while trying out the scsi the blade panics :-) and as to cpu/memory power, it seems to be slower than the pe-1750 danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Syntax Error in Kernel
I'm trying to add support for my Palm to my Freebsd 5-Stable box. I have found the following web page which describes what kernel options need to be present. http://www.thedotin.net/maillists/coldsync-hackers/msg01954.html It lists the following options has being required. pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device usb # USB Bus (required) device uvisor device ucom However when I run config on my kernel, I get a syntax error on the line that adds ppp. Anyone hav any ideas as to why this might be happening? Thanks. Nathan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell PowerEdge 1855
Hi Doug, Sorry for taking so long to reply on this, been on 3 weeks leave... On Fri, 8 Apr 2005, Doug White wrote: On Wed, 6 Apr 2005, Carl Makin wrote: The boot sequence will hang if the USB drive is attached at boot. There It seems to be acting like Uthe USB controller isn't getting interrupts. Does the problem recur on the installed system? Yes it did however that chassis and the servers were a test loaner and have been returned. We have decided to go with the 1855 though (our windows guy was *very* enthusiastic about them) and when they arrive I'll run the tests you suggested. Thanks! so now i'm testing one too :-), any nice things to say about this blade? while trying out the scsi the blade panics :-) and as to cpu/memory power, it seems to be slower than the pe-1750 danny nothing like talking to oneself :-) i disabled the mirrowing, and now the disk io is nice, and more importanly, the system does not panic, i guess the mpt/(aka da0: DELL VIRTUAL DISK IM 1998) needs some work still :-) danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Syntax Error in Kernel
Hi, Nathan, On Sun, May 22, 2005 at 02:46:22PM +, Nathan Mace wrote: I'm trying to add support for my Palm to my Freebsd 5-Stable box. I have found the following web page which describes what kernel options need to be present. http://www.thedotin.net/maillists/coldsync-hackers/msg01954.html It lists the following options has being required. pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device usb # USB Bus (required) device uvisor device ucom However when I run config on my kernel, I get a syntax error on the line that adds ppp. Anyone hav any ideas as to why this might be happening? Thanks. I think you generally want device ppp and device tun on 5-STABLE boxes, the pseudo-device ppp 1 has gone long ago... Also, the examples in sys/[ARCH]/conf/GENERIC would be helpful for reference. You may obtain a more detailed list by running make LINT under the conf directory. For descriptions of kernel options, check out the NOTES files found in architecture dependent conf directories, and sys/conf. Cheers, -- Xin LI delphij frontfree net http://www.delphij.net/ See complete headers for GPG key and other information. pgpIsQgbV98ld.pgp Description: PGP signature
hw.ata.atapi_dma in 5.4-RELEASE-p1
I am unable to get my DVD or CD drives out of PIO4 mode on two machines. One has an ICH3 controller, the other is Nforce2 based. When I put hw.ata.atapi_dma=1 in /boot/loader.conf and reboot, I'm still stuck in PIO4. What am I doing wrong? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Syntax Error in Kernel
That seems to have done it. Thanks. I had looked in the GENERIC and NOTES file, and noticed that those options didn't appear, but I couldn't find anything that said they were no long used like that, and I couldn't find anything that told me what to use in their place. Thanks for the help. Nathan On May 22, 2005, at 11:20 AM, Xin LI wrote: Hi, Nathan, On Sun, May 22, 2005 at 02:46:22PM +, Nathan Mace wrote: I'm trying to add support for my Palm to my Freebsd 5-Stable box. I have found the following web page which describes what kernel options need to be present. http://www.thedotin.net/maillists/coldsync-hackers/msg01954.html It lists the following options has being required. pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device usb # USB Bus (required) device uvisor device ucom However when I run config on my kernel, I get a syntax error on the line that adds ppp. Anyone hav any ideas as to why this might be happening? Thanks. I think you generally want device ppp and device tun on 5-STABLE boxes, the pseudo-device ppp 1 has gone long ago... Also, the examples in sys/[ARCH]/conf/GENERIC would be helpful for reference. You may obtain a more detailed list by running make LINT under the conf directory. For descriptions of kernel options, check out the NOTES files found in architecture dependent conf directories, and sys/conf. Cheers, -- Xin LI delphij frontfree nethttp://www.delphij.net/ See complete headers for GPG key and other information. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: drive failure during rebuild causes page fault
You need to overwrite the metadata (se above) which are located in different places again depending on metadata format. So where is it located with the sil3114 controler? (same as 3112, but with 4 ports...) On Sun, May 22, 2005 at 12:45:05AM +0200, Søren Schmidt wrote: Depends on what BIOS you have on there, several exists for the SiI chips, -current or mkIII would tell you which. Just null out the last 63 sectors on the disks and you should be fine since all possible formats are in that range... I know how to do this using dd from the start of the disk. How do I do this at the end of the disk? -- Joe Rhett senior geek meer.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: drive failure during rebuild causes page fault
On 22/05/2005, at 18:11, Joe Rhett wrote: You need to overwrite the metadata (se above) which are located in different places again depending on metadata format. So where is it located with the sil3114 controler? (same as 3112, but with 4 ports...) On Sun, May 22, 2005 at 12:45:05AM +0200, Søren Schmidt wrote: Depends on what BIOS you have on there, several exists for the SiI chips, -current or mkIII would tell you which. Just null out the last 63 sectors on the disks and you should be fine since all possible formats are in that range... I know how to do this using dd from the start of the disk. How do I do this at the end of the disk? man dd ? :) you need to get the size of the disk in sectors (hint atacontrol) then you do dd if=/dev/zero of=/dev/adN oseek=(size-63) - Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hw.ata.atapi_dma in 5.4-RELEASE-p1
On Sunday, 22. May 2005 17:29, Janet Sullivan wrote: I am unable to get my DVD or CD drives out of PIO4 mode on two machines. One has an ICH3 controller, the other is Nforce2 based. When I put hw.ata.atapi_dma=1 in /boot/loader.conf and reboot, I'm still stuck in PIO4. What am I doing wrong? The drives probably don't support any UDMA modes. WDMA modes aren't enabled for atapi devices because there's a very large number of devices which don't implement them right or not at all, yet claim to support them. You can enable whatever DMA modes those drives support with the atacontrol utility after the kernel has booted up. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpqUzN9MX1Hu.pgp Description: PGP signature
hw.ata.atapi_dma in 5.4-RELEASE-p1
When I put hw.ata.atapi_dma=1 in /boot/loader.conf and reboot, I'm still stuck in PIO4. What am I doing wrong? The drives probably don't support any UDMA modes. WDMA modes aren't enabled for atapi devices because there's a very large number of devices which don't implement them right or not at all, yet claim to support them. That was it. The drives only support WDMA modes. Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hw.ata.atapi_dma in 5.4-RELEASE-p1
On Sun, May 22, 2005 at 08:29:58AM -0700, Janet Sullivan wrote: I am unable to get my DVD or CD drives out of PIO4 mode on two machines. One has an ICH3 controller, the other is Nforce2 based. When I put hw.ata.atapi_dma=1 in /boot/loader.conf and reboot, I'm still stuck in PIO4. What am I doing wrong? Have you tried something like atacontrol mode 1 UDMA6 UDMA6 to change the mode to the highest values possible? I have katrin# atacontrol info 1 Master: acd0 HL-DT-ST DVDRAM GSA-4163B/A102 ATA/ATAPI revision 5 Slave: acd1 HL-DT-ST RW/DVD GCC-4120B/2.01 ATA/ATAPI revision 0 katrin# atacontrol info 0 Master: ad0 SAMSUNG SP1614N/TM100-30 ATA/ATAPI revision 7 Slave: ad1 SAMSUNG SP0802N/TK100-24 ATA/ATAPI revision 7 with katrin# atacontrol mode 1 Master = UDMA33 Slave = PIO4 after boot and end up with katrin# atacontrol mode 1 UDMA6 UDMA6 Master = UDMA33 Slave = WDMA2 Usually I only use acd0, so I didn't care (real life runs at a higher priority g right now). Regards, Holger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 forgets some of my users
Stripping -bugs and -current cc; this applies to -stable and isn't in reference to an existing PR. On Sat, 21 May 2005, [ISO-8859-1] Kövesdán Gábor wrote: Hello there, there is a strange thing FreeBSD 5.3 randomly frogets some of my users. Sometimes I see in the first column of the ps aux output the uid number instead of the login name, but next when I run it, there is the login name. Besides, I tried to chown a directory to an existing user, but the I get an error message, that there wasn't such user. What are you using for user lookups? Are you using nss_ldap or something other than the default 'files' lookup? Can you post the contents of /etc/nsswitch.conf? I'd also check your master.passwd file for any syntax errors or odd characters and then force a rebuild with: pwd_mkdb -p /etc/master.passwd as root. I immediately checked passwd, group and master.passwd files in /etc but the entry for that user was present there. The pw userdel was unable to delete that user, so I had to manually remove it from those three files and create it again. It worked then, but a bit later there was the same result. I'm quite annoyed now. This state isn't safe enough, I have to do something to get around with this. Do You have similar experiences? Or do You now some kinda workaround? Cheers, Gábor Kövesdán ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 forgets some of my users
Thanks for your suggestion. I use 'files' lookup. As You wrote I checked the syntax with pwd_mkdb -C /etc/passwd' and it returned nothing. Then I did a rebuild with -p, and now it seems to be okay, the two accounts that had gone away are working now. Anyway I haven't changed the nsswitch.conf, I have the default one: [EMAIL PROTECTED] less /etc/nsswitch.conf group: compat group_compat: nis hosts: files dns networks: files passwd: compat passwd_compat: nis shells: files Cheers, Gábor Kövesdán What are you using for user lookups? Are you using nss_ldap or something other than the default 'files' lookup? Can you post the contents of /etc/nsswitch.conf? I'd also check your master.passwd file for any syntax errors or odd characters and then force a rebuild with: pwd_mkdb -p /etc/master.passwd as root. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nForce 4, SATA Drive only runs at UDMA33?
On Fri, 20 May 2005, alan bryan wrote: --- Doug White [EMAIL PROTECTED] wrote: Can you post the output of pciconf -lv? The nForce IDE controller is properly detected, but it looks like there's another one in the system. Looking at the spec for the system it may be the proprietary nVidia RAID controller. The pciconf output should help us identify if thats the issue. FYI: RAID features are disabled in the BIOS, I'm just trying to get a single SATA drive to work at full speed. The other drive in this system is IDE and that seems to be working at proper speed. Thanks for the help! I guess turning off the RAID converts the chips into standard SATA controllers. I'll have to look into that. An nForce 4 machine recently appeared at work, so I'll see what I can get it to do. [EMAIL PROTECTED]:6:0: class=0x01018a card=0x50361297 chip=0x005310de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' class= mass storage subclass = ATA [EMAIL PROTECTED]:7:0: class=0x010185 card=0x50361297 chip=0x005410de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' class= mass storage subclass = ATA [EMAIL PROTECTED]:8:0: class=0x010185 card=0xcb8410de chip=0x005510de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' class= mass storage subclass = ATA It looks like sos added support for atapci1 and 2 in this listing in the ATAmkIII patchset. While that patchset is in -CURRENT you'll have to apply the -stable patches yourself. Search the list archives for the location, soren posts it now and again. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless boot problem
On Sat, 21 May 2005, [ISO-8859-2] S³awek ¯ak wrote: On 5/20/05, Doug White [EMAIL PROTECTED] wrote: Please try to avoid sending your message bodies base64 encoded :) My mail client got really confused by it and didn't quote the message properly. Also stripping hackers cc:. I'd like to, but Gmail doesn't offer this option. Sorry :( On Thu, 19 May 2005, [ISO-8859-2] Sawek ak wrote: Hi, I have a problem with booting Dell 2850 over network. The machine reads kernel over net, boots upto mounting / from NFS and then crashes. What is the NFS server? It seems to think the NFS handle we pulled the kernel with is no longer valid. FreeBSD 5.3/5.4-STABLE. Hm ... dunno then ... does the server complain about the client at all in the log? Does PXE and the system itself end up pulling different IP addresses? No. The IP is the same. dunno ... -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_5 panic
On Sat, 21 May 2005, Robin P. Blanchard wrote:
# uname -a
FreeBSD robinpb.homeip.net 5.4-STABLE FreeBSD 5.4-STABLE #0: Tue May 17
00:30:47 EDT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/fastipsec i386
# kgdb kernel.debug /usr/local/var/adm/crash/vmcore.44
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd.
#0 doadump () at pcpu.h:160
160 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) bt full
#0 doadump () at pcpu.h:160
No locals.
#1 0xc04dd58c in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
first_buf_printf = 1
#2 0xc04ddccd in panic (fmt=0xc066e594 %s) at
/usr/src/sys/kern/kern_shutdown.c:566
bootopt = 260
newpanic = 0
buf = page fault, '\0' repeats 245 times
can you try to fish the trap output from msgbuf? That or use dmesg's -N
and -M options to extract it from the crashdump.
#3 0xc0641e92 in trap_fatal (frame=0xc7ac0bc8, eva=36) at
/usr/src/sys/i386/i386/trap.c:817
code = 16
type = 12
ss = 16
esp = 0
softseg = {ssd_base = 0, ssd_limit = 1048575, ssd_type = 27, ssd_dpl
= 0, ssd_p = 1,
ssd_xx = 0, ssd_xx1 = 0, ssd_def32 = 1, ssd_gran = 1}
#4 0xc0642535 in trap (frame=
{tf_fs = 24, tf_es = -1066598384, tf_ds = -1066532848, tf_edi =
-1053916800, tf_esi = -1049515008, tf_ebp = -945025988, tf_isp = -945026060,
tf_ebx = -1053916800, tf_edx = -1053937024, tf_ecx = 56, tf_eax = 0,
tf_trapno = 12, tf_err = 0, tf_eip = -1068480504, tf_cs = 8, tf_eflags =
65683, tf_esp = -1053914880, tf_ss = 582}) at
/usr/src/sys/i386/i386/trap.c:255
p = (struct proc *) 0xc12e754c
sticks = 3241036032
i = 0
ucode = 0
type = 12
code = 0
eva = 36
#5 0xc062da3a in calltrap () at /usr/src/sys/i386/i386/exception.s:140
No locals.
#6 0x0018 in ?? ()
No symbol table info available.
#7 0xc06d0010 in ipq ()
No symbol table info available.
#8 0xc06e0010 in sc_buffer.3 ()
No symbol table info available.
#9 0xc12e8180 in ?? ()
No symbol table info available.
#10 0xc171ac00 in ?? ()
No symbol table info available.
#11 0xc7ac0c3c in ?? ()
No symbol table info available.
#12 0xc7ac0bf4 in ?? ()
No symbol table info available.
#13 0xc12e8180 in ?? ()
No symbol table info available.
#14 0xc12e3280 in ?? ()
No symbol table info available.
#15 0x0038 in ?? ()
No symbol table info available.
#16 0x in ?? ()
No symbol table info available.
#17 0x000c in ?? ()
No symbol table info available.
#18 0x in ?? ()
No symbol table info available.
#19 0xc0504808 in turnstile_wait (ts=0xc12e3280, lock=0xc06d022c,
owner=0xc171ac00)
at /usr/src/sys/kern/subr_turnstile.c:243
tc = (struct turnstile_chain *) 0xc06cb770
td1 = (struct thread *) 0xc12e8180
#20 0xc04d2b7f in _mtx_lock_sleep (m=0xc06d022c, td=0xc12e8180, opts=0,
file=0x0, line=0)
at /usr/src/sys/kern/kern_mutex.c:552
ts = (struct turnstile *) 0x0
owner = (struct thread *) 0xc171ac00
v = 0
#21 0xc058a592 in tcp_isn_tick (xtp=0x0) at
/usr/src/sys/netinet/tcp_subr.c:1380
projected_offset = 0
#22 0xc04ed069 in softclock (dummy=0x0) at
/usr/src/sys/kern/kern_timeout.c:279
c_func = (void (*)(void *)) 0xc058a4d0 tcp_isn_tick
c_arg = (void *) 0x0
c_flags = 14
c = (struct callout *) 0x0
bucket = (struct callout_tailq *) 0xc39ba4a8
steps = 14
depth = 2
mpcalls = 2
gcalls = 0
wakeup_cookie = 14
#23 0xc04c460a in ithread_loop (arg=0xc12fd500) at
/usr/src/sys/kern/kern_intr.c:547
ih = (struct intrhand *) 0xc12e2c80
p = (struct proc *) 0xc12e754c
count = 0
warming = 5000
warned = 0
#24 0xc04c32c2 in fork_exit (callout=0xc04c4550 ithread_loop, arg=0x0,
frame=0x0)
at /usr/src/sys/kern/kern_fork.c:791
p = (struct proc *) 0xc12e754c
#25 0xc062da9c in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:209
No locals.
(kgdb)
---
Robin P. Blanchard
Systems Integration Specialist
Georgia Center for Continuing Education
fon: 706.542.2404 - fax: 706.542.6546
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Doug White|
Re: Highpoint HPT371 support (kern/59624)
On Sun, 22 May 2005, Oliver Fromme wrote: Why is kern/59624 still open? It's about 1,5 years old. Would someone please commit it? Or, if it cannot be commited, please tell me why. If any information is missing (pcicon -lv output, verbose dmesg or whatever), I'd be happy to provide it. You may want to track down Doug Ambrisko, who has a big stack of ata patches he's been carting around. I don't know if he committed that set or not. RELENG_4 is pretty much dead development-wise -- there will be no more 4.x releases -- so finding someone to commit this for you will be difficult. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can't assign requested address with ntpd on 5-STABLE
On Sun, 22 May 2005, Richard Coleman wrote: On 5-STABLE, when I try to start ntpd, I get the following error: bind() fd 7, family 28, port 123, addr fe80:1::2a0:c9ff:fec8:ea25, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address I've used netstat to check and nothing else is on that port (other than sshd, there is nothing else on the box). This is normal; its trying to bind to the ipv6 address and you probably don't have one defined or have ipv6 disabled. It can be safely ignored. I think on later -STABLE its been disabled. Unless you _want_ to bind to the v6 address :) -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell PowerEdge 1855
On Sun, 22 May 2005, Danny Braniss wrote: Hi Doug, Sorry for taking so long to reply on this, been on 3 weeks leave... On Fri, 8 Apr 2005, Doug White wrote: On Wed, 6 Apr 2005, Carl Makin wrote: The boot sequence will hang if the USB drive is attached at boot. There It seems to be acting like Uthe USB controller isn't getting interrupts. Does the problem recur on the installed system? Yes it did however that chassis and the servers were a test loaner and have been returned. We have decided to go with the 1855 though (our windows guy was *very* enthusiastic about them) and when they arrive I'll run the tests you suggested. Thanks! so now i'm testing one too :-), any nice things to say about this blade? while trying out the scsi the blade panics :-) and as to cpu/memory power, it seems to be slower than the pe-1750 danny nothing like talking to oneself :-) i disabled the mirrowing, and now the disk io is nice, and more importanly, the system does not panic, i guess the mpt/(aka da0: DELL VIRTUAL DISK IM 1998) needs some work still :-) The mpt driver has some issues. I have an IBM machine that freaks out similiarly if the integrated mirroring is enabled. However IM works properly on other machines, so YMMV :) -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 forgets some of my users
On Sun, 22 May 2005, [ISO-8859-1] Kövesdán Gábor wrote: Thanks for your suggestion. I use 'files' lookup. As You wrote I checked the syntax with pwd_mkdb -C /etc/passwd' and it returned nothing. Then I did a rebuild with -p, and now it seems to be okay, the two accounts that had gone away are working now. Okay, perhaps the password database files had become corrupted. Anyway I haven't changed the nsswitch.conf, I have the default one: [EMAIL PROTECTED] less /etc/nsswitch.conf group: compat group_compat: nis hosts: files dns networks: files passwd: compat passwd_compat: nis shells: files Looks right. A database problem would make sense. Cheers, Gábor Kövesdán What are you using for user lookups? Are you using nss_ldap or something other than the default 'files' lookup? Can you post the contents of /etc/nsswitch.conf? I'd also check your master.passwd file for any syntax errors or odd characters and then force a rebuild with: pwd_mkdb -p /etc/master.passwd as root. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
cvsup server and firewall, new ports involved?
i used to cvsup on a server with ipfw firewall and had port 5999 open on this box therefore. Recently cvsup only worked when the firewall was down. Do i need to allow more, i.e. finger etc? -- Fritz Heinrichmeyer FernUniversitt, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup server and firewall, new ports involved?
On Sun, May 22, 2005 at 09:46:07PM +0200, Fritz Heinrichmeyer wrote: i used to cvsup on a server with ipfw firewall and had port 5999 open on this box therefore. Recently cvsup only worked when the firewall was down. Do i need to allow more, i.e. finger etc? Nothing has changed.. Kris pgpnVLKxDDzDJ.pgp Description: PGP signature
Making release with EXTSRC tag
Hello, I'm about to build an own install disc from 5.3-RELEASE-p15 but I don't want to mirror the whole CVS repo. I have my RELENG_5_3 source tree in /usr/src and according to this I edited my /usr/src/release/Makefile. I set the EXTSRC macro to /usr/src and I did a 'make buildworld' to fill /usr/obj with the system binariesand then I changed to /usr/src/release directory and I typed: 'make MAKE_ISOS=YES MAKE_FLOPPIES=YES CVSROOT=/usr/src release'. I had to set CVSROOT macro, because the Makefile requires it even if I use EXTSRC and do not want to checkout anything. The release process stopped with this: if [ -f /etc/resolv.conf ]; then cp -p /etc/resolv.conf /home/tux/release/etc; fi rm -rf /home/tux/release/usr/src cd /home/tux/release/usr cp -R -H /usr/src src rm -rf /home/tux/release/usr/ports cd /home/tux/release/usr cvs -R -d /usr/src co -P ports cvs [checkout aborted]: /usr/src/CVSROOT: No such file or directory *** Error code 1 Stop in /usr/src/release. Do You have any experience with this? What can I do now? Btw, I uploaded the Makefile: http://tux.t-hosting.hu/Makefile Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: wi0 is always status: no carrier
On Friday 20 May 2005 10:20 pm, John Baldwin wrote: I have a patch to make the PIR code trust the BIOS in this case over the $PIR table that you can test if you want. Actually, I committed the patch finally a while ago. It is rev 1.117 in HEAD. It should backport to 5.x directly. Try that and see if it fixes your problem. I wiped the drive and started over with a new install. Then, I applied your patch and rebooted into the new kernel. My dmesg output was identical between the two kernels (save for the normal little things like minor skew in clock rates). Pardon my ignorance, but should I be somehow requesting that my cbb device get bound to IRQ 11 instead of 10? There's no line containing cbb in /boot/device.hints; should I add one? -- Kirk Strauser pgpvNLWdUrcKr.pgp Description: PGP signature
FreeBSD and ProPolice Smashing Stack Protector
I find that any application which uses libpthread will not work. That include named, nslookup, dig. If you have find any work stack protector for freebsd 5.4, please share with me. Ming ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
