cpu frequency on 6.0
Dear all! I'd like to know, prior to install upcoming 6.0, about putting cpu into cooler mo- de. On 5.4 and amd64 2800+ cpu (754, 0.13) with "acpi_ppc", it works fine and temperature is just over 30. Could I do the same with "device cpufreq" and "powerd_enable"? Also, is it possible to tune celeron M processor (1400, says it has "stepping=5") the same way? Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 release date and stability
"Brett Glass" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't show a projected date for the finished product. How close is it? We are (believe it or not) still running and building production servers with 4.11, and would love to move to 6.0 (at least for uniprocessor systems; we may wait for 6.1 for SMP) if it is sufficiently stable and performs adequately. We're running our own tests on RC1, but don't have a lot of spare servers to try it on. So, it's worth asking: How stable is RC1 turning out to be on uniprocessor platforms? On SMP platforms? How is network and disk performance relative to 4.11? (When we tested 5.x, both network and file system performance were worse than that of 4.11.) With what known problems is 6.0 likely to ship, and of these which are likely to impact uniprocessor systems? Are any "showstopper" bugs merely being worked around for release? And, again, when is the likely release date? --Brett Glass Welp, it's in the RC stage, and I've not seen any reports of massive issues, so I imagine they'll move it through fairly quickly. For what it's worth, on UP, my 386 (stop laughing) is showing twice the inbound and outbound tcp throughput across multiple apps compared to 4.11. Disk throughput is slightly higher, but nothing super impressive. If 6.0 can show gains on a 386, that tells me there is some actual merit to the changes. Joshua Coombs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 release date and stability
At 06:34 PM 10/15/2005, David Syphers wrote: >http://www.freebsd.org/releases/6.0R/todo.html > >Linked to from the schedule page... Been there. Want to get folks' opinions, and also more detail than is likely to appear on th epage. --Brett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is rcorder working under /usr/local/etc/rc.d?
On Sun, 16 Oct 2005 04:42, Lefteris Tsintjelis wrote: > I am getting all these "no provider" and rcorder doesn't seem to > work properly under /usr/local/etc/rc.d. Services seem to start > alphabetically and not in the right order specified. The keywords > REQUIRE, PROVIDE, BEFORE and KEYWORD seem to be ignored. Services > like SERVERS, NETWORKING, LOGIN, etc, are all provided within > /etc/rc.d. > > rcorder /usr/local/etc/rc.d/* I believe rcorder is not used to start stuff in /usr/local/etc/rc.d (unfortunately). -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgplfHBeOjAkw.pgp Description: PGP signature
Re: 6.0 release date and stability
On Saturday 15 October 2005 04:46 pm, Brett Glass wrote: > With what known problems > is 6.0 likely to ship, and of these which are likely to impact uniprocessor > systems? Are any "showstopper" bugs merely being worked around for release? http://www.freebsd.org/releases/6.0R/todo.html Linked to from the schedule page... -David -- "What's the good of having mastery over cosmic balance and knowing the secrets of fate if you can't blow something up?" -Terry Pratchett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.0 release date and stability
The release schedule for FreeBSD 6.0, on the FreeBSD Web site, doesn't show a projected date for the finished product. How close is it? We are (believe it or not) still running and building production servers with 4.11, and would love to move to 6.0 (at least for uniprocessor systems; we may wait for 6.1 for SMP) if it is sufficiently stable and performs adequately. We're running our own tests on RC1, but don't have a lot of spare servers to try it on. So, it's worth asking: How stable is RC1 turning out to be on uniprocessor platforms? On SMP platforms? How is network and disk performance relative to 4.11? (When we tested 5.x, both network and file system performance were worse than that of 4.11.) With what known problems is 6.0 likely to ship, and of these which are likely to impact uniprocessor systems? Are any "showstopper" bugs merely being worked around for release? And, again, when is the likely release date? --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager problem
Carl Gustavsson wrote: Owe Jørgensen wrote: I recently installed FreeBSD on a Compaq ProLiant 350 and I experienced similar problems. I urge you to take a look into the BIOS/Firmware on the Motherboard. There you will have an option called Boot Device Order. Make sure that the SCSI controller channel with that system disk is set as the first boot device. Then you set up your OS to be of type Other (in BIOS). Save and exit the BIOS. From now on, you stay away from the BIOS. NOTE: You might want to disconnect ALL ide-disks (and CDROMs if you have a SCSI cdrom) if you are reinstalling. Finish the installation, and power down. Reconnect all IDE-devices, and boot up again. Continue to format and arrange the ide-drives as desired. Then install src distribution, recompile kernel and reboot. Good luck, and remember to drink a lot of coffee. ;-) Owe Jørgensen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" Hi, The problem is that there's not an option to select the scsi-controller as first boot device. I can boot on the scsi-disc but only if i don't have any IDE-discs in it. If I put in IDE-discs it tries to boot to the first IDE-disc. The BIOS is very limited in the ProLiant 400. FreeBSD is already installed on the machine and I don't need to reinstall it. The problem is only that it won't boot to the scsi disc if I dont write "1:da(0,a)/boot/loader" at the boot prompt every time i want to boot it. So I want the boot manager to boot to "1:da(0,a)/boot/loader" as default. / Carl Gustavsson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" Sorry for the late reply, but a cute lady tied me up for some hours ;-) this, if using english as the language in BIOS, should be located under the advanced menu. if not, then you can set the partitions on the IDE disks as not bootable. This can be done through sysinstall(8) and sysinstall's slice editor. When exiting the slice editor, remember to choose NO BOOTLOADER as the bootloader for the IDE disks. Then use the slice editor on the SCSI disk, and quit without doing any modifications to it, other that setting it bootable if nescessary. THEN choose the appropriate bootloader for the SCSI disk (I would choose the middle one (can't remember the name), since it will not prompt for any action during the boot process, which may be a good behaviour if you are having this computer running as some sort of server). Have fun, and don't drink too much coffee now ;-) Owe Jørgensen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager problem
Carl Gustavsson wrote: Hi, The problem is that there's not an option to select the scsi-controller as first boot device. I can boot on the scsi-disc but only if i don't have any IDE-discs in it. If I put in IDE-discs it tries to boot to the first IDE-disc. The BIOS is very limited in the ProLiant 400. FreeBSD is already installed on the machine and I don't need to reinstall it. The problem is only that it won't boot to the scsi disc if I dont write "1:da(0,a)/boot/loader" at the boot prompt every time i want to boot it. So I want the boot manager to boot to "1:da(0,a)/boot/loader" as default. / Carl Gustavsson Have you tried another boot loader like GAG? I found it easy to install and use. I have it installed on a floppy with all my OS's config'd so I can either boot via the floppy or use the floppy to install it on the hard disk without any further configuration. http://gag.sourceforge.net Hope this helps Jayton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is rcorder working under /usr/local/etc/rc.d?
On 2005-10-16 00:41, Lefteris Tsintjelis <[EMAIL PROTECTED]> wrote: > Giorgos Keramidas wrote: > >% flame:/home/keramida$ rcorder /etc/rc.d/* /usr/local/etc/rc.d/* >/dev/null > >% rcorder: Circular dependency on provision `mountcritremote' in file > >`/etc/rc.d/newsyslog'. > >% rcorder: Circular dependency on provision `mountcritremote' in file > >`/etc/rc.d/syslogd'. > > Gia sou Giorgo kai pali, Hehehe, "geia" :) > That certainly fixes just about all of the "no providers" but the start up > rcorder problem remains. To be more specific, I specify for a service this: > > # REQUIRE: mysql > > This service however still fails to start after MySQL and keeps on starting > right before it. Hmm, that's odd. Can I see the dependency lines of the two scripts and the output of rcorder? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
testers wanted for 5.4-STABLE sysctl kern.proc patch
The patch below is the 5.4-STABLE version of a patch that was recently committed to HEAD and 6.0-BETA5 to fix locking problems in the kern.proc sysctl handler that could cause panics or deadlocks. It has already been tested by myself and one other person in 5.4-STABLE, but I think it deserves wider testing before I commit it. Testing on SMP systems, while running threaded applications, and on systems that have experienced panics in the existing code is of the most interest. Also be on the lookout for any regressions, such as incorrect data being returned. Index: sys/kern/kern_proc.c === RCS file: /home/ncvs/src/sys/kern/kern_proc.c,v retrieving revision 1.215.2.6 diff -u -r1.215.2.6 kern_proc.c --- sys/kern/kern_proc.c22 Mar 2005 13:40:23 - 1.215.2.6 +++ sys/kern/kern_proc.c12 Oct 2005 19:13:14 - @@ -72,6 +72,8 @@ static void doenterpgrp(struct proc *, struct pgrp *); static void orphanpg(struct pgrp *pg); +static void fill_kinfo_proc_only(struct proc *p, struct kinfo_proc *kp); +static void fill_kinfo_thread(struct thread *td, struct kinfo_proc *kp); static void pgadjustjobc(struct pgrp *pgrp, int entering); static void pgdelete(struct pgrp *); static int proc_ctor(void *mem, int size, void *arg, int flags); @@ -601,33 +603,22 @@ } } #endif /* DDB */ -void -fill_kinfo_thread(struct thread *td, struct kinfo_proc *kp); /* - * Fill in a kinfo_proc structure for the specified process. + * Clear kinfo_proc and fill in any information that is common + * to all threads in the process. * Must be called with the target process locked. */ -void -fill_kinfo_proc(struct proc *p, struct kinfo_proc *kp) -{ - fill_kinfo_thread(FIRST_THREAD_IN_PROC(p), kp); -} - -void -fill_kinfo_thread(struct thread *td, struct kinfo_proc *kp) +static void +fill_kinfo_proc_only(struct proc *p, struct kinfo_proc *kp) { - struct proc *p; struct thread *td0; - struct ksegrp *kg; struct tty *tp; struct session *sp; struct timeval tv; struct ucred *cred; struct sigacts *ps; - p = td->td_proc; - bzero(kp, sizeof(*kp)); kp->ki_structsize = sizeof(*kp); @@ -685,7 +676,8 @@ kp->ki_tsize = vm->vm_tsize; kp->ki_dsize = vm->vm_dsize; kp->ki_ssize = vm->vm_ssize; - } + } else if (p->p_state == PRS_ZOMBIE) + kp->ki_stat = SZOMB; if ((p->p_sflag & PS_INMEM) && p->p_stats) { kp->ki_start = p->p_stats->p_start; timevaladd(&kp->ki_start, &boottime); @@ -704,71 +696,6 @@ kp->ki_nice = p->p_nice; bintime2timeval(&p->p_runtime, &tv); kp->ki_runtime = tv.tv_sec * (u_int64_t)100 + tv.tv_usec; - if (p->p_state != PRS_ZOMBIE) { -#if 0 - if (td == NULL) { - /* XXXKSE: This should never happen. */ - printf("fill_kinfo_proc(): pid %d has no threads!\n", - p->p_pid); - mtx_unlock_spin(&sched_lock); - return; - } -#endif - if (td->td_wmesg != NULL) { - strlcpy(kp->ki_wmesg, td->td_wmesg, - sizeof(kp->ki_wmesg)); - } - if (TD_ON_LOCK(td)) { - kp->ki_kiflag |= KI_LOCKBLOCK; - strlcpy(kp->ki_lockname, td->td_lockname, - sizeof(kp->ki_lockname)); - } - - if (p->p_state == PRS_NORMAL) { /* XXXKSE very approximate */ - if (TD_ON_RUNQ(td) || - TD_CAN_RUN(td) || - TD_IS_RUNNING(td)) { - kp->ki_stat = SRUN; - } else if (P_SHOULDSTOP(p)) { - kp->ki_stat = SSTOP; - } else if (TD_IS_SLEEPING(td)) { - kp->ki_stat = SSLEEP; - } else if (TD_ON_LOCK(td)) { - kp->ki_stat = SLOCK; - } else { - kp->ki_stat = SWAIT; - } - } else { - kp->ki_stat = SIDL; - } - - kg = td->td_ksegrp; - - /* things in the KSE GROUP */ - kp->ki_estcpu = kg->kg_estcpu; - kp->ki_slptime = kg->kg_slptime; - kp->ki_pri.pri_user = kg->kg_user_pri; - kp->ki_pri.pri_class = kg->kg_pri_class; - - /* Things in the thread */ - kp->ki_wchan = td->td_wchan; - kp->ki_pri.pri_level = td->td_priority; - kp->ki_pri.pri_native = td->td_base_pri; - kp->ki_lastcpu = td->td_lastcpu; - kp->ki_oncpu = td->td_
Re: Is rcorder working under /usr/local/etc/rc.d?
Giorgos Keramidas wrote: [...] These look like stuff that is "provided" by /etc/rc.d/* scripts. Try including all the scripts in the rcorder command line: % flame:/home/keramida$ rcorder /usr/local/etc/rc.d/* >/dev/null % rcorder: file `/usr/local/etc/rc.d/samba.sh' is before unknown provision `DAEMON' % rcorder: requirement `named' in file `/usr/local/etc/rc.d/samba.sh' has no providers. % rcorder: requirement `SERVERS' in file `/usr/local/etc/rc.d/samba.sh' has no providers. % rcorder: requirement `NETWORKING' in file `/usr/local/etc/rc.d/samba.sh' has no providers. % rcorder: requirement `ldconfig' in file `/usr/local/etc/rc.d/perforce.sh.sample' has no providers. % rcorder: requirement `ldconfig' in file `/usr/local/etc/rc.d/mysql.sh' has no providers. % rcorder: requirement `ldconfig' in file `/usr/local/etc/rc.d/000.pkgtools.sh' has no providers. % flame:/home/keramida$ rcorder /etc/rc.d/* /usr/local/etc/rc.d/* >/dev/null % rcorder: Circular dependency on provision `mountcritremote' in file `/etc/rc.d/newsyslog'. % rcorder: Circular dependency on provision `mountcritremote' in file `/etc/rc.d/syslogd'. Gia sou Giorgo kai pali, That certainly fixes just about all of the "no providers" but the start up rcorder problem remains. To be more specific, I specify for a service this: # REQUIRE: mysql This service however still fails to start after MySQL and keeps on starting right before it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is rcorder working under /usr/local/etc/rc.d?
On 2005-10-15 22:12, Lefteris Tsintjelis <[EMAIL PROTECTED]> wrote: > I am getting all these "no provider" and rcorder doesn't seem to work > properly under /usr/local/etc/rc.d. Services seem to start > alphabetically and not in the right order specified. The keywords > REQUIRE, PROVIDE, BEFORE and KEYWORD seem to be ignored. Services like > SERVERS, NETWORKING, LOGIN, etc, are all provided within /etc/rc.d. > > rcorder /usr/local/etc/rc.d/* > > rcorder: requirement `SERVERS' in file `squid.sh' has no providers. > rcorder: requirement `NETWORKING' in file `squid.sh' has no providers. > rcorder: requirement `DAEMON' in file `snmptrapd.sh' has no providers. [...] These look like stuff that is "provided" by /etc/rc.d/* scripts. Try including all the scripts in the rcorder command line: % flame:/home/keramida$ rcorder /usr/local/etc/rc.d/* >/dev/null % rcorder: file `/usr/local/etc/rc.d/samba.sh' is before unknown provision `DAEMON' % rcorder: requirement `named' in file `/usr/local/etc/rc.d/samba.sh' has no providers. % rcorder: requirement `SERVERS' in file `/usr/local/etc/rc.d/samba.sh' has no providers. % rcorder: requirement `NETWORKING' in file `/usr/local/etc/rc.d/samba.sh' has no providers. % rcorder: requirement `ldconfig' in file `/usr/local/etc/rc.d/perforce.sh.sample' has no providers. % rcorder: requirement `ldconfig' in file `/usr/local/etc/rc.d/mysql.sh' has no providers. % rcorder: requirement `ldconfig' in file `/usr/local/etc/rc.d/000.pkgtools.sh' has no providers. % flame:/home/keramida$ rcorder /etc/rc.d/* /usr/local/etc/rc.d/* >/dev/null % rcorder: Circular dependency on provision `mountcritremote' in file `/etc/rc.d/newsyslog'. % rcorder: Circular dependency on provision `mountcritremote' in file `/etc/rc.d/syslogd'. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Is rcorder working under /usr/local/etc/rc.d?
I am getting all these "no provider" and rcorder doesn't seem to work properly under /usr/local/etc/rc.d. Services seem to start alphabetically and not in the right order specified. The keywords REQUIRE, PROVIDE, BEFORE and KEYWORD seem to be ignored. Services like SERVERS, NETWORKING, LOGIN, etc, are all provided within /etc/rc.d. rcorder /usr/local/etc/rc.d/* rcorder: requirement `SERVERS' in file `squid.sh' has no providers. rcorder: requirement `NETWORKING' in file `squid.sh' has no providers. rcorder: requirement `DAEMON' in file `snmptrapd.sh' has no providers. rcorder: requirement `DAEMON' in file `snmpd.sh' has no providers. rcorder: requirement `LOGIN' in file `sa-spamd.sh' has no providers. rcorder: requirement `LOGIN' in file `rsyncd.sh' has no providers. rcorder: requirement `SERVERS' in file `radiusd.sh' has no providers. rcorder: requirement `NETWORKING' in file `radiusd.sh' has no providers. rcorder: requirement `NETWORKING' in file `pfspamd.sh' has no providers. rcorder: requirement `SERVERS' in file `mysql-server.sh' has no providers. rcorder: requirement `NETWORKING' in file `mysql-server.sh' has no providers. rcorder: requirement `DAEMON' in file `courier-authdaemond.sh' has no providers. rcorder: requirement `LOGIN' in file `courier-imap-pop3d.sh' has no providers. rcorder: requirement `LOGIN' in file `courier-imap-pop3d-ssl.sh' has no providers. rcorder: requirement `LOGIN' in file `courier-imap-imapd.sh' has no providers. rcorder: requirement `LOGIN' in file `courier-imap-imapd-ssl.sh' has no providers. rcorder: requirement `SERVERS' in file `apache2.sh' has no providers. rcorder: requirement `NETWORKING' in file `apache2.sh' has no providers. rcorder: requirement `ldconfig' in file `000.pkgtools.sh' has no providers. Am I doing something wrong or is this a problem? Please CC Thnx, Lefteris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager problem
Owe Jørgensen wrote: I recently installed FreeBSD on a Compaq ProLiant 350 and I experienced similar problems. I urge you to take a look into the BIOS/Firmware on the Motherboard. There you will have an option called Boot Device Order. Make sure that the SCSI controller channel with that system disk is set as the first boot device. Then you set up your OS to be of type Other (in BIOS). Save and exit the BIOS. From now on, you stay away from the BIOS. NOTE: You might want to disconnect ALL ide-disks (and CDROMs if you have a SCSI cdrom) if you are reinstalling. Finish the installation, and power down. Reconnect all IDE-devices, and boot up again. Continue to format and arrange the ide-drives as desired. Then install src distribution, recompile kernel and reboot. Good luck, and remember to drink a lot of coffee. ;-) Owe Jørgensen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" Hi, The problem is that there's not an option to select the scsi-controller as first boot device. I can boot on the scsi-disc but only if i don't have any IDE-discs in it. If I put in IDE-discs it tries to boot to the first IDE-disc. The BIOS is very limited in the ProLiant 400. FreeBSD is already installed on the machine and I don't need to reinstall it. The problem is only that it won't boot to the scsi disc if I dont write "1:da(0,a)/boot/loader" at the boot prompt every time i want to boot it. So I want the boot manager to boot to "1:da(0,a)/boot/loader" as default. / Carl Gustavsson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot manager problem
Carl Johan Gustavsson wrote: Hello, I have a Compaq ProLiant 400, that i'm using as a fileserver. (FreeBSD balder.home.swe 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386) It has a scsi-disk (da0) and two ide-disks, ad0 (at ata0-master) and ad2 (at ata1-master). da0 contains the system, ad0 and ad2 is just for storage. The problem is that the bios doesn't allow me to boot directly to da0. I solve this by having a MBR on ad0, the problem is that it tries to find a loader on the ad0 which is wrong, and i get a error message that says "Invalid partition". Then I get a boot-prompt and if i write "1:da(0,a)/boot/loader" it boots correctly. Upon booting i get: F1 FreeBSD F5 Drive 1 Default: F1 Invalid partition FreeBSD/i386 boot Default: 0:ad(0,a)/boot/loader boot: Invalid partition No /boot/loader FreeBSD/i368 boot Default: 0:ad(0,a)/boot/loader boot: 1:da(0,a)/boot/loader(i write this) After this it boots correct. How do i get the bootloader to boot 1:da(0,a)/boot/kernel directly? With regards Carl Gustavsson dmesg: 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-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium III/Pentium III Xeon/Celeron (497.44-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 402653184 (384 MB) avail memory = 384335872 (366 MB) npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0x4400-0x47ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 15.0 on pci0 pci2: on pcib2 sym0: <895> port 0x1000-0x10ff mem 0x4010-0x40100fff,0x4030-0x403000ff irq 10 at device 4.0 on pci2 sym0: No NVRAM, ID 7, Fast-40, SE, parity checking fxp0: port 0x1c00-0x1c1f mem 0x4000-0x400f,0x4050-0x40500fff irq 10 at device 5.0 on pci2 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:50:8b:94:ab:35 pci2: at device 6.0 (no driver attached) pci2: at device 7.0 (no driver attached) pci0: at device 16.0 (no driver attached) isab0: at device 20.0 on pci0 isa0: on isab0 atapci0: port 0x2060-0x206f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 20.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0x2040-0x205f irq 10 at device 20.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 20.3 (no driver attached) orm0: at iomem 0xe-0xe7fff,0xc8000-0xcdfff,0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 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 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounter "TSC" frequency 497435902 Hz quality 800 Timecounters tick every 10.000 msec ad0: 76319MB [155061/16/63] at ata0-master UDMA33 ad2: 190782MB [387621/16/63] at ata1-master UDMA33 acd0: CDROM at ata1-slave PIO4 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) Mounting root from ufs:/dev/da0s1a ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" I recently installed FreeBSD on a Compaq ProLiant 350 and I experienced similar problems. I urge you to take a look into the BIOS/Firmware on the Motherboard. There you will have an option called Boot Device Order. Make sure that the SCSI controller channel with that s
shutdown
Hi ! My laptop (dell inspiron 1150) do nothing when i want to shutdown it from power button. How can i fix this trouble ? FreeBSD dell1.xx 5.4-STABLE FreeBSD 5.4-STABLE #1: Thu Oct 13 16:11:55 MSD 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DELL1KERN5X i386 dell1# cat /var/log/messages | grep acpi|grep butt Oct 14 09:44:52 dell1 kernel: acpi_button0: on acpi0 Oct 14 09:44:52 dell1 kernel: acpi_button1: on acpi0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: application to check cpu / system temp?
I use /sysutils/xmbmon Also works from commandline without X :) -- Xander Jayton Garnett wrote: Hello, Are there any apps/utilities to check the cpu and system temperature? Regards, Jayton ___ 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]"
Boot manager problem
Hello, I have a Compaq ProLiant 400, that i'm using as a fileserver. (FreeBSD balder.home.swe 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386) It has a scsi-disk (da0) and two ide-disks, ad0 (at ata0-master) and ad2 (at ata1-master). da0 contains the system, ad0 and ad2 is just for storage. The problem is that the bios doesn't allow me to boot directly to da0. I solve this by having a MBR on ad0, the problem is that it tries to find a loader on the ad0 which is wrong, and i get a error message that says "Invalid partition". Then I get a boot-prompt and if i write "1:da(0,a)/boot/loader" it boots correctly. Upon booting i get: F1 FreeBSD F5 Drive 1 Default: F1 Invalid partition FreeBSD/i386 boot Default: 0:ad(0,a)/boot/loader boot: Invalid partition No /boot/loader FreeBSD/i368 boot Default: 0:ad(0,a)/boot/loader boot: 1:da(0,a)/boot/loader(i write this) After this it boots correct. How do i get the bootloader to boot 1:da(0,a)/boot/kernel directly? With regards Carl Gustavsson dmesg: 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-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium III/Pentium III Xeon/Celeron (497.44-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 402653184 (384 MB) avail memory = 384335872 (366 MB) npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0x4400-0x47ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 15.0 on pci0 pci2: on pcib2 sym0: <895> port 0x1000-0x10ff mem 0x4010-0x40100fff,0x4030-0x403000ff irq 10 at device 4.0 on pci2 sym0: No NVRAM, ID 7, Fast-40, SE, parity checking fxp0: port 0x1c00-0x1c1f mem 0x4000-0x400f,0x4050-0x40500fff irq 10 at device 5.0 on pci2 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:50:8b:94:ab:35 pci2: at device 6.0 (no driver attached) pci2: at device 7.0 (no driver attached) pci0: at device 16.0 (no driver attached) isab0: at device 20.0 on pci0 isa0: on isab0 atapci0: port 0x2060-0x206f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 20.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0x2040-0x205f irq 10 at device 20.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 20.3 (no driver attached) orm0: at iomem 0xe-0xe7fff,0xc8000-0xcdfff,0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 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 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounter "TSC" frequency 497435902 Hz quality 800 Timecounters tick every 10.000 msec ad0: 76319MB [155061/16/63] at ata0-master UDMA33 ad2: 190782MB [387621/16/63] at ata1-master UDMA33 acd0: CDROM at ata1-slave PIO4 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8678MB (17773524 512 byte sectors: 255H 63S/T 1106C) Mounting root from ufs:/dev/da0s1a ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Broadcom NetXtreme BCM5751M Gigabit Ethernet PCI Express and FreeBSD 4.10 [SOLVED]
On 10/14/05 01:20 Dinesh Nair said the following: has anyone got the above gigabit ethernet working with freebsd 4.10 ? upgrading to 4.11-RELEASE solved the problem. there were more special code handling functions to be added, other than just adding in the PCI IDs into if_bge.c and if_bgereg.h. -- Regards, /\_/\ "All dogs go to heaven." [EMAIL PROTECTED](0 0)http://www.alphaque.com/ +==oOO--(_)--OOo==+ | for a in past present future; do| | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=+ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"